[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink
https://bugs.kde.org/show_bug.cgi?id=456310 Radek Novacek changed: What|Removed |Added CC||ra...@centrum.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471562] Crash in KWin::DrmGammaRamp constructor
https://bugs.kde.org/show_bug.cgi?id=471562 --- Comment #16 from Radek Novacek --- I have applied that patch and it's also solid for me. No more crashes observed. Thanks everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471562] Crash in KWin::DrmGammaRamp constructor
https://bugs.kde.org/show_bug.cgi?id=471562 --- Comment #7 from Radek Novacek --- Should have said `kwin-5.27.7-2.fc37.x86_64` on Fedora 37 running Wayland session. KDE from this COPR repo: https://copr.fedorainfracloud.org/coprs/zawertun/kde/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471562] Crash in KWin::DrmGammaRamp constructor
https://bugs.kde.org/show_bug.cgi?id=471562 --- Comment #6 from Radek Novacek --- Same thing happens to me (not 100% times, more like 25%) - laptop with internal screen off, external screen connected through USB-C <-> DP cable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471562] Crash in KWin::DrmGammaRamp constructor
https://bugs.kde.org/show_bug.cgi?id=471562 Radek Novacek changed: What|Removed |Added CC||ra...@centrum.cz -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 --- Comment #9 from Radek Hušek --- The attached patch to kdepim-runtime which disables contacts sync resolves the issue with calendar sync for me. Of course it is more of a band aid than real solution which is to port the contacts to the new api. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Radek Hušek changed: What|Removed |Added CC||hu...@iuuk.mff.cuni.cz --- Comment #8 from Radek Hušek --- Created attachment 145926 --> https://bugs.kde.org/attachment.cgi?id=145926=edit Patch to disable sync of google contacts -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447280] Cut/paste under wayland is hit and miss
https://bugs.kde.org/show_bug.cgi?id=447280 Radek changed: What|Removed |Added CC||rsko...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 Radek changed: What|Removed |Added CC||rsko...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432483] New: dolphin crashed ...
https://bugs.kde.org/show_bug.cgi?id=432483 Bug ID: 432483 Summary: dolphin crashed ... Product: dolphin Version: 20.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ra...@pandan.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.1) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.4.0-65-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: ... when i wanted to look at the contents of an encrypted USB flah-drive i had just encrypted with "VeraCrypt" -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [New LWP 8148] [New LWP 8152] [New LWP 8153] [New LWP 8154] [New LWP 8155] [New LWP 8156] [New LWP 8159] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7e57266aff in __GI___poll (fds=0x7ffdd065f1e8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f7e503088c0 (LWP 8145))] Thread 8 (Thread 0x7f7e39f49700 (LWP 8159)): #0 0x7f7e57266aff in __GI___poll (fds=0x7f7e14004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7e52d0c18e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7e52d0c2c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7e54f9efbb in QEventDispatcherGlib::processEvents (this=0x7f7e14000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7e54f431ab in QEventLoop::exec (this=this@entry=0x7f7e39f48ce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f7e54d5da12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f7e54d5ebac in QThreadPrivate::start (arg=0x560a2da5a680) at thread/qthread_unix.cpp:329 #7 0x7f7e536db609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f7e57273293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f7e4489f700 (LWP 8156)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x560a2da7f168) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560a2da7f118, cond=0x560a2da7f140) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x560a2da7f140, mutex=0x560a2da7f118) at pthread_cond_wait.c:638 #3 0x7f7e46d5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f7e46d5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f7e536db609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7e57273293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f7e450a0700 (LWP 8155)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x560a2da7f168) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560a2da7f118, cond=0x560a2da7f140) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x560a2da7f140, mutex=0x560a2da7f118) at pthread_cond_wait.c:638 #3 0x7f7e46d5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f7e46d5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f7e536db609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7e57273293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f7e458a1700 (LWP 8154)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x560a2da7f168) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560a2da7f118, cond=0x560a2da7f140) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x560a2da7f140, mutex=0x560a2da7f118) at pthread_cond_wait.c:638 #3 0x7f7e46d5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f7e46d5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f7e536db609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7e57273293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f7e460a2700 (LWP 8153)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x560a2da7f168) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560a2da7f118, cond=0x560a2da7f140) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x560a2da7f140, mutex=0x560a2da7f118) at pthread_cond_wait.c:638 #3 0x7f7e46d5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f7e46d5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5
[krusader] [Bug 431173] New: Entering directory containing NFS share tries to connect six times before time out
https://bugs.kde.org/show_bug.cgi?id=431173
Bug ID: 431173
Summary: Entering directory containing NFS share tries to
connect six times before time out
Product: krusader
Version: 2.7.2
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: krusader-bugs-n...@kde.org
Reporter: radek.machu...@gmail.com
CC: krusader-bugs-n...@kde.org
Target Milestone: ---
SUMMARY:
When entering directory containing NFS share (that is not accessible at the
moment) automounted with systemd, Krusader tries to 'access' that share six
times instead of just once leading to six time longer dead time (due to six
timeouts). When entering the same directory with shell or Dolphin, for
instance, it tries just once (as excepted).
STEPS TO REPRODUCE
1. Create NFS share in /etc/fstab (but make sure it can not be accessed) like:
nfs_server:/remote/path/nfs /path/to/mountpoint/nfs nfs
rw,user,noauto,async,noatime,_netdev,x-systemd.automount,x-systemd.mount-timeout=10s,retry=1,x-systemd.idle-timeout=10min,x-systemd.requires=network-online.target
0 0
2. Monitor the process either with dmesg or journalctl
3. Run the krusader and try to open directory containing the nfs share
mountpoint ('/path/to/mountpoint' in this case)
OBSERVED RESULT
(in this case the mountpoint is /home/rad/_mount/odroid_nfs)
# dmesg -w
[54160.295668] NFS4: Couldn't follow remote path
[54170.545401] NFS4: Couldn't follow remote path
[54180.795579] NFS4: Couldn't follow remote path
[54191.044696] NFS4: Couldn't follow remote path
[54201.294051] NFS4: Couldn't follow remote path
[54211.543779] NFS4: Couldn't follow remote path
# journalctl -f
led 05 11:12:07 book systemd[1]: home-rad-_mount-odroid_nfs.automount: Got
automount request for /home/rad/_mount/odroid_nfs, triggered by 27714
(krusader)
led 05 11:12:07 book systemd[1]: Mounting /home/rad/_mount/odroid_nfs...
led 05 11:12:17 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mounting
timed out. Terminating.
led 05 11:12:17 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mount
process exited, code=killed, status=15/TERM
led 05 11:12:17 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Failed with
result 'timeout'.
led 05 11:12:17 book kernel: NFS4: Couldn't follow remote path
led 05 11:12:17 book systemd[1]: Failed to mount /home/rad/_mount/odroid_nfs.
led 05 11:12:17 book systemd[1]: home-rad-_mount-odroid_nfs.automount: Got
automount request for /home/rad/_mount/odroid_nfs, triggered by 27714
(krusader)
led 05 11:12:17 book systemd[1]: Mounting /home/rad/_mount/odroid_nfs...
led 05 11:12:27 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mounting
timed out. Terminating.
led 05 11:12:27 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mount
process exited, code=killed, status=15/TERM
led 05 11:12:27 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Failed with
result 'timeout'.
led 05 11:12:27 book kernel: NFS4: Couldn't follow remote path
led 05 11:12:27 book systemd[1]: Failed to mount /home/rad/_mount/odroid_nfs.
led 05 11:12:27 book systemd[1]: home-rad-_mount-odroid_nfs.automount: Got
automount request for /home/rad/_mount/odroid_nfs, triggered by 27714
(krusader)
led 05 11:12:28 book systemd[1]: Mounting /home/rad/_mount/odroid_nfs...
led 05 11:12:38 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mounting
timed out. Terminating.
led 05 11:12:38 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mount
process exited, code=killed, status=15/TERM
led 05 11:12:38 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Failed with
result 'timeout'.
led 05 11:12:38 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Unit process
28210 (mount.nfs) remains running after unit stopped.
led 05 11:12:38 book kernel: NFS4: Couldn't follow remote path
led 05 11:12:38 book systemd[1]: Failed to mount /home/rad/_mount/odroid_nfs.
led 05 11:12:38 book systemd[1]: home-rad-_mount-odroid_nfs.automount: Got
automount request for /home/rad/_mount/odroid_nfs, triggered by 27714
(krusader)
led 05 11:12:38 book systemd[1]: Mounting /home/rad/_mount/odroid_nfs...
led 05 11:12:48 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mounting
timed out. Terminating.
led 05 11:12:48 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Mount
process exited, code=killed, status=15/TERM
led 05 11:12:48 book systemd[1]: home-rad-_mount-odroid_nfs.mount: Failed with
result 'timeout'.
led 05 11:12:48 book kernel: NFS4: Couldn't follow remote path
led 05 11:12:48 book systemd[1]: Failed to mount /home/rad/_mount/odroid_nfs.
led 05 11:12:48 book systemd[1]: home-rad-_mount-odroid_nfs.automount: Got
automount request for /home/rad/_mount/odroid_nfs, triggered by 27714
(krusader)
led 05 11:12:48 book systemd[1]: Mounting /home/rad/_mount/odroid_nfs...
led 05 11:12:58 book systemd[1]:
[plasmashell] [Bug 394236] logout confirmation dialog is unreadable with certain light backgrounds
https://bugs.kde.org/show_bug.cgi?id=394236 --- Comment #9 from Radek Hušek <hu...@iuuk.mff.cuni.cz> --- Yes the background seems to be transparent. I didn't know it was possible / supported. Which desktop theme are you using? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394236] logout confirmation dialog is unreadable with certain light backgrounds
https://bugs.kde.org/show_bug.cgi?id=394236 --- Comment #8 from Radek Hušek <hu...@iuuk.mff.cuni.cz> --- That's the thing, leave options are not always white but their color is foreground color of complementary color group... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394236] logout confirmation dialog is unreadable with certain light backgrounds
https://bugs.kde.org/show_bug.cgi?id=394236 --- Comment #4 from Radek Hušek <hu...@iuuk.mff.cuni.cz> --- The color which decides whether make the background darker or lighter is the button background -- the color of OK button on the screenshot -- which is some kind of light blue so it is considered light background since the mentioned patch. IMHO even the buttons are hard to read which seems to be the root of the problem to me. Or is this color combination intentional? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386588] Change volume on scroll.
https://bugs.kde.org/show_bug.cgi?id=386588 Radek Hušek <hu...@iuuk.mff.cuni.cz> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-workspace/bd5619e0155a4 ||977bb891c1f01218847cab2ef1b Status|CONFIRMED |RESOLVED --- Comment #2 from Radek Hušek <hu...@iuuk.mff.cuni.cz> --- Git commit bd5619e0155a4977bb891c1f01218847cab2ef1b by Radek Hušek. Committed on 03/04/2018 at 18:24. Pushed by husek into branch 'master'. [Media controller] Add simple volume control Summary: Add simple volume control to Media Controller applet. Volume can by changed by: - mouse wheel on applet icon (3 % step), and - new global shortcuts (5 % step, unbound by default). There is no mute support currently (mpris interface does not have a mute method so we would have to keep track of old volume). Test Plan: Tested in daily use with Cantata and SMPlayer. There is no UI change. Reviewers: #plasma, broulik Reviewed By: #plasma, broulik Subscribers: broulik, nicolasfella, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D11021 M +9-0applets/mediacontroller/contents/ui/main.qml M +8-0dataengines/mpris2/mpris2.operations M +22 -0dataengines/mpris2/multiplexedservice.cpp M +20 -0dataengines/mpris2/playeractionjob.cpp M +26 -0dataengines/mpris2/playercontrol.cpp M +2-0dataengines/mpris2/playercontrol.h https://commits.kde.org/plasma-workspace/bd5619e0155a4977bb891c1f01218847cab2ef1b -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382264] Black buttons unreadable on the black logout screen
https://bugs.kde.org/show_bug.cgi?id=382264 Radek Hušek <hu...@iuuk.mff.cuni.cz> changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-workspace/af2a74341d5f1 |sma-workspace/fc0033ede6b0b |0c1dc1ba66538357c94d8e6a6e1 |b88d737752b8db359194cb4e41f --- Comment #11 from Radek Hušek <hu...@iuuk.mff.cuni.cz> --- Git commit fc0033ede6b0bb88d737752b8db359194cb4e41f by Radek Hušek. Committed on 30/03/2018 at 17:18. Pushed by husek into branch 'master'. KDE logout screen background color fix Summary: The patch D5036 did calculate wrong whether the background color is light or not which resulted in always black background. The problem was that color reported by plasma is in range 0.0 -- 1.0 not 0 -- 255. Now the background is black only when button background color is dark and otherwise it respects button background color. Reviewers: mart, #plasma Reviewed By: mart, #plasma Subscribers: fredrik, ngraham, abetts, broulik, mvourlakos, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D11262 M +3-30 lookandfeel/contents/logout/Logout.qml https://commits.kde.org/plasma-workspace/fc0033ede6b0bb88d737752b8db359194cb4e41f -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382264] Black buttons unreadable on the black logout screen
https://bugs.kde.org/show_bug.cgi?id=382264 Radek Hušek <hu...@iuuk.mff.cuni.cz> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-workspace/af2a74341d5f1 ||0c1dc1ba66538357c94d8e6a6e1 --- Comment #10 from Radek Hušek <hu...@iuuk.mff.cuni.cz> --- Git commit af2a74341d5f10c1dc1ba66538357c94d8e6a6e1 by Radek Hušek. Committed on 30/03/2018 at 13:23. Pushed by husek into branch 'master'. KDE logout screen background color fix Summary: The patch D5036 did calculate wrong whether the background color is light or not which resulted in always black background. The problem was that color reported by plasma is in range 0.0 -- 1.0 not 0 -- 255. Now the background is black only when button background color is dark and otherwise it respects button background color. Reviewers: mart, #plasma Reviewed By: mart, #plasma Subscribers: fredrik, ngraham, abetts, broulik, mvourlakos, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D11262 M +3-30 lookandfeel/contents/logout/Logout.qml https://commits.kde.org/plasma-workspace/af2a74341d5f10c1dc1ba66538357c94d8e6a6e1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362307] Some apps do not ignore wheel event when Meta+Wheel is used to raise/lower the window
https://bugs.kde.org/show_bug.cgi?id=362307 Radek Hušek <hu...@iuuk.mff.cuni.cz> changed: What|Removed |Added CC||hu...@iuuk.mff.cuni.cz --- Comment #5 from Radek Hušek <hu...@iuuk.mff.cuni.cz> --- (In reply to Martin Flöser from comment #3) > I assume that you see this with all Qt 5 applications? E.g. also kwrite/kate? > > My idea is that this is related to Qt 5 using Xinput 2 for scrolling, thus > KWin does not intercept the events properly anymore. I can confirm that this bug is caused by Qt5 using XInput2. Disabling xinput2 support in Qt fixes it. (Also on wayland everything works fine.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kunitconversion] [Bug 378967] Fuel consumption conversion incorrect
https://bugs.kde.org/show_bug.cgi?id=378967 --- Comment #1 from Radek Novacek <ra...@centrum.cz> --- Created attachment 105098 --> https://bugs.kde.org/attachment.cgi?id=105098=edit Screenshot from KRunner -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kunitconversion] [Bug 378967] New: Fuel consumption conversion incorrect
https://bugs.kde.org/show_bug.cgi?id=378967 Bug ID: 378967 Summary: Fuel consumption conversion incorrect Product: frameworks-kunitconversion Version: 5.32.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jl...@kde.org Reporter: ra...@centrum.cz CC: kdelibs-b...@kde.org Target Milestone: --- Fuel consumption unit conversion doesn't work for some unit combination. Discovered using KRunner Unit Converter plugin. Expected values: 100 mpg (US) = 2.35215 l/100km 10 l/100 km = 23.5215 mpg (US) 20 kmpl = 5 l/100km Actual values: 100 mpg (US) = 0.4251700680272109 l/100km 10 l/100 km = 2351.5 mpg (US) 20 kmpl = 0.2 l/100km Given that kmpl to mpg conversion is correct (20kmpl = 47.04mpg) I guess that just l/100km is incorrect. I've used Google Unit Conversion for checking the values (like "https://www.google.com/search?q=100 mpg to l/100km") -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368840] Show tasks from current screen uses wrong screen
https://bugs.kde.org/show_bug.cgi?id=368840 --- Comment #2 from Radek Novacek <rnova...@redhat.com> --- Also please note that both external displays are the same - could it affect some detection? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368840] Show tasks from current screen uses wrong screen
https://bugs.kde.org/show_bug.cgi?id=368840 --- Comment #1 from Radek Novacek <rnova...@redhat.com> --- Created attachment 101095 --> https://bugs.kde.org/attachment.cgi?id=101095=edit My screen layout -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368840] New: Show tasks from current screen uses wrong screen
https://bugs.kde.org/show_bug.cgi?id=368840 Bug ID: 368840 Summary: Show tasks from current screen uses wrong screen Product: plasmashell Version: 5.7.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: rnova...@redhat.com CC: plasma-b...@kde.org I have three displays (laptop and two external displays), both external displays has plasma panel on the bottom edge and I want to see only windows from given display (screen) to be shown in the panel. But if I use the checkbox "Show only tasks from current screen", the tasks get filtered incorrectly. On the left screen I see only windows from right screen and on the right screen I see only windows from left screen. Reproducible: Always Steps to Reproduce: 1. Use two (external) displays 2. Add panels with task manager on both of them 3. Open windows on both of them 4. Check the "Show only tasks from current screen" option in task manager configuration Actual Results: Task manager on the left screen shows windows from right screen and vice versa. Expected Results: Task manager only shows windows from the screen it's on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361247] Plasma crash when screen turn on
https://bugs.kde.org/show_bug.cgi?id=361247 Radek <rdebie...@yahoo.pl> changed: What|Removed |Added CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361247] Plasma crash when screen turn on
https://bugs.kde.org/show_bug.cgi?id=361247 --- Comment #2 from Radek <rdebie...@yahoo.pl> --- Screen is Philips HDMI TV set. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361247] Plasma crash when screen turn on
https://bugs.kde.org/show_bug.cgi?id=361247 Radek <rdebie...@yahoo.pl> changed: What|Removed |Added CC||rdebie...@yahoo.pl --- Comment #1 from Radek <rdebie...@yahoo.pl> --- (In reply to Radek from comment #0) > Application: plasmashell (5.6.1) > > Qt Version: 5.6.0 > Frameworks Version: 5.20.0 > Operating System: Linux 4.1.15-8-default x86_64 > Distribution: "openSUSE Leap 42.1 (x86_64)" > > -- Information about the crash: > - What I was doing when the application crashed: > 1. Turn screen off. > 2. Turn screen on. > plasmashell crash always > > The crash can be reproduced every time. > > -- Backtrace: > Application: Plazma (plasmashell), signal: Segmentation fault > Using host libthread_db library "/lib64/libthread_db.so.1". > [Current thread is 1 (Thread 0x7f62bd1cb800 (LWP 1973))] > > Thread 11 (Thread 0x7f62a5f69700 (LWP 1975)): > #0 0x7f62b66dabbd in poll () at /lib64/libc.so.6 > #1 0x7f62bb609422 in () at /usr/lib64/libxcb.so.1 > #2 0x7f62bb60b00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 > #3 0x7f62a88ef979 in () at /usr/lib64/libQt5XcbQpa.so.5 > #4 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 > #5 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 > #6 0x7f62b66e2fed in clone () at /lib64/libc.so.6 > > Thread 10 (Thread 0x7f629fdf5700 (LWP 1976)): > #0 0x7f62b66ef622 in __libc_disable_asynccancel () at /lib64/libc.so.6 > #1 0x7f62b66d6c99 in read () at /lib64/libc.so.6 > #2 0x7f62ae880073 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 > #3 0x7f62b2e05b60 in () at /usr/lib64/libglib-2.0.so.0 > #4 0x7f62b2dc4999 in g_main_context_check () at > /usr/lib64/libglib-2.0.so.0 > #5 0x7f62b2dc4df8 in () at /usr/lib64/libglib-2.0.so.0 > #6 0x7f62b2dc4f7c in g_main_context_iteration () at > /usr/lib64/libglib-2.0.so.0 > #7 0x7f62b6fe83fb in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib64/libQt5Core.so.5 > #8 0x7f62b6f9604b in > QEventLoop::exec(QFlags) () at > /usr/lib64/libQt5Core.so.5 > #9 0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 > #10 0x7f62b7d53095 in () at /usr/lib64/libQt5DBus.so.5 > #11 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 > #12 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 > #13 0x7f62b66e2fed in clone () at /lib64/libc.so.6 > > Thread 9 (Thread 0x7f629e5b7700 (LWP 2000)): > #0 0x7f62b66d6c8d in read () at /lib64/libc.so.6 > #1 0x7f62ae880073 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 > #2 0x7f62b2e05b60 in () at /usr/lib64/libglib-2.0.so.0 > #3 0x7f62b2dc4999 in g_main_context_check () at > /usr/lib64/libglib-2.0.so.0 > #4 0x7f62b2dc4df8 in () at /usr/lib64/libglib-2.0.so.0 > #5 0x7f62b2dc4f7c in g_main_context_iteration () at > /usr/lib64/libglib-2.0.so.0 > #6 0x7f62b6fe83fb in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib64/libQt5Core.so.5 > #7 0x7f62b6f9604b in > QEventLoop::exec(QFlags) () at > /usr/lib64/libQt5Core.so.5 > #8 0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 > #9 0x7f62ba0cd4d8 in () at /usr/lib64/libQt5Qml.so.5 > #10 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 > #11 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 > #12 0x7f62b66e2fed in clone () at /lib64/libc.so.6 > > Thread 8 (Thread 0x7f628dc29700 (LWP 2006)): > #0 0x7f62b2dea400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 > #1 0x7f62b2dc4f6d in g_main_context_iteration () at > /usr/lib64/libglib-2.0.so.0 > #2 0x7f62b6fe83fb in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib64/libQt5Core.so.5 > #3 0x7f62b6f9604b in > QEventLoop::exec(QFlags) () at > /usr/lib64/libQt5Core.so.5 > #4 0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 > #5 0x7f62ba0cd4d8 in () at /usr/lib64/libQt5Qml.so.5 > #6 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 > #7 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 > #8 0x7f62b66e2fed in clone () at /lib64/libc.so.6 > > Thread 7 (Thread 0x7f6287fff700 (LWP 2008)): > #0 0x7f62b66dabbd in poll () at /lib64/libc.so.6 > #1 0x7f62b2dc4e64 in () at /usr/lib64/libglib-2.0.so.0 > #2 0x7f62b2dc4f7c in g_main_context_iteration () at > /usr/lib64/libglib-2.0.so.0 > #3 0x7f62b6fe83fb in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib64/libQt5Core.so.5 > #4 0x7f62b6f9
[plasmashell] [Bug 361247] New: Plasma crash when screen turn on
https://bugs.kde.org/show_bug.cgi?id=361247 Bug ID: 361247 Summary: Plasma crash when screen turn on Product: plasmashell Version: 5.6.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rdebie...@yahoo.pl CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.6.1) Qt Version: 5.6.0 Frameworks Version: 5.20.0 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: 1. Turn screen off. 2. Turn screen on. plasmashell crash always The crash can be reproduced every time. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f62bd1cb800 (LWP 1973))] Thread 11 (Thread 0x7f62a5f69700 (LWP 1975)): #0 0x7f62b66dabbd in poll () at /lib64/libc.so.6 #1 0x7f62bb609422 in () at /usr/lib64/libxcb.so.1 #2 0x7f62bb60b00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f62a88ef979 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f62b66e2fed in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f629fdf5700 (LWP 1976)): #0 0x7f62b66ef622 in __libc_disable_asynccancel () at /lib64/libc.so.6 #1 0x7f62b66d6c99 in read () at /lib64/libc.so.6 #2 0x7f62ae880073 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 #3 0x7f62b2e05b60 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f62b2dc4999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #5 0x7f62b2dc4df8 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7f62b2dc4f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #7 0x7f62b6fe83fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f62b6f9604b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #10 0x7f62b7d53095 in () at /usr/lib64/libQt5DBus.so.5 #11 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 #12 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 #13 0x7f62b66e2fed in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f629e5b7700 (LWP 2000)): #0 0x7f62b66d6c8d in read () at /lib64/libc.so.6 #1 0x7f62ae880073 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 #2 0x7f62b2e05b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f62b2dc4999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f62b2dc4df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f62b2dc4f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f62b6fe83fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f62b6f9604b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f62ba0cd4d8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 #11 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f62b66e2fed in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f628dc29700 (LWP 2006)): #0 0x7f62b2dea400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #1 0x7f62b2dc4f6d in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7f62b6fe83fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f62b6f9604b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f62ba0cd4d8 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f62b66e2fed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f6287fff700 (LWP 2008)): #0 0x7f62b66dabbd in poll () at /lib64/libc.so.6 #1 0x7f62b2dc4e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f62b2dc4f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f62b6fe83fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f62b6f9604b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f62ba0cd4d8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f62b6dd7079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f62b66e2fed in clone ()
[kmail2] [Bug 360568] New: Address book unavailable on the composer screen
https://bugs.kde.org/show_bug.cgi?id=360568 Bug ID: 360568 Summary: Address book unavailable on the composer screen Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: radzisz...@gmail.com When I open a composer screen, the only possibility to add a recipient e-mail address it to either start typing the address in the 'To' field, or to pick it from Tools -> Select recipients. Reproducible: Always Steps to Reproduce: 1. File -> New -> New message 2. Composer shows up. You try to select a recipient from your address book, but you can't do it, unless you start typing the address in the 'To' field. Actual Results: No address book visible in the composer window. Expected Results: In Thunderbird and Evolution there is a possibility to display an address book on the left of the composer window. I think such option should be available in KMail, too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351146] Shortcut for pause/next/prev when plasmoid is active
https://bugs.kde.org/show_bug.cgi?id=351146 --- Comment #3 from Radek Janoštík <radek.janos...@gmail.com> --- Thank you,I am looking forward to the new version. -- You are receiving this mail because: You are watching all bug changes.
