[plasmashell] [Bug 476438] crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 Adi Stadi changed: What|Removed |Added Resolution|UPSTREAM|MOVED --- Comment #5 from Adi Stadi --- https://forums.developer.nvidia.com/t/kde-wayland-doesnt-work-on-the-545-drivers/269794 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 Adi Stadi changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Adi Stadi --- stupid me. released version is different: with 535.129.03: all fine with 545.29.02: crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 --- Comment #1 from Adi Stadi --- no more crash with released nvidia 545.29.03 ``` ~ inxi -G Graphics: Device-1: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 535.129.03 Device-2: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: fbdev,modesetting,vesa gpu: nvidia resolution: 2560x1440 API: OpenGL v: 4.6.0 NVIDIA 535.129.03 renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 Adi Stadi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Adi Stadi --- works with released nvidia driver 545.29.03 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] New: crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 Bug ID: 476438 Summary: crash after login with nvidia 545.29.02 Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: spaced.wom...@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.5.9-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: after login plasmashell crashes using latest nvidia beta driver 545.29.02 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1780 (plasmashell) UID: 1000 (adi) GID: 1000 (adi) Signal: 11 (SEGV) Timestamp: Wed 2023-11-01 22:54:03 CET (44s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (adi) Boot ID: c59c5c6ee9cd439d853aae416a6adafc Machine ID: 22b9d9d52a5e4f7cbb40ed1b383dd97c Hostname: adipc Storage: /var/lib/systemd/coredump/core.plasmashell.1000.c59c5c6ee9cd439d853aae416a6adafc.1780.169887564300.zst (present) Size on Disk: 92.5M Message: Process 1780 (plasmashell) of user 1000 dumped core. Stack trace of thread 1780: #0 0x7fb4aa691dec __pthread_kill_implementation (libc.so.6 + 0x91dec) #1 0x7fb4aa63f0c6 raise (libc.so.6 + 0x3f0c6) #2 0x7fb4ad267d9a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d9a) #3 0x7fb4aa63f190 __restore_rt (libc.so.6 + 0x3f190) #4 0x7fb4aa691dec __pthread_kill_implementation (libc.so.6 + 0x91dec) #5 0x7fb4aa63f0c6 raise (libc.so.6 + 0x3f0c6) #6 0x7fb4aa63f190 __restore_rt (libc.so.6 + 0x3f190) #7 0x7fb4aa68c4ec __futex_abstimed_wait_common (libc.so.6 + 0x8c4ec) #8 0x7fb4aa68f230 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8f230) #9 0x7fb4aaf09a1b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0x109a1b) #10 0x7fb4acc3b0f8 n/a (libQt5Quick.so.5 + 0x23b0f8) #11 0x7fb4acc3be33 n/a (libQt5Quick.so.5 + 0x23be33) #12 0x7fb4ab5890a5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1890a5) #13 0x7fb4ad699bf1 _ZN11PlasmaQuick6Dialog5eventEP6QEvent (libKF5PlasmaQuick.so.5 + 0x2abf1) #14 0x7fb4abda519e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1a519e) #15 0x7fb4ab0ed198 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed198) #16 0x7fb4ab57e44d _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x17e44d) #17 0x7fb4ab55038c _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x15038c) #18 0x7fb4ac9617b0 n/a (libQt5WaylandClient.so.5 + 0xbc7b0) #19 0x7fb4a9b50f30 n/a (libglib-2.0.so.0 + 0x5bf30) #20 0x7fb4a9b52b58 n/a (libglib-2.0.so.0 + 0x5db58) #21 0x7fb4a9b5320c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #22 0x7fb4ab1460d6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3460d6) #23 0x7fb4ab0ebc2b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ebc2b) #24 0x7fb4ab0f40c0 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2f40c0) #25 0x55780925baa1 n/a (plasmashell + 0x29aa1) #26 0x7fb4aa6281b0 __libc_start_call_main (libc.so.6 + 0x281b0) #27 0x7fb4aa628279 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x28279) #28 0x55780925be35 n/a (plasmashell + 0x29e35) Stack trace of thread 1783: #0 0x7fb4aa709d7f __poll (libc.so.6 + 0x109d7f) #1 0x7fb4a9b52aff n/a (libglib-2.0.so.0 + 0x5daff) #2 0x7fb4a9b5320c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #3
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open when using an NVIDIA GPU on Wayland
https://bugs.kde.org/show_bug.cgi?id=455575 Adi Stadi changed: What|Removed |Added CC||andihartm...@freenet.de --- Comment #69 from Adi Stadi --- *** Bug 454671 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 454671] krunner hangs after ALT-F2 and typing in the first letter - must be killed afterwards (wayland / nvidia)
https://bugs.kde.org/show_bug.cgi?id=454671 Adi Stadi changed: What|Removed |Added CC||spaced.wom...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Adi Stadi --- *** This bug has been marked as a duplicate of bug 455575 *** -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 411628] New: kf5.kio.core: couldn't create slave, crash
https://bugs.kde.org/show_bug.cgi?id=411628 Bug ID: 411628 Summary: kf5.kio.core: couldn't create slave, crash Product: kio-gdrive Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: spaced.wom...@gmail.com Target Milestone: --- SUMMARY kf5.kio.core: couldn't create slave: "klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/gdrive.so'." STEPS TO REPRODUCE 1. go to dolphin, network select gdrive 2. 3. OBSERVED RESULT loading error EXPECTED RESULT gdrive open SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20190902 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 5.2.11-1-default kio-gdrive: 1.2.7 ADDITIONAL INFORMATION Process 13869 (gdrive.so) of user 1000 dumped core. Stack trace of thread 13869: #0 0x7f61ad7f4890 n/a (libKPimGAPIDrive.so.5) #1 0x7f61ad7bd998 n/a (libKPimGAPIDrive.so.5) #2 0x7f61b2fb3a1a call_init.part.0 (ld-linux-x86-64.so.2) #3 0x7f61b2fb3b19 _dl_init (ld-linux-x86-64.so.2) #4 0x7f61b2fb79fe dl_open_worker (ld-linux-x86-64.so.2) #5 0x7f61b2edba51 _dl_catch_exception (libc.so.6) #6 0x7f61b2fb729a _dl_open (ld-linux-x86-64.so.2) #7 0x7f61b1dca258 dlopen_doit (libdl.so.2) #8 0x7f61b2edba51 _dl_catch_exception (libc.so.6) #9 0x7f61b2edbaef _dl_catch_error (libc.so.6) #10 0x7f61b1dca975 _dlerror_run (libdl.so.2) #11 0x7f61b1dca2e6 dlopen@@GLIBC_2.2.5 (libdl.so.2) #12 0x7f61b22d4adf n/a (libQt5Core.so.5) #13 0x7f61b22cece8 _ZN8QLibrary4loadEv (libQt5Core.so.5) #14 0x560497ef8262 n/a (kdeinit5) #15 0x560497ef9288 n/a (kdeinit5) #16 0x560497ef9c64 n/a (kdeinit5) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389448] Width and height of the window doesn't set correctly on HiDPI screen after upgrade to plasma 5.12
https://bugs.kde.org/show_bug.cgi?id=389448 --- Comment #9 from Adi Stadi <spaced.wom...@gmail.com> --- sorry, wrong workaround, i use export QT_SCREEN_SCALE_FACTORS=1 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389448] Width and height of the window doesn't set correctly on HiDPI screen after upgrade to plasma 5.12
https://bugs.kde.org/show_bug.cgi?id=389448 Adi Stadi <spaced.wom...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Adi Stadi <spaced.wom...@gmail.com> --- workaround: QT_AUTO_SCREEN_SCALE_FACTOR=1;yakuake Happens only when screen scaling is active (scaling 1.5 for my hdpi screen) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389448] Width and height of the window doesn't set correctly on HiDPI screen after upgrade to plasma 5.12
https://bugs.kde.org/show_bug.cgi?id=389448 Adi Stadi <spaced.wom...@gmail.com> changed: What|Removed |Added CC||spaced.wom...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
