Version: 0.2 (using KDE KDE 3.1) Installed from: RedHat RPMs Compiler: gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) OS: Linux I'm seeing *very* similar results a bug#47003. Selecting configure knewsticker does nothing. The applet runs fine, just can't configure.
Unfortunately, unlike bug #47003, I see nothing relavent in ~/.xsession-errrors Compiling kdenetwork with the same configure options yields a fully working knewsticker on redhat8.0. I recompiled kdenetwork using only -O1 (thinking it might be a compiler bug), but that didn't help. I think I'll try rebuilding with -O0 and --enable-debug=full to see if I can find anything.
with --enable-debug=full I still see nothing in ~/.xsession-errors, I even see no output when run from the command line: $ appletproxy knewsticker.desktop I *do* get an error when I run: $ kcmshell knewsticker QMutex::unlock: unlock from different thread than locker was locked by 0, unlock attempt from 1024 Any ideas/hints to try next?
My bad, The install of the "debug" version hadn't succeeded, I'm trying again with the --enable-debug=full option.
full debug still yielded nothing helpful.
Similar bugs: both closed WORKSFORME ??: bug #48924, bug #47003.
Does this still happen with a newer KDE version - say, KDE 3.1.4?
Yep, still there in 3.1.4. Starting to think it's a compiler bug in some other component (qt, kdelibs), but it only shows up here. Recompiling kdenetwork with no optimization and full debugging didn't help any.
Hmm no, I doubt it's a compiler bug, right now I'm tempted to blame RedHat - in case you still use that. There have been problems with RedHat and Mandrake installations in the past, because they apparently installed .desktop files into non-standard locations, which made launching applications break sometimes. In any case, I think I'll just rewrite the way the configuration dialog is launched.
> right now I'm tempted to blame RedHat FYI, these are self-compiled rpms (on redhat 7.3) not from RedHat. The non-standard file locations you mention are applicable only to redhat 8.0 and 9 where they shoe-horned in Vfolder support (where by happenstance, Configure newsticker works just fine).
Hm ok then, I just rewrote the way the configuration facility is launched. Do you use KDE CVS snapshots by any chance? If so, you could test it right now. Otherwise you'll unfortunately have to wait for the next KDE release to get the fix.
Verified as functional/fixed with kde-3.2 on rh73. Thanks.