| Summary: | KGet takes a long time to startup | ||
|---|---|---|---|
| Product: | [Applications] kget | Reporter: | Emmanuel Surleau <emmanuel.surleau> |
| Component: | general | Assignee: | KGet authors <kget> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
My kgetrc
kget strace |
||
|
Description
Emmanuel Surleau
2008-10-19 01:01:13 UTC
Do you have many downloads in the list? Have you changed something "special" in the configs? How fast do other KDE apps run on your computer? KDE runs fast enough (kate launches in maybe 2 seconds, for instance). Launching kget from the command line takes about two minutes to have a grey window popping up (all grey apart from the window decorations), and two more minutes are necessary before getting a usable window. I have 2 download groups (6 items in one, 2 items in the other one). As far as I remember, the speed of kget was OK before 4.1.2. I'm uploading my kgetrc, but it's mostly the default one. Created attachment 28019 [details]
My kgetrc
I cannot see anything special in your config.. It could also be a bug in your distribution packages.. Please try with clean config. I cannot reproduce. Quoting Carsten: You might try starting kget manually in a terminal with strace and log the output. E.g. strace kget 2>&1 | tee /tmp/kget.log That will become a huge logfile, but might provide some information what it's doing for so long. Created attachment 28055 [details]
kget strace
Strace log for kget
I renamed my kgetrc to _kgetrc and started kget. It took much less time to show up the grey window, but it still took a while before it became useful. At which point it asked me if I wanted it to make the download manager for konqueror, which I agreed to, and then it promptly crashed. I've attached the strace log file. Could it be that D-Bus does not work correctly? Are other apps able to comunicate over D-Bus? That's the only thing I can see after looking shortly into the log. I tried dbus-send --type=method_call --dest=org.kde.kopete /Kopete org.kde.Kopete.disconnectAll with success, so I'd say yes. Doesn't seem to be an issue with 4.1.3... Ok then let's close it :) Lukas |