Description of problem: From the terminal bluedevil-wizard crashes and winds up in gdb. $ bluedevil-wizard /home/bittwister/tmp/desktop_app_ck/desktop_app_ck.junk returned code=253 QObject::connect: Cannot connect (null)::unpairedDeviceFound(Device*) to DiscoverPage::deviceFound(Device*) KCrash: Application 'bluedevil-wizard' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/bittwister/.kde4/socket-wb.home.test/kdeinit4__0 kwrite(18484) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. bluedevil-wizard 2. 3. Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedAssignee: bugsquad => mageia
Is this bug still present in latest cauldron?
Keywords: (none) => NEEDINFO
Yup.
Keywords: NEEDINFO => (none)
what is this file ? /home/bittwister/tmp/desktop_app_ck/desktop_app_ck.junk
Whiteboard: (none) => MGA5TOO
Summary: 5a2: No output from kde->Internet->BlueDevil => No output from kde->Internet->BlueDevil
Just a junk file. I have a go/nogo desktop_app_ck script which reads *.desktop files and runs the Exec= line. Example: $ grep exe /usr/share/applications/kde4/bluedevil-wizard.desktop Exec=bluedevil-wizard %U %U indicates bluedevil-wizard wants a url file. Local files may either be passed as file: URLs or as file path. You can run bluedevil-wizard without arguments and it still creates a kde crash.
please install the debuginfos packages and provide the backtrace
and cat /home/bittwister/tmp/desktop_app_ck/desktop_app_ck.junk
(In reply to Nicolas Lécureuil from comment #5) > please install the debuginfos packages and provide the backtrace I am just a dumb user. You need to be specific as to which rpms to install. There is no debuginfos package. > and cat /home/bittwister/tmp/desktop_app_ck/desktop_app_ck.junk Its just an empty file to prevent File not Found errors.
This might help https://wiki.mageia.org/en/Debugging_software_crashes
why don't you simply do "bluedevil-wizard" on the terminal ?
If you look at Steps to Reproduce: I did. It also segfaults. FYI: $ cat /etc/sysconfig/desktop DESKTOP=KDE4 DISPLAYMANAGER=kdm Runlevel 3 under startx. Some info from the KDE crash handler: Application: Bluetooth Wizard (bluedevil-wizard), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x00007f6d37ed8324 in QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&) () at /lib64/libQtDBus.so.4 #6 0x00007f6d392bdf8c in BlueDevil::Manager::registerAgent(QString const&, BlueDevil::Manager::RegisterCapability) () at /lib64/libbluedevil.so.2 #7 0x000000000040c085 in WizardAgent::WizardAgent(QApplication*) () #8 0x000000000040a90e in BlueWizard::BlueWizard(KUrl const&) () #9 0x0000000000408de3 in main ()
Does the crash handler give you more information? (especially, the lines before #5).
(In reply to Samuel VERSCHELDE from comment #11) > Does the crash handler give you more information? (especially, the lines > before #5). No
Source RPM: bluedevil-2.0.0-0.git20140216.4.mga5.src.rpm => bluedevil-2.1-1.mga5.src.rpm
Assignee: mageia => kde
Keywords: (none) => 6sta2
i see no crash here under plasma 5.8.6. Please reopen if the bug is still valid for you.
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED