August 2018 - openSUSE KDE 3 - openSUSE Mailing Lists

[opensuse-kde3] TW kdm and startx both fail with timeout & crashing drkonqi kicker
by Felix Miata 19 Dec '18

19 Dec '18

Anyone else unable to run KDE3 session on TW? Anyone know how to find out why I see timeouts? I got this two days ago on host big31 and figured it out myself, but now on host p5bse I don't remember how and can't figure it out. :-( # /var/log/kdm.log tail X.Org X Server 1.19.6 Release Date: 2017-12-20 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux p5bse 4.16.12-2-default #1 SMP PREEMPT Fri May 25 18:40:19 UTC 2018 (39c7522) x86_64 Kernel command line: root=LABEL=ostwK4h50 ipv6.disable=1 net.ifnames=0 noresume vga=791 video=1024x768@60 video=1440x900@60 5 Build Date: 17 April 2018 12:00:00PM Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jun 16 22:39:57 2018 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" KCrash: Application 'kdmgreet' crashing... Warning: connect() failed: : No such file or directory KCrash cannot reach kdeinit, launching directly. (II) Server terminated successfully (0). Closing log file. X.Org X Server 1.20.1 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux p5bse 4.17.14-1-default #1 SMP PREEMPT Thu Aug 9 12:44:26 UTC 2018 (dc49b43) x86_64 Kernel command line: root=LABEL=ostwK4h50 ipv6.disable=1 net.ifnames=0 noresume vga=791 video=1024x768@60 video=1440x900@60 5 Build Date: 07 August 2018 12:00:00PM Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 26 14:13:41 2018 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. KCrash: Application 'kdmgreet' crashing... Warning: connect() failed: : No such file or directory KCrash cannot reach kdeinit, launching directly. (II) Server terminated successfully (0). Closing log file. # dmesg | grep splay Aug 26 14:13:23 p5bse kernel: [drm] Radeon Display Connectors Aug 26 14:13:38 p5bse systemd[1]: Starting X Display Manager... Aug 26 14:13:39 p5bse display-manager[922]: /etc/vconsole.conf available Aug 26 14:13:39 p5bse display-manager[922]: KEYMAP: us Aug 26 14:13:39 p5bse display-manager[922]: Command: localectl set-keymap us Aug 26 14:13:39 p5bse display-manager[922]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Aug 26 14:13:40 p5bse display-manager[922]: Starting service kdm..done Aug 26 14:13:40 p5bse systemd[1]: display-manager.service: Can't open PID file /var/run/displaymanager.pid (yet?) after start: No such file or directory Aug 26 14:13:47 p5bse kdm[978]: :0[978]: Abnormal termination of greeter for display :0, code 125, signal 0 Aug 26 14:15:08 p5bse systemd[1]: display-manager.service: Start operation timed out. Terminating. Aug 26 14:15:08 p5bse systemd[1]: display-manager.service: Failed with result 'timeout'. Aug 26 14:15:08 p5bse systemd[1]: Failed to start X Display Manager. # systemctl status display-manager ● display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Sun 2018-08-26 14:15:08 EDT; 14min ago Process: 922 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 2377) CGroup: /system.slice/display-manager.service └─950 /opt/kde3/bin/kdm Aug 26 14:13:40 p5bse display-manager[922]: Starting service kdm..done Aug 26 14:13:40 p5bse systemd[1]: display-manager.service: Can't open PID file /var/run/displaymanager.pid (yet?) after start: No such file or directory Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'SelectedUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:47 p5bse kdm[978]: :0[978]: Abnormal termination of greeter for display :0, code 125, signal 0 Aug 26 14:15:08 p5bse systemd[1]: display-manager.service: Start operation timed out. Terminating. Aug 26 14:15:08 p5bse systemd[1]: display-manager.service: Failed with result 'timeout'. Aug 26 14:15:08 p5bse systemd[1]: Failed to start X Display Manager. # journalctl -b | egrep 'kdm|splay' Aug 26 14:13:23 p5bse kernel: [drm] Radeon Display Connectors Aug 26 14:13:38 p5bse systemd[1]: Starting X Display Manager... Aug 26 14:13:39 p5bse display-manager[922]: /etc/vconsole.conf available Aug 26 14:13:39 p5bse display-manager[922]: KEYMAP: us Aug 26 14:13:39 p5bse display-manager[922]: Command: localectl set-keymap us Aug 26 14:13:39 p5bse display-manager[922]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Aug 26 14:13:40 p5bse display-manager[922]: Starting service kdm..done Aug 26 14:13:40 p5bse systemd[1]: display-manager.service: Can't open PID file /var/run/displaymanager.pid (yet?) after start: No such file or directory Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'SelectedUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:40 p5bse kdm_config[951]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Aug 26 14:13:47 p5bse kdm[978]: :0[978]: Abnormal termination of greeter for display :0, code 125, signal 0 Aug 26 14:15:08 p5bse systemd[1]: display-manager.service: Start operation timed out. Terminating. Aug 26 14:15:08 p5bse systemd[1]: display-manager.service: Failed with result 'timeout'. Aug 26 14:15:08 p5bse systemd[1]: Failed to start X Display Manager. # systemd-analyze blame | head -n12 1min 30.036s display-manager.service 12.877s dev-sda14.device 12.209s lvm2-monitor.service 3.698s systemd-fsck(a)dev-disk-by\x2dlabel-os131h50.service 3.295s kbdsettings.service 3.012s systemd-fsck(a)dev-disk-by\x2dlabel-h50usrlcl.service 2.832s initrd-switch-root.service 2.241s systemd-fsck(a)dev-disk-by\x2dlabel-h50home09.service 2.153s systemd-udevd.service 1.609s systemd-journal-flush.service 1.497s smb.service 1.487s wickedd-auto4.service I looked at big31's bash history and saw a clue in having done zypper -v in libvdpau_nouveau Mesa-dri-nouveau libXvMC_nouveau but that had NVidia gfx, and this has ATI Cedar. So I added Mesa-libva. Next startx try produced segfaults in drkonqi and kicker related to libfontconfig.so. Next I added libvdpau_va_gl1. Next startx produced a flash of Kicker, then back to black screen. Next, libvdpau_trace1, same result. Next, libvdpau_radeonsi, no help. Next, libvdpau_r600, still nada. Next, libXvMC1, no dice. Next, libXvMC_r600, nada. Next, libxcb-xf86dri0, nope. libXfont1, no. libxfonts, wants 8 deps including java, so skipped. libva-glx2, no. :~( All these failures are associated with another new ~/.config/gtkrc* file. Same PC has separate TW installation with Plasma that works as expected. :-p Ideas? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

2 6

[opensuse-kde3] KDE3 session starts Plasma as well
by Julius Schwartzenberg 10 Dec '18

10 Dec '18

Hi, I just added KDE3 to my system with OpenSUSE 42.3. I had been using KDE Plasma 5 on it before. Logging out and relogging with a KDE3 in gave me this: https://schwart6.home.xs4all.nl/kde3-with-plasmabar.png (Two panels, one KDE3 kicker and the Plasma panel.) This does not really make sense I'd say. Is this a bug or should I change something to prevent this? Thanks, Julius -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

7 12

[opensuse-kde3] Why does Updating Libre Office trigger zypper ps -s on kdm_greet?
by David C. Rankin 29 Aug '18

29 Aug '18

All, Here is another "odd" one. Updating 42.3 yesterday, only updates were: The following 15 packages are going to be upgraded: libreoffice libreoffice-base libreoffice-base-drivers-mysql libreoffice-branding-upstream libreoffice-calc libreoffice-calc-extensions libreoffice-draw libreoffice-filters-optional libreoffice-icon-themes libreoffice-impress libreoffice-l10n-en libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-writer (why the hell LO is split into 15 packages is another issue....) Nonetheless, when zypper completed the update it indicated the normal: There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper ps -s' to list these programs. So I checked: $ sudo zypper ps -s The following running processes use deleted files: PID | PPID | UID | User | Command | Service -----+------+-----+------+-----------+-------- 2384 | 1279 | 0 | root | kdm | kdm3 2385 | 2384 | 0 | root | kdm_greet | kdm3 You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. Huh?? Why does upgrading LO trigger a notice to restart kdm_greet? It just seemed strange and unrelated. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

1 0

[opensuse-kde3] Need to move KTeaTime from 'System->Desktop Applet' to 'Utilities->Time' menu
by David C. Rankin 29 Aug '18

29 Aug '18

All (dev/packager) KTeaTime is out of place in kmenu. It is by default put in System->Desktop Applet, but to be consistent it should go in Utilities->Time with the other desktop time functions (KCountdownTimer, etc..) In just the Opposite direction, Kjots, the desktop basket wannabe should come out of Utilites->Time (as it is unreleated) and should go into Utilities->Desktop along with Basket Notepads. Minor changes, I can look up where these need to be set if needed. Off the top of my head I can't recall if this is just a .desktop issue, or a kdebase issue or an individual applications/kteatime issue. I thought I would document it here while it was on my mind (and before I forgot). I know it would be a WON'T FIX if I filed it. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

1 0

[opensuse-kde3] I didn't even know this list existed ....
by Per Jessen 12 Aug '18

12 Aug '18

I'm just trying out KDE3 on Leap15 for the first time. It's fast!. I have not yet sorted out the issue with the dual task manager, but it looks like some auto-start I just need to remove. Is anyone interested in other issues? Observed today - a first start of Konqueror, default site = www.opensuse.org. Complained aboiut the certificate, when I told it to ignore it for this session, it crashed. Repeated attempts only produced repeated crashes. kpatience - unable to start, looks like a crash. -- Per Jessen, Zürich (25.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

4 11

[opensuse-kde3] Leap 15 w/kdm Hang on shutdown (old issue back?)
by David C. Rankin 11 Aug '18

11 Aug '18

All, I have had hangs on shutdown with kdm off and on with releases over the past decade (at least back to 11.4). When I choose "Shutdown", the desktop shuts down, X shuts down, the filesystem appears to have been properly unmounted, but then the terminal hangs and I have to resort to a hard poweroff to complete the shutdown. (I'll have to enable a persistent journal to make sure the filesystem is unmounted, but it has been on all prior shutdown hangs) I know this has been discussed somewhere before, but I can't recall where. I think this may have to do with the sequence for the X server shutdown (which opensuse triggers a restart of X after all logouts), so it may be an issue where X is both shutdown and attempting to restart, resulting in a block or hold being placed on final system shutdown. How would I drill down to figure out what is causing the hang? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

4 11

[opensuse-kde3] Looks like plymouthd takes continual 6% CPU in Leap 15 is fixed (at least in my VM)
by David C. Rankin 09 Aug '18

09 Aug '18

All, The prior problems I have seen with plymouthd taking a continual 6% of CPU with kdm/kde3 on all prior Leap releases (see post of 5/7/18), seems to be fixed for the Leap 15 build. I have not stripped plymouth from the default leap 15 install, and I've now loaded kde3 and configured kdm3 as the displaymanager and at least so far on the virtualbox VM I have it running on -- everything is fine. I'll let you know if it resurfaces. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

1 0

[opensuse-kde3] Leap 15 kdegraphics-kpdf missing pdftools_any dependency?
by David C. Rankin 05 Aug '18

05 Aug '18

All, First KUDOS to getting the KDE3 build done for 15! That is fantastic. I hadn't checked lately and saw the latest thread and then went and checked and sure enough -- it was built and ready to go. The only hickup I had during install was kdegraphics-pdf complained about a missing dependency 'pdftools_any' ?? I checked and the same dependency is there in 42.3, but no error was received on install. I suspect the 'pdftools_any' means any pdftools as there is no package named pdftools_any, but there is a texlive package with a similar name. Also, I was attempting a minimal install (I have 15 on a VM) and kdm pulls in kde4 and plasma libraries and the plasma icon themes. Does anybody know why this is? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

2 4

[opensuse-kde3] Problem with mc in kde3 konsole
by Mark Goldstein 04 Aug '18

04 Aug '18

Hi all, I need some advice on how to investigate the problem I see. On TW and Leap15 midnight commander does not react correctly on mouse buttons clicks. It works fine in leap 42.3 (and worked before as well). TW has mc version 4.8.21, leap15 uses v4.8.20. leap 42.3 has v4.8.15. Version of konsole is the same in all systems: 1.6.6, gpm is also the same, 1.20.7. The issue is that mouse button click is not handled as expected (e.g. move cursor to other line or other panel) and second click on the same button print some letter on mc command line. Wheel also does not work. It happens only with konsole of KDE3, that is if I open mc in xterm on tw or leap15, everything is OK. konsole5 (in plasma5) also works OK. It does not depend on DM. E.g. I started IWM and kde3 konsole under it, and the problem still existed. Same in other leap15 with plasma5 - ssh to kde3 leap15 machine, run kde3 konsole and use mouse on plasma5 machine - no luck. Looking at the change log of mc, I saw that mouse interface has been changes between v4.8.17 and 4.8.18. It looks like some configuration problem (maybe some timeout?) that causes code sequence sent from the mouse not being interpreted together. Apologies to David Haller, I copied you on this, since you are an mc guru and I'm not sure you are subscribed to kde3 list. So first simple question: someone see this as well? And second - how to investigate? BR -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

2 2