https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|openSUSE 12.2 |SUSE Other -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c2 --- Comment #2 from Dr. Werner Fink 2013-03-16 21:21:41 UTC --- Just found a workaround by adding the two lines case "$1" in start) + command -p setconsole /dev/tty1 < /dev/console > /dev/null 2>&1 + command -p chvt --userwait 1 > /dev/null 2>&1 .... this helps a lot as now kdm does its work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c4 --- Comment #4 from Dr. Werner Fink 2013-03-16 21:24:48 UTC --- Created an attachment (id=530057) --> (http://bugzilla.novell.com/attachment.cgi?id=530057) /usr/share/kde4/config/kdm/kdmrc Here we are -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c6 --- Comment #6 from Raymond Wooninck 2013-03-16 21:39:42 UTC --- As that you have the terminals hardcoded in the config (ServerVT=7,8,9,...), did you ever tried to see what happens if you let KDM do the assignments ? (removing that entry from the corresponding 1, 2, 3rd display core settings ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c8 --- Comment #8 from Dr. Werner Fink 2013-03-17 00:06:41 UTC --- Without the two lines it does not work regardless if I remove the ServerVT=7,9,9 lines ... with the two lines it takes only a few seconds longer as it seems that the kdm now starts the X servers with a delay ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c10 --- Comment #10 from Raymond Wooninck 2013-03-17 09:06:11 UTC --- Werner, I don't understand your last comment ? What do you mean with "but the boot process stops as plymouth locks doesn't the all consoles" ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c12 --- Comment #12 from Dr. Werner Fink 2013-03-30 15:50:11 UTC --- Search for Plymouth at http://www.freedesktop.org/wiki/Software/systemd/multiseat -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c13 Stefan Brüns changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.bruens@rwth-aachen.d | |e See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=975079 --- Comment #13 from Stefan Brüns 2013-06-19 11:20:19 UTC --- I have started working on a kdm with proper multiseat support, which is available in my home project: https://build.opensuse.org/package/show?package=kdebase4-workspace&project=home%3AStefanBruens%3Abranches%3AKDE%3ARelease%3A410 Multiseat and Systemd support is only enaybled for 12.3, though. Problems with plymouth / vt switching are most probably due to kdm_plymouth.patch in the kdebase4-workspace package. These problems are still somewhat existent in the current package, will work on it ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c15 Stefan Brüns changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|stefan.bruens@rwth-aachen.d | |e | --- Comment #15 from Stefan Brüns 2013-06-20 07:51:10 UTC --- kdm_plymouth.patch has the following diff for allocateVT: + if (plymouth_has_active_vt ()) { + /* plymouth was displaying a splash screen and has + * terminated leaving it on screen + */ + int vt; + vt = get_active_vt (); + if (vt > 0) { + /* start the X server on the active vt */ + d->serverVT = vt; + return; Normally, it would use reqSrvVT (==ServerVT in kdmrc) or search a unused one itself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c17 --- Comment #17 from Dr. Werner Fink 2013-06-20 10:33:19 UTC --- I've send an SR#180233 which hopefully repairs this ... now the pathc looks like + if (plymouth_has_active_vt ()) { + /* plymouth was displaying a splash screen and has + * terminated leaving it on screen + */ + int vt; + vt = get_active_vt (); + if (vt > 0) { + if (d->reqSrvVT <= 0 || d->reqSrvVT == vt) { + /* start this X server on the active vt */ + d->serverVT = vt; + return; + } + } + } the same on + /* fallback to old/deprecated method */ + } else if ( triggered_to_force_display_on_active_vt() >= 0 ) { + int vt; + vt = get_active_vt(); + if (vt > 0) { + if (d->reqSrvVT <= 0 || d->reqSrvVT == vt) { + d->serverVT = vt; + return; + } + } + } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c19 --- Comment #19 from Dr. Werner Fink 2013-06-24 14:03:21 UTC --- Q: Had the patch worked and if so how about adding this for an update for the package of 12.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c21 Stefan Brüns changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com --- Comment #21 from Stefan Brüns 2013-06-26 07:52:24 UTC --- I have completely reworked the plymouth patch, it should work in any case, see https://bugzilla.redhat.com/show_bug.cgi?id=975079#c11 for details. I has been tested by at least one multiseat user, and I will test it myself later. @Werner: can you test it as well, both with and without explicit ServerVT for the different displays? Testcatalog: 1. Singleseat - X server starts, replaces either plymouth splash screen (quiet case) or the text console (nosplash, ESCape from splash). 2. Static multiseat: all X servers start, each on a different VT, one replaces plymouth/text console 3. Dynamic multiseat: First X server starts as in 1., second server starts and presents greeter on hotplug -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c23 --- Comment #23 from Dr. Werner Fink 2013-06-26 08:11:10 UTC --- Hmmm ... seems to be home:StefanBruens:branches:KDE:Release:410/kdebase4-workspace/kdm_plymouth.patch -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c25 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|werner@suse.com | --- Comment #25 from Dr. Werner Fink 2013-06-26 14:05:47 UTC --- (In reply to comment #21) My configuration [1]:

2. Static multiseat: all X servers start, each on a different VT, one replaces plymouth/text console

does *not* work. After removing the plymouth_quit at start in /etc/init.d/xdm which I've added below `start)' the Xserver's do not crash anymore but now plymouth blocks VT7 and the only key stroke which had worked was Ctrl-Alt-Del to cause a reboot ... if I press then ESC to switch plymouth into background to see the boot messages I was able to access one of the Xserver's Now I've readded the plymouth_quit. [1]: /home/werner> grep -E '[012]-Core|ServerVT' /usr/share/kde4/config/kdm/kdmrc ServerVTs=-7 [X-:0-Core] # Better leave it zero and use ServerVTs. ServerVT=7 [X-:1-Core] ServerVT=8 [X-:2-Core] ServerVT=9 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c27 --- Comment #27 from Dr. Werner Fink 2013-06-27 00:44:01 UTC --- (In reply to comment #26)

What does "the Xserver's do not crash anymore" mean?

Before this change the three Xserver's where started on VT7 which had caused that the Xserver's died and kdm had exit with an error. After this plymouth had stopped normally with the boot process and I was able to do stop the xdm services and the restart it. This was the reason for me to add the plymouth_quit shell function in the start section /etc/init.d/xdm

What I am interested in:

- output of "cat /var/log/messages | grep kdm", i.e. any debug output from kdm - output of "ps aux | grep X", i.e. the arguments the X servers are started with

This will become complicated as plymouth screen is locked and the only command I'm able to do is Ctrl-Alt-Del to trigger a reboot. I do not have network access at home. Maybe I have to add a watch background process in /etc/init.d/xdm to get this information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c29 --- Comment #29 from Dr. Werner Fink 2013-06-27 07:47:50 UTC --- Hmmm ... in /etc/init.d/xdm the shell function plymouth_quit looks like plymouth_quit() { if [ -x /usr/bin/plymouth ]; then plymouth quit plymouth --wait fi } maybe the wait is what is missed in kdm? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c31 --- Comment #31 from Stefan Brüns 2013-06-29 20:42:35 UTC --- Hm, are you sure you were running the last version from my repository - there should be some more debug output, i.e. output of the exit codes from all the queries towards plymouth. Unfortunately, you wont be able to update at the moment, as the repository is already updated to KDE 4.10.5, which will be published next tuesday (most probably). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c33 --- Comment #33 from Stefan Brüns 2013-07-02 17:26:51 UTC --- Ok, I think I know why this was no issue for me - I use the /usr/lib/systemd/systemd-multi-seat-x wrapper which adds "-sharevts". I have changed the plymouth quit calls to "/usr/bin/plymouth quit [--retain-splash] --wait", which should solve the issue. Currently building, please check the changelog of the KDM package to make sure you have the correct version. Should be ready at 20:30 CEST. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c35 --- Comment #35 from Stefan Brüns 2013-07-02 22:57:01 UTC --- Just another question: which mechanism do you use to assign the graphics cards and input devices to the different seats? I assign distinct "seat-<xxx>" tags to the devices using udev rules, and use different layout sections for each seat. The latter is only necessary because one seat has 2 monitors, the other one only 1, otherwise the udev rules would be sufficient. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c37 --- Comment #37 from Dr. Werner Fink 2013-07-03 15:49:39 UTC --- (In reply to comment #33) To which package do you refere ... the https://build.opensuse.org/package/show/home:StefanBruens:branches:KDE:Relea... is broken -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c39 --- Comment #39 from Stefan Brüns 2013-07-03 16:09:43 UTC --- The repository is located at: http://download.opensuse.org/repositories/home:/StefanBruens:/branches:/KDE:... You can check the changelog with rpm: rpm -q --changelog kdm | head -n 30 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c41 --- Comment #41 from Dr. Werner Fink 2013-07-03 20:27:11 UTC --- Created an attachment (id=546720) --> (http://bugzilla.novell.com/attachment.cgi?id=546720) output.log Here the log for the first case from /var/log/warn (not /var/log/messages) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c43 --- Comment #43 from Stefan Brüns 2013-07-03 23:42:37 UTC --- Unfortately, the --wait statement was ineffective because it must be placed before the quit command -> fixed See also the appended plymouth wrapper, which might give some more insight. sudo mv /usr/bin/plymouth{,.bin} sudo cp plymouth_wrapper /usr/bin/plymouth sudo chmod +x /usr/bin/plymouth -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c45 --- Comment #45 from Stefan Brüns 2013-07-10 14:11:03 UTC --- Actually it is the VT handling in the Kernel which broken by lack of design. (Linus Torvalds opion on VT_ACTIVATE/VT_WAITACTIVE: https://bugzilla.redhat.com/show_bug.cgi?id=323501#c3 ) The problem is the kernels behaviour when the foreground (=^active) console is in mode KD_GRAPHICS and the terminal is in control mode VT_AUTO (opposed to VT_PROCESS). In this case the VT_ACTIVATE is silently dropped and VT_WAITACTIVE will hang until: a) another process grabs the active VT and puts it into VT_PROCESS mode, then manual (CTRL-[ALT]-Fx) switching becomes possible again b) VT_ACTIVATE was a noop in the first place The second case is what happens in the typical setup, plymouth is on VT7 and X "switches" to VT7. The behaviour was introduced by this patch from 2007: http://linux.kernel.narkive.com/NadYBuBi/patch-software-suspend-fix-suspend-... This is almost impossible to do correctly. plymouth can no longer listen to any signals for the VT, as it has to close it before the X server can open it, so it must go out of VT_PROCESS mode. Setting KD_TEXT on the other hand the screen will flicker ... I have an idea how to solve this (needs some more work on the KDM plymouth patch, and a small change in plymouth ...) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c47 --- Comment #47 from Dr. Werner Fink 2013-07-12 21:28:53 UTC --- (In reply to comment #46) This does work without the plymouthquit shell command in /etc/init.d/xdm and without the Xorg.multi wrapper script. With the Xorg.multi wrapper script the plymouth is stoppped but the console is not accessible anymore due -sharevts option I guess. The normal case *does* work. Only the screen visible is now vt8 not vt7. I guess that this is caused duethe waiting loop on plymouth: 2013-07-12T23:21:09.006026+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:09.007870+02:00 speedy kdm[1404]: plymouth is active on VT 7, reusing for :0 2013-07-12T23:21:09.009627+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:09.041226+02:00 speedy kdm[1404]: last message repeated 2 times 2013-07-12T23:21:09.041155+02:00 speedy kdm[1404]: plymouth should quit when server starts 2013-07-12T23:21:09.180634+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:09.195668+02:00 speedy kdm[1404]: plymouth should quit when server starts 2013-07-12T23:21:09.199040+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:09.224085+02:00 speedy kdm[1404]: plymouth should quit when server starts 2013-07-12T23:21:09.225958+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:09.239815+02:00 speedy kdm[1404]: plymouth should quit when server starts 2013-07-12T23:21:09.241516+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:09.260398+02:00 speedy kdm[1404]: plymouth should quit when server starts 2013-07-12T23:21:09.262150+02:00 speedy kdm[1404]: plymouth is running [...] 2013-07-12T23:21:11.180887+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:11.197801+02:00 speedy kdm[1404]: plymouth should quit when server starts 2013-07-12T23:21:11.201460+02:00 speedy kdm[1404]: plymouth is running 2013-07-12T23:21:11.227630+02:00 speedy kdm[1404]: plymouth should quit when server starts 2013-07-12T23:21:11.228112+02:00 speedy kdm[1404]: Quitting Plymouth with transition 2013-07-12T23:21:11.271651+02:00 speedy kdm[1404]: Is Plymouth still running? no 2013-07-12T23:21:11.274762+02:00 speedy kdm[1404]: plymouth is NOT running .. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c49 --- Comment #49 from Dr. Werner Fink 2013-07-13 07:35:55 UTC --- (In reply to comment #48) Indeed I see now three times (or three times a flicker to be more correct) a black screen with a clock cursor and then the VT8 is visible. The process table shows: root 2086 0.0 0.1 145344 17904 tty7 Ss+ 09:26 0:01 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0 -auth /var/lib/kdm/AuthFiles/A:0-6J8Jfa root 2950 0.0 0.2 180016 44412 tty9 Ss+ 09:26 0:06 /usr/bin/Xorg -br :2 vt9 -nolisten tcp -novtswitch -layout Seat0.2 -seat seat0 -auth /var/lib/kdm/AuthFiles/A:2-aNtcec root 3228 0.0 0.1 150724 21180 tty8 Ss+ 09:26 0:00 /usr/bin/Xorg -br :1 vt8 -nolisten tcp -novtswitch -layout Seat0.1 -seat seat0 -auth /var/lib/kdm/AuthFiles/A:1-7Dqysb -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c51 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #51 from Wolfgang Bauer 2013-07-22 07:57:30 UTC --- Sorry to say, but something seems to be wrong with this new patch. Since I installed the new kdebase4-workspace package, kdm fails to start on boot on my system (12.3 64bit with KDE 4.10.95 from KDE:Distro:Factory, standard KDM configuration). Last message on screen is "Reached graphical target", I have to press Ctrl+Alt+F1, login in text mode and start kdm manually (init 3, init 5) then it starts up, but on VT8 instead of VT7. And plymouthd keeps running (I still see the bootsplash when I switch to VT7) and it constantly uses 5-6% CPU time, even when I am already logged in to KDE. This also happens if I press ESC during boot to get the boot text messages. Sometimes instead of getting a login screen, the screen even just turns black and not even Ctrl+Alt+Fn works (but I can press Ctrl+Alt+Del to reboot). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c53 Benjamin Brunner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |bbrunner@suse.com InfoProvider| |stefan.bruens@rwth-aachen.d | |e --- Comment #53 from Benjamin Brunner 2013-07-22 12:51:22 CEST --- Wolfgang, thanks for bringing this up. Stefan could you have a look at it, please? I'll block the release for the 12.3 update for the moment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c55 --- Comment #55 from Benjamin Brunner 2013-07-22 14:22:25 CEST --- The package with the fixed plymouth should be in openSUSE:Maintenance:1860. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c57 --- Comment #57 from Stefan Brüns 2013-07-22 13:04:11 UTC --- (In reply to comment #56)

(In reply to comment #55)

...

The package with the fixed plymouth should be in openSUSE:Maintenance:1860.

Yes, that's what I installed. But that didn't change anything for me.

the plymouth fix in openSUSE:Maintenance:1860 only affects "plymouth --quit" without --retain-splash . For unknown reasons the wrong code path if triggered in the replacePlymouth() function in dm.c. I will further investigate, expect more answers tomorrow morning ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c59 --- Comment #59 from Wolfgang Bauer 2013-07-24 18:32:24 UTC --- (In reply to comment #58)

Possible fix is in https://build.opensuse.org/package/rdiff/home:StefanBruens:branches:KDE:Distro:Factory/kdebase4-workspace?opackage=kdebase4-workspace&oproject=KDE%3ADistro%3AFactory&rev=2

I installed that package and it works fine for me now. KDM/X succeeds to start and runs on VT7 as it should. Thank you! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c61 --- Comment #61 from Swamp Workflow Management 2013-07-25 12:04:27 UTC --- openSUSE-RU-2013:1252-1: An update that has one recommended fix can now be installed. Category: recommended (important) Bug References: 809806 CVE References: Sources used: openSUSE 12.3 (src): plymouth-0.8.8_git201211022126-4.10.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c63 --- Comment #63 from Raymond Wooninck 2013-09-27 20:47:24 UTC --- Stephan, The only thing I know is that we accepted the patch that Stefan Bruens created and that patch is part of workspace in 13.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c65 Stefan Brüns changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|stefan.bruens@rwth-aachen.d | |e | Benjamin Brunner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #65 from Stefan Brüns 2014-02-02 21:22:07 CET --- kdebase4-workspace / kdm is fine for 12.3 and 13.1 the plymouth patch was left out for 13.1, see https://build.opensuse.org/request/show/220631 --- Comment #66 from Benjamin Brunner 2014-02-12 11:47:04 CET --- Plymouth update for 13.1 is now released too. I think we can close this bug now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809806 https://bugzilla.novell.com/show_bug.cgi?id=809806#c68 Daniel Spannbauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ds@marco.de --- Comment #68 from Daniel Spannbauer 2014-07-31 09:12:33 UTC --- Any chance to get a fixed package for 12.3 or a patch? I tried to adopt the patch from above to kdm-4.10.0-1.8.1 and start 2 KDMs at boot, but the Xserver on vt7 crashes with [ 4.037] (WW) Falling back to old probe method for vesa [ 4.037] (EE) Screen 0 deleted because of no matching config section. [ 4.037] (II) UnloadModule: "modesetting" [ 4.037] Fatal server error: [ 4.037] Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices [ 4.037] [ 4.037] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 4.037] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 4.037] (EE) When restarting the kdm it works as expected. Updated plymouth-package (plymouth-0.8.8_git201211022126-4.10.1) is also installed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.