[plasmashell] [Bug 365246] windows in Icon-only Task manager and Task manager won't show in the right screens
https://bugs.kde.org/show_bug.cgi?id=365246 rosan...@lajt.hu changed: What|Removed |Added CC||rosan...@lajt.hu -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368831] The position and zoom effect alters the aspect ratio of a picture
https://bugs.kde.org/show_bug.cgi?id=368831 --- Comment #2 from al...@gmx.net --- Created attachment 101093 --> https://bugs.kde.org/attachment.cgi?id=101093=edit screenshot2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368831] The position and zoom effect alters the aspect ratio of a picture
https://bugs.kde.org/show_bug.cgi?id=368831 --- Comment #1 from al...@gmx.net --- Created attachment 101092 --> https://bugs.kde.org/attachment.cgi?id=101092=edit screenshot1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368831] New: The position and zoom effect alters the aspect ratio of a picture
https://bugs.kde.org/show_bug.cgi?id=368831 Bug ID: 368831 Summary: The position and zoom effect alters the aspect ratio of a picture Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: al...@gmx.net I am using the newest kdenlive version 16.08.1 on Ubuntu 16.04.1. The project profile is DV/DVD Widescreen PAL. When I add a picture with the aspect ratio 4:3 to the time line it shows up fine in th eproject monitor. However, when I add the "Position and zoom" effect it changes the aspect ratio of the picture Reproducible: Always Steps to Reproduce: 1. Add picture with aspect ratio 4:3 to timeline 2. Add Position and Zoom effect to picture 3. Actual Results: the aspect ratio of the picture is changed Expected Results: the aspect ratio should stay unaltered I am happy to send a screen shot. Just let me know, where to send it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356994] Task manager shows windows from wrong screen or not at all in dual monitor setup
https://bugs.kde.org/show_bug.cgi?id=356994 rosan...@lajt.hu changed: What|Removed |Added CC||rosan...@lajt.hu -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 368830] New: ktorrent crashes (aborting) on "data checking" on random percent of checked data
https://bugs.kde.org/show_bug.cgi?id=368830 Bug ID: 368830 Summary: ktorrent crashes (aborting) on "data checking" on random percent of checked data Product: ktorrent Version: 5.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: k...@mva.name Sometimes, I re-downloading torrents with slightly changed data (it maybe few changed files in the torrent folder, or a bit regenerated disk image, or so. So, mostly, content is the same, and only few chunks needs to be re-fetched. So, I checking "check existing data" in torrent-opening dialog. Then, ktorrent start to checking data, and... crashes after random amount of checked chunks. drKonqi says that debug info is useless and signal was "abort". After the restart of ktorrent, it... starting to download entire torrent content from scratch (!) and replacing (!) already downloaded data (and braking it by that action). If I stop it and click "check data" in context menu, it finds many already existing chunks, but crashes again after some random amount checked. Reproducible: Always Steps to Reproduce: 1. run ktorrent 2. right mouse button click on the torrent. 3. click "check data" 4. Wait for check to finish 5. It can not finish, and Ktorrent crashes (aborts) after random amount of checked chunks (sometimes 600 of 4000+, sometimes 3800 of 4000, and sometimes - 300 of 1000) and shows drkonqi dialog gdb trace: Temporary breakpoint 1 at 0x4310d4 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Temporary breakpoint 1, 0x004310d4 in main () [New Thread 0x7fffe0c4c700 (LWP 119300)] [New Thread 0x7fffdb41e700 (LWP 119301)] [New Thread 0x7fffda20d700 (LWP 119306)] [New Thread 0x7fffd9a0c700 (LWP 119307)] [Thread 0x7fffda20d700 (LWP 119306) exited] чт сент. 15 11:32:31 2016: Bound to :: чт сент. 15 11:32:31 2016: UTP: bound to :: чт сент. 15 11:32:31 2016: Bound to 0.0.0.0 чт сент. 15 11:32:31 2016: UTP: bound to 0.0.0.0 [New Thread 0x7fffda20d700 (LWP 119313)] чт сент. 15 11:32:31 2016: Bound to UDP port 6881 чт сент. 15 11:32:31 2016: Bound to :: чт сент. 15 11:32:31 2016: Cannot bind to port 0.0.0.0:6881 : Адрес уже используется чт сент. 15 11:32:31 2016: Bound to TCP port 6881 чт сент. 15 11:32:31 2016: DHT: Starting on port 7881 чт сент. 15 11:32:31 2016: Bound to :: чт сент. 15 11:32:31 2016: DHT: Bound to :: чт сент. 15 11:32:31 2016: Bound to 0.0.0.0 чт сент. 15 11:32:31 2016: DHT: Bound to 0.0.0.0 чт сент. 15 11:32:31 2016: Cannot open /home/mva/.local/share/ktorrent/groups : Нет такого файла или каталога чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor0/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor1/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Bound to :: чт сент. 15 11:32:31 2016: Bound to 0.0.0.0 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor10/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor100/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor101/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor102/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor11/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor12/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor13/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor14/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor15/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor16/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor17/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor18/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor19/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor2/ чт сент. 15 11:32:31 2016: Encoding : UTF-8 чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor20/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor21/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor22/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor23/ чт сент. 15 11:32:31 2016: Loading /home/mva/.local/share/ktorrent/tor24/ чт сент. 15
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 Rex Dieterchanged: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 368829] New: Kate/Dolphin Crash on close
https://bugs.kde.org/show_bug.cgi?id=368829 Bug ID: 368829 Summary: Kate/Dolphin Crash on close Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bugs.kde@queuemail.com Application: kdeinit5 (16.04.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.3-200.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: Closing either Kate or Dolphin causes an exception to be thrown. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f11383c9900 (LWP 10114))] Thread 2 (Thread 0x7f1115921700 (LWP 10116)): #0 0x7f11359443ed in poll () at /lib64/libc.so.6 #1 0x7f113400aa06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f113400ab1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f113674924b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f11366f85ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f1136557343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f1138485559 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f113655b99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f11351935ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f113594ff6d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f11383c9900 (LWP 10114)): [KCrash Handler] #6 0x7f11358816f5 in raise () at /lib64/libc.so.6 #7 0x7f11358832fa in abort () at /lib64/libc.so.6 #8 0x7f11358c2670 in __libc_message () at /lib64/libc.so.6 #9 0x7f11358cae0a in _int_free () at /lib64/libc.so.6 #10 0x7f11358ce36c in free () at /lib64/libc.so.6 #11 0x7f113671fe9f in QMetaCallEvent::~QMetaCallEvent() () at /lib64/libQt5Core.so.5 #12 0x7f113671fef9 in QMetaCallEvent::~QMetaCallEvent() () at /lib64/libQt5Core.so.5 #13 0x7f11366fbfe7 in QCoreApplication::removePostedEvents(QObject*, int) () at /lib64/libQt5Core.so.5 #14 0x7f11367227c9 in QObjectPrivate::~QObjectPrivate() () at /lib64/libQt5Core.so.5 #15 0x7f11367228c9 in QObjectPrivate::~QObjectPrivate() () at /lib64/libQt5Core.so.5 #16 0x7f1136729647 in QObject::~QObject() () at /lib64/libQt5Core.so.5 #17 0x7f111acbb0b9 in QXcbConnection::~QXcbConnection() () at /lib64/libQt5XcbQpa.so.5 #18 0x7f111acbca46 in QXcbIntegration::~QXcbIntegration() () at /lib64/libQt5XcbQpa.so.5 #19 0x7f111acbcb49 in QXcbIntegration::~QXcbIntegration() () at /lib64/libQt5XcbQpa.so.5 #20 0x7f1136a2dfab in QGuiApplicationPrivate::~QGuiApplicationPrivate() () at /lib64/libQt5Gui.so.5 #21 0x7f1136f88c09 in QApplicationPrivate::~QApplicationPrivate() () at /lib64/libQt5Widgets.so.5 #22 0x7f1136729647 in QObject::~QObject() () at /lib64/libQt5Core.so.5 #23 0x7f11366fff1c in QCoreApplication::~QCoreApplication() () at /lib64/libQt5Core.so.5 #24 0x7f1136a2dda3 in QGuiApplication::~QGuiApplication() () at /lib64/libQt5Gui.so.5 #25 0x7f1136f8a6cf in QApplication::~QApplication() () at /lib64/libQt5Widgets.so.5 #26 0x7f11261e8551 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so #27 0x55b36c658f37 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #28 0x55b36c65a0e7 in handle_launcher_request(int, char const*) [clone .isra.26] () #29 0x55b36c65a9f7 in handle_requests(int) () #30 0x55b36c6559ce in main () Possible duplicates by query: bug 351922, bug 347134, bug 346742. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 368828] New: Ubuntu KF5 PPA xenial package still uses oxygen icon theme
https://bugs.kde.org/show_bug.cgi?id=368828 Bug ID: 368828 Summary: Ubuntu KF5 PPA xenial package still uses oxygen icon theme Product: skrooge Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: dberg...@gmail.com CC: steph...@mankowski.fr When skrooge 2.x series is installed from the skrooge Ubuntu PPA, it still uses the oxygen icon theme. It should be using breeze instead. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368827] Using the KWin Resize keyboard shortcut, all keypresses are sent into the window during the resize
https://bugs.kde.org/show_bug.cgi?id=368827 --- Comment #2 from andydecle...@gmail.com --- Created attachment 101091 --> https://bugs.kde.org/attachment.cgi?id=101091=edit Demonstration Video -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368827] Using the KWin Resize keyboard shortcut, all keypresses are sent into the window during the resize
https://bugs.kde.org/show_bug.cgi?id=368827 --- Comment #1 from andydecle...@gmail.com --- I've attached a demonstration video. The keypresses are not reported correctly (vokoscreen bug I guess); what it reports as "s" is cursor-right, "r" is cursor-up, "q" is cursor-left. In the video's case, it seems that hitting Enter _did_ stop the resize operation. That is not consistent. But you can clearly see, regardless, that the keypresses are inappropriately affecting the application being resized. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368827] Using the KWin Resize keyboard shortcut, all keypresses are sent into the window during the resize
https://bugs.kde.org/show_bug.cgi?id=368827 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues
https://bugs.kde.org/show_bug.cgi?id=368078 --- Comment #6 from David Brooke--- To date: I have installed three different distro's: Gentoo Arch KDE Neon All reproduce the same issue with the Task Manager's grouping function and wine programs. Please let me know if other info is needed. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368827] New: Using the KWin Resize keyboard shortcut, all keypresses are sent into the window during the resize
https://bugs.kde.org/show_bug.cgi?id=368827 Bug ID: 368827 Summary: Using the KWin Resize keyboard shortcut, all keypresses are sent into the window during the resize Product: kwin Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: andydecle...@gmail.com When using the Resize keyboard shortcut for KWin, keypresses such as the cursor keys, Enter, and Esc should be swallowed by KWin's resizing operation, but are instead sent into the application window, affecting the application. Sometimes these keys _also_ affect the resizing operation (as they should), and sometimes they don't. The only reliable way to exit the resize operation is to use the mouse, defeating the purpose of the keyboard shortcut. Reproducible: Always Steps to Reproduce: 1. Open a window 2. Trigger the KWin Resize shortcut 3. Use cursor keys / Enter / Esc Actual Results: The cursor keys / Enter / Esc keypresses affect the application window as if you were not in the middle of a resize operation, meaning different results depending on the application. There is no keyboard-only method for stopping the resizing operation without closing the window or quitting the application. Expected Results: During the resize operation, the keypresses should guide the resize itself, and not affect the application window's internal state or the application run state. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues
https://bugs.kde.org/show_bug.cgi?id=368078 --- Comment #5 from David Brooke--- 9/14/16 Update Plasma-Task Manager and Wine issues I have simplified the issue of grouping not working for wine programs: 1. The issue is reproducible by: A. Opening 2 or more windows of notepad while the grouping function is always enforced. B. Opening 9 windows of notepad while grouping is only enforced when the task manager is full. Either of the above two options will show that grouping does not work for wine programs but does work for others (dolphin, konsole, etc...). Three computers have been used for evaluation (See below). Computer-3770 originally showed the issue then Computer-4790K and Computer-4790 were used for additional testing. Partition1 or C3770-P1 is the only setup that works correctly. All others fail. Test1 Currently Plasma 5.7.0 through 5.7.5 has an issue with Sierra Chart running under Wine 1.9.18 for C3770-P2. Results are the same as before. Test2 Currently Plasma 5.7.3 and 5.7.5 has an issue with Sierra Chart running under Wine 1.9.18 for C4790K-P1, C4790K-P2 and C4790-P1. C4790K-P1 with KDE Neon uses wine 1.6.2. Results are the same as before. Computer-3770 CPU - CI7-3770 Video - HD4000 Memory - 8GB Partition1 or C3770-P1 Gentoo AMD64 Stable Plasma 5.6.5 Frameworks 5.26 KDE Apps 16.08.1 QT5 - version 5.6.1 xf86-video-intel 2.99.917-r2 Partition2 or C3770-P2 Gentoo AMD64 Stable Plasma 5.7.5 Frameworks 5.26 KDE Apps 16.08.1 QT5 - version 5.6.1 xf86-video-intel 2.99.917-r2 ### Computer-4790K CPU - CI7-4790K Video - HD4600 Memory - 8GB Partition1 or C4790K-P1 Arch Plasma 5.7.4 Frameworks 5.26 KDE Apps 16.08.1 QT5 - version 5.7.0 xf86-video-intel 2.99.917+697+g12c14de Partition1 or C4790K-P1 KDE Neon Plasma 5.7.5 Frameworks 5.26 KDE Apps 16.08.0 QT5 - version 5.7.0 xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 Partition2 or C4790K-P2 Gentoo AMD64 Stable Plasma 5.7.5 Frameworks 5.26 KDE Apps 16.08.1 QT5 - version 5.6.1 xf86-video-intel 2.99.917-r2 ### Computer-4790 CPU - CI7-4790 Video - Nvidia GTX-950 Memory - 8GB Partition1 or C4790-P1 Gentoo AMD64 Stable Plasma 5.7.5 Frameworks 5.26 KDE Apps 16.08.1 QT5 - version 5.6.1 nvidia-drivers 361.28 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368816] git master - Saving a project doesn't automatically add the ".kdenlive" extension to the file name
https://bugs.kde.org/show_bug.cgi?id=368816 --- Comment #1 from Christoph Feck--- > GNOME 3.20 desktop environment This implies you are not getting the KDE save dialog (which has the "automatically add file extension" checkbox)? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 368815] Crash during login on kubuntu
https://bugs.kde.org/show_bug.cgi?id=368815 Christoph Feckchanged: What|Removed |Added Component|general |Baloo File Daemon Assignee|unassigned-b...@kde.org |pinak.ah...@gmail.com Product|kde |frameworks-baloo Version|unspecified |5.18.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368826] New: KDevelop crashed when trying to open a CMake project
https://bugs.kde.org/show_bug.cgi?id=368826 Bug ID: 368826 Summary: KDevelop crashed when trying to open a CMake project Product: kdevelop Version: 5.0.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: 0xd34df...@gmail.com Application: kdevelop (5.0.0) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.7.0-pf2 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I was trying to open a .kdev4 file generated for a CMake-based project when KDevelop crashed. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe2818ce780 (LWP 18968))] Thread 6 (Thread 0x7fe2421e9700 (LWP 19055)): #0 0x7fe276f27210 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe276f296eb in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe276f2a0eb in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe276f2a2cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe27fa12a2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe27f9c4a2a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe27f820104 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7fe27f82436c in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fe278efe474 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe27f0d221d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fe24cb21700 (LWP 18976)): #0 0x7fe27f0c512d in read () from /lib64/libc.so.6 #1 0x7fe276f6d5c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe276f29ca4 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe276f2a160 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe276f2a2cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe27fa12a2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe27f9c4a2a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe27f820104 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fe2758331f5 in ?? () from /usr/lib64/libQt5Qml.so.5 #9 0x7fe27f82436c in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fe278efe474 in start_thread () from /lib64/libpthread.so.0 #11 0x7fe27f0d221d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fe256dc5700 (LWP 18971)): #0 0x7fe278f04438 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe27f8249b8 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7fe27d1c6388 in KDevelop::DUChainPrivate::CleanupThread::run() () from /usr/lib64/libKDevPlatformLanguage.so.10 #3 0x7fe27f82436c in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x7fe278efe474 in start_thread () from /lib64/libpthread.so.0 #5 0x7fe27f0d221d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe25fdf5700 (LWP 18970)): #0 0x7fe27f0c915d in poll () from /lib64/libc.so.6 #1 0x7fe276f2a1bc in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe276f2a2cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe27fa12a2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe27f9c4a2a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe27f820104 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe281a2b885 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fe27f82436c in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fe278efe474 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe27f0d221d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe265539700 (LWP 18969)): #0 0x7fe27f0c915d in poll () from /lib64/libc.so.6 #1 0x7fe2731958f2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fe273197707 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fe267a9ec69 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe27f82436c in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fe278efe474 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe27f0d221d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe2818ce780 (LWP 18968)): [KCrash Handler] #6 0x7fe280e60929 in KDevelop::IPlugin::extensions() const () from /usr/lib64/libKDevPlatformInterfaces.so.10 #7 0x7fe24267616a in CMakeManager::builder() const () from /usr/lib64/qt5/plugins/kdevplatform/26/kdevcmakemanager.so #8 0x7fe242675e38 in
[ktorrent] [Bug 368825] New: Crash on adding torrent
https://bugs.kde.org/show_bug.cgi?id=368825 Bug ID: 368825 Summary: Crash on adding torrent Product: ktorrent Version: 4.3.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mothli...@fastmail.fm Application: ktorrent (4.3.1) KDE Platform Version: 4.14.20 Qt Version: 4.8.7 Operating System: Linux 4.6.7-200.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: Ctrl-p, added torrent, application crashed immediately afterwards. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe461190900 (LWP 15087))] Thread 10 (Thread 0x7fe3ddc41700 (LWP 18617)): #0 0x7fe45c7ffb7d in poll () at /lib64/libc.so.6 #1 0x7fe455ed418c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fe455ed429c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fe45d530d9e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #4 0x7fe45d4ff071 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #5 0x7fe45d4ff3e5 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #6 0x7fe45d3eeaa9 in QThread::exec() () at /lib64/libQtCore.so.4 #7 0x7fe45d3f139c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #8 0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0 #9 0x7fe45c80b5fd in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fe3dcdb7700 (LWP 18664)): #0 0x7fe45ea7fb20 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe42729d071 in JSC::BlockAllocator::blockFreeingThreadMain() () at /lib64/libQtWebKit.so.4 #2 0x7fe4275a14c6 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQtWebKit.so.4 #3 0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0 #4 0x7fe45c80b5fd in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fe3d7358700 (LWP 19320)): #0 0x7fe45ea7fec9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe45d3efd4a in thread_sleep(timespec*) () at /lib64/libQtCore.so.4 #2 0x7fe45d3f06fd in QThread::msleep(unsigned long) () at /lib64/libQtCore.so.4 #3 0x7fe460d5436f in net::DownloadThread::update() () at /lib64/libktorrent.so.5 #4 0x7fe460d543c9 in net::NetworkThread::run() () at /lib64/libktorrent.so.5 #5 0x7fe45d3f139c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #6 0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0 #7 0x7fe45c80b5fd in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fe3d6b57700 (LWP 19321)): #0 0x7fe460d53a04 in net::UploadThread::waitForSocketsReady() () at /lib64/libktorrent.so.5 #1 0x7fe460d53b06 in net::UploadThread::update() () at /lib64/libktorrent.so.5 #2 0x7fe460d543c9 in net::NetworkThread::run() () at /lib64/libktorrent.so.5 #3 0x7fe45d3f139c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #4 0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0 #5 0x7fe45c80b5fd in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fe3d6356700 (LWP 19323)): #0 0x7fe45ea7fb20 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe45d3f1906 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQtCore.so.4 #2 0x7fe460d56cb2 in net::ReverseResolverThread::run() () at /lib64/libktorrent.so.5 #3 0x7fe45d3f139c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #4 0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0 #5 0x7fe45c80b5fd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fe4415ac700 (LWP 20802)): #0 0x7fe45c805809 in syscall () at /lib64/libc.so.6 #1 0x7fe45d3efbd2 in QMutexPrivate::wait(int) () at /lib64/libQtCore.so.4 #2 0x7fe45d3ebfbd in QMutex::lock() () at /lib64/libQtCore.so.4 #3 0x7fe45fb3b498 in QHostInfoLookupManager::wasAborted(int) [clone .part.2] () at /lib64/libQtNetwork.so.4 #4 0x7fe45fb3d797 in QHostInfoRunnable::run() () at /lib64/libQtNetwork.so.4 #5 0x7fe45d3e46ca in QThreadPoolThread::run() () at /lib64/libQtCore.so.4 #6 0x7fe45d3f139c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #7 0x7fe45ea7a61a in start_thread () at /lib64/libpthread.so.0 #8 0x7fe45c80b5fd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fe43affd700 (LWP 3616)): #0 0x7fe45ea7fec9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe45d3f18e4 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQtCore.so.4 #2 0x7fe45d3e48a7 in QThreadPoolThread::run() () at /lib64/libQtCore.so.4 #3
[krita] [Bug 368824] New: Crash when inverting selection
https://bugs.kde.org/show_bug.cgi?id=368824 Bug ID: 368824 Summary: Crash when inverting selection Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Here is the gdb backtrace (gdb) run Starting program: /home/scott/kf5/inst/bin/krita [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". krita.lib.pigment: Legacy integer arithmetics implementation [New Thread 0x7fffe5595700 (LWP 26678)] [New Thread 0x7fffdaf00700 (LWP 26679)] [New Thread 0x7fffda6ff700 (LWP 26680)] [New Thread 0x7fffd9ccc700 (LWP 26681)] [New Thread 0x7fffc6b54700 (LWP 26683)] [New Thread 0x7fffc6353700 (LWP 26684)] Set style "fusion" OpenGL Info Vendor: Intel Open Source Technology Center Renderer: Mesa DRI Intel(R) Ivybridge Mobile Version: 3.0 Mesa 11.2.0 Shading language: 1.30 Requested format: QSurfaceFormat(version 3.0, options QFlags(0x4), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 0, profile 2) Current format:QSurfaceFormat(version 3.0, options QFlags(0x4), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 0, profile 0) Version: 3 . 0 Supports deprecated functions true krita has opengl true Setting XDG_DATA_DIRS "/home/scott/kf5/inst/bin/../share:/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop" Available translations QSet("en_US") Available domain translations QSet("en_US") Override language: "" [Thread 0x7fffc6b54700 (LWP 26683) exited] [New Thread 0x7fffc6b54700 (LWP 26685)] [New Thread 0x7fffaf99f700 (LWP 26686)] [New Thread 0x7fffaf057700 (LWP 26687)] [New Thread 0x7fffae23b700 (LWP 26688)] [Thread 0x7fffae23b700 (LWP 26688) exited] void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "C" under id 38 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action " All" under id 39 [New Thread 0x7fffae23b700 (LWP 26691)] [Thread 0x7fffae23b700 (LWP 26691) exited] [Thread 0x7fffc6353700 (LWP 26684) exited] [New Thread 0x7fffc6353700 (LWP 26692)] [Thread 0x7fffc6353700 (LWP 26692) exited] [New Thread 0x7fffc6353700 (LWP 26693)] WARNING: Level of Detail functionality is available only with openGL + GLSL 1.3 support [Thread 0x7fffc6353700 (LWP 26693) exited] krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with canvas action "rotate_canvas_left" shortcut: "Ctrl+[" krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with canvas action "rotate_canvas_right" shortcut: "Ctrl+]" krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with canvas action "rotate_canvas_left" shortcut: "Ctrl+[" krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with canvas action "rotate_canvas_right" shortcut: "Ctrl+]" WARNING: Level of Detail functionality is available only with openGL + GLSL 1.3 support [New Thread 0x7fffc6353700 (LWP 26694)] [New Thread 0x7fffae23b700 (LWP 26695)] [New Thread 0x7fff9a9b1700 (LWP 26696)] [New Thread 0x7fff9a1b0700 (LWP 26697)] [New Thread 0x7fff999af700 (LWP 26698)] [New Thread 0x7fff991ae700 (LWP 26699)] [New Thread 0x7fff989ad700 (LWP 26700)] [New Thread 0x7fff83fff700 (LWP 26701)] canvas KisCanvas2(0x6314be8) display filter false canvas KisCanvas2(0x6314be8) display filter false WARNING: Level of Detail functionality is available only with openGL + GLSL 1.3 support canvas KisCanvas2(0x6314be8) display filter false uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu [New Thread 0x7fff82ffe700 (LWP 26702)] [New Thread 0x7fff827fd700 (LWP 26703)] [Thread 0x7fff827fd700 (LWP 26703) exited] [Thread 0x7fff82ffe700 (LWP 26702) exited] [New Thread 0x7fff82ffe700 (LWP 26706)] [New Thread 0x7fff827fd700 (LWP 26707)] Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x0031 in ?? () (gdb) backtrace #0 0x0031 in ?? () #1 0x77745815 in KisSharedPtr::deref ( sp=0x7fffc8b0, t=0xc7c3a0) at /home/scott/kf5/src/krita/libs/global/kis_shared_ptr.h:214 #2 KisSharedPtr::deref (this=0x7fffc8b0) at /home/scott/kf5/src/krita/libs/global/kis_shared_ptr.h:221 #3 KisSharedPtr::~KisSharedPtr ( this=0x7fffc8b0, __in_chrg=) at /home/scott/kf5/src/krita/libs/global/kis_shared_ptr.h:109 #4 KisActionManager::runOperation (this=0x69eef20, id=...) at /home/scott/kf5/src/krita/libs/ui/kis_action_manager.cpp:380 #5
[plasmashell] [Bug 352651] Widgets get pushed off the panel despite flexible spacer [regression]
https://bugs.kde.org/show_bug.cgi?id=352651 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from David Edmundson --- Thanks I can reproduce the bug. Will try and fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349592] Widgets get pushed out of the panel when items appear in the system tray
https://bugs.kde.org/show_bug.cgi?id=349592 David Edmundsonchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- *** This bug has been marked as a duplicate of bug 352651 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 352651] Widgets get pushed off the panel despite flexible spacer [regression]
https://bugs.kde.org/show_bug.cgi?id=352651 David Edmundsonchanged: What|Removed |Added CC||patrick.auer...@gmail.com --- Comment #4 from David Edmundson --- *** Bug 349592 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 368754] KDE Plasma version 5.7.4 kactivitymanager
https://bugs.kde.org/show_bug.cgi?id=368754 --- Comment #1 from Jón Frímann--- I wanted to add to this information. I was using an old xorg-server (version 1.7.4). This seems to have triggered the issue I found. I hope that upgrading to xorg-server version 1.8.3 solves this problem. The problem has to due with how graphic (of KDE) is not properly handled by the old xorg-server, along with changes in the nvidia driver that are not properly supported by older versions of xorg-server. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368790] panel on secondary screen of dual monitor setup unclickable in wayland session
https://bugs.kde.org/show_bug.cgi?id=368790 David Edmundsonchanged: What|Removed |Added Component|Panel |generic-wayland CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359152] No application can be run after some uptime
https://bugs.kde.org/show_bug.cgi?id=359152 --- Comment #4 from David Edmundson--- So you have the file when you log in, then at some point it disappears? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 321327] Memory leak when entering specific calculation
https://bugs.kde.org/show_bug.cgi?id=321327 Christoph Feckchanged: What|Removed |Added CC||cf...@kde.org Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #19 from Christoph Feck --- Previous comments state that the calculator runner alone triggers the bug. Reopening. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368772] Can't access the plasmoids' context menu
https://bugs.kde.org/show_bug.cgi?id=368772 --- Comment #4 from David Edmundson--- it is possible to get to applet settings. long press to get the handles press the settings button in the panel: toolbox click on applet click settings You can't get the context menu, but a context menu on a touch screen would be rubbish anyway. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368603] crash when starting an lldb debug session
https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #15 from RJVB--- No, I didn't tick the "don't ask again option". I checked with an unpatched lldb 3.8.1 on OS X and I indeed got the warning in the debugger console, but IIRC everything else was functional. No, on Linux I get something else: it looks like the debug session is being created as expected, and then the IDE falls back into the regular code view. Which means I cannot even get at the debugger console to check for any relevant output there. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368823] run_a_thread_NORETURN assembly code typo for VGP_arm64_linux target
https://bugs.kde.org/show_bug.cgi?id=368823 c...@google.com changed: What|Removed |Added CC||dimi...@google.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368823] New: run_a_thread_NORETURN assembly code typo for VGP_arm64_linux target
https://bugs.kde.org/show_bug.cgi?id=368823 Bug ID: 368823 Summary: run_a_thread_NORETURN assembly code typo for VGP_arm64_linux target Product: valgrind Version: 3.11.0 Platform: Android OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: c...@google.com When compiled with clang/llvm, llvm assembler reported error in run_a_thread_NORETURN assembly code. The following diff will fix the problem. diff --git a/coregrind/m_syswrap/syswrap-linux.c b/coregrind/m_syswrap/syswrap-linux.c index f796969..6584c16 100644 --- a/coregrind/m_syswrap/syswrap-linux.c +++ b/coregrind/m_syswrap/syswrap-linux.c @@ -269,12 +269,12 @@ static void run_a_thread_NORETURN ( Word tidW ) #elif defined(VGP_arm64_linux) asm volatile ( "str %w1, %0\n" /* set tst->status = VgTs_Empty (32-bit store) */ - "mov x8, %2\n" /* set %r7 = __NR_exit */ - "ldr x0, %3\n" /* set %r0 = tst->os_state.exitcode */ + "mov x8, %2\n" /* set %x8 = __NR_exit */ + "ldr x0, %3\n" /* set %x0 = tst->os_state.exitcode */ "svc 0x\n" /* exit(tst->os_state.exitcode) */ : "=m" (tst->status) : "r" (VgTs_Empty), "n" (__NR_exit), "m" (tst->os_state.exitcode) - : "r0", "r7" + : "x0", "x8" ); #elif defined(VGP_s390x_linux) asm volatile ( Reproducible: Always Steps to Reproduce: On Android platform, use clang/llvm to build external/valgrind for aosp_arm64-eng target. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368756] Plasmashell adds obsolete widgets
https://bugs.kde.org/show_bug.cgi?id=368756 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from David Edmundson --- >No, I don't. So I am supposed to do that? This makes testing of widgets (where >plasmawindowed is not enough) quite difficult. Yes. Sorry. QML internally has a component cache. So when you instantiate it the seocnd time you're not loading the source again. Theoretically calling engine->trimComponentCache() on applet removal might do it.. but it will still make it slower for our users. plasmoidviewer from plasma-sdk should be better than plasmawindowed. (though it's still not great, feel free to improve it) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368806] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=368806 David Edmundsonchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Thanks *** This bug has been marked as a duplicate of bug 346517 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 346517] Plasmashell crashed after starting gparted
https://bugs.kde.org/show_bug.cgi?id=346517 David Edmundsonchanged: What|Removed |Added CC||rainer+kdeb...@7val.com --- Comment #37 from David Edmundson --- *** Bug 368806 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 368809] Plasma Crashes times to times when in the Main Aplication Laucher one search for Konsole
https://bugs.kde.org/show_bug.cgi?id=368809 David Edmundsonchanged: What|Removed |Added Product|plasmashell |frameworks-baloo Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com Target Milestone|1.0 |--- Component|general |general Version|5.6.5 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368822] Laptop is suspended when locked even though it's connected to a power source
https://bugs.kde.org/show_bug.cgi?id=368822 --- Comment #3 from anewuser--- Note: I've used a BIOS setting that sets a 80% limit for my )Samsung) battery change. This has never been a problem though. When it's at that value, Windows just changes the battery status to "not charging", and Linux keeps displaying "charging - 79%", but this has never interfered with any energy options. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368822] Laptop is suspended when locked even though it's connected to a power source
https://bugs.kde.org/show_bug.cgi?id=368822 --- Comment #2 from anewuser--- Created attachment 101090 --> https://bugs.kde.org/attachment.cgi?id=101090=edit Energy settings 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368822] Laptop is suspended when locked even though it's connected to a power source
https://bugs.kde.org/show_bug.cgi?id=368822 --- Comment #1 from anewuser--- Created attachment 101089 --> https://bugs.kde.org/attachment.cgi?id=101089=edit Energy settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368822] New: Laptop is suspended when locked even though it's connected to a power source
https://bugs.kde.org/show_bug.cgi?id=368822 Bug ID: 368822 Summary: Laptop is suspended when locked even though it's connected to a power source Product: plasmashell Version: 5.7.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: caip...@fastmail.fm CC: plasma-b...@kde.org Neon now suspends my session even though I haven't changed my settings. Reproducible: Always Steps to Reproduce: 1. Set your energy saving settings to never suspend on AC power, but to suspend on battery after 20 minutes 2. Lock the screen but kept your laptop plugged in without closing the lid Actual Results: Laptop is suspended when you come back. Expected Results: Laptop should stay turned on with just the screen locked up. This wasn't a problem until this week on KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368603] crash when starting an lldb debug session
https://bugs.kde.org/show_bug.cgi?id=368603 Aetf <7437...@gmail.com> changed: What|Removed |Added Attachment #101058|0 |1 is obsolete|| --- Comment #14 from Aetf <7437...@gmail.com> --- Created attachment 101088 --> https://bugs.kde.org/attachment.cgi?id=101088=edit Add propper detection of version string on OS X -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 366302] DVB-S tuning fails since 2.0 upgrade
https://bugs.kde.org/show_bug.cgi?id=366302 --- Comment #2 from Martin Weinelt--- Yes, LNB settings should be fine. Did not change anything there between 1.4 and 2.0. % kaffeine -d --dumpdvb 14-09-16 23:52:08.026 [Debug ] src/backend-vlc/vlcmediawidget.cpp#78: bool VlcMediaWidget::init(): Using libVLC with args: --no-video-title-show 14-09-16 23:52:08.084 [Info] src/dvb/dvbmanager.cpp#600: void DvbManager::loadDeviceManager(): Using built-in dvb device manager 14-09-16 23:52:08.591 [Warning ] src/dvb/dvbdevice_linux.cpp#143: void DvbLinuxDevice::startDevice(const QString&): Unsupported transmission type: 4 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb UNIVERSAL 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb DBS 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb EXTENDED 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb STANDARD 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb ENHANCED 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb C-BAND 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb C-MULT 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb DISHPRO 14-09-16 23:52:08.591 [Debug ] src/dvb/dvbdevice_linux.cpp#191: void DvbLinuxDevice::startDevice(const QString&): supports lnb 110BS 14-09-16 23:52:08.591 [Info] src/dvb/dvbdevice_linux.cpp#201: void DvbLinuxDevice::startDevice(const QString&): Found dvb device P18224e35153b1179: STB0899 Multistandard 14-09-16 23:52:29.249 [Debug ] src/dvb/dvbrecording.cpp#543: void DvbRecordingModel::findNewRecordings(): executed. 14-09-16 23:52:29.249 [Debug ] src/dvb/dvbrecording.cpp#337: void DvbRecordingModel::removeDuplicates(): executed. 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): Device STB0899 Multistandard (/dev/dvb/adapter0/frontend0) capabilities: 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): CAN_2G_MODULATION 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): CAN_FEC_AUTO 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): CAN_INVERSION_AUTO 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): CAN_QPSK 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DVB API Version 5.10, Current v5 delivery system: DVBS 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): Supported delivery systems: 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): [DVBS] 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DVBS2 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DSS 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbscan.cpp#300: DvbScan::DvbScan(DvbDevice*, const QString&, const QList&, bool): Use other NIT is disabled 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbscan.cpp#634: void DvbScan::updateState(): Transponder 0/1 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#918: virtual bool DvbLinuxDevice::satSetup(QString, int, int): Using LNBf type UNIVERSAL 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#932: virtual bool DvbLinuxDevice::tune(const DvbTransponder&): tune to: S 12551500 V 2200 5/6 14-09-16 23:52:39.001 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DiSEqC VOLTAGE: 13 14-09-16 23:52:39.002 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DiSEqC TONE: OFF 14-09-16 23:52:39.017 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DiSEqC command: e0 10 38 f5 14-09-16 23:52:39.141 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DiSEqC BURST: SEC_MINI_B 14-09-16 23:52:39.208 [Debug ] src/dvb/dvbdevice_linux.cpp#84: void dvbv5_log(int, const char*, ...): DiSEqC TONE: ON 14-09-16 23:52:40.701 [Debug ] src/dvb/dvbdevice.cpp#692: void DvbDevice::frontendEvent(): tuning failed on 12551.50 MHz 14-09-16 23:52:40.701 [Debug ] src/dvb/dvbscan.cpp#634: void DvbScan::updateState():
[kdevelop] [Bug 368603] crash when starting an lldb debug session
https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #13 from Aetf <7437...@gmail.com> --- Sorry for the delay. I don't have enough time to do any actual coding due to my course work for a few days. That looks good to me. The reason I didn't add the check for OS X was I can't find the mapping between Linux version string and OS X version string. the lldb plugin on Linux didn't work for you after applied my latest patch? Is it the case that you clicked 'don't ask again' and answered no? There should be some output in the Debug output panel saying that session stopped due to unsupported lldb version. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368820] New: audio-speakers-symbolic is semantically a device icon, yet links (is identical) to a status icon
https://bugs.kde.org/show_bug.cgi?id=368820 Bug ID: 368820 Summary: audio-speakers-symbolic is semantically a device icon, yet links (is identical) to a status icon Product: Breeze Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: andydecle...@gmail.com CC: kain...@gmail.com audio-speakers-symbolic is intended to be used to indicate a *device*, but it is linked/identical to the *status* icon audio-volume-high. These should be distinct icons, especially because it's reasonable to expect multiple audio-related icons to be present in the same visual context in user software. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368820] audio-speakers-symbolic is semantically a device icon, yet links (is identical) to a status icon
https://bugs.kde.org/show_bug.cgi?id=368820 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368819] Unable to unpair a previously connected device
https://bugs.kde.org/show_bug.cgi?id=368819 Tylerchanged: What|Removed |Added CC||tyl...@superlazy.us -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368819] Unable to unpair a previously connected device
https://bugs.kde.org/show_bug.cgi?id=368819 --- Comment #1 from Tyler--- Just FYI, figured out that this is EASILY fixed by deleting the data in /home//.config/kdeconnect/* NBD. Otherwise there is a bit of minor strangeness, but I'm using on Unity, so I can live with that. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368819] Unable to unpair a previously connected device
https://bugs.kde.org/show_bug.cgi?id=368819 Tylerchanged: What|Removed |Added Severity|grave |normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #189 from Nicolas Dietrich--- I've added a related issue in #bug 368818, which describes the panel to be accidently moved to the external panel on the left, however on the vertical position of the primary screen where it's supposed to stay. That bug might be considered a duplicate of this bug here, but I opened a new one, as it has different symptoms and I saw it for the first time yesterday, on neon/unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 --- Comment #3 from Nicolas Dietrich--- I forgot to mention that this happens on neon/unstable since around yesterday (2016-09-13). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368819] New: Unable to unpair a previously connected device
https://bugs.kde.org/show_bug.cgi?id=368819 Bug ID: 368819 Summary: Unable to unpair a previously connected device Product: kdeconnect Version: 1.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: tyl...@superlazy.us I installed the older version (0.8) and then found a way to get 1.0 on my system (YUSS). I ran into a problem when I removed the old version and installed the new. The process went like this Install client on Ubuntu (0.8) Install client on Android Remove client from android Remove client from Ubuntu (0.8) Install client on Ubuntu(1.0) Install client on Android So I go to pair again, and the computer is seeing the phone and says its trusted, the phone sees the computer, but says its not paired. I cannot unpair on the computer to initiate the pairing process again. Reproducible: Always Steps to Reproduce: 1. See above Actual Results: Phone will not send a pair request, computer will not unpair. Ping does not work from the computer either. Expected Results: Unpair, reconnect, win at life I'll figure out where the the software stashes its files and try deleting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 --- Comment #1 from Nicolas Dietrich--- Created attachment 101086 --> https://bugs.kde.org/attachment.cgi?id=101086=edit panel-in-the-air-1.png - see description text -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 --- Comment #2 from Nicolas Dietrich--- Created attachment 101087 --> https://bugs.kde.org/attachment.cgi?id=101087=edit panel-in-the-air-21.png - see description text -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] New: Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 Bug ID: 368818 Summary: Panel on wrong position on wrong screen Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: n...@mailbox.org Plugging an external HDMI monitor with a higher resolution (1920x1200) to my laptop (1920x1080) where the external screen is *left* of the primary screen, leads to the panel being moved to the external screen, however not on the bottom, but 120 px "in the air", which corresponds to the bottom of the primary screen where the panel would actually belong (see attached file "panel-in-the-air-1.png"). If I configure the primary screen to be even more "top" relative to the secondary screen, the panel moves accordingly (see "panel-in-the-air-2.png"). This might be a duplicate of bug #356225, however I didn't see the relative panel positioning issue before, so I decided to open up a new issue. Note that this only happens when the external secondary screen is configured to be *left* of the primary laptop screen! Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 367874] kMail crashes upon Thunderbird-generated invitation confirmations
https://bugs.kde.org/show_bug.cgi?id=367874 --- Comment #5 from Mark Petersen--- Created attachment 101085 --> https://bugs.kde.org/attachment.cgi?id=101085=edit email with outlook invitation -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 367874] kMail crashes upon Thunderbird-generated invitation confirmations
https://bugs.kde.org/show_bug.cgi?id=367874 Mark Petersenchanged: What|Removed |Added CC||petersen...@gmail.com --- Comment #4 from Mark Petersen --- Outlook invitations crash kmail/kontact as soon as the offending email is clicked on. openSuse Tumbleweed kmail5 16.08.0-1.2 I've added a sanitized email that triggers the crash. Mark -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage
https://bugs.kde.org/show_bug.cgi?id=368633 --- Comment #5 from b...@beuc.net --- > Is that the normal, with regard to the xkbcommon dependency? For instance, the result of this comment on your build environment would help :) # rpm -qa | grep xkb -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366558] Face detection does not honour album selection in options
https://bugs.kde.org/show_bug.cgi?id=366558 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/digi ||kam/42ccb101aeb7c3ed79dd41d ||0d10a8f67a53883e2 Version Fixed In||5.2.0 Resolution|--- |FIXED --- Comment #11 from caulier.gil...@gmail.com --- Git commit 42ccb101aeb7c3ed79dd41d0d10a8f67a53883e2 by Gilles Caulier. Committed on 14/09/2016 at 20:23. Pushed by cgilles into branch 'master'. make the album selection widget exclusive with album type : PAlbum or TAlbum (not and operator). This will prevent to scan a selection of PAlbum when TAlbum are selected. Related: bug 335013, bug 334183 FIXED-IN: 5.2.0 M +3-0NEWS M +103 -29 libs/album/albumselectors.cpp M +9-0libs/album/albumselectors.h http://commits.kde.org/digikam/42ccb101aeb7c3ed79dd41d0d10a8f67a53883e2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 335013] The face recognition and detection tool does not respect the albums selection to process
https://bugs.kde.org/show_bug.cgi?id=335013 caulier.gil...@gmail.com changed: What|Removed |Added Latest Commit||http://commits.kde.org/digi ||kam/42ccb101aeb7c3ed79dd41d ||0d10a8f67a53883e2 Version Fixed In||5.2.0 Resolution|DUPLICATE |FIXED --- Comment #12 from caulier.gil...@gmail.com --- Git commit 42ccb101aeb7c3ed79dd41d0d10a8f67a53883e2 by Gilles Caulier. Committed on 14/09/2016 at 20:23. Pushed by cgilles into branch 'master'. make the album selection widget exclusive with album type : PAlbum or TAlbum (not and operator). This will prevent to scan a selection of PAlbum when TAlbum are selected. Related: bug 334183, bug 366558 FIXED-IN: 5.2.0 M +3-0NEWS M +103 -29 libs/album/albumselectors.cpp M +9-0libs/album/albumselectors.h http://commits.kde.org/digikam/42ccb101aeb7c3ed79dd41d0d10a8f67a53883e2 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368817] New: Opening Configure Kmail
https://bugs.kde.org/show_bug.cgi?id=368817 Bug ID: 368817 Summary: Opening Configure Kmail Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: crgla...@gmail.com Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I am trying to open configure kmail to add an IMAP email account. Everytime I have tried to open the configure kmail I have received this crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fee51ece800 (LWP 5998))] Thread 20 (Thread 0x7fed95a6b700 (LWP 6150)): #0 0x7fee47ef303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fee3a2cd9cb in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7fee3a5b3ec0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7fee3a2cd9f9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fee4eb9a02d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fed96d6f700 (LWP 6044)): #0 0x7fee4eb91bfd in poll () at /lib64/libc.so.6 #1 0x7fee4612be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fee4612bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fee4f6adf7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fed880008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fee4f65d8cb in QEventLoop::exec(QFlags) (this=this@entry=0x7fed96d6edd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7fee4f4a406a in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7fee4f4a8899 in QThreadPrivate::start(void*) (arg=0x334aae0) at thread/qthread_unix.cpp:344 #7 0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fee4eb9a02d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fed97570700 (LWP 6041)): #0 0x7fee4eb8dccd in read () at /lib64/libc.so.6 #1 0x7fee3da5f073 in () at /usr/lib64/tls/libnvidia-tls.so.367.35 #2 0x7fee4616cb60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fee4612b999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fee4612bdf8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fee4612bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fee4f6adf7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fed98e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7fee4f65d8cb in QEventLoop::exec(QFlags) (this=this@entry=0x7fed9756fdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #8 0x7fee4f4a406a in QThread::exec() (this=) at thread/qthread.cpp:507 #9 0x7fee4f4a8899 in QThreadPrivate::start(void*) (arg=0x3322120) at thread/qthread_unix.cpp:344 #10 0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fee4eb9a02d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fedb4bea700 (LWP 6022)): #0 0x7fee47ef579c in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7fee47ef14a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7fee47ef1306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7fee472a880c in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7fee472ad731 in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7fee472adbeb in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7fee3da5f0f1 in () at /usr/lib64/tls/libnvidia-tls.so.367.35 #7 0x7fee4616cb60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fee4612b999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #9 0x7fee4612bdf8 in () at /usr/lib64/libglib-2.0.so.0 #10 0x7fee4612bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #11 0x7fee4f6adf7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fed9c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #12 0x7fee4f65d8cb in QEventLoop::exec(QFlags) (this=this@entry=0x7fedb4be9dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #13 0x7fee4f4a406a in QThread::exec() (this=) at thread/qthread.cpp:507 #14 0x7fee4f4a8899 in QThreadPrivate::start(void*) (arg=0x2230fa0) at thread/qthread_unix.cpp:344 #15 0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0 #16 0x7fee4eb9a02d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fedb53eb700 (LWP 6020)): #0 0x7fee4616dd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1
[KBibTeX] [Bug 368732] More options for ID generation: volume number, first page
https://bugs.kde.org/show_bug.cgi?id=368732 Thomas Fischerchanged: What|Removed |Added Latest Commit||a81c4e85d8b2c50a382ea97f464 ||fef7783d6971e Status|CONFIRMED |ASSIGNED Version|0.6 |git (master) --- Comment #2 from Thomas Fischer --- I prepare a first implementation of this request. Please checkout the following commit from my personal clone. The code is based on the current Git master (based on KF5): http://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/a81c4e85d8b2c50a382ea97f464fef7783d6971e Instructions how to build KBibTeX from source are given on this page: https://userbase.kde.org/KBibTeX/Development Please test and confirm -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368802] git master 2016-09-14: Proxies not generated for .mlt files automatically.
https://bugs.kde.org/show_bug.cgi?id=368802 Evert Vorsterchanged: What|Removed |Added Summary|git master 2016-09-14: |git master 2016-09-14: |Proxies not generated for |Proxies not generated for |.mlt files. |.mlt files automatically. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368802] git master 2016-09-14: Proxies not generated for .mlt files.
https://bugs.kde.org/show_bug.cgi?id=368802 --- Comment #2 from Evert Vorster--- My project was set to automatic proxy generation. The mlt files do not automatically get a proxy, and I assumed that the proxy generation did not work at all for it. I will change the heading of this bug to automatic proxy generation for .mlt files do not work. I have just tested, and manual proxy generation does indeed work for .mlt files. Since proxy generation is a type of render, would it be too much to ask to put a render dialog in the clip jobs as well? I would really like to be able to render .mlt files, especially stabilize, to whatever resolution I choose, and add the output to the project automatically Thanks for looking into this one! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368779] Missing translations to Categories column in Kipi Plugins settings
https://bugs.kde.org/show_bug.cgi?id=368779 Alexander Potashevchanged: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime
https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #14 from Frederick Eaton--- On Arch Linux, I think the only non-obvious packages needed to make the example compile are alsa-lib and libsndfile ... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368802] git master 2016-09-14: Proxies not generated for .mlt files.
https://bugs.kde.org/show_bug.cgi?id=368802 --- Comment #1 from Jean-Baptiste Mardelle--- Do you mean automatic creation of proxy? In my tests, I can left click on a .mlt clip in the project bin and ask a proxy, it works correctly. Can you give more details about how you expect the proxy to be build ? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64 and amd64 (membarrier)
https://bugs.kde.org/show_bug.cgi?id=361726 Carl Lovechanged: What|Removed |Added CC||c...@us.ibm.com, ||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime
https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #13 from Philippe Waroquiers--- (In reply to Julian Seward from comment #12) > Philippe, is there anything we can or should do here? The current hypothesis is that an ioctl used by alsa or a sound library is not properly handled by syswrap : the syscall wrapper does not see that the kernel will overwrite a memory zone. However, to confirm this (and fix the wrapper) implies to compile the test program (probably not very difficult, but still it does not compile out of the box: some include and/or dev libs are needed). After that, some knowledge of the sound ioctl-s are needed to see if/what is wrong. My knowledge of the sound sycalls are close to 0, so I cannot do this without a significant time (that I do not have); So, in summary, yes, there are things to do, but nobody has time to volunteer for the moment. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361405] disInstr(ppc): unhandled instruction: 0xFF81010C
https://bugs.kde.org/show_bug.cgi?id=361405 Carl Lovechanged: What|Removed |Added CC||c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage
https://bugs.kde.org/show_bug.cgi?id=368633 --- Comment #4 from b...@beuc.net --- Hi, I downloaded and installed CentOS-6.8-x86_64-bin-DVD1.iso, with the default Desktop install target (Gnome). I noted that mesa-libGLU-devel is not installed by default : $ rpm -q mesa-libGLU-devel package mesa-libGLU-devel is not installed So maybe I didn't make the same install as you, or you installed that package manually at a point? I also noticed this when in the build-deps.sh step, ext_qt part: xkbcommon-x11... yes (bundled copy, XKB config root: /usr/share/X11/xkb) xkbcommon-evdev. no Is that the normal, with regard to the xkbcommon dependency? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit
https://bugs.kde.org/show_bug.cgi?id=353825 Monty Scrogginschanged: What|Removed |Added CC||bugs.kde.org@master-minds.n ||et --- Comment #25 from Monty Scroggins --- I have been doing some testing since I cannot get kde to start over x2go with plasma5 (linux Mint 18 x64). I am getting the same KCMInit issue on startup. To see if the issue is X2go related, I downloaded and installed nomachine. I did not experience the same DCMInit issue and the desktop did load remotely. Unfortunately nomachine isnt nearly as fast as x2go (at least for me over my internet connection) so its not a viable alternative. Linux Mint 18 KDE x2goclient 4.0.5.1-1 x2goserver 4.0.1.19-0~1064~ubuntu16.04.1 I hope this info is helpful -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 368583] Konqueror crashes on most websites (Debian 8 32-bit, Pentium III processors) (QTWebKit)
https://bugs.kde.org/show_bug.cgi?id=368583 --- Comment #4 from Christoph Feck--- Bugs for QtWebKit are tracked at the WebKit bugtracker. But before reporting there, please make sure you are using newest version. For more information, see http://qtwebkit.blogspot.de/2016/08/qtwebkit-im-back.html -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 360176] [Openconnect] openconnect fails with "Necessary secrets were not provided"
https://bugs.kde.org/show_bug.cgi?id=360176 Michael Palimakachanged: What|Removed |Added CC||kensing...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368816] New: git master - Saving a project doesn't automatically add the ".kdenlive" extension to the file name
https://bugs.kde.org/show_bug.cgi?id=368816 Bug ID: 368816 Summary: git master - Saving a project doesn't automatically add the ".kdenlive" extension to the file name Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jesse.dub...@gmail.com I just started a new project and saved it. When I closed Kdenlive and went to open it again, The Kdenlive open project dialog window couldn't find it. In my file browser, I went to the file and noticed it didn't have a ".kdenlive" extension automatically at the end of it. Adding ".kdenlive" at the end, manually, allowed Kdenlive to see and open the project file. Reproducible: Always Steps to Reproduce: 1. Create new project. 2. Save project (without manually adding the ".kdenlive" part) Actual Results: Kdenlive doesn't save the project with the ".kdenlive" extension. Expected Results: Kdenlive should save the project with the ".kdenlive" extension. Bug discovered while using Kdenlive 16.11.70 git master build via ppa:kdenlive/kdenlive-master Ubuntu GNOME 16.10 beta 1, GNOME 3.20 desktop environment KDE Frameworks 5.24.0 Qt 5.6.1 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 --- Comment #7 from piedro--- Fixed for me as well, thx a lot! Some other background services are still autostarting but kalarm isn't anymore. Cheers and ty, p. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 368583] Konqueror crashes on most websites (Debian 8 32-bit, Pentium III processors) (QTWebKit)
https://bugs.kde.org/show_bug.cgi?id=368583 paul.dallas.sv...@gmail.com changed: What|Removed |Added Summary|Konqueror crashes on most |Konqueror crashes on most |websites (Debian 8 32-bit, |websites (Debian 8 32-bit, |Pentium III processors) |Pentium III processors) ||(QTWebKit) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365904] "The process for the file protocol died unexpectedly." in all dolphin related places
https://bugs.kde.org/show_bug.cgi?id=365904 --- Comment #4 from Mathias Homann--- (In reply to Mathias Homann from comment #3) > I can confirm this on openSUSE Leap 42.1 using KF5.7.5 mathias@kirika:~> rpm -qi dolphin Name: dolphin Version : 15.12.3 Release : 21.1 Architecture: x86_64 Install Date: Mi 14 Sep 2016 17:55:08 CEST Group : Productivity/File utilities Size: 1415402 License : GPL-2.0+ Signature : RSA/SHA256, Fr 01 Apr 2016 00:12:09 CEST, Key ID b88b2fd43dbdc284 Source RPM : dolphin-15.12.3-21.1.src.rpm Build Date : Fr 01 Apr 2016 00:11:18 CEST Build Host : lamb07 Relocations : (not relocatable) Packager: http://bugs.opensuse.org Vendor : openSUSE URL : http://www.kde.org/ Summary : KDE File Manager Description : This package contains the default file manager of KDE Workspaces. Distribution: openSUSE Leap 42.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365904] "The process for the file protocol died unexpectedly." in all dolphin related places
https://bugs.kde.org/show_bug.cgi?id=365904 --- Comment #3 from Mathias Homann--- I can confirm this on openSUSE Leap 42.1 using KF5.7.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368794] digiKam crashes with lossy dng image
https://bugs.kde.org/show_bug.cgi?id=368794 Maik Qualmannchanged: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- Do not crash here on Linux, only an error message from Exiv2 in the console. I check it again on Windows. Do you use determine settings for the DNG import? Maik -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 368815] New: Crash during login on kubuntu
https://bugs.kde.org/show_bug.cgi?id=368815 Bug ID: 368815 Summary: Crash during login on kubuntu Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: christophe@gmail.com Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-24-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Nothing special. Just login with valid credentials and it crashes. Happens % of the time - Unusual behavior I noticed: - Login progress bar very slow right before crash - Desktop settings (favourits, multi-monitor layout) always disappear after boot The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f542049b8c0 (LWP 3358))] Thread 2 (Thread 0x7f5415650700 (LWP 3627)): [KCrash Handler] #6 mdb_txn_begin (env=0x0, parent=parent@entry=0x0, flags=flags@entry=0, ret=ret@entry=0x7f541564fb38) at mdb.c:2773 #7 0x7f541f68499b in Baloo::Transaction::Transaction (this=0x7f541564fb30, db=..., type=Baloo::Transaction::ReadWrite) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:53 #8 0x0041df73 in Baloo::ModifiedFileIndexer::run (this=0x9c3ac0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/modifiedfileindexer.cpp:49 #9 0x7f541efa3343 in QThreadPoolThread::run (this=0xa3d7a0) at thread/qthreadpool.cpp:93 #10 0x7f541efa684e in QThreadPrivate::start (arg=0xa3d7a0) at thread/qthread_unix.cpp:331 #11 0x7f541dc0a6fa in start_thread (arg=0x7f5415650700) at pthread_create.c:333 #12 0x7f541e5b3b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f542049b8c0 (LWP 3358)): #0 0x7f541e574730 in __opendir (name=0xb9e868 "/home/cca/Documents/develop/android/vanilla_4.0.4/external/opencv3/modules/java/common_test/src/org/opencv/test/utils") at ../sysdeps/posix/opendir.c:200 #1 0x7f541f11f6a9 in QFileSystemIterator::QFileSystemIterator (this=0xb9e250, entry=..., filters=..., nameFilters=..., flags=...) at io/qfilesystemiterator_unix.cpp:58 #2 0x7f541f09ff92 in QDirIteratorPrivate::pushDirectory (this=this@entry=0xb90830, fileInfo=...) at io/qdiriterator.cpp:199 #3 0x7f541f0a10eb in QDirIteratorPrivate::QDirIteratorPrivate (this=0xb90830, entry=..., nameFilters=..., filters=..., flags=..., resolveEngine=) at io/qdiriterator.cpp:168 #4 0x7f541f0a1849 in QDirIterator::QDirIterator (this=0xb9d8a0, path=..., filters=..., flags=...) at io/qdiriterator.cpp:422 #5 0x00424889 in Baloo::FilteredDirIterator::next (this=0x828730) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/filtereddiriterator.cpp:70 #6 0x00431808 in KInotify::Private::_k_addWatches (this=0x83b080) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/kinotify.cpp:163 #7 0x0042eff1 in KInotify::qt_static_metacall (_o=, _c=, _id=, _a=0xb1c370) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:159 #8 0x7f541f1b6ea1 in QObject::event (this=0x7dafc0, e=) at kernel/qobject.cpp:1239 #9 0x7f541f18760c in QCoreApplication::notify (event=0xb0d450, receiver=0x7dafc0, this=0x7ffe93409340) at kernel/qcoreapplication.cpp:1038 #10 QCoreApplication::notifyInternal (this=0x7ffe93409340, receiver=0x7dafc0, event=event@entry=0xb0d450) at kernel/qcoreapplication.cpp:965 #11 0x7f541f189a26 in QCoreApplication::sendEvent (event=0xb0d450, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #12 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x76fde0) at kernel/qcoreapplication.cpp:1593 #13 0x7f541f189f08 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #14 0x7f541f1dd673 in postEventSourceDispatch (s=0x771220) at kernel/qeventdispatcher_glib.cpp:271 #15 0x7f541b7781a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f541b778400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f541b7784ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f541f1dda7f in QEventDispatcherGlib::processEvents (this=0x771610, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #19 0x7f541f184dea in QEventLoop::exec (this=this@entry=0x7ffe93409280, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #20 0x7f541f18ce8c in QCoreApplication::exec () at
[konversation] [Bug 235562] Can't perform nick completion on a prefix following an opening parenthesis
https://bugs.kde.org/show_bug.cgi?id=235562 Peter Simonssonchanged: What|Removed |Added Status|CONFIRMED |RESOLVED CC||peter.simons...@gmail.com Resolution|--- |FIXED --- Comment #1 from Peter Simonsson --- Commit 9532fc0eeae7ff32a20ec8349e6f5850396aca43 fixes this issue -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 368814] New: Compositor fails to load desktop effects with OpenGL
https://bugs.kde.org/show_bug.cgi?id=368814 Bug ID: 368814 Summary: Compositor fails to load desktop effects with OpenGL Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: alexlon...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Distro: fresh installation of Maui (KDE Neon User Edition). Issue: desktop effects disabled. If I set the compositor to use Xrender instead of OpenGL the effects work. If I switch back to OpenGL the effects stop working (no window shadows, no hot corners etc). Reproducible: Always Steps to Reproduce: 1. System Settings > Hardware > Compositor > Set "OpenGL" instead of Xrender tested the same versions of Plasma (5.7.3) and Frameworks (5.25/5.26) also in Manjaro and everything works. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368813] New: Request for "xorg" icon
https://bugs.kde.org/show_bug.cgi?id=368813 Bug ID: 368813 Summary: Request for "xorg" icon Product: Breeze Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: k...@privat.broulik.de CC: kain...@gmail.com The "xorg" icon is used by KWin and the Task Manager in case a window provides no icon. Currently, it would just show a blank spot which looks strange. Oxygen had an xorg icon. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 306545] Change chat text view font size using Ctrl+Mouse and Ctrl +/-
https://bugs.kde.org/show_bug.cgi?id=306545 Peter Simonssonchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/konv ||ersation/66fc2f36af5290c436 ||e3ff1abc62ad942a1f89ff --- Comment #4 from Peter Simonsson --- Git commit 66fc2f36af5290c436e3ff1abc62ad942a1f89ff by Peter Simonsson. Committed on 14/09/2016 at 17:56. Pushed by psn into branch 'master'. Add font zooming to ircview Ported patch by mayank jha to KF5 M +5-1data/konversationui.rc M +27 -0src/mainwindow.cpp M +30 -0src/viewer/ircview.cpp M +5-0src/viewer/ircview.h M +26 -2src/viewer/viewcontainer.cpp M +4-0src/viewer/viewcontainer.h http://commits.kde.org/konversation/66fc2f36af5290c436e3ff1abc62ad942a1f89ff -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 313806] Add an option to enable the key as the "action key" when cropping.
https://bugs.kde.org/show_bug.cgi?id=313806 --- Comment #8 from Christoph Feck--- You can see recent commits to Gwenview at https://quickgit.kde.org/?p=gwenview.git Regarding the Enter key: It looks like the Crop button is already the default button, but even if the crop "dialog" is active, the Enter key is hijacked by some other widget. So just looking at the crop code will not help. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368172] Cannot connect to app on Android 4.4.4 -- SSLHandshakeException
https://bugs.kde.org/show_bug.cgi?id=368172 k...@fedaix.de changed: What|Removed |Added CC||k...@fedaix.de -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 335654] reported versions of several applications are not registered on bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=335654 --- Comment #9 from Till Schäfer--- frameworks kio: https://phabricator.kde.org/T3747 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 109426] ppc: false positive in rt_sigaction
https://bugs.kde.org/show_bug.cgi?id=109426 Carl Lovechanged: What|Removed |Added CC||c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365199] plasma-pa OSD show speaker with different size if muted.
https://bugs.kde.org/show_bug.cgi?id=365199 Till Schäferchanged: What|Removed |Added Version|5.7.0 |5.7.5 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352364] ppc64: --expensive-definedness-checks=yes is not quite working here
https://bugs.kde.org/show_bug.cgi?id=352364 Carl Lovechanged: What|Removed |Added CC||c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363024] Kontact 16.08.1: New contact editor misses options to display messages in HTML
https://bugs.kde.org/show_bug.cgi?id=363024 Till Schäferchanged: What|Removed |Added Summary|Kontact 16.04.0: New|Kontact 16.08.1: New |contact editor misses |contact editor misses |options to display messages |options to display messages |in HTML |in HTML -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 322593] Power 8 code to implement Transactional support
https://bugs.kde.org/show_bug.cgi?id=322593 Carl Lovechanged: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 322593] Power 8 code to implement Transactional support
https://bugs.kde.org/show_bug.cgi?id=322593 Carl Lovechanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Carl Love --- This bugzilla was a place holder for the transactional memory support discussion. Bugzilla 346474 contains the patch for the PPC64 transacational memory support. The patch from Bugzilla 346474 was committed on April 22, 2015, VEX commit 3143, Valgrind commit 15134. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363027] KMail2 5.3.1: Per folder HTML settings are not working
https://bugs.kde.org/show_bug.cgi?id=363027 Till Schäferchanged: What|Removed |Added Summary|KMail 16.04.0: Per folder |KMail2 5.3.1: Per folder |HTML settings are not |HTML settings are not |working |working Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #7 from Till Schäfer --- i have to re-open this as the per-folder settings again have no effect in kmail2 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363024] Kontact 16.04.0: New contact editor misses options to display messages in HTML
https://bugs.kde.org/show_bug.cgi?id=363024 Till Schäferchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Till Schäfer --- confirmed by Laurent Montel in Bug 363027 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 178320] Konsole split view: in both views same content
https://bugs.kde.org/show_bug.cgi?id=178320 --- Comment #40 from xliiv--- I've suspended my work on this, because it took me too much time to learn c++/cmake/compile working in this project in general and I simple got bored by real coding of the feature. Anyway I could share my experience, which is this: First steps, Vincecio's work: I made successfully port of Vincencio's work to qt5 (perhaps it's this branch https://github.com/xliiv/konsole-multi-terminal/tree/kde5port I'm not sure :)). It worked with some minor flaws, like closing last terminal didn't trigger window closing etc. But it worked. However my tests were very limited, like compile do some splits, close terminal, etc. Then i thought about Yakuake. Experimenting with Yakuake: After that I thought that I could "reuse" some of work from Yakuake project. I started to play a bit with Yakuake and as far as i remember I extracted some code of Yakuake project and got simple minimal splitable terminal application based on Yakuake project. I've got it on private repo so I could publish it if anyone is interested. Back to Konsole: Next step was to reuse knowlegde and code from `experimenting with Yakuake` step in Konsole project. I got working horizontal split using Yakuake concept, but it was very non-production version. And then i started to reanalyze it. Because it's complex topic. Feature creation is one thing and shipping it is another thing. Not saying about the KPart should still works. And what about current split which should be removed(?). It's very complex case which lead me to the conslusion that the easiest way of doing this is to create a new application. The new application would adopt KPart (like Yakuake did). Because Yakuake is almost Konsole with splits. Yakuake doesn't allow you to run more than one instance but this is very easy change comparing it to deep down design changes in Konsole views/splits etc. And such deep changes are vary hard without A LOT OF TESTS. However I'm not sure if this solution (like new application) is acceptable by Konsole/KDE maintainers? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 143087] flexible separator widget for toolbars
https://bugs.kde.org/show_bug.cgi?id=143087 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 326795] Flexible spacers don’t work [regression]
https://bugs.kde.org/show_bug.cgi?id=326795 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 352651] Widgets get pushed off the panel despite flexible spacer [regression]
https://bugs.kde.org/show_bug.cgi?id=352651 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368416] Add tc06_two_races_xml.exp output for ppc64.
https://bugs.kde.org/show_bug.cgi?id=368416 Carl Lovechanged: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368416] Add tc06_two_races_xml.exp output for ppc64.
https://bugs.kde.org/show_bug.cgi?id=368416 Carl Lovechanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Carl Love --- Verified patch commit is OK using fresh pull of the upstream repository. It checks out fine. Closing -- You are receiving this mail because: You are watching all bug changes.