- openSUSE KDE 3

Bug 1204252 - KDE3 khelpcenter path in some apps can't launch susehelp:
by David C. Rankin 14 Oct '22

14 Oct '22

All, Minor F1 (help) key can't launch susehelp bug filed: https://bugzilla.opensuse.org/show_bug.cgi?id=1204252 screenshot attached to bug. This involves kspace-duel (and others) that can't respond to the F1 key being pressed. This is a minor bug that if I recall correctly is simply the application help path not being updated to the main /opt/kde3/doc/HTML path (may have html - lowercase instead). The actual help-content in khelpcenter is fine. You just have to launch khelpcenter and navigate to it manually rather than getting there with the F1 key. This is filed is a "minor" bug to be worked "as time permits". (damn, if this is all I have to complain about in openSUSE KDE3 -- it's in great shape!) -- David C. Rankin, J.D.,P.E.

2 2

[kde3] laggy repos + constant rebuilds = highly annoying
by Felix Miata 08 Oct '22

08 Oct '22

Does ever a day go by that none of KDE3 for TW gets rebuilt? Whatever d.o.o. is directing zypper to here is creepy-crawly slow. It takes longer on average for a dup to download KDE3 files than it does all others put together. kde3-oxygen-icon-theme takes more than a minute to download. What on earth is that icon theme getting rebuilt for? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

2 1

Change to some Qt4 library disabled color themes for Qt4 apps? Anybody know which one?
by David C. Rankin 14 Sep '22

14 Sep '22

All, This was low priority, but a month or so ago, after zypper up that pulled in updated Qt4 libraries (a lot of them), the colors displayed in Qt4 apps like keepassx, etc.. are now some default. Before the update, my Qt4 apps were dark-themed to match the kde3 color scheme. Afterward, all Qt4 apps are light-themed with a horrid green background color used for highlight. Any idea how we can go about tracking down what Qt4 package caused this or how to fix it? -- David C. Rankin, J.D.,P.E.

1 0

Bug 1202370 - KSVGplugin Preview SegFault in 15.4 Konqueror filemanagement
by David C. Rankin 29 Aug '22

29 Aug '22

All, I opened: Bug 1202370 - KDE3 Konqueror Filemanagement Segfaults on .svg Preview https://bugzilla.opensuse.org/show_bug.cgi?id=1202370 for a konqueror Segfault that occurs attempting to preview diagram.svg from https://github.com/strukturag/libheif in KSVGplugin (e.g. Rt-click, Preview-in KSVGplugin) This is repeatable 100% of the time. -- David C. Rankin, J.D.,P.E.

1 1

What sets Xresource Xft.dpi: 96 on konsole start? (old issue, not new)
by David C. Rankin 08 Aug '22

08 Aug '22

All, I've watched this problem for years and am finally chasing it down a little further. When KDE3 starts, the Xft.dpi property is unset. So for example opening an xterm (not konsole) displays in the desktop native dpi (on my laptop that is 103). However, when konsole is started, something changes the Xft.dpi property to 96 (which was a very common dpi setting in the CRT monitor days) The problem this causes is when a new xterm is opened after konsole has been started, the xterm window, fonts, etc are scaled nearly 8% smaller by the dpi changee. Manually resetting Xft.dpi using xrdb -merge fixes the issue, e.g. $ xrdb -merge Xft.dpi: 103 (ctrl+d) Now starting a new xterm is fine. Any idea where in konsole startup are Xresources modified? -- David C. Rankin, J.D.,P.E.

2 3

konqueror - file preview of "some" assembler not detected as plain-text
by David C. Rankin 31 Jul '22

31 Jul '22

All, This is a very strange circumstance. dumping C++ to assembler *without* optimization produces file previewed as plain-text in konqueror file preview. E.g. files created with: g++ -S -masm=intel -O0 -std=c++17 -o asm/findhyphen-0-cstr.asm findhyphen.cpp The preview for file findhyphen-0-cstr.asm is shown as plain text with proper syntax highlight in konqueror. However if you use any optimization, e.g. -O1 through -Ofast the file is recognized as "Unknown" in konqueror and previews as hex instead of plain-text. The compile string would be: g++ -S -masm=intel -O1 -std=c++17 -o asm/findhyphen-1-cstr.asm findhyphen.cpp In konqueror preview, the first line is shown in the hex preview as: 0000:0000 | 09 2E 66 69 6C 65 09 22 66 69 6E 64 68 79 70 68 | ..file."findhyph (which is all valid plain-text as is the rest of the file) All editors (including kwrite and kate) open the text as a proper plain-text assembler file with proper highlight in contrast to what konqueror preview shows. I never recall this happening before. All file utilities see nothing but plain-text as well, e.g. $ file findhyphen-1-cstr.asm findhyphen-1-cstr.asm: assembler source, ASCII text or $ head -n 5 findhyphen-1-cstr.asm .file "findhyphen.cpp" .intel_syntax noprefix .text .section .rodata.str1.1,"aMS",@progbits,1 .LC0: I can't explain any possible reason why konqueror preview choose "Unknown" type for findhyphen-1-cstr.asm and plain-text for findhyphen-0-cstr.asm, but something is wrong. I'll try attaching the text file here. -- David C. Rankin, J.D.,P.E.

1 2

Qt3 qmake mkspec generates Makefile that calls /usr/bin/qmake instead of $(QTDIR)/bin/qmake
by David C. Rankin 16 Jul '22

16 Jul '22

All, There is a bug in default mkspec for the qmake generation of Makefile. /usr/lib/qt3/mkspecs/linux-g++-64/qmake.conf contains: QMAKE_MOC = $(QTDIR)/bin/moc QMAKE_UIC = $(QTDIR)/bin/uic Which works fine resulting in: MOC = $(QTDIR)/bin/moc UIC = $(QTDIR)/bin/uic However, for the QMAKE variable in the generated Makefile, you have: QMAKE = qmake Which causes the build to fail because it calls qmake in /usr/bin (qt4-devel qmake) instead of qt3 qmake in /usr/lib/qt3/bin. Changing the generated Makefile to: QMAKE = $(QTDIR)/bin/qmake allows qt3 builds to work fine. I'm not sure where the bug is, but it looks like the default mkspec needs to also prepend $(QTDIR)/bin to qmake to ensure qt3 qmake is called. I don't know if that can be fixed by simply modifying the default mkspec with: QMAKE_QMAKE = $(QTDIR)/bin/qmake I ran into this issue rebuilding a small personal project that provide a spinbutton and slider to set the laptop brightness from 0-20. You can reproduce the issue in 15.4 with the following minimum example: #include <qapplication.h> #include <qspinbox.h> #include <qslider.h> #include <qfont.h> #include "brightness.h" int main( int argc, char **argv ) { QApplication a( argc, argv ); form_brightness w; a.setMainWidget( &w ); w.show(); return a.exec(); } and the .ui file is: <!DOCTYPE UI><UI version="3.3" stdsetdef="1"> <class>form_brightness</class> <widget class="QWidget"> <property name="name"> <cstring>form_brightness</cstring> </property> <property name="geometry"> <rect> <x>0</x> <y>0</y> <width>239</width> <height>63</height> </rect> </property> <property name="caption"> <string>Form1</string> </property> <widget class="QSlider"> <property name="name"> <cstring>slider1</cstring> </property> <property name="geometry"> <rect> <x>10</x> <y>30</y> <width>171</width> <height>21</height> </rect> </property> <property name="focusPolicy"> <enum>StrongFocus</enum> </property> <property name="maxValue"> <number>20</number> </property> <property name="pageStep"> <number>2</number> </property> <property name="orientation"> <enum>Horizontal</enum> </property> <property name="tickmarks"> <enum>Both</enum> </property> <property name="tickInterval"> <number>2</number> </property> <property name="toolTip" stdset="0"> <string>set screen brightness</string> </property> <property name="whatsThis" stdset="0"> <string>screen brightness</string> </property> </widget> <widget class="QLabel"> <property name="name"> <cstring>textLabel1</cstring> </property> <property name="geometry"> <rect> <x>11</x> <y>0</y> <width>210</width> <height>21</height> </rect> </property> <property name="text"> <string>Screen Brightness</string> </property> </widget> <widget class="QSpinBox"> <property name="name"> <cstring>spinBox1</cstring> </property> <property name="geometry"> <rect> <x>190</x> <y>30</y> <width>30</width> <height>20</height> </rect> </property> <property name="focusPolicy"> <enum>WheelFocus</enum> </property> <property name="toolTip" stdset="0"> <string>set screen brightness</string> </property> <property name="whatsThis" stdset="0"> <string>screen brightness</string> </property> </widget> </widget> <connections> <connection> <sender>spinBox1</sender> <signal>valueChanged(int)</signal> <receiver>slider1</receiver> <slot>setValue(int)</slot> </connection> <connection> <sender>slider1</sender> <signal>valueChanged(int)</signal> <receiver>spinBox1</receiver> <slot>setValue(int)</slot> </connection> </connections> <layoutdefaults spacing="6" margin="11"/> </UI> Let me know whether this is a bug, or something that needs some other workaround (sed ?). -- David C. Rankin, J.D.,P.E.

1 0

New packages in KDE:KDE3
by Xxx 27 Jun '22

27 Jun '22

kde3-kio-appinfo kde3-tastymenu

2 1

Building kvkbd
by Ray Vine 20 Jun '22

20 Jun '22

I've updated the KDE3 kvkbd build to include further patches developed for the TDE version. The URL is the same as for the Nov '20 posting - https://ray-v.github.io/KDE3-kvkbd-patches.tar.xz. Enhancements include: Added ColorDialog for user setting keyboard and key colours Tooltips I18n support Added levels 3 & 4 [AltGr AltGr+Shift] characters display On most physical keyboards there is a very limited number of level 3 & 4 characters shown [on the right of the key]. Kvkbd shows all the characters available when AltGr or AltGr+Shift is clicked. Keyboard selection is immediate using either the KDE keyboard tool or setxkbmap and can therefore be toggled to any other layout to insert any other character from an alternative layout. Alternatively, create your own symbols file with the characters you would want in the level 3 & 4 positions. This has been done with this mathematical symbols file which is the us [basic] layout with mathematical characters and level3(ralt_switch) added: https://github.com/CaptchaSamurai/Math-Unicode-keyboard-overlay-Linux-XKB/r… Loading this [mth] with the KDE keyboard tool or setxkbmap will enable the mathematical symbols to be seen by clicking on AltGR or AltGr+Shift, rather than having to know where they are on a physical keyboard. Kvkdb works with the physical keyboard, so the character can be printed from either. The patches have been mostly left as they developed and are commented so can be included or not for any particular feature.

2 1

[kde3][TW] recurring meaningless kdmrc changes
by Felix Miata 05 Jun '22

05 Jun '22

# diff -u kdmrc.bak kdmrc --- kdmrc.bak 2022-04-28 01:53:02.000000000 -0400 +++ kdmrc 2022-06-04 23:09:01.000000000 -0400 @@ -284,13 +284,13 @@ # Whether KDM's built-in utmp/wtmp/lastlog registration should be used. # Default is true #UseSessReg=false +# Which X-authorization mechanisms should be used. +# Default is "MIT-MAGIC-COOKIE-1" +AuthNames=MIT-MAGIC-COOKIE-1 # Restart instead of resetting the local X-server after session exit. # Use it if the server leaks memory etc. # Default is false TerminateServer=false -# Which X-authorization mechanisms should be used. -# Default is "MIT-MAGIC-COOKIE-1" -AuthNames=MIT-MAGIC-COOKIE-1 # Greeter config for all displays [X-*-Greeter] @@ -573,9 +573,9 @@ # See above ClientLogFile=.xsession-errors # See above -TerminateServer=true -# See above Authorize=true +# See above +TerminateServer=true # Greeter config for 1st local display [X-:0-Greeter] @@ -593,12 +593,12 @@ # Default is "" LogSource=/dev/xconsole -[X-:93-Core] -# See above -TerminateServer=true +[X-:1-Core] # See above Authorize=true -[X-:1-Core] +[X-:93-Core] # See above Authorize=true +# See above +TerminateServer=true # What causes this recurring nonsense? Am I missing something? These changes are all meaningless AFAICT. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

3 2