[frameworks-knewstuff] [Bug 369646] The 'free' menu in Dolphin's status bar incorrectly lists KDE Partition Manager as not installed
https://bugs.kde.org/show_bug.cgi?id=369646 Nate Grahamchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kne ||wstuff/7d3992479ea1e7a2ad52 ||3a79c73434c44c61f38c Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Nate Graham --- Git commit 7d3992479ea1e7a2ad523a79c73434c44c61f38c by Nathaniel Graham, on behalf of Gregor Mi. Committed on 15/10/2017 at 21:20. Pushed by ngraham into branch 'master'. KMoreTools: Update and fix desktopfiles Summary: Updates to KMoreTools: - add minor code comments and update developer README - update desktop files including fix for PartitionManager and KDiskFree - add a script to easily update the desktop files - add FSearch and AngrySearch to search tools - add new grouping "screenrecorder" with Peek and Simples Screen Recorder - add new grouping "mouse-tools" - add new grouping "font-tools" - add new grouping "language-dictionary" The change is so big because of the update desktop files. The interface did not change. Reviewers: ltoscano, elvisangelaccio, #kde_applications, davidedmundson, ngraham Reviewed By: elvisangelaccio, ngraham Subscribers: ngraham, ltoscano, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D7130 M +2-2autotests/kmoretools/kmoretoolstest.cpp M +4-0autotests/kmoretools/kmoretoolstest2.cpp M +17 -7data/kmoretools-desktopfiles/_INFO A +62 -0data/kmoretools-desktopfiles/_update_all_files.sh A +9-0data/kmoretools-desktopfiles/angrysearch.desktop M +88 -84 data/kmoretools-desktopfiles/catfish.desktop A +77 -0data/kmoretools-desktopfiles/com.uploadedlobster.peek.desktop A +7-0data/kmoretools-desktopfiles/ding.desktop M +1-77 data/kmoretools-desktopfiles/disk.desktop D +---data/kmoretools-desktopfiles/filelight.png A +32 -0data/kmoretools-desktopfiles/filelight.svg A +159 -0data/kmoretools-desktopfiles/fontinst.desktop A +20 -0data/kmoretools-desktopfiles/fontmatrix.desktop A +15 -0data/kmoretools-desktopfiles/fsearch.desktop M +24 -94 data/kmoretools-desktopfiles/giggle.desktop M +0-38 data/kmoretools-desktopfiles/git-cola-folder-handler.desktop M +1-73 data/kmoretools-desktopfiles/git-cola.desktop M +56 -82 data/kmoretools-desktopfiles/gitg.desktop M +144 -64 data/kmoretools-desktopfiles/gnome-search-tool.desktop M +176 -75 data/kmoretools-desktopfiles/gparted.desktop A +161 -0data/kmoretools-desktopfiles/gucharmap.desktop M +3-64 data/kmoretools-desktopfiles/htop.desktop D +0-87 data/kmoretools-desktopfiles/kdf.desktop A +13 -0data/kmoretools-desktopfiles/kding.desktop D +0-127 data/kmoretools-desktopfiles/ksystemlog.desktop M +304 -102 data/kmoretools-desktopfiles/org.gnome.clocks.desktop [TRAILING SPACE] ** M +71 -29 data/kmoretools-desktopfiles/org.kde.filelight.desktop A +156 -0data/kmoretools-desktopfiles/org.kde.kcharselect.desktop [TRAILING SPACE] ** [TRAILING SPACE] ** A +151 -0data/kmoretools-desktopfiles/org.kde.kdf.desktop [TRAILING SPACE] ** [TRAILING SPACE] ** M +68 -36 data/kmoretools-desktopfiles/org.kde.kfind.desktop A +219 -0data/kmoretools-desktopfiles/org.kde.kmousetool.desktop D +0-89 data/kmoretools-desktopfiles/org.kde.kscreengenie.desktop D +0-90 data/kmoretools-desktopfiles/org.kde.ksnapshot.desktop M +139 -13 data/kmoretools-desktopfiles/org.kde.ksysguard.desktop A +188 -0data/kmoretools-desktopfiles/org.kde.ksystemlog.desktop M +74 -12 data/kmoretools-desktopfiles/org.kde.ktimer.desktop R +67 -33 data/kmoretools-desktopfiles/org.kde.partitionmanager.desktop [from: data/kmoretools-desktopfiles/org.kde.PartitionManager.desktop - 052% similarity] A +252 -0data/kmoretools-desktopfiles/org.kde.spectacle.desktop M +60 -113 data/kmoretools-desktopfiles/shutter.desktop M +3841 -245 data/kmoretools-desktopfiles/shutter.svg A +11 -0data/kmoretools-desktopfiles/simplescreenrecorder.desktop M +102 -74 data/kmoretools-desktopfiles/xfce4-taskmanager.desktop M +31 -17 src/kmoretools/kmoretoolspresets.cpp M +13 -1src/kmoretools/kmoretoolspresets.h M +17 -4tests/kmoretools/kmoretoolstest_interactive.cpp The files marked with ** at the end have a problem. either the file contains a trailing space or the file contains a call to a potentially dangerous code. Please read: http://community.kde.org/Sysadmin/CommitHooks#Email_notifications Either fix the trailing space or review the dangerous code.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 Eugenechanged: What|Removed |Added CC||bertyf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385289] Kmail: Crash when moving or deleting imap folder (Wayland)
https://bugs.kde.org/show_bug.cgi?id=385289 --- Comment #6 from David Edmundson--- can you do "thread apply all bt" instead. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 385792] New: ksudoku: Неизвестный параметр qwindowtitle.
https://bugs.kde.org/show_bug.cgi?id=385792 Bug ID: 385792 Summary: ksudoku: Неизвестный параметр qwindowtitle. Product: ksudoku Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: atim...@yandex.ru CC: kde-games-b...@kde.org Target Milestone: --- ksudoku %i -qwindowtitle %c -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 385791] New: kde-gtk-config does not remember changes
https://bugs.kde.org/show_bug.cgi?id=385791 Bug ID: 385791 Summary: kde-gtk-config does not remember changes Product: kde-gtk-config Version: 5.11.0 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: manutort...@chakra-project.org Reporter: sombrag...@sombragris.org CC: aleix...@kde.org Target Milestone: --- After an user sets their preferences as a kcmshell5 module, changes are put into effect. However, on a second run, all values are reset to the lowest value. That is, GTK3 theme is set to Adwaita, GTK2 to whatever comes first in an alphabetical list, and this also applies to the font. The expected behavior is that this module should remember the previous choice made by the user. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385172] update for orbital comet parameters
https://bugs.kde.org/show_bug.cgi?id=385172 --- Comment #4 from claude--- Thanks: In ~/.local/share/kstars, it is only à link... (159B) marked at the current date (15/10) In /usr/share/kstars/comets.dat are the data (155.4kB) marked at the old date. In the file, i see for example the comet C/2017 O1 but i have no answer in the window: "Aucun objet nommé « C/2017 O1 » n'a été trouvé". The list of the comets don't appears. I don't understand what is wrong -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385763] Dashed line in the menu
https://bugs.kde.org/show_bug.cgi?id=385763 Nate Grahamchanged: What|Removed |Added Version|master |5.10.2 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED Platform|Other |Ubuntu Packages --- Comment #5 from Nate Graham --- No longer waiting for info. :) Kubuntu 17.10 Beta uses Plasma 5.10.2. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 381470] Dolphin's Information panel should show date modified information by default (there's plenty of room)
https://bugs.kde.org/show_bug.cgi?id=381470 Nate Grahamchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/bal ||oo-widgets/38681e7d27f57468 ||454df72fff0dedeb38224449 --- Comment #8 from Nate Graham --- Git commit 38681e7d27f57468454df72fff0dedeb38224449 by Nathaniel Graham. Committed on 15/10/2017 at 19:53. Pushed by ngraham into branch 'master'. Show Date Modified information by default in Dolphin's Information Panel and Tooltips Summary: Show Date Modified information by default in Dolphin's Information Panel and Tooltips. Test Plan: Tested in KDE Neon. Works; a fresh install using a clean baloofileinformationrc file results in Date Modified appearing in the Information Panel and Tooltips by default: {F5431178} {F5431177} Reviewers: #dolphin, #kde_applications, #frameworks, aacid, markg Reviewed By: markg Subscribers: markg, elvisangelaccio, anthonyfieroni Tags: #dolphin Differential Revision: https://phabricator.kde.org/D8303 M +1-2src/metadatafilter.cpp https://commits.kde.org/baloo-widgets/38681e7d27f57468454df72fff0dedeb38224449 -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 336994] User Manager does not show one particular user in the list unless I login as that user
https://bugs.kde.org/show_bug.cgi?id=336994 --- Comment #25 from Jack--- Of course as soon as I posted that, I discovered what is likely my issue, but may or may not affect anyone else. In my case, the "missing" users, have id's below 1000. In my case, this is because those users were originally created on a different system, years ago, but I migrated and upgraded over the years, and didn't want to change existing userid's. At some point, I suppose I'll have to break down and do so. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 336994] User Manager does not show one particular user in the list unless I login as that user
https://bugs.kde.org/show_bug.cgi?id=336994 Jackchanged: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #24 from Jack --- I'm seeing this also, on Gentoo with systemsetting 5.10.5 - multiple users "missing." What can I do, or info can I provide to help track down? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385035] Text in the fit mode segmented control's middle button frequently overflows
https://bugs.kde.org/show_bug.cgi?id=385035 --- Comment #4 from Nate Graham--- Fantastic. :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 207613] memcheck fails to handle paths with spaces on Mac; line numbers lost as result
https://bugs.kde.org/show_bug.cgi?id=207613 --- Comment #3 from Guy Harris--- $ valgrind --version valgrind-3.13.0 $ valgrind --leak-check=full /tmp/foo\ bar/foo\ bar ==98088== Memcheck, a memory error detector ==98088== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==98088== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==98088== Command: /tmp/foo\ bar/foo\ bar ==98088== --98088-- run: /usr/bin/dsymutil "/tmp/foo bar/foo bar" ... ==98088== 2,048 bytes in 1 blocks are definitely lost in loss record 37 of 42 ==98088==at 0x100096861: malloc (vg_replace_malloc.c:302) ==98088==by 0x10F6A: main (in /tmp/foo bar/foo bar) (deliberately leaked in my small test program). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385035] Text in the fit mode segmented control's middle button frequently overflows
https://bugs.kde.org/show_bug.cgi?id=385035 Henrik Fehlauerchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/gwe ||nview/7389aa55dbdf9c8af9510 ||6498aa6ce082cc03eb2 --- Comment #3 from Henrik Fehlauer --- Git commit 7389aa55dbdf9c8af95106498aa6ce082cc03eb2 by Henrik Fehlauer. Committed on 15/10/2017 at 19:33. Pushed by rkflx into branch 'Applications/17.08'. Fix padding of "Fit Width" button Summary: 3e10699ac37c4 introduced "Fit to Width", but failed to adapt the width calculation of the zoom mode buttons in the bottom zoom widget bar accordingly. This resulted in the middle button getting its text cut off for some languages, looking like this: {F5431466} There are several options to remedy this: - Give equal width to all buttons - Give equal width to the outer buttons (i.e. symmetric, probably the initial intention when there were only two buttons) - Just respect the size hint of each button individually | {F5431473} | {F5431474} | {F5431476} | As the three buttons are already quite wide, in order not to impact the minimal window size too much (rules out "equal width") and at the same time not to make the "Fit" button for English too narrow (rules out "individual width") we choose the "symmetric" option. Test Plan: Switch application language to Czech, view image. Text in "Fit to Width" (i.e. middle) button not cut off anymore, minimal window size only slightly impacted. For English, the "Fit" button is still wide enough. Reviewers: #kde_applications, broulik Reviewed By: broulik Subscribers: broulik Differential Revision: https://phabricator.kde.org/D8306 M +0-1lib/zoomwidget.cpp https://commits.kde.org/gwenview/7389aa55dbdf9c8af95106498aa6ce082cc03eb2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378544] Wayland session crash with nouveau.
https://bugs.kde.org/show_bug.cgi?id=378544 Martin Flöserchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Martin Flöser --- I assume the problem is fixed. If not please reopen. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/
https://bugs.kde.org/show_bug.cgi?id=267350 Ross Boylanchanged: What|Removed |Added CC||ross.boy...@ucsf.edu --- Comment #51 from Ross Boylan --- (In reply to lutz.wrage from comment #50) > Is there any use case that justifies storing form data in > ~/.kde/share/apps/okular/docdata/ given that the same data can be stored in > the pdf itself? > It seems to me that there isn't. While I consider the current behavior undesirable, it does have its advantages. In fact, it's the reason I decided to use okular for my taxes. Here's the use case: 1. Generate some forms automatically (e.g., opentaxsolver computes my taxes and fills in government forms). 2. Resulting forms require some manual tweaks (e.g., check boxes, fill in additional fields). 3. Discover forms need to be regenerated to correct a mistake. Modify inputs and return to 1. In this scenario, the work in 2 is lost if the results have been stored in the pdf, but is retained if the values are stored elsewhere, as okular currently does. Even if the pdf in 2 is saved under a different name, so that the results are not literally lost, one must manually identify the changed information and reenter it. There is another scenario in which the recreation of the information is less desirable. If some of the manually entered information in 2 depends on the values from 1, e.g., you manually enter line 55 as a copy of line 32 but the automatically generated line 32 changes, then the previous manual data may be invalid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383055] crash when dragging a gtk3 window with touchscreen
https://bugs.kde.org/show_bug.cgi?id=383055 Martin Flöserchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Martin Flöser --- The crash should be fixed. The relevant code was split out into a dedicated X11EventFilter and is only loaded by Workspace if operation mode is X11 only. This means the code that crashed is not executed any more. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385423] Okular print dialog doesn't offer "landscape" nor "portrait" options for paper rotation
https://bugs.kde.org/show_bug.cgi?id=385423 --- Comment #2 from LordDan--- (In reply to Albert Astals Cid from comment #1) > Just to make sure i understand what you want you want to print a landscape > in portrait so as to have a huge whitespace at the bottom? Yes, that's right. It means paper economy. More space left = space for printing another picture (or a copy from the first one), space for annotations etc. It's always better to offer options :-) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385790] Pen pressure is completely gone
https://bugs.kde.org/show_bug.cgi?id=385790 woltherachanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM CC||griffinval...@gmail.com --- Comment #1 from wolthera --- stupid question, but did you reinstall the driver? There's actually very little we can do from here, chances are that the drivers are mangled or bugged, so it would be a huion problem. In the future, please don't use the bugtracker for this, it really is for crashes and actual bugs only. the forum might be a better place for this, for one, other people who may have your tablet can pipe in :) https://forum.kde.org/viewforum.php?f=136 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385762] gwenview does not browse zip-files, cannot read zip-format
https://bugs.kde.org/show_bug.cgi?id=385762 Nate Grahamchanged: What|Removed |Added Resolution|WORKSFORME |DOWNSTREAM --- Comment #3 from Nate Graham --- Sounds likely, but that would be determined by the distro, not the desktop environment. What distro are you running XFCE on? Arch or an Arch derivative? I would report this to them. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385789] The sidebar always scrolls down despite scrolling in either directions in systemsettings
https://bugs.kde.org/show_bug.cgi?id=385789 Nate Grahamchanged: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377268] 2.5.1 - Preserve directory structure checkbox missing in "Copy..."
https://bugs.kde.org/show_bug.cgi?id=377268 --- Comment #7 from Alex Bikadorov--- As the "Copy/Move Files" feature will be integrated into the search dialog, you can use all search criteria the search dialog offers. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385790] New: Pen pressure is completely gone
https://bugs.kde.org/show_bug.cgi?id=385790 Bug ID: 385790 Summary: Pen pressure is completely gone Product: krita Version: 3.3.0 Platform: Other OS: other Status: UNCONFIRMED Severity: major Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: samtomo7...@hotmail.co.uk Target Milestone: --- I've trI'd absolutely everything to fix this bug- I've uninstalled and reinstalled Krita, restarted my tablet (Huion k58), fiddled with the display and pressure settings, made a copy of Krita and uninstalled the original, put my tablet's USB into every port on m computer, EVERYTHING. Please help, this is bugging me so much/don't make me resort to using Firealpaca! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384658] Line indented automatically when entering one of the letters i,u,e,n,d,f in python code
https://bugs.kde.org/show_bug.cgi?id=384658 Felix Wchanged: What|Removed |Added CC||felixwalte...@googlemail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385655] Multiscreen is broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=385655 --- Comment #19 from Kamil Piwowarski <9luty1...@gmail.com> --- (In reply to Martin Flöser from comment #18) > Ok, looks like the viewport gets wrong. I hope I can reproduce this with my > two screens. Let me know if I can help in any way with that (kwin debug). I know C++ very little, but I can compile kwin myself and use some qDebug(). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] SIGILL failure with ud2 opcode _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) (macOS)
https://bugs.kde.org/show_bug.cgi?id=383723 Rhys Kiddchanged: What|Removed |Added Summary|SIGILL failure with ud2 |SIGILL failure with ud2 |opcode (macOS) |opcode _dispatch_kq_init ||(in ||/usr/lib/system/libdispatch ||.dylib) (macOS) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] SIGILL failure with ud2 opcode (macOS)
https://bugs.kde.org/show_bug.cgi?id=383723 Rhys Kiddchanged: What|Removed |Added CC||shoeff...@uos.de --- Comment #15 from Rhys Kidd --- *** Bug 385604 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385604] illegal hardware instruction (OpenCV cv::namedWindow)
https://bugs.kde.org/show_bug.cgi?id=385604 Rhys Kiddchanged: What|Removed |Added Assignee|jsew...@acm.org |rhysk...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||rhysk...@gmail.com --- Comment #1 from Rhys Kidd --- Hi, this is a duplicate of an issue we are already tracking with ud2 within _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) *** This bug has been marked as a duplicate of bug 383723 *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 343688] Show desktop notifications on lock screen
https://bugs.kde.org/show_bug.cgi?id=343688 Buck Shockleychanged: What|Removed |Added CC||darkwingbuc...@gmail.com --- Comment #6 from Buck Shockley --- This report is rather old, but I would like to see this in a future version of Plasma 5. Modern desktop OS's like Mac OS and Windows 10 both implement this feature and even some Linux DE's like GNOME. It could be togglable for privacy reasons, but I would like the option. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385762] gwenview does not browse zip-files, cannot read zip-format
https://bugs.kde.org/show_bug.cgi?id=385762 --- Comment #2 from hjbitt...@gmx.net --- Created attachment 108365 --> https://bugs.kde.org/attachment.cgi?id=108365=edit error-message when I try to browse zip-files I installed gwenview in xfce. Perhaps this is a problem of dependencies. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385789] The sidebar always scrolls down despite scrolling in either directions in systemsettings
https://bugs.kde.org/show_bug.cgi?id=385789 Piotr Klocchanged: What|Removed |Added CC||pepk...@gmail.com --- Comment #1 from Piotr Kloc --- I can confirm that new systemsettings has messed up scrolling. Mouse: slow as hell but otherwise ok (I've heard that there is a Qt bug for that). Touchpad: speed is ok, but it is going in random direction. Trackpoint: same as with touchpad. Every other application is fine, for example: dolphin, firefox. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385289] Kmail: Crash when moving or deleting imap folder (Wayland)
https://bugs.kde.org/show_bug.cgi?id=385289 --- Comment #5 from Andrius Štikonas--- Ok, I obtained the following backtrace with breakpoint on exit Thread 1 (Thread 0x7fffbccec8c0 (LWP 11595)): #0 0x71f7644d in write () from /lib64/libc.so.6 #1 0x7fffdd7f0746 in g_wakeup_signal (wakeup=0x6418c0) at /usr/src/debug/dev-libs/glib-2.50.3-r1/glib-2.50.3/glib/gwakeup.c:239 #2 0x7fffdd79aa15 in g_main_context_wakeup (context=0x7fffac000990) at /usr/src/debug/dev-libs/glib-2.50.3-r1/glib-2.50.3/glib/gmain.c:4578 #3 0x72ecee95 in QEventDispatcherGlib::wakeUp (this=0x7fffac0008c0) at kernel/qeventdispatcher_glib.cpp:592 #4 0x72e4badb in QCoreApplication::postEvent (receiver=0x7fffac0032f0, event=0x4267dc0, priority=0) at kernel/qcoreapplication.cpp:1465 #5 0x72e8e0fd in QMetaObject::activate (sender=0x7fff24029200, signalOffset=0, local_signal_index=0, argv=0x7fffb0a0) at kernel/qobject.cpp:3732 #6 0x72e8db1e in QMetaObject::activate (sender=0x7fff24029200, m=0x7314fd20 , local_signal_index=0, argv=0x7fffb0a0) at kernel/qobject.cpp:3628 #7 0x72e910bc in QObject::destroyed (this=0x7fff24029200, _t1=0x7fff24029200) at .moc/moc_qobject.cpp:215 #8 0x72e871e8 in QObject::~QObject (this=0x7fff24029200, __in_chrg=) at kernel/qobject.cpp:901 #9 0x77f140b9 in QDBusServiceWatcher::~QDBusServiceWatcher() () from /usr/lib64/libQt5DBus.so.5 #10 0x72e89197 in QObjectPrivate::deleteChildren (this=0x7fff24038fd0) at kernel/qobject.cpp:1992 #11 0x72e87736 in QObject::~QObject (this=0x7fff24038ee0, __in_chrg=) at kernel/qobject.cpp:1022 #12 0x75d0bb9d in ?? () from /usr/lib64/libKF5KIOCore.so.5 #13 0x75d0bcc1 in KSslCertificateManager::~KSslCertificateManager() () from /usr/lib64/libKF5KIOCore.so.5 #14 0x75d0bce9 in ?? () from /usr/lib64/libKF5KIOCore.so.5 #15 0x71ed0b98 in ?? () from /lib64/libc.so.6 #16 0x71ed0be5 in exit () from /lib64/libc.so.6 #17 0x7fffb6239eb8 in QtWaylandClient::QWaylandDisplay::exitWithError (this=0x66d610) at qwaylanddisplay.cpp:209 #18 0x7fffb6239e50 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x66d610) at qwaylanddisplay.cpp:192 #19 0x7fffb626f02e in QtWaylandClient::QWaylandDisplay::qt_static_metacall (_o=0x66d610, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffb4e0) at .moc/moc_qwaylanddisplay_p.cpp:76 #20 0x72e8e328 in QMetaObject::activate (sender=0x6f7ac0, signalOffset=3, local_signal_index=0, argv=0x7fffb4e0) at kernel/qobject.cpp:3766 #21 0x72e8db1e in QMetaObject::activate (sender=0x6f7ac0, m=0x73157f00 , local_signal_index=0, argv=0x7fffb4e0) at kernel/qobject.cpp:3628 #22 0x72e9a2cd in QSocketNotifier::activated (this=0x6f7ac0, _t1=3, _t2=...) at .moc/moc_qsocketnotifier.cpp:137 ---Type to continue, or q to quit--- #23 0x72e9a003 in QSocketNotifier::event (this=0x6f7ac0, e=0x7fffba20) at kernel/qsocketnotifier.cpp:266 #24 0x73931bfc in QApplicationPrivate::notify_helper (this=0x647280, receiver=0x6f7ac0, e=0x7fffba20) at kernel/qapplication.cpp:3722 #25 0x7392ef9d in QApplication::notify (this=0x7fffd3c0, receiver=0x6f7ac0, e=0x7fffba20) at kernel/qapplication.cpp:3094 #26 0x72e4ae9f in QCoreApplication::notifyInternal2 (receiver=0x6f7ac0, event=0x7fffba20) at kernel/qcoreapplication.cpp:1018 #27 0x72e4f86e in QCoreApplication::sendEvent (receiver=0x6f7ac0, event=0x7fffba20) at kernel/qcoreapplication.h:233 #28 0x72ecdc90 in socketNotifierSourceDispatch (source=0x68b8e0) at kernel/qeventdispatcher_glib.cpp:106 #29 0x7fffdd798cf3 in g_main_dispatch (context=0x6aae10) at /usr/src/debug/dev-libs/glib-2.50.3-r1/glib-2.50.3/glib/gmain.c:3203 #30 0x7fffdd799c07 in g_main_context_dispatch (context=0x6aae10) at /usr/src/debug/dev-libs/glib-2.50.3-r1/glib-2.50.3/glib/gmain.c:3856 #31 0x7fffdd799dfa in g_main_context_iterate (context=0x6aae10, block=1, dispatch=1, self=0x6cb000) at /usr/src/debug/dev-libs/glib-2.50.3-r1/glib-2.50.3/glib/gmain.c:3929 #32 0x7fffdd799ed2 in g_main_context_iteration (context=0x6aae10, may_block=1) at /usr/src/debug/dev-libs/glib-2.50.3-r1/glib-2.50.3/glib/gmain.c:3990 #33 0x72ece9f8 in QEventDispatcherGlib::processEvents (this=0x681d20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #34 0x7fffb6284ae6 in QPAEventDispatcherGlib::processEvents (this=0x681d20, flags=...) at qeventdispatcher_glib.cpp:122 #35 0x72e47cbc in QEventLoop::processEvents (this=0x42f2710, flags=...) at kernel/qeventloop.cpp:134 #36 0x72e47fbd in QEventLoop::exec (this=0x42f2710, flags=...) at kernel/qeventloop.cpp:212 #37 0x732765bd in QBasicDrag::drag (this=0x689b80, o=0x4152990) at kernel/qsimpledrag.cpp:195 #38 0x7329a3cb in QDragManager::drag (this=0xab6de0, o=0x4152990) at kernel/qdnd.cpp:141 #39 0x73299155 in
[valgrind] [Bug 207613] memcheck fails to handle paths with spaces on Mac; line numbers lost as result
https://bugs.kde.org/show_bug.cgi?id=207613 Rhys Kiddchanged: What|Removed |Added CC||rhysk...@gmail.com Assignee|jsew...@acm.org |rhysk...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=205093 --- Comment #2 from Rhys Kidd --- Probably related, but can Guy confirm if this is still an issue with the most recent Valgrind release or Git version? Valgrind 3.5.0 is rather old now, having been released in August 2009. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 205093] dsymutil=yes needs quotes, locking
https://bugs.kde.org/show_bug.cgi?id=205093 Rhys Kiddchanged: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=207613 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 205093] dsymutil=yes needs quotes, locking
https://bugs.kde.org/show_bug.cgi?id=205093 Rhys Kiddchanged: What|Removed |Added CC||rhysk...@gmail.com Assignee|jsew...@acm.org |rhysk...@gmail.com OS|other |OS X -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385770] openSUSE TW (+nvidia) kmail crash when searching To: contact
https://bugs.kde.org/show_bug.cgi?id=385770 --- Comment #2 from Bruno Friedmann--- After cleaning completely the search_db kmail doesn't crash anymore when writing mail. BUT The autocompletion with my contacts (carddav source nextcloud) doesn't work anymore, while kaddressbook work perfectly. And manually use the select button also open the rights contacts. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385789] New: The sidebar always scrolls down despite scrolling in either directions in systemsettings
https://bugs.kde.org/show_bug.cgi?id=385789 Bug ID: 385789 Summary: The sidebar always scrolls down despite scrolling in either directions in systemsettings Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: i...@jsteward.moe Target Milestone: --- You can reproduce it by trying to use the scroll wheel to scroll down halfway and then back up. Despite the mouse wheel (or the touchpad as well) scrolling up, the contents still scrolls all the way to the bottom. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385788] New: plasmashell crashes when changing the icons of the system tray
https://bugs.kde.org/show_bug.cgi?id=385788 Bug ID: 385788 Summary: plasmashell crashes when changing the icons of the system tray Product: plasmashell Version: 5.11.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: i...@jsteward.moe CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.0) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.13.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Change the system tray icon entries (namely putting Vault into "Hidden" state (as I don't use it)) -- Backtrace: Application: プラズマ (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7ca6646800 (LWP 2139))] Thread 26 (Thread 0x7f7b677fe700 (LWP 6240)): #0 0x7f7c9f4b438d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7ca02f645c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7be35662ef in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7be356b339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7be356b392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7be3568b43 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7ca02f4fcb in () at /usr/lib/libQt5Core.so.5 #9 0x7f7c9f4ae08a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7c9fc0124f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f7b67fff700 (LWP 6239)): #0 0x7f7c9f4b438d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7ca02f645c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7be35662ef in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7be356b339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7be356b392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7be3568b43 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7ca02f4fcb in () at /usr/lib/libQt5Core.so.5 #9 0x7f7c9f4ae08a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7c9fc0124f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f7b88ff9700 (LWP 6238)): #0 0x7f7c9f4b438d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7ca02f645c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7be35662ef in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7be356b339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7be356b392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7be356b392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f7be356b392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f7be35657f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f7be3568b43 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f7ca02f4fcb in () at /usr/lib/libQt5Core.so.5 #13 0x7f7c9f4ae08a in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f7c9fc0124f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f7b897fa700 (LWP 6237)): #0 0x7f7c9f4b438d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7ca02f645c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7be35662ef in
[kwin] [Bug 385787] When minimizing windows, the mouse cursor will be ignored into moved
https://bugs.kde.org/show_bug.cgi?id=385787 Martin Flöserchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Flöser --- Fix landed just today. *** This bug has been marked as a duplicate of bug 378704 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378704] [Wayland] {min,max}ize, close buttons do not work on next window
https://bugs.kde.org/show_bug.cgi?id=378704 Martin Flöserchanged: What|Removed |Added CC||verme...@gmail.com --- Comment #5 from Martin Flöser --- *** Bug 385787 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385786] Context sub-menus for some applications show up at the top-left of the screen when there is not enough room on the right side of the screen
https://bugs.kde.org/show_bug.cgi?id=385786 Martin Flöserchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Martin Flöser --- Bug in Qt. Supposed to be fixed in 5.9.2. This is the same as the plasmashell context menus you reported. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385784] Plasma shell does not close context menus for panel widgets in Wayland
https://bugs.kde.org/show_bug.cgi?id=385784 Martin Flöserchanged: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Target Milestone|--- |1.0 Component|wayland-generic |generic-wayland Product|kwin|plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385782] Right-clicking tray icons (network, battery) will spawn multiple mis-placed context menus
https://bugs.kde.org/show_bug.cgi?id=385782 Martin Flöserchanged: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- Bug in Qt. Supposed to be fixed with 5.9.2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385778] Physics breaks down between the Wayland window decoration and XCB contents
https://bugs.kde.org/show_bug.cgi?id=385778 --- Comment #1 from Martin Flöser--- sorry, but I don't understand at all what you mean. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385730] Since 5.11 version, show progress and status information in tasks buttons does not appear anymore
https://bugs.kde.org/show_bug.cgi?id=385730 Ragnar Thomsenchanged: What|Removed |Added CC||rthoms...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385787] New: When minimizing windows, the mouse cursor will be ignored into moved
https://bugs.kde.org/show_bug.cgi?id=385787 Bug ID: 385787 Summary: When minimizing windows, the mouse cursor will be ignored into moved Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- This mainly affects when you are minimizing multiple windows at once. You must move the mouse slightly after each minimization in order to press the next minify button. To replicate this issue; 1. Open and maximize multiple windows. 2. Click the minimize button 3. You will see the the decoration does not 'see' the mouse, there is no hover effect on the next minimize button. Without moving the mouse, click the newly exposed minimize button. 4. Nothing happens. 5. Move the mouse slightly 6. The mouse will be 'seen' and the click will be accepted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385786] New: Context sub-menus for some applications show up at the top-left of the screen when there is not enough room on the right side of the screen
https://bugs.kde.org/show_bug.cgi?id=385786 Bug ID: 385786 Summary: Context sub-menus for some applications show up at the top-left of the screen when there is not enough room on the right side of the screen Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 108364 --> https://bugs.kde.org/attachment.cgi?id=108364=edit Screenshot of the bug Replicate by opening dolphin, and right-clicking on the display area towards the right side of the screen. The sub-menu will show up on the top right. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385783] Help button does nothing in System preferences - KDE Neon user edition
https://bugs.kde.org/show_bug.cgi?id=385783 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Is khelpcenter installed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385730] Since 5.11 version, show progress and status information in tasks buttons does not appear anymore
https://bugs.kde.org/show_bug.cgi?id=385730 Elvis Angelacciochanged: What|Removed |Added CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 385785] New: Compatibility with Qt 5.7.1
https://bugs.kde.org/show_bug.cgi?id=385785 Bug ID: 385785 Summary: Compatibility with Qt 5.7.1 Product: frameworks-kirigami Version: 5.39.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: marcelo.mat...@gmail.com Target Milestone: Not decided A problem occurs when trying to start KDE 5 systemsettings: -- $ systemsettings5 file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/main.qml:35:5: Type SubCategoryPage unavailable SubCategoryPage { ^ file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:26:1: Type Kirigami.ScrollablePage unavailable Kirigami.ScrollablePage { ^ file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:61:1: Type Page unavailable Page { ^ file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:259:20: Unexpected token `.' property T2.Page page: root ^ file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:259:26: Unexpected token `identifier' property T2.Page page: root ^ Segmentation fault -- kirigami 5.39.0 KDE 5 17.10 Qt 5.7.1 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 385781] Update KStars package to the latest version 2.8.5
https://bugs.kde.org/show_bug.cgi?id=385781 --- Comment #3 from Harald Sitter--- Huh? We have the latest release from Oct 12 http://archive.neon.kde.org/user/pool/main/k/kstars/ -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385289] Kmail: Crash when moving or deleting imap folder (Wayland)
https://bugs.kde.org/show_bug.cgi?id=385289 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- probably QtWayland [17:26] <d_ed> or kwin potentially ,you're getting told you made a protocol error and cut off, which can happen from either end [17:27] <d_ed> you have no backtrace as wayland asserted [17:27] <d_ed> if you put a break on exit you'll get a trace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385784] New: Plasma shell does not close context menus for panel widgets in Wayland
https://bugs.kde.org/show_bug.cgi?id=385784 Bug ID: 385784 Summary: Plasma shell does not close context menus for panel widgets in Wayland Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 108363 --> https://bugs.kde.org/attachment.cgi?id=108363=edit Screenshot of task manager items with mutple context menus. Opening context menus for Plasma shell panel items will not close the menu while interacting with Plasma panel elements. You can also open multiple context menus this way (unrelated to the tray item bug) and continue interacting with panels and panel widgets without dismissing the menus. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385783] New: Help button does nothing in System preferences - KDE Neon user edition
https://bugs.kde.org/show_bug.cgi?id=385783 Bug ID: 385783 Summary: Help button does nothing in System preferences - KDE Neon user edition Product: systemsettings Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aguad...@hotmail.com Target Milestone: --- The 'Help' button does nothing when clicked in any System preferences screen. This button is next to 'Default' and 'Reset' buttons. Fresh install of KDE NEON User edition. Maybe related to [bug #380081](https://bugs.kde.org/show_bug.cgi?id=380081) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385782] New: Right-clicking tray icons (network, battery) will spawn multiple mis-placed context menus
https://bugs.kde.org/show_bug.cgi?id=385782 Bug ID: 385782 Summary: Right-clicking tray icons (network, battery) will spawn multiple mis-placed context menus Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 108362 --> https://bugs.kde.org/attachment.cgi?id=108362=edit Showing multiple menus being spawned by repeatedly clicking on tray items. Some tray icons will open a single context menu placed towards the top-left of the screen. Others will spawn multiple context menus (placed similarly) Replicate by right-clicking on tray icons in a Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 385781] Update KStars package to the latest version 2.8.5
https://bugs.kde.org/show_bug.cgi?id=385781 --- Comment #2 from Jure Repinc--- (In reply to Jasem Mutlaq from comment #1) > Well, you could just add my PPA and get the latest KStars/INDI. Yeah I did just that after I noticed it :) But most people would probably not know about searching for PPAs and would get an old version. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 385781] Update KStars package to the latest version 2.8.5
https://bugs.kde.org/show_bug.cgi?id=385781 --- Comment #1 from Jasem Mutlaq--- Well, you could just add my PPA and get the latest KStars/INDI. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 385781] New: Update KStars package to the latest version 2.8.5
https://bugs.kde.org/show_bug.cgi?id=385781 Bug ID: 385781 Summary: Update KStars package to the latest version 2.8.5 Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: j...@holodeck1.com CC: j...@jriddell.org, mutla...@ikarustech.com, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I follow the blog of KStars developer Jasem Mutlaq: http://knro.blogspot.com/ and I have noticed that the version of KStars available in KDE Neon is not the latest version. The version available is version 2.7.10 but the latest released one is 2.8.5. Please update the KStars package to the latest released version. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] New: Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 Bug ID: 385780 Summary: Speed Effect is not saved after editing Product: kdenlive Version: 17.08.1 Platform: MS Windows OS: unspecified Status: UNCONFIRMED Severity: grave Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: nicolascasaba...@gmail.com Target Milestone: --- Steps to reproduce: 1. Load a clip in the timeline. 2. Apply Speed effect to the clip. 3. Do some edition, like cutting the clip, change speed, and so on. 4. Save project and exit kdenlive (*). 5. Reopen kdenlive and load the project. The speed effect is now missing from the clip. MLT version 6.5.0 (*) The bug doesn't always happen. It seems that logging out of the system affects the outcome. Perhaps is related to kdenlive processes not being closed properly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378704] [Wayland] {min,max}ize, close buttons do not work on next window
https://bugs.kde.org/show_bug.cgi?id=378704 Martin Flöserchanged: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.11 Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/1b01f1b3009474cc41d5c5831 ||8c1f3791fcff0fa --- Comment #4 from Martin Flöser --- Git commit 1b01f1b3009474cc41d5c58318c1f3791fcff0fa by Martin Flöser. Committed on 15/10/2017 at 14:38. Pushed by graesslin into branch 'Plasma/5.11'. Update pointer position whenever a window gets (un)minimized Summary: This fixes the following problem: 1. Have two windows maximized 2. Click minimize button on first window 3. Click minimize button on second window What happened: Second click was ignored as the pointer was not updated. FIXED-IN: 5.11 Test Plan: Nested KWin/Wayland, added two maximized windows, minimized both without moving the mouse Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D8145 M +1-0pointer_input.cpp M +1-0workspace.cpp M +1-0workspace.h https://commits.kde.org/kwin/1b01f1b3009474cc41d5c58318c1f3791fcff0fa -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 385779] New: Touchpad "reverse scrolling" stopped working on non-QT applications
https://bugs.kde.org/show_bug.cgi?id=385779 Bug ID: 385779 Summary: Touchpad "reverse scrolling" stopped working on non-QT applications Product: Touchpad-KCM Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: rajeeshknamb...@gmail.com Reporter: golu3...@gmail.com Target Milestone: --- The "reverse scrolling" setting suddenly seems to have stopped working on my computer, but only for non QT apps. So, I have this weird situation that I have scrolling working in one direction in Dolphin, QtCreator, Chrome and all the KDE apps, but in the exact opposite direction in PyCharm, Firefox, DeaDBeef etc. Observations: 1. Scrolling works fine in other desktop environments. I have tested it with Openbox and XFCE. 2. Removing the .config folder entirely and setting the reverse direction as reversed again makes scrolling work again on all applications. In fact, this is what I had done the last time this happened, but this problem has come back a week later. I can't keep losing my configs for all my applications for this one bug. Please help me, I really want to use KDE as my primary desktop environment but this issue is really killing the user experience for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385778] New: Physics breaks down between the Wayland window decoration and XCB contents
https://bugs.kde.org/show_bug.cgi?id=385778 Bug ID: 385778 Summary: Physics breaks down between the Wayland window decoration and XCB contents Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Conveniently marked by the thin blue strip separating window contents and the title decoration is a realm where logic, physics, and good sense break down. This area only applies to windows with XCB-based applications running in a Wayland session, not native Wayland applications. In practice it's a bit taller than the blue strip, but the blue strip is a good marker for where the issues are. It may take a few attempts to replicate the issues; - Clicking this area will sometimes pass the cursor through to the contents below. If the contents are another window, it will bring that window into the forefront. - On trackpads clicking this area will sometimes instead cause the cursor to switch into resizing mode. Dragging at this point will begin resizing the window from one of the top corners. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 211147] More options for Default Applications
https://bugs.kde.org/show_bug.cgi?id=211147 --- Comment #8 from Dr. Chapatin--- An option to set default torrent client to open magnet links would be nice too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 211147] More options for Default Applications
https://bugs.kde.org/show_bug.cgi?id=211147 Dr. Chapatinchanged: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #7 from Dr. Chapatin --- An option to set default torrent client to open magnet links would nice too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360073] Menu "Actions" -> "Send as Email Attachment" opens KMail instead of the client defined by the user
https://bugs.kde.org/show_bug.cgi?id=360073 Dr. Chapatinchanged: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 292606] Setting a custom mail client has no effect on mailto
https://bugs.kde.org/show_bug.cgi?id=292606 Dr. Chapatinchanged: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385777] Plasma default bottom panel flickers badly when using autohide.
https://bugs.kde.org/show_bug.cgi?id=385777 Mark Constablechanged: What|Removed |Added Summary|Plasma panels flickers |Plasma default bottom panel |badly when using autohide. |flickers badly when using ||autohide. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385777] New: Plasma panels flickers badly when using autohide.
https://bugs.kde.org/show_bug.cgi?id=385777 Bug ID: 385777 Summary: Plasma panels flickers badly when using autohide. Product: plasmashell Version: 5.11.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ma...@renta.net Target Milestone: 1.0 The autohide function for the bottom default panel flickers and has been (for me) for a month or two since using ~5.10.4. Currently on Kubuntu artful and the kubuntu-ci/stable plasma desperately trying to get to a version where there is no autohide flickering. It's hard to describe the problem so here is a video example... https://markc.blog/public/20171015_Plasma_Panel_Flicker.mp4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385776] "Desktop behavior" > "Visual feedback for status changes" setting change is not applied on first try
https://bugs.kde.org/show_bug.cgi?id=385776 Dr. Chapatinchanged: What|Removed |Added Platform|Other |Archlinux Packages Version|unspecified |5.11.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385776] New: "Desktop behavior" > "Visual feedback for status changes" setting change is not applied on first try
https://bugs.kde.org/show_bug.cgi?id=385776 Bug ID: 385776 Summary: "Desktop behavior" > "Visual feedback for status changes" setting change is not applied on first try Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- 1. start plasma session, open "system settings" > "Desktop behavior" 2. check/uncheck "Visual feedback for status changes", click "Apply" button 3. move your mouse wheel on audio tray icon to change the volume level and test your new setting Result: your new setting was not applied 4. restart "system settings" > "Desktop behavior" (note that the setting is not the same that you chose in the step 2) 5. repeat the steps 2 and 3 Result: your new setting was correctly applied now. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 357335] gwenview crashes every time when picture is opened
https://bugs.kde.org/show_bug.cgi?id=357335 --- Comment #3 from Henrik Fehlauer--- *** Bug 350897 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 350897] Gwenview crashes every time when it should open image
https://bugs.kde.org/show_bug.cgi?id=350897 Henrik Fehlauerchanged: What|Removed |Added CC||rk...@lab12.net Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Henrik Fehlauer --- I guess in this bug Gwenview crashes for the same reason as in your other bug, only here you are using the KDE4 based version. Surely you'll understand that I'll close this now. BTW, it would help us out immensely if you updated the state of old bugs from time to time, so the developers could focus their time on the most important bugs which are still valid. *** This bug has been marked as a duplicate of bug 357335 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385286] Konsole segfault
https://bugs.kde.org/show_bug.cgi?id=385286 --- Comment #4 from Samantha McVey--- Created attachment 108361 --> https://bugs.kde.org/attachment.cgi?id=108361=edit New crash information added by DrKonqi konsole (17.08.2) using Qt 5.9.2 I just updated my QT to 5.9.2 and the crash is still there. Konsole is now 17.08.2. As before it crashes when I run: perl -C -E'say "\x{1F3F4}\x{E0067}\x{E0062}\x{E0065}\x{E006E}\x{E0067}\x{E007F}"' I also backed up konsolerc and it crashes as well, so it doesn't seem related to the font I was using. -- Backtrace (Reduced): #6 0x7ff20d73520b in blend_untransformed_argb(int, QT_FT_Span_ const*, void*) () from /usr/lib64/libQt5Gui.so.5 #7 0x7ff20d75bd50 in fillRect_normalized(QRect const&, QSpanData*, QRasterPaintEnginePrivate*) () from /usr/lib64/libQt5Gui.so.5 #8 0x7ff20d7605ef in QRasterPaintEngine::drawImage(QPointF const&, QImage const&) () from /usr/lib64/libQt5Gui.so.5 #9 0x7ff20d77c83c in QPainter::drawImage(QPointF const&, QImage const&) () from /usr/lib64/libQt5Gui.so.5 #10 0x7ff20d7c0873 in QImageTextureGlyphCache::fillTexture(QTextureGlyphCache::Coord const&, unsigned int, QFixed) () from /usr/lib64/libQt5Gui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385286] Konsole segfault
https://bugs.kde.org/show_bug.cgi?id=385286 Samantha McVeychanged: What|Removed |Added CC||samant...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346757] In systemsettings there are sometimes graphical lags when I switch configuration modules
https://bugs.kde.org/show_bug.cgi?id=346757 Dr. Chapatinchanged: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385769] On wayland Abostroph keys switches windows and is not working as abostroph
https://bugs.kde.org/show_bug.cgi?id=385769 --- Comment #2 from FabiB--- Thanks for the reply, sadly no modifiers are active -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385730] Since 5.11 version, show progress and status information in tasks buttons does not appear anymore
https://bugs.kde.org/show_bug.cgi?id=385730 Kai Uwe Broulikchanged: What|Removed |Added Assignee|h...@kde.org|k...@privat.broulik.de Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kai Uwe Broulik --- Confirmed. Probably some fallout from the switch to using non-absolute launcher URLs. I'll have a look tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385763] Dashed line in the menu
https://bugs.kde.org/show_bug.cgi?id=385763 Hugo Pereira Da Costachanged: What|Removed |Added Product|Breeze |plasmashell Assignee|hugo.pereira.da.costa@gmail |k...@davidedmundson.co.uk |.com| Target Milestone|--- |1.0 CC||hugo.pereira.da.costa@gmail ||.com, plasma-b...@kde.org Component|QStyle |Application Launcher ||(Kickoff) Version|unspecified |master --- Comment #4 from Hugo Pereira Da Costa --- Reassigning to plasma but I'd rather suspect some Graphics driver issue. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385763] Dashed line in the menu
https://bugs.kde.org/show_bug.cgi?id=385763 --- Comment #3 from Silenøz Byrønsk--- Yes it is from the Kubuntu 17.04 after 17.10 in the preupgrade, sorry I had forgotten with. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385763] Dashed line in the menu
https://bugs.kde.org/show_bug.cgi?id=385763 --- Comment #2 from Silenøz Byrønsk--- Created attachment 108360 --> https://bugs.kde.org/attachment.cgi?id=108360=edit after installing all updates So my menu currently looks after the installation of all updates. Temporary I can fix the problem but that is not synonymous solution on permanence. So I reported the bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385775] New: KDE Plasma on Wayland unable to start with Intel GMA 3100
https://bugs.kde.org/show_bug.cgi?id=385775 Bug ID: 385775 Summary: KDE Plasma on Wayland unable to start with Intel GMA 3100 Product: plasmashell Version: 5.11.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: uflei...@users.sourceforge.net Target Milestone: 1.0 Overview: When I try to start a Plasma Wayland session from SDDM, it stops with the following dialog: Plasma is unable to start as it could not correctly use OpenGL 2. Please check that your graphics drivers are set up correctly. Steps to Reproduce: In SDDM, select "Plasma (Wayland)", then log in. Actual Results: An error dialog is displayed as described above. The user interface does not react to input, but it is possible to switch to another console using Ctrl-Alt-Fn. Expected Results: Starting of Plasma Desktop with Wayland. Build Date & Platform: Hardware: HP Compaq DC7800 with Intel GMA 3100 graphics (Mesa DRI Intel(R) Q35, OpenGL 2.1, DRI driver: i915) Software: Arch Linux with latest updates as of 2017-10-15. $ pacman -Q plasma-wayland-session qt5-base wayland xorg-server xf86-video-intel linux-lts plasma-wayland-session 5.11.0-2 qt5-base 5.9.2-1 wayland 1.14.0-1 xorg-server 1.19.5-1 xf86-video-intel 1:2.99.917+794+ga384b462-1 linux-lts 4.9.56-1 Additional Information: Plasma Wayland used to work when Arch Linux was at Qt 5.7. I tried to find the source of the problem. The error dialog is opened by /usr/bin/plasmashell, after creating instances of QQuickWindow subclasses (DesktopView, PanelView) in plasma-workspace/shell/shellcorona.cpp, sceneGraphError() is signalled, which will then lead to this dialog. So the problem must be QtQuick on Wayland. Running kwin_wayland seems to work ~~~ export $(dbus-launch) export QT_QPA_PLATFORM=wayland export XKB_DEFAULT_LAYOUT=ch export XKB_DEFAULT_VARIANT=de_sundeadkeys export XKB_DEFAULT_MODEL=pc105 export GDK_BACKEND=wayland kwin_wayland --xwayland --exit-with-session=konsole ~~~ Starting weston seems to work too, so I started Weston and tried to start QtQuick apps from the Weston shell, for instance the Qt Quick Controls 2 gallery example: ~~~ QT_QPA_PLATFORM=wayland-egl EGL_LOG_LEVEL=debug ~/src/quickcontrols2/gallery/gallery Using Wayland-EGL libEGL debug: Native platform type: x11 (build-time configuration) libEGL debug: added egl_dri2 to module array libEGL debug: the best driver is DRI2 (test only) libEGL debug: pci id for fd 6: 8086:29b2, driver i915 libEGL debug: DRI2: dlopen(/usr/lib/xorg/modules/dri/i915_dri.so) libEGL debug: found extension `DRI_Core' libEGL info: found extension DRI_Core version 1 libEGL debug: found extension `DRI_IMAGE_DRIVER' libEGL debug: found extension `DRI_DRI2' libEGL info: found extension DRI_DRI2 version 4 libEGL debug: found extension `DRI_DriverVtable' libEGL debug: found extension `DRI_ConfigOptions' libEGL debug: found extension `DRI_TexBuffer' libEGL info: found extension DRI_TexBuffer version 3 libEGL debug: found extension `DRI2_Fence' libEGL debug: found extension `DRI2_Flush' libEGL info: found extension DRI2_Flush version 3 libEGL debug: found extension `DRI_IMAGE' libEGL info: found extension DRI_IMAGE version 7 libEGL debug: found extension `DRI_RENDERER_QUERY' libEGL debug: found extension `DRI_CONFIG_QUERY' libEGL debug: found extension `DRI_NoError' libEGL debug: found extension `DRI_TexBuffer' libEGL debug: found extension `DRI2_Fence' libEGL info: found extension DRI2_Fence version 1 libEGL debug: found extension `DRI2_Flush' libEGL debug: found extension `DRI_IMAGE' libEGL debug: found extension `DRI_RENDERER_QUERY' libEGL info: found extension DRI_RENDERER_QUERY version 1 libEGL debug: found extension `DRI_CONFIG_QUERY' libEGL info: found extension DRI_CONFIG_QUERY version 1 libEGL debug: found extension `DRI_NoError' libEGL info: found extension DRI_NoError version 1 libEGL debug: did not find optional extension DRI_Robustness version 1 libEGL debug: did not find optional extension DRI2_Interop version 1 libEGL debug: the best driver is DRI2 libpng warning: iCCP: known incorrect sRGB profile Using the 'xdg-shell-v6' shell integration libEGL debug: EGL user error 0x3009 (EGL_BAD_MATCH) in dri2_create_context libEGL debug: EGL user error 0x3009 (EGL_BAD_MATCH) in dri2_create_context QWaylandGLContext: failed to create EGLContext, error=3009 libEGL debug: EGL user error 0x3006 (EGL_BAD_CONTEXT) in eglDestroyContext Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) ~~~
[knotes] [Bug 370750] knotes failed under wayland session but fine under X11
https://bugs.kde.org/show_bug.cgi?id=370750 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu --- Comment #3 from Andrius Štikonas --- What about setting QT_QPA_PLATFORM=xcb in the code, just like KMail used to do? At least that's better than crashing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385774] New: Systems Settings crash when using search
https://bugs.kde.org/show_bug.cgi?id=385774 Bug ID: 385774 Summary: Systems Settings crash when using search Product: systemsettings Version: 5.11.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: samant...@posteo.net Target Milestone: --- Application: systemsettings5 (5.11.0) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.12.0-sabayon x86_64 Distribution: "Sabayon Linux amd64 17.11" -- Information about the crash: - What I was doing when the application crashed: Typing things into the search box - Unusual behavior I noticed: The search box text was pixelated. (Looked scaled up, while the rest of the application looked fine). - Custom settings of the application: I had a HiDPI screen, and have scaling set to: Force fonts DPI: 154 Screen scaling: 1.6 The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcac4074800 (LWP 4397))] Thread 4 (Thread 0x7fca96440700 (LWP 4404)): #0 0x7fcac08f167d in poll () from /lib64/libc.so.6 #1 0x7fcabb8b8aa4 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcabb8b8bac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcac1165ebc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fcac111a53a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fcac0f85b5c in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fcabf6ae645 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7fcac0f89de2 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fcabda7e65c in start_thread () from /lib64/libpthread.so.0 #9 0x7fcac08fb4fd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fca97fbb700 (LWP 4403)): #0 0x7fcac08f167d in poll () from /lib64/libc.so.6 #1 0x7fcabb8b8aa4 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcabb8b8bac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcac1165ebc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fcac111a53a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fcac0f85b5c in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fcabf6ae645 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7fcac0f89de2 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fcabda7e65c in start_thread () from /lib64/libpthread.so.0 #9 0x7fcac08fb4fd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fcaa2bbd700 (LWP 4400)): #0 0x7fcac08f167d in poll () from /lib64/libc.so.6 #1 0x7fcabb8b8aa4 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcabb8b8bac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcac1165ebc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fcac111a53a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fcac0f85b5c in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fcac41717d5 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #7 0x7fcac0f89de2 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fcabda7e65c in start_thread () from /lib64/libpthread.so.0 #9 0x7fcac08fb4fd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fcac4074800 (LWP 4397)): [KCrash Handler] #6 0x08c7ea50 in ?? () #7 0x7fcac113f181 in QObjectData::dynamicMetaObject() const () from /usr/lib64/libQt5Core.so.5 #8 0x7fcac11246b9 in QMetaObject::cast(QObject const*) const () from /usr/lib64/libQt5Core.so.5 #9 0x7fcac25b0d63 in QGestureManager::filterEvent(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #10 0x7fcac256b611 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x7fcac111b978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #12 0x7fcabf9bf84a in QQuickKeysAttached::keyReleased(QKeyEvent*, bool) () from /usr/lib64/libQt5Quick.so.5 #13 0x7fcabf9c9ea7 in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () from /usr/lib64/libQt5Quick.so.5 #14 0x7fcabf9ca235 in QQuickItem::event(QEvent*) () from /usr/lib64/libQt5Quick.so.5 #15 0x7fcac25629bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7fcac2569ef0 in QApplication::notify(QObject*, QEvent*) () from
[gwenview] [Bug 365309] Crash when loading multiple files
https://bugs.kde.org/show_bug.cgi?id=365309 Henrik Fehlauerchanged: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED CC||rk...@lab12.net --- Comment #4 from Henrik Fehlauer --- Thanks for reporting, but I'm afraid this is more of a problem with your installation or distribution (as indicated by the klauncher error) and not with Gwenview specifically. This feature is working fine with a current KDE Frameworks 5 + Gwenview. You could try updating your Frameworks and Gwenview version (e.g. by using KDE Neon) or asking in the Ubuntu forums for help with debugging. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385771] No longer see any users
https://bugs.kde.org/show_bug.cgi?id=385771 akmchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from akm --- I have been digging a bit more and found this: https://forums.opensuse.org/showthread.php/523213-KDE-User-Manager-Does-not-show-all-users the post is what happened to me to including the 2 root password prompts, so I tried the last post there: Doing the org.freedesktop.Accounts.ListCachedUsers does not show userID 1000, only my test user with id 1001 qdbus --system --literal org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers [Argument: ao {[ObjectPath: /org/freedesktop/Accounts/User1001] Adding the user with org.freedesktop.Accounts.CacheUser dbus --system --literal org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.CacheUser akm and checking again with org.freedesktop.Accounts.ListCachedUsers shows both now: qdbus --system --literal org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers [Argument: ao {[ObjectPath: /org/freedesktop/Accounts/User1001], [ObjectPath: /org/freedesktop/Accounts/User1000]}] So I can't reproduce it anymore, will put it to Resolved. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385410] s390x: z13 vector string instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385410 Vadim Barkovchanged: What|Removed |Added CC||vbr...@gmail.com --- Comment #1 from Vadim Barkov --- Note that I will submit patch after closing 385408 issue. The reason to do so is to avoid code dublicating. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 385773] Krunner strange behavior in Plasma 5.11 on Wayland
https://bugs.kde.org/show_bug.cgi?id=385773 Toneychanged: What|Removed |Added CC||toneym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 385773] New: Krunner strange behavior in Plasma 5.11 on Wayland
https://bugs.kde.org/show_bug.cgi?id=385773 Bug ID: 385773 Summary: Krunner strange behavior in Plasma 5.11 on Wayland Product: krunner Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: toneym...@gmail.com Target Milestone: --- While using KDE Plasma 5.11 on Wayland (starting from console as startplasmacompositor) I found that typing in Krunner search string is broken: it shows only one symbol, like typing "chromium" shows the first letter 'c', but then changes it to 'h' and 'r'. 'Enter' key does not run selected application from the list anymore. Additional info: Arch x86_64 GNU/Linux plasma-desktop 5.11.0-1 krunner 5.38.0-1 wayland 1.14.0-1 Krunner in Plasma on X works fine as usual. Steps to reproduce: Start Plasma 5.11 on Wayland, press Alt+F2, start typing and try to run selected application pressing Enter. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385772] New: Various windows randomly stop redrawing (unless I move them)
https://bugs.kde.org/show_bug.cgi?id=385772 Bug ID: 385772 Summary: Various windows randomly stop redrawing (unless I move them) Product: plasmashell Version: 5.8.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 A few weeks ago I started seeing a strange problem on two remote PCs in different locations, built from different components that run Linux Mint 18.2 with KDE 5. Both use Nvidia GPUs, one has an Intel processor and uses it's IGPU for desktop, the other has a Ryzen processor and uses Nvidia or display. Some Windows randomly stop redrawing. They will redraw if I move them around the screen, but as soon as I stop moving them, they'll freeze again. The only way to get the program to work back again is restarting it. Programs seem to recieve keyboard input and respond o it, but can't refresh their windows. Most often this causes my Plasma Panel to not refresh, and flip between two frames back and forth in a glitched-out manner. Other programs that are affected are: Ardour, Firefox and LMMS (happened once so far). I didn't have that happen to Blender or Inkscape (and I use these a lot too). So there is clearly something that relates to the way the application handles display, and if it's affected. The problems started in similar time period on two machines, so I suspect a recent update must have broken something. I keep both systems updated almost daily, but the problem persists on both machines. The strangest thing is if I move the affected window around the screen it'll refresh for every frame that it's position changed. I work a lot in Ardour with 2 windows (Editor and Mixer) opened - often one will be affected, but not the other, no real rule which one and when however, this seems completely random. PS: I've reported this problem on Linux Mint forums first but maybe this is a better place. (here's the original post: https://forums.linuxmint.com/viewtopic.php?f=56=255375=1376381#p1376381 ) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368427] Resource downloads fail
https://bugs.kde.org/show_bug.cgi?id=368427 spa...@ymail.com changed: What|Removed |Added CC||spa...@ymail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385730] Since 5.11 version, show progress and status information in tasks buttons does not appear anymore
https://bugs.kde.org/show_bug.cgi?id=385730 Colin J Thomsonchanged: What|Removed |Added CC||colin.thom...@g6avk.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 379796] kscreenlocker/ksmserver-logout-greeter crashing repeatedly in Neon after recent update
https://bugs.kde.org/show_bug.cgi?id=379796 Stijn Geuenschanged: What|Removed |Added CC||valens...@gmail.com --- Comment #6 from Stijn Geuens --- ksmserver-logout-greeter close unexpected. Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f56761a3940 (LWP 16494))] Thread 4 (Thread 0x7f565715d700 (LWP 16497)): #0 0x7f5671869901 in __GI___poll (fds=0x7f5648004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f566a68b169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f566a68b27c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f56721a949b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f567214ee3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5671f6e3ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f56741c9f45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f5671f7329d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f56713457fc in start_thread (arg=0x7f565715d700) at pthread_create.c:465 #9 0x7f5671875b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f565795e700 (LWP 16496)): #0 __lll_unlock_wake () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371 #1 0x7f56713499af in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f566bda08a0) at pthread_mutex_unlock.c:55 #2 __GI___pthread_mutex_unlock (mutex=0x7f566bda08a0) at pthread_mutex_unlock.c:347 #3 0x7f566bb1cb79 in ?? () from /usr/lib/nvidia-340/libGL.so.1 #4 0x7f566bb2082b in ?? () from /usr/lib/nvidia-340/libGL.so.1 #5 0x7f56676b2fd0 in ?? () from /usr/lib/nvidia-340/tls/libnvidia-tls.so.340.104 #6 0x7f566a6cf280 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f566a68ac4b in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f566a68b110 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f566a68b27c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f56721a949b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f567214ee3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f5671f6e3ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f5672d8ce45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #14 0x7f5671f7329d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f56713457fc in start_thread (arg=0x7f565795e700) at pthread_create.c:465 #16 0x7f5671875b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f565d563700 (LWP 16495)): #0 0x7f5671869901 in __GI___poll (fds=0x7f565d562b78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f566c660747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f566c66253a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f565fac9f09 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f5671f7329d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56713457fc in start_thread (arg=0x7f565d563700) at pthread_create.c:465 #6 0x7f5671875b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f56761a3940 (LWP 16494)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f5671799f5d in __GI_abort () at abort.c:90 #8 0x7f5671f5e107 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5674896787 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f5674897755 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f567489837a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f567271bd35 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f567490bd05 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x560eb5760fd1 in ?? () #15 0x7f567335946c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f5673360d34 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f5672150de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from
[systemsettings] [Bug 385771] New: No longer see any users
https://bugs.kde.org/show_bug.cgi?id=385771 Bug ID: 385771 Summary: No longer see any users Product: systemsettings Version: 5.11.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: a.vank...@chello.nl Target Milestone: --- Created attachment 108359 --> https://bugs.kde.org/attachment.cgi?id=108359=edit how it looks now while I am logged in in Plasma 5.11 on Tumbleweed I selected my user and added its email (something I not done before), I got 2 su boxes for root password, I know the last one was sddm and after that happened the user was gone. if I try to add the same user name it I get a "not allowed sign" behind it, so it does see my current account. if I log out and in my account still exists including the custom picture and name. But it simply no longer shows in the KDE system settings account details -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385770] openSUSE TW (+nvidia) kmail crash when searching To: contact
https://bugs.kde.org/show_bug.cgi?id=385770 --- Comment #1 from Bruno Friedmann--- Just in case : I'm actually cleaning up the whole search_db of akonadi do akonadictl fsck and akonadictl vacuum Let see if it will be again reproducible. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385035] Text in the fit mode segmented control's middle button frequently overflows
https://bugs.kde.org/show_bug.cgi?id=385035 Henrik Fehlauerchanged: What|Removed |Added CC||rk...@lab12.net --- Comment #2 from Henrik Fehlauer --- Proposal for patch (please comment which of the options you like better): https://phabricator.kde.org/D8306 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 338669] GHNS dialog does not work, server newstuff.kde.org does not function properly
https://bugs.kde.org/show_bug.cgi?id=338669 --- Comment #8 from Jonathan Riddell--- Requested category in store.kde.org https://phabricator.kde.org/T7201 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 338669] GHNS dialog does not work, server newstuff.kde.org does not function properly
https://bugs.kde.org/show_bug.cgi?id=338669 Jonathan Riddellchanged: What|Removed |Added CC||j...@jriddell.org --- Comment #7 from Jonathan Riddell --- Sheets/tabs/things are saved to ~/.local/share/ksysguard/ presumably to fix it needs a way to upload to store.kde.org, a category added to store.kde.org, fixing the url and anything else to download -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385770] New: openSUSE TW (+nvidia) kmail crash when searching To: contact
https://bugs.kde.org/show_bug.cgi?id=385770 Bug ID: 385770 Summary: openSUSE TW (+nvidia) kmail crash when searching To: contact Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: kmail (5.6.1) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.4-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Open kmail, read some mail. ctrl+N for a new mail, start typing in the To: field to find the contact you want. The crask is immediate and reproductible. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f527fdee980 (LWP 4426))] Thread 32 (Thread 0x7f5107df7700 (LWP 4532)): #0 0x7f52729ff82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5267712f45 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5267713427 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f52677141c1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f526771088b in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f52729f9558 in start_thread () at /lib64/libpthread.so.0 #6 0x7f527cf0745f in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f519101d700 (LWP 4531)): #0 0x7f52729ff82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f52635e38e4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f52635e3929 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f52729f9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f527cf0745f in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f51927ff700 (LWP 4528)): #0 0x7f5270e46714 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f5270e00678 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5270e0107b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5270e0125c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f527d82569b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f527d7ce34a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f527d5fe31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f527d602d2e in () at /usr/lib64/libQt5Core.so.5 #8 0x7f52729f9558 in start_thread () at /lib64/libpthread.so.0 #9 0x7f527cf0745f in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f51b8967700 (LWP 4497)): #0 0x7f527cefccab in poll () at /lib64/libc.so.6 #1 0x7f5270e01149 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5270e0125c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f527d82569b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f527d7ce34a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f527d5fe31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f527d602d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7f52729f9558 in start_thread () at /lib64/libpthread.so.0 #8 0x7f527cf0745f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f51b9168700 (LWP 4496)): #0 0x7f527cefccab in poll () at /lib64/libc.so.6 #1 0x7f5270e01149 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5270e0125c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f527d82569b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f527d7ce34a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f527d5fe31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f527d602d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7f52729f9558 in start_thread () at /lib64/libpthread.so.0 #8 0x7f527cf0745f in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f51b9969700 (LWP 4495)): #0 0x7f527cefccab in poll () at /lib64/libc.so.6 #1 0x7f5270e01149 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5270e0125c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f527d82569b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f527d7ce34a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f527d5fe31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f527d602d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7f52729f9558 in start_thread () at /lib64/libpthread.so.0 #8 0x7f527cf0745f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f51ba16a700 (LWP 4494)): #0 0x7f527cefccab
[ksysguard] [Bug 383291] Get Hot New Stuff add-ons are not loading in 'System Monitor' KSysGuard
https://bugs.kde.org/show_bug.cgi?id=383291 Jonathan Riddellchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #1 from Jonathan Riddell --- *** This bug has been marked as a duplicate of bug 338669 *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 338669] GHNS dialog does not work, server newstuff.kde.org does not function properly
https://bugs.kde.org/show_bug.cgi?id=338669 Jonathan Riddellchanged: What|Removed |Added CC||notux...@gmail.com --- Comment #6 from Jonathan Riddell --- *** Bug 383291 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 383291] Get Hot New Stuff add-ons are not loading in 'System Monitor' KSysGuard
https://bugs.kde.org/show_bug.cgi?id=383291 Jonathan Riddellchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||j...@jriddell.org -- You are receiving this mail because: You are watching all bug changes.