[plasmashell] [Bug 359167] New: Plasmashell freezes / deadlocks on r600g mesa driver after screen lock
https://bugs.kde.org/show_bug.cgi?id=359167 Bug ID: 359167 Summary: Plasmashell freezes / deadlocks on r600g mesa driver after screen lock Product: plasmashell Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: knut.tidem...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Hello. I'm having issues with plasmashell freezing / becoming unresponsive after I unlock the screenlocker. It does not happen every time, but pretty frequently. Killing plasmashell and restarting it temporarily solves the problem. This is happening on the official arch linux packages, with mesa and a Radeon HD 5670/5690/5730. It could be a mesa bug as well. Reproducible: Sometimes Steps to Reproduce: 1. Leave computer, wait for lock screen to automatically appear 2. After a while, unlock the computer Actual Results: Plasmashell was frozen. Expected Results: A working plasmashell. The log output from plasmashell does not seem to display anything useful, this is the end of the log and I could see that plasmashell had been frozen for roughly 14 hours by looking at the clock widget: org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 261 "Properties" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 261 "Properties" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 262 "Volume" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 262 "Volume" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 268 "CardIndex" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 268 "CardIndex" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 269 "Ports" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 269 "Ports" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 270 "ActivePortIndex" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 270 "ActivePortIndex" libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription las
[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets
https://bugs.kde.org/show_bug.cgi?id=357597 --- Comment #3 from Giuseppe Margarita --- (In reply to Quantum Five from comment #2) > Unfortunately I can confirm that KUbuntu is also affected ... > > I am running KUbuntu 15.10 with all available patched applied from > ppa:kubuntu-ppa/backports. My plasmashell version is 5.5.3 and I am using > System Load widget. Interestingly is that after several hours the widget > becomes completely unresponsive (but I can launch the program it via K menu). > > I use my system for day to day work and I can confirm that after 8 hours the > CPU usage is rather high (~30%) when no other programs are running (and you > can feel that your computer has become sluggish). Killing and restarting > plasmashell always cures it (I can provide a screen shot of "before" and > "after"). It's VERY obvious. > > Last Friday I left the computer running over the weekend (my session running > and locked with no screen saver, no programs running), and when I logged > back in on Monday, the CPU usage was so high, couldn't do anything but > restart it. > > My desktop has a 8 x Intel Core i7-4770 CPU @ 3.4 GHz CPU and 16G of RAM. So > it's certainly not an old and slow machine. > > I hope you guys will now believe that this is indeed a KDE issue. > > Thank you. Hi, I find a workaround on my Arch Linux system. Open NotificationIcon.qml file with root permission in /usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui Search for line "running: visible" in "PlasmaComponents.BusyIndicator" section and change it in "running: false" After that, plasmashell should use only 4-5% of CPU load. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359168] New: I can't use skanlite with my new canon MG3650 Printer. It is not recognised missing the driver
https://bugs.kde.org/show_bug.cgi?id=359168 Bug ID: 359168 Summary: I can't use skanlite with my new canon MG3650 Printer. It is not recognised missing the driver Product: muon Version: 2.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: updater Assignee: echidna...@kubuntu.org Reporter: alain.vad...@gmail.com CC: aleix...@kde.org, sit...@kde.org When i print with my canon MG3650 its ok , but if i want to scan a documents it is not regognised. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359168] I can't use skanlite with my new canon MG3650 Printer. It is not recognised missing the driver
https://bugs.kde.org/show_bug.cgi?id=359168 --- Comment #1 from vadnal --- Is it possible for somebody to write a specific driver for this printer canon MG3650. Thanks a lot. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 359169] New: man page lists $ in front of namess of environmental variables used
https://bugs.kde.org/show_bug.cgi?id=359169 Bug ID: 359169 Summary: man page lists $ in front of namess of environmental variables used Product: frameworks-kinit Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: fa...@kde.org Reporter: m...@debian.org CC: kdelibs-b...@kde.org (Forwarding debian https://bugs.debian.org/811165) I read on the manual page for kdeinit5: ENVIRONMENT VARIABLES $HOME Specifies the home directory of the current user $KDE_HOME_READONLY Specifies if the home directory of the current user is read only $KDE_IS_PRELINKED If set, tells kdeinit5 that the KDE programs are pre-linked. (Prelinking is a process that allows you to speed up the process of dynamic linking.) However they should be listed without the evaluation operator $ at the start. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355528] Multiple monitor support is erratic
https://bugs.kde.org/show_bug.cgi?id=355528 --- Comment #16 from Murat Ursavaş --- I don't understand one thing. How is the status of the bug stays as "UNCONFIRMED", which can be reproduced so easily? I think, at least an acknowledgement would be a relief... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357238] crash when attempting to unlock with nvidia proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=357238 --- Comment #9 from tom.zoeh...@gmail.com --- Works for me aswell now, seems to have been fixed in one of the recent bug fix releases. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343772] Blank screen encountered on disconnecting secondary screen
https://bugs.kde.org/show_bug.cgi?id=343772 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 342675] screens turns black and plasma session whiped out after kscreen got installed
https://bugs.kde.org/show_bug.cgi?id=342675 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359139] I have a empty space/icon in the system tray
https://bugs.kde.org/show_bug.cgi?id=359139 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com --- Comment #1 from Raman Gupta --- Created attachment 97099 --> https://bugs.kde.org/attachment.cgi?id=97099&action=edit Screenshot I have this problem on 5.5.4 as well. Running Fedora 23 rpm-based KDE, plasma version 5.5.4, qt version 5.5.1, kernel 4.3.5-300 64 bit. Attached is a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359139] I have a empty space/icon in the system tray
https://bugs.kde.org/show_bug.cgi?id=359139 Raman Gupta changed: What|Removed |Added Attachment #97099|0 |1 is obsolete|| --- Comment #2 from Raman Gupta --- Created attachment 97100 --> https://bugs.kde.org/attachment.cgi?id=97100&action=edit Showing the entries this time -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 359169] man page lists $ in front of namess of environmental variables used
https://bugs.kde.org/show_bug.cgi?id=359169 Arthur Marsh changed: What|Removed |Added CC||arthur.ma...@internode.on.n ||et -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359170] New: RSIbreak does not show effect during breaks
https://bugs.kde.org/show_bug.cgi?id=359170 Bug ID: 359170 Summary: RSIbreak does not show effect during breaks Product: rsibreak Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: fabianr...@mailbox.org I installed RSIBreak via `sudo apt-get install rsibreak` on Kubuntu 14.04.3 (Trusty). The RSIBreak version is 0.11. I use the Kubuntu Backports ppa, the KDE version is 4.14.13. I configured RSIBreak to do the "Simple Gray Effect" during breaks. However, only a popup is shown during breaks. Also, "Show Plasma dashboard" and "Show slide show of images" does not work. Maybe important: I use two monitors. Reproducible: Always Steps to Reproduce: 1. Wait for the break to occur (I set short breaks to 1 minute) Actual Results: Pop up is shown that tells me to relax. Expected Results: The screen should be grayed out. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359171] New: paint strokes with tablet less fluent than in 2.9.6
https://bugs.kde.org/show_bug.cgi?id=359171 Bug ID: 359171 Summary: paint strokes with tablet less fluent than in 2.9.6 Product: krita Version: 3.0 Alpha Platform: MS Windows URL: https://www.dropbox.com/s/w787ckxh77vc1je/krita_paint_ bug.png?dl=0 OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: jonatan.b...@tba.nl In krita alpha 3.0 alpha 2 (fa2b0d7) my paint strokes with my wacom bamboo touch tablet are less fluent (see url). It seems every segment of the strokes starts a bit offset from the previous. I compared it with mouse strokes, and with krita 2.9.6. Both give more fluent strokes. Reproducible: Always Steps to Reproduce: 1.Create image. (I tried 1024x1024 and 8192x8192) 2.Select a brush (I tried Bristle_Details and Ink-precision_03) 3. draw a diagonal stroke with your tablet. Actual Results: Strokes contain small hiccups in their position (very noticeable when using ink-precision-03) . For the bristle_details brush, the speed influences the width, so you also notice a width change at these hiccups. See the url for a comparison Expected Results: Strokes just as fluent as in 2.9.6 Windows 7 professional 64 bit Intel core i5-4670 CPU @ 3.4 Ghz 16 GB ram nvidia Geforce GTX 760 wacom bamboo pen&touch medium tablet -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 359162] the connection is flapping all the time
https://bugs.kde.org/show_bug.cgi?id=359162 --- Comment #2 from Marcelo A. Caputo --- Dear Jan: I've check my connection and status with Nagios Core and told me that there's a flap with my connection. Then later, I've checked out my network and status from network mannager and there were a problem with my Ip. As my notebook is conected to my network via wifi I only tryed to delete my connection in the log of network mannager and recognized again. All authomatic and problem fixed. Thank you for your response but the problem was only mine. Have a good day. Marcelo. Marcelo Caputo. Powered by Samsung Mobile Mensaje original De: Jan Grulich via KDE Bugzilla Fecha: 09/02/2016 4:17 (GMT-03:00) Para: macjac...@hotmail.com Asunto: [plasma-nm] [Bug 359162] the connection is flapping all the time https://bugs.kde.org/show_bug.cgi?id=359162 --- Comment #1 from Jan Grulich --- The information about the connection state is coming from NetworkManager over DBus, which means that in your case it must be NetworkManager who is reponsible for this problem. What kind of connection is that? Can you post here log from NetworkManager? -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359172] New: RSIBreak does not show balloon message in systray on mouseover
https://bugs.kde.org/show_bug.cgi?id=359172 Bug ID: 359172 Summary: RSIBreak does not show balloon message in systray on mouseover Product: rsibreak Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: fabianr...@mailbox.org I installed RSIBreak via `sudo apt-get install rsibreak` on Kubuntu 14.04.3 (Trusty). The RSIBreak version is 0.11. I use the Kubuntu Backports ppa, the KDE version is 4.14.13. Maybe important: I use two monitors. Reproducible: Always Steps to Reproduce: 1. Move the mouse cursor over the RSIBreak icon in the systray Actual Results: Nothing happens Expected Results: A balloon message should be shown showing the time until the next break. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357238] crash when attempting to unlock with nvidia proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=357238 Martin Gräßlin changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #10 from Martin Gräßlin --- Thanks for the updates. I change to worksforme. If it happens again, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359173] New: Configuration of Notifications from "Configure RSIBreak ..." has no effect
https://bugs.kde.org/show_bug.cgi?id=359173 Bug ID: 359173 Summary: Configuration of Notifications from "Configure RSIBreak ..." has no effect Product: rsibreak Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: fabianr...@mailbox.org I installed RSIBreak via `sudo apt-get install rsibreak` on Kubuntu 14.04.3 (Trusty). The RSIBreak version is 0.11. I use the Kubuntu Backports ppa, the KDE version is 4.14.13. Maybe important: I use two monitors. Reproducible: Always Steps to Reproduce: 1. Right click on RSIBreak icon in Systray 2. Click "Configure RSIBreak ..." 3. Choose the Actions menu 4. Change any notification setting (e.g. show a message in a popup for "End of long break") 5. Click OK 6. Reopen the menu Actual Results: The change in the notification setting is gone. Expected Results: The change in the notification setting is saved. If I change the notifcations via 1. Right click on RSIBreak icon in Systray 2. Click "Configure Notifications ..." 3. Change any notification setting (e.g. show a message in a popup for "End of long break") 4. Click OK then the notification setting is saved. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359170] RSIbreak does not show effect during breaks
https://bugs.kde.org/show_bug.cgi?id=359170 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Albert Astals Cid --- The configuration dialog is a bit confusing, if you want the effect and not the popup go to settings, "during breaks" and uncheck the "use popup" checkbox. Does that fix it for you? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 359162] the connection is flapping all the time
https://bugs.kde.org/show_bug.cgi?id=359162 Jan Grulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359172] RSIBreak does not show balloon message in systray on mouseover
https://bugs.kde.org/show_bug.cgi?id=359172 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Albert Astals Cid --- The ballon is part of plasma tooltips, have you by any change disabled the rest of plasma tooltips? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356727] Plasma Panel sometimes disappears with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=356727 ayq...@gmail.com changed: What|Removed |Added CC||ayq...@gmail.com --- Comment #27 from ayq...@gmail.com --- I am running Kubuntu with Plasma 5.5.3 from the backports PPA. I can confirm this bug. Here is the behaviour for me: I have a laptop running at 1920x1080 with the default panel. I plug in a second monitor running at 1920x1080 and configure it to be the primary, and disable the laptop panel. The panel moves to the external monitor. I unplug the external monitor. The panel disappears. I plug the external monitor in again - the panel reappears. It is a similar issue if I unify the outputs across both monitors - unplugging the external monitor makes the panel disappear, plugging it in again makes it re-appear. Thanks -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359173] Configuration of Notifications from "Configure RSIBreak ..." has no effect
https://bugs.kde.org/show_bug.cgi?id=359173 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Albert Astals Cid --- rsibreak 0.11 is unsupported, only 0.12 is now, what you describe works fine for me on 0.12, please if you upgrade and still doesn't work reopen the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 David Edmundson changed: What|Removed |Added CC||gor...@dickens.com --- Comment #11 from David Edmundson --- *** Bug 357597 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets
https://bugs.kde.org/show_bug.cgi?id=357597 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from David Edmundson --- *** This bug has been marked as a duplicate of bug 356479 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets
https://bugs.kde.org/show_bug.cgi?id=357597 --- Comment #4 from David Edmundson --- Some improvement was added in latest frameworks speeding up a certain event filter. also I need some sort of logs Please can you run: kquitapp5 plasmashell valgrind --tool=callgrind --instr-atstart=no plasmashell wait till CPU usage is high then callgrind_control -i on *wait a bit* callgrind_control -i off then quit plasma and upload the relevant callgrind.something.out file. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346336] keyboard options not reapplied when keyboard unplugged / replugged
https://bugs.kde.org/show_bug.cgi?id=346336 ayq...@gmail.com changed: What|Removed |Added CC||ayq...@gmail.com --- Comment #20 from ayq...@gmail.com --- I am using Kubuntu 15.10 with Plasma 5.5.3 from backports PPA. This bug is still occurring for me when resuming from sleep intermittently. Replugging is fine. Something must have changed that makes it happen intermittently instead of constantly, but it's still a pain. Shall I submit a different bug? Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets
https://bugs.kde.org/show_bug.cgi?id=357597 --- Comment #6 from Giuseppe Margarita --- (In reply to David Edmundson from comment #4) > Some improvement was added in latest frameworks speeding up a certain event > filter. > > > > also I need some sort of logs > > Please can you run: > kquitapp5 plasmashell > valgrind --tool=callgrind --instr-atstart=no plasmashell > > wait till CPU usage is high then > > callgrind_control -i on > *wait a bit* > callgrind_control -i off > > then quit plasma and upload the relevant callgrind.something.out file. Have I to do this with "running: visible" in NotificationIcon.qml file? Ah, please, change status. This bug is not resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets
https://bugs.kde.org/show_bug.cgi?id=357597 --- Comment #7 from David Edmundson --- without the change. also it is marked as being a duplicate of another bug which is tracking a practically identical discussion. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets
https://bugs.kde.org/show_bug.cgi?id=357597 --- Comment #8 from Giuseppe Margarita --- (In reply to David Edmundson from comment #7) > without the change. > > also it is marked as being a duplicate of another bug which is tracking a > practically identical discussion. OK, I'll do the log when I can. But this is the first time I try that. After quitting plasma, where can I find callgrind.something.out file? Same directory in which I executed Konsole? -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 David Roth changed: What|Removed |Added CC||davidro...@gmail.com --- Comment #54 from David Roth --- I seem to be in the same boat. Thanks and sorry for the trouble. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339887] KMail shows pictures in html messages as attachments.
https://bugs.kde.org/show_bug.cgi?id=339887 Torsten Bielen changed: What|Removed |Added CC||bie...@gmx.de --- Comment #14 from Torsten Bielen --- Same here opensuse 42.1 KMail 5.1.1. 1. Set prefer HTML over plain text 2. Allow HTML view for specific contact, and I allow to load external references for this contact. => pictures aren't displayed inline, only as attachments. -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 359174] New: Wrong encoded text in plasmapkg2 output
https://bugs.kde.org/show_bug.cgi?id=359174 Bug ID: 359174 Summary: Wrong encoded text in plasmapkg2 output Product: Plasma SDK Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: safa1996alful...@gmail.com CC: antonis.tsiapalio...@kde.org Using an Arabic locale, the output of list, install and remove commands (and maybe others) contains Arabic text that is wrongly encoded. Help command (--help) displays text correctly. Here is a screenshot from Konsole: http://i.imgur.com/Jg2UOWF.png . The correct encoded text is in the green rectangle, while the wrong is in a red rectangle. The Arabic text (in the red rectangle) should be "يسرد أنواع الخدمات". Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 359175] New: no panel options, exept coose of soundcard
https://bugs.kde.org/show_bug.cgi?id=359175 Bug ID: 359175 Summary: no panel options, exept coose of soundcard Product: kmix Version: 4.5 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: KMix Panel Docking Assignee: es...@kde.org Reporter: devil77...@yahoo.de Created attachment 97102 --> https://bugs.kde.org/attachment.cgi?id=97102&action=edit options Hi. I'm using ASRoch x79 Extreme 9, with Creative Sound Core3D 7.1 CH (for example: http://www.asrock.com/mb/Intel/X79%20Extreme9), an external PreSonus AudioBox and a soundchip of my nvidia graficscard, wich automaticly will be set as default, after update, or after use of the external one, when unplugged. It would be really nice to have the option, to exclude nvida-soundchips compleatly. But the main Problem is there is no way to choose any kind of connection, like headset, mic1, mic2, aux... what ever. The choose of analog output or analog headset does not have any effect. The only possible option is, to choose one of the soundchips -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359176] New: Plasma desktop crashes when adding Activity Pager widget
https://bugs.kde.org/show_bug.cgi?id=359176 Bug ID: 359176 Summary: Plasma desktop crashes when adding Activity Pager widget Product: plasmashell Version: 5.5.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sam...@yahoo.co.uk CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: - What I was doing when the application crashed: Adding Activity Pager widget to the desktop (or panel) - Custom settings of the application: Two displays, with Xorg ATI driver. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6f615c9900 (LWP 3345))] Thread 10 (Thread 0x7f6f5a7fc700 (LWP 3348)): #0 0x0033934f72fd in poll () at /lib64/libc.so.6 #1 0x00339740a182 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00339740bc77 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f6f5aa57da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x00374eca33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x003393c07555 in start_thread () at /lib64/libpthread.so.0 #6 0x003393502b9d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f6f53fff700 (LWP 3367)): #0 0x7ffdcc6bac2f in clock_gettime () #1 0x003393510d9d in clock_gettime () at /lib64/libc.so.6 #2 0x00374ed53956 in qt_gettime() () at /lib64/libQt5Core.so.5 #3 0x00374eed8949 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #4 0x00374eed8eb5 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #5 0x00374eeda2ae in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x00339584935d in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #7 0x003395849ceb in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #8 0x003395849ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x00374eedaecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #10 0x00374ee81eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #11 0x00374ec9e434 in QThread::exec() () at /lib64/libQt5Core.so.5 #12 0x7f6f61d3c9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #13 0x00374eca33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #14 0x003393c07555 in start_thread () at /lib64/libpthread.so.0 #15 0x003393502b9d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f6f50d39700 (LWP 3369)): #0 0x003393c0c540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6f51def6da in radeon_drm_cs_emit_ioctl () at /usr/lib64/dri/r600_dri.so #2 0x7f6f51deee37 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x003393c07555 in start_thread () at /lib64/libpthread.so.0 #4 0x003393502b9d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f6f48f20700 (LWP 3370)): #0 0x003393510690 in __libc_disable_asynccancel () at /lib64/libc.so.6 #1 0x0033934f7309 in poll () at /lib64/libc.so.6 #2 0x003395849dbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x003395849ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x00374eedaecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x00374ee81eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x00374ec9e434 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f6f61d3c9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x00374eca33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x003393c07555 in start_thread () at /lib64/libpthread.so.0 #10 0x003393502b9d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f6f43238700 (LWP 3371)): #0 0x7ffdcc6bac2f in clock_gettime () #1 0x003393510d9d in clock_gettime () at /lib64/libc.so.6 #2 0x00374ed53956 in qt_gettime() () at /lib64/libQt5Core.so.5 #3 0x00374eed8949 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #4 0x00374eed8eb5 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #5 0x00374eeda2ae in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x00339584935d in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #7 0x003395849ceb in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #8 0x003395849ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9
[plasma-nm] [Bug 357219] Repeatable crash when attempting to edit NM openvpn connections
https://bugs.kde.org/show_bug.cgi?id=357219 Thorsten Oppels changed: What|Removed |Added CC||thopp...@web.de --- Comment #4 from Thorsten Oppels --- Same error here. Edit a existing openVPN-Connection crashes the kde-nm-connection-editor 100%. Same if I try to create a new openVPN Connection. It seems that it is possible to add a new openVPN connection via import a *.ovpn config file. It is possible to add or modify an other type of VPN-Connection (e.g. cisco-vpn) Trace: Application: Verbindungs-Editor (kde-nm-connection-editor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7f4395aa33d9 in SettingWidget::SettingWidget(QSharedPointer const&, QWidget*, QFlags) () from /usr/lib64/libplasmanetworkmanagement-editor.so #6 0x7f4395a8747a in IPv6Widget::IPv6Widget(QSharedPointer const&, QWidget*, QFlags) () from /usr/lib64/libplasmanetworkmanagement-editor.so #7 0x7f4395aa7ab9 in ConnectionDetailEditor::initTabs() () from /usr/lib64/libplasmanetworkmanagement-editor.so #8 0x7f4395aae6b2 in ConnectionDetailEditor::gotSecrets(QString const&, bool, QMap > const&, QString const&) () from /usr/lib64/libplasmanetworkmanagement-editor.so #9 0x7f43953731fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #10 0x7f439571dfad in NetworkManager::Connection::gotSecrets(QString const&, bool, QMap > const&, QString const&) () from /usr/lib64/libNetworkManagerQt.so.1 #11 0x7f439571ea52 in NetworkManager::Connection::onSecretsArrived(QDBusPendingCallWatcher*) () from /usr/lib64/libNetworkManagerQt.so.1 #12 0x7f43953731fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #13 0x7f4392c75b5f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/libQtDBus.so.4 #14 0x7f439537759e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #15 0x7f4393beb76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #16 0x7f4393bf1cad in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #17 0x7f4394db6e0a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #18 0x7f439535f2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #19 0x7f439536257d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #20 0x7f439538c8fe in ?? () from /usr/lib64/libQtCore.so.4 #21 0x7f439160aa04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #22 0x7f439160ac48 in ?? () from /usr/lib64/libglib-2.0.so.0 #23 0x7f439160acec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #24 0x7f439538c0be in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #25 0x7f4393c88676 in ?? () from /usr/lib64/libQtGui.so.4 #26 0x7f439535de6f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #27 0x7f439535e165 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #28 0x7f43953635b9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #29 0x0040a975 in ?? () #30 0x7f4392eb7b05 in __libc_start_main () from /lib64/libc.so.6 #31 0x0040aa82 in _start () -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] New: blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 Bug ID: 359177 Summary: blanks out original plasma session when I start a new a new plasma session from it Product: KScreen Version: git Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: common Assignee: se...@kde.org Reporter: mar...@lichtvoll.de Happens with both kscreen + kded5 from git as well as packaged 5.4.3 in Debian (soon to be updated to 5.5.4 I think). With kernel 4.5-rc3 and 4.4. With Intel ThinkPad, i915, internal display and external 22 inch display, both full hd resolution. Since yesterday I have it that on starting my second Plasma session via Alt-F2 start new session that something completely blanks out the Plasma session I started the second session from. All I see is a black screen. Right now this happens *everytime*. So right now I have this in a reproducable state. As I disabled KScreen 2 service on the initial desktop, it may not be related to KScreen, maybe its a powerdevil issue or whatever is dealing with brightness and display on/off controls. Reproducible: Always Steps to Reproduce: 1. Start a Plasma session. 2. Alt-F2 start a new Plasma session. On my system at least. Actual Results: Black screen on original Plasma session. And nothing works to bring it to visibility again. I tried: 1. pressing a key 2. martin@merkaba:~> cat /usr/local/bin/licht #!/bin/bash while true; do echo 0 > /sys/class/backlight/intel_backlight/bl_power echo 0 > /sys/class/backlight/acpi_video0/bl_power echo 4437 > /sys/class/backlight/intel_backlight/brightness echo 15 > /sys/class/backlight/acpi_video0/brightness sleep 1 done (it seems it is not just the backlight, it just seems to switch of the display *completely* on that session, cause the script otherwise actually works.) 3. su - othersession export DISPLAY=:othersession xrandr --auto 4. vbetool dpms off 5. Disabling KScreen 2 service on one of the sessions (so maybe this is not related to KScreen 2) 6. Of course I also tried the rm -r ~/.local/share/kscreen thing that helped me before with some servere KScreen issue. 7. Masking systemd backlight service: martin@merkaba:/etc/systemd> find -name "*backlight*" -ls 7950807 4 lrwxrwxrwx 1 root root9 Feb 9 11:13 ./system/systemd-backlight@backlight:acpi_video0.service -> /dev/null 7950809 4 lrwxrwxrwx 1 root root9 Feb 9 11:13 ./system/systemd-backlight@backlight:intel_backlight.service -> /dev/null 8. Trying with kernel 4.4 to make sure its not related to 4.5-rc3. 9. Fiddling around with Solid brightness controls by su - othersession, eval $(dbus-launch) and using martin@merkaba:~> qdbus org.kde.kded5 /org/kde/Solid/PowerManagement/Actions/BrightnessControl org.kde.Solid.PowerManagement.Actions.BrightnessControl.brightnessMax 15 to query maximum brightness. It *did* not return within half a minute for the broken session. It worked on the session that is running. Next I will go with removing all self-compiled stuff, as it means not using KDEPIM altogether, cause self-compiled KDEPIM has most recent Akonadi with multi level cache directories I cannot go back to 15.08 which is currently packaged in Debian (15.12 in experimental is not yet fully build). Expected Results: kscreen / powerdevil / sddm / systemd backlight service – frankly I do not care what component will do it, well I do think that systemd has no business fiddling with brightness, but otherwise… – *totally* *ensures* that I *always* can see my desktop sessions. In *no* case it is a valid response to present the user with a black screen. Unless there is some display connected and with a laptop there *always* is show me the desktop at least on one of the displays when I press a key. *Always*. No exception, I am the user, I am the king. No complex evaluation, just *show* the desktop. And for starters please give me a command I can use that does this: I am the user, I am the king, show me the light (i.e. the desktop) *now*. At least I want to be able to use two Plasma sessions again even if I have to manually bring the blanked one back to light. Right now I know no way to unblank the blanked session and as you can see I tried a lot. I have no words to express how broken this is. martin@merkaba:~> phoronix-test-suite system-info Phoronix Test Suite v5.2.1 System Information Hardware: Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB, Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel HD 3000 (1300MHz), Audio: Conexant CX20590, Monitor: P24T-7 LED, Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205 Software: OS: Debian unstable, Kernel: 4.5.0-rc3
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #1 from Martin Steigerwald --- PS: I will try to calm down now a bit, and I am willing to constructively help with finding what does on here, even self-compile from git master, but I hope you understand that this "I blank the screen, you no see any desktop anymore hahaha" kind of thing is as frustrating as it can get. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 359178] New: Kaddressbook does not download new contacts from Google Contacts
https://bugs.kde.org/show_bug.cgi?id=359178 Bug ID: 359178 Summary: Kaddressbook does not download new contacts from Google Contacts Product: kaddressbook Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@googlemail.com CC: to...@kde.org First of all: this is kaddressbook 5.1.1 (obviously the bug system is not yet prepared for the up to date versions...) on Arch fully updated. Changes in Google Contacts will not be reflected by the local addressbook (set up as akonadi ressource "Google Contacts"). Deleting the ressource and setting it up fresh will download all contacts from Google Contacts but refreshing the ressource has no effect at all. THis is not a configuration error (tested on fresh account) and by the way evolution (Gnome online accounts that is) works fine. I get that no one wants to fix this but please just take the code from gnome then - they got it right. p. Reproducible: Always Steps to Reproduce: 1. set up google contacts akonadi ressource 2. add a new contact on Google Contact website 3. refresh akonadi ressource Actual Results: contact list doesn't get synchronized - the new contact doesn't show up Expected Results: obviously new contacts have to show up -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 359179] New: Add Brazilian Portuguese rss feeds
https://bugs.kde.org/show_bug.cgi?id=359179 Bug ID: 359179 Summary: Add Brazilian Portuguese rss feeds Product: akregator Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: alvare...@kde.org Folder: Brazilian Portuguese feeds Language: Brazilian Portuguese (pt_BR) Default feeds: Name: Planet KDE Português feed: http://planetkde.org/pt-br/rss20.xml Name: KDE-Brasil feed: https://br.kde.org/rss.xml Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 359168] I can't use skanlite with my new canon MG3650 Printer. It is not recognised missing the driver
https://bugs.kde.org/show_bug.cgi?id=359168 Harald Sitter changed: What|Removed |Added Component|updater |general Assignee|echidna...@kubuntu.org |kare.s...@iki.fi Product|muon|Skanlite Version|2.2.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 359180] New: Crash - due to RSS feeds?
https://bugs.kde.org/show_bug.cgi?id=359180 Bug ID: 359180 Summary: Crash - due to RSS feeds? Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bu...@gmx.at Application: kontact (5.0.2) Qt Version: 5.5.1 Operating System: Linux 4.4.0-2-generic i686 Distribution: Ubuntu Xenial Xerus (development branch) -- Information about the crash: - What I was doing when the application crashed: I was browsing my RSS feeds. - Unusual behavior I noticed: The RSS feed overview list showed that there are articles, but the article lists were empty. - Custom settings of the application: I added two RSS feeds to the two default feeds "Kubuntu" and KDE": - http://www.heise.de/news-extern/news.html - http://derstandard.at/?page=rss&ressort=seite1 The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xad898840 (LWP 21826))] Thread 8 (Thread 0xabf6fb40 (LWP 21828)): #0 0xb7753c31 in __kernel_vsyscall () #1 0xb298a23c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb5fe2d26 in __pthread_cond_wait (cond=0xb5d78d54, mutex=0xb5d78d3c) at forward.c:149 #3 0xb50dd4ea in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb50dd53c in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb298518a in start_thread (arg=0xabf6fb40) at pthread_create.c:333 #6 0xb5fd600e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 7 (Thread 0xaafbdb40 (LWP 21829)): #0 0xb7753c31 in __kernel_vsyscall () #1 0xb5fcb40b in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb26d1ac0 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb26c306c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb26c31a4 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb64f9764 in QEventDispatcherGlib::processEvents (this=0xaa600468, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0xb649e2d3 in QEventLoop::processEvents (this=0xaafbd194, flags=...) at kernel/qeventloop.cpp:128 #7 0xb649e72a in QEventLoop::exec (this=0xaafbd194, flags=...) at kernel/qeventloop.cpp:204 #8 0xb62c3edd in QThread::exec (this=0x8392648) at thread/qthread.cpp:503 #9 0xb62c3fb8 in QThread::run (this=0x8392648) at thread/qthread.cpp:570 #10 0xb62c93fb in QThreadPrivate::start (arg=0x8392648) at thread/qthread_unix.cpp:331 #11 0xb298518a in start_thread (arg=0xaafbdb40) at pthread_create.c:333 #12 0xb5fd600e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 6 (Thread 0xaa49eb40 (LWP 21830)): #0 0xb7753c31 in __kernel_vsyscall () #1 0xb298a23c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb5fe2d26 in __pthread_cond_wait (cond=0xab6b2138, mutex=0xab6b2120) at forward.c:149 #3 0xb510c0bc in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb4dcad36 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb50f46b2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #6 0xb510bac1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #7 0xb298518a in start_thread (arg=0xaa49eb40) at pthread_create.c:333 #8 0xb5fd600e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 5 (Thread 0xa9affb40 (LWP 21831)): #0 0xb7753c31 in __kernel_vsyscall () #1 0xb298a23c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb5fe2d26 in __pthread_cond_wait (cond=0xab6b6734, mutex=0xab6b671c) at forward.c:149 #3 0xb510c0bc in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb4dcbe65 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb50f46b2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #6 0xb510bac1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #7 0xb298518a in start_thread (arg=0xa9affb40) at pthread_create.c:333 #8 0xb5fd600e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 4 (Thread 0xa92feb40 (LWP 21832)): #0 0xb7753c31 in __kernel_vsyscall () #1 0xb298a23c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb5fe2d26 in __pthread_cond_wait (cond=0xab6b6734, mutex=0xab6b671c) at forward.c:149 #3 0xb510c0bc in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb4dcbe65 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb50f46b2 in ?? () from /usr/lib/i386-linux-gnu/libQt5
[plasma-nm] [Bug 357219] Repeatable crash when attempting to edit NM openvpn connections
https://bugs.kde.org/show_bug.cgi?id=357219 --- Comment #5 from Thorsten Oppels --- If I run nm-connection-editor from Commandline it shows: > nm-connection-editor -c ** (nm-connection-editor:10773): WARNING **: Unsupported connection type 'vpn' ** (nm-connection-editor:10773): WARNING **: Unsupported connection type 'generic' ** (nm-connection-editor:10773): WARNING **: Unsupported connection type 'vpn' ... -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #2 from Martin Steigerwald --- After almost switching to LXDE, I know have a setup that works. On Kernel 4.4 with KScreen 2 disabled on both plasma sessions. So Kernel 4.5-rc3 may be somehow be related, but to early to say for sure as I also had these issues while running 4.4 before. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #3 from Sebastian Kügler --- Could you check if disabling the Power Management Service helps? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359083] digiKam doesn't read JPG XMP data written by Lightroom
https://bugs.kde.org/show_bug.cgi?id=359083 --- Comment #2 from george --- (In reply to caulier.gilles from comment #1) > So the LR XMP data are for LR only. We don't know whats we can do with it. Reverse engineering :P -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359083] digiKam doesn't read JPG XMP data written by Lightroom
https://bugs.kde.org/show_bug.cgi?id=359083 --- Comment #3 from caulier.gil...@gmail.com --- We have more important tasks to do than RE. Even if RE is need, this must be done in Exiv2 libs with documentation. Good luck... -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #4 from Martin Steigerwald --- okay, it is not 4.5-rc3. I just had it again with 4.4. With power management service disabled on both sessions – thought of this myself. This appears to be too crazy and I wonder whether some other crazy stuff is running that messes with display brightness. I am avalailable on IRC (depending on whether I can see anything) as helios21 or helios55 (depending on session I see) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 Martin Steigerwald changed: What|Removed |Added CC||martin.steigerwald@teamix.d ||e --- Comment #5 from Martin Steigerwald --- Just happened again. I have confirmed that on both sessions power management service is disabled. Power management kcm tells so. What I see happening is this: other session get dimmed (reduced brightness) after a time and then blanked. Despite power management service not running. Now I am really puzzled. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 321717] systray and battery widget in 4.11 is broken
https://bugs.kde.org/show_bug.cgi?id=321717 mat...@gmail.com changed: What|Removed |Added CC||mat...@gmail.com --- Comment #33 from mat...@gmail.com --- Created attachment 97103 --> https://bugs.kde.org/attachment.cgi?id=97103&action=edit screenshot of battery widget on top left corner of the screen -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 321717] systray and battery widget in 4.11 is broken
https://bugs.kde.org/show_bug.cgi?id=321717 --- Comment #34 from mat...@gmail.com --- Comment on attachment 97103 --> https://bugs.kde.org/attachment.cgi?id=97103 screenshot of battery widget on top left corner of the screen kubuntu 14.04 LTS, KDE 4.14.13 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358921] Assistant widget prevent other widgets to show contents
https://bugs.kde.org/show_bug.cgi?id=358921 Zhang Jingqiang changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Zhang Jingqiang --- I update plasma from 5.4.3 to 5.5.4, and the bug gone. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359181] New: Buffer Overflow during Demangling
https://bugs.kde.org/show_bug.cgi?id=359181
Bug ID: 359181
Summary: Buffer Overflow during Demangling
Product: valgrind
Version: unspecified
Platform: Other
OS: All
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: boehme.mar...@gmail.com
A buffer overflow in cplus-dem.c is caused when Valgrind tries to demangle
specially crafted function arguments in the binary. Both the buffer size as
well as the buffer content are controlled from the binary.
Upstream: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69687
Reproducible: Always
Steps to Reproduce:
$ cat compileme.c
#include
#include
const char*
X00020A___R0020A__U000R03000N_020A__K000(){
char *p;
p = (char *) malloc(19);
p = (char *) malloc(12);
free(p);
p = (char *) malloc(16);
return "Hello World!";
}
int main()
{
printf("%s\n",X00020A___R0020A__U000R03000N_020A__K000());
return 0;
}
$ g++ compileme.c -o temp
$ sed -b s/Z68/_20/g temp > valgrindme
$ chmod u+x valgrindme
$ ./valgrindme
Hello World!
$ valgrind --leak-check=yes ./valgrindme
--
You are receiving this mail because:
You are watching all bug changes.
[rsibreak] [Bug 359170] RSIbreak does not show effect during breaks
https://bugs.kde.org/show_bug.cgi?id=359170 --- Comment #2 from Fabian Rost --- Yes that fixes it. That's indeed confusing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359171] paint strokes with tablet less fluent than in 2.9.6
https://bugs.kde.org/show_bug.cgi?id=359171 guruguru...@outlook.jp changed: What|Removed |Added CC||guruguru...@outlook.jp --- Comment #1 from guruguru...@outlook.jp --- Created attachment 97104 --> https://bugs.kde.org/attachment.cgi?id=97104&action=edit another hiccup example I too see hiccups happen in Krita 3.0 pre-alpha2 on my PC(Windows 10, dual screen, Intuos Pro 5) I attach my screenshot using ink-precision-03. I do not seem to be able to repro the issue with Krita2.9.11. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359172] RSIBreak does not show balloon message in systray on mouseover
https://bugs.kde.org/show_bug.cgi?id=359172 --- Comment #2 from Fabian Rost --- Plasma tooltips are enabled. Tooltips are shown if I move the mouse over the volume icon, the network icon, etc. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359173] Configuration of Notifications from "Configure RSIBreak ..." has no effect
https://bugs.kde.org/show_bug.cgi?id=359173 --- Comment #2 from Fabian Rost --- Is there a repository that provides rsibreak 0.12 for Trusty? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #6 from Martin Steigerwald --- Even after removing *all* of the self-compiled KDE Frameworks + KDEPIM stuff the issue persists. So I can rule two things out: 1) Its not linux 4.5-rc3 kernel. 2) Its not any of git master. I did remove /var/tmp/kdecache stuff as well as ~/.local/share/kscreen for both users with me recent attempt. So I now have stock Debian Sid + disabled KScreen 2 services on both sessions + disabled power management settings on both sessions. And still get this issue. Additionally to that there is no such issue when I use two LXDE sessions instead. I cannot yet upgrade to 5.6 rc3 packages for Qt from Debian experimental as that would uninstall the Plasma desktop. So using Qt 5.5.1, but I think this has been in Debian for quite a while already. This is so broken beyond words. :( -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346336] keyboard options not reapplied when keyboard unplugged / replugged
https://bugs.kde.org/show_bug.cgi?id=346336 --- Comment #21 from David Rosca --- (In reply to ayqazi from comment #20) > Shall I submit a different bug? So can you confirm it is fixed with (un)plugging? This is what this bug (and my fix) is about. Please open new bug for reapplying settings after suspend. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346336] keyboard options not reapplied when keyboard unplugged / replugged
https://bugs.kde.org/show_bug.cgi?id=346336 --- Comment #22 from ayq...@gmail.com --- As I said, unplugging/plugging works. OK, I shall open another bug. Regards, Asfand Yar Qazi On 9 February 2016 at 12:39, David Rosca via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=346336 > > --- Comment #21 from David Rosca --- > (In reply to ayqazi from comment #20) >> Shall I submit a different bug? > > So can you confirm it is fixed with (un)plugging? This is what this bug (and > my > fix) is about. > > Please open new bug for reapplying settings after suspend. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 359182] New: Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=359182 Bug ID: 359182 Summary: Dolphin crash Product: dolphin Version: 15.12.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: zacc...@gmail.com Application: dolphin (15.12.1) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: until lauching application was crashed and closed it is first time crash The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4b570e67c0 (LWP 29455))] Thread 4 (Thread 0x7f4b400e6700 (LWP 29456)): #0 0x7f4b5698dc1d in poll () at /lib64/libc.so.6 #1 0x7f4b499db422 in () at /usr/lib64/libxcb.so.1 #2 0x7f4b499dd00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f4b4243b3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f4b50ad832f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f4b4c58b0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f4b5699604d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4b3469d700 (LWP 29461)): #0 0x7f4b56989ced in read () at /lib64/libc.so.6 #1 0x7f4b4ba46b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4b4ba05999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4b4ba05df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4b4ba05f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4b50d0ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f4b50cb1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f4b50ad361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f4b50ad832f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f4b4c58b0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f4b5699604d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f4b32f0d700 (LWP 29480)): [KCrash Handler] #6 0x7f4b50ad0bf5 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #7 0x7f4b50ad7568 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f4b50ad8351 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f4b4c58b0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f4b5699604d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f4b570e67c0 (LWP 29455)): #0 0x7f4b4c58f05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4b499db669 in () at /usr/lib64/libxcb.so.1 #2 0x7f4b499dcd5f in () at /usr/lib64/libxcb.so.1 #3 0x7f4b499dce72 in xcb_wait_for_reply () at /usr/lib64/libxcb.so.1 #4 0x7f4b4244ab69 in QXcbWindow::setKeyboardGrabEnabled(bool) () at /usr/lib64/libQt5XcbQpa.so.5 #5 0x7f4b51e241a6 in () at /usr/lib64/libQt5Widgets.so.5 #6 0x7f4b51e2be88 in QApplicationPrivate::closePopup(QWidget*) () at /usr/lib64/libQt5Widgets.so.5 #7 0x7f4b51e645be in QWidgetPrivate::hide_helper() () at /usr/lib64/libQt5Widgets.so.5 #8 0x7f4b51e689e8 in QWidget::setVisible(bool) () at /usr/lib64/libQt5Widgets.so.5 #9 0x7f4b51e6466b in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () at /usr/lib64/libQt5Widgets.so.5 #10 0x7f4b51f9edee in () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f4b51f9f1f1 in QMenu::internalDelayedPopup() () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f4b50ce48bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f4b51e68f64 in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f4b51fa43db in QMenu::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7f4b51e28e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x7f4b51e2dcc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #17 0x7f4b50cb3e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7f4b50d0a77d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #19 0x7f4b50d0aaa1 in () at /usr/lib64/libQt5Core.so.5 #20 0x7f4b4ba05c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #21 0x7f4b4ba05ed8 in () at /usr/lib64/libglib-2.0.so.0 #22 0x7f4b4ba05f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #23 0x7f4b50d0ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #24 0x7f4b50cb1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #25 0x7f4b51f9ea20 in QMenu::exec(QPoint const&, QAction*) () at /usr/lib64/libQt5Widgets.so.5 #26 0x7f4b56caf812 in () at /usr/
[rsibreak] [Bug 359173] Configuration of Notifications from "Configure RSIBreak ..." has no effect
https://bugs.kde.org/show_bug.cgi?id=359173 --- Comment #3 from Fabian Rost --- Or is there somewhere described how to build RSIBreak from the sources? Trying to build version 0.12.1 I got the following error: CMake Error at CMakeLists.txt:6 (find_package): Could not find a package configuration file provided by "ECM" (requested version 1.7.0) with any of the following names: ECMConfig.cmake ecm-config.cmake Add the installation prefix of "ECM" to CMAKE_PREFIX_PATH or set "ECM_DIR" to a directory containing one of the above files. If "ECM" provides a separate development package or SDK, be sure it has been installed. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 359179] Add Brazilian Portuguese rss feeds
https://bugs.kde.org/show_bug.cgi?id=359179 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im/07665163f194e58d833d61bc ||1df0c272353522c9 Version Fixed In||5.2 --- Comment #1 from Laurent Montel --- Git commit 07665163f194e58d833d61bc1df0c272353522c9 by Montel Laurent. Committed on 09/02/2016 at 12:47. Pushed by mlaurent into branch 'master'. Fix Bug 359179 - Add Brazilian Portuguese rss feeds FIXED-IN: 5.2 M +10 -0akregator/src/akregator_part.cpp http://commits.kde.org/kdepim/07665163f194e58d833d61bc1df0c272353522c9 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #7 from Sebastian Kügler --- It's also entirely confusing. The amount of data you give makes it hard to extract the useful info from it. Could you perhaps boil it down a bit? It now reads more like an unstructured testing log (this kernel, that kernel, disabled this, that-thing from packages, this-thing from source, ... I simply lost track). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 359132] Git master 2016-02-08 - Audio power meter does not work for timeline
https://bugs.kde.org/show_bug.cgi?id=359132 --- Comment #3 from Evert Vorster --- I just re-built kdenlive, and still the audio power meter does not work on the project monitor. https://youtu.be/DFgPahItlUA Has a short clip showing the issue -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #8 from Martin Steigerwald --- Well, I now have only Debian Sid. Nothing self-compiled from master (so KDEPIM + Akonadi gone for now as well). A kernel 4.4 that worked okay for more than a month. I have disabled power management service and KScreen 2. What else can cause havoc? Solid? I have no idea. Two sessions are working just fine in LXDE and for some added comfort MATE. As for unstructured: I am struggling to get back a working system. This already has taken too much time. I had hoped that there is something I can give you to better understand the issue. But I received no workable suggestion. No command to try to gather some debug output as to what is happening here… so now … I need to get back to work. So I try to get along with MATE for now. This is beyond anything I ever saw on my desktop in the last 10 years of Linux usage. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #9 from Martin Steigerwald --- I am willing to look into this again, but now I need to focus on work. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 359183] New: Sluggish desktop - nvidia gpu memory leak
https://bugs.kde.org/show_bug.cgi?id=359183 Bug ID: 359183 Summary: Sluggish desktop - nvidia gpu memory leak Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: dualhead Assignee: unassigned-b...@kde.org Reporter: vitori...@gmail.com The desktop has been very slow after upgrade to Kubuntu 15.10 Found out that Nvidia X server settings reports almost no GPU memory available(spikes to 100% eventually together with GPU utilization): Attribute 'NvidiaDriverVersion' (vpkubuntu:0[gpu:0]): 352.63 Attribute 'TotalDedicatedGPUMemory' (vpkubuntu:0[gpu:0]): 1020. Attribute 'UsedDedicatedGPUMemory' (vpkubuntu:0[gpu:0]): 849. Attribute 'GPUUtilization' (vpkubuntu:0[gpu:0]): graphics=9, memory=28, video=0, PCIe=2 Xrestop: $xrestop - Display: localhost Monitoring 59 clients. XErrors: 29 Pixmaps: 81084K total, Other: 108K total, All: 81193K total HW: GeForce GT610 32GB RAM Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 359183] Sluggish desktop - nvidia gpu memory leak
https://bugs.kde.org/show_bug.cgi?id=359183 vitoriung changed: What|Removed |Added CC||vitori...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358778] Blank space in system tray after upgrade 5.4.3 > 5.5.4
https://bugs.kde.org/show_bug.cgi?id=358778 --- Comment #6 from Petr Vorel --- I found out the culprit. It's the service xembedsniproxy. If I kill it then the blank space disappears. Restarting the service however does not make the blank space reappear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358778] Blank space in system tray after upgrade 5.4.3 > 5.5.4
https://bugs.kde.org/show_bug.cgi?id=358778 --- Comment #7 from Petr Vorel --- Created attachment 97105 --> https://bugs.kde.org/attachment.cgi?id=97105&action=edit xsession-errors -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 359184] New: Preview not working for small screenshots
https://bugs.kde.org/show_bug.cgi?id=359184 Bug ID: 359184 Summary: Preview not working for small screenshots Product: Spectacle Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: elvis.angelac...@kdemail.net The preview of the screenshot is blank when the screenshot itself is "small", with respect to the screen size. However I can drop/export/save the screenshot just fine. Reproducible: Always Steps to Reproduce: 1. Take a small screenshot, e.g. using Rectangular region or a very small Active Window Actual Results: Preview is blank. Expected Results: Preview widget shows the screenshot as expected. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #10 from Martin Steigerwald --- What also seems to work this: First session is MATE, second is Plasma. I have the impression that things get confused with two Plasma sessions running. Well at least I can now have the session I work most with with Plasma again, while the other runs with MATE. Is there anything else except power management and kscreen, both still disabled, that can mess with screen, display switched on/off, brightness? I would like to find out what component is actually dimming and blanking the screen. It would help to get a clue about whats going on here. Anything in Solid or kded5? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 --- Comment #11 from Martin Steigerwald --- Okay, one more obversation: Things actually got confused with two running Plasma sessions before – two different users – it dimmed the session before sometimes in that case. Yet it never switched off the display without enabling it again on a key press before, so that is new. I will set the severity a big back, since it appears to work with one Plasma sessions and I bet two sessions running on different X displays are a not well tested usecase. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359177] blanks out original plasma session when I start a new a new plasma session from it
https://bugs.kde.org/show_bug.cgi?id=359177 Martin Steigerwald changed: What|Removed |Added Severity|grave |major -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 358929] Script interpreter cannot be found, but kross is installed
https://bugs.kde.org/show_bug.cgi?id=358929 --- Comment #1 from Remy Glaser --- Downgrading krosspython to 4:4.14.2-0ubuntu1 (vivid version) works as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 347219] files overlap with gnome account
https://bugs.kde.org/show_bug.cgi?id=347219 --- Comment #19 from Matt Scheirer --- If Ubuntu wants their "critical" bug fixed, they make kaccounts-providers conflict with account-plugins. The fact they are refusing to do so is insane, because the whole reason this is a problem in the first place is that apps using accounts-sso will produce duplicate account configuration options if we have duplicates in the profiles dir. This is the most "not KDE's problem" of any problem ever. We're using an Intel framework for accounts management the way it is intended, as are Canonical, and by design when two messaging providers provide the same service they should conflict one another rather than provide redundant entries that mess up the GUIs. How is the practicality of adding a KDE specific tag to our provider files and then renaming them with a prefix? I can go dig into the kaccounts-integration code and see if its possible. That doesn't solve the implementation and design problem around accounts-sso that a user of accounts should be loading all the providers it finds to allow third parties to provide account support, but I'm pretty sure we all know nobody is ever going to do that with the state accounts-sso and telepathy are in. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359185] New: screensaver failing if changing hostname
https://bugs.kde.org/show_bug.cgi?id=359185 Bug ID: 359185 Summary: screensaver failing if changing hostname Product: plasmashell Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: g.schli...@dukun.de CC: bhus...@gmail.com, plasma-b...@kde.org If changing the hostname via [code] $ hostname example $ hostname badexample [/code] and locking kde5 plasma session afterwards, kscreensaver complains about being malfunctioning. it recommends switching to a console and executing 'loginctl unlock-sessions' to access the screen again. changing hostname back to the value it was before plasma started fixes the problem. Reproducible: Always Steps to Reproduce: 1. start plasma 2. change hostname 3. lock screen Actual Results: error warning -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Ovidiu-Florin BOGDAN changed: What|Removed |Added CC||ovidiu@gmail.com --- Comment #46 from Ovidiu-Florin BOGDAN --- I've kind of found a workaround for this issue and I've blogged about it here: http://ovidiu.geekaliens.com/en/2016/01/05/multiple-merge-candidates-aborting-workaround/ I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 359170] RSIbreak does not show effect during breaks
https://bugs.kde.org/show_bug.cgi?id=359170 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from Albert Astals Cid --- On 0.12 i improved a bit the wording of the configuration dialog and should be a bit less confusing. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #47 from Witko --- Yes i was already thinking about linking it here. The issue is that i got this failure mostly on MS Exchange IMAP. Cos i have 2 gmail accounts and one MS Exchange. All IMAP. On the MS Exchange i have multiple folders + kmail filtering(moving from Inbox to folder) Im not sure how to move it on MS Exchange. Wil try to find out. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 359186] New: Blutooth icon on the desktop bottom right (mini program?) even if Blutooth is disabled in BIOS and system settings
https://bugs.kde.org/show_bug.cgi?id=359186 Bug ID: 359186 Summary: Blutooth icon on the desktop bottom right (mini program?) even if Blutooth is disabled in BIOS and system settings Product: Bluedevil Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libbluedevil Assignee: now...@gmail.com Reporter: peterm.el...@yahoo.de Blutooth icon on the desktop bottom right (mini program?) even if Blutooth is disabled in BIOS and system settings LEAP 42.1 Reproducible: Always Steps to Reproduce: 1. boot 2. and 3. see Actual Results: blutooth icon Expected Results: blutooth icon should not be there see also: https://bugzilla.suse.com/show_bug.cgi?id=965543 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 359186] Blutooth icon on the desktop bottom right (mini program?) even if Blutooth is disabled in BIOS and system settings
https://bugs.kde.org/show_bug.cgi?id=359186 --- Comment #1 from David Rosca --- What is your version? And also, do you happen to have enabled "Always show all entries" in system tray settings? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359187] New: kmail crashes
https://bugs.kde.org/show_bug.cgi?id=359187 Bug ID: 359187 Summary: kmail crashes Product: kmail2 Version: 4.14.2 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: w201...@ya.ru Application: kmail (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.19.0-32-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: пытался отправить документ из Libre Office по почте, но программа kmail внезапно завершилась -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a2cbdf800 (LWP 4119))] Thread 2 (Thread 0x7f0a03ff9700 (LWP 4124)): #0 0x7f0a29f2712d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0a21f8bfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a21f8c0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a2a8c37be in QEventDispatcherGlib::processEvents (this=0x7f09fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f0a2a8950af in QEventLoop::processEvents (this=this@entry=0x7f0a03ff8da0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f0a2a8953a5 in QEventLoop::exec (this=this@entry=0x7f0a03ff8da0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0a2a791c5f in QThread::exec (this=this@entry=0xd85a40) at thread/qthread.cpp:537 #7 0x7f0a2a876823 in QInotifyFileSystemWatcherEngine::run (this=0xd85a40) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f0a2a79432f in QThreadPrivate::start (arg=0xd85a40) at thread/qthread_unix.cpp:349 #9 0x7f0a277f6182 in start_thread (arg=0x7f0a03ff9700) at pthread_create.c:312 #10 0x7f0a29f3447d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f0a2cbdf800 (LWP 4119)): [KCrash Handler] #6 ref (this=0x0) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #7 QString (other=..., this=0x14a2230) at /usr/include/qt4/QtCore/qstring.h:726 #8 AddrSpec (this=0x14a2228) at ../../kmime/kmime_header_parsing.h:55 #9 Mailbox (this=0x14a2220) at ../../kmime/kmime_header_parsing.h:69 #10 node_copy (src=0x10925e0, to=0xb48488, from=0xb08d30, this=0x7a591fc0) at /usr/include/qt4/QtCore/qlist.h:399 #11 QList::detach_helper (this=0x7a591fc0, alloc=) at /usr/include/qt4/QtCore/qlist.h:711 #12 0x7f0a26cca9d1 in detach_helper (this=0x7a591fc0) at /usr/include/qt4/QtCore/qlist.h:725 #13 QList (l=..., this=0x7a591fc0, this@entry=0x7a591860) at /usr/include/qt4/QtCore/qlist.h:122 #14 KMime::Headers::Generics::MailboxList::mailboxes (this=) at ../../kmime/kmime_headers.cpp:477 #15 0x7f0a033162b4 in buildAddrStruct (hdr=) at ../../plugins/akonadi_serializer_mail.cpp:162 #16 Akonadi::SerializerPluginMail::serialize (this=, item=..., label=..., data=..., version=) at ../../plugins/akonadi_serializer_mail.cpp:185 #17 0x7f0a2690a3b8 in Akonadi::ItemSerializer::serialize (item=..., label=..., data=..., version=@0x7a59263c: 1) at ../../akonadi/itemserializer.cpp:133 #18 0x7f0a2690ab7f in Akonadi::ItemSerializer::serialize (item=..., label=..., data=..., version=@0x7a59263c: 1, version@entry=@0x7a59263c: 0) at ../../akonadi/itemserializer.cpp:122 #19 0x7f0a268fd358 in Akonadi::ItemCreateJobPrivate::nextPartHeader (this=this@entry=0x1482540) at ../../akonadi/itemcreatejob.cpp:72 #20 0x7f0a268ffa6e in Akonadi::ItemCreateJob::doHandleResponse (this=, tag=..., data=...) at ../../akonadi/itemcreatejob.cpp:207 #21 0x7f0a26915023 in Akonadi::JobPrivate::handleResponse (this=, tag=..., data=...) at ../../akonadi/job.cpp:79 #22 0x7f0a26965842 in Akonadi::SessionPrivate::dataReceived (this=0xd1f5a0) at ../../akonadi/session.cpp:240 #23 0x7f0a2a8aa87a in QMetaObject::activate (sender=0xbc11c0, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3539 #24 0x7f0a2a8aa87a in QMetaObject::activate (sender=sender@entry=0xd0fe98, m=m@entry=0x7f0a2abf9540 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3539 #25 0x7f0a2a8f3720 in QIODevice::readyRead (this=this@entry=0xd0fe98) at .moc/release-shared/moc_qiodevice.cpp:104 #26 0x7f0a28f34ccd in QAbstractSocketPrivate::canReadNotification (this=0xd06b40) at socket/qabstractsocket.cpp:654 #27 0x7f0a28f3dcfd in QReadNotifier::event (this=, e=) at socket/qnativesocketengine.cpp:1151 #28 0x7f0a2adc7e2c in QApplicationPrivate::notify_helper (this=this@entry=0x9e5130, receiver=receiver@entry=0x9ea0c0, e=e@entry=0x7a592c90) at kernel/qapplication.cpp:4567 #29 0x7f0a2adce4a0 in QApplication::notify (this=this@entry=0x
[krunner] [Bug 358985] Command auto-complete should use time-based sorting rather than alphabetical
https://bugs.kde.org/show_bug.cgi?id=358985 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||http://commits.kde.org/plas ||ma-workspace/598f7c99e6ba73 ||ba1849891017d2cc00f8413845 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Kai Uwe Broulik --- Git commit 598f7c99e6ba73ba1849891017d2cc00f8413845 by Kai Uwe Broulik. Committed on 09/02/2016 at 14:38. Pushed by broulik into branch 'master'. [KRunner] Use time-based sorting rather than length for auto-completion This makes more recently typed queries take precedence over older ones. Differential Revision: https://phabricator.kde.org/D901 M +6-18 lookandfeel/contents/runcommand/RunCommand.qml http://commits.kde.org/plasma-workspace/598f7c99e6ba73ba1849891017d2cc00f8413845 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 348128] The sage backend does not starts with sage 6.7
https://bugs.kde.org/show_bug.cgi?id=348128 --- Comment #13 from Filipe Saraiva --- (In reply to jackdyson31 from comment #7) > Hi Fillipe and Fernando, > > Thank you so much for sorting this out - I have just one ask : > > I use Ubuntu LTS 14.04 running the excellent KDE desktop. I have (and am > locked at) Cantor 0.5. Would be possible to rebuild Cantor 0.5 with this > small change and post it as a legacy update for LTS 14.04 ? - it would make > a BIG BIG difference to so many of us who use it (I can't upgrade without > spending days reorganizing). > Hello jackdyson31, unfortunately you will need to compile Cantor to use this fix. Currently the KDE Applications available in Ubuntu 14.04 official repository is 4.13 version, a very old release. > > Cantor makes open mathematics a professional tool for researchwork, so > thanks a lot for this great piece of software, > Thank you! We love to hear positive feedback! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 348128] The sage backend does not starts with sage 6.7
https://bugs.kde.org/show_bug.cgi?id=348128
--- Comment #14 from Filipe Saraiva ---
(In reply to matpen from comment #10)
> Btw, I spotted a problem in the proposed patch.
>
> The current fix uses "(|Math)" to identify a regular expression group that
> might or might not match "Math". Unfortunately, this is a capturing group,
> so the QRegExp object will capture "Math". Later on in the code, the
> captured text are used to identify the current version of Sage. The fix thus
> interferes with this procedure.
>
> The solution I propose (see attachment) uses non-capturing groups to achieve
> the same result.
> Extract of command line output with the current patch (using Sage 6.9):
> [...]
> found version: ("SageMath Version 6.9", "Math", "6", "9")
> using an old version of sage: 0 . 6 . Using the old init command
> [...]
> AttributeErrorTraceback (most recent call last)
> in ()
> > 1 __CANTOR_IPYTHON_SHELL__.autoindent=False
> [...]
>
> Using the patch I propose:
> [...]
> found version: ("SageMath Version 6.9", "6", "9")
> using the current set of commands
> [...]
>
> Please see attachment.
Thank you matpen, your approach is better for solve this bug. If you have
developer account, could you to commit and push it? If not I can to do it for
you.
--
You are receiving this mail because:
You are watching all bug changes.
[kaddressbook] [Bug 357228] KAddressbook crashes on startup with configured CardDav
https://bugs.kde.org/show_bug.cgi?id=357228 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #1 from eric --- I have the same issue. Kaddressbook will crash immediately and at every restart after adding a new contact that has a birthday or anniversary. Adding a contact without a birthday or anniversary will not make kaddressbook crash. See: https://bugs.kde.org/show_bug.cgi?id=358696 After adding this contact with a birthday or anniversary, korganizer will also crash when adding a new to-do or event. See: https://bugs.kde.org/show_bug.cgi?id=353326 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 359185] screensaver failing if changing hostname
https://bugs.kde.org/show_bug.cgi?id=359185 Kai Uwe Broulik changed: What|Removed |Added Component|general |greeter Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Product|plasmashell |kscreenlocker Version|5.5.4 |unspecified Target Milestone|1.0 |--- CC||k...@privat.broulik.de, ||mgraess...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 354728] Korganizer crash wenn make a new event
https://bugs.kde.org/show_bug.cgi?id=354728 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #1 from eric --- More of the same issue: Kaddressbook will crash immediately and at every restart after adding a new contact that has a birthday or anniversary. Adding a contact without a birthday or anniversary will not make kaddressbook crash. See: https://bugs.kde.org/show_bug.cgi?id=358696 After adding this contact with a birthday or anniversary, korganizer will also crash when adding a new to-do or event. See: https://bugs.kde.org/show_bug.cgi?id=353326 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 359185] screensaver failing if changing hostname
https://bugs.kde.org/show_bug.cgi?id=359185 --- Comment #1 from Martin Gräßlin --- can you try the binary kscreenlocker_greet with --testing after having changed the hostname? It's in the libexec path. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 359147] Ark process hangs if no plugin could be found to create a new archive
https://bugs.kde.org/show_bug.cgi?id=359147 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||15.12.2 Latest Commit||http://commits.kde.org/ark/ ||302f86db350aa270094f8db73c3 ||eda8451fc2811 --- Comment #1 from Elvis Angelaccio --- Git commit 302f86db350aa270094f8db73c3eda8451fc2811 by Elvis Angelaccio. Committed on 09/02/2016 at 14:58. Pushed by elvisangelaccio into branch 'Applications/15.12'. Properly finish AddToArchive jobs Currently Ark hangs when AddToArchive::slotStartJob() returns before having started the underlying AddJob. Calling emitResult() before calling 'return' fixes the issue. FIXED-IN: 15.12.2 M +6-4kerfuffle/addtoarchive.cpp http://commits.kde.org/ark/302f86db350aa270094f8db73c3eda8451fc2811 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359139] I have a empty space/icon in the system tray
https://bugs.kde.org/show_bug.cgi?id=359139 --- Comment #3 from Raman Gupta --- Killing xembedsniproxy and restarting it manually fixes the problem on my system. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 359185] screensaver failing if changing hostname
https://bugs.kde.org/show_bug.cgi?id=359185 --- Comment #2 from Georg Schlisio --- well ~ > /usr/lib/kscreenlocker_greet --testing No protocol specified QXcbConnection: Could not connect to display :0 [1]2509 abort (core dumped) /usr/lib/kscreenlocker_greet --testing this happens with a lot of programmes, only a restart of plasma fixes this. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 359185] screensaver failing if changing hostname
https://bugs.kde.org/show_bug.cgi?id=359185 --- Comment #3 from Georg Schlisio --- no, sorry, a reset of the hostname fixes this as well. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password
https://bugs.kde.org/show_bug.cgi?id=358125 Martin Gräßlin changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||5.5.5 Latest Commit||http://commits.kde.org/kscr ||eenlocker/fae65f1cdd6446042 ||b31ccd0eafd7a4c0b6623e3 --- Comment #11 from Martin Gräßlin --- Git commit fae65f1cdd6446042b31ccd0eafd7a4c0b6623e3 by Martin Gräßlin. Committed on 09/02/2016 at 14:41. Pushed by graesslin into branch 'Plasma/5.5'. [greeter] Dont quit when last window closes Qt allows to have no screens. If all XRandR screens are disconnected there are also no QScreens. This is from an X11 perspective wrong, but we have to deal with it. No QScreens means that all views are destroyed and no new ones are created. Thus all windows close and the greeter exited successfully which in turn unlocked the screen. This change ensures that the greeter doesn't exit when all windows close. Funnily this was not a problem with the well known issue of Qt crashing when all screens are disconnected. The lock screen handles crashes gracefully and just restarts or more likely Qt also crashes the application using KSld and thus taking down the complete session. FIXED-IN: 5.5.5 M +1-0greeter/main.cpp http://commits.kde.org/kscreenlocker/fae65f1cdd6446042b31ccd0eafd7a4c0b6623e3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password
https://bugs.kde.org/show_bug.cgi?id=358125 --- Comment #12 from Martin Gräßlin --- Git commit 5651785ad6663e2ef4d12a94b0b5f1cb7d40a9a1 by Martin Gräßlin. Committed on 09/02/2016 at 15:37. Pushed by graesslin into branch 'Plasma/5.0'. [greeter] Dont quit when last window closes Qt allows to have no screens. If all XRandR screens are disconnected there are also no QScreens. This is from an X11 perspective wrong, but we have to deal with it. No QScreens means that all views are destroyed and no new ones are created. Thus all windows close and the greeter exited successfully which in turn unlocked the screen. This change ensures that the greeter doesn't exit when all windows close. Funnily this was not a problem with the well known issue of Qt crashing when all screens are disconnected. The lock screen handles crashes gracefully and just restarts or more likely Qt also crashes the application using KSld and thus taking down the complete session. M +1-0ksmserver/screenlocker/greeter/main.cpp http://commits.kde.org/plasma-workspace/5651785ad6663e2ef4d12a94b0b5f1cb7d40a9a1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password
https://bugs.kde.org/show_bug.cgi?id=358125 --- Comment #13 from Martin Gräßlin --- Git commit 1fe565e5dae31e57d81556b07e7459be14c5d834 by Martin Gräßlin. Committed on 09/02/2016 at 15:39. Pushed by graesslin into branch 'Plasma/5.1'. [greeter] Dont quit when last window closes Qt allows to have no screens. If all XRandR screens are disconnected there are also no QScreens. This is from an X11 perspective wrong, but we have to deal with it. No QScreens means that all views are destroyed and no new ones are created. Thus all windows close and the greeter exited successfully which in turn unlocked the screen. This change ensures that the greeter doesn't exit when all windows close. Funnily this was not a problem with the well known issue of Qt crashing when all screens are disconnected. The lock screen handles crashes gracefully and just restarts or more likely Qt also crashes the application using KSld and thus taking down the complete session. M +1-0ksmserver/screenlocker/greeter/main.cpp http://commits.kde.org/plasma-workspace/1fe565e5dae31e57d81556b07e7459be14c5d834 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password
https://bugs.kde.org/show_bug.cgi?id=358125 --- Comment #16 from Martin Gräßlin --- Git commit 23a9ed7ba9995570227dbcd69c23f009de7dde49 by Martin Gräßlin. Committed on 09/02/2016 at 15:41. Pushed by graesslin into branch 'Plasma/5.4'. [greeter] Dont quit when last window closes Qt allows to have no screens. If all XRandR screens are disconnected there are also no QScreens. This is from an X11 perspective wrong, but we have to deal with it. No QScreens means that all views are destroyed and no new ones are created. Thus all windows close and the greeter exited successfully which in turn unlocked the screen. This change ensures that the greeter doesn't exit when all windows close. Funnily this was not a problem with the well known issue of Qt crashing when all screens are disconnected. The lock screen handles crashes gracefully and just restarts or more likely Qt also crashes the application using KSld and thus taking down the complete session. M +1-0ksmserver/screenlocker/greeter/main.cpp http://commits.kde.org/plasma-workspace/23a9ed7ba9995570227dbcd69c23f009de7dde49 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 348128] The sage backend does not starts with sage 6.7
https://bugs.kde.org/show_bug.cgi?id=348128 --- Comment #15 from mat...@dnet.it --- > Thank you matpen, your approach is better for solve this bug. If you have > developer account, could you to commit and push it? If not I can to do it > for you. Sorry Filipe, I do not have a developer account... It would be great if you could take over the tast of pushing the patch. Thank you! -- You are receiving this mail because: You are watching all bug changes.
