[QtCurve] [Bug 391535] Inactive menu items have same color as active items
https://bugs.kde.org/show_bug.cgi?id=391535 Petr Nehez changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Petr Nehez --- Sorry, I am not using KDE anymore so I have no idea. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390457] Task manager pixelated previews
https://bugs.kde.org/show_bug.cgi?id=390457 Petr Nehez changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Petr Nehez changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 Petr Nehez changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #37 from Petr Nehez --- Thanks, I see. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #35 from Petr Nehez --- And could you help me where in Breeze theme/icons I can find such icons? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #33 from Petr Nehez --- OK, my bad - "network-cellular-signal-*" icons are from Papirus icons set. But the point is that if make such symlinks (to any existing icon from Breeze theme) the icon starts to work again. I have checked https://cgit.kde.org/breeze-icons.git/tree/icons-dark/status/22 and I cannot see there any "network-mobile-*" icon. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #31 from Petr Nehez --- So actually it turned out to be an issue between NM and icons set. When I created the following symlinks, the icon started to work. network-mobile-0-lte-limited.svg -> network-cellular-signal-good.svg network-mobile-0-lte.svg -> network-cellular-signal-good.svg network-mobile-100-lte.svg -> network-cellular-signal-good.svg network-mobile-40-lte.svg -> network-cellular-signal-good.svg network-mobile-60-lte.svg -> network-cellular-signal-good.svg network-mobile-80-lte.svg -> network-cellular-signal-good.svg But I do not think creating of such symlinks for in each possible icon set would be the best approach. What if NM would start using of "network-cellular-signal-*" icons? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 382452] Empty input field shorter in height by 1px
https://bugs.kde.org/show_bug.cgi?id=382452 Petr Nehez changed: What|Removed |Added Version|5.10.3 |5.50.0 Component|breeze-theme|components Assignee|plasma-b...@kde.org |notm...@gmail.com Product|kscreenlocker |frameworks-plasma Platform|Kubuntu Packages|unspecified -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #30 from Petr Nehez --- Created attachment 113133 --> https://bugs.kde.org/attachment.cgi?id=113133=edit plasma-log-limited-2 And what is strange that the icon in the plasmoid was not change even I could see in the terminal that modem is reporting signal strength at 60%. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #29 from Petr Nehez --- Created attachment 113132 --> https://bugs.kde.org/attachment.cgi?id=113132=edit plasma-log-limited Finally after few days I've got the icon for limited signal. See the attached log. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #28 from Petr Nehez --- I am running Plasma with the patched plasma-nm package already for 2 days (with few suspend & resume actions every day) and when I was on modem connection only (in a train) I spent approx 1 hour trying to replicate the issue. It could be just an issue of my modem which was reporting wrong signal value or an issue of the driver, who knows? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #27 from Petr Nehez --- I was trying to replicate the issue again but unfortunately my modem was not reporting "limited" or "zero" signal for few days what I could see so far. Isn't the real issue that there are no icons for the suffix "-limited"? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 394820] System Monitor crashed after closing it
https://bugs.kde.org/show_bug.cgi?id=394820 Petr Nehez changed: What|Removed |Added Platform|unspecified |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 394820] New: System Monitor crashed after closing it
https://bugs.kde.org/show_bug.cgi?id=394820 Bug ID: 394820 Summary: System Monitor crashed after closing it Product: ksysguard Version: 5.12.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- Application: ksysguard (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.16.12-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: I was having 2 instances of SM and after I close the 2nd instance with Alt+F4 it crashed... The crash does not seem to be reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd07bfc5e80 (LWP 7471))] Thread 4 (Thread 0x7fd052cb2700 (LWP 7474)): #0 0x7fd07b90bea9 in poll () at /usr/lib/libc.so.6 #1 0x7fd06d96d523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd06d96d63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd077101254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd0770a331b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd076eb271e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd0777bb416 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fd076eb7abd in () at /usr/lib/libQt5Core.so.5 #8 0x7fd06f992075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd07b91653f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd05ea75700 (LWP 7473)): #0 0x7fd07b90bea9 in poll () at /usr/lib/libc.so.6 #1 0x7fd0701e9180 in () at /usr/lib/libxcb.so.1 #2 0x7fd0701eae4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fd06140882a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fd076eb7abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fd06f992075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd07b91653f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd062741700 (LWP 7472)): #0 0x7fd06f997ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd076b33d5d in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:864 #2 0x7fd076b33d5d in std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7fd07528b379 in () at /usr/lib/libQt5WebKit.so.5 #4 0x7fd07528b4c9 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7fd076b39d3f in execute_native_thread_routine (__p=0x55debf6420d0) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:80 #6 0x7fd06f992075 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fd07b91653f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd07bfc5e80 (LWP 7471)): [KCrash Handler] #6 0x7fd076f344fa in operator==(QString const&, QString const&) () at /usr/lib/libQt5Core.so.5 #7 0x7fd078481cf8 in QLabel::setText(QString const&) () at /usr/lib/libQt5Widgets.so.5 #8 0x7fd07bc4bb57 in () at /usr/lib/libkdeinit5_ksysguard.so #9 0x7fd07acd495a in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/libksgrd.so.7 #10 0x7fd07acdbdc6 in () at /usr/lib/libksgrd.so.7 #11 0x7fd0770d572f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7fd07701d76b in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7fd07702448a in () at /usr/lib/libQt5Core.so.5 #14 0x7fd077024970 in () at /usr/lib/libQt5Core.so.5 #15 0x7fd0770d5606 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #16 0x7fd0770e1ee9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #17 0x7fd0770e22c4 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #18 0x7fd078343fec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7fd07834b9c6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7fd0770a4ce0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7fd077101ece in () at /usr/lib/libQt5Core.so.5 #22 0x7fd06d96d368 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #23 0x7fd06d96d5b1 in () at /usr/lib/libglib-2.0.so.0 #24 0x7fd06d96d63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #25 0x7fd077101231 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7fd061490482 in () at
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #26 from Petr Nehez --- I applied the patch to the master branch and installed the package. I think the issue is noticeable in areas with weak signal so when I am travelling with the train I will be testing it. Now when I am in the office and the mobile signal is strong and I play with connecting & disconnecting to/from LAN and/or Wifi and/or mobile I am not able to replicate the issue. I will let you know. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391992] crash on close
https://bugs.kde.org/show_bug.cgi?id=391992 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392215] Segmentation fault on Exit
https://bugs.kde.org/show_bug.cgi?id=392215 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 391176] System monitor stopped saving settings
https://bugs.kde.org/show_bug.cgi?id=391176 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390885] Crash after changes in System Tray Settings
https://bugs.kde.org/show_bug.cgi?id=390885 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 391403] KSysGuard does not remember columns setup
https://bugs.kde.org/show_bug.cgi?id=391403 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 394364] Connection with higher priority is not activated
https://bugs.kde.org/show_bug.cgi?id=394364 --- Comment #3 from Petr Nehez <petr.ne...@gmail.com> --- @Jan Grulich Out of curiosity - do you know why a magic number of 2 is being added into connection's metric? https://unix.stackexchange.com/questions/444538/metric-on-connections-and-magic-2-value-added -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 394364] Connection with higher priority is not activated
https://bugs.kde.org/show_bug.cgi?id=394364 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- OK, I will try to use metric of each connection whether it helps. It's just annoying that when I plug in a cable my LAN connection is not chosen as the default one and the system still uses modem. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 394364] New: Connection with higher priority is not activated
https://bugs.kde.org/show_bug.cgi?id=394364 Bug ID: 394364 Summary: Connection with higher priority is not activated Product: plasma-nm Version: 5.12.5 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: petr.ne...@gmail.com Target Milestone: --- I have 3 types of connection: * LAN with priority p=10, * WiFi with p=5, * 4G/LTE with p=-1. The active and working connection with the highest priority is not activated when it should be. Example: 1) There are no active connections. 2) I activate modem p=-1 and it is active and working. 3) Then I activate WiFi with p=5, the connection is established but it is not activated and the system is still using modem. I am Manjaro KDE and in the past when I was on Kubuntu this was working fine... -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #24 from Petr Nehez <petr.ne...@gmail.com> --- And when I connected to VPN (a lock appeared on a modem icon) and then disconnected it, the icon changed to 0-signal modem icon. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #23 from Petr Nehez <petr.ne...@gmail.com> --- I forgot to mention that the connection is working fine when it reports Signal=0. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #22 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 112701 --> https://bugs.kde.org/attachment.cgi?id=112701=edit bad-icon.log It took me a while to replicate it but finally I got the bad icon. Could it be caused that the modem driver is not responding with the correct signal value? As you can see there are only 0 values. I can tell you that the real signal is over 90, in the previous logs I could see the value 93, but that value appeared when I disconnetced and connected to the modem several times. And what about the icon "network-mobile-0-lte-limited"? Isn't it that issue? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #20 from Petr Nehez <petr.ne...@gmail.com> --- I compiled it with the applied patch,d added "export QT_LOGGING_RULES=plasma-nm*.debug=true" into my .profile file and restarted my system. Could you help me now where I should see log output? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #18 from Petr Nehez <petr.ne...@gmail.com> --- I don't see anything about QT_LOGGING_CATEGORY there. Did you mean QT_LOGGING_RULES? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #16 from Petr Nehez <petr.ne...@gmail.com> --- OK, I cloned the repo and could compile plasma-nm with this cmake command: cmake ../ -DCMAKE_INSTALL_PREFIX=/usr I did not try to install it yet so I can try your patch. Hopefully my system won't break then 'cause I would break my working env :) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #15 from Petr Nehez <petr.ne...@gmail.com> --- I would try that although I have not compiled any regular package yet. I am on Manjaro where my plasma-nm is 5.12.5 so I guess I should clone https://cgit.kde.org/plasma-nm.git/log/?h=Plasma/5.12 and then apply a patch? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #13 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 112648 --> https://bugs.kde.org/attachment.cgi?id=112648=edit network-with-breeze It seemed OK with Breeze theme until I was on EDGE with VPN and after disconnecting of VPN the network icon was shown. But after a while when I was preparing this screenshot it got fixed to correct mobile network icon (most likely due to a change from EDGE to 4G/LTE). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #12 from Petr Nehez <petr.ne...@gmail.com> --- OK, I have changed the theme and will be watching it. But the weird thing is that sometimes the icon is correct but in most cases it's not. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #10 from Petr Nehez <petr.ne...@gmail.com> --- Is here anybody who could fix this issue? I can be helpful on it... -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393717] Icon's preview is huge after login
https://bugs.kde.org/show_bug.cgi?id=393717 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC||petr.ne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393717] New: Icon's preview is huge after login
https://bugs.kde.org/show_bug.cgi?id=393717 Bug ID: 393717 Summary: Icon's preview is huge after login Product: plasmashell Version: 5.12.4 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112339 --> https://bugs.kde.org/attachment.cgi?id=112339=edit preview-full-screen-width When I login into Plasma the very first icon preview is shown with the full screen width. When another preview is shown it's already OK and the issue does not occur until the next login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383828] Crash in QV4::QObjectWrapper::getProperty
https://bugs.kde.org/show_bug.cgi?id=383828 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #9 from Petr Nehez <petr.ne...@gmail.com> --- If anybody wants a help I am here as it annoys me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Petr Nehez <petr.ne...@gmail.com> --- I installed and compiled 4.0.0 from AUR/krita-minimal and this issue is not happening anymore. But I get a new one - https://bugs.kde.org/show_bug.cgi?id=392215. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392215] New: Segmentation fault on Exit
https://bugs.kde.org/show_bug.cgi?id=392215 Bug ID: 392215 Summary: Segmentation fault on Exit Product: krita Version: 4.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- When I start and quit Krita I get Segmentation fault. Application: krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8d96042800 (LWP 27955))] Thread 3 (Thread 0x7f8d58fd7700 (LWP 27962)): #0 0x7f8d8cf3e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8d9309e5bd in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:864 #2 0x7f8d9309e5bd in std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7f8d45f90d09 in () at /usr/lib/libQt5WebKit.so.5 #4 0x7f8d45f90e59 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7f8d930a4b9f in std::execute_native_thread_routine(void*) (__p=0x56094507ca00) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:83 #6 0x7f8d8cf3808c in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f8d92b12e7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8d6ce89700 (LWP 27958)): #0 0x7f8d92b0897b in poll () at /usr/lib/libc.so.6 #1 0x7f8d8b3a4ff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8d8b3a510e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f8d9366b314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f8d9360d3db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f8d9341c7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8d8d163416 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f8d93421b4d in () at /usr/lib/libQt5Core.so.5 #8 0x7f8d8cf3808c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f8d92b12e7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f8d96042800 (LWP 27955)): [KCrash Handler] #6 0x7f8d8cf40e39 in sem_wait@@GLIBC_2.2.5 () at /usr/lib/libpthread.so.0 #7 0x7f8d54f8ff26 in PyThread_acquire_lock_timed () at /usr/lib/libpython3.6m.so.1.0 #8 0x7f8d550860cd in () at /usr/lib/libpython3.6m.so.1.0 #9 0x7f8d54f1cd56 in () at /usr/lib/libpython3.6m.so.1.0 #10 0x7f8d544bf345 in () at /usr/lib/python3.6/site-packages/sip.so #11 0x7f8d5421eef7 in sipDockWidgetFactoryBase::~sipDockWidgetFactoryBase() () at /usr/lib/krita-python-libs/PyKrita/krita.so #12 0x7f8d5421ef1a in sipDockWidgetFactoryBase::~sipDockWidgetFactoryBase() () at /usr/lib/krita-python-libs/PyKrita/krita.so #13 0x7f8d8fd9a7ae in KoDockRegistry::~KoDockRegistry() () at /usr/lib/libkritaflake.so.16 #14 0x7f8d8fd9a8ca in () at /usr/lib/libkritaflake.so.16 #15 0x7f8d92a54448 in __run_exit_handlers () at /usr/lib/libc.so.6 #16 0x7f8d92a5449a in () at /usr/lib/libc.so.6 #17 0x7f8d92a3df51 in __libc_start_main () at /usr/lib/libc.so.6 #18 0x560939cf709a in _start () -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 378881] Laptop screen doesn't wake up after disconnecting HDMI
https://bugs.kde.org/show_bug.cgi?id=378881 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- I found the cause - it was caused by my change :O of /etc/X11/xorg.conf.d/20-intel.conf. The problem was Option "AccelMethod" "uxa" and when I changed it back to Option "AccelMethod" "sna" it started to work again. The reason I changed this configuration was an attempt to play with with hw acceleration in Firefox which btw did not help. https://forum.manjaro.org/t/external-monitor-does-not-wake-up/41985/37?u=peke -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 378881] Laptop screen doesn't wake up after disconnecting HDMI
https://bugs.kde.org/show_bug.cgi?id=378881 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- AppImage 4.0.0 is working fine, I wonder if it is because of all bundled libraries or by fixes inside Krita itself. Will let you know later. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 --- Comment #3 from Petr Nehez <petr.ne...@gmail.com> --- Can I try AppImage from https://download.kde.org/stable/krita/4.0.0/? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 --- Comment #1 from Petr Nehez <petr.ne...@gmail.com> --- The report above is from version 4.0.0.51 beta build from AUR but I get the same exception when I install 3.3.3 from Manjaro's repository. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392162] New: Floating point exception when using speficic selection and applying blur efect
https://bugs.kde.org/show_bug.cgi?id=392162 Bug ID: 392162 Summary: Floating point exception when using speficic selection and applying blur efect Product: krita Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- Application: Krita (krita), signal: Floating point exception Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f3ea06800 (LWP 13808))] Thread 12 (Thread 0x7f1ed7fff700 (LWP 13876)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7f1eed9b1700 (LWP 13874)): [KCrash Handler] #6 0x7f1f090e9d8d in ?? () from /usr/lib/kritaplugins/kritaextensioncolorsfilters.so #7 0x7f1f3e194902 in KisFilterStrokeStrategy::doStrokeCallback(KisStrokeJobData*) () from /usr/lib/libkritaui.so.16 #8 0x7f1f394fd33c in ?? () from /usr/lib/libkritaimage.so.16 #9 0x7f1f3bcb6b22 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #11 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #12 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7f1eef0f4700 (LWP 13873)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f1eed1b0700 (LWP 13872)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1eec9af700 (LWP 13871)): #0 0x7f1f352bc6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbaee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3bcb6db1 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1eef8f5700 (LWP 13821)): #0 0x7f1f352bc3bd in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f3bcbb02c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1f3ce45586 in ?? () from /usr/lib/libQt5Widgets.so.5 #3 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f1ef00f6700 (LWP 13820)): #0 0x7f1f33769b94 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f1f337229f2 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f1f33722f96 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f1f3372310e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f1f3bf03314 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f1f3bea53db in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1f3bcb47ae in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f1f2223250b in ?? () from /usr/lib/libQt5Quick.so.5 #8 0x7f1f3bcb9b4d in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f1f352b608c in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f1f3b3aae7f in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1f01027700 (LWP 13819)): #0 0x7f1f33769b94 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f1f33722fad in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1f3372310e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f1f3bf03314 in
[plasmashell] [Bug 391915] New: Task manager thumbnail scaling method
https://bugs.kde.org/show_bug.cgi?id=391915 Bug ID: 391915 Summary: Task manager thumbnail scaling method Product: plasmashell Version: 5.12.3 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 111434 --> https://bugs.kde.org/attachment.cgi?id=111434=edit task-thumbnail Would it be possible to improve a method for generating of the thumbnail? It is just an ugly scaled down image... -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391811] Keyboard backlight is always off when laptop is resumed
https://bugs.kde.org/show_bug.cgi?id=391811 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- I went back to kernel 4.14, even 6 steps back, nothing has changed. Then I upgraded to the latest 4.14 again and voila - backlight works as expected. That's a magic - I don't like these bugs ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 --- Comment #8 from Petr Nehez <petr.ne...@gmail.com> --- This issue is still present on my laptop though... Could you at least help me and suggest me a way (ways) how to narrow down the cause? Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #7 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 111388 --> https://bugs.kde.org/attachment.cgi?id=111388=edit lan-network I am now connected via LAN and the icon is with red circle. I was connecting & disconnecting to LAN and/or WiFi because I had some issue with the specific WiFi and after disconnecting from WiFi it ended up with this crossed LAN icon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 --- Comment #6 from Petr Nehez <petr.ne...@gmail.com> --- Hmm, I upgraded my linux414 packages back to the latest ones and now it seems to be working fine... I am confused. I will be watching it and if it starts to work again then... would it be something with the kernel? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DOWNSTREAM |--- --- Comment #5 from Petr Nehez <petr.ne...@gmail.com> --- I went back to 4.14 and then downgraded this kernel (even 6 updates back) and the issue is still present. So it could not be the kernel issue because I am 100% sure this was working fine before the last update of KDE from Manjaro. Could you suggest me ways how to isolate the issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #6 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 111384 --> https://bugs.kde.org/attachment.cgi?id=111384=edit network-folder-breeze-2 I changed Look & Feel theme to Breeze Dark because I forgot that plasmoid icons are driven by that but as you can see there is the same issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- Strange thing is that icons of plasmoids have not been updated. I deleted cache, restarted system... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #3 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 111376 --> https://bugs.kde.org/attachment.cgi?id=111376=edit network-folder-breeze This is screenshot with empty icon... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 391821] Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 111375 --> https://bugs.kde.org/attachment.cgi?id=111375=edit network-folder-ubuntu When I set Breeze, I had even no icon there. And when I set Ubuntu icons, I had network folder there as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 391821] New: Icon of mobile broadband network is sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=391821 Bug ID: 391821 Summary: Icon of mobile broadband network is sometimes wrong Product: frameworks-plasma Version: 5.43.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: petr.ne...@gmail.com Target Milestone: --- Created attachment 111368 --> https://bugs.kde.org/attachment.cgi?id=111368=edit network-folder I use Papirus icon pack on Manjaro (community/papirus-icon-theme) but sometimes broadband icon is wrong - it shows network folder instead. It happens rarely ONLY with broadband network - neither with Wifi or with LAN. When I was using Kubuntu I have never met such issue. Since the time I started to use Manjaro KDE I sometimes face this issue. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391811] Keyboard backlight is always off when laptop is resumed
https://bugs.kde.org/show_bug.cgi?id=391811 --- Comment #1 from Petr Nehez <petr.ne...@gmail.com> --- Kernel: 4.15.7-1-MANJARO x86_64 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391811] New: Keyboard backlight is always off when laptop is resumed
https://bugs.kde.org/show_bug.cgi?id=391811 Bug ID: 391811 Summary: Keyboard backlight is always off when laptop is resumed Product: Powerdevil Version: 5.12.2 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- It seems that power management is broken. Whenever I resume my laptop keyboard backlight is off eventhough it was ON before. All 3 modes (AC/bat/lowbat) has not been changed for at least a month and it has no value set in all 3 modes for keyboard backlight. I am having other issue with recent Plasma - https://bugs.kde.org/show_bug.cgi?id=391558, probably related? This is part of journal after resuming: bře 13 14:50:17 NEHEZ-DELL org_kde_powerdevil[1067]: [14::50:17.102] unknown: Kbd backlight brightness value: 0 bře 13 14:50:17 NEHEZ-DELL org_kde_powerdevil[1067]: [14::50:17.102] unknown: set kbd backlight value: 0 bře 13 14:50:17 NEHEZ-DELL org_kde_powerdevil[1067]: [14::50:17.114] unknown: Keyboard brightness changed!! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 --- Comment #3 from Petr Nehez <petr.ne...@gmail.com> --- https://forum.manjaro.org/t/external-monitor-does-not-wake-up/41985 https://forum.manjaro.org/t/screen-goes-black-after-10-mins/41857 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- The workaround to wake up the monitor is to start a new terminal (e.g. Ctrl+Alt+F2) and then back to terminal 1 by pressing Ctrl+Alt+F1. This issue is super annoying... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 --- Comment #1 from Petr Nehez <petr.ne...@gmail.com> --- Does anybody know how to find such problem in logs? I enabled KScreen logging but there I don't see anything... In which log can I see something regarding switching off the screen and waking up again? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC||k...@davidedmundson.co.uk, ||se...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] New: External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 Bug ID: 391558 Summary: External monitor does not wake up Product: plasmashell Version: 5.12.2 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 My external monitor is not waken up when I move with a mouse or press a key after it has been previously switched off by the system while laptop’s screen is not used at all (OFF) while the monitor is plugged in. I have to unplug it and then plug it again. Any idea? Manjaro KDE, Plasma 5.12.2, Frameworks 5.43, Qt, 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions
https://bugs.kde.org/show_bug.cgi?id=381515 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380931] Indicator of multiple windows gets hidden
https://bugs.kde.org/show_bug.cgi?id=380931 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 379452] Plasma crash while searching for application from Application Launcher
https://bugs.kde.org/show_bug.cgi?id=379452 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386381] Plasma utilizing 100% CPU (1 core) after upgrade to 17.10
https://bugs.kde.org/show_bug.cgi?id=386381 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385505] Plasma crashed when starting Muon
https://bugs.kde.org/show_bug.cgi?id=385505 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380432] Icons pinned to task manager have huge tooltip
https://bugs.kde.org/show_bug.cgi?id=380432 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC||petr.ne...@gmail.com Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 391535] New: Inactive menu items have same color as active items
https://bugs.kde.org/show_bug.cgi?id=391535 Bug ID: 391535 Summary: Inactive menu items have same color as active items Product: QtCurve Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk2 Assignee: yyc1...@gmail.com Reporter: petr.ne...@gmail.com CC: h...@kde.org Target Milestone: --- Created attachment 111248 --> https://bugs.kde.org/attachment.cgi?id=111248=edit inactive-menu-items Inactive / disable menu items do have the same color as active items. If you take a look at the image "inactive-menu-items" items Copy/Cut/Paste are disabled but they the same color as active / enabled items. Is it a bug or can it be set somewhere? Manjaro KDE, Plasma 5.12.2, Frameworks 5.43, Qt, 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 391403] New: KSysGuard does not remember columns setup
https://bugs.kde.org/show_bug.cgi?id=391403 Bug ID: 391403 Summary: KSysGuard does not remember columns setup Product: ksysguard Version: 5.12.2 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- Created attachment 91 --> https://bugs.kde.org/attachment.cgi?id=91=edit ksysguard-default-setup I updated packages on Manjaro to https://forum.manjaro.org/t/stable-update-2018-02-25-kernels-plasma-mesa-systemd-qt5-browsers/41190 and since that time when I start KSysGuard (it does not matter whether from plasmoid or manually) it does not remember my setup of columns (widths, sorting, visible columns). I tried to delete config files but it did not help. Any idea? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390885] New: Crash after changes in System Tray Settings
https://bugs.kde.org/show_bug.cgi?id=390885 Bug ID: 390885 Summary: Crash after changes in System Tray Settings Product: plasmashell Version: 5.12.1 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I have enabled "Always show all entries" and pressed Apply... Application: plasmashell (5.12.1) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.14.20-2-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe4bd12d800 (LWP 1022))] Thread 28 (Thread 0x7fe37679f700 (LWP 19297)): #0 0x7fe4b0ec4761 in g_private_get () at /usr/lib/libglib-2.0.so.0 #1 0x7fe4b0ea6791 in g_thread_self () at /usr/lib/libglib-2.0.so.0 #2 0x7fe4b0e7e0ff in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe4b6f2fd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe4b6ed1e9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe4b6ce178e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fe4b9eeea19 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fe4b6ce6b2d in () at /usr/lib/libQt5Core.so.5 #8 0x7fe4b5e9b08c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fe4b65eee7f in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7fe3777fe700 (LWP 32756)): #0 0x7fe4b0ec4b79 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fe4b0e7dfb6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe4b0e7e10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe4b6f2fd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe4b6ed1e9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe4b6ce178e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fe4b6ce6b2d in () at /usr/lib/libQt5Core.so.5 #7 0x7fe4b5e9b08c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe4b65eee7f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7fe377fff700 (LWP 31952)): #0 0x7fe4b5ea13bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe4b6ce800c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe4008ef42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fe4008f4479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fe4008ee924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fe4008f44d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fe4008ee924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fe4008f44d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fe4008ee924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fe4008f1c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fe4b6ce6b2d in () at /usr/lib/libQt5Core.so.5 #11 0x7fe4b5e9b08c in start_thread () at /usr/lib/libpthread.so.0 #12 0x7fe4b65eee7f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fe394ff9700 (LWP 31951)): #0 0x7fe4b5ea13bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe4b6ce800c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe4008ef42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fe4008f4479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fe4008ee924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fe4008f44d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fe4008ee924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fe4008f44d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fe4008ee924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fe4008f44d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fe4008ee924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fe4008f44d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fe4008ee924 in
[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions
https://bugs.kde.org/show_bug.cgi?id=381515 --- Comment #23 from Petr Nehez <petr.ne...@gmail.com> --- I have an update on this - since the time I switched to Manjaro KDE this is not the issue anymore. So I would say there must be an issue in KScreen on Kubuntu while it had a problem to identify the monitor after resume. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #13 from Petr Nehez <petr.ne...@gmail.com> --- (In reply to Aleksey Kontsevich from comment #12) > No effect at all! If you restarted Plasma with no effect then I am out of ideas... I am not KDE expert, just an user. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #11 from Petr Nehez <petr.ne...@gmail.com> --- (In reply to Aleksey Kontsevich from comment #10) > > I think it depends also on your screen resolution, mine is 1920x1080. > Mine is same, I have 42" monitor (52 DPI). Hmm, you have quite big monitor so I guess your gridUnit is lower than mine, but this is just my guess. Try to put a real value for 'minimumHeight' - at least to see if it works (e.g. 900). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #9 from Petr Nehez <petr.ne...@gmail.com> --- >> For me to set "Layout.minimumHeight: units.gridUnit * 42" is enough. > Has no effect to me in KDE 5.11 (17.12) I think it depends also on your screen resolution, mine is 1920x1080. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #7 from Petr Nehez <petr.ne...@gmail.com> --- For those who want to set a minimum height, open /usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/FullRepresentation.qml and update it. For me to set "Layout.minimumHeight: units.gridUnit * 42" is enough. But again - it would be really helpful if KDE would remember the size across sessions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380931] Indicator of multiple windows gets hidden
https://bugs.kde.org/show_bug.cgi?id=380931 --- Comment #18 from Petr Nehez <petr.ne...@gmail.com> --- I am now on Plasma 5.11.4 and I am not able to reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380931] Indicator of multiple windows gets hidden
https://bugs.kde.org/show_bug.cgi?id=380931 --- Comment #16 from Petr Nehez <petr.ne...@gmail.com> --- I don't use this plasmoid anymore while I have seen it too complicated for daily usage but I tried to replicate it with the steps you described and I was unable to replicate the issue... What I have seen is I added a new panel with 1 plasmoid (icons-only TM) while Chrome (no audio) and Spotify was running and playing and there was no audio indicator on Spotify's icon. When I started to play audio in Chrome, audio indicators appeared on both Chrome and Spotify icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386381] Plasma utilizing 100% CPU (1 core) after upgrade to 17.10
https://bugs.kde.org/show_bug.cgi?id=386381 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Summary|Plasma frozen after upgrade |Plasma utilizing 100% CPU |to 17.10|(1 core) after upgrade to ||17.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386381] Plasma frozen after upgrade to 17.10
https://bugs.kde.org/show_bug.cgi?id=386381 --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- OK, I understand it is not specifically Plasma's code, but would it be possible to disable all plasmoids while doing an upgrade? This would avoid such problems. For less experienced users this would mean full reinstall only... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386381] Plasma frozen after upgrade to 17.10
https://bugs.kde.org/show_bug.cgi?id=386381 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID |--- --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- OK, I have written it in a bad way. Plasmashell was utilizing 1 core on 100% and doing a lot of IO writes. That line was the only thing I have found out by executing * "lsof | grep plasmashe" * "sudo strace -p -v" and checking what was being written. And that line was the only thing that was being written. When I deleted the folder "/home/petr/.local/share/plasma/plasmoids/com.github.zren.batterytime/" and restarted system, plasmashell started correctly. I deleted the folder after logging in and pressing of Ctrl+Alt+F1 and logging in again in terminal. Now I have no idea how you want from me to debug it after fixing of the issue. My computers was not usable after upgrade until I deleted that folder. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386381] New: Plasma frozen after upgrade to 17.10
https://bugs.kde.org/show_bug.cgi?id=386381 Bug ID: 386381 Summary: Plasma frozen after upgrade to 17.10 Product: plasmashell Version: 5.10.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 After uprgading Kubuntu 17.04 with plasmoid BatteryTime, Plasmashell gets frozen after logging in. It turned out that there is a problem with this plasmoid, and when I renamed the folder and restarted system, everything got fine. This is error from .xsession-errors: unknown: file:///home/petr/.local/share/plasma/plasmoids/com.github.zren.batterytime/contents/ui/main.qml:252:4: QML Text: Binding loop detected for property "height" -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385602] Add option to show volume level in OSD
https://bugs.kde.org/show_bug.cgi?id=385602 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- Yes, the textual form would be really appreciated. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385602] New: Add option to show volume level in OSD
https://bugs.kde.org/show_bug.cgi?id=385602 Bug ID: 385602 Summary: Add option to show volume level in OSD Product: plasma-pa Version: 5.10.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 108283 --> https://bugs.kde.org/attachment.cgi?id=108283=edit volume-osd I would like to see the current volume level in OSD because I often use my headset in noisy environment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385505] Plasma crashed when starting Muon
https://bugs.kde.org/show_bug.cgi?id=385505 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- And how do you want to generate them? If there is a way how to do it ad-hoc now, I can do it... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385505] New: Plasma crashed when starting Muon
https://bugs.kde.org/show_bug.cgi?id=385505 Bug ID: 385505 Summary: Plasma crashed when starting Muon Product: plasmashell Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.7.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.4-041304-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: I resumed laptop and in a minute I started Muon (pressed Meta key, typed "muo" and pressed Enter) -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f31e67b1280 (LWP 1701))] Thread 28 (Thread 0x7ef09d15b700 (LWP 14960)): #0 0x7f31e0390d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f31dafd7576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31dafd768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31e0cb30bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f31e0c5cbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f31e0a8af83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f31e394fdf5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f31e0a8fc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31df9336da in start_thread (arg=0x7ef09d15b700) at pthread_create.c:456 #9 0x7f31e039cd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 27 (Thread 0x7f30bef26700 (LWP 5742)): #0 0x7f31e0390d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f31dafd7576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31dafd768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31e0cb30bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f31e0c5cbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f31e0a8af83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f31e0a8fc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f31df9336da in start_thread (arg=0x7f30bef26700) at pthread_create.c:456 #8 0x7f31e039cd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 26 (Thread 0x7f30bcbab700 (LWP 5380)): #0 0x7f31e66b6fc5 in __GI___tls_get_addr (ti=0x7f31e10a7660) at dl-tls.c:834 #1 0x7f31e0a8eac6 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f31e0cb280a in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f31dafd6a6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f31dafd749b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f31dafd768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f31e0cb30bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f31e0c5cbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31e0a8af83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f31e394fdf5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f31e0a8fc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f31df9336da in start_thread (arg=0x7f30bcbab700) at pthread_create.c:456 #12 0x7f31e039cd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 25 (Thread 0x7ef09f7ff700 (LWP 5341)): #0 0x7f31e038c8ad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f31db01bb30 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31dafd7042 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31dafd7514 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f31dafd768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f31e0cb30bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f31e0c5cbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f31e0a8af83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31e394fdf5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f31e0a8fc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f31df9336da in
[plasmashell] [Bug 382340] Notifications are often as 1px vertical line
https://bugs.kde.org/show_bug.cgi?id=382340 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #28 from Petr Nehez <petr.ne...@gmail.com> --- I can confirm this issue is not happening anymore in 5.38. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384610] Screen is not locked when a lid is closed and VirtualBox is in the foreground
https://bugs.kde.org/show_bug.cgi?id=384610 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- OK, thanks for the info. Then I will have to live with it for some time until KDE is Wayland - do you know when it would be ready? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384610] Screen is not locked when a lid is closed and VirtualBox is in the foreground
https://bugs.kde.org/show_bug.cgi?id=384610 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- Yes, VirtualBox does hold a grab. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380432] Icons pinned to task manager have huge tooltip
https://bugs.kde.org/show_bug.cgi?id=380432 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC|petr.ne...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380958] Tooltip size too large
https://bugs.kde.org/show_bug.cgi?id=380958 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384610] New: Screen is not locked when a lid is closed and VirtualBox is in the foreground
https://bugs.kde.org/show_bug.cgi?id=384610 Bug ID: 384610 Summary: Screen is not locked when a lid is closed and VirtualBox is in the foreground Product: kscreenlocker Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: petr.ne...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- I am running Kubuntu 17.04 with 5.10.5 and 5.37 and when a VirtualBox guest with Windows 10 is in the foreground the screen is not locked when I close my lid and then reopen it. In this case I do not need to enter my password. In other cases the screen is locked when I reopen the lid. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382452] Empty input field shorter in height by 1px
https://bugs.kde.org/show_bug.cgi?id=382452 --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- Could anybody update /kscreenlocker/greeter/fallbacktheme/Greeter.qml and set a (minimal?) height of the TextField with id=password? I know this is stupid issue but it does not look well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382340] Notifications are often as 1px vertical line
https://bugs.kde.org/show_bug.cgi?id=382340 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #26 from Petr Nehez <petr.ne...@gmail.com> --- I do not know if it matters but my vertical line has black color. -- You are receiving this mail because: You are watching all bug changes.
