[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names
https://bugs.kde.org/show_bug.cgi?id=390024 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #33 from Tobias Deiminger --- (In reply to Christoph Feck from comment #32) > > Following this theory, I shouldn't be able to find bitmaps in heap. > > Your theory is wrong. Read QPixmap source. I did and found http://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/nativepainting/qpixmap_x11.cpp#n1167 (but tbh am not sure if we take that path). Also, in a gdb session with same document loaded but no scrolling yet, I can't find memory chunks large enough to hold contiguous range of memory for page bitmaps, which should be about 4MB for 1000 x 1000 px at 32 bit depth. The largest chunk there is about 70kB. Both made me believe in that theory. Could you explain where I'm wrong? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361505] kdenlive 15.1.3 is no more able to import my .VOB clips
https://bugs.kde.org/show_bug.cgi?id=361505 wilmar klose changed: What|Removed |Added CC||wi...@willy-world-wide.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396110] New: "clip problems" window keeps popping up on opening a project despite all clips are in place
https://bugs.kde.org/show_bug.cgi?id=396110 Bug ID: 396110 Summary: "clip problems" window keeps popping up on opening a project despite all clips are in place Product: kdenlive Version: 18.04.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: j...@cspv.hu Target Milestone: --- Created attachment 113729 --> https://bugs.kde.org/attachment.cgi?id=113729=edit the project file hello, I took my hdd and plugged into another machine... and files needed to be rescanned.. but it's like that ever since I did NOT have this before with kdenlive, but now both 18.4.0 and 18.4.1 does it... with this project I'm working on... I mean, it might or might not be a bug since the project is not bit at all, I thought I attach the project file and you can decide if it is something kdenlive specific or a result of my setup somehow.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #5 from Shmerl --- It functions OK for X11 session at least. And that Wayland client core did appear in dmesg before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #4 from Martin Flöser --- The log says that the platform plugin failed to initialize. Could it be that systemd/logind don't function correctly? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396098] KWIN Crashes when OpenGL is choosen with nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=396098 --- Comment #6 from Martin Flöser --- libepoxy not libproxy -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396109] New: Allow using up and down arrows for navigating both message list and message body
https://bugs.kde.org/show_bug.cgi?id=396109 Bug ID: 396109 Summary: Allow using up and down arrows for navigating both message list and message body Product: kmail2 Version: 5.7.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: shm...@mykolab.com Target Milestone: --- Currently there is no way to use up / down to navigate Kmail message list and message body depending on the current panel focus. It's pretty counter intuitive. Current configuration doesn't allow assigning it to both, and only one action can be configured. Can you please enable that depending on what is focused at the moment? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 396108] New: The mpris icon doesn't disappear when the streaming is stop playing.
https://bugs.kde.org/show_bug.cgi?id=396108 Bug ID: 396108 Summary: The mpris icon doesn't disappear when the streaming is stop playing. Product: plasma-browser-integration Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: laichiah...@outlook.com Target Milestone: --- The icon is still there, it won't disappear. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 376770] Impossible to unbind Shift + Up/Down
https://bugs.kde.org/show_bug.cgi?id=376770
andydecle...@gmail.com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|--- |INVALID
--- Comment #11 from andydecle...@gmail.com ---
I've pinned the problem down to ":smcup@:rmcup@" in my tmux terminal-overrides.
Without that, I can use shift and the cursor keys in apps in konsole, in or out
of tmux. The change breaks shift+page{up,down} in tmux, but that's fine.
So I replaced
set -ga terminal-overrides ',xterm-256color:Tc:smcup@:rmcup@'
with
set -ga terminal-overrides ',xterm-256color:Tc'
and I get to come home to konsole.
Re-closing as invalid
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 396069] plasma-discover Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=396069 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Christoph Feck --- Thanks for the update; closing. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #32 from Christoph Feck --- > Following this theory, I shouldn't be able to find bitmaps in heap. Your theory is wrong. Read QPixmap source. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396069] plasma-discover Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=396069 --- Comment #1 from Tim Steinberger --- This issue is on the package maintainer's end. The crash is occurring because packagekit did not find a file it was expecting. My apologies for not looking closely enough. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 Tim Steinberger changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #45 from Tim Steinberger --- Sorry about that, I've done more experimenting with it and my crash is happening for a different reason. Packagekit was crashing because it depended on a binary I did not have installed. This is a problem on the package maintainer's end, so the only issue I see with discover here is that it crashes when packagekit exits rather than continuing and just printing an error which is a different issue in itself. I set this back to Fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390457] Task manager pixelated previews
https://bugs.kde.org/show_bug.cgi?id=390457 --- Comment #8 from uRohan --- Created attachment 113728 --> https://bugs.kde.org/attachment.cgi?id=113728=edit Task Manager Thumbnails -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390457] Task manager pixelated previews
https://bugs.kde.org/show_bug.cgi?id=390457 David Edmundson changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||k...@davidedmundson.co.uk --- Comment #7 from David Edmundson --- Right, that commit was reverted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390457] Task manager pixelated previews
https://bugs.kde.org/show_bug.cgi?id=390457 uRohan changed: What|Removed |Added CC||navigator.ro...@gmail.com --- Comment #6 from uRohan --- OS: openSUSE Tumbleweed 20180629 KDE Plasma Version: 5.13.1 KDE Frameworks Version: 5.47.0 Qt Version: 5.11.1 Kernel Version: 4.17.3-1-default OS Type: 64-bit This bug still persist in the KDE Plasma 5.13.1. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #31 from Rooty --- (In reply to Albert Astals Cid from comment #28) > I'm not going to answer further in this bug because i don't feel compelled > to have a discussion with people that saying things like "no way a 90kb PDF > can take XX Mb of memory" as if they knew anything about they are talking > about. > > *BUT* this may actually be a manifestation of "glibc is useless and doesn't > actually free memory when you tell it to" that i workarounded at > https://cgit.kde.org/okular.git/commit/ > ?id=95bc29a76fc1f93eaabe5383d934644067dfc884 > > If this is the case one may need to add more malloc_trim around and not only > when the document is closed, but i totally don't feel like being dragged to > discuss with people that have no clue what they're talking about and have no > respect for people that give them stuff for free. "no respect for people that give them stuff for free"? "don't know what you're talking about"? for real? i meant no disrespect, i don't even use okular but i was trying to direct you to something that clearly bears closer examination. there are a myriad of other PDF readers out there we could be using but we're still here, reporting bugs/problems in okular. think long and hard about what that means with respect to the appreciation we show for the software you make. that being said, all of this is a moot point. it's taking up a lot more RAM than any other PDF reader (i'll leave you to decide whether that's appropriate). i'm sorry i can't help you out more, i know how to report a bug, but the diagnostics is beyond me (not an IT guy). thanks @Tobias for fleshing it out -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #7 from Bernard Gray --- (In reply to Albert Astals Cid from comment #6) > (In reply to Fabian Vogt from comment #5) > > It's not fixed - that commit is not in 5.12.x. > > > > @aacid: Any reason in particular it was only submitted for 5.13? > > I guess i found it to be corner case-y and not warranted a backport since > there's always the risk/benefit calculation you have to do when backporting > something to a LTS branch. > > I've no idea how common this scenario and how "live-tested" we can say my > new code is to say "yes it doesn't seem to cause regressions let's bring it > to 5.12 since it's an important fix" * sddm is shipping with a default config which uses pam_kwallet*.so * I expect most enterprise deployments will use the libpam_mkhomedir.so module ie Most enterprise deployments shipping vanilla-ish KDE which, from my perspective of course, isn't really a corner case :P -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #30 from Tobias Deiminger --- (In reply to Albert Astals Cid from comment #28) > *BUT* this may actually be a manifestation of "glibc is useless and doesn't > actually free memory when you tell it to" that i workarounded at > https://cgit.kde.org/okular.git/commit/ > ?id=95bc29a76fc1f93eaabe5383d934644067dfc884 That's well possible. I did some memory forensics with attachment 109856 loaded. The observations could be explained by glibc not freeing memory. Important note in advance: Yes, Okular caches pages. But it stores them as QPixmaps (e.g., see PagePrivate::m_pixmaps). This means, at least on X11, the image payload is not kept in Okulars heap. QPixmap objects are just wrappers around X11 pixmap handles [0]. The raw image data is stored in memory managed by the X11 server, not in Okulars heap. Following this theory, I shouldn't be able to find bitmaps in heap. I iterated over all malloc chunks in a gdb session (using gdb gef with some customization), and checked for suspicious chunks (by vtable, by size). There were several chunks of size > 4 MiB, flagged as "in use". Such big chunks could be bitmaps, just guessing by their sheer size. I dumped the memory range of such a chunk into a file, like: (gdb) dump binary memory /tmp/dump.bin 0x55a80d790560 0x55A80DB71BF0 When opening /tmp/dump.bin in Gimp as raw image, and playing around with width and height a bit, it looked like attachment 113727. Quite clear case. This is either the reminder of a page bitmap, or Maxwells Daemon did a quite good job :) What does this tell us? Imo it tells there's the inner bitmap of a QImage hanging around in the heap, a thing that shouldn't be. QImages are only used temporarily, when they're sent from the rendering thread over a queued connection to the main thread. After transforming them into QPixmap (in Generator::generatePixmap), they should be freed. If they are not, this could for example mean there are some QImages stuck in the queue, or it could be some glibc behavior as mentioned by Albert. Albert, Oliver: If you think I'm on the wrong track, please stop me from digging deeper. [0] ftp://www.x.org/pub/X11R7.7/doc/man/man3/xcb_create_pixmap.3.xhtml -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396102] ResultsModel emits wrong rowsMoved transactions
https://bugs.kde.org/show_bug.cgi?id=396102 --- Comment #3 from Ivan Čukić --- I'm currently without my development machine. I'll check this out when it becomes operational. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395174] Search using string 'keepass' does not display the program 'keepassx' in search result
https://bugs.kde.org/show_bug.cgi?id=395174 Aleix Pol changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #21 from Aleix Pol --- There's something broken in your appstream set up. I recommend checking with your distro. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396029] applications menus do not work
https://bugs.kde.org/show_bug.cgi?id=396029 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Albert Astals Cid --- I'm really sorry to close this bug, but this is not an Okular bug, it seems your system is basically broken. I would advise you hop into the support channels of the distribution you are using to try to figure out what went wrong. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 Tobias Deiminger changed: What|Removed |Added CC||haxti...@posteo.de --- Comment #29 from Tobias Deiminger --- Created attachment 113727 --> https://bugs.kde.org/attachment.cgi?id=113727=edit Memory chunk, dumped and visualized as raw image in Gimp Explanation follows... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #3 from Shmerl --- I wrote a script what intercepts kwin_wayland launch and attaches gdb to it. But when I do continue in it, it simply exists rather that segfaults. Where can I find KWin logs? That's what I see in: $HOME/.local/share/sddm/wayland-session.log startplasmacompositor: Starting up... dbus-daemon[1791]: [session uid=1000 pid=1791] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=1000 pid=1893 comm="dbus-update-activation-environment --systemd --all") dbus-daemon[1791]: [session uid=1000 pid=1791] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 No backend specified through command line argument, trying auto resolution FATAL ERROR: backend failed to initialize, exiting now startplasmacompositor: Shutting down... startplasmacompositor: Done. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396086] Changing elements order takes near 5 minutes in a folder with 50 images
https://bugs.kde.org/show_bug.cgi?id=396086 Rafael changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #2 from Rafael --- I'll try it tomorrow. Is expected some change (corruption or similar) when linking to the actual internal mysql database? -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #6 from Albert Astals Cid --- (In reply to Fabian Vogt from comment #5) > It's not fixed - that commit is not in 5.12.x. > > @aacid: Any reason in particular it was only submitted for 5.13? I guess i found it to be corner case-y and not warranted a backport since there's always the risk/benefit calculation you have to do when backporting something to a LTS branch. I've no idea how common this scenario and how "live-tested" we can say my new code is to say "yes it doesn't seem to cause regressions let's bring it to 5.12 since it's an important fix" I guess that'd would be more a question for the Plasma maintainers than for me, I really don't follow the Plasma development much and don't know what are the guidelines for backporting patches. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395894] Custom template icons are broken
https://bugs.kde.org/show_bug.cgi?id=395894 --- Comment #2 from kapyia@gmail.com --- Ah, too bad. Maybe it's on my end then. I'll report back when the new resource system is out and I can test with that! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #28 from Albert Astals Cid --- I'm not going to answer further in this bug because i don't feel compelled to have a discussion with people that saying things like "no way a 90kb PDF can take XX Mb of memory" as if they knew anything about they are talking about. *BUT* this may actually be a manifestation of "glibc is useless and doesn't actually free memory when you tell it to" that i workarounded at https://cgit.kde.org/okular.git/commit/?id=95bc29a76fc1f93eaabe5383d934644067dfc884 If this is the case one may need to add more malloc_trim around and not only when the document is closed, but i totally don't feel like being dragged to discuss with people that have no clue what they're talking about and have no respect for people that give them stuff for free. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 364937] Uncommon terminology used for Nicaragua
https://bugs.kde.org/show_bug.cgi?id=364937 --- Comment #3 from Albert Astals Cid --- it is fixable-ish We can have custom strings for the "what is the capital of" and "%1 is the capital of", bihar and world continents have them. The trouble here is finding an english word for "cabecera departamental" that then would univocally translate to "cabecera departamental", because (sorry I use Honduras as example, it's "nicer" than the Nicaragua Wikipedia page) in https://en.wikipedia.org/wiki/Departments_of_Honduras you see "Department Capital" which in https://es.wikipedia.org/wiki/Organizaci%C3%B3n_territorial_de_Honduras is correctly translated as "Cabecera" but since the "What is the Department Capital of %1" string would not be Nicaragua specific my guess as a Spain-Spanish speaker is that it would be translated to the more neutral "¿Cuál es la Capital del departamento de %1?" So it's all a bit of a mess, do kids don't really understand the word "Capital" in Nicagarua as a generic term? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392689] [Crash,Wayland] - When a plasma taskmanager in present in Latte Dock under Wayland
https://bugs.kde.org/show_bug.cgi?id=392689 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Crash when clicking on icons in Latte Dock Panel plasmoid latte-dock 0.7.5-1 Plasma: 5.13.2 Apps: 18.04.2 Frameworks: 5.47.0 Qt: 5.11.1 Kernel: 4.18.0-1-MANJARO OS: Netrunner Rolling Video: Intel 4400 Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1 Mesa 3D: 18.1.3 Screen: 1600x900 Xorg: 1.20 Wayland: 1.15.0-1 Wayland Protocols: 1.14-1 Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdae6502f00 (LWP 20283))] Thread 17 (Thread 0x7fd9eb3fe700 (LWP 21694)): #0 0x7fdadeecfffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdadfd2c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fdae3d1842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fdae3d1869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fdadfd2bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fdadeeca075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdadf61b53f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fd9ebfff700 (LWP 20860)): #0 0x7fdadeecfffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdadfd2c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fdae3d1842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fdae3d1869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fdadfd2bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fdadeeca075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdadf61b53f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fda05166700 (LWP 20859)): #0 0x7fdadeecfffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdadfd2c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fdae3d1842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fdae3d1869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fdadfd2bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fdadeeca075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdadf61b53f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fd9e9a7a700 (LWP 20838)): #0 0x7fdadeecfffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdadfd2c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fdae3d1842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fdae3d1869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fdadfd2bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fdadeeca075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdadf61b53f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fd9ea3fc700 (LWP 20826)): #0 0x7fdadeecfffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdadfd2c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fdae3d1842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fdae3d1869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fdadfd2bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fdadeeca075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdadf61b53f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fd9eabfd700 (LWP 20823)): #0 0x7fdadeecfffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdadfd2c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fdae3d1842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fdae3d1869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fdadfd2bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fdadeeca075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdadf61b53f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fd9fef3a700 (LWP 20558)): #0 0x7fdadeecfffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdadfd2c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fdae3d1842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fdae3d1869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fdadfd2bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fdadeeca075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdadf61b53f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fda14b77700 (LWP 20500)): #0 0x7fdadf60c934 in read () at /usr/lib/libc.so.6 #1 0x7fdad91bded1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fdad9177ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fdad91784c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fdad917863e in g_main_context_iteration () at
[Heaptrack] [Bug 395109] Infinite recursion during initialization when stdlib's atexit() allocates
https://bugs.kde.org/show_bug.cgi?id=395109 Milian Wolff changed: What|Removed |Added Latest Commit||https://commits.kde.org/hea ||ptrack/5ff967ab12fda2083410 ||0ea3861d65d74221db89 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Milian Wolff --- Git commit 5ff967ab12fda20834100ea3861d65d74221db89 by Milian Wolff. Committed on 02/07/2018 at 20:58. Pushed by mwolff into branch '1.1'. Call libc / libstdc++ freeres function in libheaptrack's atexit On one hand, this prevents an infinite recursion when the call to atexit allocates, which happens e.g. with uClibc, since the call from heaptrack_preload did not install the recursion guard yet. On the other hand, this code move ensures that the freeres functions get called properly before heaptrack_stop is called. M +0-19 src/track/heaptrack_preload.cpp M +19 -0src/track/libheaptrack.cpp https://commits.kde.org/heaptrack/5ff967ab12fda20834100ea3861d65d74221db89 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 396043] Percentage sign is doubled when language is set to Polish
https://bugs.kde.org/show_bug.cgi?id=396043 --- Comment #2 from Piotr Kloc --- Thanks, could you push it, or should I get my hands dirty? I could finally use my phabricator account for something useful, come to think of it Polish translation lacks in some places. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 396107] New: "Information about power"(my retranslation to english) causes "Information center" to crash imiedietlly
https://bugs.kde.org/show_bug.cgi?id=396107 Bug ID: 396107 Summary: "Information about power"(my retranslation to english) causes "Information center" to crash imiedietlly Product: kinfocenter Version: 5.13.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: kuba...@gmail.com Target Milestone: --- Application: kinfocenter (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: I launched the app and went to "Information about charging/charger/power/the option right below ram/memory" and it crashes imiedietlly after. Same goes for "File Indexation monitor" The crash can be reproduced every time. -- Backtrace: Application: Ośrodek informacji (kinfocenter), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54520fb900 (LWP 29010))] Thread 3 (Thread 0x7f542aef2700 (LWP 29017)): #0 0x7f5448cb38d3 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5448cb42bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5448cb449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f544f2480bb in QEventDispatcherGlib::processEvents (this=0x7f54240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f544f1ef5ba in QEventLoop::exec (this=this@entry=0x7f542aef1c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f544f0245e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f544d2aa195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f544f02f727 in QThreadPrivate::start (arg=0x16acd60) at thread/qthread_unix.cpp:367 #8 0x7f544a7936ba in start_thread (arg=0x7f542aef2700) at pthread_create.c:333 #9 0x7f544e93c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f5434d91700 (LWP 29013)): #0 0x7f544e93074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5448cb438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5448cb449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f544f2480bb in QEventDispatcherGlib::processEvents (this=0x7f5438c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f544f1ef5ba in QEventLoop::exec (this=this@entry=0x7f5434d90c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f544f0245e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f544c935f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f544f02f727 in QThreadPrivate::start (arg=0x7f544cbaed60) at thread/qthread_unix.cpp:367 #8 0x7f544a7936ba in start_thread (arg=0x7f5434d91700) at pthread_create.c:333 #9 0x7f544e93c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f54520fb900 (LWP 29010)): [KCrash Handler] #6 0x7f544e86a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f544e86c02a in __GI_abort () at abort.c:89 #8 0x7f544f00190d in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1842 #9 QMessageLogger::fatal (this=this@entry=0x7ffe48bf4110, msg=msg@entry=0x7f544dea840f "%s") at global/qlogging.cpp:880 #10 0x7f544dea3d8c in QQuickWidgetPrivate::handleContextCreationFailure (this=this@entry=0x1ac32a0, format=..., isEs=isEs@entry=false) at qquickwidget.cpp:850 #11 0x7f544dea3fba in QQuickWidgetPrivate::createContext (this=this@entry=0x1ac32a0) at qquickwidget.cpp:881 #12 0x7f544dea6386 in QQuickWidget::resizeEvent (this=0x182a3b0, e=) at qquickwidget.cpp:1216 #13 0x7f544fffe1ae in QWidget::event (this=this@entry=0x182a3b0, event=event@entry=0x7ffe48bf45e0) at kernel/qwidget.cpp:9065 #14 0x7f544dea719b in QQuickWidget::event (this=0x182a3b0, e=0x7ffe48bf45e0) at qquickwidget.cpp:1525 #15 0x7f544ffbe39c in QApplicationPrivate::notify_helper (this=, receiver=0x182a3b0, e=0x7ffe48bf45e0) at kernel/qapplication.cpp:3727 #16 0x7f544ffc5ab0 in QApplication::notify (this=0x7ffe48bf4ec0, receiver=0x182a3b0, e=0x7ffe48bf45e0) at kernel/qapplication.cpp:3486 #17 0x7f544f1f1228 in QCoreApplication::notifyInternal2 (receiver=receiver@entry=0x182a3b0, event=event@entry=0x7ffe48bf45e0) at kernel/qcoreapplication.cpp:1048 #18 0x7f544fff6122 in QCoreApplication::sendEvent (event=0x7ffe48bf45e0, receiver=0x182a3b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #19 QWidgetPrivate::sendPendingMoveAndResizeEvents (this=this@entry=0x1ac32a0,
[krita] [Bug 396106] Alpha Lock not toggling off for selection/move tool
https://bugs.kde.org/show_bug.cgi?id=396106 Scott Petrovic changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||scottpetro...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Scott Petrovic --- I can confirm there is something odd going on with selections and moving. I am experiencing the same bug on my Windows 10 machine following those steps -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393167] [Wayland] Child window placement does not work
https://bugs.kde.org/show_bug.cgi?id=393167 --- Comment #10 from Andrius Štikonas --- (In reply to Alexander Mentyu from comment #9) > Updated Elisa - child windows are opening in top left, top right and bottom > right screen position - after moving the main Elisa window > > elisa-0.2.0-1 Elisa updates wouldn't help. That's not Elisa's problem. Windows are placed by kwin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393167] [Wayland] Child window placement does not work
https://bugs.kde.org/show_bug.cgi?id=393167 --- Comment #9 from Alexander Mentyu --- Updated Elisa - child windows are opening in top left, top right and bottom right screen position - after moving the main Elisa window elisa-0.2.0-1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396106] New: Alpha Lock not toggling off for selection/move tool
https://bugs.kde.org/show_bug.cgi?id=396106 Bug ID: 396106 Summary: Alpha Lock not toggling off for selection/move tool Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: kapyia@gmail.com Target Milestone: --- Created attachment 113726 --> https://bugs.kde.org/attachment.cgi?id=113726=edit Video demonstration Steps to recreate: 1. Open a new document with at least one empty layer 2. Block in an area of the canvas with any color on the empty layer 3. Toggle Alpha Lock on for the same layer 4. On the same layer, draw on top of the blocked-in area 5. Toggle Alpha Lock off 6. Select an area of what you've drawn and move it with the Move tool 7. The selection will be clipped once moved, despite Alpha Lock being toggled off Switching to a different tool and back to the Selection tool, or clearing the selection to make a new one, doesn't fix the issue. The issue will go away, however, once you add something new to the canvas. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396098] KWIN Crashes when OpenGL is choosen with nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=396098 hsf83...@sawoe.com changed: What|Removed |Added Attachment #113723|0 |1 is obsolete|| --- Comment #5 from hsf83...@sawoe.com --- Created attachment 113725 --> https://bugs.kde.org/attachment.cgi?id=113725=edit This is the new report after installing libproxy-tools-dbgsym Hello. i installed libproxy-tools-dbgsym (0.4.15-1). I hope this is correct ? i have attached the new crash log of kwin. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 393155] Doesn't resume playback using the media player/controller widget.
https://bugs.kde.org/show_bug.cgi?id=393155 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #7 from Alexander Mentyu --- Cannot reproduce with Media Player tray icon and play/pause button in Elisa elisa-0.2.0-1 Plasma: 5.13.2 Apps: 18.04.2 Frameworks: 5.47.0 Qt: 5.11.1 Kernel: 4.18.0-1-MANJARO OS: Netrunner Rolling Video: Intel 4400 Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1 Mesa 3D: 18.1.3 Screen: 1600x900 Xorg: 1.20 Wayland: 1.15.0-1 Wayland Protocols: 1.14-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393167] [Wayland] Child window placement does not work
https://bugs.kde.org/show_bug.cgi?id=393167 Andrius Štikonas changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393167] [Wayland] Child window placement does not work
https://bugs.kde.org/show_bug.cgi?id=393167 --- Comment #8 from Alexander Mentyu --- Child windows of Elisa player are opening in top left position of screen - not below the titlebar of parent window elisa-0.1.1-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393167] [Wayland] Child window placement does not work
https://bugs.kde.org/show_bug.cgi?id=393167 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #7 from Alexander Mentyu --- Can reproduce - top left child windows placement - below the parent window titlebar: Plasma: 5.13.2 Apps: 18.04.2 Frameworks: 5.47.0 Qt: 5.11.1 Kernel: 4.18.0-1-MANJARO OS: Netrunner Rolling Video: Intel 4400 Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1 Mesa 3D: 18.1.3 Screen: 1600x900 Xorg: 1.20 Wayland: 1.15.0-1 Wayland Protocols: 1.14-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #23 from Eike Hein --- Thanks, that helps a lot. I think this is fixable; I'll look into it soon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #22 from Michail Vourlakos --- I found a way to reproduce easier with plasma panel: 1. Add a folderview in a plasma panel 2. Click the folderview and the popup should look just fine 3. Increase the panel thickness until the folderview shows as FullRepresentation 4. Restore the panel thickness in order for the folderview to look as icon 5. Click the folderview and you will notice the problem. Whatever you do afterwards the popup should always look very small -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 374968] Battery flyout mistranslates “Vendor” as “Vendedor”; it should be “Fabricante”
https://bugs.kde.org/show_bug.cgi?id=374968 fitosch...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #2 from fitosch...@gmail.com --- I fail to follow your logic. You have provided a definition of the English term without noting that your translation is a false cognate of the original term. It makes no sense in Spanish. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396098] KWIN Crashes when OpenGL is choosen with nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=396098 --- Comment #4 from Martin Flöser --- Could you please install debug packages for libepoxy? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 396101] KWin crashed when dragging file over Task Manager
https://bugs.kde.org/show_bug.cgi?id=396101 Martin Flöser changed: What|Removed |Added Version|5.13.1 |5.47.0 Severity|normal |crash Product|kwin|frameworks-kwayland Assignee|kwin-bugs-n...@kde.org |mgraess...@kde.org Component|wayland-generic |server -- You are receiving this mail because: You are watching all bug changes.
[ksmtp] [Bug 395279] Can no longer send email via smtp
https://bugs.kde.org/show_bug.cgi?id=395279 --- Comment #12 from Allen Winter --- Yes, my $QT_PLUGIN_PATH looks fine. I played with a few things and nothing worked except for removing the distro plugin for mailtransport_smtpplugin.so I wonder if there's a .qtconf file somewhere that is overriding QT_PLUGIN_PATH oh well, at least the immediate crisis is solved. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #27 from Rooty --- (In reply to Oliver Sander from comment #26) > I am not saying that speed/memory consumption of Okular are great and cannot > be improved. However, the path from to the rather vague "Okular uses lots of > memory" to specific improvements to the code is long and windy. It would > help a lot to know in more specific terms which memory allocations are > problematic, and I was merely suggesting that you could try and help with > that. i'll try to check it out, but seeing as my understanding of how okular exactly works is really poor i wouldn't hold my breath, sorry :D but i can at the very least tell you that this shouldn't be swept under the rug -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396105] New: Crash after closing "Launch Feedback" section in System Settings
https://bugs.kde.org/show_bug.cgi?id=396105 Bug ID: 396105 Summary: Crash after closing "Launch Feedback" section in System Settings Product: systemsettings Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@thebitlink.com Target Milestone: --- Application: systemsettings5 (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.14.52-1-lts x86_64 Distribution: "Arch Linux" -- Information about the crash: Every time i open the Applications > Launch Feedback section and try to switch away from it, the application crashes. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8d43f0e840 (LWP 5719))] Thread 15 (Thread 0x7f8cd632b700 (LWP 6014)): #0 0x7f8d387d8641 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #1 0x7f8d3fe6f054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #2 0x7f8d3fe1a94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f8d3fc63a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #4 0x7f8d3d95b9c9 in () at /usr/lib/libQt5Qml.so.5 #5 0x7f8d3fc6db45 in () at /usr/lib/libQt5Core.so.5 #6 0x7f8d3ae3a075 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f8d3f55d53f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f8cf0978700 (LWP 5756)): #0 0x7f8d3881dec5 in () at /usr/lib/libglib-2.0.so.0 #1 0x7f8d387d7ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f8d387d84c6 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f8d387d88e2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #4 0x7f8d0ab9f348 in () at /usr/lib/libgio-2.0.so.0 #5 0x7f8d38800a2a in () at /usr/lib/libglib-2.0.so.0 #6 0x7f8d3ae3a075 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f8d3f55d53f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f8cf1179700 (LWP 5755)): #0 0x7f8d3f552ea9 in poll () at /usr/lib/libc.so.6 #1 0x7f8d387d8523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8d387d863e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f8d387d8692 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f8d38800a2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f8d3ae3a075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f8d3f55d53f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f8cf2521700 (LWP 5734)): #0 0x7f8d3ae3fffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8d2498fd44 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f8d2498fa38 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8d3ae3a075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8d3f55d53f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f8cf2d92700 (LWP 5733)): #0 0x7f8d3ae3fffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8d2498fd44 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f8d2498fa38 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8d3ae3a075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8d3f55d53f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f8cf3fff700 (LWP 5732)): #0 0x7f8d3ae3fffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8d2498fd44 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f8d2498fa38 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8d3ae3a075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8d3f55d53f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f8cf8823700 (LWP 5731)): #0 0x7f8d3ae3fffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8d2498fd44 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f8d2498fa38 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8d3ae3a075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f8d3f55d53f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f8cfa364700 (LWP 5730)): #0 0x7f8d3f56a8f2 in __libc_disable_asynccancel () at /usr/lib/libc.so.6 #1 0x7f8d3f552ebd in poll () at /usr/lib/libc.so.6 #2 0x7f8d387d8523 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f8d387d863e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f8d3fe6f054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f8d3fe1a94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f8d3fc63a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f8d3d95b9c9 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f8d3fc6db45 in () at
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #21 from Michail Vourlakos --- (In reply to Eike Hein from comment #20) > Michail, note the problem people are having here isn't the applet expanding > on the panel, it's the popup being very tiny. they are relevant because it happens when the folderview is switching from single icon in the panel to FullRepresentation and vice versa. You can use Latte in order to reproduce. Way to reproduce: 1. Revert my commit (https://phabricator.kde.org/D11651) for panel icon in order for FolderView to execute always the code: Plasmoid.switchWidth: preferredWidth(true) Plasmoid.switchHeight: preferredHeight(true) 2. Open Latte and disable the parabolic effect 3. Add a folderview in Latte 4. Close Latte and re-open it. 5. Click the FolderView in Latte it should work ok 6. Enable the parabolic effect in Latte and hover the folderview in order to change to FullRepresentation 7. disable the parabolic effect again in Latte in order for FolderView in Latte to stick in icon 8. Click the folderview and you will see the problem, whatever you change afterwards in folderview settings the popup will be always very small * 1) If you dont revert my commit then the problematic code cant be accessed except if your panel has bigger thickness than the panel icon size (this is why the proposal to set panel icon size to 256px. fixes the issue after relogin) * 2) the code that breaks is from preferredWidth(true)/preferredHeigth(true) and it needs also the plasmoid to change in the panel from CompactRepresentation to FullRepresentation and vice versa -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388224] KWin Crash Tabbing from Discord to Chromium
https://bugs.kde.org/show_bug.cgi?id=388224 --- Comment #3 from ja...@japellerano.com --- Created attachment 113724 --> https://bugs.kde.org/attachment.cgi?id=113724=edit New crash information added by DrKonqi kwin_x11 (5.12.5) using Qt 5.10.1 - What I was doing when the application crashed: Tabbing between applications, FireFox, Konsole and KDE Partition Manager. Default Fedora 28 KDE desktop -- Backtrace (Reduced): #6 0x7f4d5657cdb8 in si_emit_draw_packets () from /usr/lib64/dri/radeonsi_dri.so #7 0x7f4d5657f1e5 in si_draw_vbo () from /usr/lib64/dri/radeonsi_dri.so #8 0x7f4d562cd5b6 in tc_call_draw_vbo () from /usr/lib64/dri/radeonsi_dri.so #9 0x7f4d562ca8c0 in _tc_sync.isra.21 () from /usr/lib64/dri/radeonsi_dri.so #10 0x7f4d562cd4f9 in tc_texture_subdata () from /usr/lib64/dri/radeonsi_dri.so -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388224] KWin Crash Tabbing from Discord to Chromium
https://bugs.kde.org/show_bug.cgi?id=388224 ja...@japellerano.com changed: What|Removed |Added CC||ja...@japellerano.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383495] Debug symbols cannot be installed from Crash Reporting Assistant
https://bugs.kde.org/show_bug.cgi?id=383495 --- Comment #23 from Alexander Mentyu --- Is it can be wrong duplicate marking? - crash on connect to WiFi and debug symbols installation problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #20 from Eike Hein --- Michail, note the problem people are having here isn't the applet expanding on the panel, it's the popup being very tiny. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396104] New: Plasmashell crashed after adding a cpu load widget to the panel
https://bugs.kde.org/show_bug.cgi?id=396104 Bug ID: 396104 Summary: Plasmashell crashed after adding a cpu load widget to the panel Product: plasmashell Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: marcelo.jime...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.1) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Plasmashell crashed while I was adding a CPU load widget to the panel. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". futex_wait_cancelable (private=0, expected=0, futex_word=0x55bef387d010) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 88int err = lll_futex_timed_wait (futex_word, expected, NULL, private); [Current thread is 1 (Thread 0x7f0792679880 (LWP 3218))] Thread 25 (Thread 0x7f067ca47700 (LWP 30088)): #0 0x7f078b09c4ec in futex_wait_cancelable (private=0, expected=0, futex_word=0x55befa1ea020) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f078b09c4ec in __pthread_cond_wait_common (abstime=0x0, mutex=0x55befa1e9fd0, cond=0x55befa1e9ff8) at pthread_cond_wait.c:502 #2 0x7f078b09c4ec in __pthread_cond_wait (cond=0x55befa1e9ff8, mutex=0x55befa1e9fd0) at pthread_cond_wait.c:655 #3 0x7f078bf06fdb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #4 0x7f078feb42a9 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55bef9e55c98) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #5 0x7f078feb42a9 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55bef9e55c20) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:709 #6 0x7f078feb44da in QSGRenderThread::run() (this=0x55bef9e55c20) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:738 #7 0x7f078bf0691c in () at /usr/lib64/libQt5Core.so.5 #8 0x7f078b096554 in start_thread (arg=) at pthread_create.c:463 #9 0x7f078b7ebfdf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f0686287700 (LWP 30083)): #0 0x7f078b7e15d9 in __GI___poll (fds=0x7f062800cbe0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f07859082c6 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f07859083ec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f078c0eebcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f078c09ebbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f078befd336 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f078f9ad085 in QQmlThreadPrivate::run() (this=0x7f077407da80) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #7 0x7f078bf0691c in () at /usr/lib64/libQt5Core.so.5 #8 0x7f078b096554 in start_thread (arg=) at pthread_create.c:463 #9 0x7f078b7ebfdf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f067affd700 (LWP 30037)): #0 0x7f078b09c4ec in futex_wait_cancelable (private=0, expected=0, futex_word=0x55bef9c632e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f078b09c4ec in __pthread_cond_wait_common (abstime=0x0, mutex=0x55bef9c63290, cond=0x55bef9c632b8) at pthread_cond_wait.c:502 #2 0x7f078b09c4ec in __pthread_cond_wait (cond=0x55bef9c632b8, mutex=0x55bef9c63290) at pthread_cond_wait.c:655 #3 0x7f078bf06fdb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #4 0x7f078feb42a9 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55befa86ada8) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #5 0x7f078feb42a9 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55befa86ad30) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:709 #6 0x7f078feb44da in QSGRenderThread::run() (this=0x55befa86ad30) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:738 #7 0x7f078bf0691c in () at /usr/lib64/libQt5Core.so.5 #8 0x7f078b096554 in start_thread (arg=) at pthread_create.c:463 #9 0x7f078b7ebfdf in clone () at
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #19 from Eike Hein --- There's likely going to be changes to it. There's two problems currently: a) I can't reproduce it on my system at all. I need to set up something where I can reproduce it first. b) I am currently very busy and in the middle of travel preparations, so I haven't had time for it. I may or may not find some time this week. In the meantime any other dev is very welcome to look into it to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #18 from S. Christian Collins --- Why can't this be fixed to work like it did before, where it was actually useful without taking up a crazy amount of horizontal space in the panel? In the past, I've used a folder view icon on the panel to bring up a quick access list of frequently used files. In Plasma 5.13, the files list window is too small to be of any use, and if I make the icon space super-wide, then I'm losing a ton of space on an already cramped panel. A feature that was once a major part of my workflow has now become unusable :( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396102] ResultsModel emits wrong rowsMoved transactions
https://bugs.kde.org/show_bug.cgi?id=396102 --- Comment #2 from Eike Hein --- I'm currently too busy to attempt a fix in KActivitiesStats, so here's a workaround for Kicker for now: https://phabricator.kde.org/D13856 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396103] New: "disbale clip" still does not work with title clip
https://bugs.kde.org/show_bug.cgi?id=396103 Bug ID: 396103 Summary: "disbale clip" still does not work with title clip Product: kdenlive Version: 18.04.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: j...@cspv.hu Target Milestone: --- I would expect the "disable clip" functionality (activated by ticking the checkbox) to work for title clips, too... but it doesn't ... I think, it definitely should... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396103] "disbale clip" still does not work with title clips
https://bugs.kde.org/show_bug.cgi?id=396103 peter josvai changed: What|Removed |Added Summary|"disbale clip" still does |"disbale clip" still does |not work with title clip|not work with title clips -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390510] Dolphin Crash
https://bugs.kde.org/show_bug.cgi?id=390510 --- Comment #2 from Gijsbertus --- (In reply to Julian Schraner from comment #1) > Hello and thanks for reporting this crash! Have you been able to reproduce > this crash again, especially with Dolphin v18.04? Nope, since then I haven't been able to replicate. Perhaps not a bug after all? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395174] Search using string 'keepass' does not display the program 'keepassx' in search result
https://bugs.kde.org/show_bug.cgi?id=395174 --- Comment #20 from accr...@yahoo.com --- (In reply to Aleix Pol from comment #19) > Can you check what's the output of "appstreamcli search keepass"? Output is (in direct translation): "Could not find component matching keepass!" I also searched for 'keepassX', and interestingly enough the output is the same even though the exact search does work in Discover. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396102] ResultsModel emits wrong rowsMoved transactions
https://bugs.kde.org/show_bug.cgi?id=396102 --- Comment #1 from Eike Hein --- Note that KActivitiesStatsTestApp doesn't catch this because it doesn't seem to use ResultsModel and doesn't do live updating. The query when re-run produces the right results, so the db is fine; just the model doesn't update correctly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 396102] New: ResultsModel emits wrong rowsMoved transactions
https://bugs.kde.org/show_bug.cgi?id=396102
Bug ID: 396102
Summary: ResultsModel emits wrong rowsMoved transactions
Product: frameworks-kactivities-stats
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: ivan.cu...@kde.org
Reporter: h...@kde.org
CC: plasma-b...@kde.org
Target Milestone: ---
A ResultsModel with the following query:
RecentlyUsedFirst | Agent::any() | Type::any() | Activity::current() |
Url::startsWith("applications:") | Limit(15)
... does not correctly update when apps listed in the model are launched. For
example, after launching the app at index 3, I would expect a moveRows from 3
to 0, but I get a 3 to 5.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 396101] New: KWin crashed when dragging file over Task Manager
https://bugs.kde.org/show_bug.cgi?id=396101 Bug ID: 396101 Summary: KWin crashed when dragging file over Task Manager Product: kwin Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kacperkas...@gmail.com Target Milestone: --- This was actually a one time crash, that I can't reproduce anymore. Plasmashell crashed a moment before, there is a separate bug report for that: https://bugs.kde.org/show_bug.cgi?id=396100 Steps to Reproduce: 1) Drag a file 2) Move it over Task Manager 3) Move it out of the Task Manager Actual Results: kwin crashes Expected Results: kwin does not crash Additional Information: openSuSE Tumbleweed 20180629 Qt 5.11.1 KF 5.47.0 plasma 5.13.1 Linux 4.17.3-1-default 64-bit Wayland Stack trace: #0 0x7ff09d46fd03 in KWayland::Server::DataDeviceInterface::updateDragTarget(KWayland::Server::SurfaceInterface*, unsigned int) (this=0x55d9a6f6e4f0, surface=surface@entry=0x0, serial=serial@entry=5643) at /usr/src/debug/kwayland-5.47.0-1.2.x86_64/src/server/datadevice_interface.cpp:256 #1 0x7ff09d48fa70 in KWayland::Server::SeatInterface::setDragTarget(KWayland::Server::SurfaceInterface*, QPointF const&, QMatrix4x4 const&) (this=0x55d9a6818340, surface=0x55d9a755a690, globalPosition=..., inputTransformation=...) at /usr/src/debug/kwayland-5.47.0-1.2.x86_64/src/server/seat_interface.cpp:649 #2 0x7ff09e51a52d in KWin::DragAndDropInputFilter::pointerEvent(QMouseEvent*, unsigned int) (this=, event=0x7fff3285e540, nativeButton=) at /usr/src/debug/kwin5-5.13.1-1.1.x86_64/toplevel.h:824 #3 0x7ff09e52cb78 in std::__invoke_impl(std::__invoke_memfun_deref, bool (KWin::InputEventFilter::*&)(QMouseEvent*, unsigned int), KWin::InputEventFilter* const&, KWin::MouseEvent*&, int&) (__f=@0x7fff3285e4e0: table offset 16, __f=@0x7fff3285e4e0: table offset 16, __t=@0x55d9a6818758: 0x55d9a6d0f0d0) at /usr/include/c++/8/bits/invoke.h:89 #4 0x7ff09e52cb78 in std::__invoke(bool (KWin::InputEventFilter::*&)(QMouseEvent*, unsigned int), KWin::InputEventFilter* const&, KWin::MouseEvent*&, int&) (__fn=@0x7fff3285e4e0: table offset 16) at /usr/include/c++/8/bits/invoke.h:95 #5 0x7ff09e52cb78 in std::_Bind, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)>::__call(std::tuple&&, std::_Index_tuple<0ul, 1ul, 2ul>) (__args=..., this=0x7fff3285e4e0) at /usr/include/c++/8/functional:400 #6 0x7ff09e52cb78 in std::_Bind, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)>::operator()(KWin::InputEventFilter* const&) (this=0x7fff3285e4e0) at /usr/include/c++/8/functional:484 #7 0x7ff09e52cb78 in __gnu_cxx::__ops::_Iter_pred, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> >::operator()(KWin::InputEventFilter* const*) (__it=0x55d9a6818758, this=0x7fff3285e4e0) at /usr/include/c++/8/bits/predefined_ops.h:283 #8 0x7ff09e52cb78 in std::__find_if, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> > >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, __gnu_cxx::__ops::_Iter_pred, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> >, std::random_access_iterator_tag) (__first=0x55d9a6818758, __last=0x55d9a68187c8, __pred=...) at /usr/include/c++/8/bits/stl_algo.h:128 #9 0x7ff09e528407 in std::__find_if, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> > >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, __gnu_cxx::__ops::_Iter_pred, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> >) (__pred=..., __last=, __first=) at /usr/include/c++/8/bits/stl_algo.h:159 #10 0x7ff09e528407 in std::find_if, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)>) (__pred=..., __last=, __first=) at /usr/include/c++/8/bits/stl_algo.h:3930 #11 0x7ff09e528407 in std::none_of, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)>) (__pred=..., __last=, __first=) at /usr/include/c++/8/bits/stl_algo.h:526 #12 0x7ff09e528407 in std::any_of, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)>) (__pred=..., __last=, __first=) at /usr/include/c++/8/bits/stl_algo.h:544 #13 0x7ff09e528407 in KWin::InputRedirection::processFilters, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)> >(std::_Bind, KWin::MouseEvent*, int))(QMouseEvent*, unsigned int)>) (function=..., this=) at /usr/src/debug/kwin5-5.13.1-1.1.x86_64/input.h:189 #14 0x7ff09e528407 in
[plasmashell] [Bug 396100] Dragging a file over taskbar and moving it out crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396100 Kacper Kasper changed: What|Removed |Added Component|Task Manager|Icons-only Task Manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396011] Dragging icons doesn't work most of the time
https://bugs.kde.org/show_bug.cgi?id=396011 --- Comment #3 from David Korth --- I'm using Qt 5.11.1. I'll file a bug upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396100] New: Dragging a file over taskbar and moving it out crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396100 Bug ID: 396100 Summary: Dragging a file over taskbar and moving it out crashes plasma Product: plasmashell Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kacperkas...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Steps to Reproduce: 1) Drag a file 2) Move it over Task Manager 3) Move it out of the Task Manager Actual Results: plasmashell crashes Expected Results: plasmashell does not crash Additional Information: openSuSE Tumbleweed 20180629 Qt 5.11.1 KF 5.47.0 plasma 5.13.1 Linux 4.17.3-1-default 64-bit Wayland It generates different stack traces, excerpt from one of them: #0 0x7fadff537bcc in DeclarativeMimeData::DeclarativeMimeData(QMimeData const*) (this=0x561bff2c7500, copy=0x561bfdf65230) at /usr/src/debug/kdeclarative-5.47.0-1.2.x86_64/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:55 #1 0x7fadff5370e0 in DeclarativeDragDropEvent::mimeData() (this=0x7ffe88f4eca0) at /usr/include/qt5/QtGui/qevent.h:625 #2 0x7fadff539315 in DeclarativeDragDropEvent::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /usr/src/debug/kdeclarative-5.47.0-1.2.x86_64/build/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:120 #3 0x7faeadff6e39 in QQmlPropertyData::readProperty(QObject*, void*) const (property=0x7ffe88f4cce0, target=, this=0x561bff082db8) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/include/QtQml/5.11.1/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:328 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346619] MTP IOSlave should use f_bsize for block size
https://bugs.kde.org/show_bug.cgi?id=346619 --- Comment #4 from Vladimir --- (In reply to Nate Graham from comment #3) > Thanks for the update! So the slowness of not respecting f_bsize manifested > when you used Dolphin to move or copy a file (via copy-paste or > drag-and-drop) to a local mount for an MTP device? Yes, it was like that. Current value 128K is enough for everyone © Almost I think it's generally good practive to align IO size to size of filesystem block, so filesystem will not squeeze your data into any tail-space in case of small write, etc. My MTP implementation uses partial reads/writes to avoid full object sending/retrieval, making MTP as fast as any other way to transfer data from/to device. The problem with partial objects, it's done from userspace on android, and this approach has an additional overhead of starting/committing object transaction. I've decided to advertise large block size to userspace, it worked with some other file managers, but not the dolphin. :) Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390510] Dolphin Crash
https://bugs.kde.org/show_bug.cgi?id=390510 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com --- Comment #1 from Julian Schraner --- Hello and thanks for reporting this crash! Have you been able to reproduce this crash again, especially with Dolphin v18.04? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396099] [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 --- Comment #1 from Andrius Štikonas --- Hmm, seems to work here. I could change to Dummy without a crash. I should probably try to build on F29 too to see if I can reproduce... Strangely, crash happens in the code that reads colours from settings file. Was this a new system? Or did you run older versions of KPM there (although, it shouldn't interfere in my oppinion). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396098] KWIN Crashes when OpenGL is choosen with nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=396098 David Edmundson changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|BACKTRACE |--- --- Comment #3 from David Edmundson --- thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396098] KWIN Crashes when OpenGL is choosen with nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=396098 --- Comment #2 from hsf83...@sawoe.com --- Created attachment 113723 --> https://bugs.kde.org/attachment.cgi?id=113723=edit Executable: kwin_x11 PID: 2881 Signal: Aborted (6) Time: 02.07.18 18:53:38 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396099] New: [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 Bug ID: 396099 Summary: [kauth] no devices listed and crash if select dummy backend Product: partitionmanager Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- Created attachment 113722 --> https://bugs.kde.org/attachment.cgi?id=113722=edit backtrace I tried to build kauth branch on a Fedora Rawhide (F29) test virtual machine. When I launch partitionmanager I get no device listed. Looking in the settings, I tried to change the backend from sfdisk to Dummy, as soon as I click on apply, partitionmanager crashes with the attached backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396098] KWIN Crashes when OpenGL is choosen with nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=396098 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from David Edmundson --- If kwin actually crashes, can we have a backtrace please. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396098] New: KWIN Crashes when OpenGL is choosen with nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=396098 Bug ID: 396098 Summary: KWIN Crashes when OpenGL is choosen with nouveau drivers Product: kwin Version: 5.13.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: hsf83...@sawoe.com Target Milestone: --- Whenever i select opengl rendering it doesnt matter if open gl 2.1 or 3.0 is selected Kwin crashes and falls back to xrendr mode. However this is only the case with nouveau drivers. (GTX850) Steps to Reproduce: 1) Enable the NVIDIA Card with the Variable DRI_PRIME=1 2) Go to KWIN Settings and select OPENGL Rendering Results: KWIN crashes and falls back to XRENDR Mode Expected Results: KWIN should now use OPENGL Build Date & Platform: KDE NEON 5.13 with all updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395618] Text glitching when moving file or folder on desktop w/ font rendering on subpixel hinting RGB and moderate
https://bugs.kde.org/show_bug.cgi?id=395618 --- Comment #9 from Richard Addison --- I'll check how things stand in Neon. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396074] kmail does not remember folder list columns setting
https://bugs.kde.org/show_bug.cgi?id=396074 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Laurent Montel --- qt5.10 was broken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395618] Text glitching when moving file or folder on desktop w/ font rendering on subpixel hinting RGB and moderate
https://bugs.kde.org/show_bug.cgi?id=395618 --- Comment #8 from Richard Addison --- Created attachment 113721 --> https://bugs.kde.org/attachment.cgi?id=113721=edit I've changed the settings and no more font glitching ... but The only way I could get rid of the glitch was by setting sub-pixel rendering to "none". The downside is that font rendering in Firefox has gotten somewhat worse. All info is captured in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395746] KIO Slaves visibility
https://bugs.kde.org/show_bug.cgi?id=395746 vasoserg...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #2 from vasoserg...@gmail.com --- I don't think this is a duplicate of bug 329292. I'm asking for a better more obvious way of illustrating that there are other protocols available for use. I only found it myself by accident. Bug 329292 is talking about scrolling through that list whilst you're in an empty location bar. It already assumes you have knowledge of that list in the first place. I'm asking about making it more obvious there is in fact a list to be able to scroll through or pick from. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 396097] New: Bug in KDE desktop. Set Settings to doubleclick. Plasma desktop opens TWO instance when double clicking
https://bugs.kde.org/show_bug.cgi?id=396097 Bug ID: 396097 Summary: Bug in KDE desktop. Set Settings to doubleclick. Plasma desktop opens TWO instance when double clicking Product: frameworks-plasma Version: 5.47.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: kdeb...@galaxy.za.net Target Milestone: --- Open KDE settings... set mouse to doubleclick to open application. Dolphin honors it. KDE desktop doesn't. Expected behavior: KDE desktop: doubleclick chrome icon should open ONE instance of Gooogle Chrome. Not TWO. Don't spin it. Just accept it as a bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396094] Empty Map Plots in PDF
https://bugs.kde.org/show_bug.cgi?id=396094 Oliver Sander changed: What|Removed |Added Ever confirmed|0 |1 CC||oliver.san...@tu-dresden.de Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Oliver Sander --- Can this be a Splash backend issue? I can confirm the problem with Okular 1.4.70 and poppler 0.63. However, I do see the missing data when I switch to the poppler Arthur backend. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #26 from Oliver Sander --- I am not saying that speed/memory consumption of Okular are great and cannot be improved. However, the path from to the rather vague "Okular uses lots of memory" to specific improvements to the code is long and windy. It would help a lot to know in more specific terms which memory allocations are problematic, and I was merely suggesting that you could try and help with that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396095] Pixel Brush Rotation Does Not Respond to Pressure
https://bugs.kde.org/show_bug.cgi?id=396095 --- Comment #4 from Kenneth Evans --- Hi Dmitry Thanks for the info. I didn't know what Fuzzy Dab is. Nevertheless, the bug is that it doesn't respond to pressure. I do have 1024 levels of pressure. The preset is also set to Opacity on pressure, and you can see the opacity varies. In general pressure works fine for me in Krita. Your screenshot just shows you can set it (unless I missed something). Does it work? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395921] discover 'update all' shows no error Msgs when apt preinstall step fails
https://bugs.kde.org/show_bug.cgi?id=395921 --- Comment #4 from Achim Bohnet --- On a debian based system: # cat >/etc/apt/apt.conf.d/00-fail-on-preload
[Discover] [Bug 395921] discover 'update all' shows no error Msgs when apt preinstall step fails
https://bugs.kde.org/show_bug.cgi?id=395921 --- Comment #3 from Achim Bohnet --- On a debian based system: # cat >/etc/apt/apt.conf.d/00-fail-on-preload
[kwin] [Bug 395732] KWin crashed when opening an application.
https://bugs.kde.org/show_bug.cgi?id=395732 David Edmundson changed: What|Removed |Added Resolution|FIXED |UPSTREAM --- Comment #8 from David Edmundson --- FYI, the workaround got reverted due to a side effect. Workaround concept is fine, but we need to capture more objects..and then it gets messy. A proper fix is included in the upcoming Qt 5.12 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395732] KWin crashed when opening an application.
https://bugs.kde.org/show_bug.cgi?id=395732 David Edmundson changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #9 from David Edmundson --- *** Bug 396096 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396096] /usr/bin/kwin_wayland asserts: Scene::windowClosed: assert(m_windows.contains(c));
https://bugs.kde.org/show_bug.cgi?id=396096 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 395732 *** -- You are receiving this mail because: You are watching all bug changes.
[ksmtp] [Bug 395279] Can no longer send email via smtp
https://bugs.kde.org/show_bug.cgi?id=395279 --- Comment #11 from Daniel Vrátil --- Do you have $KDE_PREFIX/lib64/plugins in your QT_PLUGIN_PATH? That's should be good enough - the code looks for the KMailTransport plugins in $QT_PLUGIN_PATH/mailtransport - at least for me it works this way just fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396096] New: /usr/bin/kwin_wayland asserts: Scene::windowClosed: assert(m_windows.contains(c));
https://bugs.kde.org/show_bug.cgi?id=396096 Bug ID: 396096 Summary: /usr/bin/kwin_wayland asserts: Scene::windowClosed: assert(m_windows.contains(c)); Product: kwin Version: 5.12.5 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bernha...@mailbox.org Target Milestone: --- Just tried a plasma wayland session and found following when closing a window. Might be related to using non default theme (changed it last year because of a Qt bug). What looks suspicious is that KWin::ShellClient::destroyClient is twice in the callstack for the same object. If there is anything else I can provide, the core file is still there and all needed debug packages installed. (Not sure about the component selected for this bug report.) Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/x86_64'. Program terminated with signal SIGABRT, Aborted. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7fc92210830f in __GI_abort () at abort.c:100 #2 0x7fc9220ff9da in __assert_fail_base (fmt=0x7fc909213129 , assertion=assertion@entry=0x7fc925110272 "m_windows.contains(c)", file=file@entry=0x7fc9251102e0 "/build/kwin-posrbs/kwin-5.12.5/scene.cpp", line=line@entry=414, function=function@entry=0x7fc925110480 "void KWin::Scene::windowClosed(KWin::Toplevel*, KWin::Deleted*)") at assert.c:92 #3 0x7fc9220ffa52 in __GI___assert_fail (assertion=assertion@entry=0x7fc925110272 "m_windows.contains(c)", file=file@entry=0x7fc9251102e0 "/build/kwin-posrbs/kwin-5.12.5/scene.cpp", line=line@entry=414, function=function@entry=0x7fc925110480 "void KWin::Scene::windowClosed(KWin::Toplevel*, KWin::Deleted*)") at assert.c:101 #4 0x7fc92501c81f in KWin::Scene::windowClosed (this=0x5638a2713d60, c=, deleted=0x5638a2ecbd40) at ./scene.cpp:414 #5 0x7fc9250edc43 in KWin::Scene::qt_static_metacall (_o=, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/kwin_autogen/EWIEGA46WW/moc_scene.cpp:98 #6 0x7fc922cfb195 in QMetaObject::activate (sender=sender@entry=0x5638a2d19c90, signalOffset=, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7fff3fa8d320) at kernel/qobject.cpp:3767 #7 0x7fc922cfb867 in QMetaObject::activate (sender=sender@entry=0x5638a2d19c90, m=m@entry=0x7fc92539fc80 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7fff3fa8d320) at kernel/qobject.cpp:3629 #8 0x7fc9250e68de in KWin::Toplevel::windowClosed (this=this@entry=0x5638a2d19c90, _t1=, _t1@entry=0x5638a2d19c90, _t2=, _t2@entry=0x5638a2ecbd40) at ./obj-x86_64-linux-gnu/kwin_autogen/EWIEGA46WW/moc_toplevel.cpp:718 #9 0x7fc92508b9ac in KWin::ShellClient::destroyClient (this=0x5638a2d19c90) at ./shell_client.cpp:362 #10 0x7fc922cfb2af in QtPrivate::QSlotObjectBase::call (a=0x7fff3fa8d490, r=0x5638a2d19c90, this=0x5638a2d20430) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378 #11 QMetaObject::activate (sender=sender@entry=0x5638a29c21d0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff3fa8d490) at kernel/qobject.cpp:3750 #12 0x7fc922cfb867 in QMetaObject::activate (sender=sender@entry=0x5638a29c21d0, m=m@entry=0x7fc923124a60 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff3fa8d490) at kernel/qobject.cpp:3629 #13 0x7fc922cfb90f in QObject::destroyed (this=this@entry=0x5638a29c21d0, _t1=, _t1@entry=0x5638a29c21d0) at .moc/moc_qobject.cpp:214 #14 0x7fc922d020ca in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:902 #15 0x7fc924127397 in KWayland::Server::XdgTopLevelV6Interface::~XdgTopLevelV6Interface (this=0x5638a29c21d0, __in_chrg=) at ./src/server/xdgshell_v6_interface_p.h:92 #16 KWayland::Server::XdgTopLevelV6Interface::~XdgTopLevelV6Interface (this=0x5638a29c21d0, __in_chrg=) at ./src/server/xdgshell_v6_interface_p.h:92 #17 0x7fc922cfbd20 in QObject::event (this=0x5638a29c21d0, e=) at kernel/qobject.cpp:1238 #18 0x7fc92328e6cc in QApplicationPrivate::notify_helper (this=this@entry=0x5638a260ae80, receiver=receiver@entry=0x5638a29c21d0, e=e@entry=0x7fc8f8006220) at kernel/qapplication.cpp:3732 #19 0x7fc923295e84 in QApplication::notify (this=0x7fff3fa8e800, receiver=0x5638a29c21d0, e=0x7fc8f8006220) at kernel/qapplication.cpp:3491 #20 0x7fc922ccb938 in QCoreApplication::notifyInternal2 (receiver=0x5638a29c21d0, event=event@entry=0x7fc8f8006220) at kernel/qcoreapplication.cpp:1050 #21 0x7fc922cce4cd in QCoreApplication::sendEvent (event=0x7fc8f8006220, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=52, data=0x5638a2613330) at
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #44 from Tim Steinberger --- Actually, I apologize, this might be a different bug. I was able to build flatpak without systemd support and install it. I found it crashes with both installed (though takes longer than if just packagekit-qt5 is installed). Bug number is 396069. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496
--- Comment #42 from Tim Steinberger ---
I found this bug after googling what seemed to be the error message most likely
to cause the crash. As this gave the exact same behavior I assumed this was
what was causing it. Here is the log from the command line if I start discover
from there, maybe I missed something obvious.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
QQmlComponent: Created graphical object was not placed in the graphics scene.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
error loading "flatpak-backend" "Cannot load library
/usr/lib/qt/plugins/discover/flatpak-backend.so: (libflatpak.so.0: cannot open
shared object file: No such file or directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","MetaData":{},"className":"FlatpakBackendFactory","debug":false,"version":330497})
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x564cc1ec2850)
could not find "org.kde.krita.desktop" "krita.desktop"
could not find "org.kde.krita.desktop" "krita.desktop"
Error when fetching the last update time
QDBusError("org.freedesktop.DBus.Error.Spawn.ChildExited", "Launch helper
exited with unknown return code 127")
Transaction error: PackageKit::Transaction::Error(ErrorInternalError) "Launch
helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1ea51d0)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f8c040)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f8c040)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f81d80)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f81d80)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f87ba0)
qml: message: Launch helper exited with unknown return code 127
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-discover path = /usr/bin pid = 2889
KCrash: Arguments: /usr/bin/plasma-discover
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 25 and type 'Read', disabling...
QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
QSocketNotifier: Invalid socket 33 and type 'Write', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Write', disabling...
QSocketNotifier: Invalid socket 32 and type 'Write', disabling...
QSocketNotifier: Invalid socket 26 and type 'Write', disabling...
QSocketNotifier: Invalid socket 28 and type 'Write', disabling...
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496
--- Comment #43 from Tim Steinberger ---
I found this bug after googling what seemed to be the error message most likely
to cause the crash. As this gave the exact same behavior I assumed this was
what was causing it. Here is the log from the command line if I start discover
from there, maybe I missed something obvious.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
QQmlComponent: Created graphical object was not placed in the graphics scene.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
error loading "flatpak-backend" "Cannot load library
/usr/lib/qt/plugins/discover/flatpak-backend.so: (libflatpak.so.0: cannot open
shared object file: No such file or directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","MetaData":{},"className":"FlatpakBackendFactory","debug":false,"version":330497})
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x564cc1ec2850)
could not find "org.kde.krita.desktop" "krita.desktop"
could not find "org.kde.krita.desktop" "krita.desktop"
Error when fetching the last update time
QDBusError("org.freedesktop.DBus.Error.Spawn.ChildExited", "Launch helper
exited with unknown return code 127")
Transaction error: PackageKit::Transaction::Error(ErrorInternalError) "Launch
helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1ea51d0)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f8c040)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f8c040)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f81d80)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f81d80)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f87ba0)
qml: message: Launch helper exited with unknown return code 127
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-discover path = /usr/bin pid = 2889
KCrash: Arguments: /usr/bin/plasma-discover
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 25 and type 'Read', disabling...
QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
QSocketNotifier: Invalid socket 33 and type 'Write', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Write', disabling...
QSocketNotifier: Invalid socket 32 and type 'Write', disabling...
QSocketNotifier: Invalid socket 26 and type 'Write', disabling...
QSocketNotifier: Invalid socket 28 and type 'Write', disabling...
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 396095] Pixel Brush Rotation Does Not Respond to Pressure
https://bugs.kde.org/show_bug.cgi?id=396095 Dmitry Kazakov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Dmitry Kazakov --- And to make the rotation of the brush random, just activate "Fuzzy Dab" sensor with linear curve. It will make your brush rotated for every dab painted. If you still have questions or you think I misunderstood the bug report, please feel free to reopen it :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396067] Update Button Absent
https://bugs.kde.org/show_bug.cgi?id=396067 --- Comment #2 from Aleix Pol --- Looks it could be an issue in the QStyle plugin you are using. Can you give a try with Breeze or one of the default ones? If so, look into reporting there. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396095] Pixel Brush Rotation Does Not Respond to Pressure
https://bugs.kde.org/show_bug.cgi?id=396095 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #2 from Dmitry Kazakov --- Created attachment 113720 --> https://bugs.kde.org/attachment.cgi?id=113720=edit Screenshot showing connecting stylus pressure to brush rotation Hi, Kenneth! Do you have pressure sensibility in Krita at all? Here I can easily connect pressure to brush rotation (see the screenshot attached) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #41 from Aleix Pol --- Tim Steinberger, how do you know this is the bug you're hitting? FWIW, I just tried here removing flatpak, it works just fine. -- You are receiving this mail because: You are watching all bug changes.
