[kwin] [Bug 361534] Kwin crashes while playing games 2D Using OpenGL?
https://bugs.kde.org/show_bug.cgi?id=361534 --- Comment #3 from Thomas Lübking --- "during the problem" has > Compositing > === > Compositing is not active Is that correct? Sounds as if the decoration window still includes some shadow padding? Can you please dump xwinfinfo and xprop of the damaged area? Run: xwinfinfo > damage.info; xwinfinfo > damage.props The cursor will turn into a "+" twice, just click somewhere into the damaged area next to the border. The output will be redirected into two files damage.info & damage.props. Please attach them *here* - do in general not use paste.kde.org nor dropbox for relevant bug information, since that information might be lost for future bug readers. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 322586] Unknown instruction (bextr) in ld-2.15.so with --march=native on AMD FX-8350
https://bugs.kde.org/show_bug.cgi?id=322586 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 336768] vex mips->IR: unhandled instruction bytes: 0x3B 0xE8 0x3 0xEC
https://bugs.kde.org/show_bug.cgi?id=336768 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 310845] Application being checked generates illegal instruction
https://bugs.kde.org/show_bug.cgi?id=310845 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 323070] The presentation mode of Okular does not allow to zoom in or out
https://bugs.kde.org/show_bug.cgi?id=323070 jp-willm changed: What|Removed |Added CC||jp.wi...@gmail.com --- Comment #11 from jp-willm --- Bonjour, Okular has many usefull features, but two very important are missing : - zoom in presentation mode - tool-bar icon to invert text color jp willm http://willms.pagesperso-orange.fr/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361544] New: Plasma shell crash when opening WLAN connection
https://bugs.kde.org/show_bug.cgi?id=361544 Bug ID: 361544 Summary: Plasma shell crash when opening WLAN connection Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: t.rot...@netzwissen.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Changed from an active WLAN connection to a new one in network plasmoid The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa38d312800 (LWP 15016))] Thread 37 (Thread 0x7fa37627c700 (LWP 15018)): #0 0x7fa38681abbd in poll () at /lib64/libc.so.6 #1 0x7fa38b76a422 in () at /usr/lib64/libxcb.so.1 #2 0x7fa38b76c00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fa3789ff3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7fa36f1ca700 (LWP 15021)): #0 0x7fa386816c8d in read () at /lib64/libc.so.6 #1 0x7fa37e9bf073 in () at /usr/lib64/tls/libnvidia-tls.so.361.42 #2 0x7fa382f39b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa382ef8999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa382ef8df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7fa38a220df8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #11 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7fa36270b700 (LWP 15044)): #0 0x7fa382f3acf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fa382ef8e4a in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa38a220df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fa360e18700 (LWP 15057)): #0 0x7fa38681abbd in poll () at /lib64/libc.so.6 #1 0x7fa382ef8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa38a220df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fa386f1332f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fa35b3ef700 (LWP 15085)): #0 0x7fa38602803f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa38c9ef86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fa38c9ef899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fa3860240a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fa386822fed in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fa358846700 (LWP 15111)): #0 0x7fa38681abbd in poll () at /lib64/libc.so.6 #1 0x7fa382ef8e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa382ef8f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa387145d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa3870ecd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa386f0e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa38adbc282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7fa386f1332f in () at /usr/lib64/libQt5C
[kleopatra] [Bug 358392] Key could not be certified. Certificate expired, but NOT!
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #13 from rigel3925-w...@yahoo.com --- Since my last comment I have stopped using Windows XP (32 bit) due to Google Chrome announcing an end of support date. I installed Windows 7 64-bit on a fresh partition along with Thunderbird, Enigmail and Kleopatra. I've redirected my documents directories to another drive partition, but I have left "documents and settings" alone since it's protected and I haven't blindly followed anyone's hacks yet. I still get the same error when trying to certify Facebook's public certificate which is the only other certificate besides my own I have stored so far: The certificate could not be certified. Error: Certificate expired My certificate is valid forever, and Facebook's is valid until 2018-05-17; two more years from now. ... I now see under "Technical Details" that Facebook's certificate has a part that will expire on 2016-06-12, two months from now, and a part that expired 2015-11-14, before I started trying to certify the certificate. Facebook has two fingerprints published--one for the main key and one for an "operational subkey". Instead having only one personal certification for the entirety of Facebook's certificate, it appears that each component part of the certificate should be independently certified with the different published fingerprints. The code in Kleopatra needs to be expanded in this way. Is encrypted email starting to take off and become ubiquitous now? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Ingmar Vanhassel changed: What|Removed |Added CC||ing...@exherbo.org -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361543] New: KAlarm Automatically Creates New Calendar Named "akonadi_kalarm_resource_N+1" Every Time a New Calender is Created (Add)
https://bugs.kde.org/show_bug.cgi?id=361543 Bug ID: 361543 Summary: KAlarm Automatically Creates New Calendar Named "akonadi_kalarm_resource_N+1" Every Time a New Calender is Created (Add) Product: kalarm Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Akonadi Assignee: djar...@kde.org Reporter: kdebugs.anon...@yahoo.com Every time a new alarm calendar file is Added, KAlarm automatically and immediately also creates a calender in the "Calanders" column named "akonadi_kalarm_resource_N+1", where "N+1" is an integer 1 greater than the last created alarm calendar. For example, "akonadi_kalarm_resource_21". When I select (right-click) an "akonadi_kalarm_resource_N+1" calendar and click the menu option labeled "Edit", I discover the "akonadi_kalarm_resource_N+1" contains the same data as the newly added calendar that immediately preceded the creation of the "akonadi_kalarm_resource_N+1" calendar. For example, If I Add a new calendar named "Test", KAlarm immediately and automatically adds a calendar named "akonadi_kalarm_resource_10". When I select (right-click) the "akonadi_kalarm_resource_10" calendar and click the menu option labeled "Edit", I discover "akonadi_kalarm_resource_10" contains the same data as the calendar named "Test". If the automatically created "akonadi_kalarm_resource_10" calender is deleted, the newly added "Test" calender tied to "akonadi_kalarm_resource_10" is automatically deleted. This undesirable behavior happens every time, even in a newly created Linux account. KAlarm Version 2.11.4-5ak Using: KDE Frameworks 5.20.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system Running on openSUSE Leap 42.1 from openSUSE binary RPM's Reproducible: Always Steps to Reproduce: 1) Click the "Add" button in the column labeled "Calendars". 2) Click the option labeled "KAlarm Calendar File". 3) Enter "/home/tux/Test 13.ics" in the text field labeled "Filename:". 4) Enter "Test 13" in the text field labeled "Name:". 5) Click the button labeled "OK". Actual Results: KAlarm creates a calender named "Test 13", and also immediately creates a calender named "akonadi_kalarm_resource_11" that is tied to the calender named "Test 13". Expected Results: KAlarm should have created ONLY a new calendar with the name specified during creation. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 361542] New: akonadictl fsck seems to hang
https://bugs.kde.org/show_bug.cgi?id=361542 Bug ID: 361542 Summary: akonadictl fsck seems to hang Product: Akonadi Version: unspecified Platform: Chakra OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: knut.hildebra...@gmx.de A way to get rid of left over mails in ~/.local/share/akonadi/file_db_data is invoking "akonadictl fsck" which moves all entries not in use anymore to ~/.local/share/akonadifile_lost+found from where they can be deleted. That worked fine for me until recently. After an update earlier this week "akonadictl fsck" seems to hang. Even if I run it for hours it neither finishes nor is there any output on the console. Reproducible: Always Steps to Reproduce: 1. stop Akonadi: akonadictl stop 2. wait some time to let Akonadi stop 3. check that Akonadi has stopped: akonadictl status 4. run Akonadi filecheck: akonadictl fsck Actual Results: it runs for ever without any output Expected Results: it should stop after a while and report on console what it has done Output of akonadictl --version -> 5.1.51 Update was from 15.12.3-1 -> 15.12.3-2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361534] Kwin crashes while playing games 2D Using OpenGL?
https://bugs.kde.org/show_bug.cgi?id=361534 --- Comment #2 from wolfyrion --- I have posted the 3 text output files in dropbox - folder corruption https://www.dropbox.com/sh/jjnfxt3qsv7ncih/AABfLxFw93N-SSAEsM7hb0_Va?dl=0 Text files no problem --> without the problem during the problem --> while running a specific game in sdlmame disabling the compositor with the problem --> exiting the game but having the texture corruption https://www.dropbox.com/sh/jjnfxt3qsv7ncih/AABfLxFw93N-SSAEsM7hb0_Va?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc
https://bugs.kde.org/show_bug.cgi?id=357800 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361541] New: Crash when connecting to HDMI
https://bugs.kde.org/show_bug.cgi?id=361541 Bug ID: 361541 Summary: Crash when connecting to HDMI Product: plasmashell Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jessetalav...@aol.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I had opened VLC to watch a video a few seconds ago. After VLC had already opened, I turned on my TV, which my laptop was already connected to via HDMI. The screen went dark for a moment, then Plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a139b0800 (LWP 12479))] Thread 8 (Thread 0x7f0a1130c700 (LWP 12481)): #0 0x7f0a2047388d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0a244babd2 in poll (__timeout=-1, __nfds=1, __fds=0x7f0a1130bcc0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1047200, cond=cond@entry=0x1047240, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7f0a244bc74f in xcb_wait_for_event (c=0x1047200) at ../../src/xcb_in.c:623 #4 0x7f0a13656a39 in QXcbEventReader::run (this=0x1051600) at qxcbconnection.cpp:1105 #5 0x7f0a20b662be in QThreadPrivate::start (arg=0x1051600) at thread/qthread_unix.cpp:337 #6 0x7f0a1fc556aa in start_thread (arg=0x7f0a1130c700) at pthread_create.c:333 #7 0x7f0a2047ee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f0a04afe700 (LWP 12487)): #0 0x7f0a1d264869 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0a1d21f9a1 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a1d220167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a1d2202fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0a20d9d29b in QEventDispatcherGlib::processEvents (this=0x7f0a08c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f0a20d4375a in QEventLoop::exec (this=this@entry=0x7f0a04afdda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f0a20b613d4 in QThread::exec (this=this@entry=0x120f470) at thread/qthread.cpp:503 #7 0x7f0a23389f85 in QQmlThreadPrivate::run (this=0x120f470) at qml/ftw/qqmlthread.cpp:141 #8 0x7f0a20b662be in QThreadPrivate::start (arg=0x120f470) at thread/qthread_unix.cpp:337 #9 0x7f0a1fc556aa in start_thread (arg=0x7f0a04afe700) at pthread_create.c:333 #10 0x7f0a2047ee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f09f8c1b700 (LWP 12551)): #0 0x7f0a1d264884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0a1d22009d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a1d2202fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a20d9d29b in QEventDispatcherGlib::processEvents (this=0x7f09f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f0a20d4375a in QEventLoop::exec (this=this@entry=0x7f09f8c1ada0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f0a20b613d4 in QThread::exec (this=this@entry=0x1445ec0) at thread/qthread.cpp:503 #6 0x7f0a23389f85 in QQmlThreadPrivate::run (this=0x1445ec0) at qml/ftw/qqmlthread.cpp:141 #7 0x7f0a20b662be in QThreadPrivate::start (arg=0x1445ec0) at thread/qthread_unix.cpp:337 #8 0x7f0a1fc556aa in start_thread (arg=0x7f09f8c1b700) at pthread_create.c:333 #9 0x7f0a2047ee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f09f221f700 (LWP 12586)): #0 0x7f0a2047388d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0a1d2201ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a1d2202fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a20d9d29b in QEventDispatcherGlib::processEvents (this=0x7f09e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f0a20d4375a in QEventLoop::exec (this=this@entry=0x7f09f221eda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f0a20b613d4 in QThread::exec (this=this@entry=0x17437b0) at thread/qthread.cpp:503 #6 0x7f0a23389f85 in QQmlThreadPrivate::run (this=0x17437b0) at qml/ftw/qqmlthread.cpp:141 #7 0x7f0a20b662be in QThreadPrivate::start (arg=0x17437b0) at thread/qthread_unix.cpp:337 #8 0x7f0a1f
[kwalletmanager] [Bug 147873] require password before displaying clear text username and password
https://bugs.kde.org/show_bug.cgi?id=147873 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 207828] JJ: Show summary info in System Activity widget
https://bugs.kde.org/show_bug.cgi?id=207828 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361540] New: inconvenient to select "create" for a new file
https://bugs.kde.org/show_bug.cgi?id=361540 Bug ID: 361540 Summary: inconvenient to select "create" for a new file Product: krita Version: 2.9.11 Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: cocolim0...@gmail.com It's not that the button isn't there, but it gets covered up by my taskbar. I can't drag it or minimize it and I can't tab to it. The only way I can get to it is to go into full screen which can get annoying if I have to open something else. Reproducible: Always Steps to Reproduce: 1. have version 2.9.11 2. open it in windows 10, keep it windowed 3. click new file Actual Results: the create button is covered by the taskbar. It can't be moved or minimized and can't be reached by tab Expected Results: show the button in windowed mode -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361539] New: KAlarm Crashes on Creation (Add) of New *.ics Calander File
https://bugs.kde.org/show_bug.cgi?id=361539 Bug ID: 361539 Summary: KAlarm Crashes on Creation (Add) of New *.ics Calander File Product: kalarm Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: djar...@kde.org Reporter: kdebugs.anon...@yahoo.com Application: kalarm (2.11.4-5ak) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: 1) Clicked the "Add" button in the column labeled "Calendars:. 2) Clicked the option labeled "KAlarm Calendar File". 3) Entered "/home/tux/Test 13.ics" in the text field labeled "Filename:". 4) Entered "Test 13"" in the text field labeled "Name:". 5) Clicked the button labeled "OK". 6) KAlarm crashes. The crash can be reproduced every time. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff444541840 (LWP 20108))] Thread 4 (Thread 0x7ff4229ed700 (LWP 20110)): #0 0x7ff43ba7abbd in poll () from /lib64/libc.so.6 #1 0x7ff435dc9422 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7ff435dcb00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7ff424d7e3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7ff43c39132f in QThreadPrivate::start (arg=0x2747490) at thread/qthread_unix.cpp:331 #5 0x7ff435fe60a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7ff43ba82fed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7ff418365700 (LWP 20162)): #0 0x7ff4356dbcf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7ff4356994b9 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff435699d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff435699f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff43c5c3d8b in QEventDispatcherGlib::processEvents (this=0x7ff418e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7ff43c56ad53 in QEventLoop::exec (this=this@entry=0x7ff418364d90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7ff43c38c61a in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7ff43c39132f in QThreadPrivate::start (arg=0x2851c50) at thread/qthread_unix.cpp:331 #8 0x7ff435fe60a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7ff43ba82fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff417b64700 (LWP 20164)): #0 0x7ff435699628 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7ff435699d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff435699f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff43c5c3d8b in QEventDispatcherGlib::processEvents (this=0x7ff4080008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff43c56ad53 in QEventLoop::exec (this=this@entry=0x7ff417b63d90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff43c38c61a in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff43c39132f in QThreadPrivate::start (arg=0x2861ec0) at thread/qthread_unix.cpp:331 #7 0x7ff435fe60a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7ff43ba82fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff444541840 (LWP 20108)): [KCrash Handler] #6 0x7ff43c534a26 in QSortFilterProxyModel::parent (this=0x2863c90, child=...) at itemmodels/qsortfilterproxymodel.cpp:1874 #7 0x7ff43c512d63 in parent (this=) at itemmodels/qabstractitemmodel.h:411 #8 QPersistentModelIndex::parent (this=this@entry=0x2bf8768) at itemmodels/qabstractitemmodel.cpp:365 #9 0x7ff43c5228b8 in isValid (this=0x2bf8760) at itemmodels/qitemselectionmodel.h:123 #10 QItemSelectionModel::isSelected (this=this@entry=0x297c5d0, index=...) at itemmodels/qitemselectionmodel.cpp:1395 #11 0x7ff43da9dacd in QListView::paintEvent (this=0x2977860, e=) at itemviews/qlistview.cpp:960 #12 0x7ff43d87252b in QWidget::event (this=this@entry=0x2977860, event=event@entry=0x7fff5b406ef0) at kernel/qwidget.cpp:8833 #13 0x7ff43d96c43e in QFrame::event (this=0x2977860, e=0x7fff5b406ef0) at widgets/qframe.cpp:540 #14 0x7ff43da8794b in QAbstractItemView::viewportEvent (this=this@entry=0x2977860, event=event@entry=0x7fff5b406ef0) at itemviews/qabstractitemview.cpp:1685 #15 0x005be229 in CollectionView::viewportEvent (this=0x2977860, e=0x7fff5b406ef0) at /usr/src/debug/kdepim-15.12.3/kalarm/collectionmodel.cpp:639 #16 0x7ff43c56d0d3 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x2710f50, receiver=receiver@entry=0x2a21540, event=event@entry=0x7fff5b406ef0) a
[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert&crash on startup
https://bugs.kde.org/show_bug.cgi?id=359255
--- Comment #8 from guruguru...@outlook.jp ---
Testing with Krita3-2.99.89.dmg - a slightly different error message("Krita
cannot find any brush presets! Krita will quit now.") but still can't run.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 361538] New: Text selection misses some characters
https://bugs.kde.org/show_bug.cgi?id=361538 Bug ID: 361538 Summary: Text selection misses some characters Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ODT backend Assignee: okular-de...@kde.org Reporter: jonat...@imatix.com Using either the txt or the odt backend, selected text (either using the selection or the text selection tool) sometimes ignores the final character on a line. I have identified two cases when this happens: 1. If the line contains no white space and is forced to wrap at a non-whitespace character, the final character on the line before the wrap will not be selected. 2. If the file does not contain a final line terminator, the last character on the last line is not selected. Reproducible: Always Steps to Reproduce: 1. Make a simple text or ODT file, for example containing the words 'Hello world' but no line terminator. 2. Load the file into okular 3. Select the final characters of the displayed line. Actual Results: Characters selected do not include the final character on the line. Expected Results: Characters selected should include the final character on the line. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 346322] kmix QAction KAction error
https://bugs.kde.org/show_bug.cgi?id=346322 Lukasz changed: What|Removed |Added CC||dolo...@outlook.com --- Comment #2 from Lukasz --- Still in version 4.6 (15.12.3) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361537] Kate crashes on startup
https://bugs.kde.org/show_bug.cgi?id=361537 --- Comment #1 from Lukasz --- Created attachment 98300 --> https://bugs.kde.org/attachment.cgi?id=98300&action=edit stacktrace -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #67 from EMR_Kde --- Is this fixed yet? I am about to install a new system, and am debating whether to go with Plasma 5 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361537] New: Kate crashes on startup
https://bugs.kde.org/show_bug.cgi?id=361537 Bug ID: 361537 Summary: Kate crashes on startup Product: kate Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: dolo...@outlook.com I am using kdeconnect plugin for accessing content on my mobile device, when I try to open a file there it crashes. But then it starts crashes every time I open any file, not only through kdeconnect. Reproducible: Always Steps to Reproduce: 1. Access file on through kdeconnect. 2. Observe how it crashes. 3. Now open any file on your computer and see it how crashes again. Actual Results: Crash Expected Results: Open files correctly. I removed the following: .local/share/kate .config/katemetainfos .config/katerc no luck -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361536] New: Seems that certain USB disks after being formatted crash the desktop
https://bugs.kde.org/show_bug.cgi?id=361536 Bug ID: 361536 Summary: Seems that certain USB disks after being formatted crash the desktop Product: plasmashell Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@dandart.co.uk CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.6.0-rc2+ x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Inserting a USB disk after formatting with kde partition manager Happened every time The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1589da3800 (LWP 15745))] Thread 16 (Thread 0x7f157501d700 (LWP 15750)): #0 0x7f158455d88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f15885a4bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f15885a674f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f1577367a39 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #4 0x7f1584c502be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1583d3f6aa in start_thread (arg=0x7f157501d700) at pthread_create.c:333 #6 0x7f1584568e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f156e903700 (LWP 15779)): #0 0x7f158455d88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f158130a1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f158130a2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1584e8729b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1584e2d75a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1584c4b3d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1587473f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f1584c502be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1583d3f6aa in start_thread (arg=0x7f156e903700) at pthread_create.c:333 #9 0x7f1584568e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f1562f43700 (LWP 15782)): #0 0x7f158134e884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f158130a306 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1584e8729b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1584e2d75a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1584c4b3d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1587473f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f1584c502be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1583d3f6aa in start_thread (arg=0x7f1562f43700) at pthread_create.c:333 #8 0x7f1584568e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f155bfff700 (LWP 15786)): #0 0x7f158455d88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f158130a1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f158130a2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1584e8729b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1584e2d75a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1584c4b3d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1587473f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f1584c502be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1583d3f6aa in start_thread (arg=0x7f155bfff700) at pthread_create.c:333 #9 0x7f1584568e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f155adf6700 (LWP 15787)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f15897ff114 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f15897ff159 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f1583d3f6aa in start_thread (arg=0x7f155adf6700) at pthread_create.c:333 #4 0x7f1584568e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f14c700 (L
[kdenlive] [Bug 361361] git master - creating a new project in Kdenlive while another is open shows frame from previous project in monitors (video example included)
https://bugs.kde.org/show_bug.cgi?id=361361 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit 5a9f5abdbc063b15162c29943442dd49aabcacc1 by Jean-Baptiste Mardelle. Committed on 08/04/2016 at 23:33. Pushed by mardelle into branch 'Applications/16.04'. Make sure to clear monitors when closing a project M +11 -3src/monitor/glwidget.cpp M +1-0src/monitor/glwidget.h M +4-0src/monitor/monitor.cpp M +2-0src/monitor/monitor.h M +6-0src/monitor/monitormanager.cpp M +1-0src/monitor/monitormanager.h M +2-0src/project/projectmanager.cpp http://commits.kde.org/kdenlive/5a9f5abdbc063b15162c29943442dd49aabcacc1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view
https://bugs.kde.org/show_bug.cgi?id=357479 Lukasz changed: What|Removed |Added CC||dolo...@outlook.com --- Comment #14 from Lukasz --- Created attachment 98299 --> https://bugs.kde.org/attachment.cgi?id=98299&action=edit stracktrace with debug symbols Still on 15.12.3 I will try to dig a little bit by myself. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361535] Dolphin crashes randomly
https://bugs.kde.org/show_bug.cgi?id=361535 --- Comment #1 from Lukasz --- After a little digging in the source code I found that it could be related to #359738. I will try to patch the source code and I will report if its working. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361395] open recent doesn't list recent save after crash
https://bugs.kde.org/show_bug.cgi?id=361395 Jean-Baptiste Mardelle changed: What|Removed |Added Latest Commit||http://commits.kde.org/kden ||live/0a0448f859c26cd5f9b3e0 ||12e7fc33c0f6ce2ba4 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jean-Baptiste Mardelle --- Git commit 0a0448f859c26cd5f9b3e012e7fc33c0f6ce2ba4 by Jean-Baptiste Mardelle. Committed on 08/04/2016 at 23:06. Pushed by mardelle into branch 'Applications/16.04'. Save recent files on each save / open M +0-3src/mainwindow.cpp M +9-0src/project/projectmanager.cpp M +1-0src/project/projectmanager.h http://commits.kde.org/kdenlive/0a0448f859c26cd5f9b3e012e7fc33c0f6ce2ba4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361535] New: Dolphin crashes randomly
https://bugs.kde.org/show_bug.cgi?id=361535 Bug ID: 361535 Summary: Dolphin crashes randomly Product: dolphin Version: 15.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dolo...@outlook.com Application: dolphin (15.12.3) Qt Version: 5.6.0 Frameworks Version: 5.20.0 Operating System: Linux 4.3.6-ck3-ck x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: When I am using dolphin very often crashes unexpectedly, usually I move, delete or switch directories and after a while while I am completely on different workspace it crashes. If someone is interested in more symbols, just tell me. I will try to dig a little bit by myself too. Thank you. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6759aca800 (LWP 16771))] Thread 6 (Thread 0x7f6741de2700 (LWP 16772)): #0 0x7f6759421c3d in poll () from /usr/lib/libc.so.6 #1 0x7f674bf6bae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f674bf6d757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f6743704a99 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f675335dde8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f674ebe6424 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f675942acbd in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f673bfff700 (LWP 16773)): #0 0x7f6759421c3d in poll () from /usr/lib/libc.so.6 #1 0x7f674e05cf7c in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f674e05d08c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f6753586cab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f675352f6fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f6753358fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f6753992a55 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f675335dde8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f674ebe6424 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f675942acbd in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f6739448700 (LWP 16774)): #0 0x7f674ebec03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f673a7a5b03 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f673a7a5257 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f674ebe6424 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f675942acbd in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f67316de700 (LWP 16775)): #0 0x7f6759421c3d in poll () from /usr/lib/libc.so.6 #1 0x7f674e05cf7c in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f674e05d08c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f6753586cab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f675352f6fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f6753358fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f675335dde8 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f674ebe6424 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f675942acbd in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f65e25e1700 (LWP 18286)): #0 0x7f674ebec3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f675335ebc6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f675335a2dc in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f675335dde8 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f674ebe6424 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f675942acbd in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f6759aca800 (LWP 16771)): [KCrash Handler] #5 0x7f67593762a8 in raise () from /usr/lib/libc.so.6 #6 0x7f675937772a in abort () from /usr/lib/libc.so.6 #7 0x7f6753345f41 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #8 0x7f67533412d1 in qt_assert_x(char const*, char const*, char const*, int) () from /usr/lib/libQt5Core.so.5 #9 0x7f67590a6d68 in QVector::at (i=20, this=0x1f7b048) at /usr/include/qt/QtCore/qvector.h:419 #10 KItemListViewAccessible::cell (index=20, this=0x1f7b030) at /home/dlh/abs/src/dolphin-15.12.3/src/kitemviews/kitemlistviewaccessible.cpp:79 #11 KItemListViewAccessible::child (this=0x1f7b030, index=20) at /home/dlh/abs/src/dolphin-15.12.3/src/kitemviews/kitemlistviewaccessible.cpp:262 #12 0x7f6753cda4af in QAccessibleEvent::accessibleInterface() const () from /usr/lib/libQt5Gui.so.5 #13 0x7f6753cda89d in Q
[kwin] [Bug 361534] Kwin crashes while playing games 2D Using OpenGL?
https://bugs.kde.org/show_bug.cgi?id=361534 --- Comment #1 from Thomas Lübking --- Looks like bug #361477 resp. bug #361154 The weird pattern is that suspending the compositor (SHIFT+Alt+F12) prevents the problems, but resuming the compositor (what implies a new GL context) restores the problem. Please attach the output of "qdbus org.kde.KWin /KWin supportInformation" (w/ running compositor, but the problem doesn't need to be present) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361533] Kickoff lacks option to display application name instead of description
https://bugs.kde.org/show_bug.cgi?id=361533 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Well, there's an option in Kickoff settings for exactly that, isn't there? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 357861] yakuake KF5 git (2016-01-11): fokus problems, no active terminal
https://bugs.kde.org/show_bug.cgi?id=357861 Lukasz changed: What|Removed |Added CC||dolo...@outlook.com --- Comment #17 from Lukasz --- Bug #360234 is related, and I can confirm issue on 3.0.2. (In reply to Hugo Parente Lima from comment #13) > Another info, on my machine the bug is only triggered if my settings has 0ms > animation time, with 100ms animation time it works. Works even with 1ms, but not with 0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361534] New: Kwin crashes while playing games 2D Using OpenGL?
https://bugs.kde.org/show_bug.cgi?id=361534 Bug ID: 361534 Summary: Kwin crashes while playing games 2D Using OpenGL? Product: kwin Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kyria...@mypcrevolution.com If I play games like super meat boy or MAME Games (sdlmame) using openg after I finish playing the games all my plasma 5 ui is corrupted. example how it looks http://i.imgur.com/bxGsIkJ.png The worst of all is that anything that I try to open it keeps flashing my whole screen and I have to restart or log out and login back again. Reproducible: Always Steps to Reproduce: 1. just play a game super meat boy from steam or sdlmame games with opengl support 2. 3. Actual Results: After finishing playing the games my whole ui looks like this http://i.imgur.com/bxGsIkJ.png it seems that KWIN compositor is crashing Expected Results: not corrupted graphics -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358083] Modifying the default profile does not work
https://bugs.kde.org/show_bug.cgi?id=358083 Lukasz changed: What|Removed |Added CC||dolo...@outlook.com --- Comment #3 from Lukasz --- I can confirm presence of the issue on konsole 15.12.3 as well as on yakuake 3.0.2 which seems to be based on some common component. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361533] Kickoff lacks option to display application name instead of description
https://bugs.kde.org/show_bug.cgi?id=361533 Janet changed: What|Removed |Added Summary|Kickoff lacks option to |Kickoff lacks option to |display entry name instead |display application name |of description |instead of description -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361533] New: Kickoff lacks option to display entry name instead of description
https://bugs.kde.org/show_bug.cgi?id=361533 Bug ID: 361533 Summary: Kickoff lacks option to display entry name instead of description Product: plasmashell Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: bugzi...@kerridis.de CC: plasma-b...@kde.org Alas Kickoff's only mode is to display the description of the applications. It shows the name of the application only on mouseover, small below the description. I'd love to see it the other way (and I am quite sure it was possible in KDE SC 4): to have the name of the application shown and the description only on mouseover. As it is now I only can identify applications by their icons... Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information
https://bugs.kde.org/show_bug.cgi?id=347344 Christoph Feck changed: What|Removed |Added CC||dat...@hotmail.fr --- Comment #25 from Christoph Feck --- *** Bug 361527 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 357931] KInfoCenter 5.5.3 Crash on close
https://bugs.kde.org/show_bug.cgi?id=357931 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 347344 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 361527] Kinfocenter crashed when I closed it
https://bugs.kde.org/show_bug.cgi?id=361527 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 347344 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information
https://bugs.kde.org/show_bug.cgi?id=347344 --- Comment #24 from Christoph Feck --- *** Bug 357931 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 357211] KinfoCenter 5.5.1 crash on close
https://bugs.kde.org/show_bug.cgi?id=357211 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 347344 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information
https://bugs.kde.org/show_bug.cgi?id=347344 Christoph Feck changed: What|Removed |Added CC||optil...@gmail.com --- Comment #23 from Christoph Feck --- *** Bug 357211 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information
https://bugs.kde.org/show_bug.cgi?id=347344 --- Comment #22 from Christoph Feck --- *** Bug 354083 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 354083] Kinfo crash, if going to shutdown computer
https://bugs.kde.org/show_bug.cgi?id=354083 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 347344 *** -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 360374] Check for QString::left(1) mis-use.
https://bugs.kde.org/show_bug.cgi?id=360374 --- Comment #1 from Sergio Martins --- When shouldn't QString::left(1) be replaced by at(0) ? Wondering if we should just warn for all occurrences. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5
https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #26 from Ivo Raisr --- Followup fix for x86 architecture: SVN r15854. Failed test case was memcheck/tests/addressable built as 32-bit executable which showed: Conditional jump or move depends on uninitialised value(s) at 0x4FFA0E4A: _vgnU_freeres (vg_preloaded.c:68) by 0x2: ??? by 0x8051987: main (addressable.c:125) Uninitialised value was created by a stack allocation at 0x8051473: test2 (addressable.c:42) because parameter 'to_run' was written to a wrong address. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361532] Deleting a track causes crash
https://bugs.kde.org/show_bug.cgi?id=361532 --- Comment #4 from Jean-Baptiste Mardelle --- Git commit 07ba26d6ce812ead4e04c18a7a1bd099e3385db9 by Jean-Baptiste Mardelle. Committed on 08/04/2016 at 20:58. Pushed by mardelle into branch 'Applications/16.04'. Fix crash on undo add track M +4-4src/timeline/customtrackview.cpp http://commits.kde.org/kdenlive/07ba26d6ce812ead4e04c18a7a1bd099e3385db9 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 359927] Cantor crashes when "Integrate plots in Worksheet" is checked (python2)
https://bugs.kde.org/show_bug.cgi?id=359927 Filipe Saraiva changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361532] Deleting a track causes crash
https://bugs.kde.org/show_bug.cgi?id=361532 Jean-Baptiste Mardelle changed: What|Removed |Added Latest Commit||http://commits.kde.org/kden ||live/f30eb161e2482b355ad728 ||10703bba7eb07e7de8 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Jean-Baptiste Mardelle --- Git commit f30eb161e2482b355ad72810703bba7eb07e7de8 by Jean-Baptiste Mardelle. Committed on 08/04/2016 at 20:41. Pushed by mardelle into branch 'Applications/16.04'. Fix crash on track deletion M +3-2src/timeline/customtrackview.cpp M +3-1src/timeline/timeline.cpp http://commits.kde.org/kdenlive/f30eb161e2482b355ad72810703bba7eb07e7de8 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360749] kludge for multiple .rodata sections on Solaris no longer needed
https://bugs.kde.org/show_bug.cgi?id=360749 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Ivo Raisr --- Fixed by SVN r15853. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353802] ELF debug info reader confused with multiple .rodata sections
https://bugs.kde.org/show_bug.cgi?id=353802 --- Comment #9 from Ivo Raisr --- Reverted by bug #360749. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 359927] Cantor crashes when "Integrate plots in Worksheet" is checked (python2)
https://bugs.kde.org/show_bug.cgi?id=359927 --- Comment #2 from Simone Gaiarin --- I've tried now and it works correctly. Maybe updating some python packages fixed the problem. On Fri, Apr 8, 2016 at 8:06 PM Filipe Saraiva via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=359927 > > --- Comment #1 from Filipe Saraiva --- > Hello Simone, I can not to reproduce this bug. Please, can you verify if > you > have this bug yet? > > I run the follow commands: > > x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] > from matplotlib import pylab > pylab.clf() > pylab.plot(x) > pylab.show() > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361532] Deleting a track causes crash
https://bugs.kde.org/show_bug.cgi?id=361532 --- Comment #2 from Ovidiu-Florin BOGDAN --- Created attachment 98297 --> https://bugs.kde.org/attachment.cgi?id=98297&action=edit project file that causes a crash if first track is deleted -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361532] Deleting a track causes crash
https://bugs.kde.org/show_bug.cgi?id=361532 --- Comment #1 from Ovidiu-Florin BOGDAN --- Created attachment 98296 --> https://bugs.kde.org/attachment.cgi?id=98296&action=edit Project file that I used -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361532] Deleting a track causes crash
https://bugs.kde.org/show_bug.cgi?id=361532 Ovidiu-Florin BOGDAN changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361532] Deleting a track causes crash
https://bugs.kde.org/show_bug.cgi?id=361532 Ovidiu-Florin BOGDAN changed: What|Removed |Added Component|general |User Interface Product|kde |kdenlive Assignee|unassigned-b...@kde.org |j...@kdenlive.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 361532] New: Deleting a track causes crash
https://bugs.kde.org/show_bug.cgi?id=361532 Bug ID: 361532 Summary: Deleting a track causes crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ovidiu@gmail.com Application: kdenlive (16.07.70) Qt Version: 5.5.1 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: * Opened a project; * File -> Save as... -> choose other existing project file -> overwrite * check to see that I have the new project file open * delete first track I'm using the master kdenlive ppa for Kubuntu. The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc002a09800 (LWP 10284))] Thread 47 (Thread 0x7fc000192700 (LWP 10285)): #0 0x7fc00dfc588d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fc008ee9bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fc008eeb74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fc0024df7e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fc00e9c3a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc00cbae6aa in start_thread (arg=0x7fc000192700) at pthread_create.c:333 #6 0x7fc00dfd0e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 46 (Thread 0x7fbfde5fc700 (LWP 10286)): #0 0x7fc00dfc588d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fbfe652b12c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x7fc00cbae6aa in start_thread (arg=0x7fbfde5fc700) at pthread_create.c:333 #3 0x7fc00dfd0e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 45 (Thread 0x7fbfd9ce3700 (LWP 10287)): #0 0x7fc00ebfa884 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fc00b1a577d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc00b1a611b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc00b1a62fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc00ebfb50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc00eba250a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc00e9beac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc00f772c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fc00e9c3a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc00cbae6aa in start_thread (arg=0x7fbfd9ce3700) at pthread_create.c:333 #10 0x7fc00dfd0e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 44 (Thread 0x7fbfd8ce2700 (LWP 10288)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fc00e9c4c46 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc00e9c06f3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc00e9c3a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc00cbae6aa in start_thread (arg=0x7fbfd8ce2700) at pthread_create.c:333 #5 0x7fc00dfd0e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 43 (Thread 0x7fbfd3fff700 (LWP 10289)): #0 0x7fc00dfc588d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fc00b1a61ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc00b1a62fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc00ebfb50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc00eba250a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc00e9beac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc00f772c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fc00e9c3a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc00cbae6aa in start_thread (arg=0x7fbfd3fff700) at pthread_create.c:333 #9 0x7fc00dfd0e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 42 (Thread 0x7fbfd155f700 (LWP 10293)): #0 0x7fc00dfc588d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fc00b1a61ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc00b1a62fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7
[Akonadi] [Bug 351628] Akonadi DAV Resource does not sync all calendars on ownCloud any more
https://bugs.kde.org/show_bug.cgi?id=351628 Randy Barlow changed: What|Removed |Added CC||ra...@electronsweatshop.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361207] Valgrind does not support the IBM POWER ISA 3.0 instructions, part 2
https://bugs.kde.org/show_bug.cgi?id=361207
Carl Love changed:
What|Removed |Added
Attachment #98163|0 |1
is obsolete||
--- Comment #5 from Carl Love ---
Created attachment 98295
--> https://bugs.kde.org/attachment.cgi?id=98295&action=edit
Updated VEX support patch
The patch was updated to address Julian's comments.
> + binop( Iop_64HLtoV128,
> + mkU64( 0x ),
> + mkU64( 0x ) ) ) );
> The ppc back end knows how to generate a 128 bit all-ones-value into a
> vector register. So
> just replace all that with mkV128(0x)
Done
> My only concern is that it seems rather repetitive in places. I wonder if you
> couldn't shorten
> it up a bit by writing a few subroutines?
The following functions were added and used in multiple places to make the code
more readable.
static inline IRExpr* mkXOr4_32( IRTemp t0, IRTemp t1,
IRTemp t2,
IRTemp t3)
{
return binop( Iop_Xor32,
binop( Iop_Xor32, mkexpr( t0 ), mkexpr( t1 ) ),
binop( Iop_Xor32, mkexpr( t2 ), mkexpr( t3 ) ) );
}
static inline IRExpr* mkOr3_V128( IRTemp t0, IRTemp t1, IRTemp t2)
{
return binop( Iop_OrV128,
mkexpr( t0 ),
binop( Iop_OrV128, mkexpr( t1 ), mkexpr( t2 ) ) );
}
static inline IRExpr* mkOr4_V128( IRTemp t0, IRTemp t1, IRTemp t2,
IRTemp t3 )
{
return binop( Iop_OrV128,
binop( Iop_OrV128, mkexpr( t0 ), mkexpr( t1 ) ),
binop( Iop_OrV128, mkexpr( t2 ), mkexpr( t3 ) ) );
}
static inline IRExpr* mkOr4_V128_expr( IRExpr* t0, IRExpr* t1, IRExpr* t2,
IRExpr* t3 )
{
/* arguments are already expressions */
return binop( Iop_OrV128,
binop( Iop_OrV128, ( t0 ), ( t1 ) ),
binop( Iop_OrV128, ( t2 ), ( t3 ) ) );
}
static IRExpr* extract_field_from_vector( IRTemp vB, IRExpr* index, UInt mask)
{
/* vB is a vector, extract bits starting at index to size of mask */
return unop( Iop_V128to64,
binop( Iop_AndV128,
binop( Iop_ShrV128,
mkexpr( vB ),
unop( Iop_64to8,
binop( Iop_Mul64, index,
mkU64( 8 ) ) )
),
binop( Iop_64HLtoV128,
mkU64( 0x0 ),
mkU64( mask ) ) ) );
}
The updated patch is attached for additional review.
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 358608] Enable "Print images" kipi plugin
https://bugs.kde.org/show_bug.cgi?id=358608 --- Comment #3 from Gregor Mi --- I would like to point out that this particular bug report is only about one of the kipi-plugins, not all of them. (On a side note, the cluttering of the Send/export menu could have also been resolved by applying a sensible grouping) > 3) Having two Print actions (one core, one via KIPI) will only confuse users. There are ways to provide additional functionality without confusing the user; for example submenus. > 2) Printing is a core feature, we don't want to rely on an external plugin > for this. If it was only for additional functionality (like second print option), would it be ok then? I have a question about Purpose: is it going to be the total replacement for kipi or shall both technologies be used along-side and only parts - like the Print dialog - will be moved to Purpose? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361397] Audio thumbnails full height if video thumbnails are off
https://bugs.kde.org/show_bug.cgi?id=361397 Jean-Baptiste Mardelle changed: What|Removed |Added Latest Commit||http://commits.kde.org/kden ||live/559a0607a5558e1d231a8e ||9b46fe143ea474a2c1 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jean-Baptiste Mardelle --- Git commit 559a0607a5558e1d231a8e9b46fe143ea474a2c1 by Jean-Baptiste Mardelle. Committed on 08/04/2016 at 19:42. Pushed by mardelle into branch 'Applications/16.04'. Use full clip height for audio thumbs if video thumbs are disabled M +1-1src/timeline/clipitem.cpp http://commits.kde.org/kdenlive/559a0607a5558e1d231a8e9b46fe143ea474a2c1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361492] Project Metadata (Title, Author,...) not saved on Project file
https://bugs.kde.org/show_bug.cgi?id=361492 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kden ||live/be474c94a167944d817560 ||364f2ee8e6c957c760 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit be474c94a167944d817560364f2ee8e6c957c760 by Jean-Baptiste Mardelle. Committed on 08/04/2016 at 19:35. Pushed by mardelle into branch 'Applications/16.04'. Fix saving and exporting project metadata M +3-0src/doc/kdenlivedoc.cpp M +1-1src/mainwindow.cpp M +16 -1src/mltcontroller/bincontroller.cpp M +1-1src/mltcontroller/bincontroller.h M +21 -7src/project/dialogs/projectsettings.cpp M +1-1src/project/projectmanager.cpp http://commits.kde.org/kdenlive/be474c94a167944d817560364f2ee8e6c957c760 -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 361528] is not clear what lines in plugins list (of application details) are related
https://bugs.kde.org/show_bug.cgi?id=361528 mariop...@yahoo.es changed: What|Removed |Added CC||mariop...@yahoo.es -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 360622] Untranslatable messages in plasmathemeexplorer
https://bugs.kde.org/show_bug.cgi?id=360622 Alexander Potashev changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 358608] Enable "Print images" kipi plugin
https://bugs.kde.org/show_bug.cgi?id=358608 Janet changed: What|Removed |Added CC||bugzi...@kerridis.de --- Comment #2 from Janet --- I am glad that you don't use the kipi-plugins for spectacle, they have cluttered the send/export to dialog of ksnapshot a lot. But I agree that it would be comfortable to have some further printing options and I'very much appreciate if it could be added to spectacle's own print feature. -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 360622] Untranslatable messages in plasmathemeexplorer
https://bugs.kde.org/show_bug.cgi?id=360622 Alexander Potashev changed: What|Removed |Added CC||notm...@gmail.com Version Fixed In||5.7.0 --- Comment #1 from Alexander Potashev --- Fixed in http://commits.kde.org/plasma-sdk/69f49817c38c4f222a516f6da95a3e0b1aae6ded -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361156] If session goes idle, after unlocking the session, panels are no longer present
https://bugs.kde.org/show_bug.cgi?id=361156 Jacob Godserv changed: What|Removed |Added Component|general |Panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361156] If session goes idle, after unlocking the session, panels are no longer present
https://bugs.kde.org/show_bug.cgi?id=361156 Jacob Godserv changed: What|Removed |Added Version|5.6.0 |5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361156] If session goes idle, after unlocking the session, panels are no longer present
https://bugs.kde.org/show_bug.cgi?id=361156 Jacob Godserv changed: What|Removed |Added Summary|When session is idle, lock |If session goes idle, after |screen fails to respond and |unlocking the session, |panels are no longer|panels are no longer |present |present -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361156] When session is idle, lock screen fails to respond and panels are no longer present
https://bugs.kde.org/show_bug.cgi?id=361156 --- Comment #5 from Jacob Godserv --- Created attachment 98294 --> https://bugs.kde.org/attachment.cgi?id=98294&action=edit New crash information added by DrKonqi plasmashell (5.6.2) using Qt 5.5.1 It appears that the lock screen issue has been fixed with 5.6.2 but the missing panel issue remains. - What I was doing when the application crashed: I unlocked my session after leaving it idle. The computer had not suspended; only the display had gone to sleep - Unusual behavior I noticed: The lock screen unlocked and everything appeared to work (including Alt+Tab and Ctrl+Space) but the panels were missing. -- Backtrace (Reduced): #9 0x00355de8815c in QEventDispatcherGlib::processEvents (this=0x8c01d0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #10 0x00355de3c25a in QEventLoop::exec (this=this@entry=0x7ffda597d1d0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #11 0x00355de4328d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #12 0x00355e2e920c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1527 #13 0x00355e957315 in QApplication::exec () at kernel/qapplication.cpp:2976 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361156] When session is idle, lock screen fails to respond and panels are no longer present
https://bugs.kde.org/show_bug.cgi?id=361156 Jacob Godserv changed: What|Removed |Added CC||jacobgods...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 354633] [ntfs] ktorrent freezes very often
https://bugs.kde.org/show_bug.cgi?id=354633 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361347] okular se cierra al rotar un pdf
https://bugs.kde.org/show_bug.cgi?id=361347 --- Comment #2 from duvan suarez --- esta es la traza inversa, espero lo puedan solucionar ;) : Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa23532b840 (LWP 1740))] Thread 7 (Thread 0x7fa233b76700 (LWP 1741)): #0 0x7fa2441a2afd in poll () from /lib/libc.so.6 #1 0x7fa2409daac2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fa2409dc69f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fa23509ac79 in ?? () from /usr/lib/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5 #4 0x7fa24481d3e9 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fa2403b1434 in start_thread () from /lib/libpthread.so.0 #6 0x7fa2441abbad in clone () from /lib/libc.so.6 Thread 6 (Thread 0x7fa232873700 (LWP 1742)): #0 0x7ffebb0e8cdb in clock_gettime () #1 0x7fa2441b8ad6 in clock_gettime () from /lib/libc.so.6 #2 0x7fa2448c6b06 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7fa244a2fa39 in QTimerInfoList::updateCurrentTime() () from /usr/lib/libQt5Core.so.5 #4 0x7fa244a2ff45 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/libQt5Core.so.5 #5 0x7fa244a312de in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7fa23e6ad88d in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #7 0x7fa23e6ae1d0 in ?? () from /usr/lib/libglib-2.0.so.0 #8 0x7fa23e6ae3ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0x7fa244a31e3c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #10 0x7fa2449dffea in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #11 0x7fa244818acc in QThread::exec() () from /usr/lib/libQt5Core.so.5 #12 0x7fa2479cffb5 in ?? () from /usr/lib/libQt5DBus.so.5 #13 0x7fa24481d3e9 in ?? () from /usr/lib/libQt5Core.so.5 #14 0x7fa2403b1434 in start_thread () from /lib/libpthread.so.0 #15 0x7fa2441abbad in clone () from /lib/libc.so.6 Thread 5 (Thread 0x7fa21bfff700 (LWP 1755)): #0 0x7fa2403b707f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fa24481dfab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fa230500f37 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fa230505178 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7fa230502870 in ThreadWeaver::Thread::run() () from /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7fa24481d3e9 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7fa2403b1434 in start_thread () from /lib/libpthread.so.0 #20 0x7fa2441abbad in clone () from /lib/libc.so.6 Thread 4 (Thread 0x7fa221e7a700 (LWP 1756)): #0 0x7fa2403b707f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fa24481dfab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fa230500f37 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fa230505178 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fa23050008f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fa2305051c2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #
[plasmashell] [Bug 361531] New: Clicking notification popup no longer hides it
https://bugs.kde.org/show_bug.cgi?id=361531 Bug ID: 361531 Summary: Clicking notification popup no longer hides it Product: plasmashell Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Notifications Assignee: mklape...@kde.org Reporter: abderrahman.naj...@gmail.com CC: plasma-b...@kde.org Prior to Plasma 5.6, if I'm not wrong, clicking on a notification popup made it disappear (the same action as clicking on the X button in its corner). However, this is no longer possible, and the user has to click X to hide it (or wait for it to autohide). Why is that the case now? I could understand if the purpose was to prevent accidental hiding if the user was in that area and clicked just as the notification appeared. But now the notifications are persistent and show in the notifications applet (so even if the notification was dismissed by accident, the user can go back and read it) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 307839] No import from automaticaly added smartphone
https://bugs.kde.org/show_bug.cgi?id=307839 caulier.gil...@gmail.com changed: What|Removed |Added CC||math...@ghack.net --- Comment #22 from caulier.gil...@gmail.com --- *** Bug 361523 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361523] Nikon Coolpix P610: "Failed to detect camera with GPhoto2 from Solid information"
https://bugs.kde.org/show_bug.cgi?id=361523 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||caulier.gil...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 307839 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 361367] Multimedia control bad working
https://bugs.kde.org/show_bug.cgi?id=361367 --- Comment #2 from varlesh --- Thx, very fast. Working fine :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360683] Cannot deselect (un-highlight) a date in the Calendar popup
https://bugs.kde.org/show_bug.cgi?id=360683 Martin Klapetek changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #9 from Martin Klapetek --- You need to update plasma-framework to 5.21. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351141] switching desktop makes pager redraw itself with one second long delay
https://bugs.kde.org/show_bug.cgi?id=351141 Viacheslav Ostroukh changed: What|Removed |Added CC||slavout...@ostroukh.me --- Comment #2 from Viacheslav Ostroukh --- Confirm for me, Xmonad 0.12, Plasma 5.5.5, Gentoo stable. Pager redraws in nearly a second. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360683] Cannot deselect (un-highlight) a date in the Calendar popup
https://bugs.kde.org/show_bug.cgi?id=360683 Abderrahman Najjar changed: What|Removed |Added Version|5.5.5 |5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360683] Cannot deselect (un-highlight) a date in the Calendar popup
https://bugs.kde.org/show_bug.cgi?id=360683 Abderrahman Najjar changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #8 from Abderrahman Najjar --- I've updated to v5.6.2-1 from the Arch repos, and the issue is still present. There's a button, but clicking it doesn't take the selection back to today, neither does closing (hiding) the applet. Clicking the "today" button actually just takes me back to the current month if I flip to another one -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 254404] JJ: Using the order in the media browser while copying files to UMS devices
https://bugs.kde.org/show_bug.cgi?id=254404 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 121844] KFolderIface should expose messages, not just message counts
https://bugs.kde.org/show_bug.cgi?id=121844 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355190] copy current date/time into clipboard
https://bugs.kde.org/show_bug.cgi?id=355190 Martin Klapetek changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #21 from Martin Klapetek --- 5.7 earliest because it contains new strings, which is not allowed in stable releases. -- You are receiving this mail because: You are watching all bug changes.
[valkyrie] [Bug 277120] Problems with compilation of the sources. use r546
https://bugs.kde.org/show_bug.cgi?id=277120 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 183355] Tree View: Folders / Feeds with Unread Messages are not Colored / Do Not Have Color
https://bugs.kde.org/show_bug.cgi?id=183355 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 188528] konsole's history adds spaces to end of lines when copying text
https://bugs.kde.org/show_bug.cgi?id=188528 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 138025] AVERAGEA: kspread vs. help -- one has to be wrong (could be a major)
https://bugs.kde.org/show_bug.cgi?id=138025 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 334669] Crash configuring cantor python2 backend
https://bugs.kde.org/show_bug.cgi?id=334669 Filipe Saraiva changed: What|Removed |Added Resolution|--- |FIXED Assignee|alexanderrie...@gmail.com |fil...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Filipe Saraiva --- It was solved some releases ago. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 157229] directory mouseover effect not displayed properly in OS X
https://bugs.kde.org/show_bug.cgi?id=157229 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 345610] Cantor crashed when using python pylab
https://bugs.kde.org/show_bug.cgi?id=345610 Filipe Saraiva changed: What|Removed |Added Assignee|alexanderrie...@gmail.com |fil...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 345610] Cantor crashed when using python pylab
https://bugs.kde.org/show_bug.cgi?id=345610 Filipe Saraiva changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Filipe Saraiva --- This bug was solved some releases ago. Test with the follow commands: x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] from matplotlib import pylab pylab.clf() pylab.plot(x) pylab.show() -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 182819] krfb crashes on email invitation
https://bugs.kde.org/show_bug.cgi?id=182819 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 347917] knotify crash on openSUSE because of mismatch in vlc version
https://bugs.kde.org/show_bug.cgi?id=347917 Shreyesh Chaudhary changed: What|Removed |Added CC|sacvi...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 359927] Cantor crashes when "Integrate plots in Worksheet" is checked (python2)
https://bugs.kde.org/show_bug.cgi?id=359927 --- Comment #1 from Filipe Saraiva --- Hello Simone, I can not to reproduce this bug. Please, can you verify if you have this bug yet? I run the follow commands: x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] from matplotlib import pylab pylab.clf() pylab.plot(x) pylab.show() -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 338079] Kleopatra will not import 4096 byte keys from keyserver
https://bugs.kde.org/show_bug.cgi?id=338079 --- Comment #3 from John Andersen --- Confirming this still fails on Opensuse 13.2 Total number processed: 0 Imported: 0 On Kleopatra Version 2.2.0 (latest in repository) Kde Dev platform 4.14.9 KGpg 2.14.1 gpg (GnuPG) 2.0.26 All from Opensuse 13.2 Repositories Confirm it WORKS on Manjaro (arch) Linux 15.12 Total number processed: 1 Imported: 1 On Kleopatra Version 2.2.0 (latest in repository) Kde Framework 5.20.0 KGpg 2.17.0 gpg (GnuPG) 2.1.11 All from Manjaro 15.12 Repositories - Summary: Failure on KDE 4.14 (opensuse) Success on KDE Framework 5. (manjaro) Entirely possible bug is in some of the underlying gpg systems that Kleopatra requires. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361530] New: Filter preview of an area under selection is becomes white , it is normal when there is no selection
https://bugs.kde.org/show_bug.cgi?id=361530 Bug ID: 361530 Summary: Filter preview of an area under selection is becomes white , it is normal when there is no selection Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: raghavendr.ra...@gmail.com In Krita latest git , if you go to apply a filter to an area which is under selection , the on canvas preview of the filter turns white instead of showing the actual preview. Reproducible: Always Steps to Reproduce: 1.Open krita and create a new document 2. draw something or fill it with some color 3. Select a region with rectangular or any other selection tool 4. trigger any filter for example press Ctrl + U for Hue saturation filter 5. Check the preview checkbox in the dialog if it is not checked by default Actual Results: the preview is white Expected Results: The preview of the filter should be shown normally -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 345100] The menu editor doesn't properly save new icons for submenus
https://bugs.kde.org/show_bug.cgi?id=345100 --- Comment #6 from Janet --- I can confirm the path problem. I am using kmenuedit from kubuntu-ci (4:5.5.4+git20160308.1732+15.10-0) and it uses the package icon for new submenus. The .directory files with that icon are stored in ~/.local/share/desktop-directories/ whereas the .directory files with the correct (i.e. user given) icon are stored in ~/.local/share/ ... -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 343892] Could not find a package configuration file provided by "Analitza"
https://bugs.kde.org/show_bug.cgi?id=343892 Filipe Saraiva changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||fil...@kde.org --- Comment #5 from Filipe Saraiva --- This was solved some releases ago, thanks for all! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 331420] Input/Output does not function properly with Cantor
https://bugs.kde.org/show_bug.cgi?id=331420 Filipe Saraiva changed: What|Removed |Added Resolution|--- |WONTFIX Assignee|m...@noughmad.eu|fil...@kde.org Summary|Input/Output does not |Input/Output does not |function properly with |function properly with |Octave backend |Cantor Component|octave-backend |general Status|UNCONFIRMED |RESOLVED CC||fil...@kde.org --- Comment #1 from Filipe Saraiva --- Hello Brandon, I think it is a limitation of the "worksheet interface" philosophy implemented in Cantor. Cantor provides an interface to scientific computing based in interactions between the tool and the user. It is different from the philosophy where the user writes a script and run it in some terminal. In Cantor there is no need to write an input function, like in script texts, because you can to write an attribution operation directly in the worksheet, like `a = something`. Sure it can be modified in the future (I saw Jupyter implements input functions), but for the moment it will not change. Thanks. -- You are receiving this mail because: You are watching all bug changes.
