[kwin] [Bug 371399] [Wayland] Firefox either hangs my desktop or crashes the session.
https://bugs.kde.org/show_bug.cgi?id=371399 Tony changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #2 from Tony --- ..Yea is not firefox, i reset my desktop configs and now it hangs soon after ksplash logo ends. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371399] [Wayland] Firefox either hangs my desktop or crashes the session.
https://bugs.kde.org/show_bug.cgi?id=371399 Martin Gräßlin changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #3 from Martin Gräßlin --- We need the backtrace, without we cannot do much :-( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371252] Master-68e89f4 Immediate crash after startup. Movit disabled.
https://bugs.kde.org/show_bug.cgi?id=371252 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit 880344c32093885b1f98f418bedf00bcf0bc7070 by Jean-Baptiste Mardelle. Committed on 21/10/2016 at 07:12. Pushed by mardelle into branch 'master'. Revert recent commit causing startup crashes M +1-1src/monitor/glwidget.cpp http://commits.kde.org/kdenlive/880344c32093885b1f98f418bedf00bcf0bc7070 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 346271] kdenlive crashes when changing clip-text colour
https://bugs.kde.org/show_bug.cgi?id=346271 Ibrahim K changed: What|Removed |Added CC||em1...@hotmail.com --- Comment #9 from Ibrahim K --- I am facing the same issue with version 16.08.2 on ArchLinux! I never faced it with the previous version. Hope a soon fix :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 346271] kdenlive crashes when changing clip-text colour
https://bugs.kde.org/show_bug.cgi?id=346271 Germano Massullo changed: What|Removed |Added Version|unspecified |16.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 346271] kdenlive crashes when changing clip-text colour
https://bugs.kde.org/show_bug.cgi?id=346271 Germano Massullo changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WONTFIX |--- -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 166249] Show unread articles only
https://bugs.kde.org/show_bug.cgi?id=166249 HP changed: What|Removed |Added CC||h...@j0t.de --- Comment #7 from HP --- I was using Liferea http://lzone.de/liferea/ the recent years and it has this feature to only display unread articles in a *folder*. Very handy. So I have all my feeds grouped and just clicking the folder only shows me the unread ones. And the guys are right - for feeds with quite an amount of new articles there are (for what reason ever) new articles popping up up inbetween the timeline. Maybe someone created a publish date for the past or he/she started writing that article hours earlier. You never know. So another option would be to have the unread articles on top. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 346271] kdenlive crashes when changing clip-text colour
https://bugs.kde.org/show_bug.cgi?id=346271 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #10 from Wegwerf --- Ibrahim, please post a useful crash backtrace, but please only the relevant crash thread. As I don't see crashes on my Kubuntu 16.04LTS this looks suspiciously like a distro packaging error. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371400] New: Umbrello does not import c++ datatype references
https://bugs.kde.org/show_bug.cgi?id=371400
Bug ID: 371400
Summary: Umbrello does not import c++ datatype references
Product: umbrello
Version: 2.18.3 (KDE Applications 15.12.3)
Platform: Other
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: umbrello-de...@kde.org
Reporter: ralf.habac...@freenet.de
Importing c++ code having a datatype reference e.g.
namespace ANameSpace {
typedef int& someType;
}
fails to import the reference.
Reproducible: Always
Steps to Reproduce:
1. start umbrello
2. import test case
Actual Results:
The imported datatype references 'int'.
Expected Results:
The imported datatype should reference 'int&'.
--
You are receiving this mail because:
You are watching all bug changes.
[umbrello] [Bug 371400] Umbrello does not import c++ datatype references
https://bugs.kde.org/show_bug.cgi?id=371400 Ralf Habacker changed: What|Removed |Added Blocks||371274 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371274] Code generator does not generate typedefs
https://bugs.kde.org/show_bug.cgi?id=371274 Ralf Habacker changed: What|Removed |Added Depends on||371400 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 344809] Gwenview crashes when moving forward to a video, then back
https://bugs.kde.org/show_bug.cgi?id=344809 --- Comment #6 from public+...@enkore.de --- I can confirm that on the machine where it crashes like this the settings is indeed "None" and setting it to something else fixes it. Also on the machines where it doesn't crash the settings was already something else. Thanks for debugging this and finding a viable workaround! :) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371400] Umbrello does not import c++ datatype references
https://bugs.kde.org/show_bug.cgi?id=371400 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||2.20.3 (KDE Applications ||16.08.03) Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/umbr ||ello/371b78c2d2cfffe78a5a94 ||40ef0e56bed3180fa0 --- Comment #1 from Ralf Habacker --- Git commit 371b78c2d2cfffe78a5a9440ef0e56bed3180fa0 by Ralf Habacker. Committed on 21/10/2016 at 07:51. Pushed by habacker into branch 'Applications/16.08'. Fix 'Umbrello does not import c++ datatype references'. FIXED-IN:2.20.3 (KDE Applications 16.08.03) M +1-1umbrello/codeimport/kdevcppparser/cpptree2uml.cpp http://commits.kde.org/umbrello/371b78c2d2cfffe78a5a9440ef0e56bed3180fa0 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371274] Code generator does not generate typedefs
https://bugs.kde.org/show_bug.cgi?id=371274 Bug 371274 depends on bug 371400, which changed state. Bug 371400 Summary: Umbrello does not import c++ datatype references https://bugs.kde.org/show_bug.cgi?id=371400 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371274] Code generator does not generate typedefs
https://bugs.kde.org/show_bug.cgi?id=371274 --- Comment #3 from Ralf Habacker --- Git commit d4f45447822d251e6ff780da47f158c05e74474a by Ralf Habacker. Committed on 21/10/2016 at 07:59. Pushed by habacker into branch 'master'. Write out typedefs located in classes for default code generator. M +24 -0umbrello/codegenerators/cpp/cppwriter.cpp M +1-0umbrello/codegenerators/cpp/cppwriter.h http://commits.kde.org/umbrello/d4f45447822d251e6ff780da47f158c05e74474a --- Comment #2 from Ralf Habacker --- Git commit 828f7dac7316cf8b0b13e290b51fcd114b3e06d1 by Ralf Habacker. Committed on 21/10/2016 at 07:57. Pushed by habacker into branch 'master'. Introduce class UMLDatatype. M +1-0umbrello/CMakeLists.txt M +2-2umbrello/codegenerators/ada/adawriter.cpp M +4-4umbrello/codegenerators/codegenerator.cpp M +1-1umbrello/codegenerators/cpp/cppheadercodedocument.cpp M +1-1umbrello/codegenerators/d/dclassifiercodedocument.cpp M +1-1umbrello/codegenerators/d/dwriter.cpp M +1-1umbrello/codegenerators/idl/idlwriter.cpp M +1-1umbrello/codegenerators/java/javaclassifiercodedocument.cpp M +1-1umbrello/codegenerators/java/javawriter.cpp M +1-1umbrello/codegenerators/pascal/pascalwriter.cpp M +1-1umbrello/codegenerators/perl/perlwriter.cpp M +4-3umbrello/codeimport/import_utils.cpp M +2-1umbrello/codeimport/kdevcppparser/cpptree2uml.cpp M +10 -7umbrello/dialogs/pages/classgeneralpage.cpp M +3-4umbrello/object_factory.cpp M +1-1umbrello/umldoc.cpp M +2-58 umbrello/umlmodel/classifier.cpp M +0-10 umbrello/umlmodel/classifier.h A +101 -0umbrello/umlmodel/datatype.cpp [License: GPL (v2+)] A +45 -0umbrello/umlmodel/datatype.h [License: GPL (v2+)] M +2-0umbrello/umlmodel/umlobject.cpp M +3-0umbrello/umlmodel/umlobject.h M +7-6umbrello/umlscene.cpp http://commits.kde.org/umbrello/828f7dac7316cf8b0b13e290b51fcd114b3e06d1 -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 371331] database calls randomly fail on Windows 10 (postgresql)
https://bugs.kde.org/show_bug.cgi?id=371331 --- Comment #2 from Simeon Kuran --- I thought so... I will upload it to some git repo, but I will need some time! Hopefully I can do it on the weekend... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371401] New: Wrong time display
https://bugs.kde.org/show_bug.cgi?id=371401 Bug ID: 371401 Summary: Wrong time display Product: plasmashell Version: 5.8.2 Platform: Kubuntu Packages URL: http://s020.radikal.ru/i704/1610/c4/954ddf4cc907.png OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: mishans...@mail.ru After upgrading to 5.8.2 broken clock Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 365762] Unable to make snapshot (screenshot) on wayland winodws (kwin_wayland session)
https://bugs.kde.org/show_bug.cgi?id=365762 dino changed: What|Removed |Added CC||dinol...@gmail.com --- Comment #3 from dino --- Atm which alternative to take snapshots under wayland? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370379] When applying a Transform Mask, the original image still appears
https://bugs.kde.org/show_bug.cgi?id=370379 --- Comment #5 from Boudewijn Rempt --- Hum... And that's with the same version of Krita? Could you try the latest beta build -- download.kde.org/unstable/krita/3.0.91 -- that has some fixes for transform masks. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 Konrad Materka changed: What|Removed |Added CC||kmate...@wp.pl -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 André Stein changed: What|Removed |Added CC|andre.stein.1...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw
https://bugs.kde.org/show_bug.cgi?id=371124 --- Comment #5 from Boudewijn Rempt --- Git commit 7c4c67f450d3c7390d65b35ff05d2e0b1e5d48e8 by Boudewijn Rempt. Committed on 21/10/2016 at 08:57. Pushed by rempt into branch 'rempt/impex-refactoring'. Check pointer before dereferencing And remove over-use of auto. This fixes at least one crash as reported in 371124 M +3-3libs/ui/input/kis_input_manager.cpp http://commits.kde.org/krita/7c4c67f450d3c7390d65b35ff05d2e0b1e5d48e8 -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 371402] New: 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number
https://bugs.kde.org/show_bug.cgi?id=371402 Bug ID: 371402 Summary: 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number Product: abakus Version: 0.90 Platform: Other URL: https://wiki.openstack.org/wiki/Out-look_technical_sup port_num-ber_1_855_338_0710_outlook_tech_support_num.b .e.r OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k.h...@gmx.de Reporter: swedrfr...@mail.com 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number ^ 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number 1 855__338__0710 outlook technical support number/outlook tech support number Outlook Customer Service Number and Outlook Customer Support Phone Number ^^^
[kdenlive] [Bug 371404] New: Preview render a zone in timeline: not work correct, maybe too tracks..?
https://bugs.kde.org/show_bug.cgi?id=371404 Bug ID: 371404 Summary: Preview render a zone in timeline: not work correct, maybe too tracks..? Product: kdenlive Version: 16.08.2 Platform: openSUSE RPMs URL: http://sendvid.com/b8mbej0k OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: manuel_songo...@yahoo.it i open topic: https://forum.kde.org/viewtopic.php?f=265&t=136695&p=365953#p365953 there are all information for problem. version is 16.08.2 KDE Frameworks 5.27.0 Qt 5.7.0 (compilato con 5.7.0) Il sistema di finestre xcb Reproducible: Always Steps to Reproduce: see my video recorded, link http://sendvid.com/b8mbej0k from topic, ask to me: "I see frm your video that you have compositing set to "High Quality", try switching it to "None" and see if it helps... " so result: NOTHING HAPPEN, SAME ISSUE.. -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 371331] database calls randomly fail on Windows 10 (postgresql)
https://bugs.kde.org/show_bug.cgi?id=371331 --- Comment #3 from Jarosław Staniek --- Simeon, you can also quickly email me zipped files, no problem. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371403] how change all Icons?
https://bugs.kde.org/show_bug.cgi?id=371403 --- Comment #1 from Ivan Kush --- it's too depressive, when all icons are black -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362459] Dolphin crashes when moving file to trash
https://bugs.kde.org/show_bug.cgi?id=362459 Alivema4ever changed: What|Removed |Added CC||alivema4e...@gmail.com --- Comment #3 from Alivema4ever --- Same here. Moving file to trash causes dolphin to crash, but the file selected is moved to trash. Starting program: /usr/bin/dolphin [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffe0d25700 (LWP 2936)] [New Thread 0x7fffd91d5700 (LWP 2937)] Thread 1 "dolphin" received signal SIGSEGV, Segmentation fault. 0x7197867d in QMimeData::hasUrls() const () from /usr/lib/libQt5Core.so.5 #0 0x7197867d in QMimeData::hasUrls() const () from /usr/lib/libQt5Core.so.5 No symbol table info available. #1 0x7605fdae in ?? () from /usr/lib/libKF5KIOWidgets.so.5 No symbol table info available. #2 0x75874692 in KIO::SimpleJob::slotFinished() () from /usr/lib/libKF5KIOCore.so.5 No symbol table info available. #3 0x75874d01 in ?? () from /usr/lib/libKF5KIOCore.so.5 No symbol table info available. #4 0x7197e659 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #5 0x7584e581 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5 No symbol table info available. #6 0x7584cbb7 in KIO::SlaveInterface::dispatch() () from /usr/lib/libKF5KIOCore.so.5 No symbol table info available. #7 0x75851f21 in KIO::Slave::gotInput() () from /usr/lib/libKF5KIOCore.so.5 No symbol table info available. #8 0x758ee205 in ?? () from /usr/lib/libKF5KIOCore.so.5 No symbol table info available. #9 0x7197e659 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #10 0x757e4b90 in ?? () from /usr/lib/libKF5KIOCore.so.5 No symbol table info available. #11 0x7197f4b9 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #12 0x728bde0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #13 0x728c5581 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #14 0x71952de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #15 0x7195556d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #16 0x719a7303 in ?? () from /usr/lib/libQt5Core.so.5 No symbol table info available. #17 0x7fffeae9e587 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #18 0x7fffeae9e7f0 in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #19 0x7fffeae9e89c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #20 0x719a770f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #21 0x7195123a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #22 0x7195973c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 No symbol table info available. #23 0x77b594f7 in kdemain () from /usr/lib/libkdeinit5_dolphin.so No symbol table info available. #24 0x77779291 in __libc_start_main () from /usr/lib/libc.so.6 No symbol table info available. #25 0x0040065a in _start () No symbol table info available. KF 5.27, plasma 5.8.2, dolphin from kde-applications 16.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371403] New: how change all Icons?
https://bugs.kde.org/show_bug.cgi?id=371403 Bug ID: 371403 Summary: how change all Icons? Product: kdevelop Version: 5.0.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ivan.v.k...@yandex.ru I very like KDevelop 4 icon set Oxygen. How can I change 5 to 4 icon set? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 359178] Kaddressbook does not download new contacts from Google Contacts
https://bugs.kde.org/show_bug.cgi?id=359178 Michal Hlavac changed: What|Removed |Added CC||hla...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 371405] New: [Konqueror Git] Broken right click
https://bugs.kde.org/show_bug.cgi?id=371405 Bug ID: 371405 Summary: [Konqueror Git] Broken right click Product: konqueror Version: Git Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: eseb...@gmail.com One of the newest commits brakes the right click, probably this: https://github.com/KDE/kde-baseapps/commit/06994f8b5405fe8e63f62b0b1f50b49f7ca72d08 Reproducible: Always Steps to Reproduce: 1. open any file 2. right click 3. nothing happens 1. right click any toolbar, location, search etc 2. nothing happens -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 371095] filter to show plasma software only
https://bugs.kde.org/show_bug.cgi?id=371095 --- Comment #2 from Martin Tlustos --- If someone wanted to have only kde software on his system to keep it as smooth and uniform and free from other libraries as possible, it would be nice, I think, because you wouldn't need to check with every promising software whether it's KDE or Gnome or other. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 368454] Easily enable automatic security/all updates
https://bugs.kde.org/show_bug.cgi?id=368454 Ingo Steuwer changed: What|Removed |Added CC||i...@steuwer.de --- Comment #1 from Ingo Steuwer --- Also in my whishlist. As KDE neon by default doesn't even check for new updates one has to initiate that also manually, see also: https://forum.kde.org/viewtopic.php?f=309&t=136620 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 278431] KDirListerCache crash when trashing a file and the trash is empty
https://bugs.kde.org/show_bug.cgi?id=278431 Alivema4ever changed: What|Removed |Added CC||alivema4e...@gmail.com --- Comment #72 from Alivema4ever --- It hasn't been completely fixed yet. Crashes still occur when moving file to trash. #362459 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371406] New: Modifier to constrain mouse pointer to the current desktop
https://bugs.kde.org/show_bug.cgi?id=371406 Bug ID: 371406 Summary: Modifier to constrain mouse pointer to the current desktop Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: pfeif...@kde.org This is probably a more esoteric feature request, so feel free to ignore it :-) The window decorations help with Fitts's law by allowing to activate the right-most (close) button of a maximized window even when the mouse pointer is at the very corner of the display. Unfortunately this works only for the top/right-most monitor in a multi-monitor setup because you cannot "throw" the mouse pointer into another monitor's corner. Unless there would be a modifier to constrain the mouse pointer to the current monitor as long as that key is pressed. E.g. while you hold the Meta or Control key, you could not move the mouse pointer across monitors. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371274] Code generator does not generate typedefs
https://bugs.kde.org/show_bug.cgi?id=371274 Ralf Habacker changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 335111] vlc crashes phonon by mixing qt4 and qt5
https://bugs.kde.org/show_bug.cgi?id=335111 Ben Cooksley changed: What|Removed |Added CC|franklin_mcw...@hotmail.com | --- Comment #82 from Ben Cooksley --- Removing subscriber per abuse report -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371274] Code generator does not generate typedefs
https://bugs.kde.org/show_bug.cgi?id=371274 --- Comment #4 from Ralf Habacker --- With the last commits writing out typedefs located in classes are implemented. Writing out data types defined in a namespace needs a little more work. Umbrello writes out classes into files named according to the exported class. As typedefs in namespaces may be used in more than one class from the related namespace or from classes outside the namespace umbrello requires some hints where to place those typedefs. There are a few variants possible: 1. Generate an extra header file in the namespace containing all related typedefs and include it in all header files generated for this namespace. 2. Extend umbrello to be able to assign UML objects to filenames which is then used by the code generator to place the typedefs in the related header. Code import can also use this feature to generate UML object to filename tracking which is required for round trip engineering. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting
https://bugs.kde.org/show_bug.cgi?id=371284 --- Comment #22 from Martin Gräßlin --- Some investigation results: if one removes the window decoration the problem is not triggered. Krita starts as a normal window and directly maximizes. This might cause a problem with the decoration not having a correct geometry and then accepting events. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 --- Comment #8 from Rajeesh K V --- Is this issue always reproducible? The problem I experience is when waking from sleep, touchpad is disabled (likely a kernel issue). Other than that, touchpad toggle is working as expected. Run the below command before you press touchpad toggle short cut and report the output: dbus-monitor "type='signal',interface='org.kde.kglobalaccel.Component'" If possible, can you revert commit cf0bf81ccd4c7f8afacda7084978af719340a138 (you may need to revert ca23c39229d607fa45a2d862b44233163853739b first) and check if the issue persists? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 365762] Unable to make snapshot (screenshot) on wayland winodws (kwin_wayland session)
https://bugs.kde.org/show_bug.cgi?id=365762 --- Comment #4 from Boudhayan Gupta --- There's no alternatives. Due to Wayland's security model it just doesn't allow applications access to an image of the screen, or of other apps. There's compositor-specific support (such as Gnome-Screenshot working only on Gnome-Shell, Weston-Screenshot working only on Weston and so on). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370379] When applying a Transform Mask, the original image still appears
https://bugs.kde.org/show_bug.cgi?id=370379 --- Comment #6 from silva --- Tried the 3.0.91 and it is solved now! Works great! Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370379] When applying a Transform Mask, the original image still appears
https://bugs.kde.org/show_bug.cgi?id=370379 --- Comment #7 from silva --- And applying a Transform Mask doesn't crash Krita anymore! -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 371407] New: Unable to start KDE Partition Manager
https://bugs.kde.org/show_bug.cgi?id=371407 Bug ID: 371407 Summary: Unable to start KDE Partition Manager Product: partitionmanager Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: palette...@hotmail.com Application: partitionmanager (2.2.1) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-45-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: Starting application and got pass root request. The application had scan my harddrives sda sdb when it reached sdc it crashed.Drive sdc is my memory card reader. The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa673bac900 (LWP 11423))] Thread 5 (Thread 0x7fa661121700 (LWP 11504)): #0 0x7fa67c9ad9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa678450740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa67840ce84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa67840d340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa67840d722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa66202e916 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7fa678433bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fa679c676fa in start_thread (arg=0x7fa661121700) at pthread_create.c:333 #8 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fa661922700 (LWP 11503)): #0 0x7fa67c9b1e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa67840d39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa67840d4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa67840d4e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa678433bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa679c676fa in start_thread (arg=0x7fa661922700) at pthread_create.c:333 #6 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fa66aaca700 (LWP 11425)): #0 0x7fa67c9b1e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa67840d39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa67840d4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa67d2dc23b in QEventDispatcherGlib::processEvents (this=0x7fa6640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa67d286cea in QEventLoop::exec (this=this@entry=0x7fa66aac9c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7fa67d0abfb4 in QThread::exec (this=this@entry=0x7fa67b5c1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x7fa67b54d7a5 in QDBusConnectionManager::run (this=0x7fa67b5c1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #7 0x7fa67d0b0b98 in QThreadPrivate::start (arg=0x7fa67b5c1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #8 0x7fa679c676fa in start_thread (arg=0x7fa66aaca700) at pthread_create.c:333 #9 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa670c8b700 (LWP 11424)): #0 0x7fa67c9b1e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa677f82c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa677f848d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa67360fa39 in QXcbEventReader::run (this=0x1a959c0) at qxcbconnection.cpp:1337 #4 0x7fa67d0b0b98 in QThreadPrivate::start (arg=0x1a959c0) at thread/qthread_unix.cpp:344 #5 0x7fa679c676fa in start_thread (arg=0x7fa670c8b700) at pthread_create.c:333 #6 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa673bac900 (LWP 11423)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:103 #8 QBasicAtomicInteger::load (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:99 #9 QtPrivate::RefCount::ref (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::operator= (this=0x7fa65c04fc78, other=...) at tools/qstrin
[plasmashell] [Bug 371401] Wrong time display
https://bugs.kde.org/show_bug.cgi?id=371401 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- See final comment in linked report. Thanks. *** This bug has been marked as a duplicate of bug 370149 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370149] Digital and Analog Clock display wrong local time (wrong timezone?)
https://bugs.kde.org/show_bug.cgi?id=370149 David Edmundson changed: What|Removed |Added CC||mishans...@mail.ru --- Comment #16 from David Edmundson --- *** Bug 371401 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371127] plasmashell and powerdevil crash on logout/reboot/shutdown
https://bugs.kde.org/show_bug.cgi?id=371127 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from David Edmundson --- Perfect Thanks. This has been reported already and will be fixed soon. Did you say you also had another crash in powerdevil? If so can you redo the kquitapp5 trick to make that crash too. *** This bug has been marked as a duplicate of bug 371215 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371215] Plasma Crashes when trying to end application with kquiapp5
https://bugs.kde.org/show_bug.cgi?id=371215 David Edmundson changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #7 from David Edmundson --- *** Bug 371127 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371398] Graphics glitches out when using firefox.
https://bugs.kde.org/show_bug.cgi?id=371398 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Then that's a firefox problem, or a graphics driver problem. Nothing to do with us. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 371408] New: Application crashes when Mouse leaves Window
https://bugs.kde.org/show_bug.cgi?id=371408 Bug ID: 371408 Summary: Application crashes when Mouse leaves Window Product: QtCurve Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: yyc1...@gmail.com Reporter: jan-pe...@ruehmann.name CC: h...@kde.org everytime qtcurve is active and I start a Application that app is crashing as soon the Mouse Pointer is leaving the Window. This happens only with qtcurve and with every Kind of Theme, Skin or Decoration. I am Using Kubuntu 16.04 LTE and QTCurve 1.8.18 Reproducible: Always Steps to Reproduce: 1. Activate QTCurve 2. open a Window 3. Move Mouse out of the Window Actual Results: App crashes Expected Results: nothing -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 --- Comment #9 from Luca Weiss --- I pressed the toggle button two times. And it is always reproducible. $ dbus-monitor "type='signal',interface='org.kde.kglobalaccel.Component'" signal time=1477047033.062264 sender=org.freedesktop.DBus -> destination=:1.81 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.81" signal time=1477047033.062294 sender=org.freedesktop.DBus -> destination=:1.81 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.81" signal time=1477047039.599343 sender=:1.13 -> destination=(null destination) serial=1100 path=/component/kcm_touchpad; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "kcm_touchpad" string "Toggle Touchpad" int64 5992314 signal time=1477047041.263323 sender=:1.13 -> destination=(null destination) serial=1101 path=/component/kcm_touchpad; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "kcm_touchpad" string "Toggle Touchpad" int64 5993987 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 371409] New: Crash/Exit if Screenshot is dragged to Chrome
https://bugs.kde.org/show_bug.cgi?id=371409 Bug ID: 371409 Summary: Crash/Exit if Screenshot is dragged to Chrome Product: Spectacle Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: j...@wiele.org When taking a screenshot and dragging it to Chrome (not releasing it), Spectacle exits with the message "The X11 connection broke (error 4). Did the X11 server die?". This does not happen with other applications like Dolphin. Reproducible: Always Steps to Reproduce: 1. Open Spectacle, take a Screenshot 2. Drag the Screenshot to Chrome, the mouse cursor changes to an arrow with an red X 3. Spectacle exists without user interaction Actual Results: Spectacle exists (gdb: [Inferior 1 (process 9692) exited with code 01]) Expected Results: Chrome should accept the image, e.g. to attach a screenshot in a slack/whatsapp message -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 344809] Gwenview crashes when moving forward to a video, then back
https://bugs.kde.org/show_bug.cgi?id=344809 --- Comment #7 from sparhawk --- Thank you, I also can confirm that setting Animations to not None fixes this on my system. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 --- Comment #10 from Rajeesh K V --- (In reply to Luca Weiss from comment #9) Thanks. > signal time=1477047039.599343 sender=:1.13 -> destination=(null destination) > serial=1100 path=/component/kcm_touchpad; > interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed >string "kcm_touchpad" >string "Toggle Touchpad" >int64 5992314 > signal time=1477047041.263323 sender=:1.13 -> destination=(null destination) > serial=1101 path=/component/kcm_touchpad; > interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed >string "kcm_touchpad" >string "Toggle Touchpad" >int64 5993987 Shortcut triggered twice in succession. Did you press the toggle shortcut twice, or just once? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 --- Comment #11 from Luca Weiss --- (In reply to Rajeesh K V from comment #10) > (In reply to Luca Weiss from comment #9) > Thanks. > > > signal time=1477047039.599343 sender=:1.13 -> destination=(null destination) > > serial=1100 path=/component/kcm_touchpad; > > interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed > >string "kcm_touchpad" > >string "Toggle Touchpad" > >int64 5992314 > > signal time=1477047041.263323 sender=:1.13 -> destination=(null destination) > > serial=1101 path=/component/kcm_touchpad; > > interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed > >string "kcm_touchpad" > >string "Toggle Touchpad" > >int64 5993987 > > Shortcut triggered twice in succession. Did you press the toggle shortcut > twice, or just once? "I pressed the toggle button two times" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #81 from iraklis --- For the past weeks I messed around with this one and found out that if I open two different konsole instances, I could close them both without the cpu drainage. This might explain the complicated threading issue? (In reply to Sergio from comment #80) > Note that a comment in the bug thread on the nvidia bug tracker states: > "From what I've seen it may not be the nVidia driver which is at fault. > There seems to be a complicated threading issue which might or might not be > caused by the driver...it may just be this driver exposes the issue > differently." > Anyway, after upgrading to Yakkety (Ubuntu 16.10), I found that the bug has disappeared/fixed/gone_in_a_place_where_good_bugs_do_bad_things . Running with the good ol' nvidia 340.98. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371406] Modifier to constrain mouse pointer to the current desktop
https://bugs.kde.org/show_bug.cgi?id=371406 Martin Gräßlin changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- Sorry KWin is the wrong layer for such a feature. That belongs into X server. KWin cannot control the pointer motion. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #4 from allan --- (In reply to allan from comment #3) > It looks like my attempts to provide an edited sample file either produce > rubbish, or remove whatever causes the problem. > So, I may have to provide a complete file, but I don't wish to broadcast it, > so would like to send it off-line. To whom? > > Allan I've sent a gpg'ed copy to Thomas. Allan -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370608] XAUTHORITY env variable changes in the middle of the night
https://bugs.kde.org/show_bug.cgi?id=370608 --- Comment #5 from kolAflash --- I used auditctl / ausearch as suggested, but got only this line after the file was deleted: type=CONFIG_CHANGE msg=audit(10/21/16 13:06:51.010:163) : auid=unset ses=unset op="updated_rules" path=/tmp/xauth-1000-_0 key=(null) list=exit res=yes I'm having no idea what type=CONFIG_CHANGE should indicate. Guess normally ausearch should give me the program's name or pid. The only thing I was able to find by that message was this bug report, which has a similar ausearch result. https://bugzilla.redhat.com/show_bug.cgi?id=567914 type=CONFIG_CHANGE msg=audit(1270141789.105:19355): auid=500 ses=5 op="updated rules" path="/home/kavol/.Xauthority" key=(null) list=4 res=1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #82 from Daniel Eckl --- I have quite the opposite result, my issues began with the update to Yakkety. I'm using nvidia-340.98 with disabled compositor. My konsole sessions were crashing so fast (and always took all existing windows with them) that I needed to switch to qterminal for the time being. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 94670] Add Feature - Overwrite When Newer
https://bugs.kde.org/show_bug.cgi?id=94670 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 371410] New: kgpg crashes on startup and otherwise
https://bugs.kde.org/show_bug.cgi?id=371410 Bug ID: 371410 Summary: kgpg crashes on startup and otherwise Product: kgpg Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: s.k...@gmx.de Application: kgpg (16.07.70) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-45-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: While the startup of each KDE-session kgpg crashes, same trouble after start from "Konsole" The crash can be reproduced every time. -- Backtrace: Application: KGpg (kgpg), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc32a6dc980 (LWP 2303))] Thread 3 (Thread 0x7fc317b7e700 (LWP 2429)): #0 0x7fc3424f2ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc3424ad939 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc3424ae2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc3424ae4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc348ea523b in QEventDispatcherGlib::processEvents (this=0x7fc318c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fc348e4fcea in QEventLoop::exec (this=this@entry=0x7fc317b7dc40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7fc348c74fb4 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7fc348c79b98 in QThreadPrivate::start (arg=0x100c680) at thread/qthread_unix.cpp:344 #8 0x7fc3449bb6fa in start_thread (arg=0x7fc317b7e700) at pthread_create.c:333 #9 0x7fc348370b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fc31700 (LWP 2346)): #0 0x7fc348364e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc3424ae39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc3424ae4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc348ea523b in QEventDispatcherGlib::processEvents (this=0x7fc3180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fc348e4fcea in QEventLoop::exec (this=this@entry=0x7fc31fffec10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7fc348c74fb4 in QThread::exec (this=this@entry=0x7fc34db21d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x7fc34daad7a5 in QDBusConnectionManager::run (this=0x7fc34db21d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #7 0x7fc348c79b98 in QThreadPrivate::start (arg=0x7fc34db21d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #8 0x7fc3449bb6fa in start_thread (arg=0x7fc31700) at pthread_create.c:333 #9 0x7fc348370b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fc32a6dc980 (LWP 2303)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x70001) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:103 #8 QBasicAtomicInteger::load (this=0x70001) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:99 #9 QtPrivate::RefCount::ref (this=0x70001) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55 #10 QString::QString (other=..., this=0xf976e0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:899 #11 KgpgCore::KgpgKeyPrivate::KgpgKeyPrivate (this=0xf97680, id=..., size=, trust=..., algo=..., subtype=..., keytype=..., creationDate=..., curve=...) at /workspace/build/core/kgpgkey.cpp:178 #12 0x004376f9 in KgpgCore::KgpgKey::KgpgKey (this=0x7ffcf1399260, id=..., size=1024, trust=..., algo=..., subtype=..., keytype=..., creationDate=..., curve=...) at /workspace/build/core/kgpgkey.cpp:205 #13 0x004ab1df in readPublicKeysProcess (p=..., readNode=readNode@entry=0x0) at /workspace/build/kgpginterface.cpp:171 #14 0x004ade68 in KgpgInterface::readPublicKeys (ids=...) at /workspace/build/kgpginterface.cpp:301 #15 0x00440429 in KGpgRootNode::addKeys (this=0xe43470, ids=...) at /workspace/build/core/KGpgRootNode.cpp:70 #16 0x00454157 in KGpgItemModel::refreshKeyIds (this=0xe283c0, ids=...) at /workspace/build/model/kgpgitemmodel.cpp:461 #17 0x00454235 in KGpgItemModel::refreshKeys (this=, ids=...) at /workspace/build/model/kgpgitemmodel.cpp:447 #18 0x0048a096 in KGpgItemModel::refreshKeys (this=) at /workspace/build/model/kgpgitemmodel.h:86 #19 KeysManager::refreshkey (this=0xde68c0
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #83 from iraklis --- (In reply to Daniel Eckl from comment #82) > I have quite the opposite result, my issues began with the update to > Yakkety. I'm using nvidia-340.98 with disabled compositor. My konsole > sessions were crashing so fast (and always took all existing windows with > them) that I needed to switch to qterminal for the time being. Might this be a different bug? The problem here isn't actually konsole crashing, rather than konsole process running in the background consuming 100% of a cpu core, after being "exited" by the X button. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 189456] powerdevil should not suspend when computer is being shutdown
https://bugs.kde.org/show_bug.cgi?id=189456 Sascha Zenglein changed: What|Removed |Added CC||sascha.zengl...@yahoo.de --- Comment #29 from Sascha Zenglein --- still happens to me... systemd-inhibit --list tells that PowerDevil has a block on all the events, so I can't workaround this by setting LidSwitchIgnoreInhibited=no in /etc/systemd/logind.conf -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #84 from Daniel Eckl --- You are right, my issue does not match the topic, but crashes have been discussed here, too. I will reconsider and search for other bugs on this tracker. Thank you for pointing this out. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363311] Ctrl+Z / Undo doesn't work on big brush strokes
https://bugs.kde.org/show_bug.cgi?id=363311 Dmitry Kazakov changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/1426e045e9cdd653b0ca3c6cb ||e29703ee57b2c81 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Dmitry Kazakov --- Git commit 1426e045e9cdd653b0ca3c6cbe29703ee57b2c81 by Dmitry Kazakov. Committed on 21/10/2016 at 11:42. Pushed by dkazakov into branch 'kazakov/undo-with-instant-preview-T2544'. Implemented Undo for Instant Preview strokes Now the user can cancel a stroke without waiting until the main full-resolution stroke finishes its execution. Just press Ctrl+Z and the your preview will be (partially) reverted and the corresponding background stroke will be cancelled. Technically it is implemented by introducing the second undo store inside the strokes queue and syncing it with the running strokes with a set of complicated rules. If the stroke can be cancelled, it is cancelled, if the stroke has already completed its execution, it is just undone. Ref T2544 M +9-1libs/image/kis_image.cc M +11 -0libs/image/kis_image.h M +4-0libs/image/kis_image_interfaces.cpp M +8-0libs/image/kis_image_interfaces.h M +1-2libs/image/kis_processing_applicator.cpp M +6-0libs/image/kis_stroke.cpp M +2-0libs/image/kis_stroke.h M +10 -10 libs/image/kis_stroke_strategy_undo_command_based.cpp M +4-5libs/image/kis_stroke_strategy_undo_command_based.h M +183 -4libs/image/kis_strokes_queue.cpp M +11 -0libs/image/kis_strokes_queue.h C +9-11 libs/image/kis_strokes_queue_undo_result.h [from: libs/image/kis_image_interfaces.cpp - 075% similarity] M +5-0libs/image/kis_undo_stores.cpp M +2-0libs/image/kis_undo_stores.h M +10 -0libs/image/kis_update_scheduler.cpp M +7-0libs/image/kis_update_scheduler.h M +1-1libs/image/tests/kis_stroke_strategy_undo_command_based_test.cpp M +189 -14 libs/image/tests/kis_strokes_queue_test.cpp M +5-0libs/image/tests/kis_strokes_queue_test.h M +11 -3libs/image/tests/scheduler_utils.h M +5-0libs/ui/KisDocument.cpp M +1-1libs/ui/actions/kis_selection_action_factories.cpp M +0-3libs/ui/kis_filter_manager.cc M +0-1libs/ui/tests/fill_processing_visitor_test.cpp M +0-1libs/ui/tool/kis_figure_painting_tool_helper.cpp M +2-4libs/ui/tool/kis_resources_snapshot.cpp M +1-1libs/ui/tool/kis_resources_snapshot.h M +1-1libs/ui/tool/kis_tool.cc M +1-2libs/ui/tool/kis_tool_freehand.cc M +0-4libs/ui/tool/kis_tool_freehand_helper.cpp M +0-2libs/ui/tool/kis_tool_freehand_helper.h M +0-1libs/ui/tool/strokes/freehand_stroke.cpp M +0-1libs/ui/tool/strokes/kis_filter_stroke_strategy.cpp M +0-19 libs/ui/tool/strokes/kis_painter_based_stroke_strategy.cpp M +0-1libs/ui/tool/strokes/kis_painter_based_stroke_strategy.h M +0-1libs/ui/widgets/kis_scratch_pad.cpp M +0-1 plugins/paintops/defaultpaintops/brush/tests/kis_brushop_test.cpp M +1-1plugins/tools/basictools/kis_tool_fill.cc M +1-1plugins/tools/basictools/kis_tool_gradient.cc M +1-2plugins/tools/basictools/kis_tool_line.cc M +2-3plugins/tools/basictools/kis_tool_line_helper.cpp M +1-2plugins/tools/basictools/kis_tool_line_helper.h M +3-4plugins/tools/basictools/kis_tool_move.cc M +16 -32 plugins/tools/basictools/strokes/move_selection_stroke_strategy.cpp M +2-4 plugins/tools/basictools/strokes/move_selection_stroke_strategy.h M +12 -22 plugins/tools/basictools/strokes/move_stroke_strategy.cpp M +2-3plugins/tools/basictools/strokes/move_stroke_strategy.h M +3-4plugins/tools/basictools/tests/move_selection_stroke_test.cpp M +1-1plugins/tools/basictools/tests/move_stroke_test.cpp M +1-1plugins/tools/tool_crop/kis_tool_crop.cc M +3-3plugins/tools/tool_transform2/kis_tool_transform.cc M +2-2 plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp M +1-1 plugins/tools/tool_transform2/strokes/transform_stroke_strategy.h M +0-1sdk/tests/stroke_testing_utils.cpp http://commits.kde.org/krita/1426e045e9cdd653b0ca3c6cbe29703ee57b2c81 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off
https://bugs.kde.org/show_bug.cgi?id=359542 Sebastian Kügler changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #29 from Sebastian Kügler --- @Olaf > At this point I decided you will probably not even read all the things I wrote > down until now and stopped playing around. I hope this is somehow useful for > debugging. I will attach the kscreen.log file and screen photos soon. That's unfortunately correct. You have by now put so much information into this bugreport that it's a pain and very inefficient to sift through. I have to filter out the relevant bits from your huge swathes of text, and often, I need to read a bugreport multiple times. You can imagine what a huge waste of time it becomes then. I wonder, if you know it's not useful, why you put so much (unrelated) info in it. So, for your understanding: - I'm interested in problems with resolution, position and enablement of outputs, these problems fall under kscreen - if you have problems with applications, file a bug against the app, leave the info out here - if you've problems with the plasmashell (panels location, containment location, etc.), file a bug against plasmashell (there's a Multiscreen component) In order to keep my bug triaging life manageable, I'm closing this bugreport, asking you to file a new one, with *only* the relevant information. Thanks for your cooperation, it's really appreciated. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 342201] Crash on Konsole exit when using proprietary nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=342201 Daniel Eckl changed: What|Removed |Added CC||daniel.e...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #85 from Sergio --- So, we have users who saw this bug with xenial and then the bug go away with yakkety, but there are also users (at least me) who did not see the bug with xenial and see it with yakkety. Then we have users on nvidia 361 before 18 see it, then see it disappear with .18 and reappear again with .28 (when possibly nvidia had never touched anything directly related to the issue in the driver). This looks very much like an issue triggered by timings of events / races. And it is very much possible that noveau cures it not because it has "better opengl" but because it is slower in some paths, significantly changing the timing of things. Can it be a Qt issue. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 365870] [Libarchive] Ark hangs when aborting a DeleteJob
https://bugs.kde.org/show_bug.cgi?id=365870 Elvis Angelaccio changed: What|Removed |Added Latest Commit||http://commits.kde.org/ark/ ||d587749dbdb1f13cd497934d153 ||88488bc199c2b Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||16.08.3 --- Comment #1 from Elvis Angelaccio --- Git commit d587749dbdb1f13cd497934d15388488bc199c2b by Elvis Angelaccio. Committed on 21/10/2016 at 12:41. Pushed by elvisangelaccio into branch 'Applications/16.08'. libarchive: properly kill DeleteJobs Use m_abortOperation like the other jobs do. FIXED-IN: 16.08.3 M +1-1plugins/libarchive/readwritelibarchiveplugin.cpp http://commits.kde.org/ark/d587749dbdb1f13cd497934d15388488bc199c2b -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 Nicolas Frattaroli changed: What|Removed |Added CC|kdeb...@fratti.ch | -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 260312] 'Apply To All' in RenameDialog is not applied throughout batch jobs
https://bugs.kde.org/show_bug.cgi?id=260312 Elvis Angelaccio changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #86 from Daniel Eckl --- I absolutely have this issue, too, using Kubuntu 16.10 Yakkety Yak and nvidia-340.98. After I tried to reproduce my (supposedly unrelated) konsole crash issue I closed every konsole window. There was no 100% process running then, I checked that. Way later I noticed one cpu core was running at 100% and it turned out it was a konsole process. -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 371331] database calls randomly fail on Windows 10 (postgresql)
https://bugs.kde.org/show_bug.cgi?id=371331 --- Comment #4 from Simeon Kuran --- I just finished cleaning up my project and uploaded it to my bitbucket account. I also added a zip archive (kdb-test-binary) which contains the compiled executable with all necessary dll files (except msvc runtime dlls). (size of the zip archive is probably to big for email...) to get it: git clone g...@bitbucket.org:simeonKuran/kdb-test.git IMPORTANT: I need to point out once more, that sometimes everything works as expected! But sometimes one or the other DB calls seem to fail. Kind of non-deterministic it seems to me... Of course to try it out, you will need a postgresql DB. I think I installed version 9.5.4 - 64bit from this link: http://www.enterprisedb.com/products-services-training/pgdownload#windows -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 183875] kmail keeps spawning "gpgsm --server" but never kills/reaps them
https://bugs.kde.org/show_bug.cgi?id=183875 Dan changed: What|Removed |Added CC||di...@betriebsdirektor.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #27 from Sebastian Kügler --- I'm trying to reproduce by running a neon session in a virt-manager, using qemu. I've the driver QXL, and I've installed qemu-ga inside the vm, but it can't find a channel, so it doesn't work. The error is: critical: error opening channel: Device or resource busy critical: error opening channel critical: failed to create guest agent channel critical: failed to initialize guest agent channel (The resize "vm with window" checkbox is greyed out, complains about missing guest agent) I'm a bit lost here, anyone who can help? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370379] When applying a Transform Mask, the original image still appears
https://bugs.kde.org/show_bug.cgi?id=370379 Boudewijn Rempt changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Boudewijn Rempt --- Thanks for checking! -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 371331] database calls randomly fail on Windows 10 (postgresql)
https://bugs.kde.org/show_bug.cgi?id=371331 --- Comment #5 from Jarosław Staniek --- > sometimes one or the other DB calls seem to fail. Is this KDbConnection::executeQuery() maybe? On failure I recommend to use qDebug() << m_connection->result() so we know what happens. Similarly, KDbCursor also has result() method. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 362295] No such object path '/modules/kdeconnect/devices/_d05cbcbd_dea5_4135_949c_6430342eec97_/sftp'
https://bugs.kde.org/show_bug.cgi?id=362295 Manuel López-Ibáñez changed: What|Removed |Added CC||lopeziba...@gmail.com --- Comment #5 from Manuel López-Ibáñez --- Same here in Kubuntu 16.04 gwenview: 15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371411] New: Unify fstat64/fstatat64 wrappers
https://bugs.kde.org/show_bug.cgi?id=371411 Bug ID: 371411 Summary: Unify fstat64/fstatat64 wrappers Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: mar...@juszkiewicz.com.pl arm/mips32/ppc32/x86 have similar wrappers for those two syscalls. arm/mips32 ones do not handled 4th arguments (int flags) of syscall. Not tested. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers
https://bugs.kde.org/show_bug.cgi?id=371411 --- Comment #1 from Marcin Juszkiewicz --- Created attachment 101680 --> https://bugs.kde.org/attachment.cgi?id=101680&action=edit patch -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363291] Plasma crashed after audio device shutdown in pulseaudio
https://bugs.kde.org/show_bug.cgi?id=363291 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-pa/f143312e3bb427fe3a31a ||e1095db4410656b749e --- Comment #3 from David Edmundson --- Git commit f143312e3bb427fe3a31ae1095db4410656b749e by David Edmundson. Committed on 21/10/2016 at 13:49. Pushed by davidedmundson into branch 'Plasma/5.8'. Fix crash in application shutdown (alternate fix) Summary: We have a SourceModel that inherits from AbastractModel AbastractModel inherits from both QObject and Ref. When we call the destructor of Ref, that kills the Pulseaudio::context that emits that the default source has changed during it's teardown. Because the QObject destructor hasn't run yet, our signals are still attached; however they refer to data from SourceModel which we've already run the destructor on - hence crash. This patch does the ref counting in an alternate way, destroying the PA Context after our model has disconnected all the signals, like it would be if the context was a child of the model. Test Plan: ran kquitapp5 plasmashell a lot, everything still seems fine. I couldn't recreate the original crash, it requires multiple outputs being deleted in the wrong order, which I don't happen to have. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D3124 M +0-1src/CMakeLists.txt M +12 -0src/pulseaudio.cpp M +3-2src/pulseaudio.h D +0-46 src/ref.cpp D +0-54 src/ref.h http://commits.kde.org/plasma-pa/f143312e3bb427fe3a31ae1095db4410656b749e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371215] Plasma Crashes when trying to end application with kquiapp5
https://bugs.kde.org/show_bug.cgi?id=371215 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from David Edmundson --- Fixed with d6853cc1dc4e63a779e126c7f23acc2f1ce180f1 which is in Plasma 5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers
https://bugs.kde.org/show_bug.cgi?id=371411 Marcin Juszkiewicz changed: What|Removed |Added Attachment #101680|0 |1 is obsolete|| --- Comment #2 from Marcin Juszkiewicz --- Created attachment 101681 --> https://bugs.kde.org/attachment.cgi?id=101681&action=edit move all *stat*64 to generic this patch adds stat64 and lstat64 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371412] New: Rename wrap_sys_shmat to sys_shmat like other wrappers
https://bugs.kde.org/show_bug.cgi?id=371412 Bug ID: 371412 Summary: Rename wrap_sys_shmat to sys_shmat like other wrappers Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: mar...@juszkiewicz.com.pl All syscall wrappers are name sys_SYSCALLNAME except wrap_sys_shmat (and few highly arch specific sys_syscall284 like ones). I have a script to generate syscall table also for valgrind and this wrapper name adds special case for no reason. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 370933] Upgrade from 16.4 to 16.10 silently fails
https://bugs.kde.org/show_bug.cgi?id=370933 --- Comment #4 from Paddyrob --- That seems to have nailed it - many thanks! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371412] Rename wrap_sys_shmat to sys_shmat like other wrappers
https://bugs.kde.org/show_bug.cgi?id=371412 --- Comment #1 from Marcin Juszkiewicz --- Created attachment 101682 --> https://bugs.kde.org/attachment.cgi?id=101682&action=edit patch -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371250] Plasma crashed while browsing
https://bugs.kde.org/show_bug.cgi?id=371250 Rich Sezov changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED Platform|unspecified |Archlinux Packages --- Comment #2 from Rich Sezov --- Here's the Awesome Widget: https://arcanis.me/projects/awesome-widgets/ This was installed from the Arch Linux AUR repo: https://aur.archlinux.org/packages/kdeplasma-applets-awesome-widgets-git/ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 370933] Upgrade from 16.4 to 16.10 silently fails
https://bugs.kde.org/show_bug.cgi?id=370933 --- Comment #5 from kantan...@outlook.com --- (In reply to bym7444 from comment #2) > (In reply to bym7444 from comment #1) > > Hey. Had the same issue as you. Was able to fit it by running: > > > > sudo apt-get install ubuntu-release-upgrader-qt > > > > Not sure why the files were missing (perhaps some dist-upgrade gone amiss?). > > But it's working fine now. > > Ah, seems that this has already been found before: > https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1633692 > > It's also in the "Known Problems" section of: > https://wiki.ubuntu.com/YakketyYak/ReleaseNotes/Kubuntu Thanks! I wasn't sure where else to look. I ended up upgrading from the CLI, but next time I'll check the Release Notes and Ubuntu Launchpad before reporting a bug here. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371252] Master-68e89f4 Immediate crash after startup. Movit disabled.
https://bugs.kde.org/show_bug.cgi?id=371252 Paul Konecny changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Paul Konecny --- Fixed, thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371413] New: I don't know what happened after an update of the Kernel and possibly Virtualbox
https://bugs.kde.org/show_bug.cgi?id=371413 Bug ID: 371413 Summary: I don't know what happened after an update of the Kernel and possibly Virtualbox Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: crgla...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I am osrry to be vague in the title but I really don't know what has happened. Yesterday I received a notice from ORacle that a new versionof VirtualBox was available. I downloaded and installed it. I also had an automatic update from through for security issues (cannot remember the details) from OpenSuSE. They may not be related. But now Plasma is not working. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f99830ad7c0 (LWP 3116))] Thread 7 (Thread 0x7f98c3fff700 (LWP 3149)): #0 0x7f9978c921d7 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9978c9483f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9978c94df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9978c94f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f997cee5d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f997ce8cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f9980b5e282 in () at /usr/lib64/libQt5Quick.so.5 #8 0x7f997ccb332f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f997c5c102d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f994f1c2700 (LWP 3147)): #0 0x7f997bdc603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f998279186b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f9982791899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f997c5c102d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9954b80700 (LWP 3146)): #0 0x7f9978cd6cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9978c948fc in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9978c94df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9978c94f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f997cee5d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f997ce8cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f997ffc2e18 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f997ccb332f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f997c5c102d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f995647a700 (LWP 3145)): #0 0x7f9978c944f1 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9978c94d80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9978c94f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f997cee5d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f997ce8cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f997ffc2e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f997ccb332f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f997c5c102d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f996205e700 (LWP 3135)): #0 0x7f997c5b4ccd in read () at /lib64/libc.so.6 #1 0x7f9974756073 in () at /usr/lib64/tls/libnvidia-tls.so.367.57 #2 0x7f9978cd5b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9978c94999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9978c94df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f9978c94f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f997cee5d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f997ce8cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f997ffc2e18 in () at /usr/lib64/libQt5Qml.so.5 #10 0
[gwenview] [Bug 362295] No such object path '/modules/kdeconnect/devices/_d05cbcbd_dea5_4135_949c_6430342eec97_/sftp'
https://bugs.kde.org/show_bug.cgi?id=362295 --- Comment #6 from Manuel López-Ibáñez --- A work-around seems to be to open Dolphin and delete the device entry from the left-hand panel. My device is disconnected when I did it, so I hope it will get recreated as needed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers
https://bugs.kde.org/show_bug.cgi?id=371411 Marcin Juszkiewicz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Marcin Juszkiewicz --- should check first with build. stat structure differ per arch ;( -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #28 from OlafLostViking --- Did you install and run the mentioned spice-vdagent? This is mandatory for virt-manager based VMs to communicate with the host. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 371414] New: When open a new konsole, it uses the last profile instead of the default
https://bugs.kde.org/show_bug.cgi?id=371414 Bug ID: 371414 Summary: When open a new konsole, it uses the last profile instead of the default Product: konsole Version: 16.08.2 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ste...@infinito.it I have 2 profiles saved: 'terminal' (the default) and 'mutt' (used only for this MUA). Also I have 2 shortcuts to open konsole and mutt: Meta + T for Konsole and Meta + M for mutt (I have set execute in konsole with '--profile mutt' in this case). Until I use Meta+T KDE opens the terminal, but after I use Meta+M to open mutt then Meta+T still opens mutt (into a konsole with profile 'mutt') and when I close mutt also the konsole closes. Same situation when I try to open konsole by kde menu or by Alt+F2 but not if I launch konsole inside a open konsole. Right mouse -> Switch Profile doesn't work. Thanks Stefano Reproducible: Always Steps to Reproduce: 1. Create 1 more profile for mutt (named 'mutt') 2. With "KDE Menu Editor" edit mutt and adds to terminal option '--profile mutt' 3. Adds also a shortcut (Meta+M) 4. Edit konsole and adds a shortcut (Meta+T) Actual Results: Press Meta+T -> open konsole Select konsole on kde menu -> open konsole Alt+F2, digit konsole -> open konsole Press Meta+M -> open mutt Press Meta+T -> open mutt Select konsole on kde menu -> open mutt Alt+F2, digit konsole -> open mutt Expected Results: Press Meta+T always open konsole -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers
https://bugs.kde.org/show_bug.cgi?id=371411 Marcin Juszkiewicz changed: What|Removed |Added Attachment #101681|0 |1 is obsolete|| --- Comment #4 from Marcin Juszkiewicz --- Created attachment 101683 --> https://bugs.kde.org/attachment.cgi?id=101683&action=edit Handle (int flags) argument of fstatat64 on arm and ppc32 x86 and mips32 have wrappers which support all 4 arguments. So let arm and ppc32 join them. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers
https://bugs.kde.org/show_bug.cgi?id=371411 Marcin Juszkiewicz changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368811] Screen freezed when trying to get desktop grid from desktop corner (3d effect)
https://bugs.kde.org/show_bug.cgi?id=368811 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #11 from Elvis Angelaccio --- I have a similar issue. Here (Intel graphics, Xorg session) kwin freezes only when I trigger the desktop grid _with_ a second monitor attached. Though it doesn't always happen, just randomly. -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 371415] New: 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647
https://bugs.kde.org/show_bug.cgi?id=371415 Bug ID: 371415 Summary: 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647 Product: abakus Version: 0.92 Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k.h...@gmx.de Reporter: france...@e8g93s9zfo.com 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647 1-877-424-6647 mozilla FirefOx mail customer care phone number 1-877-424-6647 mozilla FirefOx toll free customer care number 1-877-424-6647 %%$support+1-877-424-6647!! Mozilla Firefox Help Desk Phone Number%%$support+1-877-424-6647!! Mozilla Firefox Help Desk Phone Number%%$support+1-877-424-6647!! Mozilla Firefox Help Desk Phone Number%%$support+1-877-424-6647!! Mozilla Firefox Help Desk Phone Number%%$support+1-877-424-6647!! Mozilla Firefox Help Desk Phone Number Toll Free, @(1-877-424-6647)@-: mozilla firefox help desk phone number voses online solution for all USA/CANADA clients. For any help of query call 1-877-424-6647to get all mozilla firefox account solution. 1-877-424-6647For any help of query call 1-877-424-6647to get all mozilla firefox account solution. @@Call, 1-877-424-6647for all type help by mozilla firefox support telephone number,mozilla firefox support phone number,mozilla firefox support phone number,mozilla firefox help phone number, mozilla firefox technical support number.mozilla firefox support number, mozilla firefox phone number, mozilla firefox tech support number, mozilla firefox customer support number, mozilla firefox customer support phone number, mozilla firefox customer service phone number, mozilla firefox customer service phone number, mozilla firefox support phone number mozilla firefox help number-mozilla firefox Helpline Number; mo Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371416] New: Crash changing title clip (or color clip) color
https://bugs.kde.org/show_bug.cgi?id=371416 Bug ID: 371416 Summary: Crash changing title clip (or color clip) color Product: kdenlive Version: 16.08.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: snd.no...@gmail.com Please follow the steps. Reproducible: Always Steps to Reproduce: 1. add a color clip 2. try to switch the color 3. crash or 1. add a title clip 2. try to change the text color 3. crash This is for changing title clip color: (kdenlive:5660): Gdk-WARNING **: gdkwindow-x11.c:5554 drawable is not a native X11 window Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault. 0x7fffeed9a495 in XChangeProperty () from /usr/lib/libX11.so.6 (gdb) thread apply all bt Thread 26 (Thread 0x7fff7ae65700 (LWP 5709)): #0 0x7fffefe5a551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fffe7c2b99d in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #2 0x7fffe7c2bf8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #3 0x7fffb7a09eed in () at /usr/lib/libSDL-1.2.so.0 #4 0x7fffb79dd800 in () at /usr/lib/libSDL-1.2.so.0 #5 0x7fffb79e5fe8 in () at /usr/lib/libSDL-1.2.so.0 #6 0x7fffb7a278a9 in () at /usr/lib/libSDL-1.2.so.0 #7 0x7fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fffefe637df in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fff7f666700 (LWP 5708)): #0 0x7fffee32410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x76fa828b in () at /usr/lib/libmlt.so.6 #2 0x0075076d in RenderThread::run() (this=0x7fff80002f00) at /tmp/yaourt-tmp-farid/aur-kdenlive-git/src/kdenlive/src/monitor/glwidget.cpp:1253 #3 0x70851d78 in () at /usr/lib/libQt5Core.so.5 #4 0x7fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fffefe637df in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fff8776b700 (LWP 5707)): #0 0x7fffee32410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fffb7c74030 in () at /usr/lib/mlt/libmltsdl.so #2 0x7fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 ---Type to continue, or q to quit--- #3 0x7fffefe637df in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fff74c4c700 (LWP 5705)): #0 0x7fffefe5a48d in poll () at /usr/lib/libc.so.6 #1 0x7fffe80a9786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffe80a989c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x70a8070f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x70a2a23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7084d0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x70851d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fffefe637df in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fff7544d700 (LWP 5704)): #0 0x7fffefe5a48d in poll () at /usr/lib/libc.so.6 #1 0x7fffe80a9786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffe80a989c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x70a8070f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x70a2a23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7084d0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x70851d78 in () at /usr/lib/libQt5Core.so.5 ---Type to continue, or q to quit--- #7 0x7fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fffefe637df in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fff992c9700 (LWP 5692)): #0 0x7fffefe5a48d in poll () at /usr/lib/libc.so.6 #1 0x7fffe80a9786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffe80a989c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x70a8070f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x70a2a23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7084d0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x724472d5 in () at /usr/lib/libQt5Qml.so.5 #7 0x70851d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fffefe637df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fff9b1af700 (LWP 5690)): #0 0x7fffefe5a48d in poll () at /usr/lib/libc.so.6 #1 0x7fffe80a9786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffe80a989c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x70a8070f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x70a2a23a in QEve
[KScreen] [Bug 371417] New: screens not (re-)actived after (un-)docking cycles of a notebook
https://bugs.kde.org/show_bug.cgi?id=371417 Bug ID: 371417 Summary: screens not (re-)actived after (un-)docking cycles of a notebook Product: KScreen Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: common Assignee: se...@kde.org Reporter: olaf.the.lost.vik...@gmail.com As asked for in bug #359542 here a shorter summary of the problem mentioned there. KScreen fails to (re-)enable displays after docking/sleep cycles. Reproducible: Sometimes Steps to Reproduce: 1. Put Notebook to sleep. 2. Undock from docking station A (internal screen + one external screen). 3. Dock into docking station B (two external screens). 4. Wake-up. Actual Results: Internal display goes on, gets deactivated, external displays do not get even powered on. Undocking does not reactive the internal display. Open data/application states get lost. Expected Results: Internal display should go off but the two external displays should also get activated. DELL E6430 with a mobile nvidia chip. Docking Station A has an horizontal Full-HD display on the DVI port. The internal 1600x900 display LVDS is used. Docking Station B has an horizontal 2560x1440 display on the DP port and a vertical 2048x1152. The internal display cannot be used. -- You are receiving this mail because: You are watching all bug changes.
