Application: plasma-discover (5.11.0) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.4.0-116-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: Discover crashes immediately on attempted update. "discover closed unexpectedly." Nothing happens. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc3527278c0 (LWP 3808))] Thread 4 (Thread 0x7fc325a11700 (LWP 3812)): #0 0x00007fc3488da8d3 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007fc3488db2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fc3488db49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fc34e7bb5cb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007fc34e76264a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fc34e582554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007fc351a3b1c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007fc34e5876eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fc34a9d36ba in start_thread (arg=0x7fc325a11700) at pthread_create.c:333 #9 0x00007fc34db8b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fc335349700 (LWP 3811)): #0 0x00007fc34891fa79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007fc3488da320 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fc3488db245 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fc3488db49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fc34e7bb5cb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fc34e76264a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007fc34e582554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007fc34f15da35 in QQmlThreadPrivate::run (this=0x2675010) at qml/ftw/qqmlthread.cpp:147 #8 0x00007fc34e5876eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007fc34a9d36ba in start_thread (arg=0x7fc335349700) at pthread_create.c:333 #10 0x00007fc34db8b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fc33655a700 (LWP 3810)): #0 0x00007fc34db7f74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fc3488db38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fc3488db49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fc34e7bb5cb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007fc34e76264a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fc34e582554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007fc3509312c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007fc34e5876eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fc34a9d36ba in start_thread (arg=0x7fc33655a700) at pthread_create.c:333 #9 0x00007fc34db8b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fc3527278c0 (LWP 3808)): [KCrash Handler] #6 0x00007fc352694584 in ?? () #7 0x00007fc34effb88b in QV4::ExecutionContext::simpleCall (this=<optimized out>, scope=..., callData=callData@entry=0x7fc33430a328, function=0x28e1650) at jsruntime/qv4context.cpp:302 #8 0x00007fc34f13da1f in QQmlJavaScriptExpression::evaluate (this=this@entry=0x297b890, callData=0x7fc33430a328, isUndefined=isUndefined@entry=0x7ffe374a421f, scope=...) at qml/qqmljavascriptexpression.cpp:223 #9 0x00007fc34f148228 in QQmlNonbindingBinding::doUpdate (this=0x297b890, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:207 #10 0x00007fc34f14525b in QQmlBinding::update (this=0x297b890, flags=...) at qml/qqmlbinding.cpp:168 #11 0x00007fc34f152091 in QQmlObjectCreator::finalize (this=0x26e1010, interrupt=...) at qml/qqmlobjectcreator.cpp:1225 #12 0x00007fc34f0cad8e in QQmlComponentPrivate::complete (enginePriv=0x26a09e0, state=0x26b5860) at qml/qqmlcomponent.cpp:914 #13 0x00007fc34f0caea7 in QQmlComponentPrivate::completeCreate (this=0x26b57c0) at qml/qqmlcomponent.cpp:950 #14 0x00007fc34f0cac7a in QQmlComponent::create (this=0x26b5480, context=0x26d5a50) at qml/qqmlcomponent.cpp:769 #15 0x00007fc34f149ffb in QQmlApplicationEnginePrivate::finishLoad (this=this@entry=0x26a09e0, c=c@entry=0x26b5480) at qml/qqmlapplicationengine.cpp:134 #16 0x00007fc34f14a2ae in QQmlApplicationEnginePrivate::startLoad (this=0x26a09e0, url=..., data=..., dataFlag=dataFlag@entry=false) at qml/qqmlapplicationengine.cpp:118 #17 0x00007fc34f14a2ed in QQmlApplicationEngine::load (this=<optimized out>, url=...) at qml/qqmlapplicationengine.cpp:259 #18 0x000000000041635a in ?? () #19 0x00000000004117aa in ?? () #20 0x00007fc34daa4830 in __libc_start_main (main=0x411180, argc=3, argv=0x7ffe374a4a08, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe374a49f8) at ../csu/libc-start.c:291 #21 0x0000000000411cb9 in _start () Possible duplicates by query: bug 388728. Reported using DrKonqi
How come you still have Discover 5.11 while your distro is Neon 5.12? Sounds like your system is broken somehow.
That's a good question and I've no idea. Ran sudo update and upgrade and here's the result. Dependencies are not satisfied for plasma-discover [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 -> 5.12.2-0neon+16.04+xenial+build102 | 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) Keeping package plasma-discover:amd64
(In reply to James Rufer from comment #2) > Dependencies are not satisfied for plasma-discover [ amd64 ] < > 4:5.11.0-0neon+16.04+xenial+build83 -> 5.12.2-0neon+16.04+xenial+build102 | > 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) > Keeping package plasma-discover:amd64 What about 'pkcon refresh' and then 'pkcon update'?
Here's the output. No change in Discover behavior. james@Librem15v2:~$ pkcon refresh Refreshing cache [=========================] Loading cache [=========================] Downloading packages [=========================] Running [=========================] Finished [=========================] Enabled http://repo.steampowered.com/steam precise InRelease Enabled http://us.archive.ubuntu.com/ubuntu xenial InRelease Disabled http://dl.google.com/linux/chrome/deb stable InRelease Enabled http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu xenial InRelease james@Librem15v2:~$ pkcon update Getting updates [=========================] Finished [=========================] Loading cache [=========================] Testing changes [=========================] Finished [ ] (0%) The following packages have to be updated: signal-desktop-1.5.1.amd64 Private messaging from your desktop Proceed with changes? [N/y] y [=========================] Updating packages [=========================] Waiting for authentication [=========================] Loading cache [=========================] Downloading packages [=========================] Running [=========================] Installing packages [=========================] Committing changes [=========================] Installing packages [=========================] Finished [ ] (0%) (pkcon:30527): GLib-CRITICAL **: Source ID 139 was not found when attempting to remove it [=========================]
I have the same problem with updating here: Dependencies are not satisfied for plasma-discover [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 -> 5.12.2-0neon+16.04+xenial+build102 | 4:5.11.0-0neon+16.04+xenial+build83 > ( kde )
UPDATE: aioannou@crow:/etc/apt/sources.list.d$ sudo apt-get install plasma-discover Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) plasma-discover [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 -> 5.12.2-0neon+16.04+xenial+build102 | 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) Broken plasma-discover:amd64 Depends on plasma-discover-common [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) (= 5.12.2-0neon+16.04+xenial+build102) Considering plasma-discover-common:amd64 0 as a solution to plasma-discover:amd64 10003 Broken plasma-discover:amd64 Depends on plasma-discover-private [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) (= 5.12.2-0neon+16.04+xenial+build102) Considering plasma-discover-private:amd64 2 as a solution to plasma-discover:amd64 10003 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: plasma-discover : Depends: plasma-discover-common (= 5.12.2-0neon+16.04+xenial+build102) but 4:5.11.0-0neon+16.04+xenial+build83 is to be installed Depends: plasma-discover-private (= 5.12.2-0neon+16.04+xenial+build102) but 4:5.11.0-0neon+16.04+xenial+build83 is to be installed E: Unable to correct problems, you have held broken packages.
So it's definitely the neon repos that aren't up to date and not us right?
*** Bug 391479 has been marked as a duplicate of this bug. ***
I have have the same issue, I cannot upgrade to discover 5.12 on neon user, I'm stuck with 5.11 whereas plasma is 5.12.3 (it works fine on neon LTS btw). Has this issue been resolved? If so where is the patch / solution? Many thanks
(In reply to Gauthier from comment #9) > I have have the same issue, I cannot upgrade to discover 5.12 on neon user, > I'm stuck with 5.11 whereas plasma is 5.12.3 (it works fine on neon LTS btw). > > Has this issue been resolved? If so where is the patch / solution? > > Many thanks Should be resolved. Have you tried to manually enter "pkcon refresh && pkcon update" in a terminal?
Thank you for your answer but yes I did try. Here is the output: pkcon refresh Refreshing cache [=========================] Loading cache [=========================] Refreshing software list [=========================] Downloading packages [=========================] Running [=========================] Finished [=========================] Enabled http://download.virtualbox.org/virtualbox/debian xenial InRelease Enabled http://gb.archive.ubuntu.com/ubuntu xenial InRelease Enabled http://ppa.launchpad.net/apandada1/brightness-controller/ubuntu xenial InRelease Disabled http://download.videolan.org/pub/debian/stable InRelease Enabled http://ppa.launchpad.net/gezakovacs/ppa/ubuntu xenial InRelease Disabled http://liveusb.info/multisystem/depot all InRelease Disabled http://download.opensuse.org/repositories/home:/stevenpusser/xUbuntu_16.04 InRelease Enabled http://download.videolan.org/pub/debian/stable Release Enabled http://download.opensuse.org/repositories/home:/stevenpusser/xUbuntu_16.04 Release Enabled http://liveusb.info/multisystem/depot all Release Enabled http://ppa.launchpad.net/go-for-it-team/go-for-it-daily/ubuntu xenial InRelease Enabled http://archive.canonical.com/ubuntu xenial InRelease Enabled https://dl.winehq.org/wine-builds/ubuntu xenial InRelease Enabled http://screenshots.getdeb.net xenial-getdeb InRelease Enabled https://download.jitsi.org stable/ InRelease Enabled https://apt.syncthing.net syncthing InRelease Enabled https://dl.ring.cx/ring-nightly/ubuntu_16.04 ring InRelease Enabled http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial InRelease Enabled http://ppa.launchpad.net/linrunner/tlp/ubuntu xenial InRelease Enabled http://ppa.launchpad.net/lyx-devel/release/ubuntu xenial InRelease Enabled http://ppa.launchpad.net/me-davidsansome/clementine/ubuntu xenial InRelease Enabled http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu xenial InRelease Enabled http://ppa.launchpad.net/phoerious/keepassxc/ubuntu xenial InRelease Enabled http://ppa.launchpad.net/ubuntuhandbook1/audacity/ubuntu xenial InRelease ggn@wopr-T560:~$ pkcon update Getting updates [=========================] Finished [=========================] No packages require updating to newer versions. ggn@wopr-T560:~$ sudo apt-get upgrade [sudo] password for ggn: Reading package lists... Done Building dependency tree Reading state information... Done Entering ResolveByKeep 50% Dependencies are not satisfied for plasma-discover [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 -> 5.12.3-0neon+16.04+xenial+build105 | 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) Keeping package plasma-discover:amd64 Calculating upgrade... Done The following package was automatically installed and is no longer required: libcln6 Use 'sudo apt autoremove' to remove it. 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
And if it helps below is the output of sudo apt-get install plasma-discover Many thanks Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) plasma-discover [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 -> 5.12.3-0neon+16.04+xenial+build105 | 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) Broken plasma-discover:amd64 Depends on plasma-discover-common [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) (= 5.12.3-0neon+16.04+xenial+build105) Considering plasma-discover-common:amd64 0 as a solution to plasma-discover:amd64 10003 Broken plasma-discover:amd64 Depends on plasma-discover-private [ amd64 ] < 4:5.11.0-0neon+16.04+xenial+build83 > ( kde ) (= 5.12.3-0neon+16.04+xenial+build105) Considering plasma-discover-private:amd64 2 as a solution to plasma-discover:amd64 10003 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. plasma-discover : Depends: plasma-discover-common (= 5.12.3-0neon+16.04+xenial+build105) but 4:5.11.0-0neon+16.04+xenial+build83 is to be installed Depends: plasma-discover-private (= 5.12.3-0neon+16.04+xenial+build105) but 4:5.11.0-0neon+16.04+xenial+build83 is to be installed E: Unable to correct problems, you have held broken packages.
Hi, I have absolutely the same issue. KDE Neon Ubuntu 16.04 LTS Regards Ralf
Still same issue on plasma 5.12.4 and 5.12.5, discover is not updating and stays at version 5.11.
(In reply to Gauthier from comment #14) > Still same issue on plasma 5.12.4 and 5.12.5, discover is not updating and > stays at version 5.11. Had the same situation, but managed to force it in "aptitude": found the plasma-discover-common package [/^plasma-discover], [enter], and on versions I picked the 5.12.5 for installation ([+]) and the aptitude will warn about break of dependencies and suggest solutions - examine them [e], somewhere about third or fourth solution (next [.]) was to basically keep everything as is and "downgrade plasma-discover-**** to 5.12.5" - about four other discover packages, so I applied this [!] and since then "apt-get upgrade" seems to be happy completely and discover says it's 5.12.5 now. There's surely some CLI way to do this same with apt, but I never recall all the switches, sorry, I prefer the powerful UI of aptitude (it's just not as simple as it may look, takes some time to learn how it works and find out some details) ... anyway, still looks miles ahead of discover to me, except missing graphics, I can much more easily check all packages, see versions, download size, etc. discover is very vague about everything and offers just like the main app packages, it's probably perfect for ordinary/new user, but I can't seem to get use for it, maybe once when I did need quick overview of current media players available, at that point discover design works quite well.
(In reply to Peter Ped Helcmanovsky from comment #15) > (In reply to Gauthier from comment #14) > > Still same issue on plasma 5.12.4 and 5.12.5, discover is not updating and > > stays at version 5.11. > > Had the same situation, but managed to force it in "aptitude": > found the plasma-discover-common package [/^plasma-discover], [enter], and > on versions I picked the 5.12.5 for installation ([+]) and the aptitude will > warn about break of dependencies and suggest solutions - examine them [e], > somewhere about third or fourth solution (next [.]) was to basically keep > everything as is and "downgrade plasma-discover-**** to 5.12.5" - about four > other discover packages, so I applied this [!] and since then "apt-get > upgrade" seems to be happy completely and discover says it's 5.12.5 now. > > There's surely some CLI way to do this same with apt, but I never recall all > the switches, sorry, I prefer the powerful UI of aptitude (it's just not as > simple as it may look, takes some time to learn how it works and find out > some details) ... anyway, still looks miles ahead of discover to me, except > missing graphics, I can much more easily check all packages, see versions, > download size, etc. discover is very vague about everything and offers just > like the main app packages, it's probably perfect for ordinary/new user, but > I can't seem to get use for it, maybe once when I did need quick overview of > current media players available, at that point discover design works quite > well. That worked indeed!! Many thanks