[opensuse] Icons Awol after Update
After a clean install of Suse 10.1 x86_64 (remastered), I did an upgrade to KDE 3.5.5 Release 45.2 using the repository at opensuse.org. Upon log out, and log back in to get the new KDE, I have no icons displayed in any applications. If I start konsole from a shell, I get a stream of messages saying libpng error: Invalid image width libpng error: Invalid image width I get one of these for each icon the application tries to load. The icons are there, I can navigate to the with Kong, and click them and have them properly display in the embedded image viewer. Furthermore, desktop backgrounds that ate png images display properly. What do I need to do the fix this? Any clues? -- _____________________________________ John Andersen
On Friday 17 November 2006 17:12, John Andersen wrote:
After a clean install of Suse 10.1 x86_64 (remastered), I did an upgrade to KDE 3.5.5 Release 45.2 using the repository at opensuse.org.
Upon log out, and log back in to get the new KDE, I have no icons displayed in any applications. If I start konsole from a shell, I get a stream of messages saying libpng error: Invalid image width libpng error: Invalid image width
I get one of these for each icon the application tries to load.
The icons are there, I can navigate to the with Kong, and click them and have them properly display in the embedded image viewer. Furthermore, desktop backgrounds that ate png images display properly.
What do I need to do the fix this? Any clues? =======
John, Have you tried changing icon themes, just for the fun of it? It's possible the one you are using is broken with that build or something? bye, Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 November 2006 14:17, BandiPat wrote:
The icons are there, I can navigate to the with Kong, and click them and have them properly display in the embedded image viewer. Furthermore, desktop backgrounds that ate png images display properly.
What do I need to do the fix this? Any clues?
=======
John, Have you tried changing icon themes, just for the fun of it? It's possible the one you are using is broken with that build or something?
Yup. even tried installing a brand new theme. The fact that libpng says the width was invalid seems to suggest that it was passed something, but I have no idea what. On top of that, there are two sets of these libpng modules in an x86_64 system, one in /usr/lib (32bit) and the other set in /usr/lib64 I'm going to remove and force a re-install of those two rpms. -- _____________________________________ John Andersen
On 2006-11-17 16:12, John Andersen wrote:
<snip>
The icons are there, I can navigate to the with Kong, and click them and have them properly display in the embedded image viewer. Furthermore, desktop backgrounds that ate png images display properly.
What do I need to do the fix this? Any clues?
In the past, whenever my icons have disappeared, I just right click on the desktop, then Icons/do any kind of arrange to get them back. The problem has always been that the icons have simply been placed outside the screen boundaries. Worth a try before doing a full reinstall. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 November 2006 16:56, Darryl Gregorash wrote:
n the past, whenever my icons have disappeared, I just right click on the desktop, then Icons/do any kind of arrange to get them back. The problem has always been that the icons have simply been placed outside the screen boundaries.
Wish it were that simple. I'm not jus talking about icons on the desktop, I'm talking about every icon in every kde program, the menu, the panel, context menues, kmail, Kong, EVERY single menu is gonezo. Damn its hard to run kde without menus. Been using the alternate window manages in the meantime. -- _____________________________________ John Andersen
On 2006-11-17 20:00, John Andersen wrote:
On Friday 17 November 2006 16:56, Darryl Gregorash wrote:
n the past, whenever my icons have disappeared, I just right click on the desktop, then Icons/do any kind of arrange to get them back. The problem has always been that the icons have simply been placed outside the screen boundaries.
Wish it were that simple.
I'm not jus talking about icons on the desktop, I'm talking about every icon in every kde program, the menu, the panel, context menues, kmail, Kong, EVERY single menu is gonezo. Damn its hard to run kde without menus.
Been using the alternate window manages in the meantime.
OK, does /opt/kde3/share/icons/ still exist, and do you still have a /opt/kde3/share/icons/default.kde/? That should be a link to whatever you've selected as your default theme. If the icons directory does exist, check to see if it got updated to the new kde -- it should be owned by kde3libs (plus 2 or 3 other packages such as gnome-libs, which shouldn't be relevant). -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 November 2006 17:21, Darryl Gregorash wrote:
On 2006-11-17 20:00, John Andersen wrote:
On Friday 17 November 2006 16:56, Darryl Gregorash wrote:
n the past, whenever my icons have disappeared, I just right click on the desktop, then Icons/do any kind of arrange to get them back. The problem has always been that the icons have simply been placed outside the screen boundaries.
Wish it were that simple.
I'm not jus talking about icons on the desktop, I'm talking about every icon in every kde program, the menu, the panel, context menues, kmail, Kong, EVERY single menu is gonezo. Damn its hard to run kde without menus.
Been using the alternate window manages in the meantime.
OK, does /opt/kde3/share/icons/ still exist, and do you still have a /opt/kde3/share/icons/default.kde/? That should be a link to whatever you've selected as your default theme.
If the icons directory does exist, check to see if it got updated to the new kde -- it should be owned by kde3libs (plus 2 or 3 other packages such as gnome-libs, which shouldn't be relevant).
Yup, the directory does exist, and the default link is there and it points to a valid directory. However: When I compare two machines that are both running 10.1 the working one has a ton of icons in these directory structures and the failing ones only seem to have a very few. (Just enough to trick me into believing they were there, but not enough to fill out all the tool bars). So what package do i need to re-install to get them all to show. Kdeartwork? Themes? -- _____________________________________ John Andersen
On Friday 17 November 2006 17:34, John Andersen wrote:
However: When I compare two machines that are both running 10.1 the working one has a ton of icons in these directory structures and the failing ones only seem to have a very few. (Just enough to trick me into believing they were there, but not enough to fill out all the tool bars).
Nope, its not that the icons are missing. Comparing the same directories on the two different machines shows the exact same number of files in each of the default.kde subdirectories. The icons are there, but kde is not finding them. -- _____________________________________ John Andersen
On Friday 17 November 2006 21:55, John Andersen wrote:
On Friday 17 November 2006 17:34, John Andersen wrote:
However: When I compare two machines that are both running 10.1 the working one has a ton of icons in these directory structures and the failing ones only seem to have a very few. (Just enough to trick me into believing they were there, but not enough to fill out all the tool bars).
Nope, its not that the icons are missing. Comparing the same directories on the two different machines shows the exact same number of files in each of the default.kde subdirectories.
The icons are there, but kde is not finding them.
Since you've upgraded KDE, have you checked to see if rpm created a "kdmrc.rpmnew" under /opt/kde3/share/config/kdm"? Hint 1: make a backup copy of your existing kdmrc before doing anything else Hint 2: if replacing kdmrc with kdmrc.rpmnew doesn't work, study the README in the same directory for instructions on generating a new 'from scratch' kdmrc Hint 3: To test each change while troubleshooting, don't just log out and log back in (which theoretically restarts X each time) because in my experience it is not always reliable. Instead, log out of your session (lands you back at the login greeter), do Ctl+Alt+F1 to switch to tty1 console, log in as root, issue 'init 3' to drop to runlevel 3, wait and hit 'Enter' to regain a prompt then issue 'init 5 && exit' to return to runlevel 5. hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 November 2006 18:14, Carl Hartung wrote:
On Friday 17 November 2006 21:55, John Andersen wrote:
On Friday 17 November 2006 17:34, John Andersen wrote:
However: When I compare two machines that are both running 10.1 the working one has a ton of icons in these directory structures and the failing ones only seem to have a very few. (Just enough to trick me into believing they were there, but not enough to fill out all the tool bars).
Nope, its not that the icons are missing. Comparing the same directories on the two different machines shows the exact same number of files in each of the default.kde subdirectories.
The icons are there, but kde is not finding them.
Since you've upgraded KDE, have you checked to see if rpm created a "kdmrc.rpmnew" under /opt/kde3/share/config/kdm"?
Hint 1: make a backup copy of your existing kdmrc before doing anything else
Hint 2: if replacing kdmrc with kdmrc.rpmnew doesn't work, study the README in the same directory for instructions on generating a new 'from scratch' kdmrc
Hint 3: To test each change while troubleshooting, don't just log out and log back in (which theoretically restarts X each time) because in my experience it is not always reliable. Instead, log out of your session (lands you back at the login greeter), do Ctl+Alt+F1 to switch to tty1 console, log in as root, issue 'init 3' to drop to runlevel 3, wait and hit 'Enter' to regain a prompt then issue 'init 5 && exit' to return to runlevel 5.
Well it was worth a try, but no joy. No png icons work anywhere in the system even though the png files are there in the correct place an the correct numbers. I found one icon scheme that does work (mono) because it is composed only of .svgx files (Scalable Vector graphics). Its not a totally complete set (no try icons) but it does work. The problem is system wide, all users including root, including newly created users, so the files are there, and they can be viewed with any of the capable viewers (they are not corrupted), the icon-theme.cache was rebuilt with the fresh re-install, so its got to be a system wide setting or something. Been at it most of the day. Its Beer-O-Clock. -- _____________________________________ John Andersen
On Saturday 18 November 2006 00:53, John Andersen wrote:
Well it was worth a try, but no joy. No png icons work anywhere in the system even though the png files are there in the correct place an the correct numbers.
I found one icon scheme that does work (mono) because it is composed only of .svgx files (Scalable Vector graphics). Its not a totally complete set (no try icons) but it does work.
The problem is system wide, all users including root, including newly created users, so the files are there, and they can be viewed with any of the capable viewers (they are not corrupted), the icon-theme.cache was rebuilt with the fresh re-install, so its got to be a system wide setting or something.
Been at it most of the day. Its Beer-O-Clock.
What happens in the YaST2 'Software Management' module if you select "Reset Ignored Dependency Conflicts" under "Extras" (top menu) and click the "Check Dependencies" button? (or ensure the 'Autocheck' checkbox is enabled?) While you're there, what packages show up if you search on "png"? Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 November 2006 02:48, Carl Hartung wrote:
What happens in the YaST2 'Software Management' module if you select "Reset Ignored Dependency Conflicts" under "Extras" (top menu) and click the "Check Dependencies" button? (or ensure the 'Autocheck' checkbox is enabled?)
Did this, and no unsatisfied dependencies were revealed. (I never ignore dependencies).
While you're there, what packages show up if you search on "png"?
Did that too, in fact I searched on things that had PNG in REQUIRED just to see if installing a couple of them would trigger a dependency that was previously missed, but no joy. -- _____________________________________ John Andersen
On Saturday 18 November 2006 00:53, John Andersen wrote: <snip>
The icons are there, but kde is not finding them.
addendum: Didn't the original problem also include an error message complaining they were the 'wrong size'? Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 November 2006 02:50, Carl Hartung wrote:
On Saturday 18 November 2006 00:53, John Andersen wrote: <snip>
The icons are there, but kde is not finding them.
addendum:
Didn't the original problem also include an error message complaining they were the 'wrong size'?
This is still the case. If you contrive to see the error messages each attempt to load/view an icon will dump a message on the console saying libpng error: Invalid image width For instance, if I open a shell, and load something really simple such as konsole, there will be 8 or 10 of the above messages as konsole comes up. Each time I select one of menu items at the top, such as Bookmarks in the Konsole session I will see a few more messages in the original shell libpng error: Invalid image width one fore each icon that should have been on the Bookmark menu. This is a x86_64 machine (core 2 duo) which means there is a 64bit libpng and a 32bit libpng installed (one in /lib64 and the other in /lib) if that makes any difference. Of course KDE masks these from you unless you go looking for them with the method above or by tailing .xsession-errors. -- _____________________________________ John Andersen
On Saturday 18 November 2006 16:06, John Andersen wrote:
If you contrive to see the error messages each attempt to load/view an icon will dump a message on the console saying
libpng error: Invalid image width
I Googled this error message and got thousands of hits. Two generic problem types seem to emerge: a) an "endian" error b) 32-bit<>64-bit conflict <snip>
This is a x86_64 machine (core 2 duo) which means there is a 64bit libpng and a 32bit libpng installed (one in /lib64 and the other in /lib) if that makes any difference.
This information tends to make me suspect b), above. I seem to recall this is happening with every theme you test. What theme are you trying to use now? What is it's filename and complete path? Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 November 2006 13:50, Carl Hartung wrote:
On Saturday 18 November 2006 16:06, John Andersen wrote:
If you contrive to see the error messages each attempt to load/view an icon will dump a message on the console saying
libpng error: Invalid image width
I Googled this error message and got thousands of hits. Two generic problem types seem to emerge: a) an "endian" error b) 32-bit<>64-bit conflict
<snip>
This is a x86_64 machine (core 2 duo) which means there is a 64bit libpng and a 32bit libpng installed (one in /lib64 and the other in /lib) if that makes any difference.
This information tends to make me suspect b), above.
I seem to recall this is happening with every theme you test. What theme are you trying to use now? What is it's filename and complete path?
Yes it happens on every theme where the icons are png files. I found a theme called mono which is composed of .svgx files (Scalable Vector graphics). /opt/kde3/share/icons/mono/scalable/actions That theme works because libpng is not involved. Its sort of minimalist, but its starting to grow on me, which is just as well since its the only one that works. This theme is installed parallel to all the other themes in 10.1 in /opt/kde3/share/icons/. Your idea about endian errors seems like it might be a good candidate or be some how related. I suspected a library routing problem, where 32 bit libs are called with a 64bit data area which might explain why it thinks its getting an invalid width. When I installed 10.1 it worked perfectly. It wasn't till I upgraded KDE from http://repos.opensuse.org/KDE:/KDE3/SUSE_Linux_10.1/ via the software updater. (zmd) that the icons were no longer displayed. -- _____________________________________ John Andersen
On Saturday 18 November 2006 16:06, John Andersen wrote: <snip>
This is a x86_64 machine (core 2 duo) which means there is a 64bit libpng and a 32bit libpng installed (one in /lib64 and the other in /lib) if that makes any difference.
Addendum: You can check which libraries are linked to your selected style using ldd like this (example uses keramik style): carl@linux:~> ldd /opt/kde3/lib/kde3/plugins/styles/keramik.so linux-gate.so.1 => (0xffffe000) libkdefx.so.4 => /opt/kde3/lib/libkdefx.so.4 (0x4005b000) libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0x40088000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40783000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x40791000) libc.so.6 => /lib/tls/libc.so.6 (0x4086d000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4098c000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40a85000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x40a98000) libm.so.6 => /lib/tls/libm.so.6 (0x40aa0000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40ac6000) Note this: libpng.so.3 => /usr/lib/libpng.so.3 (0x40ad1000) And this: libz.so.1 => /lib/libz.so.1 (0x40b10000) <snip> You can use the "file" command to discern if a file is 32-bit or 64-bit like this: carl@linux:~> file /opt/kde3/lib/kde3/plugins/styles/keramik.so /opt/kde3/lib/kde3/plugins/styles/keramik.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped Finally, it appears the error message you're getting is sometimes caused when libpng can't uncompress the data because libz is not working correctly (wrong version, bad link and can't be found, etc.) Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 November 2006 15:31, Carl Hartung wrote:
On Saturday 18 November 2006 16:06, John Andersen wrote: <snip>
This is a x86_64 machine (core 2 duo) which means there is a 64bit libpng and a 32bit libpng installed (one in /lib64 and the other in /lib) if that makes any difference.
Addendum:
You can check which libraries are linked to your selected style using ldd like this (example uses keramik style):
carl@linux:~> ldd /opt/kde3/lib/kde3/plugins/styles/keramik.so linux-gate.so.1 => (0xffffe000) libkdefx.so.4 => /opt/kde3/lib/libkdefx.so.4 (0x4005b000) libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0x40088000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40783000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x40791000) libc.so.6 => /lib/tls/libc.so.6 (0x4086d000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4098c000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40a85000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x40a98000) libm.so.6 => /lib/tls/libm.so.6 (0x40aa0000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40ac6000) Note this: libpng.so.3 => /usr/lib/libpng.so.3 (0x40ad1000) And this: libz.so.1 => /lib/libz.so.1 (0x40b10000) <snip>
You can use the "file" command to discern if a file is 32-bit or 64-bit like this:
carl@linux:~> file /opt/kde3/lib/kde3/plugins/styles/keramik.so /opt/kde3/lib/kde3/plugins/styles/keramik.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped
Finally, it appears the error message you're getting is sometimes caused when libpng can't uncompress the data because libz is not working correctly (wrong version, bad link and can't be found, etc.)
---- Carl Here's what I get (snipped at about the same place as your example above jsa@nordell:~> ldd /opt/kde3/lib/kde3/plugins/styles/keramik.so linux-gate.so.1 => (0xffffe000) libkdefx.so.4 => /opt/kde3/lib/libkdefx.so.4 (0xf7e87000) libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0xf779f000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0xf7791000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf76b1000) libc.so.6 => /lib/libc.so.6 (0xf7590000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xf7499000) libpthread.so.0 => /lib/libpthread.so.0 (0xf7485000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0xf747d000) libm.so.6 => /lib/libm.so.6 (0xf7458000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf744d000) libpng.so.3 => /usr/lib/libpng.so.3 (0xf740d000) libz.so.1 => /lib/libz.so.1 (0xf73fb000) jsa@nordell:~> file /opt/kde3/lib/kde3/plugins/styles/keramik.so /opt/kde3/lib/kde3/plugins/styles/keramik.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped However, since this is a 64bit machine I also checked the 64bit version or keramic: jsa@nordell:~> ldd /opt/kde3/lib64/kde3/plugins/styles/keramik.so libkdefx.so.4 => /opt/kde3/lib64/libkdefx.so.4 (0x00002b987678b000) libqt-mt.so.3 => /usr/lib/qt3/lib64/libqt-mt.so.3 (0x00002b98768b9000) libXext.so.6 => /usr/X11R6/lib64/libXext.so.6 (0x00002b987722d000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002b987733f000) libc.so.6 => /lib64/libc.so.6 (0x00002b9877540000) libX11.so.6 => /usr/X11R6/lib64/libX11.so.6 (0x00002b9877770000) libXrender.so.1 => /usr/X11R6/lib64/libXrender.so.1 (0x00002b987797f000) libm.so.6 => /lib64/libm.so.6 (0x00002b9877a88000) libpng.so.3 => /usr/lib64/libpng.so.3 (0x00002b9877bdd000) libz.so.1 => /lib64/libz.so.1 (0x00002b9877d1a000) jsa@nordell:~> file /opt/kde3/lib64/kde3/plugins/styles/keramik.so /opt/kde3/lib64/kde3/plugins/styles/keramik.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped Then I decided to see which one was actually used. So I did some digging thru the Strace of a konsole launch. I can clearly see it using the 64bit libs, as this example shows: (I'm sending unwrapped, but it will probably wrap and make a mess outo of it., The first line is the important bit showing the call was to lib64/libpng: open("/usr/lib64/libpng.so.3", O_RDONLY) = 3 <======== 64bit read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0Px\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=247744, ...}) = 0 mmap(NULL, 1293800, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2ab92243d000 madvise(0x2ab92243d000, 1293800, MADV_SEQUENTIAL|0x1) = 0 mprotect(0x2ab922478000, 1048576, PROT_NONE) = 0 mmap(0x2ab922578000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3b000) = 0x2ab922578000 close(3) = 0 Then I looked in strace for a typical access to a png file of a theme: access("/opt/kde3/share/icons/hicolor/16x16/apps/konsole.png", R_OK) = 0 <========= lays to rest theory of missing pngs open("/opt/kde3/share/icons/hicolor/16x16/apps/konsole.png", O_RDONLY) = 11 fstat(11, {st_mode=S_IFREG|0644, st_size=826, ...}) = 0 fstat(11, {st_mode=S_IFREG|0644, st_size=826, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2ab923d4c000 lseek(11, 0, SEEK_SET) = 0 read(11, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\0\20\0\0\0\20\10\6\0\0"..., 4096) = 826 write(2, "libpng error: Invalid image widt"..., 34libpng error: Invalid image width <======= There is is... ) = 34 close(11) = 0 Finally your suggestion about libz... I looked in the strace for that and found that it looked long and hard to find this checking first under kde, then under qt3 and finally found it in /lib64 So that tells me it is using the 64 bit routines, and it is finding the actual png file. But it doesn't tell me why its crapping out. -- _____________________________________ John Andersen
On Sunday 19 November 2006 05:41, John Andersen wrote:
libpng error: Invalid image width <big snip>
Just for the record, John, how did you accomplish the KDE upgrade? Literally, what steps did you take? Other random comments: Is it reading a cached file or echoing the header?:
read(11, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\0\20\0\0\0\20\10\6\0\0"..., 4096) = 826
I'd look into that "32". Pixels? Bits? Coincidence? do an ldd to verify what libraries this style is linked to:
/opt/kde3/lib64/kde3/plugins/styles/keramik.so
ditto... an 'ldd /usr/lib64/libpng.so.3' to see what it's linked to:
open("/usr/lib64/libpng.so.3", O_RDONLY) = 3 <======== 64bit
Finally, just for the heck of it, do you see anything unusual when you run 'ldconfig' and 'SuSEconfig' (as needs to be done after installing rpms manually via CLI)? Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 November 2006 06:06, Carl Hartung wrote:
Just for the record, John, how did you accomplish the KDE upgrade? Literally, what steps did you take?
Added http://repos.opensuse.org/KDE:/KDE3/SUSE_Linux_10.1/ via the Config option to the software Updater. Clicked Refresh. Came back later to find 97 updates available. Clicked install, and came back later to see an Update Successful message. Logged out (getting a few error messages along the way because things didn't match version running). Logged back in. No Icons. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 November 2006 21:04, John Andersen wrote:
On Sunday 19 November 2006 06:06, Carl Hartung wrote:
Just for the record, John, how did you accomplish the KDE upgrade? Literally, what steps did you take?
Added http://repos.opensuse.org/KDE:/KDE3/SUSE_Linux_10.1/ via the Config option to the software Updater. Clicked Refresh. Came back later to find 97 updates available. Clicked install, and came back later to see an Update Successful message.
Logged out (getting a few error messages along the way because things didn't match version running). Logged back in. No Icons.
It's pretty clear from the error message that libpng is rejecting ("wrong image width") the icon image files. From your earlier post:
I suspected a library routing problem, where 32 bit libs are called with a 64bit data area which might explain why it thinks its getting an invalid width.
Can't you work back through the process chain with ldd to confirm the correct libraries are linked all the way through? If that doesn't get you anywhere, I've seen plenty of threads via Google ending with "reinstalled KDE and the problem went away". I know... blunt force... but I've run out of suggestions. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 20 November 2006 06:58, Carl Hartung wrote:
Can't you work back through the process chain with ldd to confirm the correct libraries are linked all the way through?
Well, the strace seemed to indicate that the 64bit routines were called, as they were specifically mentioned in the trace.
If that doesn't get you anywhere, I've seen plenty of threads via Google ending with "reinstalled KDE and the problem went away". I know... blunt force... but I've run out of suggestions.
And thats exactly where I'm going Carl. Its a new machine that I'm just putting into service and I don't have any commitment to the present install. It seems wiser to me to restart fresh than try to fix this mess. I thank you for your help, you are a gentleman and a scholar and I take back every bad thing I've said about you. ;-) BTW, this SAME thing happened to Mark Shuttleworth in late 2005. I found his posting on the ubuntu forums via google. -- _____________________________________ John Andersen
John Andersen wrote:
And thats exactly where I'm going Carl. Its a new machine that I'm just putting into service and I don't have any commitment to the present install. It seems wiser to me to restart fresh than try to fix this mess.
Have you by any chance verified that zen-updater didn't make an arch mistake and replace an x86_64 package with an i586 version? I would guess this would apply to more than just kde if more than kde was updated. -- Joe Morris Registered Linux user 231871 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 20 November 2006 14:52, Joe Morris (NTM) wrote:
John Andersen wrote:
And thats exactly where I'm going Carl. Its a new machine that I'm just putting into service and I don't have any commitment to the present install. It seems wiser to me to restart fresh than try to fix this mess.
Have you by any chance verified that zen-updater didn't make an arch mistake and replace an x86_64 package with an i586 version? I would guess this would apply to more than just kde if more than kde was updated.
Strace confirmed that the the x86_64 versions were being called. I'm doing a re-install now, s we will see what happens. I've learned never to discount the possibility that the source of the problem was between the keyboard and the chair. -- _____________________________________ John Andersen
On Monday 20 November 2006 17:42, John Andersen wrote:
And thats exactly where I'm going Carl. Its a new machine that I'm just putting into service and I don't have any commitment to the present install. It seems wiser to me to restart fresh than try to fix this mess.
Well, that's not so bad then. At least it usually goes faster the second time around. ;-) Be sure to wipe the partition(s) first. Some are skeptical, but I and others have had bits and pieces of prior installations 'bleed through'.
I thank you for your help, you are a gentleman and a scholar and I take back every bad thing I've said about you. ;-)
Er... thanks! ;-)
BTW, this SAME thing happened to Mark Shuttleworth in late 2005. I found his posting on the ubuntu forums via google.
Many similar reports at bugs.kde.org but all from years ago. Good luck and have fun! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-11-17 20:34, John Andersen wrote:
<snip>
So what package do i need to re-install to get them all to show. Kdeartwork? Themes?
rpm -qf /opt/kde3/share/icons, and compare package contents with the directory contents -- or just re-install all the packages. On my 9.3 installation, that directory is owned by: gnome-mime-data kdelibs3 gnome-libs kdvdbackup but that may differ on your system. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 November 2006 17:58, Darryl Gregorash wrote:
On 2006-11-17 20:34, John Andersen wrote:
<snip>
So what package do i need to re-install to get them all to show. Kdeartwork? Themes?
rpm -qf /opt/kde3/share/icons, and compare package contents with the directory contents -- or just re-install all the packages. On my 9.3 installation, that directory is owned by:
gnome-mime-data kdelibs3 gnome-libs kdvdbackup
but that may differ on your system.
I've replaced them three times now. I'm thinking its not likely to help. On my system, the directories are owned by root. <smirk>. nordell:~ # rpm -qf /opt/kde3/share/icons planmaker-2006.1.25-10 textmaker-2006.1.25-10 kxmleditor-1.1.4-20 kadslwatch-01.00.06-18 kisdnwatch-01.00.10-15 tellico-1.0.3-15 kdelibs3-3.5.5-45.2 -- _____________________________________ John Andersen
participants (5)
-
BandiPat
-
Carl Hartung
-
Darryl Gregorash
-
Joe Morris (NTM)
-
John Andersen