|
Bugzilla – Full Text Bug Listing |
| Summary: | System administration in KDE broken. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Teuniz XXX <teuniz> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | bill_wayson, forgotten_Xh41Ao4q6j, heiko.rommel, hmuelle, meissner, monkey9, taroth |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
i686 output of rpm -q --changelog kdebase3 | head
x86-64 output of rpm -q --changelog kdebase3 | head kdelibs3 patch entering admin mode after entering admin mode entering admin mode |
||
|
Description
Teuniz XXX
2008-01-22 18:23:59 UTC
I get a lot of hard disk activity and error with first start from console: # /opt/kde3/bin/kcmshell kdm /usr/bin/iceauth: creating new authority file /root/.ICEauthority kbuildsycoca running... Invalid entry (missing '=') at /tmp/kde-root/kconf_updaterFD3qa.tmp:1 Starting the same line again seems to be normal. # /opt/kde3/bin/kcmshell kdm kbuildsycoca running... I can (mostly) confirm Rajko's experience. The difference is that on an x86_64 installation of openSUSE 10.3, my first invocation (as root) was "kcontrol". But I did get: kbuildsycoca running... Invalid entry (missing '=') at /tmp/kde-root/kconf_updatelsD7pa.tmp:1 The second invocation was: # /opt/kde3/bin/kcmshell kdm kbuildsycoca running... DCOP Cleaning up dead connections. (Note the extra message.) On an i686 installation of openSUSE 10.3, I got this: # /opt/kde3/bin/kcmshell kde Xlib: extension "XInputExtension" missing on display "161.213.23.7:1.0". Failed to get list of devices /usr/bin/iceauth: creating new authority file /root/.ICEauthority Xlib: extension "XInputExtension" missing on display "161.213.23.7:1.0". Failed to get list of devices kbuildsycoca running... Invalid entry (missing '=') at /tmp/kde-root/kconf_updatehxOxob.tmp:1 # /opt/kde3/bin/kcmshell kde Xlib: extension "XInputExtension" missing on display "161.213.23.7:1.0". Failed to get list of devices Xlib: extension "XInputExtension" missing on display "161.213.23.7:1.0". Failed to get list of devices kbuildsycoca running... # This was run from a remote VNC connection, and I believe the Xlib:... and Failed to get... errors are VNC-related. Also, in this instance, the KDE Control Module never did actually come up. does it work after installing the latest kdebase3 updates? there was a fix for embedding kcontrol modules. please paste rpm -q --changelog kdebase3 | head * Tue Jan 15 2008 - dmueller@suse.de - include 64bit bugfix as well (#348088) * Fri Dec 21 2007 - stbinner@suse.de - fix nsplugin to make newest Flash plugin work again (#348088) * Tue Nov 20 2007 - stbinner@suse.de - make $KDEWM work more generally and allow selecting Compiz in KControl on more systems capable of running it (#332079) - fix KDED crashing at logout because of nfs (#336627) Attached are the two (i686 and x86-64) rpm outputs requested. KDE updates come from the download,opensuse.org update link, what I call the standard openSUSE 10.3 updates. I do get more recent than standard updates of OpenOffice.org and Firefox from "Additional Repository" sites on download.opensuse.org. Created attachment 192616 [details]
i686 output of rpm -q --changelog kdebase3 | head
Created attachment 192617 [details]
x86-64 output of rpm -q --changelog kdebase3 | head
Works fine with kdebase3-3.5.8-41.2, broken with kdebase3-3.5.7-87.5 ; maybe the online update patch was broken, I'll check. *** Bug 359246 has been marked as a duplicate of this bug. *** Created attachment 193707 [details]
kdelibs3 patch
Updated qxembed-flash.diff for kdelibs3.
swamp? *** Bug 363272 has been marked as a duplicate of this bug. *** SWAMPID: 16414 Please use above SWMAPID for this update, submit package and patchinfos for openSUSE10.x. Why is the patch marked security? because the previous patch breaking it was also marked security. if thats a problem, I can downgrade it to recommended. patchinfo submitted so I guess this is also fixed for SLED SP2 now? there it was also broken with Beta 1 (see duplicate of this bug: https://bugzilla.novell.com/show_bug.cgi?id=359246) yes, this should be fixed for SP2 as well. When will the fix be available via Yast update? When everybody has moved to 10.4? Dirk, I followed the instructions in the initial description. I can not reproduce the issue on SLES10 SP1 (unfixed). This is what happens: After entering the root password the right side content is not empty (as described ) but shows the generic Welcome message of KDE. This does only change if clicking on one of the other functions (font manager etc) and then switching back to the previous one. Could it be that SP1 is not affected ? Last week the openSUSE 10.3 kde3libs updates (3.5.7-72_72.9) were installed on my PCs. At least on the x86_64 machine, this problem has been fixed. I guess the patch made it into these updates. I have not checked my 32-bit PCs yet. Yes, the last kde3libs update solved this issue for me on three computers (all 32-bit). and installing the update doesn't fix the "welcome screen" appearing? Correct. Installing the update didn't fix the problem on SLE10 (if it is a problem at all). To make sure I tried to reproduce the bug on 10.3 (unfixed) and I was successful. For some reasons SLE10 behaves differently. Attaching screenshots from updated SLE10 system in a minute. Created attachment 220663 [details]
entering admin mode
Created attachment 220664 [details]
after entering admin mode
Created attachment 220665 [details]
entering admin mode
the first screenshot had an screenshot window on top :/
when testing on sle10 I used remote VNC sessions when using local logins I can reproduce the defect and I can assure the defect was fixed with the maintenance update the inability of kdesu to forward X for vnc logins has been reported in a separate bug 398617 released |