Bug 225137 - Kmix KDE4 (>=4.3.1) window does not appear under KDE3 (3.5.10)
Summary: Kmix KDE4 (>=4.3.1) window does not appear under KDE3 (3.5.10)
Status: RESOLVED DUPLICATE of bug 210973
Alias: None
Product: kmix
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-01 13:32 UTC by Jan Uhlir
Modified: 2010-02-03 02:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Uhlir 2010-02-01 13:32:18 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Mandriva RPMs

After a fresh log in to KDE 3.5.10 it is impossible to open Kmix 4.3.x window, not from konsole, not from K menu, Kickoff, Krunner. After some not yet discovered operation it starts to appear. It never ever in kicker tray, see bug #225132. This started to happen after update from KDE 4.2.x to KDE 4.3.x. I use KDE 3.5.10 but using a lot of components from upcoming KDE4. Kmix was one of them. Kmix from KDE 4.2.x worked just fine under KDE3 (3.5.10).

There is no crach report, no feedback to user. All suggests that Kmix IS running, it is named process list, multimedia keys are working, OSD shows volume reacting on pressing multimedia keys, volume reacts, sound is working. Just the main window does not shows up. Why?!

Tested with all Mandriva 2009.1 kmix packages 4.3.1 up to latest 4.3.5. including official and MIB version. I currently use kmix-4.3.5-69.1mib2009.1.

[espinosa@espinosadell ~]$ ps ax | grep -i kmix
12235 ?        S      0:00 kmix -session 1013714714f13600012650178600.....

Note, both kded (KDE3) and kded4 (KDE4) are running too.
[espinosa@espinosadell ~]$ ps ax | grep -i kde
11946 ?        Ss     0:00 /bin/sh /opt/kde3/bin/startkde
12168 ?        S      0:00 start_kdeinit --new-startup +kcminit_startup
12169 ?        Ss     0:00 kdeinit Running...
12172 ?        S      0:00 dcopserver [kdeinit] --nosid
12174 ?        S      0:00 klauncher [kdeinit] --new-startup
12176 ?        S      0:00 kded [kdeinit] --new-startup
12183 ?        S      0:00 ksmserver [kdeinit]
12184 ?        S      0:02 kwin [kdeinit] -session 1013714714f1360001249981730000000441600
12186 ?        S      0:01 kdesktop [kdeinit]
12188 ?        S      0:09 kicker [kdeinit]
12189 ?        S      0:00 kio_file [kdeinit] file /home/espinosa/tmp/ksocket-espinosa/kla..
12192 ?        S      0:00 kxkb [kdeinit]
12197 ?        S      0:00 kaccess [kdeinit]
12218 ?        Ss     0:00 kdeinit4: kdeinit4 Running...
12219 ?        S      0:00 kdeinit4: klauncher [kdeinit] --fd=8
12228 ?        Sl     0:00 kdeinit4: kded4 [kdeinit] e
12244 ?        S      0:00 kdeinit4: kglobalaccel [kdeinit]
12246 ?        Sl     0:00 xsettings-kde
12247 ?        S      0:00 knotify [kdeinit]
12250 ?        S      0:00 kpowersave [kdeinit]
12254 ?        S      0:00 klipper [kdeinit]
13464 ?        S      0:01 konsole [kdeinit]

I can provide full stack trace.
Comment 1 Jan Uhlir 2010-02-01 13:35:38 UTC
[espinosa@espinosadell ~]$ kmix -version
Qt: 4.5.3
KDE: 4.3.5 (KDE 4.3.5)
KMix: 3.5
Comment 2 Jan Uhlir 2010-02-01 13:35:50 UTC
[espinosa@espinosadell ~]$ kmix -version
Qt: 4.5.3
KDE: 4.3.5 (KDE 4.3.5)
KMix: 3.5
Comment 3 Dario Andres 2010-02-02 19:20:53 UTC
Mh, this could be caused by the new system tray protocol not registering its fallback item for the old FDO trays (like the one in KDE3): bug 210973.

- Do you experience this with "Kwalletmanager" (kdeutils) and "korgac" (kdepim) from KDE 4 ?

Regards
Comment 4 Jan Uhlir 2010-02-03 01:57:27 UTC
> kwalletmanager, korgac
The same behaviour. Seems to be running but no tray icon or window is open.
Are you interested in console output?

> bug 210973.
That was probably what I was originally looking for. Thanks.
Comment 5 Dario Andres 2010-02-03 02:00:05 UTC
I can't really tell if console output could be useful in this case as I'm not a developer of the code that is related to the bug.
Merging with bug 210973.
Thanks

*** This bug has been marked as a duplicate of bug 210973 ***