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#17937 - [roxterm] needs dbus
Attached to Project:
Community Packages
Opened by dave whom (partner550837) - Thursday, 21 January 2010, 02:30 GMT
Last edited by Dan Griffiths (Ghost1227) - Thursday, 21 January 2010, 03:49 GMT
Opened by dave whom (partner550837) - Thursday, 21 January 2010, 02:30 GMT
Last edited by Dan Griffiths (Ghost1227) - Thursday, 21 January 2010, 03:49 GMT
|
DetailsI installed community/roxterm-1.17.1-1, and I got this error when trying to run it:
** (roxterm:9122): CRITICAL **: Error connecting to dbus: /usr/bin/dbus-launch terminated abnormally without any error message process 9122: arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1525. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Aborted I then tried installing the package extra/dbus-1.2.16-1 and roxterm worked correctly, no errors. I guess roxterm also needs the dbus dependency. Thanks! |
This task depends upon
Closed by Dan Griffiths (Ghost1227)
Thursday, 21 January 2010, 03:49 GMT
Reason for closing: Fixed
Additional comments about closing: Requesting a closure might not be necessary, but I'd be happy to close it anyway! Fixed.
Thursday, 21 January 2010, 03:49 GMT
Reason for closing: Fixed
Additional comments about closing: Requesting a closure might not be necessary, but I'd be happy to close it anyway! Fixed.
Comment by Gerardo Exequiel Pozzi (djgera) -
Thursday, 21 January 2010, 03:10 GMT
- Field changed: Attached to Project (Arch Linux → Community Packages)
- Field changed: Details
@tom: There is no need to request closure when a task is opened under incorrect project, I can move it.