[frameworks-plasma] [Bug 450409] New: desktop moves up when mouse cursor is on panel taskbar
https://bugs.kde.org/show_bug.cgi?id=450409 Bug ID: 450409 Summary: desktop moves up when mouse cursor is on panel taskbar Product: frameworks-plasma Version: 5.90.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: plasma-b...@kde.org Reporter: kel...@kelvineckert.de CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- SUMMARY *** When moving the mouse cursor on the panel taskbar, the entire desktop shifts upward. There is no second virtual desktop set up. No second monitor. Happened after update to KDE 5.24. Expected: desktop should not shift. Screen edges setting is set to "switch desktop on edge" - "disabled". 3 bottom edges are set to "no action". *** STEPS TO REPRODUCE 1. move mouse cursor to bottom panel taskbar OBSERVED RESULT desktop moves up (black background) EXPECTED RESULT desktop stays fullscreen SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Tumbleweed 20220214 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 450409] desktop moves up when mouse cursor is on panel taskbar
https://bugs.kde.org/show_bug.cgi?id=450409 Kelvin changed: What|Removed |Added CC||kel...@kelvineckert.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 450409] desktop moves up when mouse cursor is on panel taskbar
https://bugs.kde.org/show_bug.cgi?id=450409 --- Comment #1 from Kelvin --- sorry, it's bottom screen edge, not taskbar -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 450409] desktop moves up when mouse cursor is on bottom screen edge
https://bugs.kde.org/show_bug.cgi?id=450409 Kelvin changed: What|Removed |Added Summary|desktop moves up when mouse |desktop moves up when mouse |cursor is on panel taskbar |cursor is on bottom screen ||edge -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 450409] desktop moves up when mouse cursor is on bottom screen edge
https://bugs.kde.org/show_bug.cgi?id=450409 Kelvin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Kelvin --- Resolved after latest Opensuse tumbleweed update- plasma 5.24.1. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 428358] New: Kmail crashes when selecting one specific email
https://bugs.kde.org/show_bug.cgi?id=428358 Bug ID: 428358 Summary: Kmail crashes when selecting one specific email Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kelvineck...@web.de Target Milestone: --- Application: kontact (5.15.2 (20.08.2)) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.15-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Reading emails in Kmail. I can read emails in Kmail without problems. When I select one specific email from the message list the message window stays blank and after 1 second Kontact closes unexpectedly. I can reopen Kmail and repeat the above. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [New LWP 8588] [New LWP 8589] [New LWP 8596] [New LWP 8598] [New LWP 8603] [New LWP 8604] [New LWP 8605] [New LWP 8606] [New LWP 8607] [New LWP 8609] [New LWP 8627] [New LWP 8628] [New LWP 8629] [New LWP 8630] [New LWP 8642] [New LWP 8656] [New LWP 8671] [New LWP 8685] [New LWP 8692] [New LWP 8723] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f8499d9fe7f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f8489963600 (LWP 8587))] Thread 21 (Thread 0x7f841bfff640 (LWP 8723)): #0 0x7f849209b3a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8494cbc06a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x3bf6 in ?? () #3 0x3615bbb9 in ?? () #4 0x3bd5 in ?? () #5 0x3615bbb9 in ?? () #6 0x in ?? () Thread 20 (Thread 0x7f83f1a9f640 (LWP 8692)): #0 0x7f84915177fd in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8491519515 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f849151aa33 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7f849151b51b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f849151b70f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f849a3625cb in QEventDispatcherGlib::processEvents (this=0x7f83ec008760, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f849a309a1b in QEventLoop::exec (this=this@entry=0x7f83f1a9e480, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f849a12a7ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f849a12b911 in QThreadPrivate::start (arg=0x55d40fa472a0) at thread/qthread_unix.cpp:329 #9 0x7f8492094eb1 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8499daaccf in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f84098f8640 (LWP 8685)): #0 0x7f8499d9fe7f in poll () from /lib64/libc.so.6 #1 0x7f849151b5ee in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f849151b70f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f849a3625cb in QEventDispatcherGlib::processEvents (this=0x55d40fc3edc0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f849a309a1b in QEventLoop::exec (this=this@entry=0x7f84098f7480, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f849a12a7ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f849a12b911 in QThreadPrivate::start (arg=0x55d40fc3d430) at thread/qthread_unix.cpp:329 #7 0x7f8492094eb1 in start_thread () from /lib64/libpthread.so.0 #8 0x7f8499daaccf in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f8418da4640 (LWP 8671)): #0 0x7f849209b082 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8494cbbf6c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in ?? () Thread 17 (Thread 0x7f841a5bd640 (LWP 8656)): #0 0x7f8491568ea9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f849151b5d4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f849151b70f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f849a3625cb in QEventDispatcherGlib::processEvents (this=0x7f83fc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f849a309a1b in QEventLoop::exec (this=this@entry=0x7f841a5bc480, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f849a12a7ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f849a12b911 in QThreadPrivate::start (arg=0x55d40d1aff50) at thread/qthread_unix.cpp:329 #7
[kontact] [Bug 428358] Kmail crashes when selecting one specific email
https://bugs.kde.org/show_bug.cgi?id=428358 --- Comment #2 from Kelvin --- (In reply to Laurent Montel from comment #1) > Hi, > Is it possible to send me (in private) your specific email? > Regards yes, done to montel email. Interestingly the same email forwarded to myself also crashes Kmail. Kind regards Kelvin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400038] Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed
https://bugs.kde.org/show_bug.cgi?id=400038 --- Comment #4 from Kelvin Miller --- I apologize. I searched but could not find a duplicate that fit my bug's profile. I checked bug 399499, that was on boot to the desktop. My bug is/was about waking from sleep. My bug involves plasmashell icon distortion also. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep
https://bugs.kde.org/show_bug.cgi?id=395583 Kelvin Miller changed: What|Removed |Added CC||uavtech2...@gmail.com --- Comment #10 from Kelvin Miller --- See this also on a fresh install of Manjaro KDE on a Surface Pro 4. This doesn't happen at all on my other laptop with KDE Neon. Here is my system information: inxi -Fxzc0 System: Host: surface-p4 Kernel: 4.19.20-1-surface x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: KDE Plasma 5.14.5 Distro: Manjaro Linux Machine: Type: Laptop System: Microsoft product: Surface Pro 4 v: D:0B:08F:1C:03P:38 serial: Mobo: Microsoft model: Surface Pro 4 serial: UEFI: Microsoft v: 108.2318.769 date: 08/14/2018 Battery: ID-1: BAT1 charge: 34.1 Wh condition: 34.1/38.2 Wh (89%) model: SMP X910527 status: Full CPU: Topology: Dual Core model: Intel Core i5-6300U bits: 64 type: MT MCP arch: Skylake rev: 3 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19968 Speed: 500 MHz min/max: 400/3000 MHz Core speeds (MHz): 1: 500 2: 500 3: 500 4: 501 Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Microsoft driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: intel unloaded: modesetting resolution: 2736x1824~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) v: 4.5 Mesa 18.3.2 direct render: Yes Audio: Device-1: Intel Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging Unit driver: N/A bus ID: 00:05.0 Device-2: Intel driver: N/A bus ID: 00:14.3 Device-3: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Sound Server: ALSA v: k4.19.20-1-surface Network: Device-1: Marvell 88W8897 [AVASTAR] 802.11ac Wireless driver: mwifiex_pcie v: 1.0 port: 3000 bus ID: 02:00.0 IF: wlp2s0 state: up mac: Drives: Local Storage: total: 238.47 GiB used: 80.03 GiB (33.6%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZFLV256HCHP-000MV size: 238.47 GiB Partition: ID-1: / size: 76.90 GiB used: 23.01 GiB (29.9%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p6 Sensors: System Temperatures: cpu: 37.0 C mobo: 0.0 C Fan Speeds (RPM): N/A Info: Processes: 186 Uptime: 5h 26m Memory: 7.72 GiB used: 1.64 GiB (21.3%) Init: systemd Compilers: gcc: 8.2.1 Shell: bash v: 5.0.0 inxi: 3.0.30 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400038] New: Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed
https://bugs.kde.org/show_bug.cgi?id=400038 Bug ID: 400038 Summary: Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed Product: kwin Version: 5.14.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: uavtech2...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.1) Qt Version: 5.11.1 Frameworks Version: 5.51.0 Operating System: Linux 4.16.3-041603-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: Waking laptop up from resume. Plasma desktop icons also have corrupted text due to this bug. Only way to fix is to restart both Kwin and Plasma Desktop. I have Nvidia 396 proprietary drivers installed. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fab8201c840 (LWP 5705))] Thread 10 (Thread 0x7faaaee6d700 (LWP 9832)): #0 0x7fab7a9cf9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fab50001894) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fab50001840, cond=0x7fab50001868) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fab50001868, mutex=0x7fab50001840) at pthread_cond_wait.c:655 #3 0x7fab7ed6b91b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x7fab50001840) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x5648b6077400, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fab79b7bbe8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fab79b7c01a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fab7ed6aaab in QThreadPrivate::start (arg=0x5648b6077380) at thread/qthread_unix.cpp:367 #8 0x7fab7a9c96db in start_thread (arg=0x7faaaee6d700) at pthread_create.c:463 #9 0x7fab8199088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7faaaf9ff700 (LWP 9831)): #0 0x7fab7a9cf9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5648b604e7c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5648b604e770, cond=0x5648b604e798) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5648b604e798, mutex=0x5648b604e770) at pthread_cond_wait.c:655 #3 0x7fab7ed6b91b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5648b604e770) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x5648b6085540, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fab79b7bbe8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fab79b7c01a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fab7ed6aaab in QThreadPrivate::start (arg=0x5648b60854c0) at thread/qthread_unix.cpp:367 #8 0x7fab7a9c96db in start_thread (arg=0x7faaaf9ff700) at pthread_create.c:463 #9 0x7fab8199088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7faab4c4a700 (LWP 9830)): #0 0x7fab81983cf6 in __GI_ppoll (fds=fds@entry=0x7faabd28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fab7ef8c7a1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7faabd28) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7faabd28, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7fab7ef8deae in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fab7ef34dea in QEventLoop::exec (this=this@entry=0x7faab4c49d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7fab7ed5fb8a in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7fab794558b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fab7ed6aaab in QThreadPrivate::start (arg=0x5648b5f9f460) at thread/qthread_unix.cpp:367 #9 0x7fab7a9c96db in start_thread (arg=0x7faab4c4a700) at pthread_create.c:463 #10 0x7fab8199088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fab56387700 (LWP 9829)): #0 0x7fab7ef8f132 in QTimerInfoList::repairTimersIfNeeded (this=0x7fab44000be0) at kernel/qtimerinfo_unix.cpp:161 #1 0x7fab7ef8f1c3 in QTimerInfoList::timerWait (this=this@entry=0x7fab44000be0, tm=...) at kernel/qtimerinfo_unix.cpp:389 #2 0x7fab7ef8e1b4 in QEventDispatcherUNIX::
[plasmashell] [Bug 500201] I would like to import google calendar
https://bugs.kde.org/show_bug.cgi?id=500201 --- Comment #2 from Kelvin Long MCPO USN Ret. --- There is no "Calendar Events" radio button when I go to configure digital clock. Please advise next. THX On 2/16/25 18:03, cwo wrote: > https://bugs.kde.org/show_bug.cgi?id=500201 > > cwo changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > CC||cwo@posteo.net > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from cwo --- > Thank you for the bug report! > > Digital Clock uses the KDE PIM service Akonadi as the calendar source. > > Please try the following: > > 1) Make sure that "Calendar Events" is enabled in the Digital Clock settings > 2) Use an Akonadi-enabled calendar application to link to the correct calendar > source, such as Google Calendar in your case. (You can use e.g. Kontact or > Merkuro) > 3) The calendar should now show up in the "Calendar Events" section of the > Digital Clock settings. > > Please let me know if the above steps did not work. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500201] New: I would like to import google calendar
https://bugs.kde.org/show_bug.cgi?id=500201 Bug ID: 500201 Summary: I would like to import google calendar Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Digital Clock widget Assignee: plasma-b...@kde.org Reporter: crowbar...@gmail.com Target Milestone: 1.0 I would like to import google calendar If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
