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#12064 - Qt from [extra] causes Shaman freeze
Attached to Project:
Arch Linux
Opened by Bartek Iwaniec (hash) - Sunday, 09 November 2008, 19:00 GMT
Last edited by Pierre Schmitz (Pierre) - Wednesday, 26 November 2008, 13:17 GMT
Opened by Bartek Iwaniec (hash) - Sunday, 09 November 2008, 19:00 GMT
Last edited by Pierre Schmitz (Pierre) - Wednesday, 26 November 2008, 13:17 GMT
|
DetailsDescription:
Shaman doesn't start when run on Arch with Qt package from [extra]. It just hangs and there is not output in the terminal. The only possible way to start Shaman with [extra] Qt package is to change GUI style in qtconfig to different than oxygen. However installing Qtmod from [kdemod-core] makes shaman to start normally even with oxygen style. It looks like it's something wrong with Qt build from [extra]. I'm not sure if this is a bug of Shaman or Qt so sorry if its not the right place to report the bug. Additional info: * Qt 4.4.3, Shaman 1.0.9/SVN Steps to reproduce: Start the Shaman with standard Qt from extra and oxygen style. |
This task depends upon
#include <QApplication>
int main( int argc, char **argv )
{
QApplication app( argc, argv, QApplication::GuiClient );
return 0;
}
...doesn't work when invoked by root user. It doesn't crash, it loops on the first instruction until I send a SIGINT.
When called by unprivileged user it runs normally.
These are the options:
-no-exceptions
-dbus-linked
-reduce-relocations
I have no time to investigate it further, sorry.