[klipper] [Bug 343519] Klipper systray widget is not closed automatically once a user has selected an item
https://bugs.kde.org/show_bug.cgi?id=343519 Sergei Stolyarov changed: What|Removed |Added CC||ser...@regolit.com --- Comment #11 from Sergei Stolyarov --- There should option like “Close menu on item select”. And, probably, another option: target, where clicked item contents should be placed (clipboard or selection). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 358353] kscreen ignores primary screen
https://bugs.kde.org/show_bug.cgi?id=358353 --- Comment #2 from Martin van Es --- I seems I can reliably work-around the problem by restarting plasmashell after connecting the external monitor. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358522] New: Fix-it hint for 'Update declaration signature' is unreliable
https://bugs.kde.org/show_bug.cgi?id=358522
Bug ID: 358522
Summary: Fix-it hint for 'Update declaration signature' is
unreliable
Product: kdevelop
Version: 4.90.91
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: fa...@kde.org
Type this:
class FooPrivate
{
void foo();
};
void FooPrivate::foo()
{
}
Then go to ::foo() and make it ::foo(bool). Wait a long time (too long a time
IMHO) and a fixit hint will appear suggesting "Update method signature". Ignore
it, type space then 'b'
(i.e. void FooPrivate::foo(bool b)). The fixit hint went away, and isn't coming
back.
Reproducible: Always
Expected Results:
It should offer me to update the method signature in order to insert "bool b".
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 358521] New: Completion only offers to implement a method when under a '}'
https://bugs.kde.org/show_bug.cgi?id=358521 Bug ID: 358521 Summary: Completion only offers to implement a method when under a '}' Product: kdevelop Version: 4.90.91 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: fa...@kde.org In kio/autotests/clipboardupdatertest.h add a method void foo() after all other test methods. In the .cpp file, go to the first line after the closing '}' of testPasteAfterRenameFiles() and request completion, it will offer (after a bit of time which I find too long) * implement void ClipboardUpdaterTest::foo() [as expected] Cancel this popup, insert one blank line, call completion again -> it doesn't offer this anymore! Reproducible: Always Expected Results: It shouldn't matter if I'm right under a '}' or not. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358520] New: Completion offers to implement std::set
https://bugs.kde.org/show_bug.cgi?id=358520
Bug ID: 358520
Summary: Completion offers to implement std::set *
qgpu_features(const QString&)
Product: kdevelop
Version: 4.90.91
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: fa...@kde.org
At the top of kio/autotests/clipboardupdatertest.cpp (probably doesn't matter),
type
class FooPrivate
{
void foo();
};
then request completion, it will offer
* implement std::set * qgpu_features(const QString&) (WTF?)
* implement void FooPrivate::foo() [as expected]
Reproducible: Always
Expected Results:
it shouldn't offer me to implement random stuff from Qt.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 358418] Alignment of widgets to grid can prevent optimal sizes and alignments for some widgets.
https://bugs.kde.org/show_bug.cgi?id=358418 --- Comment #2 from cher...@aip.de --- Weather widget: http://kde-apps.org/content/show.php/Weather+Widget?content=169572 The behaviour in the shot is reproducible with other widgets, e.g. colloquial clock . Although a perfect grid alignment would be nice, personally I would prefer an option for pixel perfect placement. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358506] Fix-it hint for missing include should suggest QCamelCase include
https://bugs.kde.org/show_bug.cgi?id=358506 --- Comment #3 from David Faure --- One possible solution is to offer for QFoo, i.e. rely on the Qt headers being correct, in addition to the code that actually parses them. I suppose that's what QtCreator does... (after checking that such a file does exist, of course). -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 358519] New: rule-of-three: ignore trivial destructors
https://bugs.kde.org/show_bug.cgi?id=358519 Bug ID: 358519 Summary: rule-of-three: ignore trivial destructors Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: nyall.daw...@gmail.com CC: smart...@kde.org The rule of three check should ignore trivial destructors - eg empty destructors -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358506] Fix-it hint for missing include should suggest QCamelCase include
https://bugs.kde.org/show_bug.cgi?id=358506 --- Comment #2 from David Faure --- No I'm using branch 5.0 now, after Milian said the same. (and yeah, I hate branches, especially when master isn't the latest and greatest...) Even in 5.0 there are two guis: the numbered suggestions at the top of the view, and the pushbutton in the "Semantic analysis" popup. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 358470] Not reconnecting to WiFi - Waiting authorization
https://bugs.kde.org/show_bug.cgi?id=358470 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #4 from Jan Grulich --- This should help: https://techbase.kde.org/Projects/Solid/Plasma-nm#Plasma-nm_fails_to_activate_my_connection -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358518] New: Canvas Zooms out whenever the stylys returns to the active area on the wacom ablet
https://bugs.kde.org/show_bug.cgi?id=358518 Bug ID: 358518 Summary: Canvas Zooms out whenever the stylys returns to the active area on the wacom ablet Product: krita Version: 3.0 Alpha Platform: Mac OS X Disk Images URL: https://youtu.be/-6339OTK7ns OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: sa...@openmailbox.org Whenever the stylus enters the active area on the tablet the canvas zooms out. Reproducible: Always Steps to Reproduce: 1. Create a new file 2. lift up the pen about 5 cm above the active area then bring it down to draw 3. canvas zooms out each time Actual Results: Canvas zooms out Expected Results: nothing to happen on the zoom level on the canvas OS: Mac OS X 10.10.5 Tablet: Wacom Intuos 4 Medium PTK 840 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358271] Some comboboxes are missing shadows and are hard to click
https://bugs.kde.org/show_bug.cgi?id=358271 Hugo Pereira Da Costa changed: What|Removed |Added Assignee|plasma-de...@kde.org|k...@davidedmundson.co.uk CC||hugo.pere...@free.fr Component|general |QtQuickControls --- Comment #2 from Hugo Pereira Da Costa --- Reassinging to QtQuickControls Does not happen to regular (QWidget based) comboboxes. Haven't checked with other widget styles. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358517] New: Krita suddenly crashed
https://bugs.kde.org/show_bug.cgi?id=358517 Bug ID: 358517 Summary: Krita suddenly crashed Product: krita Version: 2.9.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: oneagui...@gmail.com Application: krita (2.9.10) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Using ruler tool (spline option), recent new layer, platform: ubuntu gnome 15.10 The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb19c42a840 (LWP 6061))] Thread 5 (Thread 0x7fb167fff700 (LWP 6079)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb199fad286 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fb199fa9063 in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7fb196c7774b in KisTileDataPooler::waitForWork (this=0x220ae60) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/image/tiles3/kis_tile_data_pooler.cc:165 #4 KisTileDataPooler::run (this=0x220ae60) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/image/tiles3/kis_tile_data_pooler.cc:187 #5 0x7fb199facd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fb193e646aa in start_thread (arg=0x7fb167fff700) at pthread_create.c:333 #7 0x7fb1996d5eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb1677fe700 (LWP 6080)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb199fad286 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fb199fa9483 in QSemaphore::tryAcquire(int, int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7fb196c9fe83 in KisTileDataSwapper::waitForWork (this=) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7fb196ca00ea in KisTileDataSwapper::run (this=0x220aea0) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7fb199facd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fb193e646aa in start_thread (arg=0x7fb1677fe700) at pthread_create.c:333 #7 0x7fb1996d5eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb1776d4700 (LWP 6081)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb199fad286 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fb19afe829c in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x7fb199facd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7fb193e646aa in start_thread (arg=0x7fb1776d4700) at pthread_create.c:333 #5 0x7fb1996d5eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb1667fc700 (LWP 6082)): #0 0x7fb1939c3884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb19397e770 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb19397f11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb19397f2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb19a0ed20e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7fb19a0bb0d1 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fb19a0bb445 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fb199faa4f9 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fb19a09b133 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fb199facd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fb193e646aa in start_thread (arg=0x7fb1667fc700) at pthread_create.c:333 #11 0x7fb1996d5eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb19c42a840 (LWP 6061)): [KCrash Handler] #6 0x7fb19baa938b in KisPaintingAssistantsDecoration::adjustPosition (this=0x4dc7f90, point=..., strokeBegin=...) at /build/krita-2.9-az5S7I/krita-2.9-2+git20151209+r43/krita/ui/kis_painting_assistants_decoration.cpp:128 #7 0x7fb19bbc04ec in KisToolFreehand::adjustPosition (this
[valgrind] [Bug 358478] drd/tests/std_thread.cpp doesn't build with GCC6
https://bugs.kde.org/show_bug.cgi?id=358478 Bart Van Assche changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Bart Van Assche --- Does r15773 fix the compilation issue ? If so, does this change make the regression drd regression tests pass ? If not, what does drd report ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 358516] New: KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0).
https://bugs.kde.org/show_bug.cgi?id=358516 Bug ID: 358516 Summary: KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). Product: frameworks-kactivities Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: slava18+b...@gmail.com CC: plasma-b...@kde.org >From .xsession-errors, keeps crashing several times a day: KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). And whether your filesystem supports shared memory Application::crashHandler() called with signal 6; recent crashes: 1 KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit Service started, version: KActivities: FATAL ERROR: Failed to contact the activity manager daemon Plasma 5 behaves very strangely (i.e. I cannot open a right-click menu on Kicker items, crashes plasma). I suspect it's because of the above errors. Removing .local/share/kactivitymanagerd/ does not help. Reference in Archlinux Bugs: https://bugs.archlinux.org/task/47473 Reproducible: Sometimes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358193] Color labels exported from LightRoom not recognized by digiKam
https://bugs.kde.org/show_bug.cgi?id=358193 --- Comment #7 from LuHe --- Sorry it took so long - i have attached a compressed file which contains all valid color tags for Lightroom and digiKam 5 beta 2. I think it would be best if the assignment of the colors to the tags would be configurable - so that digikam allows to both read and write color tags into different sets of metadata. Just like comments, ratings and tags are configurable now (awesome feature by the way, thanks for this great work!). The use case for this is that the images are managed by different people using different applications - so it would be great if a 2-way synchronization between these tools were possible. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358193] Color labels exported from LightRoom not recognized by digiKam
https://bugs.kde.org/show_bug.cgi?id=358193 --- Comment #6 from LuHe --- Created attachment 96821 --> https://bugs.kde.org/attachment.cgi?id=96821&action=edit All possible color tags for Lightroom and digiKam 5 beta 2 -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 358515] sha0 in list generated by all_hash_types() even when sha0 is not supported.
https://bugs.kde.org/show_bug.cgi?id=358515 maurerpe changed: What|Removed |Added CC||junk4me46...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 358515] sha0 in list generated by all_hash_types() even when sha0 is not supported.
https://bugs.kde.org/show_bug.cgi?id=358515 --- Comment #1 from maurerpe --- Created attachment 96820 --> https://bugs.kde.org/attachment.cgi?id=96820&action=edit Patch to remove sha0 from all_hash_types() when sha0 is not available -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 358515] New: sha0 in list generated by all_hash_types() even when sha0 is not supported.
https://bugs.kde.org/show_bug.cgi?id=358515 Bug ID: 358515 Summary: sha0 in list generated by all_hash_types() even when sha0 is not supported. Product: qca Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dr...@land.ru Reporter: junk4me46...@yahoo.com CC: br...@frogmouth.net, jus...@affinix.com Commit qca-ossl: Fix build without support for SHA-0 on 24 Sept 2015 (0dbed8eb38afd1561907a52283091c37e7b85156), fixed qca-ossl.cpp to compile when the openssl implementation doesn't support sha0, but it didn't remove sha0 from the list returned by all_hash_types(). Reproducible: Always Actual Results: sha0 included. Expected Results: sha0 should not be included. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 358513] plasmashell crashed when I moving mouse on lower left corner on desktop
https://bugs.kde.org/show_bug.cgi?id=358513 David Edmundson changed: What|Removed |Added Component|general |General Target Milestone|1.0 |--- Product|plasmashell |Baloo Assignee|k...@davidedmundson.co.uk|m...@vhanda.in CC||pinak.ah...@gmail.com Version|5.5.3 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356490] Project Bin design and workflow improvement suggestions (video example included)
https://bugs.kde.org/show_bug.cgi?id=356490 --- Comment #5 from Jesse --- More than fair. If it's a need, it's a need. :) I'd say disregard suggestion #4 then. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 358514] New: [UserBase Wiki] Make registration possible to find, fix registration links
https://bugs.kde.org/show_bug.cgi?id=358514 Bug ID: 358514 Summary: [UserBase Wiki] Make registration possible to find, fix registration links Product: www.kde.org Version: unspecified Platform: Other URL: http://i.imgur.com/3qGbNOP.png OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: qubo...@gmail.com 1. Two pages link to https://userbase.kde.org/Special:UserLogin/signup which confuses new users who are trying to figure out how to register. The messages need to be changed. Instead they should link to https://userbase.kde.org/index.php?title=Special:OpenIDLogin https://userbase.kde.org/MediaWiki:Nosuchuser https://userbase.kde.org/MediaWiki:Anontalkpagetext Video of one problematic case: https://youtu.be/d2jHIIt_KaI 2. It is impossible to quickly find how to register. Please solve this by editing the skin so that in "PERSONAL TOOLS" instead of "OpenID / Identity login" it says "Register" because it seems an openid/kdeid/whatever login results in the requirement to create a username which is what "registration" is to people. OpenID and "identity" is unknown and makes people think they have to look elsewhere. If you rename it into "Register", then people will quicker realize that they have to read the wall of text below the openid form (by the way, you might want to make the kde identity login the one that is pre-selected and on the left). Ideally also remove the openid icon. it's confusing. people who like openid will cheer when they go to registration but people who just want to register and have no clue about openid are confused by the icon. 3. If you're at it, you could remove the layout-distrubing language icon and padding from the "English" (language) link. See http://i.imgur.com/3qGbNOP.png for how it could be... Reproducible: Always These issues cause you to lose contributions because users can't figure out how to start contributing. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356499] Issues and suggestions with the "Properties" widget (video example included)
https://bugs.kde.org/show_bug.cgi?id=356499 Jesse changed: What|Removed |Added CC||jesse.dub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358396] Kdenlive-git - Wipe transition is discoloring image during playback in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=358396 Jesse changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Jesse --- Yessir, that worked! in Antergos, I used Pamac, the software center, to uninstall mlt, then build + install the mlt-git package, re-installed Kdenlive, and it seems to work fine now. I guess that would make sense that the Kdenlive-git package would work with the mlt-git package (assuming the dev's are using that version as their backbone). I guess that fixes the issue -- being that I am using the development version. Thanks wegwerf! Marking this bug as fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358513] New: plasmashell crashed when I moving mouse on lower left corner on desktop
https://bugs.kde.org/show_bug.cgi?id=358513 Bug ID: 358513 Summary: plasmashell crashed when I moving mouse on lower left corner on desktop Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mrl...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I moving cursor on lower left side on desktop and then plasmashell crashed - Unusual behavior I noticed: plasmashell crashed - Custom settings of the application: nothing, I think The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa93fbc8800 (LWP 998))] Thread 17 (Thread 0x7fa92ae25700 (LWP 1000)): #0 0x7fa93a2498dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa93e367bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa93e36974f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa92cf977e9 in QXcbEventReader::run (this=0xbbce90) at qxcbconnection.cpp:1229 #4 0x7fa93a94ba6e in QThreadPrivate::start (arg=0xbbce90) at thread/qthread_unix.cpp:331 #5 0x7fa939a256aa in start_thread (arg=0x7fa92ae25700) at pthread_create.c:333 #6 0x7fa93a254eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fa923fff700 (LWP 1036)): #0 0x7fa93a2498dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa936f801ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa936f802fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa93ab8350b in QEventDispatcherGlib::processEvents (this=0x7fa91c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa93ab2a50a in QEventLoop::exec (this=this@entry=0x7fa923ffeda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa93a946ac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa93d219c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa93a94ba6e in QThreadPrivate::start (arg=0xc9ff90) at thread/qthread_unix.cpp:331 #8 0x7fa939a256aa in start_thread (arg=0x7fa923fff700) at pthread_create.c:333 #9 0x7fa93a254eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fa9197c5700 (LWP 1039)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa921a331b3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fa921a328a8 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fa939a256aa in start_thread (arg=0x7fa9197c5700) at pthread_create.c:333 #4 0x7fa93a254eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fa914f55700 (LWP 1040)): #0 0x7fa93a2498dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa936f801ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa936f802fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa93ab8350b in QEventDispatcherGlib::processEvents (this=0x7fa918c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa93ab2a50a in QEventLoop::exec (this=this@entry=0x7fa914f54da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa93a946ac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa93d219c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa93a94ba6e in QThreadPrivate::start (arg=0xf2eb20) at thread/qthread_unix.cpp:331 #8 0x7fa939a256aa in start_thread (arg=0x7fa914f55700) at pthread_create.c:333 #9 0x7fa93a254eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fa90f08d700 (LWP 1049)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa93f5fc194 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fa93f5fc1d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fa939a256aa in start_thread (arg=0x7fa90f08d700) at pthread_create.c:333 #4 0x7fa93a254eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fa88e145700 (LWP 1050)): #0 0x7ffef0568c4f in clock_gettime () #1 0x7fa93a26338d in __GI___clock_gettime (clock_id=, tp=tp@entry=0x7fa88e144b10) at ../sysdeps/unix/clock_gettime.c:115 #2 0x000
[kdenlive] [Bug 356491] "Audio Signal" widget doesn't show level indicator numbers after Kdenlive restarts (video example included)
https://bugs.kde.org/show_bug.cgi?id=356491 --- Comment #7 from Jesse --- Just saw the monitor audio level indicator changes in the latest 15.13.0 master-git build. Looks AWESOME! I'd be perfectly satisfied as a professional to work with this. :) So yes, you have my vote: the audio level widget would be unneeded for me at this point. If the consensus is with me, I'd say yeah, drop the widget and save yourself any extra effort with it. :) Great work sir! -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 337254] [UserBase Wiki] Unable to use Google accounts to login
https://bugs.kde.org/show_bug.cgi?id=337254 qubo...@gmail.com changed: What|Removed |Added CC||qubo...@gmail.com --- Comment #11 from qubo...@gmail.com --- Logging in using Google ins still impossible. Please remove google as an option. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 303162] Icon task widget mixes the dolphin launcher and dolphin-emulator launcher
https://bugs.kde.org/show_bug.cgi?id=303162 dolphinus...@gmail.com changed: What|Removed |Added CC||dolphinus...@gmail.com --- Comment #19 from dolphinus...@gmail.com --- (In reply to Gatoso from comment #0) > Dolphin emulator is an open source emulator for gamecube and wii games, its > web site is: http://dolphin-emulator.com That is not the official Dolphin website. The official site is: https://dolphin-emu.org/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358296] Kdevelop crashes when trying to scp a file by rightclick --> run external script
https://bugs.kde.org/show_bug.cgi?id=358296 --- Comment #3 from Michael Brown --- Sorry for the delay.. I have not updated in the meanwhile. Yes I can confirm closing all editor tabs and rightl-click --> External_scripts--> triggers a crash immediately.. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358427] 15.13 git master: monitor audio levels have no indicators for 0, -5, -10, -20 dB
https://bugs.kde.org/show_bug.cgi?id=358427 --- Comment #2 from Jean-Baptiste Mardelle --- Git commit 16b00e2d27ed516bac4044cdce8c1072806eca36 by Jean-Baptiste Mardelle. Committed on 25/01/2016 at 01:11. Pushed by mardelle into branch 'master'. Improved audio monitoring M +2-12 src/monitor/glwidget.cpp M +55 -47 src/monitor/monitoraudiolevel.cpp http://commits.kde.org/kdenlive/16b00e2d27ed516bac4044cdce8c1072806eca36 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358512] New: false importing of mail - kmail2 akonadi bug
https://bugs.kde.org/show_bug.cgi?id=358512 Bug ID: 358512 Summary: false importing of mail - kmail2 akonadi bug Product: kmail2 Version: 4.14.3 Platform: FreeBSD Ports OS: FreeBSD Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dae...@optushome.com.au Kmail2 gives a false report that it has finished importing mail. ** Other unexplained bug reports about mail disappearing could be related to this systemic bug. The illusion is that Kmail2 has imported your mail into your mail directory, when it has in fact moved it to the akonadi database which may or may not succeed in exporting your mail or some of your mail to your mail diretory over the next few hours or days. The result is that people can & do lose some or all of their mail if either the process or the database are disrupted before the slow process is finished. Reproducible: Always Steps to Reproduce: 1. Have over 1 gb email in a non-kmal folder or mbox 2. import the import mail Actual Results: Kmail2 import functions move your email onto the akonadi database instead of your mail directory. Also as Kmail2 puts your email in jeopardy on the akonadi database, the import dialogue tells the user/victim that 100% of the mail has been imported and that the importing is finished. For hours or years afterwards your system becomes unresponsive and clogged up with unexplained akonadi activity while your email remains in jeopardy and will disappear if either the process or database are disrupted. Expected Results: Kmail2 imports email to your mail directory. If importing mail requires a temporary staging area, that it would use /tmp and NOT a database! This appears to be another example of children wanting to use databases for things that should not be on a database. Its arogance to assume previous programers decided against using databases because they failed to understand how fast databases can be; with experience you too may learn that things like configuration & storage files should be kept on disc and not in a database that is open. It's been going on since the 1980s, people design good systems and then next generation of programers foul it up with inappropriate databases. Databases are great in their place and a menace outside it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 --- Comment #37 from AJslye --- Never mind, after waiting 10 minutes or so I tried to log out and back in again and problem came back. I can however log into Plasma (failsafe) without the issue. Here are my current logs: .xsession-errors - http://pastebin.com/fGhKYy6m Xorg.0.log - http://pastebin.com/v9qwzkWU -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 --- Comment #7 from Thomas Lübking --- I meant the "resolved/upstream" condition - you kept reverting it to "unconfirmed" Maybe mousewheel and stupid browser? Could happen if wheeling over the "resolved" combobox alters it instead of scrolling the page - *shrug* -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #26 from Thomas Lübking --- (In reply to Alexey Chernov from comment #25) > According to what? According to "This is not fixed in years and each and every session management code was ported as "#if 0"" If there was some relevant interest, it would be fixed long time, since it's really not that hard. > > Loosing your data is however relevant for everyone. And the latter is the by > > far more severe issue. Restarting applications is merely an annoyance, > > loosing your work is truely expensive. > Hey, how could session management be "apparently relevant for only a > minority of users", but fixes in its behaviour be crucial for a lot of them? [...] > Fully agree here, but we should confirm that nobody said in the beggining > that upstream changes were about to break session management for KF5 > applications. It was just broken. Errr... what? Session management (in terms of "please restore the desktop as I left it") doesn't seem very important, but if you click "logout" and *booom*, gone is your work of the last two hours because the application had no chance (or, well, listened to the wrong events) to ask you to save it, that's pretty important... We're apparently talking past each other. There're two steps: a) logout, clients ask to save your stuff. That works (because of the close event) b) login, clients should restart. That's broken (because the close event is not just an event, but the window "illegally" being withdrawn during logout) You propse to fix (b) by breaking (a) and I'm trying to convince you that this is a really bad idea. > bugs which should be fixed either in library and its clients. It's better to > fix them when no one really relies on the stability too much. It looks like > this time is now for KF5-based application and environment. Yes, we should fix KMainWindow now (if faking close events is finally not considered a permanent behavior despite the majority of clients will probably do that in return to the data commit request - with a fair share actually just calling close() ...) but that has absolutely no implications on whether it's ok to easily break away from established (even though maybe wrong) behavior. > No, that's just postponing and messing up the whole problem. If, as you > stated, almost no one implemented easy and pretty simple interaction > appeared in Qt5, even less would care of possible bugs and corner cases of > the workaround, more complex protocol with close event you propose. There > would be just another argument that it's just too messy, not to mention > already existing argument that no one uses session management. Sorry, but I really cannot read any sense into this paragraph. Please try to rephrase it. The above isn't English grammar at all. > It won't be fixed until it's broken So you demand to jeopardize userdata because otherwise code won't be fixed. Sorry, but there's no way you're ever gonna convince me in this. Any solution that builds upon "jeopardize userdata" is not a solution at all. It's malicious. > I'm pretty sure there would be packages that would require just > most recent Qt version, and it would be acceptable. And jeopardize userdata. What exactly should this help in this case? > What's wrong in relying on changes in recent Qt release That you are not. "Recent Qt releases" start to jeopardize userdata because (no way) all Qt client code has been fixed, ie. distros must not use Qt 5.7 until all client code releases picked up the change. > In this way all the bugfixes should be postponed till Qt6 If a bugfix is *very* likely gonna break more things more badly than it fixes and there is absolutely no need to take this risk? Yes, avoid that fix and come up with a more robust interim solution. > By the way, are you completely sure your changes won't break any clients? > What if someone relies exactly on the current code? Err, on the close event? Well, that's exactly what I suggest to preserve. You're not gonna see more from a ::close() call in client code (it's no virtual and not invoked as slot) > In the opposite, close event or aboutToClose do mean closing > and quitting, but don't imply any data interactions (as it's too late) Errr, no. Please read the Qt API docs. You simply ::ignore() the close event and nothing is gonna be closed or changed. That's why it's massively intercepted to ask users to save stuff - what's also explicitly suggested in the API docs. And that's why somebody considered it a good idea to explicitly close windows on session end, what it's just not. That "somebody" actually wanted to trigger and check the result of the event, but not really close windows. And that's what I'm proposing to deal with the situation. The justification for QGuiApplication::commitDataRequest() though is, that a QGuiApplication doesn't necessarily have any windows at all and still wants to save stuff on logout (and of course before the SIGTERM) = Complete
[plasma-pa] [Bug 358339] Plasma crash after changing default audio output
https://bugs.kde.org/show_bug.cgi?id=358339 David Edmundson changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Product|plasmashell |plasma-pa Target Milestone|1.0 |--- Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358418] Alignment of widgets to grid can prevent optimal sizes and alignments for some widgets.
https://bugs.kde.org/show_bug.cgi?id=358418 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- What's the weather plasmoid you're using in the first shot? Another approach on this is we make sure plasmoids align to the grid properly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 --- Comment #36 from AJslye --- I seemed to have fixed this on one of my system.However, I still need to test this on my other two tomorrow. Here is what I did: First, I added a plasma-safe.desktop file under /usr/share/xsessions with this in it: [Desktop Entry] Encoding=UTF-8 Type=XSession Exec=/usr/bin/startkde --failsafe TryExec=/usr/bin/startkde DesktopNames=KDE Name=Plasma (Failsafe) Comment=Plasma by KDE (Failsafe) X-KDE-PluginInfo-Version=5.5.3 Next, I logged out and into Plasma (Failsafe), no issue. Then I logged out again and selected Plasma, no issue. I have rebooted my system 4 times and logged in and out 10+ times, now it logs in the first time every time. @ David, Is there some file or settings somewhere that startkde --failsafe changes that could have corrected this issue with the normal startkde (Plasma) session? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358463] Crash Upon Login
https://bugs.kde.org/show_bug.cgi?id=358463 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- Error raised here means there's something broken with your openGL drivers. One common cause is NVidia's libGL installed, but the NVidia kernel module missing. *** This bug has been marked as a duplicate of bug 345563 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed
https://bugs.kde.org/show_bug.cgi?id=345563 David Edmundson changed: What|Removed |Added CC||kerryla...@islandnet.com --- Comment #66 from David Edmundson --- *** Bug 358463 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358317] xembedsniproxy crashes when clicking on empty fcitx icon
https://bugs.kde.org/show_bug.cgi?id=358317 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from David Edmundson --- Fixed with 988a7bef7e84a4a2fc6a2f6ec6145e093dfb84f8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358511] New: blocked from using kcron
https://bugs.kde.org/show_bug.cgi?id=358511 Bug ID: 358511 Summary: blocked from using kcron Product: systemsettings Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: paullef...@yahoo.com Application: systemsettings (4.11.16) KDE Platform Version: 4.14.5 (Compiled from sources) 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: went into system tools to see what program might be running that was rapidly filling up my /home disc which appeared to be copying all the photos and videos it could find on my harddrive to /home/tmp/kde-paul. I kept deleting them and eventually changed the permissionsa on /home/tmp/kde-paul so that nothing could write to it. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7f13f3803cb1 in VariablesWidget::needUserColumn() () from /usr/lib64/kde4/kcm_cron.so #6 0x7f13f3803d13 in VariablesWidget::refreshHeaders() () from /usr/lib64/kde4/kcm_cron.so #7 0x7f13f3807d3d in VariablesWidget::VariablesWidget(CrontabWidget*) () from /usr/lib64/kde4/kcm_cron.so #8 0x7f13f3808604 in CrontabWidget::initialize() () from /usr/lib64/kde4/kcm_cron.so #9 0x7f13f3808811 in CrontabWidget::CrontabWidget(QWidget*, CTHost*) () from /usr/lib64/kde4/kcm_cron.so #10 0x7f13f380e766 in KCMCron::KCMCron(QWidget*, QList const&) () from /usr/lib64/kde4/kcm_cron.so #11 0x7f13f38106ab in QObject* KPluginFactory::createInstance(QWidget*, QObject*, QList const&) () from /usr/lib64/kde4/kcm_cron.so #12 0x7f14103e1d03 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /lib64/libkdecore.so.5 #13 0x7f1411c0fd70 in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () from /lib64/libkcmutils.so.4 #14 0x7f1411c158db in KCModuleProxyPrivate::loadModule() () from /lib64/libkcmutils.so.4 #15 0x7f1411c165a5 in KCModuleProxy::realModule() const () from /lib64/libkcmutils.so.4 #16 0x7f1411c169a3 in KCModuleProxy::showEvent(QShowEvent*) () from /lib64/libkcmutils.so.4 #17 0x7f14108c2388 in QWidget::event(QEvent*) () from /lib64/libQtGui.so.4 #18 0x7f141087279c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #19 0x7f1410878e40 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #20 0x7f14115a525a in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5 #21 0x7f140fbedcad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4 #22 0x7f14108bf924 in QWidgetPrivate::show_helper() () from /lib64/libQtGui.so.4 #23 0x7f14108bf77a in QWidgetPrivate::showChildren(bool) () from /lib64/libQtGui.so.4 #24 0x7f14108bf80f in QWidgetPrivate::show_helper() () from /lib64/libQtGui.so.4 #25 0x7f14108c168a in QWidget::setVisible(bool) () from /lib64/libQtGui.so.4 #26 0x7f14108bf78e in QWidgetPrivate::showChildren(bool) () from /lib64/libQtGui.so.4 #27 0x7f14108bf80f in QWidgetPrivate::show_helper() () from /lib64/libQtGui.so.4 #28 0x7f14108c168a in QWidget::setVisible(bool) () from /lib64/libQtGui.so.4 #29 0x7f14108a5166 in QStackedLayout::setCurrentIndex(int) () from /lib64/libQtGui.so.4 #30 0x7f14115d5d4d in KPageViewPrivate::_k_pageSelected(QItemSelection const&, QItemSelection const&) () from /lib64/libkdeui.so.5 #31 0x7f140fc0188a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4 #32 0x7f1410dbd497 in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /lib64/libQtGui.so.4 #33 0x7f1410dc297e in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) () from /lib64/libQtGui.so.4 #34 0x7f1410dc31c6 in QItemSelectionModel::select(QItemSelection const&, QFlags) () from /lib64/libQtGui.so.4 #35 0x7f1410dbe2e8 in QItemSelectionModel::select(QModelIndex const&, QFlags) () from /lib64/libQtGui.so.4 #36 0x7f1410dbd6c2 in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib64/libQtGui.so.4 #37 0x7f14115d4eeb in KPageViewPrivate::_k_rebuildGui() () from /lib64/libkdeui.so.5 #38 0x7f14115d59a5 in KPageViewPrivate::_k_modelChanged() () from /lib64/libkdeui.so.5 #39 0x7f140fc0188a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4 #40 0x7f14115da758 in KPageWidgetModel::addPage(KPageWidgetItem*) () fr
[kdenlive] [Bug 358396] Kdenlive-git - Wipe transition is discoloring image during playback in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=358396 --- Comment #5 from Jesse --- @wegwerf, thanks for the suggestion. I'll give it a try and send an update after testing! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 --- Comment #6 from superrobowiz...@gmail.com --- I actually haven't moved it, that's where DrKonqui put it. I don't see either of those under "component", and selecting qtcurve as the product (there is nothing for nvidia) still leaves only aurorae as the component. (I've never used this website before; can you tell? lol) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358510] New: Akonadi Resource davgroupware crash
https://bugs.kde.org/show_bug.cgi?id=358510 Bug ID: 358510 Summary: Akonadi Resource davgroupware crash Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: dbyent...@gmail.com Application: akonadi_davgroupware_resource (4.89.0) Qt Version: 5.5.1 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Netrunner 17 -- Information about the crash: - What I was doing when the application crashed: The only application that was in active use was an internet browser. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Resource (akonadi_davgroupware_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0d81e71840 (LWP 2643))] Thread 3 (Thread 0x7f0d7fda0700 (LWP 2704)): #0 0x7f0d9215a8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0d8ce31bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f0d8ce3374f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f0d81ac67e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f0d92a67a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0d8d0506aa in start_thread (arg=0x7f0d7fda0700) at pthread_create.c:333 #6 0x7f0d92165eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f0d7d524700 (LWP 3310)): #0 0x7f0d8c751884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0d8c70c770 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0d8c70d11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0d8c70d2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0d92c9f50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0d92c4650a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0d92a62ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0d92a67a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0d8d0506aa in start_thread (arg=0x7f0d7d524700) at pthread_create.c:333 #9 0x7f0d92165eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f0d81e71840 (LWP 2643)): [KCrash Handler] #6 QString::QString (other=..., this=this@entry=0x7ffcb4e81f60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:811 #7 Akonadi::Entity::remoteId (this=this@entry=0x7f0d92d1c3d8 ) at ../../../../akonadi/src/core/entity.cpp:82 #8 0x00468b7e in DavGroupwareResource::retrieveItems (this=this@entry=0x18ec230, collection=...) at ../../../../resources/dav/resource/davgroupwareresource.cpp:257 #9 0x7f0d963f132d in Akonadi::ResourceBasePrivate::slotItemRetrievalCollectionFetchDone (this=, job=0x1885760) at ../../../../akonadi/src/agentbase/resourcebase.cpp:954 #10 0x7f0d963f3200 in Akonadi::ResourceBase::qt_static_metacall (_o=, _c=, _id=, _a=) at ./moc_resourcebase.cpp:294 #11 0x7f0d92c778ea in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0d941a0752 in KJob::result (this=this@entry=0x1885760, _t1=_t1@entry=0x1885760) at ./moc_kjob.cpp:555 #13 0x7f0d941a1311 in KJob::finishJob (this=0x1885760, emitResult=) at ../../../src/lib/jobs/kjob.cpp:109 #14 0x7f0d941a132a in KJob::emitResult (this=) at ../../../src/lib/jobs/kjob.cpp:295 #15 0x7f0d9596e3b3 in Akonadi::JobPrivate::delayedEmitResult (this=) at ../../../../akonadi/src/core/jobs/job.cpp:153 #16 Akonadi::Job::qt_static_metacall (_o=, _c=, _id=, _a=) at ./moc_job.cpp:107 #17 0x7f0d92c787b1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f0d9353d9dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f0d93542ea6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f0d92c48d7b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f0d92c4b176 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f0d92c9f0e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f0d8c70cff7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f0d8c70d250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f0d8c70d2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-
[Breeze] [Bug 358495] pptx has different icon from ppt and odp
https://bugs.kde.org/show_bug.cgi?id=358495 andreas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from andreas --- thanks for reporting the bug. should be fixed now. https://quickgit.kde.org/?p=breeze-icons.git&a=commit&h=f3102cfd83a887df2b80dbce4274b400dbe4b290 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358509] New: Dolphin Crashed
https://bugs.kde.org/show_bug.cgi?id=358509 Bug ID: 358509 Summary: Dolphin Crashed Product: dolphin Version: 15.12.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: boblovgre...@gmail.com Application: dolphin (15.12.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160121) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Copied file in Dolphin from one folder to another, gave some permissions error then crashed -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0da819b8c0 (LWP 3714))] Thread 4 (Thread 0x7f0d90cc8700 (LWP 3716)): #0 0x7f0da7a3724d in poll () from /lib64/libc.so.6 #1 0x7f0d9aa3b432 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f0d9aa3d007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f0d9301be29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f0da1bac94f in QThreadPrivate::start (arg=0x14b1320) at thread/qthread_unix.cpp:331 #5 0x7f0d9d69b4a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f0da7a3fbdd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f0d83831700 (LWP 3717)): #0 0x7f0d9d6a107f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0d8a2cfe63 in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7f0d8a2cf6a7 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7f0d9d69b4a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f0da7a3fbdd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0d7e7fb700 (LWP 3718)): #0 0x7f0da7a3724d in poll () from /lib64/libc.so.6 #1 0x7f0d9cb12264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f0d9cb1236c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0da1dd152b in QEventDispatcherGlib::processEvents (this=0x7f0d780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f0da1d7b63a in QEventLoop::exec (this=this@entry=0x7f0d7e7fad10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f0da1ba7b1c in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f0da1bac94f in QThreadPrivate::start (arg=0x196fb80) at thread/qthread_unix.cpp:331 #7 0x7f0d9d69b4a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f0da7a3fbdd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0da819b8c0 (LWP 3714)): [KCrash Handler] #6 0x8003 in ?? () #7 0x7f0da1d8de67 in QMetaObject::invokeMethod (obj=0x1b87fc0, member=0x7f0da6064b86 "next", type=2313432000, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1464 #8 0x7f0da6056869 in KDialogJobUiDelegate::Private::next() () from /usr/lib64/libKF5JobWidgets.so.5 #9 0x7f0da1dabd79 in QObject::event (this=0x1b87fc0, e=) at kernel/qobject.cpp:1239 #10 0x7f0da2ef08cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x7f0da2ef59d6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7f0da1d7dcf3 in QCoreApplication::notifyInternal (this=0x7fff89e43550, receiver=0x1b87fc0, event=event@entry=0x1ce9ad0) at kernel/qcoreapplication.cpp:965 #13 0x7f0da1d80016 in sendEvent (event=0x1ce9ad0, receiver=) at kernel/qcoreapplication.h:224 #14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x148aa40) at kernel/qcoreapplication.cpp:1593 #15 0x7f0da1d804f8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #16 0x7f0da1dd1103 in postEventSourceDispatch (s=0x14f0360) at kernel/qeventdispatcher_glib.cpp:271 #17 0x7f0d9cb12097 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #18 0x7f0d9cb122c8 in ?? () from /usr/lib64/libglib-2.0.so.0 #19 0x7f0d9cb1236c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #20 0x7f0da1dd150f in QEventDispatcherGlib::processEvents (this=0x14f7690, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #21 0x7f0da1d7b63a in QEventLoop::exec (this=this@entry=0x7fff89e43430, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #22 0x7f0da1d832fd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #23 0x7f0da7d5a862 in kdemain (argc=2, argv=) at /usr/src/debug/dolphin-15.12.0/src/main.cpp:150 #24 0x7f0da7976610 in __libc_start_main () from /lib64/libc.so.6 #25 0x004007f9 in _start () at ../sysdeps/x86_64/start.S:118 Possible duplicat
[ark] [Bug 358508] New: Ark crashes when closing a package while opening a file from it
https://bugs.kde.org/show_bug.cgi?id=358508 Bug ID: 358508 Summary: Ark crashes when closing a package while opening a file from it Product: ark Version: 2.19 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kdemail.net Reporter: sebastian.end...@online.de CC: rak...@freebsd.org Application: ark (2.19) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.3-300.fc23.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I closed ark while one file was opened in the preview (pdf) and I opened another large pdf. During the opening I closed ark and a bit later the first pdf closed and ark crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x558e62cdf905 in MainWindow::updateActions() (this=0x558e646d9a00) at ../../app/mainwindow.cpp:178 #7 0x7f73679bea80 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0x558e64866d20, m=m@entry=0x7f734e7d4600 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #8 0x7f734e5acd23 in Ark::Part::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (this=) at moc_part.cpp:187 #9 0x7f734e5acd23 in Ark::Part::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _id=, _a=, _c=) at moc_part.cpp:99 #10 0x7f73679c4821 in QObject::event(QEvent*) (this=0x558e64866d20, e=) at kernel/qobject.cpp:1222 #11 0x7f73688f193c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x558e645e1210, receiver=receiver@entry=0x558e64866d20, e=e@entry=0x7f7344013970) at kernel/qapplication.cpp:4565 #12 0x7f73688f8796 in QApplication::notify(QObject*, QEvent*) (this=this@entry=0x7ffcabdb6fc0, receiver=receiver@entry=0x558e64866d20, e=e@entry=0x7f7344013970) at kernel/qapplication.cpp:4351 #13 0x7f736967d54a in KApplication::notify(QObject*, QEvent*) (this=0x7ffcabdb6fc0, receiver=0x558e64866d20, event=0x7f7344013970) at ../../kdeui/kernel/kapplication.cpp:311 #14 0x7f73679aa8dd in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffcabdb6fc0, receiver=receiver@entry=0x558e64866d20, event=event@entry=0x7f7344013970) at kernel/qcoreapplication.cpp:955 #15 0x7f73679adef6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x7f7344013970, receiver=0x558e64866d20) at kernel/qcoreapplication.h:231 #16 0x7f73679adef6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x558e6459cf50) at kernel/qcoreapplication.cpp:1579 #17 0x7f73679ae1d3 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1472 #18 0x7f73679dad1e in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) () at kernel/qcoreapplication.h:236 #19 0x7f73679dad1e in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x558e645caf70) at kernel/qeventdispatcher_glib.cpp:300 #20 0x7f7362399e3a in g_main_context_dispatch (context=0x558e645e14f0) at gmain.c:3154 #21 0x7f7362399e3a in g_main_context_dispatch (context=context@entry=0x558e645e14f0) at gmain.c:3769 #22 0x7f736239a1d0 in g_main_context_iterate (context=context@entry=0x558e645e14f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3840 #23 0x7f736239a27c in g_main_context_iteration (context=0x558e645e14f0, may_block=may_block@entry=1) at gmain.c:3901 #24 0x7f73679dae8e in QEventDispatcherGlib::processEvents(QFlags) (this=0x558e6459e820, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #25 0x7f736899a3e6 in QGuiEventDispatcherGlib::processEvents(QFlags) (this=, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #26 0x7f73679a9151 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7ffcabdb6010, flags=...) at kernel/qeventloop.cpp:149 #27 0x7f73679a94c5 in QEventLoop::exec(QFlags) (this=0x7ffcabdb6010, flags=...) at kernel/qeventloop.cpp:204 #28 0x7f7349845baf in Okular::Document::closeDocument() () at /lib64/libokularcore.so.6 #29 0x7f7349b1f324 in Okular::Part::closeUrl(bool) () at /usr/lib64/kde4/okularpart.so #30 0x7f7349b1fc3a in Okular::Part::~Part() () at /usr/lib64/kde4/okularpart.so #31 0x7f7349b1fc99 in Okular::Part::~Part() () at /usr/lib64/kde4/okularpart.so #32 0x7f736a56f239 in KParts::Part::slotWidgetDestroyed() (this=0x558e6504f110) at ..
[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 Thomas Lübking changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #5 from Thomas Lübking --- > unredirectFullscreen: false Nope. btw, please leave the bug state as it is - whether the bug is in the nvidia blob or QtQuick - it's not in the aurorae engine (or any kwin) As mentioned, resort to the breeze decoration to prevent running into this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342326] window contents freeze
https://bugs.kde.org/show_bug.cgi?id=342326 --- Comment #30 from Thomas Lübking --- It seems the southern islands chips do Xv via GLAMOR, ie. OpenGL... http://xorg.freedesktop.org/wiki/RadeonFeature/ So this seems strictly related to redirected GL clients. Did you try downforcing buffer_age support? export KWIN_USE_BUFFER_AGE=0; kwin_x11 --replace & (I do not assume this to be the cause if it's related to some windows only) Can you please attach /var/log/Xorg.0.log and - if present - ~/.drirc? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 superrobowiz...@gmail.com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|UPSTREAM|--- --- Comment #4 from superrobowiz...@gmail.com --- FYI I'm using a GTX 960. Output of "qdbus org.kde.KWin /KWin supportInformation": https://paste.kde.org/pfa68qbgi -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 351693] Screen brightness is not restored after screen unlock (idle time)
https://bugs.kde.org/show_bug.cgi?id=351693 Alejandro Villar changed: What|Removed |Added CC||alx5...@alx5000.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 352497] laptop back light not coming back on after long period of lcd being in dpms power save mode.
https://bugs.kde.org/show_bug.cgi?id=352497 Alejandro Villar changed: What|Removed |Added CC||alx5...@alx5000.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357621] Screen cannot be turned on after it has been set to "energy saving" (goes off)
https://bugs.kde.org/show_bug.cgi?id=357621 Alejandro Villar changed: What|Removed |Added CC||alx5...@alx5000.net -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 358507] Crash on document close
https://bugs.kde.org/show_bug.cgi?id=358507 Camilla Boemann changed: What|Removed |Added Resolution|--- |WORKSFORME CC||c...@boemann.dk Status|UNCONFIRMED |RESOLVED --- Comment #1 from Camilla Boemann --- This bug is already fixed - please upgrade to a newer version -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358232] When System Tray is restarted after a crash formerly opened konsole windows cannot be accessed anymore
https://bugs.kde.org/show_bug.cgi?id=358232 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- What do you mean by "System Tray" in your posts? How do you get Konsole in there? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358232] When System Tray is restarted after a crash formerly opened konsole windows cannot be accessed anymore
https://bugs.kde.org/show_bug.cgi?id=358232 Maciej Sitarz changed: What|Removed |Added CC||macieksit...@wp.pl --- Comment #1 from Maciej Sitarz --- It seems I have encountered the same problem. When using multiscreen konsole windows seem to dissapear but they are still running. Unfortunately I couldn't find any way to reach those konsole windows. Distribution: Arch Linux KDE version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 344328] krunner is not visible when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=344328 Maciej Sitarz changed: What|Removed |Added CC||macieksit...@wp.pl --- Comment #17 from Maciej Sitarz --- I confirm this bug is still present on version 15.12.1 on Arch Linux. Also the workaround from micuu from comment #5 works. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358492] Quick Open: clicking on filename in the suggestion list doesn't work
https://bugs.kde.org/show_bug.cgi?id=358492 Kevin Funk changed: What|Removed |Added Keywords||regression, release_blocker -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358499] Popups like "Problem in Semantic Analysis" doesn't disappear when it should
https://bugs.kde.org/show_bug.cgi?id=358499 Kevin Funk changed: What|Removed |Added Target Milestone|--- |5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358499] Popups like "Problem in Semantic Analysis" doesn't disappear when it should
https://bugs.kde.org/show_bug.cgi?id=358499 Kevin Funk changed: What|Removed |Added Keywords||release_blocker -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358506] Fix-it hint for missing include should suggest QCamelCase include
https://bugs.kde.org/show_bug.cgi?id=358506 Kevin Funk changed: What|Removed |Added CC||kf...@kde.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Component|general |Language Support: CPP ||(Clang-based) --- Comment #1 from Kevin Funk --- Regarding the duplication of GUIs: You're using kdevelop from master, right? We have a few "bad commits" in there which change the way fixits are handled. We've reverted them in the 5.0 branch, but didn't do so in master yet. Sorry for this. Regarding KDevelop not suggesting : That's a problem with the developer-build of Qt indeed. Right now we don't propose headers which just include other headers. (In a developer build, the QBuffer header just includes qbuffer.h, that's all it does). As far as I remember this rule is here to be able to only propose include files which actually contain the declaration you're looking for (IOW: KDevelop knows the QBuffer decl is part of qbuffer.h, but not , thus doesn't propose the latter). We should probably ignore that rule specifically for Qt developer-builds, in some way... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 --- Comment #35 from AJslye --- Here is what I get in a running session launching from konsole: sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze [17:10:52.221] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop" [17:10:52.221] (EE) GREETER: Socket error: "QLocalSocket::connectToServer: Invalid name" [17:10:52.852] (II) GREETER: Adding view for "LVDS1" QRect(0,0 1600x900) [17:10:59.309] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop" [17:10:59.310] (WW) GREETER: QIODevice::write (QLocalSocket): device not open -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 358507] New: Crash on document close
https://bugs.kde.org/show_bug.cgi?id=358507 Bug ID: 358507 Summary: Crash on document close Product: calligrawords Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: xav...@online.fr Application: calligrawords (2.8.7) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.1.15-desktop-2.mga5 i686 Distribution: "Mageia 5" -- Information about the crash: - What I was doing when the application crashed: Each time i am closing a document. If the document is not saved then i am prompted to decide if i want to or not. Then i save and when i close it, the application crash. If i just close without saving, it crashes too. If i manage two document at the sametime, it is more serious because if i choose to close the application and none of the documents are saved, then, the first one will get the prompt to decide whether i want to save it, and after the application crashes, without prompting for the second document. So it is mandatory to save each document before to close the application. The crash can be reproduced every time. -- Backtrace: Application: Calligra Words (calligrawords), signal: Segmentation fault Using host libthread_db library "/lib/i686/libthread_db.so.1". [Current thread is 1 (Thread 0xb4ff1740 (LWP 20735))] Thread 2 (Thread 0xaabf5b40 (LWP 20988)): #0 0xb7703bc0 in __kernel_vsyscall () #1 0xb5db238b in poll () from /lib/i686/libc.so.6 #2 0xb5721c30 in g_poll () from /lib/libglib-2.0.so.0 #3 0xb5712e14 in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0 #4 0xb5712f56 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0xb6c1dca4 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/libQtCore.so.4 #6 0xb6bec883 in QEventLoop::processEvents(QFlags) () from /lib/libQtCore.so.4 #7 0xb6becbbe in QEventLoop::exec(QFlags) () from /lib/libQtCore.so.4 #8 0xb6ad9760 in QThread::exec() () from /lib/libQtCore.so.4 #9 0xb6bcd48b in QInotifyFileSystemWatcherEngine::run() () from /lib/libQtCore.so.4 #10 0xb6adc253 in QThreadPrivate::start(void*) () from /lib/libQtCore.so.4 #11 0xb6a5f386 in start_thread () from /lib/i686/libpthread.so.0 #12 0xb5dbf45e in clone () from /lib/i686/libc.so.6 Thread 1 (Thread 0xb4ff1740 (LWP 20735)): [KCrash Handler] #6 0xae79cc0c in QHash::duplicateNode(QHashData::Node*, void*) () from /lib/libkotext.so.13 #7 0xb6af9247 in QHashData::detach_helper2(void (*)(QHashData::Node*, void*), void (*)(QHashData::Node*), int, int) () from /lib/libQtCore.so.4 #8 0xae79d2ef in QHash::detach_helper() () from /lib/libkotext.so.13 #9 0xae79d358 in QHash::remove(int const&) () from /lib/libkotext.so.13 #10 0xae79bbff in KoInlineTextObjectManager::removeInlineObject(KoInlineObject*) () from /lib/libkotext.so.13 #11 0xae7a1443 in KoInlineObject::~KoInlineObject() () from /lib/libkotext.so.13 #12 0xae7a1cf4 in KoVariable::~KoVariable() () from /lib/libkotext.so.13 #13 0xab8afb5c in DateVariable::~DateVariable() () from /usr/lib/kde4/calligra_textinlineobject_variables.so #14 0xab8afb8a in DateVariable::~DateVariable() () from /usr/lib/kde4/calligra_textinlineobject_variables.so #15 0xb6c010c4 in qDeleteInEventHandler(QObject*) () from /lib/libQtCore.so.4 #16 0xb6c07599 in QObject::event(QEvent*) () from /lib/libQtCore.so.4 #17 0xb60bb53a in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/libQtGui.so.4 #18 0xb60c1f23 in QApplication::notify(QObject*, QEvent*) () from /lib/libQtGui.so.4 #19 0xae9e8963 in KoApplication::notify(QObject*, QEvent*) () from /lib/libkomain.so.13 #20 0xb6beddfc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib/libQtCore.so.4 #21 0xb6bf1094 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/libQtCore.so.4 #22 0xb6bf1605 in QCoreApplication::sendPostedEvents(QObject*, int) () from /lib/libQtCore.so.4 #23 0xb6c1db21 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib/libQtCore.so.4 #24 0xb5712b74 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #25 0xb5712e89 in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0 #26 0xb5712f56 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #27 0xb6c1dc83 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/libQtCore.so.4 #28 0xb6167e79 in QGuiEventDispatcherGlib::processEvents(QFlags) () from /lib/libQtGui.so.4 #29 0xb6bec883 in QEventLoop::processEvents(QFlags) () from /lib/libQtCore.so.4 #30 0xb6becbbe in QEventLoop::exec(QFlags) () from /lib/libQtCore.so.4 #31 0xb6bf259b in QCoreApplication::exec() () from /lib/libQtCore.so.4 #32 0xb60b9774 in QApplication::exec() () from /lib/libQtGui.so.4 #33 0xb4deb9bd in kdemain () from /usr/lib/libkdeinit4_calligrawords.so #34 0x0804ef22 in
[kmahjongg] [Bug 358496] KMahjongg with "explosion" board layout contains unresponsive tiles with vertical edge exposed
https://bugs.kde.org/show_bug.cgi?id=358496 Ian Wadham changed: What|Removed |Added CC||iandw...@gmail.com Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Ian Wadham --- I also have seen this happen with the Explosion layout. The problem appears to be that the Explosion layout has a very large number of tiles and often fails to generate a puzzle. Normally this should leave you with an empty background and a message in the status bar. Then you can try again --- or try another layout. If puzzle generation fails for Explosion when you are in the Settings dialog for Board Layout, you get an empty background in the layout Preview widget. If you then click "OK", you get a garbage puzzle (not a proper Explosion layout, nor an empty background) and it has the problems you report. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358506] New: Fix-it hint for missing include should suggest QCamelCase include
https://bugs.kde.org/show_bug.cgi?id=358506 Bug ID: 358506 Summary: Fix-it hint for missing include should suggest QCamelCase include Product: kdevelop Version: 4.90.91 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: fa...@kde.org The fix-it hint in case of missing #include for e.g. QBuffer should suggest , not just and <../src/corelib/io/qbuffer.h> Reproducible: Always Steps to Reproduce: 1. Configure Qt with -developer-build (I don't know if it works on an installed Qt) 2. Open kio/autotests/clipboardupdatertest.cpp 3. In initTestCase() type QBuffer buffer; Actual Results: The fix-it hints (both the ones on top and the redundant ones in the "Problem in semantic analysis" button (why the duplication of GUI?) offer only and <../src/corelib/io/qbuffer.h> Expected Results: I would expect only one GUI for fix-it hints (right now it's a bit of a mess, it seems quite unreliable when either one is going to pop up), but mostly this bug is that I would expect as a suggested include, as recommended by the Qt documentation (and as QtCreator does). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356315] 15.13 git master: support split view in project monitor similar to split view in clip monitor
https://bugs.kde.org/show_bug.cgi?id=356315 --- Comment #2 from wegwerf-1-...@gmx.de --- An implementation hurdle may be that split view in project monitor needs two rendering flows: one without any effects, and the one with all effects. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358371] Forms in the document (see URL) are displayed with black background, instead of white.
https://bugs.kde.org/show_bug.cgi?id=358371 --- Comment #9 from wgzimmer-zu...@gmx.ch --- (In reply to Jonathan Verner from comment #8) > > Now that you mention it, I just checked with evince and have the same > > troubles there. Should I maybe file this as an XFCE bug? > > > > I appear to have poppler library version 0.30.0 > > > > $ pdftops -v > > pdftops version 0.30.0 > > Copyright 2005-2015 The Poppler Developers - http://poppler.freedesktop.org > > Copyright 1996-2011 Glyph & Cog, LLC > > I don't think it has anything to do with the desktop environment. The fact > that evince has > the same behaviour indicates it might be a bug in poppler (the library both > evince and okular, afaik, use to render pdfs). However, since Adobe Reader > here also has some trouble with the forms, it might also just be that the > pdf is corrupted. I see, thanks for the explanation! Under Windows 7, my Adobe Reader displays the file just fine. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356315] 15.13 git master: support split view in project monitor similar to split view in clip monitor
https://bugs.kde.org/show_bug.cgi?id=356315 wegwerf-1-...@gmx.de changed: What|Removed |Added Summary|15.13 git master: project |15.13 git master: support |monitor has no split view |split view in project |icon, while clip monitor|monitor similar to split |has |view in clip monitor -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356315] 15.13 git master: project monitor has no split view icon, while clip monitor has
https://bugs.kde.org/show_bug.cgi?id=356315 --- Comment #1 from wegwerf-1-...@gmx.de --- This bug is related to https://bugs.kde.org/show_bug.cgi?id=356314, yet not the same. As "split view" in project monitor has been renamed to "multitrack view", this should get a different icon anyway. I'm renaming this bug report to clearify the situation: please provide also a split view in the project monitor in the same way the clip monitor works: showing both side-by-side the rendered output without any effect as well as with all effects applied. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354854] Signals and slots functions are not colorized inside of connect/disconnect macro
https://bugs.kde.org/show_bug.cgi?id=354854 --- Comment #6 from Milian Wolff --- To report uses inside SIGNAL()/SLOT() macros, we have multiple options: - rewrite uses of qFlagLocation based on the string literal argument it gets passed: CallExpr (103) | type: "const char *" (101) | display: "qFlagLocation" | loc: test.cpp@[(17,5),(17,23)] | isUse UnexposedExpr (100) | type: "const char *(*)(const char *)" (101) | display: "qFlagLocation" | loc: test.cpp@[(17,5),(17,23)] DeclRefExpr (101) | type: "const char *(const char *)" (111) | display: "qFlagLocation" | loc: test.cpp@[(17,5),(17,23)] | isUse UnexposedExpr (100) | type: "const char *" (101) | loc: test.cpp@[(17,5),(17,23)] StringLiteral (109) | type: "const char [24]" (112) | canonical type: "char const[24]" (112) | display: ""2mySignal()\000test.cpp:17"" | loc: test.cpp@[(17,5),(17,23)] - rewrite uses of the macros themselves, assuming we get access to its argument - we could also overwrite the macros as needed using our new qobjectdefs.h shim. The oldcpp plugin has some logic for finding the corresponding signal/slot from a normalized signature afaik, which we can revive for that purpose. Once that is done we can look at the nice-to-have things: For Q_PROPERTY we can leverage the static assert trick that Olivier found and documented here: https://woboq.com/blog/moc-with-clang.html This would then be followed by a parsing of the string literal and extracting the getter, setter and notify signal and reporting uses for them. For Q_PRIVATE_SLOT we could use a custom macro with a special marker attribute. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358449] 15.13 git master: transition list not properly reset when clearing filter input field
https://bugs.kde.org/show_bug.cgi?id=358449 --- Comment #3 from wegwerf-1-...@gmx.de --- Still persisting with recent git pull; make clean; cmake; make cycle. Totally strange. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358426] 15.13 git master: cannot change zoom of monitors; monitor does not properly resize in free mode
https://bugs.kde.org/show_bug.cgi?id=358426 wegwerf-1-...@gmx.de changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358328] Java application systray icon: No context menu
https://bugs.kde.org/show_bug.cgi?id=358328 Joerg Mensmann changed: What|Removed |Added CC||bugs-...@bitplanet.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342326] window contents freeze
https://bugs.kde.org/show_bug.cgi?id=342326 --- Comment #29 from Bernd Steinhauser --- (In reply to Bernd Steinhauser from comment #28) > (In reply to Thomas Lübking from comment #26) > > vdpau specific: does it > > a) start to update when you suspend the compositor > > b) still update when you resume the compositor afterwards? > > Not sure if that matters, but for xv video output, both a) and b) can be > answered with yes. Trying with vdpau again, now. Ok, so I'm now pretty sure, that it doesn't with vdpau. Why? I had two mpv running, one with --vo=vdpau and one with --vo=xv. The latter is now frozen, the former is still running fine. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358255] Konsole stuck on blank window
https://bugs.kde.org/show_bug.cgi?id=358255 Freddy Rietdijk changed: What|Removed |Added CC||fr...@fridh.nl --- Comment #1 from Freddy Rietdijk --- I have the same issue with Konsole, Dolphin and Kate on NixOS. The applications are version 15.12.1, frameworks is 5.18.0, Qt5 5.5.1. My integrated graphics card is Intel® HD Graphics 4000. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 --- Comment #22 from Christophe Giboudeaux --- as I can't reproduce anymore, I'm wondering : do you restore the previous session when you log in ? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 341884] dozens of duplicate mails in ~/.local/share/akonadi/file_db_data
https://bugs.kde.org/show_bug.cgi?id=341884 Daniel Vrátil changed: What|Removed |Added CC||jprofeso...@o2.pl --- Comment #15 from Daniel Vrátil --- *** Bug 344937 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344937] Akonadi keeps multiple revisions of the same message in .local/share/akonadi/file_db_data
https://bugs.kde.org/show_bug.cgi?id=344937 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 341884 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358505] New: If I try to use any tool, the tool won't write anything, even after many restarts to the program.
https://bugs.kde.org/show_bug.cgi?id=358505 Bug ID: 358505 Summary: If I try to use any tool, the tool won't write anything, even after many restarts to the program. Product: krita Version: 2.9.10 Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: dollarhide200...@aol.com Tools will not write anything, but I can undo things like it did write something Reproducible: Sometimes It does it at random. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344937] Akonadi keeps multiple revisions of the same message in .local/share/akonadi/file_db_data
https://bugs.kde.org/show_bug.cgi?id=344937 Milian Wolff changed: What|Removed |Added CC||m...@milianw.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358371] Forms in the document (see URL) are displayed with black background, instead of white.
https://bugs.kde.org/show_bug.cgi?id=358371 --- Comment #8 from Jonathan Verner --- > Now that you mention it, I just checked with evince and have the same > troubles there. Should I maybe file this as an XFCE bug? > > I appear to have poppler library version 0.30.0 > > $ pdftops -v > pdftops version 0.30.0 > Copyright 2005-2015 The Poppler Developers - http://poppler.freedesktop.org > Copyright 1996-2011 Glyph & Cog, LLC I don't think it has anything to do with the desktop environment. The fact that evince has the same behaviour indicates it might be a bug in poppler (the library both evince and okular, afaik, use to render pdfs). However, since Adobe Reader here also has some trouble with the forms, it might also just be that the pdf is corrupted. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358504] New: Possibility to show duration of selected zone
https://bugs.kde.org/show_bug.cgi?id=358504 Bug ID: 358504 Summary: Possibility to show duration of selected zone Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: s...@cameralibre.cc It would be very useful if there was a timecode box somewhere in the GUI (or an option to reveal one) which showed the duration of the selected zone between In and Out points. I have to calculate this duration manually whenever I'm trying to keep track of certain sections of an edit - eg. to compare the lengths of particular scenes, to see how much time I am giving to particular subjects. This is particularly frustrating when working with a Producer, when they ask me how long a particular section of the timeline is - in Final Cut or Avid I could have a quick answer, but with Kdenlive I suddenly show everybody in the room how bad at mathematics I am: "um... hang on, I will tell you soon... just working it out... ok, um, 14 minutes 21 seconds 7 frames minus, ah, 9 minutes, 32 seconds, and 17 frames... errr..?" Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 358502] Random crash, WINE related?
https://bugs.kde.org/show_bug.cgi?id=358502 David Edmundson changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|m...@vhanda.in CC||pinak.ah...@gmail.com Version|5.5.3 |unspecified Component|general |General Product|plasmashell |Baloo Target Milestone|1.0 |--- -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358503] New: some timecode is not displayed in monospace font
https://bugs.kde.org/show_bug.cgi?id=358503 Bug ID: 358503 Summary: some timecode is not displayed in monospace font Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: s...@cameralibre.cc (at least in my install) the timecode displayed under the Clip Monitor and Project Monitor is in a proportional width font, meaning playback causes a slight jitter like that seen with https://bugs.kde.org/show_bug.cgi?id=356661 could this be changed to a monospace font, like the status bar? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358502] New: Random crash, WINE related?
https://bugs.kde.org/show_bug.cgi?id=358502 Bug ID: 358502 Summary: Random crash, WINE related? Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: p...@alicious.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Loading Wine desktop from an entry in the Kickoff menu. This may be unrelated. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5880ddd800 (LWP 1671))] Thread 17 (Thread 0x7f586c126700 (LWP 1681)): #0 0x7f587b4728dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f587f590bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f587f59274f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f586e2987e9 in QXcbEventReader::run (this=0x1be3340) at qxcbconnection.cpp:1229 #4 0x7f587bb74a6e in QThreadPrivate::start (arg=0x1be3340) at thread/qthread_unix.cpp:331 #5 0x7f587ac4e6aa in start_thread (arg=0x7f586c126700) at pthread_create.c:333 #6 0x7f587b47deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f58698be700 (LWP 1732)): #0 0x7f58781f5884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f58781b11e1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f58781b12fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f587bdac50b in QEventDispatcherGlib::processEvents (this=0x7f585c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f587bd5350a in QEventLoop::exec (this=this@entry=0x7f58698bdda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f587bb6fac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f587e442c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f587bb74a6e in QThreadPrivate::start (arg=0x1cc7970) at thread/qthread_unix.cpp:331 #8 0x7f587ac4e6aa in start_thread (arg=0x7f58698be700) at pthread_create.c:333 #9 0x7f587b47deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f5861366700 (LWP 1733)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f58628714da in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7f5862870c17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7f587ac4e6aa in start_thread (arg=0x7f5861366700) at pthread_create.c:333 #4 0x7f587b47deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f5856a3e700 (LWP 1734)): #0 0x7f58781f5884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f58781b0c19 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f58781b1190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f58781b12fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f587bdac50b in QEventDispatcherGlib::processEvents (this=0x7f5858c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f587bd5350a in QEventLoop::exec (this=this@entry=0x7f5856a3dda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f587bb6fac4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f587e442c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f587bb74a6e in QThreadPrivate::start (arg=0x1ddc7e0) at thread/qthread_unix.cpp:331 #9 0x7f587ac4e6aa in start_thread (arg=0x7f5856a3e700) at pthread_create.c:333 #10 0x7f587b47deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f5854bee700 (LWP 1739)): #0 0x7f58781f5884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f58781b0770 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f58781b111b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f58781b12fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f587bdac50b in QEventDispatcherGlib::processEvents (this=0x7f58480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f587bd5350a in QEventLoop::exec (this=this@entry=0x7f5854bedda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f587bb6fac4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f587e442c35 in ?? () f
[kdevelop] [Bug 358499] Popups like "Problem in Semantic Analysis" doesn't disappear when it should
https://bugs.kde.org/show_bug.cgi?id=358499 Milian Wolff changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Milian Wolff --- I can't trigger the "it doesn't hide on focus loss" issue, for me opening e.g. yakuake (f12) or alt-tabbing out of the window works. Interestingly, it doesn't hide when I switch to another editor view via ctrl + tab ;-) So there's certainly something broken in that regard. I also agree that it should get hidden on escape. Hiding it immediately when typing should also happen, this is btw. already the case for "normal" popups we use to show non-problematic code browsing information. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358493] Create From Template: preview doesn't get cleared between templates
https://bugs.kde.org/show_bug.cgi?id=358493 Milian Wolff changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdev ||platform/fdcefb278d59b1816f ||6158f92a7581480fa4402d Status|CONFIRMED |RESOLVED --- Comment #1 from Milian Wolff --- Git commit fdcefb278d59b1816f6158f92a7581480fa4402d by Milian Wolff. Committed on 24/01/2016 at 20:13. Pushed by mwolff into branch '5.0'. Render file template previews into correct temporary folder. Yet another KUrl porting bug... For QUrl::resolved to work properly it is crucial that the path of the QUrl ends with a /, so add that manually. M +1-1plugins/filetemplates/templateselectionpage.cpp http://commits.kde.org/kdevplatform/fdcefb278d59b1816f6158f92a7581480fa4402d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 344843] Add hard-edged selection mode
https://bugs.kde.org/show_bug.cgi?id=344843 --- Comment #4 from kali...@wp.pl --- That works nice with all but "select opaque" - there's no possibility to disable it there, since it's automatic selection. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 358470] Not reconnecting to WiFi - Waiting authorization
https://bugs.kde.org/show_bug.cgi?id=358470 --- Comment #3 from Jacobtey --- What should I do? What steps? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358501] New: New Message shortcut not working correctly
https://bugs.kde.org/show_bug.cgi?id=358501 Bug ID: 358501 Summary: New Message shortcut not working correctly Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: rew...@thestrayworld.com After successfully moving my KMail4 to KMail5, I discovered the Ctrl+N shortcut threw up an error. "The key sequence 'Ctrl+N' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered." The shortcut settings had not been changed from the default setting and no other application was in conflict with it. After assigning nothing to the custom shortcut to New Message, the actual shortcut for New Message worked again. Attempts to reassign the shortcut back to the default setting threw up this error: "The 'Ctrl+N' key combination is already used by the New Message... action. Please select a different one." It is possible that remnants of the shortcuts in KMail4 are still being run, hence resulting in a conflict. Reproducible: Always Steps to Reproduce: 1. Tries to use (default setting) Ctrl+N in KMail5 after upgrading from KMail4 Actual Results: Error message given. Expected Results: New message window should have launched. The computer is running openSUSE Tumbleweed with subscriptions to the Frameworks, Applications, and Extras repositories taking priority over stock repositories. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 358470] Not reconnecting to WiFi - Waiting authorization
https://bugs.kde.org/show_bug.cgi?id=358470 --- Comment #1 from Jan Grulich --- *** Bug 358466 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 358470] Not reconnecting to WiFi - Waiting authorization
https://bugs.kde.org/show_bug.cgi?id=358470 --- Comment #2 from Jan Grulich --- Could you please provide NetworkManager log? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 358466] Can't authorize Wifi
https://bugs.kde.org/show_bug.cgi?id=358466 Jan Grulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 358470 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356314] 15.13 git master: split view garbles display/not working in project monitor
https://bugs.kde.org/show_bug.cgi?id=356314 --- Comment #7 from wegwerf-1-...@gmx.de --- Jean-Baptiste, on another note: shall I draw up a new icon for multi-view mode? My idea is to take the existing single window metaphor, but with dotted lines that divide this window into four quadrants. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356314] 15.13 git master: split view garbles display/not working in project monitor
https://bugs.kde.org/show_bug.cgi?id=356314 --- Comment #6 from wegwerf-1-...@gmx.de --- A note on the existing multitrack view: I'm constantly working with between 5 to 8 tracks in my projects. In this setup I use tracks for dedicated purposes. Most "live" clips are on bottom tracks, while upper tracks contain different overlays, such a paper background getting multiplied into a clip, or a title bar, et cetera. In consequence, a four corner display typically doesn't work for me. It would be great if the multitrack view could be developed further. 1. For instance, what about controlling the tracks to monitor in multitrack view using a new "view" toggle in the track headers? Such as an eye in a window as an indication? This way, the editor has close control over the tracks getting monitored. 2. What about modifying multi track view to have three states? a. multi-track view off; b. 2x2 multi-track view; c. 3x3 multi-track view? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 333451] Krita cannot import SVG as editable vectors
https://bugs.kde.org/show_bug.cgi?id=333451 --- Comment #9 from Boudewijn Rempt --- We've been triaging all wishes today, and yours was classified as part of the next big kickstarter topics: improving vector tools. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358500] New: Krunner does not index mkv and flac files
https://bugs.kde.org/show_bug.cgi?id=358500 Bug ID: 358500 Summary: Krunner does not index mkv and flac files Product: krunner Version: 5.5.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: filesearch Assignee: m...@vhanda.in Reporter: akhil...@openmailbox.org Krunner says it indexes videos but none of my mkv files seem to be indexed. However, recently used mkv files do show up with the "recents" search feature of krunner enabled. Reproducible: Always Steps to Reproduce: 1. Have a mkv file 2. Let krunner/baloo index 3. Search wont show any mkv file Actual Results: No search results Expected Results: myvideo.mkv -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358499] Popups like "Problem in Semantic Analysis" doesn't disappear when it should
https://bugs.kde.org/show_bug.cgi?id=358499 --- Comment #1 from David Faure --- Also, it doesn't go away on Key_Escape. Shouldn't that hide it too? And if I type another letter (e.g. Key_End followed by 'o' to start writing the rest of "invokeMethod"), shouldn't that hide the semantic analysis popup? Go away, I'm fixing it. Otherwise I end up with that popup plus the completion popup on top of each other, it's just too much. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358499] New: Popups like "Problem in Semantic Analysis" doesn't disappear when it should
https://bugs.kde.org/show_bug.cgi?id=358499 Bug ID: 358499 Summary: Popups like "Problem in Semantic Analysis" doesn't disappear when it should Product: kdevelop Version: 4.90.91 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: fa...@kde.org That popup remains visible when switching to another virtual desktop using a key shortcut (in my case Alt+PageUp). Reproducible: Always Steps to Reproduce: 1. Type QMetaObject::inv 2. Wait until QMetaObject is underlined, click into it 3. The popup "Problem in Semantic Analysis, No type named inv in QMetaObject" appears 4. I press the shortcut to switch desktops (Alt+PageUp), the popup stays up. With Ctrl+F1 it works, so it seems "release Ctrl" is hardcoded as a way to hide the popup (although Alt+Tab works too). I think focus-out should hide it too. -- You are receiving this mail because: You are watching all bug changes.
