[kdepim] [Bug 358116] messageviewer leaks temporary files with mail parts in it
https://bugs.kde.org/show_bug.cgi?id=358116 --- Comment #12 from Thomas Monjalon --- Wow! So efficient! Thanks Laurent -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384254] New: window title not updated when switching tab
https://bugs.kde.org/show_bug.cgi?id=384254 Bug ID: 384254 Summary: window title not updated when switching tab Product: kmail2 Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: tho...@monjalon.net Target Milestone: --- The name of the current folder is displayed in the window title. When opening a folder in a new tab, the window title is updated. But when selecting another old tab, the title is not updated. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384255] New: Idea to suggest latest contacts in recipient picker
https://bugs.kde.org/show_bug.cgi?id=384255 Bug ID: 384255 Summary: Idea to suggest latest contacts in recipient picker Product: kmail2 Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: tho...@monjalon.net Target Milestone: --- When writing part of a name in the recipient field, some contact suggestions appear. Then we have to choose one among some outdated email contacts or some picked from emails received with address typo in Cc. In order to suggest the best one first, I think these sorting rules could be used: - contacts from sent mails first - latest sent mails first - for contacts from received emails, most frequent occurences first About the format of the recipient contact, we often have this because of Outlook emails: "contact.n...@company.com" The first part is useless and could be automatically converted to contact.n...@company.com It would be simpler to visually parse. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 358116] messageviewer leaks temporary files with mail parts in it
https://bugs.kde.org/show_bug.cgi?id=358116 --- Comment #13 from Laurent Montel --- But there is still a case where we can't fix, it's when you launch kmail and use CRTL+C => no crash and kmail can't delete by itself temp file. it's not possible to manage this case. But we reduce the number of temporary file. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 384256] New: Akregator mark 'new' messages to 'read' if using the fIlter
https://bugs.kde.org/show_bug.cgi?id=384256 Bug ID: 384256 Summary: Akregator mark 'new' messages to 'read' if using the fIlter Product: akregator Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: thopp...@web.de Target Milestone: --- Open Akregator to see all messages, old, unread and new. Then use the search bar and check the left icon to choose the filter 'new'. Now you see only new messages but they become to mark read immediately. This is without further actions from the user! So after this you see no messages. If you change the filter to 'all', you see all messages as read. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 --- Comment #2 from RJVB --- Personally I'd guess this is just a side-effect of what Konsole can see of whatever the clear command sends to the tty. I'd hope that both the Konsole and gnome-term authors sat back to consider whether the other(s) implemented a feature the way they'd like to see it before copying it! ;) I think there are at least 2 levels at which an attempt can be made to improve this. Currently Konsole emulates well-known terminals, but it could very well define its own terminal type with the accompanying termcap/terminfo file that modifies an existing entry (or builds on one, if that database supports inheritance). The other possibility might be to support E3 (might also require shipping a dedicated terminfo file!), catch whatever specific `clear` sends to the tty as a result, and the provide a profile option whether or not the scrollback buffer should be cleared. The simple presence of that E3 command indicates that a clear was requested. FWIW, clear sends this to an xterm: `ESC[HESC[2J` -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 358116] messageviewer leaks temporary files with mail parts in it
https://bugs.kde.org/show_bug.cgi?id=358116 --- Comment #14 from Thomas Monjalon --- About Ctrl+C, not a big issue, but strange. Issue with catching SIGINT? About your fix, is it cleaning temp files only on crash? My issue is that these files are filling /tmp when kmail is running. Is it possible to avoid creating these files at the first place? Or could they be created in a subfolder of /tmp? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384233] color value lagging behind when dragging with cursor or changing w/ cursor wheel
https://bugs.kde.org/show_bug.cgi?id=384233 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Summary|color value bugging behind |color value lagging behind |when dragging with cursor |when dragging with cursor |or changing w/ cursor wheel |or changing w/ cursor wheel -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.
https://bugs.kde.org/show_bug.cgi?id=372221 Boudewijn Rempt changed: What|Removed |Added CC||nicolas.boug...@z-uo.com --- Comment #12 from Boudewijn Rempt --- *** Bug 383780 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.
https://bugs.kde.org/show_bug.cgi?id=372221 Boudewijn Rempt changed: What|Removed |Added CC||jamesedwa...@gmx.de --- Comment #13 from Boudewijn Rempt --- *** Bug 384233 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384233] color value lagging behind when dragging with cursor or changing w/ cursor wheel
https://bugs.kde.org/show_bug.cgi?id=384233 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 372221 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383780] difficulty to select color in some color selector
https://bugs.kde.org/show_bug.cgi?id=383780 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 372221 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383948] window decoration/title bar: resizes on window resize
https://bugs.kde.org/show_bug.cgi?id=383948 --- Comment #3 from arne anka --- Created attachment 107637 --> https://bugs.kde.org/attachment.cgi?id=107637&action=edit requested info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380343] Selections made with polygon, outline and bezier selection tools don't extend beyond canvas boundaries
https://bugs.kde.org/show_bug.cgi?id=380343 Nicholas LaPointe changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/a032e569bf674a4886804e6e ||0fee7df4b4791ec9 Status|UNCONFIRMED |RESOLVED --- Comment #3 from Nicholas LaPointe --- Git commit a032e569bf674a4886804e6e0fee7df4b4791ec9 by Nicholas LaPointe. Committed on 01/09/2017 at 08:35. Pushed by nicholasl into branch 'krita/3.2'. Allow selections outside of canvas boundary using when using selection tools This mostly reverts the changes made by 6b1b59121368222130daa15e11c3f3d557d8279a and 46b602ce35c920a337a31401f48d75e3c133bd71 and also removes a call in __KisToolSelectRectangularLocal::finishRect() that cropped the selection to the canvas boundary. (removing that call should also fix the bug that the two reverted commits were intended to fix -- see https://phabricator.kde.org/T4094 ) M +2-38 libs/ui/tool/kis_selection_tool_helper.cpp M +0-2libs/ui/tool/kis_selection_tool_helper.h M +0-1plugins/tools/selectiontools/kis_tool_select_rectangular.cc https://commits.kde.org/krita/a032e569bf674a4886804e6e0fee7df4b4791ec9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383948] window decoration/title bar: resizes on window resize
https://bugs.kde.org/show_bug.cgi?id=383948 --- Comment #4 from arne anka --- after the latest updates, the title bar at "tiny" is back to tiny. resizing issue was not reproducible on another machine, and in fact, also not on the original machine. I am now unsure whether it really occured or I confused something else with it. from my PoV this bug can be closed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380343] Selections made with polygon, outline and bezier selection tools don't extend beyond canvas boundaries
https://bugs.kde.org/show_bug.cgi?id=380343 Nicholas LaPointe changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/a032e569bf674a4886804e6e |ta/43b9a526a7e9d0cecd84b543 |0fee7df4b4791ec9|7d03a2b715bcde52 --- Comment #4 from Nicholas LaPointe --- Git commit 43b9a526a7e9d0cecd84b5437d03a2b715bcde52 by Nicholas LaPointe. Committed on 01/09/2017 at 08:39. Pushed by nicholasl into branch 'master'. Allow selections outside of canvas boundary using when using selection tools This mostly reverts the changes made by 6b1b59121368222130daa15e11c3f3d557d8279a and 46b602ce35c920a337a31401f48d75e3c133bd71 and also removes a call in __KisToolSelectRectangularLocal::finishRect() that cropped the selection to the canvas boundary. (removing that call should also fix the bug that the two reverted commits were intended to fix -- see https://phabricator.kde.org/T4094 ) M +2-38 libs/ui/tool/kis_selection_tool_helper.cpp M +0-2libs/ui/tool/kis_selection_tool_helper.h M +0-1plugins/tools/selectiontools/kis_tool_select_rectangular.cc https://commits.kde.org/krita/43b9a526a7e9d0cecd84b5437d03a2b715bcde52 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384036] "Edit application" missing in entries in search results
https://bugs.kde.org/show_bug.cgi?id=384036 --- Comment #2 from Simone Gaiarin --- Super fast! Thanks for your work. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 358116] messageviewer leaks temporary files with mail parts in it
https://bugs.kde.org/show_bug.cgi?id=358116 --- Comment #15 from Laurent Montel --- (In reply to Thomas Monjalon from comment #14) > About Ctrl+C, not a big issue, but strange. Issue with catching SIGINT? > > About your fix, is it cleaning temp files only on crash? Yep and others fix was already done. > My issue is that these files are filling /tmp when kmail is running. > Is it possible to avoid creating these files at the first place? nope it's not possible as we need to extract text from message or attachement for message. > Or could they be created in a subfolder of /tmp? messageviewer_XXX is not enough ? What is the advantage to create a subfolder ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 191917] Folders Panel: start in $HOME not /
https://bugs.kde.org/show_bug.cgi?id=191917 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Resolution|--- |FIXED Version|16.12.2 |16.12.3 Status|CONFIRMED |RESOLVED Version Fixed In||17.12.0 --- Comment #8 from Elvis Angelaccio --- Implemented in http://commits.kde.org/dolphin/94fab8c80ed60958043d13145aaf4c54412e052f -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384254] window title not updated when switching tab
https://bugs.kde.org/show_bug.cgi?id=384254 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I confirm it. I will work on it soon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 191917] Folders Panel: start in $HOME not /
https://bugs.kde.org/show_bug.cgi?id=191917 Elvis Angelaccio changed: What|Removed |Added Version|16.12.3 |17.08.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384257] New: KDE Crashes when closing applications in quick successions
https://bugs.kde.org/show_bug.cgi?id=384257 Bug ID: 384257 Summary: KDE Crashes when closing applications in quick successions Product: plasmashell Version: 5.9.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: supp...@bb-services.co.za CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.8-200.fc25.i686 i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: When multiple windows exists from various open aplications, closing them rapidly (using the top-right closing icon on the window) caused KDE to crash. (in my case (multiple Dolphins, multiple Evince pdf reader, LibreOffice Spreadsheet, and Opera Browser, + Thunderbird) -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb197d040 (LWP 1273))] Thread 11 (Thread 0x7e04eb40 (LWP 2898)): #0 0xb77b5cc9 in __kernel_vsyscall () #1 0xb48aae2c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb4ebe034 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/libQt5Core.so.5 #3 0xa9203090 in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*) () from /lib/libKF5ThreadWeaver.so.5 #4 0xa9203f78 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/libKF5ThreadWeaver.so.5 #5 0xa9208f8a in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #6 0xa9202fc7 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #7 0xa9208fde in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #8 0xa9202fc7 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #9 0xa9208fde in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #10 0xa9202fc7 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #11 0xa9208fde in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #12 0xa9202fc7 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #13 0xa92065b7 in ThreadWeaver::Thread::run() () from /lib/libKF5ThreadWeaver.so.5 #14 0xb4ebd87a in QThreadPrivate::start(void*) () from /lib/libQt5Core.so.5 #15 0xb48a54be in start_thread () from /lib/libpthread.so.0 #16 0xb4b55fc6 in clone () from /lib/libc.so.6 Thread 10 (Thread 0x7e84fb40 (LWP 2897)): #0 0xb77b5cc9 in __kernel_vsyscall () #1 0xb48aae2c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb4ebe034 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/libQt5Core.so.5 #3 0xa9203090 in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*) () from /lib/libKF5ThreadWeaver.so.5 #4 0xa9203f78 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/libKF5ThreadWeaver.so.5 #5 0xa9208f8a in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #6 0xa9202fc7 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #7 0xa9208fde in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #8 0xa9202fc7 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/libKF5ThreadWeaver.so.5 #9 0xa92065b7 in ThreadWeaver::Thread::run() () from /lib/libKF5ThreadWeaver.so.5 #10 0xb4ebd87a in QThreadPrivate::start(void*) () from /lib/libQt5Core.so.5 #11 0xb48a54be in start_thread () from /lib/libpthread.so.0 #12 0xb4b55fc6 in clone () from /lib/libc.so.6 Thread 9 (Thread 0x7f0fdb40 (LWP 2896)): #0 0xb77b5cc9 in __kernel_vsyscall () #1 0xb48aae2c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb4ebe034 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/libQt5Core.so.5 #3 0xa9203090 in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*) () from /lib/libKF5ThreadWeaver.so.5 #4 0xa9203f78 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/libKF5ThreadWeaver.so.5 #5 0xa9208f8a in ThreadWeaver::Working
[plasmashell] [Bug 384257] KDE Crashes when closing applications in quick successions
https://bugs.kde.org/show_bug.cgi?id=384257 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 381006 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381006] Crash after switching activities (QSortFilterProxyModelPrivate::updateChildrenMapping)
https://bugs.kde.org/show_bug.cgi?id=381006 David Edmundson changed: What|Removed |Added CC||supp...@bb-services.co.za --- Comment #22 from David Edmundson --- *** Bug 384257 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384049] Add an option for group icon-view frame
https://bugs.kde.org/show_bug.cgi?id=384049 Mohamed changed: What|Removed |Added Latest Commit|https://commits.kde.org/dig |https://commits.kde.org/dig |ikam/a487715b6de2258ec0584d |ikam/1a63597b76c83ccc5da380 |8daa485f4ba544d74f |26a517a79b6bc9f9f2 --- Comment #3 from Mohamed --- Git commit 1a63597b76c83ccc5da38026a517a79b6bc9f9f2 by Mohamed Anwer, on behalf of Maik Qualmann. Committed on 01/09/2017 at 09:10. Pushed by mohamedanwer into branch 'gsoc17-dlna'. add option to disable draw frames to grouped Items FIXED-IN: 5.7.0 M +2-1NEWS M +3-1app/items/imagedelegate.cpp M +2-0libs/settings/applicationsettings.cpp M +3-0libs/settings/applicationsettings.h M +10 -0libs/settings/applicationsettings_miscs.cpp M +3-0libs/settings/applicationsettings_p.cpp M +3-0libs/settings/applicationsettings_p.h M +8-2utilities/setup/setupmisc.cpp https://commits.kde.org/digikam/1a63597b76c83ccc5da38026a517a79b6bc9f9f2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382364] segfault after saying “no” to locale mismatch warning question
https://bugs.kde.org/show_bug.cgi?id=382364 Mohamed changed: What|Removed |Added Latest Commit|https://commits.kde.org/dig |https://commits.kde.org/dig |ikam/1a396687af3ed8889e44e3 |ikam/bb595216858426dde93af6 |fe1ac628d4893a7390 |85a4b7f58f81963a84 --- Comment #4 from Mohamed --- Git commit bb595216858426dde93af685a4b7f58f81963a84 by Mohamed Anwer, on behalf of Maik Qualmann. Committed on 31/08/2017 at 17:35. Pushed by mohamedanwer into branch 'gsoc17-healing'. fix crash after cancel the locale warning dialog FIXED-IN: 5.8.0 M +2-1NEWS M +8-1app/main/main.cpp M +1-1libs/album/albummanager.cpp https://commits.kde.org/digikam/bb595216858426dde93af685a4b7f58f81963a84 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 384258] New: kmymoney build fails with cmake 3.9
https://bugs.kde.org/show_bug.cgi?id=384258 Bug ID: 384258 Summary: kmymoney build fails with cmake 3.9 Product: kmymoney4 Version: git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: buildsystem Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- Created attachment 107638 --> https://bugs.kde.org/attachment.cgi?id=107638&action=edit full log Building kmymoney from git master branch with cmake 3.9 fails with the following error: [ 116s] CMake Error: The inter-target dependency graph contains the following strongly connected component (cycle): [ 116s] "onlinetask_interfaces" of type STATIC_LIBRARY [ 116s] depends on "onlinetask_unavailabletask" (weak) [ 116s] "onlinetask_unavailabletask" of type STATIC_LIBRARY [ 116s] depends on "onlinetask_interfaces" (weak) [ 116s] depends on "onlinetask_unavailabletask_autogen" (strong) [ 116s] "onlinetask_unavailabletask_autogen" of type UTILITY [ 116s] depends on "onlinetask_interfaces" (strong) [ 116s] At least one of these targets is not a STATIC_LIBRARY. Cyclic dependencies are allowed only among static libraries. [ 116s] -- Build files have been written to: /home/abuild/rpmbuild/BUILD/kmymoney-4.99.40.fb8c80ff/build [ 116s] error: Bad exit status from /var/tmp/rpm-tmp.Xo4GqZ (%build) [ 116s] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384222] Do not changed background on login screen
https://bugs.kde.org/show_bug.cgi?id=384222 David Edmundson changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #10 from David Edmundson --- >I'm power off my notebook. Then power on and on login I see correct new >background. So it worked \o/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382364] segfault after saying “no” to locale mismatch warning question
https://bugs.kde.org/show_bug.cgi?id=382364 Mohamed changed: What|Removed |Added Latest Commit|https://commits.kde.org/dig |https://commits.kde.org/dig |ikam/bb595216858426dde93af6 |ikam/a55f5291e75ac22e6e4185 |85a4b7f58f81963a84 |ef49be71cb5b44afe0 --- Comment #5 from Mohamed --- Git commit a55f5291e75ac22e6e4185ef49be71cb5b44afe0 by Mohamed Anwer, on behalf of Maik Qualmann. Committed on 01/09/2017 at 09:10. Pushed by mohamedanwer into branch 'gsoc17-dlna'. fix crash after cancel the locale warning dialog FIXED-IN: 5.8.0 M +2-1NEWS M +8-1app/main/main.cpp M +1-1libs/album/albummanager.cpp https://commits.kde.org/digikam/a55f5291e75ac22e6e4185ef49be71cb5b44afe0 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 384259] New: Akgregator wont start any method, ever.
https://bugs.kde.org/show_bug.cgi?id=384259 Bug ID: 384259 Summary: Akgregator wont start any method, ever. Product: akregator Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: raymun...@gmail.com Target Milestone: --- Application: akregator (5.6.0) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.12.8-2-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: freshly logging in - Unusual behavior I noticed: empty window border appears, then app crashes. - Custom settings of the application: none fresh install of kde and plasma on Arch. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff09e121900 (LWP 855))] Thread 25 (Thread 0x7fefe5f33700 (LWP 892)): #0 0x7ff0943991ad in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7ff0898190a5 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7ff089819587 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7ff08981a321 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7ff0898169eb in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7ff094393049 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7ff099f78f0f in clone () from /usr/lib/libc.so.6 Thread 24 (Thread 0x7fefe77fe700 (LWP 886)): #0 0x7ff0943991ad in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7ff086a62b04 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7ff086a62b49 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7ff094393049 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7ff099f78f0f in clone () from /usr/lib/libc.so.6 Thread 23 (Thread 0x7feff8f36700 (LWP 884)): #0 0x7ff0920bb239 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #1 0x7ff0920bbb3b in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7ff0920bbd1c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7ff09a8a3084 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7ff09a846ffb in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7ff09a66040e in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7ff09a66515b in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7ff094393049 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7ff099f78f0f in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7feff9b45700 (LWP 882)): #0 0x7ff099f6ee9d in poll () from /usr/lib/libc.so.6 #1 0x7ff0920bbc09 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7ff0920bbd1c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7ff09a8a3084 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7ff09a846ffb in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7ff09a66040e in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7ff098289030 in ?? () from /usr/lib/libKF5WebEngineViewer.so.5 #7 0x7ff09a66515b in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7ff094393049 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7ff099f78f0f in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7ff02cff9700 (LWP 877)): #0 0x7ff099f6ee9d in poll () from /usr/lib/libc.so.6 #1 0x7ff0920bbc09 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7ff0920bbd1c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7ff09a8a3084 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7ff09a846ffb in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7ff09a66040e in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7ff09a66515b in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7ff094393049 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7ff099f78f0f in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7ff02d7fa700 (LWP 876)): #0 0x7ff08122b99c in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0 #1 0x7ff08122bd9c in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #2 0x7ff08122be40 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #3 0x7ff081239e29 in ?? () from /usr/lib/libpulse.so.0 #4 0x7ff07896afe8 in ?? () from /usr/lib/pulseaudio/libpulsecommon-10.0.so #5 0x7ff094393049 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7ff099f78f0f in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7ff02dffb700 (LWP 875)): #0 0x7ff099f6ac0d in write () from /usr/lib/libc.so.6 #1 0x7ff099eff93d in _IO_new_fil
[kwin] [Bug 383948] window decoration/title bar: resizes on window resize
https://bugs.kde.org/show_bug.cgi?id=383948 Hugo Pereira Da Costa changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383948] window decoration/title bar: resizes on window resize
https://bugs.kde.org/show_bug.cgi?id=383948 --- Comment #5 from Hugo Pereira Da Costa --- Ok. Closing. Feel free to reopen if the problem reappears. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384187] [XP-Star] Graphics tablet buttons not working
https://bugs.kde.org/show_bug.cgi?id=384187 Alvin Wong changed: What|Removed |Added CC||alvinhoc...@gmail.com --- Comment #6 from Alvin Wong --- Are you sure it really works with 3.2.0 but not with 3.2.1? That's weird because I don't see any changes in the code that affect how keyboard input is handled. Have you tried rebooting after installing Krita 3.2.1? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 383403] Rotoscoping not working
https://bugs.kde.org/show_bug.cgi?id=383403 --- Comment #8 from alcinos --- Hi Roxane, Double clic on the project monitor (make sure it is not the clip monitor) should never trigger start playback. If you have no effects or have disabled on-screen widgets, it should toggle full-screen. If you do have a rotoscoping enabled for the current effect and double clicking toggles full-screen, make sure that on-screen widgets are enabled (square icon just on the right of the volume control icon, below the project monitor) Tell me how it goes. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68
https://bugs.kde.org/show_bug.cgi?id=384230 Tom Hughes changed: What|Removed |Added Attachment #107621|0 |1 is obsolete|| --- Comment #2 from Tom Hughes --- Created attachment 107639 --> https://bugs.kde.org/attachment.cgi?id=107639&action=edit Patch to ignore addr16 prefix on relative call So it seems that this isn't actually (as we first thought) a relative call with a 16 bit offset but rather is still a 32 bit offset but just with an (apparently redundant) addr16 prefix. This patch just ignores that prefix and has been confirmed to fix the problem. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 240726] Seperate shortcuts for play and pause
https://bugs.kde.org/show_bug.cgi?id=240726 James Hogan changed: What|Removed |Added CC||ja...@albanarts.com --- Comment #2 from James Hogan --- I have a slightly different use case for this. I have a set of bluetooth headphones (Plantronics backbeat pro) which has a sensor on the left side so it knows when you take it off your ear. When that happens it sends XF86AudioPause: KeyRelease event, serial 41, synthetic NO, window 0x9a1, root 0xd3, subw 0x9a2, time 67076582, (62,54), root:(1800,898), state 0x0, keycode 209 (keysym 0x1008ff31, XF86AudioPause), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False and when you put it back on your ear it sends XF86AudioPlay: KeyRelease event, serial 41, synthetic NO, window 0x9a1, root 0xd3, subw 0x9a2, time 67077375, (62,54), root:(1800,898), state 0x0, keycode 208 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES, XKeysymToKeycode returns keycode: 172 XLookupString gives 0 bytes: XFilterEvent returns: False It also has a play/pause button on that side, which again alternates sending separate XF86AudioPlay / XF86AudioPause. This works great on an android phone. if somebody wants your attention you just take it off your head and it pauses and then plays immediately when putting it back on. Trying to get that to work with amarok is a right pain, especially in combination with the Play/Pause button I have on my keyboard. I had a script which attempted it, but had issues with xmodmap and its since stopped working. At the moment I have Play mapped to Play/Pause, and have to press the button twice after putting it back on my head as it doesn't pause when taking it off, and pauses when i put it back on, then the button sends another pause followed by play on second press which amarok finally interprets as play. Frustrating. It'd be far better to have separate Play, Pause and PlayPause events which you can bind different keys to. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68
https://bugs.kde.org/show_bug.cgi?id=384230 --- Comment #3 from Laszlo Papp --- Yes, thank you so much for the quick replies and work. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384254] window title not updated when switching tab
https://bugs.kde.org/show_bug.cgi?id=384254 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/mes ||sagelib/e5b25cbd01bc0966bb8 ||f07032833cb9ace7b7585 Resolution|--- |FIXED Version Fixed In||5.7.0 --- Comment #2 from Laurent Montel --- Git commit e5b25cbd01bc0966bb8f07032833cb9ace7b7585 by Montel Laurent. Committed on 01/09/2017 at 11:50. Pushed by mlaurent into branch 'master'. Fix Bug 384254 - window title not updated when switching tab FIXED-IN: 5.7.0 M +1-1CMakeLists.txt M +6-0messagelist/src/core/widgetbase.cpp M +1-0messagelist/src/core/widgetbase.h M +9-0messagelist/src/pane.cpp M +3-0messagelist/src/pane.h https://commits.kde.org/messagelib/e5b25cbd01bc0966bb8f07032833cb9ace7b7585 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384254] window title not updated when switching tab
https://bugs.kde.org/show_bug.cgi?id=384254 --- Comment #3 from Laurent Montel --- Git commit e7f2298d6fe4a6c85ec865ce636fcb4122fe5637 by Montel Laurent. Committed on 01/09/2017 at 11:51. Pushed by mlaurent into branch 'master'. Fix Bug 384254 - window title not updated when switching tab M +1-1CMakeLists.txt M +1-0src/kmmainwidget.cpp https://commits.kde.org/kmail/e7f2298d6fe4a6c85ec865ce636fcb4122fe5637 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384260] New: Export to flickr includes un-checked tag group names
https://bugs.kde.org/show_bug.cgi?id=384260 Bug ID: 384260 Summary: Export to flickr includes un-checked tag group names Product: digikam Version: 5.6.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: syiad.al-d...@web.de Target Milestone: --- I have set up some group names for my tags, e.g. Place, Subject, etc., to sort them into a bit of a hierarchy. These are not used as tags themselves, but only to group tags like different places in the Place group. These group names get exported to flickr, if one of the tags in such a group is checked. However, I would like to only export the tags that are checked, not those un-checked at a higher level. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 384260] Export to flickr includes un-checked tag group names
https://bugs.kde.org/show_bug.cgi?id=384260 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Flickr Product|digikam |kipiplugins CC||caulier.gil...@gmail.com Assignee|digikam-bugs-n...@kde.org |imaging-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377312] Colosing of Plasma settings
https://bugs.kde.org/show_bug.cgi?id=377312 Christoph Feck changed: What|Removed |Added CC||it_li...@hotmail.com --- Comment #9 from Christoph Feck --- *** Bug 384252 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 384252] Taskbar disappears when Look and Feel changed
https://bugs.kde.org/show_bug.cgi?id=384252 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 377312 *** -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 384208] Umbrello crash after delete Directional Assotiation line
https://bugs.kde.org/show_bug.cgi?id=384208 Christoph Feck changed: What|Removed |Added Component|general |general Version|unspecified |frameworks5 Product|kde |umbrello Assignee|unassigned-b...@kde.org |umbrello-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384203] can't assign shortcut
https://bugs.kde.org/show_bug.cgi?id=384203 Christoph Feck changed: What|Removed |Added Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk Product|kde |plasmashell CC||plasma-b...@kde.org Version|unspecified |5.10.4 Component|general |Application Launcher ||(Kickoff) Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 384258] kmymoney build fails with cmake 3.9
https://bugs.kde.org/show_bug.cgi?id=384258 NSLW changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||lukasz.wojnilow...@gmail.co ||m --- Comment #1 from NSLW --- You're not at the latest commit. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 384155] Can't add new keys on 17.08, regression to 17.04
https://bugs.kde.org/show_bug.cgi?id=384155 Christoph Feck changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Christoph Feck --- It is possible that the port to stricter connections broke them, adding Laurent for inspection. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384250] PlasmaShell and systemsettings crash on Intel GPU 530
https://bugs.kde.org/show_bug.cgi?id=384250 --- Comment #1 from Christoph Feck --- Are you able to run 'kwin_x11' with OpenGL compositing? If yes, please start it, and add the output of qdbus org.kde.KWin /KWin supportInformation Otherwise, I guess your OpenGL drivers are not setup correctly. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #33 from Cristian Aravena Romero --- Created attachment 107640 --> https://bugs.kde.org/attachment.cgi?id=107640&action=edit k3b v17.11.90 (git) Hello, At night I try, already is the version of compiled k3b Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #34 from Thomas Schmitt --- Hi, i just did a git pull in my clone from git://anongit.kde.org/k3b.git and cannot see any related commit by git log. Can you point me to the changeset which puts the print statements into the code ? (My proposals are in https://bugs.kde.org/show_bug.cgi?id=381074#c15 ) Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 384078] dolphin thumbnailer coredump
https://bugs.kde.org/show_bug.cgi?id=384078 --- Comment #9 from Mr Tsui 徐先生 --- i dont think this is useful: kdeinit5: Shutting down running client. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #35 from Leslie Zhai --- Please use GDB to set breakpoint and print -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #36 from Cristian Aravena Romero --- (In reply to Leslie Zhai from comment #35) > Please use GDB to set breakpoint and print Hello Leslie ? Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #37 from Cristian Aravena Romero --- (In reply to Thomas Schmitt from comment #34) > Hi, > > i just did a git pull in my clone from git://anongit.kde.org/k3b.git > and cannot see any related commit by git log. > Can you point me to the changeset which puts the print statements into > the code ? > (My proposals are in > https://bugs.kde.org/show_bug.cgi?id=381074#c15 > ) Hello Thomas, How do I test? git ...? Regards, - Cristian -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384261] New: Assert failure on helgrind with the SIDT instruction
https://bugs.kde.org/show_bug.cgi?id=384261 Bug ID: 384261 Summary: Assert failure on helgrind with the SIDT instruction Product: valgrind Version: 3.13.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: helgrind Assignee: jsew...@acm.org Reporter: amadva...@gmail.com Target Milestone: --- A program that uses threading and the SIDT instruction makes helgrind to fail with the assertion failure: Helgrind: hg_main.c:4478 (instrument_mem_access): Assertion 'szB > 8 && szB <= 512' failed. In my understanding this happens because instrument_mem_access() expects memory accesses of size 1,2,4 and >=8 bytes, but not of 6 bytes, like the SIDT instruction is doing. Just changing the assert in hg_main.c to allow szB==6 makes helgrind to work. I'm using valgrind 13.0 compiled from source in a Ubuntu 14.04 x64 system running a 32 bit program. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 384240] Dolphin doesn't read samba shares when V1 smb protocol is disabled
https://bugs.kde.org/show_bug.cgi?id=384240 Elvis Angelaccio changed: What|Removed |Added Component|smb |default Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Product|kio |kio-extras CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384228] KWin crash when changing windows of programs
https://bugs.kde.org/show_bug.cgi?id=384228 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Martin Flöser --- Partially :-) The actual crash is in #5 0x7fe392062270 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #6 0x7fe391de05a2 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #7 0x7fe391bd0991 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #8 0x7fe391b956e0 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #9 0x7fe391b95b7a in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so And for that the backtrace still lacks all symbols. This would be the most interesting part. If you get the symbols for that you can report it to the radeon developers. Given the information we have it's completely outside of KWin's code (only frame #33 is from KWin). -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384253] Month view font display incomplete.
https://bugs.kde.org/show_bug.cgi?id=384253 Allen Winter changed: What|Removed |Added CC||win...@kde.org Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Allen Winter --- this has been fixed in version 5.6.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)
https://bugs.kde.org/show_bug.cgi?id=344433 Steffen Coenen changed: What|Removed |Added CC||tarding...@googlemail.com --- Comment #12 from Steffen Coenen --- I think I experience the same bug. I can fix it by setting MaxFPS and RefreshRate to 70 in kwinrc as described in another bug report but this leads to windows lagging behind the mouse cursor when moving them. Another bug report that might be the same bug. https://bugs.kde.org/show_bug.cgi?id=351700 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #38 from Thomas Schmitt --- Hi, @Cristian: Leslie asks you to run K3B under control of the program gdb, to set a "breakpoint" at line 257 of k3bemptydiscwaiter.cpp, and to let gdb print the desired variable content when it stops execution at that breakpoint. The desired info is listed in https://bugs.kde.org/show_bug.cgi?id=381074#c15 after my naive proposal to Leslie that he could try to reach the interesting location in the K3B code by help of CDEmu. @Leslie: We should concentrate on exploiting Cristian's willingness to build and run K3B, not try to give him a quick course in debugging. Can you make a git branch for Cristian and make a code change which prints the desired info in a user-visible way ? (Then post the git command line which fetches it. At least for me that would be necessary.) Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 383107] Crash when writing new mail
https://bugs.kde.org/show_bug.cgi?id=383107 --- Comment #3 from Axel Braun --- After current update (KMail 5.6.0, KDE 17.08) this can not be observed any longer -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 383169] Use a standard template to guide users unfamiliar with bug tracker style and etiquette
https://bugs.kde.org/show_bug.cgi?id=383169 Aleix Pol changed: What|Removed |Added CC||aleix...@kde.org, ||cf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 384262] New: Allow to use 7z to extract rar
https://bugs.kde.org/show_bug.cgi?id=384262 Bug ID: 384262 Summary: Allow to use 7z to extract rar Product: ark Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: plugins Assignee: rthoms...@gmail.com Reporter: cf...@kde.org CC: elvis.angelac...@kde.org Target Milestone: --- '7z' can extract .rar archives. Having neither 'rar' nor 'unrar' installed, but '7z' is installed, ark fails to open .rar archive files. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #39 from Thomas Schmitt --- Hi, just to summarize the riddle we are trying to solve: K3B reports to see an empty BD-R medium but in the same window demands to get fed by an empty medium of at least 21.4 GiB. An empty (in SCSI/MMC terms: "blank") BD-R should fulfill this demand. dvd+rw-mediainfo confirmed before the try that the medium is blank, offers 22.5 GiB in its default formatting size, or 23.3 GiB unformatted. So why doesn't K3B accept it ? Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 384262] Allow to use 7z to extract rar
https://bugs.kde.org/show_bug.cgi?id=384262 --- Comment #1 from Elvis Angelaccio --- IIRC rar support in 7z is read-only. The problem with ark is that the 7z plugin is read-write, so it expects a read-write backend. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384263] New: Crash to run plasma-discover
https://bugs.kde.org/show_bug.cgi?id=384263 Bug ID: 384263 Summary: Crash to run plasma-discover Product: Discover Version: 5.10.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: elfimov8...@gmail.com Target Milestone: --- Application: plasma-discover (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.12.8-2-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Application: Центр приложений Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff0f3356e40 (LWP 2872))] Thread 10 (Thread 0x7ff0b9d2f700 (LWP 2889)): #0 0x7ff0eea41029 in syscall () at /usr/lib/libc.so.6 #1 0x7ff0eed8e0e7 in __cxxabiv1::__cxa_guard_acquire(__cxxabiv1::__guard*) (g=0x7ff0ed9fd168) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/guard.cc:302 #2 0x7ff0ed74f94d in () at /usr/lib/libQt5Network.so.5 #3 0x7ff0ed74246c in () at /usr/lib/libQt5Network.so.5 #4 0x7ff0ef12e341 in () at /usr/lib/libQt5Core.so.5 #5 0x7ff0ef13215b in () at /usr/lib/libQt5Core.so.5 #6 0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7ff0e04cf700 (LWP 2888)): #0 0x7ff0eea41029 in syscall () at /usr/lib/libc.so.6 #1 0x7ff0eed8e0e7 in __cxxabiv1::__cxa_guard_acquire(__cxxabiv1::__guard*) (g=0x7ff0ed9fd168) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/guard.cc:302 #2 0x7ff0ed74f94d in () at /usr/lib/libQt5Network.so.5 #3 0x7ff0ed74246c in () at /usr/lib/libQt5Network.so.5 #4 0x7ff0ef12e341 in () at /usr/lib/libQt5Core.so.5 #5 0x7ff0ef13215b in () at /usr/lib/libQt5Core.so.5 #6 0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7ff0ba530700 (LWP 2882)): [KCrash Handler] #5 0x7ff0f318b8e8 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2 #6 0x7ff0f3193813 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #7 0x7ff0eea7fe44 in _dl_catch_error () at /usr/lib/libc.so.6 #8 0x7ff0f319315a in _dl_open () at /lib64/ld-linux-x86-64.so.2 #9 0x7ff0e936eea6 in () at /usr/lib/libdl.so.2 #10 0x7ff0eea7fe44 in _dl_catch_error () at /usr/lib/libc.so.6 #11 0x7ff0e936f5a7 in () at /usr/lib/libdl.so.2 #12 0x7ff0e936ef42 in dlopen () at /usr/lib/libdl.so.2 #13 0x7ff0ef31172e in () at /usr/lib/libQt5Core.so.5 #14 0x7ff0ef30af89 in QLibrary::load() () at /usr/lib/libQt5Core.so.5 #15 0x7ff0ed74f349 in () at /usr/lib/libQt5Network.so.5 #16 0x7ff0ed74f95a in () at /usr/lib/libQt5Network.so.5 #17 0x7ff0ed74246c in () at /usr/lib/libQt5Network.so.5 #18 0x7ff0ef12e341 in () at /usr/lib/libQt5Core.so.5 #19 0x7ff0ef13215b in () at /usr/lib/libQt5Core.so.5 #20 0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0 #21 0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7ff0bad31700 (LWP 2881)): #0 0x7ff0e90eaa84 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7ff0e90a5d26 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x7ff0ef370084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7ff0ef313ffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff0ef12d40e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7ff0ef13215b in () at /usr/lib/libQt5Core.so.5 #6 0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7ff0bbbd2700 (LWP 2880)): #0 0x7ffe68be4b52 in clock_gettime () #1 0x7ff0eea53546 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7ff0ef36f972 in () at /usr/lib/libQt5Core.so.5 #3 0x7ff0ef36e10a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7ff0ef36e6e6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7ff0ef36fdcf in () at /usr/lib/libQt5Core.so.5 #6 0x7ff0e90a5148 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7ff0e90a5b3b in () at /usr/lib/libglib-2.0.so.0 #8 0x7ff0e90a5d1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7ff0ef370084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7ff0ef313ffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7ff0ef12d40e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7ff0ef13215b in () at /usr/lib/libQt5Core.so.5 #13 0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.
[kwalletmanager] [Bug 384155] Can't add new keys on 17.08, regression to 17.04
https://bugs.kde.org/show_bug.cgi?id=384155 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwa ||lletmanager/2c8fc9dc93ed609 ||da154caac26773868ac716c42 Version Fixed In||17.08.1 --- Comment #2 from Laurent Montel --- Git commit 2c8fc9dc93ed609da154caac26773868ac716c42 by Montel Laurent. Committed on 01/09/2017 at 15:40. Pushed by mlaurent into branch 'Applications/17.08'. Fix Bug 384155 - Can't add new keys on 17.08, regression to 17.04 FIXED-IN: 17.08.1 M +1-1src/manager/kwmapeditor.cpp https://commits.kde.org/kwalletmanager/2c8fc9dc93ed609da154caac26773868ac716c42 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 353855] Media controls should be shown on lock screen.
https://bugs.kde.org/show_bug.cgi?id=353855 Vincent Petry changed: What|Removed |Added CC||pvinc...@yahoo.fr --- Comment #3 from Vincent Petry --- Works for me on Plasma 5.10.4 when either smplayer or amarok is running. Maybe it wasn't implemented back then ? Can you retry ? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] New: Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 Bug ID: 384264 Summary: Make it possible to disable media controls on lock screen Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: breeze-theme Assignee: plasma-b...@kde.org Reporter: pvinc...@yahoo.fr CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Basically implement this: https://github.com/KDE/plasma-workspace/blob/master/lookandfeel/contents/lockscreen/LockScreenUi.qml#L183 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 Martin Flöser changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- I'm against adding more options to the lock screen. As this is completely controlled by the Look'n'Feel package it's not possible for the lock screen to expose the options as it doesn't know what the current look'n'feel package provides. This would be highly confusing to users. Given that I prefer that such customization is moved outside the core feature set we provide. This should be provided in a specialized look and feel package provided by users on store.kde.org. We just cannot take on the maintenance burden for every customization a user wants. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #40 from Leslie Zhai --- I will add qDebug to print them next Monday, I am using my phone to reply :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] MacOS 10.12.x: UNKNOWN workq_ops option 128, and ud2 opcode
https://bugs.kde.org/show_bug.cgi?id=383723 --- Comment #2 from Andy --- Is there anything else I can provide to help with this? I'm afraid actually fixing it is beyond my capabilities. (It's a blocker for me - and anyone else trying to use valgrind for Qt-based apps on macOS it seems.) Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 CnZhx changed: What|Removed |Added CC||z...@cnzhx.net -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 --- Comment #2 from CnZhx --- (In reply to Martin Flöser from comment #1) > I'm against adding more options to the lock screen. As this is completely > controlled by the Look'n'Feel package it's not possible for the lock screen > to expose the options as it doesn't know what the current look'n'feel > package provides. This would be highly confusing to users. > > Given that I prefer that such customization is moved outside the core > feature set we provide. This should be provided in a specialized look and > feel package provided by users on store.kde.org. We just cannot take on the > maintenance burden for every customization a user wants. I think the OP didn't mean to add more options on the "lock screen" screen according to the comments on a post related to this topic. Maybe the title is a little implicit. When the media-controller-on-lock-screen feature was introduced, it has an option for disabling this feature in the qml (mentioned in comment #1). But this option is not exposed to user, so we cannot set it to be disabled unless we change the qml directly as root. Exposing this option to the setting/configuration for users is what we ask for. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384265] New: special mouse button assignement
https://bugs.kde.org/show_bug.cgi?id=384265 Bug ID: 384265 Summary: special mouse button assignement Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: martin.marmso...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Hello, I have a Mouse with special buttons. I can assign some actions to the mouse buttons when I call the workspace menu. But there is no possibility to assign global commands to the button. Is there a possibility to add a feature like this or is it due wayland port? -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 382680] 3.0.2 release build fails with cmake 3.9
https://bugs.kde.org/show_bug.cgi?id=382680 --- Comment #7 from Sumit Bhardwaj --- Quick comment: I was able to build after pulling from master. make test failed for 1 (out of 33) tests. I will take a look at failing test when I get time - probably next week. On Sat, Aug 26, 2017 at 6:15 AM, Robby Stephenson wrote: > https://bugs.kde.org/show_bug.cgi?id=382680 > > --- Comment #6 from Robby Stephenson --- > Should be fixed in [d3054ddb] now...thanks > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 --- Comment #3 from CnZhx --- Sorry, I mean comment #0 for the qml file. And, to keep it simple, I do not want the media controller to appear on the lock screen so that the lock screen can be the same as before the feature is introduced. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 321669] multipart mails incompletely displayed
https://bugs.kde.org/show_bug.cgi?id=321669 Manuel Mommertz <2...@gmx.de> changed: What|Removed |Added CC||2...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 384266] New: Muon needs the ability to select the data in the package history window for copying.
https://bugs.kde.org/show_bug.cgi?id=384266 Bug ID: 384266 Summary: Muon needs the ability to select the data in the package history window for copying. Product: muon Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: lnx...@westlot.net CC: silh...@gmail.com Target Milestone: --- The package history window in Muon Package Manager is great but there needs to be some way to select and copy the data. Knowing the location of the history file would be helpful in the meantime. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||elfimov8...@gmail.com --- Comment #28 from Antonio Rojas --- *** Bug 384263 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384263] Crash to run plasma-discover
https://bugs.kde.org/show_bug.cgi?id=384263 Antonio Rojas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||aro...@archlinux.org --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 380496 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)
https://bugs.kde.org/show_bug.cgi?id=383976 --- Comment #5 from Albert Astals Cid --- I've a very basic "fix" at https://phabricator.kde.org/D7644 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384267] New: Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow
https://bugs.kde.org/show_bug.cgi?id=384267 Bug ID: 384267 Summary: Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow Product: okular Version: 1.0.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: fm...@fhmtech.com Target Milestone: --- Since Macintosh System 6.5 days (showing my age!) I've set my text highlight color to a bright purple. This color's rare use in documents, my general liking for purple, and my long use of it for this purpose all conspire to quickly draw my eyes to highlighted text. I'm sure other users have their own equally valid preferences for text highlight color. KDE accommodates all of us by allowing each of us to set: System Settings: Appearance: Colors: Edit Scheme: Colors: Common Colors: Selection Background just how we like it. Most applications pick up this system setting and things Just Work(TM) as each of us wants. It appears that Okular does pick up and use the system-wide "Selection Background" color for its "Selection" tool. But then it seems to use a hard-coded bright yellow to highlight the background of text found via ctrl-f. At least, I've been unable to find a way to change this color to anything but the default bright yellow. Although this bright yellow often works acceptably to highlight found text, not being able to change it causes these problems: Problem 1) Using bright yellow to highlight found text conflicts with using the same bright yellow by default for Reviews: Pop-up Note, Inline Note, and Highlighter. This can make it difficult or impossible to locate highlighted found text in a heavily marked-up document. Several bugs have been opened over the years regarding this problem: Bug 355043 - Cannot differentiate between review and search highlights Bug 244049 - Search/find highlighting color should be different from annotation highlighting color Bug 237014 - Find tool when text has been highlighted Bug 273968 - Usability: change highlight color for text search and/or annotation Bug 330158 - Default colour of search highlighting is almost the same as annotation colour. Bug 317824 - Highlight color of search term is overlapping with annotation Bug 311034 - default search result and highlight colours are the same - usability problem Partial solution 1a) Newer Okular allows each of these Reviews colors to be changed, and that is much appreciated. But that alone does not completely solve this problem, because bright yellow is such a traditional color (and thus excellent default choice) for highlighting and sticky notes. A far better solution in my opinion is to keep using bright yellow for these Reviews purposes, and to change the found text background highlight color. Partial solution 1b) As noted in Bug 375735 - Option to change default highlight search color there's a patch on the way to draw a black outline around found text to help highlight it. While helpful, I'd argue that this is also an incomplete solution to this problem. A bright color is far more effective than a black outline at drawing my eyes to highlighted found text. Especially when working with documents like forms that already contain many black-outlined boxes. Problem 2) Hard-coding the found text highlight color is contrary to what users expect. Especially since KDE allows us to customize so many colors and themes to our liking, it's natural to assume that there's a KDE setting *somewhere* that will allow changing Okular's found text highlight color. So we spend time searching for the right setting to change, becoming increasingly frustrated when we can't find it. And eventually filing bugs like this one and the others linked. Proposed solution) I respectfully suggest that a future version of Okular highlight found text using the background color from System Settings: Appearance: Colors: Edit Scheme: Colors: Common Colors: Selection Background or another system-wide setting if that one is deemed more appropriate. Sincerely, Frank -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384267] Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow
https://bugs.kde.org/show_bug.cgi?id=384267 Frank Myhr changed: What|Removed |Added CC||fm...@fhmtech.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 384268] New: Gwenview segfaults with specific pictures since latest version
https://bugs.kde.org/show_bug.cgi?id=384268 Bug ID: 384268 Summary: Gwenview segfaults with specific pictures since latest version Product: gwenview Version: 17.08.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ma...@free.fr Target Milestone: --- Hi ! Using KDE Neon (non-LTS), since KDE apps upgraded from 14.04.3 to 17.08.0, gwenview segfaults with a specific set of pictures. Unfortunately, as those are private pictures (with pictures of children) I cannot make them public but I can give access to whoever asks. What occurs : open any of those pictures with gwenview : pic is displayed. Then hit spacebar to open the next one : instant segfault. Here is a gdb trace : https://framabin.org/?260d1410e39184c1#UXye4waTiONmBaCE8VdbEaw3iI8jhNIhLymes/cx6gU= Thread 1 "gwenview" received signal SIGSEGV, Segmentation fault. 0x72509b4f in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 (gdb) bt #0 0x72509b4f in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #1 0x72553f81 in Exiv2::Internal::PentaxMakerNote::printShutterCount(std::ostream&, Exiv2::Value const&, Exiv2::ExifData const*) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #2 0x77476016 in Exiv2::operator<< (md=..., os=...) at /usr/include/exiv2/metadatum.hpp:305 #3 Gwenview::ImageMetaInfoModelPrivate::fillExivGroup > (this=0x128bdf0, parent=..., group=group@entry=0xfba550, container=...) at /workspace/build/lib/imagemetainfomodel.cpp:276 #4 0x774731a3 in Gwenview::ImageMetaInfoModel::setExiv2Image (this=, image=0x7fbfc802dc50) at /workspace/build/lib/imagemetainfomodel.cpp:372 #5 0x77432a14 in Gwenview::Document::setExiv2Image (this=0x1288800, image=...) at /workspace/build/lib/document/document.cpp:395 #6 0x77431aa1 in Gwenview::AbstractDocumentImpl::setDocumentExiv2Image (this=this@entry=0x128fb90, image=...) at /workspace/build/lib/document/abstractdocumentimpl.cpp:82 #7 0x7743f1da in Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded (this=0x128fb90) at /workspace/build/lib/document/loadingdocumentimpl.cpp:491 #8 0x73e6ec19 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x73c65221 in QFutureWatcherBase::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7518f3fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x75196e07 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x73e42798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x73e44f7b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x73e98323 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fffed929197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fffed9293f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fffed92949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x73e9792f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x73e407ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x73e49704 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x00431dfa in main (argc=1, argv=) at /workspace/build/app/main.cpp:158 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 384268] Gwenview segfaults with specific pictures since latest version
https://bugs.kde.org/show_bug.cgi?id=384268 --- Comment #1 from Mahendra Tallur --- TYPO : I obiously meant : from 17.04.3 to 17.08.0. Please note : I assumed it occurs since KDE apps 17.08.0 because I'm pretty sure I watched them recently with no segfault, plus I started a liveCD (manjaro) containing KDE apps 17.04.3. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] MacOS 10.12.x: UNKNOWN workq_ops option 128, and ud2 opcode
https://bugs.kde.org/show_bug.cgi?id=383723 --- Comment #3 from John Reiser --- On 09/01/2017 09:18 AM, Andy wrote: > https://bugs.kde.org/show_bug.cgi?id=383723 > > --- Comment #2 from Andy --- > Is there anything else I can provide to help with this? I'm afraid actually > fixing it is beyond my capabilities. > > (It's a blocker for me - and anyone else trying to use valgrind for Qt-based > apps on macOS it seems.) > > Thanks! > Locate some good documentation on MacOS workq. Specifically, find the MacOS source code which handles all workq options, including those that correspond to the cases in PRE(workq_ops) in coregrind/m_syswrap/syswrap-darwin.c . The closest I could find after modest searching is https://opensource.apple.com/source/xnu/xnu-3789.51.2/bsd/kern/pthread_shims.c.auto.html Apparently there used to be a file pthread_synch.c but I cannot find it. I did find https://opensource.apple.com/source/libpthread/libpthread-137.1.1/kern/workqueue_internal.h which does have #define WQOPS_SET_EVENT_MANAGER_PRIORITY 0x80 /* max() in the provided priority in the the priority of the event manager */ and looks like a clue. If so, then option 128 could be a no-op for valgrind. Try that? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 382842] Segfault when opening certain image
https://bugs.kde.org/show_bug.cgi?id=382842 Antonio Rojas changed: What|Removed |Added CC||ma...@free.fr --- Comment #7 from Antonio Rojas --- *** Bug 384268 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 384268] Gwenview segfaults with specific pictures since latest version
https://bugs.kde.org/show_bug.cgi?id=384268 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 382842 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 279848] System freeze within 5 minutes after login
https://bugs.kde.org/show_bug.cgi?id=279848 Gilles Turgeon changed: What|Removed |Added CC||turg...@cgocable.ca -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 384268] Gwenview segfaults with specific pictures since latest version
https://bugs.kde.org/show_bug.cgi?id=384268 --- Comment #3 from Mahendra Tallur --- Hi ! Thanks for the fast triaging ! I'm so sorry, I tend to file duplicates although I always check before :-( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 383403] Rotoscoping not working
https://bugs.kde.org/show_bug.cgi?id=383403 Roxane changed: What|Removed |Added Resolution|WORKSFORME |FIXED Status|NEEDSINFO |RESOLVED --- Comment #9 from Roxane --- Hi, You're right, it plays when I click and goes full screen when I double click. It worked ! I actually had the show/hide edit mode not selected, I didn't even know what that was but now I know, thank you so much :D -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 Vincent Petry changed: What|Removed |Added Resolution|WONTFIX |FIXED --- Comment #4 from Vincent Petry --- In general, the reason I want to disable these controls is of privacy: when you leave your computer locked, curious people could just come to your desk and browse through your songs with the previous/next buttons. To achieve the desired results, I think we can look at different levels. 1) Adding a setting on the screen locker level >From my understand this doesn't fit the architecture, because a look and feel package is able to provide a free range of controls. The screen locker cannot guess what other kind of crazy controls a look and feel implementor would come up with. So this is clearly not a good solution. 2) Adding a setting on the look and feel level I'm not sure whether look and feel plugins are able to provide their own configuration pages and settings. If yes, then the setting could be added in the look and feel config page. Now I understand that adding one there might be an additional maintenance burden as it requires extra testing to make sure the enabling/disabling works correctly. 3) Implementing a separate look and feel that does not contain any media controls (or provides the setting from 2)) >From what I understand, people can publish their own look and feel plugins on https://store.kde.org So one alternative would be to clone the base look and feel and modify it (assuming the license permits, but I guess it does). The drawback here is that you need to regularily check if the original version has changed and pull the changes into the clone. Does QML support any kind of overlay ? If a look and feel was able to extend another one, then this extra version could simply modify that one. 3b) Modify the distro's custom look and feel For example openSUSE provides its own look and feel which also has the media buttons. Similar to 3) and 2), but the maintenance burden would then be on said distro look and feel maintainers. Also it doesn't have the benefit that it would apply to all possible distros out there. 4) Disabling the general media control engine I've noticed that many apps seem to be able to register themselves into some kind of media control engine/backend (not sure what it is called, data service?). This is likely the same engine into which the media buttons from the system tray are connecting to. Maybe there's a way to uninstall or disable this media engine and prevent any kind of media control buttons to appear anywhere, even on the systray (I personally don't use these). If not possible, then add a setting on this level. Might be a bit too advanced for regular users though. 5) Preventing your favorite media player to advertise itself to the media control engine This would require modifying the source code of said media player, or having a switch in the media player itself (ex: Amarok) to tell it to not connect to the media engine. This feels a bit too far fetched and patching source code is a no-go. 6) Automatically close the media player / clear playlist when screen is locked Likely too hacky and far-fetched. Any other ideas ? So far it seems that having an own look and feel might be the best. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] MacOS 10.12.x: UNKNOWN workq_ops option 128, and ud2 opcode
https://bugs.kde.org/show_bug.cgi?id=383723 --- Comment #4 from Andy --- Great - thanks John! Those MACH_SEND_TRAILER warnings you mentioned earlier were reported a couple of years ago: https://bugs.kde.org/show_bug.cgi?id=343306 Like you I cannot find any documentation on Darwin's workq except some source code. I found the most recent (released) version of workqueue_internal.h - for macOS 10.12.4: https://opensource.apple.com/source/libpthread/libpthread-218.1.3/kern/workqueue_internal.h.auto.html and where the WQOPS_SET_EVENT_MANAGER_PRIORITY case is processed (see _workq_kernreturn): https://opensource.apple.com/source/libpthread/libpthread-218.1.3/kern/kern_support.c.auto.html and where it is called with this value (see _pthread_workqueue_set_event_manager_priority): https://opensource.apple.com/source/libpthread/libpthread-218.1.3/src/pthread.c.auto.html Based on my reading I think you are correct and it can be ignored for valgrind's purposes because it's for scheduling priorities. Assuming I did things correctly to test this (simply adding "case 128: break;" to PRE(workq_ops)), it now crashes with an "Unrecognised instruction" instead: ==57909== Callgrind, a call-graph generating cache profiler ==57909== Copyright (C) 2002-2017, and GNU GPL'd, by Josef Weidendorfer et al. ==57909== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info ==57909== Command: /Users/maloney/dev/build-test-valgrind/test-valgrind.app/Contents/MacOS/test-valgrind ==57909== ==57909== For interactive control, run 'callgrind_control -h'. --57909-- run: /usr/bin/dsymutil "/Users/maloney/dev/build-test-valgrind/test-valgrind.app/Contents/MacOS/test-valgrind" --57909-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option --57909-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times) --57909-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times) ==57909== valgrind: Unrecognised instruction at address 0x104018b50. ==57909==at 0x104018B50: _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x1040168FB: _dispatch_client_callout (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x1040168B8: dispatch_once_f (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x104018A90: _dispatch_kq_update (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x10401A0CD: _dispatch_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x10401A03D: _dispatch_source_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x104019E85: _dispatch_source_kevent_register (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x104029651: _dispatch_queue_resume_finalize_activation (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x105AE43C0: _notify_lib_init (in /usr/lib/system/libsystem_notify.dylib) ==57909==by 0x105AE49AB: notify_register_dispatch (in /usr/lib/system/libsystem_notify.dylib) ==57909==by 0x1049FE916: CFUniCharMapTo (in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation) ==57909==by 0x1040168FB: _dispatch_client_callout (in /usr/lib/system/libdispatch.dylib) ==57909== Your program just tried to execute an instruction that Valgrind ==57909== did not recognise. There are two possible reasons for this. ==57909== 1. Your program has a bug and erroneously jumped to a non-code ==57909==location. If you are running Memcheck and you just saw a ==57909==warning about a bad jump, it's probably your program's fault. ==57909== 2. The instruction is legitimate but Valgrind doesn't handle it, ==57909==i.e. it's Valgrind's fault. If you think this is the case or ==57909==you are not sure, please let us know and we'll try to fix it. ==57909== Either way, Valgrind will now raise a SIGILL signal which will ==57909== probably kill your program. ==57909== ==57909== Process terminating with default action of signal 4 (SIGILL) ==57909== Illegal opcode at address 0x104018B50 ==57909==at 0x104018B50: _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x1040168FB: _dispatch_client_callout (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x1040168B8: dispatch_once_f (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x104018A90: _dispatch_kq_update (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x10401A0CD: _dispatch_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x10401A03D: _dispatch_source_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x104019E85: _dispatch_source_kevent_register (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x104029651: _dispatch_queue_resume_finalize_activation (in /usr/lib/system/libdispatch.dylib) ==57909==by 0x105AE43C0: _notify_lib_init (in /usr/lib/system/libsystem_notify.dylib) ==57909==by 0x105AE49AB: notify_register_dispatch (in /usr/lib/system/libsystem_notify.dylib) ==57909==by 0x1049FE916: CFUniCharMapTo (in /System/Library/Fram
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 Vincent Petry changed: What|Removed |Added Resolution|FIXED |WONTFIX --- Comment #5 from Vincent Petry --- Setting back to WONTFIX for now, sorry (not sure how this slipped) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 353547] krunner uses 726GiB (Gigabytes!) of virtual memory - mapped the baloo index ~3000 times
https://bugs.kde.org/show_bug.cgi?id=353547 --- Comment #13 from Pranav Ashok --- I have the same issue too, though it doesn't seem to causing any problems. I'm on Kubuntu 17.04, Plasma 5.9.5, krunner uses 256G virtual memory. ➜ balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 48024 / 48024 files Current size of index is 378,46 MiB -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384267] Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow
https://bugs.kde.org/show_bug.cgi?id=384267 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Severity|normal |wishlist --- Comment #1 from Albert Astals Cid --- No, that solution doesn't work, because people that use dark themes (where selection is usually a white-ish color) would not see the selection when reading PDFs (that usually have a white background). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 --- Comment #3 from Egmont Koblinger --- (In reply to RJVB from comment #2) > Currently Konsole emulates well-known terminals, but it could > very well define its own terminal type [...] As far as I know, konsole has been there, it used to work with TERM=konsole or something similar. I guess they had their reason to go for TERM=xterm (or a variant thereof) instead. gnome-terminal has also been there, it used to set TERM=gnome or maybe TERM=vte. It also had its reason to revert. Probably both approaches have their own downsides, but apparently both projects decided that going with TERM=xterm sucks less. > FWIW, clear sends this to an xterm: `ESC[HESC[2J` This is the old fashioned one that does not clear the scrollback. The new version is: ESC[3J -> clears the scrollback ESC[H -> moves the cursor to the upper left corner ESC[2J -> clears the onscreen contents For the first one, I can't think of any other possible reasonable behavior than either clearing the scrollback, or not doing anything. I'll get back to this. For the middle one there's not much to discuss, changing its behavior in any way would probably break tons of apps. Also it's pretty much irrelevant to this bug. For the last one, this is where konsole and VTE (gnome-terminal and friends) differ from xterm and scroll out these lines to the scrollback buffer. I'll get back to this too. > The other possibility might be to support E3 (might also require shipping a > dedicated terminfo file!), catch whatever specific `clear` sends to the tty > as a result, and the provide a profile option whether or not the scrollback > buffer should be cleared. The simple presence of that E3 command indicates > that a clear was requested. So... Let's first see the old behavior where \e[3J wasn't emitted or wasn't yet supported by the terminal emulator, or assume that there's a profile setting implemented where the user disables this feature. Then: - The traditional way, xterm's approach wipes out the onscreen contents, but the scrollback remains intact. That is, effectively, a screenful of lines will go missing from the scrollback. From a usability point of view, this doesn't make any sense to me. - Hence here come konsole and vte which modify this and scroll out these lines. The behavior is now sane, I get to see the proper history in the scrollback. Now let's introduce the "clear scrollback" feature. - The traditional way, xterm's now makes sense when you execute "clear". You pretty much get a "clean start". (It still doesn't make too much sense with let's say hitting Ctrl+L in bash which does an old-fashioned clear, without clearing the scrollback.) - konsole's and vte's behavior no longer make too much sense with the "clear" command, at least a screenful of empty lines appear in the scrollback – this is what your bugreport is about. (It still makes sense with e.g. bash's Ctrl+L.) So we already see a damn complicated support matrix of all possible scenarios with no straightforward way of getting all possibilities work as expected. One idea that occurred to me but I don't find it a good one: If a config option is introduced to enable/disable wiping out the scrollback (i.e. whether to support \e[3J or not), this same option could also change the behavior of \e[2J (current vs. xterm-compatible). This would "fix" the "clear" command, but would probably cause even more breakage and confusion for bash's Ctrl+L. Also, it's not the way terminal emulators should work. It shouldn't be the escape sequence emitted by the app defining how the terminal emulation should be done, it's the other way around. The terminal emulation behavior should determine what the app in turn emits. Also ugly as hell and other unforeseen side effects are also possible. Another possible approach, although I'm really unsure if the relevant person could be convinced to adapt terminfo to konsole's and vte's xterm-incompatible behavior: Alter the sequence emitted by "clear" so that wiping out the scrollback is the last step. (Doing this would indeed be simpler if konsole used its own TERM.) Yet another possibility is to drop \e[3J support, for reasons outlined in the already mentioned https://bugzilla.gnome.org/show_bug.cgi?id=771953. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384267] Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow
https://bugs.kde.org/show_bug.cgi?id=384267 --- Comment #2 from Frank Myhr --- @Albert Astals Cid: You're right, I didn't think of that as I don't personally use dark themes. Hmm... how about using system Selection Background color for the found text highlight, and its inverse color to draw a box around this highlight. And an option to invert these colors in case that works better with the theme in use? Perhaps someone who uses dark themes can chime in... Thanks, Frank -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] MacOS 10.12.x: UNKNOWN workq_ops option 128, and ud2 opcode
https://bugs.kde.org/show_bug.cgi?id=383723 --- Comment #5 from John Reiser --- The crash looks very similar to the 'ud2' diagnosed in the original Description. In particular, the offset 0xb50 is the same. This probably indicates that valgrind has more-or-less completely missed some aspect of what MacOS is doing. We need advice from an expert. So, spend two weeks at the bar/pub/tavern/restaurants in Cupertino and Sunnyvale. Buy a beer for the next 10 people who enter. Chat them up. Apply dtruss and/or dtrace to the original program without valgrind, and to valgrind when running the program. Correlate the system calls between the two runs; try to understand the difference. [Also investigate "valgrind --trace-syscalls=yes ..." as an additional or alternate source of information.] That's quite tedious, but logically should work. Also, contrast with running on Linux (which uses 'strace'). The Qt implementation might be similar enough to provide a clue. -- You are receiving this mail because: You are watching all bug changes.
