[plasmashell] [Bug 374072] plasmashell spams log with "QFileInfo::absolutePath: Constructed with empty filename"
https://bugs.kde.org/show_bug.cgi?id=374072 --- Comment #8 from George R. Goffe --- Justin, Let's close this one too. I haven't seen it in a while. George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378795] Konsole text on fully maximized widget displays top 3-4 lines at low intensity
https://bugs.kde.org/show_bug.cgi?id=378795 --- Comment #7 from George R. Goffe --- Justin, Thanks for responding... I haven't seen this bug in several years. Sigh. Close it please. Thanks, George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425759] Konsole alarm configuration missing
https://bugs.kde.org/show_bug.cgi?id=425759 --- Comment #8 from George R. Goffe --- Christoph, Yes... and MANY thanks for the information. Best regards... STAY SAFE! George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425759] Konsole alarm configuration missing
https://bugs.kde.org/show_bug.cgi?id=425759 --- Comment #6 from George R. Goffe --- Hi, The modification of the "Shell" profile made the whole konsole flash. Thanks for all your help! Regards, George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425759] Konsole alarm configuration missing
https://bugs.kde.org/show_bug.cgi?id=425759 --- Comment #5 from George R. Goffe --- Hi, Thanks to those who responded. I can see that I left some information out of my initial report. I am not using the KDE desktop at this time. I think that this is where the KDE settings and not in konsole. I will try the .local change I REALLY LIKE KONSOLE by the way. Thanks again for responding. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425759] Konsole alarm configuration missing
https://bugs.kde.org/show_bug.cgi?id=425759 --- Comment #1 from George R. Goffe --- The sound part of this system is broken so NO audio alarms or alerts are effective. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425759] New: Konsole alarm configuration missing
https://bugs.kde.org/show_bug.cgi?id=425759 Bug ID: 425759 Summary: Konsole alarm configuration missing Product: konsole Version: 20.04.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- SUMMARY I'm having trouble with konsole. I want to change the alarm from a sound to a flash. I don't see any place where this kind of change can be made. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: plasma-desktop-5.19.4-2.fc33.x86_64 (available in About System) KDE Plasma Version: kde-settings-plasma-32.2-2.fc33.noarch KDE Frameworks Version: Qt Version: qt3-3.3.8b-84.fc33.x86_64 ADDITIONAL INFORMATION This is a Fedora Core System (Rawhide, x86_64). ALL available updates/patches are installed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #20 from George R. Goffe --- I hear what you're saying. In attempting to isolate the problem I have found (I think) shortcomings in the code. Things like turning on debug mode with kde et. al., identifying the necessary parts of kde that should be running but aren't, the need for a better logging system, the ability to turn on/off debug for kde components and/or starting/restarting kde components. Some/all of these would have gone a long way towards identifying where the problem happens and why. As it is now, I'm back to using "nomodeset" with NO problems with kde. The only thing left is to activate the .xinitrc in "my" home directory. Clearly something has changed but what? I REALLY do appreciate your (and others) time and energy spent in working this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #18 from George R. Goffe --- Rex, I am interested in contributing to the rawhide releases. I don't know enough to do much debugging on my own though. For the most part, I work well with developers... forming a team of sorts. I am more than willing to work with developers to resolve these kinds of problems... WHEN they are willing. I have a rather long history of systems administration type work (about 50 years) and have been a developer in the past. I like working with developers... I learn with EVERY experience and I like to think that they learn too. Thanks for all your input! George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 George R. Goffe changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED --- Comment #16 from George R. Goffe --- I'm hoping that this post will resolve the needs info flag on this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #15 from George R. Goffe --- Created attachment 119511 --> https://bugs.kde.org/attachment.cgi?id=119511=edit flat file containing all "kde" rpms and their "current" levels Thank you VERY MUCH for your help/interest/support/WAY COOL CODE. George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #14 from George R. Goffe --- Christoph, Thanks for your response AND your question. I have tried several of the .iso images provided by the Fedora project (fc27, fc28, fc29, fc31). I implemented the "nomodeset" change and "my" .xinitrc file with NO problems up to fc31). The problem seems to have started with fc30 which I gave up on in favor of fc31 (rawhide). I have responded with several comments 4, 7, 10 and 12. I am currently running a FC31 system with KDE et. al. at their "current/latest" version(s). I'll add a list of all(?) my kde components to this upgrade. What do you mean by "stock liveCD"? Only one provided by KDE.org? Given my current status, I don't think a out of the box liveCD would show/prove anything. It seems to me that comment 12 and possibly 10 show where I am at this point but I'll summarize with my latest state/info since I do have an update: Current system is FC31 (rawhide). nomodeset is active in the kernel commandline at boot. The startx command works just fine (I'm at runlevel 3 (NO DM active). my .xinitrc is NOT active (I disabled it as part of a debugging effort). To get to this state I disabled all "my" modifications and put them back one at a time. So far, no problems. My next step is to activate my .xinitrc which contains ONLY a "/usr/bin/bash -xv /usr/bin/bash/startkde" command. All these hoops seem to point out the need for something from KDE.org to query all KDE "services or daemons" that should be running AND verify their status (i.e., running). Possibly, some way to start inactive/broken services. Some way to turn on a global and/or individual logging activity within the KDE components. This would help the debugging effort immensely. I will post the results of this change later today. Thanks again for your attention to this problem. George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #12 from George R. Goffe --- It's late... I don't see what info is needed. Can you tell me the comment number where the request is made please? In any event, I have info to submit here: 1) This bug continues to exist with "NOMODESET" in the kernel boot parameters. 2) With my profile active AND .xinitrc the bug seems to exist. 3) KDE is now working. "currently", nomodeset is NOT set and .xinitrc is NOT present... KDE startup executes seemingly correctly in a reasonable amount of time. The freeze is gone. 4) I'm trying to isolate where the problem occurrs. I will post here when/if I discover something. Thanks, George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #10 from George R. Goffe --- David, I have reinstalled several older versions of Fedora Core (27, 29, 31) in a virtual environment (VirtualBox). FC27 and FC29 seem to be working well... even with the startx and .xinitrc changes. I have been working on the Fedora Core 31 virtual machine by applying package installations "dnf install '*xorg*' and other "normal" upgrades but still no joy (WITH NOMODESET installed). I have removed the "nomodeset" kernel command-line parameter and am seeing a more or less "normal" response to the startx & .xinitrc setup. All these Fedora Core systems worked with "SDDM". As I understand it, "nomodeset" turns off the kernel level hardware support for the video card. Here's what one site says "https://askubuntu.com/questions/716957/what-do-the-nomodeset-quiet-and-splash-kernel-parameters-mean": The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts.. This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen. Unfortunately, on some cards this doesn't work properly and you end up with a black screen. Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Have you seen anything in the KDE code that might depend on the setting of "nomodeset"? Regards, George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #9 from George R. Goffe --- David, Thanks for your response. Up to the FC30 system, KDE was working fine... startup took less than 2 minutes. Along came FC30... Start up times > 30 minutes... and longer. The problem is that I got disgusted after 10-20 minutes and went to get lunch... an hour (or more) later there was a KDE screen. Not what I would call the best of circumstances. My latest results show that no matter how long I wait, nothing appears. This is on a freshly installed FC31 system with NO user mods and using SDDM. It's like some component of KDE has made a request of some other component that is not responding or isn't running. Using run level 3, the startx, and .xinitrc I executed the startkde script with "-xv" flags, "/usr/bin/bash -xv /usr/bin/startkde" and recorded the results. With all the clutter, I'm not able to determine what has failed or stopped responding. It would be VERY useful to know just what's supposed to be running. It would be VERY useful to be able to restart failed components to possibly do some debugging? I'm willing to give whatever help I can give to get this problem resolved. The bug report at "https://bugs.kde.org/show_bug.cgi?id=380495; looked like a good match to the symptoms that I'm seeing so I added my info to that report. What can I do to help get this problem resolved? As it is now, KDE is NOT usable. George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 George R. Goffe changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #7 from George R. Goffe --- Hi, This problem still seems to exist, even with an OUT OF THE BOX FC31 system AND no other modifications of any kind. Is someone working this problem? If not, what do I need to do to get some action on this from the KDE folks? Please help, George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380495] Freezes during login process
https://bugs.kde.org/show_bug.cgi?id=380495 --- Comment #11 from George R. Goffe --- This problem still seems to exist. Is anyone working this bug? George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380495] Freezes during login process
https://bugs.kde.org/show_bug.cgi?id=380495 --- Comment #10 from George R. Goffe --- Dave, Unsupported? Are you kidding me? I've been using KDE for over 10 years and have not had this problem. I have in fact tried SDDM and still have the problem. George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380495] Freezes during login process
https://bugs.kde.org/show_bug.cgi?id=380495 --- Comment #7 from George R. Goffe --- I forgot to indicate "my" level of ksplashqml... so here it is: plasma-workspace-5.15.3-1.fc31.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380495] Freezes during login process
https://bugs.kde.org/show_bug.cgi?id=380495 George R. Goffe changed: What|Removed |Added CC||grgo...@yahoo.com --- Comment #6 from George R. Goffe --- Created attachment 118832 --> https://bugs.kde.org/attachment.cgi?id=118832=edit gzip'd file containing the execution of startkde from my .xinitrc file. Hi, I think I have this same problem with a Fedora Core 31 (rawhide) system. The system is freshly installed and has several rounds of "normal" package upgrades. I have my run level set to 3, a text mode login. After login I issue a startx command which uses my .xinitrc config file which contains " /usr/bin/bash -xv /usr/bin/startkde". Startkde just never ends. I have included output of this .xinitrc script. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 147094] The "--geometry" option does not work for Konsole
https://bugs.kde.org/show_bug.cgi?id=147094 --- Comment #26 from George R. Goffe --- Christoph, I think part of the problem is described by comment 13 below. I'll give your suggestion a try anyway. George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 147094] The "--geometry" option does not work for Konsole
https://bugs.kde.org/show_bug.cgi?id=147094 --- Comment #24 from George R. Goffe --- Correction: "Why would someone choose to implement geometry is beyond me" should read "Why would someone choose to implement geometry this way is beyond me" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 147094] The "--geometry" option does not work for Konsole
https://bugs.kde.org/show_bug.cgi?id=147094 --- Comment #23 from George R. Goffe --- Hi, I think I reported this "kind" of bug some time ago... I'm currently using konsole5-18.12.2-1.fc30.x86_64... a Fedora 30 (rawhide) system. It appears to work from the command line of another konsole instance. I thank Mr. Wu for pointing out that the unit of measure is PIXELS and not the "normal" X11 way of specifying geometry. Why would someone choose to implement geometry is beyond me. Sorry. konsole -geometry 01210x610+011+011 produced a knosole near the top left side of the desktop (kde that is). Does the above mean that geometry is supported? George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #5 from George R. Goffe --- Created attachment 116709 --> https://bugs.kde.org/attachment.cgi?id=116709=edit uncompressed flat file containing output from the ps command. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #4 from George R. Goffe --- David, The default display manager worked... I went back to trying to startkde and gave up in disgust... left it with a working mouse pointer and an otherwise black screen. Came back about an hour later and kde was now displaying a desktop. I noticed some tweaks that I missed earlier and attempted to correct them. System settings had other ideas though. "Global Shortcut daemon" was not running. Several other items seemed to put system settings in a loop. Clearly there seems to be some kde components that are not running. I've included the output of the ps command... if you could identify what's missing and how to start them or troubleshoot them. Thanks for your help, George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #2 from George R. Goffe --- David, I'm not sure what you mean by "Display Manager". Can you elucidate please? My knowledge of KDE doesn't go much deeper than having .xinitrc contain "startkde" and my issuing a startx command. I have done some minor configuration changes with the "systems manager" tool... Most of these changes are what I would call tweaks. George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] New: kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 Bug ID: 401808 Summary: kde fails to actualize a desktop at startup Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: grgo...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 116704 --> https://bugs.kde.org/attachment.cgi?id=116704=edit uncompressed flat file from /var/log SUMMARY startx with .xinitrc containing startkde fails to show a desktop. I have NO idea where this bug really belongs because KDE appears to be stuck somewhere in it's initialization processing. This is a Fedora 30 x86_64 distribution. kde-workspace-common-4.11.22-23.fc29.noarch is as close as I can come to where the problem possibly exists. Are there other files you need to see? STEPS TO REPRODUCE 1. startx 2. 3. OBSERVED RESULT Splash screen appears with a small circle chasing itself. Finally this ends and a blank screen appears. The mouse works and displays a cursor-pointer but NOTHING else appears. Is there a hidden trick to get kde to show more of what it's doing? What processes should be running when kde is behaving "normally"? Is there a log other than Xorg.0.log? /var/log/messages shows nothing. EXPECTED RESULT a fully operational kde desktop SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: kf5-plasma-5.52.0-2.fc30.x86_64 (available in About System) KDE Plasma Version: KDE Frameworks Version: kf5-frameworkintegration-5.52.0-1.fc30.x86_64 Qt Version: qt5-qtenginio-1.6.2-19.fc30.x86_64 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 320844] Several warning messages appear on stdout at start up and at end of run.
https://bugs.kde.org/show_bug.cgi?id=320844 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 287013] Sorting by "status" is missing.
https://bugs.kde.org/show_bug.cgi?id=287013 --- Comment #4 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 359370] Fields that need to be filled in during bug reporting are hard to see.
https://bugs.kde.org/show_bug.cgi?id=359370 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377903] auto hide fails for task panel
https://bugs.kde.org/show_bug.cgi?id=377903 --- Comment #4 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 327102] ctrl-d in konsole killed ALL related processes
https://bugs.kde.org/show_bug.cgi?id=327102 --- Comment #2 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358412] Attempt to logout from KDE crashed.
https://bugs.kde.org/show_bug.cgi?id=358412 --- Comment #2 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 304265] at startup, file menu is too small to show filenames
https://bugs.kde.org/show_bug.cgi?id=304265 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361123] numerous messages about ktorrent and nepomuk and/or virtuoso backend
https://bugs.kde.org/show_bug.cgi?id=361123 --- Comment #2 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 352970] create a bug report via ktorrent -> help -> bug report produces incorrect product string
https://bugs.kde.org/show_bug.cgi?id=352970 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 352969] Missing method to change font sizes with ctrl-"+ or -"
https://bugs.kde.org/show_bug.cgi?id=352969 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 350734] Move selected before "move after download completes" finishes, creating an error condition "download missing components"
https://bugs.kde.org/show_bug.cgi?id=350734 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 347987] --foreground (--fg) --background (--bg) specifications are ignored
https://bugs.kde.org/show_bug.cgi?id=347987 --- Comment #2 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 345485] Download went through the "end of torrent" processing but is NOT complete
https://bugs.kde.org/show_bug.cgi?id=345485 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 343865] Ktorrent seems to run wild after a while consuming all memory/swap
https://bugs.kde.org/show_bug.cgi?id=343865 --- Comment #8 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) No activity? Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 339497] ktorrent reports download complete but the % complete is 99.98
https://bugs.kde.org/show_bug.cgi?id=339497 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 342403] Manual execution of "Check Data" runs VERY slowly
https://bugs.kde.org/show_bug.cgi?id=342403 --- Comment #3 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 338867] ktorrent randomly reports falsely a torrent's completion
https://bugs.kde.org/show_bug.cgi?id=338867 --- Comment #2 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 338866] Move torrent to a directory with bad permissions fails silently
https://bugs.kde.org/show_bug.cgi?id=338866 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 338867] ktorrent randomly reports falsely a torrent's completion
https://bugs.kde.org/show_bug.cgi?id=338867 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 338465] sharing ratio settings ineffective when selecting multiple torrents
https://bugs.kde.org/show_bug.cgi?id=338465 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 337596] ktorrent randomly reports download complete in error
https://bugs.kde.org/show_bug.cgi?id=337596 --- Comment #1 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 277604] KTorrent: 4.2dev anomalous behaviors
https://bugs.kde.org/show_bug.cgi?id=277604 --- Comment #5 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 346226] Unexpected condition popup
https://bugs.kde.org/show_bug.cgi?id=346226 --- Comment #4 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 366600] print scrn key produces no apparent behavior
https://bugs.kde.org/show_bug.cgi?id=366600 --- Comment #2 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 328778] Downloaded files location is updated even if the move fails.
https://bugs.kde.org/show_bug.cgi?id=328778 --- Comment #4 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 323207] build of latest repository fails
https://bugs.kde.org/show_bug.cgi?id=323207 --- Comment #8 from George R. Goffe --- Andrew (andrew.croutha...@kdemail.net) Let's kill this one, ok? George -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 277604] KTorrent: 4.2dev anomalous behaviors
https://bugs.kde.org/show_bug.cgi?id=277604 --- Comment #4 from George R. Goffe --- Andrew, The age of this bug report and the lack of activity by the developer indicates to me that he just doesn't care. I have stopped using Ktorent due to this perceived lack of concern Let's just close it, ok? George... -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358805] ksplashqml segfault
https://bugs.kde.org/show_bug.cgi?id=358805 --- Comment #7 from George R. Goffe --- Andrew, I haven't seen this in some time... Let's close it, ok? Best regards, George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358403] konsole spontaneous crash at exit
https://bugs.kde.org/show_bug.cgi?id=358403 --- Comment #2 from George R. Goffe --- Andrew, I haven't seen this in some time... Let's close it, ok? Best regards, George... -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 334164] building ktorrent from the repository fails: undefined reference to `bt::qHash(bt::SHA1Hash const&)'
https://bugs.kde.org/show_bug.cgi?id=334164 --- Comment #12 from George R. Goffe --- Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 328778] Downloaded files location is updated even if the move fails.
https://bugs.kde.org/show_bug.cgi?id=328778 --- Comment #2 from George R. Goffe --- If the developer doesn't care about this one then why should we? I stopped reporting AND using Ktorrent some time ago. Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 346226] Unexpected condition popup
https://bugs.kde.org/show_bug.cgi?id=346226 --- Comment #2 from George R. Goffe --- Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 328867] Ktorrent (dev) crash at startup
https://bugs.kde.org/show_bug.cgi?id=328867 --- Comment #4 from George R. Goffe --- Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[kpackagekit] [Bug 270321] software system windows ussualy crashed (
https://bugs.kde.org/show_bug.cgi?id=270321 --- Comment #5 from George R. Goffe --- Andrew, Thanks for your help. I would point to this bug as evidence to the wast of time statement. Again, bugs with NO activity for N years should go through an automatic closure process... i.e., contact the user and/or the developer and/or maintainer and give them one more chance to avoid the closure. In any event... Best regards, George... -- You are receiving this mail because: You are watching all bug changes.
[kpackagekit] [Bug 270321] software system windows ussualy crashed (
https://bugs.kde.org/show_bug.cgi?id=270321 --- Comment #3 from George R. Goffe --- Andrew, I see that this bug was reported in 2011! Why is that? I would suggest that bugs older than a year be closed automatically with a request for more info needed... like, "Is this bug still happening". I think it's a big waste of everyone's time and energy to spend time on these old bugs. George... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382486] Menuing component and task bar crashing
https://bugs.kde.org/show_bug.cgi?id=382486 --- Comment #5 from George R. Goffe --- Since this problem has not happened since I reported it, I presume it's no longer a problem. Please go ahead and close it. Thanks, George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 321846] Top few lines of konsole are dim.
https://bugs.kde.org/show_bug.cgi?id=321846 --- Comment #6 from George R. Goffe --- Andrew, Thanks for your information... I haven't seen the problem since my last communication. George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386840] help -> what's this produces NOTHING
https://bugs.kde.org/show_bug.cgi?id=386840 --- Comment #4 from George R. Goffe <grgo...@yahoo.com> --- Kurt, The problem seems to have disappeared. I'm at konsole5-17.12.1-1.fc28.x86_64 now. Thanks for your help. George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386840] help -> what's this produces NOTHING
https://bugs.kde.org/show_bug.cgi?id=386840 --- Comment #2 from George R. Goffe <grgo...@yahoo.com> --- I have not seen this since this bug report was created. ctrl-f produces the menu but there's a red 'x' on the left that allows one to delete the find menuing. The menuing that I reported did not have the red 'x'. I will attempt to recreate the problem and report herė -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386841] ctrl-left/right arrow does not move the cursor a word left or right
https://bugs.kde.org/show_bug.cgi?id=386841 --- Comment #2 from George R. Goffe <grgo...@yahoo.com> --- Ahmad, You're absolutely correct. I made the change a few weeks ago... several times in an attempt to resolve the problem but had NO luck. Does this mean that the other two "terms" are broken? ctrl-rightarrow works there but NOT ctrl-leftarrow. You are the man! Could I get you to take a peek at this bug please? https://bugzilla.mozilla.org/show_bug.cgi?id=1381255 THANKS! George.. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 348663] VIM ctrl-left-arrow and ctrl-right-arrow to jump between words not working
https://bugs.kde.org/show_bug.cgi?id=348663 --- Comment #3 from George R. Goffe <grgo...@yahoo.com> --- I forgot to add that this is a Fedora 28 rawhide system. The problem first appeared with Fedora 27. bugzilla.redhat.com has this bug as well, https://bugzilla.redhat.com/show_bug.cgi?id=1507337 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 348663] VIM ctrl-left-arrow and ctrl-right-arrow to jump between words not working
https://bugs.kde.org/show_bug.cgi?id=348663 George R. Goffe <grgo...@yahoo.com> changed: What|Removed |Added CC||grgo...@yahoo.com --- Comment #2 from George R. Goffe <grgo...@yahoo.com> --- This problem exists with vim-enhanced-2:8.0.1283-1.fc28.x86_64. It also exists with command line editing. see bug id 386841. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386841] New: ctrl-left/right arrow does not move the cursor a word left or right
https://bugs.kde.org/show_bug.cgi?id=386841 Bug ID: 386841 Summary: ctrl-left/right arrow does not move the cursor a word left or right Product: konsole Version: 17.08.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- This is a Fedora 28 rawhide system. This problem has been happening since Fedora 27 rawhide. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386840] New: help -> what's this produces NOTHING
https://bugs.kde.org/show_bug.cgi?id=386840 Bug ID: 386840 Summary: help -> what's this produces NOTHING Product: konsole Version: 17.08.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- Konsole started displaying the find menu all the time now. Help what's this produced NOTHING. No popup, no text. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355711] System Settings crashed during exit processing.
https://bugs.kde.org/show_bug.cgi?id=355711 --- Comment #53 from George R. Goffe <grgo...@yahoo.com> --- Hi, I'm running a Fedora 27 (rawhide) system with this version of systemsettings and have not seen this problem in some time. Has it gone away (i.e. been fixed)? plasma-systemsettings-5.10.4-3.fc27.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374072] plasmashell spams log with "QFileInfo::absolutePath: Constructed with empty filename"
https://bugs.kde.org/show_bug.cgi?id=374072 George R. Goffe <grgo...@yahoo.com> changed: What|Removed |Added CC||grgo...@yahoo.com --- Comment #4 from George R. Goffe <grgo...@yahoo.com> --- Created attachment 106951 --> https://bugs.kde.org/attachment.cgi?id=106951=edit gziped flat file of /var/log/messages Hi, I'm running Fedora 27 (rawhide) and am seeing TONS of these and other messages from plasmashell. See attachment. George... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382486] Menuing component and task bar crashing
https://bugs.kde.org/show_bug.cgi?id=382486 --- Comment #3 from George R. Goffe <grgo...@yahoo.com> --- Created attachment 106742 --> https://bugs.kde.org/attachment.cgi?id=106742=edit tar.xz of plasmashell.messages and plasmashell.strace Christoph, Here's more info about this bug... and some extra messsages. George... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382486] Menuing component and task bar crashing
https://bugs.kde.org/show_bug.cgi?id=382486 --- Comment #2 from George R. Goffe <grgo...@yahoo.com> --- Christoph, Apparently this is not a crash... gdb "said" no stack... Here's the log of what did happen. George... (gdb) run Starting program: /usr/bin/plasmashell [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib64/libthread_db.so.1". [New Thread 0x7f88f2a4c700 (LWP 4969)] [New Thread 0x7f88e4bb2700 (LWP 4970)] [New Thread 0x7f88e1517700 (LWP 4971)] [New Thread 0x7f88da394700 (LWP 4972)] [New Thread 0x7f88cf7bc700 (LWP 4973)] [New Thread 0x7f884881e700 (LWP 4974)] [New Thread 0x7f883f81d700 (LWP 4975)] [New Thread 0x7f884781d700 (LWP 4976)] [New Thread 0x7f884681c700 (LWP 4977)] [New Thread 0x7f884581b700 (LWP 4978)] [New Thread 0x7f883e81c700 (LWP 4979)] [New Thread 0x7f883d81b700 (LWP 4980)] [New Thread 0x7f881700 (LWP 4981)] WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Desktop" trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height" [New Thread 0x7f8817950700 (LWP 4982)] Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:362: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:363: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:364: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:365: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:362: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:363: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:364: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:365: TypeError: Cannot read property 'padding' of null Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined s [Thread 0x7f88f2a4c700 (LWP 4969) exited] [Thread 0x7f884681c700 (LWP 4977) exited] [Thread 0x7f883d81b700 (LWP 4980) exited] [Thread 0x7f881700 (LWP 4981) exited] [Thread 0x7f883e81c700 (LWP 4979) exited] [Thread 0x7f884581b700 (LWP 4978) exited] [Thread 0x7f884781d700 (LWP 4976) exited] [Thread 0x7f883f81d700 (LWP 4975) exited] [Thread 0x7f884881e700 (LWP 4974) exited] [Thread 0x7f88cf7bc700 (LWP 4973) exited] [Thread 0x7f88da394700 (LWP 4972) exited] [Thread 0x7f88e1517700 (LWP 4971) exited] [Thread 0x7f88e4bb2700 (LWP 4970) exited] [Thread 0x7f89078f7000 (LWP 4965) exited] [Inferior 1 (process 4965) exited with code 02] (gdb) where No stack. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382486] New: Menuing component and task bar crashing
https://bugs.kde.org/show_bug.cgi?id=382486 Bug ID: 382486 Summary: Menuing component and task bar crashing Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- During KDE (plasma?) init, the component of KDE that provides desktop menuing and the task-bar (same component?) crashes, leaving KDE with major functions unavailable. plasma-desktop-5.10.3-1.fc27.x86_64 It is unclear to me the exact component that's failing. It would sure be nice to have some way of telling what should be running and comparing that with what is running. Being able to restart all of KDE or the portions that have crashed would be a nice feature too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377903] auto hide fails for task panel
https://bugs.kde.org/show_bug.cgi?id=377903 --- Comment #3 from George R. Goffe <grgo...@yahoo.com> --- Wiz, There is no artifact that I can see... what I get is the panel... I can make it hide but then when I do just about anything, it comes back. Might as well not auto-hide. I have seen what I think is the artifact that you're talking about but the panel is ALL blurry AND never goes away... seems to be related to a crash of plasmashell maybe? "Whoever" owns the panel. Sigh... George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377903] auto hide fails for task panel
https://bugs.kde.org/show_bug.cgi?id=377903 --- Comment #1 from George R. Goffe <grgo...@yahoo.com> --- Hi, This problem still appears. I'm using the latest rawhide versions of kde from Fedora (Fedora 27). Current version of this code is plasma-workspace-5.9.5.1-1.fc27.x86_64 Is anyone working on this? George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378795] Konsole text on fully maximized widget displays top 3-4 lines at low intensity
https://bugs.kde.org/show_bug.cgi?id=378795 --- Comment #5 from George R. Goffe <grgo...@yahoo.com> --- Christopf, Alt+Shift+F12 did nothing to change the behavior. Any thoughts as to what I should do? Regards, George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378795] Konsole text on fully maximized widget displays top 3-4 lines at low intensity
https://bugs.kde.org/show_bug.cgi?id=378795 --- Comment #2 from George R. Goffe <grgo...@yahoo.com> --- Kurt, Thank you for taking your time to answer this bug report. Apparently screenshot via shift-prnt-scrn is broken. The tool that Rex suggested that I use does not appear to be able to capture the problem. Are you unable to create the problem? I see this problem with two separate actions. #1) fully maximize the Konsole widget via the up arrow (^); clear the screen (clear cmd), the widget should darken... add 3 or more lines (ls). Screen returns from dimness. #2) make a Konsole, fully maximize it vertically (this is important) move it to far right or far left to get enough room to show the problem when you grab the left/right border and start to drag it to the left/right. The widget doesn't need to occupy the full screen for the dimness to happen... about 7/8ths of the screen will work. For some reason, the whole screen dims but when the grab is released everything returns to normal but the Konsole stays dim until there are 3 or more output lines at the top. Adding more lines reverses the dimness. Really odd bug! George... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 344288] New Fedora 21 x86_64 install; mouse pointer redrawn constantly produces "tails".
https://bugs.kde.org/show_bug.cgi?id=344288 --- Comment #9 from George R. Goffe <grgo...@yahoo.com> --- Hi, As far as I'm concerned this bug can be closed. I'm on Fedora 27 (rawhide) now and havve not seen the bug in years. Thanks for your help, George... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378795] New: Konsole text on fully maximized widget displays top 3-4 lines at low intensity
https://bugs.kde.org/show_bug.cgi?id=378795 Bug ID: 378795 Summary: Konsole text on fully maximized widget displays top 3-4 lines at low intensity Product: konsole Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- Reported also as Fedora Bug 1438439 (bugzilla.redhat.com). See that bug for more details. Fully maximized Konsole is misbehaving. If only 3-4 lines are displayed at the top, the text is dim, more lines and the display is "normal" intensity. This problem appears to be widget size dependent. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 378409] New: dnf install kde'*' produces numerous error messages about packages unavailable
https://bugs.kde.org/show_bug.cgi?id=378409 Bug ID: 378409 Summary: dnf install kde'*' produces numerous error messages about packages unavailable Product: kdelibs Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- Description of problem: Install of KDE produces NUMEROUS error messages about dependencies NOT available Version-Release number of selected component (if applicable): dnf whatprovides /usr/bin/startkde Last metadata expiration check: 0:27:32 ago on Mon Apr 03 05:23:28 2017 PDT. plasma-workspace-5.9.4-1.fc27.x86_64 : Plasma workspace, applications and applets How reproducible: always Steps to Reproduce: 1.dnf install kde'*' 2. 3. Actual results: see below Expected results: successful installation of KDE Additional info: dnf --allowerasing install kde'*' Last metadata expiration check: 0:22:03 ago on Mon Apr 03 05:23:28 2017 PDT. Package kde-apps-rpm-macros-6:4.14.30-1.fc27.noarch is already installed, skipping. Package kde-cli-tools-5.9.4-1.fc27.x86_64 is already installed, skipping. Package kde-filesystem-4-55.fc26.x86_64 is already installed, skipping. Package kde-gtk-config-5.9.4-1.fc27.x86_64 is already installed, skipping. Package kde-l10n-16.12.3-1.fc27.noarch is already installed, skipping. Package kde-partitionmanager-3.0.1-2.fc26.x86_64 is already installed, skipping. Package kde-platform-plugin-1:4.11.22-17.fc26.x86_64 is already installed, skipping. Package kde-runtime-16.12.3-1.fc27.x86_64 is already installed, skipping. Package kde-runtime-flags-16.12.3-1.fc27.noarch is already installed, skipping. Package kde-runtime-libs-16.12.3-1.fc27.x86_64 is already installed, skipping. Package kde-settings-25-5.fc27.1.noarch is already installed, skipping. Package kde-settings-plasma-25-5.fc27.1.noarch is already installed, skipping. Package kde-settings-pulseaudio-25-5.fc27.1.noarch is already installed, skipping. Package kde-style-breeze-5.9.4-1.fc27.x86_64 is already installed, skipping. Package kde-workspace-common-1:4.11.22-17.fc26.noarch is already installed, skipping. Package kdeaddons-atlantikdesigner-3.5.10-15.fc26.x86_64 is already installed, skipping. Package kdecoration-5.9.4-1.fc27.x86_64 is already installed, skipping. Package kdeedu-data-16.12.3-1.fc27.noarch is already installed, skipping. Package kdegames3-3.5.10-24.fc26.x86_64 is already installed, skipping. Package kdegames3-libs-3.5.10-24.fc26.x86_64 is already installed, skipping. Package kdegraphics-mobipocket-16.12.3-1.fc27.x86_64 is already installed, skipping. Package kdegraphics-thumbnailers-16.12.3-1.fc27.x86_64 is already installed, skipping. Package kdelibs-6:4.14.30-1.fc27.x86_64 is already installed, skipping. Package kdelibs-common-6:4.14.30-1.fc27.x86_64 is already installed, skipping. Package kdelibs-devel-6:4.14.30-1.fc27.x86_64 is already installed, skipping. Package kdelibs-ktexteditor-6:4.14.30-1.fc27.x86_64 is already installed, skipping. Package kdelibs-webkit-6:4.14.30-1.fc27.x86_64 is already installed, skipping. Package kdelibs-webkit-devel-6:4.14.30-1.fc27.x86_64 is already installed, skipping. Package kdelibs3-3.5.10-84.fc27.x86_64 is already installed, skipping. Package kdepim-common-7:16.12.2-3.fc26.x86_64 is already installed, skipping. Package kdepim3-libs-3.5.10-19.fc26.x86_64 is already installed, skipping. Package kdepimlibs-4.14.10-19.fc27.x86_64 is already installed, skipping. Package kdepimlibs-akonadi-4.14.10-19.fc27.x86_64 is already installed, skipping. Package kdepimlibs-devel-4.14.10-19.fc27.x86_64 is already installed, skipping. Package kdepimlibs-gpgme-4.14.10-19.fc27.x86_64 is already installed, skipping. Package kdepimlibs-kxmlrpcclient-4.14.10-19.fc27.x86_64 is already installed, skipping. Package kdeplasma-addons-5.9.4-1.fc27.x86_64 is already installed, skipping. Package kdesdk-thumbnailers-16.12.3-1.fc27.x86_64 is already installed, skipping. Package kdesu-1:5.9.4-1.fc27.x86_64 is already installed, skipping. Package kdesvn-1.7.0-2.fc26.x86_64 is already installed, skipping. Error: Problem 1: package kdepim-runtime-1:16.12.3-1.fc27.x86_64 requires libQt5WebEngineCore.so.5()(64bit), but none of the providers can be installed - conflicting requests - nothing provides qt5-qtbase(x86-64) = 5.7.1 needed by qt5-qtwebengine-5.7.1-6.fc26.x86_64 Problem 2: package kdepim-7:16.12.2-3.fc26.x86_64 requires akregator >= 16.12, but none of the providers can be installed - package akregator-16.12.3-1.fc27.x86_64 requires libKF5AkonadiCore.so.5()(64bit), but none of the providers can be installed - conflicting requests - nothing provides qt5-qtbase(x86-64) = 5.7.1 needed by kf5-akonadi-server-16.12.3-1.fc27.x86_64 Problem 3: package kdevelop-9:5.1.0-1.fc27.x86_64
[plasma4] [Bug 377903] New: auto hide fails for task panel
https://bugs.kde.org/show_bug.cgi?id=377903 Bug ID: 377903 Summary: auto hide fails for task panel Product: plasma4 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: desktop Assignee: plasma-b...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- Set auto hide on via panel settings but the panel keeps on showing up. I'm not sure what component of kde (plasma) is responsible for this. my version of plasma (et. al.) is "plasma-workspace-5.9.3-3.fc27.x86_64" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374646] New: System Settings crash (abrt 6) updating "widget decorations"
https://bugs.kde.org/show_bug.cgi?id=374646 Bug ID: 374646 Summary: System Settings crash (abrt 6) updating "widget decorations" Product: systemsettings Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: grgo...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.15-300.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: I was updating settings and had just poked apply for the "Widget Decorations" section. This problem seems to be readily re-creatable... The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3994ad8900 (LWP 20957))] Thread 15 (Thread 0x7f392ddd2700 (LWP 21015)): #0 0x7f39a06a701d in poll () at /usr/lib64/libc.so.6 #1 0x7f399950b156 in g_main_context_poll (priority=, n_fds=1, fds=0x7f39380231a0, timeout=, context=0x7f393803d7e0) at gmain.c:4228 #2 0x7f399950b156 in g_main_context_iterate (context=context@entry=0x7f393803d7e0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3924 #3 0x7f399950b26c in g_main_context_iteration (context=0x7f393803d7e0, may_block=1) at gmain.c:3990 #4 0x7f39a14af73b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f39a146073a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f39a12bd5f3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f399fe6c4e5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #8 0x7f39a12c19da in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7f399d7546ca in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7f39a06b2f7f in clone () at /usr/lib64/libc.so.6 Thread 14 (Thread 0x7f3945def700 (LWP 21011)): #0 0x7f39995507f9 in g_mutex_lock (mutex=mutex@entry=0x7f3934002800) at gthread-posix.c:1336 #1 0x7f399950ad06 in g_main_context_dispatch (context=context@entry=0x7f3934002800) at gmain.c:3850 #2 0x7f399950b1c0 in g_main_context_iterate (context=context@entry=0x7f3934002800, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3929 #3 0x7f399950b26c in g_main_context_iteration (context=0x7f3934002800, may_block=1) at gmain.c:3990 #4 0x7f39a14af73b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f39a146073a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f39a12bd5f3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f399fe6c4e5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #8 0x7f39a12c19da in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7f399d7546ca in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7f39a06b2f7f in clone () at /usr/lib64/libc.so.6 Thread 13 (Thread 0x7f3947df1700 (LWP 21008)): #0 0x7f39a06a2bed in read () at /usr/lib64/libc.so.6 #1 0x7f399954f450 in read (__nbytes=16, __buf=0x7f3947df0a80, __fd=) at /usr/include/bits/unistd.h:44 #2 0x7f399954f450 in g_wakeup_acknowledge (wakeup=0x561dd559e6a0) at gwakeup.c:210 #3 0x7f399950ac60 in g_main_context_check (context=context@entry=0x7f393c001e00, max_priority=2147483647, fds=fds@entry=0x7f393c001c60, n_fds=n_fds@entry=1) at gmain.c:3707 #4 0x7f399950b0f4 in g_main_context_iterate (context=context@entry=0x7f393c001e00, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3926 #5 0x7f399950b26c in g_main_context_iteration (context=0x7f393c001e00, may_block=1) at gmain.c:3990 #6 0x7f39a14af73b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f39a146073a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f39a12bd5f3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f399fe6c4e5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #10 0x7f39a12c19da in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #11 0x7f399d7546ca in start_thread () at /usr/lib64/libpthread.so.0 #12 0x7f39a06b2f7f in clone () at /usr/lib64/libc.so.6 Thread 12 (Thread 0x7f3946df0700 (LWP 21007)): #0 0x7f3999508260 in g_source_iter_clear (iter=iter@entry=0x7f3946defae0) at gmain.c:995 #1 0x7f399950a768 in g_main_context_prepare (context=context@entry=0x7f3930003400, priority=priority@entry=0x7f3946defb60) at gmain.c:3565 #2 0x7f399950b07b in g_main_context_iterate (context=context@entry=0x7f3930003400, block=block@entry=1,
[systemsettings] [Bug 355711] System Settings crashed during exit processing.
https://bugs.kde.org/show_bug.cgi?id=355711 --- Comment #43 from George R. Goffe <grgo...@yahoo.com> --- Christopf, When I notice that the problems I report no longer exist, should I post that "event" on the bug report? It might help you guys? George... -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 366600] New: print scrn key produces no apparent behavior
https://bugs.kde.org/show_bug.cgi?id=366600 Bug ID: 366600 Summary: print scrn key produces no apparent behavior Product: ksnapshot Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: ase...@kde.org Reporter: grgo...@yahoo.com Firefox beta addons list. print-scrn with or without shift produces no apparent activity. Reproducible: Always Steps to Reproduce: 1.Start Firefox 2.(shift) print-scrn 3.note that no popup appears Actual Results: nothing Expected Results: popup menu from ksnapshot with screen contents nothing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.
https://bugs.kde.org/show_bug.cgi?id=346768 --- Comment #71 from George R. Goffe <grgo...@yahoo.com> --- Hi, Please accept my apologies for this out of bandwidth response. Maybe "we" should abandon all the distributions that use 5.5 and go with Fedora Rawhide? I'm sure that would get someone's attention. I use Fedora 23 and Rawhide (24) and don't seem to have these problems. George... -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361123] New: numerous messages about ktorrent and nepomuk and/or virtuoso backend
https://bugs.kde.org/show_bug.cgi?id=361123 Bug ID: 361123 Summary: numerous messages about ktorrent and nepomuk and/or virtuoso backend Product: ktorrent Version: 4.3.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: grgo...@yahoo.com Numerous messages like this one. Why does ktorrent want to do anything with nepomuk and/or virtuoso? Critical: ktorrent(12187)/nepomuk (library): Could not find virtuoso backend Reproducible: Always Steps to Reproduce: 1.unknown 2. 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361119] New: Plasma crash while navigating between virtual desktops with task bar
https://bugs.kde.org/show_bug.cgi?id=361119 Bug ID: 361119 Summary: Plasma crash while navigating between virtual desktops with task bar Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: grgo...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.6-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I have had several days with NO crashes like this one. I've been cheering all those who put in the massive amount of time to fix the problem. I was navigating from desktop #1 to #2 via the button for virtualbox in the task bar when this crash happened. Maybe it's the same one "we've" been chasing for some time or maybe not. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fbacf441940 (LWP 3727))] Thread 15 (Thread 0x7fbaa75ef700 (LWP 3759)): #0 0x7fbac6df1fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fbac231516c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fbaa0003070, timeout=, context=0x7fbaa990) at gmain.c:4135 #2 0x7fbac231516c in g_main_context_iterate (context=context@entry=0x7fbaa990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7fbac231527c in g_main_context_iteration (context=0x7fbaa990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7fbac7c31ecb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fbaa8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fbac7bd8eca in QEventLoop::exec(QFlags) (this=this@entry=0x7fbaa75eec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fbac79f5434 in QThread::exec() (this=this@entry=0x559d830a2850) at thread/qthread.cpp:503 #7 0x7fbacbd439b5 in QQmlThreadPrivate::run() (this=0x559d830a2850) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7fbac79fa3de in QThreadPrivate::start(void*) (arg=0x559d830a2850) at thread/qthread_unix.cpp:331 #9 0x7fbac613560a in start_thread (arg=0x7fbaa75ef700) at pthread_create.c:334 #10 0x7fbac6dfda4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fba9c994700 (LWP 3773)): #0 0x7fbac613ab10 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fba9f96da23 in thread_function (mtx=0x559d833f2170, cond=0x559d833f2198) at ../../../../include/c11/threads_posix.h:159 #2 0x7fba9f96da23 in thread_function (sema=0x559d833f2170) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 0x7fba9f96da23 in thread_function (init_data=init_data@entry=0x559d833f20c8) at lp_rast.c:805 #4 0x7fba9f96d887 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7fbac613560a in start_thread (arg=0x7fba9c994700) at pthread_create.c:334 #6 0x7fbac6dfda4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fba9b993700 (LWP 3774)): #0 0x7fbac613ab10 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fba9f96da23 in thread_function (mtx=0x559d833f22d8, cond=0x559d833f2300) at ../../../../include/c11/threads_posix.h:159 #2 0x7fba9f96da23 in thread_function (sema=0x559d833f22d8) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 0x7fba9f96da23 in thread_function (init_data=init_data@entry=0x559d833f2230) at lp_rast.c:805 #4 0x7fba9f96d887 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7fbac613560a in start_thread (arg=0x7fba9b993700) at pthread_create.c:334 #6 0x7fbac6dfda4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fba9a992700 (LWP 3775)): #0 0x7fbac613ab10 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fba9f96da23 in thread_function (mtx=0x559d833f2440, cond=0x559d833f2468) at ../../../../include/c11/threads_posix.h:159 #2 0x7fba9f96da23 in thread_function (sema=0x559d833f2440) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 0x7fba9f96da23 in thread_function (init_data=init_data@entry=0x559d833f2398) at lp_rast.c:805 #4 0x7fba9f96d887 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87
[plasmashell] [Bug 360912] New: plasma desktoop/plasmashell segfault
https://bugs.kde.org/show_bug.cgi?id=360912 Bug ID: 360912 Summary: plasma desktoop/plasmashell segfault Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: grgo...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: This crash happened after powering up my second screen monitor (Samsung 29" TV). PLEASE NOTE THAT THERE ARE MORE BUGS IN THIS REPORT. +1) drkonqi font WAY TOO SMALL to be readily readable. +2) drkonqi popup has TWO help buttons! - Unusual behavior I noticed: NOTHING but this crash and popup problem - Custom settings of the application: Only one monitor selected. "NOMODESET" boot parameter is NOT specified, KDE display set to make this Samsung TV the primary display. Task bar set to autohide. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbbe77e4940 (LWP 3662))] Thread 8 (Thread 0x7fbbc6d5d700 (LWP 3697)): #0 0x7fbbdf194fdd in poll () at /usr/lib64/libc.so.6 #1 0x7fbbe564f272 in _xcb_conn_wait () at /usr/lib64/libxcb.so.1 #2 0x7fbbe5650ee7 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fbbc9687da9 in QXcbEventReader::run() () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fbbdfd9d3de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbbde4d860a in start_thread () at /usr/lib64/libpthread.so.0 #6 0x7fbbdf1a0a4d in clone () at /usr/lib64/libc.so.6 Thread 7 (Thread 0x7fbbbf9cf700 (LWP 3787)): #0 0x7fbbda6fc719 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fbbda6b7719 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbbda6b809b in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbbda6b827c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbbdffd4ecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbbdff7beca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fbbdfd98434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fbbe40e69b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #8 0x7fbbdfd9d3de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7fbbde4d860a in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7fbbdf1a0a4d in clone () at /usr/lib64/libc.so.6 Thread 6 (Thread 0x7fbbb62e9700 (LWP 3806)): #0 0x7fbbdf194fdd in poll () at /usr/lib64/libc.so.6 #1 0x7fbbda6b816c in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbbda6b827c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbbdffd4ecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fbbdff7beca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbbdfd98434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fbbe40e69b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #7 0x7fbbdfd9d3de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7fbbde4d860a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7fbbdf1a0a4d in clone () at /usr/lib64/libc.so.6 Thread 5 (Thread 0x7fbba700 (LWP 3808)): #0 0x7fbbda6fc734 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fbbda6b717e in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbbda6b8025 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbbda6b827c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbbdffd4ecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbbdff7beca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fbbdfd98434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fbbe40e69b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #8 0x7fbbdfd9d3de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7fbbde4d860a in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7fbbdf1a0a4d in clone () at /usr/lib64/libc.so.6 Thread 4 (Thread 0x7fbbadf0e700 (LWP 3822)): #0 0x7fbbde4ddb10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fbbe6f3f514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
[kde] [Bug 360873] New: Konsole crash
https://bugs.kde.org/show_bug.cgi?id=360873 Bug ID: 360873 Summary: Konsole crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: grgo...@yahoo.com Application: kdeinit5 (15.12.1) Qt Version: 5.5.1 Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: After a period of inactivity, I returned to the monitor and attempted to switch to another, adjacent, virtual desktop when this crash popup appeared. - Unusual behavior I noticed: I have been having trouble with the whole QT/KDE/PLASMA desktop. Spontaneous (to me) crashes, system freezes. KDE NEEDS to be able to restart by itself or manually and reconnect with processes that are already running. This crash has happened due to an earlier crash of something. The desktop and all widgets have disappeared and the desktop manager(?) that responds to keyboard interrupts and provides menues on the background for the desktop has ceased functioning. I did a ctrl-f2 and then restarted X (startx) and this desktop has been running for several days now. I still see earlier processes from the earlier instance of the desktop but have, apparently lost contact with them. I must say that I'm REALY surprised that F23 made it to release when all these KDE/PLASMA issues remain open. I just poked the desktop to get a menu and got another drkonqi popup for an apparent crash. Same one as this one? Who knows? - Custom settings of the application: It is unknown as to which settings are "normal" and which ones are "different". I hide the task bar all the time. I have two monitors but the laptop monitor is de-selected, current monitor is a Samsung 29" TV. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (kdeinit5), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7f2701c5b55c in QXcbScreen::mapFromNative(QPoint const&) const () at /usr/lib64/libQt5XcbQpa.so.5 #6 0x7f2701c639ba in QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) () at /usr/lib64/libQt5XcbQpa.so.5 #7 0x7f2701c4cafd in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib64/libQt5XcbQpa.so.5 #8 0x7f2701c4d433 in QXcbConnection::processXcbEvents() () at /usr/lib64/libQt5XcbQpa.so.5 #9 0x7f271e619161 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7f271f2ce41c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f271f2d38e6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f271e5e973b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f271e5ebb36 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #14 0x7f271e63faa3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f271bc8fe3a in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #16 0x7f271bc901d0 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #17 0x7f271bc9027c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #18 0x7f271e63feaf in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #19 0x7f271e5e6eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #20 0x7f271e5eefac in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #21 0x7f2703fd164e in kdemain () at /usr/lib64/libkdeinit5_konsole.so #22 0x558fb868b463 in handle_launcher_request(int, char const*) [clone .isra.26] () #23 0x558fb868d72b in handle_requests(int) () #24 0x558fb8685e1b in main () Possible duplicates by query: bug 358370, bug 355585. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360684] New: Kwin spontaneous crash
https://bugs.kde.org/show_bug.cgi?id=360684 Bug ID: 360684 Summary: Kwin spontaneous crash Product: kwin Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: grgo...@yahoo.com Application: kwin_x11 (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I had just returned from dinner and powered up the Samsung TV monitor; laptop is de-selected with "nomodeset" on boot command in grub.cfg. Moved the mouse to "wake" the display which caused this crash - Unusual behavior I noticed: Nothing - Custom settings of the application: Unknown The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f86e75b5940 (LWP 3443))] Thread 3 (Thread 0x7f86bbfff700 (LWP 3667)): #0 0x7f86dc46cd63 in select () at /usr/lib64/libc.so.6 #1 0x7f86dd9c952f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f86dd9cb02e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f86dd9cb55e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f86dd974eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f86dd791434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f86e51aa9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #7 0x7f86dd7963de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f86dfb6360a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f86dc476a4d in clone () at /usr/lib64/libc.so.6 Thread 2 (Thread 0x7f86b9f95700 (LWP 3671)): #0 0x7f86dfb68b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7f86e6368514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQt5Script.so.5 #2 0x7f86e6368559 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f86dfb6360a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7f86dc476a4d in clone () at /usr/lib64/libc.so.6 Thread 1 (Thread 0x7f86e75b5940 (LWP 3443)): [KCrash Handler] #5 0x7f86c52f455c in QXcbScreen::mapFromNative(QPoint const&) const () at /usr/lib64/libQt5XcbQpa.so.5 #6 0x7f86c52fc9ba in QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) () at /usr/lib64/libQt5XcbQpa.so.5 #7 0x7f86c52e5afd in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib64/libQt5XcbQpa.so.5 #8 0x7f86c52e6433 in QXcbConnection::processXcbEvents() () at /usr/lib64/libQt5XcbQpa.so.5 #9 0x7f86dd9a7161 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7f86de65c41c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f86de6618e6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f86dd97773b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f86dd979b36 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #14 0x7f86dd9cb422 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #15 0x7f86c534a96d in QUnixEventDispatcherQPA::processEvents(QFlags) () at /usr/lib64/libQt5XcbQpa.so.5 #16 0x7f86dd974eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7f86dd97cfac in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #18 0x7f86e7288c33 in kdemain () at /usr/lib64/libkdeinit5_kwin_x11.so #19 0x7f86dc394580 in __libc_start_main () at /usr/lib64/libc.so.6 #20 0x55b8c597bd99 in _start () Possible duplicates by query: bug 360079, bug 358370, bug 355937, bug 355585. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360591] New: spontaneuous desktop crash
https://bugs.kde.org/show_bug.cgi?id=360591 Bug ID: 360591 Summary: spontaneuous desktop crash Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: grgo...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.4-301.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I was trying to navigate between widgets and moved the mouse pointer over the task bar. - Unusual behavior I noticed: Crash Reporting Assistant problems: 1) two "help" buttons on the left hand bottom 2) font WAY TOO SMALL to be visible; 6pt? 3) after showing me a list of possible bugs, NONE of the "forward/proceed/next" buttons were NON-gray The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f272f969940 (LWP 3502))] Thread 8 (Thread 0x7f270eee2700 (LWP 3523)): #0 0x7f2727319fdd in poll () at /usr/lib64/libc.so.6 #1 0x7f272d7d4272 in _xcb_conn_wait () at /usr/lib64/libxcb.so.1 #2 0x7f272d7d5ee7 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f271180cda9 in QXcbEventReader::run() () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f2727f223de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7f272665d60a in start_thread () at /usr/lib64/libpthread.so.0 #6 0x7f2727325a4d in clone () at /usr/lib64/libc.so.6 Thread 7 (Thread 0x7f2707bd8700 (LWP 3544)): #0 0x7f2727319fdd in poll () at /usr/lib64/libc.so.6 #1 0x7f272283d16c in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f272283d27c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2728159ecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2728100eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2727f1d434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f272c26b9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #7 0x7f2727f223de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f272665d60a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f2727325a4d in clone () at /usr/lib64/libc.so.6 Thread 6 (Thread 0x7f26fe363700 (LWP 3577)): #0 0x7f2727319fdd in poll () at /usr/lib64/libc.so.6 #1 0x7f272283d16c in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f272283d27c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2728159ecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2728100eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2727f1d434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f272c26b9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #7 0x7f2727f223de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f272665d60a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f2727325a4d in clone () at /usr/lib64/libc.so.6 Thread 5 (Thread 0x7f26f7fff700 (LWP 3600)): #0 0x7f2727319fdd in poll () at /usr/lib64/libc.so.6 #1 0x7f272283d16c in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f272283d27c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2728159ecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2728100eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2727f1d434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f272c26b9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #7 0x7f2727f223de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f272665d60a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f2727325a4d in clone () at /usr/lib64/libc.so.6 Thread 4 (Thread 0x7f26f5fb6700 (LWP 3608)): #0 0x7f2726662b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7f272f0c4514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQt5Script.so.5 #2 0x7f272f0c4559 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f272665d60a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7f2727325a4d in clone () at /usr/lib64/libc.so.6 Thread 3 (Thread 0x7f266dd60700 (LWP 3610)): #0 0x7f2728159486 in postEventSourcePrepare(_GSource*, int*) () at /usr/lib64/libQt5Core.so.5 #1
[plasmashell] [Bug 360496] New: spontaneous plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=360496 Bug ID: 360496 Summary: spontaneous plasmashell crash Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: grgo...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.3-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed:Plasmashell crash after attempting to raise the control panel for audio. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc128cdd940 (LWP 6513))] Thread 15 (Thread 0x7fc105005700 (LWP 6530)): #0 0x7fc12068dfdd in poll () at /usr/lib64/libc.so.6 #1 0x7fc11bbb116c in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc11bbb127c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc1214cdecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc121474eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc121291434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc1255df9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc1212963de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 14 (Thread 0x7fc0f5b2c700 (LWP 6539)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fc0fdcdba23 in thread_function () at /usr/lib64/dri/swrast_dri.so #2 0x7fc0fdcdb887 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so #3 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 13 (Thread 0x7fc0f4b2b700 (LWP 6540)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fc0fdcdba23 in thread_function () at /usr/lib64/dri/swrast_dri.so #2 0x7fc0fdcdb887 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so #3 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 12 (Thread 0x7fc0f3b2a700 (LWP 6541)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fc0fdcdba23 in thread_function () at /usr/lib64/dri/swrast_dri.so #2 0x7fc0fdcdb887 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so #3 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 11 (Thread 0x7fc0f2b29700 (LWP 6542)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fc0fdcdba23 in thread_function () at /usr/lib64/dri/swrast_dri.so #2 0x7fc0fdcdb887 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so #3 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 10 (Thread 0x7fc0f1b28700 (LWP 6543)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fc0fdcdba23 in thread_function () at /usr/lib64/dri/swrast_dri.so #2 0x7fc0fdcdb887 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so #3 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 9 (Thread 0x7fc0f0b27700 (LWP 6544)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fc0fdcdba23 in thread_function () at /usr/lib64/dri/swrast_dri.so #2 0x7fc0fdcdb887 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so #3 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 8 (Thread 0x7fc0efb26700 (LWP 6545)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fc0fdcdba23 in thread_function () at /usr/lib64/dri/swrast_dri.so #2 0x7fc0fdcdb887 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so #3 0x7fc11f9d160a in start_thread () at /usr/lib64/libpthread.so.0 #4 0x7fc120699a4d in clone () at /usr/lib64/libc.so.6 Thread 7 (Thread 0x7fc0eeb25700 (LWP 6546)): #0 0x7fc11f9d6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at
[plasmashell] [Bug 360220] New: Crash while returning from monitor sleep mode
https://bugs.kde.org/show_bug.cgi?id=360220 Bug ID: 360220 Summary: Crash while returning from monitor sleep mode Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: grgo...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.3-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: The screens were in standby(?) mode due to inactivity. I moved the mouse to "wake" them up and this crash happened. I had been running a script to compare files on two different disks and removing equal files from the first disk. The font size on this pop up is TOO SMALL for me to see/read well at all. - Unusual behavior I noticed Nothing other than these crashes. This is the second crash since I upgraded this system yesterday.: - Custom settings of the application: I can think of NO settings that might affect this situation. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd9c98b8940 (LWP 11464))] Thread 8 (Thread 0x7fd9a8e36700 (LWP 11465)): #0 0x7fd9c126dfdd in poll () at /usr/lib64/libc.so.6 #1 0x7fd9c7727272 in _xcb_conn_wait () at /usr/lib64/libxcb.so.1 #2 0x7fd9c7728ee7 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fd9ab760da9 in QXcbEventReader::run() () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd9c1e763de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9c05b160a in start_thread () at /usr/lib64/libpthread.so.0 #6 0x7fd9c1279a4d in clone () at /usr/lib64/libc.so.6 Thread 7 (Thread 0x7fd9a5be5700 (LWP 11524)): #0 0x7fd9bc7d5734 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd9bc790ba9 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd9bc791110 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd9bc79127c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd9c20adecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9c2054eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd9c1e71434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd9c61be9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #8 0x7fd9c1e763de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7fd9c05b160a in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7fd9c1279a4d in clone () at /usr/lib64/libc.so.6 Thread 6 (Thread 0x7fd996fe6700 (LWP 11526)): #0 0x7fd9c20ad78a in idleTimerSourcePrepare(_GSource*, int*) () at /usr/lib64/libQt5Core.so.5 #1 0x7fd9bc79070d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd9bc79109b in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd9bc79127c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd9c20adecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9c2054eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd9c1e71434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd9c61be9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #8 0x7fd9c1e763de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7fd9c05b160a in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7fd9c1279a4d in clone () at /usr/lib64/libc.so.6 Thread 5 (Thread 0x7fd995dac700 (LWP 11529)): #0 0x7fd9c126dfdd in poll () at /usr/lib64/libc.so.6 #1 0x7fd9bc79116c in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd9bc79127c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd9c20adecb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd9c2054eca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9c1e71434 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd9c61be9b5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #7 0x7fd9c1e763de in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7fd9c05b160a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7fd9c1279a4d in clone () at /usr/lib64/libc.so.6 Thread 4 (Thread 0x7fd98fbef700 (LWP 11540)): #0 0x7fd9c05b6b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1
[kde] [Bug 359716] New: Spontaneous Konsole crash
https://bugs.kde.org/show_bug.cgi?id=359716 Bug ID: 359716 Summary: Spontaneous Konsole crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: grgo...@yahoo.com Application: kdeinit5 (15.12.2) Qt Version: 5.6.0 Operating System: Linux 4.5.0-0.rc5.git0.1.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Rawhide)" -- Information about the crash: - What I was doing when the application crashed: I had just finished adding a "default" Konsole profile and making changes. - Unusual behavior I noticed: xpad had started. I did NOT start this! I don't use it! Why is it here? - Custom settings of the application: None that I'm aware of. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (kdeinit5), signal: Floating point exception Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2e7fd498c0 (LWP 5139))] Thread 2 (Thread 0x7f2e62c0a700 (LWP 5140)): #0 0x7f2e7d17f1cd in poll () from /usr/lib64/libc.so.6 #1 0x7f2e7b833ee6 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2e7b833ffc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2e7dfd8aeb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f2e7df7fe9a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f2e7dda4523 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f2e7fe0a359 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #7 0x7f2e7dda954f in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f2e7c9bd69a in start_thread () from /usr/lib64/libpthread.so.0 #9 0x7f2e7d18b08d in clone () from /usr/lib64/libc.so.6 Thread 1 (Thread 0x7f2e7fd498c0 (LWP 5139)): [KCrash Handler] #5 0x7f2e7c9c3f79 in pthread_barrier_destroy () from /usr/lib64/libpthread.so.0 #6 0x7f2e5395d07f in lp_rast_destroy () from /usr/lib64/dri/swrast_dri.so #7 0x7f2e53966f71 in llvmpipe_destroy_screen () from /usr/lib64/dri/swrast_dri.so #8 0x7f2e535afe7f in dri_destroy_screen_helper () from /usr/lib64/dri/swrast_dri.so #9 0x7f2e535aff25 in dri_destroy_screen () from /usr/lib64/dri/swrast_dri.so #10 0x7f2e535ae272 in driDestroyScreen () from /usr/lib64/dri/swrast_dri.so #11 0x7f2e7b5bb1c5 in driswDestroyScreen () from /usr/lib64/libGL.so.1 #12 0x7f2e7b596f8c in FreeScreenConfigs.isra.3 () from /usr/lib64/libGL.so.1 #13 0x7f2e7b597009 in glx_display_free () from /usr/lib64/libGL.so.1 #14 0x7f2e7b59715e in __glXCloseDisplay () from /usr/lib64/libGL.so.1 #15 0x7f2e7f27ba42 in XCloseDisplay () from /usr/lib64/libX11.so.6 #16 0x7f2e61274152 in QXcbConnection::~QXcbConnection() () from /usr/lib64/libQt5XcbQpa.so.5 #17 0x7f2e612744e9 in QXcbConnection::~QXcbConnection() () from /usr/lib64/libQt5XcbQpa.so.5 #18 0x7f2e61275ea9 in QXcbIntegration::~QXcbIntegration() () from /usr/lib64/libQt5XcbQpa.so.5 #19 0x7f2e61275fb9 in QXcbIntegration::~QXcbIntegration() () from /usr/lib64/libQt5XcbQpa.so.5 #20 0x7f2e7e2cb125 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib64/libQt5Gui.so.5 #21 0x7f2e7e8b9449 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib64/libQt5Widgets.so.5 #22 0x7f2e7dfb76f2 in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #23 0x7f2e7df83cef in QCoreApplication::~QCoreApplication() () from /usr/lib64/libQt5Core.so.5 #24 0x7f2e7e8bad75 in QApplication::~QApplication() () from /usr/lib64/libQt5Widgets.so.5 #25 0x7f2e648a1328 in kdemain () from /usr/lib64/libkdeinit5_konsole.so #26 0x557117c16da3 in handle_launcher_request(int, char const*) [clone .isra.25] () #27 0x557117c1896a in handle_requests(int) () #28 0x557117c1195d in main () Possible duplicates by query: bug 358403. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 359370] New: Fields that need to be filled in during bug reporting are hard to see.
https://bugs.kde.org/show_bug.cgi?id=359370 Bug ID: 359370 Summary: Fields that need to be filled in during bug reporting are hard to see. Product: drkonqi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: grgo...@yahoo.com I have seen this problem in Fedora 22/23/24. When filling out fields presented by Drkonqi, the fields are the same color as the background thereby making them hard to find. Different shading would make them so much easier to see and use. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359085] New: Plasma Shell(?) crash. No core file.
https://bugs.kde.org/show_bug.cgi?id=359085 Bug ID: 359085 Summary: Plasma Shell(?) crash. No core file. 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: grgo...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.6.0 Operating System: Linux 4.5.0-0.rc2.git3.1.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I was switching to a task via the task bar. Something that looks like a small "stickit" that you make notes to people and stick them on your monitor or refrigerator. I was trying to identify the program so I could remove it from my KDE start list. When I poked the widget itself, this drkonqi popup appeared. - Unusual behavior I noticed: Nothing unusual that I could see. - Custom settings of the application: None that I'm aware of. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f64e805d940 (LWP 19694))] Thread 11 (Thread 0x7f64df528700 (LWP 19723)): #0 0x7f64f6629edd in poll () at /usr/lib64/libc.so.6 #1 0x7f64fb7cc272 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f64df527b80) at /usr/include/bits/poll2.h:46 #2 0x7f64fb7cc272 in _xcb_conn_wait (c=c@entry=0x55f808bbf7a0, cond=cond@entry=0x55f808bbf7e0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7f64fb7cdee7 in xcb_wait_for_event (c=0x55f808bbf7a0) at xcb_in.c:693 #4 0x7f64e0bdef09 in QXcbEventReader::run() (this=0x55f808bcdc20) at qxcbconnection.cpp:1288 #5 0x7f64f72536b8 in QThreadPrivate::start(void*) (arg=0x55f808bcdc20) at thread/qthread_unix.cpp:340 #6 0x7f64f595d69a in start_thread () at /usr/lib64/libpthread.so.0 #7 0x7f64f6635dbd in clone () at /usr/lib64/libc.so.6 Thread 10 (Thread 0x7f64dd703700 (LWP 19726)): #0 0x7f64f6625a5d in read () at /usr/lib64/libc.so.6 #1 0x7f64f21a2880 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7f64dd702a40, __fd=) at /usr/include/bits/unistd.h:44 #2 0x7f64f21a2880 in g_wakeup_acknowledge (wakeup=0x7f64d80015b0) at gwakeup.c:210 #3 0x7f64f215edc4 in g_main_context_check (context=context@entry=0x7f64d990, max_priority=2147483647, fds=fds@entry=0x7f64d0003020, n_fds=n_fds@entry=1) at gmain.c:3632 #4 0x7f64f215f270 in g_main_context_iterate (context=context@entry=0x7f64d990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3837 #5 0x7f64f215f3dc in g_main_context_iteration (context=0x7f64d990, may_block=may_block@entry=1) at gmain.c:3901 #6 0x7f64f7479acb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f64d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #7 0x7f64f742250a in QEventLoop::exec(QFlags) (this=this@entry=0x7f64dd702c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7f64f724e744 in QThread::exec() (this=this@entry=0x7f64f7c7f040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #9 0x7f64f7c0d225 in QDBusConnectionManager::run() (this=0x7f64f7c7f040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:152 #10 0x7f64f72536b8 in QThreadPrivate::start(void*) (arg=0x7f64f7c7f040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #11 0x7f64f595d69a in start_thread () at /usr/lib64/libpthread.so.0 #12 0x7f64f6635dbd in clone () at /usr/lib64/libc.so.6 Thread 9 (Thread 0x7f64d75ef700 (LWP 19768)): #0 0x7f64f6629edd in poll () at /usr/lib64/libc.so.6 #1 0x7f64f215f2cc in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f64cc002e70, timeout=, context=0x7f64cc000990) at gmain.c:4135 #2 0x7f64f215f2cc in g_main_context_iterate (context=context@entry=0x7f64cc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f64f215f3dc in g_main_context_iteration (context=0x7f64cc000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f64f7479acb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f64cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f64f742250a in QEventLoop::exec(QFlags) (this=this@entry=0x7f64d75eec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f64f724e744 in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7f64fa658da5 in QQmlThreadPrivate::run() () at /usr/lib64/libQt5Qml.so.5 #8 0x7f64f72536b8 in QThreadPrivate::start(void*)
[krunner] [Bug 358805] ksplashqml segfault
https://bugs.kde.org/show_bug.cgi?id=358805 --- Comment #3 from George R. Goffe <grgo...@yahoo.com> --- This problem just happens during "normal" processing. I had just updated my system and rebooted and issued a "startx" command to get the GUI up. It just happens. I do have 99+% of all the packages in "dnf group list" installed. Can "we" instrument the crash somehow? Set a "trap" for the crash? I'm all ears. George... -- You are receiving this mail because: You are watching all bug changes.
