- openSUSE KDE 3

Kde3 app (dialog) to change acpi_video0 backlight via dbus
by David C. Rankin 25 Jul '24

25 Jul '24

All, I've use a shell script for backlight control on my laptop for years, but finally got around writing a little Qt3 app for kde3 to do the same. It's just a slider and spinbox that automatically reads the current brightness and max_brightness values from /sys/class/backlight/acpi_video0/ and then sets the limits for the slider and spinbox. When you mousewheel over the dialog, the brightness is changed up/down. https://paste.opensuse.org/pastes/f6a583fb9a69 If interested I'm happy to post the source. It needs more work (I'm going to make the parent mainwindow the systray so it can work like kmix, allowing mouseweel over the icon without having to launch it -- but that comes later) If your video/monitor supports acpi_video0 and it's present on your system (or you add "acpi_backlight=video" to GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub, you can control any monitor that supports backlight change) I'm currently using it with a Nvdia card on a HP laptop. -- David C. Rankin, J.D.,P.E.

1 0

Why are krename and kwinstyle-crystal always updated? (just curious)
by David C. Rankin 23 Jul '24

23 Jul '24

Yasuhiko, (all), I've notice when doing updates (dupes for TW) or just checking with "zypper lu", kde3-krename and kde3-kwinstyle-crystal are always being updated, e.g. today: v | kde3 | kde3-krename | 3.0.14-4.190 | 3.0.14-4.191 v | kde3 | kde3-kwinstyle-crystal | 1.0.7-6.98 | 1.0.7-6.99 It is really just a curiosity as why a rebuild on those two packages always seems to be triggered. Other than the standard BuildRequires in the specs, they don't seem to have anything else in common. If it was a BuildRequires change, then a rebuild would be triggered on most packages... If you know, drop a reply, don't spend time chasing it down, it's not that important. -- David C. Rankin, J.D.,P.E.

2 3

Filed Bug 1228133 - KDE3 kmix cannot find mixer, alsamixer and kamix okay
by David C. Rankin 21 Jul '24

21 Jul '24

All, Just passing along a bug report regarding kmix losing it mind (mixer) in Tumbleweed. KDE3 kmix cannot find mixer, alsamixer and kamix okay https://bugzilla.opensuse.org/show_bug.cgi?id=1228133 I'm no sound expert, so if you have additional information about why kmix is broken in Tumbleweed, please add your information to the bug report (and hopefully it can get fixed) The odd part is sound in KDE3 on Tumbleweed is fine. Alsamixer works fine in konsole. kamix works fine in systray (it's ugly, basically being a KDE2 app, but it works) So why kmix can't at least do at minimum what alsamixer and kamix can is a mystery to me. -- David C. Rankin, J.D.,P.E.

3 6

Bug - Alf+F2 no longer displays search-as-you-type matching results in list-box
by David C. Rankin 16 Jul '24

16 Jul '24

All, Another subtle bug in KDE3 on TW (or recent builds) is that the Alt+F2 (Run Command) dialog in KDE3 no longer opens the dialog list-box with search-as-you-type opening to show prior matching commands so you can simply arrow down and select the command you want. Can someone please confirm this behavior. Test Case: 1. Alt + F2 2. type kmenuedit 3. return (to run it) 4. close kmenuedit 5. Alt + F2 6. type kmenuedit again As you type the 'k' you will see the icon displayed change to the kmenuedit icon showing at least the search-as-you-type part has identified the prior kmenuedit command -- but -- the list-box does not open. You have to manually click the list-box to see the previous kmenuedit command. This too may be related to the problem with focus-follows-mouse in Gtk apps mentioned in the last post. This points to a problem somewhere in the focus-model that it isn't able to trigger the list-box open command when a matching command is found in the Run Command dialog. If yours works in TW, then that points to some problem with my fresh TW install. -- David C. Rankin, J.D.,P.E.

1 0

Re: Why does mozilla repo have FF 115.12.0 for 15.4 and 115.11.0 for TW?
by David C. Rankin 15 Jul '24

15 Jul '24

On 7/15/24 6:44 AM, Dave Howorth wrote: > But you said you had a problem on Leap 15.4 as well? I did, but I was mistaken (infant Alzheimer's) I've booted back and forth between 15.4 and TW so many times in the past week, it appears I got the releases mixed up. KDE3 and 15.4 with TB and FF continue to accept focus-follows-mouse and mousewheel-scroll without any issue. This points to a very recent KDE3 build issue as my 15.4 and TW come from the same KDE3 repo, but I haven't updated the KDE3 on 15.4 for several months (for just this type reason) On 15.4 KDE3 has NO issues whatsoever (other than then handful of nits we have known for 15 years). So it looks like the recent builds are pulling in a library that hasn't been tweaked to avoid the Gtk GDK_CORE_DEVICE_EVENTS=1 problem. cc: kde3(a)lists.opensuse.org -- David C. Rankin, J.D.,P.E.

1 0

Thoughts on Creating a KDE3 desktop-data-openSUSE to preserve Menu Categories?
by David C. Rankin 13 Jul '24

13 Jul '24

All, We really need to find a better solution for preserving menu categories in KDE3 and loading the Leap 15.3 desktop-data-openSUSE and then adding a lock to prevent it from being updated. I just got caught again by not having added a zypper lock for desktop-data-openSUSE. All my menu categories disappeared when I did a zypper dup and the current stripped versions of desktop-data-openSUSE was pulled back in. What about creating a desktop-data-openSUSE-KDE3 rpm that preserves the proper XDG desktop specification for menu categories? That seems like a better solution that bandaiding everything post Leap-15.3 with the 15.3 rpm. It's sad the Gnome convinced SUSE to strip the XDG menu categories from desktop-data-openSUSE. What should have been done is to create desktop-data-openSUSE-Gnome with special non-standard requirements for Gnome rather than impact all desktop using the XDG menu spec -- but that is hindsight. Is there any support for creating a desktop-data-openSUSE-KDE3 from the 15.3 .srpm so that we can include that package in the KDE3 repo? That would save anyone loading KDE3 all the grief of wondering "Where the hell did all the menu categories got?" and "How am I supposed to find anything in a menu that wraps from the top of the screen to the bottom?" Not everyone knows the trick to grab the 15.3 rpm and then add a zypper lock on the package -- nor should they need to know that hack. Let me know and I'll see if I can pull the 15.3 source into buildservice and tweak the spec for TW. -- David C. Rankin, J.D.,P.E.

1 0

Great Job with KDE3 in Tumbleweed
by David C. Rankin 08 Jul '24

08 Jul '24

All, I just did a fresh install of Tumbleweed to minimal X, then added the KDE3 and mozilla repos. I installed KDE3 and copied my config from 15.4. Other than a few nits (no libbonoboui for kde3-qt-gtk-engine install, and kmix not finding a mixer), everything is working quite well. Same laptop, but on TW, it almost feels crisper than 15.4 (which was blisteringly fast with KDE3 on an i7 and SSD) The TW NET install was a nightmare due to US mirror issues, and defaulting to NetworkManager which has caused initial network setup to be more difficult than on 15.4, but it did the job. KDE3 is in great shape. We will get those bugs worked on with kmix and the kde3-qt-gtk-engine in the near future -- I hope! Great job to all that continue to make this desktop a joy to use! -- David C. Rankin, J.D.,P.E.

1 0

libbonoboui for TW kde3-gtk-qt-engine package
by David C. Rankin 08 Jul '24

08 Jul '24

All, It looks like the latest source for libbonoboui that isn't in default Tumbleweed can be found here: http://download.opensuse.org/repositories/Mono:/Factory/openSUSE_Factory/sr… (or the 15.4 source will do) Without it kde3-gtk-qt-engine cannot be installed from the kde3 repo. While it is of diminishing importance, there are still a number of packages with gtk2 themes/icons/etc that look quite odd without it. Anybody think it's worth build for completeness? -- David C. Rankin, J.D.,P.E.

1 0

Tumbleweed - kmix shows no volume in systray and no mixer when opened - what's up?
by David C. Rankin 08 Jul '24

08 Jul '24

All, I installed Tumbleweed fresh and then KDE3. Kmix displays in systray, but with the red X where it would normally display the volume. Opening kmix and there is no mixer shown - at all. Has anyone experienced this, and how to fix it? Also, kde3-gtk-qt-engine cannot be installed on Tumbleweed due to the missing libbonoboui (lib bonobo ui - however it is named). That dependency is nowhere to be found in the configured TW repositories. Has anyone found a work-around? -- David C. Rankin, J.D.,P.E.

1 0

There may be a desktop time issue in KDE3 that causes different TOTP gen between keepassxc GUI and CLI
by David C. Rankin 07 Jun '24

07 Jun '24

All, I ran across this strange bug building keepassxc on a 15.4 box. The build failed at TestPasskeys check which led to updating libbotan and libbotan-devel to 2.19 and the build issue was fixed. However, here is the bizarre part. With keepassx 2.7.6 and now with the fresh 2.7.8 with the GUI, I get different TOTP codes generated using the keepassx-cli command line in konsole and using the keepassx GUI. For example, in the keepassxc GUI, I got the following TOTP (times the same to the second): 176393 From the CLI, I get a completely different TOTP, e.g. $ keepassxc-cli show -t ~/.config/xxxxx.kdbx -k ~/.config/xxxxx.key "/Internet Sites/accounts/GitLab - Archlinux" Enter password to unlock /home/david/.config/xxxxx.kdbx: 103475 The CLI TOTP is correct, the GUI generated one is not. I ran into the TOTP issue a few weeks ago when gitlab just stopped accepting my TOTP codes as "Invalid". After stumbling across the build failure, I figured out the keepassxc-cli generate TOTP works fine with gitlab. I had opened a keepassxc issue on the build failure (the TestPasskeys check failure) which led to discovering the libbotan issue and comes down to this. The GUI and CLI use the same code to create the TOTP, the only possible difference is the time between the console and time reported by the desktop environment. If there is some strange zoneinfo, etc.. issue lingering in KDE3 that is just now manifesting, we may see more of this type issue. You can read the full discussion of the build and then GUI/CLI TOTP disagreement in this issue on github: https://github.com/keepassxreboot/keepassxc/issues/10854 I thought I would post here before I missed the chance, just in case there is some desktop time/system time issue. I've never seen anything like this before and checking the environment, the only thing I see time related is "COMPREPLY" that I'll have to look at further. Just make a note of this post if you run into anything funny time related in the future, this may give a starting point for debugging. I'll update if I find more on the issue I'm having. -- David C. Rankin, J.D.,P.E.

1 1