[kdevelop] [Bug 385058] A file search result becomes unreadable.
https://bugs.kde.org/show_bug.cgi?id=385058 --- Comment #4 from Markus Elfring --- (In reply to Thomas Piekarski from comment #3) > For me it looks more like an issue with the colors and themes, > than something "fix-able" in kdevelop itself. Would you like to check any more the desired display effects after double-clicks on selected entries in file search result views? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398409] KMyMoney does not prompt for password when connecting to database
https://bugs.kde.org/show_bug.cgi?id=398409 --- Comment #6 from Thomas Piekarski --- (In reply to Eleazar from comment #5) > Just downloaded the latest master code (09/10/2018 @ 22:30 MDT build > 5.0.80-90212a2b) and rebuild and deployed the code. I started it up using > the -n option, connected to my DB. After it loaded I closed KMM and opened > it again and I did not get prompted for a password. The commit #ac602f is not yet in master, can you please checkout the 5.0 branch? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385058] A file search result becomes unreadable.
https://bugs.kde.org/show_bug.cgi?id=385058 --- Comment #3 from Thomas Piekarski --- (In reply to Markus Elfring from comment #2) > (In reply to Thomas Piekarski from comment #1) > > The KDE colour scheme “Breeze” should be active together with the design > “openSUSE” in my desktop session so far. > > > Did you encounter these trouble in any other KDE application? > > I noticed a few display surprises also with other programs (as can be seen > from published clarification requests). Thanks for the additional information. For me it looks more like an issue with the colors and themes, than something "fix-able" in kdevelop itself. Are you able to set the colors in such a way that you can read the current highlighted search result? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 253657] missing some amd64 to let wine/amd64 run on valgrind/amd64
https://bugs.kde.org/show_bug.cgi?id=253657 Daniel Lehman changed: What|Removed |Added CC||dlehma...@gmail.com --- Comment #18 from Daniel Lehman --- Created attachment 114891 --> https://bugs.kde.org/attachment.cgi?id=114891=edit simple test case for wine64 pdb -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398450] okular saves as with too few permissions
https://bugs.kde.org/show_bug.cgi?id=398450 --- Comment #4 from Thomas Piekarski --- (In reply to Christoph Feck from comment #3) > It was committed to 18.04 branch, so it won't show up in 18.08 release > changelog. Deducing from date, it should be fixed since KDE Applications > 18.04.1 which comes with Okular 1.4.1. Thanks for clarifying in which version this bug was fixed - with version 1.4.1 it looks more promising for backporting :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398472] No Pen Pressure
https://bugs.kde.org/show_bug.cgi?id=398472 --- Comment #2 from mvowada --- I've also read that sometimes it helps using "the “Wacom Tablet Preference File Utility” to clear all the preferences. This should allow Krita to detect the correct settings automatically". Be aware that this will reset your tablets configuration, thus you will need to recalibrate/reconfigure it (https://docs.krita.org/en/KritaFAQ.html#how-to-fix-a-tablet-offset-on-multiple-screen-setup-on-windows). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 253657] missing some amd64 to let wine/amd64 run on valgrind/amd64
https://bugs.kde.org/show_bug.cgi?id=253657 --- Comment #17 from Daniel Lehman --- Created attachment 114890 --> https://bugs.kde.org/attachment.cgi?id=114890=edit patches for wine64 and pdbs The attached patches get wine64 with pdbs working. I'm sure additional patches will be needed, but it's a start. The attached leakage.c produces the following output on 64-bit Wine with these changes: ==689== 12,345 bytes in 1 blocks are definitely lost in loss record 70 of 71 ==689==at 0x7BC5ACCD: initialize_block (heap.c:238) ==689==by 0x7BC5ACCD: RtlAllocateHeap (???:0) ==689==by 0x140006C0A: a (leakage.c:9) ==689==by 0x140006C28: b (leakage.c:14) ==689==by 0x140006C48: c (leakage.c:19) ==689==by 0x140006D28: main (leakage.c:43) ==689== ==689== 23,456 bytes in 1 blocks are possibly lost in loss record 71 of 71 ==689==at 0x7BC5ACCD: initialize_block (heap.c:238) ==689==by 0x7BC5ACCD: RtlAllocateHeap (???:0) ==689==by 0x140006CBC: setframe (leakage.c:28) ==689==by 0x140006CE8: d (leakage.c:33) ==689==by 0x140006D08: e (leakage.c:38) ==689==by 0x140006D3C: main (leakage.c:44) leakage.c built 32-bit with pdb fails with and without my changes. But with the attached, both 32-bit and 64-bit Wine tests still run under valgrind. Tested with the following: - Visual Studio 2017 (15.8.3) (Optimizing Compiler Version 19.15.26726 for x64) - Wine 3.15 - valgrind-3.14.0.GIT (097b2076013bd6082be189ab55dbdb2eb1e572b7) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395262] Transparency/blur is corrupted on context menu of desktop files
https://bugs.kde.org/show_bug.cgi?id=395262 --- Comment #20 from mthw0 --- (In reply to Dr. Chapatin from comment #19) > Where is the fix? Bug persists on both Arch Linux (plasma 5.13.5) and neon > dev unstable under X11. AFAIK The fix landed a while ago, and works just fine. The bug only persists in VLC. Arch Linux + Plasma 5.13.5 intel GPU -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398472] No Pen Pressure
https://bugs.kde.org/show_bug.cgi?id=398472 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from mvowada --- (In reply to cademedearis from comment #0) > I am using Krita 4.1.1 with a Wacom Intuos Pro Medium updated to Windows - > Driver 6.3.30-6 on Windows 10. Pen pressure does not work, have tried > reinstalling new and old versions of Krita. I'd check with a previous version of the Wacom drivers (https://wacom.com/en-it/support/product-support/drivers) since it seems that "the 6.3.30.x drivers are known to be broken" (https://forum.kde.org/viewtopic.php?f=139=153717#p403018). (In reply to cademedearis from comment #0) Another issue is when I lift my > pen away from tablet range, the cursor only shows up and is able to click > when it is outside the Krita window Have you tried to use to the Windows 8+ Pointer Input instead of WinTab (https://docs.krita.org/en/reference_manual/preferences/tablet_settings.html#tablet-settings)? Please, let we know, thanks -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 398454] GPG signatures can be faked with HTML/CSS
https://bugs.kde.org/show_bug.cgi?id=398454 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/mes ||sagelib/a19720ae8e0aa2074fe ||4f055bc0464948bdd0d36 Version Fixed In||5.10.0 --- Comment #4 from Laurent Montel --- Git commit a19720ae8e0aa2074fe4f055bc0464948bdd0d36 by Laurent Montel. Committed on 11/09/2018 at 05:07. Pushed by mlaurent into branch 'master'. Fix Bug 398454 - GPG signatures can be faked with HTML/CSS FIXED-IN: 5.10.0 M +27 -5messageviewer/src/header/grantleeheaderformatter.cpp M +18 -2 messageviewer/src/messageviewerheaderplugins/defaultgrantleeheaderstyleplugin/theme/5.2/header.html https://commits.kde.org/messagelib/a19720ae8e0aa2074fe4f055bc0464948bdd0d36 -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 357667] ‘Previous tab’ only switches between last two used tabs
https://bugs.kde.org/show_bug.cgi?id=357667 --- Comment #7 from Adrián Chaves (Gallaecio) --- That would be great, Simon. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398409] KMyMoney does not prompt for password when connecting to database
https://bugs.kde.org/show_bug.cgi?id=398409 Eleazar changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from Eleazar --- Just downloaded the latest master code (09/10/2018 @ 22:30 MDT build 5.0.80-90212a2b) and rebuild and deployed the code. I started it up using the -n option, connected to my DB. After it loaded I closed KMM and opened it again and I did not get prompted for a password. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396264] KWin crash after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=396264 988a...@mail.ru changed: What|Removed |Added CC||988a...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398474] New: Kwin sometimes freezes, consuming 100% of one CPU core
https://bugs.kde.org/show_bug.cgi?id=398474 Bug ID: 398474 Summary: Kwin sometimes freezes, consuming 100% of one CPU core Product: kwin Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Sometimes kwin freezes, and does not respond to mouse movement, keyboard shortcuts etc. It usually happens when I am triggering the 'desktop grid' effect via a screen corner, and the animation just stops halfway. However, I cannot reporduce this consistently, and I am not sure if this is actually the trigger. If I switch to a tty during such a freeze and open htop, I find that kwin_x11 is taking 100% of a CPU core. It does not respond to SIGTERM, so I usually have to send SIGKILL and then start kwin again. I tried to capture to output of kwin during one such run (by starting kwin using something like 'nohup kwin_x11 --replace > kwin_log_20180911-0915.txt &', and it is below: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL version string: 4.5 (Core Profile) Mesa 18.1.8 OpenGL shading language version string: 4.50 Driver: Intel GPU class: Haswell OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 18.1.8 X server version: 1.20.1 Linux kernel version: 4.18.6 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_x11: ../libepoxy/src/dispatch_common.c:858: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. After the last line, there is some stuff about raising a crash handler, which I assume happens when I kill the process. I am runnning Arch Linux, and using the 'xf86-video-intel' driver. I am not sure what other information would be relevant here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398455] Plasma crashes when trying to configure desktop settings
https://bugs.kde.org/show_bug.cgi?id=398455 --- Comment #3 from Nate Graham --- It was just an observation; I didn't close the bug. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 341914] Allow Annotation Tools in Toolbar
https://bugs.kde.org/show_bug.cgi?id=341914 andresimi changed: What|Removed |Added CC||andres...@gmail.com --- Comment #4 from andresimi --- Hi, I would like to reinforce the request... The highlight process of Okular is very unfriendly: 1) you have to discover a hidden annotation bar (review bar) 2) Okular don't have a way to keep the annotation tool (pin). So if I highlight a word, I have to click it again to make another highlight. 3) If I use a lot of colors to highlight words I have to configure a lot of things in the review bar. Today, I use Foxit reader, where the annotations tools are much more accessible, but I would change to an opens source alternative as Okular if it addressed theses items. Thank you for the app. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398455] Plasma crashes when trying to configure desktop settings
https://bugs.kde.org/show_bug.cgi?id=398455 --- Comment #2 from snusmoomrick --- (In reply to Nate Graham from comment #1) > Crashing somewhere in Nouveau drivers. I see, that problem is in Nouveau driver. But in other cases (DE's and WM's) it works fine, and Xorg has no errors. Proprietary drivers don't work with my old video card and with last version of Xorg. Wayland also doesn't work properly. So, nouveau is the only working variant for me. And it's buggy only with Plasma desktop. Ok, maybe it has the meaning to ask nouevau developers about this problem. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 398473] New: powerdevil does not compile with >=ddcutil-0.8.6
https://bugs.kde.org/show_bug.cgi?id=398473 Bug ID: 398473 Summary: powerdevil does not compile with >=ddcutil-0.8.6 Product: Powerdevil Version: 5.13.5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nilat...@gmx.net Target Milestone: --- The current ddcutilbrightness.cpp implementation has been broken since the following ddcutil commit: https://github.com/rockowitz/ddcutil/commit/3276de053ec2b3771213f14f7dddba569b82e16f After fixing a minor issue in a CMakeLists file of powerdevil-5.11.2, I was able to successfully enable the brightness control using ddcutil-0.8.4. I was eagerly waiting for the CMakeLists patch to make it into powerdevil-5.13 (https://phabricator.kde.org/D8626?id=33105), but obviously it didn't. However after fixing the CMakeLists of powerdevil-5.13 locally again, I'm no longer able to compile: powerdevil-5.13.5 + >=ddcutil-0.8.6 + gcc-8.2.0 => FAIL due to ddcutil API changes powerdevil-5.13.5 + FAIL ddcutil needs https://github.com/nilathak/powerdevil/commit/74b679d773639cac34d5730cd007e9d59130d6f7 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 384813] Yakuake keyboard shortcuts not following KDE global shortcuts.
https://bugs.kde.org/show_bug.cgi?id=384813 --- Comment #2 from Sic Volo --- for anyone getting here from google - finally found the right solution - right click anywhere inside yakuake, then hover over "copy" and right click again, "configure shortcut..." will pop up, left click on it and configure the secondary shortcut to ctrl+ins -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 367634] Copying text with ctrl+ins does not work
https://bugs.kde.org/show_bug.cgi?id=367634 --- Comment #7 from Sic Volo --- for anyone getting here from google - finally found the right solution (the previous one with a global shortcut is a little too broad). The actual solution is simple - right click anywhere inside yakuake, then hover over "copy" and right click again, "configure shortcut..." will pop up, left click on it and configure the secondary shortcut to ctrl+ins Only took a year to solve, with no help from the dev. Is Yakuake dead? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395262] Transparency/blur is corrupted on context menu of desktop files
https://bugs.kde.org/show_bug.cgi?id=395262 --- Comment #19 from Dr. Chapatin --- Where is the fix? Bug persists on both Arch Linux (plasma 5.13.5) and neon dev unstable under X11. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398472] New: No Pen Pressure
https://bugs.kde.org/show_bug.cgi?id=398472 Bug ID: 398472 Summary: No Pen Pressure Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: cademedea...@gmail.com Target Milestone: --- I am using Krita 4.1.1 with a Wacom Intuos Pro Medium updated to Windows - Driver 6.3.30-6 on Windows 10. Pen pressure does not work, have tried reinstalling new and old versions of Krita. Another issue is when I lift my pen away from tablet range, the cursor only shows up and is able to click when it is outside the Krita window, then I am able to use the cursor in Krita again, which is kind of annoying. Pen pressure has worked in Firealpaca, Sai (With some issues with pen going to second monitor and not staying on one monitor whenever the canvas is drawn on), and Medibang. Tablet Tester Mouse press X=117 Y=47 B=1 Mouse move X=117 Y=46 B=1 Mouse move X=117 Y=45 B=1 Mouse move X=118 Y=45 B=1 Mouse move X=118 Y=46 B=1 Mouse move X=118 Y=47 B=1 Mouse move X=117 Y=48 B=1 Mouse move X=116 Y=50 B=1 Mouse move X=114 Y=53 B=1 Mouse move X=112 Y=58 B=1 Mouse move X=107 Y=64 B=1 Mouse move X=101 Y=72 B=1 Mouse move X=94 Y=80 B=1 Mouse move X=87 Y=89 B=1 Mouse move X=80 Y=97 B=1 Mouse move X=74 Y=104 B=1 Mouse move X=68 Y=110 B=1 Mouse move X=63 Y=115 B=1 Mouse move X=58 Y=119 B=1 Mouse move X=55 Y=122 B=1 Mouse move X=53 Y=123 B=1 Mouse move X=52 Y=123 B=1 Mouse move X=51 Y=123 B=1 Mouse move X=51 Y=122 B=1 Mouse move X=51 Y=120 B=1 Mouse move X=53 Y=115 B=1 Mouse move X=56 Y=106 B=1 Mouse move X=63 Y=93 B=1 Mouse move X=71 Y=78 B=1 Mouse move X=80 Y=64 B=1 Mouse move X=90 Y=50 B=1 Mouse move X=99 Y=38 B=1 Mouse move X=108 Y=27 B=1 Mouse move X=118 Y=17 B=1 Mouse move X=127 Y=9 B=1 Mouse move X=135 Y=3 B=1 Mouse move X=142 Y=-2 B=1 Mouse move X=148 Y=-5 B=1 Mouse move X=152 Y=-6 B=1 Mouse move X=155 Y=-6 B=1 Mouse move X=157 Y=-5 B=1 Mouse move X=158 Y=-2 B=1 Mouse move X=159 Y=3 B=1 Mouse move X=159 Y=13 B=1 Mouse move X=157 Y=28 B=1 Mouse move X=153 Y=46 B=1 Mouse move X=147 Y=66 B=1 Mouse move X=141 Y=86 B=1 Mouse move X=134 Y=106 B=1 Mouse move X=127 Y=126 B=1 Mouse move X=120 Y=145 B=1 Mouse move X=114 Y=164 B=1 Mouse move X=108 Y=181 B=1 Mouse move X=103 Y=196 B=1 Mouse move X=100 Y=209 B=1 Mouse move X=97 Y=218 B=1 Mouse move X=96 Y=223 B=1 Mouse move X=95 Y=226 B=1 Mouse move X=95 Y=227 B=1 Mouse move X=96 Y=227 B=1 Mouse move X=97 Y=225 B=1 Mouse move X=100 Y=221 B=1 Mouse move X=106 Y=213 B=1 Mouse move X=115 Y=199 B=1 Mouse move X=125 Y=182 B=1 Mouse move X=135 Y=162 B=1 Mouse move X=144 Y=143 B=1 Mouse move X=153 Y=125 B=1 Mouse move X=162 Y=108 B=1 Mouse move X=170 Y=93 B=1 Mouse move X=177 Y=80 B=1 Mouse move X=182 Y=71 B=1 Mouse move X=187 Y=64 B=1 Mouse move X=189 Y=60 B=1 Mouse move X=191 Y=58 B=1 Mouse move X=191 Y=57 B=1 Mouse move X=191 Y=58 B=1 Mouse move X=190 Y=61 B=1 Mouse move X=188 Y=67 B=1 Mouse move X=184 Y=77 B=1 Mouse move X=177 Y=93 B=1 Mouse move X=170 Y=111 B=1 Mouse move X=162 Y=131 B=1 Mouse move X=155 Y=149 B=1 Mouse move X=149 Y=165 B=1 Mouse move X=143 Y=180 B=1 Mouse move X=137 Y=193 B=1 Mouse move X=133 Y=205 B=1 Mouse move X=129 Y=215 B=1 Mouse move X=127 Y=223 B=1 Mouse move X=125 Y=228 B=1 Mouse move X=124 Y=232 B=1 Mouse move X=124 Y=233 B=1 Mouse move X=124 Y=234 B=1 Mouse move X=125 Y=233 B=1 Mouse move X=128 Y=231 B=1 Mouse move X=131 Y=227 B=1 Mouse move X=137 Y=221 B=1 Mouse move X=143 Y=212 B=1 Mouse move X=150 Y=203 B=1 Mouse move X=157 Y=193 B=1 Mouse move X=163 Y=184 B=1 Mouse move X=168 Y=176 B=1 Mouse move X=172 Y=169 B=1 Mouse move X=176 Y=164 B=1 Mouse move X=179 Y=159 B=1 Mouse move X=182 Y=156 B=1 Mouse move X=184 Y=154 B=1 Mouse move X=185 Y=153 B=1 Mouse move X=186 Y=152 B=1 Mouse move X=187 Y=151 B=1 Mouse move X=188 Y=151 B=1 Mouse move X=189 Y=151 B=1 Mouse move X=189 Y=152 B=1 Mouse move X=188 Y=154 B=1 Mouse move X=188 Y=157 B=1 Mouse move X=187 Y=160 B=1 Mouse move X=186 Y=163 B=1 Mouse move X=184 Y=166 B=1 Mouse move X=183 Y=170 B=1 Mouse move X=182 Y=173 B=1 Mouse move X=182 Y=175 B=1 Mouse move X=181 Y=177 B=1 Mouse move X=181 Y=179 B=1 Mouse move X=181 Y=180 B=1 Mouse move X=181 Y=181 B=1 Mouse move X=181 Y=182 B=1 Mouse move X=182 Y=182 B=1 Mouse move X=184 Y=182 B=1 Mouse move X=185 Y=182 B=1 Mouse move X=187 Y=182 B=1 Mouse move X=189 Y=181 B=1 Mouse move X=191 Y=180 B=1 Mouse move X=194 Y=180 B=1 Mouse move X=196 Y=179 B=1 Mouse move X=198 Y=178 B=1 Mouse move X=200 Y=178 B=1 Mouse move X=202 Y=177 B=1 Mouse move X=204 Y=176 B=1 Mouse move X=206 Y=176 B=1 Mouse move X=208 Y=176 B=1 Mouse move X=209 Y=175 B=1 Mouse move X=211 Y=175 B=1 Mouse move X=213 Y=175 B=1 Mouse move X=215 Y=175 B=1 Mouse move X=216 Y=175 B=1 Mouse move X=218 Y=175 B=1 Mouse move X=219 Y=175 B=1 Mouse move X=220 Y=175 B=1
[okular] [Bug 392682] Okular ignores umask on save file as
https://bugs.kde.org/show_bug.cgi?id=392682 Christoph Feck changed: What|Removed |Added CC||s.oosth...@xs4all.nl --- Comment #3 from Christoph Feck --- *** Bug 398450 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398450] okular saves as with too few permissions
https://bugs.kde.org/show_bug.cgi?id=398450 Christoph Feck changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #3 from Christoph Feck --- It was committed to 18.04 branch, so it won't show up in 18.08 release changelog. Deducing from date, it should be fixed since KDE Applications 18.04.1 which comes with Okular 1.4.1. *** This bug has been marked as a duplicate of bug 392682 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #2 from Stas Sergeev --- Created attachment 114889 --> https://bugs.kde.org/attachment.cgi?id=114889=edit 2-process test-case Hi, thanks for your reply. Here is the test-case that does the same thing but with 2 processes scheme. Same valgrind error. While the first test-case represents my real program more, I really see no difference. As for the difficulty of fixing this - yes, I perfectly understand it. While I can think of some ugly work-arounds (like, for example, checking if the values have changed, and consider them initialized in that case), nothing good can probably be done. How about downgrading the error to warning if it comes from the shared mem? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398220] Invisible windows appear randomly on wayland
https://bugs.kde.org/show_bug.cgi?id=398220 --- Comment #3 from Alexandre Pereira --- thanx David for the reply. Sorry for the lame video, but i got a invisible window, a konsole window, and recorded a video: https://youtu.be/-c5my2wp0tg the window is a konsole window, other konsole windows display fine. The problematic window is selected in showDebugConsole. Is there a way to save the info of showDebugConsole into a file ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398471] New: [Wayland] Random crash when widget explorer is closed
https://bugs.kde.org/show_bug.cgi?id=398471 Bug ID: 398471 Summary: [Wayland] Random crash when widget explorer is closed Product: plasmashell Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x7fc2b2b92bee in QtWaylandClient::QWaylandXdgSurfaceV6::setPopup(QtWaylandClient::QWaylandWindow*, QtWaylandClient::QWaylandInputDevice*, int, bool) () from /usr/lib/libQt5WaylandClient.so.5 (gdb) thread apply all bt Thread 21 (Thread 0x7fc1c7bb1700 (LWP 26781)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc2bccf4a1c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc2baed9005 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc2ba861a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc2babbda43 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fc1f7fff700 (LWP 26780)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc2bccf4a1c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc2baed9005 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc2ba861a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc2babbda43 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fc204a7f700 (LWP 26753)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc2bccf4a1c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc2baed9005 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc2ba861a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc2babbda43 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fc1e5791700 (LWP 26718)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc2bccf4a1c in () at /usr/lib/libQt5Quick.so.5 --Type for more, q to quit, c to continue without paging-- #4 0x7fc2baed9005 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc2ba861a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc2babbda43 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fc1f5a6c700 (LWP 26715)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc2bccf4a1c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc2baed9005 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc2ba861a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc2babbda43 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fc1f77fe700 (LWP 26710)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc2bccf4a1c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc2baed9005 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc2ba861a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc2babbda43 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fc1e77fe700 (LWP 26631)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc2bccf4a1c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc2baed9005 in () at /usr/lib/libQt5Core.so.5 #5 0x7fc2ba861a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc2babbda43 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fc1e7fff700 (LWP 26610)): #0 0x7fc2ba867afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 --Type for more, q to quit, c to continue without paging-- #1 0x7fc2baed97bc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc2bccf47ad in () at /usr/lib/libQt5Quick.so.5 #3
[kdevelop] [Bug 398470] New: KDevelop: problemreporter caused crash on exit
https://bugs.kde.org/show_bug.cgi?id=398470 Bug ID: 398470 Summary: KDevelop: problemreporter caused crash on exit Product: kdevelop Version: unspecified Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- Application: kdevelop (5.2.80 (v5.2.4-635-gcbb2c3aa89)) (Compiled from sources) Qt Version: 5.9.6 Frameworks Version: 5.47.0 Operating System: Darwin 13.4.0 x86_64 Distribution (Platform): MacPorts Packages -- Information about the crash: - What I was doing when the application crashed: I quit KDevelop after working on a project for about a day, and got the crash below. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault: 11 (lldb) process attach --pid 57850 Process 57850 stopped Executable module set to "/Applications/MacPorts/KF5/kdevelop.app/Contents/MacOS/kdevelop.bin". Architecture set to: x86_64-apple-macosx. (lldb) set term-width 200 (lldb) thread info thread #1: tid = 0x58833d, 0x7fff86579e20 libsystem_kernel.dylib`__wait4 + 8, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP (lldb) bt all * thread #1: tid = 0x58833d, 0x7fff86579e20 libsystem_kernel.dylib`__wait4 + 8, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP * frame #0: 0x7fff86579e20 libsystem_kernel.dylib`__wait4 + 8 frame #1: 0x000109fddd1e libKF5Crash.5.dylib`KCrash::startProcess(int, char const**, bool) [inlined] startProcessInternal(argc=, directly=) + 125 at kcrash.cpp:649 frame #2: 0x000109fddca1 libKF5Crash.5.dylib`KCrash::startProcess(argc=, argv=, waitAndExit=) + 17 at kcrash.cpp:631 frame #3: 0x000109fddae5 libKF5Crash.5.dylib`KCrash::defaultCrashHandler(sig=11) + 1061 at kcrash.cpp:528 frame #4: 0x7fff893415aa libsystem_platform.dylib`_sigtramp + 26 frame #5: 0x00010aee8471 libKF5TextEditor.5.dylib`Kate::TextBlock::removeRange(Kate::TextRange*) [inlined] QHashNode::same_key(this=0x, h0=, key0=0x7fa6a4eb5f60) const + 5 at qhash.h:158 frame #6: 0x00010aee846c libKF5TextEditor.5.dylib`Kate::TextBlock::removeRange(Kate::TextRange*) [inlined] QHash::findNode(this=, akey=0x7fa6a4eb5f60, h=) const + 19 at qhash.h:908 frame #7: 0x00010aee8459 libKF5TextEditor.5.dylib`Kate::TextBlock::removeRange(Kate::TextRange*) [inlined] QHash::findNode(this=, akey=0x7fa6a4eb5f60) const + 23 at qhash.h:927 frame #8: 0x00010aee8442 libKF5TextEditor.5.dylib`Kate::TextBlock::removeRange(Kate::TextRange*) [inlined] QHash::find(this=, akey=0x7fa6a4eb5f60) + 99 at qhash.h:891 frame #9: 0x00010aee83df libKF5TextEditor.5.dylib`Kate::TextBlock::removeRange(this=0x7fa6a1a2cb30, range=0x7fa6a4eb5f60) + 47 at katetextblock.cpp:700 frame #10: 0x00010aeeb8db libKF5TextEditor.5.dylib`Kate::TextRange::fixLookup(this=0x7fa6a4eb5f60, oldStartLine=, oldEndLine=, startLine=-1, endLine=-1) + 251 at katetextrange.cpp:248 frame #11: 0x00010aeeb73c libKF5TextEditor.5.dylib`Kate::TextRange::~TextRange(this=0x7fa6a4eb5f60) + 92 at katetextrange.cpp:55 frame #12: 0x00010aeeb93e libKF5TextEditor.5.dylib`Kate::TextRange::~TextRange() [inlined] Kate::TextRange::~TextRange(this=0x7fa6a4eb5f60) + 14 at katetextrange.cpp:48 frame #13: 0x00010aeeb939 libKF5TextEditor.5.dylib`Kate::TextRange::~TextRange(this=0x7fa6a4eb5f60) + 9 at katetextrange.cpp:48 frame #14: 0x0001228f8d41 kdevproblemreporter.so`ProblemHighlighter::~ProblemHighlighter() [inlined] void qDeleteAll::const_iterator>(begin=const_iterator at rbx) + 29 at qalgorithms.h:320 frame #15: 0x0001228f8d24 kdevproblemreporter.so`ProblemHighlighter::~ProblemHighlighter() [inlined] void qDeleteAll >(QList const&) + 16 at qalgorithms.h:328 frame #16: 0x0001228f8d14 kdevproblemreporter.so`ProblemHighlighter::~ProblemHighlighter(this=0x7fa6a142d5a0) + 68 at problemhighlighter.cpp:93 frame #17: 0x0001228f8e5e kdevproblemreporter.so`ProblemHighlighter::~ProblemHighlighter() [inlined] ProblemHighlighter::~ProblemHighlighter(this=0x7fa6a142d5a0) + 14 at problemhighlighter.cpp:89 frame #18: 0x0001228f8e59 kdevproblemreporter.so`ProblemHighlighter::~ProblemHighlighter(this=0x7fa6a142d5a0) + 9 at problemhighlighter.cpp:89 frame #19: 0x0001228f3132 kdevproblemreporter.so`ProblemReporterPlugin::documentClosed(this=0x7fa69cb4b2a0, doc=) + 98 at problemreporterplugin.cpp:128 frame #20: 0x00010e0198d8 QtCore`QMetaObject::activate(QObject*, int, int, void**) [inlined] QtPrivate::QSlotObjectBase::call(this=, r=, a=) + 1992 at qobject_impl.h:101 frame #21: 0x00010e0198bc QtCore`QMetaObject::activate(sender=0x7fa69cf62310, signalOffset=,
[systemsettings] [Bug 398469] New: Bad font rendering when display scaling factor is 1.2
https://bugs.kde.org/show_bug.cgi?id=398469 Bug ID: 398469 Summary: Bad font rendering when display scaling factor is 1.2 Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_plymouth Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 114888 --> https://bugs.kde.org/attachment.cgi?id=114888=edit screenshot Set display scaling factor to 1.2 in system settings > display and monitor. Restart plasma session and open plymouth kcm. My screenshot taken on neon dev unstable shows the result. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398455] Plasma crashes when trying to configure desktop settings
https://bugs.kde.org/show_bug.cgi?id=398455 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 CC||n...@kde.org, ||plasma-b...@kde.org Component|general |general Product|kde |plasmashell Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk Version|unspecified |5.13.5 --- Comment #1 from Nate Graham --- Crashing somewhere in Nouveau drivers. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398450] okular saves as with too few permissions
https://bugs.kde.org/show_bug.cgi?id=398450 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED CC||n...@kde.org Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[calligragemini] [Bug 398468] New: Calligra Gemini crashes when opening any document
https://bugs.kde.org/show_bug.cgi?id=398468 Bug ID: 398468 Summary: Calligra Gemini crashes when opening any document Product: calligragemini Version: 3.1.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: rherb...@sympatico.ca Target Milestone: --- Application: calligragemini (3.1.0) (Compiled from sources) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.19.0-rc3 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: Open Gemini. Choose any method to open a document. The app crashes. The crash can be reproduced every time. -- Backtrace: Application: Calligra Gemini (calligragemini), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f69a42b22c0 (LWP 26940))] Thread 11 (Thread 0x7f6975563700 (LWP 26952)): #0 0x7f69a7ca14f7 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #1 0x7f69a7ca1c9f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f69a7ca1e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f69ae085a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f69ae02d31a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f69ade5c13a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f69aff937b2 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f69ade66928 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f69ad277637 in start_thread () at /lib64/libpthread.so.0 #9 0x7f69ad5abe8f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f6975d64700 (LWP 26951)): #0 0x7f69ad27dc4e in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69ade675f0 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69ade5e5ee in () at /usr/lib64/libQt5Core.so.5 #3 0x7f69ade66928 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f69ad277637 in start_thread () at /lib64/libpthread.so.0 #5 0x7f69ad5abe8f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f6976565700 (LWP 26950)): #0 0x7f69ad27dc4e in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69ade675f0 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69ade5e5ee in () at /usr/lib64/libQt5Core.so.5 #3 0x7f69ade66928 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f69ad277637 in start_thread () at /lib64/libpthread.so.0 #5 0x7f69ad5abe8f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f6976d66700 (LWP 26949)): #0 0x7f69ad27dc4e in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69ade675f0 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69ade5e5ee in () at /usr/lib64/libQt5Core.so.5 #3 0x7f69ade66928 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f69ad277637 in start_thread () at /lib64/libpthread.so.0 #5 0x7f69ad5abe8f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f6977567700 (LWP 26948)): #0 0x7f69ad27d783 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f697c71a86b in () at /usr/lib64/xorg/modules/dri/r600_dri.so #2 0x7f697c71a627 in () at /usr/lib64/xorg/modules/dri/r600_dri.so #3 0x7f69ad277637 in start_thread () at /lib64/libpthread.so.0 #4 0x7f69ad5abe8f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f6977ea9700 (LWP 26947)): #0 0x7f69ad27d783 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f697c71a86b in () at /usr/lib64/xorg/modules/dri/r600_dri.so #2 0x7f697c71a627 in () at /usr/lib64/xorg/modules/dri/r600_dri.so #3 0x7f69ad277637 in start_thread () at /lib64/libpthread.so.0 #4 0x7f69ad5abe8f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f698eb85700 (LWP 26944)): #0 0x7f69ad59fb79 in poll () at /lib64/libc.so.6 #1 0x7f69a7ca1d1e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f69a7ca1e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f69ae085a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f69ae02d31a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f69ade5c13a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f69ade66928 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f69ad277637 in start_thread () at /lib64/libpthread.so.0 #8 0x7f69ad5abe8f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f699adaf700 (LWP 26943)): #0 0x7f69a7ce54e3 in g_private_get () at /usr/lib64/libglib-2.0.so.0 #1 0x7f69a7cc8830 in g_thread_self ()
[KEXI] [Bug 393094] Restore support for date/time constants in KEXI SQL
https://bugs.kde.org/show_bug.cgi?id=393094 --- Comment #1 from Jarosław Staniek --- Design page: https://community.kde.org/Kexi/Plugins/Queries/SQL_Constants -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #1 from Philippe Waroquiers --- At my work, we are also using shared memory (shared between several processes). In the same process, the shared memory is mapped only once. In that setup, a piece of shared memory can be initialised by one process, but read by another process. So, for this, we are using a valgrind client request to declare the shared memory as initialised after attach. In your test case, the same memory is mapped twice (at different addresses) by the same process. This is an unusual usage pattern of shared memory. Is that representative of your real application ? If yes, then I think it will be quite unlikely this can be improved in valgrind: even if valgrind could maybe track the system calls to detect that the same piece of memory is in fact mapped twice, handling this in memcheck will very probably imply a specific data structure to be looked at for each access, and that will bring a very high cost on programs not using this unusual shared memory usage. So, in summary, it would be better to map the memory only once and/or declare it initialised after map. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #26 from Nick Stefanov --- Created attachment 114887 --> https://bugs.kde.org/attachment.cgi?id=114887=edit solid-hardware5_details_after_mounting_after reboot_CDEmu_Virt_2e_CD_2fDVD_ROM_1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #25 from Nick Stefanov --- Created attachment 114886 --> https://bugs.kde.org/attachment.cgi?id=114886=edit solid-hardware5_details_after_mounting_after reboot_CDEmu_Virt_2e_CD_2fDVD_ROM -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #24 from Nick Stefanov --- Created attachment 114885 --> https://bugs.kde.org/attachment.cgi?id=114885=edit solid-hardware5_details_before_mounting_after reboot -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #23 from Nick Stefanov --- I rebooted and the "solid-hardware5 list | grep CDEmu" command now gives only one possible device: udi = '/org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM' When I mount an image after the reboot, the command gives again two possible devices: udi = '/org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM_1' udi = '/org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM Now I'll attach logs after the reboot. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373839] Continuously face thumbnails flicker/update
https://bugs.kde.org/show_bug.cgi?id=373839 --- Comment #14 from Maik Qualmann --- That's right, the thumbnails are "preloaded" by the Paint Event. The thumbnail task will send a signal to the image model that the thumbnail is available and it will be drawn. By you over and over again. The advantage of this thumbnail preload only with the fast scrolling, the thumbnails appear faster. The problem is the Paint Event, which is constantly triggered by you. So again my question: which desktop? which display manager and extension? Graphics card and driver? Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397675] cannot connect to kmysql database because of prepended slash
https://bugs.kde.org/show_bug.cgi?id=397675 Thomas Baumgart changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.0.2 Latest Commit||https://cgit.kde.org/kmymon ||ey.git/commit/?id=c5a3c44b2 ||a341d6efc1a55bc55dcff9ff5a5 ||94c8 --- Comment #3 from Thomas Baumgart --- I cannot duplicate this problem with current 5.0 branch which is the same code base as master wrt to db code. Maybe it complained about a missing password. That was another problem I just fixed in the 5.0 branch. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #22 from Nick Stefanov --- Created attachment 114884 --> https://bugs.kde.org/attachment.cgi?id=114884=edit solid-hardware5_details_after_mounting -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 394384] MySQL connection error with dbname "KMyMoney"
https://bugs.kde.org/show_bug.cgi?id=394384 Thomas Baumgart changed: What|Removed |Added Version Fixed In||5.0.2 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/ac602ffdb0297706f1f39 ||602856bbe20225e906c --- Comment #5 from Thomas Baumgart --- Git commit ac602ffdb0297706f1f39602856bbe20225e906c by Thomas Baumgart. Committed on 10/09/2018 at 19:47. Pushed by tbaumgart into branch '5.0'. Ask for password when connecting to database Related: bug 398409 FIXED-IN: 5.0.2 M +46 -20 kmymoney/plugins/sql/sqlstorage.cpp M +3-0kmymoney/plugins/sql/sqlstorage.h https://commits.kde.org/kmymoney/ac602ffdb0297706f1f39602856bbe20225e906c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398467] Video Edit Plugin
https://bugs.kde.org/show_bug.cgi?id=398467 --- Comment #2 from Dan Mittelstadt --- Thanks Maik! (In reply to Maik Qualmann from comment #1) > In the video preview you can rotate the video image with the right mouse > button over the view clockwise. In digiKam-6.0.0-beta1 the orientation flag > is recognized if it is present in the video and then automatically rotated > (manual is still possible). > > Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362360] When switching virtual desktops with the Desktop Cube Animation effect, the Blur and Background Contrast effect cause visual artifacts in the upper right quarter of the screen
https://bugs.kde.org/show_bug.cgi?id=362360 Vlad Zagorodniy changed: What|Removed |Added Summary|When switching virtual |When switching virtual |desktop, glitch appears |desktops with the Desktop ||Cube Animation effect, the ||Blur and Background ||Contrast effect cause ||visual artifacts in the ||upper right quarter of the ||screen -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #21 from Nick Stefanov --- Created attachment 114883 --> https://bugs.kde.org/attachment.cgi?id=114883=edit solid-hardware5_details_before_mounting -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398409] KMyMoney does not prompt for password when connecting to database
https://bugs.kde.org/show_bug.cgi?id=398409 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.0.2 Latest Commit||https://commits.kde.org/kmy ||money/ac602ffdb0297706f1f39 ||602856bbe20225e906c Status|UNCONFIRMED |RESOLVED --- Comment #4 from Thomas Baumgart --- Git commit ac602ffdb0297706f1f39602856bbe20225e906c by Thomas Baumgart. Committed on 10/09/2018 at 19:47. Pushed by tbaumgart into branch '5.0'. Ask for password when connecting to database Related: bug 394384 FIXED-IN: 5.0.2 M +46 -20 kmymoney/plugins/sql/sqlstorage.cpp M +3-0kmymoney/plugins/sql/sqlstorage.h https://commits.kde.org/kmymoney/ac602ffdb0297706f1f39602856bbe20225e906c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362360] When switching virtual desktop, glitch appears
https://bugs.kde.org/show_bug.cgi?id=362360 Vlad Zagorodniy changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #13 from Vlad Zagorodniy --- *** Bug 398438 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398438] Desktop cube corruption on misaligned multiple monitors
https://bugs.kde.org/show_bug.cgi?id=398438 Vlad Zagorodniy changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #6 from Vlad Zagorodniy --- Thank you for the info. *** This bug has been marked as a duplicate of bug 362360 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #20 from Nick Stefanov --- The "solid-hardware5 list | grep CDEmu" command gives only two possible devices: udi = '/org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM_1' udi = '/org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM' I already gave you logs for udi = '/org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM. Do you need the logs for udi = '/org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM_1? Actually this problem is present everywhere. Can't you get the needed info from your system? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398467] Video Edit Plugin
https://bugs.kde.org/show_bug.cgi?id=398467 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- In the video preview you can rotate the video image with the right mouse button over the view clockwise. In digiKam-6.0.0-beta1 the orientation flag is recognized if it is present in the video and then automatically rotated (manual is still possible). Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398458] Places tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=398458 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Sure that Places no longer exist? The screenshot does not give that. Because Places would come after Pets... Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #19 from Stefan Brüns --- The logs still do not provide the required information, as you used the wrong UDI. CDEmu seems to create new virtual drives when mounting images. Make sure you use the UDI matching the drive you are currently using. check "solid-hardware5 list | grep CDEmu" for possible UDIs. Speaking name - e.g. "solid-hardware5_details_after_mounting.txt" -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397649] Unified Folder
https://bugs.kde.org/show_bug.cgi?id=397649 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/kma ||il/52eee4a475ad2e27c732d988 ||701f1ef6dd128754 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Daniel Vrátil --- Git commit 52eee4a475ad2e27c732d988701f1ef6dd128754 by Daniel Vrátil. Committed on 10/09/2018 at 18:42. Pushed by dvratil into branch 'master'. Merge branch 'dev/unified-mailboxes' The Unified Mailboxes Agent (which in reality is a Resource in order to be able to own Collections) creates Inbox, Sent and Drafts virtual Collections and links all Items from real special Collections into them. It listens for changes in the source collections and updates the virtual Collections accordingly. Uses can also customize the default unified mailboxes and create their own. The agent can be enabled or disalbed from KMail's Plugins settings like other agents. By default the agent is off, however, if KMail detects that user has more than one account set up it will ask the user if they want to enable the feature. User is only ever asked once, the purpose is to make the feature easier to discover without bothering users with only one email account. CHANGELOG: Unified mailboxes in KMail Test Plan: Reviewers: mlaurent Reviewed By: mlaurent Subscribers: lueck, ngraham, mlaurent, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D15065 M +1-1kmail.categories M +1-1src/configuredialog/configureaccountpage.cpp M +2-0 src/configuredialog/configureplugins/configurepluginslistwidget.cpp M +13 -0src/kmkernel.cpp M +2-1src/kmkernel.h M +53 -0src/kmmainwidget.cpp M +1-0src/kmmainwidget.h M +4-1src/settings/kmail.kcfg.cmake https://commits.kde.org/kmail/52eee4a475ad2e27c732d988701f1ef6dd128754 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 Jakob Sinclair changed: What|Removed |Added Version|17.04.1 |18.08.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 --- Comment #4 from Jakob Sinclair --- Version: 18.08 Actually got a backtrace here: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". To enable execution of this file add add-auto-load-safe-path /usr/lib64/libstdc++.so.6.0.25-gdb.py line to your configuration file "/home/jakob/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/jakob/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" [Current thread is 1 (Thread 0x7f2fc3225040 (LWP 5253))] Thread 38 (Thread 0x7f2f1b7f8700 (LWP 5312)): #0 0x7f2fca4020fb in futex_wait_cancelable (private=, expected=0, futex_word=0x2f48954) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f2fca4020fb in __pthread_cond_wait_common (abstime=0x0, mutex=0x2f48900, cond=0x2f48928) at pthread_cond_wait.c:502 #2 0x7f2fca4020fb in __pthread_cond_wait (cond=0x2f48928, mutex=0x2f48900) at pthread_cond_wait.c:655 #3 0x7f2fb80317cd in () at /usr/lib64/mlt/libmltsdl2.so #4 0x7f2fca3fc091 in start_thread (arg=) at pthread_create.c:463 #5 0x7f2fcd1d3eff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 37 (Thread 0x7f2f1bff9700 (LWP 5311)): #0 0x7f2fcd198d97 in getpid () at ../sysdeps/unix/syscall-template.S:60 #1 0x7f2fc3644cbe in pa_detect_fork () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7f2fc472102e in pa_stream_writable_size () at /usr/lib/libpulse.so.0 #3 0x7f2fa8c65875 in () at /usr/lib/libSDL2-2.0.so.0 #4 0x7f2fa8b7bebe in () at /usr/lib/libSDL2-2.0.so.0 #5 0x7f2fa8be617c in () at /usr/lib/libSDL2-2.0.so.0 #6 0x7f2fa8c848a9 in () at /usr/lib/libSDL2-2.0.so.0 #7 0x7f2fca3fc091 in start_thread (arg=) at pthread_create.c:463 #8 0x7f2fcd1d3eff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 36 (Thread 0x7f2f1c7fa700 (LWP 5310)): #0 0x7f2fca4020fb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f2f40024a80) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f2fca4020fb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f2f40024ae8, cond=0x7f2f40024a58) at pthread_cond_wait.c:502 #2 0x7f2fca4020fb in __pthread_cond_wait (cond=0x7f2f40024a58, mutex=0x7f2f40024ae8) at pthread_cond_wait.c:655 #3 0x7f2f9f0ba2c6 in () at /usr/lib/libavcodec.so.57 #4 0x7f2fca3fc091 in start_thread (arg=) at pthread_create.c:463 #5 0x7f2fcd1d3eff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 35 (Thread 0x7f2f1cffb700 (LWP 5309)): #0 0x7f2fca4020fb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f2f400248d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f2fca4020fb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f2f40024938, cond=0x7f2f400248a8) at pthread_cond_wait.c:502 #2 0x7f2fca4020fb in __pthread_cond_wait (cond=0x7f2f400248a8, mutex=0x7f2f40024938) at pthread_cond_wait.c:655 #3 0x7f2f9f0ba2c6 in () at /usr/lib/libavcodec.so.57 #4 0x7f2fca3fc091 in start_thread (arg=) at pthread_create.c:463 #5 0x7f2fcd1d3eff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7f2f1d7fc700 (LWP 5308)): #0 0x7f2fca4020fb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f2f40024724) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f2fca4020fb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f2f40024788, cond=0x7f2f400246f8) at pthread_cond_wait.c:502 #2 0x7f2fca4020fb in __pthread_cond_wait (cond=0x7f2f400246f8, mutex=0x7f2f40024788) at pthread_cond_wait.c:655 #3 0x7f2f9f0ba2c6 in () at /usr/lib/libavcodec.so.57 #4 0x7f2fca3fc091 in start_thread (arg=) at pthread_create.c:463 #5 0x7f2fcd1d3eff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7f2f1dffd700 (LWP 5307)): #0 0x7f2fca4020fb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f2f40024574) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f2fca4020fb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f2f400245d8, cond=0x7f2f40024548) at pthread_cond_wait.c:502 #2 0x7f2fca4020fb in __pthread_cond_wait (cond=0x7f2f40024548, mutex=0x7f2f400245d8) at pthread_cond_wait.c:655 #3 0x7f2f9f0ba2c6 in () at /usr/lib/libavcodec.so.57 #4 0x7f2fca3fc091 in start_thread (arg=) at pthread_create.c:463 #5 0x7f2fcd1d3eff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7f2f19f71700 (LWP 5306)): #0 0x7f2fca4020fb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f2f400243c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f2fca4020fb in
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 Jakob Sinclair changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||sinclair.ja...@mailbox.org Ever confirmed|0 |1 --- Comment #3 from Jakob Sinclair --- Can reproduce this issue when GPU is enabled. Every time I add Fade from Black to a video or image it instantly crashes. I don't have debug packages on Solus so I can't provide a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #18 from Nick Stefanov --- I see, sorry :) Here it is with no mounted image: https://pastebin.com/D6jfZaqm And with mounted image: https://pastebin.com/bnctGbM6 sudo losetup -a gives no output no matter if image is mounted or not. What do you mean with "speaking name"? English is not my native language and for me is difficult to understand, sorry. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #17 from Stefan Brüns --- You need to run "solid-hardware5 details ", e.g. "solid-hardware details /org/freedesktop/UDisks2/drives/CDEmu_Virt_2e_CD_2fDVD_ROM" Run it after mounting and after unmounting, and, *please*, give your logs a speaking name. Also run "sudo losetup -a" after mounting and unmounting. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398467] New: Video Edit Plugin
https://bugs.kde.org/show_bug.cgi?id=398467 Bug ID: 398467 Summary: Video Edit Plugin Product: digikam Version: 5.9.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Preview-Video Assignee: digikam-bugs-n...@kde.org Reporter: dmittelst...@gmail.com Target Milestone: --- Would like to use digiKam for video management as well. - For preview purposes it would be very helpful to be able to rotate a video. - Just a couple video editing tools like ability to trim would also be very helpful. - Ability to import / export from youtube. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398061] Missing auto-detect button in digiKam
https://bugs.kde.org/show_bug.cgi?id=398061 --- Comment #6 from caulier.gil...@gmail.com --- Hi Marcus, With MXE, you don't need a Windows OS to compile libgphoto2/gphoto2. All is done under Linux, from scratch. Here i cross compile digiKam + KF5 + qt5 + all required extra dependencies. This take 2 hours on my host computer, but at end, i can run the setup.exe to install whole digiKam under Windows >= 7. MXE rock. Some libgphoto2 dependencies are already available, as libusb1 or gettext. Only libexif is not yet in MXE, but I'm sure that it can be compiled without difficulty as it support already MinGW. If you help me to support MXE with libgphoto2, i will compile the digiKam windows installer with Gphoto2 support. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398466] New: No delay before first image possible
https://bugs.kde.org/show_bug.cgi?id=398466 Bug ID: 398466 Summary: No delay before first image possible Product: kstars Version: 2.9.8 Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: wreis...@gmx.de Target Milestone: --- The capture module has the option to set a delay. But this is only between two consecutive captures in the same sequence job. I would like to have it *before* a capture takes place and not afterwards. For example, if you want to shoot one frame per filter every 1 minute directed by the scheduler, this is not possible. Instead, the capture module shoots as fast as possible. There is another thing not possible: you cannot delay a capture after filter change, because exactly the first one after the change is shot immediately. Or is there another I did not discover yet? -Wolfgang -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 398465] New: Tray of optical device closes itself when a disc is ejected if auto-mounting is unchecked in "Removable devices" kcm and the disc was inside device while plasma se
https://bugs.kde.org/show_bug.cgi?id=398465 Bug ID: 398465 Summary: Tray of optical device closes itself when a disc is ejected if auto-mounting is unchecked in "Removable devices" kcm and the disc was inside device while plasma session was started Product: frameworks-solid Version: 5.50.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: lu...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- right click device notifier applet in the system tray click "Configure removable devices" uncheck "Enable automatic mounting of removable media" option, click "Ok" button insert a disc into the optical device restart computer start plasma session eject the disc by pressing device physical button Result: device tray opens and closes itself. Tray does not close itself if no disc is inside device while tray is ejected. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398450] okular saves as with too few permissions
https://bugs.kde.org/show_bug.cgi?id=398450 --- Comment #2 from Simon Oosthoek --- Thanks, that confirms this is a bug in the versions up to 1.5. I hope it can be backported to a bugfix in ubuntu stable... I'll see if I can make a bugreport on launchpad for it. I'm wondering when this bug was introduced to okular... Cheers /Simon -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398450] okular saves as with too few permissions
https://bugs.kde.org/show_bug.cgi?id=398450 Thomas Piekarski changed: What|Removed |Added CC||t.piekar...@deloquencia.de --- Comment #1 from Thomas Piekarski --- Hello, this problem with umask is already fixed, please see the issue at phabricator: https://phabricator.kde.org/D12049 - with a very literal title ;) It was merged at April 23rd and should be available with Okular 1.5 (though its not mentioned in the release log: https://www.kde.org/announcements/fulllog_applications.php?version=18.08.0#okular, so I checked out the latest commit from master and I can not reproduce. The file permissions are set according to the umask.). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #33 from Eike Hein --- Here's a mitigation approach to this problem for review: https://phabricator.kde.org/D15410 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #16 from Nick Stefanov --- Thank you very much :) Here is the output without mounted image: https://pastebin.com/TQxwzUpD And with mounted ISO: https://pastebin.com/sUNYGNWB -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398464] New: Discover crashes when I try to launch it
https://bugs.kde.org/show_bug.cgi?id=398464 Bug ID: 398464 Summary: Discover crashes when I try to launch it Product: Discover Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: j.l.vanderz...@gmail.com Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-33-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: Doing web-development. As a result, I was editing some code with VSCode, browsing the internet Firefox 62 and, Chromium was open for testing a webpage being developed. Desktop clients for Slack and Telegram were also running in the background, as well as Dropbox and Redshift-GTK. Nothing else (that was directly visible to me as a user). (Running KDE Neon, so I guess that makes it an Ubuntu derivative?) The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcf9b927900 (LWP 12343))] Thread 8 (Thread 0x7fcf57d96700 (LWP 12352)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fcf975edfa4 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:92 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:221 #4 futexSemaphoreTryAcquire (timeout=-1, n=1, u=...) at thread/qsemaphore.cpp:264 #5 QSemaphore::acquire (this=this@entry=0x7fcf57d94100, n=n@entry=1) at thread/qsemaphore.cpp:328 #6 0x7fcf977e91b6 in QMetaObject::activate (sender=0x2dc4610, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3739 #7 0x7fcf94abf378 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7fcf94b60d3d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7fcf977e8f79 in QMetaObject::activate (sender=0x7fcf50002860, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3771 #10 0x7fcf94ab4c02 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7fcf94ab54cd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7fcf977e8f79 in QMetaObject::activate (sender=0x7fcf50002f00, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3771 #13 0x7fcf94b5ad77 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #14 0x7fcf94b570db in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7fcf94b57ac6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7fcf94b3a8d1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7fcf977e8f79 in QMetaObject::activate (sender=0x7fcf500042d0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3771 #18 0x7fcf94b05973 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #19 0x7fcf94b05a2c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #20 0x7fcf94b19371 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #21 0x7fcf98e1639c in QApplicationPrivate::notify_helper (this=, receiver=0x7fcf50005730, e=0x7fcf57d95a90) at kernel/qapplication.cpp:3727 #22 0x7fcf98e1dab0 in QApplication::notify (this=0x7ffeba9e17d0, receiver=0x7fcf50005730, e=0x7fcf57d95a90) at kernel/qapplication.cpp:3486 #23 0x7fcf977bc228 in QCoreApplication::notifyInternal2 (receiver=0x7fcf50005730, event=event@entry=0x7fcf57d95a90) at kernel/qcoreapplication.cpp:1048 #24 0x7fcf97813d1d in QCoreApplication::sendEvent (event=0x7fcf57d95a90, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #25 socketNotifierSourceDispatch (source=0x7fcf500013a0) at kernel/qeventdispatcher_glib.cpp:106 #26 0x7fcf91757197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fcf917573f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fcf9175749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fcf978130bb in QEventDispatcherGlib::processEvents (this=0x7fcf58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #30 0x7fcf977ba5ba in QEventLoop::exec (this=this@entry=0x7fcf57d95cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #31 0x7fcf975ef5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #32 0x7fcf975fa727 in QThreadPrivate::start (arg=0x2dc1ce0) at thread/qthread_unix.cpp:367 #33 0x7fcf9368c6ba in start_thread (arg=0x7fcf57d96700) at pthread_create.c:333 #34 0x7fcf96bf441d in
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #15 from Kai Uwe Broulik --- Check solid-hardware5 list, it lists all your devices, most like one of those that start with /org/freedesktop/UDisks2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398401] Missing Calibre icon on Wayland
https://bugs.kde.org/show_bug.cgi?id=398401 --- Comment #5 from Rainer Finke --- It is the Calibre 3.31.0 package of Arch Linux. There is a Calibre icon in the kicker menu, but not on the task bar or in the top left corner of the window decoration on Plasma Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398463] New: Discover crashes when opened
https://bugs.kde.org/show_bug.cgi?id=398463 Bug ID: 398463 Summary: Discover crashes when opened Product: Discover Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: wdd5...@gmail.com Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-33-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: Try to open Discover from krunner or menu or update icon. It crashes everytime since last update. Did update using konsole and pkcon, discover still crashes. KDE Developers Edition The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8bcdba9900 (LWP 2265))] Thread 7 (Thread 0x7f8b93fff700 (LWP 2274)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f8bc986655f in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8bc985be8a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f8bc9865727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8bc59016ba in start_thread (arg=0x7f8b93fff700) at pthread_create.c:333 #5 0x7f8bc8e6941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f8b98fe3700 (LWP 2273)): #0 0x7f8bc8e5d74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8bc39ce38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8bc39ce49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8bc9a7e0bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8bc9a255ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8bc985a5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8bc9865727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8bc59016ba in start_thread (arg=0x7f8b98fe3700) at pthread_create.c:333 #8 0x7f8bc8e6941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f8b9a51c700 (LWP 2272)): #0 0x7f8bc8e5d74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8bc39ce38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8bc39ce49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8bc9a7e0bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8bc9a255ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8bc985a5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8bc9865727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8bc59016ba in start_thread (arg=0x7f8b9a51c700) at pthread_create.c:333 #8 0x7f8bc8e6941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f8ba31e4700 (LWP 2271)): #0 0x7f8bc98566e0 in QMutex::unlock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f8bc9a7dfe1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8bc39cd91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8bc39ce2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8bc39ce49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8bc9a7e0bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8bc9a255ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8bc985a5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8bcccaaf86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f8bc9865727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f8bc59016ba in start_thread (arg=0x7f8ba31e4700) at pthread_create.c:333 #11 0x7f8bc8e6941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f8bb0f68700 (LWP 2268)): #0 0x7f8bc8e5927d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8bc286a073 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.130 #2 0x7f8bc3a116f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8bc39cde74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4
[latte-dock] [Bug 398456] latte-dock takes a lot % of CPU
https://bugs.kde.org/show_bug.cgi?id=398456 --- Comment #3 from Michail Vourlakos --- (In reply to Tom Kijas from comment #2) > Michal Vourlakos: Thanks, how can I do it? This would be possible only if you are a programmer and you can investigate the code in order to find a better way to improve parabolic effect consumption -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #14 from Nick Stefanov --- I don't know how to get udi solid-hardware5 details. Can you help with this? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #13 from Nick Stefanov --- Umounting mounted disk image (e.g. .iso file), as the title says. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387961] Device action disappears from device notifier when its description is edited
https://bugs.kde.org/show_bug.cgi?id=387961 Dr. Chapatin changed: What|Removed |Added Version|5.11.4 |5.13.5 --- Comment #2 from Dr. Chapatin --- Bug persists in plasma 5.13.5, Arch Linux. I have just edited "Open with VLC player" and such option disappeared from device notifier. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #12 from Stefan Brüns --- (In reply to Nick Stefanov from comment #10) > Hello, > now in Solid 5.50 the problem is solved partially. When mount CD/DVD and > then unmount it, the Dolphin icon in the side bar disappears but the device > manager icon stays in the system tray and there's no way to remove it. Please be more specific. Physical CD/DVD drive or iso image? Please provide the output of "solid-hardware5 details" for the relevant UDI, both mounted and unmounted. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348
--- Comment #11 from Dr. Chapatin ---
I can confirm the problem described in comment 10 on Arch Linux + frameworks
5.50 when I mount the ISO image using cdemu.
When I use Gnome disks ("disk image mounter" in dolphin context menu) to mount
the ISO instead cdemu a new entry appears in the side bar of Dolphin under
"Devices" instead under "Removable devices" and no related entry appears in
device notifier applet.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeplasma-addons] [Bug 398403] Application Dashboard: Add possibility to remove grouping by ABC
https://bugs.kde.org/show_bug.cgi?id=398403 Scott Harvey changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398462] IPTC from Lifgthroom
https://bugs.kde.org/show_bug.cgi?id=398462 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Can you share some image samples, including XMP sidecar, to test here ? Please use cloud storage and paste the link here... Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 398403] Application Dashboard: Add possibility to remove grouping by ABC
https://bugs.kde.org/show_bug.cgi?id=398403 --- Comment #3 from Scott Harvey --- I get it now. Looks just like the App Drawer on my Android tablet. Let me pull in one of our user interface gurus and get his input. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398462] New: IPTC from Lifgthroom
https://bugs.kde.org/show_bug.cgi?id=398462 Bug ID: 398462 Summary: IPTC from Lifgthroom Product: digikam Version: 5.9.0 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Iptc Assignee: digikam-bugs-n...@kde.org Reporter: vou...@hotmail.com Target Milestone: --- Hello, I want to recover the iptc data, from a Ligthroom database to DIGIKAM, but fields such as the title are not included ... Do you have an idea. In the other direction, it's all good. Thank you -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398461] New: Discover crashes on launch
https://bugs.kde.org/show_bug.cgi?id=398461 Bug ID: 398461 Summary: Discover crashes on launch Product: Discover Version: 5.13.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: blacki...@gmail.com Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-33-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: Freshly booted desktop. First application that was launched is Discover and results in the crash. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3214becc80 (LWP 2224))] Thread 16 (Thread 0x7f31a7fff700 (LWP 2244)): #0 0x7f320a6d9faa in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f320a6da4c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f320a6da54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f32109b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3210a4edea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3210879b8a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3210884aab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f320c8756db in start_thread (arg=0x7f31a7fff700) at pthread_create.c:463 #8 0x7f321017788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f31b6b8c700 (LWP 2242)): #0 0x7f321016abf9 in __GI___poll (fds=0x7f31ac003600, nfds=1, timeout=9649) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f320a6da439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f320a6da54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f32109b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3210a4edea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3210879b8a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3210884aab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f320c8756db in start_thread (arg=0x7f31b6b8c700) at pthread_create.c:463 #8 0x7f321017788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f31b738d700 (LWP 2241)): #0 0x7f320a71fcf4 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f320a6d9930 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f320a6da36b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f320a6da7d2 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f31bf685e76 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7f320a701e05 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f320c8756db in start_thread (arg=0x7f31b738d700) at pthread_create.c:463 #7 0x7f321017788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f31b7b8e700 (LWP 2240)): #0 0x7f321016abf9 in __GI___poll (fds=0x558f51aed210, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f320a6da439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f320a6da54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f320a6da591 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f320a701e05 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f320c8756db in start_thread (arg=0x7f31b7b8e700) at pthread_create.c:463 #6 0x7f321017788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f31ddffb700 (LWP 2238)): #0 0x7ffe6569b979 in ?? () #1 0x7ffe6569bc30 in clock_gettime () #2 0x7f3210186ea6 in __GI___clock_gettime (clock_id=1, tp=0x7f31ddffaaa0) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f3210aaa3a1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3210aa8bd9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3210aa91b5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3210aaa7fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f320a6d9998 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f320a6da36b in ?? () from
[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off
https://bugs.kde.org/show_bug.cgi?id=389585 --- Comment #42 from Valeriy Malov --- Workaround for QTBUG-3459 https://phabricator.kde.org/D15406 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398324] Dophin has ambiguous shortcuts
https://bugs.kde.org/show_bug.cgi?id=398324 Jaime Torres changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dol ||phin/9991eb0f5eaf38aa7f0c61 ||206937d4cd013e24c8 Resolution|--- |FIXED --- Comment #2 from Jaime Torres --- Git commit 9991eb0f5eaf38aa7f0c61206937d4cd013e24c8 by Jaime Torres Amate. Committed on 10/09/2018 at 14:47. Pushed by jtamate into branch 'Applications/18.08'. Don't assign twice the same key to the action New Tab Summary: QKeySequence::AddTab = Qt::CTRL + Qt::Key_T. Leaving only the first avoids the warning window "There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T)" Test Plan: su - test unset KDE_FULL_SESSION dolphin After: No more the warning window. Reviewers: #dolphin, elvisangelaccio Reviewed By: #dolphin, elvisangelaccio Subscribers: elvisangelaccio, kfm-devel Tags: #dolphin Differential Revision: https://phabricator.kde.org/D15371 M +1-1src/dolphinmainwindow.cpp https://commits.kde.org/dolphin/9991eb0f5eaf38aa7f0c61206937d4cd013e24c8 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397675] cannot connect to kmysql database because of prepended slash
https://bugs.kde.org/show_bug.cgi?id=397675 --- Comment #2 from adoII --- Sorry, took me some time to compile Master. The problem is still the same, just a slash too much -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #293 from undecidable --- ok, have now moved multiple machines and VMs to Xubuntu 18.04. In fact is not that painful and works well. I have created a HowTo to help others who want to efficiently make the transition without wasting time on dead ends. The key issues that need to be addressed in moving: a. Xfce apps are mostly too basic. b. Configuration is more difficult but you waste less time wrestling with stuff you don't want. Four key points: 1. You can take many Kde apps to Xubuntu 2. Some kde apps can be replaced by gtk apps that are as good or better 3. Some kde apps can be replaced by desktop independent apps that are better or much better 4. Xfce is quite configurable, but it takes longer, but you waste less time on stuff you don't want thread is here: https://ubuntuforums.org/showthread.php?t=2400715 Hope this helps others. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 398400] Get Involved page available
https://bugs.kde.org/show_bug.cgi?id=398400 Neofytos Kolokotronis changed: What|Removed |Added CC||neofyt...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388885] Pointer does not unfreeze after closing an app that locks it
https://bugs.kde.org/show_bug.cgi?id=35 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #8 from Mayeul Cantan --- *** Bug 398421 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398421] Wayland: pointer locking not released after application closed
https://bugs.kde.org/show_bug.cgi?id=398421 Mayeul Cantan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mayeul Cantan --- (In reply to Alexander Mentyu from comment #1) > Related closed bugs https://bugs.kde.org/show_bug.cgi?id=395815 > https://bugs.kde.org/show_bug.cgi?id=35 > > How did you launched Final DOOM in Linux? - says invalid platform for me and > no install/play button I played it (tried to) trough SteamPlay, though you need to enable it for every game in your library. Steam settings -> steamplay -> Enable for all titles. Try not to spend too much time playing around with this ;-) I put a screenshot of the setting there some time ago: https://askubuntu.com/a/1067783/483325 Note that it isn't specific to that game (I tested this one because I needed something light), I remember seeing something similar after playing VV, which was also grabbing the mouse for some reason. The issue here is really to release the pointer after a game quit, if it didn't do it itself. This indeed seems like a duplicate of Bug 35, which I didn't see while searching. Looks like the fix will only land in the next plasma release (fix landed in git the 26th of june, 5.13 was released on the 12th). Thanks for pointing this out. *** This bug has been marked as a duplicate of bug 35 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 398460] New: Screen hotplug not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=398460 Bug ID: 398460 Summary: Screen hotplug not working under Wayland Product: KScreen Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Not sure this is the right place. I use a docking station with my computer (dell lattitude 5580, dell wd15). Intel graphics, Mesa 18.2.8 (Arch). The docking station is connected over USB C, DP alternate mode, and everything works fine under X. Under Wayland, though, the screens are not detected when I plug the docking station in. Everything else works fine: keyboard, mouse, network, charging, audio, USB. The extra screens remain blank, there is no OSD to pick the layout, and the screens don't appear in the KCM, only the laptop's. Moreover, when logging out, there might be a problem with SDDM or kwin (dmesg says kwin_wayland[31085]: segfault at 556790bdc740 ip 556790bdc740 sp 7ffeca4c4798 error 15) during shutdown, as the three screens are blank, and I can't switch to a VT (even with Sysrq+R). I need to REISUB my way out of this (S and U are logged to the screen in text mode, though). -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 398459] New: Crash caused by color custimization
https://bugs.kde.org/show_bug.cgi?id=398459 Bug ID: 398459 Summary: Crash caused by color custimization Product: korganizer Version: 5.9.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kde...@posteo.de Target Milestone: --- Application: korganizer (5.9.0) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.17.15-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: In KOrganizer (standalone), I changed the color of TODO incidents that are due today, via [translated from German:] Settings -> Configure Korganizer -> Colors and Fonts. A click on Apply crashed the application. I reproduced it like this two more times, without doing anything else between starting KOrganizer and setting the color. After each crash, the color that I last chose before the crash for due TODOs, so at least the new setting was saved. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6d73197c0 (LWP 5418))] Thread 7 (Thread 0x7fa69d675700 (LWP 5922)): #0 0x7fa6caac87bd in futex_wait_cancelable (private=, expected=0, futex_word=0x7fa6c3e2cfb8 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fa6c3e2cf68 , cond=0x7fa6c3e2cf90 ) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fa6c3e2cf90 , mutex=0x7fa6c3e2cf68 ) at pthread_cond_wait.c:655 #3 0x7fa6c3b38434 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7fa6c3e1eec0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7fa6c3b38479 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7fa6caac18ea in start_thread (arg=0x7fa69d675700) at pthread_create.c:465 #6 0x7fa6d2bcc61f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fa69ff50700 (LWP 5439)): #0 0x7fa6caac87bd in futex_wait_cancelable (private=, expected=0, futex_word=0x55abbd4ee3c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55abbd4ee370, cond=0x55abbd4ee398) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55abbd4ee398, mutex=0x55abbd4ee370) at pthread_cond_wait.c:655 #3 0x7fa6a05e69cb in cnd_wait (mtx=0x55abbd4ee370, cond=0x55abbd4ee398) at /var/tmp/portage/media-libs/mesa-18.1.6/work/mesa-18.1.6/include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55abbd97d060) at /var/tmp/portage/media-libs/mesa-18.1.6/work/mesa-18.1.6/src/util/u_queue.c:255 #5 0x7fa6a05e66f7 in impl_thrd_routine (p=) at /var/tmp/portage/media-libs/mesa-18.1.6/work/mesa-18.1.6/include/c11/threads_posix.h:87 #6 0x7fa6caac18ea in start_thread (arg=0x7fa69ff50700) at pthread_create.c:465 #7 0x7fa6d2bcc61f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fa6b0ad1700 (LWP 5429)): #0 0x7fa6c8ca9909 in g_mutex_lock (mutex=mutex@entry=0x7fa6a8000bf0) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gthread-posix.c:1336 #1 0x7fa6c8c64bb8 in g_main_context_iteration (context=0x7fa6a8000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4032 #2 0x7fa6d373752b in QEventDispatcherGlib::processEvents (this=0x7fa6a8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7fa6d36e353a in QEventLoop::exec (this=this@entry=0x7fa6b0ad0de0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #4 0x7fa6d3546c4a in QThread::exec (this=) at thread/qthread.cpp:525 #5 0x7fa6d355069f in QThreadPrivate::start (arg=0x55abbd460be0) at thread/qthread_unix.cpp:367 #6 0x7fa6caac18ea in start_thread (arg=0x7fa6b0ad1700) at pthread_create.c:465 #7 0x7fa6d2bcc61f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fa6b12d2700 (LWP 5424)): #0 0x7fa6d2bbc34a in __GI___libc_read (fd=, buf=buf@entry=0x7fa6b12d1bc0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fa6c8ca85c0 in read (__nbytes=16, __buf=0x7fa6b12d1bc0, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7fa6ac0039a0) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gwakeup.c:210 #3 0x7fa6c8c6459b in g_main_context_check (context=context@entry=0x7fa6a4000bf0, max_priority=2147483647, fds=fds@entry=0x7fa6a406f880, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3750 #4
[kate] [Bug 398395] Kate: No separator between the main part of the window and Search pane
https://bugs.kde.org/show_bug.cgi?id=398395 --- Comment #4 from Hugo Pereira Da Costa --- (In reply to Hugo Pereira Da Costa from comment #2) > Style in the screenshot is not breeze. > There is no splitter/separator there. > It is true that even if there were one, it would be invisible in breeze, but > at least the spacing would be larger and the mouse cursor would change when > hovering the splitter. > > Reassigning to kate. > this is a kate bug. ok sorry. Ignore the comment. In fact there is a splitter ... (blush) it turns out it is invisible in both fusion and breeze. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398395] Kate: No separator between the main part of the window and Search pane
https://bugs.kde.org/show_bug.cgi?id=398395 --- Comment #3 from Christoph Feck --- There actually are some tiny dots in the splitter. The reason the default rendering for splitters does not show any frames or lines is that they are designed to be used between two (framed) views. It would help if there was an upstream way to style splitters that are used between (non-framed) plain widgets. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398395] Kate: No separator between the main part of the window and Search pane
https://bugs.kde.org/show_bug.cgi?id=398395 Hugo Pereira Da Costa changed: What|Removed |Added Component|QStyle |application Product|Breeze |kate Assignee|unassigned-b...@kde.org |kwrite-bugs-n...@kde.org CC||hugo.pereira.da.costa@gmail ||.com --- Comment #2 from Hugo Pereira Da Costa --- Style in the screenshot is not breeze. There is no splitter/separator there. It is true that even if there were one, it would be invisible in breeze, but at least the spacing would be larger and the mouse cursor would change when hovering the splitter. Reassigning to kate. this is a kate bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #3 from Mayeul Cantan --- It looks like some symbols are missing, though. I'm unsure of the library. Would that be part of Qt or the frameworks? Would it be useful at all to produce another backtrace with those debug symbols? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 Nate Graham changed: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #2 from Mayeul Cantan --- Created attachment 114882 --> https://bugs.kde.org/attachment.cgi?id=114882=edit Backtrace of the crash Here is a backtrace obtained manually from gdb after recompiling with debug symbols. Dr Konqui somehow was unable to generate the backtrace, and asked me about debug symbols for /usr/bin/plasmashell, although those weren't stripped. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398458] Places tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=398458 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Probably the database file become corrupted while the crash. Under Windows, playing with metadata is problematic with the low level Exiv2 library. In 6.0.0, we introduce a guard, especially for Windows and C++ exception. I recommend to rebuild your database with the current Windows 6.0.0-beta1 installer available here : https://files.kde.org/digikam/ Take a care : make a database backup has 6.0.0 introduce new tables and break the backward compatibility with 5.9.0 Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396047] Discover crashed when searching for app via krunner
https://bugs.kde.org/show_bug.cgi?id=396047 --- Comment #2 from k...@o.librepush.net --- Created attachment 114881 --> https://bugs.kde.org/attachment.cgi?id=114881=edit New crash information added by DrKonqi plasma-discover (5.13.4) using Qt 5.11.1 - What I was doing when the application crashed: Trying to 'Get Mumble...' from krunner, though also happens with any application to-be-installed that way. KDE neon -- Backtrace (Reduced): #8 0x7f628e3cb1dc in qobject_cast (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:504 #9 QQmlDelegateModelItem::dataForObject (object=object@entry=0x13b7170) at types/qqmldelegatemodel.cpp:1987 #10 0x7f628e3d2317 in QQmlDelegateModelPrivate::release (this=0x10089a0, object=0x13b7170) at types/qqmldelegatemodel.cpp:543 #11 0x7f628e3d239d in QQmlDelegateModel::release (this=, item=) at types/qqmldelegatemodel.cpp:567 #12 0x7f628e3c6379 in QQmlInstantiatorPrivate::clear (this=this@entry=0x106cc20) at types/qqmlinstantiator.cpp:83 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396047] Discover crashed when searching for app via krunner
https://bugs.kde.org/show_bug.cgi?id=396047 k...@o.librepush.net changed: What|Removed |Added CC||k...@o.librepush.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398141] Dropping an Icon from Screen1 onto Screen2 opens the copy/cut contextmenu when Screen2 uses "desktop:/"
https://bugs.kde.org/show_bug.cgi?id=398141 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
