[plasmashell] [Bug 481878] Plasma Crashes while dragging a file to Chromium's icon in the icons-only task manager when there are Chromium windows
https://bugs.kde.org/show_bug.cgi?id=481878 --- Comment #1 from Eric R --- Created attachment 166120 --> https://bugs.kde.org/attachment.cgi?id=166120=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481878] New: Plasma Crashes while dragging a file to Chromium's icon in the icons-only task manager when there are Chromium windows
https://bugs.kde.org/show_bug.cgi?id=481878 Bug ID: 481878 Summary: Plasma Crashes while dragging a file to Chromium's icon in the icons-only task manager when there are Chromium windows Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-21-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Bug 481876 is also my report, from the first time this happened. This is my retry. I also tried it once with only one Chromium window open, but that worked without problem. With two Chromium windows open, I dragged a file to the Chromium icon in the task manager. The panel disappeared as I dragged the file from the panel to the preview of the Chromium window. In spite of that, I was able to complete the drag and drop and attached the file to an email successfully (this time and last time). Also, in both cases, Plasma re-started successfully and I was able to continue working. Until recently, Wayland was a "no-go" on my Thinkpad T510, but now it's working well! Except for this. But again, Plasma re-started without drama. So, overall, Kudos to the Plasma team! The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_acquire, this=) at /usr/include/c++/11/bits/atomic_base.h:818 #7 std::atomic::load(std::memory_order) const (__m=std::memory_order_acquire, this=) at /usr/include/c++/11/atomic:578 #8 QAtomicOps::loadAcquire(std::atomic const&) (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:251 #9 QBasicAtomicPointer::loadAcquire() const (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:255 #10 QBasicAtomicPointer::operator QThreadData*() const (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:251 The reporter indicates this bug may be a duplicate of or related to bug 480474, bug 481876. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481876] New: Plasma crashed while using Chromium
https://bugs.kde.org/show_bug.cgi?id=481876 Bug ID: 481876 Summary: Plasma crashed while using Chromium Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-21-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Plasma crashed while I was using Outlook in Chromium. I had just dragged a file onto the icon-only task manager and into the email to attach it, but I was able to do a little more typing before the crash, so I don't know if dragging the icon onto the task manager is what caused the crash. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_acquire, this=) at /usr/include/c++/11/bits/atomic_base.h:818 #7 std::atomic::load(std::memory_order) const (__m=std::memory_order_acquire, this=) at /usr/include/c++/11/atomic:578 #8 QAtomicOps::loadAcquire(std::atomic const&) (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:251 #9 QBasicAtomicPointer::loadAcquire() const (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:255 #10 QBasicAtomicPointer::operator QThreadData*() const (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:251 The reporter indicates this bug may be a duplicate of or related to bug 480474. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481876] Plasma crashed while using Chromium
https://bugs.kde.org/show_bug.cgi?id=481876 --- Comment #1 from Eric R --- Created attachment 166118 --> https://bugs.kde.org/attachment.cgi?id=166118=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 476113] Plasma crashed upon restart after system update
https://bugs.kde.org/show_bug.cgi?id=476113 --- Comment #3 from Eric R --- Created attachment 162595 --> https://bugs.kde.org/attachment.cgi?id=162595=edit Backtrace generated by coredumpctl Please let me know if you need anything else. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476113] Plasma crashed upon restart after system update
https://bugs.kde.org/show_bug.cgi?id=476113 --- Comment #1 from Eric R --- Created attachment 162574 --> https://bugs.kde.org/attachment.cgi?id=162574=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476113] New: Plasma crashed upon restart after system update
https://bugs.kde.org/show_bug.cgi?id=476113 Bug ID: 476113 Summary: Plasma crashed upon restart after system update Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.2.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: I had just run a system update via Discover, and I allowed the system to restart after the update. After the restart, and after I logged into the X11 Plasma session, Plasma crashed as the UI was rendering. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #8 0x7f894c894ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f894c926a40 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475036] New: Plasma Crashed After Deleting Widget from Panel
https://bugs.kde.org/show_bug.cgi?id=475036 Bug ID: 475036 Summary: Plasma Crashed After Deleting Widget from Panel Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.2.0-33-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.8 [CoredumpBackend] -- Information about the crash: I removed the Application Launcher widget from a secondary Panel. After that, the notification that the widget had been removed showed. I was still in the panel edit mode, and I clicked the close button on the widget removal notification. That is when Plasma crashed. The panels and desktop background image did not re-display. I locked the screen and then unlocked the screen, and then Plasma started and the Dr Konqi window displayed. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #3 0x7f2f6888071f in QtQml::qmlExecuteDeferred(QObject*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7f2f68d536ee in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) (this=this@entry=0x55904db1b940, actions=..., after=..., manager=manager@entry=0x55904e99d430, defaultTarget=0x55904e9ac7a0) at util/qquicktransition.cpp:259 #5 0x7f2f68d48a85 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) (this=0x55904e99d430, list=, transition=0x55904db1b940, defaultTarget=) at util/qquicktransitionmanager.cpp:207 #6 0x7f2f670ea2ef in QObject::event(QEvent*) (this=0x55904e9ac7a0, e=0x7ffd9dba6720) at kernel/qobject.cpp:1369 #7 0x7f2f67d6c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475036] Plasma Crashed After Deleting Widget from Panel
https://bugs.kde.org/show_bug.cgi?id=475036 --- Comment #1 from Eric R --- Created attachment 161959 --> https://bugs.kde.org/attachment.cgi?id=161959=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475035] Plasma Crashed & Restarted After Reboot and Login
https://bugs.kde.org/show_bug.cgi?id=475035 --- Comment #2 from Eric R --- I have rebooted a couple times since this reported crash, and I have not been able to reproduce it. The second of those reboots was after an update by Discover. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475035] Plasma Crashed & Restarted After Reboot and Login
https://bugs.kde.org/show_bug.cgi?id=475035 --- Comment #1 from Eric R --- Created attachment 161958 --> https://bugs.kde.org/attachment.cgi?id=161958=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475035] New: Plasma Crashed & Restarted After Reboot and Login
https://bugs.kde.org/show_bug.cgi?id=475035 Bug ID: 475035 Summary: Plasma Crashed & Restarted After Reboot and Login Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.2.0-33-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.8 [CoredumpBackend] -- Information about the crash: I had just rebooted KDE Neon, and logged in. Plasma crashed after the desktop image showed, but before the panel showed. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x7f4e928e7738 in std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x159) at /usr/include/c++/11/bits/atomic_base.h:818 #7 std::atomic::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x159) at /usr/include/c++/11/atomic:578 #8 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #9 QBasicAtomicPointer::loadRelaxed() const (this=0x159) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #10 QObject::thread() const (this=this@entry=0x55676e240930) at kernel/qobject.cpp:1520 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472544] New: KWin crash on login
https://bugs.kde.org/show_bug.cgi?id=472544 Bug ID: 472544 Summary: KWin crash on login Classification: Plasma Product: kwin Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: aer0...@gmail.com Target Milestone: --- Application: kwin_x11 (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: I just installed Debian 12 with Plasma. I have not installed any plugins. There has been a lot of odd UI flickering, usually in the Panel and on the standard login screen. I suspect some of this is becuase I am running this on a fairly old netbook. Thanks! The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault PID: 955 (kwin_x11) UID: 1000 (ericr) GID: 1000 (ericr) Signal: 11 (SEGV) Timestamp: Sun 2023-07-23 15:01:13 EDT (1min 29s ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service Unit: user@1000.service User Unit: plasma-kwin_x11.service Slice: user-1000.slice Owner UID: 1000 (ericr) Boot ID: 74791329403f4d4c96ef164fefe01815 Machine ID: aa44e909bc6843e585e7776453857a57 Hostname: Eric-Latitude-2120 Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.74791329403f4d4c96ef164fefe01815.955.169013887300.zst (present) Size on Disk: 5.3M Message: Process 955 (kwin_x11) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.6-1.amd64 Module libudev.so.1 from deb systemd-252.6-1.amd64 Stack trace of thread 955: #0 0x7f3ae26aebb4 pthread_sigmask (libc.so.6 + 0x8fbb4) #1 0x7f3ae265b179 sigprocmask (libc.so.6 + 0x3c179) #2 0x7f3ae59e3e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f3ae59e4b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f3ae265af90 n/a (libc.so.6 + 0x3bf90) #5 0x7f3ad6deef54 n/a (i915_dri.so + 0x9eef54) #6 0x7f3ad6de7264 n/a (i915_dri.so + 0x9e7264) #7 0x7f3ad6de2136 n/a (i915_dri.so + 0x9e2136) #8 0x7f3ad69d7997 n/a (i915_dri.so + 0x5d7997) #9 0x7f3ad69d88e7 n/a (i915_dri.so + 0x5d88e7) #10 0x7f3ad6a4d480 n/a (i915_dri.so + 0x64d480) #11 0x7f3ad6a4d7f2 n/a (i915_dri.so + 0x64d7f2) #12 0x7f3ad69e5ee9 n/a (i915_dri.so + 0x5e5ee9) #13 0x7f3ad69df008 n/a (i915_dri.so + 0x5df008) #14 0x7f3ad69df3be n/a (i915_dri.so + 0x5df3be) #15 0x7f3ad69df805 n/a (i915_dri.so + 0x5df805) #16 0x7f3ad6dde2c7 n/a (i915_dri.so + 0x9de2c7) #17 0x7f3ad666b125 n/a (i915_dri.so + 0x26b125) #18 0x7f3ae54ac2fe _ZN4KWin18ItemRendererOpenGL10renderItemEPNS_4ItemEiRK7QRegionRKNS_15WindowPaintDataE (libkwin.so.5 + 0x2ac2fe) #19 0x7f3ae541cd6d _ZN4KWin18EffectsHandlerImpl10drawWindowEPNS_12EffectWindowEiRK7QRegionRNS_15WindowPaintDataE (libkwin.so.5 + 0x21cd6d) #20 0x7f3ae541cd6d _ZN4KWin18EffectsHandlerImpl10drawWindowEPNS_12EffectWindowEiRK7QRegionRNS_15WindowPaintDataE (libkwin.so.5 + 0x21cd6d) #21 0x7f3ae541cbf4 _ZN4KWin18EffectsHandlerImpl11paintWindowEPNS_12EffectWindowEiRK7QRegionRNS_15WindowPaintDataE (libkwin.so.5 + 0x21cbf4) #22 0x7f3ae541cbf4 _ZN4KWin18EffectsHandlerImpl11paintWindowEPNS_12EffectWindowEiRK7QRegionRNS_15WindowPaintDataE (libkwin.so.5 + 0x21cbf4) #23 0x7f3ae54b98f8 _ZN4KWin14WorkspaceScene11paintWindowEPNS_10WindowItemEiRK7QRegion (libkwin.so.5 + 0x2b98f8) #24 0x7f3ae54b9bae _ZN4KWin14WorkspaceScene17paintSimpleScreenEiRK7QRegion (libkwin.so.5 + 0x2b9bae) #25 0x7f3ae541cac4 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x21cac4) #26 0x7f3ae541cac4 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x21cac4) #27 0x7f3ae54b8795 _ZN4KWin14WorkspaceScene5paintEPNS_12RenderTargetERK7QRegion (libkwin.so.5 + 0x2b8795) #28 0x7f3ae54ae499
[plasmashell] [Bug 467825] Plasmashell crashes when using Mullvad GUI App system tray context menu
https://bugs.kde.org/show_bug.cgi?id=467825 --- Comment #4 from Eric R --- (In reply to Fushan Wen from comment #2) > Can you run `QDBUS_DEBUG=1 plasmashell --replace` in a console, reproduce > the crash and paste the output of plasmashell here? I tried this, but after running that command and plasma restarted, when I disconnected and reconnected from the system tray icon a couple of times, I couldn't reproduce the error. Maybe the crash was a one-off? Thanks for taking a look! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467825] Plasmashell crashes when using Mullvad GUI App system tray context menu
https://bugs.kde.org/show_bug.cgi?id=467825 --- Comment #1 from Eric R --- Created attachment 157599 --> https://bugs.kde.org/attachment.cgi?id=157599=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467825] New: Plasmashell crashes when using Mullvad GUI App system tray context menu
https://bugs.kde.org/show_bug.cgi?id=467825 Bug ID: 467825 Summary: Plasmashell crashes when using Mullvad GUI App system tray context menu Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 5.19.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.3 [CoredumpBackend] -- Information about the crash: I used the Mullvad VPN GUI tray icon right-click menu to enable VPN. I don't know if this is a Plasma GUI issue or an issue with the Mullvad GUI app (version 2023.1). Plasmashell crashed "gracefully" and restarted a few seconds later. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #3 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140686968268352) at ./nptl/pthread_kill.c:44 #4 __pthread_kill_internal (signo=6, threadid=140686968268352) at ./nptl/pthread_kill.c:78 #5 __GI___pthread_kill (threadid=140686968268352, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #6 0x7ff464842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7ff4648287f3 in __GI_abort () at ./stdlib/abort.c:79 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466862] Cannot pkcon update due to unmet dependencies with poppler and okular-backends
https://bugs.kde.org/show_bug.cgi?id=466862 --- Comment #22 from Eric R --- (In reply to Jonathan Riddell from comment #19) > It's a new bug due to libharfbuzz0b not having an i386 build. I've removed > harfbuzz now and will snapshot once tested I agree, this is now fixed for me. I did "sudo pkcon refresh" and it looked like a normal refresh. So far, so good. I did "sudo pkcon update" and I had a look at what it wanted to update. This time, it didn't want to delete anything, just update a bunch of packages. So I hit "Y" and let it run. Then I rebooted. Everything looks fine now. I don't think I'll blindly do "sudo pkcon refresh && sudo pkcon update -y" any more, though. I'm going to pay attention to what pkcon has to tell me before I let it proceed! As far as I'm concerned, this bug can be closed. Thanks to everyone who worked on this, and on ALL of KDE! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466862] Cannot pkcon update due to unmet dependencies with poppler and okular-backends
https://bugs.kde.org/show_bug.cgi?id=466862 --- Comment #18 from Eric R --- (In reply to Carlos De Maine from comment #17) > i prefer apt dist-upgrade as it lets you review what packages it installs > and removes and asks for your confirmation before doing anything, > > sudo apt install --install-recommends plasma-desktop neon-desktop > > should also bring back it to a normal install Carlos, This seems to have gone from a couple of broken packages to a BUNCH of broken packages and even unusable systems for a lot of users, according to what I'm seeing here, in the KDE forums, and on Reddit. So I wonder now, is this still the same bug, or should there be a new bug? Is this perhaps fixed at the repo/dev end, but now users just need to clean up broken packages? Just trying to figure out what to do next, for myself and other users who seem to have this same problem. I haven't tried your latest suggestions yet, because I'm waiting to see if there is any other movement on this. Thanks, Eric -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466862] Cannot pkcon update due to unmet dependencies with poppler and okular-backends
https://bugs.kde.org/show_bug.cgi?id=466862 --- Comment #9 from Eric R --- Hi. sudo pkcon refresh && sudo pkcon update -y now produces: Fatal error: The following packages have unmet dependencies: libokular5core10: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5printsupport5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed drkonqi-pk-debug-installer: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed qt5-gtk-platformtheme: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed okular-backends: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5printsupport5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed gwenview: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5printsupport5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed qtwayland5: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5waylandclient5 (>= 5.15.8+p22.04+tunstable+git20230310.0045) but 5.15.8+p22.04+tunstable+git20230304.0049-0 is to be installed libqt5waylandcompositor5: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed libqt5widgets5: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed okular-dbgsym: Depends: okular (= 4:22.12.3-0xneon+22.04+jammy+release+build22) but 4:22.12.2-0xneon+22.04+jammy+release+build19 is to be installed okular: Depends: libokular5core10 (= 4:22.12.2-0xneon+22.04+jammy+release+build19) but 4:22.12.3-0xneon+22.04+jammy+release+build22 is to be installed okular-extra-backends: Depends: libokular5core10 (= 4:22.12.2-0xneon+22.04+jammy+release+build19) but 4:22.12.3-0xneon+22.04+jammy+release+build22 is to be installed So I suppose the original problem is fixed, but now there are other broken packages. sudo apt update && sudo apt dist-upgrade upgrades other packages, but the broken packages are still broken. I also tried this: sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded. What else should I try? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466862] Cannot pkcon update due to unmet dependencies with poppler and okular-backends
https://bugs.kde.org/show_bug.cgi?id=466862 --- Comment #4 from Eric R --- (In reply to Carlos De Maine from comment #2) > a new package has just been produced in release which links to the correct > version of libpoppler*. it will be promoted to user in the next few days. Hi. This is still going on. When is "the next few days"? Where can I see the releases & updates? Do I need to do anything else to fix the broken packages? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466862] Cannot pkcon update due to unmet dependencies with poppler and okular-backends
https://bugs.kde.org/show_bug.cgi?id=466862 --- Comment #3 from Eric R --- (In reply to Carlos De Maine from comment #2) > a new package has just been produced in release which links to the correct > version of libpoppler*. it will be promoted to user in the next few days. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #9 from Eric R --- (In reply to Nate Graham from comment #8) > Can you confirm that the items are still there after you restart the > computer? Yes. Just to make sure, I just rebooted now, and the same three items are there. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #7 from Eric R --- I can reproduce "Forget Recent Files" never working for Firefox. Please see new "Comparison of Menus, 2022 & 2023" attachment. Currently on firefox/jammy,now 110.0.1+build2-0ubuntu0.22.04.1~mt1 amd64 [installed,automatic] Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz Memory: 7.6 GiB of RAM Graphics Processor: NVA8 Manufacturer: LENOVO Product Name: 43142MU System Version: ThinkPad T510 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #6 from Eric R --- Created attachment 157038 --> https://bugs.kde.org/attachment.cgi?id=157038=edit Comparison of Menus, 2022 & 2023 Firefox task bar right-click menus from 2022 and 2023 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466862] New: Cannot pkcon update due to unmet dependencies with poppler and okular-backends
https://bugs.kde.org/show_bug.cgi?id=466862 Bug ID: 466862 Summary: Cannot pkcon update due to unmet dependencies with poppler and okular-backends Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: aer0...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. sudo pkcon refresh && sudo pkcon update -y 2. 3. OBSERVED RESULT Fatal error: The following packages have unmet dependencies: libpoppler-qt5-1: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed okular-backends: Depends: libokular5core10 (= 4:22.12.2-0xneon+22.04+jammy+release+build19) but 4:22.12.3-0xneon+22.04+jammy+release+build20 is to be installed libpoppler-cpp0v5: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed poppler-utils: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed libpoppler-glib8: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed EXPECTED RESULT A successful update of packages. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz Memory: 7.6 GiB of RAM Graphics Processor: NVA8 Manufacturer: LENOVO Product Name: 43142MU System Version: ThinkPad T510 ADDITIONAL INFORMATION Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462783] Unknown Error Code 150 when launching Kate from app menu
https://bugs.kde.org/show_bug.cgi?id=462783 --- Comment #2 from Eric R --- (In reply to Christoph Cullmann from comment #1) > No idea what that should be, please try 22.12 Ok, yup, works for me in 22.12, too! Thanks anyhow! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462783] Unknown Error Code 150 when launching Kate from app menu
https://bugs.kde.org/show_bug.cgi?id=462783 Eric R changed: What|Removed |Added CC||aer0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462783] New: Unknown Error Code 150 when launching Kate from app menu
https://bugs.kde.org/show_bug.cgi?id=462783 Bug ID: 462783 Summary: Unknown Error Code 150 when launching Kate from app menu Classification: Applications Product: kate Version: 22.08.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: aer0...@gmail.com Target Milestone: --- Created attachment 154428 --> https://bugs.kde.org/attachment.cgi?id=154428=edit Error dialog at Kate launch SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When I launch Kate from the Application Launcher, Kate shows me a dialog stating "Unknown error code 150 Bad parameters" STEPS TO REPRODUCE 1. Launch Kate from Application Launcher 2. 3. OBSERVED RESULT Dialog box stating "Unknown error code 150 Bad parameters". See attachment. After dismissing dialog, Kate seems to function normally. EXPECTED RESULT Kate launches without an error dialog SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz Memory: 7.6 GiB of RAM Graphics Processor: NVA8 Manufacturer: LENOVO Product Name: 43142MU System Version: ThinkPad T510 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #3 from Eric R --- Also present in KDE Neon 5.25 w/ Plasma 5.25.3, Firefox 102.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 Eric R changed: What|Removed |Added CC||aer0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455594] On Nvidia X11, snapping/unsnapping/unmaximizing Firefox causes screen to flicker
https://bugs.kde.org/show_bug.cgi?id=455594 --- Comment #3 from Eric R --- Created attachment 150094 --> https://bugs.kde.org/attachment.cgi?id=150094=edit Firefox flickering when Quick-Tiling to Left with Meta+L Firefox flickering when Quick-Tiling to Left with Meta+L, then no flicker when tiling by dragging title bar to left. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455594] On Nvidia X11, snapping/unsnapping/unmaximizing Firefox causes screen to flicker
https://bugs.kde.org/show_bug.cgi?id=455594 Eric R changed: What|Removed |Added CC||aer0...@gmail.com --- Comment #2 from Eric R --- I get the same sort of behavior when I use Meta+L to "Quick Tile to Left" with either Firefox 101.0.1 or Chromium 103.0.5060.53 in KDE Neon 5.25. If I drag the title bar to the left to tile to the left, I do not see this behavior. See the attached gif. In it, I start with Firefox maximized, then press Meta+L to tile to the left to exhibit the flicker. Then I Meta+Up to maximize again, then I drag the window to the left to tile without flicker, then I maximize with the title bar Maximize button. Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-51-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz Memory: 7.6 GiB of RAM Graphics Processor: NVA8 Manufacturer: LENOVO Product Name: 43142MU System Version: ThinkPad T510 ``` System:Host: Marvin Kernel: 5.13.0-51-generic x86_64 bits: 64 compiler: N/A Console: tty 0 wm: kwin_x11 dm: SDDM Distro: KDE neon 20.04 5.25 base: Ubuntu 20.04 LTS Focal Machine: Type: Laptop System: LENOVO product: 43142MU v: ThinkPad T510 serial: R8322DB Chassis: type: 10 serial: R8322DB Mobo: LENOVO model: 43142MU serial: 1ZHP102123Z BIOS: LENOVO v: 6MET91WW (1.51 ) date: 06/05/2012 CPU: Topology: Dual Core model: Intel Core i5 M 520 bits: 64 type: MT MCP arch: Nehalem rev: 2 L1 cache: 32 KiB L2 cache: 3072 KiB L3 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19151 Speed: 1333 MHz min/max: 1199/2400 MHz Core speeds (MHz): 1: 1455 2: 1463 3: 1415 4: 1463 Graphics: Device-1: NVIDIA GT218M [NVS 3100M] vendor: Lenovo driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0a6c Display: server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 resolution: 1366x768~60Hz OpenGL: renderer: NVA8 v: 3.3 Mesa 21.2.6 direct render: Yes ``` Please let me know if I can provide more info. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #23 from Eric R --- (In reply to Jonathan Riddell from comment #21) > Great, sorry for the faff. I've made a To Do item to look at doing more QA > of 32 bit packages when a new Qt gets rolled out. Thanks, Jonathan! There is also the question about why kwin-x11 got uninstalled. Again, there were comments on r/kdeneon from others for whom kwin-x11 got uninstalled. Discover warned me that kwin-x11 would be uninstalled, but I decided to trust the process and let it happen. Should that be a separate bug? Thx! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #20 from Eric R --- When I did the update yesterday, I noticed that kwin-x11 got uninstalled. So I re-installed it. Now everything seems to be back to normal on an X11 session in Neon. In case it helps someone, here is what I did: sudo apt update; sudo apt install neon-desktop; sudo apt full-upgrade sudo apt install kwin-x11 sudo reboot now Please let me know if I can provide any more information. Thanks Jonathan and everyone! (In reply to Eric R from comment #19) > Jonathan, > > I tried this, and it didn’t help. The windows still don’t have title bars. > > What else can I try, or what other info can I gather? > > Thanks! > -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #19 from Eric R --- Jonathan, I tried this, and it didn’t help. The windows still don’t have title bars. What else can I try, or what other info can I gather? Thanks! (In reply to Eric R from comment #16) > FWIW, it wasn’t just you and me. There were some other comments about this > in r/kdeneon on Reddit. > > I’ll try this when I get home from work. > > Thanks Peter and Jonathan! > > (In reply to Peter from comment #13) > > What was it about our set ups that meant only Eric and me were seeing this > > problem? Also, is there anywhere the intelligent layman can read about > > what lcms does? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #16 from Eric R --- FWIW, it wasn’t just you and me. There were some other comments about this in r/kdeneon on Reddit. I’ll try this when I get home from work. Thanks Peter and Jonathan! (In reply to Peter from comment #13) > What was it about our set ups that meant only Eric and me were seeing this > problem? Also, is there anywhere the intelligent layman can read about > what lcms does? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #9 from Eric R --- (In reply to Jonathan Riddell from comment #4) > Did you have any non-default window themes? The new version of Qt likely > means any need a recompile. I don't think so. Let's see... * Global Theme: Breeze Dark * Application Style: Fusion * Plasma Style: "No Items Found" -Interesting * Colors: Breeze Dark * Window Decorations: Breeze * Fonts: Different sizes of Ubuntu Condensed * Icons: Tela black dark * Cursors: Breeze * Launch Feedback: Bouncing * Splash Screen: Breeze * Boot Splash Screen: thanks! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #5 from Eric R --- Also, I did another `pkcon refresh && pkcon update -y` and it told me that "The following packages have unmet dependencies:" liblcms2-utils & kwin-common both say "liblcms2-2 (>= 2.12~rc1) but 2.9-4 is to be installed" -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #3 from Eric R --- Created attachment 149161 --> https://bugs.kde.org/attachment.cgi?id=149161=edit Stack trace from attempted bug report after May 23 2022 update. I'm not the OP, but I have what looks like the same problem after updating on the evening of May 23, 2022. I tried to file a bug with Kcrash, but it failed. However, I did get this stack trace. I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 Eric R changed: What|Removed |Added CC||aer0...@gmail.com --- Comment #2 from Eric R --- Hello. I got what I think is the same problem after the update last night. I tried to report the bug with kcrash, but I was unable to complete it. However, I got the stack trace before it failed. I'm attaching it here. I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436939] startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=436939 --- Comment #2 from Eric R --- (In reply to Nate Graham from comment #1) > A lot has changed since then, and I don't recommend using the Wayland > session in any Plasma version prior to 5.23. Can you try again in 5.23 to > see if it's still happening? Thanks! I haven't been able to update my Fedora 34 VM to try this again. The X11 session isn't working much better than the Wayland session, and I can't run much of anything on this VM. I think we should close this bug, because I think my VM setup is the real problem, and there doesn't seem to be a way for me to provide more useful info. Thanks anyhow! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445698] Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or "Che
https://bugs.kde.org/show_bug.cgi?id=445698 --- Comment #3 from Eric R --- I tried to generate one at the time with the Crash Report tool, but it didn't. The crash hasn't happened for about a week, and I have done a couple of successful updates since then, including one just now. I read the link about backtraces, and I made sure I have GDM and coredumctl installed. coredumpctl didn't get me anything just now. So, if it happens again, I'll try to get you a backtrace or a coredump so you have something to work with. Meanwhile, it seems that I can work around this on the command line with `pkcon update`, `flatpak update`, and `snap refresh`. Recently, I have seen at least a couple other people asking on Reddit about this same behavior, I think in r/kde or r/kdeneon IIRC. I don't think any of them had any more info than I do, though. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445698] Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or "Che
https://bugs.kde.org/show_bug.cgi?id=445698 --- Comment #1 from Eric R --- Update: I also couldn’t update with pkcon. Pkcon seemed to hang and “sit and spin” for about a half-hour at the “Running” phase of the update. I updated my flatpaks on the command line, and then I tried pkcon again, and pkcon still seemed stuck. So I tried Discover again, and it worked. It seemed to install the updates unusually quickly. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445698] New: Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or
https://bugs.kde.org/show_bug.cgi?id=445698 Bug ID: 445698 Summary: Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or "Check for Updates" doesn't seem to do anything. Product: Discover Version: 5.23.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: aer0...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 143694 --> https://bugs.kde.org/attachment.cgi?id=143694=edit Discover's Updates list repeatedly refreshing SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Click "Updates" in system tray 2. Wait for Discover to get updates OBSERVED RESULT Discover's Updates list blinks/refreshes repeatedly. Clicking "Update All" does nothing. Discover eventually crashes. EXPECTED RESULT Discover's Updates list shows, and allows user to click the "Update All" button to update packages. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.23.3 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 440991] Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login
https://bugs.kde.org/show_bug.cgi?id=440991 --- Comment #1 from Eric R --- Hi. I found [this thread on the Nvidia Linux Dev Forums] (https://forums.developer.nvidia.com/t/nvidia-340-108-driver-kernel-5-11-support/182663) ...that points out incompatibility between nvidia-340.108 and the 5.11.x kernel. I will report my bug there. It looks like Nvidia has been notified, but they don't seem to be doing anything about it at the moment. I have uninstalled `nvidia-340` and gone back to the nouveau driver, and all seems well in Neon 5.22.4 with the 5.11.0-27 kernel (updated since I reported this). I don't know if any further action is required here, other than watching for an update to nvidia-340. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436939] startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=436939 Eric R changed: What|Removed |Added CC||aer0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 440991] Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login
https://bugs.kde.org/show_bug.cgi?id=440991 Eric R changed: What|Removed |Added CC||aer0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 440991] New: Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login
https://bugs.kde.org/show_bug.cgi?id=440991 Bug ID: 440991 Summary: Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: aer0...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Today I updated Neon 5.22.4, using Discover, and after the installation(s) and reboot(s), laptop froze on Neon startup splash. I was able to Alt-F2 to log in via CLI. I found a [thread on the Neon forums](https://forum.kde.org/viewtopic.php?f=309=172175=683dca1e932bc55ef0216b2f1b9c2539) that suggested there is a problem with the Nvidia 340.108 driver under Kernel 5.11.0-25, and to use the Grub menu to boot to Kernal 5.8.0-63 instead. This workaround has allowed me to log into Plasma. STEPS TO REPRODUCE 1. Apply current updates in Discover 2. Allow machine to install and reboot OBSERVED RESULT Neon Boot Splash freezes, but I can Alt-F2 to the CLI. EXPECTED RESULT Expected to be able to log in via GUI/Plymouth login screen SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.13.3 ADDITIONAL INFORMATION sudo inxi -Fxxx: https://bin.privacytools.io/?66a914c115f9d56f#2J19XX2qKhZmjtwFA1zHMyeS4LyeAcM5E51MdeHMNJhk Please let me know if I can provide more info. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 436939] New: startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=436939 Bug ID: 436939 Summary: startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aer0...@gmail.com Target Milestone: --- Application: kde-open5 (5.21.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.3 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I had just installed Fedora 34 Plasma in a VM in VirutualBox. I added the Guest Additions CD to the VM, and I was mounting the CD when the session went black, and showed an xmessage dialog with the message "startkde: Could not start Plasma session." I am running a Wayland session. FWIW, the host is Ubuntu MATE 20.04.2 Also FWIW, I saw this a few times during installation, and using an Xsession worked better. - Unusual behavior I noticed: The black screen with xmessage dialog described above. Thanks! The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KIO Client (kde-open5), signal: Aborted [KCrash Handler] #4 0x7f7884b6e292 in raise () from /lib64/libc.so.6 #5 0x7f7884b578a4 in abort () from /lib64/libc.so.6 #6 0x7f7884fd042d in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #7 0x7f78810d6ef3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5 #8 0x7f78810e56fa in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #9 0x7f78851ce4fd in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f78851ea6d2 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7f788519c9b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #12 0x7f78851a4544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #13 0x55c9322474f5 in main () [Inferior 1 (process 2370) detached] Possible duplicates by query: bug 436863, bug 435427, bug 433524, bug 432084, bug 431077. Reported using DrKonqi This report was filed against 'kde' because the product 'kde-open5' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 423164] Black square instead of close button & notification pie chart timer
https://bugs.kde.org/show_bug.cgi?id=423164 Eric R changed: What|Removed |Added CC||aer0...@gmail.com --- Comment #4 from Eric R --- FWIW, I am seeing the same issue, black square instead of close button and pie chart timer. Please let me know if I can provide more info. I hope this helps. $ sudo inxi -Fxx [sudo] password for erinehart42: System:Host: Marvin Kernel: 5.3.0-59-generic x86_64 bits: 64 gcc: 7.5.0 Console: tty 1 dm: sddm,sddm Distro: KDE neon User Edition 5.19 Machine: Device: laptop System: LENOVO product: 43142MU v: ThinkPad T510 serial: R8322DB Mobo: LENOVO model: 43142MU serial: 1ZHP102123Z BIOS: LENOVO v: 6MET91WW (1.51 ) date: 06/05/2012 Chassis: type: 10 serial: R8322DB BatteryBAT0: charge: 74.0 Wh 96.2% condition: 76.8/94.0 Wh (82%) volts: 12.4/10.8 model: Panasonic 42T4801 serial: 723 status: N/A hidpp__0: charge: N/A condition: NA/NA Wh volts: NA model: Logitech Wireless Mouse serial: 4055-d2-2c-6b-b6 status: Discharging CPU: Dual core Intel Core i5 M 520 (-MT-MCP-) arch: Nehalem rev.2 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9575 clock speeds: min/max: 1199/2400 MHz 1: 2710 MHz 2: 2780 MHz 3: 2649 MHz 4: 2638 MHz Graphics: Card: NVIDIA GT218M [NVS 3100M] bus-ID: 01:00.0 chip-ID: 10de:0a6c Display Server: X.Org 1.19.6 driver: nvidia Resolution: 1366x768@59.64hz OpenGL: renderer: NVS 3100M/PCIe/SSE2 version: 3.3.0 NVIDIA 340.108 Direct Render: Yes Audio: Card-1 Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:3b56 Card-2 NVIDIA High Definition Audio Controller driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 10de:0be3 Sound: Advanced Linux Sound Architecture v: k5.3.0-59-generic Network: Card-1: Intel 82577LM Gigabit Network Connection driver: e1000e v: 3.2.6-k port: 1820 bus-ID: 00:19.0 chip-ID: 8086:10ea IF: enp0s25 state: down mac: 00:26:2d:f2:a3:9b Card-2: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi bus-ID: 03:00.0 chip-ID: 8086:0084 IF: wlp3s0 state: up mac: 00:26:c7:20:46:96 Drives:HDD Total Size: 1000.2GB (9.5% used) ID-1: /dev/sda model: TOSHIBA_HDWJ110 size: 1000.2GB serial: 373XC952T temp: 37C Partition: ID-1: / size: 916G used: 89G (11%) fs: ext4 dev: /dev/sda1 RAID: System: supported: N/A No RAID devices: /proc/mdstat, md_mod kernel module present Unused Devices: none Sensors: System Temperatures: cpu: 52.0C mobo: 0.0C gpu: 0.0: Fan Speeds (in rpm): cpu: 2731 Info: Processes: 240 Uptime: 19:12 Memory: 4491.6/7821.9MB Init: systemd v: 237 runlevel: 5 Gcc sys: 7.5.0 Client: Shell (sudo running in bash) inxi: 2.3.56 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420826] System Settings Crashed on Launch
https://bugs.kde.org/show_bug.cgi?id=420826 --- Comment #2 from Eric R --- (In reply to Christoph Feck from comment #1) > Are you using NVIDIA binary OpenGL drivers? > > Probably a duplicate of bug 346519. Yes I am. Also, this hasn't happened again since a reboot. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420828] New: Discover Crashes on Launch
https://bugs.kde.org/show_bug.cgi?id=420828 Bug ID: 420828 Summary: Discover Crashes on Launch Product: Discover Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: aer0...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I tried to open Discover from the app menu to install software. I had run an update in Discover earlier, it was fine. Just a minute ago, System Settings also crashed on launch, so maybe something larger is happening. I have not yet tried a restart. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb57b99c980 (LWP 23695))] Thread 9 (Thread 0x7fb53b45a700 (LWP 23706)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fb577279e04 in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb5774a231e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb5753ba70b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7fb575462b6d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7fb5774a2139 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb5753b0879 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7fb5753b1125 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7fb5774a2139 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb57545b10f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7fb5754502bb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7fb5754508fd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7fb57542c841 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7fb5774a2139 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fb5753f70c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7fb5753f716c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7fb57540a781 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7fb578c489ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fb578c4fbb0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb577467128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb5774c6ff8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb570e54417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fb570e54650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fb570e546dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fb5774c642c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fb5774659aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fb5772763d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb5772778ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fb5730b26db in start_thread (arg=0x7fb53b45a700) at pthread_create.c:463 #29 0x7fb576b6c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fb540872700 (LWP 23705)): #0 __GI___pthread_getspecific (key=5) at pthread_getspecific.c:30 #1 0x7fb570e7c660 in g_thread_self () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb570e546cd in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb5774c644b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb5774659aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb5772763d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb5772778ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb5730b26db in start_thread (arg=0x7fb540872700) at pthread_create.c:463 #8 0x7fb576b6c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb522d43700 (LWP 23703)): #0 0x7fb576b5b0b4 in __GI___libc_read (fd=17, buf=0x7fb522d42b50,
[systemsettings] [Bug 420826] New: System Settings Crashed on Launch
https://bugs.kde.org/show_bug.cgi?id=420826 Bug ID: 420826 Summary: System Settings Crashed on Launch Product: systemsettings Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I attempted to launch System Settings from the app menu. I had run it earlier and it ran fine. I tried to launch it a couple more times, and it didn't work. I have not yet tried a restart. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efd19f79840 (LWP 23135))] Thread 5 (Thread 0x7efce86bf700 (LWP 23140)): #0 0x7efd0e9b1642 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7efd0e96afd9 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efd0e96b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efd0e96b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efd15d1d44b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7efd15cbc9aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7efd15acd3d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7efd13611fc5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7efd15ace8ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7efd10deb6db in start_thread (arg=0x7efce86bf700) at pthread_create.c:463 #10 0x7efd153c388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7efcf18f9700 (LWP 23139)): #0 0x7efd15acee9f in QMutex::unlock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7efd15d1dac7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7efd0e96afe1 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efd0e96b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efd0e96b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efd15d1d44b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7efd15cbc9aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7efd15acd3d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7efd13611fc5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7efd15ace8ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7efd10deb6db in start_thread (arg=0x7efcf18f9700) at pthread_create.c:463 #11 0x7efd153c388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7efcfbfff700 (LWP 23138)): #0 __lll_unlock_wake () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371 #1 0x7efd10def7df in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7efd1078b8a0) at pthread_mutex_unlock.c:54 #2 __GI___pthread_mutex_unlock (mutex=0x7efd1078b8a0) at pthread_mutex_unlock.c:345 #3 0x7efd10507b79 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #4 0x7efd1050b888 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #5 0x7efd0d46cfe1 in ?? () from /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.108 #6 0x7efd0e9b02b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7efd0e96b0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7efd0e96b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7efd0e96b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7efd15d1d44b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7efd15cbc9aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7efd15acd3d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7efd161a9555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #14 0x7efd15ace8ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7efd10deb6db in start_thread (arg=0x7efcfbfff700) at pthread_create.c:463 #16 0x7efd153c388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7efd03fb0700
