[kwin] [Bug 378532] fast window switching (ALT+Tab) is broken for fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=378532 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Martin Gräßlin --- (In reply to FabiB from comment #2) > (In reply to Martin Gräßlin from comment #1) > > might it be that the window closes when losing focus? > > It only gets minimized when it loses fokus. Minimized windows are moved to the last position in window switching. This is clearly a bug in the games. There is no reason to minimize and that is not the expected behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378544] Wayland session crash with nouveau.
https://bugs.kde.org/show_bug.cgi?id=378544 Martin Gräßlinchanged: What|Removed |Added Keywords|usability | Flags||Wayland+, X11- --- Comment #2 from Martin Gräßlin --- Please provide the output of qdbus org.kde.KWin /KWin supportInformation >From a working X11 session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378544] Wayland session crash with nouveau.
https://bugs.kde.org/show_bug.cgi?id=378544 Martin Gräßlinchanged: What|Removed |Added Assignee|mgraess...@kde.org |kwin-bugs-n...@kde.org Product|kwayland-integration|kwin Version|unspecified |5.9.4 Component|general |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378364] Sequence number options appear to be ignored when sequence number specified as "###"
https://bugs.kde.org/show_bug.cgi?id=378364 --- Comment #4 from Tom Cunningham--- Confirmed that on several folders by date the sequence number does not get reset for each folder, it continues where it left off at the last folder. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378530] plasmashell using more cpu when teamspeak 3 system tray is enabled on intel graphic card.
https://bugs.kde.org/show_bug.cgi?id=378530 TOM Harrisonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from TOM Harrison --- thanks for giving my information. it actually teamspeak3 continuous span the dbus. I may report to teamspeak3 author -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 378368] Kmail/Kontact crash due to missing symbol
https://bugs.kde.org/show_bug.cgi?id=378368 idoitpronechanged: What|Removed |Added CC||monkeyboy...@yahoo.com --- Comment #3 from idoitprone --- lsb_release -a No LSB modules are available. Distributor ID: neon Description:KDE neon Developer Edition Release:16.04 Codename: xenial I am just here to post my crashes. March 30 - kmail: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5MessageCore.so.5: undefined symbol: _ZNK5KMime5Types7Mailbox13prettyAddressEv April 7- kmail: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkmailprivate.so.5: undefined symbol: _ZN10MailCommon24FavoriteCollectionWidget19prefereCreateNewTabEb Progress? I guess kmail keeps complaining about different symbols every update -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Ogichanged: What|Removed |Added CC||ognyan.mo...@gmail.com --- Comment #12 from Ogi --- I too also have this issue (on Arch linux, using my Dell XPS 15 laptop). Don't really need to do anything special to reproduce the issue other than use konsole for a bit, and routinely the clear horizontal lines will come by (usually on the line below the current terminal). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378546] New: KIOExec Error
https://bugs.kde.org/show_bug.cgi?id=378546 Bug ID: 378546 Summary: KIOExec Error Product: plasmashell Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bronsonmath...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Very regularly I get a dialog pop up with the following error. Error - KIOEXEC A folder named /home/user/.cache/kioexec/krun/6746_0/ already exists. It mostly seems to be when clicking a web link from one application other than the web browser. But also happens with other stuff like opening dolphin regularly too... The temporary fix is to just delete the .cache folder. But thats a little frustrating to be constantly deleting that folder. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 378545] New: Disabling power management does not prevent suspend on lid close
https://bugs.kde.org/show_bug.cgi?id=378545 Bug ID: 378545 Summary: Disabling power management does not prevent suspend on lid close Product: Powerdevil Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: istaz...@gmail.com Target Milestone: --- I want to play music with the lid closed. I expect that clicking the battery icon in the system tray and un-checking "Enable Power Management" will accomplish this, but it does not. I can go into power management settings and un-check "Butten events handling", but I would rather not have to do this. Un-checking "Enable Power Management" from the system tray should do this. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375855] Show differences is not working.
https://bugs.kde.org/show_bug.cgi?id=375855 Kevin Funkchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Kevin Funk --- Works fine for me as well (KDev 5.1). Needs more information (e.g. the debug output) if the issue persists. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375855] Show differences is not working.
https://bugs.kde.org/show_bug.cgi?id=375855 Diego Garciachanged: What|Removed |Added CC||dnico...@gmail.com --- Comment #1 from Diego Garcia --- I can't reproduce in Kdev 5.1 / KF 5.32 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378532] fast window switching (ALT+Tab) is broken for fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=378532 --- Comment #2 from FabiB--- (In reply to Martin Gräßlin from comment #1) > might it be that the window closes when losing focus? It only gets minimized when it loses fokus. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 358457] QSaveFile: Kate removes a hard link to file when opening a file with several hard links
https://bugs.kde.org/show_bug.cgi?id=358457 midnathe...@yahoo.com changed: What|Removed |Added CC||midnathe...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 378544] Wayland session crash with nouveau.
https://bugs.kde.org/show_bug.cgi?id=378544 --- Comment #1 from kde38--- I want to add that KDE Neon is the Dev Stable version and it is fully updated. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 296800] Sideways tabs
https://bugs.kde.org/show_bug.cgi?id=296800 Sven Brauchchanged: What|Removed |Added CC||m...@svenbrauch.de --- Comment #4 from Sven Brauch --- We could do it like QtCreator, I guess. I personally don't see an issue, I think it's readable just fine. It's not like you would struggle to decipher the word "Projects" written on the tab fifteen times every day. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 378544] Wayland session crash with nouveau.
https://bugs.kde.org/show_bug.cgi?id=378544 kde38changed: What|Removed |Added Severity|grave |major Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 378544] New: Wayland session crash with nouveau.
https://bugs.kde.org/show_bug.cgi?id=378544 Bug ID: 378544 Summary: Wayland session crash with nouveau. Product: kwayland-integration Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: rickard.gerths...@gmail.com Target Milestone: --- I have tried to use wayland session with both an NVIDIA GT210 and a GTX580 using open source nouveau drivers but the session either crashes right away or hangs/freeze when it has logged in or whn I click on the start menu button. The start menu barely becomes visible before the system freeze. I have tried this in KDE Neon, OpenMandriva Lx and Antergos and they all behave the same. All the distros have been x86_64/amd64 and the X11 sessions works. If you need more inforamtion then please tell me what I should provide and how I will do that. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 296800] Sideways tabs
https://bugs.kde.org/show_bug.cgi?id=296800 Diego Garciachanged: What|Removed |Added CC||dnico...@gmail.com --- Comment #3 from Diego Garcia --- I'm also not a fan of vertical text. A good solution would be to have an option to only show the icons in the docks. That way we can also keep more panels in the left/right docks. Something like like Atom's toolbar plugin: https://atom.io/packages/tool-bar -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378536] Window title isn't RGB antialiased
https://bugs.kde.org/show_bug.cgi?id=378536 Hugo Pereira Da Costachanged: What|Removed |Added Component|window decoration |decorations Assignee|hugo.pereira.da.costa@gmail |kwin-bugs-n...@kde.org |.com| Product|Breeze |kwin Target Milestone|--- |5 --- Comment #4 from Hugo Pereira Da Costa --- So double checking here. It seems the problem is also present for any other window decoration, (e.g. oxygen, plastique, which is Aurorae). So upstreaming to kwin. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 --- Comment #15 from gust...@angulosolido.pt --- Note: the attached tarball contents belong to the plasmoid that got installed directly from the KDE UI as a user. I then located it in the home folder, put it into a tarball, deinstalled using the KDE UI and tried to put it system wide at /usr/share/plasma/plasmoids (which worked). I don't know exactly where KDE downloads it from. Tested with Ubunty 16.04 and KDE LTS backport from the Kubuntu repositiories. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 369470] Typo in balooshow -h
https://bugs.kde.org/show_bug.cgi?id=369470 Elvis Angelacciochanged: What|Removed |Added Version Fixed In||5.34 Latest Commit||https://commits.kde.org/bal ||oo/ab37f37b96bd26ad9b6710bf ||3f5bb554836848d9 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Elvis Angelaccio --- Git commit ab37f37b96bd26ad9b6710bf3f5bb554836848d9 by Elvis Angelaccio. Committed on 07/04/2017 at 21:18. Pushed by elvisangelaccio into branch 'master'. balooshow: fix typo FIXED-IN: 5.34 M +1-1src/tools/balooshow/main.cpp https://commits.kde.org/baloo/ab37f37b96bd26ad9b6710bf3f5bb554836848d9 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 --- Comment #14 from gust...@angulosolido.pt --- Created attachment 104918 --> https://bugs.kde.org/attachment.cgi?id=104918=edit alternative widget Batterytime alternative widget Batterytime -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 --- Comment #13 from gust...@angulosolido.pt --- I still have this problem with KDE 5.8.5 LTS and I confirmed it really is a problem with powerdevil because an alternative widget works fine. I'm attaching the widget that I have confirmed that works. It only needs to be untarred at: /usr/share/plasma/plasmoids and then it can be added to the system tray. In short: the original battery monitor from KDE seems to fail randomly. The attached one works everytime. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla
https://bugs.kde.org/show_bug.cgi?id=375053 Luca Giamboninichanged: What|Removed |Added CC||luc...@bluewin.ch -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #15 from Janet--- Any news on this? This bug is still present in 5.9. Related: Bug 356377? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 378543] Present Window effect inhibits kscreenlocker
https://bugs.kde.org/show_bug.cgi?id=378543 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Martin Gräßlin --- This is fixed on Wayland and impossible to fix on X11. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 257602] K3B cannot burn Blurays (or AVCHDs)
https://bugs.kde.org/show_bug.cgi?id=257602 Chrischanged: What|Removed |Added CC||k...@ontoemail.com -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 378497] kbibtex crashes when closing settings dialog
https://bugs.kde.org/show_bug.cgi?id=378497 --- Comment #4 from Thomas Fischer--- (In reply to Andrius Štikonas from comment #2) > Works now! Ok, thanks for the quick reply > P.S. I'll leave this bug open since the fix is not yet committed. Indeed, I can do that by adding a special keyword in the commit message: https://community.kde.org/Policies/Commit_Policy#Special_keywords_in_GIT_and_SVN_log_messages -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 378497] kbibtex crashes when closing settings dialog
https://bugs.kde.org/show_bug.cgi?id=378497 Thomas Fischerchanged: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Version Fixed In||0.8 Latest Commit||https://commits.kde.org/kbi ||btex/b89b498f719361c6026bed ||e4893a5456dc3c34fe --- Comment #3 from Thomas Fischer --- Git commit b89b498f719361c6026bede4893a5456dc3c34fe by Thomas Fischer. Committed on 07/04/2017 at 19:26. Pushed by thomasfischer into branch 'master'. Remove 'static' from QObject-derived objects Objects of classes that are derived from QObject are supposed to be in a clear parent-children relation: at object creation, a QObject-derived parent is passed to the QObject constructor. QObject's destructor will take care that all child objects will be destroyed as well. This conflicts with QObject-derived objects that are declared 'static', as this may imply a different life span than the object's parent. This may lead to double-destroy situations crashing KBibTeX. This commit will avoid having the 'static' keyword at variable declarations of QObject-derived objects. FIXED-IN: 0.8 M +1-1src/gui/preferences/settingsidsuggestionswidget.cpp M +0-4src/io/fileimporterbibtex.cpp M +0-1src/io/fileimporterbibtex.h M +1-1src/networking/zotero/items.cpp https://commits.kde.org/kbibtex/b89b498f719361c6026bede4893a5456dc3c34fe -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 378543] New: Present Window effect inhibits kscreenlocker
https://bugs.kde.org/show_bug.cgi?id=378543 Bug ID: 378543 Summary: Present Window effect inhibits kscreenlocker Product: kscreenlocker Version: unspecified Platform: Fedora RPMs OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sud...@sudhirkhanger.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- If you leave your system in present window effect then system won't be locked. How to reproduce? Trigger Present Window effect with either mouse hover in the corner or Ctrl+F9/F10. Wait for system to be locked. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368175] Error creating new partition with KDE auto-mount enabled
https://bugs.kde.org/show_bug.cgi?id=368175 --- Comment #2 from Andrius Štikonas--- (In reply to Mattia from comment #1) > This still applies to PM 3.0.1 Yeah, there were no changes so far :(. I tried asking other Plasma people but nobody knew how to disable automount... -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 378497] kbibtex crashes when closing settings dialog
https://bugs.kde.org/show_bug.cgi?id=378497 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Andrius Štikonas --- Works now! P.S. I'll leave this bug open since the fix is not yet committed. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 378497] kbibtex crashes when closing settings dialog
https://bugs.kde.org/show_bug.cgi?id=378497 --- Comment #1 from Thomas Fischer--- Created attachment 104917 --> https://bugs.kde.org/attachment.cgi?id=104917=edit Remove 'static' property from instances of FileImporterBibTeX Please check if this patch fixes the crash for you. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368175] Error creating new partition with KDE auto-mount enabled
https://bugs.kde.org/show_bug.cgi?id=368175 Mattiachanged: What|Removed |Added Version|2.2 |3.0 --- Comment #1 from Mattia --- This still applies to PM 3.0.1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368688] Control-tab not working in VI mode
https://bugs.kde.org/show_bug.cgi?id=368688 Kevin Funkchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Kevin Funk --- Works fine for me as well. Assuming fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368688] Control-tab not working in VI mode
https://bugs.kde.org/show_bug.cgi?id=368688 Kevin Funkchanged: What|Removed |Added Version Fixed In||5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 --- Comment #12 from Tim Taylor--- I still have this problem with Kubuntu 16.10. As an interim measure I've written a little script that will report the key battery stats: --- #!/bin/bash upower -i /org/freedesktop/UPower/devices/battery_BAT0 | gawk '/percentage|state|time/ {print}' --- -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 378476] Dark themes compatibility
https://bugs.kde.org/show_bug.cgi?id=378476 Matthieu Gallienchanged: What|Removed |Added Latest Commit|https://commits.kde.org/eli |https://commits.kde.org/eli |sa/2428fb8ee9c6b2f26372fc52 |sa/1ee439d514f39bae3c6a413e |b66c2b488df839c4|b71e96ae9107b397 --- Comment #2 from Matthieu Gallien --- Git commit 1ee439d514f39bae3c6a413eb71e96ae9107b397 by Matthieu Gallien. Committed on 07/04/2017 at 15:47. Pushed by mgallien into branch 'master'. fix more problems with colors not being good or refreshed when changing palette M +15 -3src/MediaPlayListView.qml https://commits.kde.org/elisa/1ee439d514f39bae3c6a413eb71e96ae9107b397 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 366040] libkf5wallet5: timeout when using GPG and gpg-agent
https://bugs.kde.org/show_bug.cgi?id=366040 Rolf Eike Beerchanged: What|Removed |Added CC||k...@opensource.sf-tec.de Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Rolf Eike Beer --- Same on 5.30. Even worse: after e.g. suspend the password must be typed in again (or copied from kwalletmanager5) as there seems tobe no try to reconnect to wallet (which could be a NM problem, but I had similar issues with KMail in KDE4 days). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368688] Control-tab not working in VI mode
https://bugs.kde.org/show_bug.cgi?id=368688 Diego Garciachanged: What|Removed |Added CC||dnico...@gmail.com --- Comment #2 from Diego Garcia --- I can't reproduce this. Ctrl+tab and all the others work for me in all modes (normal, insert, visual).Maybe it's been fixed since the report? Plasma 5.9 Kdevelop 5.1 KF 5.32.0 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 Rolf Eike Beerchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||k...@opensource.sf-tec.de Ever confirmed|0 |1 --- Comment #11 from Rolf Eike Beer --- I have the same, KF5 5.30, plasma 5.8.95. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 360681] Battery monitor shows 0:60 instead of 1:00 for remaining battery
https://bugs.kde.org/show_bug.cgi?id=360681 Rolf Eike Beerchanged: What|Removed |Added Ever confirmed|0 |1 CC||k...@opensource.sf-tec.de Status|UNCONFIRMED |CONFIRMED --- Comment #5 from Rolf Eike Beer --- I've seen the same on openSUSE. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 372163] Investment sells giving the wrong result
https://bugs.kde.org/show_bug.cgi?id=372163 --- Comment #10 from NSLW--- (In reply to Jose Arthur Benetasso Villanova from comment #9) > Download test.kmy and fakequote.sh. > > Configure kmymoney online quote in "Settings" > "Configure KMymoney..." > > "Online Quotes" > > Create a new Online quote as: > Name: TEST > URL file:///home/ze/bin/fakequote.sh %1 > Symbol: '([^"]*)', > Price: '[^"]*','[^"]*','([^"]*)' > Date: '[^"]*','([^"]*)', > Date Format: %y-%m-%d > > Check if the investment is pointing to the corret online source. > > In investments, right button, "online price update". > > Result: > Executing /home/ze/bin/fakequote.sh TEST... > Symbol found: TEST','2017-55-07 > Price found: 12.34567890 (12.3457) > Price for TEST updated (id E01) > > But in investment: 12.3500 The problem is fixed now. BTW. Your problem wasn't caused by my fix to this problem and you had that problem before, so please don't lie. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 378164] "No suitable accounts were found at this bank" after successful login to OFX URL
https://bugs.kde.org/show_bug.cgi?id=378164 --- Comment #9 from Bob Igo--- Is there any other test information I can provide? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 378542] New: Sorting connections
https://bugs.kde.org/show_bug.cgi?id=378542 Bug ID: 378542 Summary: Sorting connections Product: plasma-nm Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: fuermetz+...@mailbox.org Target Milestone: --- Is it possible to implement an option to display the VPN connections after the wireless connections on the popup? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378540] New: Crash after setting default screen
https://bugs.kde.org/show_bug.cgi?id=378540 Bug ID: 378540 Summary: Crash after setting default screen Product: plasmashell Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kdeb...@loftwyr.ca CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-18-generic x86_64 Distribution: Ubuntu Zesty Zapus (development branch) -- Information about the crash: - What I was doing when the application crashed: I had just set up a default screen (new monitor setup) and then when I double clicked on a systray icon (skype) to open it up plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef99560d40 (LWP 5010))] Thread 24 (Thread 0x7fee79363700 (LWP 7866)): #0 0x7fef926d58b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fef6f571e44 in () at /usr/lib/nvidia-378/libGLX_nvidia.so.0 #2 0x7fef6e28f394 in () at /usr/lib/nvidia-378/libnvidia-glcore.so.378.13 #3 0x7fef6f57112c in () at /usr/lib/nvidia-378/libGLX_nvidia.so.0 #4 0x7fef926cf6da in start_thread (arg=0x7fee79363700) at pthread_create.c:456 #5 0x7fef9313917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 23 (Thread 0x7fee79b64700 (LWP 7837)): #0 0x7fef926d5510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef9382eb4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fef972e6495 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fef972e6d8a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fef9382dc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fef926cf6da in start_thread (arg=0x7fee79b64700) at pthread_create.c:456 #6 0x7fef9313917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 22 (Thread 0x7fee7db1a700 (LWP 6868)): #0 0x7fef926d58b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fef6f571e44 in () at /usr/lib/nvidia-378/libGLX_nvidia.so.0 #2 0x7fef6e28f394 in () at /usr/lib/nvidia-378/libnvidia-glcore.so.378.13 #3 0x7fef6f57112c in () at /usr/lib/nvidia-378/libGLX_nvidia.so.0 #4 0x7fef926cf6da in start_thread (arg=0x7fee7db1a700) at pthread_create.c:456 #5 0x7fef9313917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 21 (Thread 0x7fee7b366700 (LWP 6867)): #0 0x7fef926d5510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef9382eb4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fef972e6495 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fef972e6d8a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fef9382dc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fef926cf6da in start_thread (arg=0x7fee7b366700) at pthread_create.c:456 #6 0x7fef9313917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 20 (Thread 0x7fee5b7fe700 (LWP 6866)): #0 0x7fef926d58b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fef6f571e44 in () at /usr/lib/nvidia-378/libGLX_nvidia.so.0 #2 0x7fef6e28f394 in () at /usr/lib/nvidia-378/libnvidia-glcore.so.378.13 #3 0x7fef6f57112c in () at /usr/lib/nvidia-378/libGLX_nvidia.so.0 #4 0x7fef926cf6da in start_thread (arg=0x7fee5b7fe700) at pthread_create.c:456 #5 0x7fef9313917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 19 (Thread 0x7fee597fa700 (LWP 6865)): #0 0x7fef926d5510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef9382eb4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fef972e6495 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fef972e6d8a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fef9382dc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fef926cf6da in start_thread (arg=0x7fee597fa700) at pthread_create.c:456 #6 0x7fef9313917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 18 (Thread 0x7fee3bfff700 (LWP 6748)): #0 0x7fef926d58b9 in
[Spectacle] [Bug 375382] Wish: DBus Function for copy to clipboard
https://bugs.kde.org/show_bug.cgi?id=375382 Anton Skorokhodchanged: What|Removed |Added CC||an...@nsl.cz -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 378541] New: Contact crash when deleting Local Folder
https://bugs.kde.org/show_bug.cgi?id=378541 Bug ID: 378541 Summary: Contact crash when deleting Local Folder Product: kontact Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: as9902...@gmail.com Target Milestone: --- Application: kontact (4.14.5) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.1.8-server-1.mga5 x86_64 Distribution: "Mageia 5" -- Information about the crash: Since my email wasn't working after the IT sent me parameters for using new email service IMAP + SMTP from office365.com in our company, I decided to delete everything and start setting up the new account again. However, when I deleted Local Folders, which had a lot of data and subfolders, Kmail crashed. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0556621800 (LWP 21926))] Thread 4 (Thread 0x7f053729b700 (LWP 21927)): #0 0x7f054dc5f67f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0551332bdf in () at /lib64/libQtWebKit.so.4 #2 0x7f0551332c19 in () at /lib64/libQtWebKit.so.4 #3 0x7f054dc5a5bd in start_thread () at /lib64/libpthread.so.0 #4 0x7f0553b9662d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f04f6581700 (LWP 21928)): #0 0x7f054dc5f67f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0551061d83 in () at /lib64/libQtWebKit.so.4 #2 0x7f0551363826 in () at /lib64/libQtWebKit.so.4 #3 0x7f054dc5a5bd in start_thread () at /lib64/libpthread.so.0 #4 0x7f0553b9662d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f04e7705700 (LWP 21937)): #0 0x7f0553b866fd in read () at /lib64/libc.so.6 #1 0x7f054d6cabf0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f054d68899c in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f054d688e5b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f054d688fbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f0554307e3e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #6 0x7f05542d9931 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #7 0x7f05542d9c45 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #8 0x7f05541d7899 in QThread::exec() () at /lib64/libQtCore.so.4 #9 0x7f05541d9fff in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #10 0x7f054dc5a5bd in start_thread () at /lib64/libpthread.so.0 #11 0x7f0553b9662d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0556621800 (LWP 21926)): [KCrash Handler] #5 0x7f0553ad2547 in raise () at /lib64/libc.so.6 #6 0x7f0553ad3cda in abort () at /lib64/libc.so.6 #7 0x7f05541cfae4 in qt_message_output(QtMsgType, char const*) () at /lib64/libQtCore.so.4 #8 0x7f05541cfc69 in qt_message(QtMsgType, char const*, __va_list_tag*) () at /lib64/libQtCore.so.4 #9 0x7f05541d0474 in qFatal(char const*, ...) () at /lib64/libQtCore.so.4 #10 0x7f04ec6a4cb7 in MailCommon::Kernel::self() () at /lib64/libmailcommon.so.4 #11 0x7f04ec6ec390 in MailCommon::FolderCollection::writeConfig() const () at /lib64/libmailcommon.so.4 #12 0x7f04ec6ecb82 in MailCommon::FolderCollection::~FolderCollection() () at /lib64/libmailcommon.so.4 #13 0x7f04ec6ecc8f in QMap >::freeData(QMapData*) [clone .isra.19] () at /lib64/libmailcommon.so.4 #14 0x7f0553ad5232 in __run_exit_handlers () at /lib64/libc.so.6 #15 0x7f0553ad5285 in () at /lib64/libc.so.6 #16 0x7f04ec6a3fae in MailCommon::Kernel::emergencyExit(QString const&) () at /lib64/libmailcommon.so.4 #17 0x7f04ec6a43b7 in MailCommon::Kernel::createDefaultCollectionDone(KJob*) () at /lib64/libmailcommon.so.4 #18 0x7f05542ee88a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #19 0x7f0554775b52 in KJob::result(KJob*) () at /lib64/libkdecore.so.5 #20 0x7f0554775b90 in KJob::emitResult() () at /lib64/libkdecore.so.5 #21 0x7f0552bad4c9 in Akonadi::SpecialCollectionsRequestJobPrivate::lockResult(KJob*) () at /lib64/libakonadi-kde.so.4 #22 0x7f05542ee88a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #23 0x7f0554775b52 in KJob::result(KJob*) () at /lib64/libkdecore.so.5 #24 0x7f0554775b90 in KJob::emitResult() () at /lib64/libkdecore.so.5 #25 0x7f0552ba46f3 in Akonadi::GetLockJob::Private::timeout() () at /lib64/libakonadi-kde.so.4 #26 0x7f05542ee88a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #27
[Breeze] [Bug 378536] Window title isn't RGB antialiased
https://bugs.kde.org/show_bug.cgi?id=378536 --- Comment #3 from Alex--- It seems that only window title has got problem with rgb antialiasing. RGB is not enabled by default in Neon distro. To enable it go to font settings and change antialiasing from system settings to enabled, then choose settings and change subpixel to rgb there. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378011] KMail 5.4.3 Mailing list not resolved
https://bugs.kde.org/show_bug.cgi?id=378011 --- Comment #7 from Gerry Gavigan--- [code] linux-g2qv:~ # zypper in akonadi-runtime Retrieving repository 'Packman Repository' metadata ...[done] Building repository 'Packman Repository' cache [done] Loading repository data... Reading installed packages... Resolving package dependencies... Problem: installed akonadi-server-16.12.3-1.1.x86_64 obsoletes akonadi-runtime < 16.12.3 provided by akonadi-runtime-1.13.0-9.1.x86_64 Solution 1: Following actions will be done: deinstallation of akonadi-server-16.12.3-1.1.x86_64 deinstallation of akonadi-server-sqlite-16.12.3-1.1.x86_64 Solution 2: do not install akonadi-runtime-1.13.0-9.1.x86_64 Choose from above solutions by number or cancel [1/2/c] (c): [/code] -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 378536] Window title isn't RGB antialiased
https://bugs.kde.org/show_bug.cgi?id=378536 Hugo Pereira Da Costachanged: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com --- Comment #2 from Hugo Pereira Da Costa --- Hi, Thanks for reporting Two questions: - does it work as expected with other window decorations ? - any idea how to setup RGB font antialiasing in Qt ? (I would have thought it automatic, but maybe am missing something. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 Petroschanged: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #10 from Petros --- LLVM/Clang-4.0.0-r1 solved for me this issue. KDevelop no longer crashes if I remove the comment (//) infront of text. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366609] Context menu do not close when discarded on Wayland
https://bugs.kde.org/show_bug.cgi?id=366609 Martin Gräßlinchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/1193b0da771a5d1042bf2aed0 ||a2727f89ddf488e Resolution|--- |FIXED Version Fixed In||5.10 --- Comment #9 from Martin Gräßlin --- Git commit 1193b0da771a5d1042bf2aed0a2727f89ddf488e by Martin Gräßlin. Committed on 07/04/2017 at 14:14. Pushed by graesslin into branch 'master'. Initial support for popup window handling Summary: So far KWin did not properly handle popup windows. That is when a popup surface got created and a click outside the surface happened KWin did not send out the popupDone Wayland event. This change makes KWin aware of whether a surface is a popup and tracks through a new PopupInputFilter whether there are popup windows. In case there are popups the new filter waits for mouse press events and cancels the popups if the press does not happen on any surface belonging to the same client. To quote the relevant section of the Wayland documentation: The popup grab continues until the window is destroyed or a mouse button is pressed in any other client's window. A click in any of the client's surfaces is reported as normal, however, clicks in other clients' surfaces will be discarded and trigger the callback. So far the support is still incomplete. Not yet implemented are: * support xdg_shell popup windows * verifying whether the popup is allowed to be a popup * cancel the popup on more global interactions like screen lock or kwin effect FIXED-IN: 5.10 Test Plan: Auto test and manual testing with QtWayland client Reviewers: #plasma, #kwin Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D5177 M +1-0CMakeLists.txt M +81 -0autotests/integration/pointer_input.cpp M +2-0input.cpp M +0-1pointer_input.cpp A +80 -0popup_input_filter.cpp [License: GPL (v2/3)] A +50 -0popup_input_filter.h [License: GPL (v2/3)] M +16 -0shell_client.cpp M +3-0shell_client.h M +26 -0toplevel.h https://commits.kde.org/kwin/1193b0da771a5d1042bf2aed0a2727f89ddf488e -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #6 from Wayne Arnold--- any suggestions on how to add in the MEM option. are there other instructions that can be used as a guide ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 378539] balooshow: always a kf5.kcoreaddons.kaboutdata error displayed
https://bugs.kde.org/show_bug.cgi?id=378539 Don Curtischanged: What|Removed |Added Severity|normal |major --- Comment #1 from Don Curtis --- While debugging the "balooshow" code and, comparing it to the "balooctl" and "baloosearch" code the following seems to be the cause of this issue: "balooshow": main.cpp: lines 63 and 64: * KAboutData::setApplicationData is being called before the "QCoreApplication" constructor. Swapping these two lines and recompiling resolves this issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 378539] New: balooshow: always a kf5.kcoreaddons.kaboutdata error displayed
https://bugs.kde.org/show_bug.cgi?id=378539 Bug ID: 378539 Summary: balooshow: always a kf5.kcoreaddons.kaboutdata error displayed Product: frameworks-baloo Version: 5.26.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: pinak.ah...@gmail.com Reporter: bugrprt21...@online.de Target Milestone: --- Whenever balooshow is called, regardless of options and/or a file name, or not, the following error is displayed: "kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=344326 Martin Gräßlinchanged: What|Removed |Added CC||redredempt...@protonmail.co ||m --- Comment #157 from Martin Gräßlin --- *** Bug 378537 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378537] Screen artifacts after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=378537 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 344326 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371015] wayland : X applications have default X icon.
https://bugs.kde.org/show_bug.cgi?id=371015 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||andr...@stikonas.eu Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 375022] Volume Step resets to 5%
https://bugs.kde.org/show_bug.cgi?id=375022 Harald Sitterchanged: What|Removed |Added Version|5.7.5 |unspecified Assignee|sit...@kde.org |now...@gmail.com Product|systemsettings |plasma-pa Component|kcm_phonon |kcm CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378538] Crash when loading a document with vector data
https://bugs.kde.org/show_bug.cgi?id=378538 Boudewijn Remptchanged: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378538] New: Crash when loading a document with vector data
https://bugs.kde.org/show_bug.cgi?id=378538 Bug ID: 378538 Summary: Crash when loading a document with vector data Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: b...@valdyas.org Target Milestone: --- To reproduce: * load a kra image with a vector layer created in 3.x in git master * save the image under another name with git master * close the image * load the new image Backtrace: (gdb) bt #0 0x7fffee037c8e in QObject::removeEventFilter(QObject*) () at /home/boud/dev/deps/lib/libQt5Core.so.5 #1 0x77865721 in KisInputManager::setupAsEventFilter(QObject*) (this=0x6d12df8, receiver=0xa5c76c0) at /home/boud/dev/krita/libs/ui/input/kis_input_manager.cpp:150 #2 0x7786b1d7 in KisInputManager::Private::CanvasSwitcher::addCanvas(KisCanvas2*) (this=0x6b4db18, canvas=0xab4e818) at /home/boud/dev/krita/libs/ui/input/kis_input_manager_p.cpp:178 #3 0x778656d0 in KisInputManager::addTrackedCanvas(KisCanvas2*) (this=, canvas=) at /home/boud/dev/krita/libs/ui/input/kis_input_manager.cpp:103 #4 0x7791f86f in KisViewManager::slotViewAdded(KisView*) (this=0x6d12950, view=) at /home/boud/dev/krita/libs/ui/KisViewManager.cpp:324 #5 0x7797ebf4 in KisViewManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /home/boud/dev/build/libs/ui/kritaui_automoc.dir/moc_KisViewManager_XZDRS5QDZO4IUV.cpp:172 #6 0x7fffee030441 in QMetaObject::activate(QObject*, int, int, void**) () at /home/boud/dev/deps/lib/libQt5Core.so.5 #7 0x77970a42 in KisPart::sigViewAdded(KisView*) (this=this@entry=0x77dda050 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>, _t1=_t1@entry=0xab4ec90) at /home/boud/dev/build/libs/ui/kritaui_automoc.dir/moc_KisPart_US6NGILVIMA7VI.cpp:291 #8 0x7790545e in KisPart::addView(KisView*) (this=this@entry=0x77dda050 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>, view=view@entry=0xab4ec90) at /home/boud/dev/krita/libs/ui/KisPart.cpp:261 #9 0x77907118 in KisPart::createView(KisDocument*, KoCanvasResourceManager*, KActionCollection*, QWidget*) (this=0x77dda050 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>, document=document@entry=0xa2b1fd0, resourceManager=resourceManager@entry=0x6d12d90, actionCollection=actionCollection@entry=0x6d12930, parent=parent@entry=0x6b4d550) at /home/boud/dev/krita/libs/ui/KisPart.cpp:245 #10 0x778ecd24 in KisMainWindow::addViewAndNotifyLoadingCompleted(KisDocument*) (this=0x6b4d550, document=0xa2b1fd0) at /home/boud/dev/krita/libs/ui/KisMainWindow.cpp:789 #11 0x778ece30 in KisMainWindow::slotLoadCompleted() (this=0x6b4d550) at /home/boud/dev/krita/libs/ui/KisMainWindow.cpp:810 #12 0x778fbdb7 in KisMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x6b4d550, _c=, _id=, _a=0x7fffbb20) at /home/boud/dev/build/libs/ui/moc_KisMainWindow.cpp:325 #13 0x7fffee030441 in QMetaObject::activate(QObject*, int, int, void**) () at /home/boud/dev/deps/lib/libQt5Core.so.5 #14 0x778d2a78 in KisDocument::openUrlInternal(QUrl const&) (this=this@entry=0xa2b1fd0, url=...) at /home/boud/dev/krita/libs/ui/KisDocument.cpp:1471 #15 0x778d2d30 in KisDocument::openUrl(QUrl const&, KisDocument::OpenUrlFlags) (this=this@entry=0xa2b1fd0, _url=..., flags=flags@entry=KisDocument::OPEN_URL_FLAG_NONE) at /home/boud/dev/krita/libs/ui/KisDocument.cpp:972 #16 0x778ecff0 in KisMainWindow::openDocumentInternal(QUrl const&, KisDocument*) (this=this@entry=0x6b4d550, url=..., newdoc=0xa2b1fd0, newdoc@entry=0x0) at /home/boud/dev/krita/libs/ui/KisMainWindow.cpp:772 #17 0x778f436d in KisMainWindow::openDocument(QUrl const&) (this=this@entry=0x6b4d550, url=...) at /home/boud/dev/krita/libs/ui/KisMainWindow.cpp:754 #18 0x778f4571 in KisMainWindow::slotFileOpenRecent(QUrl const&) (this=0x6b4d550, url=...) at /home/boud/dev/krita/libs/ui/KisMainWindow.cpp:1347 #19 0x778fbd0e in KisMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x6b4d550, _c=, _id=, _a=0x7fffbfe0) at /home/boud/dev/build/libs/ui/moc_KisMainWindow.cpp:311 #20 0x7fffee030441 in QMetaObject::activate(QObject*, int, int, void**) () at /home/boud/dev/deps/lib/libQt5Core.so.5 #21 0x7474fc32 in KRecentFilesAction::urlSelected(QUrl const&) (this=this@entry=0x7d41770, _t1=...) at /home/boud/dev/build/libs/widgetutils/moc_krecentfilesaction.cpp:204 #22 0x74751042 in KRecentFilesActionPrivate::_k_urlSelected(QAction*) (this=, action=0xa2eedc0) at /home/boud/dev/krita/libs/widgetutils/config/krecentfilesaction.cpp:99 #23 0x747511bb in
[kwin] [Bug 378537] New: Screen artifacts after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=378537 Bug ID: 378537 Summary: Screen artifacts after resuming from sleep Product: kwin Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: redredempt...@protonmail.com Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Resuming PC from sleep. - Unusual behavior I noticed: The entire screen is filled up with artifacts that are gone once you switch to any virtual console, or Kwin crashes. However, this is the first time when Kwin crashes after several reproduces of the bug. The bug was orginally reported on the NVIDIA forums due to its occurence after upgrading the driver from 378.13-4 to 378.13-5 on Arch Linux: https://devtalk.nvidia.com/default/topic/1002810/linux/gtx-1070-378-13-arch-linux-kde-plasma-5-screen-artifacts-after-resuming-from-sleep/?_sec=1&_sem=WW91IGhhdmUgYmVlbiBsb2dnZWQgb3V0IGZvciBzZWN1cml0eSBwdXJwb3NlcyBkdWUgdG8gYW4gYWNjb3VudCBpbmNvbnNpc3RlbmN5LiAgUGxlYXNlIGxvZyBiYWNrIGluIHRvIGNvbnRpbnVlIGFzIG5vcm1hbC4= The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f06bb338840 (LWP 748))] Thread 12 (Thread 0x7f05ea5c3700 (LWP 1908)): #0 0x7f06b3fc2ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0698135e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f0689dd0394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7f069813512c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7f06b3fbc2e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f06bad8054f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f0699acc700 (LWP 1907)): #0 0x7f06b3fc2756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f06b81d058b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f06b33c6665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f06b33c6f72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f06b81cf6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f06b3fbc2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f06bad8054f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f0683a33700 (LWP 1906)): #0 0x7f06bad7676b in ppoll () at /usr/lib/libc.so.6 #1 0x7f06b83fa2f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f06b83fb96a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f06b83a889a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f06b81caa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f06b2ce3025 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f06b81cf6d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f06b3fbc2e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f06bad8054f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f05f2564700 (LWP 1256)): #0 0x7f06b3fc2ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0698135e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f0689dd0394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7f069813512c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7f06b3fbc2e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f06bad8054f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f05f2fad700 (LWP 1255)): #0 0x7f06b3fc2756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f06b81d058b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f06b33c6665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f06b33c6f72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f06b81cf6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f06b3fbc2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f06bad8054f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f068b7ff700 (LWP 1254)): #0 0x7f06bad7676b in ppoll () at /usr/lib/libc.so.6 #1 0x7f06b83fa2f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f06b83fb96a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f06b83a889a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f06b81caa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f06b2ce3025 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f06b81cf6d8 in () at /usr/lib/libQt5Core.so.5
[krita] [Bug 378417] Regression in 3.1.3 with Pan tool
https://bugs.kde.org/show_bug.cgi?id=378417 Scott Petrovicchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378417] Regression in 3.1.3 with Pan tool
https://bugs.kde.org/show_bug.cgi?id=378417 --- Comment #3 from Scott Petrovic--- this was fixed as of Krita 3.1.2 beta 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378532] fast window switching (ALT+Tab) is broken for fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=378532 --- Comment #1 from Martin Gräßlin--- might it be that the window closes when losing focus? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 378528] WhisList: Dynamic Themes
https://bugs.kde.org/show_bug.cgi?id=378528 Martin Gräßlinchanged: What|Removed |Added Product|plasma-integration |Breeze Assignee|mgraess...@kde.org |plasma-de...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377614] Crash when moving larger quantities of animation frames
https://bugs.kde.org/show_bug.cgi?id=377614 Dmitry Kazakovchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/b0aa6b3cd990ed276bfcaced ||bba97a5bd0efb154 --- Comment #5 from Dmitry Kazakov --- Git commit b0aa6b3cd990ed276bfcacedbba97a5bd0efb154 by Dmitry Kazakov. Committed on 07/04/2017 at 12:38. Pushed by dkazakov into branch 'master'. Fix a crash when the layer gets changed too quickly during frames move Ref T5753 M +6-1plugins/dockers/animation/timeline_frames_model.cpp https://commits.kde.org/krita/b0aa6b3cd990ed276bfcacedbba97a5bd0efb154 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 363376] KDevelop crashes on valgrind debug launch
https://bugs.kde.org/show_bug.cgi?id=363376 Kevin Funkchanged: What|Removed |Added Component|Plugin: Valgrind|valgrind integration -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 375022] Volume Step resets to 5%
https://bugs.kde.org/show_bug.cgi?id=375022 Mike Morrischanged: What|Removed |Added CC||mikro...@gmail.com --- Comment #1 from Mike Morris --- Confirming this bug. For me Volume Step ALWAYS resets to 5% between logouts despite that I always set it manually to 2%. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 336948] Kdev crashed when using the "import project from github" option
https://bugs.kde.org/show_bug.cgi?id=336948 Kevin Funkchanged: What|Removed |Added Component|general |Project provider: Github -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360589] Kdevelop fails authentication and Crashes when tried to integrate with GitHub
https://bugs.kde.org/show_bug.cgi?id=360589 Kevin Funkchanged: What|Removed |Added Component|general |Project provider: Github -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372144] GitHub is never authorized Kubuntu 16.10 no crash
https://bugs.kde.org/show_bug.cgi?id=372144 Kevin Funkchanged: What|Removed |Added Component|VCS: git|Project provider: Github -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371053] KDevelop crashes when fetching a project from Github
https://bugs.kde.org/show_bug.cgi?id=371053 Kevin Funkchanged: What|Removed |Added Component|general |Project provider: Github -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378534] GitHub Integration Limited to Getting 30 Repos By Default, But API Can Get More w/ Paging
https://bugs.kde.org/show_bug.cgi?id=378534 Kevin Funkchanged: What|Removed |Added Component|UI: general |Project provider: Github -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 331883] Whenever I try to fetch a GitHub project, KDevelop crashes.
https://bugs.kde.org/show_bug.cgi?id=331883 Kevin Funkchanged: What|Removed |Added Component|general |Project provider: Github -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 Milian Wolffchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/hea ||ptrack/e203d56632b94e6607d6 ||cdc8710f947d644fc764 Resolution|--- |FIXED --- Comment #10 from Milian Wolff --- Git commit e203d56632b94e6607d6cdc8710f947d644fc764 by Milian Wolff. Committed on 07/04/2017 at 12:24. Pushed by mwolff into branch 'master'. Disable signal handling in timer thread When the host application sets up a custom signal handler thread only that thread is supposed to handle the signals. But heaptrack spawns up the timer thread on initialization, i.e. when it first encounters a memory allocation. This usually happens before the host application has setup the signal mask. As such, our timer thread would still receive e.g. SIGTERM and then shutdown the whole application. Now, we disable signal handling in the helper thread to fix this behavior for applications that rely on it. M +24 -0src/track/libheaptrack.cpp M +3-0tests/manual/CMakeLists.txt A +110 -0tests/manual/signals.cpp [License: LGPL (v2+)] https://commits.kde.org/heaptrack/e203d56632b94e6607d6cdc8710f947d644fc764 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377070] Kmail emptied inbox, all emails deleted!!!
https://bugs.kde.org/show_bug.cgi?id=377070 --- Comment #9 from Martin Steigerwald--- William, do you really expect someone to read this after all your previous ranting? I wouldn´t. Also "something with filters" is *way* to unspecific in order to say anything about it. So if you have a reproducable bug regarding filters, feel free to report it, but please 1. with a different tone, and 2. in a *new* bug report. I do have an insanely complex filter setup and it works just fine. But there are many ways to setup filters in a way that they conflict which each other and so on, so what you see can easily just be a result of misconfigured filters (i.e. mistake made by you as an user.) Thanks, Martin (do not expect me to reply to any rants you may come up with, its not that I think Akonadi is perfect – far from it, I even agree it might be good to replace it at some time, maybe with the new Sink – but for me it basically works quite okayish meanwhile). Thank you and good luck with Claws Mail. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378530] plasmashell using more cpu when teamspeak 3 system tray is enabled on intel graphic card.
https://bugs.kde.org/show_bug.cgi?id=378530 Kai Uwe Broulikchanged: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Can you check whether there's DBus spamming going on by checking dbus-monitor. I have the feeling that Teamspeak constantly signals updates to its context menu. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 378536] Window title isn't RGB antialiased
https://bugs.kde.org/show_bug.cgi?id=378536 Kai Uwe Broulikchanged: What|Removed |Added CC||k...@privat.broulik.de Component|general |window decoration Target Milestone|1.0 |--- Product|plasmashell |Breeze Assignee|k...@davidedmundson.co.uk|hugo.pereira.da.costa@gmail ||.com --- Comment #1 from Kai Uwe Broulik --- Re-assigning to Breeze window decoration which paints the label -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370949] PDF bookmarks off by one
https://bugs.kde.org/show_bug.cgi?id=370949 Gilbert Assafchanged: What|Removed |Added CC||gas...@gmx.de --- Comment #2 from Gilbert Assaf --- I can reproduce this problem, with current Master. But I think it's a Bug in poppler. I also tested it with various other pdf readers: Okular: Bookmarks are off by one Firefox: Same Problem Evince: Same Problem Chromium: Works fine Adobe Reader: Works fine -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377614] Crash when moving larger quantities of animation frames
https://bugs.kde.org/show_bug.cgi?id=377614 --- Comment #4 from Dmitry Kazakov--- Yes, I can reproduce the problem by dropping frames into the active layer that doesn't have "show in timeline" option set and *very quickly* pressing pgdown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378536] New: Window title isn't RGB antialiased
https://bugs.kde.org/show_bug.cgi?id=378536 Bug ID: 378536 Summary: Window title isn't RGB antialiased Product: plasmashell Version: 5.9.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ene...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 104916 --> https://bugs.kde.org/attachment.cgi?id=104916=edit Window title greyscale antialiasing - screenshot zoom After switching on RGB antialiasing inside fonts settings it seems, that window title is still antialiased using greyscale method, not RGB. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377614] Crash when moving larger quantities of animation frames
https://bugs.kde.org/show_bug.cgi?id=377614 Dmitry Kazakovchanged: What|Removed |Added CC||dimul...@gmail.com --- Comment #3 from Dmitry Kazakov --- The crash seem to happen because the source or destination layers do not exist. Or, exists, bit expunged from the timeline due to some combination of "show in timeline" option -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátilchanged: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #44 from Daniel Vrátil --- The crash should be fixed in 17.04 release. http://cgit.kde.org/akonadi.git/commit/?id=da7070a7facb3c2f91c03b28c36ba5b929b89a42 Please test against the new version and reopen if you can still reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 261509] meinproc4: crash with segfault on Mac OS X
https://bugs.kde.org/show_bug.cgi?id=261509 --- Comment #23 from Luigi Toscano--- If KHelpCenter is not installed, the "foobar Handbook" link from the Help menu of Frameworks applications redirects to docs.kde.org. If KHelpCenter is installed, the issue is on KHelpCenter (and I think it's already reported), but anyway out of scope for this bug... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 377302] Baloo keeps some removed files in the index
https://bugs.kde.org/show_bug.cgi?id=377302 --- Comment #2 from Gennady Uraltsev--- Can confirm on 5.26.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378535] Valgrind reports INTERNAL ERROR in execve syscall wrapper
https://bugs.kde.org/show_bug.cgi?id=378535 --- Comment #1 from Ivo Raisr--- Created attachment 104915 --> https://bugs.kde.org/attachment.cgi?id=104915=edit proposed patch -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378535] Valgrind reports INTERNAL ERROR in execve syscall wrapper
https://bugs.kde.org/show_bug.cgi?id=378535 Ivo Raisrchanged: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org |iv...@ivosh.net CC||iv...@ivosh.net Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378535] New: Valgrind reports INTERNAL ERROR in execve syscall wrapper
https://bugs.kde.org/show_bug.cgi?id=378535 Bug ID: 378535 Summary: Valgrind reports INTERNAL ERROR in execve syscall wrapper Product: valgrind Version: 3.13 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: iv...@ivosh.net Target Milestone: --- Valgrind reports INTERNAL ERROR when a bogus address is passed to execve(argv) or execve(envp) syscall wrapper. That's because ML_(pre_argv_envp)() blindly dereferences address passed by the client program. The syscall wrapper should check at least that the first entry of argv and envp belongs to a valid client memory segment (there needs to be always at least one entry for terminating NULL). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378534] New: GitHub Integration Limited to Getting 30 Repos By Default, But API Can Get More w/ Paging
https://bugs.kde.org/show_bug.cgi?id=378534 Bug ID: 378534 Summary: GitHub Integration Limited to Getting 30 Repos By Default, But API Can Get More w/ Paging Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jason.sm...@qualityaddict.org Target Milestone: --- I found this morning I was only seeing 30 repositories in the retrieved list but I have 32 repositories on GitHub. With help from kfunk on #kdevelop learned the API was limiting to 30 by default. Found you can do ?per_page= to retrieve more repositories. https://api.github.com/users/qa/repos?per_page=100 where is your GitHub account. This is a nice-to-have, wish list item for me. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 --- Comment #9 from Milian Wolff--- heaptrack already depends on pthread (for the timer thread). I also asked a colleague and he confirmed this is safe to do. I'll push it - thanks for the report and helpful test case! -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 261509] meinproc4: crash with segfault on Mac OS X
https://bugs.kde.org/show_bug.cgi?id=261509 --- Comment #22 from RJVB--- It should be possible to perform an automatic search of the online documentation first, no? In fact, it should be possible to provide all existing handbooks online at least for projects that are part of KF5 Applications and Plasma5. Would be considerably more user-friendly! -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 --- Comment #8 from Maksim Golov--- Confirm that it works for my case. One thing to note, the proposed patch introduces a dependency on pthreads, which is probably quite safe in practice, and I'd expect CMake can probe for pthreads being available. I wouldn't be able to say if there are potential heaptrack users affected by this, though. An alternative would be to somehow allow the application to expose a hook which heaptrack will call when starting the timer thread - not sure if this is worth the trouble. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 378533] New: Kontact crash
https://bugs.kde.org/show_bug.cgi?id=378533 Bug ID: 378533 Summary: Kontact crash Product: kontact Version: 5.4.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: j.vermaak...@gmail.com Target Milestone: --- Application: kontact (5.4.3) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.9.20-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I installed Korganizer and since then Kontact crashes a few times before it opens The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3c5d44e8c0 (LWP 13422))] Thread 34 (Thread 0x7f3a93f96700 (LWP 13589)): #0 0x7f3c4e10ce49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f3c4e0c6c99 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f3c4e0c76cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7f3c4e0c78bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f3c5aa3b06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3c5a9e489a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f3c5a806a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f3c5a80b6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 33 (Thread 0x7f3b09e3b700 (LWP 13521)): #0 0x7f3c4e10ce64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f3c4e0c779a in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3c4e0c78bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3c5aa3b06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3c5a9e489a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3c5a806a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f3c5a80b6d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f3ac08ae700 (LWP 13511)): #0 0x7f3c502df756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3c54cc70d9 in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x7f3c54cc7709 in () at /usr/lib/libQt5WebEngineCore.so.5 #3 0x7f3c54cc78c0 in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7f3c54cc4442 in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f3b0a7fc700 (LWP 13505)): #0 0x7f3c502df756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b32c9b563 in () at /usr/lib/libQt5WebKit.so.5 #2 0x7f3b32fd3781 in () at /usr/lib/libQt5WebKit.so.5 #3 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f3b0affd700 (LWP 13504)): #0 0x7f3c502df756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b32c9b563 in () at /usr/lib/libQt5WebKit.so.5 #2 0x7f3b32fd3781 in () at /usr/lib/libQt5WebKit.so.5 #3 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f3b0b7fe700 (LWP 13503)): #0 0x7f3c502df756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b32c9b563 in () at /usr/lib/libQt5WebKit.so.5 #2 0x7f3b32fd3781 in () at /usr/lib/libQt5WebKit.so.5 #3 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f3b0bfff700 (LWP 13502)): #0 0x7f3c502df756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b32c9a411 in () at /usr/lib/libQt5WebKit.so.5 #2 0x7f3b32fd3781 in () at /usr/lib/libQt5WebKit.so.5 #3 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f3b19286700 (LWP 13501)): #0 0x7f3c502df756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b32fa260b in () at /usr/lib/libQt5WebKit.so.5 #2 0x7f3b32fa2649 in () at /usr/lib/libQt5WebKit.so.5 #3 0x7f3c502d92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3c59f0754f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f3b1ada8700 (LWP
[kwin] [Bug 378532] New: fast window switching (ALT+Tab) is broken for fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=378532 Bug ID: 378532 Summary: fast window switching (ALT+Tab) is broken for fullscreen windows Product: kwin Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: plusf...@gmail.com Target Milestone: --- KDE Frameworks 5.32.0 Qt 5.8.0 (built against 5.8.0) The xcb windowing system (also on Wayland) Open a few windows, now you can "fast switch" between 2 windows via ALT+Tab. That works good and many use it. Now when you open a game (Stardew Valles, Tomb Raider, RocketLeague and all other games i have in Steam) and its launched fullscreen, fast user switch will not work anymore. Start the game -> game opens ALT+Tab switches out of the game another ALT+Tab will NOT switch back to the game, but a random other window. It seems this only affects OpenGL and Vulkan windows. If i run Chromium with F11 in fullscreen an can switch just fine in and out. If I start the game in windowed-mode, fastswitch also works fine. If you need more infos - please let me know :) -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 --- Comment #7 from Milian Wolff--- Reading up a bit, I think this patch should actually quite safe to do. Can you confirm, considering you seem to have more knowledge around this idiom? If so, then I'd push it to master in the hope that it's not breaking anything else ;-) -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 378494] Debugee terminates on any signal
https://bugs.kde.org/show_bug.cgi?id=378494 --- Comment #6 from Milian Wolff--- Indeed, that work-arounds this issue: diff --git a/src/track/libheaptrack.cpp b/src/track/libheaptrack.cpp index b21b00b..6df2101 100644 --- a/src/track/libheaptrack.cpp +++ b/src/track/libheaptrack.cpp @@ -30,6 +30,8 @@ #include #include #include +#include +#include #include #include @@ -487,6 +489,14 @@ private: fprintf(stderr, "WARNING: Failed to open /proc/self/statm for reading.\n"); } timerThread = thread([&]() { +sigset_t mask; +sigfillset(); +int ret = pthread_sigmask(SIG_SETMASK, , nullptr); +if (ret < 0) { +perror("failed to block signals, disabling timer thread"); +return; +} + RecursionGuard::isActive = true; debugLog("%s", "timer thread started"); while (!stopTimerThread) { I'm simply a bit reluctant applying it, as I don't know what else it could potentially break... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378511] Numlock key not turning on under Wayland
https://bugs.kde.org/show_bug.cgi?id=378511 --- Comment #6 from Andrius Štikonas--- I can't reproduce it from either Weston or Gnome session. Only in Plasma session. Hm, I wonder if this bug is caused by the same thing as #375708. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 378531] KScreenlocker does not support custom hotkeys for layout switching
https://bugs.kde.org/show_bug.cgi?id=378531 --- Comment #2 from Mike Krutov--- Wow, that was fast. Thank you! -- You are receiving this mail because: You are watching all bug changes.