[deleted]
christophe60_fr wroteAs far as I'm concerned, disabling consolekit do not change anything.
That's why I leave Obarun for now (unless you have other ideas). I think I'll go back on a classic Arch. Anyway, thanks again for your help.
Hello christophe60_fr
There is a problem with SDDM that me and eric trying to solve. To be honest it's the worst DM I ever seen.
So, I spent the whole day to find an alternative to this horror and I decided to start with lightdm. I got good results during my work and test and problems with consolekit has disappeared.
If a DM like lightdm it's not a problem for you, then tomorrow morming I will build a new plasma live iso with my today work and test it once again.
Be patient yet a little bit.
THX
christophe60_fr
Oh yes, lightdm is the DM I use with Arch that I just installed (with Xfce4).
So, if you can do something with lightdm rather than with sddm, it's not a problem for me. I'm ready to uninstall Arch (and systemd) and try Obarun again as soon as you think it can run properly.
Sorry to force you to work like beasts :p
[deleted]
Ok, good news, it works. You can make a try with the new
Obarun plasma 2019-05 live iso.
If you want to use it with another DE like JWM, you have at this time to manually configure some files.
Tell me what do you plan to install and I will help you from the beginning to the end.
christophe60_fr
Well, same issue : the system usually stops before lightdm opens.
On the other hand, lightdm is able to get started maybe more often now. But when it doesn't start, to be able to raise Obarun, I have to presse ctrl + Alt + F1 + Del. It becomes complicated...
By the way, I use the Obarun plasma 2019-05 live iso, as suggested, but with xfce4.
[deleted]
Hi christophe60_fr
Are you testing the plasma live iso with virtualbox ? If it's the case you have to select from virtualbox option:
Display > Graphics controller > VBoxVGA and do not check the 3D option.
There is a problem with main Arch kernel but I don't know what's wrong exactly. ( Some users report that tty1 and tty2 take time to appear. To see it quickly, switch multiple time between tty1 and tty2 with CTRL+ALT+F1 and CTRL+ALT+F2. On VM like Virtualbox use ALT+F1 and ALT+F2.)
There is no such problem with a custom kernel.
PS: I'm installation xfce4 to see how everything work with this DE
marianarlt
@ christoph60_fr
Are you sure you're not a victim of
this bug?!
[deleted]
Hi marianrlt.
I'm going to test the fix right now. Thx
marianarlt
In any case, like any other similar "quickly change ttys/do some key strokes" bug regarding linux boot has to do with entropy.
banned_9-26-2021
I tested it in vbox everything is fine. I am using 4.20 and dkms modules. I've been saying since 5.0.1 there is something corky with this kernel.
That tty1/tty2 issue that Eric has alerted in the downloads announcement, is it only evident in virtual machines and with 5.0.xx kernel, or is it happening in hard booting. I've never experienced it in any situation. When I wrote in my blog about the newly released iso images someone commented that this is evidence that Obarun is not a real stable distro but it is only for tinkerers. I have a feeling he is someone from Distrowatch defending it that "obarun doesn't deserve a release announcement". In any case, I too think it is a bad idea to be right there in front page (downloads) if it is an issue particular to hw or vm setup.
Apart from my disliking of plasma it worked perfect with consolekit. I think it is a good move.
[deleted]
Obarun is not a real stable distro
LoL what a good joke. I'm using Obarun since the first day I discovered this distro ( Registered: Jan 30 2018 ) for my daily work, and even the switch/upgrade from s6 to 66 was not a problem.
So for a so-called "unstable" distribution which I never needed to reinstall, it's amazing :D
That tty1/tty2 issue that Eric has alerted in the downloads announcement, is it only evident in virtual machines and with 5.0.xx kernel,
Not only in VM or kernel 5.x. I was affected by this bug with official Arch kernel revision 4.x. But as I said the problem does not occur when you build your own custom kernel and I'm using a custom built kernel.
Nobody else until recently had reported the same issue.
banned_9-26-2021
> So for a so-called "unstable" distribution which I never needed to reinstall, it's amazing big_smile
Me too, sometime Fall 2017, after I had gotten bored with Artix/OpenRC and was searching. I have cloned the original distro, but this is what I use daily for whatever I do. The rest are all test installations of how different distros and installations upgrade and develop.
Debian 7 (mixed with Siduction) till it became old-stable --> Refracta --> Devuan --> Antix --> Manjaro-OpenRC --> Artix OpenRC --> Obarun. I really like void too, but whenever I try to use it I return to Obarun really fast.
Anyway, thousands of people have been looking at Obarun in the past few days just because Smith put the 05 release on that left column of his. Too bad the JWM and 66 announcement never made it there. I only get 100-150 hits a day on my site.
Broken to me means that I boot and get to Openbox and my conkies show I am using more than 150MB of Ram, and 30MB is conkies alone :)
[deleted]
Debian 7 till it became old-stable --> Refracta --> Devuan --> Antix --> Manjaro-OpenRC --> Artix OpenRC --> Obarun.
Mandrake > Gentoo > Funtoo > Void > Obarun.
But I tested them all, ubuntu, fedora, mageia, opensuse, debian, etc...
I followed S6 evolution for a long time, all that was missing was the distro. :)
[deleted]
marianarlt wroteIn any case, like any other similar "quickly change ttys/do some key strokes" bug regarding linux boot has to do with entropy.
I tought that you post here was something related to this bug. That mean and it's my first idea that perhaps this bug has something to do with the graphical card.
I'm using Nvidia with the proprietary driver. Someone else has a same problem with other graphical card ?
marianarlt
I'm not sure if I understand you right on that one. I threw in that comment because of the behavior christophe described (which I know very well but under a very specific non-standard system configuration [EFISTUB]; which after all may be unrelated).
Based on that are you saying that you suspect christophes issue to be GPU related?
As said earlier, I've read a lot of posts regarding this kind of behavior and it's basically always related to random blocking itself out. Sometimes it's remedied by generating extra entropy with haveged, sometimes it is by creating caches, sometimes by generating entropy in the initramfs.
That being said, I'm running my screen on the DVI output of an AMD R7 250X (CAPE VERDE/Southern Island) using the open source AMDGPU driver enabling SI support with a kernel parameter instead of the open source legacy driver RADEON.
The issues I experienced were not different using the RADEON driver though, neither when I used the integrated Intel GPU from my Intel Pentium G3258.
Let's hear what christophe can tell us on that one :)
christophe60_fr
English is not my strong point. So I have trouble following you..
You mean that my concern is related to my graphics card?
inxi :
Graphics:
Device-1: AMD Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
driver: radeon v: kernel
Display: x11 server: X.org 1.20.4 driver: none
resolution: <xdpyinfo missing>
Message: Unable to show advanced data. Required tool glxinfo missing.
Never had a problem until now. And this morning, I was still under Arch and everything was ok.
I still see a clear improvement with lightdm since it opens much more often at first time. But It may be a coincidence, Idon't know.
just now, I changed my lightdm.conf so :
logind-check-graphical=true instead of logind-check-graphical=false. Maybe it helps ?
eric
please @ christophe60_fr follow this thread carefully :
https://forum.obarun.org/viewtopic.php?id=729 and try to apply the changes suggested
[deleted]
Ok, so. I was wrong about this problem related with the graphic card, particularly in my case with an Nvidia proprietary driver. At least that mean Nvidia proprietary driver is no so bad :D
I had a discussion with eric, and part of the problem was related to changes within the kernel and urandom. Not being a kernel guru, I advise you to follow the link recommended by eric.
For my part I intend to quickly release a new live with the latest packages.
PS: I removed the plasma live iso for now. I want to offer you the best of obarun, sorry for the inconvenience.
banned_9-26-2021
I added a note in my article of temporary absence of the plasma-iso but let me know when the new one is up so I can change it again.
christophe60_fr
Do not be angry, guys,
I'll come back to Obarun another day.
For now, I need a 100% operational distro quickly.
Thanks you for everything.
marianarlt
No worries christophe, if you keep having issues then that's totally understandable!
Hope to see you sooner than later :)