[kwin] [Bug 395807] Closing an application crashes Kwin (aurora on x11)
https://bugs.kde.org/show_bug.cgi?id=395807 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Flags||X11+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395807] Closing an application crashes Kwin (aurora on x11)
https://bugs.kde.org/show_bug.cgi?id=395807 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Summary|Closing an application |Closing an application |crashes Kwin|crashes Kwin (aurora on ||x11) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395807] New: Closing an application crashes Kwin
https://bugs.kde.org/show_bug.cgi?id=395807 Bug ID: 395807 Summary: Closing an application crashes Kwin Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: 1i5t5.dun...@cox.net CC: familieku...@arcor.de, k...@davidedmundson.co.uk, kwin-bugs-n...@kde.org, now.im@gmail.com, pmaiol...@gmail.com Depends on: 395346 Target Milestone: --- +++ This bug was initially created as a clone of Bug #395346 +++ kwin git master head at e69da579f, using gentoo/kde's overlay repo kde live-git packages and qt-5.11.0-rc2 (latest available in gentoo main repo). Git commit 275b7ee0f apparently fixed a crash on kwin-wayland with aurora windecos, referring to the bug I cloned for this one. But it breaks kwin_x11 in the same way it fixes kwin_wayland -- closing a window with an aurora windeco set crashes kwin_x11! Confirmed that it's aurora windecos only by trying breeze (ok), oxygen (ok) and plastik (broken, believed to be aurora). Confirmed that reverting just that commit on current master head ( e69da579f ) fixes the problem. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=395346 [Bug 395346] Closing an application crashes Kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395346] Closing an application crashes Kwin
https://bugs.kde.org/show_bug.cgi?id=395346 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Blocks||395807 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=395807 [Bug 395807] Closing an application crashes Kwin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 --- Comment #6 from leodream2...@gmail.com --- Created attachment 113531 --> https://bugs.kde.org/attachment.cgi?id=113531=edit display setting -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 leodream2...@gmail.com changed: What|Removed |Added CC||leodream2...@gmail.com --- Comment #5 from leodream2...@gmail.com --- I has encountered the same issue. In my case, the primary display is 90 degrees rotated (1200*1920) and the second one is on its right. Please reference attached displaysetting.png I placed a widget in the lower-left corner of the primary display. Every time the computer reboots, the widget will be placed to the middle of the left edge and I have to drag the widget again. Maybe it is because the widget is rendered or position recalculated before applying the rotation during the startup? The issue is a bit annoying. I am trying to find a way to move the widget through command line so I can schedule it at the startup, avoiding manually drag the widget every time. Using the API from https://userbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting#API , I can only modify the widget position in the plasma-org.kde.plasma.desktop-appletsrc file. Any help is appreciated. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395806] When drawing, random lines are appearing
https://bugs.kde.org/show_bug.cgi?id=395806 cruz...@yahoo.com changed: What|Removed |Added OS|Linux |OS X -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395806] New: When drawing, random lines are appearing
https://bugs.kde.org/show_bug.cgi?id=395806 Bug ID: 395806 Summary: When drawing, random lines are appearing Product: krita Version: 4.0.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: cruz...@yahoo.com Target Milestone: --- Created attachment 113530 --> https://bugs.kde.org/attachment.cgi?id=113530=edit this is the problem. I am using Huion H610 on a MacOsX. Whenever I draw in Krita, random lines just keep appearing when drawing normal lines. For example, if I draw just a normal straight line, another line would just branch out and it goes for the same with circles. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394921] Desktop Display Corrupted
https://bugs.kde.org/show_bug.cgi?id=394921 nroycea+...@gmail.com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WORKSFORME |--- --- Comment #19 from nroycea+...@gmail.com --- Ugh, too soon I'm afraid. (also, seeing I have the option to change the status). No idea why it happened now. But I will say 2 changes I've made was to the workspace theme/colors and adding widgets. I've changed them back (I think), but the corruption didn't change. I probably have to log out first for it to clear up. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395805] New: Accents are not working in Falkon
https://bugs.kde.org/show_bug.cgi?id=395805 Bug ID: 395805 Summary: Accents are not working in Falkon Product: Falkon Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: rrnetopant...@gmail.com Target Milestone: --- The accents not working in Facebook, but in another sites it works fine. Version: 3.0.1. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 395804] New: Regression: "Switch Display" invoked via global shortcut no longer allows keyboard-only operation
https://bugs.kde.org/show_bug.cgi?id=395804 Bug ID: 395804 Summary: Regression: "Switch Display" invoked via global shortcut no longer allows keyboard-only operation Product: KScreen Version: 5.13.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: andydecle...@gmail.com Target Milestone: --- The new pop-up display invoked by the "Switch Display" global keyboard shortcut is very nice, but also brings a regression in that it cannot be operated, or even exited, using the keyboard alone. It does not take keyboard focus, so ESC or cursor keys or Enter or any other keys affect an active window below the pop-up, which I find unexpected and inconvenient. In my case, I'm often using the global shortcut after hooking up a laptop to one or more external displays and then moving across a room to operate by wireless keyboard, which is now impossible. I suggest keyboard operability to be restored by having the pop-up take keyboard focus, having ESC trigger the "Leave unchanged" action, cursor keys change which action is selected, and Enter trigger the selected action. I do not know which action ought to be selected initially. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393888] kickoff unusable/broken when I change the position of plasma panel on screen from bottom/top to left/right or vice-versa
https://bugs.kde.org/show_bug.cgi?id=393888 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395803] New: Rotoscopy undo not working
https://bugs.kde.org/show_bug.cgi?id=395803 Bug ID: 395803 Summary: Rotoscopy undo not working Product: kdenlive Version: 18.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- Sometimes I delete some keyframe accidentally. If I try to "undo" (ctrl-z) the action, KDEnlive doesn't not recover last removed keyframe. In fact, KDEnlive seems to undo last global action, not latest action I made in Rotoscopy effect. Please, any way to "undo" properly in rotoscopy? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395774] Doesn't prompt to save KRA before Saving as PNG
https://bugs.kde.org/show_bug.cgi?id=395774 --- Comment #2 from Kenneth Evans --- Thanks, I'll try export. However I think this should be fixed. Having a check box in a dialog is a long ways from prompting you for sure to not lose your work. It is almost universal to ask to save before leaving unsaved work (for good reason). Krita is not doing that in this case, and that makes it unfriendly. And it isn't that hard to fix. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395802] New: Quality level: Selection bar and numeric value unsynchronized
https://bugs.kde.org/show_bug.cgi?id=395802 Bug ID: 395802 Summary: Quality level: Selection bar and numeric value unsynchronized Product: kdenlive Version: 18.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- Created attachment 113529 --> https://bugs.kde.org/attachment.cgi?id=113529=edit Quality level unsynchronized I am using a project in KDEnlive to make several videos, changing only some tracks in the project and rendering after each change. However, I realized that despite I have selected 30 for quality the previous rendering, each time I begin a new render, despite the numeric value is 30, the draggable selector is at the right (max quality) as you can see in attached image. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395801] New: Text with shadow extrange behaviour on editing
https://bugs.kde.org/show_bug.cgi?id=395801 Bug ID: 395801 Summary: Text with shadow extrange behaviour on editing Product: kdenlive Version: 18.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: rafael.linux.u...@gmail.com Target Milestone: --- Created attachment 113528 --> https://bugs.kde.org/attachment.cgi?id=113528=edit Shadow incorrectly showed when editing. I have several text clips with shadow (x=0, y=0, blur=3). When I enter to edit text, the shadow the shadow of the last lines appears unaligned (see attached image) while editing. When I accept changes, all is fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395375] Pop-up palette rotates with canvas if using external ring
https://bugs.kde.org/show_bug.cgi?id=395375 --- Comment #7 from Jonathan Liu --- I have submitted a patch to fix the bug: https://phabricator.kde.org/D13703 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 388439] Find -> Filename - doesn't find anything in Dolphin
https://bugs.kde.org/show_bug.cgi?id=388439
skierpage changed:
What|Removed |Added
CC||skierp...@gmail.com
--- Comment #3 from skierpage ---
I have many and various problems like this with Baloo. It mostly works but with
many corner cases and quirks.
I have many text files that Dolphin Find by Filename won't find when I choose
type "Any", but which *do* show up if I choose type "Documents". So try
different type restrictions.
Dolphin Find by Filename works oddly if you enter a single letter. It will
return no or few files when you type one letter, but as you type more it will
return a lot. E.g. if I type 'o' it returns 3 files TABLES_O.FW3, NEW_VS_O.DIF,
and BYK8KO~O.PDF, but if I type 'or' it returns 4 Folders and 62 Files with
names like CCMAIL.ORG, oracover.doc, etc. So at first it seems to be looking
for an exact match with the letter 'o' on its own, treating the filename as a
set of words ("TABLES" and "O" and "FW3"), but then it switches to do a partial
match. But it's still matching from the start of "words" in filenames, e.g.
typing 'mai' won't find CCMAIL.txt but will find SPAGE_MAIL.txt The behavior is
undocumented and non-obvious. It would be great if someone knowledgeable wrote
an explanation of Dolphin's find by Filename.
In reply to Nate Graham from comment #1)
> The find panel uses information from Baloo, so
> it's likely Baloo is messed up on your machine. You might try some of the
> things outlined here: https://community.kde.org/Baloo/Debugging
How can you simulate Dolphin's Find by Filename from the command line?
baloosearch doesn't have a filename switch.
https://community.kde.org/Baloo/Debugging doesn't say anything about how
Dolphin's Find by Filename works. `balooshow -x /path/to/γένεος_baloo_test.txt`
has a line
File Name Terms: Fbaloo Ftest Ftxt Fγενεος baloo test txt γενεος
and I think if you type more than one character in Dolphin's find by Filename,
it does a match against these terms anchored at the start. Or something like
that...
^If these sentences are correct I can add them to KDE Community Wiki somewhere.
--
You are receiving this mail because:
You are watching all bug changes.
[gwenview] [Bug 386034] Wish: Drag image from Gwenview's view mode to initiate drag and drop operation
https://bugs.kde.org/show_bug.cgi?id=386034
Huon changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/gwe
||nview/984b9737f0796c48ab68f
||e0f60bc179e26fbcf62
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Version Fixed In||18.08.0
--- Comment #2 from Huon ---
Git commit 984b9737f0796c48ab68fe0f60bc179e26fbcf62 by Huon Imberger.
Committed on 24/06/2018 at 01:26.
Pushed by huoni into branch 'master'.
Allow dragging from View mode to external applications
Summary:
This patch adds drag functionality to {nav View} mode. A
drag operation is only initiated if dragging wouldn't
otherwise do something, e.g. when zoomed and the image is
pannable, or the crop tool is active.
In order to get a drag pixmap for all cases (videos
included), we use a ThumbnailProvider to generate a file
preview. However, if the image is modified, we generate a
new pixmap using the edited version. Using
`MimeTypeUtils::selectionMimeData`, this should mean the
drag pixmap always matches the image the receiving
application gets.
FIXED-IN: 18.08.0
{F5781358}
Test Plan:
Drag from View mode, comparison mode.
Try raster, SVG, and video file types, including when the
image is modified (cropped or rotated).
Panning a zoomed image should still be possible.
Drag operation should always get a thumbnail/icon pixmap
representing the dropped image.
Reviewers: #gwenview, rkflx
Reviewed By: #gwenview, rkflx
Tags: #gwenview
Differential Revision: https://phabricator.kde.org/D11877
M +2-2lib/documentview/abstractdocumentviewadapter.h
M +6-0lib/documentview/abstractimageview.cpp
M +2-0lib/documentview/abstractimageview.h
M +106 -0lib/documentview/documentview.cpp
M +3-0lib/documentview/documentview.h
M +5-0lib/documentview/rasterimageviewadapter.cpp
M +1-0lib/documentview/rasterimageviewadapter.h
M +5-0lib/documentview/svgviewadapter.cpp
M +2-0lib/documentview/svgviewadapter.h
https://commits.kde.org/gwenview/984b9737f0796c48ab68fe0f60bc179e26fbcf62
--
You are receiving this mail because:
You are watching all bug changes.
[korganizer] [Bug 395800] New: Tasklist Panel in "Agenda" view doesn't show my tasks.
https://bugs.kde.org/show_bug.cgi?id=395800 Bug ID: 395800 Summary: Tasklist Panel in "Agenda" view doesn't show my tasks. Product: korganizer Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-b...@kde.org Reporter: aalexand...@gmail.com Target Milestone: --- Tasklist Panel in "Agenda" view doesn't show my tasks. It can show one to-do, after turning off and on related source, but after switching view, for example to "To-do List" and back, it also disappears. All my to-dos are simple, without due date, and priorities. I have to-dos as from gmail, as from Next Cloud Server (CalDAV). They are all visible in "To-do List" view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395799] New: typing "Th"+another letter in app search tool crashes dashboard
https://bugs.kde.org/show_bug.cgi?id=395799 Bug ID: 395799 Summary: typing "Th"+another letter in app search tool crashes dashboard Product: plasmashell Version: 5.12.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: christopher.horw...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.16.0-kali2-amd64 x86_64 Distribution: Kali GNU/Linux Rolling -- Information about the crash: - What I was doing when the application crashed: Nothing, happens after each restart of system - Unusual behavior I noticed: The dashoard will flash several times then crash when you type 'Th'+any other letter in the application search toolbar in kali linux - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f52b5478cc0 (LWP 1536))] Thread 27 (Thread 0x7f5183fff700 (LWP 1922)): #0 0x7f52ae2254ec in futex_wait_cancelable (private=, expected=0, futex_word=0x55bd7394cb14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52ae2254ec in __pthread_cond_wait_common (abstime=0x0, mutex=0x55bd7394cac0, cond=0x55bd7394cae8) at pthread_cond_wait.c:502 #2 0x7f52ae2254ec in __pthread_cond_wait (cond=0x55bd7394cae8, mutex=0x55bd7394cac0) at pthread_cond_wait.c:655 #3 0x7f52af078fbb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f51f9c4c6d5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f51f9c507a8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f51f9c4b8fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f51f9c50802 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f51f9c4b8fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f51f9c4e66b in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f52af077b4f in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f52ae21f5aa in start_thread (arg=0x7f5183fff700) at pthread_create.c:463 #12 0x7f52ae976cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f51b0ff9700 (LWP 1921)): #0 0x7f52ae2254ec in futex_wait_cancelable (private=, expected=0, futex_word=0x55bd7394cb14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52ae2254ec in __pthread_cond_wait_common (abstime=0x0, mutex=0x55bd7394cac0, cond=0x55bd7394cae8) at pthread_cond_wait.c:502 #2 0x7f52ae2254ec in __pthread_cond_wait (cond=0x55bd7394cae8, mutex=0x55bd7394cac0) at pthread_cond_wait.c:655 #3 0x7f52af078fbb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f51f9c4c6d5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f51f9c507a8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f51f9c4b8fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f51f9c50802 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f51f9c4b8fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f51f9c50802 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f51f9c4b8fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f51f9c4e66b in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f52af077b4f in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f52ae21f5aa in start_thread (arg=0x7f51b0ff9700) at pthread_create.c:463 #14 0x7f52ae976cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f51b17fa700 (LWP 1920)): #0 0x7f52ae2254ec in futex_wait_cancelable (private=, expected=0, futex_word=0x55bd7394cb14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52ae2254ec in __pthread_cond_wait_common (abstime=0x0, mutex=0x55bd7394cac0, cond=0x55bd7394cae8) at
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #11 from sac --- OK, we need a proper solution. Apart from security, evdevremapkeys & xbindkeys don't work for productive use (GTK apps like Thunderbird remap input events, one has to click several times to trigger an action after another window had focus; totally messed up). Libinput pointed back to DE & Toolkit ( https://gitlab.freedesktop.org/libinput/libinput/issues/44 ). This affects basically every user and we expect from them to reprogram Kernels if they want to remap sth. properly :( Does noone have good connections to QT, which I guess is our last option here? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395798] New: Density in Bristle brush isn't pressure sensitive parameter and it isn't exposed in Popup Palette
https://bugs.kde.org/show_bug.cgi?id=395798 Bug ID: 395798 Summary: Density in Bristle brush isn't pressure sensitive parameter and it isn't exposed in Popup Palette Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: nikola.knezevic@gmail.com Target Milestone: --- - DENSITY - Bristle engine in Krita have great potential and I find it really unique. It is strange that density parameter isn't exposed to be controlled via pen pressure. It is not exposed to controllable parameters in Popup palette. Available parameters are (Brush HUD Configuration): Angle, Auto Spacing, Flow (???), Opacity, Size, Spacing. - FLOW - Flow doesn't exist in bristle brush settings interface but it is exposed in Popup palette. It doesn't have any effect on bristle brush behavior either. Something is confusing here. ... I think Density should/must be pressure controlled and exposed to Popup palette. I wonder if Density can become Flow in bristle engine? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395766] Moving panel from bottom to left breaks the start menu
https://bugs.kde.org/show_bug.cgi?id=395766 Dr. Chapatin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 393888 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393888] kickoff unusable/broken when I change the position of plasma panel on screen from bottom/top to left/right or vice-versa
https://bugs.kde.org/show_bug.cgi?id=393888 Dr. Chapatin changed: What|Removed |Added CC||loveshufflebl...@gmail.com --- Comment #4 from Dr. Chapatin --- *** Bug 395766 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 340667] Add "sort By" rating option
https://bugs.kde.org/show_bug.cgi?id=340667
Henrik Fehlauer changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/gwe
||nview/faa19b06b14eb2e6c74b6
||c88f170f5c66a77b80a
Status|CONFIRMED |RESOLVED
--- Comment #1 from Henrik Fehlauer ---
Git commit faa19b06b14eb2e6c74b6c88f170f5c66a77b80a by Henrik Fehlauer, on
behalf of Farid Boudedja.
Committed on 23/06/2018 at 22:03.
Pushed by rkflx into branch 'master'.
Add possibility to sort by rating
Summary:
Gwenview allows to rate images but there is no option to sort images by rating.
Add 'Rating' as a sorting option to Gwenview's SortedDirModel.
Add 'Rating' to Gwenview's 'Sort By' menu.
Add 'Rating' to Gwenview's 'Sorting' configuration entry.
Depends on: D13669
Test Plan:
- Give specific ratings to some images in Gwenview.
- Click {nav View > Sort By > Rating}.
- The images should be sorted according to their ratings.
Reviewers: #gwenview, rkflx
Reviewed By: #gwenview, rkflx
Subscribers: muhlenpfordt, rkflx, broulik
Differential Revision: https://phabricator.kde.org/D13344
M +14 -0app/browsemainpage.cpp
M +1-0lib/gwenviewconfig.kcfg
M +16 -5lib/semanticinfo/sorteddirmodel.cpp
M +4-1lib/sorting.h
https://commits.kde.org/gwenview/faa19b06b14eb2e6c74b6c88f170f5c66a77b80a
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 395796] Bristle brush Ink depletion checkbox doesn't turn off some settings when unchecked
https://bugs.kde.org/show_bug.cgi?id=395796 nikola changed: What|Removed |Added Summary|Bristle brush Ink depletion |Bristle brush Ink depletion |checkbox doesn't turn off |checkbox doesn't turn off |some settings when |some settings when |inchecked |unchecked -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395797] New: any fading out transparency + using this effect = system frozen
https://bugs.kde.org/show_bug.cgi?id=395797 Bug ID: 395797 Summary: any fading out transparency + using this effect = system frozen Product: kwin Version: 5.8.9 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: adria...@gmail.com Target Milestone: --- Hi, I have a problem related to KWin, I'm using "Show Desktop Grid" hotkey (Default is Ctrl+F8) a lot. This is listed under KWin component. If there's a fade out going on the screen of any element, and I press the hotkey, plasma desktop freezes. For example, the fadeout of a tooltip: you get a frozen half faded out tooltip, cpu fan goes to max speed, and you only get to move the mouse cursor. Pressing Ctrl+Alt+F1 works: I tried killing kwin to see if it would automatically restart, restoring my workspace but it doesn't. Let me know if you need any more information. I'm running into this bug almost every day Cheers! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395796] New: Bristle brush Ink depletion checkbox doesn't turn off some settings when inchecked
https://bugs.kde.org/show_bug.cgi?id=395796 Bug ID: 395796 Summary: Bristle brush Ink depletion checkbox doesn't turn off some settings when inchecked Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: nikola.knezevic@gmail.com Target Milestone: --- test case: 1. turn Ink depletion on (check) 2. check Soak Ink 3. turn Ink depletion off (uncheck) 4. Soak Ink is still active (paint something to ensure) tested on windows 7 and 8.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395626] [Regression] Combining composite + position and zoom effect crops too early
https://bugs.kde.org/show_bug.cgi?id=395626 --- Comment #7 from Vincent Petry --- Created attachment 113527 --> https://bugs.kde.org/attachment.cgi?id=113527=edit Revert patch for bd78c208bc43f5d2e2833621fb6a4a1bcc9d54f2 Revert of bd78c208bc43f5d2e2833621fb6a4a1bcc9d54f2. Does NOT solve the transition issue. Unless I didn't overwrite the correct so files... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395626] [Regression] Combining composite + position and zoom effect crops too early
https://bugs.kde.org/show_bug.cgi?id=395626 --- Comment #6 from Vincent Petry --- Hmph... Whatever I do, when using the manually compiled mlt from git with proper dirs, kdenlive shows green vertical bars in the preview panel and crashes when I open my test project. I took the compilation option from the RPM build log to make sure it has the right paths: % ./configure --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/lib --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-sdl --enable-sdl2 --enable-debug --enable-gpl --enable-gpl3 --enable-extra-versioning --swig-languages=python % make -j4 % sudo make install This gives me the green bars and crashes. Maybe I've hit upon another bug or env issue. I'll need to get this working to be able to properly bisect later on. For now, I've used a barbaric approach and copied the modules manually on top of the RPM files: % sudo cp lib*.so /usr/lib64/mlt-6/ At least now kdenlive works as before. And using this approach, reverting bd78c208bc43f5d2e2833621fb6a4a1bcc9d54f2 did NOT solve the transition issue. So I'll likely need to bisect. I've attached the reverted commit in case I did something wrong during conflict resolution. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395795] New: Zoom and Position hides backgrond layer
https://bugs.kde.org/show_bug.cgi?id=395795 Bug ID: 395795 Summary: Zoom and Position hides backgrond layer Product: kdenlive Version: 18.04.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: ezra...@gmail.com Target Milestone: --- Hi I get this bug both on Kdenlive and Shotcut, which makes me suspect this is a problem with a dependency rather than the software itself. I'm trying to add a small image on top of a video using the 'Position and Zoom' effect, like this: https://imgur.com/91xy4ER but instead I'm getting something like this: https://imgur.com/7xEntwP Video and image used for this case: https://videos.pexels.com/videos/blurry-video-of-people-working-853789 https://pixabay.com/en/shoe-print-sole-reprint-trace-3482282/ STR: * Open Kdenlive * Add the video and image to files * Add the video to 'Video 1' track * Add the image to 'Video 2' track * Expand the image to the entire video size * Add a 'Position and Zoom' effect to the image * Render video to file (the bug appears already on the preview, but just to be sure I've rendered the project and it shows on the output too) Screenshot of workspace: https://imgur.com/1y7ebsA -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395626] [Regression] Combining composite + position and zoom effect crops too early
https://bugs.kde.org/show_bug.cgi?id=395626 --- Comment #5 from Vincent Petry --- Thanks for the info. While I could settle on the workaround, I think the issue should be addressed in general for other people who might be using Composite for other purposes. Here is my action plan: 0) Solve crash issues with kdenlive from git v18.04.2 and mlt from git v6.8.0, likely related to environment and/or compilation options 1) Attempt to revert bd78c208bc43f5d2e2833621fb6a4a1bcc9d54f2 on top of v6.8.0 (with conflict resolution) and see if issue is fixed 2) If not fixed, bisect mlt to find when it stopped working (needs compiling matching kdenlive version when crossing mlt version boundaries) 3) Try out dissolve workaround (not sure why I used composite and never saw this one) Currently at step 0 and have some alternative things to try out before asking for help. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 183429] open externally called folder in new tab
https://bugs.kde.org/show_bug.cgi?id=183429 King Kang Kong changed: What|Removed |Added CC||r2b2x3+kde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382418] Krita froze during a save and Autosave didn't save the animation
https://bugs.kde.org/show_bug.cgi?id=382418 Eli changed: What|Removed |Added CC||elizabethstreeter66@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395381] Crashing Xwayland locks-up kwin_wayland keboard and mouse
https://bugs.kde.org/show_bug.cgi?id=395381 --- Comment #16 from Martin Flöser --- If you are not satisfied with the quality of Xwayland you have the option to run KWin without it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395703] Can't change window decoration
https://bugs.kde.org/show_bug.cgi?id=395703 --- Comment #9 from Martin Flöser --- You are still using egl. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 --- Comment #6 from Martin Flöser --- (In reply to Benjamin Xiao from comment #4) > The monitor most definitely supports 144Hz. It's a Acer Predator XB271HU > bmiprz 27" WQHD (2560x1440) NVIDIA G-SYNC IPS Display. > > xrandr also shows that I am on 144Hz as well. How come KWin doesn't just > check xrandr for refresh rate and then match that? Well we do exactly that. We use the xrandr API. It's btw. not that surprising that it works on Wayland. There we interact more directly with the API. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395785] Kwin_X11 crash when I open lid
https://bugs.kde.org/show_bug.cgi?id=395785 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387449] Creating a folder named "." or ".." doesn't display an error
https://bugs.kde.org/show_bug.cgi?id=387449 Julian Schraner changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||juliquad...@gmail.com Version|17.08.3 |18.04.2 --- Comment #1 from Julian Schraner --- Can confirm with Dolphin 18.04.2, thanks for reporting! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 sanya7...@gmail.com changed: What|Removed |Added CC||sanya7...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387652] Dolphin crashed after selection of 'Open With...' for .zip file
https://bugs.kde.org/show_bug.cgi?id=387652 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Julian Schraner --- Hmm, I cannot reproduce this crash with Dolphin 18.04.2. Have you been experiencing this behavior again? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389265] Dolphin crashes when quickly deleting files
https://bugs.kde.org/show_bug.cgi?id=389265 --- Comment #6 from k...@trummer.xyz --- I don't see it either on Dolphin 18.04.2 anymore so I assume it has been fixed in between this version and 17.12. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389265] Dolphin crashes when quickly deleting files
https://bugs.kde.org/show_bug.cgi?id=389265 Julian Schraner changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||juliquad...@gmail.com Status|UNCONFIRMED |NEEDSINFO --- Comment #5 from Julian Schraner --- I cannot reproduce this crash with Dolphin 18.04.2... If you do still experience the crash, please attach a complete backtrace. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395778] Impliment Display Tab Of All Items Connected To USB In Panels Device Notifier
https://bugs.kde.org/show_bug.cgi?id=395778 --- Comment #3 from Zakhar --- Make kinfo center available via system notification areA, some people have hubs and like to know whats active -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395701] When rendering MP4 - the dominating format (H264/AAC) it cuts off some frames from the beginning of clips
https://bugs.kde.org/show_bug.cgi?id=395701 --- Comment #1 from Barade --- When I select the clip and the action "Analyse keyframes" it says "no valid clip". I am trying to transcode the clips now and another format. Shouldn't all the keyframes be recalculated when the video is rendered and so no frames should be cut off? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393752] Budgeted vs. Actual report: Budgeted values broken if ticks selected to Bi-Monthly, Quarterly or Yearly
https://bugs.kde.org/show_bug.cgi?id=393752 Michael Carpino changed: What|Removed |Added CC||mfcarp...@gmail.com --- Comment #1 from Michael Carpino --- It appears the issue is related to the calculation within the first column of the report. If you change the ticks as noted by Erik it only takes into account a single month of the budgeted amount in the first column when you change from Bi-Monthly, Quarterly or Yearly. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 395747] The mute mic button in plasmoid does not indicate current system state
https://bugs.kde.org/show_bug.cgi?id=395747 Aditya Mehra changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Aditya Mehra --- Mycroft shouldn't be muting the whole system audio capture in the first place, and should only be muting Mycroft mic capture internally. Fix in progress -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 395794] New: Easily switch between devices
https://bugs.kde.org/show_bug.cgi?id=395794 Bug ID: 395794 Summary: Easily switch between devices Product: plasma-pa Version: 5.13.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: snd.no...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Hi, This is more of a feature request than a bug actually, nevertheless it is an important usability issue. Add the possibility to switch between connected devices from within the audio applet. This widget kind of does this but it should be incorporated into the audio widget: https://store.kde.org/p/1195707 -- 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 vinnywright changed: What|Removed |Added CC||charles.v.wri...@gmail.com --- Comment #5 from vinnywright --- Created attachment 113526 --> https://bugs.kde.org/attachment.cgi?id=113526=edit crash report.txt -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 289207] KMail sometimes fails to send messages with cyrus-sasl-2.1.25
https://bugs.kde.org/show_bug.cgi?id=289207 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 395793] New: qif export date range ignored
https://bugs.kde.org/show_bug.cgi?id=395793 Bug ID: 395793 Summary: qif export date range ignored Product: kmymoney Version: 5.0.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: exporter Assignee: kmymoney-de...@kde.org Reporter: b...@mroczka.com Target Milestone: --- The export to qif file is not working as expected. When attempting to specify a date range the resulting output file contains all account transactions instead of those that fall within the specified date range. I have found that it sometimes works if I type in a new file that does not already exist. If the output file does exist there is no prompt to overwrite and the output always contains all transactions in the account. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 365944] SIGSEGV in Akonadi::Tag::isValid() crashing KAddressbook on startup with configured CardDav, or KOrganizer on event edition (or creation) or access to settings
https://bugs.kde.org/show_bug.cgi?id=365944 Filipus Klutiero changed: What|Removed |Added Summary|KAddressbook crashes on |SIGSEGV in |startup with configured |Akonadi::Tag::isValid() |CardDav |crashing KAddressbook on ||startup with configured ||CardDav, or KOrganizer on ||event edition (or creation) ||or access to settings -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 395777] disInstr(arm): unhandled instruction: 0xE7F000F0 (wine, dlls/msvcp90/tests/misc.c)
https://bugs.kde.org/show_bug.cgi?id=395777 Peter Maydell changed: What|Removed |Added CC||peter.mayd...@linaro.org --- Comment #2 from Peter Maydell --- The last four of those are all in 0xe7fxxxfx, which is the UDF always-undefined insn. The only "handling" needed here would be suppressing the warning (probably reasonable, since these undefined insns tend to get used by JITs and the like for various clever tricks). 0xe611 is a random not-yet-allocated encoding in the "parallel arithmetic" instruction class. Google claims it was "used by gdb 4.x"... -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 395792] New: Skrooge V 2.13.0 Crash On Opening
https://bugs.kde.org/show_bug.cgi?id=395792 Bug ID: 395792 Summary: Skrooge V 2.13.0 Crash On Opening Product: skrooge Version: unspecified Platform: PCLinuxOS OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: timnj...@hotmail.co.uk CC: steph...@mankowski.fr Target Milestone: --- Did my weekly Reload of PCLinuxOS earlier today, since when Skrooge crashes immediately you try and open it. It crashes so quickly it's impossible to see any error message. I've tried to reinstall just Skrooge using Synaptic, but it produces an "failed" type message with no details. I have restarted the machine three times - same result. I'm on PCLinuxOS (4.11.8-PCLOS1) 2017 Thanks in anticipation. Tim Johnson -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395455] Discover buttons install/remove/launch disappear
https://bugs.kde.org/show_bug.cgi?id=395455 --- Comment #6 from Michał Dybczak --- Ah thanks. In two panel mode bug still exists. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 395749] Device pairings are lost between reboots
https://bugs.kde.org/show_bug.cgi?id=395749 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- Just to be sure, your are talking about rebooting the desktop? Does this happen with all your devices? The pairing is stored in ~/.config/kdeconnect/trusted_devices Can you please compare its content before and after reboot? Also please provide your KDE Connect version, distro version and KDE Frameworks version -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 375840] MTP connection crashes after few minutes on several phones
https://bugs.kde.org/show_bug.cgi?id=375840 Gery changed: What|Removed |Added CC||bugzi...@cablelink.at -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395381] Crashing Xwayland locks-up kwin_wayland keboard and mouse
https://bugs.kde.org/show_bug.cgi?id=395381 --- Comment #15 from ahc --- In my case I did patch plasma-workspace, ie krunner, to not call Xwayland by defaulting to QT_QPA_PLATFORM=wayland, which is why I'm not experiencing any Xwayland crash. When you run startplasmacompositor, the script invokes xwayland: "/bin/kwin_wayland --xwayland --libinput --exit-with-session=/lib/startplasma". I must point out that I don't use any Xorg server. Plasma doesn't run completely on wayland, so Xwayland is required I guess. for instance, I had to patch splasma-desktop to build kcm_mouse cutting cutting out the Xorg code. This has been a long waited feature for me. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395791] New: Discover crashes upon launching 'Manage [program]' from app menu
https://bugs.kde.org/show_bug.cgi?id=395791 Bug ID: 395791 Summary: Discover crashes upon launching 'Manage [program]' from app menu Product: Discover Version: 5.13.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: yst...@posteo.net Target Milestone: --- Created attachment 113525 --> https://bugs.kde.org/attachment.cgi?id=113525=edit backtrace Attaching backtrace as attachment (too long for comment) Reproducible every time. - What I was doing when the application crashed: Steps to reproduce: 1. Open app menu 2. Right-click any app 3. Choose the option 'Manage [program]' 4. Discover launches and displays the app entry, crashes after 2 secs The crash can be reproduced every time. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 365944] KAddressbook crashes on startup with configured CardDav
https://bugs.kde.org/show_bug.cgi?id=365944 --- Comment #26 from Volker --- Because it's unclear to me: Do You expect me to change the title of the (resolved) bug report? To what it should be changed? I reported this crash 2 years ago, my actual system is working, so what to do?? Greetings, volker -- 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 cr...@solarsells.co.za changed: What|Removed |Added CC||cr...@solarsells.co.za Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from cr...@solarsells.co.za --- I have the same issue. Since the 5.13.1 update my system has bee unusable. I have spent half an hour just trying to post this bug report. Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd3783b7940 (LWP 3096))] Thread 5 (Thread 0x7fd33351c700 (LWP 3106)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd3740c6e04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fd3740c6e49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fd370e326ba in start_thread (arg=0x7fd33351c700) at pthread_create.c:333 #4 0x7fd377de541d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fd33b427700 (LWP 3105)): #0 0x7fd377dd9811 in __GI_ppoll (fds=0x7fd334000ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7fd375194651 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd375195ce2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd3751401ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd374f755e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd36fad0cf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fd374f80727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd370e326ba in start_thread (arg=0x7fd33b427700) at pthread_create.c:333 #8 0x7fd377de541d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fd347fff700 (LWP 3104)): #0 0x7fd377dd9811 in __GI_ppoll (fds=0x7fd34ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7fd375194651 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd375195ce2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd3751401ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd374f755e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd36fad0cf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fd374f80727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd370e326ba in start_thread (arg=0x7fd347fff700) at pthread_create.c:333 #8 0x7fd377de541d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fd356997700 (LWP 3101)): #0 0x7fd377dd9811 in __GI_ppoll (fds=0x7fd35000f828, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7fd375194651 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd375195ce2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd3751401ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd374f755e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd36e9def35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fd374f80727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd370e326ba in start_thread (arg=0x7fd356997700) at pthread_create.c:333 #8 0x7fd377de541d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fd3783b7940 (LWP 3096)): [KCrash Handler] #6 0x7fd37514c7e1 in QMetaObject::indexOfProperty(char const*) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd37516cceb in QObject::property(char const*) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd3701fa746 in QSGDefaultRenderContext::invalidate() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fd370314fbb in QQuickRenderControl::invalidate() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fd370314ff0 in QQuickRenderControl::~QQuickRenderControl() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fd370315039 in QQuickRenderControl::~QQuickRenderControl() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fd37516fc00 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fd375f0b29c in
[digikam] [Bug 395790] New: Rename with nested tags breaks due to | bar character
https://bugs.kde.org/show_bug.cgi?id=395790 Bug ID: 395790 Summary: Rename with nested tags breaks due to | bar character Product: digikam Version: 5.9.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: AdvancedRename Assignee: digikam-bugs-n...@kde.org Reporter: vilkm...@gmail.com Target Milestone: --- When renaming a file using "[file] - [meta:Xmp.digiKam.TagsList]" nested tags are separated by a bar | character, which is not a valid filename character in Windows 10. The rename fails at this point. Example tags: Location|Paris -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395789] New: Plasma crashed after trying to select WiFi network under Wayland
https://bugs.kde.org/show_bug.cgi?id=395789 Bug ID: 395789 Summary: Plasma crashed after trying to select WiFi network under Wayland Product: plasmashell Version: 5.13.1 Platform: Netrunner Rolling OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: notux...@gmail.com 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-MANJARO x86_64 Distribution: "Netrunner Rolling" -- Information about the crash: - What I was doing when the application crashed: Pressed once NetworkManager WiFi menu applet and nothing happens pressed one more time and Plasma crashed -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57262f1f00 (LWP 1579))] Thread 9 (Thread 0x7f5655989700 (LWP 1850)): [KCrash Handler] #6 0x7f571e2aaf31 in wl_proxy_create_wrapper () at /usr/lib/libwayland-client.so.0 #7 0x7f5707de6244 in () at /usr/lib/libEGL_mesa.so.0 #8 0x7f5707dcffdc in () at /usr/lib/libEGL_mesa.so.0 #9 0x7f570c466a52 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #10 0x7f570c464e92 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #11 0x7f572029d4c9 in QOpenGLContext::makeCurrent(QSurface*) () at /usr/lib/libQt5Gui.so.5 #12 0x7f5723af33d5 in () at /usr/lib/libQt5Quick.so.5 #13 0x7f5723af8cbe in () at /usr/lib/libQt5Quick.so.5 #14 0x7f5723af83de in () at /usr/lib/libQt5Quick.so.5 #15 0x7f5723af869c in () at /usr/lib/libQt5Quick.so.5 #16 0x7f571fb0bb45 in () at /usr/lib/libQt5Core.so.5 #17 0x7f571ecaa075 in start_thread () at /usr/lib/libpthread.so.0 #18 0x7f571f3fb53f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f5657434700 (LWP 1763)): #0 0x7f571ecafffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f571fb0c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f5723af842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7f5723af869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f571fb0bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7f571ecaa075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f571f3fb53f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f566f7ff700 (LWP 1745)): #0 0x7f571f3f0ea9 in poll () at /usr/lib/libc.so.6 #1 0x7f5718f58523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f5718f5863e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f571fd0d054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f571fcb894c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f571fb01a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f5723a7723b in () at /usr/lib/libQt5Quick.so.5 #7 0x7f571fb0bb45 in () at /usr/lib/libQt5Core.so.5 #8 0x7f571ecaa075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f571f3fb53f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f5674a19700 (LWP 1744)): #0 0x7f571ecafffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f571fb0c2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f5723af842d in () at /usr/lib/libQt5Quick.so.5 #3 0x7f5723af869c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f571fb0bb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7f571ecaa075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f571f3fb53f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f56f6c64700 (LWP 1743)): #0 0x7f571ecafffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57259c3aac in () at /usr/lib/libQt5Script.so.5 #2 0x7f57259c3ac9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f571ecaa075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f571f3fb53f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f5705134700 (LWP 1646)): #0 0x7f571ecafffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5705dcf124 in () at /usr/lib/dri/i965_dri.so #2 0x7f5705dcee18 in () at /usr/lib/dri/i965_dri.so #3 0x7f571ecaa075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f571f3fb53f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f570dcb8700 (LWP 1637)): #0 0x7f5718f9f2f4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f5718f57f1a in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f5718f584c6 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f5718f5863e in g_main_context_iteration () at
[kwin] [Bug 395703] Can't change window decoration
https://bugs.kde.org/show_bug.cgi?id=395703 --- Comment #8 from Ennai --- Here: https://pastebin.com/BA90bzg0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395381] Crashing Xwayland locks-up kwin_wayland keboard and mouse
https://bugs.kde.org/show_bug.cgi?id=395381 --- Comment #14 from James --- Obviously, the presumption that "we are using the non-blocking xcb library" is a false assumption, since, in what follows, the assertion is tacitly made that, in fact, the xcb library *is* blocking. It is a contradiction to say that "the xcb library is non-blocking" and then that "the xcb library is blocking". Saying both that "xcb is not robust for these kind of issues" and then that "xcb is still blocking is not a problem" is also a contradiction in reasoning. "xcb is not robust" *is* a problem. This is not the 20th Century any more. The world has moved along, and no matter that xcb was released in 2001. X11 is out. Wayland is in. xcb needs to grow-up. And then saying "we cannot do anything about it" is just not true. KDE is not the bastard step child of xcb, just lucky to survive on crumbs. Don't put-up with brain-dead problems caused by xcb. Tell them to fix it! Or, do not use xcb. Only punk mechanics blame their tools for bad worksmanship! Use something that works, and stop blaming other people. Still, none of that explains why the kwin_wayland calls to xcb are blocking. Nor does it explain why the Plasma Panel is calling out to xcb in the first place. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391312] Rename with time template can add colons (:) forbidden character in Windows 10
https://bugs.kde.org/show_bug.cgi?id=391312 vilkm...@gmail.com changed: What|Removed |Added CC||vilkm...@gmail.com --- Comment #7 from vilkm...@gmail.com --- *** Bug 395788 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395788] If tags have a : in them, rename effectively deletes the file
https://bugs.kde.org/show_bug.cgi?id=395788 vilkm...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from vilkm...@gmail.com --- *** This bug has been marked as a duplicate of bug 391312 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395788] If tags have a : in them, rename effectively deletes the file
https://bugs.kde.org/show_bug.cgi?id=395788 --- Comment #1 from vilkm...@gmail.com --- This may have just been fixed in 5.9.0 https://bugs.kde.org/show_bug.cgi?id=391312 -- 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 moreheadst...@gmail.com changed: What|Removed |Added CC||moreheadst...@gmail.com --- Comment #3 from moreheadst...@gmail.com --- I have the exact same issue. Not using Wayland. Nvidia 384.130 binary. Currently using Cinnamon as temp DE, as KDE/Plasma too unstable until this gets fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395763] file:/// as cmake toolchain file on android build
https://bugs.kde.org/show_bug.cgi?id=395763 Kevin Funk changed: What|Removed |Added CC||aleix...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395788] New: If tags have a : in them, rename effectively deletes the file
https://bugs.kde.org/show_bug.cgi?id=395788 Bug ID: 395788 Summary: If tags have a : in them, rename effectively deletes the file Product: digikam Version: 5.8.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: AdvancedRename Assignee: digikam-bugs-n...@kde.org Reporter: vilkm...@gmail.com Target Milestone: --- I tried renaming an image to include the tags. One of the tags has a : in it, which I don't think is a viable character for a filename. The process still ran (no warning), but it ends up creating a 0 byte file named with everything up until the : character, with no file extension. This completely deletes the original image. 1. Create a file "test.jpg" with "Location: Paris" as a tag. 2. Rename the file using "[file] - [meta:Xmp.digiKam.TagsList]" 3. Notice the file becomes "test - Location" with no file extension 4. File is now 0 bytes and the original image is completely lost. -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 22164] gradient pattern fill
https://bugs.kde.org/show_bug.cgi?id=22164 tom.fjallst...@gmail.com changed: What|Removed |Added CC||tom.fjallst...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 365944] KAddressbook crashes on startup with configured CardDav
https://bugs.kde.org/show_bug.cgi?id=365944 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #25 from Filipus Klutiero --- This is not specific to CardDav, nor just about startup crashes. Please retitle accordingly. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395455] Discover buttons install/remove/launch disappear
https://bugs.kde.org/show_bug.cgi?id=395455 --- Comment #5 from Nate Graham --- You can reproduce the bug by reducing the window size so that it shows a two-pane layout, then repeatedly navigate from one app page back to the list, then back to another. Try searching too. FWIW we're testing out a potential fix for the issue: https://phabricator.kde.org/D13663 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384771] Error when move a file from my home dir, to a windows partition
https://bugs.kde.org/show_bug.cgi?id=384771 --- Comment #3 from regis.car...@free.fr --- I precise, I use the dolphin split window : on the left side my linux folder partition, on the right side the win32 partition. After upgrade, when I cut a file from home system in order to paste it in a win32 partition, I have a new message (I translate from french to english) : " access refused to " my file name. And I have 4 buttons below : "try again", "ignore", "ignore always", "cancel" I'm used to click on "ignore", and then dolphin windows crashes closing itself automatically... I don't have a bug report window to copy/paste here. If I reopen my linux folder the file has been deleted, and in my win32 folder the file is present : so in despite of the crash window, the file has been cut/pasted. Note : The contrary cut/paste (from win32 partition to linux folder) works fine. Let me know if you need more information. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395787] New: System Settings app crashed in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=395787 Bug ID: 395787 Summary: System Settings app crashed in VirtualBox Product: systemsettings Version: 5.13.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.1) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.18.0-1-MANJARO x86_64 Distribution: "Netrunner Rolling" -- Information about the crash: - What I was doing when the application crashed: Launched System Settings app in VirtualBox, navigated it's entries on the left side, app crashed Host system is using Wayland -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb99b558840 (LWP 1804))] Thread 8 (Thread 0x7fb9558ef700 (LWP 1845)): #0 0x7fb996b7f934 in read () at /usr/lib/libc.so.6 #1 0x7fb98fe4bed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb98fe05ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fb98fe064c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb98fe068e2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7fb95686d348 in () at /usr/lib/libgio-2.0.so.0 #6 0x7fb98fe2ea2a in () at /usr/lib/libglib-2.0.so.0 #7 0x7fb99246b075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb996b8e53f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fb9560f0700 (LWP 1844)): #0 0x7fb996b7f934 in read () at /usr/lib/libc.so.6 #1 0x7fb98fe4bed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb98fe05ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fb98fe064c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb98fe0663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb98fe06692 in () at /usr/lib/libglib-2.0.so.0 #6 0x7fb98fe2ea2a in () at /usr/lib/libglib-2.0.so.0 #7 0x7fb99246b075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb996b8e53f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fb95700 (LWP 1812)): #0 0x7fb996b7f934 in read () at /usr/lib/libc.so.6 #1 0x7fb98fe4bed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb98fe05ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fb98fe064c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb98fe0663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb9974a0054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb99744b94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fb997294a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fb994f8c9c9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fb99729eb45 in () at /usr/lib/libQt5Core.so.5 #10 0x7fb99246b075 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fb996b8e53f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fb96bfff700 (LWP 1811)): #0 0x7fb996b83ea9 in poll () at /usr/lib/libc.so.6 #1 0x7fb98fe06523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb98fe0663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb9974a0054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb99744b94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb997294a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb994f8c9c9 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fb99729eb45 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb99246b075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fb996b8e53f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fb9720cc700 (LWP 1809)): #0 0x7fb992470ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb977156994 in () at /usr/lib/dri/swrast_dri.so #2 0x7fb9771568d8 in () at /usr/lib/dri/swrast_dri.so #3 0x7fb99246b075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb996b8e53f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb9728cd700 (LWP 1808)): #0 0x7fb992470ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb977156994 in () at /usr/lib/dri/swrast_dri.so #2 0x7fb9771568d8 in () at /usr/lib/dri/swrast_dri.so #3 0x7fb99246b075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb996b8e53f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb97edf0700 (LWP 1807)): #0 0x7fb98fe4d2f4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7fb98fe05cfa in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #2 0x7fb98fe0649c in () at /usr/lib/libglib-2.0.so.0 #3 0x7fb98fe0663e in
[krita] [Bug 395786] New: Crash every time I select the transform tool
https://bugs.kde.org/show_bug.cgi?id=395786 Bug ID: 395786 Summary: Crash every time I select the transform tool Product: krita Version: 4.1.0 beta Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: kib...@gmail.com Target Milestone: --- Hi, Krita crashes imediatly, as soon as I select the transform tool. It happends every time I select it, I tried a few different types of documents, always the same. here are my infos : Krita Version: 4.1.0-beta.2 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17134 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info **OpenGL not initialized** I draw on a 2017 surface pro. (This is my first time doing a bug repport and I'm really not that technically inclined, pretty sure I'm doing it wrong, so sorry about that, trying to learn) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395462] 100% CPU usage (one core) and freezing when entering some sections of System Settings
https://bugs.kde.org/show_bug.cgi?id=395462 --- Comment #4 from magib...@hotmail.com --- Enabling compositing (Shift-Alt-F12) in either OpenGL 2.0 or 3.1 doesn't solve the issue. This is part of the output of glxinfo: > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.4 > server glx extensions: > > client glx vendor string: Mesa Project and SGI > client glx version string: 1.4 > client glx extensions: > GLX version: 1.4 > Extended renderer info (GLX_MESA_query_renderer): > Vendor: Intel Open Source Technology Center (0x8086) > Device: Mesa DRI Intel(R) Pineview M (0xa011) > Version: 18.1.1 > Accelerated: yes > Video memory: 384MB > Unified memory: yes > Preferred profile: compat (0x2) > Max core profile version: 0.0 > Max compat profile version: 1.4 > Max GLES1 profile version: 1.1 > Max GLES[23] profile version: 2.0 > > OpenGL vendor string: Intel Open Source Technology Center > OpenGL renderer string: Mesa DRI Intel(R) Pineview M > OpenGL version string: 2.1 Mesa 18.1.1 > OpenGL shading language version string: 1.20 > > OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.1.1 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395462] 100% CPU usage (one core) and freezing when entering some sections of System Settings
https://bugs.kde.org/show_bug.cgi?id=395462 --- Comment #3 from magib...@hotmail.com --- I have to add that Right Click on Desktop > 'Configure Desktop' has this issue as well, with the difference that it's the plasmashell process that takes 100% of CPU and freezes. I made a backtrace of /usr/bin/systemsettings5 while it's frozen. It looks like a graphics-related issue. I tried to reproduce the issue in another computer with integrated graphics Intel HD Graphics 4000 (i965 driver), but I couldn't. It works well there. > #0 0x7fffd8a97677 in ?? () from /usr/lib/dri/i915_dri.so > #1 0x7fffd8a98041 in ?? () from /usr/lib/dri/i915_dri.so > #2 0x7fffd8a3a18e in ?? () from /usr/lib/dri/i915_dri.so > #3 0x7fffd8a3fa4b in ?? () from /usr/lib/dri/i915_dri.so > #4 0x7fffd8a531fd in ?? () from /usr/lib/dri/i915_dri.so > #5 0x7fffd8a22975 in ?? () from /usr/lib/dri/i915_dri.so > #6 0x7fffd8a23318 in ?? () from /usr/lib/dri/i915_dri.so > #7 0x7fffd8a17f1a in ?? () from /usr/lib/dri/i915_dri.so > #8 0x7fffd877811e in ?? () from /usr/lib/dri/i915_dri.so > #9 0x7fffd8a17507 in ?? () from /usr/lib/dri/i915_dri.so > #10 0x7fffd8a17c89 in ?? () from /usr/lib/dri/i915_dri.so > #11 0x7fffd8b0e609 in ?? () from /usr/lib/dri/i915_dri.so > #12 0x7fffd8b0efef in ?? () from /usr/lib/dri/i915_dri.so > #13 0x71e921d7 in > QSGBatchRenderer::Renderer::renderUnmergedBatch(QSGBatchRenderer::Batch > const*) () from /usr/lib/libQt5Quick.so.5 > #14 0x71e928dc in QSGBatchRenderer::Renderer::renderBatches() () from > /usr/lib/libQt5Quick.so.5 > #15 0x71e98103 in QSGBatchRenderer::Renderer::render() () from > /usr/lib/libQt5Quick.so.5 > #16 0x71e884ee in QSGRenderer::renderScene(QSGBindable const&) () > from /usr/lib/libQt5Quick.so.5 > #17 0x71ec99fb in QSGDefaultLayer::grab() () from > /usr/lib/libQt5Quick.so.5 > #18 0x71ec9fee in QSGDefaultLayer::updateTexture() () from > /usr/lib/libQt5Quick.so.5 > #19 0x7203ec77 in QQuickOpenGLShaderEffectMaterial::updateTextures() > const () from /usr/lib/libQt5Quick.so.5 > #20 0x71e88e02 in QSGRenderer::preprocess() () from > /usr/lib/libQt5Quick.so.5 > #21 0x71e884b9 in QSGRenderer::renderScene(QSGBindable const&) () > from /usr/lib/libQt5Quick.so.5 > #22 0x71e88990 in QSGRenderer::renderScene(unsigned int) () from > /usr/lib/libQt5Quick.so.5 > #23 0x71ec3030 in > QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from > /usr/lib/libQt5Quick.so.5 > #24 0x71f26db5 in QQuickWindowPrivate::renderSceneGraph(QSize const&) > () from /usr/lib/libQt5Quick.so.5 > #25 0x71fe7e8a in QQuickRenderControl::render() () from > /usr/lib/libQt5Quick.so.5 > #26 0x723b1397 in ?? () from /usr/lib/libQt5QuickWidgets.so.5 > #27 0x723b435e in QQuickWidget::resizeEvent(QResizeEvent*) () from > /usr/lib/libQt5QuickWidgets.so.5 > #28 0x74ed5cce in QWidget::event(QEvent*) () from > /usr/lib/libQt5Widgets.so.5 > #29 0x723b5256 in QQuickWidget::event(QEvent*) () from > /usr/lib/libQt5QuickWidgets.so.5 > #30 0x74e95a74 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () from /usr/lib/libQt5Widgets.so.5 > #31 0x74e9d341 in QApplication::notify(QObject*, QEvent*) () from > /usr/lib/libQt5Widgets.so.5 > #32 0x73e91cb9 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) () from /usr/lib/libQt5Core.so.5 > #33 0x74ecda55 in > QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from > /usr/lib/libQt5Widgets.so.5 > #34 0x74ed1af4 in QWidgetPrivate::show_helper() () from > /usr/lib/libQt5Widgets.so.5 > #35 0x74ed4e35 in QWidget::setVisible(bool) () from > /usr/lib/libQt5Widgets.so.5 > #36 0x74ed1aa9 in QWidgetPrivate::showChildren(bool) () from > /usr/lib/libQt5Widgets.so.5 > #37 0x74ed1b12 in QWidgetPrivate::show_helper() () from > /usr/lib/libQt5Widgets.so.5 > #38 0x74ed4e35 in QWidget::setVisible(bool) () from > /usr/lib/libQt5Widgets.so.5 > #39 0x74ed4242 in ?? () from /usr/lib/libQt5Widgets.so.5 > ---Type to continue, or q to quit--- > #40 0x73ebc3d2 in QObject::event(QEvent*) () from > /usr/lib/libQt5Core.so.5 > #41 0x74ed576c in QWidget::event(QEvent*) () from > /usr/lib/libQt5Widgets.so.5 > #42 0x74e95a74 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () from /usr/lib/libQt5Widgets.so.5 > #43 0x74e9d341 in QApplication::notify(QObject*, QEvent*) () from > /usr/lib/libQt5Widgets.so.5 > #44 0x73e91cb9 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) () from /usr/lib/libQt5Core.so.5 > #45 0x73e94d4c in QCoreApplicationPrivate::sendPostedEvents(QObject*, > int, QThreadData*) () from /usr/lib/libQt5Core.so.5 > #46 0x73ee5a54 in ?? () from /usr/lib/libQt5Core.so.5 > #47 0x7fffec84e368 in
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 --- Comment #5 from Benjamin Xiao --- Created attachment 113524 --> https://bugs.kde.org/attachment.cgi?id=113524=edit kwin wayland support info Funny enough, if I run KDE with Wayland, it gets the correct refresh rate from the monitor. I've attached the support info logs for comparison. Screen 0: - Name: ACR DP-1-XB271HU/#ASNFeULjO7/ Geometry: 0,0,2560x1440 Scale: 1 Refresh Rate: 143.998 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395778] Impliment Display Tab Of All Items Connected To USB In Panels Device Notifier
https://bugs.kde.org/show_bug.cgi?id=395778 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist --- Comment #2 from Christoph Feck --- Could you please add more information why this is useful? To view the USB device tree, we have KInfoCenter. -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 395770] No window icon on Wayland
https://bugs.kde.org/show_bug.cgi?id=395770 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kaj ||ongg/25df9d9ae82a2ced4cdd4d ||4bbaeb9458d5f0b5fb --- Comment #1 from Andrius Štikonas --- Git commit 25df9d9ae82a2ced4cdd4d4bbaeb9458d5f0b5fb by Andrius Štikonas. Committed on 23/06/2018 at 11:18. Pushed by stikonas into branch 'master'. Fix application icon under Wayland. M +1-1src/about.py M +4-0src/kajongg.py https://commits.kde.org/kajongg/25df9d9ae82a2ced4cdd4d4bbaeb9458d5f0b5fb -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 386013] Kontact & Akregator crash on startup
https://bugs.kde.org/show_bug.cgi?id=386013 Aristide changed: What|Removed |Added CC||fmet...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 386013] Kontact & Akregator crash on startup
https://bugs.kde.org/show_bug.cgi?id=386013 --- Comment #1 from Aristide --- Created attachment 113523 --> https://bugs.kde.org/attachment.cgi?id=113523=edit New crash information added by DrKonqi korganizer (5.8.40 alpha) using Qt 5.11.0 I have same problem but with Kontact 5.8.40 Alpha. Launch Kmail : Work Launch Korganizer : Crash Launch Akregator : Crash -- Backtrace (Reduced): #7 0x7f38ab55ed3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x004084ce in main (argc=1, argv=0x7ffc447d13d8) at /workspace/build/src/main.cpp:55 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395752] kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 --- Comment #5 from dS810 --- @Stefano: exactly... It's a confirmed bug and I hope it will be fixed next release :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395785] New: Kwin_X11 crash when I open lid
https://bugs.kde.org/show_bug.cgi?id=395785 Bug ID: 395785 Summary: Kwin_X11 crash when I open lid Product: kwin Version: 5.13.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: shake...@gmail.com Target Milestone: --- Application: kwin_x11 (5.13.1) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.2-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Kwin_X11 crash when I open lid. Also the desktop icons text are pixeled. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3010717840 (LWP 509))] Thread 5 (Thread 0x7f2fd7fff700 (LWP 619)): #0 0x7f30090f0ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f300c3b3aac in () at /usr/lib/libQt5Script.so.5 #2 0x7f300c3b3ac9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f30090eb075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f301009953f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f2fedb28700 (LWP 590)): #0 0x7f301008efa6 in ppoll () at /usr/lib/libc.so.6 #1 0x7f300d48ff0b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f300d4913fb in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f300d43f94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f300d288a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f3007b329c9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f300d292b45 in () at /usr/lib/libQt5Core.so.5 #7 0x7f30090eb075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f301009953f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f2fe700 (LWP 584)): #0 0x7f301008efa6 in ppoll () at /usr/lib/libc.so.6 #1 0x7f300d48ff0b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f300d4913fb in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f300d43f94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f300d288a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f3006a24976 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f300d292b45 in () at /usr/lib/libQt5Core.so.5 #7 0x7f30090eb075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f301009953f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f2ff6626700 (LWP 546)): #0 0x7f301008eea9 in poll () at /usr/lib/libc.so.6 #1 0x7f300efb2180 in () at /usr/lib/libxcb.so.1 #2 0x7f300efb3e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f2ff771522a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f300d292b45 in () at /usr/lib/libQt5Core.so.5 #5 0x7f30090eb075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f301009953f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f3010717840 (LWP 509)): [KCrash Handler] #6 0x7f300cc263fb in KWin::WindowQuadList::makeInterleavedArrays(unsigned int, KWin::GLVertex2D*, QMatrix4x4 const&) const () at /usr/lib/libkwineffects.so.11 #7 0x7f2fec6d41f8 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #8 0x7f2fec6dcd73 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #9 0x7f2fec6dceb9 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #10 0x7f300fc20aac in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #11 0x7f300cc2249d in KWin::Effect::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwineffects.so.11 #12 0x7f300fc20a44 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #13 0x7f300c9be7a6 in () at /usr/lib/libkwin4_effect_builtins.so.1 #14 0x7f300fc20a44 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #15 0x7f300c92b57a in () at /usr/lib/libkwin4_effect_builtins.so.1 #16 0x7f300fc20a44 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #17 0x7f300fc0ca2d in KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #18 0x7f300fc208d5 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #19 0x7f300c9aca8f in () at
[plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf?
https://bugs.kde.org/show_bug.cgi?id=386665 --- Comment #12 from Martin Steigerwald --- (In reply to David Rosca from comment #6) > I think we can make the gconf dependency optional until we find a > replacement. Any progress on that? Probably with Pulseaudio 12 if paprefs can use gsettings, plasma-pa can too? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395784] New: Settings app crash
https://bugs.kde.org/show_bug.cgi?id=395784 Bug ID: 395784 Summary: Settings app crash Product: systemsettings Version: 5.13.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vegaso...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.1) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.16.13-2-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: hitting the back button on the app after changing a setting, does this almost everytime dispite the setting I'm changing... 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 0x7fb5c0e6e840 (LWP 4133))] Thread 2 (Thread 0x7fb5a42c8700 (LWP 4162)): #0 0x7fb5b57812d9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fb5b57398b6 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fb5b573a44e in () at /usr/lib/libglib-2.0.so.0 #3 0x7fb5b573a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fb5bcdd1054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb5bcd7c94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb5bcbc5a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fb5bd221976 in () at /usr/lib/libQt5DBus.so.5 #8 0x7fb5bcbcfb45 in () at /usr/lib/libQt5Core.so.5 #9 0x7fb5b7d9c075 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fb5bc4bf53f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fb5c0e6e840 (LWP 4133)): [KCrash Handler] #6 0xab90 in () #7 0x7fb5c0cd310a in call_init.part () at /lib64/ld-linux-x86-64.so.2 #8 0x7fb5c0cd3206 in _dl_init () at /lib64/ld-linux-x86-64.so.2 #9 0x7fb5c0cd7273 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #10 0x7fb5bc4fa94f in _dl_catch_exception () at /usr/lib/libc.so.6 #11 0x7fb5c0cd6b48 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #12 0x7fb5b5a05e66 in () at /usr/lib/libdl.so.2 #13 0x7fb5bc4fa94f in _dl_catch_exception () at /usr/lib/libc.so.6 #14 0x7fb5bc4fa9df in _dl_catch_error () at /usr/lib/libc.so.6 #15 0x7fb5b5a06597 in () at /usr/lib/libdl.so.2 #16 0x7fb5b5a05f06 in dlopen () at /usr/lib/libdl.so.2 #17 0x7fb59702b8f1 in () at /usr/lib/libvlccore.so.9 #18 0x7fb596fa1d8d in () at /usr/lib/libvlccore.so.9 #19 0x7fb596fa1c29 in () at /usr/lib/libvlccore.so.9 #20 0x7fb596fa211d in () at /usr/lib/libvlccore.so.9 #21 0x7fb596fa2728 in () at /usr/lib/libvlccore.so.9 #22 0x7fb596f8a53a in libvlc_InternalInit () at /usr/lib/libvlccore.so.9 #23 0x7fb596d566ac in libvlc_new () at /usr/lib/libvlc.so.5 #24 0x7fb5972c92ea in () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #25 0x7fb59729c10c in () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #26 0x7fb5972cdbfa in qt_plugin_instance () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #27 0x7fb5bcd6827b in QPluginLoader::instance() () at /usr/lib/libQt5Core.so.5 #28 0x7fb5a69128f1 in () at /usr/lib/libphonon4qt5.so.4 #29 0x7fb5a6914514 in () at /usr/lib/libphonon4qt5.so.4 #30 0x7fb5a69149b1 in () at /usr/lib/libphonon4qt5.so.4 #31 0x7fb5a6915364 in Phonon::Factory::backend(bool) () at /usr/lib/libphonon4qt5.so.4 #32 0x7fb5a69158f4 in () at /usr/lib/libphonon4qt5.so.4 #33 0x7fb5a690a9c2 in () at /usr/lib/libphonon4qt5.so.4 #34 0x7fb5a6907def in () at /usr/lib/libphonon4qt5.so.4 #35 0x7fb5a7b0b871 in () at /usr/lib/libKF5Notifications.so.5 #36 0x7fb5a7ae4ca9 in () at /usr/lib/libKF5Notifications.so.5 #37 0x7fb5a7ae1336 in KNotification::sendEvent() () at /usr/lib/libKF5Notifications.so.5 #38 0x7fb5bcda83d2 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #39 0x7fb5bdd81a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #40 0x7fb5bdd89341 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #41 0x7fb5bcd7dcb9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #42 0x7fb5bcd80d4c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #43 0x7fb5bcdd1a54 in () at /usr/lib/libQt5Core.so.5 #44 0x7fb5b573a368 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #45 0x7fb5b573a5b1 in () at /usr/lib/libglib-2.0.so.0 #46 0x7fb5b573a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
[kstars] [Bug 395783] New: Solver process crashed
https://bugs.kde.org/show_bug.cgi?id=395783 Bug ID: 395783 Summary: Solver process crashed Product: kstars Version: 2.9.6 Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jcjes...@free.fr Target Milestone: --- I'm a bit at a loss because I recently get the following error when I try to solve : "Solver failed. Try again Error starting solver: Process crashed" I get this error only on laptop and not on the desktop although I'm using exactly the same KStars configuration on both machines (I copied in fact the whole disk of the desktop to the laptop) The Astrometry folders are identical. I'm using the simulators. What is the origin of this problem ? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 Cristiano Rodrigues changed: What|Removed |Added CC||microc...@aeiou.pt --- Comment #7 from Cristiano Rodrigues --- Hi there! It is just to say that as simple as Kuser may seem it is of great value. Of course we can live without it because we can have the same results using the console but what can be done in 10 seconds with Kuser will take 2 or 3 minutes without it (at least for me, I always have to google for the right commands and arguments for user and groups manipulation) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf?
https://bugs.kde.org/show_bug.cgi?id=386665 --- Comment #11 from Lars Wendler (Polynomial-C) --- Here's a quote from pulseaudio-12.0 release notes (https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/): Notes for packagers The GConf dependency can now be avoided paprefs has so far required module-gconf to be loaded in the PulseAudio daemon, which is bad, because the GConf project is deprecated and unmaintained. paprefs 1.0 is expected to be released shortly, and that will use GSettings instead of GConf. The new paprefs version requires module-gsettings to be loaded in the PulseAudio daemon. PulseAudio still provides module-gconf in case there's need for it. GSettings and GConf can both be enabled when building PulseAudio, but note that both modules should not be installed at the same time, so distributions should make module-gconf conflict with module-gsettings in their packaging system. It may be useful to enable both when building PulseAudio, so that PulseAudio can be updated before paprefs. If only GSettings is enabled, PulseAudio and paprefs need to be updated at the same time. There can be some problems for users after updating paprefs. When module-gsettings is installed along with the new paprefs version, the module won't be automatically loaded by the PulseAudio daemon that is already running during the update, so any configuration changes done with paprefs will have effect only after the daemon has been restarted. Another issue is that if the gsettings-data-convert program is not installed, the old settings from GConf won't be migrated to GSettings. gsettings-data-convert is provided by GConf, so to ensure that the program is installed, the module-gsettings package would have to depend on GConf, but since the whole point of this exercise is to get rid of GConf, such dependency may not be feasible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392447] dolphin shows nothing on smb:// or smb://workgroup/
https://bugs.kde.org/show_bug.cgi?id=392447 Bernd Lachner changed: What|Removed |Added CC||d...@lachner-net.de --- Comment #5 from Bernd Lachner --- I can confirm this behavior with openSUSE Leap 15.0 (Plasma 5.12.5, Frameworks 5.45.0) on the client and Samba 4.6.14 on the server. Dolphin shows nothing with smb:// if I go to the share directly in Dolphin it works. With smbtree the shares are showing correctly. The following file on the client helps, thank you: ~/.smb/smb.conf [global] client max protocol = NT1 But it would be better do solve this issue in the smb kio plugin directly. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend (Sage version 7.6)
https://bugs.kde.org/show_bug.cgi?id=375467 --- Comment #20 from Kishore Gopalakrishnan --- (In reply to Nikita Sirgienko from comment #19) > Now, on master branch, Cantor have patch for sage login for versions 8.1 and > 8.2 (I think the patch also can work with future 8.3 version) > I will want to add this patch in 18.04.3 release, but it will be usefull, if > this patch will be tested before release not only by developers. > Could anybody with Sage 8.1 or 8.2 builds Cantor from source code and > confirm, that login starts work correctly? Cantor built from source works on Arch with sagemath version 8.2. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 395782] New: Problems with background some elements while change themes
https://bugs.kde.org/show_bug.cgi?id=395782 Bug ID: 395782 Summary: Problems with background some elements while change themes Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: warqu...@gmail.com Target Milestone: --- Created attachment 113522 --> https://bugs.kde.org/attachment.cgi?id=113522=edit Archive with screenshots Steps to reproduce: 1) Change themes Actual Results: Some certain elements still have dark background but already have dark text color, or have white text and white background. I see this problem only for this elements and another GUI elements haven't this problem at all, as I see See attachments for examples -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394534] kcminit crash on startup
https://bugs.kde.org/show_bug.cgi?id=394534 Fabian Vogt changed: What|Removed |Added Version Fixed In||5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394534] kcminit crash on startup
https://bugs.kde.org/show_bug.cgi?id=394534 --- Comment #11 from softw...@mike.franken.de --- Created attachment 113521 --> https://bugs.kde.org/attachment.cgi?id=113521=edit New crash information added by DrKonqi kdeinit5 () using Qt 5.11.0 - What I was doing when the application crashed: Logging in via sddm. Happens with all users on this system, even with new created ones. -- Backtrace (Reduced): #6 0x7f21e87e11ea in QMapData::findNode (this=0x4545454545454545, akey=...) at /usr/include/qt5/QtCore/qmap.h:284 #7 0x7f21e87e639b in QMap::constFind (this=0x561798ad0500, akey=...) at /usr/include/qt5/QtCore/qmap.h:874 #8 QMap::find (akey=..., this=0x561798ad0500) at /usr/include/qt5/QtCore/qmap.h:876 #9 KEntryMap::findEntry (this=this@entry=0x561798ad0500, group=..., key=..., flags=...) at /usr/src/debug/kconfig-5.46.0-1.2.x86_64/src/core/kconfigdata.cpp:74 #10 0x7f21e87e64bb in KEntryMap::getEntry (this=this@entry=0x561798ad0500, group=..., key=..., defaultValue=..., flags=..., flags@entry=..., expand=0x7ffd1aba4b27) at /usr/src/debug/kconfig-5.46.0-1.2.x86_64/src/core/kconfigdata.cpp:224 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 395680] Akregator won't start...
https://bugs.kde.org/show_bug.cgi?id=395680 blackfireb...@hotmail.com changed: What|Removed |Added CC||blackfireb...@hotmail.com --- Comment #1 from blackfireb...@hotmail.com --- if you run them from terminal do you get any extra output? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394534] kcminit crash on startup
https://bugs.kde.org/show_bug.cgi?id=394534 softw...@mike.franken.de changed: What|Removed |Added CC||softw...@mike.franken.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395769] Multi-line paragraph transform into single line when edited
https://bugs.kde.org/show_bug.cgi?id=395769 --- Comment #2 from David REVOY --- Thank you @mvowada for finding the exact condition, and the video very well made to demo the bug. -- You are receiving this mail because: You are watching all bug changes.
