[kscreenlocker] [Bug 368884] Kscreenlocker locks screen for ever! (a critical bug)
https://bugs.kde.org/show_bug.cgi?id=368884 Martin Gräßlin changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|CONFIRMED |RESOLVED --- Comment #10 from Martin Gräßlin --- Thanks for the update. I don't think there is anything we can do from our side to protect against such situations in future. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 366625] Single event reported through multiple devices is not coalesced (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366625 Martin Gräßlin changed: What|Removed |Added Version Fixed In||5.27 Latest Commit||http://commits.kde.org/kway ||land/98628f9387ff9628b3c7c3 ||fa66b0db4b01ef67c8 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #7 from Martin Gräßlin --- Git commit 98628f9387ff9628b3c7c3fa66b0db4b01ef67c8 by Martin Gräßlin. Committed on 15/09/2016 at 07:35. Pushed by graesslin into branch 'master'. [server] Don't send key release for not pressed keys and no double key press Summary: This change makes use of the internal key state in better way. If a key is not considered pressed, no key release is sent. This can happen for example if the compositor grabs a key press (global shortcut) but not the release. The Wayland client cannot do anything with the release as it never got the press. Thus it doesn't make sense to send the release. Similar if a key is already pressed, it doesn't make sense to send another press event. This ensures that if the server sends in repeating key presses they are filtered out. Key repeat is handled on client side. Also if several physical keys send the same key code, pressing them at the same time won't send double press/release event. This change might cause regressions in KWin in case KWin does not handle the situation correctly. But that would be a bug in KWin which needs to be fixed there. If it causes regressions the bug might have shown in other situations as well. FIXED-IN: 5.27 Reviewers: #plasma_on_wayland, #kwin Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2786 M +15 -0autotests/client/test_wayland_seat.cpp M +12 -4src/server/seat_interface.cpp M +1-1src/server/seat_interface_p.h http://commits.kde.org/kwayland/98628f9387ff9628b3c7c3fa66b0db4b01ef67c8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368499] Panel option "windows can cover" doesn't work on wayland
https://bugs.kde.org/show_bug.cgi?id=368499 --- Comment #3 from Martin Gräßlin --- Git commit 7d93b585789f680e09f7d100a2b1ba1a2a182f56 by Martin Gräßlin. Committed on 16/09/2016 at 12:30. Pushed by graesslin into branch 'Plasma/5.8'. Fix whether a panel is supposed to have a strut in ShellClient Summary: The PanelBehavior was incorrectly mapped to hasStrut resulting in too many modes creating a strut for the panel. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2788 M +48 -0autotests/integration/plasma_surface_test.cpp M +1-1shell_client.cpp http://commits.kde.org/kwin/7d93b585789f680e09f7d100a2b1ba1a2a182f56 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368887] The "Note" plasmoid does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=368887 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |WORKSFORME CC||k...@privat.broulik.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kai Uwe Broulik --- Resize the note larger. There's something off with DPI/font calculations on Wayland right now, so the fonts are larger also increasing the minimum threshold for the applet to work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368887] The "Note" plasmoid does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=368887 --- Comment #2 from tro...@free.fr --- I can't resize the note widget on Wayland ; I can resize the content that appears near the Note, but it does not solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368887] The "Note" plasmoid does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=368887 --- Comment #3 from Kai Uwe Broulik --- Long-pressing the widget should reveal its handle where you can resize it? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368367] Dolphin Crashes on right-click for list-menu options
https://bugs.kde.org/show_bug.cgi?id=368367 --- Comment #1 from Thomas --- Created attachment 101121 --> https://bugs.kde.org/attachment.cgi?id=101121&action=edit New crash information added by DrKonqi dolphin (15.12.3) using Qt 5.6.1 - What I was doing when the application crashed: I right clicked on a videofile. It crashed even when I hit the options button on the keyboard to open the menu (when file is selected and that button is hit on the keyboard). - Custom settings of the application: ffmpegthumbs is installed and activated, previews are on. -- Backtrace (Reduced): #6 0x7f936ebf0204 in _GLOBAL__sub_I_qprinterinfo.cpp () from /lib64/libQtGui.so.4 #7 0x7f93a5e9773a in call_init.part () from /lib64/ld-linux-x86-64.so.2 #8 0x7f93a5e9784b in _dl_init () from /lib64/ld-linux-x86-64.so.2 #9 0x7f93a5e9c3a2 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2 #10 0x7f93a5e975e4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368367] Dolphin Crashes on right-click for list-menu options
https://bugs.kde.org/show_bug.cgi?id=368367 Thomas changed: What|Removed |Added CC||thomasatz...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368887] The "Note" plasmoid does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=368887 --- Comment #4 from tro...@free.fr --- Yes, you're right, resizing it makes it work. Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 302916] Print / Export looks extremely ugly for Task View
https://bugs.kde.org/show_bug.cgi?id=302916 Dag Andersen changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/call ||igra/9a6b2ce59d85eda2b7736d ||4a0c807409d69142b2 Resolution|--- |FIXED Version Fixed In||3.0 --- Comment #2 from Dag Andersen --- Git commit 9a6b2ce59d85eda2b7736d4a0c807409d69142b2 by Dag Andersen. Committed on 16/09/2016 at 12:56. Pushed by danders into branch 'master'. Plan: Fix printing treeviews Todo: Indent tree FIXED-IN:3.0 M +120 -19 plan/libs/ui/kptviewbase.cpp M +1-1plan/libs/ui/kptviewbase.h http://commits.kde.org/calligra/9a6b2ce59d85eda2b7736d4a0c807409d69142b2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368499] Panel option "windows can cover" doesn't work on wayland
https://bugs.kde.org/show_bug.cgi?id=368499 Martin Gräßlin changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-workspace/f0300cec3cbb5e ||2c3605d89a68a921ff2c90dd2c Resolution|--- |FIXED --- Comment #4 from Martin Gräßlin --- Git commit f0300cec3cbb5e2c3605d89a68a921ff2c90dd2c by Martin Gräßlin. Committed on 16/09/2016 at 12:58. Pushed by graesslin into branch 'Plasma/5.8'. [shell] Pass the panel visibility mode to KWayland PanelBehavior Summary: The visibility mode needs to be passed to KWayland by mapping to the PanelBehavior. This is required to pass the correct hint to KWin to adjust the layering, etc. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2789 M +27 -0shell/panelview.cpp M +1-0shell/panelview.h http://commits.kde.org/plasma-workspace/f0300cec3cbb5e2c3605d89a68a921ff2c90dd2c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368899] New: .desktop starter containing cmdline won't be executed anymore
https://bugs.kde.org/show_bug.cgi?id=368899 Bug ID: 368899 Summary: .desktop starter containing cmdline won't be executed anymore Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Dashboard Assignee: notm...@gmail.com Reporter: ila...@gmail.com CC: bhus...@gmail.com I've a desktop starter which opens a ssh connection. This did work before and suddenly it won't anymore. Tested on my workstation and notebook (both Arch Linux) here is the .desktop file: [Desktop Entry] Comment[de_DE]= Comment= Exec=ssh 192.168.1.123 -l foo GenericName[de_DE]= GenericName= Icon=/home/foo/Bilder/icons/NAS.png MimeType= Name[de_DE]=NAS Name=NAS Path=/home/foo/ StartupNotify=true Terminal=true TerminalOptions=\s--noclose Type=Application X-DBUS-ServiceName= X-DBUS-StartupType= X-KDE-SubstituteUID=false X-KDE-Username= Reproducible: Always Steps to Reproduce: 1. Create a new starter on desktop Enter a valid commandline. Set execute in terminal and keep window opened after program ended (in extended options) 2. Start the desktop shortcut from desktop 3. Actual Results: nothing Expected Results: open a terminal/konsole window and execute the commandline journalctl -xe klauncher[846]: -miniicon isn't supported anymore (service "NAS" ) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362575] Cannot unsubscribe IMAP folder
https://bugs.kde.org/show_bug.cgi?id=362575 Benoit Grégoire changed: What|Removed |Added CC||beno...@coeus.ca -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 356233] File is not writeable when creating a new collection
https://bugs.kde.org/show_bug.cgi?id=356233 godfried.borrem...@gmail.com changed: What|Removed |Added CC||godfried.borrem...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356138] vex amd64->IR unhandled instruction bytes 0x8F 0xEA 0x78 0x10 0xD2 0x6 0x6 0x0
https://bugs.kde.org/show_bug.cgi?id=356138 Julian Seward changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Julian Seward --- *** This bug has been marked as a duplicate of bug 339596 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339596] AMD64 fma4 and xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9
https://bugs.kde.org/show_bug.cgi?id=339596 --- Comment #21 from Julian Seward --- *** Bug 356138 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368698] Can't explore plasmoids with a touch screen
https://bugs.kde.org/show_bug.cgi?id=368698 --- Comment #4 from Thomas Pfeiffer --- (In reply to Kai Uwe Broulik from comment #3) > I said "That's a general problem with drag area and *touch*", behavior for > when using a mouse wouldn't change. Qt can tell when it's an actual mouse > click or a finger tap. I know, and my reply was based on that knowledge. Press-and-hold is just not a nice interaction, neither with touch nor with a mouse. But as I said, I think this is acceptable in a desktop environment which is not optimized for touch in general. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368900] New: Add the possibility for small pinned task entries
https://bugs.kde.org/show_bug.cgi?id=368900 Bug ID: 368900 Summary: Add the possibility for small pinned task entries Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: fab...@web2.0-apps.de CC: plasma-b...@kde.org It would be nice if one could create a list of applications for which the task manager shows always an icon only entry, to save space for other applications. Similar to pinned tabs in Firefox https://support.mozilla.org/en-US/kb/pinned-tabs-keep-favorite-websites-open?redirectlocale=en-US&redirectslug=what-are-app-tabs While I have multiple windows open of some applications, eg 4 firefox, firebug window, for which the title is very help full to activate the correct one, there are other application I "never" have multiple windows open, eg Ktp, Amarok, Kdevelop, KRDC, ... . A (small) icon only entry for those would be enough and there would be more space for the others. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356823] Unsupported ARM instruction: stlex
https://bugs.kde.org/show_bug.cgi?id=356823
Julian Seward changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Julian Seward ---
Fixed in r3248, along with its friends, LDAEX{,B,H,D}, STLEX{,B,H,D}.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 363060] Crash while opening recovered file at new startup
https://bugs.kde.org/show_bug.cgi?id=363060 thivel changed: What|Removed |Added CC||thive...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364583] Composition effect: Using the zoom produces black outlines
https://bugs.kde.org/show_bug.cgi?id=364583 --- Comment #6 from Wegwerf --- Which version of frei0r are you using? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362934] [AsusWRT] Arm v7 illegal instruction
https://bugs.kde.org/show_bug.cgi?id=362934 --- Comment #1 from Julian Seward --- What CPU/SOC is this? Do you know if it is NEON capable? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368901] New: Pressing ALT+f2 and entering exact executable name and pressing enter can run another program
https://bugs.kde.org/show_bug.cgi?id=368901 Bug ID: 368901 Summary: Pressing ALT+f2 and entering exact executable name and pressing enter can run another program Product: kwin Version: 5.7.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jonas@thiem.email Pressing ALT+f2 and entering exact executable name and pressing enter does sometimes run another program for me as default choice, I assume that program has that name assigned in the .desktop file but it's definitely not as a binary in the $PATH with that exact name (it's a wine program with .exe file extension). Reproducible: Always Steps to Reproduce: 1. Install a program that has the name of an executable in $PATH in the .desktop file which matches an existing binary, or a wine program Actual Results: Program with not the exact executable name gets sometimes picked as default choice when entering the name in ALT+f2 Expected Results: Entering an exact executable name in ALT+f2 and pressing enter must always run that program with that exact executalbe name as a default choice. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368901] Pressing ALT+f2 and entering exact executable name and pressing enter can run another program
https://bugs.kde.org/show_bug.cgi?id=368901 --- Comment #1 from Jonas Thiem --- Basically to give this some more context, I installed steam in wine and steam natively which has the exact name "steam" as system-wide binary. When I do ALT+f2, "steam", ENTER, I always expect the native one to launch since that is the exact name of the binary - however, right now that will launch the wine one. I think ranking stuff in order of use and other heuristics are very useful, but if I enter an exact existing binary name I highly expect that one to run always, no matter what sort of other interesting search results there might be... -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 362176] Parley can write lock file
https://bugs.kde.org/show_bug.cgi?id=362176 godfried.borrem...@gmail.com changed: What|Removed |Added CC||godfried.borrem...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364583] Composition effect: Using the zoom produces black outlines
https://bugs.kde.org/show_bug.cgi?id=364583 --- Comment #7 from Dany --- (In reply to Wegwerf from comment #6) > Which version of frei0r are you using? The one I find in Mint 18 (Cinnamon) repository. They write 1.5+git201604011602-0xenial1 Yesterday I opened a new bug report with ID 368875. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368902] New: Top-left cot corner doesn't work reliably when window extends to top-left corner
https://bugs.kde.org/show_bug.cgi?id=368902 Bug ID: 368902 Summary: Top-left cot corner doesn't work reliably when window extends to top-left corner Product: kwin Version: 5.7.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jonas@thiem.email The top-left cot corner doesn't work reliably when window extends to top-left corner. The cursor rapidly changes shape to resize cursor, grab cursor and normal cursor and jumps 1-2 px if you move it up there, with an apparent fight of the resize handler of the window corner and the hot corner of plasma. This means the hot corner action only works if you slam the cursor in there multiple times persistently, which makes it almost useless since it's not possible to use it reliably (and as a result it's super frustrating to use). Reproducible: Sometimes Steps to Reproduce: 1. Move a non-maximized window such that the upper left corner reaches the top-left corner of your desktop 2. Set an action to the top-left hot corner 3. Try to use it Actual Results: Sometimes the hot corner action works immediately, sometimes with a slight delay, sometimes I need to slam the cursor multiple times into the corner Expected Results: Hot corner always triggers as soon as cursor has reached the corner and is moved more towards corner. If anything like the window resize handle displaces the cursor for some reason, this must never interfere -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 357673] crash if I try to run valgrind with a binary link with libcurl
https://bugs.kde.org/show_bug.cgi?id=357673 Julian Seward changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Julian Seward --- (In reply to Arthur LAMBERT from comment #2) > It is possible to have a link to get the patch and test them manually until > the official integration or is it too soon ? Download and build the trunk: svn co svn://svn.valgrind.org/valgrind/trunk cd trunk ./autogen.sh then configure and build as normal. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362650] an extra space character in attached file names the UTF-8 encoded
https://bugs.kde.org/show_bug.cgi?id=362650 --- Comment #3 from Alexander Yavorsky --- Created attachment 101122 --> https://bugs.kde.org/attachment.cgi?id=101122&action=edit Screenshot with additional spaces Сorrect filename is: Договор 1 на оказание услуг по обработке почвы. Технология. Талдом. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362650] an extra space character in attached file names the UTF-8 encoded
https://bugs.kde.org/show_bug.cgi?id=362650 --- Comment #5 from Alexander Yavorsky --- Created attachment 101124 --> https://bugs.kde.org/attachment.cgi?id=101124&action=edit source screenshot Sorry, #4 comment with wrong attachment. In source i see encoded filename spited into three rows and exactly at breaks occurs additional spaces: -source --sOA2imNDPik6TVvdYIdSdZP56q77z6Ia-zEBUqmjdMGgRKwkE-1461416403 Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="=?UTF-8?B?0JTQvtCz0L7QstC+0YAgMSDQvdCwINC+0LrQsNC30LDQvdC40LUg0YPRgdC7?= =?UTF-8?B?0YPQsyDQv9C+INC+0LHRgNCw0LHQvtGC0LrQtSDQv9C+0YfQstGLLiDQotC1?= =?UTF-8?B?0YXQvdC+0LvQvtCz0LjRjy4g0KLQsNC70LTQvtC8LmRvY3g=?=" Content-Disposition: attachment Content-Transfer-Encoding: base64 UEsDBBQABgAIIQDYiDys8gEAANUJAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC ... -source -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362650] an extra space character in attached file names the UTF-8 encoded
https://bugs.kde.org/show_bug.cgi?id=362650 --- Comment #4 from Alexander Yavorsky --- Created attachment 101123 --> https://bugs.kde.org/attachment.cgi?id=101123&action=edit Source screenshot In source i see encoded filename spited into three rows and exactly at breaks occurs additional spaces: -source --sOA2imNDPik6TVvdYIdSdZP56q77z6Ia-zEBUqmjdMGgRKwkE-1461416403 Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="=?UTF-8?B?0JTQvtCz0L7QstC+0YAgMSDQvdCwINC+0LrQsNC30LDQvdC40LUg0YPRgdC7?= =?UTF-8?B?0YPQsyDQv9C+INC+0LHRgNCw0LHQvtGC0LrQtSDQv9C+0YfQstGLLiDQotC1?= =?UTF-8?B?0YXQvdC+0LvQvtCz0LjRjy4g0KLQsNC70LTQvtC8LmRvY3g=?=" Content-Disposition: attachment Content-Transfer-Encoding: base64 UEsDBBQABgAIIQDYiDys8gEAANUJAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC ... -source -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359109] ibus terminated when switching back from virtual terminal
https://bugs.kde.org/show_bug.cgi?id=359109 spa...@modanese.net changed: What|Removed |Added Version|5.6.2 |5.7.5 --- Comment #5 from spa...@modanese.net --- Still an issue in 5.7.5. Another effect worth mentioning is that all Konsole windows (and sometimes Firefox too) stop accepting any input once ibus is terminated, i.e. when I switch back from the VT. Closing every single window and starting Konsole again makes it "operational" again, but things just really get out of hand when I have critical stuff such as vim or ssh running in the Konsole window. -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 368871] Unknown file type
https://bugs.kde.org/show_bug.cgi?id=368871 Giovanni Rallo changed: What|Removed |Added Platform|Other |Debian testing Version|unspecified |0.9.2 --- Comment #2 from Giovanni Rallo --- KDE Frameworks 5.25.0 Qt 5.6.1 (compilato con 5.6.1) Il sistema di finestre xcb whyle I try to save file cannot recognize format kvtml ... and I try even whith other format but is the same :( -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 368871] Unknown file type
https://bugs.kde.org/show_bug.cgi?id=368871 --- Comment #3 from Giovanni Rallo --- I use Xfce testing Debian... in the Xfce Debian 8.5 Stable work fine... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368899] .desktop starter containing cmdline won't be executed anymore
https://bugs.kde.org/show_bug.cgi?id=368899 installepatr...@p-installe.be changed: What|Removed |Added CC||InstallePatrick@P-Installe. ||be --- Comment #1 from installepatr...@p-installe.be --- Same here with manjaro. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 351106] Crash using "Create Copy from Current Image"
https://bugs.kde.org/show_bug.cgi?id=351106 Dmitry Kazakov changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/47e8ee0294ce0441ce93ec6a8 ||38dad5bca13130f Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #16 from Dmitry Kazakov --- Git commit 47e8ee0294ce0441ce93ec6a838dad5bca13130f by Dmitry Kazakov. Committed on 16/09/2016 at 14:59. Pushed by dkazakov into branch 'master'. Fix crash when copying the image with Instant Preview active Fixes T3758,T3709 M +5-0libs/image/kis_base_node.cpp M +2-0libs/image/kis_base_node.h M +1-1libs/image/kis_group_layer.h M +1-0libs/image/kis_image.cc M +10 -11 libs/image/kis_layer.cc M +1-1libs/image/kis_layer.h M +1-1libs/image/kis_mask.h M +1-1libs/image/kis_paint_layer.h M +1-1libs/image/kis_selection_based_layer.h M +1-1libs/image/lazybrush/kis_colorize_mask.h M +1-1libs/ui/flake/kis_shape_layer.h http://commits.kde.org/krita/47e8ee0294ce0441ce93ec6a838dad5bca13130f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368811] Screen freezed when trying to get desktop grid from desktop corner (3d effect)
https://bugs.kde.org/show_bug.cgi?id=368811 --- Comment #10 from Christophe Larsonneur --- FYI: I stopped the hp myroom tool and all were good until the time I used it back! So, another freeze occurs and then, I decided to kill hpmyroom process. But kwin did not recover from his freeze state. The process is still at 100% CPU, at this time. As soon as I have the final coredump, I can send it here also. I don't know if it can help you guys. Just tell me. If you need anything else from my side, do not hesitate. -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 368871] Unknown file type
https://bugs.kde.org/show_bug.cgi?id=368871 --- Comment #4 from Giovanni Rallo --- I try from terminal and this is the result Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed Thank you very much for your attention.. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 364807] KWrite does not sport its icon.
https://bugs.kde.org/show_bug.cgi?id=364807
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #2 from RJVB ---
FWIW, the correct cross-platform way of getting the icon to show up in task
switchers, Docks etc. is something along the lines of
app.setWindowIcon(QIcon::fromTheme("appIconName", app.windowIcon()));
this avoids replacing the application icon (resource) installed in or with the
application with an empty icon; as a general rule of thumb one can say that
platforms either store the app icon resource with the app (OS X, MS Windows) or
else they use an icon from a user-selectable icon theme from some central
location.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 368903] New: Attempts to set a screen on a child window
https://bugs.kde.org/show_bug.cgi?id=368903
Bug ID: 368903
Summary: Attempts to set a screen on a child window
Product: kate
Version: 16.08
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
I didn't really notice when this started; since at least 16.04.2 I'm seeing a
series of Qt warnings on the calling terminal whenever I open a document in
Kate5 (see below).
This warning is generated in QWindowPrivate::setTopLevelScreen(), which is NOT
a platform-specific method. Somehow this warning isn't triggered on Linux or
even on OS X when using the XCB QPA.
I'm also not seeing it in any other application (including KDevelop which is
built on KTextEditor and (AFAIK) the Kate kpart).
I thus think Kate is doing something it shouldn't on OS X.
Reproducible: Always
Steps to Reproduce:
1. Start Kate so that it's stdout and stderr are connected to a terminal
2. open a document
Actual Results:
QWidgetWindow(0x7fd2c60e1510, name="QFrameClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60e0be0, name="QSplitterClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60dfd30, name="QFrameClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60def20, name="QSplitterClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60def20, name="QSplitterClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60def20, name="QSplitterClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60dfd30, name="QFrameClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60dfd30, name="QFrameClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60e0be0, name="QSplitterClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60e0be0, name="QSplitterClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60e1510, name="QFrameClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
QWidgetWindow(0x7fd2c60e1510, name="QFrameClassWindow") (
QScreen(0x7fd2c2c3fc50, name="Color LCD") ): Attempt to set a screen on a child
window.
[...]
Expected Results:
I'd expect Kate NOT to generate this warnings on OS X like it doesn't generate
them elsewhere.
Here's a backtrace from a breakpoint in QWindowPrivate::setTopLevelScreen():
* thread #1: tid = 0xfb6638, 0x0001018f7bc0
QtGui`QWindowPrivate::setTopLevelScreen(this=,
newScreen=0x0001052a3740, recreate=) + 80 at qwindow.cpp:372,
queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x0001018f7bc0
QtGui`QWindowPrivate::setTopLevelScreen(this=,
newScreen=0x0001052a3740, recreate=) + 80 at qwindow.cpp:372
[opt]
369 {
370 Q_Q(QWindow);
371 if (parentWindow) {
-> 372 qWarning() << q << '(' << newScreen << "): Attempt to set a
screen on a child window.";
373 return;
374 }
375 if (newScreen != topLevelScreen) {
(lldb) bt
* thread #1: tid = 0xfb6638, 0x0001018f7bc0
QtGui`QWindowPrivate::setTopLevelScreen(this=,
newScreen=0x0001052a3740, recreate=) + 80 at qwindow.cpp:372,
queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x0001018f7bc0
QtGui`QWindowPrivate::setTopLevelScreen(this=,
newScreen=0x0001052a3740, recreate=) + 80 at qwindow.cpp:372
[opt]
frame #1: 0x0001096876b4
libqcocoa.dylib`QCocoaWindow::exposeWindow(this=0x00010ec56450) + 276 at
qcocoawindow.mm:1807 [opt]
frame #2: 0x00010968d5ba libqcocoa.dylib`::-[QNSView
windowNotification:](self=, _cmd=,
windowNotification=) + 378 at qnsview.mm:443 [opt]
frame #3: 0x7fff8bc2de0c
CoreFoundation`__CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
frame #4: 0x7fff8bb2182d CoreFoundation`_CFXNotificationPost + 2893
frame #5: 0x7fff8e2a5dda Foundation`-[NSNotificationCenter
postNotificationName:object:userInfo:] + 68
frame #6: 0x7fff85a2cc32 AppKit`-[NSWindow
_windowTransformAnimationDidEnd:] + 312
frame #7: 0x7fff859ec46e AppKit`-[NSWindow
_doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 800
frame #8: 0x7fff859ec0e0 AppKit`-[NSWindow orderWindow:relativ
[plasmashell] [Bug 368904] New: plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=368904 Bug ID: 368904 Summary: plasmashell crash Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: orceph...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: This seams to happen when the Laptop is left alone for a while and the sceen is locked. I do not know if the time is consistent with anything else. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faeab9a47c0 (LWP 21431))] Thread 8 (Thread 0x7fade1266700 (LWP 21445)): #0 0x7faea4ebbbfd in poll () at /lib64/libc.so.6 #1 0x7faea1598e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7faea1598f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7faea57e8d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7faea578fd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7faea55b161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fade28b2cf7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7faea55b632f in () at /usr/lib64/libQt5Core.so.5 #8 0x7faea46c50a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7faea4ec402d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fadf32f9700 (LWP 21439)): #0 0x7faea4eb7ccd in read () at /lib64/libc.so.6 #1 0x7faea15d9b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7faea1598999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7faea1598df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7faea1598f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7faea57e8d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7faea578fd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7faea55b161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7faea9461282 in () at /usr/lib64/libQt5Quick.so.5 #9 0x7faea55b632f in () at /usr/lib64/libQt5Core.so.5 #10 0x7faea46c50a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7faea4ec402d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fae79f92700 (LWP 21438)): #0 0x7faea46c903f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faeab09486b in () at /usr/lib64/libQt5Script.so.5 #2 0x7faeab094899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7faea46c50a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7faea4ec402d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fae7b86b700 (LWP 21437)): #0 0x7faea55aebfa in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7faea57e9885 in () at /usr/lib64/libQt5Core.so.5 #2 0x7faea15988f1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7faea1598df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7faea1598f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7faea57e8d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7faea578fd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7faea55b161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7faea88c5e18 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7faea55b632f in () at /usr/lib64/libQt5Core.so.5 #10 0x7faea46c50a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7faea4ec402d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fae811a0700 (LWP 21436)): #0 0x7faea4ebbbfd in poll () at /lib64/libc.so.6 #1 0x7faea1598e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7faea1598f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7faea57e8d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7faea578fd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7faea55b161a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7faea88c5e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7faea55b632f in () at /usr/lib64/libQt5Core.so.5 #8 0x7faea46c50a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7faea4ec402d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fae8e6f3700 (LWP 21435)): #0 0x7faea4ebbbfd in poll () at /lib64/libc.so.6 #1 0x7faea1598e64 in () at /usr/lib64/libglib-2.0.so.0 #2
[valgrind] [Bug 362934] [AsusWRT] Arm v7 illegal instruction
https://bugs.kde.org/show_bug.cgi?id=362934 Peter Maydell changed: What|Removed |Added CC||peter.mayd...@linaro.org --- Comment #3 from Peter Maydell --- "Features : swp half thumb fastmult edsp" in the /proc/cpuinfo means no Neon, and not even any VFP -- integer only core. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356906] Irregular updates
https://bugs.kde.org/show_bug.cgi?id=356906 --- Comment #2 from kdde@porcupinefactory.org --- After 5.7 I haven't seen this reoccur. There haven't been any changes on my part, besides having to restart plasma every few hours, so the bug may still be there. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 363150] Crash when clicking on "Tools -> Burn Image..."
https://bugs.kde.org/show_bug.cgi?id=363150 northon_patri...@yahoo.ca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from northon_patri...@yahoo.ca --- I can confirm it is fixed. Thanks, best regards. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368905] New: a shell is started even when the konsole plugin isn't loaded
https://bugs.kde.org/show_bug.cgi?id=368905 Bug ID: 368905 Summary: a shell is started even when the konsole plugin isn't loaded Product: kate Version: 16.08 Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: rjvber...@gmail.com Even when Kate's konsole plugin isn't loaded (used), a shell is started when a document is opened. Reproducible: Always Steps to Reproduce: A: 1. Start Kate so that it's stdout and stderr are connected to a terminal 2. Quit. B: 1. Start Kate so that it's stdout and stderr are connected to a terminal 2. Open a document 3. Quit. Actual Results: A: No warnings about shells on exit. B: shell did not close, sending SIGHUP Process 37896 did not die with SIGHUP I see the same "sending SIGHUP" message on Linux, but there the shell apparently reacts as expected to the signal. Expected Results: There appears to be no reason to start a shell when the konsole plugin isn't being used. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364559] Changing project settings and saving crashes the software
https://bugs.kde.org/show_bug.cgi?id=364559 --- Comment #7 from Stefan Naumann --- Still persists in 16.08.1 . What I found out: using round numbers as framerates (e.g. 25, 30, 60) does work fine. So probably the resolution-change is not the killer. Changing from 720p29,997 to 1080p59,997 then saving the project crashes KDEnlive. So probably the save-code and / or project-settings-change-code cannot handle switches from an float-framerate to a different float-framerate. I hope that helps. -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 368871] Unknown file type
https://bugs.kde.org/show_bug.cgi?id=368871 --- Comment #5 from Burkhard Lueck --- I cannot reproduce this behavior. Please provide the output of "ls -al /full/path/to/your.kvtml" in a terminal and attach the file -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362934] [AsusWRT] Arm v7 illegal instruction
https://bugs.kde.org/show_bug.cgi?id=362934 --- Comment #2 from Sergey --- I could only point you to this info: https://wikidevi.com/wiki/ASUS_RT-AC87U => the SOC is BCM4709A0 https://wikidevi.com/wiki/Broadcom -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368573] Tablet Pen stops responding for a short period of time after each stroke
https://bugs.kde.org/show_bug.cgi?id=368573 --- Comment #4 from Autumn Lansing --- Yes, but the problem only came about with 3.0.1. 3.0 works perfectly. Something changed in Krita that's causing the skipping. The tablet and pen work fine in all other apps I've tested them in, such as GIMP. It's only in Krita 3.0.1 that there's a problem, so something in the way that Krita handles events in its latest version is creating the issue. Aside from breaking the lock when moving the pen to the other monitor, the lock is also broken if another app is brought into focus on the same monitor, so as long as Krita is in focus, it keeps the pen locked up for around five seconds before releasing it. What changed in Krita's handling of pen events between versions that might cause this? If I file this with the Awesome team, they may not have the equipment to test it. If the problem is on their end, then I need to be able to point them in the right direction. As it is, Krita seems to be doing something different from all other apps, and I fear they may kick the bug back to you. I'm a developer, though not very experienced with C++, which I assume Krita is written in, but I'd be happy to look into the bug further if I knew where to start. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368318] Crash during session restore at startup
https://bugs.kde.org/show_bug.cgi?id=368318 --- Comment #5 from Kevin Funk --- Git commit eaf3739fba2229187938123ec0af7459dad3ad28 by Kevin Funk. Committed on 16/09/2016 at 16:23. Pushed by kfunk into branch '5.0'. Hardening: Fix one of the immediate crashes M +1-0language/duchain/topducontextdynamicdata.cpp http://commits.kde.org/kdevplatform/eaf3739fba2229187938123ec0af7459dad3ad28 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368901] Pressing ALT+f2 and entering exact executable name and pressing enter can run another program
https://bugs.kde.org/show_bug.cgi?id=368901 Martin Gräßlin changed: What|Removed |Added Version|5.7.4 |5.7.5 Product|kwin|krunner Assignee|kwin-bugs-n...@kde.org |k...@privat.broulik.de Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368902] Top-left cot corner doesn't work reliably when window extends to top-left corner
https://bugs.kde.org/show_bug.cgi?id=368902 Martin Gräßlin changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- The cursor is pushed back and there is a cooldown delay before you can trigger it again. Please go to systemsettings -> desktop behavior -> Screen edges and adjust the settings to your personal preferences. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368318] Crash during session restore at startup
https://bugs.kde.org/show_bug.cgi?id=368318 Kevin Funk changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Kevin Funk --- Well, assuming this particular crash got fixed. Please reopen / open another bug report for any related crashes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368318] Crash during session restore at startup
https://bugs.kde.org/show_bug.cgi?id=368318 Kevin Funk changed: What|Removed |Added Version Fixed In||5.0.1 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 368030] Crash on declining invite for messenger via google+
https://bugs.kde.org/show_bug.cgi?id=368030 jeova changed: What|Removed |Added CC||jeova.r...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368906] New: Plasma crashes when unlocking from standby
https://bugs.kde.org/show_bug.cgi?id=368906 Bug ID: 368906 Summary: Plasma crashes when unlocking from standby Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: robe...@echelon-it.ro CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: The computer was in standby due to no activity. When I move the mouse the unlocking screen shows up. I enter my user's password and even tough everything is fine I get the pop-up with "Plasma crash". I have dual monitors, one is primary and another is in extended mode. AMD A8 K7700 with the integrated GPU. Both displays are full hd. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f775a46d7c0 (LWP 26027))] Thread 25 (Thread 0x7f74cdfe7700 (LWP 4211)): #0 0x7f775310003f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f775400034b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7757f621cb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f7757f62663 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f7753fff32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f77530fc0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f775390902d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f76427f8700 (LWP 27370)): #0 0x7f775310003f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f775400034b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f769230965f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f769230d43a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f769230d481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f769230b005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f7753fff32f in () at /usr/lib64/libQt5Core.so.5 #23 0x7f77530fc0a4 in start_thread () at /lib64/libpthread.so.0 #24 0x7f775390902d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f7642ff9700 (LWP 27369)): #0 0x7f775310003f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f775400034b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f769230965f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f769230d43a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f76923076cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f769230d481 in () at /usr/lib6
[dolphin] [Bug 365968] scrolling is unusable slow with libinput in dolphin places and folders panel
https://bugs.kde.org/show_bug.cgi?id=365968 Jake changed: What|Removed |Added CC||ja...@posteo.de --- Comment #4 from Jake --- I have this issue also on multiple Manjaro/Arch machines, not using xf86-input-libinput. The bug came with version 16.08 (this includes 16.07.80 + 16.07.90). Can someone verify this? Version 16.04 works fine for me, as temporary workaround you could downgrade the dolphin package without big problems. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 368705] Port to Qt5 and Add webEngine
https://bugs.kde.org/show_bug.cgi?id=368705 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] New: kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 Bug ID: 368907 Summary: kaffeine sometimes uses 100% CPU Product: kaffeine Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: lists.jjo...@free.fr I use kaffeine for DVB-T, and it uses nicely VDPAU, as the CPU used is less than 20% like other players with VDPAU. But sometimes, it starts using 100% CPU, and then it keeps at this level even when channels are stopped. This happens sometimes directly when I start playing the first channel, or when changing the channel. It never starts happening when simply playing a channel. I tried to run with debug log (-d), but I saw nothing different with between sessions with this bug or without. Reproducible: Sometimes Steps to Reproduce: 1. play dvb-t 2. it is in the french TNT system Actual Results: 100% CPU Expected Results: At least the CPU should not be used if I stop playing/ -- You are receiving this mail because: You are watching all bug changes.
Could you help me on this ? dont write very well in english ...
Application: ktp-text-ui (0.8.1) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.19.0-32-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: I was in the text interface TELEPATHY window I clicked in action > invite to chart and then it crashed. The crash can be reproduced every time. -- Backtrace: Application: Interface de texto do Telepathy (ktp-text-ui), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #5 SharedPtr (o=, this=0x7ffcf49ef1f0, this@entry=0x7ffcf49ef1a0) at /usr/include/telepathy-qt4/TelepathyQt/shared-ptr.h:105 #6 ChatWidget::account (this=this@entry=0x0) at /build/buildd/ktp-text-ui-0.8.1/lib/chat-widget.cpp:219 #7 0x00412777 in ChatWindow::onInviteToChatTriggered (this=0x1614860) at /build/buildd/ktp-text-ui-0.8.1/app/chat-window.cpp:433 #8 0x00417f05 in ChatWindow::qt_static_metacall (_o=, _id=, _a=, _c=) at /build/buildd/ktp-text-ui-0.8.1/obj-x86_64-linux-gnu/app/chat-window.moc:127 #9 0x7fc80ba2c87a in QMetaObject::activate (sender=sender@entry=0x16603d0, m=m@entry=0x7fc80b5e0de0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcf49ef370) at kernel/qobject.cpp:3539 #10 0x7fc80ab30a62 in QAction::triggered (this=this@entry=0x16603d0, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 #11 0x7fc80ab32433 in QAction::activate (this=this@entry=0x16603d0, event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1257 #12 0x7fc80af60509 in QMenuPrivate::activateCausedStack (this=this@entry=0x38e8cb0, causedStack=..., action=action@entry=0x16603d0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1038 #13 0x7fc80af64a39 in QMenuPrivate::activateAction (this=0x38e8cb0, action=0x16603d0, action_e=QAction::Trigger, self=) at widgets/qmenu.cpp:1130 #14 0x7fc80db1a615 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libkdeui.so.5 #15 0x7fc80ab8651a in QWidget::event (this=this@entry=0x37e35b0, event=event@entry=0x7ffcf49efaa0) at kernel/qwidget.cpp:8376 #16 0x7fc80af6883b in QMenu::event (this=0x37e35b0, e=0x7ffcf49efaa0) at widgets/qmenu.cpp:2481 #17 0x7fc80ab36e2c in QApplicationPrivate::notify_helper (this=this@entry=0x14978c0, receiver=receiver@entry=0x37e35b0, e=e@entry=0x7ffcf49efaa0) at kernel/qapplication.cpp:4567 #18 0x7fc80ab3d5dd in QApplication::notify (this=, receiver=0x37e35b0, e=0x7ffcf49efaa0) at kernel/qapplication.cpp:4110 #19 0x7fc80da63cca in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #20 0x7fc80ba184dd in QCoreApplication::notifyInternal (this=0x147ac80, receiver=receiver@entry=0x37e35b0, event=event@entry=0x7ffcf49efaa0) at kernel/qcoreapplication.cpp:953 #21 0x7fc80ab3cd93 in sendEvent (event=, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x37e35b0, event=event@entry=0x7ffcf49efaa0, alienWidget=alienWidget@entry=0x0, nativeWidget=nativeWidget@entry=0x37e35b0, buttonDown=buttonDown@entry=0x7fc80b61c318 , lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3178 #23 0x7fc80abb1d1c in QETWidget::translateMouseEvent (this=this@entry=0x37e35b0, event=event@entry=0x7ffcf49efdf0) at kernel/qapplication_x11.cpp:4568 #24 0x7fc80abb1289 in QApplication::x11ProcessEvent (this=0x147ac80, event=event@entry=0x7ffcf49efdf0) at kernel/qapplication_x11.cpp:3627 #25 0x7fc80abd8b32 in x11EventSourceDispatch (s=0x1497e10, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #26 0x7fc803d6ae04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fc803d6b048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fc803d6b0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fc80ba457be in QEventDispatcherGlib::processEvents (this=0x143eab0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #30 0x7fc80abd8be6 in QGuiEventDispatcherGlib::processEvents (this=, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x7fc80ba170af in QEventLoop::processEvents (this=this@entry=0x7ffcf49f01c0, flags=...) at kernel/qeventloop.cpp:149 #32 0x7fc80ba173a5 in QEventLoop::exec (this=this@entry=0x7ffcf49f01c0, flags=...) at kernel/qeventloop.cpp:204 #33 0x7fc80ba1cb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #34 0x7fc80ab3537c in QApplication::exec () at kernel/qapplication.cpp:3828 #35 0x0040e995 in main (argc=1, argv=0x7ffcf49f03e8) at /build/buildd/ktp-text-ui-0.8.1/app/main.cpp:72 Relatar para https://bugs.kde.org/
[kdenlive] [Bug 364559] Changing project settings and saving crashes the software
https://bugs.kde.org/show_bug.cgi?id=364559 --- Comment #8 from YEK --- Thanks for posting your well-researched and thoughtful comment. We have clearly a confirmed bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues
https://bugs.kde.org/show_bug.cgi?id=368078 --- Comment #7 from David Brooke --- Tested plasma 5.7.95 and the results are the same. Refer to the first "Doesn't work as expected" video. Partition2 or C3770-P2 Gentoo AMD64 Stable Plasma 5.7.95 Frameworks 5.26 KDE Apps 16.08.1 QT5 - version 5.6.1 xf86-video-intel 2.99.917-r2 -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 368871] Unknown file type
https://bugs.kde.org/show_bug.cgi?id=368871 --- Comment #6 from Giovanni Rallo --- I haven't .kvtml files becouse program can't save... another guy have the same problem i Ubuntu... another friend debian's think that problem is from the new Kde system i Debian Testing... is very different... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 368785] konsole tab title format only uses the first program you ever ran, not the current one
https://bugs.kde.org/show_bug.cgi?id=368785 Julio J. changed: What|Removed |Added CC||julioelpo...@gmail.com --- Comment #4 from Julio J. --- Yup, can confirm, it happens also when you connect to a remote host, the title stays the same afterwards. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368908] New: Crash when trying to play a transition
https://bugs.kde.org/show_bug.cgi?id=368908 Bug ID: 368908 Summary: Crash when trying to play a transition Product: kdenlive Version: 16.08.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: juliquad...@gmail.com When trying to play a transition, KDE instantly crashes. Reproducible: Always Steps to Reproduce: 1. Adding any transition to a new project with two video files 2. Trying to play it in the video player Actual Results: It instantly crashed. Expected Results: It should play the transition. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fe1eb1f98c0 (LWP 5563))] Thread 22 (Thread 0x7fe1637fd700 (LWP 5777)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe1da7cf63e in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56 #2 0x7fe1f558a6fa in start_thread (arg=0x7fe1637fd700) at pthread_create.c:333 #3 0x7fe1f6c68b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 21 (Thread 0x7fe163ffe700 (LWP 5776)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe1da7cf63e in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56 #2 0x7fe1f558a6fa in start_thread (arg=0x7fe163ffe700) at pthread_create.c:333 #3 0x7fe1f6c68b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 20 (Thread 0x7fe184ff9700 (LWP 5775)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe1da7cf63e in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56 #2 0x7fe1f558a6fa in start_thread (arg=0x7fe184ff9700) at pthread_create.c:333 #3 0x7fe1f6c68b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7fe199ac3700 (LWP 5774)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe1da7cf63e in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56 #2 0x7fe1f558a6fa in start_thread (arg=0x7fe199ac3700) at pthread_create.c:333 #3 0x7fe1f6c68b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7fe1b2ffe700 (LWP 5773)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe1da7cf63e in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56 #2 0x7fe1f558a6fa in start_thread (arg=0x7fe1b2ffe700) at pthread_create.c:333 #3 0x7fe1f6c68b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7fe1867fc700 (LWP 5772)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe1c61c995d in video_thread (arg=0x46bce50) at consumer_sdl_audio.c:423 #2 0x7fe1f558a6fa in start_thread (arg=0x7fe1867fc700) at pthread_create.c:333 #3 0x7fe1f6c68b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fe19547c700 (LWP 5771)): #0 0x7fe1f1d34a3c in pa_stream_get_state () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #1 0x7fe1cca98fd0 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #2 0x7fe1cca6b920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #3 0x7fe1cca750b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #4 0x7fe1ccab4f59 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #5 0x7fe1f558a6fa in start_thread (arg=0x7fe19547c700) at pthread_create.c:333 #6 0x7fe1f6c68b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fe19731d700 (LWP 5770)): [KCrash Handler] #6 0x7fe19f9f025f in addition::update(double, unsigned int*, unsigned int const*, unsigned int const*, unsigned int const*) () from /usr/lib/frei0r-1/addition.so #7 0x7fe19f9efa54 in f0r_update2 () from /usr/lib/frei0r-1/addition.so #8 0x7fe1ddcfc11a in process_frei0r_item (service=service@entry=0xa7a0f00, position=position@entry=0, time=0, prop=prop@entry=0xa7a0f00, this=this@entry=0x7fe1801c3550, image=image@entry=0x7fe19731caf0, width=width@entry=0x7fe19731ccc4, height=height@entry=0x7fe19731ccc8) at frei0r_helper.c:167 #9 0x7fe1ddcfbb90 in transition_get_image (a_frame=a_frame@entry=0x7fe1801c3550, image=image@entry=0x7fe19731ccd8, format=format@entry=0x3e1d40c, width=width@entry=0x7fe19731ccc4, height=height@entry=0x7fe19731ccc8, writable=writable@entry=0) at transition_frei0r.c:71 #10 0x7fe1fc51e757 in mlt_frame_ge
[korganizer] [Bug 352043] Regression: kOrganizer 5 systray reminder module does not open main application window on click
https://bugs.kde.org/show_bug.cgi?id=352043 Gunter Ohrner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Gunter Ohrner --- Seems to be fixed as of kOrganizer Version 5.3.0 (QtWebEngine) (KDE Neon packages). -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 366055] kOrganizer 5.1.3: Incidents inviting "myself" are invisible
https://bugs.kde.org/show_bug.cgi?id=366055 --- Comment #2 from Gunter Ohrner --- Probably a duplicate of Bug 352214 (https://bugs.kde.org/show_bug.cgi?id=352214) (or the other way around?) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 352214] Event is not added if the invitation list contains the creator's email address
https://bugs.kde.org/show_bug.cgi?id=352214 Gunter Ohrner changed: What|Removed |Added Blocks||366055 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 366055] kOrganizer 5.1.3: Incidents inviting "myself" are invisible
https://bugs.kde.org/show_bug.cgi?id=366055 Gunter Ohrner changed: What|Removed |Added Depends on||352214 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366833] Panels misplaced after restart
https://bugs.kde.org/show_bug.cgi?id=366833 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 352215] kOrganizer 5.0.0 crashes whenever I add an event which invites other participants
https://bugs.kde.org/show_bug.cgi?id=352215 Gunter Ohrner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Gunter Ohrner --- Does not happen any more since quite a while now. (KDE Neon packages) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364852] Plasmashell panel when put on the middle edge of a multi screen setup does not autohide
https://bugs.kde.org/show_bug.cgi?id=364852 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 335654] reported versions of several applications are not registered on bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=335654 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 336007] split-view status not maintained across sessions
https://bugs.kde.org/show_bug.cgi?id=336007 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368909] New: Regression: Windows with demands attention flag are falsely shown on all workspaces
https://bugs.kde.org/show_bug.cgi?id=368909 Bug ID: 368909 Summary: Regression: Windows with demands attention flag are falsely shown on all workspaces Product: plasmashell Version: 5.7.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: deve...@fuchsnet.ch As reported on IRC: as the same model is used for the pager as for the task-manager, windows that have the demands attention flag set will be falsely shown on all workspaces. Reproducible: Always Steps to Reproduce: 1. Have multiple workspaces and a pager 2. Place a window on one workspace, let's take the great IRC client konversation as an example 3. Have that window trigger demands attention (e.g. get highlighted in konversation) Actual Results: Window is shown on all workspaces in the pager, as if it was sticky Expected Results: Window is only shown on the correct workspace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage
https://bugs.kde.org/show_bug.cgi?id=368633 --- Comment #8 from b...@beuc.net --- Created attachment 101125 --> https://bugs.kde.org/attachment.cgi?id=101125&action=edit appimage: add missing build dependencies to fix lack of keyboard support when building from minimal CentOS environment appimage: add missing build dependencies to fix lack of keyboard support when building from minimal CentOS environment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage
https://bugs.kde.org/show_bug.cgi?id=368633 --- Comment #9 from b...@beuc.net --- Created attachment 101126 --> https://bugs.kde.org/attachment.cgi?id=101126&action=edit appimage: do not remove previously built appimages appimage: do not remove previously built appimages -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage
https://bugs.kde.org/show_bug.cgi?id=368633 --- Comment #10 from b...@beuc.net --- Created attachment 101127 --> https://bugs.kde.org/attachment.cgi?id=101127&action=edit appimage: add documentation appimage: add documentation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368862] Thumbnails for Olympus raw (ORF) in albumview are blurred
https://bugs.kde.org/show_bug.cgi?id=368862 --- Comment #10 from Maik Qualmann --- Yes, there are 2 preview images in different sizes available: maik@linux-tpgn:~> exiv2 -pp GME15390.ORF Preview 1: image/jpeg, 160x120 pixels, 6946 bytes Preview 2: image/jpeg, 3200x2400 pixels, 1004415 bytes I have searched another RAW image from this camera on the Web. At this file libraw used the large preview for the thumbnail. However, the firmware version from your camera is greater. Strange. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage
https://bugs.kde.org/show_bug.cgi?id=368633 --- Comment #11 from b...@beuc.net --- Build now works from a minimal CentOS such as Docker's :) Attached are 3 patched: - adding missing QT build dependencies - avoid clearing /out/* since I lost all my previous builds :/ - add documentation I would recommend pushing it to krita/3.0.1 along with fe518206866a6cffdc64903ce3bf18b5e7a80867 2ac3c47e3ba91005143f4b59768f4e235e6d6762 so that people checking out the stable branch get a fully-working script. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368909] Regression: Windows with demands attention flag are falsely shown on all workspaces
https://bugs.kde.org/show_bug.cgi?id=368909 Eike Hein changed: What|Removed |Added CC||h...@kde.org Assignee|plasma-b...@kde.org |h...@kde.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 Alexander Schlarb changed: What|Removed |Added CC|alexander-...@xmine128.tk | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368579] The pager doesn't fit desktop names into the boxes anymore
https://bugs.kde.org/show_bug.cgi?id=368579 Eike Hein changed: What|Removed |Added Ever confirmed|0 |1 CC||h...@kde.org Assignee|plasma-b...@kde.org |h...@kde.org Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368578] Pager shows only 8 virtual desktops
https://bugs.kde.org/show_bug.cgi?id=368578 Eike Hein changed: What|Removed |Added Resolution|--- |FIXED CC||h...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Eike Hein --- Fixed the other day. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364559] Changing project settings and saving crashes the software
https://bugs.kde.org/show_bug.cgi?id=364559 --- Comment #9 from Jean-Baptiste Mardelle --- Git commit 54554d178e00bcee5deb588a2ad1cb522d5e2c3a by Jean-Baptiste Mardelle. Committed on 16/09/2016 at 18:36. Pushed by mardelle into branch 'Applications/16.08'. Fix crash when changing project fps while a clip was selected in timeline M +1-0src/timeline/customtrackview.cpp http://commits.kde.org/kdenlive/54554d178e00bcee5deb588a2ad1cb522d5e2c3a -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368910] New: Monitor change not detected on docking
https://bugs.kde.org/show_bug.cgi?id=368910 Bug ID: 368910 Summary: Monitor change not detected on docking Product: KScreen Version: 5.7.95 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: common Assignee: se...@kde.org Reporter: matth...@blaicher.com On a Lenovo Thinkpad L430, running Plasma 5.8 Beta with Arch Linux testing packages, monitor changes due to docking/undocking are not detected. It also had the same beviour back with Plasma 5.7. However, a simple execution of "xrandr" makes kscreen detect the monitor change. Afterwards plasmashell need to be killed and restarted to have a proper desktop layout. This happens with the intel as well as the mode setting driver. The dock has two DVI outputs, but the problem behaves the same on both ports. Installed packages are: kde-unstable/plasma-workspace 5.7.95-1 kde-unstable/kscreen 5.7.95-1 kde-unstable/libkscreen 5.7.95-1 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) Tomorrow, I will take the time to add propper logs to this bug report. If you require specific tests, feel free to tell me. I would also be willing to try kscreen patches. Reproducible: Always Steps to Reproduce: 1. Plug/Unplug laptop to dock Actual Results: Nothing happens. Only detected when xrandr is executed. Expected Results: Direct detection of monitor changes, proper Plasma desktop applied after screens are adjusted. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368603] crash when starting an lldb debug session
https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #16 from Aetf <7437...@gmail.com> --- Could you start KDevelop from the console and check the output when starting the debug session on Linux? You can enable debug output from KDevelop by launching it with the command env QT_LOGGING_CONF='logging.conf' kdevelop where the content of logging.conf is [Rules] kdevelop.debuggers.lldb.debug=true kdevelop.debuggers.common.debug=true Also, even if the debug session ends, there should be an output panel titled "Debug" being raised. See if there's any relevant output in that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368579] The pager doesn't fit desktop names into the boxes anymore
https://bugs.kde.org/show_bug.cgi?id=368579 Eike Hein changed: What|Removed |Added Latest Commit||http://commits.kde.org/plas ||ma-desktop/5c941198a9f62946 ||08588d863bc105488426249e Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Eike Hein --- Git commit 5c941198a9f6294608588d863bc105488426249e by Eike Hein. Committed on 16/09/2016 at 18:54. Pushed by hein into branch 'Plasma/5.8'. Fix desktop label clipping. M +15 -1applets/pager/package/contents/ui/main.qml http://commits.kde.org/plasma-desktop/5c941198a9f6294608588d863bc105488426249e -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 279222] icon of the progress of the system tray doesn't work
https://bugs.kde.org/show_bug.cgi?id=279222 --- Comment #17 from Tomasz C. --- A progress bar still does not work in version 16.08.1 Systray icon was restored with kde4 and did not fit the Plasma 5. I think it's better to undo the change and let it be a nice icon that corresponds to the Plasma 5, although it will not be a progress bar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues
https://bugs.kde.org/show_bug.cgi?id=368078 Eike Hein changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #8 from Eike Hein --- I can reproduce something now - will take a closer look soon. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368910] Monitor change not detected on docking
https://bugs.kde.org/show_bug.cgi?id=368910 --- Comment #1 from Matthias Blaicher --- Created attachment 101128 --> https://bugs.kde.org/attachment.cgi?id=101128&action=edit Annotated kscreen log Annotated kscreen log with relevant input from journald of the folliowing sequence: 1. Boot into KDE undocked 2. Dock laptop 3. Execute xrandr 4. Close lid While there is nothing happening in the kscreen logs, there is one entry after docking (point 2) I'd like to point out: Sep 16 20:51:32 meinpc kwin_x11[6183]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10182, resource id: 94371848, major code: 18 (ChangeProperty), minor code: 0 Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter Sep 16 20:51:32 meinpc kcminit[6975]: Initializing "kcm_input" : "kcminit_mouse" Sep 16 20:51:32 meinpc kwin_x11[6183]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10561, resource id: 92274696, major code: 18 (ChangeProperty), minor code: 0 Could it be, the ChangeProperty is the event we need, but it is dropped somehow? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #62 from S. Bryant --- I've just installed the OpenSuse Leap 42.2 beta to test this (Kontact 5.1.3). The bug is still present - Kontact is not seeing calendar events from the server. I should point out that I'm not using Owncloud for this either, so no kitten-eating here. I'm using the caldav software from Synology that's on my diskstation (with the most up-to-date software). Thunderbird (Lightning) and Android (Davdroid) sync just fine here, and Synology list other software they've tested it with. The bug is not on the server side. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 365067] Subtitles don't show on dvb
https://bugs.kde.org/show_bug.cgi?id=365067 Mauro Carvalho Chehab changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #9 from Mauro Carvalho Chehab --- The DVB subtitles logic were indeed broken in a number of ways. It should be working fine after this commit: http://commits.kde.org/kaffeine/63c3694da12c904a88178859c650b6c30cf748ee Please test. Locally, I tested with both VLC 2.x and 3.x. PS.: now, --debug will display messages related to the DVB messages. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 368911] New: Konsole re-uses EWMH -name when it reuses a process
https://bugs.kde.org/show_bug.cgi?id=368911 Bug ID: 368911 Summary: Konsole re-uses EWMH -name when it reuses a process Product: konsole Version: 16.08.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: single-process Assignee: konsole-de...@kde.org Reporter: temporalabstract...@gmail.com When a konsole window has been created with the `-name` option to give it an EWMH name and a new window is spawned which re-uses the process (which is apparently automatic if not spawned from a terminal) the new window will obtain the EWMH name already given via `-name` to the other process. A current workaround is simply spawning with `--separate` in which case the bug does not occur. Reproducible: Always Steps to Reproduce: 1. kill all existing konsole sessions 2. spawn a new konsole with `-name foo` 3. spawn another konsole session without any `-name` argument An easy way to do it is using a hotkey daemon of some kind and just bind the `konsole -name foo` and `konsole` commands to two different hotkeys, this is the exact scenario that caused the bug for me. Actual Results: The second konsole window will get the EWMH window name `foo` Expected Results: The second window should get the EWMH name `konsole` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368912] New: Apps menu and its tooltip must use the same icon when user sets a customized menu icon
https://bugs.kde.org/show_bug.cgi?id=368912 Bug ID: 368912 Summary: Apps menu and its tooltip must use the same icon when user sets a customized menu icon Product: plasmashell Version: 5.7.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: yy...@gmx.com CC: plasma-b...@kde.org This affects both kickoff and classic menu. Reproducible: Always Steps to Reproduce: 1.right click on apps menu icon, select "Application launcher settings" 2.choose any customized icon and apply the change 3. Actual Results: kde menu and its tooltip have different icons. See the screenshot please. Expected Results: kde menu and its tooltip have the same icon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368912] Apps menu and its tooltip must use the same icon when user sets a customized menu icon
https://bugs.kde.org/show_bug.cgi?id=368912 --- Comment #1 from Dr. Chapatin --- Created attachment 101129 --> https://bugs.kde.org/attachment.cgi?id=101129&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368913] New: WARNING: unhandled arm64-linux syscall: 117
https://bugs.kde.org/show_bug.cgi?id=368913 Bug ID: 368913 Summary: WARNING: unhandled arm64-linux syscall: 117 Product: valgrind Version: 3.11.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: mar...@juszkiewicz.com.pl <<>> tag=ptrace01_valgrind_memory_leak_check stime=1473972958 cmdline=" valgrind -q --leak-check=full --trace-children=yes ptrace01" contacts="" analysis=exit <<>> --23224-- WARNING: unhandled arm64-linux syscall: 117 --23224-- You may be able to write your own handler. --23224-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --23224-- Nevertheless we consider this a bug. Please report --23224-- it at http://valgrind.org/support/bug_reports.html. ptrace010 TWARN : ptrace01.c:237: ptrace() failed in child ptrace011 TFAIL : ptrace01.c:182: Test Failed --23225-- WARNING: unhandled arm64-linux syscall: 117 --23225-- You may be able to write your own handler. --23225-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --23225-- Nevertheless we consider this a bug. Please report --23225-- it at http://valgrind.org/support/bug_reports.html. ptrace010 TWARN : ptrace01.c:237: ptrace() failed in child ptrace012 TFAIL : ptrace01.c:182: Test Failed <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=58 cstime=3 <<>> Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368914] New: WARNING: unhandled arm64-linux syscall: 142
https://bugs.kde.org/show_bug.cgi?id=368914 Bug ID: 368914 Summary: WARNING: unhandled arm64-linux syscall: 142 Product: valgrind Version: 3.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: mar...@juszkiewicz.com.pl <<>> tag=reboot01_valgrind_memory_leak_check stime=1473973971 cmdline=" valgrind -q --leak-check=full --trace-children=yes reboot01" contacts="" analysis=exit <<>> --24614-- WARNING: unhandled arm64-linux syscall: 142 --24614-- You may be able to write your own handler. --24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --24614-- Nevertheless we consider this a bug. Please report --24614-- it at http://valgrind.org/support/bug_reports.html. --24614-- WARNING: unhandled arm64-linux syscall: 142 --24614-- You may be able to write your own handler. --24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --24614-- Nevertheless we consider this a bug. Please report --24614-- it at http://valgrind.org/support/bug_reports.html. reboot011 TFAIL : reboot01.c:109: reboot(2) Failed for option LINUX_REBOOT_CMD_CAD_ON reboot012 TFAIL : reboot01.c:109: reboot(2) Failed for option LINUX_REBOOT_CMD_CAD_OFF <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=44 cstime=2 <<>> Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368915] New: Preserve favorite apps when user changes apps menu layout
https://bugs.kde.org/show_bug.cgi?id=368915 Bug ID: 368915 Summary: Preserve favorite apps when user changes apps menu layout Product: plasmashell Version: 5.7.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: yy...@gmx.com CC: plasma-b...@kde.org Apps menu loses favorite apps when its layout is changed Reproducible: Always Steps to Reproduce: 1.open apps menu, right click on any app, select "Add to favorites" 2.rigth click on apps menu icon, select "Alternatives", alternate to any option 3. Actual Results: favorite app is missing from menu. Even if I back to previous apps menu layout the favorite app is still missing. Expected Results: preserve favorite app even when alternate the apps menu layout. -- You are receiving this mail because: You are watching all bug changes.
