[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Tom F changed: What|Removed |Added CC||tomfoley...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484940] libkcolorpicker-qt6-0 failed to install in updates
https://bugs.kde.org/show_bug.cgi?id=484940 Tom F changed: What|Removed |Added CC||tomfoley...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484940] libkcolorpicker-qt6-0 failed to install in updates
https://bugs.kde.org/show_bug.cgi?id=484940 --- Comment #7 from Tom F --- Same object is in two packages... E: /var/cache/apt/archives/libkcolorpicker-qt6-0_0.3.1-0xneon+22.04+jammy+release+build2_amd64.deb: trying to overwrite '/usr/lib/x86_64-linux-gnu/libkColorPicker.so.0', which is also in package libkcolorpicker0:amd64 0.1.6-2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455540] Unable to download from Settings with error "invalid number of concurrent streams"
https://bugs.kde.org/show_bug.cgi?id=455540 Tom F changed: What|Removed |Added CC||tomfoley...@gmail.com --- Comment #15 from Tom F --- (In reply to Paul Eveleigh from comment #13) > The update came through for Kubuntu on my desktop and fixed the issue > > MX Linux which I run on my primary desktop was never affected and is still > running free of this bug > > KDE Neon, which I run on my laptop, still has the problem reporting > "SETTINGS invalid number of concurrent streams" > > KDE Neon is currently reporting running Qt version 5.15.4 (In reply to Felix Fischer from comment #10) > Can confirm that just today on arch extra/qt5-base got an update to > 5.15.5+kde+r163-1 that fixed it I'm running KDE Neon testing edition, and QT on that platform is at 5.14.4 as of this moment, with the issue present. So QT 5.15.5 is awaited with anticipation. Thanks for posting and giving us hope :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458600] New: Plasma Crash when turning off monitor in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=458600 Bug ID: 458600 Summary: Plasma Crash when turning off monitor in multi-monitor setup Product: plasmashell Version: 5.25.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tomfoley...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.15.0-46-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: If I'm going to be away from my desk I turn off my displays. Upon return I'm informed Plasma has crashed. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x7f82f16cd9d5 in QFutureWatcherBase::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f82f25dce83 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f82f25e5c98 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f82f18a9c6a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f82f18ac571 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458600] Plasma Crash when turning off monitor in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=458600 --- Comment #1 from Tom F --- Created attachment 151763 --> https://bugs.kde.org/attachment.cgi?id=151763&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 480063] Bad Request after add google drive account (Plasma 6.1Dev in Neon)
https://bugs.kde.org/show_bug.cgi?id=480063 Tom F changed: What|Removed |Added CC||tomfoley...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 480063] Bad Request after add google drive account (Plasma 6.1Dev in Neon)
https://bugs.kde.org/show_bug.cgi?id=480063 --- Comment #5 from Tom F --- Error is also present in the User Edition: KDE Plasma Version 6.1.3 KDE Frameworks Version 6.4.0 QT Version 6.7 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 411010] New: File-->Exit ends with a crash.
https://bugs.kde.org/show_bug.cgi?id=411010 Bug ID: 411010 Summary: File-->Exit ends with a crash. Product: ktorrent Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: tomfoley...@gmail.com Target Milestone: --- Application: ktorrent (5.1.1) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-25-generic x86_64 Distribution: KDE neon Testing Edition -- Information about the crash: - What I was doing when the application crashed: I downloaded a torrent file without any issues. To quit the program I performed a "File-->Exit||" which causes program to crash. I can reporoduce consistently. Running KDE Neon. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd26bc91800 (LWP 6059))] Thread 5 (Thread 0x7fd231569700 (LWP 6072)): #0 0x7fd261a1a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5600b9b69cb4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5600b9b69c60, cond=0x5600b9b69c88) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5600b9b69c88, mutex=0x5600b9b69c60) at pthread_cond_wait.c:655 #3 0x7fd2669a7dbb in QWaitConditionPrivate::wait (deadline=..., this=0x5600b9b69c60) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x5600b9af6010, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fd2669a80c9 in QWaitCondition::wait (this=0x5600b9af6018, mutex=0x5600b9af6010, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7fd26b4d0403 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #7 0x7fd2669a0c72 in QThreadPrivate::start (arg=0x5600b9af6000) at thread/qthread_unix.cpp:361 #8 0x7fd261a146db in start_thread (arg=0x7fd231569700) at pthread_create.c:463 #9 0x7fd265cea88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fd23b1cf700 (LWP 6064)): #0 0x7fd261a1a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5600b949dff8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5600b949dfa8, cond=0x5600b949dfd0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5600b949dfd0, mutex=0x5600b949dfa8) at pthread_cond_wait.c:655 #3 0x7fd23c3da0aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fd23c3d9dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fd261a146db in start_thread (arg=0x7fd23b1cf700) at pthread_create.c:463 #6 0x7fd265cea88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd24d24e700 (LWP 6063)): #0 0x7fd265cddbf9 in __GI___poll (fds=0x7fd2400032e0, nfds=1, timeout=8590) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd25f8765c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd25f8766dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd266bd6dcb in QEventDispatcherGlib::processEvents (this=0x7fd240004850, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fd266b7803a in QEventLoop::exec (this=this@entry=0x7fd24d24dda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fd26699f4ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fd2669a0c72 in QThreadPrivate::start (arg=0x5600b8e68630) at thread/qthread_unix.cpp:361 #7 0x7fd261a146db in start_thread (arg=0x7fd24d24e700) at pthread_create.c:463 #8 0x7fd265cea88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd24e45f700 (LWP 6061)): #0 0x7fd265cd90b4 in __GI___libc_read (fd=11, buf=0x7fd24e45eb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fd25f8bb2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd25f8760b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd25f876570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd25f8766dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd266bd6dcb in QEventDispatcherGlib::processEvents (this=0x7fd248000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fd266b7803a in QEventLoop::exec (this=this@entry=0x7fd24e45ed70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fd26699f4ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7fd26808f015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fd2669a0c72 in QThreadPrivate::start (arg=0x7fd268306d80) at thread/qthread_unix.cpp:361 #10 0x7fd261a1
[plasmashell] [Bug 416617] black screen after updating qml-module-org-kde-qqc2desktopstyle
https://bugs.kde.org/show_bug.cgi?id=416617 Tom F changed: What|Removed |Added CC||tomfoley...@gmail.com --- Comment #1 from Tom F --- I have the identical issue. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416662] Desktop not working after latest update
https://bugs.kde.org/show_bug.cgi?id=416662 Tom F changed: What|Removed |Added CC||tomfoley...@gmail.com --- Comment #9 from Tom F --- I think this is related to https://bugs.kde.org/show_bug.cgi?id=416617. Manually installing qml-module-org-kde-qqc2desktopstyle from a prior build will restore desktop visibility. A quick test proves it. Since I'm not set up for development, I just downloaded https://ubuntu.pkgs.org/19.10/kubuntu-backports-amd64/qml-module-org-kde-qqc2desktopstyle_5.66.0-0ubuntu1~ubuntu19.10~ppa1_amd64.deb.html and put that in it's place. It brought the desktop back. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416662] Desktop not working after latest update
https://bugs.kde.org/show_bug.cgi?id=416662 --- Comment #11 from Tom F --- (In reply to Valter Mura from comment #10) > (In reply to Tom F from comment #9) > > I think this is related to https://bugs.kde.org/show_bug.cgi?id=416617. > > Manually installing qml-module-org-kde-qqc2desktopstyle from a prior build > > will restore desktop visibility. A quick test proves it. Since I'm not set > > up for development, I just downloaded > > https://ubuntu.pkgs.org/19.10/kubuntu-backports-amd64/qml-module-org-kde- > > qqc2desktopstyle_5.66.0-0ubuntu1~ubuntu19.10~ppa1_amd64.deb.html and put > > that in it's place. It brought the desktop back. > > Hi, > > thanks for the hint, of course I'll wait for the solution of the issue by > the developers. > In the meanwhile I downloaded the package you indicate but, as I'm not very > skilled, could you suggest the passages to use for installing it? TIA. Hi Valter, >From the command line change to the folder where you downloaded the package, then run sudo dpkg -i qml-module-org-kde-qqc2desktopstyle_5.66.0-0ubuntu1_ubuntu19.10_ppa1_amd64.deb This will run without errors and your desktop will be restored. After reboot, you will get a notification that there is an update available for this module, but that's currently the version that's broken, so just ignore that until a new one is released. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416662] Desktop not working after latest update
https://bugs.kde.org/show_bug.cgi?id=416662 --- Comment #13 from Tom F --- > Thank you Tom, I run the command indicated, with a little change for me and > the package has been installed and the desktop working again. > > This is the command I ran: sudo dpkg -i > qml-module-org-kde-qqc2desktopstyle_5.62.0-0ubuntu1_amd64.deb > > After that, I launched: kstart5 plasmashell and the desktop reappeared. I > don't know if everything is ok, presently I haven't rebooted yet. > > For sure I'll wait the closing of this bug before launching updates from > pkcon or Discover. I'm glad it worked for you. As for the slight version difference I can understand how that may happen. The page from which you downloaded shows older versions before the most current version. You have to scroll down to the bottom of the page for the latest version in that repo. It's poor design of the page in my opinion, but it is what it is. As long as it's working for you great, just be aware that there is a version 5.66 on that page as opposed to 5.62 which is what you selected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416617] black screen after updating qml-module-org-kde-qqc2desktopstyle
https://bugs.kde.org/show_bug.cgi?id=416617 Tom F changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Tom F --- *** This bug has been marked as a duplicate of bug 416662 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416662] Desktop not working after latest update
https://bugs.kde.org/show_bug.cgi?id=416662 Tom F changed: What|Removed |Added CC||g...@ppetw.com --- Comment #15 from Tom F --- *** Bug 416617 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416662] Desktop not working after latest update
https://bugs.kde.org/show_bug.cgi?id=416662 --- Comment #16 from Tom F --- With latest update the issue no longer occurs. Performing pkcon update and installing the newer packages results in desktop displaying correctly on start/restart. -- You are receiving this mail because: You are watching all bug changes.
