Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27813 - ktorrent 4.1.3-1 will not open
Attached to Project:
Arch Linux
Opened by Jason Begley (jayray) - Tuesday, 03 January 2012, 20:43 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 January 2012, 03:28 GMT
Opened by Jason Begley (jayray) - Tuesday, 03 January 2012, 20:43 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 January 2012, 03:28 GMT
|
DetailsDescription:
Recent reboot after pacman upgrades caused ktorrent to not start. Running this box headless with Xvnc calling icewm for wm and ktorrent will not load. Below is output from term when ran. ktorrent 4.1.3-1 tightvnc 1.3.10-5 QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. unnamed app(9358): Communication problem with "ktorrent" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.ktorrent.ktorrent was not provided by any .service files" " Steps to reproduce: |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Wednesday, 04 January 2012, 03:28 GMT
Reason for closing: Not a bug
Additional comments about closing: was a configuration issue
Wednesday, 04 January 2012, 03:28 GMT
Reason for closing: Not a bug
Additional comments about closing: was a configuration issue