Re: BUG - qt3-3.3.8c-168.3 BREAKS kdm/ksplash background, causes KDE styles to disappear
On 3/10/25 3:39 PM, Felix Miata wrote:
All of my kdm and ksplash themes and backgrounds are custom. The kstyle issue is bizarre. All I can tell you is the downgrade was like flipping a switch from broken kdm/kspash themes, no advaced kde-shutdown dialog (the one with konqui) and all the KDE styles missing, but Qt styles shown. I mean, I can't make this stuff up: kde missing styles https://paste.opensuse.org/pastes/1559c91d31d4 kde non-enhanched shutdown dialog https://paste.opensuse.org/pastes/d300a1bf9575 After downgrade of Qt3, all of that is fixed and back to normal -- so something changed. My system is fully updated except for the Qt3 downgrade. -- David C. Rankin, J.D.,P.E.
Hi David, Unfortunately, this problem cannot be reproduced in my local environment. In addition, since nothing has been changed between them (3.3.8c-168.3 and 3.3.8c-168.1), so the behavior should not be changed (i.e. if a problem occurs in 3.3.8c-168.3, it should occur in the 3.3.8c-168.1 too). So I think that it may be due to a temporary incompatibilities between Tumbleweed and Slowroll. Because there is a difference (the timing of updating) between them, if you use repository KDE:KDE3-Tumbleweed within Slowroll, some problems may arise. Maybe it will be resolved after a while. If the problems persists after waiting some days, it is possible that some incompatible packages has been mixed-in. Please check your repository setup. Thanks, On Mon, 10 Mar 2025 15:58:50 -0500 "David C. Rankin" <drankinatty@gmail.com> wrote:
-- Yasuhiko Kamata E-mail: belphegor@belbel.or.jp
On 3/11/25 4:38 AM, Yasuhiko Kamata wrote:
Thank you Yasuhiko for checking. This is really odd. This is Tumbleweed, not Slowroll, so I was surprised to run into the issue. I had just done a fresh install of Tumblweed and kde3, and all was working, but when I did the last zypper dup, all of the items listed -- broke. I'll try an update later, there are gigabytes of new packages, but I'll have to wait for the kde3 repo to fix itself: Retrieving repository 'kde3' metadata ........................................................................[error] Repository 'kde3' is invalid. [kde3|http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Tumbleweed/] Failed to retrieve new repository metadata. History: - [|] Error trying to read from 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Tumbleweed/' - Location 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Tumbleweed/repo...' is temporarily unaccessible. So it looks like it is in the middle of an update itself. Will report results, and I'm a bit hesitant. Right now the new desktop install is back to being a thing of beauty... -- David C. Rankin, J.D.,P.E.
On 3/11/25 4:38 AM, Yasuhiko Kamata wrote:
Just did a FULL zypper dup and it is BROKEN again. My repositories are: # | Alias | Name | Enabled | GPG Check | Refresh ---+----------------------------------+----------------------------------------+---------+-----------+-------- 1 | armnone | armnone | Yes | (r ) Yes | Yes 2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes 3 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes 4 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes 5 | kde3 | kde3 | Yes | (r ) Yes | Yes 6 | mmedia | mmedia | No | ---- | ---- 7 | openSUSE-20250224-0 | openSUSE-20250224-0 | No | ---- | ---- 8 | packman | Packman | Yes | (r ) Yes | Yes 9 | packman-essentials | packman-essentials | Yes | (r ) Yes | Yes 10 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- 11 | repo-openh264 | Open H.264 Codec (openSUSE Tumbleweed) | Yes | (r ) Yes | Yes 12 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- 13 | takashi | takashi | Yes | (r ) Yes | Yes 14 | videolan | videolan | Yes | (r ) Yes | Yes 15 | vscodium | vscodium | Yes | (r ) Yes | Yes 6, 7, 10 and 12 are disabled. 6 was : https://download.opensuse.org/repositories/home:ecsos/openSUSE_Tumbleweed/ 7 was : http://download.opensuse.org/tumbleweed/repo/oss/ 10 & 12 are the normal source and debug repos. Downgrading: The following 2 packages are going to be downgraded: qt3 3.3.8c-168.4 -> 3.3.8c-168.1 qt3-devel 3.3.8c-168.4 -> 3.3.8c-168.1 Fixed everything again. How do we figure out what is going on? -- David C. Rankin, J.D.,P.E.
On 3/11/25 1:11 PM, David C. Rankin wrote:
Also, I just checked and I have nothing installed from the mmedia repo, al package there have been superseded by OSS since I disable that repository. The only packages from videolan other than libdvdcss2 are: S | Name | Type | Version | Arch | Repository ---+----------------------+---------+--------------+--------+---------------------- i | libdca0 | package | 0.0.7+2-10.5 | x86_64 | videolan v | libdca0 | package | 0.0.7+2-1.7 | x86_64 | Main Repository (OSS) v | libdca0 | package | 0.0.7+2-10.5 | i586 | videolan | libdca0-32bit | package | 0.0.7+2-1.7 | x86_64 | Main Repository (OSS) | libdca0-debuginfo | package | 0.0.7+2-10.5 | x86_64 | videolan | libdca0-debuginfo | package | 0.0.7+2-10.5 | i586 | videolan i | libmpeg2-0 | package | 0.5.1-9.47 | x86_64 | videolan v | libmpeg2-0 | package | 0.5.1-3.21 | x86_64 | Main Repository (OSS) v | libmpeg2-0 | package | 0.5.1-9.47 | i586 | videolan I can't see how either of those packages could be the issue. Ideas? -- David C. Rankin, J.D.,P.E.
On 3/11/25 1:23 PM, David C. Rankin wrote:
Also checking packman for possible problems, and the only thing I have installed from packman is rar, e.g. i+ | Packman | rar | 6.2.2-1699.1.pm.12 | x86_64 That's not it. I'll try moving libdca0 and libmpeg2-0 back to Main. From what I see I don't expect it to change. I've also compared common shared object dependencies between kdm and ksplash. Presumably one of them has to be the issue. moodin isn't common between kdm and kspash, so that shouldn't be a cause. That still leaves the issue of why the KDE styles vanish from my system?? I still need to update my laptop, so that will be another test. The only difference between the laptop and desktop is the desktop is selinux and the laptop isn't. But why would different qt3 point-release versions make any difference there? -- David C. Rankin, J.D.,P.E.
On 3/11/25 4:10 PM, David C. Rankin wrote:
It is DEFINITELY a change in qt3 that breaks the themes. I just updated my laptop. Background is broken in the kdm theme and ksplash. Most likely it is a break in the one of the libraries qt3 is compiled against that has broken the ability to display the background images. Here is the kdm theme I use: https://paste.opensuse.org/pastes/85b58a90c355 You can install it through kcontrol/kdm_theme or easier just $ cd /opt/kde3/share/apps/kdm/theme # tar -xjf kdedigital_kdm-1.2.tar.bz2 Then just edit /opt/kde3/share/config/kdm/kdmrc and changed the theme to: Theme=/opt/kde3/share/apps/kdm/themes/kdedigital_kdm and edit /opt/kde3/share/config/kdm/backgroundrc and set: Wallpaper[$e]=/opt/kde3/share/apps/kdm/themes/kdedigital_kdm/background.jpg Reboot or restart display-manager. The background will not be displayed. The greeter works fine. It's like the ability to display .jpg or .png backgrounds has been removed. Likely only allowing .svg to be displayed or something. That's just a guess. I'm not sure how else to figure out what broke -- but something definitely broke in qt3-3.3.8c-168.3 (and .4), it could have happened in .2, but I never installed it on my laptop. The only way I can restore a working laptop or desktop and keep my kdm theme and ksplash theme working is to downgrade: qt3 3.3.8c-168.4 -> 3.3.8c-168.1 qt3-devel 3.3.8c-168.4 -> 3.3.8c-168.1 -- David C. Rankin, J.D.,P.E.
On 3/11/25 5:59 PM, David C. Rankin wrote:
I'm not sure how Qt and X11 play together to draw the background, but just by chance, was Patch143: qt3-trident-add-glib-mainloop-support.patch https://build.opensuse.org/projects/KDE:KDE3/packages/qt3/files/qt3-trident-... active in 3.3.8c-168.1, but not in 3.3.8c-168.3 (or maybe .2)? The qeventloop it adds may well be how kdm_greet was notifying X to draw the background. The changelog from 12 days ago says that patch was commented to fix a tumbleweed build problem. Could that change be the change that is causing the issues? I can load the Qt versions and tell when problems start, but I'm still unclear how best to check why? I've checked the journal, Xorg.0.log.... WAIT - Found a Clue! In all the kdm.log, the last boot on my laptop before downgrading qt3 has the following QImage::smoothScale errors that only occur with 3.3.8c-168.3 (and 4): X.Org X Server 1.21.1.15 X Protocol Version 11, Revision 0 Current Operating System: Linux wizard 6.13.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Mar 10 08:49:24 UTC 2025 (495d82 a) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.13.6-1-default root=UUID=17f7b9ba-8760-4a74-bcc3-3f4ff0908233 splas h=silent quiet security=apparmor mitigations=off nosimplefb=1 acpi_backlight=video resume=/dev/disk/by-uuid/9ecc931 d-e17d-4ffe-8691-da8d555196b6 nvidia-drm.modeset=1 Current version of pixman: 0.43.4 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: Tue Mar 11 17:35:00 2025 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" The XKEYBOARD keymap compiler (xkbcomp) reports:
Checking the desktop kdm.log the error is the same, but adds a liblazy error as well: X.Org X Server 1.21.1.15 X Protocol Version 11, Revision 0 Current Operating System: Linux niflheim 6.13.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Mar 10 08:49:24 UTC 2025 (495d 82a) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.13.6-1-default root=UUID=a8db0bca-a4a7-4793-a03d-bae860476dc5 splas h=silent quiet mitigations=off security=selinux selinux=1 enforcing=0 i915.enable_dc=0 Current version of pixman: 0.43.4 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: Tue Mar 11 13:03:28 2025 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" The XKEYBOARD keymap compiler (xkbcomp) reports:
These "QImage::smoothScale: Image is a null image" do not occur in 3.3.8c-168.1 but do in 3.3.8c-168.3 and 3.3.8c-168.4. -- David C. Rankin, J.D.,P.E.
Hi, I'm still trying to reproduce it, but not succeeded so far. Custom theme "kdedigital_kdm" can be loaded without any problems and background image as follows: https://paste.opensuse.org/pastes/2137bac91c76
These "QImage::smoothScale: Image is a null image" do not occur in 3.3.8c-168.1 but do in 3.3.8c-168.3 and 3.3.8c-168.4.
It means that no image memory was allocated inside the QImage object. Probably image file was failed to load. One possibility is SELinux, but it could also be that the file system or memory (hardware) is partially corrupted. Thanks, On Tue, 11 Mar 2025 19:10:16 -0500 "David C. Rankin" <drankinatty@gmail.com> wrote:
-- Yasuhiko Kamata E-mail: belphegor@belbel.or.jp
On 3/12/25 11:38 PM, Yasuhiko Kamata wrote:
Yep, that's it! Now I'm really pulling my hair out. How can I have screwed something up? I mean I'm not doing anything other that what you are. I wonder if it is a conflict with one of the packman files for jpeg or the like?
Is there a way I can get more debugging detail on the error? The Qimage errors mean something is failing, but what? I'm still running the 3.3.8c-168.1 version and all is fine.
One possibility is SELinux, but it could also be that the file system or memory (hardware) is partially corrupted.
What is really giving me fits is that I have 2 computers. One with selinux and one with the old apparmor install. I see the same behavior on both. That rules out selinux. It also rules out a file system or memory corruption. The fact that I am running the 3.3.8c-168.1 with no issue also rules out some image file on my computer that is causing the issue. It would be the same there too. I've branched Qt3 and I'm reworking the qt3-trident-add-glib-mainloop-support.patch so it builds again on Tumbleweed. It will be a bit of an effort, but that is the only change I can see to Qt3 between the time my system worked and when it broke. If that can't be the issue, let me know so it's all not just wasted effort.
-- David C. Rankin, J.D.,P.E.
On 3/13/25 12:21 AM, David C. Rankin wrote:
Well I just duped and tried qt3-3.3.8c-168.5.x86_64.rpm and it has the same issue on my system. As soon as I rebooted, kdm appears with no background :( kdm.log shows the same QImage::smoothScale errors: X.Org X Server 1.21.1.15 X Protocol Version 11, Revision 0 Current Operating System: Linux niflheim 6.13.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Mar 10 08:49:24 UTC 2025 (495d82a) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.13.6-1-default root=UUID=a8db0bca-a4a7-4793-a03d-bae860476dc5 splash=silent quiet mitigations=off security=selinux selinux=1 enforcing=0 i915.enable_dc=0 Current version of pixman: 0.43.4 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: Fri Mar 14 01:58:49 2025 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" The XKEYBOARD keymap compiler (xkbcomp) reports:
Back to qt3-3.3.8c-168.1 and everything works again. Added a lock on qt3 until I get the patch tried. This is bizarre. Any debug setting you can think of that would make the kdm.log more verbose to catch the details of what image is causing?: QImage::smoothScale: Image is a null image Back to the drawing-board... -- David C. Rankin, J.D.,P.E.
On 3/14/25 2:20 AM, David C. Rankin wrote:
Getting closer, I've only got to trace down which patch is modifying src/kernel/qt_kernel.pri prior to the qt3-trident-add-glib-mainloop-support.patch (patch 143) being applied. The only patch I find is qt-x11-immodule-unified-qt3.3.8-20060318.diff (patch 25) patch 25 applies fine on it's own before patch 143 and the patch 143 applies fine thereafter, so there is a prior modification of src/kernel/qt_kernel.pri by sed or awk causing the Hunk 1 & 2 to fail from (patch 143). I move applying 143 immediately after 25 and it seems fine. If apply 143 before 25, then 25 will fail for that reason. As it stands now, this is the patch failure: [ 21s] + echo 'Patch #143 (qt3-trident-add-glib-mainloop-support.patch):' [ 21s] Patch #143 (qt3-trident-add-glib-mainloop-support.patch): [ 21s] + /usr/bin/patch --no-backup-if-mismatch -f -p1 --fuzz=0 [ 21s] patching file configure [ 21s] Hunk #1 succeeded at 287 (offset 3 lines). [ 21s] Hunk #2 succeeded at 370 (offset 3 lines). [ 21s] Hunk #3 succeeded at 875 (offset 9 lines). [ 21s] Hunk #4 succeeded at 2989 (offset 52 lines). [ 21s] Hunk #5 succeeded at 3567 (offset 64 lines). [ 21s] patching file src/kernel/qeventloop.h [ 21s] patching file src/kernel/qeventloop_glib_p.h [ 21s] patching file src/kernel/qeventloop_p.h [ 21s] patching file src/kernel/qeventloop_unix_glib.cpp [ 21s] patching file src/kernel/qeventloop_x11_glib.cpp [ 21s] patching file src/kernel/qt_kernel.pri [ 21s] Hunk #2 FAILED at 99. [ 21s] Hunk #3 FAILED at 128. [ 21s] Hunk #4 succeeded at 146 (offset 6 lines). [ 21s] Hunk #5 succeeded at 178 (offset 6 lines). [ 21s] 2 out of 5 hunks FAILED -- saving rejects to file src/kernel/qt_kernel.pri.rej [ 21s] patching file src/qt.pro [ 21s] Hunk #1 succeeded at 198 (offset 7 lines). No other patch touches src/kernel/qt_kernel.pri, so it is a shell command being used somewhere we will need to find. Yasuhiko, any idea where those modifications are found in the build? -- David C. Rankin, J.D.,P.E.
On 3/15/25 3:15 AM, David C. Rankin wrote:
Okay, I need help solving this Qt3 no background in kdm/kspash and missing KDE styles issue. I've worked to reorder patches to bring the commented out patch 143 back into use, but it looks like I will take much more than reordering. Patch 143 must be applied after patch 25 to succeed, but any time those patches are moved too early in the order, patching of [ 19s] patching file src/kernel/qapplication_x11.cpp fails at hunk 22. The breakage occurred between: qt3-3.3.8c-168.1 -> qt3-3.3.8c-168.2 If I update qt3-3.3.8c-168.1 to ANY version after that and restart display-manager the background disappears and: QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image errors appear in kdm.log. How in the heck do we debug this issue and find out what broke between qt3-3.3.8c-168.1 -> qt3-3.3.8c-168.2? -- David C. Rankin, J.D.,P.E.
On 3/12/25 11:38 PM, Yasuhiko Kamata wrote:
I am still trying to figure this out. Each time there is a new qt3, I hold my breath and update - boom into the same failure: X.Org X Server 1.21.1.15 X Protocol Version 11, Revision 0 Current Operating System: Linux niflheim 6.13.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Mar 10 08:49:24 UTC 2025 (495d82a) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.13.6-1-default root=UUID=a8db0bca-a4a7-4793-a03d-bae860476dc5 splash=silent quiet mitigations=off security=selinux selinux=1 enforcing=0 i915.enable_dc=0 Current version of pixman: 0.43.4 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: Tue Mar 18 23:05:55 2025 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" The XKEYBOARD keymap compiler (xkbcomp) reports:
I've looked at increasing the log level for kdm, e.g. $ Usage: kdm [options] [tty] -daemon - Daemonize even when started by init -nodaemon - Don't daemonize even when started from command line -config <file> - Use alternative master configuration file -xrm <res> - Override frontend-specific resource -error <file> - Use alternative log file -debug <num> - Debug option bitfield: 0x1 - core log 0x2 - config reader log 0x4 - greeter log 0x8 - IPC log 0x10 - session sub-daemon post-fork delay 0x20 - config reader post-start delay 0x40 - greeter post-start delay 0x80 - don't use syslog 0x100 - core Xauth log 0x400 - valgrind config reader and greeter 0x800 - strace config reader and greeter So I edited /usr/lib/X11/displaymanagers/kdm3 and added: KDM_BIN="/opt/kde3/bin/kdm --debug 0x1ff" That made no difference in the debug information in /var/log/kdm.log. (it looks like the "--debug 0x1ff" was ignored). The latest entry with qt3-3.3.8c-168.6.x86_64.rpm is what is shown above. I've downgraded to qt3-3.3.8c-168.1.x86_64.rpm and magically everything works fine (on both installs, one apparmor, no plymount, or selinux with plymouth). Where should I make this change to the kdm command line to make sure debug info is shown in the log? The "alternative" is just a circular firing squad of symlinks that resolves to /usr/lib/X11/displaymanagers/kdm3. That makes it a bit difficult to know where to include the --debug option. I can't for the life of me understand why upgrading qt3 breaks whatever it breaks, but it does, and downgrading back to qt3-3.3.8c-168.1 fixes it. I also can't figure out why the change in qt3 would cause the QImage::smoothScale errors. What images is it talking about and why does qt3-3.3.8c-168.1 not have any problem while everything from qt3-3.3.8c-168.2 on does? Nothing else on the system changes. I can update 1 rpm to qt3-3.3.8c-168.2, the kdm theme, ksplash theme shows no background, jpeg previews in the konqueror tooltips break, and all KDE styles disappear. I downgrade 1 rpm to qt3-3.3.8c-168.1 and everything works again. It is the same on both my boxes. Looking at the qt3 package contents, the only thing jpeg related is . Checking with ldd, I have: $ ldd /usr/lib/qt3/plugins/imageformats/libqjpeg.lib64.so linux-vdso.so.1 (0x00007f253d188000) libjpeg.so.8 => /lib64/glibc-hwcaps/x86-64-v3/libjpeg.so.8.3.2 (0x00007f253d076000) libqt-mt.so.3 => /lib64/libqt-mt.so.3 (0x00007f253c800000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f253c400000) libc.so.6 => /lib64/libc.so.6 (0x00007f253c000000) /lib64/ld-linux-x86-64.so.2 (0x00007f253d18a000) libpng16.so.16 => /lib64/glibc-hwcaps/x86-64-v3/libpng16.so.16.44.0 (0x00007f253c7b2000) libz.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libz.so.1.3.1 (0x00007f253c798000) libXi.so.6 => /lib64/libXi.so.6 (0x00007f253d060000) libXrender.so.1 => /lib64/libXrender.so.1 (0x00007f253c78b000) libXrandr.so.2 => /lib64/libXrandr.so.2 (0x00007f253c77e000) libXcursor.so.1 => /lib64/libXcursor.so.1 (0x00007f253c76f000) libXinerama.so.1 => /lib64/libXinerama.so.1 (0x00007f253c76a000) libXft.so.2 => /lib64/libXft.so.2 (0x00007f253c74f000) libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007f253c68e000) libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x00007f253c3af000) libXext.so.6 => /lib64/libXext.so.6 (0x00007f253c679000) libX11.so.6 => /lib64/libX11.so.6 (0x00007f253c266000) libSM.so.6 => /lib64/libSM.so.6 (0x00007f253c66c000) libICE.so.6 => /lib64/libICE.so.6 (0x00007f253c248000) libm.so.6 => /lib64/libm.so.6 (0x00007f253bf0b000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f253c21b000) libXfixes.so.3 => /lib64/libXfixes.so.3 (0x00007f253c213000) libbz2.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libbz2.so.1.0.6 (0x00007f253bef2000) libbrotlidec.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libbrotlidec.so.1.1.0 (0x00007f253bee4000) libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f253beb8000) libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f253be8c000) libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f253c209000) libbrotlicommon.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libbrotlicommon.so.1.1.0 (0x00007f253be69000) libXau.so.6 => /lib64/libXau.so.6 (0x00007f253c663000) Yasuhiko, Felix, do you see anything different? I'm running out of ideas of what to check. Ideas?? -- David C. Rankin, J.D.,P.E.
Hi David, Unfortunately, this problem cannot be reproduced in my local environment. In addition, since nothing has been changed between them (3.3.8c-168.3 and 3.3.8c-168.1), so the behavior should not be changed (i.e. if a problem occurs in 3.3.8c-168.3, it should occur in the 3.3.8c-168.1 too). So I think that it may be due to a temporary incompatibilities between Tumbleweed and Slowroll. Because there is a difference (the timing of updating) between them, if you use repository KDE:KDE3-Tumbleweed within Slowroll, some problems may arise. Maybe it will be resolved after a while. If the problems persists after waiting some days, it is possible that some incompatible packages has been mixed-in. Please check your repository setup. Thanks, On Mon, 10 Mar 2025 15:58:50 -0500 "David C. Rankin" <drankinatty@gmail.com> wrote:
-- Yasuhiko Kamata E-mail: belphegor@belbel.or.jp
On 3/11/25 4:38 AM, Yasuhiko Kamata wrote:
Thank you Yasuhiko for checking. This is really odd. This is Tumbleweed, not Slowroll, so I was surprised to run into the issue. I had just done a fresh install of Tumblweed and kde3, and all was working, but when I did the last zypper dup, all of the items listed -- broke. I'll try an update later, there are gigabytes of new packages, but I'll have to wait for the kde3 repo to fix itself: Retrieving repository 'kde3' metadata ........................................................................[error] Repository 'kde3' is invalid. [kde3|http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Tumbleweed/] Failed to retrieve new repository metadata. History: - [|] Error trying to read from 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Tumbleweed/' - Location 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Tumbleweed/repo...' is temporarily unaccessible. So it looks like it is in the middle of an update itself. Will report results, and I'm a bit hesitant. Right now the new desktop install is back to being a thing of beauty... -- David C. Rankin, J.D.,P.E.
On 3/11/25 4:38 AM, Yasuhiko Kamata wrote:
Just did a FULL zypper dup and it is BROKEN again. My repositories are: # | Alias | Name | Enabled | GPG Check | Refresh ---+----------------------------------+----------------------------------------+---------+-----------+-------- 1 | armnone | armnone | Yes | (r ) Yes | Yes 2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes 3 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes 4 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes 5 | kde3 | kde3 | Yes | (r ) Yes | Yes 6 | mmedia | mmedia | No | ---- | ---- 7 | openSUSE-20250224-0 | openSUSE-20250224-0 | No | ---- | ---- 8 | packman | Packman | Yes | (r ) Yes | Yes 9 | packman-essentials | packman-essentials | Yes | (r ) Yes | Yes 10 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- 11 | repo-openh264 | Open H.264 Codec (openSUSE Tumbleweed) | Yes | (r ) Yes | Yes 12 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- 13 | takashi | takashi | Yes | (r ) Yes | Yes 14 | videolan | videolan | Yes | (r ) Yes | Yes 15 | vscodium | vscodium | Yes | (r ) Yes | Yes 6, 7, 10 and 12 are disabled. 6 was : https://download.opensuse.org/repositories/home:ecsos/openSUSE_Tumbleweed/ 7 was : http://download.opensuse.org/tumbleweed/repo/oss/ 10 & 12 are the normal source and debug repos. Downgrading: The following 2 packages are going to be downgraded: qt3 3.3.8c-168.4 -> 3.3.8c-168.1 qt3-devel 3.3.8c-168.4 -> 3.3.8c-168.1 Fixed everything again. How do we figure out what is going on? -- David C. Rankin, J.D.,P.E.
On 3/11/25 1:11 PM, David C. Rankin wrote:
Also, I just checked and I have nothing installed from the mmedia repo, al package there have been superseded by OSS since I disable that repository. The only packages from videolan other than libdvdcss2 are: S | Name | Type | Version | Arch | Repository ---+----------------------+---------+--------------+--------+---------------------- i | libdca0 | package | 0.0.7+2-10.5 | x86_64 | videolan v | libdca0 | package | 0.0.7+2-1.7 | x86_64 | Main Repository (OSS) v | libdca0 | package | 0.0.7+2-10.5 | i586 | videolan | libdca0-32bit | package | 0.0.7+2-1.7 | x86_64 | Main Repository (OSS) | libdca0-debuginfo | package | 0.0.7+2-10.5 | x86_64 | videolan | libdca0-debuginfo | package | 0.0.7+2-10.5 | i586 | videolan i | libmpeg2-0 | package | 0.5.1-9.47 | x86_64 | videolan v | libmpeg2-0 | package | 0.5.1-3.21 | x86_64 | Main Repository (OSS) v | libmpeg2-0 | package | 0.5.1-9.47 | i586 | videolan I can't see how either of those packages could be the issue. Ideas? -- David C. Rankin, J.D.,P.E.
On 3/11/25 1:23 PM, David C. Rankin wrote:
Also checking packman for possible problems, and the only thing I have installed from packman is rar, e.g. i+ | Packman | rar | 6.2.2-1699.1.pm.12 | x86_64 That's not it. I'll try moving libdca0 and libmpeg2-0 back to Main. From what I see I don't expect it to change. I've also compared common shared object dependencies between kdm and ksplash. Presumably one of them has to be the issue. moodin isn't common between kdm and kspash, so that shouldn't be a cause. That still leaves the issue of why the KDE styles vanish from my system?? I still need to update my laptop, so that will be another test. The only difference between the laptop and desktop is the desktop is selinux and the laptop isn't. But why would different qt3 point-release versions make any difference there? -- David C. Rankin, J.D.,P.E.
On 3/11/25 4:10 PM, David C. Rankin wrote:
It is DEFINITELY a change in qt3 that breaks the themes. I just updated my laptop. Background is broken in the kdm theme and ksplash. Most likely it is a break in the one of the libraries qt3 is compiled against that has broken the ability to display the background images. Here is the kdm theme I use: https://paste.opensuse.org/pastes/85b58a90c355 You can install it through kcontrol/kdm_theme or easier just $ cd /opt/kde3/share/apps/kdm/theme # tar -xjf kdedigital_kdm-1.2.tar.bz2 Then just edit /opt/kde3/share/config/kdm/kdmrc and changed the theme to: Theme=/opt/kde3/share/apps/kdm/themes/kdedigital_kdm and edit /opt/kde3/share/config/kdm/backgroundrc and set: Wallpaper[$e]=/opt/kde3/share/apps/kdm/themes/kdedigital_kdm/background.jpg Reboot or restart display-manager. The background will not be displayed. The greeter works fine. It's like the ability to display .jpg or .png backgrounds has been removed. Likely only allowing .svg to be displayed or something. That's just a guess. I'm not sure how else to figure out what broke -- but something definitely broke in qt3-3.3.8c-168.3 (and .4), it could have happened in .2, but I never installed it on my laptop. The only way I can restore a working laptop or desktop and keep my kdm theme and ksplash theme working is to downgrade: qt3 3.3.8c-168.4 -> 3.3.8c-168.1 qt3-devel 3.3.8c-168.4 -> 3.3.8c-168.1 -- David C. Rankin, J.D.,P.E.
participants (2)
-
David C. Rankin -
Yasuhiko Kamata