[plasmashell] [Bug 364227] The Super (Windows) key should launch Kickoff, like most other DEs
https://bugs.kde.org/show_bug.cgi?id=364227 Kai Uwe Broulik changed: What|Removed |Added Version Fixed In||5.8 Resolution|REMIND |FIXED --- Comment #5 from Kai Uwe Broulik --- This works in plasma 5.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368230] New: systemsettings crashes when i change theme to oxygen
https://bugs.kde.org/show_bug.cgi?id=368230 Bug ID: 368230 Summary: systemsettings crashes when i change theme to oxygen Product: systemsettings Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: isc.oscar.baland...@gmail.com Application: systemsettings5 (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I was changing the theme to use oxygen, then i changed to another option. I read about a bug related and there somebody made the next comment: (https://bugs.kde.org/show_bug.cgi?id=355711) "This bug is fixed since KDE Frameworks version 5.19, but Ubuntu LTS 16.04 only ships 5.18 version. Please report this to the bug tracker of your distribution." I use kubuntu 16.04 and i see the version 5.18 for KDE The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70f28728c0 (LWP 13739))] Thread 2 (Thread 0x7f70e0f86700 (LWP 13740)): #0 0x7f70eef8ce8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f70ecc74c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f70ecc768d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f70e32d8629 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f70ef68284e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f70ec3fe6fa in start_thread (arg=0x7f70e0f86700) at pthread_create.c:333 #6 0x7f70eef98b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f70f28728c0 (LWP 13739)): [KCrash Handler] #6 0x7f70ef8961e7 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f70d2a8b1b3 in KParts::PartManager::~PartManager() () from /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #8 0x7f70d2a8b369 in KParts::PartManager::~PartManager() () from /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #9 0x7f70ef89052b in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f70ef899da0 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f70d31ce31b in KHTMLPart::~KHTMLPart() () from /usr/lib/x86_64-linux-gnu/libKF5KHtml.so.5 #12 0x7f70d31ce439 in KHTMLPart::~KHTMLPart() () from /usr/lib/x86_64-linux-gnu/libKF5KHtml.so.5 #13 0x7f70ef892ec0 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f70f0d3605c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f70f0d3b516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f70ef86362b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f70ef865a26 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f70ef8b9673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f70ebedd1a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f70ebedd400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f70ebedd4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f70ef8b9a7f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f70ef860dea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f70ef868e8c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x0040f7a1 in main () Possible duplicates by query: bug 367884, bug 366515, bug 366489, bug 364754, bug 364048. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368220] Animated GIFs don't play
https://bugs.kde.org/show_bug.cgi?id=368220 kmi changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from kmi --- Gwenview is our image viewer. Okular is a viewer for static documents, not a movie player. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368210] New monitor isn't detected correctly, and task bar disappears after disconnecting it
https://bugs.kde.org/show_bug.cgi?id=368210 kmi changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||5.7 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 368086] KDE 5
https://bugs.kde.org/show_bug.cgi?id=368086 --- Comment #3 from Yura Shevhuk --- Created attachment 100924 --> https://bugs.kde.org/attachment.cgi?id=100924&action=edit Console crash if close the console window Console crash if close the console window -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368229] New: [Frameworks] 'change light & dark colors' broken
https://bugs.kde.org/show_bug.cgi?id=368229 Bug ID: 368229 Summary: [Frameworks] 'change light & dark colors' broken Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ras...@gmail.com In settings > configure okular > accessibility, there is an option to change light & dark colors. I set the light (background) color to black and the dark (text) color to light gray. The background is dark gray, and the text is light gray around the edges and black in the middle. After turning off text anti-aliasing, the text is black. http://i.imgur.com/F13sAf4.png http://i.imgur.com/1lNbGvG.png Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 --- Comment #5 from Frits Spieker --- Not to be blunt, but deleting all imap accounts, dropping and recreating the akonadi database and recreating of all imap accounts is not what I would call resolved. It is a messy workaround and a very messy one at that. What about users that also still have pop3 email boxes? What about the less technical inclined? It's a messy workaround which hides a messy bug which is in need of a proper fix. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368228] Have a more professional description of the package on Launchpad
https://bugs.kde.org/show_bug.cgi?id=368228 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||cf...@kde.org Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Please report this on Launchpad. KDE developers do not maintain the Launchpad site. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 368096] Unable to load ical over http
https://bugs.kde.org/show_bug.cgi?id=368096 --- Comment #1 from Laurent Montel --- Git commit 5c198eb6adb662a462c3f19462d0872a0efa7786 by Montel Laurent. Committed on 04/09/2016 at 06:05. Pushed by mlaurent into branch 'Applications/16.08'. Investigate Bug 368096 - Unable to load ical over http We need to create path. It's not perfect yet as there is still a problem here, but we can create ical directory now. M +3-1resources/shared/singlefileresource/singlefileresourcebase.cpp http://commits.kde.org/kdepim-runtime/5c198eb6adb662a462c3f19462d0872a0efa7786 -- You are receiving this mail because: You are watching all bug changes.
[KDE Config Driver Manager] [Bug 368225] Driver management software is collecting information forever
https://bugs.kde.org/show_bug.cgi?id=368225 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED CC||cf...@kde.org --- Comment #2 from Christoph Feck --- Bugs for the "Driver Manager" are not handled in the KDE bug tracker. Please report this issue to the bug tracker of your distribution. "KDE Config Driver Manager" is only a Systemsettings module to configure "Driver Manager". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368047] Clone Tool acts weird after a brush resize
https://bugs.kde.org/show_bug.cgi?id=368047 mvowada changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368047] Clone Tool acts weird after a brush resize
https://bugs.kde.org/show_bug.cgi?id=368047 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #2 from mvowada --- Created attachment 100923 --> https://bugs.kde.org/attachment.cgi?id=100923&action=edit (Video example) (krita-3.0.99.91-Beta-x86_64.appimage - Ubuntu 14.04 Unity) I can reproduce this on Ubuntu with Krita appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367641] Unable to get source point move with the clone tool
https://bugs.kde.org/show_bug.cgi?id=367641 mvowada changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||freebo...@tiscali.it Ever confirmed|0 |1 --- Comment #1 from mvowada --- (krita-3.0.99.91-Beta-x86_64.appimage - Ubuntu 14.04 Unity) I can reproduce this, ("Edit brush settings > Painting Mode" >): "Source point move", "Healing" and "Clone From All Visible Layers" checkboxes are not selectable. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368228] New: Have a more professional description of the package on Launchpad
https://bugs.kde.org/show_bug.cgi?id=368228 Bug ID: 368228 Summary: Have a more professional description of the package on Launchpad Product: kate Version: unspecified Platform: Other URL: https://launchpad.net/ubuntu/+source/kate OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: ddascalescu+...@gmail.com The description right now has typos, emoticons etc. "I hope it works well and improves workspeed on many little textfiles. ;-) Our new buffer managment will allow it to open 50MB files ++ in less than 5 seconds (at least on my 400Mhz P2 ;)" Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368216] Switch to open windows using Super/Meta/Windows key + 0..9 digits/numbers
https://bugs.kde.org/show_bug.cgi?id=368216 Christoph Feck changed: What|Removed |Added Assignee|plasma-de...@kde.org|kwin-bugs-n...@kde.org Component|Window List |general CC||cf...@kde.org Product|plasmashell |kwin Severity|normal |wishlist Target Milestone|1.0 |--- --- Comment #1 from Christoph Feck --- Could you please clarify how the mapping "windows <-> numbers" should be done? Let's say, I have 12 windows open, how should kwin select which windows get which numbers? -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 368177] Bookmarks/places are separated and hard to use, and there's no "Recents"
https://bugs.kde.org/show_bug.cgi?id=368177 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #3 from Christoph Feck --- Pinta is not KDE software, so it does not use the KDE file dialogs. Regarding the bookmark icon in the KDE file dialog, I do not see it here. Can you please check: - if it appears with all KDE applications, if not, which not? - if it does appear in all KDE applications, if it also appears with a freshly created user account? - if yes, can you try a different distribution? Also, can you please ask Mint developers, why they let you beta test the old Plasma 5.5 software, when we already released Plasma 5.6 and 5.7 as stable releases. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 368154] filelight crashes if invoked with a directory parameter
https://bugs.kde.org/show_bug.cgi?id=368154 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368173] Must the window be so small
https://bugs.kde.org/show_bug.cgi?id=368173 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||cf...@kde.org Resolution|--- |UPSTREAM --- Comment #3 from Christoph Feck --- That is the Qt font selection dialog. Please report this issue directly to Qt developers via https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368178] What is "Backtab"?
https://bugs.kde.org/show_bug.cgi?id=368178 Christoph Feck changed: What|Removed |Added Product|kde |kwin Component|general |general Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368227] plasma crashed suddenly
https://bugs.kde.org/show_bug.cgi?id=368227 --- Comment #1 from Vadym Krevs --- Created attachment 100922 --> https://bugs.kde.org/attachment.cgi?id=100922&action=edit crash stacktrace. Bug submitted manually because comment length limit prevents it from being submittable via the kde crash reporter. WHich renders the crash reporter useless. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 368183] Crash of weather plasmoid
https://bugs.kde.org/show_bug.cgi?id=368183 Christoph Feck changed: What|Removed |Added Product|kde |plasma4 Component|general |general Version|4.14.1 |4.11.11 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368227] New: plasma crashed suddenly
https://bugs.kde.org/show_bug.cgi?id=368227 Bug ID: 368227 Summary: plasma crashed suddenly Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vkr...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.7.4) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Waiting for a copy of several files to a SMB share to complete -- Backtrace: attached. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Selected 3 local files in dolphin, right-clicked and selected Cut. 2. Navigated to a samba share via Places. 3. Right clicked, selected "Paste 3 items". Actual Results: Plasma crashed during the file copy. Expected Results: No crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368200] Crash somewhere in taskbar on desktop switching
https://bugs.kde.org/show_bug.cgi?id=368200 Christoph Feck changed: What|Removed |Added Product|kde |plasmashell CC||bhus...@gmail.com, ||plasma-b...@kde.org Component|general |general Target Milestone|--- |1.0 Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk Version|unspecified |master -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 337806] Unable to click on links in "invitations" encrypted with GnuPG
https://bugs.kde.org/show_bug.cgi?id=337806 --- Comment #6 from Laurent Montel --- Perhaps the method to encrypt it :) -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 368204] plasma-desktop crashes on startup after an update
https://bugs.kde.org/show_bug.cgi?id=368204 Christoph Feck changed: What|Removed |Added Assignee|notm...@gmail.com |plasma-b...@kde.org Product|frameworks-plasma |plasma4 Component|libplasma |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368226] KRunner and the application launcher show on the secondary screen
https://bugs.kde.org/show_bug.cgi?id=368226 --- Comment #2 from Dan Dascalescu --- Created attachment 100921 --> https://bugs.kde.org/attachment.cgi?id=100921&action=edit Krunner appears on the secondary screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368226] KRunner and the application launcher show on the secondary screen
https://bugs.kde.org/show_bug.cgi?id=368226 Dan Dascalescu changed: What|Removed |Added CC||ddascalescu+...@gmail.com --- Comment #1 from Dan Dascalescu --- Created attachment 100920 --> https://bugs.kde.org/attachment.cgi?id=100920&action=edit Application Launcher appears on the secondary monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368226] New: KRunner and the application launcher show on the secondary screen
https://bugs.kde.org/show_bug.cgi?id=368226 Bug ID: 368226 Summary: KRunner and the application launcher show on the secondary screen Product: plasmashell Version: 5.6.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: ddascalescu+...@gmail.com CC: plasma-b...@kde.org When I press Alt+Space, I expect Krunner to display on my primary monitor; especially if that screen has received user input. Same for pressing the Super key (I've installed ksuperkey) - I expect the launcher to appear on the primary monitor. Reproducible: Always Steps to Reproduce: 1. Connect laptop to external monitor. 2. In Display Configuration, ensure that HDMI1 is the primary display 3. Disconnect the laptop and go work at a coffee shop for a while. 4. Connect the laptop again to the same monitor. 5. Press Alt+Space and type something 6. Press the Super key Actual Results: Krunner's input box appears at (0, 0) on the secondary monitor, and the Application Launcher appears at (MAX_X, 0) on the secondary monitor. Expected Results: Krunner should appear in the top center of the primary display, and the launcher in the bottom left. -- You are receiving this mail because: You are watching all bug changes.
[KDE Config Driver Manager] [Bug 368225] New: Driver management software is collecting information forever
https://bugs.kde.org/show_bug.cgi?id=368225 Bug ID: 368225 Summary: Driver management software is collecting information forever Product: KDE Config Driver Manager Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sit...@kde.org Reporter: ddascalescu+...@gmail.com I've run Driver Manager in hopes of updating my video drivers and eliminating tearing. The problem is that it never finishes collecting information (I've left it running for over an hour), and there's no clear progress indicator. I have no idea if it does anything at all. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[KDE Config Driver Manager] [Bug 368225] Driver management software is collecting information forever
https://bugs.kde.org/show_bug.cgi?id=368225 --- Comment #1 from Dan Dascalescu --- Created attachment 100919 --> https://bugs.kde.org/attachment.cgi?id=100919&action=edit Is this a progress indicator of some sort? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 368190] "Update Stock and Currency Prices" doesn't work when base currency is South Korean Won(KRW)
https://bugs.kde.org/show_bug.cgi?id=368190 Yeohwan Yoon changed: What|Removed |Added CC|yoon0...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368224] In Dolphin's Compact and Details view, my Documents folder looks like a plain document
https://bugs.kde.org/show_bug.cgi?id=368224 --- Comment #1 from skierpage --- Created attachment 100918 --> https://bugs.kde.org/attachment.cgi?id=100918&action=edit My home folder in Dolphin with Breeze Note how Documents looks like a plain document. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368224] New: In Dolphin's Compact and Details view, my Documents folder looks like a plain document
https://bugs.kde.org/show_bug.cgi?id=368224 Bug ID: 368224 Summary: In Dolphin's Compact and Details view, my Documents folder looks like a plain document Product: Breeze Version: 5.6.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: skierp...@gmail.com CC: kain...@gmail.com In Dolphin using the Breeze default Plasma 5 theme, I stumbled over my ~/Documents folder. I realized the reason I scan past it is in Details view (and Compact view), its icon is that of a plain document. In Icons views your Documents folder is an emblem on top of a folder, but in the Compact and Details you only see the emblem. This works for other special folders such as Home, Music, and Pictures because their emblems look distinctive, but not so well for Documents. Reproducible: Always Steps to Reproduce: 1. Set your theme to Breeze 2. Start Dolphin 3. Navigate to ~ (your home directory) 4. Set View > View Mode to Details or Compact Actual Results: The Documents folder icon looks the same as a regular unrecognized file's icon (foo.bar, foo.doc, etc.) Expected Results: Maybe add an outline ( ⌟ ) to indicate a stack of documents. The icon for your Documents folder is actually slightly different than a plain foo.bar file, the document has a darker outline. But it's too subtle. Fedora F24 KDE spin (with the package breeze-icon-theme 5.25.0.1) has the same behavior. FWIW https://specifications.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html#names calls for "emblem-documents: The icon used as an emblem for the directory where a user's documents are stored." In general Breeze looks great, thanks! -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 364140] Product search without wildcards doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=364140 Dan Dascalescu changed: What|Removed |Added CC||ddascalescu+...@gmail.com --- Comment #2 from Dan Dascalescu --- Created attachment 100917 --> https://bugs.kde.org/attachment.cgi?id=100917&action=edit Search only works for prefixes This isn't a "nice to have" nowadays. It's a key feature and its lack keeps hurting users. I wasted a bunch of time trying to file a bug against plasmashell was was made fun of because I couldn't find the product. See bug 368176 and https://forum.kde.org/viewtopic.php?f=289&t=135101&p=363323#p363306 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368223] New: KDE crash after reboot
https://bugs.kde.org/show_bug.cgi?id=368223 Bug ID: 368223 Summary: KDE crash after reboot 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: u...@flanagan-consulting.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: After seeing cursor hesitate to start and pause for a second or two irratically, rebooted (to clear any memory leak). Closed KDE wallet window (not used). Closed p/w window for Wi-Fi (not used at this time, on wired LAN). Then crash. - Unusual behavior I noticed: Hesitation in the cursor movement, which is really annoying. Makes it hard to select. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbf508d67c0 (LWP 1460))] Thread 7 (Thread 0x7fbe886dc700 (LWP 1740)): #0 0x7ffcc60ceb26 in clock_gettime () #1 0x7fbf49de8c7d in clock_gettime () from /lib64/libc.so.6 #2 0x7fbf4a57f7d6 in qt_clock_gettime (ts=0x7fbe886dbb60, clock=) at tools/qelapsedtimer_unix.cpp:105 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #5 0x7fbf4a6ff3b9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fbe80002cd0) at kernel/qtimerinfo_unix.cpp:84 #6 0x7fbf4a6ff945 in QTimerInfoList::timerWait (this=0x7fbe80002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #7 0x7fbf4a700b5e in timerSourcePrepareHelper (timeout=0x7fbe886dbc14, src=) at kernel/qeventdispatcher_glib.cpp:127 #8 timerSourcePrepare (source=, timeout=0x7fbe886dbc14) at kernel/qeventdispatcher_glib.cpp:160 #9 0x7fbf464b04ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7fbf464b0d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7fbf464b0f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7fbf4a700d8b in QEventDispatcherGlib::processEvents (this=0x7fbe88c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #13 0x7fbf4a6a7d53 in QEventLoop::exec (this=this@entry=0x7fbe886dbdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #14 0x7fbf4a4c961a in QThread::exec (this=) at thread/qthread.cpp:503 #15 0x7fbe89d29cf7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #16 0x7fbf4a4ce32f in QThreadPrivate::start (arg=0x2d563d0) at thread/qthread_unix.cpp:331 #17 0x7fbf495dd0a4 in start_thread () from /lib64/libpthread.so.0 #18 0x7fbf49ddc02d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fbe9771d700 (LWP 1497)): #0 0x7ffcc60ceb26 in clock_gettime () #1 0x7fbf49de8c7d in clock_gettime () from /lib64/libc.so.6 #2 0x7fbf4a57f7d6 in qt_clock_gettime (ts=0x7fbe9771cb40, clock=) at tools/qelapsedtimer_unix.cpp:105 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #5 0x7fbf4a6ff3b9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fbe90002ed0) at kernel/qtimerinfo_unix.cpp:84 #6 0x7fbf4a6ff945 in QTimerInfoList::timerWait (this=0x7fbe90002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #7 0x7fbf4a700b5e in timerSourcePrepareHelper (timeout=0x7fbe9771cbf4, src=) at kernel/qeventdispatcher_glib.cpp:127 #8 timerSourcePrepare (source=, timeout=0x7fbe9771cbf4) at kernel/qeventdispatcher_glib.cpp:160 #9 0x7fbf464b04ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7fbf464b0d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7fbf464b0f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7fbf4a700d8b in QEventDispatcherGlib::processEvents (this=0x7fbe98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #13 0x7fbf4a6a7d53 in QEventLoop::exec (this=this@entry=0x7fbe9771cdb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #14 0x7fbf4a4c961a in QThread::exec (this=) at thread/qthread.cpp:503 #15 0x7fbf4e379282 in ?? () from /usr/lib64/libQt5Quick.so.5 #16 0x7fbf4a4ce32f in QThreadPrivate::start (arg=0x2228d60) at thread/qthread_unix.cpp:331 #17 0x7fbf495dd0a4 in start_thread () from /lib64/libpthread.so.0 #18 0x7fbf49ddc02d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fbf1ef31700 (LWP 1488)): #0 0x7fbf495e103f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbf4ffac86b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fbf4ffac899 in ?? () from /usr/lib64/libQt5Script.so.
[kwin] [Bug 368222] New: KDE hangs when VLC or dragon plays video
https://bugs.kde.org/show_bug.cgi?id=368222 Bug ID: 368222 Summary: KDE hangs when VLC or dragon plays video Product: kwin Version: 5.6.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: daniel.armbrust.l...@gmail.com Much like some of the details in https://bugs.kde.org/show_bug.cgi?id=338999, I can consistently make the entire KDE desktop hang, simply by playing a video in VLC, or the Dragon Video player - currently running 5.6.5 of plasma, 5.23.0 of kde frameworks. I'm using the NVidia binary driver at version 367.35. I'm currently using the OpenGL 2.0 rendring backend, with the GLX interface - have tried OpenGL 3.1 - doesn't seem to make any difference. I have stable hardware - I was running the 14.04 LTS edition (with whatever version of KDE is included) for a long period of time with no issues. After making the (mistake) to upgrade to 16.04 LTS, KDE is nearly unusable on a multi-monitor system. I'm aware of https://bugs.kde.org/show_bug.cgi?id=346961 and hoping that the claimed fixes in 5.8 finally fix that mess (but still waiting for a way to easily get 5.8 onto this ubuntu system - doesn't seem to be any packages for ubuntu yet...) This issue, is that anytime I open VLC 2.2.2, upon playing a video for a while - the entire KDE desktop will hang. The hang can be made to happen sooner by jumping around in the video - it happens within seconds. The only recovery is to Ctrl+Alt F key to another terminal (and even that usually takes 30+ seconds to respond) and then kill -9 VLC. Dragon player seems to behave even worse - launching that player typically causes my desktop to instantly forget that it has 3 monitors - reconfiguring itself in a mode where all 3 of my monitors are set to mirror, and their resolution is set to a very low value. The Totem video player seems to work ok - so it would seem to be tied to whatever technique VLC and Dragon have in common for handling video. Happy to provide any useful debug info, or other information, as I can reproduce the problem at will. Reproducible: Always Steps to Reproduce: 1.Launch VLC - leave windowed. 2. Jump forward and back in the video. 3. Sometimes the video just freezes in VLC. Most times, the entire KDE desktop hangs - can't even move the mouse. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 368213] mediaframe: Cannot change Fill mode
https://bugs.kde.org/show_bug.cgi?id=368213 m_loui...@yahoo.com changed: What|Removed |Added CC||m_loui...@yahoo.com --- Comment #1 from m_loui...@yahoo.com --- I can confirm this on Arch Linux and Plasma 5.7.4. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 368221] New: Unable to adjust display brightness on Dell laptop, powerdevil messages in journalctl
https://bugs.kde.org/show_bug.cgi?id=368221 Bug ID: 368221 Summary: Unable to adjust display brightness on Dell laptop, powerdevil messages in journalctl Product: Powerdevil Version: 5.7.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: jamiesexto...@gmail.com This seems to be a bug with either the Powerdevil configuration but looks related to the Xorg driver, I had previously added this but should have reported properly instead of just on the ubuntu bugtracker https://bugs.launchpad.net/bugs/1503168. I haven't tried that fix yet with the latest Manjaro but it does also apply as well with both Kubuntu 16.10 and Manjaro with all updates including the Intel DRM nightly drivers from git. This seems to affect multiple types of Dell laptops also including the Studio 1737 and N7010 (both about 10 years old) and both with integrated Intel HD graphics. The Kubuntu install is since Alpha release, and the Manjaro install since 8/15 and is running 4.8.0-rc4-mainline as well. Appears the issue has resurfaced since the KDE 5.x branch. Will add additional bug report from Kubuntu 16.10 as well for secondary verification and information reporting Reproducible: Always Steps to Reproduce: 1.Use the function keys to adjust brightness 2.Watch the brightness bar go from none to full and back Actual Results: End result, no change in display brightness but does log some journalctl error messages when checking with `journalctl -xe --no-pager|grep -C10 bright` Expected Results: screen backlight brightness should have changed inxi -SG ``` System:Host: Manjaro-N7010 Kernel: 4.8.0-rc4-mainline x86_64 (64 bit) Desktop: KDE Plasma 5 Distro: Manjaro Linux Graphics: Card: Intel Core Processor Integrated Graphics Controller Display Server: X.Org 1.17.4 driver: intel Resolution: 1600x900@60.28hz GLX Renderer: Mesa DRI Intel Ironlake Mobile GLX Version: 2.1 Mesa 12.0.1 ``` Latest KDE frameworks and version from Manjaro kdeinit5 --version ``` Qt: 5.7.0 KDE: 5.25.0 ``` journalctl --no-pager -u user@1000.service ``` Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Output: 66 Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Property: Backlight Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: State (newValue, Deleted): 0 Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Output: 66 Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Property: Backlight Sep 03 18:48:40 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.help ``` Manjaro-N7010 ~]$ journalctl -xe --no-pager|grep -C10 bright | tail -30 ``` Sep 03 18:58:01 Manjaro-N7010 kdeinit5[793]: powerdevil: Brightness changed!! Sep 03 18:58:01 Manjaro-N7010 kdeinit5[793]: powerdevil: Screen brightness value max: 15 Sep 03 18:58:01 Manjaro-N7010 kdeinit5[793]: powerdevil: Screen brightness value: 5 Sep 03 18:58:01 Manjaro-N7010 kdeinit5[793]: powerdevil: Brightness changed!! Sep 03 18:58:02 Manjaro-N7010 kdeinit5[793]: powerdevil: Screen brightness value: 5 Sep 03 18:58:02 Manjaro-N7010 kdeinit5[793]: powerdevil: Screen brightness value max: 15 Sep 03 18:58:02 Manjaro-N7010 kdeinit5[793]: powerdevil: set screen brightness value: 6 Sep 03 18:58:02 Manjaro-N7010 kdeinit5[793]: powerdevil: Screen brightness value max: 15 Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Output: 66 Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Property: Backlight Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: State (newValue, Deleted): 0 Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Output: 66 Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: Property: Backlight Sep 03 18:58:02 Manjaro-N7010 kscreen_backend_launcher[881]: kscreen.xcb.helper: State (newValue, Deleted): 0 Sep 03 18:58:02 Manjaro-N7010 kdeinit5[793]: powerdevil: Screen brightness value: 6 Sep 03 18:58:02 Manjaro-N7010 kdeinit5[793]: powerdevil: Brightness changed!! Se
[kapman] [Bug 366685] All dots have been eaten but next level does not begin. Stuck
https://bugs.kde.org/show_bug.cgi?id=366685 veralee changed: What|Removed |Added Severity|wishlist|major -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 366685] All dots have been eaten but next level does not begin. Stuck
https://bugs.kde.org/show_bug.cgi?id=366685 --- Comment #4 from veralee --- (In reply to veralee from comment #3) > I'd classify this as a UI bug. > I later found that the color of the dots and the background are so close in > one area of gameplay (lower left) that it is very difficult to determine if > dots are present. > > I see from my attachment that the dots are there but I did not see them. Update: I recreated the bug... it's not a UI issue. It really does get stuck with no dots left. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 368219] Marble master f52af133e3f8 build error of shp2pn2_automoc.cpp (gcc 4.8)
https://bugs.kde.org/show_bug.cgi?id=368219 --- Comment #2 from Jarosław Staniek --- BTW, Builds with gcc 4.9.2 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 368219] Marble master f52af133e3f8 build error of shp2pn2_automoc.cpp (gcc 4.8)
https://bugs.kde.org/show_bug.cgi?id=368219 Jarosław Staniek changed: What|Removed |Added Summary|Marble master f52af133e3f8 |Marble master f52af133e3f8 |build error of |build error of |shp2pn2_automoc.cpp |shp2pn2_automoc.cpp (gcc ||4.8) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368047] Clone Tool acts weird after a brush resize
https://bugs.kde.org/show_bug.cgi?id=368047 aferguson1...@gmail.com changed: What|Removed |Added CC||aferguson1...@gmail.com --- Comment #1 from aferguson1...@gmail.com --- Having the same issue on Windows 10. After resizing the Clone or Heal brush all of the options under 'Painting Mode' get unchecked and can't be reactivated. Unchecking 'Source point move' causes the behavior described above. It's the same if you use [] or Shift dragging to resize the brush. Krita 3.0 just crashes entirely when using the clone or heal tool. Krita version: krita_3.0.99.91 OS: Windows 10 Version 1607 (OS Build 14393.82) GPU: NVIDIA GeForce GTX 960M GPU Driver: 372.70 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368220] New: Animated GIFs don't play
https://bugs.kde.org/show_bug.cgi?id=368220 Bug ID: 368220 Summary: Animated GIFs don't play Product: okular Version: 0.24.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Image backend components Assignee: okular-de...@kde.org Reporter: ddascalescu+...@gmail.com Chrome plays the GIF just fine. Reproducible: Always Steps to Reproduce: 1. Download this GIF, http://i.imgur.com/YCWIve2.gif 2. Open it in Okular Actual Results: Only the first frame of the GIF is displayed Expected Results: Animate the GIF -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 368219] Marble master f52af133e3f8 build error of shp2pn2_automoc.cpp
https://bugs.kde.org/show_bug.cgi?id=368219 Jarosław Staniek changed: What|Removed |Added Platform|Other |openSUSE RPMs --- Comment #1 from Jarosław Staniek --- (opensuse 13.2) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368215] Air style missing for per-window progress indicator
https://bugs.kde.org/show_bug.cgi?id=368215 Eike Hein changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Flags||VisualDesign+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364227] The Super (Windows) key should launch Kickoff, like most other DEs
https://bugs.kde.org/show_bug.cgi?id=364227 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #4 from Rex Dieter --- This is a free software project, whose contributors are primarily volunteers. Questioning motives or any perceived lack of priorities is not constructive. Please have a look at https://www.kde.org/code-of-conduct/ and reflect what you wrote. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 368219] New: Marble master f52af133e3f8 build error of shp2pn2_automoc.cpp
https://bugs.kde.org/show_bug.cgi?id=368219 Bug ID: 368219 Summary: Marble master f52af133e3f8 build error of shp2pn2_automoc.cpp Product: marble Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: stan...@kde.org Hello, I'm getting marble master f52af133e3f8 build error of shp2pn2_automoc.cpp as below. gcc version 4.8.3 20140627 [ 92%] Building CXX object tools/shp2pn2/CMakeFiles/shp2pn2.dir/shp2pn2_automoc.cpp.o In file included from /usr/include/c++/4.8/algorithm:62:0, from /usr/include/qt5/QtCore/qglobal.h:88, from /usr/include/qt5/QtCore/qalgorithms.h:37, from /usr/include/qt5/QtCore/qvector.h:37, from /usr/include/qt5/QtCore/QVector:1, from /home/jarek/dev/src/marble/src/lib/marble/geodata/data/GeoDataLineString.h:16, from /home/jarek/dev/src/marble/src/lib/marble/geodata/data/GeoDataLinearRing.h:17, from /home/jarek/dev/src/marble/tools/osm-simplify/BaseClipper.h:16, from /home/jarek/dev/src/marble/tools/osm-simplify/BaseClipper.cpp:13: /usr/include/c++/4.8/bits/stl_algo.h: In instantiation of ‘_RandomAccessIterator std::__unguarded_partition(_RandomAccessIterator, _RandomAccessIterator, const _Tp&, _Compare) [with _RandomAccessIterator = QList >::iterator; _Tp = QSharedPointer; _Compare = Marble::BaseClipper::clipPolyObject(const QPolygonF&, QVector&, bool)::__lambda1]’: /usr/include/c++/4.8/bits/stl_algo.h:2296:78: required from ‘_RandomAccessIterator std::__unguarded_partition_pivot(_RandomAccessIterator, _RandomAccessIterator, _Compare) [with _RandomAccessIterator = QList >::iterator; _Compare = Marble::BaseClipper::clipPolyObject(const QPolygonF&, QVector&, bool)::__lambda1]’ /usr/include/c++/4.8/bits/stl_algo.h:2337:62: required from ‘void std::__introsort_loop(_RandomAccessIterator, _RandomAccessIterator, _Size, _Compare) [with _RandomAccessIterator = QList >::iterator; _Size = int; _Compare = Marble::BaseClipper::clipPolyObject(const QPolygonF&, QVector&, bool)::__lambda1]’ /usr/include/c++/4.8/bits/stl_algo.h:5490:44: required from ‘void std::sort(_RAIter, _RAIter, _Compare) [with _RAIter = QList >::iterator; _Compare = Marble::BaseClipper::clipPolyObject(const QPolygonF&, QVector&, bool)::__lambda1]’ /home/jarek/dev/src/marble/tools/osm-simplify/BaseClipper.cpp:454:14: required from here /usr/include/c++/4.8/bits/stl_algo.h:2263:35: error: no match for call to ‘(Marble::BaseClipper::clipPolyObject(const QPolygonF&, QVector&, bool)::__lambda1) (QSharedPointer&, const QSharedPointer&)’ while (__comp(*__first, __pivot)) ^ /home/jarek/dev/src/marble/tools/osm-simplify/BaseClipper.cpp:452:74: note: candidates are: std::sort(intersectionsTop.begin(), intersectionsTop.end(), [](QSharedPointer& A, QSharedPointer& B) { Reproducible: Always Steps to Reproduce: Make libshp1 available, configure, build. Actual Results: Build break Expected Results: Builds, installs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 fl...@mailoo.org changed: What|Removed |Added CC||fl...@mailoo.org --- Comment #3 from fl...@mailoo.org --- I can confirm this bug on openSUSE Tumbleweed. Also with an Owncloud calendar (I disabled "sync only XX months" option in Akonadi so this is a large calendar, but the memory imprint --memory filled on a 8Go RAM system-- cannot be explained by this alone). I also confirms that the system becomes unusable due to the memory being filled. Maybe a memory leak somewhere? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368218] New: cursor not accurate on rtl language like persian and arabic
https://bugs.kde.org/show_bug.cgi?id=368218 Bug ID: 368218 Summary: cursor not accurate on rtl language like persian and arabic Product: kate Version: 16.04.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: zahir.i1...@gmail.com in occasion like when copy and paste a rtl language text like persian in kate, cursor not accurate and it seem always one character behind where it is. for example when i put cursor between ش and خ in word مشخص , and press delete, i expect to delete خ but in reality its delete letter ص. Reproducible: Always Steps to Reproduce: 1. copy any persian or arabic language text and paste it in kate. 2. put cursor on a word. 3. press delete or space button. Actual Results: kate delete or put space one character ahead of where cursor is. for example when i put cursor between ش and خ in word مشخص , and press delete, its delete letter ص. Expected Results: when i put cursor between ش and خ in word مشخص , and press delete, i expect to delete خ instead of ص. -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 366685] All dots have been eaten but next level does not begin. Stuck
https://bugs.kde.org/show_bug.cgi?id=366685 veralee changed: What|Removed |Added Severity|normal |wishlist --- Comment #3 from veralee --- I'd classify this as a UI bug. I later found that the color of the dots and the background are so close in one area of gameplay (lower left) that it is very difficult to determine if dots are present. I see from my attachment that the dots are there but I did not see them. -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 368217] Error while eating treats causes massive increase of score
https://bugs.kde.org/show_bug.cgi?id=368217 --- Comment #2 from veralee --- Notice score of over 100,000 at level 4. I think you can determine this should not be mathematically possible given how the game is designed. -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 368217] Error while eating treats causes massive increase of score
https://bugs.kde.org/show_bug.cgi?id=368217 --- Comment #1 from veralee --- Created attachment 100916 --> https://bugs.kde.org/attachment.cgi?id=100916&action=edit Screenshot of score just after hitting this erroneous jackpot -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 368217] New: Error while eating treats causes massive increase of score
https://bugs.kde.org/show_bug.cgi?id=368217 Bug ID: 368217 Summary: Error while eating treats causes massive increase of score Product: kapman Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: tg8...@yahoo.fr Reporter: d...@ravennasprings.com CC: kde-games-b...@kde.org While playing the game, occasionally, the treat pop-up just below the center of the screen becomes broken allowing for the user to pass over it dozens of times which causes the score to go through the roof. Reproducible: Sometimes Steps to Reproduce: 1. run over the treat when it pops up 2. return and run over the treat again as it does not disappear 3. repeat Actual Results: The score goes ballistic Expected Results: The treat should disappear after running over it to collect the bonus. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 368006] Download progress halts with OSM
https://bugs.kde.org/show_bug.cgi?id=368006 Giuseppe Calà changed: What|Removed |Added CC||jive...@gmail.com --- Comment #1 from Giuseppe Calà --- Confirming with Marble 2.0.0: Chakra KDE Frameworks 5.25.0 Qt 5.7.0 (built against 5.7.0) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 368176] The bug tracker asks me to file Plasma 5 bugs in "plasmashell", which doesn't exist
https://bugs.kde.org/show_bug.cgi?id=368176 Dan Dascalescu changed: What|Removed |Added CC||ddascalescu+...@gmail.com --- Comment #3 from Dan Dascalescu --- Created attachment 100915 --> https://bugs.kde.org/attachment.cgi?id=100915&action=edit "plasmashell" not found when searching in descriptions Actually, please reopen the ticket. "plasmashell" isn't found when searching for "plasma" among the descriptions. It's only found when searching in the product list. Please see the attached screencast. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368216] New: Switch to open windows using Super/Meta/Windows key + 0..9 digits/numbers
https://bugs.kde.org/show_bug.cgi?id=368216 Bug ID: 368216 Summary: Switch to open windows using Super/Meta/Windows key + 0..9 digits/numbers Product: plasmashell Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Window List Assignee: plasma-de...@kde.org Reporter: ddascalescu+...@gmail.com This is especially handy if you often switch among the same few apps, e.g. a browser, a file manager and an editor, but also have other apps open, so Alt+Tabbing to the desired window would take more time.[1] That keyboard shortcut saves me probably 5 seconds per minute on the average, so ~40 minutes a day, and it's supported by Unity and Windows 7 as well. Adding custom keyboard shortcuts for the app doesn't work, because pressing the shortcut will launch a new instance of the app.[2] Adding Meta+1/2/3... via the window menu -> More Actions -> Window shortcut works, but there are two annoying problems: 1. The shortcut is forgotten when the window is closed, and you have to configure it again 2. If the app isn't running, the OS won't launch it for you. In Windows, you can launch the app that way. [1]: KDE will order the most frequently used windows first, but you have to first look and see how many times you have to press Alt+Tab; while with Super+1 or Super+2, you always know which shortcut goes to one app or the other. [2]: Some apps have an option to allow only one instance, but this is the exception rather than the rule, and even in that case, there will be a noticeable flicker of launching the new instance and seeing it exiting immediately. Reproducible: Always Demand for this feature: * Windows supports it * Unity supports it * Cinnamon users want it - https://github.com/linuxmint/Cinnamon/issues/5561 * http://askubuntu.com/questions/813262/which-desktop-environments-allow-switching-among-windows-with-supernumbers * I've placed a $100 bounty on it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368215] Air style missing for per-window progress indicator
https://bugs.kde.org/show_bug.cgi?id=368215 --- Comment #1 from Dainius Masiliūnas --- Created attachment 100914 --> https://bugs.kde.org/attachment.cgi?id=100914&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368215] New: Air style missing for per-window progress indicator
https://bugs.kde.org/show_bug.cgi?id=368215 Bug ID: 368215 Summary: Air style missing for per-window progress indicator Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: past...@gmail.com CC: plasma-b...@kde.org When the panel is set to use the Air style, and a program uses the progress indicor functionality for its entry in the task manager, a fallback style (same as cutoff mouse-over) is used for it. See attached image. Reproducible: Always Steps to Reproduce: 1. Set the desktop style to Air 2. Launch Kdenlive or some other application that makes use of progress tracking 3. Start a task Actual Results: The progress indicator in unclear and cut off. Expected Results: The progress indicator should have a style that makes it obvious that it is a progress indicator. This might also apply to the Oxygen theme (the dark variant of Air), I haven't checked yet. I'm also not entirely sure if this should be filed under plasmashell/task manager, or Oxygen, since it's the intersection of both. I'm using openSUSE Tumbleweed, Plasma 5.7.4. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368150] Kontact crashes when email is moved to a folder
https://bugs.kde.org/show_bug.cgi?id=368150 Lukasz changed: What|Removed |Added CC||dolo...@outlook.com --- Comment #1 from Lukasz --- I was able to reproduce this crash when deleting emails. I guess deleting is like moving to a trash. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%
https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #2 from Kurt Hindenburg --- Git commit 07cbdbcd128781fe77d78533436ef2172dcc5993 by Kurt Hindenburg. Committed on 03/09/2016 at 21:34. Pushed by hindenburg into branch 'Applications/16.08'. Change the default to not underline links Set UnderlineLinksEnabled to false for now. Users can alway enable in profile settings. M +1-1src/Profile.cpp http://commits.kde.org/konsole/07cbdbcd128781fe77d78533436ef2172dcc5993 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #9 from Eike Hein --- Thanks for your reports, hopefully we get to fixing this soon. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 368086] KDE 5
https://bugs.kde.org/show_bug.cgi?id=368086 --- Comment #2 from Kurt Hindenburg --- It doesn't look like debug symbols are enabled so the attached is very helpful - can you describe what happened and if you can reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 340813] sometimes two copies of mysqld are running with Akonadi
https://bugs.kde.org/show_bug.cgi?id=340813 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de --- Comment #9 from Christian Saemann --- I'm not sure if this helps, but I also run into situations where Akonadi seems to initiate two mysqld processes. This is with the latest KDE packages (16.08) from openSUSE Tumbleweed. The first one is just after startup, I can often read and browse emails for 10 seconds or so, then kmail says akonadi is not running properly. I then have to killall mysqld and restart akonadi. The second one, and this happens reliably each time, is when I initiate an email search, having deleted all prior search folders. Kmail states that it can't connect to akonadi-service, and stops working properly. After this, I always have two mysqld processes running. akonadiserver.error.old contains just one line: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) If there's any additional specific error logs or debug information you'd like to see, just let me know. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 --- Comment #5 from caulier.gil...@gmail.com --- Marble is also a stand alone application to study world maps. digiKam only use a shared widget from this application. Install marble application on your computer and run it with OSM map. If it crash too, the problem is definitively in Marble code (that i suspect in fact)... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 Hans-Peter changed: What|Removed |Added CC||hans...@web.de --- Comment #4 from Hans-Peter --- I can confirm what Jens wrote, exactly the same behavior on my machine. I have Marble with OSM enabled. HP -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368214] New: FEATURE REQUEST: Notification custom size, look and location
https://bugs.kde.org/show_bug.cgi?id=368214 Bug ID: 368214 Summary: FEATURE REQUEST: Notification custom size, look and location Product: plasmashell Version: master Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Notifications Assignee: mklape...@kde.org Reporter: ttv...@gmail.com CC: plasma-b...@kde.org Add option to: - change the location of notification (which corner and how close to the corner) - change the size of notification. the size of the header, text, padding - change the transparency of notification thanks Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 368213] New: mediaframe: Cannot change Fill mode
https://bugs.kde.org/show_bug.cgi?id=368213 Bug ID: 368213 Summary: mediaframe: Cannot change Fill mode Product: kdeplasma-addons Version: 5.7.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: aspotas...@gmail.com When I open mediaframe configuration dialog, Fill mode is always set to "Preserve aspect fit". If I change it to something else, I cannot apply the change. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 352346] Description and options for Hunyango and Haenau wallpaper types are missing
https://bugs.kde.org/show_bug.cgi?id=352346 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 368086] KDE 5
https://bugs.kde.org/show_bug.cgi?id=368086 --- Comment #1 from Yura Shevhuk --- Created attachment 100913 --> https://bugs.kde.org/attachment.cgi?id=100913&action=edit add fille info for new crach console -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368211] crashes after start
https://bugs.kde.org/show_bug.cgi?id=368211 Andrius Štikonas changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- KDE Partition Manager 1.0.3 is simply too old (6 years since the release). Please upgrade to newer version, e.g. 2.2.1. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368212] New: The process for the file protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=368212 Bug ID: 368212 Summary: The process for the file protocol died unexpectedly Product: dolphin Version: 4.14.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jc_yeahri...@hotmail.com Application: dolphin (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.1 Operating System: Linux 3.2.0-109-generic x86_64 Distribution: Ubuntu 12.04.5 LTS -- Information about the crash: - What I was doing when the application crashed: I was browsing folders and subfolders, and opening files with kate. I was not able to reproduce it. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5369844780 (LWP 21601))] Thread 3 (Thread 0x7f534ec79700 (LWP 21676)): #0 0x7f53609c2f69 in __pthread_mutex_lock (mutex=0x7f5348000a60) at pthread_mutex_lock.c:92 #1 0x7f536052f5b1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f53604f3635 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f53604f3f1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f53604f4124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f53650fe426 in QEventDispatcherGlib::processEvents (this=0x7f53480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f53650cdc82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f53650cded7 in QEventLoop::exec (this=0x7f534ec78dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f5364fccfa7 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f53650af5a8 in QDnotifySignalThread::run (this=0x2098460) at io/qfilesystemwatcher_dnotify.cpp:179 #10 0x7f5364fcffcb in QThreadPrivate::start (arg=0x2098460) at thread/qthread_unix.cpp:298 #11 0x7f53609c0e9a in start_thread (arg=0x7f534ec79700) at pthread_create.c:308 #12 0x7f536910336d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 2 (Thread 0x7f534df95700 (LWP 21765)): #0 0x7f53690f5f4d in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f536052e8df in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f53604f3b64 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f53604f3f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f53604f4124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f53650fe426 in QEventDispatcherGlib::processEvents (this=0x7f5348c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f53650cdc82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f53650cded7 in QEventLoop::exec (this=0x7f534df94e00, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f5364fccfa7 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f5364fcffcb in QThreadPrivate::start (arg=0x1ff5470) at thread/qthread_unix.cpp:298 #10 0x7f53609c0e9a in start_thread (arg=0x7f534df95700) at pthread_create.c:308 #11 0x7f536910336d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7f5369844780 (LWP 21601)): [KCrash Handler] #6 0x7f5369046035 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f536904979b in __GI_abort () at abort.c:91 #8 0x7f536908322e in __libc_message (do_abort=2, fmt=0x7f536918b15a "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201 #9 0x7f5369119e37 in __GI___fortify_fail (msg=0x7f536918b0f1 "buffer overflow detected") at fortify_fail.c:32 #10 0x7f5369118d30 in __GI___chk_fail () at chk_fail.c:29 #11 0x7f5369119dee in __fdelt_chk (d=) at fdelt_chk.c:26 #12 0x7f53650a94d4 in QProcessPrivate::waitForStarted (this=, msecs=3) at io/qprocess_unix.cpp:1038 #13 0x7f53650644c3 in QProcess::waitForFinished (this=0x7ffe4e39fe10, msecs=3) at io/qprocess.cpp:1752 #14 0x7f5363c5f7d4 in Attica::ProviderManager::loadPlatformDependent(QFlags const&) () from /usr/lib/x86_64-linux-gnu/libattica.so.0.4 #15 0x7f5363c5fdf7 in Attica::ProviderManager::ProviderManager(QFlags const&) () from /usr/lib/x86_64-linux-gnu/libattica.so.0.4 #16 0x7f53667765a0 in ?? () from /usr/lib/libkdeui.so.5 #17 0x7f536677289b in KAboutApplicationDialog::Private::init(KAboutData const*, QFlags) () from /usr/lib/libkdeui.so.5 #18 0x7f5366773347 in KAboutApplicationDialog::KAboutApplicationDialog(KAboutData const*, QWidget*) () from /usr/lib/libkdeui.so.5 #19 0x7f53668b0bdf in KHelpMenu::aboutApplication() () from /usr/
[partitionmanager] [Bug 368211] New: crashes after start
https://bugs.kde.org/show_bug.cgi?id=368211 Bug ID: 368211 Summary: crashes after start Product: partitionmanager Version: 1.0.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: wettererschein...@bb-goettingen.de Application: partitionmanager-bin (1.0.3) KDE Platform Version: 4.14.23 Qt Version: 4.8.7 Operating System: Linux 4.5.0-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: I started it as root from the console and it crashed immediately. (Starting as another user graphically with kdesu doesn't work as well but thats a different bug report.) Thanks! The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager-bin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f418605e1c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f418605f64a in __GI_abort () at abort.c:89 #8 0x7f41876c2f15 in qt_message_output (msgType=, buf=0x120c8e8 "partitionmanager(9691)/kdeui (kdelibs): Session bus not found \nTo circumvent this problem try the following command (with Linux and bash) \nexport $(dbus-launch) ") at global/qglobal.cpp:2447 #9 0x7f4187d4264c in QDebug::~QDebug (this=0x7ffe0267dc10, __in_chrg=) at /usr/include/qt4/QtCore/qdebug.h:85 #10 0x7f4187d9b2ba in KApplicationPrivate::init (this=0x1169e80, GUIenabled=GUIenabled@entry=true) at ./kdeui/kernel/kapplication.cpp:516 #11 0x7f4187d9bc92 in KApplication::KApplication (this=0x7ffe0267de70, GUIenabled=true) at ./kdeui/kernel/kapplication.cpp:352 #12 0x004010e2 in ?? () #13 0x7f418604b730 in __libc_start_main (main=0x400fb0, argc=1, argv=0x7ffe0267df88, init=, fini=, rtld_fini=, stack_end=0x7ffe0267df78) at ../csu/libc-start.c:291 #14 0x004011fd in _start () Possible duplicates by query: bug 363463, bug 357541. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368210] New: New monitor isn't detected correctly, and task bar disappears after disconnecting it
https://bugs.kde.org/show_bug.cgi?id=368210 Bug ID: 368210 Summary: New monitor isn't detected correctly, and task bar disappears after disconnecting it Product: plasmashell Version: 5.5.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: ddascalescu+...@gmail.com CC: plasma-b...@kde.org I have a Dell E7450 laptop, connected via HDMI to a NEC monitor. This monitor is detected correctly in Display Configuration, and I made it the primary monitor, and moved the task bar to the bottom of that screen. Reproducible: Always Steps to Reproduce: 1. Disconnect NEC monitor 2. Connect instead Philips TV via the same HDMI cable 3. Open Display Configuration Actual Results: The NEC monitor still shows up as the connected monitor. After disconnecting the TV, and using only the laptop, the task bar is completely gone (I mean the horizontal strip including the K logo, the task bar and the system tray panels). Windows that were maximized on the TV screen are no off-screen. In this situation, Mint Cinnamon, Unity, and Windows 7 would bring the task bar onto the only display available. Some of these OSes would also reposition windows so they're at least partially visible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364227] The Super (Windows) key should launch Kickoff, like most other DEs
https://bugs.kde.org/show_bug.cgi?id=364227 --- Comment #3 from Dan Dascalescu --- Users have been complaining about this since 2009. That's 7 years ago. SEVEN YEARS. I'm sorry, but where were you guys thinking? Do you have a product manager who can set priorities based on user input? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 368142] Operations property dialog do not show source code
https://bugs.kde.org/show_bug.cgi?id=368142 --- Comment #2 from Ralf Habacker --- Git commit 6811456a28954ad5d77949f4b8e1f6bc985589f6 by Ralf Habacker. Committed on 03/09/2016 at 19:50. Pushed by habacker into branch 'master'. KF5 compile fix. Thanks to cfeck at kde.org for pointing out. M +5-0umbrello/dialogs/widgets/documentationwidget.cpp http://commits.kde.org/umbrello/6811456a28954ad5d77949f4b8e1f6bc985589f6 -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 368176] The bug tracker asks me to file Plasma 5 bugs in "plasmashell", which doesn't exist
https://bugs.kde.org/show_bug.cgi?id=368176 --- Comment #2 from Dan Dascalescu --- I can see it now as well. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 --- Comment #2 from Jens B. Benecke --- IIRC it was Marble with OSM. I don't remember ... is there any way to track it (eg. by activating more console debug output)? Which Marble standalone app should I try out? I still have the old config so I can try more debugging ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 --- Comment #3 from Jens B. Benecke --- IIRC it was Marble with OSM. I don't remember ... is there any way to track it (eg. by activating more console debug output)? Which Marble standalone app should I try out? I still have the old config so I can try more debugging ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363859] digiKam core port from QWebKit to QWebEngine [patch]
https://bugs.kde.org/show_bug.cgi?id=363859 Maik Qualmann changed: What|Removed |Added Attachment #99331|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363859] digiKam core port from QWebKit to QWebEngine [patch]
https://bugs.kde.org/show_bug.cgi?id=363859 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Created attachment 100912 --> https://bugs.kde.org/attachment.cgi?id=100912&action=edit portWebEngine.2patch Updated patch. Not yet ready for production use. QWebEngineView crashes with Nouveau driver (I use the NVidia driver for testing). Update items still not perfect, only after clicking in the view. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365904] "The process for the file protocol died unexpectedly." in all dolphin related places
https://bugs.kde.org/show_bug.cgi?id=365904 jc_yeahri...@hotmail.com changed: What|Removed |Added CC||jc_yeahri...@hotmail.com --- Comment #2 from jc_yeahri...@hotmail.com --- version 4.14.2 Error was produced while navigating folders and expanding folders. Using the up, and back buttons, using the bar to navigate. I was not able to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368207] New: Crash when moving filter mask (GDB backtrace)
https://bugs.kde.org/show_bug.cgi?id=368207 Bug ID: 368207 Summary: Crash when moving filter mask (GDB backtrace) Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com I was drawing, then moved my layerstack. Krita sefaulted. I ran this on gdb, so I have a backtrace and some terminal spam: canvas action "rotate_canvas_left" shortcut: "Ctrl+[" QAccessibleTree::indexFromLogical: invalid index: 16 0 for KisFilterTree(0x1db7a750, name="filtersSelector") Cannot creat accessible child interface for object: KisFilterTree(0x1db7a750, name = "filtersSelector") index: 17 QAccessibleTree::indexFromLogical: invalid index: 16 0 for KisFilterTree(0x1db7a750, name="filtersSelector") Cannot creat accessible child interface for object: KisFilterTree(0x1db7a750, name = "filtersSelector") index: 17 QAccessibleTree::indexFromLogical: invalid index: 16 0 for KisFilterTree(0x1db7a750, name="filtersSelector") Cannot creat accessible child interface for object: KisFilterTree(0x1db7a750, name = "filtersSelector") index: 17 QAccessibleTree::indexFromLogical: invalid index: 16 0 for KisFilterTree(0x1db7a750, name="filtersSelector") Cannot creat accessible child interface for object: KisFilterTree(0x1db7a750, name = "filtersSelector") index: 17 QAccessibleTree::indexFromLogical: invalid index: 16 0 for KisFilterTree(0x1db7a750, name="filtersSelector") Cannot creat accessible child interface for object: KisFilterTree(0x1db7a750, name = "filtersSelector") index: 17 QFSFileEngine::open: No file name specified Thread 106 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff6bfff700 (LWP 5827)] 0x75746b20 in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 (gdb) thread apply all backtrace Thread 109 (Thread 0x7fff6b7fe700 (LWP 5830)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7555c738 in QWaitCondition::wait(QMutex*, unsigned long) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #2 0x75558467 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #3 0x7555bc89 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #4 0x7fffeecee6fa in start_thread (arg=0x7fff6b7fe700) at pthread_create.c:333 #5 0x74c57b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 108 (Thread 0x7fff7b7b5700 (LWP 5829)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7555c738 in QWaitCondition::wait(QMutex*, unsigned long) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #2 0x75558467 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #3 0x7555bc89 in ?? () ---Type to continue, or q to quit--- from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #4 0x7fffeecee6fa in start_thread (arg=0x7fff7b7b5700) at pthread_create.c:333 #5 0x74c57b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 107 (Thread 0x7fff6affd700 (LWP 5828)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7555c738 in QWaitCondition::wait(QMutex*, unsigned long) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #2 0x75558467 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #3 0x7555bc89 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #4 0x7fffeecee6fa in start_thread (arg=0x7fff6affd700) at pthread_create.c:333 #5 0x74c57b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 106 (Thread 0x7fff6bfff700 (LWP 5827)): #0 0x75746b20 in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 ---Type to continue, or q to quit--- #1 0x776fbad3 in BatchMoveUpdateData::addInitialUpdate ( moveStruct=..., this=0x1d259090) at /home/krita/kde/src/krita/libs/ui/kis_node_juggler_compressed.cpp:198 #2 DuplicateLayers::populateChildCommands (this=) at /home/krita/kde/src/krita/libs/ui/kis_node_juggler_compressed.cpp:541 #3 0x72f67a87 in KisCommandUtils::AggregateCommand::redo ( this=0x1e2585a0) at /home/krita/kde/src/krita/libs/image/kis_command_utils.cpp:31 #4 0x72f2d5aa in KisStrokeStrategyUndoCommandBased::doStrokeCallback ( this=0x1a841290, data=) at /home/krita/kde/src/krita/libs/image/kis_stroke_strategy_undo_command_based.cpp:118 #5 0x73076681 in KisStrokeJob::run (this=) at /h
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #68 from CaCO3 --- I created a shell script with this content: -- #! /bin/sh killall plasmashell; plasmashell -- Then I added a link to it to the desktop. So I simply can run it when it is required. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #67 from Aliaksandr Stelmachonak --- killall plasmashell && kstart plasmashell Easier and cleaner -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #66 from Joel --- Playing with this a bit more I found this works best for me, killall plasmashell; nohup plasmashell >/dev/null 2>&1 & Now I can close the terminal when done and it does not create an ever growing nohup.out file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368209] New: Plasma crash after creating USB partition
https://bugs.kde.org/show_bug.cgi?id=368209 Bug ID: 368209 Summary: Plasma crash after creating USB partition Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dplin...@netscape.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: Created fat32 partition on USB drive using KDE Partition Manager. This may be a dup of 346517, but the crash reporting assistant did not respond properly. After indicating that my crash is related to 346517, the asistant was upset that I had not selected a related crash. I had, so it was confused. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffbb4def8c0 (LWP 3519))] Thread 12 (Thread 0x7ffad98e8700 (LWP 3862)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ffbafbfdaeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3be2a60) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4355b10, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7ffafa2d92bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7ffafa2dd4e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7ffafa2db353 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7ffbafbfc84e in QThreadPrivate::start (arg=0x433f490) at thread/qthread_unix.cpp:331 #16 0x7ffbaece96fa in start_thread (arg=0x7ffad98e8700) at pthread_create.c:333 #17 0x7ffbaf512b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7ffada0e9700 (LWP 3861)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ffbafbfdaeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3be2a60) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4355b10, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7ffafa2d92bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7ffafa2dd4e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7ffafa2db353 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7ffbafbfc84e in QThreadPrivate::start (arg=0x7ffad4003190) at thread/qthread_unix.cpp:331 #12 0x7ffbaece96fa in start_thread (arg=0x7ffada0e9700) at pthread_create.c:333 #13 0x7ffbaf512b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:1
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #65 from Joel --- typo, killall plasmashell && nohup plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #64 from Joel --- I tried this and it does seem to work. I had to add nohup so I could close the terminal window. killall pasmashell && nohup plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368208] New: Unreadable tooltips on GTK+ 2 applications
https://bugs.kde.org/show_bug.cgi?id=368208 Bug ID: 368208 Summary: Unreadable tooltips on GTK+ 2 applications Product: plasmashell Version: 5.7.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: caip...@fastmail.fm CC: bhus...@gmail.com, plasma-b...@kde.org I'm not sure what "product" to report this to because it affects any theme, not just Breeze. Tooltips are unreadable on GTK+2 applications by default. You can test it with MComix (available on the Ubuntu repositories). I tested different combinations of Plasma themes and GTK application styles. I also unchecked "Apply colors to non-QT applications" on the Color settings. The problem still persisted. The only solution I've found to this problem is commenting out these lines in ~/.config/gtkrc-2.0 : widget "gtk-tooltip" style "ToolTip" widget "gtk-tooltips" style "ToolTip" Adding # before these lines make the applications use the default tooltips of my current KDE Plasma theme. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368198] crashes after installing snap from beta channel
https://bugs.kde.org/show_bug.cgi?id=368198 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Boudewijn Rempt --- Ah, I see that you're using an Nvidia gpu -- I think that's still not supported by Ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368187] Outdated KPM 1.2.1 available in Discover
https://bugs.kde.org/show_bug.cgi?id=368187 Andrius Štikonas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Andrius Štikonas --- Yeah, unfortunately noone packages it for Kubuntu :(. Even older version is in Debian. 1.2.1 for Kubuntu was packaged by Jonathan Riddell but he now works on Neon (which by the way has much newer version of KDE Partition Manager). Try to report this bug to Kubuntu developers (probably on Launchpad)... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368206] New: Folders in project not renameable because the original string keeps reappearing
https://bugs.kde.org/show_bug.cgi?id=368206 Bug ID: 368206 Summary: Folders in project not renameable because the original string keeps reappearing Product: kdenlive Version: 16.08.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@stefannaumann.de A an project you can have folders to manage your files, for example putting audio-only-files and audio-video-files into two seperate folders. Creating a folder is easy, then renaming it is pretty hard. Upon double-click (or context-menu -> rename folder), entering some text, after some characters the old text will re-appear, deleting your changes. Unless you are very fast entering the wanted text and pressing enter it becomes nearly impossible to rename a folder or a file in the project. Reproducible: Always Steps to Reproduce: 1. Create an project, may add some files 2. Create a folder 3. Try to rename a folder or a file Actual Results: The original text keeps reappearing when renaming the file. Expected Results: The edited text stays, until I press enter for "saving" the text happens both with folders and with files. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 368205] New: Add Peruse to the KDE Neon repository
https://bugs.kde.org/show_bug.cgi?id=368205 Bug ID: 368205 Summary: Add Peruse to the KDE Neon repository Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: caip...@fastmail.fm CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org https://peruse.kde.org/ - comic book reader Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 366781] [frameworks] Implement zooming with a pinch gesture on a touch screen
https://bugs.kde.org/show_bug.cgi?id=366781 --- Comment #2 from Oliver Sander --- I managed to upload the patch to reviewboard after all: https://git.reviewboard.kde.org/r/128821/ Unlike the patch that I attached above, the one at reviewboard applies directly to the frameworks branch, and contains all necessary gesture-grabbing infrastructure. Therefore, https://git.reviewboard.kde.org/r/126809/ is not needed. Instead, the two will conflict. I'll update one as soon as the other one is committed. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 357335] gwenview crashes every time when picture is opened
https://bugs.kde.org/show_bug.cgi?id=357335 sq...@web.de changed: What|Removed |Added CC||sq...@web.de --- Comment #1 from sq...@web.de --- Happens for me too for seveeral weeks now: Actually, I can successfully start gwenview with no command line arguments. Also, the initial view of recently opened folders properly shows folder icons with image preview overlays. But on any attempt to open a JPG, a PNG or a folder or even navigating a sub folder from within gwenview, gwenview crashes within a few seconds without ever showing any images, see backtrace at the end. I just did a "zypper search -i gwenview" revealing S | Name | Summary | Type --+---+-+ i | Gwenview | A simple image viewer | application | gwenview | Simple Image Viewer for KDE | package i | gwenview5 | Simple Image Viewer for KDE | package which is a bit confusing, but since 'rpm -q Gwenview' yields "package Gwenview is not installed", hence it seems to be some kind of meta 'package' which does not matter for this bug. Possible duplicates proposed by the KDE crash assistant are bug 353841, bug 354273, bug 357992 and bug 363141. Two of them are for Ubuntu packages (hence, if this is a versioning or package dependency issue, then at least two distributions get it wrong). System info from the Gwenview help dialog is openSUSE Tumbleweed with KDE Frameworks 5.25.0 Qt 5.6.1 (kompiliert gegen 5.6.1) Das xcb Fenstersystem and only 'zypper info gwenview5' reveals the application version Repository : openSUSE:Factory Name : gwenview5 Version: 16.08.0-1.1 Arch : x86_64 Vendor : openSUSE Backtrace of crashing thread: Application: Gwenview (gwenview), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbee543c9c0 (LWP 29138))] Thread 4 (Thread 0x7fbd7c499700 (LWP 29185)): [KCrash Handler] #6 0x7fbedfcac975 in raise () at /lib64/libc.so.6 #7 0x7fbedfcadd8a in abort () at /lib64/libc.so.6 #8 0x7fbedfce83d0 in __libc_message () at /lib64/libc.so.6 #9 0x7fbedfcedbd6 in malloc_printerr () at /lib64/libc.so.6 #10 0x7fbedfcee3ae in _int_free () at /lib64/libc.so.6 #11 0x7fbee4b8d2b8 in Gwenview::JpegContent::loadFromData(QByteArray const&, Exiv2::Image*) () at /usr/lib64/libgwenviewlib.so.5 #12 0x7fbee4b5583a in () at /usr/lib64/libgwenviewlib.so.5 #13 0x7fbee4b538e1 in () at /usr/lib64/libgwenviewlib.so.5 #14 0x7fbee04525df in () at /usr/lib64/libQt5Core.so.5 #15 0x7fbee04562d8 in () at /usr/lib64/libQt5Core.so.5 #16 0x7fbed9f2c474 in start_thread () at /lib64/libpthread.so.0 #17 0x7fbedfd603ed in clone () at /lib64/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 340602] KMail puts PGP/MIME signed attachments twice into the same mail (doubling mailsize)
https://bugs.kde.org/show_bug.cgi?id=340602 --- Comment #8 from kolAflash --- Looks like this got fixed in KMail 5.1.3 but the fix wasn't backported to 4.x. At least for me the bug is gone since updating to KMail 5.1.3 and it returns when downgrading to 4.14.10. (all software used from openSUSE 42.1) Can someone confirm? If yes, feel free to set status "RESOLVED". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 368204] plasma-desktop crashes on startup after an update
https://bugs.kde.org/show_bug.cgi?id=368204 --- Comment #1 from Elmar Stellnberger (AT/K) --- Since my latest update today I can no more boot into KDE because plasma-desktop crashes every time when it has almost booted 99% and would be expected to show the desktop background. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 368204] New: plasma-desktop crashes on startup after an update
https://bugs.kde.org/show_bug.cgi?id=368204 Bug ID: 368204 Summary: plasma-desktop crashes on startup after an update Product: frameworks-plasma Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: estel...@elstel.org Application: plasma-desktop (4.11.22) KDE Platform Version: 4.14.23 Qt Version: 4.8.7 Operating System: Linux 4.8.0-rc4-ARCH-00609-g6db4082-dirty x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Plasma-Desktop-Umgebung (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f60f0d8a800 (LWP 2383))] Thread 6 (Thread 0x7f60bdc81700 (LWP 2394)): #0 0x7f60ef67210f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f60e111d79a in ?? () from /usr/lib/libQtScript.so.4 #2 0x7f60e111d7c9 in ?? () from /usr/lib/libQtScript.so.4 #3 0x7f60ef66c454 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f60ee2ee7df in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f60b7429700 (LWP 2391)): #0 0x7f60ef6724b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f60ef90e674 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f60ef9015d7 in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f60ef90e12c in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f60ef66c454 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f60ee2ee7df in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f60bfc2a700 (LWP 2390)): #0 0x7f60ef6724b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f60ef90e674 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f60ef9015d7 in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f60ef90e12c in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f60ef66c454 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f60ee2ee7df in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f60c042b700 (LWP 2389)): #0 0x7f60ef6724b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f60ef90e674 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f60ef9015d7 in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f60ef90e12c in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f60ef66c454 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f60ee2ee7df in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f60c0c2c700 (LWP 2388)): #0 0x7f60ef6724b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f60ef90e674 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f60ef9015d7 in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f60ef90e12c in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f60ef66c454 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f60ee2ee7df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f60f0d8a800 (LWP 2383)): [KCrash Handler] #6 0x7f60efa39b37 in QObject::setProperty(char const*, QVariant const&) () from /usr/lib/libQtCore.so.4 #7 0x7f60cc052eef in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #8 0x7f60cc052149 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #9 0x7f60e3a6a66b in ?? () from /usr/lib/libplasma.so.3 #10 0x7f60e3a7ce22 in ?? () from /usr/lib/libplasma.so.3 #11 0x7f60e3a7dfd8 in Plasma::Corona::loadLayout(QString const&) () from /usr/lib/libplasma.so.3 #12 0x7f60e3a7e0e4 in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib/libplasma.so.3 #13 0x7f60d9dc0ac8 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so #14 0x7f60d9dc3084 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so #15 0x7f60d9dc8725 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so #16 0x7f60efa38331 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #17 0x7f60eeb339af in QApplication::event(QEvent*) () from /usr/lib/libQtGui.so.4 #18 0x7f60eeb2e2dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #19 0x7f60eeb35136 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #20 0x7f60f080f2da in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #21 0x7f60efa1e4dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #22 0x7f60efa21966 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #23 0x7f60efa4e6ce in ?? () from /usr/lib/libQtCore.so.4 #24 0x7
[kdenlive] [Bug 368203] New: projects saved with kdenlive 16.07.7 beta cant be opened with kdenlive 16.04.0
https://bugs.kde.org/show_bug.cgi?id=368203 Bug ID: 368203 Summary: projects saved with kdenlive 16.07.7 beta cant be opened with kdenlive 16.04.0 Product: kdenlive Version: 16.04.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: blackendwh...@web.de When I safe a project in kdenilve 16.07.7 and then try to open it in 16.04.0 I get the error message: This project type is unsupported (version 0.95) and cant be loaded. please consider uprading kdenlive soon. This really is a problem , because: As u try things in beta and then the beta freezes, there s no back up to work safe on the same crashing project again... Reproducible: Always Steps to Reproduce: 1. safe session in 16.07.7 2.open session in 16.04 3. -- You are receiving this mail because: You are watching all bug changes.