[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#691406: some KDE programs take very long to start



Package: kde-standard
Version: 5:77
Severity: important

Hi,

I have installed yesterday's Debian testing nightly build ISO for amd64.
KDE works but takes very long to start up. Other KDE programs have
the same problem whereas e.g. firefox or icedove work just well.
I have also described the problem in bug #691366 [1] against the
pseudo-package "installation-report".

1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691366

In the meantime I upgraded some packages to unstable.

KDE tools that come up immediately are:
 - kdm
 - konsole
   (with two identical D-Bus warning messages:
    QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.)
 - kdialog
 - konqueror (now, after upgrading to unstable ... somehow this does not make sense,
     perhaps it is caused by some cached library or something...)
 - kaddressbook (with the two D-Bus warning messages)
 - kcalc
 - kfind
 - kfontview (with 2 D-Bus warning messages)
 - kinfocenter
 - kmail (with 2 D-Bus warning messages)
 - knotes (with 2 D-Bus warning messages)
 - krunner (with 2 D-Bus warning messages,
     but the first run in one KDE session takes some seconds, too)


KDE tools that take minutes to start:
 - KDE startup itself (4 minutes!)
 - k3b (the splash screen comes after the mentioned D-Bus warning messages,
        but it gets stuck at "Creating GUI...")
 - konqueror (yesterday, a fresh testing installation)
 - dolphin
 - kate (with D-Bus warning message but only one)
 - kopete (with 2 D-Bus warning messages, an empty window comes up immediately
   but then it gets stuck)
 - korganizer
 - kwrite
 - the logout dialog of KDE
I have compared the dependencies of those packages. When I exclude konqueror and
kmail, possible candidates for causing the startup delay turn out to be:
 - libkde3support4
 - libqt4-qt3support
 - libphonon4 or phonon

Since phonon is used for mixing audio, I have to mention that the standard Debian
installation runs PulseAudio. However, stopping the PulseAudio service did not help.
Hence I suspect the other two libraries being the bad guys (I may be totally wrong
though).


Best
  Stephan

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kde-standard depends on:
ii  akregator                     4:4.4.11.1+l10n-3+b1
ii  ark                           4:4.8.4-2
ii  dragonplayer                  4:4.8.4-2
ii  gwenview                      4:4.8.4-2
ii  juk                           4:4.8.4-2
ii  kaddressbook                  4:4.4.11.1+l10n-3+b1
ii  kate                          4:4.8.4-1
ii  kcalc                         4:4.8.4-2
ii  kde-plasma-desktop            5:77
ii  kdeplasma-addons              4:4.8.4-1
ii  khelpcenter4                  4:4.8.4-1
ii  kmail                         4:4.4.11.1+l10n-3+b1
ii  kmix                          4:4.8.4-2
ii  knotes                        4:4.4.11.1+l10n-3+b1
ii  kopete                        4:4.8.4-1+b1
ii  korganizer                    4:4.4.11.1+l10n-3+b1
ii  kscreensaver                  4:4.8.4-2
ii  ksnapshot                     4:4.8.4-1
ii  kwalletmanager                4:4.8.4-2
ii  okular                        4:4.8.4-2
ii  plasma-desktopthemes-artwork  4:4.8.4-2
ii  polkit-kde-1                  0.99.0-3
ii  sweeper                       4:4.8.4-1

Versions of packages kde-standard recommends:
ii  freespacenotifier                4:4.8.4-4
ii  konq-plugins                     4:4.8.4-2
ii  plasma-widget-networkmanagement  0.9.0.3-1
ii  update-notifier-kde              1.2.4

Versions of packages kde-standard suggests:
pn  kde-l10n<none>
ii  kde-plasma-desktop  5:77
pn  kde-plasma-netbook<none>
pn  skanlite<none>

-- no debconf information


Reply to: