[plasmashell] [Bug 382340] Notifications are often as 1px vertical line
https://bugs.kde.org/show_bug.cgi?id=382340 --- Comment #19 from Petr Nehez <petr.ne...@gmail.com> --- Is there anything more we can help on this issue? It is quite annoying while seeing this type of notifications... If there is a logging option I can enable it so that this issue can be analyzed more deeply. -- 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 #11 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106614 --> https://bugs.kde.org/attachment.cgi?id=106614=edit dc__no_indicator_4 -- 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 #9 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106612 --> https://bugs.kde.org/attachment.cgi?id=106612=edit dc__no_indicator_2 -- 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 #8 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106611 --> https://bugs.kde.org/attachment.cgi?id=106611=edit dc__no_indicator_1 -- 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 #10 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106613 --> https://bugs.kde.org/attachment.cgi?id=106613=edit dc__no_indicator_3 -- 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 Version|5.10.0 |5.10.3 -- 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 #12 from Petr Nehez <petr.ne...@gmail.com> --- So it seems that this issue is not related to IconsOnly but right now it is happing for me with the regular Task manager. See the images attached on 14 July 2017 where I had no indicator for Double Commander process and its 3 windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382340] New: Notifications are often as 1px vertical line
https://bugs.kde.org/show_bug.cgi?id=382340 Bug ID: 382340 Summary: Notifications are often as 1px vertical line Product: plasmashell Version: 5.10.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 106620 --> https://bugs.kde.org/attachment.cgi?id=106620=edit vertical_line I have Kubuntu 17.04 with KDE backports and after upgrading framework from 5.35 to 5.36 desktop notifications become as 1px vertical line quite often. The position for notifications is set to top-center. See the attached image "vertical_line". -- 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 --- Comment #5 from Petr Nehez <petr.ne...@gmail.com> --- FYI I am using Ultra Flat Icons (https://store.kde.org/p/1171748/ - my [bug #380958](https://bugs.kde.org/show_bug.cgi?id=380958) ). -- 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 --- Comment #7 from Petr Nehez <petr.ne...@gmail.com> --- OK, I have enabled logging so when I have something to share I will attach it here. -- 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 Petr Nehez <petr.ne...@gmail.com> changed: What|Removed |Added CC||petr.ne...@gmail.com --- Comment #5 from Petr Nehez <petr.ne...@gmail.com> --- This is so annoying, I vote to re-open this issue as an enhancement too. The only fix for me to change the minimum dimensions as described at https://ubuntuforums.org/showthread.php?t=2321781. -- 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 #3 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106699 --> https://bugs.kde.org/attachment.cgi?id=106699=edit fonts My font configuration -- 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 #2 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106698 --> https://bugs.kde.org/attachment.cgi?id=106698=edit filled_input -- 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 #1 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106697 --> https://bugs.kde.org/attachment.cgi?id=106697=edit empty_input -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382452] New: Empty input field shorter in height by 1px
https://bugs.kde.org/show_bug.cgi?id=382452 Bug ID: 382452 Summary: Empty input field shorter in height by 1px Product: kscreenlocker Version: 5.10.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: breeze-theme Assignee: plasma-b...@kde.org Reporter: petr.ne...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- The password input field on the lock screen is growing by 1px when I start to type a password into it - when it is empty it is shorter in the height than if it contains a text. -- 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 --- Comment #6 from Petr Nehez <petr.ne...@gmail.com> --- If there are multiple notifications to be shown at the same time, only the first item is messed up as 1px line, the other notifications are fine (dimensions & position). -- 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 --- Comment #14 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106773 --> https://bugs.kde.org/attachment.cgi?id=106773=edit kscreen-1 And here are the logs and configurations when playing with EIZO monitor. It seems that KScreen has a problem to identify a monitor after disconnecting a different monitor. -- 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 --- Comment #16 from Petr Nehez <petr.ne...@gmail.com> --- Ahh, I forgot to execute this command. I'll do it next week when I am in the office with Dell, currently I am at home with Eizo. -- 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 --- Comment #21 from Petr Nehez <petr.ne...@gmail.com> --- @Simone Gaiarin Nope, I do not use docking station, just laptop's HDMI. And always 1 screen at the time - when a monitor is connected laptop's screen is off. -- 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 --- Comment #16 from Petr Nehez <petr.ne...@gmail.com> --- I have only laptop which is used with 2 different monitors but always exclusively with 1 plugged in and I always have only 1 screen active (while a monitor is plugged in laptop's screen is off). But it seems a fix is on the way... -- 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 --- Comment #17 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106829 --> https://bugs.kde.org/attachment.cgi?id=106829=edit kscreen-2 I performed today a way of connecting Dell in the office and then Eizo at home and the results with "xrandr -q --verbose" are attached "kscreen-2". -- 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|DUPLICATE |--- -- 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 --- Comment #18 from Petr Nehez <petr.ne...@gmail.com> --- @ftumpt Yeah, you are right, I was too fast and have not read bug 381130 carefully. 381130 is a completely different issue, it is about misplaced notifications but this bug is about 1px wide notifications. -- 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 --- Comment #18 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106851 --> https://bugs.kde.org/attachment.cgi?id=106851=edit kscreen-3 And in "kscreen-3" archive there are logs after resuming of my laptop (Eizo 1080p was connected before suspend), connecting Dell 1200p where 1080p was activated and then restarting of the system. -- 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 --- Comment #11 from Petr Nehez <petr.ne...@gmail.com> --- I can confirm that this is not happening anymore. -- 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 --- Comment #10 from Petr Nehez <petr.ne...@gmail.com> --- I can confirm that this is not happening anymore. -- 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 CC||petr.ne...@gmail.com --- Comment #1 from Petr Nehez <petr.ne...@gmail.com> --- This also happened to me few times but when I tried to reproduce it, I was not successful. Due to my main problem in bug 381515 I do have kscreen.log so when it occurs again I will attach my kscreen.log here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380106] KWin crashed after changing audio settings in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=380106 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.
[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions
https://bugs.kde.org/show_bug.cgi?id=381515 --- Comment #8 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106747 --> https://bugs.kde.org/attachment.cgi?id=106747=edit kscreen-0-console -- 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 --- Comment #10 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106749 --> https://bugs.kde.org/attachment.cgi?id=106749=edit kscreen-0-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 --- Comment #9 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106748 --> https://bugs.kde.org/attachment.cgi?id=106748=edit kscreen-0-0 -- 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 --- Comment #11 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106750 --> https://bugs.kde.org/attachment.cgi?id=106750=edit kscreen-0-2 -- 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 --- Comment #13 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106751 --> https://bugs.kde.org/attachment.cgi?id=106751=edit screenshot-0 -- 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 --- Comment #12 from Petr Nehez <petr.ne...@gmail.com> --- See my log and configuration files for this issue: * kscreen-0-0 after resume with no monitor connected, * kscreen-0-1 after resume and connected Dell U2415 (assumes it as Eizo EV2459 with 1920x1080, see also the screenshot), * kscreen-0-2 after restart and connected Dell U2415. I also attached outputs from a command "kscreen-console bug" (file kscreen-0-console). -- 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 #14 from Petr Nehez <petr.ne...@gmail.com> --- Is there anything more I can help with? Enabling of logs, running special command etc. -- 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 --- Comment #5 from Petr Nehez <petr.ne...@gmail.com> --- Is there anybody who can check this issue? -- 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 --- Comment #22 from Petr Nehez <petr.ne...@gmail.com> --- Is here anything else I can do to help you out? This issue is making me crazy... -- 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 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 105977 --> https://bugs.kde.org/attachment.cgi?id=105977=edit screenshot-2 -- 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 --- Comment #1 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 105976 --> https://bugs.kde.org/attachment.cgi?id=105976=edit screenshot-1 -- 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 --- Comment #3 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 105978 --> https://bugs.kde.org/attachment.cgi?id=105978=edit screenshot-3 -- 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 --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 105979 --> https://bugs.kde.org/attachment.cgi?id=105979=edit screenshot-4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380958] New: Tooltip size too large
https://bugs.kde.org/show_bug.cgi?id=380958 Bug ID: 380958 Summary: Tooltip size too large Product: plasmashell Version: 5.10.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 "Ultra-flat-icons" collection used for icons Tooltip is too large when an icon uses vector data. I am working on Kubuntu 17.04 with KDE backports and with 5.9 version it was OK but now the tooltip is horrible. -- 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 --- Comment #5 from Petr Nehez <petr.ne...@gmail.com> --- The problem can be seen on 3 of screenshots, "screenshot-1" is showing that with the icon provided by the app itself the tooltip is fine. -- 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 #6 from Petr Nehez <petr.ne...@gmail.com> --- Unfortunately I have not been to replicate this issue since the time I have reported the issue. It's strange, at that time I could see the problem few times. Could it be that 5.10.1 or 5.10.2 fixed the issue? I will monitor it and if it happens again I will attach a screenshot. -- 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 --- Comment #3 from Petr Nehez <petr.ne...@gmail.com> --- 1 thing I have noticed - after restart of the system there was no primary output set - see screenshots "monitor-1" and "monitor-0". -- 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 --- Comment #4 from Petr Nehez <petr.ne...@gmail.com> --- Could it be related to #340548? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 381515] New: KScreen has problem with multiple monitors with different resolutions
https://bugs.kde.org/show_bug.cgi?id=381515 Bug ID: 381515 Summary: KScreen has problem with multiple monitors with different resolutions Product: KScreen Version: 5.10.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- I have a Dell Precision 3510 laptop which has 1920x1080 screen. I use this laptop with 2 monitors on different places: 1) Dell U2415 with 1920x1200, 2) Eizo EV2450 with 1920x1080. I will describe now my problem (both monitors have been already correctly set long time ago): * I started my laptop and then connected Dell monitor and the resolution on this monitor was correctly set to 1920x1200. * I disconnected Dell monitor and put a laptop into Sleep mode. * Then I resumed the laptop and worked on it without any monitor and after 2 hours I put it into Sleep mode again. * At home I resumed the laptop, plugged Eizo monitor but it has not been correctly detected as Eizo but as Dell as shown on the screenshot "monitor-0". * After restart of the system and plugging of Eizo again this monitor has been correctly detected as Eizo as shown on "monitor-1". These steps do not show the real problem but if we would swap usage of those monitors in the description we would end up with Dell 1920x1200 detected as Eizo but with the resolution set to 1920x1080 and in this case we would have to set it manually to 1920x1200 but this would lead to changing the KScreen's configuration for Eizo and not for Dell. -- 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 --- Comment #1 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106222 --> https://bugs.kde.org/attachment.cgi?id=106222=edit monitor-0 -- 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 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 106223 --> https://bugs.kde.org/attachment.cgi?id=106223=edit monitor-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380106] New: KWin crashed after changing audio settings in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=380106 Bug ID: 380106 Summary: KWin crashed after changing audio settings in VirtualBox Product: kwin Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: petr.ne...@gmail.com Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-21-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: I was changing audio from Pulse to ALSA for a Windows 10 guest and then it crashed. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f79c1bff580 (LWP 8128))] Thread 7 (Thread 0x7f7967819700 (LWP 8140)): #0 0x7f79bad2d510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f79be0582c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f79be058309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f79bad276da in start_thread (arg=0x7f7967819700) at pthread_create.c:456 #4 0x7f79c163317f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7f796cd1b700 (LWP 8139)): #0 0x7f79bad2d8b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f79beccfa86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f79beccb2b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f79beccec98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79bad276da in start_thread (arg=0x7f796cd1b700) at pthread_create.c:456 #5 0x7f79c163317f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f7985542700 (LWP 8137)): #0 0x7f79c1627251 in __GI_ppoll (fds=0x7f798ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f79b251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f79beeefb4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f79bee9c88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79becc9fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f79b9a94df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f79beccec98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79bad276da in start_thread (arg=0x7f7985542700) at pthread_create.c:456 #8 0x7f79c163317f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f799efbd700 (LWP 8136)): #0 0x7f79c1627251 in __GI_ppoll (fds=0x7f798c000ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f79b251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f79beeefb4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f79bee9c88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79becc9fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f79b9a94df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f79beccec98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79bad276da in start_thread (arg=0x7f799efbd700) at pthread_create.c:456 #8 0x7f79c163317f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f799fded700 (LWP 8134)): #0 0x7f79bad2d8b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f79beccfa86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f79beccb2b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f79beccec98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79bad276da in start_thread (arg=0x7f799fded700) at pthread_create.c:456 #5 0x7f79c163317f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f79a83eb700 (LWP 8131)): #0 0x7f79c1627251 in __GI_ppoll (fds=0x7f79a000d5a8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f79b251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f79beeefb4a in QEventDispatcherUNIX::processEvents(QFlags) () at
[kwin] [Bug 380106] KWin crashed after changing audio settings in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=380106 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 380931] Indicator of multiple windows gets hidden
https://bugs.kde.org/show_bug.cgi?id=380931 --- Comment #2 from Petr Nehez <petr.ne...@gmail.com> --- I noticed it several times but I do not know exactly how to reproduce the problem. What I do (usually 2x a day) is to suspend my laptop and then I resume it later. What I remember so far it has happened to me with Thunderbird and with Double Commander in the past as well. Today I opened a reply in Thunderbird and I could not see the indicator eventhough there were 2 windows opened in TB. Then I tried to open another window in Double Commander but there it was working fine, the indicator was present. TB and Double Commander was both running before suspending and resuming the laptop. When I closed TB and reopened it and the opened a reply I could see the indicator again. It seems to me so random so I do not know what to watch... -- 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 #5 from Petr Nehez <petr.ne...@gmail.com> --- Created attachment 105963 --> https://bugs.kde.org/attachment.cgi?id=105963=edit indicator I don't think I have met the same situation as described in #373075, I have had the problem with the indicator so far. My icons do not hide. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380931] New: Indicator of multiple windows gets hidden
https://bugs.kde.org/show_bug.cgi?id=380931 Bug ID: 380931 Summary: Indicator of multiple windows gets hidden Product: plasmashell Version: 5.10.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Usually when I resume a computer some apps do not show an indicator of multiple windows opened (not exatcly the same app always). When I relaunch the specified app then it gets fixed and I can see a white indicator at the bottom of the app's icon. -- 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 #3 from Petr Nehez <petr.ne...@gmail.com> --- Maybe something to consider - I work on Dell Latitude 3510 FHD laptop and on 2 places where each place has a different monitor (1st is with 1920x1080 and 2nd with 1920x1200). And then between these places I work on the laptop itself with connected monitor. -- 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|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.
[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 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.
[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.
[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 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.
[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 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.
[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] 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 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 Resolution|FIXED |WAITINGFORINFO --- Comment #24 from Petr Nehez <petr.ne...@gmail.com> --- I am on 5.10.5 and 5.37 and this issue is still happening on my system. It's just happened for the very first notification after restart of the system. Should this issue be fixed now? -- 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.
[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
[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.
[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.
[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 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 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 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] 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] 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-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 #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 #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 #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 #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 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 #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 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.
[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.
[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.
[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.
[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.
[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 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.
[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 #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 #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.
[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
[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.
