[kdevelop] [Bug 361693] Crash when removing breakpoint in Review mode (commit action)
https://bugs.kde.org/show_bug.cgi?id=361693 Kevin Funk changed: What|Removed |Added Keywords||junior-jobs --- Comment #1 from Kevin Funk --- @Piotr: Wanna have a look? Thanks for the detailed bug reports! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 333759] "Variables" tool view sometimes not in sync with Frame Stack view
https://bugs.kde.org/show_bug.cgi?id=333759 --- Comment #7 from Kevin Funk --- @Aetf: Please go for the simpler change, try if it works. Note regarding "duplication": Yes, we might have a copy of thread/frame in IVariableController, but there's a reason for it: Updating the variables is expensive (lots of communication with GDB required), so we need to reduce the number of updates as much as possible. Thus we "cache" thread/frame here, not "duplicate". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361704] window on external screen disappears when hibernating with external screen connected and resuming when it is not connected
https://bugs.kde.org/show_bug.cgi?id=361704 Thomas Lübking changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Thomas Lübking --- > It is not even in window bar in control panel. > Same with Konsole except process not running anymore. (Next time) check the output of "xwinfo -root -tree" on whether the window actually still exists (the taskbar and kwin are different processes) - the window is probably gone and that is because multiscreen is completely FUBAR in Qt5 (and plasmashell in addition, but that's not the problem here), ie. the bug is in the clients and caused by Qt. See bug #341497 - don't even try to trigger randr events of any type. *** This bug has been marked as a duplicate of bug 341497 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions
https://bugs.kde.org/show_bug.cgi?id=341497 Thomas Lübking changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #56 from Thomas Lübking --- *** Bug 361704 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #36 from Thomas Lübking --- I've seen the imbalanced painter warnings all the time. The undefined swap behavior worries me much more since it will result in an undefined context/PBO (whatever is operated on) and the artifacts look like that - And I've not seen them before. No idea where those might stem from, though. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 361696] baloo_file_extractor is at 100% CPU after login until killed
https://bugs.kde.org/show_bug.cgi?id=361696 Alexander Potashev changed: What|Removed |Added Version|unspecified |5.20.0 Product|Baloo |frameworks-baloo CC||aspotas...@gmail.com Component|Baloo File Daemon |Baloo File Daemon -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 344456] Plasma 5 desktop does not suspend with only upower, no systemd
https://bugs.kde.org/show_bug.cgi?id=344456
Anton Filimonov changed:
What|Removed |Added
CC||anton.filimo...@gmail.com
--- Comment #38 from Anton Filimonov ---
Had same problem with suspend in Gentoo with plasma 5.5.5. Localauthority files
mentioned above didn't help. Managed to solve missing suspend issue by adding
polkit rule instead:
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.upower.suspend")
{
return polkit.Result.YES;
}
});
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 361706] New: Krita does not recognize a right click performed by Surface Pen while on canvas
https://bugs.kde.org/show_bug.cgi?id=361706 Bug ID: 361706 Summary: Krita does not recognize a right click performed by Surface Pen while on canvas Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: p...@fauth-mayer.de By default, the side button of the Surface Pen performs a right click which should open the popup palette while on canvas. Instead it performs the operation of the current brush. While not on canvas, right clicking with the pen works fine. Reproducible: Always Steps to Reproduce: 1. Use Surface Pen to perform a right click 2. See that it paints instead of opening the popup palette 3. Profit Actual Results: Krita uses the equipped brush Expected Results: Krita should have opened the popup palette PC: Surface Pro 4, all drivers up to date Surface Pen came with Surface Pro 4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360511] clang-parser utility doesn't get standard include files
https://bugs.kde.org/show_bug.cgi?id=360511 --- Comment #2 from Kevin Funk --- @Pedro: Care to work on a patch? -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 361707] New: Baloo keeps crashing
https://bugs.kde.org/show_bug.cgi?id=361707 Bug ID: 361707 Summary: Baloo keeps crashing Product: Baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: vojtech.zei...@opensuse.org CC: pinak.ah...@gmail.com Application: baloo_file (5.21.0) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Every time I turn on the computer, baloo is after some time crashing. "balooctl status" shows indexing doesn't move forward - it is still in about 1/3 of files and the number and index size doesn't grow up. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2331e75780 (LWP 1964))] Thread 3 (Thread 0x7f2327189700 (LWP 1966)): #0 0x7f232f9b7bbd in poll () at /lib64/libc.so.6 #1 0x7f232c3e1e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f232c3e1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f23305c63fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f233057404b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f23303b05da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f233176a095 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f23303b5079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f232ea060a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f232f9bffed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f2326787700 (LWP 3190)): #0 0x7f232f9b7bbd in poll () at /lib64/libc.so.6 #1 0x7f232c3e1e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f232c3e1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f23305c63fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f233057404b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x004155de in () #6 0x7f23303b1ede in () at /usr/lib64/libQt5Core.so.5 #7 0x7f23303b5079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f232ea060a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f232f9bffed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f2331e75780 (LWP 1964)): [KCrash Handler] #6 0x7f232d6cd25c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so #7 0x7f2330c6555d in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x7f2330c62a50 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x7f2330c74421 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x0041d8f3 in () #11 0x0041e232 in () #12 0x7f23305a0253 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #13 0x0041eb2a in () #14 0x0042 in () #15 0x7f23305a0253 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x7f233061904e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #17 0x7f23305acd89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7f23305760cc in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x7f2330576005 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7f23305c71ae in () at /usr/lib64/libQt5Core.so.5 #21 0x7f232c3e1c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x7f232c3e1ed8 in () at /usr/lib64/libglib-2.0.so.0 #23 0x7f232c3e1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x7f23305c63dc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #25 0x7f233057404b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #26 0x7f233057bf56 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #27 0x0040a902 in () #28 0x7f232f8fcb05 in __libc_start_main () at /lib64/libc.so.6 #29 0x0040aa7e in _start () Possible duplicates by query: bug 359672, bug 355210, bug 353223. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360511] clang-parser utility doesn't get standard include files
https://bugs.kde.org/show_bug.cgi?id=360511 --- Comment #3 from Pedro Ferreira --- Oh hi, Hm, sure I'll dig something up - been a while since I've had time to do any KDev hacking :( -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361613] Dropbox icons disappears completely when entry is hidden
https://bugs.kde.org/show_bug.cgi?id=361613 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- can't reproduce, dropbox gets loaded correctly in the popup for me. the problem is that it doesn't show the name, but seems that's dropbox not exporting it to dbus -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361614] Hidden visibility in system tray settings isn't remembered unless the entry is closed during the same session
https://bugs.kde.org/show_bug.cgi?id=361614 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- does this happen only for entries that are applications or also entries that are plasmoids? (such as audio,battery, clipboard) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361614] Hidden visibility in system tray settings isn't remembered unless the entry is closed during the same session
https://bugs.kde.org/show_bug.cgi?id=361614 --- Comment #2 from irli...@gmail.com --- After some more investigation, it seems that the hiddenItems field in the configuration file ~/.config/plasma-org.kde.plasma.desktop-appletsrc seems to be populated with more and more entries: "hiddenItems=10485813,50335619,35651636,41944964,35651637,48236384,58720275,qBittorrent,71303177,41943911,46137352,37748789,54525956,35651682,44040200,39845940,33554485,48234515,46137348,48234500,69217378,37748834,60820430,62916533,62919417,62949545,58720260,46137407,QuiteRss,83886307,50331667,60817417,60817412,48234559,52429027,52428804,39846001,44040419,41943048,117441896,144703551,44040255,94371903,83886089,39846115,35651697,12583897,41943267,48234504,62914569,50331652" I suspect this to be the root of the problem. Somehow the mechanism to detect the same application across sessions fails to work properly: known applications, for which visibility has been specifically configured, are not recognized and a new identifier is created. It only happens for entries that are applications. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361613] Dropbox icons disappears completely when entry is hidden
https://bugs.kde.org/show_bug.cgi?id=361613 --- Comment #2 from irli...@gmail.com --- I created two bug reports, the other one here: https://bugs.kde.org/show_bug.cgi?id=361614. I am pretty sure that I created this one erroneously, as this is seems to be a symptom of my other bug report. Sorry about this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361614] Hidden visibility in system tray settings isn't remembered unless the entry is closed during the same session
https://bugs.kde.org/show_bug.cgi?id=361614 --- Comment #3 from irli...@gmail.com --- To elaborate on this: "The hidden visibility setting in the system tray settings window aren't saved unless the application represented by the entry is closed once during the session in which the changes have been made."; I know believe this to be inaccurate and something else (the identifier generation) is responsible for it working or not. Sometimes it does, often a new identifier is created and it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 krasno changed: What|Removed |Added CC||krasnog...@gmail.com --- Comment #37 from krasno --- I'm also having this issue. Current Arch with nvidia 361.28 on gk110 chip. I have compositing enabled. When I launch a fullscreen shooter, the compositing turnes off(I don't know why, the option to turn it of for fullscreen apps is unchecked), when compsiting return after I exit the game, I have black borders around unmaximized windows. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361708] New: System stuck in ac-plugged in mode ignoring Power management rules
https://bugs.kde.org/show_bug.cgi?id=361708 Bug ID: 361708 Summary: System stuck in ac-plugged in mode ignoring Power management rules Product: Powerdevil Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: sud...@sudhirkhanger.com I have noticed it several times that my system won't go into any of the power states like suspend or hibernate according to the rules set in Power management settings. The battery icon will be stuck in ac-plugged in state where as on expanding it, it would show the battery is discharging. This is very bad because system will eventually shut down and I will lose all my work. Reproducible: Sometimes Actual Results: Power management settings are ignored. System doesn't go into suspend or hibernate as per power management settings. Battery icon shows charging where as on expanding it shows discharging. System suspends and hibernates fine via Plasma menu options or via systemctl but not automatically as per power management settings. $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Wednesday 13 April 2016 09:31:19 AM IST (16286 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: SANYO model:42T4763 serial: 13920 power supply: yes updated: Wednesday 13 April 2016 02:02:33 PM IST (12 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 13.07 Wh energy-empty:0 Wh energy-full: 27.43 Wh energy-full-design: 47.52 Wh energy-rate: 0.415 W voltage: 11.234 V time to empty: 31.5 hours percentage: 47% capacity:57.7231% technology: lithium-ion icon-name: 'battery-good-symbolic' History (charge): 1460536353 47.000 discharging History (rate): 1460536353 0.415 discharging Device: /org/freedesktop/UPower/devices/mouse_0003o046DoC52Fx0002 native-path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:046D:C52F.0002 vendor: Logitech, Inc. model:M185 serial: 03E8C0B4 power supply: no updated: Wednesday 13 April 2016 02:02:33 PM IST (12 seconds ago) has history: yes has statistics: no mouse present: no rechargeable:yes state: unknown warning-level: none percentage: 70% icon-name: 'battery-missing-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Wednesday 13 April 2016 02:02:33 PM IST (12 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: none energy: 13.07 Wh energy-full: 27.43 Wh energy-rate: 0.415 W time to empty: 31.5 hours percentage: 47% icon-name: 'battery-good-symbolic' Daemon: daemon-version: 0.99.3 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 331963] KDE Telepathy rename contact - no way to change contact name and avatar
https://bugs.kde.org/show_bug.cgi?id=331963 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #8 from Martin Riethmayer --- Would it be possible to have a temporary solution with some kind of "merge" strategy? It's been more than 2 years now for (quote) "One of the most requested features in KDE Telepathy" and this is still not possible. I trust that the overall design and pairing with the PIM-stack is a really good idea in the long term, however it's blocking the development of important features, it seems. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 327320] No-breaking space not visible
https://bugs.kde.org/show_bug.cgi?id=327320 Nick Shaforostoff changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #38 from Thomas Lübking --- > When I launch a fullscreen shooter In particular? > I don't know why, the option to turn it of for fullscreen apps is unchecked Because the game asks for it, this has nothng to do with fullscreen unredirection. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 361670] Highlighting special (formatting/layouting) chars in sources/translations
https://bugs.kde.org/show_bug.cgi?id=361670 --- Comment #1 from Nick Shaforostoff --- non-breakable space is already being highlighted with light grey (there is even bug 327320 and bug 360823 about that) -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 356133] crash when starting - segmentation fault
https://bugs.kde.org/show_bug.cgi?id=356133 --- Comment #9 from maj...@outlook.sk --- $ pacman -Q kamoso kamoso 3.1.0-2 in this version, there is no segfault -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #39 from krasno --- I launch steam with this: _GLVND_DISALLOW_PATCHING=1 steam because of a bug in nvidia driver right now. Then I launch "Fistful of Frags" from steam. >Because the game asks for it, this has nothng to do with fullscreen >unredirection. Umm, ok. It's just unfamiliar to me. I used Unity before, when this game was Alt-tabbed from, I had full compositing. Probably Unity turns it on when not in the game... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361556] Plasma crash after using xkill
https://bugs.kde.org/show_bug.cgi?id=361556 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||notm...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 360888 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 360888] Crash just after plasma launches
https://bugs.kde.org/show_bug.cgi?id=360888 Marco Martin changed: What|Removed |Added CC||philant...@exherbo.org --- Comment #1 from Marco Martin --- *** Bug 361556 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 356133] crash when starting - segmentation fault
https://bugs.kde.org/show_bug.cgi?id=356133 --- Comment #10 from Raghavendra kamath --- I have the same version , but i get the segfault like earlier. a month ago it started working but died again , My graphic card is nvidia and i don't remember if the drivers got updated -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 361555] Plasma crashed when closing the Network Manager applet
https://bugs.kde.org/show_bug.cgi?id=361555 Marco Martin changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|jgrul...@redhat.com CC||lu...@kde.org, ||notm...@gmail.com Component|general |applet Target Milestone|1.0 |--- Product|plasmashell |plasma-nm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361553] Plasma crash on startup when switching between tty and plasma
https://bugs.kde.org/show_bug.cgi?id=361553 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 348812 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348812] Crash in __strstr_sse2 after QSGRenderContext::initialize(QOpenGLContext*)
https://bugs.kde.org/show_bug.cgi?id=348812 Marco Martin changed: What|Removed |Added CC||adrien1...@live.fr --- Comment #41 from Marco Martin --- *** Bug 361553 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361518] playing with add widget plasma 5.6.1 crash
https://bugs.kde.org/show_bug.cgi?id=361518 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE CC||notm...@gmail.com --- Comment #1 from Marco Martin --- can you try to reproduce with KPackage debug symbols installed? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361709] New: With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 Bug ID: 361709 Summary: With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: elk...@yahoo.com If you have more than 1 curve based assistant, e.g. Fish Eye Point, Spline, Concentric Ellipse, zooming in will black screen part or all of the drawing window. It can be any combination of curved based assistants. For example, 2 Fish Eyes, 1 Spline & ! Fish Eye, 1 Concentric & 1 Spline will all cause the problem. The zoom factor at which this happens varies, but I believe it has to do with the position of the assistants' control points. Once a certain number of them are no longer visible in the UI the error is triggered. This does not happen with line based assistants, like Vanishing Point, Parallel Ruler, etc., but can happen with Perspective grid. Turning off Open GL eliminates the black screening of the drawing window, but without it the assistant preview lines don't function and the cursor leaves a 'permanent' light gray trail. This trail is strictly a display error and not part of the image, and can be removed by re-enabling OGL. Happens with both Windows 7 64bit SP 1 & Linux Mint 17 LTS, Nvidia 750 Ti This does NOT happen with Krita 2.9.11, so I assume it has something to do with the switch to QT. Reproducible: Always Steps to Reproduce: 1.Make at least 2 curve based assistants. Putting control points outside of the image will make it happen at lower zooms 2.Zoom in. Actual Results: Black screened drawing window Expected Results: Display the drawing window normally -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361513] Crash when switching windows shortly after disconnecting HDMI
https://bugs.kde.org/show_bug.cgi?id=361513 Marco Martin changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|h...@kde.org CC||notm...@gmail.com Component|general |Task Manager -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 351438] scale max volume value to more than 100%
https://bugs.kde.org/show_bug.cgi?id=351438 krasno changed: What|Removed |Added CC||krasnog...@gmail.com --- Comment #2 from krasno --- Very important issue to me. I stopped using physical controls after some pretty nasty ear pain from unanticipated loud sounds. Now I set my devices to level below pain threshold, and use overdrive for quiet sources. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361519] Plasmashell crashed after resume from suspend with connected external monitor
https://bugs.kde.org/show_bug.cgi?id=361519 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- can it be reproduced with console output as well? (to see what exactly is the assert being hit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361673] systemmonitor detailed view : breeze-dark unreadable
https://bugs.kde.org/show_bug.cgi?id=361673 --- Comment #2 from Marco Martin --- the screenshot seems empty. what applet exactly is giving the problem? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361673] systemmonitor detailed view : breeze-dark unreadable
https://bugs.kde.org/show_bug.cgi?id=361673 --- Comment #3 from Bruno Friedmann --- Created attachment 98371 --> https://bugs.kde.org/attachment.cgi?id=98371&action=edit systemmonitor with breeze-dark theme detailed view -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361673] systemmonitor detailed view : breeze-dark unreadable
https://bugs.kde.org/show_bug.cgi?id=361673 --- Comment #4 from Bruno Friedmann --- Sorry Martin, get caught by a spectale bug ;-) The new screenshot should better show the problem in the detailled view as described in the report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361629] No feedback when clicking on clipboard history item
https://bugs.kde.org/show_bug.cgi?id=361629 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/plas ||ma-workspace/edd301531af3a9 ||7b57bd8104bc4fabc9dd25a104 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-workspace/ddcf590f968f9b ||11c392208bf05f4b2072c6e334 --- Comment #1 from Marco Martin --- Git commit edd301531af3a97b57bd8104bc4fabc9dd25a104 by Marco Martin. Committed on 13/04/2016 at 09:20. Pushed by mart into branch 'master'. close popup upon item select klipper follows the pattern of a menu, in order to be consistent with other applets that use this pattern (like launchers or device notifier) close the menu after cliching on an item to show the user something happened M +4-1applets/clipboard/contents/ui/ClipboardItemDelegate.qml http://commits.kde.org/plasma-workspace/edd301531af3a97b57bd8104bc4fabc9dd25a104 --- Comment #2 from Marco Martin --- Git commit ddcf590f968f9b11c392208bf05f4b2072c6e334 by Marco Martin. Committed on 13/04/2016 at 09:18. Pushed by mart into branch 'Plasma/5.6'. close popup upon item select klipper follows the pattern of a menu, in order to be consistent with other applets that use this pattern (like launchers or device notifier) close the menu after cliching on an item to show the user something happened M +4-1applets/clipboard/contents/ui/ClipboardItemDelegate.qml http://commits.kde.org/plasma-workspace/ddcf590f968f9b11c392208bf05f4b2072c6e334 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361629] No feedback when clicking on clipboard history item
https://bugs.kde.org/show_bug.cgi?id=361629 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/plas ||ma-workspace/edd301531af3a9 ||7b57bd8104bc4fabc9dd25a104 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-workspace/ddcf590f968f9b ||11c392208bf05f4b2072c6e334 --- Comment #1 from Marco Martin --- Git commit edd301531af3a97b57bd8104bc4fabc9dd25a104 by Marco Martin. Committed on 13/04/2016 at 09:20. Pushed by mart into branch 'master'. close popup upon item select klipper follows the pattern of a menu, in order to be consistent with other applets that use this pattern (like launchers or device notifier) close the menu after cliching on an item to show the user something happened M +4-1applets/clipboard/contents/ui/ClipboardItemDelegate.qml http://commits.kde.org/plasma-workspace/edd301531af3a97b57bd8104bc4fabc9dd25a104 --- Comment #2 from Marco Martin --- Git commit ddcf590f968f9b11c392208bf05f4b2072c6e334 by Marco Martin. Committed on 13/04/2016 at 09:18. Pushed by mart into branch 'Plasma/5.6'. close popup upon item select klipper follows the pattern of a menu, in order to be consistent with other applets that use this pattern (like launchers or device notifier) close the menu after cliching on an item to show the user something happened M +4-1applets/clipboard/contents/ui/ClipboardItemDelegate.qml http://commits.kde.org/plasma-workspace/ddcf590f968f9b11c392208bf05f4b2072c6e334 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361710] New: TaskManager wrongly render Gtk-based application
https://bugs.kde.org/show_bug.cgi?id=361710 Bug ID: 361710 Summary: TaskManager wrongly render Gtk-based application Product: plasmashell Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: xiangzha...@gmail.com CC: plasma-b...@kde.org The screenshot shown as https://twitter.com/xiangzhai/status/720179947868794880 TaskManager correctly render Qt5.6.1 based application such as dolphin and konsole, but wrong for pidgin and thunderbird. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361704] window on external screen disappears when hibernating with external screen connected and resuming when it is not connected
https://bugs.kde.org/show_bug.cgi?id=361704 --- Comment #3 from Martin Steigerwald --- Hmmm, I didn´t see any kwin_x11 crashes. Maybe not reported by Dr. Konqi? I will try the xwinfo -root -tree thing next time and post here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #11 from Mateusz --- It's strange. I think it happens more often when I have second display connected using HDMI. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361710] TaskManager wrongly render Gtk-based application
https://bugs.kde.org/show_bug.cgi?id=361710 --- Comment #1 from Leslie Zhai --- It is pidgin`s ***SUB*** window, such as chat group window, ***NOT*** the main pidgin window, taskmanager is able to render correctly for main window! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361624] notifications exceed screen, hiding close button, so that they can not be closed manually
https://bugs.kde.org/show_bug.cgi?id=361624 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #2 from Marco Martin --- may be a good idea to make the TextEdit have a maximum height and clip the text in those cases? (even if it will look bad, but at least would be usable) being the body potentially html isprobably not safe to just cut the string -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361623] Notifications is shown in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=361623 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- is there a second screen connected? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions
https://bugs.kde.org/show_bug.cgi?id=341497 --- Comment #57 from Martin Steigerwald --- Just to make it clear here, the QT-BUG – https://bugreports.qt.io/browse/QTBUG-42985 – also refers to disappearing windows, not just crashes. From reading from the QTBUG I bet the issue is fixed in Qt 5.5.1 with patches and hopefully in 5.6. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361704] window on external screen disappears when hibernating with external screen connected and resuming when it is not connected
https://bugs.kde.org/show_bug.cgi?id=361704 --- Comment #4 from Thomas Lübking --- it's not a kwin crash. *every* qt5 client is prone to segfault or misbehave on randr events (in this case konsole/kmail) it's not really a dupe, just belongs into the same epic qt5 let-down -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 361670] Highlighting special (formatting/layouting) chars in sources/translations
https://bugs.kde.org/show_bug.cgi?id=361670 --- Comment #2 from Friedrich W. H. Kossebau --- Created attachment 98372 --> https://bugs.kde.org/attachment.cgi?id=98372&action=edit Screenshot: no-break space highlighting almost invisible -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Jan Grulich changed: What|Removed |Added CC||franz.berges...@gmail.com --- Comment #86 from Jan Grulich --- *** Bug 361555 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 361555] Plasma crashed when closing the Network Manager applet
https://bugs.kde.org/show_bug.cgi?id=361555 Jan Grulich changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jgrul...@redhat.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 346118 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361531] Clicking notification popup no longer hides it
https://bugs.kde.org/show_bug.cgi?id=361531 Marco Martin changed: What|Removed |Added Latest Commit||http://commits.kde.org/plas ||ma-workspace/2826b64fe98025 ||446c84f5b2c87a0f3ad3358b75 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Marco Martin --- Git commit 2826b64fe98025446c84f5b2c87a0f3ad3358b75 by Marco Martin. Committed on 13/04/2016 at 10:54. Pushed by mart into branch 'master'. use MouseEventListener to close popup on click restore plasma 4 behavior on correctly closing the notification popup when clicking anywhere on it. only on master as requires recent frameworks to work correctly. M +3-1applets/notifications/package/contents/ui/NotificationPopup.qml http://commits.kde.org/plasma-workspace/2826b64fe98025446c84f5b2c87a0f3ad3358b75 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 360777] Due to faulty configuration desktop loading time is ~20 seconds longer
https://bugs.kde.org/show_bug.cgi?id=360777 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO --- Comment #3 from David Edmundson --- >After some updates and testing various widgets i have noticed that my desktop >is loading ~ 20 seconds longer (screen after sddm) - progress bar reaches 100% >and than waits mention time. does it affect the time when running: - kquitapp5 plasmashell - plasmashell ? -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 361677] Kleopatra does not accept IDNA encoded domains for E-Mail address
https://bugs.kde.org/show_bug.cgi?id=361677 --- Comment #2 from K. Frör --- Thanks a lot for your help, I will try that. Karin __ 616982100/890050768 Dipl.-Psych. Karin Frör Hauptstr. 68 73087 Bad Boll Tel.: 07164/7997911 Fax: 07164/7999043 kontakt@praxis-frör.de -Ursprüngliche Nachricht- Von: Andre Heinecke via KDE Bugzilla [mailto:bugzilla_nore...@kde.org] Gesendet: Dienstag, 12. April 2016 18:23 An: kontakt@praxis-frör.de Betreff: [kleopatra] [Bug 361677] Kleopatra does not accept IDNA encoded domains for E-Mail address https://bugs.kde.org/show_bug.cgi?id=361677 Andre Heinecke changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Summary|When I try to create my |Kleopatra does not accept |personal key for the GpgOL |IDNA encoded domains for |certificate, my e-mail is |E-Mail address |not accepted| --- Comment #1 from Andre Heinecke --- Thanks for your report. I can reproduce your Problem with Kleopatra and it works with GnuPG on the command line so this is indeed a Bug in Kleopatra. As a workaround you can use gnupg directly from the command line. Start the command line window cmd.exe Enter: gpg2 --gen-key And follow the instructions to generate your Certificate this will accept kont...@xn--praxis-frr-mcb.de Alternatively you can use --edit-key and the adduid command to add a user ID to your existing key. Just search the web for "GnuPG adduid windows" and you should find something. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 361570] krdc-16.03.90: fullscreen mode does not survive minimizing window
https://bugs.kde.org/show_bug.cgi?id=361570 brancaleone changed: What|Removed |Added CC||cedric.devill...@gmail.com --- Comment #1 from brancaleone --- For your information, i can confirm the same problem with krdc recently upgraded to 16.03.90 It's quite problematic because then you can still maximise the windows, but KRDC "top bar" is lost and you cannot exit the fullscreen windows or change server easily. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 347022] Unable to setup wacom tablet - widget missing
https://bugs.kde.org/show_bug.cgi?id=347022 spamgoesh...@tutanota.com changed: What|Removed |Added CC||spamgoesh...@tutanota.com --- Comment #17 from spamgoesh...@tutanota.com --- Is it possible that these settings will be back in the near future? I really want to jump on the Plasma 5 wagon, but I can't, xsetwacom is too much of a hustle. I have not seen such convenient way to set graphic tablets in any other DE. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 361670] More contrast for highlighting of special (formatting/layouting) chars in sources/translations
https://bugs.kde.org/show_bug.cgi?id=361670 Friedrich W. H. Kossebau changed: What|Removed |Added Summary|Highlighting special|More contrast for |(formatting/layouting) |highlighting of special |chars in|(formatting/layouting) |sources/translations|chars in ||sources/translations --- Comment #3 from Friedrich W. H. Kossebau --- Oh, indeed you are right, there is highlighting already. But then I have to still request a change (and thus changed the bug title now): at least to me the highlighting is barely noticeable with my current color scheme (which is the default of Plasma 5.6), as the initial bug report proves. And my eyes are not that bad :) Please consider improving the contrast a little bit with any color schemes. See the attached screenshot, at least on my IPS display of my X220 I have to look 3x times to notice the highlight with bright color schemes (like the default Breeze theme of Plasma 5.6). It's clearly visible with dark schemes, but not with most(?) bright ones. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361711] New: can't close discover after update
https://bugs.kde.org/show_bug.cgi?id=361711 Bug ID: 361711 Summary: can't close discover after update Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PackageKit Assignee: aleix...@kde.org Reporter: sit...@kde.org did an update - packagekitd seems fairly idle - discover lists no updates (anymore) - progress bar still stuck at 'updating' - can't close discover since it says there are still tasks in the queue apt hasn't seen an upgrade for 15 minutes > $ date && apt-history upgrade |tail -1 > Wed Apr 13 13:00:27 CEST 2016 > 2016-04-13 12:42:39 upgrade qtdeclarative5-xmllistmodel-plugin:amd64 > 5.5.1-2ubuntu5 5.5.1-2ubuntu6 $ dpkg -s packagekit |grep Vers Version: 1.1.0-2+16.04+build2 discover master from an hour ago Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Insane virtual memory consumption and icon-cache mappings
https://bugs.kde.org/show_bug.cgi?id=361521 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #2 from Marco Martin --- any particular applet loaded? i have always only one icon cache line even after several hours running -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361712] New: discover-exporter is a dev util but can be translated
https://bugs.kde.org/show_bug.cgi?id=361712 Bug ID: 361712 Summary: discover-exporter is a dev util but can be translated Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sit...@kde.org plasma-discover-exporter is a development util not installed by default, but it can and is being translated. translations are subsequently installed regardless of whether or not the exporter was built. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361451] Wrong frequency is set after plugging different monitor
https://bugs.kde.org/show_bug.cgi?id=361451 Marco Martin changed: What|Removed |Added Component|general |common CC||notm...@gmail.com Assignee|k...@davidedmundson.co.uk|se...@kde.org Product|plasmashell |KScreen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361393] 15.10 ---> 16.04 Release Upgrade Hangs (Mime Configuration)
https://bugs.kde.org/show_bug.cgi?id=361393 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361624] notifications exceed screen, hiding close button, so that they can not be closed manually
https://bugs.kde.org/show_bug.cgi?id=361624 --- Comment #3 from Marco Martin --- related to https://bugs.kde.org/show_bug.cgi?id=361389 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content
https://bugs.kde.org/show_bug.cgi?id=361389 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- related to https://bugs.kde.org/show_bug.cgi?id=361624 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Insane virtual memory consumption and icon-cache mappings
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #3 from Laurent Bonnaud --- I use two non default applets: - system load - weather applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361624] notifications exceed screen, hiding close button, so that they can not be closed manually
https://bugs.kde.org/show_bug.cgi?id=361624 --- Comment #4 from Cyril Brosch --- Arrg, sorry for the duplicate, I didn't find #361389 although I searched for "notification"?! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361296] draggable objects don't move at the same speed as mouse input
https://bugs.kde.org/show_bug.cgi?id=361296 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- that's because in Qt xcb it seems drag windows are marked as tooltips, that's wrong (tooltip animation KWin effect gets triggered for them) Martin: any idea how to heuristically detect such windows? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 --- Comment #8 from eliotJ --- Yes. I confirm this... Windows 7 64 bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content
https://bugs.kde.org/show_bug.cgi?id=361389 Cyril Brosch changed: What|Removed |Added CC||i...@cyrilbrosch.net --- Comment #2 from Cyril Brosch --- *** Bug 361624 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361624] notifications exceed screen, hiding close button, so that they can not be closed manually
https://bugs.kde.org/show_bug.cgi?id=361624 Cyril Brosch changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #5 from Cyril Brosch --- *** This bug has been marked as a duplicate of bug 361389 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361296] draggable objects don't move at the same speed as mouse input
https://bugs.kde.org/show_bug.cgi?id=361296 Marco Martin changed: What|Removed |Added Component|general |effects-various Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org Target Milestone|1.0 |--- Product|plasmashell |kwin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361325] Immense problems and inconsistencies in shortcut dialog, changes in shortcuts are not saved too
https://bugs.kde.org/show_bug.cgi?id=361325 eliotJ changed: What|Removed |Added CC||os...@jadamspam.pl --- Comment #6 from eliotJ --- I confirm this bug... Win 7 64 bit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361531] Clicking notification popup no longer hides it
https://bugs.kde.org/show_bug.cgi?id=361531 --- Comment #2 from Martin Klapetek --- Now couple things - it was actually never really intended to have close-to-click in Plasma 5 popus for various usability reasons and then since recently the popus have selectable text as a feature. That one must remain working. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361713] New: Unable to save changes when modifying Krita Configuration
https://bugs.kde.org/show_bug.cgi?id=361713 Bug ID: 361713 Summary: Unable to save changes when modifying Krita Configuration Product: krita Version: 3.0 Alpha Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: jaquematealakal...@gmail.com I was trying to modify Krita shortcuts in order to make them work as I'm used to. The Configuration Widow pops up, everything is fine... Also I'm able to introduce the new shortcuts without a problem. However, as soon as I hit the OK button and the widow closes, Krita does not apply those changes. What is more, when I open the configuration window again, the shortcuts remain as default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361713] Unable to save changes when modifying Krita Configuration
https://bugs.kde.org/show_bug.cgi?id=361713 --- Comment #1 from Kalesi --- Sorry, I found someone else had reported this bug alredy... Mea culpa -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor
https://bugs.kde.org/show_bug.cgi?id=344076 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #8 from S. Bryant --- I'm using Plasma 5.6.2 on OpenSUSE Leap, and the problem is very much still there. When I connect my external screen to the laptop, the panel from the laptop screen may get moved to the external screen (or moved back if it was on the external screen). The panel on the external screen doesn't get moved. Connecting/disconnecting the external screen prior to X starting results in the same behaviour as doing so after logging in. Moving a panel to a specific display/position seemed to help for the remainder of that session, but the behavour reverted at the next login. Disconnecting the external screen leaves the panels where they are. While this bug's problem description could be counted as solved, the underlying issue is not. This problem was never correctly addressed in the previous generation of the software, as there are two opposing use cases: 1. having a panel that always remain visible, and automatically changes screen to do so (and returns to the user's preferred screen when it becomes available again). This is probably what a user expects when a single panel is in use; Windows also works like this. 2. having panels tied to specific screens, and being unreachable if that particular screen is not connected. My recommendations: On screen disconnect, there should be a check that at least one panel remains visible - if not, the first panel should be moved (but the lastScreen setting should not be altered). On screen connect, each panel should be moved to its 'lastScreen' if there is no panel already at that position on that screen. The lastScreen setting should only be updated when a panel is created or when the user explicitly moves the panel to a different screen. (Not sure if this is currently the case.) -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 350571] kdebugdialog fails to complete (login greyed out)
https://bugs.kde.org/show_bug.cgi?id=350571 Paschalis Veskos changed: What|Removed |Added CC||ves...@gmail.com --- Comment #6 from Paschalis Veskos --- duplicate of #354292 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 350571] kdebugdialog fails to complete (login greyed out)
https://bugs.kde.org/show_bug.cgi?id=350571 --- Comment #7 from Paschalis Veskos --- Can confirm this (every time) on opensuse 42.1, plasma 5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 242137] Valgrind on LLVM compiled code reports tons of 'Conditional jump or move depends on uninitialised' false positives
https://bugs.kde.org/show_bug.cgi?id=242137 --- Comment #33 from Julian Seward --- Those checks are enabled now by --expensive-definedness-checks=yes, which was introduced in 3.11.0. --expensive-definedness-checks=no|yes Use extra-precise definedness tracking [no] There's still a problem with LLVM optimised code though, and to some extent also with gcc. Both of these compilers will now sometimes compile if (a && b) ... as if it was written if (b && a) in the case that they can prove that a is always false whenever b is undefined. The transformation is correct but it means that there is a branch on uninitialised data and so Memcheck complains (wrongly.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358418] Alignment of widgets to grid can prevent optimal sizes and alignments for some widgets.
https://bugs.kde.org/show_bug.cgi?id=358418 Nick Stefanov changed: What|Removed |Added CC||m...@abv.bg --- Comment #3 from Nick Stefanov --- It would be nice to have option to enable or disable grid as it was in KDE 4. Lack of such feature is a bad idea. This is the only reason that prevents me to migrate to Plasma 5 and I know a lot of other people with the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361714] New: Kontact/Korganizer crashes when changing email link
https://bugs.kde.org/show_bug.cgi?id=361714 Bug ID: 361714 Summary: Kontact/Korganizer crashes when changing email link Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: crgla...@gmail.com Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I have two instances of a Google calendar showing. Not sure why as I only added one calendar. When trying to unselect one copy infavor of the other events will temporarily show but then Korganizer produces this crash. Has been happening repeatedly for three days. I have used Akonadiconnsole to remove the calendars, rebooted, and tried to instal only one calendar. However two instances show. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54fc3bd840 (LWP 3855))] Thread 33 (Thread 0x7f54dd9ce700 (LWP 3856)): #0 0x7f54f8ffbbbd in poll () from /lib64/libc.so.6 #1 0x7f54f279a422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f54f279c00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f54e01503c9 in QXcbEventReader::run (this=0x1b7d1a0) at qxcbconnection.cpp:1229 #4 0x7f54f990b32f in QThreadPrivate::start (arg=0x1b7d1a0) at thread/qthread_unix.cpp:331 #5 0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f54f9003fed in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f54d664d700 (LWP 3858)): #0 0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f54f6b5a733 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f54f6b5a759 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f54f9003fed in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f548d30d700 (LWP 3862)): #0 0x7f54f8ffbbbd in poll () from /lib64/libc.so.6 #1 0x7f54f1b59e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f54f1b59f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f54f9b3dd8b in QEventDispatcherGlib::processEvents (this=0x7f54880008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f54f9ae4d53 in QEventLoop::exec (this=this@entry=0x7f548d30cd90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f54f990661a in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f54f990b32f in QThreadPrivate::start (arg=0x1ca6a90) at thread/qthread_unix.cpp:331 #7 0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f54f9003fed in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f54877a4700 (LWP 3863)): #0 0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f54f686675d in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f54f9003fed in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f5486fa3700 (LWP 3864)): #0 0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f54f6867733 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f54f9003fed in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f54867a2700 (LWP 3865)): #0 0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f54f6867733 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f54f9003fed in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f5485fa1700 (LWP 3866)): #0 0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f54f6867733 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f54f9003fed in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f546c795700 (LWP 3867)): #0 0x7f54f237d79c in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x7f54f23794a4 in _L_lock_986 () from /lib64/libpthread.so.0 #2 0x7f54f2379306 in pthread_mutex_lock () from /lib64/libpthread.so.0 #3 0x7f54f11d404c in ?? () from /usr/X11R6/lib64/libGL.so.1 #4 0x7f54f11d8f21 in ?? () from /usr
[kontact] [Bug 361714] Kontact/Korganizer crashes when changing email link
https://bugs.kde.org/show_bug.cgi?id=361714 Chris changed: What|Removed |Added CC||crgla...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361714] Kontact/Korganizer crashes when changing email link
https://bugs.kde.org/show_bug.cgi?id=361714 --- Comment #1 from Chris --- Created attachment 98373 --> https://bugs.kde.org/attachment.cgi?id=98373&action=edit New crash information added by DrKonqi kontact (5.1.3) using Qt 5.5.1 I removed all instances of Google calendars using Akonadiconsole. However the calendars still appear in Korganizer. Any attempt to unselect an email address within the calendar in Korganizer causes this crash. Re-establishing an agent in Akonadiconsole creates a second instance of the calendar in KOrganizer. There is noway to tell which calendar is from Akonadiconsole though. And deleting within KOrganizer does not work on either calendar. -- Backtrace (Reduced): #7 0x7f3d4b33c16f in KCalCore::Calendar::notifyIncidenceDeleted (this=this@entry=0x24324f0, incidence=...) at /usr/src/debug/kcalcore-16.03.90/src/calendar.cpp:1346 #8 0x7f3d4b381fcc in KCalCore::MemoryCalendar::deleteIncidence (this=0x24324f0, incidence=...) at /usr/src/debug/kcalcore-16.03.90/src/memorycalendar.cpp:196 [...] #12 0x7f3dd0a4f73f in call (a=0x7ffca51d7110, r=0x242af30, this=0x2456c70) at ../../src/corelib/kernel/qobject_impl.h:124 [...] #15 0x7f3dd0acea04 in QAbstractItemModel::rowsAboutToBeRemoved (this=this@entry=0x213e3f0, _t1=..., _t2=_t2@entry=0, _t3=_t3@entry=145) at .moc/moc_qabstractitemmodel.cpp:590 #16 0x7f3dd09cc044 in QAbstractItemModel::beginRemoveRows (this=0x213e3f0, parent=..., first=0, last=145) at itemmodels/qabstractitemmodel.cpp:2656 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361710] TaskManager wrongly render Gtk-based application
https://bugs.kde.org/show_bug.cgi?id=361710 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Eike Hein --- Please provide a better screenshot, I can't understand the one on Twitter (blurry mess, don't know what I am seeing). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361715] New: After wake up PC Krita crash
https://bugs.kde.org/show_bug.cgi?id=361715 Bug ID: 361715 Summary: After wake up PC Krita crash Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: os...@jadamspam.pl It crash directly after wake up PC and only after doing some little longer drawing / painting (for example 10 minutes) and with opened, active window of Krita. Without any opened file Krita doesn’t crash. I noticed also that Krita doesn’t crash if is minimalized to Windows taskbar (before goes to Windows sleep mode of course). I tested on Windows 7 64 bit, NVidia card. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 360374] Check for QString::left(1) mis-use.
https://bugs.kde.org/show_bug.cgi?id=360374 --- Comment #2 from Volker Krause --- I haven't found a valid use of left(1) yet, so an unconditional warning would probably be fine. In theory it differs from at(0) in that it returns a QString rather than a QChar, which doesn't matter for string concatenations or comparisons, but might be relevant in some other context. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361716] New: Duplicate suggestions in include file completion
https://bugs.kde.org/show_bug.cgi?id=361716 Bug ID: 361716 Summary: Duplicate suggestions in include file completion Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: aspotas...@gmail.com When I write #include "" and press Ctrl+Space inside the double quotes, I see a list of .h files where the .h from the current directory appear twice. Reproducible: Always I have several include directories set up manually in the project configuration, including the above mentioned current directory. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361543] KAlarm Automatically Creates New Calendar Named "akonadi_kalarm_resource_N+1" Every Time a New Calender is Created (Add)
https://bugs.kde.org/show_bug.cgi?id=361543 kdebugs.anon...@yahoo.com changed: What|Removed |Added CC||kdebugs.anon...@yahoo.com --- Comment #2 from kdebugs.anon...@yahoo.com --- Wow! :) Thank you very much for getting on this so quickly! :) :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 343362] Random crashes in KMail while being "inactive"
https://bugs.kde.org/show_bug.cgi?id=343362 Wolfgang Brehm changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Wolfgang Brehm --- It seems to me that it is either fixed or more probably was my fault all along. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361518] playing with add widget plasma 5.6.1 crash
https://bugs.kde.org/show_bug.cgi?id=361518 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #2 from Bruno Friedmann --- As the git has quite changed since 8th April I'm using plasma 5.6.90git~20160411T195322~cc3edde-18.1 now and libQt5Core5 5.6.1-11.1 has been rebuild and update on 11 April. I was unable to repoduce it this morning. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 273836] kde short cuts not working
https://bugs.kde.org/show_bug.cgi?id=273836 --- Comment #4 from Wolfgang Brehm --- For me the shortcuts are fixed in KDE5 on opensuse. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361578] Settings and Window menu absent from keyboard shortcut list
https://bugs.kde.org/show_bug.cgi?id=361578 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Markus, Thanks for your report. I can confirm the issue. I also think I know why this is: both menus are created outside the xmlgui system, so the configure shortcuts thing doesn't know about them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345696] when adding any monitor widget (CPU, MEM, NETWORK, I/O Disk) directly huge %CPU consomption with plasmashell process
https://bugs.kde.org/show_bug.cgi?id=345696 gamaro...@gmail.com changed: What|Removed |Added CC||gamaro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361717] New: KAlarm Crashes on Creation (Add) of New *.ics Calander File
https://bugs.kde.org/show_bug.cgi?id=361717 Bug ID: 361717 Summary: KAlarm Crashes on Creation (Add) of New *.ics Calander File Product: kalarm Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: djar...@kde.org Reporter: kdebugs.anon...@yahoo.com Application: kalarm (2.11.4-5ak) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I believe this is releated to Bug 361539. The bug reporter has a bug that would not let me continue after confirming this bug report is related to Bug 361539. - What I was doing when the application crashed: 1) Clicked the "Add" button in the column labeled "Calendars:. 2) Clicked the option labeled "KAlarm Calendar File". 3) KAlarm crashes. Version 2.11.4-5ak Using: KDE Frameworks 5.20.0 The xcb windowing system The crash can be reproduced sometimes. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd083080840 (LWP 2177))] Thread 4 (Thread 0x7fd06152e700 (LWP 2178)): #0 0x7fd07a5d in poll () from /lib64/libc.so.6 #1 0x7fd07490a422 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7fd07490c00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fd0638bf3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd07aed232f in QThreadPrivate::start (arg=0x1a58460) at thread/qthread_unix.cpp:331 #5 0x7fd074b270a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fd07a5c3fed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fd056f26700 (LWP 2204)): #0 0x7ffdda591d33 in clock_gettime () #1 0x7fd07a5d0c3d in clock_gettime () from /lib64/libc.so.6 #2 0x7fd07af837d6 in qt_clock_gettime (ts=0x7fd056f25b20, clock=) at tools/qelapsedtimer_unix.cpp:105 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #5 0x7fd07b1033b9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fd050002ed0) at kernel/qtimerinfo_unix.cpp:84 #6 0x7fd07b103945 in QTimerInfoList::timerWait (this=0x7fd050002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #7 0x7fd07b104b5e in timerSourcePrepareHelper (timeout=0x7fd056f25bd4, src=) at kernel/qeventdispatcher_glib.cpp:127 #8 timerSourcePrepare (source=, timeout=0x7fd056f25bd4) at kernel/qeventdispatcher_glib.cpp:160 #9 0x7fd0741da4ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7fd0741dad80 in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7fd0741daf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7fd07b104d8b in QEventDispatcherGlib::processEvents (this=0x7fd058e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #13 0x7fd07b0abd53 in QEventLoop::exec (this=this@entry=0x7fd056f25d90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #14 0x7fd07aecd61a in QThread::exec (this=) at thread/qthread.cpp:503 #15 0x7fd07aed232f in QThreadPrivate::start (arg=0x1b407d0) at thread/qthread_unix.cpp:331 #16 0x7fd074b270a4 in start_thread () from /lib64/libpthread.so.0 #17 0x7fd07a5c3fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fd0562be700 (LWP 2346)): #0 0x7fd07a5d in poll () from /lib64/libc.so.6 #1 0x7fd0741dae64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd0741daf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd07b104d8b in QEventDispatcherGlib::processEvents (this=0x7fd0480008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fd07b0abd53 in QEventLoop::exec (this=this@entry=0x7fd0562bdd90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd07aecd61a in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fd07aed232f in QThreadPrivate::start (arg=0x1c63a80) at thread/qthread_unix.cpp:331 #7 0x7fd074b270a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7fd07a5c3fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd083080840 (LWP 2177)): [KCrash Handler] #6 0x7fd07b075a26 in QSortFilterProxyModel::parent (this=0x1d5f9c0, child=...) at itemmodels/qsortfilterproxymodel.cpp:1874 #7 0x7fd07b053d63 in parent (this=) at itemmodels/qabstractitemmodel.h:411 #8 QPersistentModelIndex::parent (this=this@entry=0x7ffdda53dbb0) at itemmodels/qabstractitemmodel.cpp:365 #9 0x7fd07b064fd7 in mergeIndexes (indexes=...) at itemmodels/qitemselectionmodel.cpp:939 #10 0x7fd07b06aafe in QItemSelectionModelPrivate::_q_layoutChanged (this=0x1d4dc20, hint=) at itemmodels/qitemselectionmodel.cpp:1047 #11 0x7fd07b06b67b in QItemSelectionModel::qt_
[kalarm] [Bug 361539] KAlarm Crashes on Creation (Add) of New *.ics Calander File
https://bugs.kde.org/show_bug.cgi?id=361539 kdebugs.anon...@yahoo.com changed: What|Removed |Added CC||kdebugs.anon...@yahoo.com --- Comment #2 from kdebugs.anon...@yahoo.com --- Using: KDE Frameworks 5.20.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361577] Clone tool brush stroke causes crash
https://bugs.kde.org/show_bug.cgi?id=361577 --- Comment #4 from Boudewijn Rempt --- Ah, I can confirm, too. I was mislead because of the "you cannot select the only item in the resource selector bug"... And I was wondering why the clone tool painted black, too -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358328] Application systray icon: No context menu
https://bugs.kde.org/show_bug.cgi?id=358328 Māris Nartišs changed: What|Removed |Added CC||maris@gmail.com --- Comment #16 from Māris Nartišs --- I observe the same behaviour with Rachota app (http://rachota.sourceforge.net/en/index.html) - I see a blank square where icon should be and can not get any pop-up menu to appear. .xsession-errors: Could not find DBusMenu interface, falling back to calling ContextMenu() kde.xembedsniproxy: Received click 3 with passed x*y 1237 834 kde.xembedsniproxy: Received click 1 with passed x*y 1237 834 kde-apps/plasma-apps-15.08.3:4/15.08 kde-apps/plasma-runtime-15.12.3:4/15.12 kde-base/kdeplasma-addons-4.14.3:4/4.14 kde-base/libplasmaclock-4.11.22:4/4.11 kde-base/libplasmagenericshell-4.11.22:4/4.11 kde-frameworks/plasma-5.21.0:5/5.21 kde-plasma/plasma-desktop-5.6.2:5 kde-plasma/plasma-workspace-5.6.2:5 dev-libs/sni-qt-0.2.6-r1 dev-libs/libappindicator-12.10.0-r200 dev-libs/libappindicator-12.10.0-r300 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 361718] New: Support for Volume Overdrive like in KMix?
https://bugs.kde.org/show_bug.cgi?id=361718 Bug ID: 361718 Summary: Support for Volume Overdrive like in KMix? Product: plasma-pa Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: kcm Assignee: now...@gmail.com Reporter: irli...@gmail.com CC: plasma-b...@kde.org Hey, are there any plans to support the "Volume Overdrive" option found in the old KMix applet? It's the only way that my microphone is loud enough, since I couldn't find an easier option than to simply use KMix, which unfortunately isn't as well integrated into the Plasma shell as the actual audio applet. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 351438] scale max volume value to more than 100%
https://bugs.kde.org/show_bug.cgi?id=351438 David Rosca changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||now...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
