[kwin] [Bug 415798] [Wayland] task switcher is black after changing
https://bugs.kde.org/show_bug.cgi?id=415798 Götz changed: What|Removed |Added CC||goetzchr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421020] New: "Replay" and "Mark as read" buttons are sometimes swapped
https://bugs.kde.org/show_bug.cgi?id=421020 Bug ID: 421020 Summary: "Replay" and "Mark as read" buttons are sometimes swapped Product: kdeconnect Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: goetzchr...@gmail.com Target Milestone: --- SUMMARY When receiving a SMS, a Plasma notification shows with the message with the "Replay" and "Mark as read" buttons. On some occasions, which look to me to be random, these buttons swap their functionality, that is, clicking on "Mark as read" shows the replay text filed, and clicking on "Replay" marks it as read. STEPS TO REPRODUCE 1. receive a SMS 2. click any of the buttons OBSERVED RESULT Randomly both button have their labels or functionality swapped. EXPECTED RESULT Consistent and appropriate behavior. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I have observed this behavior since possibly half a year. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418307] Additional keyboard shortcuts for Klipper navigation (Vim-like)
https://bugs.kde.org/show_bug.cgi?id=418307 Götz changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418307] Additional keyboard shortcuts for Klipper navigation (Vim-like)
https://bugs.kde.org/show_bug.cgi?id=418307 --- Comment #2 from Götz --- Thanks @David. I did set the Standard Shortcuts for "Next Item in List" —which has primary shortcut set as "Down"— on the Alternative option to Ctrl+j, but unfortunately this behaves as having no effect. The same with "Previews Item in List". This does not only happen on Klipper but is also reproducible on other programs like Gweenview, Up/Down keys work, but not Ctrl-j/k. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 116482] metakit: akregator crashes at startup
https://bugs.kde.org/show_bug.cgi?id=116482 Götz changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #283 from Götz --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418307] New: Additional keyboard shortcuts for Klipper navigation (Vim-like)
https://bugs.kde.org/show_bug.cgi?id=418307 Bug ID: 418307 Summary: Additional keyboard shortcuts for Klipper navigation (Vim-like) Product: klipper Version: 5.18.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: goetzchr...@gmail.com Target Milestone: --- SUMMARY The Klipper window can be navigated using the Up and Down keyboard arrows, but lacks other popular options, like Vim-like shortcuts (Ctrl-j and Ctrl-k, also modal modes) or Emacs-style shortcuts (Ctrl-p and Ctrl-n). STEPS TO REPRODUCE 1. Open the Klipper Plasma tray icon or the "Open Klipper at Mouse Position" window. 2. Try to navigate using the keyboard with anything other than the arrows. 3. Press Ctrl-p, Ctrl-n, Ctrl-j, or Ctrl-k. OBSERVED RESULT Nothing. EXPECTED RESULT Previews/next clipboard item should be selected. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415971] Falkon crashed
https://bugs.kde.org/show_bug.cgi?id=415971 --- Comment #5 from Götz Wilhelm Renger --- (In reply to Graham Perrin from comment #3) > Created attachment 125246 [details] > application style (example) > > (In reply to Götz Wilhelm Renger from comment #2) > > > … How can I show you my 'system settings for application style and for > > window decorations'? … > > Example attached (screenshot) Thank you very much. The Answer of your question is: My kde application style is 'Breeze'. My kde window style is also 'Breeze'. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415971] Falkon crashed
https://bugs.kde.org/show_bug.cgi?id=415971
--- Comment #2 from Götz Wilhelm Renger ---
(In reply to Graham Perrin from comment #1)
> Please, is this bug still reproducible?
>
> If so: what are your system settings for application style and for window
> decorations?
Hi Graham.
Here is Götz Wilhelm Renger from Berlin.
How can I show you my 'system settings for application style and for window
decorations'?
I've changed my /etc/portage/make.conf to
COMMON_FLAGS="-march=core2 -Og -ggdb"
With this, is it possible to produce a better failure log. If so, what I've to
do to deliver a better failure log then the following:
- - - - - - - snip - - - - - - -
goetz@sky2:~$ falkon
WebEngineContext used before QtWebEngine::initialize() or OpenGL context
creation failed.
QGLXContext: Failed to create dummy context
Use of deprecated not thread-safe setter, use setUrlRequestInterceptor instead.
Cannot initialize model with data QJsonObject() . missing: QJsonValue(string,
"urls")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/ftp.so" supports protocols
("ftp")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/help.so" supports protocols
("help")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/remote.so" supports protocols
("remote")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/kdeconnect.so" supports protocols
("kdeconnect")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/ghelp.so" supports protocols
("ghelp")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/file.so" supports protocols
("file")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/trash.so" supports protocols
("trash")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/audiocd.so" supports protocols
("audiocd")
kf5.kio.core: "/usr/lib64/qt5/plugins/kf5/kio/http.so" supports protocols
("http", "https", "webdav", "webdavs")
Please register the custom scheme 'desktop' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'sftp' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'ar' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'trash' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'man' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'gzip' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'pnm' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'recentdocuments' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'fish' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'webdav' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'mmst' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'mmsu' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'network' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'baloosearch' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'ghelp' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'zip' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'camera' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'bluetooth' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'videodvd' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'webdavs' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'thumbnail' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'rtspt' via
QWebEngineUrlScheme::registerScheme() before installing the custom scheme
handler.
Please register the custom scheme 'rtspu' via
QWebEngineUrlScheme::registerScheme() before installing th
[Falkon] [Bug 415971] New: Falkon crashed
https://bugs.kde.org/show_bug.cgi?id=415971 Bug ID: 415971 Summary: Falkon crashed Product: Falkon Version: 3.1.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: now...@gmail.com Reporter: ren...@freenet.de Target Milestone: --- Application: falkon (3.1.0) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.19.86-gentoo-alpha x86_64 Distribution: Gentoo/Linux -- Information about the crash: USE="debug" emerge -vt --ask '=www-client/falkon-3.1.0-r1' The crash can be reproduced every time. -- Backtrace: Application: Falkon (falkon), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1900e05a00 (LWP 12190))] Thread 20 (Thread 0x7f18cd0c9700 (LWP 12226)): #0 0x7f19071331dc in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f190ab632e6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f190ab63d23 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f190ab63ea1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f190ab79622 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f190ab79b0f in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f190ab7a234 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f190ab65d1a in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f190712c3a7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f19106b571f in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f18cd8ca700 (LWP 12214)): #0 0x7f1907132e77 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f190ab631ec in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f190ab63d30 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f190ab63e5f in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f190ab79638 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f190ab79d78 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f190ab7a2b4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f190ab65d1a in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f190712c3a7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f19106b571f in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f18ce7fc700 (LWP 12213)): #0 0x7f19106a9a53 in poll () at /lib64/libc.so.6 #1 0x7f19068d871e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f19068d883f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1910c9f223 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f1910c4a73b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f1910ab0e21 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f1910ab1eb2 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f190712c3a7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f19106b571f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f18ceffd700 (LWP 12212)): #0 0x7f19106a9a53 in poll () at /lib64/libc.so.6 #1 0x7f18febf13e2 in () at /usr/lib64/libpulse.so.0 #2 0x7f18febe2e39 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f18febe34bf in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f18febe3570 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f18febf1329 in () at /usr/lib64/libpulse.so.0 #6 0x7f18feafcfd8 in () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f190712c3a7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f19106b571f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f18cf7fe700 (LWP 12211)): #0 0x7f19071331dc in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f190ab632e6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f190ab63d23 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f190ab63ea1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f190ab79622 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f190ab79b0f in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f190ab7a234 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f190ab65d1a in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f190712c3a7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f19106b571f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f18c700 (LWP 12210)): #0 0x7f1907132e77 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f190ab631ec in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f190ab63d30 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f190ab63e5f in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f190aae514e in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f190ab02967 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6
[plasmashell] [Bug 369128] When hidding a system tray element using a kbd shortcut, the close animation behaivs wrong
https://bugs.kde.org/show_bug.cgi?id=369128 Götz changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Götz --- Indeed the behavior changed. Closing this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412036] New: Plasma crash when opening wigdet
https://bugs.kde.org/show_bug.cgi?id=412036 Bug ID: 412036 Summary: Plasma crash when opening wigdet Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: goetzchr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.2.14-arch2-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Tryed to open the widget "Audio Volume (Win 7 Mixer)" from with in the Plasma panel. - Custom settings of the application: Using Wayland session. Custom widget installed from "Get hot new stuff", called "Audio Volume (Win 7 Mixer)". It works on X11 session. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2507e7c880 (LWP 1847466))] Thread 10 (Thread 0x7f24dd1b7700 (LWP 1853054)): #0 0x7f250c609667 in poll () at /usr/lib/libc.so.6 #1 0x7f250ae32130 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f250ae32201 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f250cbaba1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f250cb524ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f250c984385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f250e6e46eb in () at /usr/lib/libQt5Quick.so.5 #7 0x7f250c9855b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f250be5757f in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f250c6140e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f24fdf75700 (LWP 1850001)): [KCrash Handler] #6 0x7f250c456e94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #7 0x7f2507a914d0 in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #8 0x7f2504d38b31 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7f250cf2ea72 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f250e76c0ee in () at /usr/lib/libQt5Quick.so.5 #11 0x7f250e76ffc8 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f250c9855b0 in () at /usr/lib/libQt5Core.so.5 #13 0x7f250be5757f in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f250c6140e3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f24bfbcd700 (LWP 1847629)): #0 0x7f250be5d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f250c98b660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f250c98b752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f250e76fdad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f250e77005e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f250c9855b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f250be5757f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f250c6140e3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f24ddb30700 (LWP 1847618)): #0 0x7f250be5d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f250c98b660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f250c98b752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f250e76fdad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f250e77005e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f250c9855b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f250be5757f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f250c6140e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f24e058b700 (LWP 1847570)): #0 0x7f250c6152fc in recv () at /usr/lib/libc.so.6 #1 0x7f250c09ebf0 in () at /usr/lib/libQt5Network.so.5 #2 0x7f250c08ee34 in () at /usr/lib/libQt5Network.so.5 #3 0x7f250c08f673 in QNetworkInterface::allInterfaces() () at /usr/lib/libQt5Network.so.5 #4 0x7f24dfd454ff in () at /usr/lib/qt/plugins/bearer/libqgenericbearer.so #5 0x7f250cb61efd in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () at /usr/lib/libQt5Core.so.5 #6 0x7f250cb63b44 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
[plasma-pa] [Bug 410905] Update description for 'Provide visual feedback: When volume changes'
https://bugs.kde.org/show_bug.cgi?id=410905 --- Comment #2 from Götz --- Awesome, thanks Nate! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410905] New: Update description for 'Provide visual feedback: When volume changes'
https://bugs.kde.org/show_bug.cgi?id=410905 Bug ID: 410905 Summary: Update description for 'Provide visual feedback: When volume changes' Product: plasma-pa Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: now...@gmail.com Reporter: goetzchr...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 122119 --> https://bugs.kde.org/attachment.cgi?id=122119=edit "Audio Volume Settings" section SUMMARY Un/marking this checkbox switches the "audio feedback" when changing volume, not a "visual feedback". The description should be updated to reflect the actual behavior. STEPS TO REPRODUCE 0. Change volume (hear the audio feedback) 1. Open the "Audio Volume Settings" window 2. Unmark "When volume changes" 3. Change volume (no audio feedback) Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Not sure what happens when plugging a sound card, no sound feedback, seem that the check box doesn't change anything un/marked. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 407101] Make the menubar searchable
https://bugs.kde.org/show_bug.cgi?id=407101 Götz changed: What|Removed |Added CC||goetzchr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 198175] Konsole should set blur region for the new kwin effect
https://bugs.kde.org/show_bug.cgi?id=198175 --- Comment #90 from Götz <goetzchr...@gmail.com> --- On Feb 4, 2018 4:11 PM, "Alex Nemeth" <bugzilla_nore...@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=198175 How would a GNOME user even see the description in the KDE system settings? And why would someone use Konsole under GNOME, when GNOME has a nice terminal too? Why? So many reasons, for example I use Konsole under GNOME, and I don't have KDE's System Settings because it fits my needs. The most appropriate place for placing the notice is where you flip the switch, in this case, on Konsole settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction
https://bugs.kde.org/show_bug.cgi?id=381630 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC|goetzchr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386305] New: Plasma crash when interacting with system tray icons
https://bugs.kde.org/show_bug.cgi?id=386305 Bug ID: 386305 Summary: Plasma crash when interacting with system tray icons Product: plasmashell Version: 5.11.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: goetzchr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.2) Qt Version: 5.9.2 Frameworks Version: 5.39.0 Operating System: Linux 4.13.9-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Was clicking around on plasma5-applets-redshift-control. Haven't experienced such crash using Xorg. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f882411b800 (LWP 2399))] Thread 44 (Thread 0x7f86b7e7f700 (LWP 9789)): #0 0x7f881cf7138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f881ddb345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f8821b4e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7f8821b4ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f881ddb1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7f881cf6b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f881d6be24f in clone () at /usr/lib/libc.so.6 Thread 43 (Thread 0x7f86b8680700 (LWP 9788)): #0 0x7f881cf7138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f87fcad3dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f87fcad3cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f881cf6b08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f881d6be24f in clone () at /usr/lib/libc.so.6 Thread 42 (Thread 0x7f86b9ecd700 (LWP 9786)): #0 0x7f8817fd4664 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f8817facde8 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8817facfae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f881dff0cf4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f881df9448b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f881ddad27e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8820f20bc9 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f881ddb1fcb in () at /usr/lib/libQt5Core.so.5 #8 0x7f881cf6b08a in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f881d6be24f in clone () at /usr/lib/libc.so.6 Thread 41 (Thread 0x7f86cb7fe700 (LWP 9416)): #0 0x7f881d6af868 in read () at /usr/lib/libc.so.6 #1 0x7f88118f37c2 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-11.1.so #2 0x7f88121987af in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7f8812199241 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f8812199301 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f88121a76ae in () at /usr/lib/libpulse.so.0 #6 0x7f881192381c in () at /usr/lib/pulseaudio/libpulsecommon-11.1.so #7 0x7f881cf6b08a in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f881d6be24f in clone () at /usr/lib/libc.so.6 Thread 40 (Thread 0x7f86d0ffa700 (LWP 8523)): #0 0x7f881cf7138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f881ddb345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f8821b4e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7f8821b4ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f881ddb1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7f881cf6b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f881d6be24f in clone () at /usr/lib/libc.so.6 Thread 39 (Thread 0x7f86d27fc700 (LWP 8522)): #0 0x7f881cf7138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f87fcad3dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f87fcad3cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f881cf6b08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f881d6be24f in clone () at /usr/lib/libc.so.6 Thread 38 (Thread 0x7f86d1ffb700 (LWP 8521)): #0 0x7f881d6af868 in read () at /usr/lib/libc.so.6 #1 0x7f8817fd4521 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8817fab90b in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f8817face76 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f8817facfae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f881dff0cf4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f881df9448b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7
[systemsettings] [Bug 386303] New: SystemSettigns crash when closing
https://bugs.kde.org/show_bug.cgi?id=386303 Bug ID: 386303 Summary: SystemSettigns crash when closing Product: systemsettings Version: 5.11.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: goetzchr...@gmail.com Target Milestone: --- Application: systemsettings5 (5.11.2) Qt Version: 5.9.2 Frameworks Version: 5.39.0 Operating System: Linux 4.13.9-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: After changing some settings and navigation thru systemsettings, I closed it (no save promt) using the Kwin close button. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8a6e3ca800 (LWP 3849))] Thread 10 (Thread 0x7f8a1b4ed700 (LWP 3863)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f8a337fe700 (LWP 3857)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f8a33fff700 (LWP 3856)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f8a48a28700 (LWP 3855)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f8a49229700 (LWP 3854)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f8a49a2a700 (LWP 3853)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8a4a430700 (LWP 3852)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f8a4b46f700 (LWP 3851)): #0 0x7f8a65dd038d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8a50525dac in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f8a50525cb8 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f8a65dca08a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8a6a01e24f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8a58ed9700 (LWP 3850)): #0 0x7ffdacf5b969 in () #1 0x7ffdacf5bc20 in clock_gettime () #2 0x7f8a6a02baf6 in clock_gettime () at /usr/lib/libc.so.6 #3 0x7f8a6a9505e2 in () at /usr/lib/libQt5Core.so.5 #4 0x7f8a6a94ed7a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #5 0x7f8a6a94f356 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #6 0x7f8a6a950a3f in () at /usr/lib/libQt5Core.so.5 #7 0x7f8a63bfd771 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #8 0x7f8a63bfddf6 in () at
[konsole] [Bug 355421] Konsole crashed on login
https://bugs.kde.org/show_bug.cgi?id=355421 --- Comment #15 from Götz <goetzchr...@gmail.com> --- I haven't seen this issue since a few months. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355540] Tooltips color wrong in gtk applications
https://bugs.kde.org/show_bug.cgi?id=355540 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC|goetzchr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)
https://bugs.kde.org/show_bug.cgi?id=371494 --- Comment #7 from Götz <goetzchr...@gmail.com> --- This is the discussion: https://github.com/jonls/redshift/issues/55 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)
https://bugs.kde.org/show_bug.cgi?id=371494 --- Comment #5 from Götz <goetzchr...@gmail.com> --- In case someone is interested, sway supports this with a modified version of redshift. https://github.com/SirCmpwn/sway/pull/1019 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371494] New: Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)
https://bugs.kde.org/show_bug.cgi?id=371494 Bug ID: 371494 Summary: Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux) Product: kwin Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: colorcorrection Assignee: cas...@candrei.ro Reporter: goetzchr...@gmail.com CC: kwin-bugs-n...@kde.org Adapting the computer's display color (adapting to the time of day or ambient light, using a sensor) improves sleep (avoiding disrupting the circadian rhythm) and helps the eyes hurt less if working in front of the screen at night or in low light condition, warm at night and colder (like sunlight) during the day. The American Medical Association's Council on Science and Public Health, made this recommendation: "Recognizes that exposure to excessive light at night, including extended use of various electronic media, can disrupt sleep or exacerbate sleep disorders, especially in children and adolescents. This effect can be minimized by using dim red lighting in the nighttime bedroom environment." More here: https://justgetflux.com/research.html http://www.pnas.org/content/early/2014/12/18/1418490112.full.pdf+html Reproducible: Always Steps to Reproduce: 1. Blue light temperature at night 2. Eyes hurt 3. Relies you need warmer light -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366605] Tap-to-click missing on Wayland
https://bugs.kde.org/show_bug.cgi?id=366605 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com --- Comment #9 from Götz <goetzchr...@gmail.com> --- I did a "org.freedesktop.DBus.Properties.GetAll" on my input device to search for a Natural Scrolling configuration option, and it seems to be missing. Is this to be handled in a different but report or all input related here as well? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session
https://bugs.kde.org/show_bug.cgi?id=363109 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 369493] Strange string when changing process priority: ") za dani proces"
https://bugs.kde.org/show_bug.cgi?id=369493 --- Comment #1 from Götz <goetzchr...@gmail.com> --- Created attachment 101333 --> https://bugs.kde.org/attachment.cgi?id=101333=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 369493] New: Strange string when changing process priority: ") za dani proces"
https://bugs.kde.org/show_bug.cgi?id=369493 Bug ID: 369493 Summary: Strange string when changing process priority: ") za dani proces" Product: ksysguard Version: 5.7.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: goetzchr...@gmail.com When raising some process priority, the user is prompt for the password, in that polkit dialog, there is a odd string: ") za dani proces" Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369390] In file preview, pressing enter closes preview
https://bugs.kde.org/show_bug.cgi?id=369390 --- Comment #1 from Götz <goetzchr...@gmail.com> --- Bug 369401 might be related to this issue. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369401] New: In file preview, default focus should be inside the text field
https://bugs.kde.org/show_bug.cgi?id=369401 Bug ID: 369401 Summary: In file preview, default focus should be inside the text field Product: ark Version: 16.08.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: goetzchr...@gmail.com CC: rak...@freebsd.org, rthoms...@gmail.com The preview can be closed with Esc or Alt+F4. Right now, one has to change focus with tab or pointer, to be able to search in the text. Having focus by default inside the text field would improve this situation. And closing the preview still can be done at once with different methods. Reproducible: Always Steps to Reproduce: 1. Open archive with Ark 2. Open file for preview Actual Results: Focus is on the Close button. Expected Results: Focus to be inside the text view -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369390] New: In file preview, pressing enter closes preview
https://bugs.kde.org/show_bug.cgi?id=369390 Bug ID: 369390 Summary: In file preview, pressing enter closes preview Product: ark Version: 16.08.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: goetzchr...@gmail.com CC: rak...@freebsd.org, rthoms...@gmail.com After opening a compressed archive with Ark, there is the possibility to preview a file, and you can search a string with Ctrl+F. Upon pressing key Enter, the preview is closed, which is very much unexpected. Enter should search the next string, the same say as Kate does. Reproducible: Always Steps to Reproduce: 1. Open archive in ark 2. Open some file for preview. 3. Search a string with Ctrl+F 4. Press enter Actual Results: The preview is closed. Expected Results: Show the next text result. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369128] New: When hidding a system tray element using a kbd shortcut, the close animation behaivs wrong
https://bugs.kde.org/show_bug.cgi?id=369128 Bug ID: 369128 Summary: When hidding a system tray element using a kbd shortcut, the close animation behaivs wrong Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: goetzchr...@gmail.com Instead of animation the closing of the system tray element, it animates as opening and then closing. Reproducible: Always Steps to Reproduce: 1. Assign a keyboard shortcut for some entry, e.g. the Battery and Brightness (in system tray widget's settings) 2. Press the shortcut to open the widget, or do it manually. 3. Press the shortcut to close the widget (don't do it manually). Actual Results: Two animations when closing the widget. Expected Results: Only one close animation. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 238309] folder in recycle bin makes dolphin fill up /tmp dir
https://bugs.kde.org/show_bug.cgi?id=238309 --- Comment #7 from Götz <goetzchr...@gmail.com> --- The same with Dolphin 16.08 and KIO 5.25. When /tmp fill up, many problems arise. I understand this doesn't occur always, and is not easy to debug, and considering the consequences of a full /tmp, could you give this bug more priority? There seems to be more affected users and not tracked duplicates, some of them: Hard spamming in /tmp when browsing the trash directory. https://bugs.kde.org/show_bug.cgi?id=272249 Dolphins temporary files aren't deleted https://bugs.kde.org/show_bug.cgi?id=208625 dolphin from git master pollutes /tmp/ with dolphin.* files https://bugs.kde.org/show_bug.cgi?id=352975 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 Götz <goetzchr...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #46 from Götz <goetzchr...@gmail.com> --- It seems to be a kernel driver bug or such, as linux 4.6 has resolved this. Testing with linux 4.4 brings the issue back. I'll mark this as resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365995] Shorter date formats for vertical taskbar users.
https://bugs.kde.org/show_bug.cgi?id=365995 --- Comment #5 from Götz <goetzchr...@gmail.com> --- *** Bug 366409 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366409] Add more configuration options to show or hide additional date/time information
https://bugs.kde.org/show_bug.cgi?id=366409 Götz <goetzchr...@gmail.com> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Götz <goetzchr...@gmail.com> --- *** This bug has been marked as a duplicate of bug 365995 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365995] Shorter date formats for vertical taskbar users.
https://bugs.kde.org/show_bug.cgi?id=365995
Götz <goetzchr...@gmail.com> changed:
What|Removed |Added
CC||goetzchr...@gmail.com
--- Comment #4 from Götz <goetzchr...@gmail.com> ---
This is not only useful for vertical taskbar users, more options for the date
format would be very handy for horizontal panels, for example, show the date
without the current year, as it is not useful, who doesn't know the current
year.
Or a general option to allow a string specifying the format.[1]
Currently in my setup:
ISO: 2016-08-10
Short: 10/08/2016
Allowing the user to specify the date using those strings, which QML allows,
one could have:
Monday
Wed
Sep 4
15 Jan
7 October
Wednesday 10 August
10-8
10 Aug
Right know, Plasma 5.7.3, one has to manually edit DigitalClock.qml and in
function setupLabels(), inside if (main.showDate) For example:
---
/usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml
2016-08-10 18:44:57.835617323 -0500
+++
/usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml
2016-08-09 00:56:49.205248552 -0500
@@ -534,7 +534,8 @@
if (main.showDate) {
if (main.tooSmall) {
-dateLabelLeft.text = Qt.formatDate(main.currentTime,
main.dateFormat);
+dateLabelLeft.text = Qt.formatDate(main.currentTime, " d
");
} else {
dateLabel.text = Qt.formatDate(main.currentTime,
main.dateFormat);
}
Instead of main.dateFormat, use string format.[1]
[1] http://doc.qt.io/qt-5/qml-qtqml-date.html#details
--
You are receiving this mail because:
You are watching all bug changes.
[kio] [Bug 238309] folder in recycle bin makes dolphin fill up /tmp dir
https://bugs.kde.org/show_bug.cgi?id=238309 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com --- Comment #6 from Götz <goetzchr...@gmail.com> --- Same behavior seen here with latest stable version: Dolphin 16.04.3 Frameworks 5.24.0 Qt 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362836] "Short date" option in clock is not short
https://bugs.kde.org/show_bug.cgi?id=362836 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com --- Comment #1 from Götz <goetzchr...@gmail.com> --- I can confirm this. In my setup: ISO: 2016-08-04 Short: 04/08/2016 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366409] New: Add more configuration options to show or hide additional date/time information
https://bugs.kde.org/show_bug.cgi?id=366409 Bug ID: 366409 Summary: Add more configuration options to show or hide additional date/time information Product: plasmashell Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: goetzchr...@gmail.com More options for the date format, for example, show the date without the current year, as it is not useful, who doesn't know the current year. Or a general option to allow a string specifying the format.[1] [1] http://doc.qt.io/qt-5/qml-qtqml-date.html#details Reproducible: Always Expected Results: More option to display the time and date format. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it
https://bugs.kde.org/show_bug.cgi?id=364915 --- Comment #4 from Götz <goetzchr...@gmail.com> --- I see this issue since the past year, on an [AMD/ATI] Mullins, Radeon R3 Graphics. xf86-video-ati 7.7.0 mesa 12.0.1 linux 4.6.4 Plasma 5.7.2 Qt 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 366317] New: When resuming from suspend, the desktop is shown before kscreenlocker_greet starts
https://bugs.kde.org/show_bug.cgi?id=366317 Bug ID: 366317 Summary: When resuming from suspend, the desktop is shown before kscreenlocker_greet starts Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: goetzchr...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Sometimes when resuming from suspend, the desktop with the opened windows and panel is shown for a short period of time ~1 second. It seems that kscreenlocker_greet starts after resuming, maybe starting it before suspending could improve this. Reproducible: Sometimes Actual Results: Desktop with open windows and possible private data is shown. Expected Results: Don't show the desktop. I have seen this since some versions ago. Currently using latest version 5.7.2. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 365963] New: Try to take the screenshot ASAP on startup
https://bugs.kde.org/show_bug.cgi?id=365963 Bug ID: 365963 Summary: Try to take the screenshot ASAP on startup Product: Spectacle Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: goetzchr...@gmail.com If you want to take a screenshot of something in screen that can change quickly, and if Spectacle starts 'slowly', the taken screenshot will no be the same image as it was, when the screenshot key was pressed. Reproducible: Always Actual Results: The screenshot image is no the one expected as the time has passed, 2-4 seconds. Expected Results: When I press the Prt Scr key, I expect to see the same screenshot image as the one taken. ImageMagic's takes the shot instantaneously, maybe because it has no GUI: import -window root ~/name.png If spectacle could take the screenshot ASAP, before starting the GUI, it would be handy in some situations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365780] Blur effect doesn't work with semi-transparent windows
https://bugs.kde.org/show_bug.cgi?id=365780 --- Comment #2 from Götz <goetzchr...@gmail.com> --- Oh, so it is not forced by the compositor. The actual effect description seems to state that it is. Shouldn't the description be updated to reflect that? And what about a similar effect which does force blur all transparent regions? Or how could that be archived, a kwin rule? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365780] New: Blur effect doesn't work with semi-transparent windows
https://bugs.kde.org/show_bug.cgi?id=365780 Bug ID: 365780 Summary: Blur effect doesn't work with semi-transparent windows Product: kwin Version: 5.7.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: goetzchr...@gmail.com The Blur effect description says: "Blurs the background of semi-transparent windows". But it seems to only work for the Plasma widget Application Dashwoard, and does not work with other windows like Konsole of Firefox, or tooltip pop-ups. Reproducible: Always Steps to Reproduce: 1a. Move a window with Alt key and mouse click. or 1b. Move the mouse over some widget with a tooltip so that a pop-up appears. Actual Results: 1a. The window becomes transparent and has not blur effect. 1b. The pop-up is transparent without blur. Expected Results: A transparent and blurred window. The blur effect is active with the default settings. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364991] Don't only search for kioclient, but (also) for kioclient5
https://bugs.kde.org/show_bug.cgi?id=364991 --- Comment #2 from Götz <goetzchr...@gmail.com> --- Sure: https://phabricator.kde.org/D2066 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364991] New: Don't only search for kioclient, but (also) for kioclient5
https://bugs.kde.org/show_bug.cgi?id=364991 Bug ID: 364991 Summary: Don't only search for kioclient, but (also) for kioclient5 Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: goetzchr...@gmail.com When trying to use the Konsole inside KDevelop, the below message appears, kioclient5 is installed. In Arch Linux, package kde-cli-tools includes the kioclient5 binary. "The utility kioclient is not in your path, the shell integration will not work properly." Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364989] Add option to select the whole text line
https://bugs.kde.org/show_bug.cgi?id=364989 --- Comment #1 from Götz <goetzchr...@gmail.com> --- Created attachment 99794 --> https://bugs.kde.org/attachment.cgi?id=99794=edit screenshot Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364989] New: Add option to select the whole text line
https://bugs.kde.org/show_bug.cgi?id=364989 Bug ID: 364989 Summary: Add option to select the whole text line Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: goetzchr...@gmail.com Like the feature available in Sublime Text, where you can expand the selection to the current line (there are also options for: word, paragraph, scope, brackets, indentation, tag). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 364988] New: FTBFS: error: ‘WhitespaceSensitivity’ does not name a type
https://bugs.kde.org/show_bug.cgi?id=364988 Bug ID: 364988 Summary: FTBFS: error: ‘WhitespaceSensitivity’ does not name a type Product: kdev-python Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@svenbrauch.de Reporter: goetzchr...@gmail.com CC: m...@svenbrauch.de When building from git master, I get this error: kdevelop-python3-git/src/kdev-python/pythonlanguagesupport.h:70:5: error: ‘WhitespaceSensitivity’ does not name a type WhitespaceSensitivity whitespaceSensititivy() const override; ^ make[2]: *** [duchain/CMakeFiles/kdevpythonduchain.dir/build.make:255: duchain/CMakeFiles/kdevpythonduchain.dir/contextbuilder.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:591: duchain/CMakeFiles/kdevpythonduchain.dir/all] Error 2 make: *** [Makefile:139: all] Error 2 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #44 from Götz <goetzchr...@gmail.com> --- Today I found something interesting. First the screenlocker was frozen, then I changed the brightness with the corresponding hotkey and the screenlocker unfroze, the cursor was blinking and I could write the password and unlock the screen. Another thing, sometimes, when waking from suspend, shows a black screen, as if the display backlight was very dimmed. Changing brightness makes the display functional. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 355421] Konsole crashed on login
https://bugs.kde.org/show_bug.cgi?id=355421 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #37 from Götz <goetzchr...@gmail.com> --- This is strange, since a week or two, using KWin with OpenGL 2.0 and XGL composition, when the locker becomes unresponsive, just switching to a TTY and back (without killing any process) makes the locker become responsive again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355577] KIconLoader::global()->theme() returns a nullptr and crashes plasma
https://bugs.kde.org/show_bug.cgi?id=355577 Götz <goetzchr...@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 --- Comment #5 from Götz <goetzchr...@gmail.com> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #33 from Götz <goetzchr...@gmail.com> --- I forgot to add, that before restarting the greeter, I used a shortcut to change the Keyboard Layout, and after the greeter restarted, the layout was changed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #32 from Götz <goetzchr...@gmail.com> --- Using EGL, there same issue(s) continue. > Can you try to kill just kscreenlocker_greet instead? (see jmux's input) Yes, the newly restarted kscreenlocker_greet works fine, and after unlocking it, plasmashell is unresponsive. Is it also unresponsive for you Jan-Marek? After killing plasmashell, the panel is still shown (there is no longer a plasma process). Restarting kwin_x11 solves this. For me, at the beginning (December), switching to a TTY and back was sufficient to make kscreenlocker_greet work, but since February (see comment #13) it was not sufficient and had to kill kscreenlocker_greet. > In such case, suspending the compositor (SHIFT+Alt+F12) *after* the assumed > unlock should present you the uncomposited, but correct desktop. I 'll try this on the next opportunity. > Is this btw. part of the broken process? I have not seen a correlation between the greeter not responding and the artifacts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #27 from Götz <goetzchr...@gmail.com> --- It seems that there are no "OpenGL interface" options (the combobox is empty), when kwin is not running. Bug or feature? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #26 from Götz <goetzchr...@gmail.com> --- > Comment #2 said "Just tried using KWin with compton as compositor and the > same problem." I don't remember that :) There are to many variables I forgot that one. > Yes, but while hidden when you select XRender, it's never supposed to be > disabled (there's simply no code that does such) - and in your case should > list GLX & EGL This is also strange. The combobox was empty while OpenGL 2.0 or 3 where selected. Now I see the options (now sure what changed) and I have selected EGL. But now, after using kwin_x11 with compton, then selecting EGL and applying, kwin seems to be frozen. Killing it makes the GUI intractable again. I can reproduce this and open a new bug report if you like. > What exactly did you kill? I will try to be more descriptive: A timeout has passed and the screen locked. The locker was frozen or it was kwin, but the screen did not react to keyboard input or mouse clicks, only the cursor could be moved around. Then I entered the password and Enter; nothing changes on screen. Then I switched to TTY 2 to kill kwin_x11, back to TTY 1 and I see those Firefox tabs (first screenshot). So I kill kscreenlocker_greet, which changes the screen content to my desktop, showing a window and the kscreenlocker background in the vertical-left Plasma panel area (second screenshot). Then I started kwin_x11, parts of the screen flickered. Killing and restarting kwin makes everything work again. > So either the screenlocker are artifacts in the framebuffer or the konsole > window managed to raise above the screenlocker. I think it where the artifacts, and that the locker was working but kwin did not work correctly. So the screen unlocked after entering the password, but kwin didn't update the screen content. But there is something else, today after starting the computer from suspend, the first thing I was was my desktop wallpaper, the it changed rapidly to the locker screen with its own wallpaper image. I can observe such behavior very often. > try to invoke the greeter directly instead of locking the screen: It does work, but I will continue doing this and Ctrl+Alt+L and letting the screen lock automatically to see what happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #24 from Götz <goetzchr...@gmail.com> --- > - Have you tried EGL compositing? I haven't tried EGL. And I don't known how to do it. Is that the 'OpenGL interface' in System Settings? That combobox is disabled in my system. And I haven't tried KWin + compton (will do it now), only the KWin build-in compositor, and openbox+compton. > - Was/is the konsole window in the second shot interactable? Yes it was interactable. > About the input behavior What I meant with "kwin_x11 --replace and locking the screen makes everything unusable (windows don't react or react strange to keyboard or mouse input)", was that Ctrl+Alt+L didn't show the kscreenlocker greeter, I don't know if it started maybe yes, as it brought problems for input. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #22 from Götz <goetzchr...@gmail.com> --- Created attachment 97730 --> https://bugs.kde.org/attachment.cgi?id=97730=edit then, screenshot after killing kscreenlocker the left Plasma panel is not shown, only an empty transparent section, showing the kscreenlocker background (not my plasma wallpaper). The button panel is shown but without widgets. After invoking kwin_x11, the screen flickers when updating content. Killing and restarting kwin_x11 makes everything work again. Locking the screen and unlocking works too. But usually, after n times it won't work. All this with kwin compositor OpenGL 2 or 3. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #21 from Götz <goetzchr...@gmail.com> --- Created attachment 97729 --> https://bugs.kde.org/attachment.cgi?id=97729=edit After killing kwin_x11 kscreenlocker is active/shown, but without reacting to keyboard input, password is entered, without screen being updated. Then after killing kwin_x11, some Firefox tabs are shown. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #20 from Götz <goetzchr...@gmail.com> --- I can not reproduce that, but other odd things happen. It was, Alt+Tab not working, Alt+F4 neither, mouse clicks don't works. Sometimes kscreenlocker works but after unlocking, screen parts which update, flicker. I'll also attach some pictures and screenshots. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #19 from Götz <goetzchr...@gmail.com> --- Created attachment 97728 --> https://bugs.kde.org/attachment.cgi?id=97728=edit "qdbus org.kde.KWin /KWin supportInformation" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 Götz <goetzchr...@gmail.com> changed: What|Removed |Added Component|general |general Version|5.5.1 |5.5.5 Product|kscreenlocker |kwin --- Comment #16 from Götz <goetzchr...@gmail.com> --- This issue is going worse, but now I think it is caused by KWin. When using Openbox and with compton as compositor the problem is gone, kscreenlocker_greet works all the time. kwin_x11 --replace and locking the screen makes everything unusable (windows don't react or react strange to keyboard or mouse input) , openbox --replace makes the desktop usable again. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #15 from Götz <goetzchr...@gmail.com> --- Now it seems that with Caledonia the same issue continues, and it just happen using Oxygen as Plasma theme. All this with compositor enabled. A note about the freeze, now the locker freezes and there is no workaround I'm aware of, to unfreeze it. I have to kill it sending signal 9. With signal 15 it doesn't respond. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #13 from Götz <goetzchr...@gmail.com> --- Now (after some updates), when running with the compositor, kscreenlocker_greet doesn't respond even after switching to a TTY and back. After killing the process, and it being self-restarted plasmashell becomes unresponsive. I'll test using another theme as suggested by mrl586. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #14 from Götz <goetzchr...@gmail.com> --- I can confirm that kscreenlocker_greet works without problems using Caledonia as Plasma theme. The problem occurs using Breeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359113] New: System tray icons overlap
https://bugs.kde.org/show_bug.cgi?id=359113 Bug ID: 359113 Summary: System tray icons overlap Product: plasmashell Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: goetzchr...@gmail.com Sometimes, when starting Plasma from login manager or after killing and restarting plasmashell, the arrow icon (to show more icons) and the next visible icon (Networks in my setup) overlap. See screenshots. Reproducible: Sometimes I have seen the bug since some releases ago, maybe Plasma 5.4 or 5.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359113] System tray icons overlap
https://bugs.kde.org/show_bug.cgi?id=359113 --- Comment #1 from Götz <goetzchr...@gmail.com> --- Created attachment 97073 --> https://bugs.kde.org/attachment.cgi?id=97073=edit system tray showing two icons overlaping -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 358830] New: Display file name in window title
https://bugs.kde.org/show_bug.cgi?id=358830 Bug ID: 358830 Summary: Display file name in window title Product: ark Version: 15.12.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kdemail.net Reporter: goetzchr...@gmail.com CC: rak...@freebsd.org Just like web browsers or music players. e.g.: archive.zip - Ark Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353195] Copy error for folders with mixed files & folders in Split View
https://bugs.kde.org/show_bug.cgi?id=353195 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #9 from Götz <goetzchr...@gmail.com> --- Created attachment 96602 --> https://bugs.kde.org/attachment.cgi?id=96602=edit glxinfo It does not freeze always, but sometimes, using the OpenGL compositor. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #7 from Götz <goetzchr...@gmail.com> --- With XRender the lockscreen seems to be responsive every time. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355540] Tooltips color wrong in gtk applications
https://bugs.kde.org/show_bug.cgi?id=355540 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com --- Comment #5 from Götz <goetzchr...@gmail.com> --- I experience the same issue GTK+2 and GTK+3 have light on light tooltip. But additionally I can see in a PyQt4 app (PyQt5 works), that the tooltip is not like the default Breeze color scheme, it shows dark text on a light background. So it seems that only Qt5 apps use the Breeze color scheme style. Arch Linux Plasma 5.5.2 KF 5.17 Qt 5.5.1 GTK+ 3.18.6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355540] Tooltips color wrong in gtk applications
https://bugs.kde.org/show_bug.cgi?id=355540 --- Comment #6 from Götz <goetzchr...@gmail.com> --- Qt4 and Qt5 tooltips http://i.imgur.com/xr5bQtX.png -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 353168] Akregator is unable to fetch favicons
https://bugs.kde.org/show_bug.cgi?id=353168 Götz <goetzchr...@gmail.com> changed: What|Removed |Added CC||goetzchr...@gmail.com --- Comment #5 from Götz <goetzchr...@gmail.com> --- Is this what you mean? https://quickgit.kde.org/?p=kde-baseapps.git In path: /lib/konq/favicons/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357289] Broken path in "bread crumb" mode in FTP
https://bugs.kde.org/show_bug.cgi?id=357289 --- Comment #1 from Götz <goetzchr...@gmail.com> --- Created attachment 96347 --> https://bugs.kde.org/attachment.cgi?id=96347=edit "bread crumb" mode showing the issue -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357289] Broken path in "bread crumb" mode in FTP
https://bugs.kde.org/show_bug.cgi?id=357289 --- Comment #2 from Götz <goetzchr...@gmail.com> --- Created attachment 96348 --> https://bugs.kde.org/attachment.cgi?id=96348=edit In "edit mode" without issue, and right path -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #2 from Götz <goetzchr...@gmail.com> --- Just tried using KWin with compton as compositor and the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] New: kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 Bug ID: 357007 Summary: kscreenlocker_greet unresponsive when using compositor Product: kscreenlocker Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: goetzchr...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org When using the kwin_x11 compositor, sometimes the screenlocker is unresponsive, like it is freezed. Switching to a TTY and back to the locker "unfreezes" everything and it is possible to enter the password. When disabling the compositor Sift+ALT+F12, the locker doesn't freeze, it works as expected. Reproducible: Sometimes When it is "freezed", it is possible to enter the password and press Enter, but the screen doesn't change. A switch to a virtual console and back shows the unlocked desktop. I have observed this behavior not only in version 5.5.x, but also with version 5.4 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #1 from Götz <goetzchr...@gmail.com> --- 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] linux 4.2.5 (x86_64) xf86-video-ati 7.6.1 xorg-server 1.18.0 mesa 11.0.7 qt5-base 5.5.1 KF 5.17 -- You are receiving this mail because: You are watching all bug changes.
