[plasmashell] [Bug 371858] Occasional wrong desktop at startup
https://bugs.kde.org/show_bug.cgi?id=371858 --- Comment #29 from it...@inwind.it --- I can confirm that the laptop screen (LVDS1) is disabled. I can also tell you that I've only got a single activity; there used to be 2 (I deleted one a while ago in hopes of fixing the issue), but there have never been 4 as far as I can remember, since I've never created any new activity. Not sure what the mess in appletsrc was caused by. It might be due to the fact that I've gone through all the Plasma upgrades since 5.1; I remember clearing my plasma configuration once or twice upon upgrade because of compatibility issues, but definitely not for every major upgrade. I'll wait until the modification you pointed to is released and see if it works. Still no reoccurrence of the problem so far -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374621] New: Can't click anywhere on plasma desktop
https://bugs.kde.org/show_bug.cgi?id=374621 Bug ID: 374621 Summary: Can't click anywhere on plasma desktop Product: plasmashell Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zionnimc...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Hi All! So I've got a stumper of a problem. I posted on reddit here: https://www.reddit.com/r/kde/comments/5m1d36/cant_click_anywhere_newly_installed_plasma/, but after a re-install the issue still persisted, I figured it was time to report a bug. I can't seem to click anywhere on the KDE plasma window. The little stack of pancakes in the top left corner reacts when I hover over it, but nothing happens when I click. Nothing happens on-hover in the toolbar. It's a brand-new installation of Arch Linux. I can use lxqt with openbox fine, and can even use lxqt with kwin and it works fine. For input I'm using a mouse, not a trackpad. I can actually interact with KDE fine using the keyboard, for example Alt+F2 to open an application, tab and arrow keys to move around. Specs: Arch Linux 64-bit with the latest updates. Nvidia GTX 1070 with nvidia and nvidia-libgl packages installed. KDE 5.8.5 running on X11. 128 GB Btrfs ssd with ntfs-3g hard drive Two identical 1080p monitors and one HTC Vive. Intel i7-4770 (non-k) Dell XPS 8700 Motherboard, bios etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374606] Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using XRender.
https://bugs.kde.org/show_bug.cgi?id=374606 --- Comment #5 from prince.re...@gmail.com --- Why? Anyway it happens also with Guvcview. I want to add that I am using nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374596] inconsistent RDTSCP support on x86_64
https://bugs.kde.org/show_bug.cgi?id=374596 --- Comment #7 from Tom Hughes--- I'm not saying it isn't a bug, just explaining what I think is causing it. What I do know is it's not likely to be easy to fix, but it probably needs Julian to comment in more detail about whether it might be fixable and whether there is any way to word around it. I would guess that putting the RDTSCP in a separate function from the check might work, so long as the compiler doesn't optimise them back together... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374571] Created starter runs wrong command
https://bugs.kde.org/show_bug.cgi?id=374571 --- Comment #3 from Eike Hein--- It works fine for me, but note that you can't use xprop. xprop -s uses XChangeProperty, which can't set the WM_CLASS property because it doesn't support the stupid special format history cooked up for WM_CLASS (two consecutive null-terminated strings in a string prop for the two parts that make it up). I recommend using xdotool, which uses XClassHint and can set the required struct format. E.g. I turned my Firefox into Konversation with: xdotool set_window --class konversation 0x4e00010 xdotool set_window --classname konversation 0x4e00010 When you then use the context menu to add a launcher, and make sure Firefox is later using this WM_CLASS again, things fall into place. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374191] Unusable context menu entries in tags and people view
https://bugs.kde.org/show_bug.cgi?id=374191 Wolfgang Scheffnerchanged: What|Removed |Added CC||wscheffn...@gmail.com --- Comment #24 from Wolfgang Scheffner --- (In reply to Mario Frank from comment #22) > ... > > I would implement the context menu item Find Duplicates for face tags to > lead to the selection of normal tags. Introducing a face similarity search > is far more complex and could be added to the wishlist. I agree that this > should be included in the handbook. > > ... > > Cheers, > Mario I understood Gilles in the way that he just want to make clear in the handbook that if one chooses "Find Similar..." from a face tag icon in People View digiKam will compare the whole image, not just the face. And about the wishlist: what is the point for a similarity search on faces? What would be the difference to face recognition? I'm not very keen on explaining that to the users. And by the way: face recognition is still not very satisfying to me. I don't even really know how to test it because I don't understand how I can see the result of a scan. Insofar I would hat to complicate matters, at least right now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368912] Apps menu and its tooltip must use the same icon when user sets a customized menu icon
https://bugs.kde.org/show_bug.cgi?id=368912 --- Comment #5 from Eike Hein--- Too late for 5.9 imho, remind me for 5.10 and we can try. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 --- Comment #13 from Tsu Jan--- OK, I may be wrong but I couldn't find any problem in kio. Of course, someone knowledgeable about kio would know better. I tested with Kvantum and found that ensurePolished() (only at Style::styleHint()) is enough for all menus to have translucency and/or rounded corners (will make a commit after some tests). I think QtCurve can do the same, i.e. it can use ensurePolished() instead of addAlphaChannel() for menus -- although, as I mentioned above, most menus wouldn't need it. In other words, addAlphaChannel() should be used only for window translucency. All this trouble is because of https://bugreports.qt.io/browse/QTBUG-34064 P.S. This question isn't answered yet: why does the creation of a window handle for KFileDialog's menu cause a freeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374620] New: plasma crash related to NoMachine client
https://bugs.kde.org/show_bug.cgi?id=374620 Bug ID: 374620 Summary: plasma crash related to NoMachine client Product: plasmashell Version: 5.8.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bryg...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.9.0-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: clicked "Disconnect" on NoMachine client. At that moment 5 xterms were open on remote machine. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fab1b10f8c0 (LWP 2792))] Thread 17 (Thread 0x7faa0b5fe700 (LWP 16791)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fab14eaf37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab18dd32a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fab18dd3b9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fab14eae4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fab13fb4454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fab147bb37f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7faa0a3fd700 (LWP 16573)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fab14eaf37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab18dd32a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fab18dd3b9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fab14eae4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fab13fb4454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fab147bb37f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7faa0bfff700 (LWP 8975)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fab14eaf37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab18dd32a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fab18dd3b9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fab14eae4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fab13fb4454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fab147bb37f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7faa10b1e700 (LWP 6558)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fab14eaf37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab18dd32a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fab18dd3b9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fab14eae4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fab13fb4454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fab147bb37f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7faa29fdd700 (LWP 5893)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fab14eaf37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab18dd32a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fab18dd3b9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fab14eae4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fab13fb4454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fab147bb37f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7faa297dc700 (LWP 3139)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fab14eaf37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab18dd32a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fab18dd3b9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fab14eae4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fab13fb4454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fab147bb37f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7faa2a9de700 (LWP 3137)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fab14eaf37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab18dd32a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fab18dd3b9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fab14eae4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fab13fb4454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fab147bb37f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7faa37dff700 (LWP 3136)): #0 0x7fab13fba10f in pthread_cond_wait@@GLIBC_2.3.2 () at
[digikam] [Bug 320666] Add search of similar images outside digiKam collections [patch]
https://bugs.kde.org/show_bug.cgi?id=320666 --- Comment #19 from Wolfgang Scheffner--- (In reply to Mario Frank from comment #18) > Created attachment 103203 [details] > Patch for triggering duplicates search for multiple tags with context menu > and introducing the similarity value as column in table view.. > > Already made some tests. But more testers are better. I'd volunteer to test but I'm working with the AppImage version right now. I guess there is no easy way to apply the patch to that? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374596] inconsistent RDTSCP support on x86_64
https://bugs.kde.org/show_bug.cgi?id=374596 --- Comment #6 from bugzi...@dcopp.net --- (In reply to Tom Hughes from comment #4) > Ah sorry I misunderstood your original report... > > You're saying that valgrind aborts on the instruction even though you don't > try and execute it. My guess is that it's happening because that will be > reported at translation time and valgrind translates instructions in blocks > so it may translate an instruction that never gets executed. This is contrary to how the processor works. A program can have potentially any number of regions in the code segment that do not contain valid opcodes and are never executed (despite routinely making their way into the processor's prefetch/decode queue.) An illegal instruction exception only arises from an actual attempted execution. But let's suppose your guess about valgrind's behavior is correct. How would one rewrite this test program to ensure that the inclusion (but not execution) of the RDTSCP opcode would not provoke this problem under valgrind? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 374619] Activating window through krunner does not work with multiple activities and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=374619 --- Comment #2 from Shitikanth--- Another observation: this problem only happens when "Remember the current virtual desktop for each activity" option is selected in the System Settings > Desktop Behaviour > Activities > Switching. Looks like this setting is overriding the virtual desktop change that would have happened otherwise. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374596] inconsistent RDTSCP support on x86_64
https://bugs.kde.org/show_bug.cgi?id=374596 --- Comment #5 from bugzi...@dcopp.net --- (In reply to Tom Hughes from comment #3) > Sure, but is the program compiled as 64 bit or 32 bit? It's using 32 bit > register names in the assembly but that might be normal for RDTSCP which is > why I asked how you were compiling it. 64 bit platform and tools. The register names are only specifying "clobbers" to the assembler template. The 'e' prefix for CPUID is appropriate (CPUID clobbers ecx). The 'r' prefix on a register name indicates 64 bit. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 374619] Activating window through krunner does not work with multiple activities and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=374619 --- Comment #1 from Shitikanth--- I just noticed that the same problem happens when I try to use "wmctrl -a Firefox" instead of krunner. So, this is likely not a bug in krunner but in the window manager (Kwin). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 374619] Activating window through krunner does not work with multiple activities and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=374619 Shitikanthchanged: What|Removed |Added Summary|Activating window through |Activating window through |krunner does not work |krunner does not work with ||multiple activities and ||virtual desktops -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 374619] New: Activating window through krunner does not work
https://bugs.kde.org/show_bug.cgi?id=374619 Bug ID: 374619 Summary: Activating window through krunner does not work Product: krunner Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: windows Assignee: k...@privat.broulik.de Reporter: golu3...@gmail.com Target Milestone: --- Steps to reproduce: 1. Open at least two activities and at least two virtual desktops. 2. Open any application, say Firefox. 3. Switch to a different activity *and* a different virtual desktop. (Things work fine if the window is either in the same activity or the same virtual desktop) 4. Search for "firefox" in krunner and select the result in "Windows" category. Expected behaviour: The window should become visible and get focus. What happens: Focus switches to the correct activity, but not the correct virtual desktop. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374508] Dolphin overwrites Hidden icons toolbar button icon
https://bugs.kde.org/show_bug.cgi?id=374508 --- Comment #2 from jacob.bec...@uni-konstanz.de --- I see. It does have the "eye" icon in the breeze icon theme , but not in other themes. So Oxygen and the other are missing a symbol for this funktion. But on the other hand. If i manually set the symbol to something other than default (the eye) the issue remains. All other symbols than the default are overwritten at first click. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374618] New: KWin crash while closing Firefox
https://bugs.kde.org/show_bug.cgi?id=374618 Bug ID: 374618 Summary: KWin crash while closing Firefox Product: kwin Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: sid1...@btinternet.com Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Closing Firefox 50.1.0 (with 6 open tabs) openSUSE Leap 42.2 Kernel 4.4.36-8-default-x86_64 KDE Plasma 5.8.3 KDE Framework 5.26.0 Qt 5.6.1 There was a lot of random flashing of screen graphics with open windows breaking up. I ahve had similar problems before but those resulted in the KWin Greeter crashing and not restarting. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94d5e29940 (LWP 2289))] Thread 6 (Thread 0x7f94b37fe700 (LWP 15329)): #0 0x7f94d5587b03 in select () at /lib64/libc.so.6 #1 0x7f94d2c5a849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f94d2c5c0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f94d2c5c527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f94d2c0bfdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f94d2a46f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f94cd6389b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f94d2a4b9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f94d5850734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f94d558ed3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f94a30aa700 (LWP 2419)): #0 0x7f94d58550af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f94d1be193b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f94d1be1969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f94d5850734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f94d558ed3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f94b2d5f700 (LWP 2410)): #0 0x7f94d5587b03 in select () at /lib64/libc.so.6 #1 0x7f94d2c5a849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f94d2c5c0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f94d2c5c527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f94d2c0bfdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f94d2a46f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f94cd6389b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f94d2a4b9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f94d5850734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f94d558ed3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f94b3fff700 (LWP 2373)): #0 0x7f94d2a443f0 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f94d2c5c4cd in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f94d2c0bfdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f94d2a46f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f94cc8191d5 in () at /usr/lib64/libQt5DBus.so.5 #5 0x7f94d2a4b9e9 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f94d5850734 in start_thread () at /lib64/libpthread.so.0 #7 0x7f94d558ed3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f94ba774700 (LWP 2364)): #0 0x7f94d558649d in poll () at /lib64/libc.so.6 #1 0x7f94d470d3e2 in () at /usr/lib64/libxcb.so.1 #2 0x7f94d470efcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f94bb850839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f94d2a4b9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f94d5850734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f94d558ed3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f94d5e29940 (LWP 2289)): [KCrash Handler] #6 0x7f94cd624dd0 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #7 0x7f94cd62624a in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #8 0x7f94cd62f2f6 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f94cd5bd93b in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5 #10 0x7f94cd5bd9f7 in QQmlComponentPrivate::completeCreate() () at
[ksnapshot] [Bug 374600] KStandardDirs::locateLocal aborts with type="tmp"
https://bugs.kde.org/show_bug.cgi?id=374600 Michael Pynechanged: What|Removed |Added Component|general |general Assignee|elvis.angelac...@kde.org|ase...@kde.org Product|ark |ksnapshot CC||mp...@kde.org --- Comment #1 from Michael Pyne --- The locateLocal("tmp",...) call needs to be ported to use QDir::tempPath() as described at https://community.kde.org/Frameworks/Porting_Notes/KStandardDirs I seem to remember there was some discussion about replacing ksnapshot with spectacle as well, though I'm not sure what happened with that. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371913] icon request: KeepassX
https://bugs.kde.org/show_bug.cgi?id=371913 --- Comment #2 from andreas--- can you post a screenshot cause I don't use KeepassX do you need an icon for the system tray or for the application. what is the icon called? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370248] The Person Widget is using the Desktop icon in ...
https://bugs.kde.org/show_bug.cgi?id=370248 andreaschanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from andreas --- is person the same than user switch? how is the package called in kde neon? -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 374617] New: Segfault while trying to play a Netflix DVD
https://bugs.kde.org/show_bug.cgi?id=374617 Bug ID: 374617 Summary: Segfault while trying to play a Netflix DVD Product: dragonplayer Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: ofe...@nowaker.net CC: myr...@kde.org Target Milestone: --- Application: dragon (16.12.0) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: 1. Insert a Netflix DVD in the drive 2. KDE offers to open the DVD with Dragon Player. 3. I choose to play the DVD. 4. Segfault. The crash can be reproduced every time. -- Backtrace: Application: Dragon Player (dragon), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe2da0e9480 (LWP 6487))] Thread 7 (Thread 0x7fe2b08d5700 (LWP 6504)): [KCrash Handler] #6 0x7fe2d0d2022c in g_slice_alloc () at /usr/lib/libglib-2.0.so.0 #7 0x7fe2d0d242b3 in g_string_sized_new () at /usr/lib/libglib-2.0.so.0 #8 0x7fe2d0d24862 in g_string_new () at /usr/lib/libglib-2.0.so.0 #9 0x7fe2d0d096cd in g_log_writer_format_fields () at /usr/lib/libglib-2.0.so.0 #10 0x7fe2d0d0a53e in g_log_writer_standard_streams () at /usr/lib/libglib-2.0.so.0 #11 0x7fe2d0d0a647 in g_log_writer_default () at /usr/lib/libglib-2.0.so.0 #12 0x7fe2d0d08b8c in g_log_structured_array () at /usr/lib/libglib-2.0.so.0 #13 0x7fe2d0d09047 in g_log_default_handler () at /usr/lib/libglib-2.0.so.0 #14 0x7fe2d0d09354 in g_logv () at /usr/lib/libglib-2.0.so.0 #15 0x7fe2d0d0955f in g_log () at /usr/lib/libglib-2.0.so.0 #16 0x7fe2be0363bc in gst_registry_feature_filter () at /usr/lib/libgstreamer-1.0.so.0 #17 0x7fe2ae00d0ac in () at /usr/lib/gstreamer-1.0/libgstautoconvert.so #18 0x7fe2ae00d29e in () at /usr/lib/gstreamer-1.0/libgstautoconvert.so #19 0x7fe2ae00d5af in () at /usr/lib/gstreamer-1.0/libgstautoconvert.so #20 0x7fe2be01dfa8 in gst_pad_query () at /usr/lib/libgstreamer-1.0.so.0 #21 0x7fe2be01e5a9 in gst_pad_peer_query () at /usr/lib/libgstreamer-1.0.so.0 #22 0x7fe2be0543a8 in () at /usr/lib/libgstreamer-1.0.so.0 #23 0x7fe2be01cb4e in gst_pad_forward () at /usr/lib/libgstreamer-1.0.so.0 #24 0x7fe2be056ca2 in gst_pad_proxy_query_caps () at /usr/lib/libgstreamer-1.0.so.0 #25 0x7fe2be01ce80 in gst_pad_query_default () at /usr/lib/libgstreamer-1.0.so.0 #26 0x7fe2be01dfa8 in gst_pad_query () at /usr/lib/libgstreamer-1.0.so.0 #27 0x7fe2be01e5a9 in gst_pad_peer_query () at /usr/lib/libgstreamer-1.0.so.0 #28 0x7fe2be059ae4 in gst_pad_peer_query_caps () at /usr/lib/libgstreamer-1.0.so.0 #29 0x7fe2ae46918a in () at /usr/lib/gstreamer-1.0/libgstvideoparsersbad.so #30 0x7fe2bcfd8170 in () at /usr/lib/libgstbase-1.0.so.0 #31 0x7fe2ae4694b7 in () at /usr/lib/gstreamer-1.0/libgstvideoparsersbad.so #32 0x7fe2bcfd5814 in () at /usr/lib/libgstbase-1.0.so.0 #33 0x7fe2be01dfa8 in gst_pad_query () at /usr/lib/libgstreamer-1.0.so.0 #34 0x7fe2be057424 in gst_pad_query_caps () at /usr/lib/libgstreamer-1.0.so.0 #35 0x7fe2aeac5ac9 in () at /usr/lib/gstreamer-1.0/libgstresindvd.so #36 0x7fe2aeac5c10 in () at /usr/lib/gstreamer-1.0/libgstresindvd.so #37 0x7fe2c415e1c8 in ffi_call_unix64 () at /usr/lib/libffi.so.6 #38 0x7fe2c415dc2a in ffi_call () at /usr/lib/libffi.so.6 #39 0x7fe2bd8a37ae in g_cclosure_marshal_generic () at /usr/lib/libgobject-2.0.so.0 #40 0x7fe2bd8a2f75 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0 #41 0x7fe2bd8b4f82 in () at /usr/lib/libgobject-2.0.so.0 #42 0x7fe2bd8bdbcc in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0 #43 0x7fe2bd8bdfaf in g_signal_emit () at /usr/lib/libgobject-2.0.so.0 #44 0x7fe2bdffd318 in gst_element_add_pad () at /usr/lib/libgstreamer-1.0.so.0 #45 0x7fe2aead1f6a in () at /usr/lib/gstreamer-1.0/libgstresindvd.so #46 0x7fe2aead28dc in () at /usr/lib/gstreamer-1.0/libgstresindvd.so #47 0x7fe2be0168f7 in () at /usr/lib/libgstreamer-1.0.so.0 #48 0x7fe2be016dbe in () at /usr/lib/libgstreamer-1.0.so.0 #49 0x7fe2be020eb9 in gst_pad_push_event () at /usr/lib/libgstreamer-1.0.so.0 #50 0x7fe2aeace166 in () at /usr/lib/gstreamer-1.0/libgstresindvd.so #51 0x7fe2bcff45ff in () at /usr/lib/libgstbase-1.0.so.0 #52 0x7fe2bcff5faf in () at /usr/lib/libgstbase-1.0.so.0 #53 0x7fe2be04bb41 in () at /usr/lib/libgstreamer-1.0.so.0 #54 0x7fe2d0d2aace in () at /usr/lib/libglib-2.0.so.0 #55 0x7fe2d0d2a0d5 in () at /usr/lib/libglib-2.0.so.0 #56 0x7fe2d29ed454 in start_thread () at
[kphotoalbum] [Bug 374608] KphotoAlbum is not multithreaded
https://bugs.kde.org/show_bug.cgi?id=374608 Johannes Zarl-Zierlchanged: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #1 from Johannes Zarl-Zierl --- The screenshot you posted shows that not a single core of your system is near 100%. This means that your real problem is filesystem performance. Using more cores for the scanning would make things worse in your specific case. How many image files are we talking about? What kind of storage do you use? Reading the meta-data from all your files means that kphotoalbum (and any other comparable program) needs to read every single image file (often in a non-sequential way). If you run "iotop" as root, you should see that your disk IO is busy. For reference: On my (not quite as powerful) computer, deleting my database and rebuilding it from scratch causes the a single core to run at 5% of its capacity, while the disk subsystem has an IO load of ~ 60% (6-8Mb/s). -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 374616] New: Visibility of association role name labels are not updated
https://bugs.kde.org/show_bug.cgi?id=374616 Bug ID: 374616 Summary: Visibility of association role name labels are not updated Product: umbrello Version: 2.21.0 (KDE Applications 16.12.0) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- How to reproduce: 1. start umbrello 2. add two classes to a diagram named A and B 3. add attribute a of type B to class A -> the association role name label of B end shows '-b' which indicates private visibility. 4. double click on attribute b in tree view, change visibility to public and press okay -> the association role name label of B end still shows '-b'. What is expected: The association role name label of B end should show the correct visibility -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 374609] kgpg fails to start
https://bugs.kde.org/show_bug.cgi?id=374609 Rolf Eike Beerchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Rolf Eike Beer --- *** This bug has been marked as a duplicate of bug 373408 *** -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 373408] kgpg segfault on boot and every later run
https://bugs.kde.org/show_bug.cgi?id=373408 Rolf Eike Beerchanged: What|Removed |Added CC||ro...@xtra.co.nz --- Comment #4 from Rolf Eike Beer --- *** Bug 374609 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368160] Panel autohides when context menu is shown
https://bugs.kde.org/show_bug.cgi?id=368160 Kai Uwe Broulikchanged: What|Removed |Added CC||k...@privat.broulik.de --- Comment #5 from Kai Uwe Broulik --- Can you explain? Why should the panel show up when you send a notification? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369835] QML BindingLoop in org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:210:17: QML ColumnLayout: Binding loop detected for property "width"
https://bugs.kde.org/show_bug.cgi?id=369835 Kai Uwe Broulikchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Can you still reproduce this issue? I just tried and I can't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369740] QML BindingLoop on first Kickoff launch ("contents/ui/FullRepresentation.qml:67:25: QML FavoritesMod")
https://bugs.kde.org/show_bug.cgi?id=369740 Kai Uwe Broulikchanged: What|Removed |Added CC||k...@privat.broulik.de Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374602] Cannot resize columns
https://bugs.kde.org/show_bug.cgi?id=374602 --- Comment #3 from David Jarvie--- The fact that the first column doesn't fit its contents is a bug. There are no column headings defined for your third and fourth columns, so even if you resized them, nothing would show. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374615] New: file system browser plugin's "parent folder" button doesn't work when synchronizing documents
https://bugs.kde.org/show_bug.cgi?id=374615 Bug ID: 374615 Summary: file system browser plugin's "parent folder" button doesn't work when synchronizing documents Product: kate Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: stevemcqu...@mailinator.com Target Milestone: --- I have the file system browser plugin enabled. I've also checked "automatically synchronize with current document". If I open a file, I can't use the browser plugin's up/parent folder button to navigate to the parent folder. I have to uncheck the synchronize button to get it working again. The previous KDE 4 behavior allowed this. Setup: 1. enable filesystem browser plugin and open it as a sidebar. 2. add the parent folder button to the plugin's toolbar 3. enable automatically synchronizing steps to reproduce: 1. Use the file system browser to navigating into a folder, say '~/foo/' 2. Open a file or two, say 'bar.txt' 3. (Possibly optional) open another file, change between their tabs in the main view in order to cause the plugin to kick off a sync. 4. Click the parent folder up arrow button. (note: for step 3, when navigating locally I seem to have to flip active documents as described before the button 'breaks'. If I'm navigating remotely to something like fish:/myserver/foo then this step doesn't seem to be required and it breaks immediately) Expected result: The browser should go up a folder, from ~/foo to ~/ Actual result: Nothing happens. I have to disable the sync option to navigate up again. Back/forward and entering into deeper folders still work. Version info: OS: KDE Neon current, 16.04 Ubuntu based? Kate: 16.12 KDE Frameworks: 5.29 Qt: 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373126] Icon Request: cups
https://bugs.kde.org/show_bug.cgi?id=373126 andreaschanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/bre ||eze-icons/ff9604f1bdd34347b ||8d55d7651452e4a7f281991 --- Comment #3 from andreas --- Git commit ff9604f1bdd34347b8d55d7651452e4a7f281991 by andreas kainz. Committed on 05/01/2017 at 22:38. Pushed by andreask into branch 'master'. add cups icon thanks colin A +1-0icons/devices/16/cups.svg A +1-0icons/devices/16/cupsprinter.svg A +1-0icons/devices/16/printer.svg A +1-0icons/devices/22/cups.svg A +1-0icons/devices/22/cupsprinter.svg A +1-0icons/devices/22/printer.svg A +1-0icons/devices/64/cups.svg A +1-0icons/devices/64/cupsprinter.svg https://commits.kde.org/breeze-icons/ff9604f1bdd34347b8d55d7651452e4a7f281991 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374310] Cannot build plasma-desktop without AppStreamQt installed
https://bugs.kde.org/show_bug.cgi?id=374310 --- Comment #8 from Omar Plummer--- Works for me as well. My sincerest thanks to everyone who contributed to fixing this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 --- Comment #12 from Tsu Jan--- I haven't found anything in kio yet but I'm pretty sure about this: The freeze happens when a window handle is going to be created for those menus, whether by setting WA_NativeWindow to `true` temporarily or by using `createTLExtra()` and `createTLSysExtra()`, as QtCurve does. I mean, the freeze isn't related to setting the format -- `setFormat()` -- but to the creation of a window handle for menus. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374591] Deleting image only removes the file and sets the status to hidden but does not delete the image from DB
https://bugs.kde.org/show_bug.cgi?id=374591 --- Comment #5 from Mario Frank--- Oh, yes. The complete patch description: https://bugs.kde.org/show_bug.cgi?id=320666#c17 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374591] Deleting image only removes the file and sets the status to hidden but does not delete the image from DB
https://bugs.kde.org/show_bug.cgi?id=374591 --- Comment #4 from Mario Frank--- (In reply to caulier.gilles from comment #3) > Mario, you is right. > > In fact, we need a garbage collector, as it's explained in this file : > > https://bugs.kde.org/show_bug.cgi?id=317210 > > ...even if the DB transactions must be improved when action are processed. > > Gilles Yes, I see. A garbage collection would be helpful. But some cleanup could be already done without garbage collection. There are some spots I wanted to improve anyway. But I will leave this for after the release. Did you see the patch (https://bugs.kde.org/attachment.cgi?id=103203) for https://bugs.kde.org/show_bug.cgi?id=374191 (context menu in tags and people sidebar? It also improves the way similarity information is handled in table view, image view and for sorting. The new approach is much more stable and the functionality is now tested quite excessively. Also, the DB handling seems to work as expected apart from the problems described in this bug here. I would like to commit the patch. Cheers, Mario -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374602] Cannot resize columns
https://bugs.kde.org/show_bug.cgi?id=374602 --- Comment #2 from Germano Massullo--- Created attachment 103222 --> https://bugs.kde.org/attachment.cgi?id=103222=edit screenshot (In reply to David Jarvie from comment #1) > The columns are all sized to fit their contents. The only resizable column > is the last one, which stretches or shrinks to the window width. > > Is there a reason why you want to resize them? In my opinion, user should be able to resize as much as he wants. In my case there is the first column that does not fit its content, moreover there are other columns without heading -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374424] Calendar files are wrongly created read-only or disabled
https://bugs.kde.org/show_bug.cgi?id=374424 --- Comment #2 from David Jarvie--- See Bug 362962 for the read-only creation bug report. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374602] Cannot resize columns
https://bugs.kde.org/show_bug.cgi?id=374602 --- Comment #1 from David Jarvie--- The columns are all sized to fit their contents. The only resizable column is the last one, which stretches or shrinks to the window width. Is there a reason why you want to resize them? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes
https://bugs.kde.org/show_bug.cgi?id=369194 --- Comment #7 from Ian Haber--- Created attachment 103221 --> https://bugs.kde.org/attachment.cgi?id=103221=edit Parser bug video Added a video of the bug. In the first part, i show the correct case, what it is supposed to do. the second section i show the bug i'm having with the parser. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374614] Pasting text in title clip window changes color when element loses focus
https://bugs.kde.org/show_bug.cgi?id=374614 --- Comment #1 from Christian Weiske--- Step 11 makes further behavior weirder, because the text element somehow stays in focus-mode until clicked again - and it switches to black then. Fresh steps: 1. Create a title clip 2. Add a text element and paste text with ctrl+v 3. Cick on the "Add Text" toolbar button 4. Create the second text element, paste with ctrl+v. 5. Click somewhere on the free clip area. Color of 2nd text changes to black. 6. Click 2nd text element. It gets a red "active" frame. 7. Click 1st text element. It's still in cursor-mode (ready to input text). 8. Click somewhere on the free clip area. Color of 1st text stays white. 9. Double-click on the text element. Text will be selected now. 10. Click somewhere on the free clip area. Color of 1st text changes to black! 11. Click 1st text element. It now has the red "active" frame. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374614] New: Pasting text in title clip window changes color when element loses focus
https://bugs.kde.org/show_bug.cgi?id=374614 Bug ID: 374614 Summary: Pasting text in title clip window changes color when element loses focus Product: kdenlive Version: 16.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: cwei...@cweiske.de Target Milestone: --- This is a very weird issue. When creating a title clip with text elements, the text color changes after copy and pasting text from the clipboard and then clicking somewhere else. Steps to reproduce: 1. Create a new project 2. Create a title clip 3. In the title clip editor, add a text element/frame and type something. The color of the text is white (default here) 4. Click somewhere on the free space on the clip so that the text element loses focus. The text stays white. 5. Open a text editor (e.g. pluma or gedit) 6. Write some text in it, select it and copy it to the clipboard 7. Return to the title clip editor 8. Add a text element. Press Ctrl+v to paste the text from the clipboard. The text is white. 9. Click somewhere on the free space. The text color switches to black! It gets even weirder: 10. Add a text element. Press Ctrl+v to paste the text from the clipboard. 11. Click on the "Add Text" toolbar button and add a new text element somewhere. The previously pasted text loses focus but stays white! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374606] Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using XRender.
https://bugs.kde.org/show_bug.cgi?id=374606 --- Comment #4 from Martin Gräßlin--- Sorry, but I'm not going to download random windows applications to run them through wine. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 370902] Title clip duration
https://bugs.kde.org/show_bug.cgi?id=370902 Christian Weiskechanged: What|Removed |Added CC||cwei...@cweiske.de --- Comment #4 from Christian Weiske --- This also happens with slideshow clips. Steps to reproduce: 0. Create 30fps project 1. Create slideshow clip pointing to folder with 1 image, default frame length of 5 seconds 2. Project bin shows slideshow with 5 seconds length 3. Edit slideshow clip: Change frame length to 6 seconds. 4. Project bin still shows 5 seconds length. Looking at the project file I see that both properties "length" and "ttl" have been changed (180), but the "kdenlive:duration" property still has the old value (150). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 374599] Cannot delete payee
https://bugs.kde.org/show_bug.cgi?id=374599 --- Comment #2 from Scott Russell--- I have no scheduled transactions. On Jan 5, 2017 3:30 PM, "Thomas Baumgart" wrote: > https://bugs.kde.org/show_bug.cgi?id=374599 > > --- Comment #1 from Thomas Baumgart --- > Could it be, that the payee is still referenced by a scheduled transaction? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 374603] Crash on installing icons
https://bugs.kde.org/show_bug.cgi?id=374603 Kai Uwe Broulikchanged: What|Removed |Added Product|systemsettings |frameworks-karchive Component|general |general Assignee|plasma-b...@kde.org |fa...@kde.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Version|5.8.4 |unspecified CC||k...@privat.broulik.de, ||kdelibs-b...@kde.org --- Comment #1 from Kai Uwe Broulik --- Can reproduce. Re-assigning to KArchive, could be a bug in GHNS, though. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374613] New: Project bin shows clip length of "00:00:04:30" when the clip is 5 seconds
https://bugs.kde.org/show_bug.cgi?id=374613 Bug ID: 374613 Summary: Project bin shows clip length of "00:00:04:30" when the clip is 5 seconds Product: kdenlive Version: 16.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: cwei...@cweiske.de Target Milestone: --- The project bin doesn't correctly show the clip duration for a 30fps project: It shows 00:00:04:30 for a 5 seconds long clip - which should show up as "00:00:05:00". Clip properties correctly show it as 00:00:05:00. Steps to reproduce: 1. Create new project "HD 720", 30fps 2. Create a color clip with length 00:00:05:00 3. Project bin shows the clip length as "00:00:04:30" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374612] New: Slideshow animation setting broken when using german locale
https://bugs.kde.org/show_bug.cgi?id=374612 Bug ID: 374612 Summary: Slideshow animation setting broken when using german locale Product: kdenlive Version: 16.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: cwei...@cweiske.de Target Milestone: --- Editing a slideshow clip resets the "Animation" property when the German locale is used. Steps to reproduce: 1. Create slideshow clip pointing to a folder with a single image, and "animation" set to "Verschieben und Zoomen" (Pan and Zoom). 2. Save the project. The .kdenlive file correctly contains Pan and zoom 3. Edit the slideshow clip. The animation dropdown value is empty. When starting kdenlive with "LC_ALL=C kdenlive" it works fine. I guess it's a setting-to-title-mapping problem. -- You are receiving this mail because: You are watching all bug changes.
[KDE Config Driver Manager] [Bug 374611] New: reporter
https://bugs.kde.org/show_bug.cgi?id=374611 Bug ID: 374611 Summary: reporter Product: KDE Config Driver Manager Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: kendal@gmail.com Target Milestone: --- i cant do my upgrades , because they said they nee dto install more package but all the packages needed are already donwnloaded , crash sometimes with wine and league of legends , much ips drops, can't upgrade my nvdia graphic card -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374564] File search opens multiple sessions of the same file
https://bugs.kde.org/show_bug.cgi?id=374564 --- Comment #1 from Ferdinand Gruber--- May be that I have not expressed clearly: Each mouse click in the search result shown at the bottom of the editor window opens a new tab of the same file, for example: file.php, file.php(2), file.php(3), file.php(4) ... The files are numbered and they are identical. If I change something in one of theese files I get trouble with saving the changes because of the other opened instances. Very annoying! -- You are receiving this mail because: You are watching all bug changes.
[kdm] [Bug 374610] New: kms server crash after opening laptop (was suspend) and pressing power button
https://bugs.kde.org/show_bug.cgi?id=374610 Bug ID: 374610 Summary: kms server crash after opening laptop (was suspend) and pressing power button Product: kdm Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: kdmdesktop Assignee: kdm-bugs-n...@kde.org Reporter: azahmed...@hotmail.com Target Milestone: --- Application: ksmserver (ksmserver), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0602579940 (LWP 1513))] Thread 2 (Thread 0x7f05eb20b700 (LWP 1533)): #0 0x7f060204e56d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f05f68709f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f05f6870b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f05fd7cb6fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f05fd77507a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f05fd5970d3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f06026cc6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f05fd59bd88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f05f857a464 in start_thread (arg=0x7f05eb20b700) at pthread_create.c:333 #9 0x7f06020579df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f0602579940 (LWP 1513)): [KCrash Handler] #6 __GI___libc_free (mem=0x8) at malloc.c:2963 #7 0x7f05fc249771 in XIQueryDevice () from /usr/lib/x86_64-linux-gnu/libXi.so.6 #8 0x7f05ee118366 in QXcbConnection::handleEnterEvent() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f05ee104d18 in QXcbWindow::handleEnterNotifyEvent(int, int, int, int, unsigned char, unsigned char, unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7f05ee10528f in QXcbWindow::handleXIEnterLeave(xcb_ge_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7f05ee11d3bc in QXcbConnection::xi2HandleEvent(xcb_ge_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #12 0x7f05ee0efaca in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #13 0x7f05ee0f0015 in QXcbConnection::processXcbEvents() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #14 0x7f05fd7a3b39 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f05fe05eb2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f05fe0662e1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f05fd777090 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f05fd77981d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f05fd7cb2d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f05f68707f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f05f6870a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f05f6870b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f05fd7cb6df in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f05fd77507a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f05fd77d7ec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f060231f591 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_ksmserver.so #27 0x7f0601f8f2b1 in __libc_start_main (main=0x4006c0 , argc=1, argv=0x7ffcd6e177e8, init=, fini=, rtld_fini=, stack_end=0x7ffcd6e177d8) at ../csu/libc-start.c:291 #28 0x004006fa in _start () -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 374609] New: kgpg fails to start
https://bugs.kde.org/show_bug.cgi?id=374609 Bug ID: 374609 Summary: kgpg fails to start Product: kgpg Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: ro...@xtra.co.nz Target Milestone: --- Application: kgpg (16.11.90) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: kgpg crashes both on KDE startup and whenever I try to start it subesquently. The crash can be reproduced every time. -- Backtrace: Application: KGpg (kgpg), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc3b1f938c0 (LWP 3436))] Thread 4 (Thread 0x7fc381631700 (LWP 3445)): #0 0x7fc3abba049d in poll () from /lib64/libc.so.6 #1 0x7fc3a5022314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fc3a502242c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc3ac6b29eb in QEventDispatcherGlib::processEvents (this=0x7fc37c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fc3ac6622db in QEventLoop::exec (this=this@entry=0x7fc381630d10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fc3ac4a7fca in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fc3ac4ac7f9 in QThreadPrivate::start (arg=0x2d03890) at thread/qthread_unix.cpp:368 #7 0x7fc3a7bc9734 in start_thread () from /lib64/libpthread.so.0 #8 0x7fc3abba8d3d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fc390a54700 (LWP 3440)): #0 0x7fc3abba049d in poll () from /lib64/libc.so.6 #1 0x7fc3a5022314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fc3a502242c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc3ac6b29eb in QEventDispatcherGlib::processEvents (this=0x7fc3840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fc3ac6622db in QEventLoop::exec (this=this@entry=0x7fc390a53ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fc3ac4a7fca in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fc3acd24a25 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fc3ac4ac7f9 in QThreadPrivate::start (arg=0x7fc3acf8bd00) at thread/qthread_unix.cpp:368 #8 0x7fc3a7bc9734 in start_thread () from /lib64/libpthread.so.0 #9 0x7fc3abba8d3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fc392fba700 (LWP 3438)): #0 0x7fc3abba049d in poll () from /lib64/libc.so.6 #1 0x7fc3a6c963e2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fc3a6c97fcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fc3954cf779 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fc3ac4ac7f9 in QThreadPrivate::start (arg=0x26aaaf0) at thread/qthread_unix.cpp:368 #5 0x7fc3a7bc9734 in start_thread () from /lib64/libpthread.so.0 #6 0x7fc3abba8d3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fc3b1f938c0 (LWP 3436)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x280001) at /usr/include/c++/4.8/bits/atomic_base.h:496 #7 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:96 #8 QBasicAtomicInteger::load (this=0x280001) at /usr/include/qt5/QtCore/qbasicatomic.h:116 #9 QtPrivate::RefCount::ref (this=0x280001) at /usr/include/qt5/QtCore/qrefcount.h:49 #10 QString::QString (other=..., this=0x2ccc258) at /usr/include/qt5/QtCore/qstring.h:890 #11 KgpgCore::KgpgKeySubPrivate::KgpgKeySubPrivate (this=0x2ccc220, id=..., size=, trust=..., algo=..., type=..., date=..., curve=...) at /usr/src/debug/kgpg-16.11.90/core/kgpgkey.cpp:55 #12 0x00438aad in KgpgCore::KgpgKeySub::KgpgKeySub (this=0x7fff49042bf0, id=..., size=2048, trust=..., algo=..., type=..., date=..., curve=...) at /usr/src/debug/kgpg-16.11.90/core/kgpgkey.cpp:74 #13 0x004ac57c in readPublicKeysProcess (p=..., readNode=readNode@entry=0x0) at /usr/src/debug/kgpg-16.11.90/kgpginterface.cpp:206 #14 0x004aec60 in KgpgInterface::readPublicKeys (ids=...) at /usr/src/debug/kgpg-16.11.90/kgpginterface.cpp:302 #15 0x00441de6 in KGpgRootNode::addKeys (this=0x2af3ce0, ids=...) at /usr/src/debug/kgpg-16.11.90/core/KGpgRootNode.cpp:70 #16 0x00454d3c in KGpgItemModel::refreshAllKeys (this=0x2b0d700) at /usr/src/debug/kgpg-16.11.90/model/kgpgitemmodel.cpp:474 #17 0x00489ca0 in KeysManager::refreshkey (this=0x2aab180) at /usr/src/debug/kgpg-16.11.90/keysmanager.cpp:2648 #18 0x004e9fca in KeysManager::qt_static_metacall (_o=0x2aab180, _c=, _id=, _a=) at /usr/src/debug/kgpg-16.11.90/build/moc_keysmanager.cpp:431 #19
[krita] [Bug 374565] krita crash on start with eigen 3.3
https://bugs.kde.org/show_bug.cgi?id=374565 Gael Guennebaudchanged: What|Removed |Added CC||g.g...@free.fr --- Comment #3 from Gael Guennebaud --- Let me paste what I said on IRC. My best bet is that libs/image is built with -mavx or -march=native (or similar), whereas the plugin convolutionfilters is built with SSE only. This breaks the ABI, and in particular, the plugin create a MatrixXd with 16bytes alignement whereas lib/image expect 32 bytes alignment by default to comply with AVX requirements. If you want SSE/AVX compatibility, then you have to compile all libs/plugins that use Eigen with either: -DEIGEN_MAX_ALIGN_BYTES=16 -DEIGEN_MAX_ALIGN_BYTES=32 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374606] Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using XRender.
https://bugs.kde.org/show_bug.cgi?id=374606 --- Comment #3 from prince.re...@gmail.com --- http://www54.zippyshare.com/v/XEuO8bZs/file.html It needs Wine. wine --version: wine-2.0-rc3 (i think the latest) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 374599] Cannot delete payee
https://bugs.kde.org/show_bug.cgi?id=374599 --- Comment #1 from Thomas Baumgart--- Could it be, that the payee is still referenced by a scheduled transaction? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374596] inconsistent RDTSCP support on x86_64
https://bugs.kde.org/show_bug.cgi?id=374596 --- Comment #4 from Tom Hughes--- Ah sorry I misunderstood your original report... You're saying that valgrind aborts on the instruction even though you don't try and execute it. My guess is that it's happening because that will be reported at translation time and valgrind translates instructions in blocks so it may translate an instruction that never gets executed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 296673] Please preserve the window geometry relative to it's original screen instead of globally when adding a screen
https://bugs.kde.org/show_bug.cgi?id=296673 Martin Gräßlinchanged: What|Removed |Added CC||rainer.kl...@gmx.de --- Comment #47 from Martin Gräßlin --- *** Bug 374498 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374498] Windows get moved to second monitor when the latter is connected
https://bugs.kde.org/show_bug.cgi?id=374498 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 296673 *** -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 374608] New: KphotoAlbum is not multithreaded
https://bugs.kde.org/show_bug.cgi?id=374608 Bug ID: 374608 Summary: KphotoAlbum is not multithreaded Product: kphotoalbum Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: angeran...@gmail.com Target Milestone: --- Created attachment 103219 --> https://bugs.kde.org/attachment.cgi?id=103219=edit Screenshot of cpu not used Hello, I started to use kphotAlbum with my large photo collection, after 2 hours it reached just the 20% of my collection on my high speed 8 cores computer. I launched the system monitors (see attached image) and I noticed that quite all cores was sleeping instead of scanning files. Why don't you use the "parallel" command for scanning? See https://www.gnu.org/software/parallel/ , it's a simple open source command that permit to speed up executions. I use it with all my softwares that works with many files, it speed up process incredibly. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 373967] Android File System not Mounted and Pairing is no longer persistent.
https://bugs.kde.org/show_bug.cgi?id=373967 Rasmus Bchanged: What|Removed |Added CC||ras...@screendream.se --- Comment #2 from Rasmus B --- I'm experiencing the same thing with the filesystem - however, my permissions are correctly set. Trying to mount the filesystem i get an "Error - Kioexec" dialog with the text: "A folder named /home/user/.cache/kioexec/krun/9363_0/ already exists." Hade stable version first and changed to kdeconnect-git r1551.82ca0b4-1 to try if that helped, but no change. Using Arch Linux and running the mobile app version 1.5 on a Samsung Galaxy S7. Any ideas? Regards, Rasmus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374498] Windows get moved to second monitor when the latter is connected
https://bugs.kde.org/show_bug.cgi?id=374498 Martin Gräßlinchanged: What|Removed |Added Component|general |xrandr --- Comment #3 from Martin Gräßlin --- The behavior you are experiencing is kind of expected. To explain: the windows are positioned on a virtual screen. The actual outputs are overlapped to the virtual screen. The windows have their position in a virtual screen coordinates, they are not bound to an actual output. Consider you have a window at 0/0. When you attach a new output above your existing output what happens is the virtual screen gets resized, your windows keep the positions they have relative to the virtual screen. But the outputs changed. The position at 0/0 is now covered by the new output. It looks like all windows moved to the new output, but in truth the windows did not move at all. The situation is difficult to handle for a window manager. X11 does not give us the information to which output a window belongs. Some windows adjust themselves (e.g. Plasma), some windows just close and get recreated (Qt 5 did so at some time). So KWin cannot know what to do in this situation. Should it move the windows or not? What if it moves one which adjusted itself? Overall a non fixable situation on X11 and even on Wayland it will be tricky as we kind of follow the X11 approach due to the legacy debt of KWin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374606] Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using XRender.
https://bugs.kde.org/show_bug.cgi?id=374606 --- Comment #2 from prince.re...@gmail.com --- Ok I will upload the program with which it crashes so you can reproduce the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 216353] Make it possible to apply lens correction in batch
https://bugs.kde.org/show_bug.cgi?id=216353 --- Comment #9 from i...@axel-krebs.de --- Created attachment 103218 --> https://bugs.kde.org/attachment.cgi?id=103218=edit BQM- pic and distorted corrected pics version After BQM _and_ distortion correction, it should be possible to choose the final cut -INcluding original distortion- or -EXcluding original distortion. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374606] Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using XRender.
https://bugs.kde.org/show_bug.cgi?id=374606 prince.re...@gmail.com changed: What|Removed |Added Summary|Kwin crash when using |Kwin crash when using |multimedia related |multimedia related |applications. Screen goes |applications. Screen goes |blurry. Never happens when |blurry. Never happens when |using Xrandr. |using XRender. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374596] inconsistent RDTSCP support on x86_64
https://bugs.kde.org/show_bug.cgi?id=374596 --- Comment #2 from bugzi...@dcopp.net --- No, this is on a 12-core 64-bit system, apparently running under libvirt. /etc/redhat-release = CentOS release 6.6 /proc/cpuinfo = processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version (cpu64-rhel6) stepping : 3 microcode : 1 cpu MHz : 2933.436 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm unfair_spinlock pni cx16 hypervisor lahf_lm bogomips : 5866.87 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ...etc. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374596] inconsistent RDTSCP support on x86_64
https://bugs.kde.org/show_bug.cgi?id=374596 --- Comment #3 from Tom Hughes--- Sure, but is the program compiled as 64 bit or 32 bit? It's using 32 bit register names in the assembly but that might be normal for RDTSCP which is why I asked how you were compiling it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 216353] Make it possible to apply lens correction in batch
https://bugs.kde.org/show_bug.cgi?id=216353 i...@axel-krebs.de changed: What|Removed |Added CC||i...@axel-krebs.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374607] [Regression] Show Desktop Grid effect is broken
https://bugs.kde.org/show_bug.cgi?id=374607 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- Issue 1) is already reported. Issue 2) is an explicit change in how the effect works. The zooming was removed again. *** This bug has been marked as a duplicate of bug 364509 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364509] Applications window disappears while dragging them through Desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=364509 Martin Gräßlinchanged: What|Removed |Added CC||dima...@gmail.com --- Comment #3 from Martin Gräßlin --- *** Bug 374607 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374606] Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using Xrandr.
https://bugs.kde.org/show_bug.cgi?id=374606 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages provided by your distribution (please ask the distribution support channel on how to install them) and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 374600] KStandardDirs::locateLocal aborts with type="tmp"
https://bugs.kde.org/show_bug.cgi?id=374600 Martin Gräßlinchanged: What|Removed |Added CC|mgraess...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374607] New: [Regression] Show Desktop Grid effect is broken
https://bugs.kde.org/show_bug.cgi?id=374607 Bug ID: 374607 Summary: [Regression] Show Desktop Grid effect is broken Product: kwin Version: 5.8.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: dima...@gmail.com Target Milestone: --- "Show Desktop Grid" effect (the effect which is triggered with Ctrl+F8 shortcut) is broken. 1) Just after I click a window and try to drag it (to another desktop for example) it instantly disappears. 2) Hovering over a window does not enlarge it anymore. 3) It seems that the size of dropped window is calculated incorrectly I recorded two videos: Working effect (kwin version is 5.5.5) - https://drive.google.com/file/d/0B4r5nJvpzEHGVWVLVTlzYm5pY3M/view?usp=sharing Not working effect (kwin version is 5.8.5) - https://drive.google.com/file/d/0B4r5nJvpzEHGamVDQnU5djRscHc/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374588] kwin 5.8.5 compilation fails with lto enabled gcc-5.4.0
https://bugs.kde.org/show_bug.cgi?id=374588 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #4 from Martin Gräßlin --- Maybe also a gcc error? I'm setting to RESOLVED UPSTREAM as from our side there is not much to do. I do not even see which are in KWin seems to be responsible for it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374605] New: Chuck Norris slide takes a long time to be displayed in presentation view
https://bugs.kde.org/show_bug.cgi?id=374605 Bug ID: 374605 Summary: Chuck Norris slide takes a long time to be displayed in presentation view Product: okular Version: 0.26.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: gree...@greenrd.org Target Milestone: --- 1. Open https://github.com/Andromedans/andromeda/raw/master/doc/talks/marseille/MAP%202016%20Marseille.pdf 2. Go into presentation mode (Ctrl+Shift+P) 3. Advance through the slides one by one, until you reach slide 52 (the second picture of Chuck Norris) The last transition takes wy too long. When Firefox renders this PDF it loads the 52nd slide instantly. So in this instance Firefox's Javascript PDF implementation is faster than Okular's native one! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374606] New: Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using Xrandr.
https://bugs.kde.org/show_bug.cgi?id=374606 Bug ID: 374606 Summary: Kwin crash when using multimedia related applications. Screen goes blurry. Never happens when using Xrandr. Product: kwin Version: 5.8.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: prince.re...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.5) Qt Version: 5.7.0 Frameworks Version: 5.29.0 Operating System: Linux 4.9.0-040900-generic x86_64 Distribution: KDE neon User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: When using certain multimedia application like wine o webcam applications - Unusual behavior I noticed: Screen becomes blurry and buggy. It never happens when using XRanrar - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3d8f31e900 (LWP 15991))] Thread 9 (Thread 0x7f3d4a21b700 (LWP 16799)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3d8cac5a4b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3d88156eed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f3d881577c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f3d8cac4b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3d88b2f6ba in start_thread (arg=0x7f3d4a21b700) at pthread_create.c:333 #6 0x7f3d8ee1b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f3d74acf700 (LWP 16632)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3d8cac5a4b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3d88156eed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f3d881577c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f3d8cac4b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3d88b2f6ba in start_thread (arg=0x7f3d74acf700) at pthread_create.c:333 #6 0x7f3d8ee1b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f3d49750700 (LWP 16629)): #0 0x7f3d8ee0fb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3d8cceb60a in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3d8ccecee8 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3d8cc9acea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3d8cabffb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3d87c8c675 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3d8cac4b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3d88b2f6ba in start_thread (arg=0x7f3d49750700) at pthread_create.c:333 #8 0x7f3d8ee1b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f3d40e1d700 (LWP 15999)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3d8be565c4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f3d8be56609 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f3d88b2f6ba in start_thread (arg=0x7f3d40e1d700) at pthread_create.c:333 #4 0x7f3d8ee1b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f3d5a958700 (LWP 15996)): #0 0x7f3d8ee0fb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3d8cceb60a in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3d8ccecee8 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3d8cc9acea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3d8cabffb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3d87c8c675 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3d8cac4b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3d88b2f6ba in start_thread (arg=0x7f3d5a958700) at pthread_create.c:333 #8 0x7f3d8ee1b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f3d64950700 (LWP 15995)): #0 0x7f3d8ee0fb5d in poll () at
[unknown] [Bug 374604] KDE-Classic icon theme is not updated for KDE5
https://bugs.kde.org/show_bug.cgi?id=374604 Christoph Feckchanged: What|Removed |Added CC||kain...@gmail.com Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED Component|general |general Assignee|cf...@kde.org |unassigned-b...@kde.org Product|frameworks-kiconthemes |unknown --- Comment #1 from Christoph Feck --- We used to have a bugzilla entry for kdeartwork. Since it does no longer exist, I assume that this package is unmaintained. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 369122] ~/.cache/kioexec/krun/_0_ does not exist
https://bugs.kde.org/show_bug.cgi?id=369122 Andreas Schallenbergchanged: What|Removed |Added CC||Andreas.Schallenberg@Eurobi ||ld.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 337685] SFTP: Filesystem expose doesn't work
https://bugs.kde.org/show_bug.cgi?id=337685 Andreas Schallenbergchanged: What|Removed |Added CC||Andreas.Schallenberg@Eurobi ||ld.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 374085] no button to answer to an sms
https://bugs.kde.org/show_bug.cgi?id=374085 --- Comment #4 from Philippe ROUBACH--- in "sound and notifications" > "advanced settings" > "notifications access" there is only "kdeconnect" my default sms app is "Messenger" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358046] Changelog missing since 15.12
https://bugs.kde.org/show_bug.cgi?id=358046 qubo...@gmail.com changed: What|Removed |Added CC||qubo...@gmail.com --- Comment #5 from qubo...@gmail.com --- Created attachment 103217 --> https://bugs.kde.org/attachment.cgi?id=103217=edit changelog with 16.12 changes included Please commit this file. In time I can add changelogs for other missing versions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 374604] New: KDE-Classic icon theme is not updated for KDE5
https://bugs.kde.org/show_bug.cgi?id=374604 Bug ID: 374604 Summary: KDE-Classic icon theme is not updated for KDE5 Product: frameworks-kiconthemes Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: yourbestfri...@openmailbox.org CC: kdelibs-b...@kde.org Target Milestone: --- Hello. KDE-Classic icon theme https://websvn.kde.org/tags/KDE/4.14.3/kdeartwork/IconThemes/kdeclassic/ misses a lot of icons on KDE5. Please update! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 --- Comment #11 from Tsu Jan--- > You'll also have to look in kdiroperator.cpp, that's where the context menu > (for right-clicking on items in the file list) is defined. Thanks! I will soon. > I have rounded corners configured for popup menus, and that required some > translucency. That's correct. Anyway, I'll report back as soon as I find something in those files. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 --- Comment #10 from RJVB--- Heh, and your reaction taught about a widget style I never heard about, and which might be even more appropriate to implement an "OS X" lookalike that makes KDE applications actually looks good on Mac (without specific tuning) and not as if they're designed for the visually impaired ;) You'll also have to look in kdiroperator.cpp, that's where the context menu (for right-clicking on items in the file list) is defined. I think I understand why I'm running into issues without using menu translucency. I have rounded corners configured for popup menus, and that required some translucency. You don't happen to have a suggestion how to obtain that without calling addAlphaChannel() (or let it do only safe things), by chance? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 --- Comment #9 from Tsu Jan--- @RJVB Actually, I was lead to your report by google, while trying to know why KFileDialog is an exception and which source file I should read. Your patch says "kfilewidget.cpp". That will be a good start :) -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 361688] kscreen.xcb.help fill log at insane rate
https://bugs.kde.org/show_bug.cgi?id=361688 --- Comment #15 from Bruno Friedmann--- I can just concur to that : Here's a simple backlight event in system journal Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: State (newValue, Deleted): 0 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Output: 547 Jan 05 19:39:21 qt-kt.labaroche.ioda.net org.kde.KScreen[2351]: kscreen.xcb.helper: Property: Backlight Jan 05 19:39:21
[systemsettings] [Bug 374603] New: Crash on installing icons
https://bugs.kde.org/show_bug.cgi?id=374603 Bug ID: 374603 Summary: Crash on installing icons Product: systemsettings Version: 5.8.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@falkp.no Target Milestone: --- Application: systemsettings5 (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.14-300.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Tried installing https://store.kde.org/p/1167075/ via "Get new icons". The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f172d9486c0 (LWP 7863))] Thread 5 (Thread 0x7f170d7e5700 (LWP 7890)): #0 0x7f17394dfbed in read () from /lib64/libc.so.6 #1 0x7f17323b9450 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f1732374c60 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f17323750f4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f173237526c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f173a2ea73b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f173a29b73a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f173a0f85f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f173a0fc9da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f17365be6ca in start_thread () from /lib64/libpthread.so.0 #10 0x7f17394eff7f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f170e03e700 (LWP 7889)): #0 0x7f17323ba7f9 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7f1732374577 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f173237507b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f173237526c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f173a2ea73b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f173a29b73a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f173a0f85f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f173a0fc9da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f17365be6ca in start_thread () from /lib64/libpthread.so.0 #9 0x7f17394eff7f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f171a0fe700 (LWP 7865)): #0 0x7f17394e401d in poll () from /lib64/libc.so.6 #1 0x7f1732375156 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f173237526c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f173a2ea73b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f173a29b73a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f173a0f85f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f173a9e7739 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f173a0fc9da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f17365be6ca in start_thread () from /lib64/libpthread.so.0 #9 0x7f17394eff7f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f17225f2700 (LWP 7864)): #0 0x7f17394e401d in poll () from /lib64/libc.so.6 #1 0x7f1736bffd10 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f1736c01aa9 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f1726cbbd69 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f173a0fc9da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f17365be6ca in start_thread () from /lib64/libpthread.so.0 #6 0x7f17394eff7f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f172d9486c0 (LWP 7863)): [KCrash Handler] #6 0x7f173778be37 in KArchiveDirectory::addEntry(KArchiveEntry*) () from /lib64/libKF5Archive.so.5 #7 0x7f1737797505 in KTar::openArchive(QFlags) [clone .part.18] () from /lib64/libKF5Archive.so.5 #8 0x7f170f7c7847 in KNS3::Installation::installDownloadedFileAndUncompress(KNS3::EntryInternal const&, QString const&, QString) () from /lib64/libKF5NewStuff.so.5 #9 0x7f170f7c9750 in KNS3::Installation::install(KNS3::EntryInternal, QString const&) () from /lib64/libKF5NewStuff.so.5 #10 0x7f170f7ca378 in KNS3::Installation::slotPayloadResult(KJob*) () from /lib64/libKF5NewStuff.so.5 #11 0x7f173a2c3ae6 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7f173a51c8e2 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #13
[digikam] [Bug 374368] Unchecking "Show splash screen at startup" causes no window to display at launch
https://bugs.kde.org/show_bug.cgi?id=374368 jst...@gmx.de changed: What|Removed |Added CC||jst...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374591] Deleting image only removes the file and sets the status to hidden but does not delete the image from DB
https://bugs.kde.org/show_bug.cgi?id=374591 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- Mario, you is right. In fact, we need a garbage collector, as it's explained in this file : https://bugs.kde.org/show_bug.cgi?id=317210 ...even if the DB transactions must be improved when action are processed. Gilles -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 --- Comment #8 from RJVB--- Ah, thanks! This sounds like a reasonable beginning of explanation that just leaves 2 questions open: - why is only the toplevel pop-up menu concerned, i.e. why can I open its submenus normally when rendered in QtCurve as long as I use another widget style for the parent menu? - I don't have translucency configured in my QtCurve settings (all 3 parameters are 100% opaque). That suggests that the operations required to obtain translucency are what triggers the behaviour, not the translucency itself, and offers the possibility of another workaround (behave as if translucency isn't supported when not requested). -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 308443] Crash when update a favicon twice
https://bugs.kde.org/show_bug.cgi?id=308443 Hector Wilvert Ivan Valdez Rezachanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 antonio.guadag...@gmail.com changed: What|Removed |Added CC||antonio.guadag...@gmail.com --- Comment #91 from antonio.guadag...@gmail.com --- Same problem : Opensuse Leap 42.1 Kernel 4.9.0-4 Nvidia 340.101 patched for 4.9 kernel series + KDE KDE Frameworks 5.29.0 Qt 5.7.1 I found this workaroud : if konsole is executed under strace the problem doesn't occur. So, in KDE Menu Editor you can change "konsole" command into "strace konsole". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 Tsu Janchanged: What|Removed |Added CC||tsujan2...@gmail.com --- Comment #7 from Tsu Jan --- I'm on Linux (Manjaro and Debian). This problem happens only when QtCurve menus are translucent. Then, a freeze occurs when an options dropdown submenu of KFileDialog is supposed to be shown by selecting a menu-item. For me, the only way out of this situation has been ctrl+atl+f2 and restarting sddm manually. Qt5 window translucency requires setting of RGBA format before windows have native handles. QtCurve does it in `Style::prePolish()` and `addAlphaChannel()`, using private headers. Kvantum does the same thing in `Style::setSurfaceFormat()` but without private headers. Now, in Kvantum, I encountered exactly the same freeze ONLY WITH KFileDialog. As a workaround, I excluded menus from `setSurfaceFormat()` because most menus didn't need it for translucency (there are rare exceptions when both WA_WState_Created and WA_NativeWindow are set for a menu, in which case, they don't have translucency in Kvantum). It isn't strange that this only happens with QtCurve because no other Qt5 style engine (except for Kvantum, that has a workaround) supports translucent menus. I haven't read the code of KFileDialog but as far as I know, QtCurve doesn't do anything invalid. Therefore, I think the problem is in KFileDialog. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Ralf Habackerchanged: What|Removed |Added CC||ralf.habacker@saght.tessag. ||com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371858] Occasional wrong desktop at startup
https://bugs.kde.org/show_bug.cgi?id=371858 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 373796] Partition Manager uses different config when not launched from terminal emulator
https://bugs.kde.org/show_bug.cgi?id=373796 --- Comment #5 from Andrius Štikonas--- For version 3.1 I think I'll also pass $HOME environmental variable to keep user home dir and theming. Then config will be stored in ~/.config/ -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 David Edmundsonchanged: What|Removed |Added CC||frederic.ra...@gmail.com --- Comment #170 from David Edmundson --- *** Bug 374580 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369864] Plasma crash when second monitor is plugged
https://bugs.kde.org/show_bug.cgi?id=369864 David Edmundsonchanged: What|Removed |Added CC||jdr...@mailbox.org --- Comment #2 from David Edmundson --- *** Bug 374582 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374580] KDE crashed when establishing kde connection
https://bugs.kde.org/show_bug.cgi?id=374580 David Edmundsonchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 346118 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374582] plasmashell crashed with virtualbox
https://bugs.kde.org/show_bug.cgi?id=374582 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- Thanks. Crash is deep in Qt, please try to keep up-to-date with Qt releases and hopefully it'll get fixed soon. *** This bug has been marked as a duplicate of bug 369864 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 374272] Partition Manager Doesn't Look Like Screenshots (Uses old gui)
https://bugs.kde.org/show_bug.cgi?id=374272 --- Comment #9 from Andrius Štikonas--- For version 3.1 I think I'll also pass $HOME environmental variable to keep user home dir and theming. -- You are receiving this mail because: You are watching all bug changes.