[kwin] [Bug 394772] Some GTK apps temporarily lose scroll focus while desktop notification are shown
https://bugs.kde.org/show_bug.cgi?id=394772 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348270] Cannot scroll properly in GTK3 apps after focus switching
https://bugs.kde.org/show_bug.cgi?id=348270 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 423497] Feature Req: Ability to close/exit on android and desktop.
https://bugs.kde.org/show_bug.cgi?id=423497 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 423497] New: Feature Req: Ability to close/exit on android and desktop.
https://bugs.kde.org/show_bug.cgi?id=423497 Bug ID: 423497 Summary: Feature Req: Ability to close/exit on android and desktop. Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: k...@codywohlers.ca Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. boot device (android or desktop) 2. attempt to exit/close/stop kdeconnect OBSERVED RESULT There is no way to exit the app from the app. You have to kill it with system tools. EXPECTED RESULT You should be able to close/exit from the app interface. Reasons: When not using persistent features you can save phone battery life, reduce needless network traffic, reduce `.xsession-errors` spam on desktop, or whatever other reason you would like to close it. I would prefer to run it only when needed. I see the need for it to be persistent for some of the features, and also convenience, but you should be able to close/exit if you want to. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 Android Version: 7.0 kdeconnect version (desktop): 1.3.3 kdeconnect version (android): 1.14.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 272361] Unavailable mounts that are Places entries make clients displaying a Places panel (e.g. Dolphin, Gwenview, file open or save dialogs) hang or become extremely slow
https://bugs.kde.org/show_bug.cgi?id=272361 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 344967] 99 minute maximum for lock screen
https://bugs.kde.org/show_bug.cgi?id=344967 codywohlers changed: What|Removed |Added Version|5.2.1 |5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 344967] 99 minute maximum for lock screen
https://bugs.kde.org/show_bug.cgi?id=344967 codywohlers changed: What|Removed |Added Resolution|INTENTIONAL |UNMAINTAINED --- Comment #24 from codywohlers --- WORKAROUND: You can edit `$HOME/.config/kscreenlockerrc` and set Timeout=285120 ** * WARNING ** ** DO NOT EVER OPEN THE LOCK SCREEN DIALOG OR IT WILL OVERWRITE YOUR SETTINGS AND YOU'LL HAVE TO REMEMBER RE-EDIT THE FILE -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 344967] 99 minute maximum for lock screen
https://bugs.kde.org/show_bug.cgi?id=344967 --- Comment #23 from codywohlers --- (In reply to Martin Flöser from comment #22) > Please use inhibition from the script. How do I do that? Where is that setting? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 344967] 99 minute maximum for lock screen
https://bugs.kde.org/show_bug.cgi?id=344967 codywohlers changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INTENTIONAL |--- Ever confirmed|0 |1 --- Comment #20 from codywohlers --- reopening as I have supplies a use case, as requested by the developer -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 344967] 99 minute maximum for lock screen
https://bugs.kde.org/show_bug.cgi?id=344967 --- Comment #21 from codywohlers --- (In reply to codywohlers from comment #20) > reopening as I have supplies a use case, as requested by the developer I have long terminal processes that run that sometimes take more than 99 minutes. I work on another machine and occasionally glance back over. I have to disable the lock (or edit .config/kscreenlockerrc manually) or remember to move the mouse every 99 minutes. (Then I have to remember to manually lock my station when I leave, or decide if I'm leaving for a long time each time I leave) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403362] Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips
https://bugs.kde.org/show_bug.cgi?id=403362 codywohlers changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |UPSTREAM --- Comment #5 from codywohlers --- Closing as upstream issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403362] Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips
https://bugs.kde.org/show_bug.cgi?id=403362 --- Comment #4 from codywohlers --- from Xorg.0.log: [ 8419.445] (WW) NVIDIA: The Composite and Xinerama extensions are both enabled, which [ 8419.445] (WW) NVIDIA: is an unsupported configuration. The driver will continue [ 8419.445] (WW) NVIDIA: to load, but may behave strangely. Closing as upstream issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403362] Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips
https://bugs.kde.org/show_bug.cgi?id=403362 --- Comment #3 from codywohlers --- WORKAROUND: If I change the Compositor setting "Rendering backend" to something not OpenGL (like XRender) then my other 3 monitors instantly work again. OpenGL 2.0 and 3.1 settings do not work. https://devtalk.nvidia.com/default/topic/1026340/linux/black-or-incorrect-textures-in-kde/ Similar bugs have indicated this is probably an Nvidia driver issue and I should submit the bug to them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400680] plasma shell randomly crashes while using openGL apps
https://bugs.kde.org/show_bug.cgi?id=400680 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400718] Clicking on a tray icon to minimize an app sometimes crashes the shell
https://bugs.kde.org/show_bug.cgi?id=400718 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401257] Random plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=401257 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403362] Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips
https://bugs.kde.org/show_bug.cgi?id=403362 --- Comment #1 from codywohlers --- Created attachment 117540 --> https://bugs.kde.org/attachment.cgi?id=117540&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403362] Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips
https://bugs.kde.org/show_bug.cgi?id=403362 --- Comment #2 from codywohlers --- Created attachment 117541 --> https://bugs.kde.org/attachment.cgi?id=117541&action=edit xorg.conf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403362] Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips
https://bugs.kde.org/show_bug.cgi?id=403362 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403362] New: Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips
https://bugs.kde.org/show_bug.cgi?id=403362 Bug ID: 403362 Summary: Xinerama with Nvidia not showing other monitor contents, only cursors and tooltips Product: plasmashell Version: 5.12.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@codywohlers.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.7) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: 4 monitor setup with GTX-560 and GTX-550Ti using 2 Twinview X Screens with Xinerama to make it one big desktop. Login screen shows correctly on all 4 monitors. After logging in only the primary monitor displays a dektop and 3 of the 4 monitors are black but will display a cursor. Windows can be moved on to those monitors but will not be displayed. I have window move/resizing tooltips on and when you move a window on those monitors it leaves trails of the tooltips. https://i.imgur.com/bmnkO67.png Notes: The exact same Nvidia driver and and xorg.conf worked in KDE4 (Mint 17.3) yesterday. If I maximize a window it stretches across all monitors and it should not with Twinview enabled. If I disable Twinview then 2 of the 4 monitors (X Screen 1) will be black but show the cursor and leave trails of tooltips. Twinview without Xinerama and just 2 monitors in total (one X Screen) works fine. The 4 monitor setup works as expected with the Nouveau driver. During the Nvidia driver install, the installer found "An incomplete installation of libglvnd" and installed it's own "full copy". xorg.conf - https://www.dropbox.com/s/q4vt3nrapmm2s0a/xorg.conf2019-01-18?dl=0 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f014bb00c80 (LWP 5393))] Thread 10 (Thread 0x7f0069ffb700 (LWP 5562)): [KCrash Handler] #6 0x7f009ae10ba8 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.87 #7 0x7f009b0e1d0a in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.87 #8 0x7f009afa970a in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.87 #9 0x7f009afbfe14 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.87 #10 0x7f009afb8bc5 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.87 #11 0x7f009b0c6a16 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.87 #12 0x7f0149527f0f in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f014952900d in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f014952e85e in QSGBatchRenderer::Renderer::render() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f014951f2a0 in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f014951f75b in QSGRenderer::renderScene(unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f0149559af0 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f01495b7b68 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f0149562bbc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f0149567ac8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7f01457e116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f01449626db in start_thread (arg=0x7f0069ffb700) at pthread_create.c:463 #23 0x7f01450dc88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f0074bfd700 (LWP 5561)): #0 0x7f01449689f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564760947ee0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x564760947e90, cond=0x564760947eb8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x564760947eb8, mutex=0x564760947e90) at pthread_cond_wait.c:655 #3 0x7f01457e259b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f01495676a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f0149567b0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f01457e116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f01449626db in start_thread (arg=0x7f00
[ksmserver] [Bug 344967] 99 minute maximum for lock screen
https://bugs.kde.org/show_bug.cgi?id=344967 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca --- Comment #16 from codywohlers --- (In reply to Thomas Pfeiffer from comment #14) > (In reply to John Andrew McInnes from comment #11) > > KDE used to be the opposite philosophy. > > If you can make a case where a lock time of more then 99 minutes is needed > ... then we'll happily change that value. I have long terminal processes that run that sometimes take more than 99 minutes. I work on another machine and occasionally glance back over. I have to disable the lock (or edit .config/kscreenlockerrc manually) or remember to move the mouse every 99 minutes. (Then I have to remember to manually lock my station when I leave, or decide if I'm leaving for a long time each time I leave) The main complaint non-linux users have about linux is the command line. And I always say "try KDE, you can do everything from the GUI". But if the new philosophy is "Simple by default. Powerful when needed." this should continue to apply to the GUI configuration. That what makes KDE different - you can configure anything the way you want with the built-in GUI. Not being able to set that number to *anything* is poor design. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 codywohlers changed: What|Removed |Added CC||k...@codywohlers.ca -- You are receiving this mail because: You are watching all bug changes.
