[systemsettings] [Bug 390539] New: Searching crashes Systemsettings
https://bugs.kde.org/show_bug.cgi?id=390539 Bug ID: 390539 Summary: Searching crashes Systemsettings Product: systemsettings Version: 5.12.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dominik.schl...@gmail.com Target Milestone: --- Created attachment 110703 --> https://bugs.kde.org/attachment.cgi?id=110703&action=edit Crash Information I'm not sure if that's a general bug or just specific to my search terms. I'm on a German System if that matters. To reproduce: - open Systemsettings - Search (top left) for "start" - Click on "Applications" und "Personal Information" - directly search for "num" This reproducibly crashes Systemsettings for me. Might be, that searching for something while being in a section that isn't returned on that searches causes the Problem? Crash Information are attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390538] New: Krita 3.3.3 keeps giving me trouble with saving
https://bugs.kde.org/show_bug.cgi?id=390538 Bug ID: 390538 Summary: Krita 3.3.3 keeps giving me trouble with saving Product: krita Version: 3.3.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ever_enduring_the_p...@yahoo.com Target Milestone: --- Created attachment 110702 --> https://bugs.kde.org/attachment.cgi?id=110702&action=edit A screen shot of the error notice. It doesn't matter if it has the same name or not, even if I change the name from the one that it originated from, if I try to save it as a .GIF it won't save. I have attached a screen shot of the error for a recent picture I was trying to save. Please help! I rely on this program to do commissions, as well as my own stuff, and this one was just a simple background removal, so I needed it saved as a .GIF! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390489] Settings options menu show dropdown arrow in the background description
https://bugs.kde.org/show_bug.cgi?id=390489 Delfino changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Delfino --- (In reply to Aleix Pol from comment #1) > This is a bug in your widget style Yes, you are right this is a widget style problem. If a change it to "Breeze" it looks normal, with Fusion or Windows style it breaks. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 291835] KIO very slow when copying from network through smb
https://bugs.kde.org/show_bug.cgi?id=291835 --- Comment #53 from Krzysztof Marczak --- Maybe look for the answers in other software. Gnome-commander also uses SMB and SFTP and uses all possible hardware throughput. Maybe if you look into source code of this application, will be possible to figure out how it should be done. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390537] kwin_x11 crashes while task switching
https://bugs.kde.org/show_bug.cgi?id=390537 --- Comment #2 from tuo...@protonmail.ch --- Terribly sorry, the active visualization was BREEZE, I used the alternative keys and didn't check it properly. Without any vizualisation and only showing active window crashes kwin a lot more rarely, with breeze it's almost sure to crash. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390264] Clicking autocomplete entry crashes application
https://bugs.kde.org/show_bug.cgi?id=390264 Thomas Baumgart changed: What|Removed |Added CC||fmet...@gmail.com --- Comment #2 from Thomas Baumgart --- *** Bug 390530 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390530] KMymoney crash when I select payee into combo by Keyboard
https://bugs.kde.org/show_bug.cgi?id=390530 Thomas Baumgart changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Thomas Baumgart --- And you must have missed, that this is already fixed. Thanks for taking the time to report it anyway. *** This bug has been marked as a duplicate of bug 390264 *** -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 390522] Ekos focuser hardcoded max travel range default
https://bugs.kde.org/show_bug.cgi?id=390522 Jasem Mutlaq changed: What|Removed |Added Version Fixed In||2.9.3 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kst ||ars/7e7636c2c5af66d702f2c74 ||4c233aa33e4e26381 --- Comment #1 from Jasem Mutlaq --- Git commit 7e7636c2c5af66d702f2c744c233aa33e4e26381 by Jasem Mutlaq. Committed on 16/02/2018 at 07:20. Pushed by mutlaqja into branch 'master'. Raise maximum value if saved maximum travel is higher than default maximum value of 50,000 FIXED-IN:2.9.3 M +2-0kstars/ekos/focus/focus.cpp https://commits.kde.org/kstars/7e7636c2c5af66d702f2c744c233aa33e4e26381 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 390107] crash on focus framing loop start
https://bugs.kde.org/show_bug.cgi?id=390107 --- Comment #13 from Jasem Mutlaq --- Can you please check if this issue is fixed? I merged your PR on Github. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390537] kwin_x11 crashes while task switching
https://bugs.kde.org/show_bug.cgi?id=390537 tuo...@protonmail.ch changed: What|Removed |Added CC||tuo...@protonmail.ch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390537] New: kwin_x11 crashes while task switching
https://bugs.kde.org/show_bug.cgi?id=390537 Bug ID: 390537 Summary: kwin_x11 crashes while task switching Product: kwin Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tuo...@protonmail.ch Target Milestone: --- Application: kwin_x11 (5.12.1) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: Kwin crashes often while task switching. It happens at least with Thumbnail visualisation, other visualisations not tested. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa743eed840 (LWP 3867))] Thread 19 (Thread 0x7fa722ae2700 (LWP 4321)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa711936ef8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7fa6ef7fe700 (LWP 4320)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa711936ef8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fa6d6ffd700 (LWP 4059)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa73fb2df77 in () at /usr/lib/libQt5Script.so.5 #2 0x7fa73fb2dfb9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fa6d77fe700 (LWP 4058)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa711936ef8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fa6d7fff700 (LWP 4057)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa711936ef8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fa6eeffd700 (LWP 4034)): #0 0x7fa74388ea76 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa740c59883 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa740c5b01f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa740bffe9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa740a0f78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa73b319a19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fa740a14b2d in () at /usr/lib/libQt5Core.so.5 #7 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fa6e700 (LWP 3953)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa711936ef8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fa704d75700 (LWP 3952)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa711936ef8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa705576700 (LWP 3951)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa711936ef8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa73c84908c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa743898e7f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa705d77700 (LWP 3950)): #0 0x7fa73c84f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa711936fec in () at /u
[valgrind] [Bug 384930] Valgrind fails to compute correctly some code using the GMP library
https://bugs.kde.org/show_bug.cgi?id=384930 --- Comment #19 from Julian Seward --- Fix committed, 6ae2edea014669d8082747f0f268e9404e0fd296. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390526] Add option to "Open groups using 'Present Windows Effect'" in Task Manager
https://bugs.kde.org/show_bug.cgi?id=390526 Omar Plummer changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Omar Plummer --- I've tried Icon-only Task Manager, and I find its use of the Present Windows effect for displaying grouped windows much more useful/usable than the grouped thumbnail popup used by the standard Task Manager. Initially, I expected that I would have had a hard time warming up to the idea of not having titles/labels right there on the task-bar, but as it turns out, hovering my mouse over the task to have the title displayed actually doesn't feel like "too much", especially since I set my panels to auto-hide (so I have to move my mouse there to see the task manager anyway). All things considered, this could work. Going to keep it for a while and see what happens. In the meantime, I'm marking this as resolved. Thanks again Kai Uwe Broulik. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390166] Folder list should show number of unread mails for top-level folder and children separately
https://bugs.kde.org/show_bug.cgi?id=390166 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I don"t understand what is the problem it's the case. It was not changed. Please add a screenshot regards -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389604] All konsole windows and tab go black when closing tab with running program
https://bugs.kde.org/show_bug.cgi?id=389604 --- Comment #8 from baar...@xs4all.nl --- I do understand the remark, but I think it is a bit unfair, since 16.04 is LTS, and an update was not offered by Discover. But okay, machines are updating now. Thanks for telling it has been corrected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390536] New: KDE hangs when using Kaffeine
https://bugs.kde.org/show_bug.cgi?id=390536 Bug ID: 390536 Summary: KDE hangs when using Kaffeine Product: plasmashell Version: 5.11.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mar...@wp.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.5) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.15.0-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: Dual screen configuration. Nvidia graphics card. After a few minutes, KDE stops respond from time to time when Kaffeine is running. Sound also stops. Without Kaffeine hang never occur . Mouse pointer working, but KDE do not respond. KWin recover after changing screen to console and go back. Sometimes kill Kaffeine from console is necessary. The crash can be reproduced sometimes. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f75fcc84800 (LWP 713))] Thread 18 (Thread 0x7f75269c6700 (LWP 11622)): #0 0x7f75f5a0a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f75f685100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f75fa6939ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f75fa693e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f75f684fb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f75f5a0408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f75f6157e7f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f751f7fe700 (LWP 6463)): #0 0x7f75f5a0a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f75f685100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f75fa6939ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f75fa693e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f75f684fb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f75f5a0408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f75f6157e7f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f74dbf3d700 (LWP 4419)): #0 0x7f75f5a0a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f75f685100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f75fa6939ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f75fa693e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f75f684fb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f75f5a0408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f75f6157e7f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f751effd700 (LWP 1968)): #0 0x7f75f5a0a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f75f685100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f75fa6939ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f75fa693e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f75f684fb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f75f5a0408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f75f6157e7f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f751dffb700 (LWP 1069)): #0 0x7f75f5a0a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f75f685100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f75fa6939ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f75fa693e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f75f684fb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f75f5a0408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f75f6157e7f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f750ad72700 (LWP 929)): #0 0x7f75f5a0a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f75f685100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f75fa6939ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f75fa693e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f75f684fb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f75f5a0408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f75f6157e7f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f750a571700 (LWP 928)): #0 0x7f75f5a0a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f75f685100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f75fa6939ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f75fa693e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f75f684fb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f75f5a0408c in start_thread () at /usr/lib/
[krusader] [Bug 388266] Closing calculate occupied space window does not abort the calculation
https://bugs.kde.org/show_bug.cgi?id=388266 Nikita Melnichenko changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Version|2.6.0 |Git CC||nikita+...@melnichenko.name --- Comment #1 from Nikita Melnichenko --- I confirm it can be reproduced on master. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390479] Wrong stacking order when a window has been moved to another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=390479 Martin Flöser changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #10 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 119323 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 119323] Per-desktop stacking order
https://bugs.kde.org/show_bug.cgi?id=119323 Martin Flöser changed: What|Removed |Added CC||vladz...@gmail.com --- Comment #1 from Martin Flöser --- *** Bug 390479 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389984] Changing screen rotation under Wayland hangs the session hard
https://bugs.kde.org/show_bug.cgi?id=389984 --- Comment #5 from Martin Flöser --- The support info is from X11, we need the wayland one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390481] [Wayland] plasma session crashes when closing dolphin after MTP access
https://bugs.kde.org/show_bug.cgi?id=390481 --- Comment #3 from Martin Flöser --- We need a backtrace. I don't use mtp, thus I cannot try to reproduce. With a backtrace we can know whether it's already a known issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390535] New: Night color in Wayland causes seg fault if Operation Mode = Location | Time
https://bugs.kde.org/show_bug.cgi?id=390535 Bug ID: 390535 Summary: Night color in Wayland causes seg fault if Operation Mode = Location | Time Product: systemsettings Version: 5.12.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dan.mulholl...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.1) Qt Version: 5.9.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-041503-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: I installed Plasma 5.12 from the KDE backports for Kubuntu and run a session in Wayland. I test Night Colour under System Settings > Display and Monitor > Night Colour. All is well until I change Operation Mode to Location in which case it always immediately crashes. == System Details (I guess these are automatically added anyways) $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful $ uname -a Linux mulhollandd-XPS-13-9360 4.15.3-041503-generic #201802120730 SMP Mon Feb 12 07:31:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ plasmashell --version plasmashell 5.12.1 $ kf5-config --version Qt: 5.9.1 KDE Frameworks: 5.43.0 kf5-config: 1.0 The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff75b184140 (LWP 23284))] Thread 6 (Thread 0x7ff71f155700 (LWP 23297)): [KCrash Handler] #6 0x7ff7495ebb30 in wl_proxy_create_wrapper () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7ff73afdd9f1 in get_wl_surface_proxy (window=0x7ff718091f40, window=0x7ff718091f40) at ../../../src/egl/drivers/dri2/platform_wayland.c:125 #8 dri2_wl_create_window_surface (drv=, disp=0x5646d05835b0, conf=0x5646d05739c0, native_window=0x7ff718091f40, attrib_list=0x0) at ../../../src/egl/drivers/dri2/platform_wayland.c:199 #9 0x7ff73afcad17 in _eglCreateWindowSurfaceCommon (disp=0x5646d05835b0, config=config@entry=0x5646d05739c0, native_window=native_window@entry=0x7ff718091f40, attrib_list=attrib_list@entry=0x0) at ../../../src/egl/main/eglapi.c:907 #10 0x7ff73afcb104 in eglCreateWindowSurface (dpy=, config=config@entry=0x5646d05739c0, window=window@entry=140699236900672, attrib_list=attrib_list@entry=0x0) at ../../../src/egl/main/eglapi.c:923 #11 0x7ff73b203f4d in QtWaylandClient::QWaylandEglWindow::updateSurface (this=this@entry=0x5646d7135320, create=create@entry=true) at ../../../../hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:141 #12 0x7ff73b2024c5 in QtWaylandClient::QWaylandGLContext::makeCurrent (this=this@entry=0x5646d7114700, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:410 #13 0x7ff757d6e286 in QOpenGLContext::makeCurrent (this=0x5646d71358d0, surface=surface@entry=0x5646d70f9e40) at kernel/qopenglcontext.cpp:984 #14 0x7ff75532d004 in QSGRenderThread::invalidateOpenGL (this=this@entry=0x5646d7136260, window=0x5646d70f9e30, inDestructor=, fallback=0x0) at scenegraph/qsgthreadedrenderloop.cpp:487 #15 0x7ff7553348eb in QSGRenderThread::event (this=0x5646d7136260, e=0x5646d59f3190) at scenegraph/qsgthreadedrenderloop.cpp:402 #16 0x7ff755333b77 in QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x5646d7136260) at scenegraph/qsgthreadedrenderloop.cpp:702 #17 0x7ff755333f4a in QSGRenderThread::run (this=0x5646d7136260) at scenegraph/qsgthreadedrenderloop.cpp:730 #18 0x7ff75730429d in QThreadPrivate::start (arg=0x5646d7136260) at thread/qthread_unix.cpp:368 #19 0x7ff752e167fc in start_thread (arg=0x7ff71f155700) at pthread_create.c:465 #20 0x7ff756c06b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7ff7268a2700 (LWP 23289)): #0 0x7ff756bf606d in __GI___libc_read (fd=19, buf=buf@entry=0x7ff7268a1a70, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7ff750b71280 in read (__nbytes=16, __buf=0x7ff7268a1a70, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7ff728003590) at ../../../../glib/gwakeup.c:210 #3 0x7ff750b2cc4b in g_main_context_check (context=context@entry=0x7ff72be0, max_priority=2147483647, fds=fds@entry=0x7ff720002de0, n_fds=n_fds@entry=1) at ../../../../glib/gmain.c:3664 #4 0x7ff750b2d110 in g_main_context_iterate (context=context@entry=0x7ff72be0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3883 #5 0x7ff750b2d27c in g_main_context_iteration (context=0x7ff72be0, may_block=may_block@entry=1) at ../../
[krusader] [Bug 387551] ActionMan: random ampersand characters
https://bugs.kde.org/show_bug.cgi?id=387551 Nikita Melnichenko changed: What|Removed |Added CC||nikita+...@melnichenko.name Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Nikita Melnichenko --- What do you actually do to get multiple ampersands? Can you share your useractions.xml before and after? Can you check if this reproduces with v2.6 or git version if possible? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 386448] With krarc:/ handler installed, Dolphin doesn't exit archive when clicking on parent folder in location bar
https://bugs.kde.org/show_bug.cgi?id=386448 Nikita Melnichenko changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||nikita+...@melnichenko.name --- Comment #5 from Nikita Melnichenko --- I also confirm. Changing status. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390041] Ruler cause slow canvas performance in high zoom level
https://bugs.kde.org/show_bug.cgi?id=390041 --- Comment #5 from Alvin Wong --- Created attachment 110700 --> https://bugs.kde.org/attachment.cgi?id=110700&action=edit GammaRay shows ruler painting with 4.0 beta 1 The image here is still 3600px wide -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390041] Ruler cause slow canvas performance in high zoom level
https://bugs.kde.org/show_bug.cgi?id=390041 --- Comment #4 from Alvin Wong --- Hi Michael, This isn't exactly what I observed though. Yes, the ruler being a little bit larger than the canvas does seem to exist before your change, but it definitely is a bug. I would have expected you to have fixed it since you did rewrite a huge part of the code, oh well. The behaviour of painting the marks outside of the visible range does not exist on 4.0 beta 1. I checked it with GammaRay just now (I'll attach a screenshot of it). And it definitely does affect the performance. It depends on the size of the image: In the screenshot from comment #1, the image width is 3600px, and the visible ruler range is 1722-1741 which consists of 20 marks, so only 0.556% of the marks are visible. The cost of painting the text of each invisible mark is around 0.02% to 0.03% which makes the percentage of time wasted in painting the invisible marks to be about 0.02% * (3604-20) = 71.68%. For me it causes the canvas fps to drop significantly when panning (compared to having the ruler invisible). You can test with the nightly build. The latest Windows nightly build can be found here: https://binary-factory.kde.org/job/Krita_Nightly_Build/ It would be great if you can check it soon. (While you are at it, there are also some undesirable behaviours: (1.) At a certain zoom level, the subdivision marks aren't aligned to the pixel boundaries. (2.) At high zoom levels, the subdivision marks reaches subpixel-level which seems a bit unnecessary.) (In reply to simeirxh from comment #3) > The behavior of the ruler to be a little larger than the canvas and to paint > all marks no matter if they are visible existed before my commit you > mentioned. They exist in both 3.3.3 (it's the newest stable release, right?) > and master, which are both having their rulers working normally. It's true > that they are not working completely in the expected way (I feel that they > are strange, too when I was reading the code), but the unexpected behaviors > doesn't actually affect usage, right? The extra pixels hardly make any > difficulties in painting, and the extra painted marks are not visible > because they are out of the range of the widget. I suppose that's why the > original programmer left them there... Therefore, I don't think either my > commit or the behaviors you mentioned caused the bug. I don't know how the > nightly packages work. If you can tell me that, then I think I might be able > to go back to the ruler class and see if I can do something, on both the bug > and the strange behaviors. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 390450] sftp connect don't read ~/.ssh/config correctly
https://bugs.kde.org/show_bug.cgi?id=390450 Nikita Melnichenko changed: What|Removed |Added Resolution|UNMAINTAINED|--- Component|net-connection |sftp Status|NEEDSINFO |UNCONFIRMED Product|krusader|kio Assignee|m...@fork.pl |a...@cryptomilk.org Version|2.4.0-beta3 "Single Step" |unspecified --- Comment #3 from Nikita Melnichenko --- Krusader doesn't implement sftp protocol but uses KIO. This is a KIO bug, likely it's a duplicate of bugs #338432, #230530. I'll reassign. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 169847] split view feature
https://bugs.kde.org/show_bug.cgi?id=169847 --- Comment #28 from Nate Graham --- Feel free to read the documentation I linked to, which will help you find what you're looking for! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 169847] split view feature
https://bugs.kde.org/show_bug.cgi?id=169847 --- Comment #27 from Musikolo --- Sounds fair! Can you please pass me a link to the source code? This said, I had no intention of pushing, because as you said, open source software is all good will... ;-) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 169847] split view feature
https://bugs.kde.org/show_bug.cgi?id=169847 --- Comment #26 from Nate Graham --- There's always a chance! But this is a mostly volunteer project, and it needs a developer to do the work. You, maybe? ;) https://community.kde.org/Get_Involved/development -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 169847] split view feature
https://bugs.kde.org/show_bug.cgi?id=169847 --- Comment #25 from Musikolo --- Is there any chance this feature gets eventually implemented? I'm asking because it was originally requested over 9 years ago, and I see nothing that suggests it's coming anytime in the future. Thank you and long live Okular! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 389909] Allow dragging navigation panel to the right
https://bugs.kde.org/show_bug.cgi?id=389909 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=141289 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 141289] Allow navigation panel on the bottom instead of side
https://bugs.kde.org/show_bug.cgi?id=141289 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=389909 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389604] All konsole windows and tab go black when closing tab with running program
https://bugs.kde.org/show_bug.cgi?id=389604 --- Comment #7 from Nate Graham --- Old software strikes again! In the future please see https://community.kde.org/Get_Involved/Bug_Reporting#Step_2:_Make_sure_it_hasn.27t_already_been_fixed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 169847] split view feature
https://bugs.kde.org/show_bug.cgi?id=169847 Christoph Feck changed: What|Removed |Added CC||david.cortes.rivera@gmail.c ||om --- Comment #24 from Christoph Feck --- *** Bug 389951 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 389951] Add option to open new window/tab with the same document
https://bugs.kde.org/show_bug.cgi?id=389951 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- See also bug 339971. *** This bug has been marked as a duplicate of bug 169847 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390140] Systemsettings fails to associate .rds files with RStudio
https://bugs.kde.org/show_bug.cgi?id=390140 Christoph Feck changed: What|Removed |Added Assignee|plasma-b...@kde.org |fa...@kde.org Component|general |kcm_filetypes -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390140] Systemsettings fails to associate .rds files with RStudio
https://bugs.kde.org/show_bug.cgi?id=390140 --- Comment #1 from Christoph Feck --- Why does it say 'kbuildsycoca4'? You should be using 'kbuildsycoca5'. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 387426] FB2 module do not display content inside tags
https://bugs.kde.org/show_bug.cgi?id=387426 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 390394] Changing notification sounds volume does nothing
https://bugs.kde.org/show_bug.cgi?id=390394 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #7 from Dr. Chapatin --- (In reply to David from comment #6) > Funny, now with Phonon Gstreamer I get no notification sounds at all, I had the same problem some time ago. https://bugs.kde.org/show_bug.cgi?id=385759 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 390518] Fedora27: By default connection editor sets Ethernet to "no auto", 100MBits/s half duplex
https://bugs.kde.org/show_bug.cgi?id=390518 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Dr. Chapatin --- same thing on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390534] New: Enabling notifications in system tray causes plasmashell to crash
https://bugs.kde.org/show_bug.cgi?id=390534 Bug ID: 390534 Summary: Enabling notifications in system tray causes plasmashell to crash Product: plasmashell Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: akontsev...@gmail.com Target Milestone: 1.0 Created attachment 110699 --> https://bugs.kde.org/attachment.cgi?id=110699&action=edit Disable system notifications in system tray settings Enabling system notifications in system tray causes plasmashell to hang - 100% CPU and no response if new notification come up. To fix forced to disable system notifications in system tray settings (see screenshot attached). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 387426] FB2 module do not display content inside tags
https://bugs.kde.org/show_bug.cgi?id=387426 --- Comment #2 from abogi...@gmail.com --- patch pending approval: https://phabricator.kde.org/D10566 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 390533] New: kdenlive crashes on project playback
https://bugs.kde.org/show_bug.cgi?id=390533 Bug ID: 390533 Summary: kdenlive crashes on project playback Product: kdenlive Version: 17.08.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: z...@mail.zp.ua Target Milestone: --- Created attachment 110698 --> https://bugs.kde.org/attachment.cgi?id=110698&action=edit backtrace - What I was doing when the application crashed: opened prviously saved project that has multiple H264 video sources atored in mp4 and mts containers with different resolution and framerate cursor navigation doesn't work after reopening this particular project video source playback works project playback causes kdenlive to crash immediately with segfault - Custom settings of the application: using default settings The crash can be reproduced every time. (KDE bug submission didn't work, having to create the bug report manually) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390041] Ruler cause slow canvas performance in high zoom level
https://bugs.kde.org/show_bug.cgi?id=390041 --- Comment #3 from simei...@gmail.com --- (In reply to Alvin Wong from comment #0) > Panning the canvas is noticeable slower with ruler enabled when under high > zoom level (> 1000%). > > Found in krita-nightly-x64-v4.0.0.51-222-g34bb24e195, not on beta 1. I > suspected the commit > https://phabricator.kde.org/R37:ba60778bd55071449c56acd78c056623ce7e7ac6 to > have introduced the regression, confirmation needed. > > CC: Michael Zhou (I think the email should be right?) Hi Alvin, Sorry for the late reply. The behavior of the ruler to be a little larger than the canvas and to paint all marks no matter if they are visible existed before my commit you mentioned. They exist in both 3.3.3 (it's the newest stable release, right?) and master, which are both having their rulers working normally. It's true that they are not working completely in the expected way (I feel that they are strange, too when I was reading the code), but the unexpected behaviors doesn't actually affect usage, right? The extra pixels hardly make any difficulties in painting, and the extra painted marks are not visible because they are out of the range of the widget. I suppose that's why the original programmer left them there... Therefore, I don't think either my commit or the behaviors you mentioned caused the bug. I don't know how the nightly packages work. If you can tell me that, then I think I might be able to go back to the ruler class and see if I can do something, on both the bug and the strange behaviors. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390532] New: Printers settings causes login prompt and crash
https://bugs.kde.org/show_bug.cgi?id=390532 Bug ID: 390532 Summary: Printers settings causes login prompt and crash Product: systemsettings Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gis...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.1) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Within system settings, clicked the Printers section. A login dialog appeared, I entered the password. Upon submitting the password, the application crashed. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f672f9ed800 (LWP 10177))] Thread 12 (Thread 0x7f66a26b6700 (LWP 11138)): #0 0x7f6724e31e43 in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #1 0x7f6724e32ea7 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6724e3310e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f672bce0d24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f672bc82e9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f672ba9278e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f66744c01ba in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f672ba97b2d in () at /usr/lib/libQt5Core.so.5 #8 0x7f67274b708c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f672b39de7f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f66a00f9700 (LWP 11012)): #0 0x7f67274bd3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f672b7135bd 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 0x7f672b7135bd 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 0x7f66ac3a4aa9 in () at /usr/lib/libQt5WebKit.so.5 #4 0x7f66ac3a4bf9 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7f672b719b9f in std::execute_native_thread_routine(void*) (__p=0x5574e8e2ab80) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:83 #6 0x7f67274b708c in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f672b39de7f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f66ccfb7700 (LWP 10889)): #0 0x7f672b39397b in poll () at /usr/lib/libc.so.6 #1 0x7f6724e32ff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6724e3310e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f66ccfbeb0e in () at /usr/lib/gio/modules/libdconfsettings.so #4 0x7f6724e5b26a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f67274b708c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f672b39de7f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f66d8707700 (LWP 10885)): #0 0x7f672b39397b in poll () at /usr/lib/libc.so.6 #1 0x7f6724e32ff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6724e333b2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f66d79dd6d8 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f6724e5b26a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f67274b708c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f672b39de7f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f66d693f700 (LWP 10884)): #0 0x7f6724e32b85 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #1 0x7f6724e33081 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6724e3310e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6724e33162 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f6724e5b26a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f67274b708c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f672b39de7f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f66e7657700 (LWP 10787)): #0 0x7f672b38f3d8 in read () at /usr/lib/libc.so.6 #1 0x7f6724e787d1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6724e32ac8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f6724e32f96 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f6724e3310e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f672bce0d24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f672bc82e9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f672ba9278e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f672958ba19 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f672ba97
[valgrind] [Bug 384930] Valgrind fails to compute correctly some code using the GMP library
https://bugs.kde.org/show_bug.cgi?id=384930 --- Comment #18 from jacobly@gmail.com --- Created attachment 110697 --> https://bugs.kde.org/attachment.cgi?id=110697&action=edit Test mem variants of instructions in test-amd64. I think this triggers a latent bug in the test code with string instructions (I'm guessing due to the fact that assemblers will accept operands for them, but ignore them since there's only one possible encoding to output, which just happens to match up with how parameters are passed to functions), but it certainly tests more arithmetic code paths in VEX. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385712] Unhinted rendering of bold fonts
https://bugs.kde.org/show_bug.cgi?id=385712 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- This issue could be in Qt or in the font rendering libraries (freetype or Mesa). Plasma itself has no code to render fonts. If this is still reproducible with a Tumbleweed live ISO or any other rolling release ISO image, I suggest to report this issue directly to Qt developers via https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386433] Window sizing is not expanding properly
https://bugs.kde.org/show_bug.cgi?id=386433 --- Comment #14 from Christoph Feck --- The KCM shell adds scrollbars to help modules needing more space than is available on the screen. This, however, requires that modules correctly set their minimum size. You can see this issue with some modules. kcmshell5 --list | tail -n+2 | awk '{print$1}' | xargs -L1 kcmshell5 I do not think this can be solved at a single location. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390110] Weird behavior when utilizing acentuation
https://bugs.kde.org/show_bug.cgi?id=390110 --- Comment #15 from Pedro Gabriel Drumond Pereira --- When I press tilde the kwin console gives me Xcb symbol 0 at odd and Xcb symbol 126 for even presses, no modifiers for either of then and scan code 40. When I press accute, Xcb symbols are 0 for odd, 126 for even, no modifiers and scan code 40. I can now input those keys in text box eventually, but krita opens in process, and if it's already open it makes krita window gain or lose focus. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389251] Add KSysGuard to Desktop toolbox
https://bugs.kde.org/show_bug.cgi?id=389251 --- Comment #1 from Christoph Feck --- As far as I know, clicking on the systemloadviewer applet opens ksysguard. Users needing quick UI access to the process list could add this widget to their status area. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389665] Rotating screen doesn't work on wayland
https://bugs.kde.org/show_bug.cgi?id=389665 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #10 from Michael D --- I've the same issue--can't rotate 90 degree, but can 180 degrees. Automatic screen rotation doesn't work, though, and if I click on the icon in the tray, nothing happens. Another thing: after rotating the screen 180, then 90, then back to normal, I lost input to gtk apps such as firefox. Not sure if they're related though, since I haven't tried to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389280] The prompt appearing for .desktop files has no parent
https://bugs.kde.org/show_bug.cgi?id=389280 Christoph Feck changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389283] Plasma hangs and uses 100% of a CPU core [0x00007f339e7bc7c5 in QV4::PersistentValueStorage::allocate (this=0x55711959f670) at jsruntime/qv4persistent.cpp:189...]
https://bugs.kde.org/show_bug.cgi?id=389283 --- Comment #3 from Christoph Feck --- Could you please try with a fresh Plasma configuration? (Move ~/.config/plasma*rc temporary away, or create a new user account) If this is not reproducible there, try to find out which change causes the CPU issue. Otherwise, even try to remove the default widgets (task bar, notification area, etc.) It could give us a clue which part of the code is responsible for the CPU usage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388322] Digital Clock Plasmoid ignores timezone settings and displays wrong time
https://bugs.kde.org/show_bug.cgi?id=388322 --- Comment #5 from Christoph Feck --- If you can provide the information requested in comment #4, please add it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355679] Add "Display Configuration" to Desktop toolbox and/or desktop context menu
https://bugs.kde.org/show_bug.cgi?id=355679 Christoph Feck changed: What|Removed |Added Keywords||junior-jobs --- Comment #3 from Christoph Feck --- Code to open kcm-kscreen should be similar to code for the clock applet opening kcm-clock. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390092] plasmashell crashes on boot
https://bugs.kde.org/show_bug.cgi?id=390092 Christoph Feck changed: What|Removed |Added Keywords||wayland Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 390019] Screen unlocked notification not triggered when screen is unlocked.
https://bugs.kde.org/show_bug.cgi?id=390019 Christoph Feck changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 389284 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 389284] Screen lock notification does not work anymore
https://bugs.kde.org/show_bug.cgi?id=389284 Christoph Feck changed: What|Removed |Added CC||lnx...@westlot.net --- Comment #5 from Christoph Feck --- *** Bug 390019 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390531] Default icon grid doesn't leave enough horizontal and vertical space for file and folder titles
https://bugs.kde.org/show_bug.cgi?id=390531 --- Comment #2 from Nate Graham --- I can understand that. We had the same problem at Apple for more than a decade; people always complained that the padding was too high. Eventually we solved it with a slider you can use to change the padding between icons, which makes sense to me because this is the kind of thing where you're never going to please everybody with an immutable setting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390531] Default icon grid doesn't leave enough horizontal and vertical space for file and folder titles
https://bugs.kde.org/show_bug.cgi?id=390531 --- Comment #1 from Eike Hein --- I can look into the titles maybe, but the padding won't change - it was actually reduced twice, because of great repeated user clamoring both times, and people are much happier now with the tighter grid. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 390515] Allow users to override "login cancelled by app"
https://bugs.kde.org/show_bug.cgi?id=390515 David Edmundson changed: What|Removed |Added Target Milestone|1.0 |--- Component|general |general Assignee|k...@davidedmundson.co.uk|l.lu...@kde.org Product|plasmashell |ksmserver -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 389920] After using File > Close, window shadow remains
https://bugs.kde.org/show_bug.cgi?id=389920 --- Comment #7 from Christoph Feck --- Is this a QMdiSubWindow? If yes, it is the Breeze QStyle that adds the shadows, and it is possible that it is a bug there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390526] Add option to "Open groups using 'Present Windows Effect'" in Task Manager
https://bugs.kde.org/show_bug.cgi?id=390526 --- Comment #2 from Omar Plummer --- (In reply to Kai Uwe Broulik from comment #1) > Did you try icon-only task manager? No I have not. I'll give it a shot, but truth be told; I prefer having the window titles displayed in my task manager. I'm not able to test it out right now, because plasmashell crashes when I try adding the Icons-Only Task Manager to any of my panels, but I suppose that's a separate bug report. Thanks for the pointer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390531] New: Default icon grid doesn't leave enough horizontal and vertical space for file and folder titles
https://bugs.kde.org/show_bug.cgi?id=390531 Bug ID: 390531 Summary: Default icon grid doesn't leave enough horizontal and vertical space for file and folder titles Product: plasmashell Version: master Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 110696 --> https://bugs.kde.org/attachment.cgi?id=110696&action=edit Spacing, title width, and max number of lines in Folder view and Dolphin Files and Folders in Folder View always look really cramped because long titles very easily get split up into multiple lines and then elided. The behavior here is a bit too aggressive, I think. I see a lot of user complaints about it. Part of the problem is the default maximum number of lines (2), but another part is that the width available for titles is so narrow that long-ish words often get chopped up into multiple lines right in the middle. For the same sized icons, Dolphin's icon view offers more horizontal space and slightly larger padding between icons. See attached screenshot from my own machine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389984] Changing screen rotation under Wayland hangs the session hard
https://bugs.kde.org/show_bug.cgi?id=389984 Christoph Feck changed: What|Removed |Added Product|systemsettings |kwin Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Component|general |general --- Comment #4 from Christoph Feck --- Thanks for the update; I guess it is a duplicate of bug 389665. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390530] KMymoney crash when I select payee into combo by Keyboard
https://bugs.kde.org/show_bug.cgi?id=390530 --- Comment #1 from Aristide --- So, I have forget to add video into description : https://www.youtube.com/watch?v=OtuAEHyoAzA -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390530] New: KMymoney crash when I select payee into combo by Keyboard
https://bugs.kde.org/show_bug.cgi?id=390530 Bug ID: 390530 Summary: KMymoney crash when I select payee into combo by Keyboard Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: fmet...@gmail.com Target Milestone: --- Created attachment 110695 --> https://bugs.kde.org/attachment.cgi?id=110695&action=edit Trace PROBLEM : Kmymoney Segfault when you search payee into new operation by Keyboard. REPRODUCE BUG : → Create ONE payee (or more) (Example : Jacques) → Create a new operation. → In payee type « Jac » ... Select « Jacques » → NOW : Kmymoney ask for save document, and crash. WORKAROUND : → Select payee in list without search with keyboard. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390515] Allow users to override "login cancelled by app"
https://bugs.kde.org/show_bug.cgi?id=390515 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||plasma-b...@kde.org Target Milestone|--- |1.0 Product|ksmserver |plasmashell Assignee|l.lu...@kde.org |k...@davidedmundson.co.uk Component|ui |general -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 390500] .docx files are recognized as zip archives
https://bugs.kde.org/show_bug.cgi?id=390500 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- The version of the shared-mime-info package provided by your distro is too old. See the bug that this is a duplicate of. *** This bug has been marked as a duplicate of bug 389724 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389724] Upgrade shared-mime-info so that LibreOffice documents stop opening with Ark
https://bugs.kde.org/show_bug.cgi?id=389724 Nate Graham changed: What|Removed |Added CC||david.cortes.rivera@gmail.c ||om --- Comment #1 from Nate Graham --- *** Bug 390500 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 388420] Dotted line artifact when switching focused item
https://bugs.kde.org/show_bug.cgi?id=388420 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390529] New: import from scanner not enabled
https://bugs.kde.org/show_bug.cgi?id=390529 Bug ID: 390529 Summary: import from scanner not enabled Product: digikam Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: showfoto Assignee: digikam-bugs-n...@kde.org Reporter: coll...@laboiteaprog.com Target Milestone: --- when i start showfoto and go to tools menu, import from scanner is not enabled. i need to go to open folder, to get access to it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390487] Open in File Manager function enhancement
https://bugs.kde.org/show_bug.cgi?id=390487 --- Comment #5 from nimbu...@egosurf.net --- I would think either the function would not operate on multiple files, or it would just open one instance of each folder if you select multiple files. For comparison, currently the Open function (F4) only operates on one file if you select multiple. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 291835] KIO very slow when copying from network through smb
https://bugs.kde.org/show_bug.cgi?id=291835 --- Comment #52 from Christoph Feck --- Mark, the issue is not whether user-space code can saturate the network. The problem is that there is no async I/O API available in libsmbclient. If I understand the previous comments correctly, there is a limitation in the specification to 64 KB chunks. libsmbclient does not allow to send a network request for the next 64KB chunk while an old one is still running. You have to wait for the reply, then send the request for the next chunk. On some networks, this causes a several ms delay between the requests. The faster the transfer speed, the more painful is the delay (delay vs. payload ratio). The CIFS implementation in the kernel does not have this issue; while created by the same (Samba) team, it does not use libsmbclient and always requests the next chunk ahead of arrival of the previous chunk, so that the network is always saturated. It would be possible to write a network client out-of-kernel that does not have the libsmbclient limitation, but we do not have the power to write one. I do not know if there is any other library or code out there that we could use. > We just need someone Not me for anything related to networks or databases ;) -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 382391] Accept both decimal separators (comma and dot) from clipboard with locales where it is straightforward
https://bugs.kde.org/show_bug.cgi?id=382391 --- Comment #5 from martonmiklos --- The attached patch only works for locale which decimal separator is , and the thousand separator is neither . or , (most commonly space). With this locale it will interpret the . as a decimal point too. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 390437] Bring back icons and styles form previous KDE versions
https://bugs.kde.org/show_bug.cgi?id=390437 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- We do not have the manpower to maintain multiple icon themes or window decorations. Even Oxygen icon theme no longer gets new graphics, but only icon name updates. If you are not satisfied with the content of application store, please report it to the authors of the themes offered there. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373378] Add a Point scaling filter.
https://bugs.kde.org/show_bug.cgi?id=373378 Jeff Knox changed: What|Removed |Added CC||jd.k...@gmail.com --- Comment #5 from Jeff Knox --- Is there a known workaround in case we need a nearest neighbor or point filter? Such a filter is nice for reducing pixel art. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390038] Desktop Toolbox should be in top-right corner to keep it from intruding on Folder View icons
https://bugs.kde.org/show_bug.cgi?id=390038 --- Comment #5 from Kai Uwe Broulik --- https://phabricator.kde.org/D10563 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390128] KMM 5.0 is core dumping when entering any new transaction
https://bugs.kde.org/show_bug.cgi?id=390128 w...@nurfuerspam.de changed: What|Removed |Added CC||w...@nurfuerspam.de -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 382391] Accept both decimal separators (comma and dot) from clipboard with locales where it is straightforward
https://bugs.kde.org/show_bug.cgi?id=382391 --- Comment #4 from Evan Teran --- It has been a while since I was terribly active with kcalc. Fortunately, Christopher has been awesome about handling the occasiobal issue that crops up (thanks!). I've always had mixed feeling about how to handle the separator issue. How shall we parse 1,234? 1234? Or 1 + (234/1000) You solution seems mostly reasonable, but we should be careful about the corner cases if any come up. Thanks for looking into this issue! On Thu, Feb 15, 2018, 3:19 PM martonmiklos wrote: > https://bugs.kde.org/show_bug.cgi?id=382391 > > --- Comment #3 from martonmiklos --- > Thanks Cristoph for the hint, I have created the D10555 phabricator issue. > I have no idea who should I add as reviewer. Evan Teran no longer seems to > be > active here and I have not been able to find him in the reviewer list. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 390019] Screen unlocked notification not triggered when screen is unlocked.
https://bugs.kde.org/show_bug.cgi?id=390019 lnx...@westlot.net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from lnx...@westlot.net --- This seems to have been fixed in the 5.43 update. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390460] Plasma Crash Due to Lack of Memory
https://bugs.kde.org/show_bug.cgi?id=390460 --- Comment #1 from David Edmundson --- We can't do much about crashing due to lack of memory. We can do something about the lack of memory. Was the memory usage of plasma increasing? Do you have a slideshow wallpaper background? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #69 from Christoph Feck --- Thomas, let me reply to you. 1. Gregor is not a Plasma developer, but occasionally helps in this bug tracker. The feedback he gave you was honest and we hoped that it would answer your question. 2. Please read https://www.kde.org/code-of-conduct/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390526] Add option to "Open groups using 'Present Windows Effect'" in Task Manager
https://bugs.kde.org/show_bug.cgi?id=390526 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Did you try icon-only task manager? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390481] [Wayland] plasma session crashes when closing dolphin after MTP access
https://bugs.kde.org/show_bug.cgi?id=390481 --- Comment #2 from farmb...@googlemail.com --- Dolphin 17.08.3 Steps to reproduce: 1. Attach Android phone to computer, set USB mode to file transfer 2. Open the device through the device popup in the systray which should open dolphin with an MTP url of the device (i have dolphin in split view mode) in both views 3. Open Home in one view 4. Copy a file in the android view(i copied a file from the Camera) 5. Paste it to the Home view 6. close dolphin by clicking the x in the upper right corner 7. have fun logging in again I updated to Plasma 5.12.1 and the crash still happens. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #68 from Nate Graham --- OK, I'll wade into this pool of fire. :) It seems like there are multiple interrelated underlying complaints here: - Some content-heavy widgets (like the network widget) are too small - Some content-light widgets (like the media status indicator) are too big - The default size is too big on small screens Any more? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389845] FN keys for screen brightness no longer work
https://bugs.kde.org/show_bug.cgi?id=389845 Christoph Feck changed: What|Removed |Added CC||matthewtresc...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 390348 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 390348] Screen brightness hotkeys not working
https://bugs.kde.org/show_bug.cgi?id=390348 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 389845 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384930] Valgrind fails to compute correctly some code using the GMP library
https://bugs.kde.org/show_bug.cgi?id=384930 --- Comment #17 from Julian Seward --- (In reply to Niels Möller from comment #15) > But I've run the mini-gmp tests [..] Good, thanks. That's good enough for me. I'll land the fix. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384930] Valgrind fails to compute correctly some code using the GMP library
https://bugs.kde.org/show_bug.cgi?id=384930 --- Comment #16 from Julian Seward --- (In reply to jacobly.alt from comment #14) > I added mem,reg and reg,mem tests to test-amd64 [..] Great! Can you pls make the testcase diffs available? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390489] Settings options menu show dropdown arrow in the background description
https://bugs.kde.org/show_bug.cgi?id=390489 --- Comment #2 from Christoph Feck --- Is this QtCurve style? If yes, we can reassign there. Otherwise, you would need to write to a different bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389991] Sleep key no longer initiates sleep
https://bugs.kde.org/show_bug.cgi?id=389991 Michal Hlavac changed: What|Removed |Added CC||hla...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390527] Add Ctrl+H as Alternative Shortcut for Alt+. to Toggle Show Hidden Files
https://bugs.kde.org/show_bug.cgi?id=390527 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Nate Graham --- Submitted a patch for this: https://phabricator.kde.org/D10558 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390528] Symbols table now no longer automatically refreshes itself.
https://bugs.kde.org/show_bug.cgi?id=390528 Royce changed: What|Removed |Added CC||ro...@ecs.vuw.ac.nz -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390528] New: Symbols table now no longer automatically refreshes itself.
https://bugs.kde.org/show_bug.cgi?id=390528 Bug ID: 390528 Summary: Symbols table now no longer automatically refreshes itself. Product: kate Version: 17.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: ro...@ecs.vuw.ac.nz Target Milestone: --- Problem is with Symbols Viewer Plugin. Symbols table now no longer automatically refreshes itself. If while editing you add/remove lines then click on a symbol in the symbols viewer table. It takes you to the wrong place. Right clicking on the symbols viewer and choosing Refresh List then update the table. Automatically refreshing works in version Kate v17.04.03. Below is the versions of kate where it was not working that I tried. Kate version 17.12.(1 & 2) KDE Framework 5.42.0 Qt 5.10.0 Thanks Royce -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372147] Add option to populate taskbar items from right to left
https://bugs.kde.org/show_bug.cgi?id=372147 Christoph Feck changed: What|Removed |Added CC||colingz...@gmail.com --- Comment #8 from Christoph Feck --- *** Bug 390525 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390525] Tasks in the task manager should be able to be aligned to the right in settings.
https://bugs.kde.org/show_bug.cgi?id=390525 Christoph Feck changed: What|Removed |Added Component|general |Task Manager Version|unspecified |5.12.1 Assignee|cf...@kde.org |h...@kde.org Target Milestone|--- |1.0 Resolution|--- |DUPLICATE CC||plasma-b...@kde.org Status|UNCONFIRMED |RESOLVED Product|frameworks-kwidgetsaddons |plasmashell --- Comment #1 from Christoph Feck --- Spacers indeed dynamically change size, but Plasma developers might revisit this. *** This bug has been marked as a duplicate of bug 372147 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 390518] Fedora27: By default connection editor sets Ethernet to "no auto", 100MBits/s half duplex
https://bugs.kde.org/show_bug.cgi?id=390518 Ed Greshko changed: What|Removed |Added CC||ed.gres...@greshko.com --- Comment #2 from Ed Greshko --- I can confirm that on a fresh install of Fedora 27 Bringing up the Network-Manager GUI one sees Allow Auto-negotiation: Unchecked Speed: Automatic Duplex: Half The hardware is 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller The driver in use is (from lsmod) e1000. The ifcfg-enp0s3 file contains... [egreshko@f27k-v network-scripts]$ cat ifcfg-enp0s3 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=enp0s3 UUID=7f87f7d8-1d0f-316e-9a2c-419042156b19 ONBOOT=yes AUTOCONNECT_PRIORITY=-999 DEVICE=enp0s3 (No, ETHTOOL_OPTS= line) And ethtool reports Settings for enp0s3: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Cannot get wake-on-lan settings: Operation not permitted Current message level: 0x0007 (7) drv probe link Link detected: yes So, what the GUI has and what reality is are different. The Speed is actually 1000Mb/s Possibly a function of the driver? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 335117] Information leak when using GPG on Bcc recipients
https://bugs.kde.org/show_bug.cgi?id=335117 --- Comment #10 from Sandro Knauß --- In my opinion there is no information leakage, that's why I would close this bug as Resolved/Invalid. But I really want to be sure (as this topic is important to me), that there is no information leakage, that's why I want to keep this bug report open to give the reporter time to give more details, how he thinks this information is leaked. The information I need is a mail encrypted for keys where I have access to their private keys, that shows me the information leakage or a description how the reporter found out that there is information leakage, as I can't reproduce this. -- You are receiving this mail because: You are watching all bug changes.