[plasmashell] [Bug 420325] New: plasmashell crash.
https://bugs.kde.org/show_bug.cgi?id=420325 Bug ID: 420325 Summary: plasmashell crash. Product: plasmashell Version: 5.18.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mackel13411987...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.4-1-default x86_64 Windowing system: X11 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: When I open the handbrake - Unusual behavior I noticed: - Custom settings of the application: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9a3550b440 (LWP 1799))] Thread 25 (Thread 0x7f99c17fa700 (LWP 2964)): #0 0x7f9a36c9b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a3781f1db in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9a3781f299 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f9a3952c59f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f9a3952c819 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f9a37819698 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f9a36c94efa in start_thread () at /lib64/libpthread.so.0 #7 0x7f9a374a73bf in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f999700 (LWP 2585)): #0 0x7f9a36c9b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a3781f1db in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9a3781f299 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f9a3952c59f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f9a3952c819 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f9a37819698 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f9a36c94efa in start_thread () at /lib64/libpthread.so.0 #7 0x7f9a374a73bf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f99c1ffb700 (LWP 2489)): #0 0x7f9a36c9b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a3781f1db in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9a3781f299 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f9a1e1976b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f9a1e197a1a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f9a1e197a71 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f9a1e18fcce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f9a1e19709b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f9a37819698 in () at /usr/lib64/libQt5Core.so.5 #24 0x7f9a36c94efa in start_thread () at /lib64/libpthread.so.0 #25 0x7f9a374a73bf in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f99c27fc700 (LWP 2488)): #0
[plasmashell] [Bug 420325] plasmashell crash.
https://bugs.kde.org/show_bug.cgi?id=420325 --- Comment #1 from mackel zhag --- Created attachment 127702 --> https://bugs.kde.org/attachment.cgi?id=127702=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420260] Segfault when opening anything (master)
https://bugs.kde.org/show_bug.cgi?id=420260 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- Created attachment 127701 --> https://bugs.kde.org/attachment.cgi?id=127701=edit GDB backtrace I can confirm this on my end, and it happens with both my build from master and a recent AppImage. My backtrace is attached, too. What seems to solve it most of the time is if I move my resources folder and let Krita regenerate the default one on next startup. Then I can move my resources back and when I restart Krita it still manages to open documents. After I update my build, the crash usually returns, if that makes any sense. Additionally, I think the same kind of crash happens after editing and resetting brush presets. The first part of that backtrace looks identical the attached one. To reproduce: 1. Pick a (default) brush preset and edit some of its settings. 2. Press the reset icon to undo the temporary changes, then click on another preset. Krita freezes and quits for me at that point. Let me know if I should move the latter to a separate bug report. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420324] New: Unable to load application
https://bugs.kde.org/show_bug.cgi?id=420324 Bug ID: 420324 Summary: Unable to load application Product: Discover Version: 5.18.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ssh.nur.az...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 127700 --> https://bugs.kde.org/attachment.cgi?id=127700=edit discovery unable to load SUMMARY STEPS TO REPRODUCE 1. open discovery 2. unable to load home though it's connected to the internet 3. see screenshot OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 420323] New: All KSysguard windows return 'mainwindow#1' as window role.
https://bugs.kde.org/show_bug.cgi?id=420323
Bug ID: 420323
Summary: All KSysguard windows return 'mainwindow#1' as window
role.
Product: ksysguard
Version: 5.18.4
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: ksysguard
Assignee: ksysguard-b...@kde.org
Reporter: i...@kintsugi-computers.org
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
When launching two instances of Ksysguard both are labelled as 'mainwindow#1'
and it is not possible to apply separate KWin rules to each.
STEPS TO REPRODUCE
1. Launch Ksysguard twice.
2. Detect window properties for each with the KWin configuration tool.
3. Try to set separate placement rules for each.
OBSERVED RESULT
KWin treats them both as the same window and applies the same rules to each.
Other KDE applications I have tried do not appear to do this.
EXPECTED RESULT
Kwin correctly detects the window role ('mainwindow#1', 'mainwindow#2' and so
forth) and can apply placement rules separately.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.4 / KDE Neon
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 420317] Python wrapper creates a non-None Node for null parent (which causes an assert)
https://bugs.kde.org/show_bug.cgi?id=420317 Tymond changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/2a391d814b0a46 |krita/commit/94a83a77a47237 |624bd8ddd6b29ae1498397187c |71b9b8030a60fbd38ef209b7c8 --- Comment #2 from Tymond --- Git commit 94a83a77a4723771b9b8030a60fbd38ef209b7c8 by Agata Cacko. Committed on 20/04/2020 at 01:14. Pushed by tymond into branch 'master'. Fix assert on Node::parentNode() for root Before this commit, because of both parentNode() not checking for parent() existing and createNode() not checking for the node existing (which in this case was originalNode->parent()), trying to access parentNode() of root node would result in an assert or crash. This commit fixes that behaviour in both places. (cherry picked from commit 2a391d814b0a46624bd8ddd6b29ae1498397187c) M +4-0libs/libkis/Node.cpp https://invent.kde.org/kde/krita/commit/94a83a77a4723771b9b8030a60fbd38ef209b7c8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420317] Python wrapper creates a non-None Node for null parent (which causes an assert)
https://bugs.kde.org/show_bug.cgi?id=420317 Tymond changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/2a391d814b0a46 ||624bd8ddd6b29ae1498397187c Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Tymond --- Git commit 2a391d814b0a46624bd8ddd6b29ae1498397187c by Agata Cacko. Committed on 20/04/2020 at 01:07. Pushed by tymond into branch 'krita/4.3'. Fix assert on Node::parentNode() for root Before this commit, because of both parentNode() not checking for parent() existing and createNode() not checking for the node existing (which in this case was originalNode->parent()), trying to access parentNode() of root node would result in an assert or crash. This commit fixes that behaviour in both places. M +4-0libs/libkis/Node.cpp https://invent.kde.org/kde/krita/commit/2a391d814b0a46624bd8ddd6b29ae1498397187c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420322] New: Krita crashing instantly on certain files
https://bugs.kde.org/show_bug.cgi?id=420322 Bug ID: 420322 Summary: Krita crashing instantly on certain files Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: triggerpigk...@protonmail.com Target Milestone: --- Created attachment 127699 --> https://bugs.kde.org/attachment.cgi?id=127699=edit One of the files crashing Krita SUMMARY I upgraded to the Krita nightly build "krita-nightly-x64-v4.3.0-prealpha-1511-gb8bc4d6cf2" from a much older version, it worked smoothly at first however since a few hours ago it is crashing to desktop instantaneously on certain files. It is leaving no crash-log but is mentioned in the logfile so i'll paste the last few instances here. This happens whether I open it from inside the program via open file, or via desktop. I have also attached a copy of one of the files crashing. Other Krita files seem to be working fine so it does'nt appear to be a file type issue, i've not seen crashes on anything but Krita files either but I can't confirm if that's the case for certain. This is my first bug report, sorry if it's missing some information or if I've placed it wrong, tried to put as much in as I could think of. SESSION: 20 Apr 2020 01:26:33 +0100. Executing C:\Users\trigg\Downloads\New folder\krita-nightly-x64-v4.3.0-prealpha-1511-gb8bc4d6cf2\krita-nightly-x64-v4.3.0-prealpha-1511-gb8bc4d6cf2\bin\krita.exe Krita Version: 4.3.0-prealpha (git b8bc4d6), Qt version compiled: 5.12.7, loaded: 5.12.7. Process ID: 11652 -- -- -- -- -- -- -- -- 20 Apr 2020 01:32:14 +0100: Importing application/x-krita to application/x-krita. Location: C:/Users/trigg/OneDrive/Desktop/Eve The Elf/Page1-.kra. Real location: C:/Users/trigg/OneDrive/Desktop/Eve The Elf/Page1-.kra. Batchmode: 0 20 Apr 2020 01:32:14 +0100: ASSERT (krita): "m_buffer[currentIndex].loadAcquire() > 0" in file C:\Packaging\workspace\Krita_Stable_Windows_Build\krita\libs\image\tiles3\KisTiledExtentManager.cpp, line 87 SESSION: 20 Apr 2020 01:36:28 +0100. Executing C:\Users\trigg\Downloads\New folder\krita-nightly-x64-v4.3.0-prealpha-1511-gb8bc4d6cf2\krita-nightly-x64-v4.3.0-prealpha-1511-gb8bc4d6cf2\bin\krita.exe Krita Version: 4.3.0-prealpha (git b8bc4d6), Qt version compiled: 5.12.7, loaded: 5.12.7. Process ID: 17844 -- -- -- -- -- -- -- -- 20 Apr 2020 01:37:39 +0100: Importing application/x-krita to application/x-krita. Location: C:/Users/trigg/OneDrive/Desktop/dailysketch.kra. Real location: C:/Users/trigg/OneDrive/Desktop/dailysketch.kra. Batchmode: 0 20 Apr 2020 01:37:40 +0100: ASSERT (krita): "m_buffer[currentIndex].loadAcquire() > 0" in file C:\Packaging\workspace\Krita_Stable_Windows_Build\krita\libs\image\tiles3\KisTiledExtentManager.cpp, line 87 SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420321] New: 1000 based number to words grouping is not suitable for Korean language
https://bugs.kde.org/show_bug.cgi?id=420321 Bug ID: 420321 Summary: 1000 based number to words grouping is not suitable for Korean language Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: k...@peremen.name Target Milestone: --- SUMMARY According to plugins/checkprinting/numbertowords.cpp, the grouping of numbers for conversion into human readable form is hard-coded into groups of 1000: Thousand, Million, Billion. However this scale does not fit into numbers used in Korean language, as numbers are grouped by 1 (instead of 1000) and more than billion (short scale) is often discussed as a monetary unit in Korean language. Let me give some example: * 10,000 KRW should be converted into "일만원". We have a separate noun for 10,000, not calling them as an equivalent of "ten thousand". * 3,000,000 KRW should be converted into "삼백만원", literally meaning 300 * 1. There is no equivalent word of "million", and we don't call them in "three million". * 200,000,000 KRW should be converted into "이억원". We have a separate noun for 100,000,000, not calling them as an equivalent of "two hundred million". * When it comes to the budget of small to medium sized companies, more than hundred billion KRW is not unheard of. At least numerals for 10^12 and 10^16 is not unheard of in newspapers. I don't know where and how to address this situation. The same 1 base grouping is also used in Chinese/Japanese language too. See also: https://en.wikipedia.org/wiki/Chinese_numerals#Large_numbers -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420320] New: Black screen and no audio as a result of a render
https://bugs.kde.org/show_bug.cgi?id=420320 Bug ID: 420320 Summary: Black screen and no audio as a result of a render Product: kdenlive Version: 18.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: fflisjdppokgcli...@ttirv.net Target Milestone: --- BUG DESCRIPTION When I edit one mp4 file (add the Dissolve effect to both its beginning and its end and lower the volume of the audio at one point) and I render it, I get a black screen with no sound. This is funny, because all of my other videos render correctly (albeit none of them is as long as this particular file - this one is about 35 minutes long). I checked the Project settings - I recorded the original mp4 video with Kazam on my 1920x1080 screen using 30 FPS. I used the Project Settings for 1080p HD 30 fps video. I also tried other Project settings. Same result - black screen, no audio. Is this maybe related to the length of the clip? On the shorter clips it renders normally. SOFTWARE/OS VERSIONS Linux: Debian 10 Buster -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420315] Leave actions do nothing (cannot log out or shutdown from plasma)
https://bugs.kde.org/show_bug.cgi?id=420315 Francis T changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Francis T --- I'm running my development version from ~/kde/..., using the install-sessions.sh script as described here: https://community.kde.org/Get_Involved/development dbus is 1.12.16-5. I'm not sure how recently it was pushed to manjaro repositories, unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377653] Default window size too small
https://bugs.kde.org/show_bug.cgi?id=377653
Nate Graham changed:
What|Removed |Added
Latest Commit|https://cgit.kde.org/plasma |https://commits.kde.org/pla
|-desktop.git/commit/?id=8e0 |sma-desktop/8e0f525a9633110
|f525a96331102cdb3d20aadbc4c |2cdb3d20aadbc4cd8508e5146
|d8508e5146 |
--- Comment #6 from Nate Graham ---
Git commit 8e0f525a96331102cdb3d20aadbc4cd8508e5146 by Nate Graham.
Committed on 19/04/2020 at 22:43.
Pushed by ngraham into branch 'Plasma/5.18'.
[KCMs/Standard Actions] Give KCMShell window a sane default size
Summary:
FIXED-IN: 5.18.5
Test Plan:
Before: {F7884930}
After: {F7884929}
Reviewers: #plasma
Subscribers: cfeck, davidedmundson, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D26695
M +3-0kcms/standard_actions/standard_actions_module.cpp
https://commits.kde.org/plasma-desktop/8e0f525a96331102cdb3d20aadbc4cd8508e5146
--
You are receiving this mail because:
You are watching all bug changes.
[kdelibs] [Bug 341072] Missing imperial gallons and US pints
https://bugs.kde.org/show_bug.cgi?id=341072 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Nate Graham --- These units were added more than a year ago, in Frameworks 5.53. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 420143] Kid3 - Does not tag DSF files larger than 2GB
https://bugs.kde.org/show_bug.cgi?id=420143 --- Comment #5 from Christophe --- Hello, I confirm the problem is fixed, for DSF files, with the "dev" version you proposed for downloading. Many thanks. Regards On 19/04/2020 19:45, Urs Fleisch wrote: > https://bugs.kde.org/show_bug.cgi?id=420143 > > --- Comment #2 from Urs Fleisch --- > I have investigated the issue further. It only happens on Windows because on > Linux and macOS, long values are 64-bit on 64-bit architectures whereas on > Windows long is always 32-bit. To fix this, all variables which are used to > index data from a large file have to be replaced by a 64-bit type. I have > patched the TagLib which is used to build the Windows 64-bit edition. I have > tested it with large MP4, MP3, FLAC and Opus files, but not with a large DSF > file, simply because I do not have a DSF file larger than 2GB and I do not > know > how to easily create such a file (for the other formats it can be done using > ffmpeg). The DSF format seems to be quite simple, so I could have created such > a file containing large invalid data, but probably it is easier if you test it > with your files. So please get the win32-x64.zip file from > https://sourceforge.net/projects/kid3/files/kid3/development/ and tell me if > it > works. > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420319] New: DVD Sturcture Broken (old bug: 403128)
https://bugs.kde.org/show_bug.cgi?id=420319
Bug ID: 420319
Summary: DVD Sturcture Broken (old bug: 403128)
Product: kdenlive
Version: unspecified
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Video Display & Export
Assignee: j...@kdenlive.org
Reporter: richard.sutherland...@gmail.com
Target Milestone: ---
SUMMARY
Exact Same as this bug: 403128
https://www.mail-archive.com/search?l=kde-bugs-dist@kde.org=subject:%22%5C%5Bkdenlive%5C%5D+%5C%5BBug+403128%5C%5D+Creating+DVD+image%5C%3A+DVD+structure+broken%22=newest
v. 20.7.70
On the currently nightly build: 367
STEPS TO REPRODUCE
1. Open kdenlive
2. File-->DVD Wizard
3. Load Project/Add Movie Files/Next
4. Add Chapters works! Next
5. Create Menu (or load from project load)/Next
6. Create Iso Image; as process continues, gets to DVD Structure creation and
fails with "DVD Structure Broken"
OBSERVED RESULT
Errors out ("DVD Structure Broken") See video: https://jwp.io/s/DwVbbH0v
EXPECTED RESULT
Iso would be created;
SOFTWARE/OS VERSIONS
Windows: 10
macOS: n/a
Linux/KDE Plasma: n/a
(available in About System)
KDE Plasma Version: n/a
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
ADDITIONAL INFORMATION
DVDAuthor: 072
mkisofs: 2.01
genisoimage: 1.1.11-1
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 377653] Default window size too small
https://bugs.kde.org/show_bug.cgi?id=377653 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://cgit.kde.org/plasma ||-desktop.git/commit/?id=8e0 ||f525a96331102cdb3d20aadbc4c ||d8508e5146 Version Fixed In||5.18.5 Resolution|--- |FIXED --- Comment #5 from Nate Graham --- Fixed by https://cgit.kde.org/plasma-desktop.git/commit/?id=8e0f525a96331102cdb3d20aadbc4cd8508e5146 (not sure why the bug didn't get closed automatically) -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 420143] Kid3 - Does not tag DSF files larger than 2GB
https://bugs.kde.org/show_bug.cgi?id=420143 --- Comment #4 from Christophe --- Hello Urs, Thank you very much for your investigation and fixing. As we're confined in France, I work from home but it's also the opportunity, to rip my collection of SACDs. I test this ASAP and get back to you. Regards, Christophe PS : I found another issue due to file name length but workaround is easier, for tagging files larger 2GB I used Mp3Tag as workaround but Kid3 is a greater interface with useful features On 19/04/2020 19:45, Urs Fleisch wrote: > https://bugs.kde.org/show_bug.cgi?id=420143 > > --- Comment #2 from Urs Fleisch --- > I have investigated the issue further. It only happens on Windows because on > Linux and macOS, long values are 64-bit on 64-bit architectures whereas on > Windows long is always 32-bit. To fix this, all variables which are used to > index data from a large file have to be replaced by a 64-bit type. I have > patched the TagLib which is used to build the Windows 64-bit edition. I have > tested it with large MP4, MP3, FLAC and Opus files, but not with a large DSF > file, simply because I do not have a DSF file larger than 2GB and I do not > know > how to easily create such a file (for the other formats it can be done using > ffmpeg). The DSF format seems to be quite simple, so I could have created such > a file containing large invalid data, but probably it is easier if you test it > with your files. So please get the win32-x64.zip file from > https://sourceforge.net/projects/kid3/files/kid3/development/ and tell me if > it > works. > -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 419105] Process still running when closing k3b after changing the splash screen visibility flag
https://bugs.kde.org/show_bug.cgi?id=419105 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/k3b ||/aa7df7817b88bd5a571dfce6c3 ||ba4777830efedf Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Albert Astals Cid --- Git commit aa7df7817b88bd5a571dfce6c3ba4777830efedf by Albert Astals Cid. Committed on 19/04/2020 at 22:10. Pushed by aacid into branch 'release/20.04'. Fix k3b not finishing if started without splash screen M +3-5src/k3bapplication.cpp https://commits.kde.org/k3b/aa7df7817b88bd5a571dfce6c3ba4777830efedf -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 --- Comment #4 from andreas.sturmlech...@gmail.com --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 --- Comment #3 from David Edmundson --- Oh, I certainly meant do it when you asked. Done now. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #104 from Nick Stefanov --- My icon cache is in RAM and is being deleted on every reboot :) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 420318] New: ItemRetrievalRequest heap-use-after-free
https://bugs.kde.org/show_bug.cgi?id=420318 Bug ID: 420318 Summary: ItemRetrievalRequest heap-use-after-free Product: Akonadi Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: lukas.ka...@centrum.cz Target Milestone: --- Akonadi crash sometimes on my machine. To get better idea where the bug is, I build akonadi server with address sanitizer ( -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_CXX_FLAGS=-fsanitize=address ). It shows me heap-use-after-free: ==772029==ERROR: AddressSanitizer: heap-use-after-free on address 0x604000272a90 at pc 0x55899a50df07 bp 0x7fd9cd9ef1c0 sp 0x7fd9cd9ef1b0 READ of size 8 at 0x604000272a90 thread T4 (ItemRetrievalMa) #0 0x55899a50df06 in QListData::begin() const /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:116 #1 0x55899a5b1087 in QList::begin() const /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:325 #2 0x55899a8aec12 in QDebug QtPrivate::printSequentialContainer >(QDebug, char const*, QList const&) /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:219 #3 0x55899a8aaebb in QDebug operator<< (QDebug, QList const&) /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:238 #4 0x55899a8b99e2 in Akonadi::Server::ItemRetrievalJob::start() /home/karry/data/cecko/KDE/akonadi/src/server/storage/itemretrievaljob.cpp:47 #5 0x55899a8a69fe in Akonadi::Server::ItemRetrievalManager::processRequest() /home/karry/data/cecko/KDE/akonadi/src/server/storage/itemretrievalmanager.cpp:164 #6 0x55899a8b779c in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (Akonadi::Server::ItemRetrievalManager::*)()>::call(void (Akonadi::Server::ItemRetrievalManager::*)(), Akonadi::Server::ItemRetrievalManager*, void**) /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152 #7 0x55899a8b5c84 in void QtPrivate::FunctionPointer::call, void>(void (Akonadi::Server::ItemRetrievalManager::*)(), Akonadi::Server::ItemRetrievalManager*, void**) /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185 #8 0x55899a8b385d in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:414 #9 0x7fd9d76e0d59 in QObject::event(QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2b2d59) #10 0x7fd9d76b4916 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x286916) #11 0x7fd9d76b75b7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2895b7) #12 0x7fd9d770cf66 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2def66) #13 0x7fd9d6068fbc in g_main_context_dispatch (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51fbc) #14 0x7fd9d606923f (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5223f) #15 0x7fd9d60692e2 in g_main_context_iteration (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x522e2) #16 0x7fd9d770c564 in QEventDispatcherGlib::processEvents(QFlags) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2de564) #17 0x7fd9d76b34da in QEventLoop::exec(QFlags) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2854da) #18 0x7fd9d74eb784 in QThread::exec() (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xbd784) #19 0x7fd9d74ec9d1 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xbe9d1) #20 0x7fd9d7013608 in start_thread /build/glibc-aevPTw/glibc-2.31/nptl/pthread_create.c:477 #21 0x7fd9d7162102 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122102) 0x604000272a90 is located 0 bytes inside of 40-byte region [0x604000272a90,0x604000272ab8) freed by thread T12 (0x611c1ec0-) here: #0 0x7fd9d8078025 in operator delete(void*, unsigned long) (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x111025) #1 0x55899a8a22ee in std::default_delete::operator()(Akonadi::Server::ItemRetrievalRequest*) const (/usr/bin/akonadiserver+0x4692ee) #2 0x55899a8a0ea2 in std::unique_ptr >::~unique_ptr() /usr/include/c++/9/bits/unique_ptr.h:292 #3 0x55899a8a09b5 in void std::_Destroy > >(std::unique_ptr >*) /usr/include/c++/9/bits/stl_construct.h:98 #4 0x55899a89e842 in void std::_Destroy_aux::__destroy >*>(std::unique_ptr >*, std::unique_ptr >*) /usr/include/c++/9/bits/stl_construct.h:108 #5 0x55899a89c583 in void std::_Destroy >*>(std::unique_ptr >*, std::unique_ptr >*) /usr/include/c++/9/bits/stl_construct.h:137 #6 0x55899a8991cc in void std::_Destroy >*, std::unique_ptr > >(std::unique_ptr >*, std::unique_ptr >*, std::allocator > >&) /usr/include/c++/9/bits/stl_construct.h:206 #7 0x55899a8966e3 in std::vector >, std::allocator > > >::~vector() /usr/include/c++/9/bits/stl_vector.h:677 #8 0x55899a890ca8 in Akonadi::Server::ItemRetriever::exec()
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 --- Comment #2 from andreas.sturmlech...@gmail.com --- (In reply to David Edmundson from comment #1) > Fixed recently > > b2ebd8f2ca332473f09e589d9e7ee0af0e1c7d98 in drkonqi Ah thanks. That's the one I asked about the possibility of picking it for Plasma/5.18 branch - it's not in there. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420272] Update to 4.2.9 hides lower parts of the screen (timeline, scrollbar, etc.)
https://bugs.kde.org/show_bug.cgi?id=420272 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #3 from Tymond --- By "docker", Boudewijn meant all those little windows on Krita UI: https://docs.krita.org/en/user_manual/getting_started/navigation.html#dockers - you can move them around to make more space. I noticed that a lot of default workspaces (default configurations of dockers) have three dockers on top of each other, which makes it hard to use on fullHD resolution display, and if you have lower resolution - or higher, but with HiDPI scaling that makes it lower than fullHD - it can make Krita's window too big to fit on the screen. If you remove or move around some of them, you'll be able to make it fit the screen. If you have more trouble, please head over to krita-artists.org and post a screenshot of your Krita window (and link to this page) so we can help you further. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420315] Leave actions do nothing (cannot log out or shutdown from plasma)
https://bugs.kde.org/show_bug.cgi?id=420315 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Do you install into a separate prefix? If so have you updated your DBus session correctly? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 420316] Opcion de notificaciones y perfil en youtube no abre
https://bugs.kde.org/show_bug.cgi?id=420316 --- Comment #1 from pikebuc...@gmail.com --- Al abrir la opcion de notificaciones (campana) y el boton de perfil el menu se queda cargando y no aparece nada -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 420316] New: Opcion de notificaciones y perfil en youtube no abre
https://bugs.kde.org/show_bug.cgi?id=420316 Bug ID: 420316 Summary: Opcion de notificaciones y perfil en youtube no abre Product: Falkon Version: 3.0.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: pikebuc...@gmail.com Target Milestone: --- Created attachment 127698 --> https://bugs.kde.org/attachment.cgi?id=127698=edit captura de pantalla del error Opcion de notificaciones y perfil en youtube no abre -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420317] New: Python wrapper creates a non-None Node for null parent (which causes an assert)
https://bugs.kde.org/show_bug.cgi?id=420317 Bug ID: 420317 Summary: Python wrapper creates a non-None Node for null parent (which causes an assert) Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- SUMMARY In cpp part of Krita, the parentNode() of the root layer will be null. In Python wrapper, it will return a non-None Node with "" as name() etc. STEPS TO REPRODUCE 1. Open an image with one layer. 2. Access the parentNode() of that layer. 3. Access the parentNode() of the parentNode() OBSERVED RESULT There will be an assert thrown: ASSERT: "d" in file /home/tymon/kritadev/krita/libs/global/kis_shared_ptr.h, line 180 EXPECTED RESULT No assert. The parentNode() at some point will return None, signalising the end of the hierarchy (instead of non-Nones all the way up :) ) SOFTWARE/OS VERSIONS Krita Version: 5.0.0-prealpha (git 54b7496) (last upstream: 3145ca0914) Languages: pl, pl_PL, pl Hidpi: true Qt Version (compiled): 5.11.1 Version (loaded): 5.11.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.7-050307-generic Pretty Productname: Linux Mint 19.3 Product Type: linuxmint Product Version: 19.3 Desktop: X-Cinnamon ADDITIONAL INFORMATION Relevant part of the backtrace: #0 0x73ef6ed7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x73ed8535 in __GI_abort () at abort.c:79 #2 0x746c08d7 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x746bfd59 in qt_assert_x(char const*, char const*, char const*, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fffcd3cd7f5 in KisSharedPtr::operator->() (this=) at /home/tymon/kritadev/krita/libs/global/kis_shared_ptr.h:180 #5 0x7fffcd3f2d29 in Node::createNode(KisSharedPtr, KisSharedPtr, QObject*) (image=..., node=..., parent=0x0) at /home/tymon/kritadev/krita/libs/libkis/Node.cpp:87 #6 0x7fffcd3f3556 in Node::parentNode() const (this=0x63c2d0a0) at /home/tymon/kritadev/krita/libs/global/kis_shared_ptr.h:179 #7 0x7fffcceaa003 in meth_Node_parentNode(PyObject*, PyObject*) (sipSelf=, sipArgs=) at /home/tymon/kritadev/build/plugins/extensions/pykrita/sip/./krita/sipkritapart0.cpp:19504 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401861] Menu search doesn't return any results if cursor happens to be positioned below the tab bar
https://bugs.kde.org/show_bug.cgi?id=401861 Nate Graham changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|k...@davidedmundson.co.uk|tr...@yandex.com --- Comment #21 from Nate Graham --- Patch: https://phabricator.kde.org/D28985 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420272] Update to 4.2.9 hides lower parts of the screen (timeline, scrollbar, etc.)
https://bugs.kde.org/show_bug.cgi?id=420272 --- Comment #2 from lonjas...@gmail.com --- Hi Boudewijn, as described above, I am using ubuntu, installed krita via the packet manager. I am not dealing with docker images. The GUI does not scale when clicking on the maximize button, the lower areas of the main window is not shown on the screen and no scrollbar enables me to scroll down. So the program is simply not usable anymore. What could I do? Any help is appreciated. Greetings Am Sa., 18. Apr. 2020 um 22:36 Uhr schrieb Boudewijn Rempt < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=420272 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > Resolution|--- |NOT A BUG > Status|REPORTED|RESOLVED > > --- Comment #1 from Boudewijn Rempt --- > I'm sorry, but this is not a bug, of course. You need to rearrange Krita's > docker layout to fit the dimensions of your screen, change the system font > size > or get a monitor that is suitable for animation work. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #103 from jack --- Seems like there is a lot more going on than just the rearrangement bug that others and me are describing. Have you tried deleteing your icon-cache.kcache? Some reddit post said it helped but for me it didn't: https://www.reddit.com/r/kde/comments/fmd18x/at_reboot_my_kde_desktop_icons_are_fully_messed_up/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #102 from Nick Stefanov --- Yes, I use only one Screen/Activity and FolderView Desktop Layout. I use this workaround: https://bugs.kde.org/show_bug.cgi?id=389705#c0 And it helps a lot but not always. Sometimes my additionaly created files are moving just on monitor tiurn off/turn on and the doesn't stay where I placed them. Sometimes, when a resolution change occurs for some reason, some of the icons get double right border and it's a harbinger of almost sure icon movement in the future. https://i.imgur.com/wOi9zrd.png When I try to move the doubled icon it get blured, zoomed and the picture in it was misplacedb but the two last are not obligate: https://i.imgur.com/9KoTi4c.png It's very strange... https://i.imgur.com/vEbw5Cq.png https://youtu.be/Kon0Mnr1yJI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415798] [Wayland] task switcher is black after changing
https://bugs.kde.org/show_bug.cgi?id=415798 --- Comment #7 from Stefan K. --- Created attachment 127696 --> https://bugs.kde.org/attachment.cgi?id=127696=edit default left-side task switcher -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415798] [Wayland] task switcher is black after changing
https://bugs.kde.org/show_bug.cgi?id=415798 --- Comment #6 from Stefan K. --- It also happens when I change the font settings. In my case I switched the title bar font, clicked on "Apply" and after a short workspace flickering the task switcher is broken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 jack changed: What|Removed |Added CC||j4ck...@pm.me --- Comment #101 from jack --- hey, expirienced this Bug too. Do you use only one Screen/Activity like me? For me it doesn't happen all the time. sometimes the items stay after reboot (or logout/login) and sometimes they dont.- Just to clarify. you are using FolderView Desktop Layout? I tried this now (based on Comment 54, 55 by Valdo) and i think it helped: time will tell if the icons get rearranged again: open dolphin and go to your ./config folder to locate the file "plasma-org.kde.plasma.desktop-appletsrc" Then open a terminal and run kquitapp5 plasmashell your desktop should get black but the filemanger(dolphin) stays open. Then open the file mentioned above and scroll down till u find the Section [ScreenMapping] itemsOnDisabledScreens= screenMapping= for me there were lots of old names/files in those 2 lines (after the =) that got long deleted and were not present anywhere anymore. I dont know what these 2 lines are there for and what they do. its always good to make a backup before edits. So i deleted everything after the "=" signs so it looks like above and then run: kstart5 plasmashell i post this so others may try this at their own risk as i havent seen the icons rearranged after this but it didnt happen all the time anyways so i am not sure if it helped.. Maybe some dev can tell us what these lines are there for and why old long gone filenames end up in those lines... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420315] New: Leave actions do nothing (cannot log out or shutdown from plasma)
https://bugs.kde.org/show_bug.cgi?id=420315 Bug ID: 420315 Summary: Leave actions do nothing (cannot log out or shutdown from plasma) Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: frther...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When selecting a leave action from the plasma Application Launcher, nothing happens. The only way I've found to logout is via loginctl terminate-user. "Sleep" and "Lock" seem to work STEPS TO REPRODUCE 1. Application Launcher > Leave 2. Select Log Out, Shut Down, or Restart OBSERVED RESULT Nothing happens. EXPECTED RESULT Logout or shutdown procedure should start. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Linux 5.4.33-1-MANJARO #1 SMP PREEMPT Fri Apr 17 18:16:26 UTC 2020 x86_64 GNU/Linux (available in About System) KDE Plasma Version: Noticed while building plasma-workspace from master (see below for bisected commit) KDE Frameworks Version: I believe it was also built from master Qt Version: 5.14.2-1 ADDITIONAL INFORMATION My distro had plasma-workspace 5.18.4.1, which does not have the issue. I checked out the commit tagged "v5.18.4.1" in plasma-workspace and built it, no issue also. I ran git bisect between that commit and master, and the result is that commit 3c34dfa in plasma-workspace (https://phabricator.kde.org/D27629) seems to be the first commit with the issue. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420241] Parts of Icons that use the selection color disappear when the icon's list item (etc.) is selected
https://bugs.kde.org/show_bug.cgi?id=420241 --- Comment #4 from David Hurka --- (In reply to Nate Graham from comment #3) > This has the potential > to fix other instances of the same issue in other places too. Honestly, I think this is just a cosmetic issue, which isn’t relevant everywhere else. To mitigate that we could use a slightly darker shade for SelectionFocus. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420314] New: Freeze screen
https://bugs.kde.org/show_bug.cgi?id=420314 Bug ID: 420314 Summary: Freeze screen Product: kwin Version: 5.12.9 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: acracia.sky...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.9) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.3.0-46-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: I justo surf in firefox and see videos on youtube, just that. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa79c65fcc0 (LWP 1035))] Thread 15 (Thread 0x7fa6b30b3700 (LWP 4561)): #0 0x7fa79bfa1cf6 in __GI_ppoll (fds=0x7fa76c012828, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fa79937c561 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa79937dc7e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa79932590a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa79914423a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa793a4d6f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fa79914917d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa794f846db in start_thread (arg=0x7fa6b30b3700) at pthread_create.c:463 #8 0x7fa79bfae88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fa6b9fa4700 (LWP 3600)): #0 0x7fa794f8a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a33f9e5878) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fa794f8a9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55a33f9e5828, cond=0x55a33f9e5850) at pthread_cond_wait.c:502 #2 0x7fa794f8a9f3 in __pthread_cond_wait (cond=0x55a33f9e5850, mutex=0x55a33f9e5828) at pthread_cond_wait.c:655 #3 0x7fa7693a4a0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fa7693a4607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fa794f846db in start_thread (arg=0x7fa6b9fa4700) at pthread_create.c:463 #6 0x7fa79bfae88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fa76bdd4700 (LWP 3570)): #0 0x7fa79bfa1cf6 in __GI_ppoll (fds=0x7fa764060698, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fa79937c561 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa79937dc7e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa79932590a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa79914423a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa793a4d6f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fa79914917d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa794f846db in start_thread (arg=0x7fa76bdd4700) at pthread_create.c:463 #8 0x7fa79bfae88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fa75d3e1700 (LWP 3468)): #0 0x7fa794f8a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a33f293b28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fa794f8a9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55a33f293ad8, cond=0x55a33f293b00) at pthread_cond_wait.c:502 #2 0x7fa794f8a9f3 in __pthread_cond_wait (cond=0x55a33f293b00, mutex=0x55a33f293ad8) at pthread_cond_wait.c:655 #3 0x7fa7693a4a0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fa7693a4607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fa794f846db in start_thread (arg=0x7fa75d3e1700) at pthread_create.c:463 #6 0x7fa79bfae88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fa6b915c700 (LWP 3467)): #0 0x7fa79bfa1cf6 in __GI_ppoll (fds=0x7fa6ac015468, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fa79937c561 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa79937dc7e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa79932590a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa79914423a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5
[systemsettings] [Bug 413954] Needless precision in night colour coordinates
https://bugs.kde.org/show_bug.cgi?id=413954 Nate Graham changed: What|Removed |Added Version Fixed In||5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420313] New: Night color does not respect my time zone
https://bugs.kde.org/show_bug.cgi?id=420313 Bug ID: 420313 Summary: Night color does not respect my time zone Product: systemsettings Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: j...@van-spaandonk.nl CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set the time zone to Amsterdam in system settings - date & time 2. open night color module in system settings 3. OBSERVED RESULT Observe longitude and lattitude that do not match with Amsterdam) Lattitude: 25,8295, Longitude: -80,2927 EXPECTED RESULT I would expect to see the lattitude and longitude of Amsterdam, About 5 and 52 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION This worked before but stopped working a few weeks ago. Sorry that I cannot be more specific. At the moment I use night color in manual mode. Another bug: Night color shows latitude 0 Longitude 0 before quickly updating it to the above reporting results. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420273] DVD Wizard Crashes When "add chapter" button is pressed
https://bugs.kde.org/show_bug.cgi?id=420273 richard.sutherland...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from richard.sutherland...@gmail.com --- Issue has been resolved as of nightly build 367(20.7.70). Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420241] Parts of Icons that use the selection color disappear when the icon's list item (etc.) is selected
https://bugs.kde.org/show_bug.cgi?id=420241 --- Comment #3 from Nate Graham --- (In reply to David Hurka from comment #2) > Currently the class is ColorScheme-Highlight. We talked about changing it to > ColorScheme-ButtonFocus, but that didn’t work everywhere (until now). I > think it wouldn’t change the situation anyway, because it’s the same color. Yeah. > What about using just Focus? That could change during selection, if I > understand it correctly. Currently, in the Breeze color scheme, it is also > just the same color, so we need to change the Breeze color scheme there. That's a good idea. If it changes when selected, all we need to do is make sure the color gets changes to a contrasting color. This has the potential to fix other instances of the same issue in other places too. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no thumbnails and previews of heic files
https://bugs.kde.org/show_bug.cgi?id=420195 --- Comment #10 from Maik Qualmann --- Hmm, interesting. I had exchanged all QFile::encodeName() calls in the metadataengine directory to FILENAME.toUtf8().constData(). However, Exiv2 was unable to read metadata from images in these special directories. I test it again the days. Maik -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420241] Parts of Icons that use the selection color disappear when the icon's list item (etc.) is selected
https://bugs.kde.org/show_bug.cgi?id=420241 --- Comment #2 from David Hurka --- Currently the class is ColorScheme-Highlight. We talked about changing it to ColorScheme-ButtonFocus, but that didn’t work everywhere (until now). I think it wouldn’t change the situation anyway, because it’s the same color. What about using just Focus? That could change during selection, if I understand it correctly. Currently, in the Breeze color scheme, it is also just the same color, so we need to change the Breeze color scheme there. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420258] Several entries of the context menus inside "Network" under "Remote" section of places panel are useless and cause error messages
https://bugs.kde.org/show_bug.cgi?id=420258 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420241] Parts of Icons that use the selection color disappear when the icon's list item (etc.) is selected
https://bugs.kde.org/show_bug.cgi?id=420241 Nate Graham changed: What|Removed |Added CC||kain...@gmail.com Product|plasmashell |Breeze Keywords||usability Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Version|master |unspecified Component|general |Icons Target Milestone|1.0 |--- Summary|Desktop switcher OSD|Parts of Icons that use the |selection has same color as |selection color disappear |part of the pictograms |when the icon's list item ||(etc.) is selected Assignee|k...@davidedmundson.co.uk|visual-des...@kde.org --- Comment #1 from Nate Graham --- Urgh. This happens for every element of every icon that incorporates the selection color. Seems like a fundamental error to use this color in an icon. Either that, or the selection color should be made less intense in the center, as with the Plasma highlight effect or Noah's new selection patch. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no thumbnails and previews of heic files
https://bugs.kde.org/show_bug.cgi?id=420195 --- Comment #9 from caulier.gil...@gmail.com --- Maik, Exiv2 has a compilation for windows to handle UTF16 path strings. It' normally enabled now since few weeks has this option compile now with MinGW. https://invent.kde.org/kde/digikam/-/blob/master/project/bundles/3rdparty/ext_exiv2/CMakeLists.txt#L34 Gilles -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420312] New: Dolphin services not being remove after uninstall
https://bugs.kde.org/show_bug.cgi?id=420312 Bug ID: 420312 Summary: Dolphin services not being remove after uninstall Product: dolphin Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: raul.aventuramen...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 127695 --> https://bugs.kde.org/attachment.cgi?id=127695=edit options of an uninstalled services are still there SUMMARY When I uninstall a service on Dolphin It keeps showing it's services options under the "Services" tab STEPS TO REPRODUCE 1. Install a Service 2. Uninstall it 3. Watch the Service tab, their options are still there OBSERVED RESULT The options from an uninstalled service (like "mount ISO") are not being remove from the service list. EXPECTED RESULT "select which services should be shown in the context menu" should only show the dafault options and the installed ones. Not the options from an uninstalled service. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 408690] Area containing Start Page text not properly displayed on KHelpCenter
https://bugs.kde.org/show_bug.cgi?id=408690 --- Comment #7 from David C. Bryant --- On Sunday, April 19, 2020 11:34:20 AM CDT John Hayes wrote: > https://bugs.kde.org/show_bug.cgi?id=408690 > > John Hayes changed: > >What|Removed |Added > > CC||jdhayes.li...@gmail.com > > --- Comment #5 from John Hayes --- > When I started Help from the menu the graphic was distorted. It looked like > a newline was inserted between the words Start and Page with the horizontal > line covering up most of the word Page This bug must only be showing up with certain packages. I just checked it in OpenSUSE (Leap 15.1), Debian 10, and KDE Neon 15.8.2 (base package is Ubuntu 18.04). It worked fine in all three environments -- there was no garbled image. D. Bryant Canyon Lake, Texas -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419801] XMP-digiKam:TagsList not read from video files
https://bugs.kde.org/show_bug.cgi?id=419801 --- Comment #4 from Dries Hoet --- I added the tags with exiftool, with this command: exiftool '-XMP-digiKam:TagsList=Subjects/Animals/Fish, Categories/Underwater, Places/Asia/Philippines' '-XMP-exif:DateTimeOriginal=2020:01:19 17:42:19+08:00' '-XMP-tiff:Artist=xyz' '-XMP-tiff:Copyright=Copyright © 2020 xyz, all rights reserved.' file_example_MP4_480_1_5MG.mp4 I attached the example to the ticket. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no thumbnails and previews of heic files
https://bugs.kde.org/show_bug.cgi?id=420195 --- Comment #8 from Maik Qualmann --- Thank you, with the directory structure the problem can be reproduced well under Windows. The problem is clear, but can hardly be solved. JPG files are only loaded by the QImage loader, Exiv2 cannot read metadata. The QImage loader uses the Windows API directly and uses the correct UTF16 file name. We use QFile::encodeName() this function can convert all characters within the current code page, but not if characters are outside. We would have to use a wrapper to replace fopen() that under Windows only uses code page with _wfopen(). However, a test shows that even Exiv2 does not handle it correctly internally when we pass UTF8 file names. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419801] XMP-digiKam:TagsList not read from video files
https://bugs.kde.org/show_bug.cgi?id=419801 --- Comment #3 from Dries Hoet --- Created attachment 127693 --> https://bugs.kde.org/attachment.cgi?id=127693=edit Example video with TagsList -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410800] Device in Bookmark will show docker mount point when docker container opened
https://bugs.kde.org/show_bug.cgi?id=410800 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Nate Graham --- Agreed. Please report this to the Docker folks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416087] Optionally find hidden files using Dolphin's standard search
https://bugs.kde.org/show_bug.cgi?id=416087 Peter changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #7 from Peter --- I believe that using baloo is a very serious logical mistake. Because: - Most users do not use search 24/7. - Baloo at the same time kills my SSD and takes a lot of resources. - Dolphin gives an irrelevant search due to Baloo. - Dolphin cannot just find files that are not in the index. This tricks the user. No as a result of the search? So this file does not exist! Me and 99% of users are ready to wait 5 seconds to find the file. They have been asking for this for almost a decade. The days of Windows 98 (file indexing) and super-slow hard drives are over. Need to give up Baloo. And ready-made solutions for the search are already there. For example KFind. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"
https://bugs.kde.org/show_bug.cgi?id=399245 Niko sagiadinos changed: What|Removed |Added CC||k...@saghiadinos.de --- Comment #15 from Niko sagiadinos --- +1 This bar is annoying and ugly. The user should be allowed to decide whether to display an element and not be patronized like a small child. ;-) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416087] Optionally find hidden files using Dolphin's standard search
https://bugs.kde.org/show_bug.cgi?id=416087 --- Comment #6 from Patrick Silva --- Created attachment 127692 --> https://bugs.kde.org/attachment.cgi?id=127692=edit screen recording on Neon unstable On Neon unstable baloo indexes hidden files but Dolphin can not find them. I recorded a video showing the issue. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420291] Useless m_delayShow config variable
https://bugs.kde.org/show_bug.cgi?id=420291 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- >Code one the following like should use m_delayShow boolean variable instead of >m_delayShowTime. but we'd still want to check for the time being 0. Is showDelay explosed in the config UI anywhere? You've done the work, do you want to commit your first patch? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 420311] New: The prepare/teardown signal is emitted for each query
https://bugs.kde.org/show_bug.cgi?id=420311
Bug ID: 420311
Summary: The prepare/teardown signal is emitted for each query
Product: frameworks-krunner
Version: 5.69.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@privat.broulik.de
Reporter: alex1701c@gmx.net
Target Milestone: ---
SUMMARY
The prepare/teardown signal is emitted for each query and not for each match
session.
STEPS TO REPRODUCE
1. Connect to the signal in a runner:
connect(this, ::prepare, [=]() {
qWarning() << "prepare";
});
2. Install plugin, restart krunner
3. Type some letters
OBSERVED RESULT
The warning is displayed for each letter typed.
EXPECTED RESULT
The warning gets displayed when the first letter is typed.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon beta
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.1
ADDITIONAL INFORMATION
It works as expected with krunner 5.62.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-browser-integration] [Bug 420294] Chrome drops Qt scaling environment variables
https://bugs.kde.org/show_bug.cgi?id=420294 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |LATER Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- PBI cannot influence that. If we make kde-open5 use ApplicationLaunchJob and we merge the patches that make ApplicationLaunchJob use the systemd launch env, that will resolve the issue -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 408690] Area containing Start Page text not properly displayed on KHelpCenter
https://bugs.kde.org/show_bug.cgi?id=408690 Yuri Chornoivan changed: What|Removed |Added CC||yurc...@ukr.net --- Comment #6 from Yuri Chornoivan --- I wasted some time on this with no results. Somehow KHC (or rather its HTML engine) fails to calculate the size of the "title" for "Start Page" for the first time. But it is enough to go to the next page to fix rendering. It might happen that this can be fixed with a one-liner in navigator.cpp but I do not know what this line is. :) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 420297] building llvm test case broken
https://bugs.kde.org/show_bug.cgi?id=420297 Ralf Habacker changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||umbrello/commit/9ab35ae8f44 ||08b16d437f3d6e2156c4a87afb7 ||8e Version Fixed In||2.31.0 (KDE releases ||20.04.0) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 420297] building llvm test case broken
https://bugs.kde.org/show_bug.cgi?id=420297 Ralf Habacker changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 416466] GoPro footage thumbnails are just noise in Dolphin
https://bugs.kde.org/show_bug.cgi?id=416466 --- Comment #5 from Isaac A. --- Sorry, just now checked up on this issue. I'll upload a file shortly -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Fixed recently b2ebd8f2ca332473f09e589d9e7ee0af0e1c7d98 in drkonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420303] Crash while parsing python Library
https://bugs.kde.org/show_bug.cgi?id=420303 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #3 from Francis Herne --- Unfortunately Debian (at least in stable) doesn't package the latest version of KDevelop, which is 5.5.0. It doesn't even package the latest bugfix release in the 5.3.x series, which was 5.3.3. A similar bug was fixed in 5.3.2: https://bugs.kde.org/show_bug.cgi?id=403045 Please test the 5.5.0 AppImage available at https://www.kdevelop.org/download , which will run on Debian without affecting your system installation. (or use a distribution that actually updates the software they distribute). Thank you for taking the trouble to report this. -Francis H -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 388562] kleopatra is _NOT_ the active window when started from system-tray 'Status & Notifications'
https://bugs.kde.org/show_bug.cgi?id=388562 Andrey Legayev changed: What|Removed |Added CC||legaev.and...@gmail.com --- Comment #1 from Andrey Legayev --- As I see v3.1.11 works as expected: - it's active window when started via command or menu - on logout/login hide/show status is restored according to saved KDE session -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 415206] By default cannot be used with Elisa for music files outside of $HOME
https://bugs.kde.org/show_bug.cgi?id=415206 --- Comment #3 from Stefan Brüns --- (In reply to Martin Steigerwald from comment #2) > I just tested it more closely on adding some other folders outside of $HOME > to Baloo indexing, it cannot be done with balooctl config: > > % LANG=en balooctl config set > The following configuration options may be modified: > > hidden Controls if Baloo indexes hidden files and folders > contentIndexing Controls if Baloo indexes file content > > balooctl does not give more options than the KCM. > > So the user really has to edit ~/.config/baloofilerc in order to use Elisa > with Baloo file indexer on a folder outside of $HOME. $> balooctl config add The following configuration options may be modified: includeFolders The list of folders which Baloo indexes excludeFolders The list of folders which Baloo will never index excludeFilters The list of filters which are used to exclude files excludeMimetypes The list of mimetypes which are used to exclude files -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408229] When adding Clips Crashes, drag and drop clips are added OK
https://bugs.kde.org/show_bug.cgi?id=408229 --- Comment #3 from emohr --- Please delete kdenliverc and try again. See here https://userbase.kde.org/Kdenlive/Manual/Windows_Issues#Cannot_open_projects_made_with_previous_version.2C_timeline_snaps_back.2C_cannot_import_clip -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 420143] Kid3 - Does not tag DSF files larger than 2GB
https://bugs.kde.org/show_bug.cgi?id=420143 --- Comment #3 from Urs Fleisch --- Git commit e11dd41f4ae6891230857bda4539a5238b0f95a6 by Urs Fleisch. Committed on 19/04/2020 at 16:42. Pushed by ufleisch into branch 'master'. Patch TagLib for Windows 64-bit to support large files M +1800 -0buildlibs.sh M +20 -12 src/plugins/taglibmetadata/taglibfile.cpp https://invent.kde.org/kde/kid3/commit/e11dd41f4ae6891230857bda4539a5238b0f95a6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383717] Move tool won't update the image in real-time
https://bugs.kde.org/show_bug.cgi?id=383717 tyo_mansh...@yahoo.com changed: What|Removed |Added CC||tyo_mansh...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 420143] Kid3 - Does not tag DSF files larger than 2GB
https://bugs.kde.org/show_bug.cgi?id=420143 --- Comment #2 from Urs Fleisch --- I have investigated the issue further. It only happens on Windows because on Linux and macOS, long values are 64-bit on 64-bit architectures whereas on Windows long is always 32-bit. To fix this, all variables which are used to index data from a large file have to be replaced by a 64-bit type. I have patched the TagLib which is used to build the Windows 64-bit edition. I have tested it with large MP4, MP3, FLAC and Opus files, but not with a large DSF file, simply because I do not have a DSF file larger than 2GB and I do not know how to easily create such a file (for the other formats it can be done using ffmpeg). The DSF format seems to be quite simple, so I could have created such a file containing large invalid data, but probably it is easier if you test it with your files. So please get the win32-x64.zip file from https://sourceforge.net/projects/kid3/files/kid3/development/ and tell me if it works. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420091] Kdenlive crashes on loading the project
https://bugs.kde.org/show_bug.cgi?id=420091 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||Brainstorm+ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420165] Speed effect adds additional frame at the end of rendered file
https://bugs.kde.org/show_bug.cgi?id=420165 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Status|REPORTED|CONFIRMED Flags||Backport+ Ever confirmed|0 |1 --- Comment #1 from emohr --- Thank you for reporting. Confirmed. Speed change to 142.43% -> render the clip (MP4). Import the rendered clip -> 1 frame longer then the clip in the timeline. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420273] DVD Wizard Crashes When "add chapter" button is pressed
https://bugs.kde.org/show_bug.cgi?id=420273 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #1 from emohr --- I think we fixed some DVD wizard issues lately. Please try with nightly Windows_Nightly_Build https://binary-factory.kde.org/job/Kdenlive_Nightly_mingw64/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420277] Opening and saving files does not work
https://bugs.kde.org/show_bug.cgi?id=420277 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Flags||timeline_corruption+ Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- Please try with the current Kdenlive AppImage version 19.12.3 to see if there are any packaging issues https://files.kde.org/kdenlive/release/ If the problem/issue doesn't occur when using the AppImage, then it's your configuration or packaging. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 411926] The wifi not save the credentials after resume from startup, sleep and hibernate
https://bugs.kde.org/show_bug.cgi?id=411926 --- Comment #3 from Varaskkar --- Done! https://forum.manjaro.org/t/manjaro-kde-wifi-doesnt-save-the-credentials-after-startup-sleep-and-hibernate/137059 Hopefully could be solved. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 162653] .pcx-Images are not displayed in view mode, until a action (e.g. rotate) is performed
https://bugs.kde.org/show_bug.cgi?id=162653 tyo_mansh...@yahoo.com changed: What|Removed |Added CC||tyo_mansh...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410544] Investment in foreign currency
https://bugs.kde.org/show_bug.cgi?id=410544 Jack changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #14 from Jack --- Changing status back to REPORTED, as it looks to be still in progress. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 418444] Add SVG/highres icons to the source tree
https://bugs.kde.org/show_bug.cgi?id=418444 Martin Koller changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kol ||ourpaint/9582b7a1e68a46bc67 ||983a55abfc7c306117c3db --- Comment #3 from Martin Koller --- Git commit 9582b7a1e68a46bc67983a55abfc7c306117c3db by Martin Koller. Committed on 19/04/2020 at 16:49. Pushed by mkoller into branch 'master'. add 128x128 application png image A +---pics/app/128-apps-kolourpaint.png M +1-0pics/app/CMakeLists.txt https://commits.kde.org/kolourpaint/9582b7a1e68a46bc67983a55abfc7c306117c3db -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 411926] The wifi not save the credentials after resume from startup, sleep and hibernate
https://bugs.kde.org/show_bug.cgi?id=411926 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Nate Graham --- Yeah, we've gotten many reports about this from Manjaro users. It's a bug in how Manjaro has configured pam_kwallet (or not). Please report it to them. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 420050] Follow the default applications to open files/urls
https://bugs.kde.org/show_bug.cgi?id=420050 Jan Grulich changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED CC||jgrul...@redhat.com --- Comment #2 from Jan Grulich --- I opened an upstream bug https://github.com/flatpak/xdg-desktop-portal/issues/472. If anyone wants to step in, feel free to. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] New: drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 Bug ID: 420310 Summary: drkonqi itself crashed while trying to submit another crash report Product: drkonqi Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andreas.sturmlech...@gmail.com Target Milestone: --- Created attachment 127691 --> https://bugs.kde.org/attachment.cgi?id=127691=edit drkonqi-20200419-182721.kcrash.txt And unfortunately it does not want to report its own crash (button is greyed out) so I'm doing it manually here. The crash happened after login. Operating System: Gentoo KDE Plasma Version: 5.18.4++ (Plasma/5.18 branch @b2008aac7 built yesterday) KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 Kernel Version: 5.6.5-gentoo OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410800] Device in Bookmark will show docker mount point when docker container opened
https://bugs.kde.org/show_bug.cgi?id=410800 --- Comment #3 from Stefan Brüns --- There is a well-known, cross-desktop mount option to hide file systems, x-gvfs-hidden. Docker should set it if the FS is not meant as a user-accessible storage. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 408690] Area containing Start Page text not properly displayed on KHelpCenter
https://bugs.kde.org/show_bug.cgi?id=408690 John Hayes changed: What|Removed |Added CC||jdhayes.li...@gmail.com --- Comment #5 from John Hayes --- When I started Help from the menu the graphic was distorted. It looked like a newline was inserted between the words Start and Page with the horizontal line covering up most of the word Page -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 411777] import of vcs fails, still says success
https://bugs.kde.org/show_bug.cgi?id=411777 --- Comment #4 from Martin Koller --- I tested now again with a self-compiled KDE-PIM (20.04) on Operating System: openSUSE Tumbleweed 20200415 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 5.6.2-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Now korganizer and korgac crash when I import it and merge it into an existing calendar (stored on a nextcloud server). backtrace of korganizer below. When I import it as a new calendar, then it is still not shown in korganizer but at least no crash. Checking with akonadiconsole and looking on the new calendar shows 0 items. Thread 1 (Thread 0x7fd1985ed880 (LWP 15319)): [KCrash Handler] #6 0x7fd19b572ea1 in raise () from /lib64/libc.so.6 #7 0x7fd19b55c53d in abort () from /lib64/libc.so.6 #8 0x7fd19bad1aef in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1894 #9 QMessageLogger::fatal (this=this@entry=0x7fff2e279750, msg=msg@entry=0x7fd19bdbeea0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:893 #10 0x7fd19bad0f2f in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #11 0x7fd19e33ed39 in Akonadi::ETMCalendarPrivate::updateItem (this=0x2430480, item=...) at /home/KDE5/source/kde/pim/akonadi-calendar/src/etmcalendar.cpp:408 #12 0x7fd19e33d534 in Akonadi::ETMCalendarPrivate::onDataChangedInFilteredModel (this=0x2430480, topLeft=..., bottomRight=...) at /home/KDE5/source/kde/pim/akonadi-calendar/src/etmcalendar.cpp:394 #13 0x7fd19e34b947 in QtPrivate::FunctorCall, QtPrivate::List, void, void (Akonadi::ETMCalendarPrivate::*)(QModelIndex const&, QModelIndex const&)>::call (f=(void (Akonadi::ETMCalendarPrivate::*)(Akonadi::ETMCalendarPrivate * const, const QModelIndex &, const QModelIndex &)) 0x7fd19e33d420 , o=0x2430480, arg=0x7fff2e279bf0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #14 0x7fd19e34b8a8 in QtPrivate::FunctionPointer::call, void> (f=(void (Akonadi::ETMCalendarPrivate::*)(Akonadi::ETMCalendarPrivate * const, const QModelIndex &, const QModelIndex &)) 0x7fd19e33d420 , o=0x2430480, arg=0x7fff2e279bf0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #15 0x7fd19e34b7d5 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x246d9b0, r=0x2430480, a=0x7fff2e279bf0, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:414 #16 0x7fd19bd149fe in QtPrivate::QSlotObjectBase::call (a=0x7fff2e279bf0, r=0x2430480, this=0x246d9b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #17 doActivate (sender=0x247a4b0, signal_index=3, argv=0x7fff2e279bf0) at kernel/qobject.cpp:3870 #18 0x7fd19bd0f1bf in QMetaObject::activate (sender=sender@entry=0x247a4b0, m=m@entry=0x7fd19bfa1060 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff2e279bf0) at kernel/qobject.cpp:3930 #19 0x7fd19bc83d35 in QAbstractItemModel::dataChanged (this=this@entry=0x247a4b0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #20 0x7fd19bcb7b2d in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x247f6c0, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1500 #21 0x7fd19bcb8c2a in QSortFilterProxyModel::qt_static_metacall (_o=, _c=, _id=, _a=) at itemmodels/qsortfilterproxymodel.h:199 #22 0x7fd19bd14a30 in doActivate (sender=0x24430e0, signal_index=3, argv=0x7fff2e279ee0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:391 #23 0x7fd19bd0f1bf in QMetaObject::activate (sender=sender@entry=0x24430e0, m=m@entry=0x7fd19bfa1060 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff2e279ee0) at kernel/qobject.cpp:3930 #24 0x7fd19bc83d35 in QAbstractItemModel::dataChanged (this=this@entry=0x24430e0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #25 0x7fd19bcb7b2d in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x247e6d0, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1500 #26 0x7fd19bcb8c2a in QSortFilterProxyModel::qt_static_metacall (_o=, _c=, _id=, _a=) at itemmodels/qsortfilterproxymodel.h:199 #27 0x7fd19bd14a30 in doActivate (sender=0x23fef30, signal_index=3, argv=0x7fff2e27a1d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:391 #28 0x7fd19bd0f1bf in QMetaObject::activate (sender=sender@entry=0x23fef30, m=m@entry=0x7fd19bfa1060 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff2e27a1d0) at kernel/qobject.cpp:3930 #29 0x7fd19bc83d35 in QAbstractItemModel::dataChanged (this=this@entry=0x23fef30, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #30 0x7fd19bcb7b2d in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x247d3b0, source_top_left=..., source_bottom_right=..., roles=...) at
[dolphin] [Bug 420188] SMB1 says connection to host is broken
https://bugs.kde.org/show_bug.cgi?id=420188 --- Comment #4 from Harald Sitter --- (In reply to Nate Graham from comment #2) > (In reply to Harald Sitter from comment #1) > > kf5.kio.core: "Can't load /etc/samba/smb.conf - run testparm to debug it\n" > > > > It seems you or your distro broke your smb config which would result in > > defaults getting used and the samba defaults are to not speak the deprecated > > SMB1 protocol hence you cannot talk to the router with only SMB1 support. > Maybe we should have Dolphin show a user-comprehensible error message when > this is the case? Ideally yes, but, we don't know that it's an SMB1 problem. When SMB1 is disabled libsmbc isn't allowed to talk SMB1 with the remote. A remote that only speaks SMB1 isn't really distinguishable from a remote that has a HTTP server run on that port for example, they both speak gibberish from libsmbc's POV. Windows 10 has fundamentally the same problem. The best we could do is make the error more descriptive. Patches welcome ;) I expect we'll also need an entire wiki page or docs page somewhere explaining the entire mess though. Telling people that this may be because their device only supports SMB1 isn't that useful without explaining what can be done about it. (In reply to Jack from comment #3) > I have never modified or touched that file on my PC (it never existed) or > even enabled Samba to talk with SMB1, it always worked out of the box. You'll want to talk to your distribution. We haven't changed anything there, and in fact it's always been libsmbclient's defaults that decided whether or not SMB1 is supported (it has been off by default for years now though). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401861] Menu search doesn't return any results if cursor happens to be positioned below the tab bar
https://bugs.kde.org/show_bug.cgi?id=401861 tr...@yandex.com changed: What|Removed |Added CC||cryptonot...@protonmail.com --- Comment #20 from tr...@yandex.com --- *** Bug 420282 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420282] Visual glitch causes Application Launcher to seemingly not find apps
https://bugs.kde.org/show_bug.cgi?id=420282 tr...@yandex.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||tr...@yandex.com --- Comment #4 from tr...@yandex.com --- *** This bug has been marked as a duplicate of bug 401861 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 419646] can not submit bug report
https://bugs.kde.org/show_bug.cgi?id=419646 Harald Sitter changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |ASSIGNED --- Comment #9 from Harald Sitter --- Huh. I am thinking what is happening is that you have a cookie and KIO is trying to be smart and inject the cookie into the request so the API goes "WTF" seeing as it's not cookie based. Will have to try to reproduce on Monday. Thanks for the logs! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420270] Monochrome icons are barely visible. Sometimes they are correctly rendered on mouseover.
https://bugs.kde.org/show_bug.cgi?id=420270 Patrick Silva changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #12 from Patrick Silva --- (In reply to David Redondo from comment #11) > Hi, does this happen with this commit > https://phabricator.kde.org/R31:66d0b0b4e3e1adc389dbd4ce1976d81860d1880d ? > This fixed a similiar bug in the "you have unsaved changes dialog" in > kolourpaint and kwrite? the patch from your link fixes the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420303] Crash while parsing python Library
https://bugs.kde.org/show_bug.cgi?id=420303 jkoehle...@protonmail.com changed: What|Removed |Added CC||jkoehle...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411349] Dolphin 100% CPU core usage
https://bugs.kde.org/show_bug.cgi?id=411349
--- Comment #8 from Méven Car ---
> I also have this bug in Fedora 31.
> Dolphin load 100% one core not immediately after startup and on any open
> folder without > pictures.
> But on other my system I don't see this.
We need a backtrace or a file to diagnose, we cannot even confirm your bug is
related to this one.
Regarding this bug and code it points to in previewjob.cpp:
> QMimeDatabase db;
>// check mime type inheritance, resolve aliases
>const QMimeType mimeInfo = db.mimeTypeForName(mimeType);
>if (mimeInfo.isValid()) {
According to the backtrace in first comment, a file triggers a crash in
QMimeDatabase.
So this could be a Qt bug, we would need to find the file triggering the bug
ideally to move forward.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 420309] New: Font blurry in konsole's tabbar on KWayland
https://bugs.kde.org/show_bug.cgi?id=420309 Bug ID: 420309 Summary: Font blurry in konsole's tabbar on KWayland Product: konsole Version: 19.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: hanyd2...@163.com Target Milestone: --- Created attachment 127689 --> https://bugs.kde.org/attachment.cgi?id=127689=edit blurry on 4k external monitor SUMMARY Font blurry in konsole's tabbar on KWayland. My laptop's monitor has scale factor 1x, my external monitor (4k) has scale factor 2x. Everything works fine on my laptop monitor, but when I am using external monitor, font got blurry on some cases(firefox, konsole, system settings etc.). Konsole's tabbar is just one of them. I just want to figure out what this bug is (maybe duplicate?). Meanwhile I would like to find a way to temporary fix this bug (for example maybe set my external monitor primary?) STEPS TO REPRODUCE 1. plugin external 4k monitor with scale factor 2x 2. open konsole 3. click konsole's tabbar OBSERVED RESULT font blurry EXPECTED RESULT no blurry SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.6.4-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 15.3 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420308] New: plasma settings crashed after theming my desktop with kvantum.
https://bugs.kde.org/show_bug.cgi?id=420308 Bug ID: 420308 Summary: plasma settings crashed after theming my desktop with kvantum. Product: systemsettings Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: duttashaan...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.5.17-200.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: I was tweaking the various ui settings with kvantum and adding new themes from the default add-on store in the settings. This error never happened before while using the same tweaks in Kubuntu - Custom settings of the application: kvantum theme : kvmojave theme : macmojave iconpack : tela-circle-blue-dark The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8d1518800 (LWP 4834))] Thread 4 (Thread 0x7fb8bb7fa700 (LWP 4837)): #0 0x7fb8d425bd45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb8c0d1019b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7fb8c0d0fdab in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7fb8d42554e2 in start_thread () from /usr/lib64/libpthread.so.0 #4 0x7fb8d56a16a3 in clone () from /usr/lib64/libc.so.6 Thread 3 (Thread 0x7fb8c2a41700 (LWP 4836)): #0 0x7fb8d5696a3f in poll () from /usr/lib64/libc.so.6 #1 0x7fb8d390186e in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb8d39019a3 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb8d5c27843 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb8d5bd11db in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb8d5a21c45 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fb8d5eadf6a in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #7 0x7fb8d5a22d96 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fb8d42554e2 in start_thread () from /usr/lib64/libpthread.so.0 #9 0x7fb8d56a16a3 in clone () from /usr/lib64/libc.so.6 Thread 2 (Thread 0x7fb8c41eb700 (LWP 4835)): #0 0x7fb8d5696a3f in poll () from /usr/lib64/libc.so.6 #1 0x7fb8d421438a in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7fb8d4215fea in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb8c43f4d48 in QXcbEventQueue::run() () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fb8d5a22d96 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb8d42554e2 in start_thread () from /usr/lib64/libpthread.so.0 #6 0x7fb8d56a16a3 in clone () from /usr/lib64/libc.so.6 Thread 1 (Thread 0x7fb8d1518800 (LWP 4834)): [KCrash Handler] #6 0x7fb8d66325a0 in QGestureManager::getState(QObject*, QGestureRecognizer*, Qt::GestureType) () from /usr/lib64/libQt5Widgets.so.5 #7 0x7fb8d6635cc5 in QGestureManager::filterEventThroughContexts(QMultiMap const&, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #8 0x7fb8d6639164 in QGestureManager::filterEvent(QWidget*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #9 0x7fb8d65ed965 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #10 0x7fb8d5bd23e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb8d65eb4b7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7fb8d6641c8d in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7fb8d6644c8c in QWidgetWindow::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7fb8d65e2ab6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7fb8d65ec150 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7fb8d5bd23e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #17 0x7fb8d604bb83 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #18 0x7fb8d604d37b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #19 0x7fb8d60296eb in
[kdeplasma-addons] [Bug 420307] New: Window list plasmoid cannot select window that is on another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=420307 Bug ID: 420307 Summary: Window list plasmoid cannot select window that is on another virtual desktop Product: kdeplasma-addons Version: 5.14.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: k...@kde.lka.org.lu Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Click on window list plasmoid 2. In Window click on an application that is running on another desktop than the current one OBSERVED RESULT 1. The screen flickers briefly, but then comes back to desktop where it was before 2. The target window (on other desktop) is indeed uniconified (when it was iconified before). EXPECTED RESULT 1. The desktop should switch to the desktop where the chosen Window is. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.14.5 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.14.5 Qt Version: 5.11.3 ADDITIONAL INFORMATION Debian 10 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410800] Device in Bookmark will show docker mount point when docker container opened
https://bugs.kde.org/show_bug.cgi?id=410800 --- Comment #2 from Ricardo Sanz --- Same problem here. Additionally, Dolphin sometimes hangs or reacts very very slow, not sure if it's related. Would be possible to have a regexp or something similar that hides devices? So, for example, any /var/lib/docker/overlay/* would be hidden. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 394775] Annotations in the separated XML files
https://bugs.kde.org/show_bug.cgi?id=394775 --- Comment #13 from David Hurka --- (In reply to ederag from comment #12) > okular part.cpp was very readable (as often with kde code), > and docdata capability is still around (for archives). > That opens other possibilities. > > A workaround might be found, without bothering okular devs. Need to think. Wow, I had a hard time understanding the code. (I didn’t read much C++ code before.) If you invest time, it should be possible to make an Okular fork which uses XML annotations. (“Oxular”?) It will probably not be merged, because users who don’t know that old versions of Okular will not miss it, and for the other users it was probably more frustrating than useful. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420270] Monochrome icons are barely visible. Sometimes they are correctly rendered on mouseover.
https://bugs.kde.org/show_bug.cgi?id=420270 --- Comment #11 from David Redondo --- Hi, does this happen with this commit https://phabricator.kde.org/R31:66d0b0b4e3e1adc389dbd4ce1976d81860d1880d ? This fixed a similiar bug in the "you have unsaved changes dialog" in kolourpaint and kwrite? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420270] Monochrome icons are barely visible. Sometimes they are correctly rendered on mouseover.
https://bugs.kde.org/show_bug.cgi?id=420270 --- Comment #10 from Hugo Pereira Da Costa --- addind David in CC Can you have a look ? Possibly git-bisect ? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420270] Monochrome icons are barely visible. Sometimes they are correctly rendered on mouseover.
https://bugs.kde.org/show_bug.cgi?id=420270 Hugo Pereira Da Costa changed: What|Removed |Added CC||k...@david-redondo.de -- You are receiving this mail because: You are watching all bug changes.
