[opensuse-kde3] Problems with screensavers
Actually, this appears to be a problem that has been an increasing pain since I first ran across it in V12.1. The symptoms go a bit like this. When I try to open the screensaver settings from the "Configure Desktop" right-click option, the window opens for a couple of seconds, showing "Loading..." in the screensaver selection area. It will then crash with no visible error and take the entirety of the desktop with it. The only fix I have to hand at that point is to restart the session. If I try to do the same thing from the control centre, it does almost exactly the same thing except that it doesn't take the desktop with it. I suspect the fault is the same one but the fact that the screensaver setup page is embedded in another program means that it doesn't get a chance to kill the desktop. I have now built KDE3 on openSUSE 13.1 four different times, both by overlaying it on KDE4 or building it on a minimal X Window build, and I have used different systems to do it on, though on each occasion this has been on VirtualBox systems. The only other clue I have to hand is that the kio_sysinfo slave comes up with "Process for the sysinfo protocol died unexpectedly" error when I try to use that (which is very annoying and, before anyone says it, NO I do NOT want to use that overstuffed "infocenter" thing!) Any clues? Ta -- Chika -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Saturday 21 December 2013 20:51:17 Chika wrote:
I have now built KDE3 on openSUSE 13.1 four different times, both by overlaying it on KDE4 or building it on a minimal X Window build, and I have used different systems to do it on, though on each occasion this has been on VirtualBox systems.
Why do you build KDE3 yourself? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 21/12/2013 17:19, Ilya Chernykh wrote:
On Saturday 21 December 2013 20:51:17 Chika wrote:
I have now built KDE3 on openSUSE 13.1 four different times, both by overlaying it on KDE4 or building it on a minimal X Window build, and I have used different systems to do it on, though on each occasion this has been on VirtualBox systems.
Why do you build KDE3 yourself?
Sorry. Probably needed to put that better - I built the system then attempted to put 13.1 + KDE3 on it. Actually, I was having a look at the system and wondered if this was in any way related to the way in which xorg.conf is set up these days. I'll need to check my 12.3 VB (which works) to see what I did there. -- Chika -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
I don't know whether this helps. I use the following packages: kdeartwork3-xscreensaver xscreensaver and I don't see any problems. Which screensaver package do you use? Gianluca On Sat, 21 Dec 2013, Chika wrote:
On 21/12/2013 17:19, Ilya Chernykh wrote:
On Saturday 21 December 2013 20:51:17 Chika wrote:
I have now built KDE3 on openSUSE 13.1 four different times, both by overlaying it on KDE4 or building it on a minimal X Window build, and I have used different systems to do it on, though on each occasion this has been on VirtualBox systems.
Why do you build KDE3 yourself?
Sorry. Probably needed to put that better - I built the system then attempted to put 13.1 + KDE3 on it.
Actually, I was having a look at the system and wondered if this was in any way related to the way in which xorg.conf is set up these days. I'll need to check my 12.3 VB (which works) to see what I did there.
-- Chika -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Sorry this has been left so long, but I've left a few things in my blog at Livejournal about all this (some of it possibly not safe for work!) Yes, I did try to use xscreensaver as you mention (I was using the default kscreensaver setup). That seemed to resolve much of the trouble but didn't resolve everything. I therefore decided to jump in and set up my reserve machine using the KDE3-over-KDE4 method which, surprise surprise, actually worked, but with a number of bugs. Screensaver, kio_sysinfo working though the latter is not showing all disc info. A bit of digging revealed that HAL is unable to talk to udev because udev isn't what it was anymore. It has been sucked into systemd and the 90-hal.rules file is no longer valid, giving the following error: Dec 30 11:54:46 Kanata systemd-udevd[312]: failed to execute '/usr/lib/udev/socket:/org/freedesktop/hal/udev_event' 'socket:/org/freedesktop/hal/udev_event': No such file or directory (Actually it repeats this error many times over which looks to me like it is trying to find wherever udev is sending its info to but is failing). /usr/lib/udev/rules.d/90-hal.rules looks like this: # pass all events to the HAL daemon RUN+="socket:@/org/freedesktop/hal/udev_event" The only change I can see in this from openSUSE 12.2 (where HAL works with no problem) is that everything was in /lib/udev rather than /usr/lib/udev. This would also, I presume, be why kio_sysinfo is not producing a full file list and possibly why it kept falling over on my previous VBs (well partly). I found a note somewhere saying that the "RUN+="socket..." line was deprecated (I hate that word, mostly because it's used by developers to mean "I really can't be bothered" or somesuch) but so far I've seen no clue about a possible replacement other than "we don't use HAL anymore" (which so far is not a valid option as udisks2 is essentially broken or has been in every attempt I have ever made to use it). To be honest, this whole business points faitly and squarely at the monumental mess left by openSUSE's wholesale charge towards integrating everything into systemd. OK, I know that openSUSE aren't alone in that, but it's not an excuse. Anyway it looks increasingly likely that my works machine will not be using KDE3 and my home server will be going to openSUSE 12.3 and no further until I have better solutions to the problems I'm facing here. Thanks, and a happy new year! -- Chika
Date: Sat, 21 Dec 2013 15:56:44 -0800 From: gianluca@u.washington.edu To: madoka_d@hotmail.com CC: opensuse-kde3@opensuse.org Subject: Re: [opensuse-kde3] Problems with screensavers
I don't know whether this helps. I use the following packages:
kdeartwork3-xscreensaver xscreensaver
and I don't see any problems. Which screensaver package do you use?
Gianluca
On Sat, 21 Dec 2013, Chika wrote:
On 21/12/2013 17:19, Ilya Chernykh wrote:
On Saturday 21 December 2013 20:51:17 Chika wrote:
I have now built KDE3 on openSUSE 13.1 four different times, both by overlaying it on KDE4 or building it on a minimal X Window build, and I have used different systems to do it on, though on each occasion this has been on VirtualBox systems.
Why do you build KDE3 yourself?
Sorry. Probably needed to put that better - I built the system then attempted to put 13.1 + KDE3 on it.
Actually, I was having a look at the system and wondered if this was in any way related to the way in which xorg.conf is set up these days. I'll need to check my 12.3 VB (which works) to see what I did there.
-- Chika -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/
Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 12/21/2013 11:19 AM, Ilya Chernykh wrote:
On Saturday 21 December 2013 20:51:17 Chika wrote:
I have now built KDE3 on openSUSE 13.1 four different times, both by overlaying it on KDE4 or building it on a minimal X Window build, and I have used different systems to do it on, though on each occasion this has been on VirtualBox systems. Why do you build KDE3 yourself?
Ilya, I have seen this problem as well with tde. If you are running on systemd without consolekit, the this problem along with the 'automount of USB' problem as well as problems with user-sound are most likely due to the lack of user session/process tracking that prevents udev from being able to assign permission properly in the case of USB and sound, and it is the failure to register the desktop greeter session with the PAM session stack. That's the bug I'm referencing in my question about a patch in the post "User session tracking patch needed for pure systemd (no consolekit)". If you have any ideas, please let me know in the other thread. I'll let you know if I find a solution first. Thanks. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (5)
-
Chika -
Chika Johnson
-
David C. Rankin -
Gianluca Interlandi -
Ilya Chernykh