[kgpg] [Bug 357462] Decryption failure when message has no version header
https://bugs.kde.org/show_bug.cgi?id=357462 nowi changed: What|Removed |Added CC||ha...@andnow.elefteria.net --- Comment #1 from nowi --- I can confirm this confusing behaviour. Kgpg failure notice should not include the decrypted message. bye nowi KGpg Version 2.17.0 KDE 4.14.16 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert&crash on startup
https://bugs.kde.org/show_bug.cgi?id=359255 --- Comment #13 from Boudewijn Rempt --- Hum, that gives exactly the error you were getting, which is not too strange... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert&crash on startup
https://bugs.kde.org/show_bug.cgi?id=359255 --- Comment #12 from Boudewijn Rempt --- That is strange... Why would a japanese version of OSX look in a different place than the US English version? I'll test that change locally, though, and use it in the next release if it works. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363750] KUIT layout not working in dialog
https://bugs.kde.org/show_bug.cgi?id=363750 --- Comment #2 from Martin Gräßlin --- Created attachment 99296 --> https://bugs.kde.org/attachment.cgi?id=99296&action=edit Untranslated This works fine in the untranslated version. So this is either a problem with the translations or with the translation infrastructure. I'm not familiar with the translation architecture to properly investigate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344326] Black or corrupted screen on resume from suspend
https://bugs.kde.org/show_bug.cgi?id=344326 Ben Cooksley changed: What|Removed |Added CC|rajind...@hotmail.com | --- Comment #107 from Ben Cooksley --- Removing person from CC list per abuse reports from Microsoft. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 363773] New: search in discover does not give any result
https://bugs.kde.org/show_bug.cgi?id=363773 Bug ID: 363773 Summary: search in discover does not give any result Product: Discover Version: 5.6.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: wpeb...@yahoo.com search for applications does not show any result despite the program(s) are in the list, so I have just to scroll manually and install the program or do it with terminal Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 363772] volume control for separate speakers fails to maintain user settings
https://bugs.kde.org/show_bug.cgi?id=363772 philipps...@gmail.com changed: What|Removed |Added CC||philipps...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 363772] New: volume control for separate speakers fails to maintain user settings
https://bugs.kde.org/show_bug.cgi?id=363772 Bug ID: 363772 Summary: volume control for separate speakers fails to maintain user settings Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: philipps...@gmail.com After setting different volume levels for left and right speaker using pulse audio volume control (PAVU), adjusting the master volume controller in either PAVU or the plasmashell audio volume controller resets both speakers to the same output level. In Gnome and Mate the levels maintain their user-set distinction. There does not seem to be a way in KDE to set the volume levels separately and then adjust the overall volume without having the channels resync undesirably. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363771] New: deactivate "Aufklappmenue"
https://bugs.kde.org/show_bug.cgi?id=363771 Bug ID: 363771 Summary: deactivate "Aufklappmenue" Product: plasmashell Version: 5.6.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde-b...@linuxhotel.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.6.4) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: In Thunderbird I've copied a hyperlink to the clipboard. The plasma clipboard-manager opened an annoying window with some useless actions. I chose "Aufklappmenu deaktivieren" from the list. Next, the bug assistant appeared. 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 0x7f9f8c0147c0 (LWP 7865))] Thread 17 (Thread 0x7f9f75837700 (LWP 7867)): #0 0x7f9f85514bbd in poll () from /lib64/libc.so.6 #1 0x7f9f8a44a422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f9f8a44c00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f9f77b8bd69 in QXcbEventReader::run (this=0x1497600) at qxcbconnection.cpp:1325 #4 0x7f9f85c13079 in QThreadPrivate::start (arg=0x1497600) at thread/qthread_unix.cpp:340 #5 0x7f9f84d1e0a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f9f8551cfed in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f9f6fb81700 (LWP 7868)): #0 0x7f9f85c0baad in QMutex::lock (this=this@entry=0x14d1ef8) at thread/qmutex.cpp:217 #1 0x7f9f85e24a15 in QMutexLocker (m=0x14d1ef8, this=) at ../../src/corelib/thread/qmutex.h:128 #2 canWaitLocked (this=0x14d1ed0) at ../../src/corelib/thread/qthread_p.h:247 #3 postEventSourcePrepare (timeout=, s=0x7f9f680012d0) at kernel/qeventdispatcher_glib.cpp:253 #4 postEventSourceCheck (source=0x7f9f680012d0) at kernel/qeventdispatcher_glib.cpp:263 #5 0x7f9f81bfc8f1 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #6 0x7f9f81bfcdf8 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7f9f81bfcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #8 0x7f9f85e243fb in QEventDispatcherGlib::processEvents (this=0x7f9f680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #9 0x7f9f85dd204b in QEventLoop::exec (this=this@entry=0x7f9f6fb80de0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #10 0x7f9f85c0e5da in QThread::exec (this=) at thread/qthread.cpp:503 #11 0x7f9f86b8f095 in ?? () from /usr/lib64/libQt5DBus.so.5 #12 0x7f9f85c13079 in QThreadPrivate::start (arg=0x7f9f86df7d00) at thread/qthread_unix.cpp:340 #13 0x7f9f84d1e0a4 in start_thread () from /lib64/libpthread.so.0 #14 0x7f9f8551cfed in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f9f6e343700 (LWP 7875)): #0 0x7f9f81bfc628 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9f81bfcd80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9f81bfcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9f85e243fb in QEventDispatcherGlib::processEvents (this=0x7f9f68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f9f85dd204b in QEventLoop::exec (this=this@entry=0x7f9f6e342df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f9f85c0e5da in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f9f88f0b4d8 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f9f85c13079 in QThreadPrivate::start (arg=0x1589120) at thread/qthread_unix.cpp:340 #8 0x7f9f84d1e0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f9f8551cfed in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f9f5cf56700 (LWP 7903)): #0 0x7f9f81c3ed14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9f81bfc8e9 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9f81bfcdf8 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9f81bfcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f9f85e243fb in QEventDispatcherGlib::processEvents (this=0x7f9f580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f9f85dd204b in QEventLoop::exec (this=this@entry=0x7f9f5cf55df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f9f85c0e5da in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f9f88f0b4d8 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f9f85c13079 in QThreadPrivate::start (arg=0x191dd40) at thread/qthread_unix.cpp:340 #9 0x7f9f84d1e0a4 in start_thread () from /lib64/libpthread.so.
[kate] [Bug 363765] Allow “Tab key inserts tab character” as tab key action
https://bugs.kde.org/show_bug.cgi?id=363765 Kåre Särs changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||kare.s...@iki.fi Resolution|--- |WORKSFORME --- Comment #1 from Kåre Särs --- I had the exact same problem some years ago. I have a workaround for that: Set the shortcut for the "Insert Tab" action to Tab (there is no default set) I don't totally agree with the available options for indentation and tab, but the workaround fixes it for me ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363770] Selection outline appears black or green with OpenGL enabled
https://bugs.kde.org/show_bug.cgi?id=363770 --- Comment #1 from Chris Jones --- Correction, it appears black instead of *inverse* on the SP4, and green instead of inverse on my desktop PC (which makes it hard to seen on green backgrounds). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363770] Selection outline appears black or green with OpenGL enabled
https://bugs.kde.org/show_bug.cgi?id=363770 Chris Jones changed: What|Removed |Added Summary|Selection outline appears |Selection outline appears |black on Surface Pro 4 with |black or green with OpenGL |OpenGL enabled |enabled -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363621] Krita 3.0 is slower than 2.8
https://bugs.kde.org/show_bug.cgi?id=363621 --- Comment #3 from sun...@hotmail.ru --- Tried http://files.kde.org/krita/3/linux/krita-3.0-x86_64.appimage Its not crashing on changing OpenGL enabled/disabled anymore but it is still slow. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363770] New: Selection outline appears black on Surface Pro 4 with OpenGL enabled
https://bugs.kde.org/show_bug.cgi?id=363770 Bug ID: 363770 Summary: Selection outline appears black on Surface Pro 4 with OpenGL enabled Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: ch...@outlook.com When using a selection tool, the outline that is drawn before the selection is closed and turns into marching ants appears black instead of the usual green when OpenGL is turned on. This makes it difficult or impossible to see the selection as it is being drawn onto a dark image. Surface Pro 4 i5 8GB, Windows 10, Krita 3.0 (git f0cbffc) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 358050] Events ending on midnight are shown 24 hours too late
https://bugs.kde.org/show_bug.cgi?id=358050 --- Comment #2 from sparhawk --- I'm not sure how the versioning works. From the menu and korganizer --version, I'm also running 5.2.1. However, from Arch's packages, it says it's version 16.04.1. Either way, I can confirm this bug is still present. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 358011] dual screen not setup after reboot
https://bugs.kde.org/show_bug.cgi?id=358011 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
неразрушающий контроль
Здравствуйте! Напоминаем вам о необходимости прохождения курса переподготовки для сотрудников и руководителей испытательных лабораторий, строительных и грунтовых лаб-ий. Информация по теме и контактные данные прилагаются. С уважением, Юрий Анисимов, менеджер по работе с заказчиками. испытательные лаборатории.docx Description: Binary data
[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert&crash on startup
https://bugs.kde.org/show_bug.cgi?id=359255 --- Comment #11 from guruguru...@outlook.jp --- I found moving all of krita.app/share contents to krita.app/Resource folder makes Krita work, including UI localization. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363769] New: Exporting to file format such as .png and .bmp appends extra period to filename
https://bugs.kde.org/show_bug.cgi?id=363769 Bug ID: 363769 Summary: Exporting to file format such as .png and .bmp appends extra period to filename Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: nimth...@gmail.com When exporting a file in the portable Krita 64-bit windows version to .png (and other formats) the name you give the file contains an extra period after exporting. For example, exporting something as "Test.png" will be called "Test..png". Reproducible: Always Steps to Reproduce: 1. Make a new canvas 2. Draw anything 3. Export file as .png and give it a name 4. Look at file in filesystem (and notice the extra period) Actual Results: Filename contains an extra period Expected Results: Filename should be named what you told it to be named -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363739] Brush lag at zoom level 50 below
https://bugs.kde.org/show_bug.cgi?id=363739 --- Comment #5 from kirrin.artemi...@gmail.com --- I haven't tried yet. Let me check later. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 363381] Crash of Kaffeine with any MPEG file
https://bugs.kde.org/show_bug.cgi?id=363381 Mauro Carvalho Chehab changed: What|Removed |Added CC||mche...@infradead.org --- Comment #1 from Mauro Carvalho Chehab --- The Kaffeine version you're using is too old... it still uses the xine backend. We moved to libVLC sometime ago, and we just released upstream a version 2.0.1, with is based on KDE5. So, lots of change too. Could you please test the upstream version and see it if works? the README file contains instructions about how to compile it. You can find it at our git repository: https://quickgit.kde.org/?p=kaffeine.git -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 296638] add configuration option to allow selection of delivery system of hybrid dvb device
https://bugs.kde.org/show_bug.cgi?id=296638 Mauro Carvalho Chehab changed: What|Removed |Added CC||mche...@infradead.org --- Comment #1 from Mauro Carvalho Chehab --- Fixed on Kaffeine 2.0.1: it now uses libdvb5 and properly supports devices with frontends with multiple delivery systems. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363768] New: Font size is changed when form value is modified
https://bugs.kde.org/show_bug.cgi?id=363768 Bug ID: 363768 Summary: Font size is changed when form value is modified Product: okular Version: 0.24.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: fry@gmail.com Created attachment 99294 --> https://bugs.kde.org/attachment.cgi?id=99294&action=edit test file #1 Open the test file and note the font sizes of the pre-filled form fields. Try to update a text field with a short text string -- font size becomes changed. Also, the new size is too big to fit (unless a long string of text is entered -- then font size becomes tiny -- however, that behavior is expected when font size is "auto"). Even if text value is changed to the original, font size stays too big. Try entering letters that have descenders: g,j,p,q,y -- they appear cut off. The behavior is especially bad in a list box. Try selecting item 3 -- it disappears because Item 1 becomes so big Note: in test file #2, the font sizes are fixed - that works around this bug. However, there should be no reason to cut off some letters in "auto" mode. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363768] Font size is changed when form value is modified
https://bugs.kde.org/show_bug.cgi?id=363768 --- Comment #1 from Konstantin Svist --- Created attachment 99295 --> https://bugs.kde.org/attachment.cgi?id=99295&action=edit test file #2 -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 363716] There is no Python scripting
https://bugs.kde.org/show_bug.cgi?id=363716 --- Comment #3 from David E. Narvaez --- (In reply to Burkhard Lueck from comment #2) > Maybe a packaging issue? Correct, this seems to be a packaging issue. Might be intentional to avoid the Python dependency or might be because Python detection at compile time has been sort of a hit or miss lately. If the latter is the case, I would be happy to help the packagers figure things out. I suggest someone opens a bug downstream and see what the packagers think about this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert&crash on startup
https://bugs.kde.org/show_bug.cgi?id=359255 --- Comment #10 from guruguru...@outlook.jp --- This is still happening on 3.0 on my Mac and there is a report from another Japanese Krita user on twitter as well. I tested some more and it seems, Krita is looking at User//Library/Application Support/krita/paintoppresets and says "There is no preset" and quits. I copied a preset from the application package(krita.app/share/krita) to User//Library/Application Support/krita/paintoppresets then Krita does run - while most of the resources(non QT ui labels etc) are still missing. So somehow the correct default resources are not being loaded in Japanese environment and causing this issue. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363767] New: KWrite crashes during the opening of a file txt
https://bugs.kde.org/show_bug.cgi?id=363767 Bug ID: 363767 Summary: KWrite crashes during the opening of a file txt Product: kate Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: nmr...@free.fr Application: kwrite (4.14.3) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.1.15-desktop-2.mga5 x86_64 Distribution: "Mageia 5" -- Information about the crash: - What I was doing when the application crashed: Kwrite plante lors de l'ouverture d'un fichier texte. KWrite crashes during the opening of a file txt The crash can be reproduced every time. -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f06cb75e780 (LWP 28565))] Thread 2 (Thread 0x7f06a97c4700 (LWP 28566)): #0 0x7f06ca00867f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f06bc15b73a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQtScript.so.4 #2 0x7f06bc15b769 in () at /lib64/libQtScript.so.4 #3 0x7f06ca0035bd in start_thread () at /lib64/libpthread.so.0 #4 0x7f06c8d7b62d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f06cb75e780 (LWP 28565)): [KCrash Handler] #5 0x7f06ca8f9141 in KSycocaEntry::name() const () at /lib64/libkdecore.so.5 #6 0x7f06ad6a838f in Kate::TextBuffer::load(QString const&, bool&, bool&, bool) () at /lib64/libkatepartinterfaces.so.4 #7 0x7f06ad71c5b6 in KateBuffer::openFile(QString const&, bool) () at /lib64/libkatepartinterfaces.so.4 #8 0x7f06ad71232c in KateDocument::openFile() () at /lib64/libkatepartinterfaces.so.4 #9 0x7f06bf32dbda in KParts::ReadOnlyPartPrivate::openLocalFile() () at /usr/lib64/libkparts.so.4 #10 0x7f06bf32fe2e in KParts::ReadOnlyPart::openUrl(KUrl const&) () at /usr/lib64/libkparts.so.4 #11 0x7f06ad6fe1ae in KateDocument::openUrl(KUrl const&) () at /lib64/libkatepartinterfaces.so.4 #12 0x7f06b3552616 in KWriteApp::init() () at /usr/lib64/libkdeinit4_kwrite.so #13 0x7f06b3552f17 in KWriteApp::KWriteApp(KCmdLineArgs*) () at /usr/lib64/libkdeinit4_kwrite.so #14 0x7f06b3551843 in kdemain () at /usr/lib64/libkdeinit4_kwrite.so #15 0x0040819a in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #16 0x00409021 in handle_launcher_request(int, char const*) [clone .isra.15] () #17 0x0040972a in handle_requests(int) () #18 0x00405303 in main () Possible duplicates by query: bug 359754, bug 356473, bug 350099, bug 348977. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 304772] FACTORING : allow to set face properties on exported files when remote web service support this feature
https://bugs.kde.org/show_bug.cgi?id=304772 s...@fstab.net changed: What|Removed |Added CC||s...@fstab.net -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 363766] New: Some trouble with DL with Thinkpad T440s + debian 8.4 + UltraDock (3 outputscreens)
https://bugs.kde.org/show_bug.cgi?id=363766 Bug ID: 363766 Summary: Some trouble with DL with Thinkpad T440s + debian 8.4 + UltraDock (3 outputscreens) Product: kdelibs Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: laubossl...@society-lbl.com Application: kded4 (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.17.1-dp-mst x86_64 Distribution: Debian GNU/Linux 8.4 (jessie) -- Information about the crash: See ticket open here https://github.com/AdnanHodzic/displaylink-debian/issues/13 The crash can be reproduced every time. -- Backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe2d0910780 (LWP 1095))] Thread 4 (Thread 0x7fe2a77fe700 (LWP 1153)): #0 __libc_enable_asynccancel () at ../nptl/sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7fe2ce0a4d32 in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0x7fe2caf8bee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe2caf8bffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe2cf520d37 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7fe2cf4f0271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fe2cf4f05d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fe2cf3e4e99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fe2cf4d0ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fe2cf3e770f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fe2cb87d0a4 in start_thread (arg=0x7fe2a77fe700) at pthread_create.c:309 #11 0x7fe2ce0ad87d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fe2a6ffd700 (LWP 1160)): #0 0x7c5fea83 in clock_gettime () #1 0x7fe2ce0ba4cd in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fe2cf43ea05 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7fe2cf521b85 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7fe2cf52046c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7fe2cf520535 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fe2caf8b45d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fe2caf8be0b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fe2caf8bffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fe2cf520d37 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fe2cf4f0271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7fe2cf4f05d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7fe2cf3e4e99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7fe2b1e16bc7 in KCupsConnection::run() () from /usr/lib/libkcupslib.so #14 0x7fe2cf3e770f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x7fe2cb87d0a4 in start_thread (arg=0x7fe2a6ffd700) at pthread_create.c:309 #16 0x7fe2ce0ad87d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fe2a67fc700 (LWP 1161)): #0 0x7fe2ce0a4d3d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fe2caf8bee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe2caf8bffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe2cf520d37 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7fe2cf4f0271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7fe2cf4f05d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fe2cf3e4e99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fe2cf3e770f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fe2cb87d0a4 in start_thread (arg=0x7fe2a67fc700) at pthread_create.c:309 #9 0x7fe2ce0ad87d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fe2d0910780 (LWP 1095)): [KCrash Handler] #6 0x7fe2b26841ee in ?? () from /usr/lib/x86_64-linux-gnu/kde4/plugins/kscreen/1/KSC_XRandR.so #7 0x7fe2b267465e in ?? () from /usr/lib/x86_64-linux-gnu/kde4/plugins/kscreen/1/KSC_XRandR.so #8 0x7fe2cf50671c in QMetaObject::activate(QObject
[ksplash] [Bug 363042] Splash screen frozen for ~20-30 seconds
https://bugs.kde.org/show_bug.cgi?id=363042 matheusfbr...@gmail.com changed: What|Removed |Added CC||matheusfbr...@gmail.com --- Comment #1 from matheusfbr...@gmail.com --- Plasmashell 5.6.4 ArchLinux - 4.5.4-1-ARCH Its happening here too... But, i no longer have to wait, i just switch to TTY 2 and back again to TTY 1 ( Can be different, depending on system or installation ), and instantly resume. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 329174] Lost copied text after close application
https://bugs.kde.org/show_bug.cgi?id=329174 --- Comment #22 from EMR_Kde --- So I guess my settings would be pertinent (consdering you've mentioned GTK/Gnome app, I've noted weird copy/paste/select/grab behavior, and it's very annoying in Eclipse). "Save clipboard contents on Exit" (Checked) "Prevent empty clipboard" (Checked) "Ignore Images" (Checked) "Ignore Selection" (Checked) - I like my double clipboard ;) "Remove whitespace" (Checked) "Enable MIME-based actions" (Checked?!) - I have no actions defined though. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363765] New: Allow “Tab key inserts tab character” as tab key action
https://bugs.kde.org/show_bug.cgi?id=363765 Bug ID: 363765 Summary: Allow “Tab key inserts tab character” as tab key action Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: fantasai.b...@inkedblade.net It's currently not possible to insert a tab character when indentation is using spaces, except by pasting one copied from another document. This is pretty confusing to a lot of users (as evidenced by the number of bugs reported by people having trouble inserting tab characters). It would be nice if Kate could have the option to merely insert a tab character whenever the tab key is pressed instead of doing any of the various fancy options it currently has. Reproducible: Always Steps to Reproduce: 1. Choose indentation by spaces in Settings > Configure Kate... > Editing > Indentation > Indent using... 2. Press tab key in document Actual Results: Notice it inserts spaces. Great for people who want to indent with Tab instead of Ctrl+I, but sad for people who want to insert tab characters! Expected Results: Possible to configure Tab key to insert actual Tab character. Reporting against version 15.12.3. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 358011] dual screen not setup after reboot
https://bugs.kde.org/show_bug.cgi?id=358011 --- Comment #10 from Sebastian Kügler --- After some debugging, I found a race condition which may cause this bug. (I can't say for sure since I can reproduce the race, but can't reproduce the exact problem you have.) What happens is that on login, a config is applied that triggers a changed signal, which will write out the config. This doesn't make sense and it may actually lead to writing out intermediate, wrong configs, which are then applied on next login. Essentially, this patch makes the kded kscreen daemon more careful about writing out configs. In earlier patches, I've made the code more robust against corrupt configs, that may also help a bit in this situation. This is Plasma 5.7 material. There's a patch addressing this race condition up for review: https://phabricator.kde.org/D1730 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 --- Comment #43 from Sergey --- After applying patch from comment https://bugs.kde.org/show_bug.cgi?id=360033#c28 compositing has started to work like in good old times of KDE4. $ kwin_x11 --replace OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2 OpenGL version string: 2.1.2 NVIDIA 304.131 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 304.131 GPU class: NV40/G70 OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.17.4 Linux kernel version: 3.18.34 Requires strict binding:no GLSL shaders: limited Texture NPOT support: yes Virtual Machine:no Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. QXcbConnection: XCB error: 8 (BadMatch), sequence: 2083, resource id: 65011718, major code: 42 (SetInputFocus), minor code: 0 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2 OpenGL version string: 2.1.2 NVIDIA 304.131 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 304.131 GPU class: NV40/G70 OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.17.4 Linux kernel version: 3.18.34 Requires strict binding:no GLSL shaders: limited Texture NPOT support: yes Virtual Machine:no QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2473, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2483, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2484, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2485, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2486, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2487, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QMetaProperty::read: Unable to handle unregistered datatype 'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface' $ qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.6.4 Qt Version: 5.5.1 Qt compile version: 5.5.1 XCB compile version: 1.11.1 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11704000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.kwin.aurorae Theme: __aurorae__svg__my-glowglass-lite-black Blur: 1 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 14 font: DejaVu Sans,12,-1,5,50,0,0,0,0,0 smallSpacing: 3 largeSpacing: 14 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 3
[kontact] [Bug 363764] New: Kontact Spadl při zobrazení úkolů
https://bugs.kde.org/show_bug.cgi?id=363764 Bug ID: 363764 Summary: Kontact Spadl při zobrazení úkolů Product: kontact Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: vi...@hippy.cz Application: kontact (4.14.1) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 4.5.0-0.bpo.2-amd64 x86_64 Distribution: Debian GNU/Linux 8.4 (jessie) -- Information about the crash: Po přidání https://github.com/nefaste/akonadi_redmine_resource a napojení na redmine se stahly tasky a issues. Bylo jich nekolik set. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbe01935800 (LWP 2768))] Thread 5 (Thread 0x7fbde1d13700 (LWP 2772)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbdfc5cc06f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fbdfc5cc0a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fbdf8b5b0a4 in start_thread (arg=0x7fbde1d13700) at pthread_create.c:309 #4 0x7fbdfedf287d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7fbda13f8700 (LWP 2775)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbdfc2ee973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fbdfc5fb7f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fbdf8b5b0a4 in start_thread (arg=0x7fbda13f8700) at pthread_create.c:309 #4 0x7fbdfedf287d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fbd91682700 (LWP 2786)): #0 0x7fbdfede9d3d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fbdf8673ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbdf8673ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbdff575d37 in QEventDispatcherGlib::processEvents (this=0x7fbd8c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fbdff545271 in QEventLoop::processEvents (this=this@entry=0x7fbd91681dd0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fbdff5455d5 in QEventLoop::exec (this=this@entry=0x7fbd91681dd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fbdff439e99 in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7fbdff43c70f in QThreadPrivate::start (arg=0x22541d0) at thread/qthread_unix.cpp:349 #8 0x7fbdf8b5b0a4 in start_thread (arg=0x7fbd91682700) at pthread_create.c:309 #9 0x7fbdfedf287d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fbd85067700 (LWP 3339)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbd980c4dea in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7fbd980c4e19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7fbdf8b5b0a4 in start_thread (arg=0x7fbd85067700) at pthread_create.c:309 #4 0x7fbdfedf287d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fbe01935800 (LWP 2768)): [KCrash Handler] #6 QApplication::notify (this=this@entry=0x7ffce1da0ac0, receiver=receiver@entry=0x3f249e0, e=e@entry=0x7ffce1da0290) at kernel/qapplication.cpp:4097 #7 0x7fbe00cdd1aa in KApplication::notify (this=0x7ffce1da0ac0, receiver=0x3f249e0, event=0x7ffce1da0290) at ../../kdeui/kernel/kapplication.cpp:311 #8 0x7fbdff54671d in QCoreApplication::notifyInternal (this=0x7ffce1da0ac0, receiver=receiver@entry=0x3f249e0, event=event@entry=0x7ffce1da0290) at kernel/qcoreapplication.cpp:955 #9 0x7fbdfff6b76f in sendEvent (event=, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #10 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x3f249e0, event=event@entry=0x7ffce1da0290, alienWidget=alienWidget@entry=0x3f249e0, nativeWidget=nativeWidget@entry=0x3073a40, buttonDown=buttonDown@entry=0x7fbe00a8a538 , lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3178 #11 0x7fbdfffe2432 in QETWidget::translateMouseEvent (this=this@entry=0x3073a40, event=event@entry=0x7ffce1da05f0) at kernel/qapplication_x11.cpp:4540 #12 0x7fbdfffe0e2c in QApplication::x11ProcessEvent (this=0x7ffce1da0ac0, event=event@entry=0x7ffce1da05f0) at kernel/qapplication_x11.cpp:3663 #13 0x7fbe9ed2 in x11EventSourceDispatch (s=0x20e98e0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #14 0x7fbdf8673c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fbdf8673f48
[dolphin] [Bug 352177] Moving/copying by drag n' drop between dolphin windows does not respect pressed Ctrl/shift
https://bugs.kde.org/show_bug.cgi?id=352177 Johannes E. Krause changed: What|Removed |Added CC||kra...@informatik.uni-halle ||.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363487] brush lags behind when making quick or long strokes
https://bugs.kde.org/show_bug.cgi?id=363487 William Kensinger changed: What|Removed |Added Version|3.0 Release Candidate |3.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363487] brush lags behind when making quick or long strokes
https://bugs.kde.org/show_bug.cgi?id=363487 --- Comment #11 from William Kensinger --- (In reply to Boudewijn Rempt from comment #10) > Hi William, > > Thanks for checking back! Well... this is unfortunate. It would appear that the driver update didn't solve the issue. It doesn't seem to be happening as frequently or as badly, but it's still enough of a problem to force me to close krita occasionally and come back later. That can really put a damper on my workflow. I've updated to newest version of krita, so I know that it hasn't necessarily been resolved in the latest build, either. Please let me know if there's any more information I can collect that might be able to go towards solving this bug. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 363763] krunner (and also plasmashell) often segfault when trying to type things to search for
https://bugs.kde.org/show_bug.cgi?id=363763 --- Comment #1 from Dan Dart --- Created attachment 99293 --> https://bugs.kde.org/attachment.cgi?id=99293&action=edit crash backtrace -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 363763] New: krunner (and also plasmashell) often segfault when trying to type things to search for
https://bugs.kde.org/show_bug.cgi?id=363763 Bug ID: 363763 Summary: krunner (and also plasmashell) often segfault when trying to type things to search for Product: krunner Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: k...@dandart.co.uk Could be that I have a location to search that isn't expected or liked, or that I have turned off Baloo. Reproducible: Sometimes Steps to Reproduce: 1. Run alt-F2 to search or type something in the Kmenu Actual Results: When loading results it segfaults either krunner or plasmashell. Expected Results: To be able to launch the program. Attached info. I have as many debug packages as ubuntu can provide so I could get this as good as possible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 351059] [GENIUS] Krita crashes while using a genius tablet
https://bugs.kde.org/show_bug.cgi?id=351059 --- Comment #21 from chrisgualo --- Now that 3.0 is finally out, I did some testings, running Win10 as of now. First of all, whenever I put the pen on the tablet, krita now shows a pop-up about screen-resolution > https://goo.gl/ZUquJG. I use (and had been using before my first post here) two monitors. One's resolution is 1920x1080 and the other's is 1366x768 (this one is vertically oriented thru nVidia driver, like this > https://goo.gl/7GKbWW). If I choose the first option, it immediately crashes. If I choose the second option, it works for some time, and even sensitivity works! However, it ends up crashing. It crashed: once when I changed windows, once when I moved the cursor all the way to the upper border (?), sometimes when opening a blank document... Bright side: crash is not immediate. If I choose the third option, using the settings on the screenshot, it works well as well, yet I've had the same issues as in the second option. Then I deleted the temp files in AppData\Temp, and krita started normally. There was no pop-up when used the pen, and pen worked fine, but with no sensitivity. I tried krita-3.0-RC-1-master-7785651-x64 and pop-up came up, sensitivity worked, but crashed. Then started 3.0 again, without clearing temp files, and got same results as before the ones above: worked for a while and crashed eventually. Later I will try this disconnecting one monitor. On the driver utility, I've set the tablet to use only the main monitor. Also, I updated the driver to v5.05, found on WALTOP's website > http://www.waltop.com/english/03_support/01_download.php?xpid=1&MID=1 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 363762] New: kmserver crash after come out of 'lock screen'
https://bugs.kde.org/show_bug.cgi?id=363762 Bug ID: 363762 Summary: kmserver crash after come out of 'lock screen' Product: ksmserver Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: bru...@alcoholjustice.org Application: ksmserver () Qt Version: 5.5.1 Operating System: Linux 4.2.0-36-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Either manually activating 'lock screen' or display sleep - Unusual behavior I noticed: No desktop manager or plasmashell; only existing open applications alive The crash can be reproduced every time. -- Backtrace: Application: ksmserver (ksmserver), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 QXcbScreen::mapToNative (this=this@entry=0x0, rect=...) at qxcbscreen.cpp:267 #7 0x7f1ef8f4d6e3 in QXcbWindow::mapToNative (this=, rect=..., screen=0x0) at qxcbwindow.cpp:199 #8 0x7f1ef8f4eedb in QXcbWindow::propagateSizeHints (this=0x2588b90) at qxcbwindow.cpp:1606 #9 0x7f1ef8f5406c in QXcbWindow::setGeometry (this=0x2588b90, rect=...) at qxcbwindow.cpp:709 #10 0x7f1f0e33534a in ?? () from /usr/lib/x86_64-linux-gnu/libKScreenLocker.so.5 #11 0x7f1f09ff3777 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb727c3f0, r=0x2370c10, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #12 QMetaObject::activate (sender=sender@entry=0x2446c50, signalOffset=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb727c3f0) at kernel/qobject.cpp:3698 #13 0x7f1f09ff40e7 in QMetaObject::activate (sender=sender@entry=0x2446c50, m=m@entry=0x7f1f0adc65a0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb727c3f0) at kernel/qobject.cpp:3578 #14 0x7f1f0a91b021 in QDesktopWidget::screenCountChanged (this=this@entry=0x2446c50, _t1=_t1@entry=0) at .moc/moc_qdesktopwidget.cpp:218 #15 0x7f1f0a91c39d in QDesktopWidgetPrivate::_q_updateScreens (this=0x23aae40) at kernel/qdesktopwidget.cpp:117 #16 0x7f1f09ff47b1 in QObject::event (this=this@entry=0x2446c50, e=e@entry=0x24a0040) at kernel/qobject.cpp:1239 #17 0x7f1f0a90474b in QWidget::event (this=0x2446c50, event=0x24a0040) at kernel/qwidget.cpp:9105 #18 0x7f1f0a8c19dc in QApplicationPrivate::notify_helper (this=this@entry=0x23505a0, receiver=receiver@entry=0x2446c50, e=e@entry=0x24a0040) at kernel/qapplication.cpp:3716 #19 0x7f1f0a8c6ea6 in QApplication::notify (this=0x23519a0, receiver=0x2446c50, e=0x24a0040) at kernel/qapplication.cpp:3499 #20 0x7f1f09fc4d7b in QCoreApplication::notifyInternal (this=0x23519a0, receiver=0x2446c50, event=event@entry=0x24a0040) at kernel/qcoreapplication.cpp:965 #21 0x7f1f09fc7176 in QCoreApplication::sendEvent (event=0x24a0040, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x234e940) at kernel/qcoreapplication.cpp:1593 #23 0x7f1f09fc7658 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #24 0x7f1f0a01b0e3 in postEventSourceDispatch (s=0x23b1a30) at kernel/qeventdispatcher_glib.cpp:271 #25 0x7f1f0400fff7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f1f04010250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f1f040102fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f1f0a01b4ef in QEventDispatcherGlib::processEvents (this=0x23b1ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #29 0x7f1f09fc250a in QEventLoop::exec (this=this@entry=0x7ffcb727cac0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #30 0x7f1f09fca5ec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #31 0x7f1f0a2ffd1c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1530 #32 0x7f1f0a8bde15 in QApplication::exec () at kernel/qapplication.cpp:2976 #33 0x7f1f0e92f136 in kdemain (argc=1, argv=) at ../../ksmserver/main.cpp:349 #34 0x7f1f0e56eac0 in __libc_start_main (main=0x4007a0 , argc=1, argv=0x7ffcb727cd78, init=, fini=, rtld_fini=, stack_end=0x7ffcb727cd68) at libc-start.c:289 #35 0x004007d9 in _start () Possible duplicates by query: bug 362075, bug 354934. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361537] libgit2 v0.23: Kate crashes on startup
https://bugs.kde.org/show_bug.cgi?id=361537 --- Comment #6 from Lukasz --- > Hmm, sorry, if already the libgit2 unit tests fail, I think you need to > report this issue to libgit2. In version 0.24.1 tests are passing, but the crash still happens. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #5 from Yichao Yu --- I don't thinkt he crash is OSX specific (fwiw I think this is a dup of https://bugs.kde.org/show_bug.cgi?id=362907). I'm guessing this can be due to other plugins here that uses dbus too which is why I smell a global destruction ordering issue and (as mentioned above) I'm not sure how to guess the right behavior. (i.e. if qdbus is destructed before us then I don't need to disconnect the connection since it's better been disconnected already). I'm interested to know if the Qt patch helps. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #4 from RJVB --- Interesting, I've never seen those segfaults you mention unless they were those that got fixed when Qt stopped unloading/closing plugins at exit (that may have been after 5.5.1). I also never tested QtCurve under a full-blown Plasma session yet. I haven't tested the latest QtCurve under X11 yet either, so maybe the crash is due to some specific interplay between DBus/OS X and Qt/OS X. My crash went away when I cached DBusConnection::sessionDBus() (not required I know now) and skipped the KWin specific connections on OS X. Then I got a deadlock though, so now I'm just skipping the disconnect completely. I'll test Thiago's patch tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 340931] Read status of emails not updated when changed outside KMail, but only for GMail accounts via IMAP
https://bugs.kde.org/show_bug.cgi?id=340931 Jesús changed: What|Removed |Added CC||jesus...@hotmail.com --- Comment #7 from Jesús --- I have the same bug on Manjaro with kmail 5.2.1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 353369] network-connect and network-disconnect are too similar
https://bugs.kde.org/show_bug.cgi?id=353369 andreas changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/bree ||ze-icons/65e6f73d56f2aaec67 ||2c34ed1896e0a394b30076 Resolution|--- |FIXED --- Comment #10 from andreas --- Git commit 65e6f73d56f2aaec672c34ed1896e0a394b30076 by andreas kainz. Committed on 31/05/2016 at 21:37. Pushed by andreask into branch 'master'. update disconnect network icon for bigger diference to conntected M +9-1icons-dark/actions/16/network-disconnect.svg M +9-1icons-dark/actions/22/network-disconnect.svg M +4-1icons-dark/actions/24/network-disconnect.svg M +8-0icons/actions/16/network-disconnect.svg M +8-0icons/actions/22/network-disconnect.svg M +3-0icons/actions/24/network-disconnect.svg http://commits.kde.org/breeze-icons/65e6f73d56f2aaec672c34ed1896e0a394b30076 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352489] 15.13 git master: MLT processing threads>1 causes (re)positioning playhead to not work any longer
https://bugs.kde.org/show_bug.cgi?id=352489 GPSanino changed: What|Removed |Added CC||gpsan...@gmail.com --- Comment #11 from GPSanino --- I confirm this issue in OpenSuSE of several versions. Having MLT 6.0.2 and KDE 4.14.18 over OpenSuSE Leap 42.1-x64, Kdenlive presents this problem on versions: 15.12.3, 16.04.1 and Kdenlive5 v16.04.1. This I checked on a MackBookPro as well as on a box AMD/Nvidia with 6 cores of 3Ghz. see: https://forum.kde.org/viewtopic.php?f=265&t=133096&p=357706#p357706 I also confirm that returning Threads to 1, solves the issue. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #3 from Yichao Yu --- > not really sure what's the right solutions As in not sure what action to take here. From the description in the qt review you linked, it seems that this can be fixed properly on Qt side. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #2 from Yichao Yu --- I guess that makes sense. OTOH, the commit that introduces this is due to the observation that the dbus callbacks are being called **after** qtcurve is `dlclose`d which segfault on the function call (after all the code isn't there anymore). I'm not really sure what's the right solutions here (or what changed on Qt 5.6 that's causing this). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363604] Project bin doesn't list folders in proper numerical order (screenshot included)
https://bugs.kde.org/show_bug.cgi?id=363604 --- Comment #2 from Jean-Baptiste Mardelle --- Git commit bbb0bc62aae117b3080d63d524178762a4e56417 by Jean-Baptiste Mardelle. Committed on 31/05/2016 at 21:09. Pushed by mardelle into branch 'master'. Use natural sort order in Bin M +2-1src/bin/projectsortproxymodel.cpp M +2-0src/bin/projectsortproxymodel.h http://commits.kde.org/kdenlive/bbb0bc62aae117b3080d63d524178762a4e56417 -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #1 from RJVB --- I asked on the Qt interest ML and got this answer from Thiago Macieira: > > just like the ctor does when setting up DBus. Is that correct practice or > > should one somehow cache the result of sessionBus() in order to call it > > only once? > > It's not correct practice. > > The problem is attempting to use QtDBus during global destruction. > Apparently QtDBus has already destroyed its internals. > > I can add a few protections for that. https://codereview.qt-project.org/161056 -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 246580] Can't move Kruler when vertical
https://bugs.kde.org/show_bug.cgi?id=246580 Alexander Neundorf changed: What|Removed |Added CC||neund...@kde.org --- Comment #6 from Alexander Neundorf --- Does this still happen ? I never had such a problem, also not now using KRuler 5.0 with KF5.21 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 356347] Crash trying to enter settings
https://bugs.kde.org/show_bug.cgi?id=356347 geo...@wildturkeyranch.net changed: What|Removed |Added Severity|crash |major --- Comment #2 from geo...@wildturkeyranch.net --- I think it is time someone took a look at this. The back trace seems clear. Just clicking the settings button does it every time. Need more help from me, just ask. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 356347] Crash trying to enter settings
https://bugs.kde.org/show_bug.cgi?id=356347 --- Comment #1 from geo...@wildturkeyranch.net --- Created attachment 99292 --> https://bugs.kde.org/attachment.cgi?id=99292&action=edit New crash information added by DrKonqi kmymoney (4.6.90-e625006875) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Trying to look at and change kmymoney settings. -- Backtrace (Reduced): #6 0x7f5b06ecdca2 in free () at /lib64/libc.so.6 #7 0x7f5b077f33a4 in std::basic_string, std::allocator >::~basic_string() () at /lib64/libstdc++.so.6 #8 0x008805ca in GpgME::Error::~Error() (this=0x7ffe929d6400, __in_chrg=) at /usr/include/kde4/gpgme++/error.h:40 #9 0x0087f324 in KGPGFile::GPGAvailable() () at //usr/src/incoming/Kmymoney/kmymoney/libkgpgfile/kgpgfile.cpp:293 #10 0x0074cd77 in KSettingsGpg::KSettingsGpg(QWidget*) (this=0x5c46260, parent=0x0) at //usr/src/incoming/Kmymoney/kmymoney/kmymoney/dialogs/settings/ksettingsgpg.cpp:49 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 356347] Crash trying to enter settings
https://bugs.kde.org/show_bug.cgi?id=356347 geo...@wildturkeyranch.net changed: What|Removed |Added CC||geo...@wildturkeyranch.net -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 277795] build failure in klineal
https://bugs.kde.org/show_bug.cgi?id=277795 Alexander Neundorf changed: What|Removed |Added CC||neund...@kde.org --- Comment #2 from Alexander Neundorf --- Can we close this one ? The report is 5 years old, we moved to Qt5 and KF5 and newer compiler versions in the meantime... -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 184249] Wrong position indicator with orizontal kruler
https://bugs.kde.org/show_bug.cgi?id=184249 Alexander Neundorf changed: What|Removed |Added CC||neund...@kde.org --- Comment #4 from Alexander Neundorf --- Here with kruler 5.0, KF5.21 I don't see any problem. The last confirmation is from 2009. Maybe we can close it ? I'm not sure the comment from Vincenzo is actually about the same issue. In several KDE 4.x release the icons used for the orientations in the context menu were wrong, maybe Vincenzo refers to that ? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 eric changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696
--- Comment #15 from eric ---
Created attachment 99291
--> https://bugs.kde.org/attachment.cgi?id=99291&action=edit
Backtrace of kaddressbook after applying patch in comment 13
I've patched akonadi using the diff in the commit you linked to in comment 13
and recompiled.
It still crashes. I've attached the backtrace of this crash.
The output on konsole between start and crash:
Recreating ksycoca file
("/tmp/test/.cache/ksycoca5_C_3hIv+tPrC1WaYX0kkAsoimmSnJQ=", version 303)
Menu "applications-kmenuedit.menu" not found.
Saving
ATTENTION: default value of option vblank_mode overridden by environment.
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: collection: "Personal Contacts"
org.kde.akonadi.ETM: Fetch job took 187 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Personal Contacts"
org.kde.akonadi.ETM: Fetch job took 35 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: Fetch job took 359 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Personal Contacts"
KCrash: Application 'kaddressbook' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
QSocketNotifier: Invalid socket 43 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
QSocketNotifier: Invalid socket 26 and type 'Read', disabling...
QSocketNotifier: Invalid socket 31 and type 'Read', disabling...
QSocketNotifier: Invalid socket 33 and type 'Read', disabling...
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 363758] bamboo pen alignment issue
https://bugs.kde.org/show_bug.cgi?id=363758 Christoph Feck changed: What|Removed |Added Component|Brush engine|tablet support -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 363760] Crash when parsing some old python library
https://bugs.kde.org/show_bug.cgi?id=363760 Sven Brauch changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #3 from Sven Brauch --- I just checked, still crashes with 1.7.3. Here's the trace: (gdb) bt #0 0x73521440 in KDevelop::DUChainPointerData::base() const () from /usr/lib/libkdevplatformlanguage.so.8 #1 0x7fff3d5800af in Python::Helper::declarationForName(KDevelop::QualifiedIdentifier const&, KDevelop::RangeInRevision const&, KDevelop::DUChainPointer) () from /usr/lib/libkdev4pythonduchain.so #2 0x7fff3d575e1b in Python::ExpressionVisitor::visitName(Python::NameAst*) () from /usr/lib/libkdev4pythonduchain.so #3 0x7fff3d5794d2 in Python::ExpressionVisitor::visitBinaryOperation(Python::BinaryOperationAst*) () from /usr/lib/libkdev4pythonduchain.so #4 0x7fff3d5794df in Python::ExpressionVisitor::visitBinaryOperation(Python::BinaryOperationAst*) () from /usr/lib/libkdev4pythonduchain.so #5 0x7fff3d57d161 in Python::ExpressionVisitor::visitListComprehension(Python::ListComprehensionAst*) () from /usr/lib/libkdev4pythonduchain.so #6 0x7fff3d5794df in Python::ExpressionVisitor::visitBinaryOperation(Python::BinaryOperationAst*) () from /usr/lib/libkdev4pythonduchain.so #7 0x7fff3d57d161 in Python::ExpressionVisitor::visitListComprehension(Python::ListComprehensionAst*) () from /usr/lib/libkdev4pythonduchain.so #8 0x7fff3d57a3cb in Python::ExpressionVisitor::visitCall(Python::CallAst*) () from /usr/lib/libkdev4pythonduchain.so #9 0x7fff3d576fb6 in Python::ExpressionVisitor::visitAttribute(Python::AttributeAst*) () from /usr/lib/libkdev4pythonduchain.so #10 0x7fff3d57a445 in Python::ExpressionVisitor::visitCall(Python::CallAst*) () from /usr/lib/libkdev4pythonduchain.so #11 0x7fff3d594e38 in Python::DeclarationBuilder::visitReturn(Python::ReturnAst*) () from /usr/lib/libkdev4pythonduchain.so #12 0x7fff3d58d4c5 in Python::ContextBuilder::visitFunctionBody(Python::FunctionDefinitionAst*) () from /usr/lib/libkdev4pythonduchain.so #13 0x7fff3d59f33a in Python::DeclarationBuilder::visitFunctionDefinition(Python::FunctionDefinitionAst*) () from /usr/lib/libkdev4pythonduchain.so #14 0x7fff5918b9dc in Python::AstDefaultVisitor::visitCode(Python::CodeAst*) () from /usr/lib/libkdev4pythonparser.so #15 0x7fff3d58f896 in Python::ContextBuilder::visitCode(Python::CodeAst*) () from /usr/lib/libkdev4pythonduchain.so #16 0x7fff3d5a235e in ?? () from /usr/lib/libkdev4pythonduchain.so #17 0x7fff3d58e3fd in Python::ContextBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext) () from /usr/lib/libkdev4pythonduchain.so #18 0x7fff3d5954b3 in Python::DeclarationBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext) () from /usr/lib/libkdev4pythonduchain.so #19 0x7fff3d595450 in Python::DeclarationBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext) () from /usr/lib/libkdev4pythonduchain.so #20 0x7fff3da74d0a in ?? () from /usr/lib/kde4/kdevpythonlanguagesupport.so #21 0x7fffeab4c932 in ?? () from /usr/lib/libthreadweaver.so.4 #22 0x7fffeab4cb3e in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () from /usr/lib/libthreadweaver.so.4 #23 0x7fffeab4c20b in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #24 0x74c2c12c in ?? () from /usr/lib/libQtCore.so.4 #25 0x72239474 in start_thread () from /usr/lib/libpthread.so.0 #26 0x7455f69d in clone () from /usr/lib/libc.so.6 It still crashes in current master actually, trace there is: Thread 9 (Thread 0x7ffa290d5700 (LWP 10865)): [KCrash Handler] #5 0x7ffa4470e295 in raise () from /usr/lib/libc.so.6 #6 0x7ffa4470f6da in abort () from /usr/lib/libc.so.6 #7 0x7ffa453afc61 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #8 0x7ffa453aaebe in qt_assert(char const*, char const*, int) () from /usr/lib/libQt5Core.so.5 #9 0x7ff9ea311dfe in Python::ExpressionVisitor::visitListComprehension (this=0x7ffa290d2ec0, node=0x7ffa18163c60) at ../duchain/expressionvisitor.cpp:511 #10 0x7ff9f48afd27 in Python::AstVisitor::visitNode (this=0x7ffa290d2ec0, node=0x7ffa18163c60) at ../parser/astvisitor.cpp:70 #11 0x7ff9ea313719 in Python::ExpressionVisitor::visitBinaryOperation (this=0x7ffa290d3100, node=0x7ffa18163520) at ../duchain/expressionvisitor.cpp:712 #12 0x7ff9f48afc49 in Python::AstVisitor::visitNode (this=0x7ffa290d3100, node=0x7ffa18163520) at ../parser/astvisitor.cpp:64 #13 0x7ff9ea311e20 in Python::ExpressionVisitor::visitListComprehension (this=0x7
[kdev-python] [Bug 363760] Crash when parsing some old python library
https://bugs.kde.org/show_bug.cgi?id=363760 --- Comment #2 from Mattia Basaglia --- This is from the ubuntu debs, I can try to compile it but it might take some time before I'll get around to do that. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 363761] New: Baloo file indexer crashed in background
https://bugs.kde.org/show_bug.cgi?id=363761 Bug ID: 363761 Summary: Baloo file indexer crashed in background Product: Baloo Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: jonwy...@yahoo.com CC: pinak.ah...@gmail.com Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I was using the eclipse IDE to do a complex C++ build. I also had some Dolphin windows open. I'm not very familiar with the entire kde architecture, but is the baloo file indexing service related to Dolphin? -- 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 0x7f1e7321c8c0 (LWP 19948))] Thread 2 (Thread 0x7f1d296d2700 (LWP 19958)): #0 0x7f1e71325e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1e6e4f631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1e6e4f642c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1e71f5ba9b in QEventDispatcherGlib::processEvents (this=0x7f1d240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f1e71f02dea in QEventLoop::exec (this=this@entry=0x7f1d296d1bc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x00420cd8 in Baloo::FileContentIndexer::run (this=0x8d40f0) at ../../../src/file/filecontentindexer.cpp:71 #6 0x7f1e71d21343 in QThreadPoolThread::run (this=0x9ccfb0) at thread/qthreadpool.cpp:93 #7 0x7f1e71d2484e in QThreadPrivate::start (arg=0x9ccfb0) at thread/qthread_unix.cpp:331 #8 0x7f1e709886fa in start_thread (arg=0x7f1d296d2700) at pthread_create.c:333 #9 0x7f1e71331b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f1e7321c8c0 (LWP 19948)): [KCrash Handler] #6 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:118 #7 0x7f1e7240e8da in memcpy (__len=601157784, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #8 Baloo::PostingCodec::decode (this=this@entry=0x7ffdc84e9aff, arr=...) at ../../../src/codecs/postingcodec.cpp:42 #9 0x7f1e723fa814 in Baloo::PostingDB::get (this=this@entry=0x7ffdc84e9be0, term=...) at ../../../src/engine/postingdb.cpp:100 #10 0x7f1e7240b3c6 in Baloo::WriteTransaction::commit (this=) at ../../../src/engine/writetransaction.cpp:277 #11 0x7f1e72403032 in Baloo::Transaction::commit (this=this@entry=0x7ffdc84e9c80) at ../../../src/engine/transaction.cpp:262 #12 0x004296d5 in Baloo::MetadataMover::removeFileMetadata (this=0x8a9d60, file=...) at ../../../src/file/metadatamover.cpp:67 #13 0x7f1e71f33e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffdc84e9dd0, r=0x8a9d60, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #14 QMetaObject::activate (sender=sender@entry=0x8d3560, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffdc84e9dd0) at kernel/qobject.cpp:3698 #15 0x7f1e71f347d7 in QMetaObject::activate (sender=sender@entry=0x8d3560, m=m@entry=0x645940 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffdc84e9dd0) at kernel/qobject.cpp:3578 #16 0x00432f05 in Baloo::PendingFileQueue::removeFileIndex (this=this@entry=0x8d3560, _t1=...) at moc_pendingfilequeue.cpp:217 #17 0x00427856 in Baloo::PendingFileQueue::processCache (this=0x8d3560) at ../../../src/file/pendingfilequeue.cpp:89 #18 0x7f1e71f33e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffdc84e9f50, r=0x8d3560, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #19 QMetaObject::activate (sender=sender@entry=0x8d3578, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3698 #20 0x7f1e71f347d7 in QMetaObject::activate (sender=sender@entry=0x8d3578, m=m@entry=0x7f1e7214e840 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3578 #21 0x7f1e71fb36d0 in QTimer::timeout (this=this@entry=0x8d3578) at .moc/moc_qtimer.cpp:197 #22 0x7f1e71f40878 in QTimer::timerEvent (this=0x8d3578, e=) at kernel/qtimer.cpp:247 #23 0x7f1e71f34e53 in QObject::event (this=0x8d3578, e=) at kernel/qobject.cpp:1261 #24 0x7f1e71f0560c in QCoreApplication::notify (event=0x7ffdc84ea0d0, receiver=0x8d3578, this=0x7ffdc84ea3d0) at kernel/qcoreapplication.cpp:1038 #25 QCoreApplication::notifyInternal (this=0x7ffdc84ea3d0, receiver=0x8d3578, event=event@entry=0x7ffdc84ea0d0) at kernel/qcoreapplicat
[kdev-python] [Bug 363760] Crash when parsing some old python library
https://bugs.kde.org/show_bug.cgi?id=363760 Sven Brauch changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Sven Brauch --- Since it looks like you build yourself anyways, can you please rebuild 1.7.3? 1.7.1 is very old and several crashes were fixed since then. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 363760] New: Crash when parsing some old python library
https://bugs.kde.org/show_bug.cgi?id=363760
Bug ID: 363760
Summary: Crash when parsing some old python library
Product: kdev-python
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: m...@svenbrauch.de
Reporter: mattia.basag...@gmail.com
CC: m...@svenbrauch.de
Sometimes when background parser is scanning some old python code KDevelop
crashes.
Here is the log from a crash:
> PARSING > parsing file
KUrl("file:///.../lib/python2.5/site-packages/statlib/matfunc.py") ; has
priority 1
> AST > building abstract syntax tree for
"/.../lib/python2.5/site-packages/statlib/matfunc.py"
> DUCHAIN > building duchain for
"/.../lib/python2.5/site-packages/statlib/matfunc.py"
ASSERT: "comprehensionContext" in file
/build/buildd/kdev-python-1.7.1/duchain/expressionvisitor.cpp, line 581
KCrash: Application 'kdevelop' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/my_user/.kde/socket-my_hostname/kdeinit4__0
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
QSocketNotifier: Invalid socket 34 and type 'Read', disabling...
QSocketNotifier: Invalid socket 39 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
kdevelop: Fatal IO error: client killed
IndexedContainerData::m_values There were items left on destruction: 1
ClassDeclarationData::m_decorators There were items left on destruction: 56
SpecialTemplateDeclarationData::m_specializations There were items left on
destruction: 12
ClassFunctionDeclarationData::m_defaultParameters There were items left on
destruction: 4606
DUContextData::m_uses There were items left on destruction: 67212
TopDUContextData::m_usedDeclarationIds There were items left on destruction:
1678
TopDUContextData::m_problems There were items left on destruction: 1797
FunctionDeclarationData::m_decorators There were items left on destruction:
1140
DUContextData::m_importers There were items left on destruction: 32139
DUContextData::m_importedContexts There were items left on destruction: 33480
FunctionTypeData::m_arguments There were items left on destruction: 9
FunctionDeclarationData::m_defaultParameters There were items left on
destruction: 34508
DUContextData::m_childContexts There were items left on destruction: 79390
ClassDeclarationData::baseClasses There were items left on destruction: 4712
DUContextData::m_localDeclarations There were items left on destruction: 79390
Unable to start Dr. Konqi
Not forwarding the crash to Apport.
And a copy of the file causing the issue:
https://raw.githubusercontent.com/seperman/python-statlib/master/statlib/matfunc.py
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 361740] Disable warning "The document requested to be launched in presentation mode" on document reload
https://bugs.kde.org/show_bug.cgi?id=361740 --- Comment #5 from Stas Fomin --- Full URL should be «https://github.com/belonesox/demo-of-beamer-problem-for-okular-», bugzilla did not hyperlink correctly in prev.comment. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361740] Disable warning "The document requested to be launched in presentation mode" on document reload
https://bugs.kde.org/show_bug.cgi?id=361740 --- Comment #4 from Stas Fomin --- Yes, demo https://github.com/belonesox/demo-of-beamer-problem-for-okular- Need texlive/pdflatex. run demo.sh -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363746] no double click setting for open a file with dolphin avaliable
https://bugs.kde.org/show_bug.cgi?id=363746 Rog131 changed: What|Removed |Added CC||samrog...@hotmail.com --- Comment #1 from Rog131 --- KDE System Settings > Input Devices > Mouse... More - KDE Forums: https://forum.kde.org/viewtopic.php?f=223&t=128669 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361827] Issue on system tray media player icon
https://bugs.kde.org/show_bug.cgi?id=361827 --- Comment #4 from tago --- The screenshot is in the URL link -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363759] New: Program crashes when attempting to turn on onion skins for animation (windows)
https://bugs.kde.org/show_bug.cgi?id=363759 Bug ID: 363759 Summary: Program crashes when attempting to turn on onion skins for animation (windows) Product: krita Version: 3.0 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: wandaclayhen...@gmail.com In both the portable and installed version of Krita 3 the program has crashed when I tried turning on onion skins. When it doesn't crash and I make sure everything is setup (Lightbulb checked, make sure onion skins options are right) they just don't show up on the next or previous frames. I am running windows 10. Reproducible: Sometimes Steps to Reproduce: 1.Go to animation docker 2. turn on onion skins 3. crash Actual Results: Sometimes crash sometimes onion skins just won't show up. Have not gotten onion skins to work on the stable version of krita 3 yet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 --- Comment #22 from elk...@yahoo.com --- Update on the workaround: Well, sadly it's not perfect. You will still get partial canvas blackout if you zoom in on the top edge of the image, but even with that issue it still makes 5 point perspective completely doable in 3.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363758] New: bamboo pen alignment issue
https://bugs.kde.org/show_bug.cgi?id=363758 Bug ID: 363758 Summary: bamboo pen alignment issue Product: krita Version: unspecified Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: ja...@pandapanther.com in 2.9 everything works perfectly. in V3.0 the cursor is aligned properly over the menus and icons however it's way off over the canvas area. Reproducible: Always Steps to Reproduce: 1.just normal startup 2. 3. Expected Results: aligned the cursor with bamboo input i am using surface pro 2 with wacom bamboo pen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 --- Comment #42 from Sergey --- I have the latest x11-drivers/nvidia-drivers-304.131-r4 for this card (Geforce 7 series). Also, I have a glitch of incorrect placement of Plasma startup window right after login from SDDM. It disappears right after start of Plasma but it's placement is incorrect. It should be in the center, but it's in the top-left corner. I'm talking about this window (in the center on the video): https://youtu.be/Y1NAZGsQtjQ?t=2m11s Maybe it will help to investigate a problem. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363734] Incorrect frame rate conversion
https://bugs.kde.org/show_bug.cgi?id=363734 --- Comment #2 from Jean-Baptiste Mardelle --- Hi, thanks for your report. It's actually hard to understand the exact problem from your description. In your expected results, you say: "The 1st frame should be shown for 1000ms, the 2nd for 993ms, etc". That is quite puzzling... Can you give more details about what is the framerate of your video clip and what is the framerate of the project ? Does this framerate issue appear in Kdenlive's monitor, or in rendered files, or both ? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 363679] muon update manager crashes on segmentation fault during startup
https://bugs.kde.org/show_bug.cgi?id=363679 --- Comment #3 from mabbott...@gmail.com --- I just tried it and it is now working properly. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 363757] New: Baloo crashes frequently for various applications
https://bugs.kde.org/show_bug.cgi?id=363757 Bug ID: 363757 Summary: Baloo crashes frequently for various applications Product: Baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: magpi...@gmail.com CC: pinak.ah...@gmail.com Application: baloo_file (5.21.0) Qt Version: 5.5.1 Operating System: Linux 4.1.21-14-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Amarok, downloading a PDF after viewing within FF. NO ryme or reason, other than when accessing anything with the filesystem. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb6a6eb3780 (LWP 1777))] Thread 2 (Thread 0x7fb55aa78700 (LWP 1952)): #0 0x7fb6a49c1bbd in poll () from /lib64/libc.so.6 #1 0x7fb6a1402e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb6a1402f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb6a55efd8b in QEventDispatcherGlib::processEvents (this=0x7fb5540008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fb6a5596d53 in QEventLoop::exec (this=this@entry=0x7fb55aa77d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x0041531b in Baloo::FileContentIndexer::run (this=0x20e9600) at /usr/src/debug/baloo-5.21.0/src/file/filecontentindexer.cpp:73 #6 0x7fb6a53ba382 in QThreadPoolThread::run (this=0x235b5c0) at thread/qthreadpool.cpp:93 #7 0x7fb6a53bd32f in QThreadPrivate::start (arg=0x235b5c0) at thread/qthread_unix.cpp:331 #8 0x7fb6a39fe0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fb6a49c9fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb6a6eb3780 (LWP 1777)): [KCrash Handler] #6 0x7fb6a26ee25c in mdb_get (txn=0x7fb6a0408e64, dbi=7, key=0x7ffdd6b052c0, data=0x7ffdd6b052d0) at mdb.c:5286 #7 0x7fb6a5c8b4cd in Baloo::IdTreeDB::get (this=this@entry=0x7ffdd6b05340, docId=docId@entry=0) at /usr/src/debug/baloo-5.21.0/src/engine/idtreedb.cpp:82 #8 0x7fb6a5c88dc0 in Baloo::DocumentUrlDB::getId (this=this@entry=0x7ffdd6b053b0, docId=0, fileName=...) at /usr/src/debug/baloo-5.21.0/src/engine/documenturldb.cpp:186 #9 0x7fb6a5c9a949 in Baloo::Transaction::documentId (this=this@entry=0x7ffdd6b05430, path=...) at /usr/src/debug/baloo-5.21.0/src/engine/transaction.cpp:121 #10 0x0041d453 in Baloo::MetadataMover::removeMetadata (this=this@entry=0x211dc60, tr=tr@entry=0x7ffdd6b05430, url=...) at /usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:74 #11 0x0041de02 in Baloo::MetadataMover::moveFileMetadata (this=0x211dc60, from=..., to=...) at /usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:53 #12 0x7fb6a55c873f in call (a=0x7ffdd6b055a0, r=0x7ffdd6b05d00, this=0x20e1d60) at ../../src/corelib/kernel/qobject_impl.h:124 #13 QMetaObject::activate (sender=sender@entry=0x20fe530, signalOffset=, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffdd6b055a0) at kernel/qobject.cpp:3698 #14 0x7fb6a55c92e7 in QMetaObject::activate (sender=sender@entry=0x20fe530, m=m@entry=0x638bc0 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffdd6b055a0) at kernel/qobject.cpp:3578 #15 0x0041e75a in KInotify::moved (this=this@entry=0x20fe530, _t1=..., _t2=...) at /usr/src/debug/baloo-5.21.0/build/src/file/moc_kinotify.cpp:330 #16 0x004228f9 in KInotify::slotEvent (this=, socket=) at /usr/src/debug/baloo-5.21.0/src/file/kinotify.cpp:421 #17 0x7fb6a55c873f in call (a=0x7ffdd6b05860, r=0x20fe530, this=0x20f9d40) at ../../src/corelib/kernel/qobject_impl.h:124 #18 QMetaObject::activate (sender=sender@entry=0x2113b30, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdd6b05860) at kernel/qobject.cpp:3698 #19 0x7fb6a55c92e7 in QMetaObject::activate (sender=sender@entry=0x2113b30, m=m@entry=0x7fb6a59e7780 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdd6b05860) at kernel/qobject.cpp:3578 #20 0x7fb6a564a8ee in QSocketNotifier::activated (this=this@entry=0x2113b30, _t1=13) at .moc/moc_qsocketnotifier.cpp:134 #21 0x7fb6a55d5a89 in QSocketNotifier::event (this=0x2113b30, e=0x7ffdd6b059d0) at kernel/qsocketnotifier.cpp:260 #22 0x7fb6a559918d in QCoreApplication::notify (this=, receiver=, event=) at kernel/qcoreapplication.cpp:1038 #23 0x7fb6a5598e95 in QCoreApplication::notifyInternal (this=0x7ffdd6b05c70, receiver=0x2113b30, event=event@entry=0x7ffdd6b059d0) at kernel/qcoreapplication.cpp:965 #24 0x7fb6a55f0ca5 in sendEvent (event=0x7ffdd6b059d0, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:224 #25 s
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 --- Comment #41 from Sergey --- My hardware is the following: CPU: Phenom II X4 810 GPU: NVIDIA GeForce 7600 GS/PCIe/SSE2 512MB RAM: 12GB I had no problems in KDE4. Games like OpenRA are still working in Plasma 5, so it's not a problem of video card/drivers. [code] $ mv ~/.config/kwinrc ~/.config/kwinrc.bak $ kwin_x11 --replace OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2 OpenGL version string: 2.1.2 NVIDIA 304.131 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 304.131 GPU class: NV40/G70 OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.17.4 Linux kernel version: 3.18.34 Requires strict binding:no GLSL shaders: limited Texture NPOT support: yes Virtual Machine:no Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 0, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.44882, 0.14882, 0.14882, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.50064, 0.80064, 0.50064, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.05054, 0.05054, 0.35054, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0, 0, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0.4, 0, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 0.5, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0.4, 0.5, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.134646, 0.044646, 0.044646, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.200256, 0.320256, 0.200256, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.02527, 0.02527, 0.17527, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.360172, 0.390172, 0.420172, 0.6) kwin_core: ShaderManager self test failed kwin_core: Failed to initialize compositing, compositing disabled QXcbConnection: XCB error: 3 (BadWindow), sequence: 710, resource id: 1185, major code: 3 (GetWindowAttributes), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 711, resource id: 1185, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1772, resource id: 65011718, major code: 42 (SetInputFocus), minor code: 0 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2 OpenGL version string: 2.1.2 NVIDIA 304.131 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 304.131 GPU class: NV40/G70 OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.17.4 Linux kernel version: 3.18.34 Requires strict binding:no GLSL shaders: limited Texture NPOT support: yes Virtual Machine:no Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 0, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.44882, 0.14882, 0.14882, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.50064, 0.80064, 0.50064, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.05054, 0.05054, 0.35054, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0, 0, 0.6) P
[amarok] [Bug 363054] Building amarok-2.8.90 with GCC-6.1.0 fails with "error: 'Playlists::Playlist::ModelStack' has not been declared"
https://bugs.kde.org/show_bug.cgi?id=363054 Johannes Huber changed: What|Removed |Added CC||j...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 363679] muon update manager crashes on segmentation fault during startup
https://bugs.kde.org/show_bug.cgi?id=363679 --- Comment #2 from Ron St. Denis --- (In reply to Aleix Pol from comment #1) > Can you check again if it works? We've had some issues in our OCS servers. Although I'm not the original submitter, I experienced the same issue yesterday and it is working fine today, so I'm guessing that it was in fact a problem with your OCS servers. Thank you... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 Sergey changed: What|Removed |Added CC||energumenos...@gmail.com --- Comment #40 from Sergey --- I have the same problem with compositor not working on the following versions of Plasma: 5.5.5-r1 and 5.6.4. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 363679] muon update manager crashes on segmentation fault during startup
https://bugs.kde.org/show_bug.cgi?id=363679 Ron St. Denis changed: What|Removed |Added CC||rjstde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361301] [WACOM] Eraser "paints" when using the pen's eraser tip
https://bugs.kde.org/show_bug.cgi?id=361301 --- Comment #3 from Boudewijn Rempt --- Thanks for checking back! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 --- Comment #21 from elk...@yahoo.com --- Created attachment 99290 --> https://bugs.kde.org/attachment.cgi?id=99290&action=edit Assistant glitch workaround demo image I've found a workaround for this, at least in regard to 5 point perspective using fisheye assistants. Attached is a blank image demonstrating this workaround. With it you can zoom in to your heart's content without the canvas blacking out (and it's surprising just how happy that makes me:)). The key to avoiding the issue is that the area defined by either fisheye must be completely outside of the image. Since fisheyes repeat themselves once on either side (along their defining line segment, a feature usually used for making panoramas) you will still get assisted drawing on the image if things are set up properly. Note: If you want to change the resolution of this demo image adjust pixels per inch or pixels per cenimeter. Assistants use points for their positional unit, and points key off of inches or centimeters, so if you scale the image any other way, the assistants will not match that scaling. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363756] Empty "Tool options" docker after upgrade
https://bugs.kde.org/show_bug.cgi?id=363756 --- Comment #1 from Ilya V. Portnov --- Created attachment 99289 --> https://bugs.kde.org/attachment.cgi?id=99289&action=edit Screenshot of empty "tool options" docker -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363756] New: Empty "Tool options" docker after upgrade
https://bugs.kde.org/show_bug.cgi?id=363756 Bug ID: 363756 Summary: Empty "Tool options" docker after upgrade Product: krita Version: git master Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: port...@bk.ru I just did fresh "git pull" and "make install" after a pair of weeks; when I started krita, I saw empty "tool options" docker (will attach screenshot). Switching to another workspace did not help; neither did restarting of krita. What helps is to switch from brush to another tool and than switch to brush again. But if I restart krita, the docker is empty again. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362221] Used language is platform language, but Krita thinks it has American English selected
https://bugs.kde.org/show_bug.cgi?id=362221 --- Comment #3 from Boudewijn Rempt --- This bug is a duplicate of another I cannot find right now; what works for me to get Krita totally in, say, Japanese, is open a cmd window, type set LANG=ja then go to the krita install directory and execute krita.exe. This seems something that went totally wrong inside Qt5, and I haven't figured it out yet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363755] Moving a Saturation layer crashes
https://bugs.kde.org/show_bug.cgi?id=363755 jalmiart changed: What|Removed |Added CC||jalmi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363754] crashes when trying open with tablet pen
https://bugs.kde.org/show_bug.cgi?id=363754 Boudewijn Rempt changed: What|Removed |Added Component|usability |tablet support CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- This is likely related to your brand of tablet. Which we haven;t got access to. It sounds like the problem people reported about Trust, Genius, Peritab and similar cheap uc-logic rebranded tablets. Please make a tablet log following https://docs.krita.org/KritaFAQ#Tablets. But without hardware, we cannot work around the broken tablet drivers; we tried buying a Trust tablet, and that works on our test system. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363755] New: Moving a Saturation layer crashes
https://bugs.kde.org/show_bug.cgi?id=363755 Bug ID: 363755 Summary: Moving a Saturation layer crashes Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: jalmi...@gmail.com Moving a Saturation layer by dragging crashes Krita. See Steps to reproduce. Reproducible: Always Steps to Reproduce: 1. Create new custom document: Predefined A3, 300ppi, landscape, name it. On content tab, set 3 layers, with medium grey bg color. Other settings with default values. 2. Add some new layers, name them. 3. Fill one of the layers with black color and set its layer Blending Mode to Saturation. 4. Try to grag the layer to be topmost. If this does not yet cause crash, drag the layer somewhere once or twice again. Actual Results: UI becomes laggy/unresponsive, processor usage goes up from 5% to around 30% and memory usage from 35% to 95% and over. UI goes greyed out and soon "Krita has stopped working" dialog appears. Expected Results: The layer is moved without too much lagginess. Software does not crash. Windows 7 Professional SP 1 64-bit Intel Core i7-4712MQ CPU @2.30GHz 8,00 GB RAM NVIDIA GeForce GT 740M In Krita's performance settings, memory limit is set to 50% (all at default settings). Tried to reproduce 4 times, always crashed. Problem signature: Problem Event Name:APPCRASH Application Name:krita.exe Application Version:0.0.0.0 Application Timestamp:0409 Fault Module Name:libkritaimage.dll Fault Module Version:0.0.0.0 Fault Module Timestamp:6f808060 Exception Code:c005 Exception Offset:0014e990 OS Version:6.1.7601.2.1.0.256.48 Locale ID:1035 Additional Information 1:82db Additional Information 2:82db4fd4bbdfe684fa3453fcfce68442 Additional Information 3:f8a3 Additional Information 4:f8a3a304453e7c46f9b9bbf9a29eef78 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363526] git master - running latest build (May 25th) via master ppa causes the user's home directory to be deleted.
https://bugs.kde.org/show_bug.cgi?id=363526 --- Comment #14 from Wegwerf --- Hehe, nice reminder. Now we need someone to draw up some animated KDE mascot eating my homework! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363526] git master - running latest build (May 25th) via master ppa causes the user's home directory to be deleted.
https://bugs.kde.org/show_bug.cgi?id=363526 Jesse changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #13 from Jesse --- This bug has now been fixed in the latest git master build. The dev's have added a warning in the status bar after running the Kdenlive master version from the kdenilve-master ppa (I added a screenshot before posting this comment). Issue has been fixed/resolved. Thanks JB for all your hard work! As always. :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363526] git master - running latest build (May 25th) via master ppa causes the user's home directory to be deleted.
https://bugs.kde.org/show_bug.cgi?id=363526 --- Comment #12 from Jesse --- Created attachment 99288 --> https://bugs.kde.org/attachment.cgi?id=99288&action=edit Screenshot example -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363754] New: crashes when trying open with tablet pen
https://bugs.kde.org/show_bug.cgi?id=363754 Bug ID: 363754 Summary: crashes when trying open with tablet pen Product: krita Version: 3.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: drabik.mari...@gmail.com When I trying open Krita with tablet it crashes. When I open by mause and after that i try to manipulate with tablet it crashes. Tablet is old but with kirta 2.9 works fine. Open O`wide Pentagram tablet. Reproducible: Always Steps to Reproduce: 1. trying to open with tablet pen 2. 3. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362221] Used language is platform language, but Krita thinks it has American English selected
https://bugs.kde.org/show_bug.cgi?id=362221 Marcus Kjeldsen changed: What|Removed |Added CC||herrkjeld...@gmail.com --- Comment #2 from Marcus Kjeldsen --- I can confirm on win 10 krita 3.0, norwegian locale, english system language. I can get American English by first adding a fallback language, and switching them both, and then removing the fallback language (although the switch application language dialog box still retains some norwegian :D ) -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 363054] Building amarok-2.8.90 with GCC-6.1.0 fails with "error: 'Playlists::Playlist::ModelStack' has not been declared"
https://bugs.kde.org/show_bug.cgi?id=363054 --- Comment #6 from nsane...@gmail.com --- This patch fixes the issue on my end: https://build.opensuse.org/package/view_file/openSUSE:Factory/amarok/gcc6-workaround.patch?rev=b81d335fe49337f84d9c5c232b5746a2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Bruno Léon changed: What|Removed |Added CC||bruno.l...@nividic.org -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] New: crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 Bug ID: 363753 Summary: crash-at-exit in QtCurve::Style::disconnectDBus Product: QtCurve Version: git Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: qt5 Assignee: yyc1...@gmail.com Reporter: rjvber...@gmail.com CC: h...@kde.org I've just experience a crash exiting from KDevelop5, leading to the backtrace attached below. I'm looking into it. It is not a regular event, fortunately. It's probably related to the recent changes from March 19th 2016 (I only updated yesterday). It looks like a double free, or a double disconnect in this case, calling QDbusConnection::sessionBus() when there is no more connection (=> this==NULL in frame #12). Reproducible: Couldn't Reproduce Actual Results: Application: kdevelop (kdevelop), signal: Segmentation fault: 11 (lldb) process attach --pid 18494 Process 18494 stopped Executable module set to "/Applications/MacPorts/KF5/kdevelop.app/Contents/MacOS/kdevelop.bin". Architecture set to: x86_64-apple-macosx. (lldb) set set term-width 200 (lldb) thread info thread #1: tid = 0x12ad634, 0x7fff85129e20 libsystem_kernel.dylib`__wait4 + 8, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP (lldb) bt all * thread #1: tid = 0x12ad634, 0x7fff85129e20 libsystem_kernel.dylib`__wait4 + 8, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP * frame #0: 0x7fff85129e20 libsystem_kernel.dylib`__wait4 + 8 frame #1: 0x0001070c6fde libKF5Crash.5.dylib`KCrash::startProcess(int, char const**, bool) [inlined] startProcessInternal(argc=, directly=) + 125 at kcrash.cpp:641 frame #2: 0x0001070c6f61 libKF5Crash.5.dylib`KCrash::startProcess(argc=, argv=, waitAndExit=) + 17 at kcrash.cpp:623 frame #3: 0x0001070c6de9 libKF5Crash.5.dylib`KCrash::defaultCrashHandler(sig=) + 1049 at kcrash.cpp:527 frame #4: 0x7fff8b9035aa libsystem_platform.dylib`_sigtramp + 26 frame #5: 0x00010a30b15f QtCore`QMutex::lock() [inlined] std::__1::__atomic_base::compare_exchange_strong(__m=) + 1 at atomic:622 frame #6: 0x00010a30b15e QtCore`QMutex::lock() [inlined] bool QAtomicOps::testAndSetAcquire(std::__1::atomic&, QMutexData*, QMutexData*, QMutexData**) at qatomic_cxx11.h:158 frame #7: 0x00010a30b15e QtCore`QMutex::lock() [inlined] QBasicAtomicPointer::testAndSetAcquire(QMutexData*, QMutexData*, QMutexData*&) at qbasicatomic.h:276 frame #8: 0x00010a30b15e QtCore`QMutex::lock() [inlined] QBasicMutex::fastTryLock(QMutexData*&) at qmutex.h:82 frame #9: 0x00010a30b15e QtCore`QMutex::lock(this=0x0020) + 14 at qmutex.cpp:219 frame #10: 0x000108b60f31 QtDBus`QDBusConnectionManager::busConnection(QDBusConnection::BusType) [inlined] QMutexLocker::QMutexLocker(m=0x0020) + 81 at qmutex.h:128 frame #11: 0x000108b60f29 QtDBus`QDBusConnectionManager::busConnection(QDBusConnection::BusType) [inlined] QMutexLocker::QMutexLocker(m=0x0020) at qmutex.h:131 frame #12: 0x000108b60f29 QtDBus`QDBusConnectionManager::busConnection(this=0x, type=SessionBus) + 73 at qdbusconnection.cpp:116 frame #13: 0x000108b63878 QtDBus`QDBusConnection::sessionBus() + 24 at qdbusconnection.cpp:1180 frame #14: 0x000116821ead qtcurve.so`QtCurve::Style::disconnectDBus(this=0x7fa47899f000) + 61 at qtcurve.cpp:694 frame #15: 0x00011685aea6 qtcurve.so`QtCurve::StylePlugin::~StylePlugin() [inlined] QtCurve::runAllCleanups() + 13 at qtcurve_plugin.cpp:86 frame #16: 0x00011685ae99 qtcurve.so`QtCurve::StylePlugin::~StylePlugin() [inlined] QtCurve::StylePlugin::~StylePlugin(this=) + 16 at qtcurve_plugin.cpp:167 frame #17: 0x00011685ae89 qtcurve.so`QtCurve::StylePlugin::~StylePlugin() [inlined] QtCurve::StylePlugin::~StylePlugin(this=) at qtcurve_plugin.cpp:166 frame #18: 0x00011685ae89 qtcurve.so`QtCurve::StylePlugin::~StylePlugin(this=) + 9 at qtcurve_plugin.cpp:166 frame #19: 0x00010a4c524d QtCore`QLibraryPrivate::unload(this=0x7fa469f1dff0, flag=NoUnloadSys) + 93 at qlibrary.cpp:551 frame #20: 0x00010a4bdd48 QtCore`QFactoryLoaderPrivate::~QFactoryLoaderPrivate(this=0x7fa469f1d160) + 88 at qfactoryloader.cpp:88 frame #21: 0x00010a4be14e QtCore`QFactoryLoaderPrivate::~QFactoryLoaderPrivate() [inlined] QFactoryLoaderPrivate::~QFactoryLoaderPrivate(this=0x7fa469f1d160) + 14 at qfactoryloader.cpp:85 frame #22: 0x00010a4be149 QtCore`QFactoryLoaderPrivate::~QFactoryLoaderPrivate(this=0x7fa469f1d160) + 9 at qfactoryloader.cpp:85 frame #23: 0x00010a4fc801 QtCore`QObject::~QObject() [inlined] QScopedPointerDeleter::cleanup(pointer=) + 2033 at qscopedpointer.h:54 frame #24: 0x00010a4fc7f6 QtCore`QObject::~QObject() [inlined] QScopedPointer >::~Q
[krita] [Bug 336122] Impossible to colour-pick outside of original image when in wrap-around mode
https://bugs.kde.org/show_bug.cgi?id=336122 David REVOY changed: What|Removed |Added Resolution|FIXED |--- CC||i...@davidrevoy.com Status|RESOLVED|REOPENED --- Comment #5 from David REVOY --- I reopen this one as a regression in 3.0, it was confirmed on Linux and Windows during the live-stream of Gdquest. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 363752] New: typo in builtindocumentation.py
https://bugs.kde.org/show_bug.cgi?id=363752 Bug ID: 363752 Summary: typo in builtindocumentation.py Product: kdevelop Version: 4.7.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: all build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: alexeyt...@gmail.com in /usr/share/apps/kdevpythonsupport/documentation_files/builtindocumentation.py there is a typo class set(): ... def intersetion(self, other, *others): return set() should be interse c tion Reproducible: Always Please fix. -- You are receiving this mail because: You are watching all bug changes.
