[konqueror] [Bug 356330] New: Konqueror crashed when opening www.faz.net
https://bugs.kde.org/show_bug.cgi?id=356330 Bug ID: 356330 Summary: Konqueror crashed when opening www.faz.net Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: jens.jablon...@gmx.de Application: konqueror (4.14.10) KDE Platform Version: 4.14.10 Qt Version: 4.8.6 Operating System: Linux 4.1.12-1-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I surfed to www.faz.net. Konqueror crashed. I use opensuse 42.1 with QT 5.5.0, plasma 5.4.3 and konqueror 4.14.10 The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f59c879d780 (LWP 25974))] Thread 8 (Thread 0x7f59afe65700 (LWP 25975)): #0 0x7f59c706305f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f59b3617eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f59b3617ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f59c705f0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f59c5d5304d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f596e918700 (LWP 25976)): #0 0x7f59c7065a9d in read () from /lib64/libpthread.so.0 #1 0x7f59c2e9cb60 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f59c2e5b999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f59c2e5bdf8 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f59c2e5bf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f59c7423fde in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7f59c73f5d4f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #7 0x7f59c73f6045 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #8 0x7f59c72f34df in QThread::exec() () from /usr/lib64/libQtCore.so.4 #9 0x7f59c72f5bbf in ?? () from /usr/lib64/libQtCore.so.4 #10 0x7f59c705f0a4 in start_thread () from /lib64/libpthread.so.0 #11 0x7f59c5d5304d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f596d43d700 (LWP 25979)): #0 0x7f59c706305f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f59b338ab3d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f59b363fa06 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f59c705f0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f59c5d5304d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f5953fff700 (LWP 25982)): #0 0x7f59c7065a9d in read () from /lib64/libpthread.so.0 #1 0x7f59c2e9cb60 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f59c2e5b999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f59c2e5bdf8 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f59c2e5bf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f59c7423fde in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7f59c73f5d4f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #7 0x7f59c73f6045 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #8 0x7f59c72f34df in QThread::exec() () from /usr/lib64/libQtCore.so.4 #9 0x7f59c73d7653 in ?? () from /usr/lib64/libQtCore.so.4 #10 0x7f59c72f5bbf in ?? () from /usr/lib64/libQtCore.so.4 #11 0x7f59c705f0a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7f59c5d5304d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f59677fe700 (LWP 26315)): #0 0x7f59c706305f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5946750d79 in ?? () from /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f5946751819 in ?? () from /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f59c705f0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f59c5d5304d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f5967fff700 (LWP 26316)): #0 0x7f59c706305f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5946750d79 in ?? () from /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f5946751819 in ?? () from /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f59c705f0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f59c5d5304d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f59466e9700 (LWP 26317)): #0 0x7f59c706305f in pthread_cond_wait@
[plasmashell] [Bug 356325] Each KDE session manager session save between sessions produces one additional input for xembedsniproxy in ksmserverrc
https://bugs.kde.org/show_bug.cgi?id=356325 Claudio Morales changed: What|Removed |Added CC||claudioantonio.morales11@gm ||ail.com --- Comment #4 from Claudio Morales --- I can confirm I have this same issue too. I'm using openSUSE Leap 42.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 291526] Krita crash at opening file after proposing to recover a backup
https://bugs.kde.org/show_bug.cgi?id=291526 ultmateinfe...@gmail.com changed: What|Removed |Added CC||ultmateinfe...@gmail.com --- Comment #6 from ultmateinfe...@gmail.com --- There's still a problem! It just happened to me and I need the file! -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 356329] New: the is bug when opened editor
https://bugs.kde.org/show_bug.cgi?id=356329 Bug ID: 356329 Summary: the is bug when opened editor Product: parley Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: editor Assignee: parley-bugs-n...@kde.org Reporter: daniel.gomez.1...@gmail.com when I click on editor, whole program closes Reproducible: Always Steps to Reproduce: 1. click on editor Actual Results: whole program closes Expected Results: open editor I have ubuntu 15.04 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.
https://bugs.kde.org/show_bug.cgi?id=356326 Christoph Feck changed: What|Removed |Added Product|kde |kopete CC||hausm...@kde.org Component|general |IRC Plugin Assignee|unassigned-b...@kde.org |kopete-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356305] Ascending/Descending sort arrow reversed
https://bugs.kde.org/show_bug.cgi?id=356305 Christoph Feck changed: What|Removed |Added Assignee|joris.guis...@gmail.com |hugo.pere...@free.fr --- Comment #5 from Christoph Feck --- Oh sorry, I had falsely assumed that Breeze was built on Oxygen code, and had the option already implemented. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356328] Moving the cursor and moving windows leaves drawing artefacts in with the Framebuffer backend
https://bugs.kde.org/show_bug.cgi?id=356328 --- Comment #1 from bluescreen_aven...@verizon.net --- Created attachment 95912 --> https://bugs.kde.org/attachment.cgi?id=95912&action=edit Photo of the drawing artifacts with fbdev -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356328] New: Moving the cursor and moving windows leaves drawing artefacts in with the Framebuffer backend
https://bugs.kde.org/show_bug.cgi?id=356328 Bug ID: 356328 Summary: Moving the cursor and moving windows leaves drawing artefacts in with the Framebuffer backend Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend-fbdev Assignee: kwin-bugs-n...@kde.org Reporter: bluescreen_aven...@verizon.net It seems that by switching the false in FramebufferQPainterBackend::needsFullRepaint() const to true fixes this issue. not sure if it's false for performance reasons... but the one for the wayland backend seems to set needsFullRepaint to true... Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356327] Cpp parser doesn't act when I remove global member
https://bugs.kde.org/show_bug.cgi?id=356327 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 95911 --> https://bugs.kde.org/attachment.cgi?id=95911&action=edit simple test project -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356327] New: Cpp parser doesn't act when I remove global member
https://bugs.kde.org/show_bug.cgi?id=356327 Bug ID: 356327 Summary: Cpp parser doesn't act when I remove global member Product: kdevelop Version: 4.90.90 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com There is following code: header: #include class MyClass { public: /** This function something do. * @param pointer some pointer * @param string some string */ MyClass( int *pointer, const QString &string ); private: bool m_bSomeGlobalMember; }; definition: #include "myclass.h" MyClass::MyClass( int *pointer, const QString &string ) { int *localPointer = pointer; QString localString = string; bSomeGlobalMember = true; } When I remove member "bSomeGlobalMember" from header file then in cpp properly line(s) are not marked as incorrect only changes color to dark red. Problem view doesn't report any problem. Case 1: When I back to header and restore just removed member pressing Ctrl+Z then switching to cpp I will have correct color of member. Please note that in bigger (then 2 files) project it might take more time or doesn't work properly just leaving wrong coloring. I experienced it in my own project. It was really annoying. I had to close KDevelop, remove cache and start KDevelop again to have correctly parsed file :-/. Case 2: I don't restore member in header, but I'm starting write something, for example, in last empty line of constructor. Parser wakes up and I get marks line where is used removed member. Reproducible: Always Steps to Reproduce: 1. Being in header please remove member "bSomeGlobalMember" just pressing Ctrl+K (remove line) on this line. 2. Please switch to cpp file and look at removed in header member. Actual Results: Member changes color to dark red. There is no reported error in Problem view. Expected Results: Every use of member should be marked as error. In Problem view should be reported such problem. KDevelop and KDevplatform cloned at December 5-th 2015. Branch "5.0". I attach package containing simple project. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #9 from Chris Jones --- Well, all I know is this: If I start with a 16 bit image using the default colour profile (sRGB-elle-V2-g10.icc (Default)), and I change it to 8 bit, the profile automatically changes to sRGB-elle-v2-srgbtrc.icc, which produces incorrect results. If I change it back to sRGB-elle-V2-g10.icc (Default) before converting though, it produces correct results. So unless it has adverse ramifications elsewhere, it would seem that when starting with 16 bit using the default profile, it should stay that way when converting to 8 bit. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #8 from wolthera --- Ah! Sorry. Well, maybe? Or maybe not? We are having a ball deciding the best behaviour that avoids people coming to us to tell us their images look strange. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #7 from wolthera --- I'm not sure, but perhaps a solution would be for the "Profile" section of the "Convert Image Color Space" panel to switch to a srgbtrc.icc colour profile when "Depth" is changed from 16 Bit to 8 Bit? < it should already be doing this. Isn't it? You should be careful with what is causing it now(and make sure to watch the optimisations checkbox). 1. 16bit linear to/from 8bit linear should give the same results, only with banding in the dark shades. 2. 16bit srgbtrc to/from 8bit srgbtrc should give the same results as well. 3. 16bit/8bit linear to/from 16bit/8bit srgbtrc, should give different results. (But it may be that the cache isn't updated yet, so toggle the layer visibility maybe?) Everything else is a bug. The overlay thing is something I'll need to ask boud the specifics about, I am curious what ps is doing there :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356325] Each KDE session manager session save between sessions produces one additional input for xembedsniproxy in ksmserverrc
https://bugs.kde.org/show_bug.cgi?id=356325 --- Comment #3 from Fero Hrach --- Yast shows me plasma-framework 5.16.0-3.1 . If this is not required info, please write me help, how do get Plasma version. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #6 from Chris Jones --- Wait a sec - that's what it does already! Sorry, getting confused. :) When I select 8 Bits in the "convert Image Color Space" panel, it also automatically changes the Profile to sRGB-elle-v2-srgbtrc.icc - and maybe that's the problem right there. Shouldn't it retain the same profile that the image already uses? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #5 from Chris Jones --- Same results after looking at the color management page. Photoshop does produce solid white when using 8 bit, as does Krita. I can confirm that using Photoshop's default settings on a 16 bit image does not produce solid white (as I have now come to realise is normal behaviour), although it's using a different default colour profile to Krita so it produces a lighter shade of grey. The key difference though is that it doesn't change anything when converting to 8 bit, which I think is the fundamental issue here. I'm not sure, but perhaps a solution would be for the "Profile" section of the "Convert Image Color Space" panel to switch to a srgbtrc.icc colour profile when "Depth" is changed from 16 Bit to 8 Bit? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356326] New: Code in kdenetwork is licensed under the non-free ARTISTIC license.
https://bugs.kde.org/show_bug.cgi?id=356326 Bug ID: 356326 Summary: Code in kdenetwork is licensed under the non-free ARTISTIC license. Product: kde Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dwort...@mykolab.com I am a volunteer working on gNewSense, a free ( as defined by the Free Software Foundation (FSF)) GNU/Linux distro where the next version (4) will be based on Debian Wheezy. We noticed that KDE has dependencies on the Artistic License 1.0 which the FSF does not regard as free or is at least ambiguous (https://www.gnu.org/licenses/license-list.html#NonFreeSoftwareLicenses) and they encourage use of the Artistic License 2.0 (https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses). Specifically we noticed in /kdenetwork-4.8.4/kopete/protocols/irc/ksparser.h (the kdenetwork package for Debian Wheezy) /* This file is part of the KDE project Copyright (C) 2001 Simon Hausmann This program is free software; you can redistribute it and/or modify it under the terms of the Artistic License. */ Can the license be changed to "Artistic 2.0 License" instead of "Artistic License"? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #4 from wolthera --- The solid white thing is something inherit in the overlay algorithm as referenced from the official Adobe PDF documentation. If you can't reproduce it with photoshop, mypaint or even the css blending modes, then we have a problem(Gimp's overlay algorithm has been non-standard for a whole version or two, should be fixed in 2.8). I need you to do something really really dumb. Could you go to settings->configure Krita->color management. And then just -look- at the page and press ok. Then try to reproduce your bug? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #3 from Chris Jones --- Correction: the default settings use 8 bit - the problem begins when starting with a 16 bit image (as I typically do). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it
https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #9 from Philippe Waroquiers --- An additional note: on x86 linux, valgrind gdbserver only reports the Xfer:features:read+ supported if --vgdb-shadow-registers=yes is given. On amd64 linux, Xfer:features:read+ is reported as supported if either shadow registers are requested or if the host has avx register. Otherwise, valgrind gdbserver expects that the debugger knows the register layout of x86 or amd64. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356317] Only a black screen after login on Fedora Rawhide with Plasma 5.4.95
https://bugs.kde.org/show_bug.cgi?id=356317 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied
https://bugs.kde.org/show_bug.cgi?id=347602 Andreas changed: What|Removed |Added CC||ads-kde-b...@wars-nicht.de --- Comment #28 from Andreas --- I have the same problem. The "Updates" icon remains red even after all updates are applied (and no reboot is required). If I click on the icon, it tells me that there are no remaining updates. System is 15.10, fresh install. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #2 from Chris Jones --- I'm using 16 bit with sRGB-elle-V2-g10.icc (Default), and converting to 8 bit sRGB-elle-V2-g10.icc (Default). If I convert to 8 bit sRGB-elle-v2-srgbtrc.icc as you suggest, it still changes the opacity. If I start with a 16 bit sRGB-elle-v2-srgbtrc.icc however, it does stay the same after converting to 8 bit. This suggests to me that the issue then is that the default settings cause things to change unexpectedly when converting the colour depth, and if the default settings were used to begin with, there is no apparent way within Krita to do this without affecting the appearance of layers using Overlay. Also, I haven't tested all of the colour profiles (there are a lot of them!), but so far none of the ones I've tested seem to allow solid white when using Overlay. Do any of them? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356325] Each KDE session manager session save between sessions produces one additional input for xembedsniproxy in ksmserverrc
https://bugs.kde.org/show_bug.cgi?id=356325 David Edmundson changed: What|Removed |Added Severity|grave |normal Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from David Edmundson --- Can you confirm your version number of Plasma -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it
https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #8 from Philippe Waroquiers --- I already committed (svn 15743) the support for qC (slightly modified patch). With this, lldb somewhat works on debian8/x86 or Ubuntu14/amd64 (e.g. continue till a breakpoint works). However, in both environments, I encounter several things not working: * unwind and/or frame discovery seems to not work properly. e.g. bt shows an empty frame: * thread #1: tid = 29071, , stop reason = signal SIGTRAP * frame #0: register read gives an error (lldb) register read error: invalid frame Despite the fact that valgrind gdbserver tells qXfer:features:read+; is supported, lldb does not send requests to read the target description. Finally, it is not very clear how to send monitor commands from lldb. 'process plugin packet monitor v.info scheduler' sends the command v.info scheduler, but the behaviour is strange: * the first output line is shown (encoded in protocol layout). * then if continue is given, the rest of the output is shown properly. Note that the Hc-1 handling seems not very critical, but applying the patch does not improve the above in any case. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 315702] Export button in kinfocenter is always inactive
https://bugs.kde.org/show_bug.cgi?id=315702 --- Comment #6 from Christopher Yeleighton --- The Export button in the button bar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356325] Each KDE session manager session save between sessions produces one additional input for xembedsniproxy in ksmserverrc
https://bugs.kde.org/show_bug.cgi?id=356325 --- Comment #1 from Fero Hrach --- One correction as for VirtualBox - it declared, there is NO HW support for 3D display acceleration. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356325] New: Each KDE session manager session save between sessions produces one additional input for xembedsniproxy in ksmserverrc
https://bugs.kde.org/show_bug.cgi?id=356325 Bug ID: 356325 Summary: Each KDE session manager session save between sessions produces one additional input for xembedsniproxy in ksmserverrc Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: XembedSNIProxy Assignee: plasma-b...@kde.org Reporter: hra...@post.sk Using openSUSE Leap 42.1 64bit. When KDE session is saved (manuallly or automatically at logout), to .config/ksmserverrc is added one additional entry for xembedsniproxy. Empty session starts with one xembedsniproxy process setup 2302 2205 0 22:40 ?00:00:00 /usr/bin/xembedsniproxy After saving session, logout and login back we see setup 2302 2205 0 22:40 ?00:00:00 /usr/bin/xembedsniproxy setup 2307 2205 0 22:40 ?00:00:00 /usr/bin/xembedsniproxy -session 101751ea1a41a14492695110017930005_1449269813_757803 In .config/session there is no file entry xembedsniproxy_101751ea1a41a14492695110017930005_1449269813_757803 When in this state is session saved again, after logout and login we can see 3 xembedsniproxy processes. One without parameter and 2 with "-session" parameter. In .config/session there is no file entry starting with xembedsniproxy. This behaviour is big problem, when user configured automatic session save on logout. In my case I had after ca 1 moth of Linux usage ca 100 xembedsniproxy processes at session start and it caused various problems in system - KDE applications cannot be started, kdeinit5 randomly crashed after login, VirtualBox said there is HW support for 3D display acceleration. Reproducible: Always Steps to Reproduce: 1. Save KDE session (manually or automatic save on logout) 2. Logout and login back 3. Again save KDE session (manually or automatic save on logout) Actual Results: Number of xembedsniproxy processes grows. From some point in time system has various problems (KDe applications do not start, kdeinit5 randomly crashed after login, VirtualBox said there is HW support for 3D display acceleration) Expected Results: KDE session save will include only one xembedsniproxy entry. After start there will be only one xembedsniproxy process - same behaviour as if empty session is started. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 339967] Plasma 5 default component settings don't affect KDE4 apps
https://bugs.kde.org/show_bug.cgi?id=339967 Aranjedeath changed: What|Removed |Added CC||orangewi...@gmail.com --- Comment #12 from Aranjedeath --- (In reply to David Edmundson from comment #11) > I pushed a fix for 5.3 that should fix this. It didn't. I'm on Kubuntu (latest updates installed), which should put me on 5.4.2 or 5.4.3, and I have set chrome as default in both kde 4 and kde 5 (using command in comment 5). the make-default-browser button does nothing in chrome. Links (for example opened in Contacts (or whatever the chat app is called -- not konversation)) open in firefox, even though both kde4 and kde5 default browser menus say to open in chrome. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356322] Black screen after login, mouse pointer visible
https://bugs.kde.org/show_bug.cgi?id=356322 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=328718, ||https://bugs.kde.org/show_b ||ug.cgi?id=349219 --- Comment #1 from Thomas Lübking --- lacks debug symbols, but looks quite like bug #328718 or bug #349219 => Please attach the output of "glxinfo" and (when running, composited) the output of "qdbus org.kde.KWin /KWin supportInformation" Though, KWin crash does not explain "black empty screen", sounds as if plasma-desktop crashes as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 328718] KWin
https://bugs.kde.org/show_bug.cgi?id=328718 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356322 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 349219] logged in and kwin crashed
https://bugs.kde.org/show_bug.cgi?id=349219 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356322 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356324] Notes settings button is invisible.
https://bugs.kde.org/show_bug.cgi?id=356324 Kai Uwe Broulik changed: What|Removed |Added Product|kdeplasma-addons|plasmashell Component|notes |Theme - Breeze Assignee|plasma-b...@kde.org |visual-des...@kde.org CC||k...@privat.broulik.de, ||plasma-b...@kde.org Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #35 from Piotr Mierzwinski --- I tried to reproduce it (including cache located on ram disk) using KDevelop 4.90.90 (cloned at 30.11.2015, run on Kubuntu 15.10, Plasma 5 session) and here all is working fine. "Find uses" function found all matching occurrences of "currentFileName()" and finished with success. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 356324] New: Notes settings button is invisible.
https://bugs.kde.org/show_bug.cgi?id=356324 Bug ID: 356324 Summary: Notes settings button is invisible. Product: kdeplasma-addons Version: 5.4.3 Platform: Other URL: http://imgur.com/y2B0kOA OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: notes Assignee: plasma-b...@kde.org Reporter: gaanto...@civil.auth.gr There is a button located bottom right in notes widget that opens the settings dialog and is invisible with every plasma theme. See screenshot. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356317] Only a black screen after login on Fedora Rawhide with Plasma 5.4.95
https://bugs.kde.org/show_bug.cgi?id=356317 --- Comment #2 from Mustafa Muhammad --- Now I tested on F23 with 5.4.95 copr and it works fine, probably Rawhide problem, not Plasma. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 356323] New: Auto-completion intervenes with calculator results.
https://bugs.kde.org/show_bug.cgi?id=356323 Bug ID: 356323 Summary: Auto-completion intervenes with calculator results. Product: krunner Version: 5.4.3 Platform: Other URL: http://www.mediafire.com/watch/ue0d2btn1ap8fhv/vokoscr een-2015-12-05_23-16-31.mkv OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: calculator Assignee: m...@vhanda.in Reporter: gaanto...@civil.auth.gr Please watch the video Reproducible: Always Steps to Reproduce: 1. Show coords with marble, ie: 40.780211, 23.189253 2. type 80/2 press Enter Actual Results: krunner shows the coords Expected Results: it should display 40 since I chose the calculator result. Note, there is no indication that, that would happen, autocompletion did not show any highlighted text. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 296526] Dolphin is too slow when upload a file on a SSH server
https://bugs.kde.org/show_bug.cgi?id=296526 --- Comment #4 from Andreas Schneider --- We do not have an async sftp upload API yet. It is on the TODO list ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356322] New: Black screen after login, mouse pointer visible
https://bugs.kde.org/show_bug.cgi?id=356322 Bug ID: 356322 Summary: Black screen after login, mouse pointer visible Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jura@gmail.com Application: kwin (4.11.20) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-24-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Normal system boot. - Unusual behavior I noticed: After login there was just a black screen. The mouse pointer was visible but there was nothing to click on. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5a2d269800 (LWP 1739))] Thread 2 (Thread 0x7f5a0d802700 (LWP 1743)): #0 0x7f5a26a6805f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5a2bc958cb in () at /usr/lib64/libQtScript.so.4 #2 0x7f5a2bc95909 in () at /usr/lib64/libQtScript.so.4 #3 0x7f5a26a640a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5a2ca9408d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f5a2d269800 (LWP 1739)): [KCrash Handler] #5 0x7f5a2c9e4187 in raise () at /lib64/libc.so.6 #6 0x7f5a2c9e5538 in abort () at /lib64/libc.so.6 #7 0x7f5a2c9dd126 in __assert_fail_base () at /lib64/libc.so.6 #8 0x7f5a2c9dd1d2 in () at /lib64/libc.so.6 #9 0x7f5a2a892a39 in () at /usr/lib64/libX11.so.6 #10 0x7f5a2a892acc in () at /usr/lib64/libX11.so.6 #11 0x7f5a2a892d9d in _XEventsQueued () at /usr/lib64/libX11.so.6 #12 0x7f5a2a895a45 in _XGetRequest () at /usr/lib64/libX11.so.6 #13 0x7f5a278e56ce in () at /usr/lib64/libGL.so.1 #14 0x7f5a27b4c9d4 in KWin::checkGLError(char const*) () at /usr/lib64/libkwinglutils.so.1 #15 0x7f5a2ce35a73 in () at /usr/lib64/libkdeinit4_kwin.so #16 0x7f5a2ce35d07 in () at /usr/lib64/libkdeinit4_kwin.so #17 0x7f5a2ce1a843 in () at /usr/lib64/libkdeinit4_kwin.so #18 0x7f5a26e143b1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #19 0x7f5a25f7876c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #20 0x7f5a25f7ecad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #21 0x7f5a2b6e8e0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #22 0x7f5a26dfc2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #23 0x7f5a26e2bcbc in () at /usr/lib64/libQtCore.so.4 #24 0x7f5a26e2cd18 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #25 0x7f5a26015f96 in () at /usr/lib64/libQtGui.so.4 #26 0x7f5a26dfae6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #27 0x7f5a26dfb165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #28 0x7f5a26e005b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #29 0x7f5a2cdd47a3 in kdemain () at /usr/lib64/libkdeinit4_kwin.so #30 0x7f5a2c9d0b05 in __libc_start_main () at /lib64/libc.so.6 #31 0x0040075e in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 356134] kxmlgui.xsd does not allow "append" attribute in element "Separator"
https://bugs.kde.org/show_bug.cgi?id=356134 --- Comment #2 from Allen Winter --- https://git.reviewboard.kde.org/r/126253/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #33 from Piotr Mierzwinski --- Created attachment 95909 --> https://bugs.kde.org/attachment.cgi?id=95909&action=edit Find_uses-memory_usage1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #34 from Piotr Mierzwinski --- Created attachment 95910 --> https://bugs.kde.org/attachment.cgi?id=95910&action=edit Find_uses-memory_usage2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #32 from Piotr Mierzwinski --- Created attachment 95908 --> https://bugs.kde.org/attachment.cgi?id=95908&action=edit "Find uses" hungs with 25% -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #31 from Piotr Mierzwinski --- Hmm. I think you told me that in KDevelop 5 there is pretty new parser based on clang, so I thought this is new code. Never mind. Maybe not all is new. What do you mean saying "another oldcpp bug"? Here, in Mageia 5, I have installed "libstdc++6-4.9.2-4.1.mga5" is this "oldcpp"? Or you mean oldcpp plugin in KDevelop? Back to test. OK. I tried to reproduce it again using this time test case from Bug 353905 (marked as duplicate) with KDevelop-4.7.2 on Mageia 5 (on real machine, but it happen also in VirtualBox 5). I will say at the outset that my KDevelop cache is placed on the ram disk, so I have linked "~/.cache/kdevduchain" to /tmp/piotr-kdevduchain. I'm not sure if this is important, but maybe will help. Going further. Before running the test I removed kdevduchain cache (of course KDevelop wasn't running in this moment) - it was session directory calling: "kdevelop-{e4d7275a-9f43-4eb0-a9cb-f5cb819a0df5}". Time for the steps (a bit improved comparing mentioned bug report): 1. Run KDevelop with my project (qtcmd2) and only opened src/filelistview.cpp 2. When cache has been generated. Find (using shortcut Ctrl+Alt+N) following method: slotOpenSelected 3. Find following line: "m_sLastSelectedItemName = currentFileName();" (the way of looking doesn't matter) Note, In this function there are two occurrences such assignment and in my test I used second one, which is placed couple of lines below first one. 4. Move cursor on the "currentFileName()" (second occurrence) 5. Invoke "Show uses" KDevelop doesn't crash, but parser does something through for a while and stops on 25% (see attachment) or 0% (happened when I repeat test). Anyway I was waiting till finished about 10-15 min. and nothing changed. So I started to invoked other "Find uses" on other functions located in slotOpenSelected, for example: "slotBreakCurrentOperation" - no result, "openSelectedItemsWith" - no result, "numberOfSelectedItems" - no result. Code browser still empty. Only I can see that KDevelop uses a lot of CPU: PID USER PRI NI VIRTRES SHR S CPU% MEM% TIME+ Command 1076 piotr 20 0 1476M 1076M 77624 S 69.36.7 12:58.44 /usr/bin/kdevelop 1188 piotr 20 0 1476M 1076M 77624 S 16.46.7 4:04.99 /usr/bin/kdevelop 1097 piotr 20 0 1476M 1076M 77624 S 11.66.7 3:54.56 /usr/bin/kdevelop 1182 piotr 20 0 1476M 1076M 77624 R 40.76.7 3:53.70 /usr/bin/kdevelop And still allocates more and more memory. Please take a look at the screen shots. Second one I made several dozen after first one. I have now 16GB ram and swap, so I will wait a while till free memory finished and then probably KDevelop crashed. In a moment of original test I had only 4GB, so it happened a bit faster. Anyway when I closed KDevelop then I get "KDevelop crash window" - using to send crash report. I didn't attach report, because it told me that I have not enough information for programmers (despite I have installed debug packages). I know that I should to run KDevelop in gdb If I want to get the backtrace from the crash. I think it should finish ("Find uses" operation) really quickly, because I have now quite strong hardware (Core i7-6700 Skylake + 16GB ram). Before (in a moment of original test) I had AMD Phenom II X4 955 + 4GB and happened the same. OK. Sometime KDevelop crashed faster. When I was using 4.7.1 version I didn't observe such behavior. KDevelop either worked (all were found) or crashed, but didn't parser stop like this and allocated memory without end. Because this test based on my project I remind its location: git://git.qtcmd.org/qtcmd2.git Sorry, my test is not some simply one-file project. I didn't test this with other project. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 356133] crash when starting - segmentation fault
https://bugs.kde.org/show_bug.cgi?id=356133 Cyril Brosch changed: What|Removed |Added CC||i...@cyrilbrosch.net --- Comment #2 from Cyril Brosch --- I confirm. Kamoso crashes when USB webcam is plugged it, but it starts when it is not plugged in (plugin it in afterwards does nothing, but trying to get a picture then crashes Kamoso again). gdb gives me just the following output: #0 0x0041a9d0 in WebcamControl::play(Device*) () #1 0x0041b680 in WebcamControl::WebcamControl() () #2 0x004129fc in main () -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 343255] Kate 5 saving with another encoding is missing
https://bugs.kde.org/show_bug.cgi?id=343255 Daimonion changed: What|Removed |Added CC||de...@krutt.org --- Comment #10 from Daimonion --- Ktexteditor 5.16.0, encoding menu on file save dialog is missing again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356321] New: OpenSuse 42.1 plasma desktop crash
https://bugs.kde.org/show_bug.cgi?id=356321 Bug ID: 356321 Summary: OpenSuse 42.1 plasma desktop crash Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rtp...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.0 Operating System: Linux 4.1.12-1-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: trying to create a link-to-application. - Unusual behavior I noticed: when the create dlg appears, there are only 2 tabs (general and permissions). No place to specify the program. If cancel is used, that's OK. But OK killed desktop. Saw this message after OK clicked The file or folder :/kio5/newfile-templates/.source/Program.desktop does not exist. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94185fc7c0 (LWP 2089))] Thread 9 (Thread 0x7f9402055700 (LWP 2090)): #0 0x7f9411b57c1d in poll () at /lib64/libc.so.6 #1 0x7f9416a7e422 in () at /usr/lib64/libxcb.so.1 #2 0x7f9416a8000f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f94041a5c29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f941224e55f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f94113610a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f9411b6004d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f93fafca700 (LWP 2125)): #0 0x7ffed2795b26 in clock_gettime () #1 0x7f9411b6cc9d in clock_gettime () at /lib64/libc.so.6 #2 0x7f94122feb06 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f941247e089 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f941247e615 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f941247f82e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f940e2384ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f940e238d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f940e238f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f941247fa5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f9412426a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f941224984a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f94155325f8 in () at /usr/lib64/libQt5Qml.so.5 #13 0x7f941224e55f in () at /usr/lib64/libQt5Core.so.5 #14 0x7f94113610a4 in start_thread () at /lib64/libpthread.so.0 #15 0x7f9411b6004d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f93ed5bf700 (LWP 2129)): #0 0x7f941136505f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f93f39f8e53 in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f93f39f85d7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f94113610a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9411b6004d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f93e78ef700 (LWP 2130)): #0 0x7f9411b57c1d in poll () at /lib64/libc.so.6 #1 0x7f940e238e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f940e238f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f941247fa5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9412426a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f941224984a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f94155325f8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f941224e55f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f94113610a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f9411b6004d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f93e5ee9700 (LWP 2140)): #0 0x7ffed2795b26 in clock_gettime () #1 0x7f9411b6cc9d in clock_gettime () at /lib64/libc.so.6 #2 0x7f94122feb06 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f941247e089 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f941247e615 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f941247f82e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f940e2384ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f940e238d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f940e238f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f941247fa5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f9412426a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f94
[kmail2] [Bug 355498] Kmail 4.14.9 Error notification "Multiple merge candidates. aborting" after clicking "check mail" for an imap source
https://bugs.kde.org/show_bug.cgi?id=355498 d...@newtech.fi changed: What|Removed |Added CC||d...@newtech.fi --- Comment #2 from d...@newtech.fi --- Exactly the same problem here with the same version -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356304] Kate Crashes On Startup
https://bugs.kde.org/show_bug.cgi?id=356304 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- On KF5 configs are in ~/.local not ~/.kde -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 356320] New: Kopete history logs import not work.
https://bugs.kde.org/show_bug.cgi?id=356320 Bug ID: 356320 Summary: Kopete history logs import not work. Product: telepathy Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: log-viewer Assignee: kde-telepathy-b...@kde.org Reporter: flate...@atlas.cz Hello, I can't import my Kopete history to the KDE Telepathy. When I add new accouts (Jabber, ICQ) in to the Online Accouns and start ktp-log-viewer, click to "Logs -> Import Kopete logs" I see only dialog "No Kopete Logs Found" and nothing happens. Tested with clean profile and with changed InitialKopeteImportDone param to false in ~/.config/ktp-log-viewerrc. Distro: Archlinux (kde-unstable/testing repo) Telepathy-kde version: 15.11.90 Plasma version: 5.4.95 KF5 version: 5.16.0 Old Kopete logs dir: ~/.kde4/share/apps/kopete/logs/ $cat .config/ktp-log-viewerrc [MainWindow] State=/wD9AoHFBAQICPwA ToolBarsMovable=Disabled [logs] InitialKopeteImportDone=true -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 356319] New: Download time not being computed correctly
https://bugs.kde.org/show_bug.cgi?id=356319 Bug ID: 356319 Summary: Download time not being computed correctly Product: ktorrent Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mark.ray...@gmail.com When I have multiple downloads in process the first download time is computed correctly but the second or third computation time is always incorrect. Reproducible: Always Steps to Reproduce: 1.Do multiple concurrent downloads 2.Watch computed download times 3. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356316] 15.11.90: split view button does not update clip view when last action was in timeline
https://bugs.kde.org/show_bug.cgi?id=356316 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kden ||live/f1726ffcc7dd4fc10f15e0 ||212d6ae0ddfd0e8018 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit f1726ffcc7dd4fc10f15e0212d6ae0ddfd0e8018 by Jean-Baptiste Mardelle. Committed on 05/12/2015 at 18:51. Pushed by mardelle into branch 'Applications/15.12'. Refresh monitor when compare effect is activated M +1-1src/monitor/monitor.cpp http://commits.kde.org/kdenlive/f1726ffcc7dd4fc10f15e0212d6ae0ddfd0e8018 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 336089] Font preview - rendering problem
https://bugs.kde.org/show_bug.cgi?id=336089 d...@kaosx.us changed: What|Removed |Added CC||d...@kaosx.us -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355918] Plasma panel sometimes don't respect "autohide" option in plasma/layout-templates/*/contents/layout.js
https://bugs.kde.org/show_bug.cgi?id=355918 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Same bug as we had for min, max length. Will fix, thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356264] Plasma crash when disconnecting external screens (docking station)
https://bugs.kde.org/show_bug.cgi?id=356264 David Edmundson changed: What|Removed |Added CC||flywh...@illogical.dk --- Comment #2 from David Edmundson --- *** Bug 356302 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356302] P crashed when doing nothing
https://bugs.kde.org/show_bug.cgi?id=356302 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 356264 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356318] New: I can run wayland plasma session from terminal, not from sddm
https://bugs.kde.org/show_bug.cgi?id=356318 Bug ID: 356318 Summary: I can run wayland plasma session from terminal, not from sddm Product: plasmashell Version: 5.4.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mustafa10...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Using openSUSE Tumbleweed with latest Plasma from openSUSE KDE repos (following git), I can start (and use) wayland session from terminal, but not from sddm. If I try to log into Plasma on wayland, sddm looks freezed and I only have a mouse curser moving. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355936] 15.11.90: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 wegwerf-1-...@gmx.de changed: What|Removed |Added Summary|15.11.80: Spacer tool moves |15.11.90: Spacer tool moves |transitions of locked |transitions of locked |tracks |tracks -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355380] 15.11.90: deleting topmost track with clip with transition does leave transition behind
https://bugs.kde.org/show_bug.cgi?id=355380 wegwerf-1-...@gmx.de changed: What|Removed |Added Summary|15.11.80: deleting topmost |15.11.90: deleting topmost |track with clip with|track with clip with |transition does leave |transition does leave |transition behind |transition behind -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356317] Only a black screen after login on Fedora Rawhide with Plasma 5.4.95
https://bugs.kde.org/show_bug.cgi?id=356317 --- Comment #1 from Mustafa Muhammad --- Tested on bare metal (Intel GPU), and KVM virtual machine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356317] New: Only a black screen after login on Fedora Rawhide with Plasma 5.4.95
https://bugs.kde.org/show_bug.cgi?id=356317 Bug ID: 356317 Summary: Only a black screen after login on Fedora Rawhide with Plasma 5.4.95 Product: plasmashell Version: 5.4.95 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mustafa10...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org After updating to 5.4.95, after login there is no panel and no desktop, only black space, I can still run applications using krunner. Reproducible: Always Steps to Reproduce: 1. Use an up to date Fedora Rawhide 2. Login to Plasma 3. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356316] New: 15.11.90: split view button does not update clip view when last action was in timeline
https://bugs.kde.org/show_bug.cgi?id=356316 Bug ID: 356316 Summary: 15.11.90: split view button does not update clip view when last action was in timeline Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de When toggling the split view button in the clip view it does not update the clip view when the last action was in the timeline; that is, the timeline was "selected" and "has the focus". Reproducible: Always Steps to Reproduce: 1. Create new Kdenlive project 2. Add video clip to project bin 3. Add clearly visible effect to clip in project bin; charcoal will do. 4. Drag clip also into timeline. 5. Click anywhere into timeline. 6. Click on "split view" button in clip view. Actual Results: Clip monitor does not update to show split view or non-split view. Expected Results: Clip monitor should update to show either split view or non-split view. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356316] 15.11.90: split view button does not update clip view when last action was in timeline
https://bugs.kde.org/show_bug.cgi?id=356316 wegwerf-1-...@gmx.de changed: What|Removed |Added CC||wegwerf-1-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356315] 15.11.90: project monitor has no split view icon, while clip monitor has
https://bugs.kde.org/show_bug.cgi?id=356315 wegwerf-1-...@gmx.de changed: What|Removed |Added CC||wegwerf-1-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356315] New: 15.11.90: project monitor has no split view icon, while clip monitor has
https://bugs.kde.org/show_bug.cgi?id=356315 Bug ID: 356315 Summary: 15.11.90: project monitor has no split view icon, while clip monitor has Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de The clip monitor has a "split view" icon in its tool bar along its bottom. In contrast, the project monitor doesn't have a "split view" icon it its tool bar. For reasons of similarity and thus user expectation wouldn't it be better to have the same tool icons in both monitor as long as they make sense in a particular monitor? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356314] 15.11.90: split view does not work in project monitor
https://bugs.kde.org/show_bug.cgi?id=356314 wegwerf-1-...@gmx.de changed: What|Removed |Added CC||wegwerf-1-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356314] New: 15.11.90: split view does not work in project monitor
https://bugs.kde.org/show_bug.cgi?id=356314 Bug ID: 356314 Summary: 15.11.90: split view does not work in project monitor Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de While the "split view" function works in the clip monitor as intended, it doesn't work correctly in the project monitor. The outcome of enabling "split view" in the project monitor depends on the project and vary: 1. no indication of split view at all, albeit a clearly visible effect is present in both a clip in the timeline or alternatively on the same timeline clip in the project bin. 2. quarter view, mostly black, with a changing quarter showing the project view. During playback, which quarter of the project monitor is used changes also. Reproducible: Always Steps to Reproduce: 1. Create new Kdenlive project. 2. Add any video clip to the project bin. 3. Add this clip to the timeline. 4. Add "Charcoal" effect or any other video effect yielding clearly visible effects. 5. In the project view choose "split view" Actual Results: Varies: 1. No visible change at all. 2. quarter-size project view image, the rest of the project monitor is black. The quarter used may change during project playback. Expected Results: Split view to show "uneffected" clip as well as clip effects side-by-side, as does the clip monitor in split view mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351425] Make the "windows" in taskbar smaller
https://bugs.kde.org/show_bug.cgi?id=351425 jeremy9...@gmail.com changed: What|Removed |Added Summary|Add the possibility to make |Make the "windows" in |the "windows" in taskbar|taskbar smaller |smaller | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356313] New: Deleting empty track while two clips in timeline are grouped causes delayed crash
https://bugs.kde.org/show_bug.cgi?id=356313 Bug ID: 356313 Summary: Deleting empty track while two clips in timeline are grouped causes delayed crash Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: qubo...@gmail.com catalyst-libgl 15.11-1 ffmpeg 1:2.8.3-1 ffmpeg-compat 1:0.10.16-4 mlt 0.9.8-3 qt5-base 5.5.1-3 xorg-server 1.16.4-1 v15.11.90-21-g5a606d4 * Applications/15.12 Steps to reproduce: 1. Start kdenlive 2. RClick project bin and add color clip, press OK in popup window 3. Drag clip to Video 2 track twice (next to each other) 4. Ctrl+A to select both clips 5. Right-click one of them and select "group clips" 6. Right click the control panel of Video 1 track and select "delete track", press OK in popup window 7. Don't do anything, wait for 5 seconds Expected result: 1. Video 1 track gets deleted 2. Nothing else happens Actual result: 1. Video 1 track gets deleted 2. After a short delay, Kdenlive crashes GDB: Program received signal SIGSEGV, Segmentation fault. 0x716cb596 in ?? () from /usr/lib/libQt5Widgets.so.5 BT: #0 0x716cb596 in ?? () from /usr/lib/libQt5Widgets.so.5 #1 0x716c0f8f in QGraphicsItem::childItems() const () from /usr/lib/libQt5Widgets.so.5 #2 0x004e2d64 in ClipManager::groupsXml() const () #3 0x0049eaa8 in KdenliveDoc::groupsXml() const () #4 0x004f56e8 in ProjectManager::prepareSave() () #5 0x004f55d4 in ProjectManager::slotAutoSave() () #6 0x00826f18 in ProjectManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () #7 0x7fffef5f512a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #8 0x7fffef602048 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQt5Core.so.5 #9 0x7fffef5f5fa3 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x713bd01c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #11 0x713c24f6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7fffef5c69ab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7fffef61c16d in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #14 0x7fffef61c671 in ?? () from /usr/lib/libQt5Core.so.5 #15 0x7fffeb7a0dc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0x7fffeb7a1020 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0x7fffeb7a10cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #18 0x7fffef61d34f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #19 0x7fffef5c437a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #20 0x7fffef5cc33c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #21 0x007bf8b1 in main () Instead of creating and grouping two clips, you can also import a video with audio, place it in timeline and split it (both clips will be grouped by default). It appears to be important that you delete a track that is not occupied by one of the group elements to trigger this bug. Video: https://youtu.be/b2PERiv4vhY -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 352779] Akonadi significantly slow down the login process.
https://bugs.kde.org/show_bug.cgi?id=352779 Daniel Eklöf changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #10 from Daniel Eklöf --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 352779] Akonadi significantly slow down the login process.
https://bugs.kde.org/show_bug.cgi?id=352779 Daniel Eklöf changed: What|Removed |Added CC||dan...@ekloef.se -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer
https://bugs.kde.org/show_bug.cgi?id=355569 --- Comment #15 from bluescreen_aven...@verizon.net --- I added lines +qWarning() << "Bytes Per Line: " << backend->bytesPerLine(); +qWarning() << "Buffer Size: " << backend->bufferSize(); +qWarning() << "Bits Per Pixel: " << backend->bitsPerPixel(); in QEMU: Bytes Per Line: 3072 Buffer Size: 2359296 Bits Per Pixel: 24 It also seems that that qpainter debug message happens with: QPainter p(&m_backBuffer); judging by the debug lines I threw into it. On intel box Bytes Per Line: 5120 Buffer Size: 4096000 Bits Per Pixel: 32 ...and now for some reason this time after realizing I should set my Framebuffer to be 32 bits, it worked in QEMU too (I must have been mistaken somewhere, as I thought setting the framebuffer to 32 bits in QEMU still failed the first time... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356305] Ascending/Descending sort arrow reversed
https://bugs.kde.org/show_bug.cgi?id=356305 Hugo Pereira Da Costa changed: What|Removed |Added Latest Commit||http://commits.kde.org/bree ||ze/c327915a8d864501ff0c7f70 ||1693225d457a8369 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Hugo Pereira Da Costa --- Git commit c327915a8d864501ff0c7f701693225d457a8369 by Hugo Pereira Da Costa. Committed on 05/12/2015 at 17:09. Pushed by hpereiradacosta into branch 'master'. added ViewInvertSortIndicator hidden option (to be added to $HOME/.config5/breezerc) in order to changed sort order arrow orientation. (copied from oxygen) M +4-0kstyle/breeze.kcfg M +3-0kstyle/breezestyle.cpp http://commits.kde.org/breeze/c327915a8d864501ff0c7f701693225d457a8369 -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 350979] kteatime freezes plasma when run from application launcher
https://bugs.kde.org/show_bug.cgi?id=350979 --- Comment #10 from Andrius Štikonas --- Well, dbus interface can be reenabled. But it's probably harder and less safe to do just before the release of 15.12. I also don't know much of dbus myself :(... -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 350979] kteatime freezes plasma when run from application launcher
https://bugs.kde.org/show_bug.cgi?id=350979 --- Comment #9 from Luigi Toscano --- (In reply to Andrius Štikonas from comment #8) > Ok, I committed the patch in > http://commits.kde.org/kteatime/d2922c0b8fcf4f500908d826073907ed26453ec7 > > Thanks for reporting. So the removal of dbus interface in the Frameworks version is a planned choice (not questioning, just for reference; the alternative to this problem would have been reenabling the dbus interface). (PS: I think you know and you just forgot, but if you use BUG: n in a separate line in the commit message, the bug is closed automatically). -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 353835] Tea progress not shown in Plasma 5.3 (Breeze Theme)
https://bugs.kde.org/show_bug.cgi?id=353835 Andrius Štikonas changed: What|Removed |Added Resolution|--- |DUPLICATE CC||andr...@stikonas.eu Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- *** This bug has been marked as a duplicate of bug 279222 *** -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 279222] icon of the progress of the system tray doesn't work
https://bugs.kde.org/show_bug.cgi?id=279222 Andrius Štikonas changed: What|Removed |Added CC||daniel-r.schm...@gmx.de --- Comment #13 from Andrius Štikonas --- *** Bug 353835 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 350979] kteatime freezes plasma when run from application launcher
https://bugs.kde.org/show_bug.cgi?id=350979 Andrius Štikonas changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Andrius Štikonas --- Ok, I committed the patch in http://commits.kde.org/kteatime/d2922c0b8fcf4f500908d826073907ed26453ec7 Thanks for reporting. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356187] icons missing in 15.11.80
https://bugs.kde.org/show_bug.cgi?id=356187 farid changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from farid --- (In reply to Jean-Baptiste Mardelle from comment #4) > Looks like you are using the master branch, and all my recent changes have > only gone in the 15.12 branch that will be released very soon, so you didn't > have all my recent commits. I just merged the branch 5 minutes ago, so can > you update to latest revision of master and try again ? done! :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356312] DVD wizard freezes
https://bugs.kde.org/show_bug.cgi?id=356312 --- Comment #1 from noeb...@web.de --- output console: Cursor: Cannot create bitmap cursor; invalid bitmap(s) [producer_xml] failed to load transition "frei0r.cairoblend" [producer_xml] failed to load transition "frei0r.cairoblend" [NULL @ 0x3b73e60] start time for stream 0 is not set in estimate_timings_from_pts [NULL @ 0x4649300] start time for stream 0 is not set in estimate_timings_from_pts [NULL @ 0x46da760] start time for stream 0 is not set in estimate_timings_from_pts [NULL @ 0x45d8fe0] start time for stream 0 is not set in estimate_timings_from_pts [NULL @ 0x45f1120] start time for stream 0 is not set in estimate_timings_from_pts [NULL @ 0x45c3420] start time for stream 0 is not set in estimate_timings_from_pts [swscaler @ 0x46960e0] Warning: data is not aligned! This can lead to a speedloss [NULL @ 0x3b73e60] start time for stream 0 is not set in estimate_timings_from_pts [NULL @ 0x4649300] start time for stream 0 is not set in estimate_timings_from_pts [NULL @ 0x4645fa0] start time for stream 0 is not set in estimate_timings_from_pts -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354238] Comment field in time zones dialogue in digital clock not searchable
https://bugs.kde.org/show_bug.cgi?id=354238 --- Comment #1 from Martin Klapetek --- I'm putting this up for Google Code-in as a coding task. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356312] New: DVD wizard freezes
https://bugs.kde.org/show_bug.cgi?id=356312 Bug ID: 356312 Summary: DVD wizard freezes Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: noeb...@web.de Version 15.11.80 with Xubuntu 15.10 I load a *.vob-file, created by kdenlive (PAL 16:9), click on continue and the program freezes. This problem occurs with several *.vob files. Reproducible: Always Steps to Reproduce: 1. Invoke DVD-Wizard. 2. Load a vob 3. click on "continue" Actual Results: the program freezes. Some shadow of a new window can be seen. Expected Results: it should continue :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353428] KWin freezes until drkonqi is closed from a terminal
https://bugs.kde.org/show_bug.cgi?id=353428 --- Comment #24 from Thomas Lübking --- No, but this is no deterministic error (depends on when the crash occurs and when the next xcb flush takes place) - I personally saw it once or twice only. Also kwin should not crash itfp. and maybe your distro has simply backported the patch that prevents 0x0 QScreen deref segfault ... (less crashes, less problems with crash handling ;-) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356310] Deleting all tracks possible and crashes Kdenlive
https://bugs.kde.org/show_bug.cgi?id=356310 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kden ||live/5a606d40263404b9ca0249 ||1fa340311769ae913d Status|UNCONFIRMED |RESOLVED --- Comment #2 from Jean-Baptiste Mardelle --- Git commit 5a606d40263404b9ca02491fa340311769ae913d by Jean-Baptiste Mardelle. Committed on 05/12/2015 at 16:09. Pushed by mardelle into branch 'Applications/15.12'. Fix crash when trying to delete last track M +1-0src/mainwindow.cpp M +4-2src/timeline/customtrackview.cpp M +14 -0src/timeline/timeline.cpp M +2-0src/timeline/timeline.h http://commits.kde.org/kdenlive/5a606d40263404b9ca02491fa340311769ae913d -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 351819] Changing Icon on created entry has no effect.
https://bugs.kde.org/show_bug.cgi?id=351819 MH changed: What|Removed |Added CC||mhejp...@mhn.cz --- Comment #4 from MH --- I have similar problem with 5.4.3 version on OpenSUSE Leap 42.1. When icon to the new submenu is added, it has no effect for menu - there is still some ugly default icon visible. Appropriate file is not changed in ~/.local/share/desktop-directories . There is Icon=package forever in *.directory files. Logout/Login does not help - of course. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 356311] New: Improper handling of sshfs filesystem.
https://bugs.kde.org/show_bug.cgi?id=356311 Bug ID: 356311 Summary: Improper handling of sshfs filesystem. Product: ktorrent Version: 4.3.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: adrin.jal...@gmail.com Ktorrent tries to preallocate space for downloading files, which fails somehow on sshfs mounted path. The reason I'm trying sshfs is that I don't seem to be able to enter an sftp path as a destination folder. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 356311] Improper handling of sshfs filesystem.
https://bugs.kde.org/show_bug.cgi?id=356311 adrin changed: What|Removed |Added CC||adrin.jal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356310] Deleting all tracks possible and crashes Kdenlive
https://bugs.kde.org/show_bug.cgi?id=356310 --- Comment #1 from qubo...@gmail.com --- PS: Video: https://youtu.be/K1QoCjGQKig Details: catalyst-libgl 15.11-1 ffmpeg 1:2.8.3-1 ffmpeg-compat 1:0.10.16-4 mlt 0.9.8-3 qt5-base 5.5.1-3 xorg-server 1.16.4-1 v15.11.90-37-g5d40b7f * master -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348550] present windows layout should optimize screen estate
https://bugs.kde.org/show_bug.cgi?id=348550 Thomas Lübking changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #7 from Thomas Lübking --- (In reply to miklos from comment #6) > Steam creates popup dialogs for group events, that are invisible > ... > These don't show up in present windows, but they are accounted for. *cough* https://git.reviewboard.kde.org/r/122435/ *cough cough* ;-) > However, I can still force the natural layout to produce weird results Quite frankly, I personally don't deem the "natural" layout a very reasonable approach - the idea of present window (aka "exposé"...) is to provide a general overview on your windows. Trying to reproduce the desktop mess as it is seems rather counterproductive. Closing "worksforme" If you'd like to open a bug that says "If clients map iconified, there's no thumbnail in the compositor and an empty space in some effects" ... I'm not holding you back :-P -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356310] New: Deleting all tracks possible and crashes Kdenlive
https://bugs.kde.org/show_bug.cgi?id=356310 Bug ID: 356310 Summary: Deleting all tracks possible and crashes Kdenlive Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: qubo...@gmail.com In the unlikely event that the user deletes all tracks, Kdenlive crashes. Steps to reproduce: 1. Start kdenlive 2. Delete all tracks by right-clicking on the track info panel and selecting "delete track", repeat for each track Expected result: 1. The last track (when only one track remains in the timeline) should not allow getting deleted (grayed out option in context menu) or gets deleted but kdenlive remains functional Actual result: 1. When the last track is deleted, Kdenlive crashes with a Segmentation fault. GDB: Program received signal SIGSEGV, Segmentation fault. 0x00480a80 in QString::isEmpty() const () BT: #0 0x00480a80 in QString::isEmpty() const () #1 0x0050b419 in TransitionSettings::updateTrackList() () #2 0x0050b126 in TransitionSettings::updateProjectFormat() () #3 0x0082b69c in MainWindow::slotDeleteTrack() () #4 0x0083990a in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (MainWindow::*)()>::call(void (MainWindow::*)(), MainWindow*, void**) () #5 0x00839077 in void QtPrivate::FunctionPointer::call, void>(void (MainWindow::*)(), MainWindow*, void**) () #6 0x00838589 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () #7 0x7fffef5f4fb7 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #8 0x713b3402 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #9 0x713b5888 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #10 0x715381b2 in ?? () from /usr/lib/libQt5Widgets.so.5 #11 0x7153e47c in ?? () from /usr/lib/libQt5Widgets.so.5 #12 0x71542380 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x71400038 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x71542dc3 in QMenu::event(QEvent*) () ---Type to continue, or q to quit--- from /usr/lib/libQt5Widgets.so.5 #15 0x713bd01c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x713c2bf9 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #17 0x7fffef5c69ab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #18 0x713c1b02 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/libQt5Widgets.so.5 #19 0x7141a8fd in ?? () from /usr/lib/libQt5Widgets.so.5 #20 0x7141cb5b in ?? () from /usr/lib/libQt5Widgets.so.5 #21 0x713bd01c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x713c24f6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #23 0x7fffef5c69ab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #24 0x7fffefb26111 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #25 0x7fffefb27de5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #26 0x7fffefb0d208 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #27 0x7fffe43bd3c0 in ?? () from /usr/lib/libQt5XcbQpa.so.5 ---Type to continue, or q to quit--- #28 0x7fffeb7a0dc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0x7fffeb7a1020 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0x7fffeb7a10cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0x7fffef61d34f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #32 0x7fffef5c437a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #33 0x7153d1c0 in QMenu::exec(QPoint const&, QAction*) () from /usr/lib/libQt5Widgets.so.5 #34 0x7153d331 in QMenu::exec(QList, QPoint const&, QAction*, QWidget*) () from /usr/lib/libQt5Widgets.so.5 #35 0x71400a10 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #36 0x713bd01c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #37 0x713c2fac in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #38 0x7fffef5c69ab in QCoreApplication::n
[Breeze] [Bug 356305] Ascending/Descending sort arrow reversed
https://bugs.kde.org/show_bug.cgi?id=356305 Hugo Pereira Da Costa changed: What|Removed |Added Product|kwin|Breeze Status|RESOLVED|REOPENED CC||hugo.pere...@free.fr Component|general |QStyle Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #3 from Hugo Pereira Da Costa --- Re-oppening/reassigning. Thing is, I have not ported the infamous option to breeze. Also maybe we should move it upstream to kstyle (mmm but then that would break oxygen installation). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356283] Any message contents that shows in the message preview bottom pane shows <<< Grantlee theme "" is not valid >>> prefixed to the actual msg body
https://bugs.kde.org/show_bug.cgi?id=356283 --- Comment #3 from Laurent Montel --- ok but which is kmail version ? I don't know kubuntu :) So kmail -> help -> about kmail -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 354258] The cursor is inactive after Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=354258 --- Comment #3 from Victor Porton --- Weird, this bug appeared for me again! (maybe after Debian Linux upgrade) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356299] Trying to import broken video causes crash
https://bugs.kde.org/show_bug.cgi?id=356299 --- Comment #5 from qubo...@gmail.com --- To me, as a non-developer and just one user it sounds like checking a file before adding it makes sense if it can prevent a crash caused by a library that kdenlive has no control over due to the way packages are managed in Linux usually. Then again I don't know any better as I don't know how to code it and I don't know how expensive time-wise that would be. ffmpeg seems fine with it now but mlt appears to fail: http://curlpaste.com/id/bdx68n Maybe it's an mlt issue after all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Are you sure that the colorspace isn't linear(for example, sRGB-elle-v2-g10.icc (the g10 means gamma=1.0, thus linear). Color maths works differently in a linear space(It works in fact more accurately to real life physics, as real life doesn't have the gamma crunching we impose on computer graphics) Go to image->convert image colorspace and chose anything appended with srgbtrc.icc(preferably srgb-elle-v2-srgbtrc.icc) to fix this. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356298] Dolphin crashes when selecting multiple (more than 10) files
https://bugs.kde.org/show_bug.cgi?id=356298 Christoph Feck changed: What|Removed |Added CC||pinak.ah...@gmail.com Assignee|dolphin-bugs-n...@kde.org |m...@vhanda.in Component|general |General Product|dolphin |Baloo Version|15.08.2 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 354558] Dolphin crashed when accessing to "Configure Dolphin"
https://bugs.kde.org/show_bug.cgi?id=354558 Christoph Feck changed: What|Removed |Added CC||niktische...@gmail.com --- Comment #8 from Christoph Feck --- *** Bug 356288 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356288] Dolphin crashes if 'Configure Dolphin' selected in menu
https://bugs.kde.org/show_bug.cgi?id=356288 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 354558 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356305] Ascending/Descending sort arrow reversed
https://bugs.kde.org/show_bug.cgi?id=356305 --- Comment #2 from Christoph Feck --- See also bug 349608. -- You are receiving this mail because: You are watching all bug changes.