Bug 20506 - k3b crash in XFCE maybe due miss dependency
Summary: k3b crash in XFCE maybe due miss dependency
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-16 21:47 CET by katnatek
Modified: 2018-05-12 00:00 CEST (History)
3 users (show)

See Also:
Source RPM: k3b-2.10.0-6.mga6
CVE:
Status comment:


Attachments
console output of k3b (149.55 KB, text/plain)
2017-03-16 21:47 CET, katnatek
Details

Description katnatek 2017-03-16 21:47:18 CET
Created attachment 9106 [details]
console output of k3b

Maybe this is "the chair" guilty, i uninstall some packages to make more space in my sistem.

I try to run k3b under Xfce and crash, i unistall k3b, remome orphans and reinstall k3b and the issue persist.

This is the packages installed when reinstall k3b

urpmi k3b
Para satisfacer la dependencia «libdbusmenu-qt5.so.2», se necesita uno de los paquetes siguientes:
 1- libdbusmenuqt5_2-0.9.3-0.20150604bzr.4.mga6.i586: A Qt implementation of the DBusMenu protocol (Qt5 version) (para instalar)
 2- libdbusmenu-qt5_2-0.9.3-1.20160218.1.mga6.i586: A Qt implementation of the DBusMenu protocol (Qt5 version) (para instalar)
¿Qué elige? (1-2)1
Use of uninitialized value in null operation at /usr/lib/perl5/vendor_perl/5.22.2/i386-linux-thread-multi/URPM/Resolve.pm line 1847.
Para satisfacer las dependencias, se instalarán los paquetes siguientes:
  Paquete                        Versión      Revisión      Arq.    
(soporte «Core Release»)
  cdrskin                        1.4.2        2.mga6        i586    
  libdbusmenuqt5_2               0.9.3        0.20150604bz> i586    
  libqt5quickwidgets5            5.6.2        2.mga6        i586    
(soporte «Core Release2»)
  kcmutils                       5.32.0       1.mga6        i586    
  knewstuff                      5.32.0       2.mga6        i586    
  libkf5declarative5             5.32.0       1.mga6        i586    
  libkf5kcmutils5                5.32.0       1.mga6        i586    
  libkf5newstuff5                5.32.0       2.mga6        i586    
  libkf5newstuffcore5            5.32.0       2.mga6        i586    
  libkf5notifications5           5.32.0       2.mga6        i586    
  libkf5notifyconfig5            5.32.0       2.mga6        i586    
  libkf5package5                 5.32.0       1.mga6        i586    
  libkf5quickaddons5             5.32.0       1.mga6        i586    
  sox                            14.4.2       4.mga6        i586    
(soporte «Tainted Release»)
  cdrdao                         1.2.3        12.mga6.tain> i586    
  k3b                            2.10.0       5.mga6.taint> i586    
  libk3bdevice7                  2.10.0       5.mga6.taint> i586    
  libk3blib7                     2.10.0       5.mga6.taint> i586
Marja Van Waes 2017-03-16 23:15:55 CET

CC: (none) => jani.valimaa, marja11
Assignee: bugsquad => kde

Comment 1 katnatek 2017-03-17 00:25:24 CET
Looks like the recent libdbusmenu-qt5_2-0.9.3-1.20160218.1.mga6 solve the issue
Plus my internal device looks failing, k3b run but not detect buner.
Plug external burner, run again k3b and run as must (previously k3b also crash with this device).

I think this could be closed.
Comment 2 Rémi Verschelde 2017-03-17 09:35:52 CET
Assigning to myself as libdbusmenu-qt5_2 should obsolete (replace) libdbusmenuqt5_2.

Assignee: kde => rverschelde
Source RPM: k3b: k3b-2.10.0-5.mga6.src.rpm => dbusmenu-qt

Comment 3 katnatek 2017-03-21 02:20:55 CET
kernel update 4.9.16-1 make crash again, i can't the previous kernel, but i report again after the 4.9.16-2 update
Comment 4 katnatek 2017-03-21 20:19:44 CET
system full update still crashing, some test i could do?
Comment 5 katnatek 2017-03-29 02:34:25 CEST
Not sure if this gdb backtrace could help

#0  K3b::Device::from2Byte (
    d=0xc0000002 <error: Cannot access memory at address 0xc0000002>)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdeviceglobals.cpp:222
#1  0xb7a6125b in K3b::Device::Device::getSupportedWriteSpeedsVia2A (
    this=0x87723e0, list=..., mediaType=K3b::Device::MEDIA_UNKNOWN)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevice.cpp:3254
#2  0xb7a62141 in K3b::Device::Device::determineSupportedWriteSpeeds (
    this=0x87723e0)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevice.cpp:3213
#3  0xb7a62580 in K3b::Device::Device::determineMaximalWriteSpeed (
    this=0x87723e0)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevice.cpp:3164
#4  0xb7a62975 in K3b::Device::Device::init (this=0x87723e0, 
    bCheckWritingModes=true)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevice.cpp:427
#5  0xb7a6eac8 in K3b::Device::DeviceManager::addDevice (this=0x83b7290, 
    device=0x87723e0)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevicemanager.cpp:377
#6  0xb7a6f0a0 in K3b::Device::DeviceManager::addDevice (this=0x83b7290, 
    solidDevice=...)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevicemanager.cpp:365
#7  0x080d632e in K3b::AppDeviceManager::addDevice (this=0x83b7290, 
    solidDev=...) at /usr/src/debug/k3b-2.10.0/src/k3bappdevicemanager.cpp:119
#8  0xb7a6d101 in K3b::Device::DeviceManager::checkDevice (this=0x83b7290, 
    dev=...) at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevicemanager.cpp:251
#9  0xb7a6e51a in K3b::Device::DeviceManager::scanBus (this=0x83b7290)
    at /usr/src/debug/k3b-2.10.0/libk3bdevice/k3bdevicemanager.cpp:239
#10 0xb7dc6583 in K3b::Core::init (this=0x84182f8)
    at /usr/src/debug/k3b-2.10.0/libk3b/core/k3bcore.cpp:206
#11 0x0808497b in K3b::Application::Core::init (this=0x84182f8)
    at /usr/src/debug/k3b-2.10.0/src/k3bapplication.cpp:259
#12 0x081d64b0 in K3b::Application::Core::qt_static_metacall (_o=0x84182f8, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x85bfca0)
    at /usr/src/debug/k3b-2.10.0/build/src/k3b_automoc.dir/moc_k3bapplication_NQLHE44NDIFSP7.cpp:194
#13 0xb5ff73f0 in QMetaCallEvent::placeMetaCall(QObject*) ()
   from /lib/sse2/libQt5Core.so.5
#14 0xb5ffad93 in QObject::event(QEvent*) () from /lib/sse2/libQt5Core.so.5
#15 0xb68f371a in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /lib/libQt5Widgets.so.5
#16 0xb68f8ca1 in QApplication::notify(QObject*, QEvent*) ()
   from /lib/libQt5Widgets.so.5
#17 0xb5fcdb15 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
   from /lib/sse2/libQt5Core.so.5
#18 0xb5fd0725 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/sse2/libQt5Core.so.5
#19 0xb5fd0c37 in QCoreApplication::sendPostedEvents(QObject*, int) ()
   from /lib/sse2/libQt5Core.so.5
#20 0xb60224f3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) ()
   from /lib/sse2/libQt5Core.so.5
#21 0xb1fe0449 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0xb1fe06c9 in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0
#23 0xb1fe0794 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0xb60228c6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/sse2/libQt5Core.so.5
#25 0xae782321 in QPAEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/libQt5XcbQpa.so.5
#26 0xb5fcb2d6 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/sse2/libQt5Core.so.5
#27 0xb5fcb6f2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /lib/sse2/libQt5Core.so.5
#28 0xb5fd403d in QCoreApplication::exec() () from /lib/sse2/libQt5Core.so.5
#29 0xb63018a1 in QGuiApplication::exec() () from /lib/sse2/libQt5Gui.so.5
#30 0xb68f0594 in QApplication::exec() () from /lib/libQt5Widgets.so.5
#31 0x0807f492 in main (argc=1, argv=0xbffff034)
    at /usr/src/debug/k3b-2.10.0/src/main.cpp:133
Comment 6 katnatek 2017-05-12 00:24:22 CEST
This sound like this old bug https://bugs.kde.org/show_bug.cgi?id=272427

By the way, why still have this k3b version?, in my search for info i found that for plasma is a newer version https://github.com/KDE/k3b/blob/master/ChangeLog , that is the current master branch mentioned in this bug https://bugs.kde.org/show_bug.cgi?id=360170

Openmandriva https://openmandriva.pkgs.org/cooker/openmandriva-main-release-x86_64/k3b-17.04.0-1-omv3001.x86_64.rpm.html and pclinux https://pclinuxos.pkgs.org/rolling/pclinuxos-kde5/k3b-17.04.0-2pclos2017.x86_64.rpm.html already have packages for that version
Rémi Verschelde 2017-05-12 07:25:31 CEST

Source RPM: dbusmenu-qt => k3b-2.10.0-6.mga6

Comment 7 katnatek 2017-05-22 23:29:46 CEST
After having fun with: fixing pclinux spec, installing around 280 buildrequires and spending like 1h building, i got 0 luck, the version in the previous comment also crash :(
Comment 8 katnatek 2017-05-23 22:52:35 CEST
I surrender, i install the mga 5 version in my cauldron system and works until now.

I can't stay without burn software, i try even build other "alternatives" but nothing even decent.

I hope no one suffer this bug.
Comment 9 Charles Edwards 2017-05-23 23:03:51 CEST
Have you tried nerolinux.
It's free now.
I actually bought mine when it first came out and have been using it for years.

http://www.nero.com/enu/downloads/previous-versions/download-linux4-update.php

CC: (none) => cae

Comment 10 katnatek 2017-05-24 18:43:30 CEST
(In reply to Charles Edwards from comment #9)
> Have you tried nerolinux.
> It's free now.
> I actually bought mine when it first came out and have been using it for
> years.
> 
> http://www.nero.com/enu/downloads/previous-versions/download-linux4-update.
> php

i test nero for linux long time ago but don't provide nothing that k3b don't can do, i even let use in windows.

i hope in future updates the issue will be fixed but if not i prefer use an old version
Comment 11 katnatek 2018-05-12 00:00:56 CEST
Fixed after the big update

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.