[systemsettings] [Bug 488184] When setup multiple displays configs, the 'Primary Display' option does not appear at first
https://bugs.kde.org/show_bug.cgi?id=488184 Bruno changed: What|Removed |Added CC||bol...@outlook.com.br -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488184] New: When setup multiple displays configs, the 'Primary Display' option does not appear at first
https://bugs.kde.org/show_bug.cgi?id=488184 Bug ID: 488184 Summary: When setup multiple displays configs, the 'Primary Display' option does not appear at first Classification: Applications Product: systemsettings Version: 6.0.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bol...@outlook.com.br Target Milestone: --- Created attachment 170244 --> https://bugs.kde.org/attachment.cgi?id=170244=edit Video replicating the issue When setup multiple displays configs, the 'Primary Display' option does not appear at first. I had to apply changes, go out and then on to see the option appear. STEPS TO REPRODUCE 1. With two displays available, the system is connected to only one display. 2. Open the 'Display & Monitor' section in system settings. 3. Enable the second display and click apply. 4. After the changes have been applied, the 'Primary' radio button to select the primary button does appear. 5. After moving out and in to the section, the option then appeared. OBSERVED RESULT The 'Primary' radio button was not visible. EXPECTED RESULT The 'Primary' radio button is visible after the second display is enabled (or after the changes have been applied). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 40 KDE Plasma (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 485691] Ghostwriter crashes on launch
https://bugs.kde.org/show_bug.cgi?id=485691 Bruno Pitrus changed: What|Removed |Added CC||brunopit...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487374] Missing icons
https://bugs.kde.org/show_bug.cgi?id=487374 --- Comment #34 from Bruno Santos --- Hello! I'm using Neon Testing. I used Breeze-Dark forever, but today while working in a very bright environment I had to change to Breeze (light), and all the Breeze icons are missing. I noticed that I had breeze-icons-installed and kf6-breeze-icon-theme, for some reason apt doesn't show any conflict if I have both packages installed... dpkg -L shows that only kf6-breeze-icon-theme has index files for breeze and breeze-dark. But I also only have Breeze Dark listed in System Settings. I think I had mistakenly closed this bug by mistake while trying to subscribe to it, sorry for that. :-\ kf6-breeze-icon-theme is at 6.2.80xneon20240522+p22.04+vstable+git20240522.2037-0 but maybe this is an issue somewhere else? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487374] Missing icons
https://bugs.kde.org/show_bug.cgi?id=487374 Bruno Santos changed: What|Removed |Added Ever confirmed|1 |0 Resolution|FIXED |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487374] Missing icons
https://bugs.kde.org/show_bug.cgi?id=487374 Bruno Santos changed: What|Removed |Added CC||bsan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 487601] New: Deleting an event (stored on nextcloud) in month view crash kalendar
https://bugs.kde.org/show_bug.cgi?id=487601 Bug ID: 487601 Summary: Deleting an event (stored on nextcloud) in month view crash kalendar Classification: Applications Product: korganizer Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: korganizer (6.0.2 (24.02.2)) Qt Version: 5.15.13 Frameworks Version: 5.116.0 Operating System: Linux 6.9.1-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: This is really easy to reproduce, with a remote nextcloud agenda, set kalendar in month view (maybe other view have the same result), select an event then clic delete (keyboard del) as soon as the event is going away the crash is present. This (mis)behavior appear once my plasma setup was moved to qt6/wayland (was working well before with qt5/X11) The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 QScopedPointer >::get() const (this=0x8) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/tools/qscopedpointer.h:110 #5 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/global/qtclasshelpermacros.h:79 #6 QObject::d_func() (this=0x0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.h:107 #7 QObject::deleteLater() (this=0x0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:2456 #8 0x7f4bd45673d5 in Akonadi::IncidenceChangerPrivate::handleInvitationsAfterChange(QSharedPointer const&) (this=this@entry=0x55692b378270, change=...) at /usr/src/debug/akonadi-calendar-24.02.2/src/incidencechanger.cpp:658 #9 0x7f4bd45686f8 in Akonadi::IncidenceChangerPrivate::handleDeleteJobResult(KJob*) (this=0x55692b378270, job=) at /usr/src/debug/akonadi-calendar-24.02.2/src/incidencechanger.cpp:358 #10 0x7f4bd4fd232e in QObject::event(QEvent*) (this=0x55692b378270, e=0x55692bb85bb0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:1446 #11 0x7f4bd61c2f1e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55692b378270, e=0x55692bb85bb0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287 #12 0x7f4bd4f8f060 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55692b378270, event=0x55692bb85bb0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1134 #13 0x7f4bd4f8f099 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1575 #14 0x7f4bd4f8f3c0 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55692aff9960) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1932 #15 0x7f4bd51c2053 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55692b006840) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventdispatcher_glib.cpp:244 #16 0x7f4bd33fa740 in () at /lib64/libglib-2.0.so.0 #17 0x7f4bd33fc388 in () at /lib64/libglib-2.0.so.0 #18 0x7f4bd33fca3c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #19 0x7f4bd51c0b0c in QEventDispatcherGlib::processEvents(QFlags) (this=0x55692af9d350, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventdispatcher_glib.cpp:394 #20 0x7f4bd4f997db in QEventLoop::exec(QFlags) (this=0x7ffefce705e0, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/global/qflags.h:34 #21 0x7f4bd4f92fe6 in QCoreApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/global/qflags.h:74 #22 0x5569128c19d9 in main(int, char**) (argc=, argv=) at /usr/src/debug/korganizer-24.02.2/src/main.cpp:62 [Inferior 1 (process 5044) detached] The reporter indicates this bug may be a duplicate of or related to bug 487484. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 485733] Spectacle fails to save recorded video with error
https://bugs.kde.org/show_bug.cgi?id=485733 --- Comment #8 from bruno --- sorry for the late response, all default here too, and amd gpu here too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486034] clicklockd, a mouse accessibility tool doesn't work correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=486034 --- Comment #4 from Bruno Filipe --- Hey, took a try at fixing this: https://invent.kde.org/plasma/kwin/-/merge_requests/5696 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486034] clicklockd, a mouse accessibility tool doesn't work correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=486034 --- Comment #3 from Bruno Filipe --- Here's some reference for expected multiseat behavior (from https://wayland.freedesktop.org/libinput/doc/latest/seats.html) if the same button is pressed on different devices, the button should only be considered logically pressed once. if the same button is released on one device, the button should be considered logically down if still down on another device. if two different buttons or keys are pressed on different devices, the logical state is that of both buttons/keys down. if a button is pressed on one device and another device moves, this should count as dragging. if two touches are down on different devices, the logical state is that of two touches down. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 485733] Spectacle fails to save recorded video with error
https://bugs.kde.org/show_bug.cgi?id=485733 bruno changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from bruno --- bump -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 486301] New: No reports available
https://bugs.kde.org/show_bug.cgi?id=486301 Bug ID: 486301 Summary: No reports available Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: bgar...@gmail.com Target Milestone: --- Created attachment 169001 --> https://bugs.kde.org/attachment.cgi?id=169001=edit Welcome screen copy I just installed FEDORA 40 Plasma (upgrade from FEDORA 39 Plasma) which brought kmymoney 5.1.3 and i have no more reports (c.f. copy screen). It asks to install a report external module but i found none. It works like a charm before. I have tried with Wayland and X11 renderer but no change. SUMMARY STEPS TO REPRODUCE 1. Install FEDORA 40 Plasma 2. Start kmymoney OBSERVED RESULT No reports icon and no report in the Welcome screen EXPECTED RESULT Reports available SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: FEDORA 40 Plasma 6 (available in About System) KDE Plasma Version: 5.115.0 KDE Frameworks Version: Qt Version: 5.15.13 compiled with 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486106] some applications pinned to taskbar are started inside `plasma-plasmashell.service` instead of their own cgroup
https://bugs.kde.org/show_bug.cgi?id=486106 --- Comment #1 from Bruno Pitrus --- Likely cause: `/usr/bin/code` forks on startup and exits immediately. If i replace the script with `exec xterm`, the xterm gets correctly put into `app-code-BLAHBLAHBLAH.scope`. This suggests that there's a race condition somewhere. This may be related to bug 450810 but i'm not using Latte and don't know what a Latte is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486106] New: some applications pinned to taskbar are started inside `plasma-plasmashell.service` instead of their own cgroup
https://bugs.kde.org/show_bug.cgi?id=486106 Bug ID: 486106 Summary: some applications pinned to taskbar are started inside `plasma-plasmashell.service` instead of their own cgroup Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: brunopit...@hotmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY When vscode (OSS build from the openSUSE repo) is pinned to taskbar, clicking the icon does not result in it being correctly launched in a new cgroup, instead remaining in `plasma-plasmashell.service`. This results in `systemctl --user restart plasma-plasmashell` (to fix a hung/misbehaving plasma) causing VSCode to crash. If VSCode was launched from the start menu or from KRunner, it gets correctly assigned its own cgroup. STEPS TO REPRODUCE 1. Pin `code.desktop` to taskbar 2. Click the pinned icon to launch vscode 3. `systemctl --user restart plasma-plasmashell` OBSERVED RESULT VSCode crashes. EXPECTED RESULT Any apps opened are unaffected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240423 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Content of `/usr/share/applications/code.desktop`: [Desktop Entry] Name=Code - OSS Comment=Code Editing. Redefined. GenericName=Text Editor Exec=code --unity-launch %F Icon=code-oss Type=Application StartupNotify=false StartupWMClass=Code Categories=TextEditor;Development;IDE; MimeType=text/plain;inode/directory;application/x-code-workspace; Actions=new-empty-window; Keywords=vscode; [Desktop Action new-empty-window] Name=New Empty Window Name[de]=Neues leeres Fenster Name[es]=Nueva ventana vacía Name[fr]=Nouvelle fenêtre vide Name[it]=Nuova finestra vuota Name[ja]=新しい空のウィンドウ Name[ko]=새 빈 창 Name[ru]=Новое пустое окно Name[zh_CN]=新建空窗口 Name[zh_TW]=開新空視窗 Exec=code --new-window %F Icon=code-oss -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486034] clicklockd, a mouse accessibility tool doesn't work correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=486034 --- Comment #2 from Bruno Filipe --- (In reply to Zamundaaa from comment #1) > Can confirm. KWin is lacking the key press deduplication logic that's > required for multiple devices on the same seat to cooperate with each other. Hey Zamundaaa, thanks for the quick confirmation. I got a bit of practical evidence on what's happening after playing a bit with libinput debug (sudo libinput debug-events --verbose) , along with clicklockd and also a script using python-evsieve to simulate my scenario. In summary, like you already said, the current issue in kwin Wayland behavior is that when the same key is pressed/released on multiple seats it lacks any logic to avoid repeating events to mess with each other. In my scenario what happens is this: -event4 POINTER_BUTTON +1.541s BTN_LEFT (272) pressed, seat count: 1 # Real mouse BTN_LEFT pressed, from neutral state - Self-explanatory -event15 POINTER_BUTTON +1.541s BTN_LEFT (272) pressed, seat count: 2 # Virtual mouse BTN_LEFT pressed - This click should be ignored since we're already in pressed state on another seat (real mouse), but it is not. It generates a double-click instead. -event4 POINTER_BUTTON +3.125s BTN_LEFT (272) released, seat count: 1 # Real mouse BTN_LEFT released - This one should also be ignored since virtual is still in pressed state, but it is not. event4 POINTER_BUTTON +4.589s BTN_LEFT (272) pressed, seat count: 2 # Real mouse BTN_LEFT pressed again - Also should be ignored since virtual is still in pressed state, but it is not. event4 POINTER_BUTTON +4.677s BTN_LEFT (272) released, seat count: 1 # Real mouse BTN_LEFT released - Also should be ignored since virtual is still in pressed state, but it is not. -event15 POINTER_BUTTON +4.677s BTN_LEFT (272) released, seat count: 0 # Virtual BTN_LEFT released - Now kwin/Plasma should actually release effectively. A bit difficult to explain, but something like this. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 486071] Kontact crashes when furiously showing and hiding remote calendars using mouse
https://bugs.kde.org/show_bug.cgi?id=486071 --- Comment #1 from Bruno Pitrus --- Created attachment 168865 --> https://bugs.kde.org/attachment.cgi?id=168865=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 486071] New: Kontact crashes when furiously showing and hiding remote calendars using mouse
https://bugs.kde.org/show_bug.cgi?id=486071 Bug ID: 486071 Summary: Kontact crashes when furiously showing and hiding remote calendars using mouse Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: brunopit...@hotmail.com Target Milestone: --- Application: kontact (6.0.2 (24.02.2)) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.8.7-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: 1. Add some remote calendars from Google account 2. Switch Kontact to calendar module using left sidebar 3. Rapidly check and unceck checkboxes beside multiple calendars by clicking them The crash can be reproduced every time. -- Backtrace (Reduced): #5 0x7fb6ff5a61a4 in KCalendarCore::OccurrenceIterator::Private::setupIterator (this=this@entry=0x5591e1551700, calendar=..., incidences=...) at /usr/src/debug/kcalendarcore-6.1.0/src/occurrenceiterator.cpp:115 #6 0x7fb6ff5a7e2b in KCalendarCore::OccurrenceIterator::OccurrenceIterator (this=, calendar=..., incidence=..., start=..., end=..., this=, calendar=..., incidence=..., start=..., end=...) at /usr/include/qt6/QtCore/qlist.h:113 #7 0x7fb6d9f37ddc in EventViews::AgendaView::displayIncidence (this=this@entry=0x5591db990cc0, incidence=..., createSelected=createSelected@entry=false) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:274 #8 0x7fb6d9f39c60 in EventViews::AgendaView::fillAgenda (this=0x5591db990cc0) at /usr/src/debug/eventviews-24.02.2/src/agenda/agendaview.cpp:2033 #9 0x7fb748de8443 in QtPrivate::QSlotObjectBase::call (a=0x7ffcec1a0350, r=0x5591dd7a1000, this=0x5591dc6956c0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobjectdefs_impl.h:469 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486034] clicklockd, a mouse accessibility tool doesn't work correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=486034 Bruno Filipe changed: What|Removed |Added CC||bmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486034] New: clicklockd, a mouse accessibility tool doesn't work correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=486034 Bug ID: 486034 Summary: clicklockd, a mouse accessibility tool doesn't work correctly on Wayland Classification: Plasma Product: kwin Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: bmil...@gmail.com Target Milestone: --- SUMMARY Hello, I'm a quadriplegic KDE user and can't migrate to Wayland due to this issue, I appreciate and thank in advance any help even though I realize it's a really niche use-case. Clicklockd is a open source tool that mimics a Windows accessibility feature known as Clicklock. It's the only public tool that does it correctly. As described by it's author, germag: "Clicklockd enables you to highlight or drag without holding down the mouse button. This feature allows you to hold the mouse button for a few seconds, move the mouse to the new location, and then click it again. The effect is the same as a drag and drop but without having to hold the mouse button for a long time." Instead of the expected behavior, clicks doesn't lock at all and single clicks are turned into double clicks. It works fine on Plasma X11 and other Wayland DE's/compositors like GNOME, and only depends on libudev, so the dev believies it's likely something related to how Plasma/kwin Wayland handles inputs. STEPS TO REPRODUCE 1. Build and run clicklockd (https://github.com/germag/clicklockd) OBSERVED RESULT . Clicklock won't work correctly and single clicks become double clicks instead. EXPECTED RESULT When we hold left click for x seconds, specified in argument like "-t 1.5s" passed to clicklockd, that click should be held on until another click comes in. SOFTWARE/OS VERSIONS KDE Plasma 6.0.4 on Arch Linux ADDITIONAL INFORMATION Github issue and discussion with developer: https://github.com/germag/clicklockd/issues/6 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 bruno changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #9 from bruno --- yeah, now it's fine on my end too as of the last update. weird. closing for now! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 485790] New: [Feature Request] add "[current subtitle] to dynamic text
https://bugs.kde.org/show_bug.cgi?id=485790 Bug ID: 485790 Summary: [Feature Request] add "[current subtitle] to dynamic text Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: kde_...@brunodevries.xyz Target Milestone: --- Created attachment 168674 --> https://bugs.kde.org/attachment.cgi?id=168674=edit quick composition how i would envision it to work I hope this is no duplicate, I looked but found nothing. I am coming from the gaming video corner of video editing. Think SovietWomble or any other highlight content creator. They usually have subtitles to humoristically enhance the experience for people with a low attention span. Those subtitles are often color coded and motion tracked to something in the video. Currently we only have TitleClips that are super tedious as soon as you have more than a few lines of text Alternatively a keyframeable title clip text would also work, but i can see how that would create tons of problems. The easiest solutions seems to be a transparent picture with dynamic text on top of any given video that just displays the subtitle text transformed by any motion tracking one wants. Thus leveraging the already existing subtitle engine and interface. This of course would only solve _my_ problems partly as there is only one subtitle track but it _seems_ low effort to integrate and would help me a ton (and probably some other people as well) -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 484620] Spectacle crashes after ending a recording
https://bugs.kde.org/show_bug.cgi?id=484620 --- Comment #5 from bruno --- while this is now fixed, another error still occurs, which i've reported in #485733 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 485733] New: Spectacle fails to save recorded video with error
https://bugs.kde.org/show_bug.cgi?id=485733 Bug ID: 485733 Summary: Spectacle fails to save recorded video with error Classification: Applications Product: Spectacle Version: 24.02.2 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: br...@oikei.net CC: k...@david-redondo.de Target Milestone: --- SUMMARY Spectacle fails to save recorded video with error "Failed to export video: Temporary file URL must be an existing local file" STEPS TO REPRODUCE 1. Open Spectacle 2. Go to the Recording tab 3. Press any of the three recording modes to start the recording 4. Stop the recording after a few seconds OBSERVED RESULT Recording is discarded, not saved to Videos/Screencasts and the error message "Failed to export video: Temporary file URL must be an existing local file" is displayed in a new error popup. EXPECTED RESULT Recording is properly saved to Videos/Screencasts (or whichever path is configured) without any error messages. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Occurs after the crash in #484620 has been fixed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 bruno changed: What|Removed |Added CC||aleix...@kde.org Product|kde |Discover Component|general |discover Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Version|unspecified |6.0.4 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 --- Comment #6 from bruno --- i can see it now (on wayland too)! i was using breeze dark to test. i'm not sure where to move this so i'm gonna give discover a shot and if someone has a better place to move it to (breeze?) feel free to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485626] I see this bug after I sleep my machine.
https://bugs.kde.org/show_bug.cgi?id=485626 bruno changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from bruno --- yeah, i think just answering yes will be enough - DEBUGINFO_URLS looks properly set on your system. no need to close anything, i've reopened this so you can make a new comment with the backtrace here. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 --- Comment #3 from bruno --- same but white as you'd usually expect it to be -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485626] I see this bug after I sleep my machine.
https://bugs.kde.org/show_bug.cgi?id=485626 bruno changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||br...@oikei.net Status|REPORTED|NEEDSINFO --- Comment #1 from bruno --- your backtrace seems to be missing symbols! https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 bruno changed: What|Removed |Added CC||br...@oikei.net --- Comment #1 from bruno --- can't reproduce on latest neon on two separate machines. maybe it's a weird system-specific fault just for you? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485598] New: Linux-image-6.5.0-26-generic and linux-image-6.5.0-9-generic can't be uninstal during update and discover crash
https://bugs.kde.org/show_bug.cgi?id=485598 Bug ID: 485598 Summary: Linux-image-6.5.0-26-generic and linux-image-6.5.0-9-generic can't be uninstal during update and discover crash Classification: Applications Product: Discover Version: 5.27.8 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: bruno.nor...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-25-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Linux-image-6.5.0-26-generic and linux-image-6.5.0-9-generic are not in use. But i can't uninstall, autoremove etc -> error . Discover can't update packages because it want uninstall them -> and crash during process The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7dbe93ed8f18 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7dbe93ed9119 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7dbe940f6985 in QObjectPrivate::ConnectionData::removeConnection(QObjectPrivate::Connection*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7dbe94103b7b in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7dbe70731b64 in ??? () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/kns-backend.so #9 0x7dbe940f976b in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7dbe95b6bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7dbe940cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7dbe940cfeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7dbe941286f7 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7dbe92913b2c in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7dbe9296f46f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7dbe92911d20 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7dbe94127daa in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7dbe940cb15b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7dbe940d3904 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x5e61cca29c0f in ??? () #21 0x7dbe93628150 in __libc_start_call_main (main=main@entry=0x5e61cca29320, argc=argc@entry=3, argv=argv@entry=0x7ffec41dcad8) at ../sysdeps/nptl/libc_start_call_main.h:58 #22 0x7dbe93628209 in __libc_start_main_impl (main=0x5e61cca29320, argc=3, argv=0x7ffec41dcad8, init=, fini=, rtld_fini=, stack_end=0x7ffec41dcac8) at ../csu/libc-start.c:360 #23 0x5e61cca2a5e5 in ??? () [Inferior 1 (process 212026) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 483021] No fallback font
https://bugs.kde.org/show_bug.cgi?id=483021 Bruno Massa changed: What|Removed |Added CC||brma...@gmail.com --- Comment #3 from Bruno Massa --- I confirm this behavior. No emoji is shown in the app. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485148] vfmadd213ss instruction is instrumented incorrectly (the remaining part of the register is cleared instead of kept unmodified)
https://bugs.kde.org/show_bug.cgi?id=485148 --- Comment #13 from Bruno Lathuilière --- I added in verrou ( branch bl/fmaAvxSse_llo ) test cases for fma low lane only (float and double) with SSE and AVX registers (Thanks the Petr remark). For AVX, I was not able to write it with intrinsics so I use asm. If someone know how to do it, it could be slightly cleaner. I test only the 213 version. With these tests, I get failures without patch and with my patch. The patch of Paul Floyd works well. The bad news is my test cases can not be integrated directly in "none" test as I do not have the same test infrastructure. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485148] vfmadd213ss instruction is instrumented incorrectly (the remaining part of the register is cleared instead of kept unmodified)
https://bugs.kde.org/show_bug.cgi?id=485148 Bruno Lathuilière changed: What|Removed |Added CC||bruno.lathuili...@edf.fr --- Comment #9 from Bruno Lathuilière --- Created attachment 168346 --> https://bugs.kde.org/attachment.cgi?id=168346=edit Patch which remove the high lane explicitly to zero. It should solve the problem. I hope there are no bad side effects. As I did not see this bug with verrou, it mean I have to modify the verrou test suite. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482484] Themes symlinked to other themes are shown twice in the KCM
https://bugs.kde.org/show_bug.cgi?id=482484 --- Comment #10 from bruno --- bump! any update on this? -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484970] New Follower Notification Shows i18N_ARGUMENT_MISSING error
https://bugs.kde.org/show_bug.cgi?id=484970 --- Comment #1 from Bruno Rocha --- Created attachment 168094 --> https://bugs.kde.org/attachment.cgi?id=168094=edit Follow tab -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484970] New: New Follower Notification Shows i18N_ARGUMENT_MISSING error
https://bugs.kde.org/show_bug.cgi?id=484970 Bug ID: 484970 Summary: New Follower Notification Shows i18N_ARGUMENT_MISSING error Classification: Applications Product: Tokodon Version: 24.02.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rochacbr...@gmail.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- Created attachment 168093 --> https://bugs.kde.org/attachment.cgi?id=168093=edit General Notifications SUMMARY When I have a new follower, instead of new follower information it is showing %1(I18N_ARGUMENT_MISSING) followed you STEPS TO REPRODUCE 1. Check notifications under Notifications menu OBSERVED RESULT New follower shows as @undefined EXPECTED RESULT I expected to see the summary of the new follower on the card SOFTWARE/OS VERSIONS Linux/KDE Plasma: Endeavour OS / Wayland (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: Qt 6.6.2 ADDITIONAL INFORMATION It happens only at the general notifications, if I click on `follows` tab it works. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484877] DEBUGINFOD_URLS environment variable is incorrectly set
https://bugs.kde.org/show_bug.cgi?id=484877 --- Comment #3 from bruno --- thank you! :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484877] DEBUGINFOD_URLS environment variable is incorrectly set
https://bugs.kde.org/show_bug.cgi?id=484877 bruno changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from bruno --- i found the offending file: https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/usr/lib/environment.d/90-neon-debuginfod.conf?ref_type=heads but i'm not sure how to go on about it, because i don't think these environment .conf files work like traditional scripts, so there's no way to check if $DEBUGINFOD_URLS is empty before adding the URL and colon behind it. could someone please share their thoughts? maybe it would be better if it could be moved to /etc/profile.d or something similar -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484877] New: DEBUGINFOD_URLS environment variable is incorrectly set
https://bugs.kde.org/show_bug.cgi?id=484877 Bug ID: 484877 Summary: DEBUGINFOD_URLS environment variable is incorrectly set Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: br...@oikei.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY DEBUGINFOD_URLS environment variable is incorrectly set. STEPS TO REPRODUCE 1. Fire up a new shell 2. Run "echo $DEBUGINFOD_URLS" OBSERVED RESULT The output is "https://debuginfod.neon.kde.org/:;. Note the colon (:) at the end, usually used as a separator for multiple URLs but wrong in this case where we only have a single URL. Since it's at the end of the string, it's interpreted as a part of the URL and makes all debuginfod downloads broken since it tries to fetch them all from https://debuginfod.neon.kde.org/:/ instead of just https://debuginfod.neon.kde.org/ . EXPECTED RESULT The output is "https://debuginfod.neon.kde.org/; Note the lack of colon (:) at the end. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0.3 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION / -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484560] Dual monitor setup, unable to extend to the right throught the panel applet ends in crash
https://bugs.kde.org/show_bug.cgi?id=484560 --- Comment #3 from Bruno Santos --- I was able to start using Wayland since finding I was missing the package libnvidia-egl-wayland1, and in Wayland this crash and issue isn't present. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 480546] Backup status applet is completly empty and always shown even though showing is set to show when relevant
https://bugs.kde.org/show_bug.cgi?id=480546 --- Comment #3 from Bruno Santos --- I also have an empty applet. Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: Wayland I tried to use the latest applet files from https://invent.kde.org/system/kup but it had the same issue. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 475128] akregator / kmail : can't restore / reduce to tray
https://bugs.kde.org/show_bug.cgi?id=475128 Bruno P. changed: What|Removed |Added CC||peterm...@ymail.com --- Comment #5 from Bruno P. --- *** Bug 484232 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484232] Kmail/Kontact will not open with click on systray symbol
https://bugs.kde.org/show_bug.cgi?id=484232 Bruno P. changed: What|Removed |Added CC||bruno+...@patri.fr Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Bruno P. --- *** This bug has been marked as a duplicate of bug 475128 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 475128] akregator / kmail : can't restore / reduce to tray
https://bugs.kde.org/show_bug.cgi?id=475128 Bruno P. changed: What|Removed |Added CC||philippe.roub...@free.fr --- Comment #4 from Bruno P. --- *** Bug 483656 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483656] icon in kde systray, no effect
https://bugs.kde.org/show_bug.cgi?id=483656 --- Comment #7 from Bruno P. --- *** This bug has been marked as a duplicate of bug 475128 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484232] Kmail/Kontact will not open with click on systray symbol
https://bugs.kde.org/show_bug.cgi?id=484232 Bruno P. changed: What|Removed |Added CC||philippe.roub...@free.fr --- Comment #3 from Bruno P. --- *** Bug 483656 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483656] icon in kde systray, no effect
https://bugs.kde.org/show_bug.cgi?id=483656 Bruno P. changed: What|Removed |Added CC||bruno+...@patri.fr Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Bruno P. --- *** This bug has been marked as a duplicate of bug 484232 *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482015] Kup system tray icon and settings module missing on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482015 Bruno Santos changed: What|Removed |Added CC||er...@armbruster-online.de --- Comment #12 from Bruno Santos --- *** Bug 480546 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 480546] Backup status applet is completly empty and always shown even though showing is set to show when relevant
https://bugs.kde.org/show_bug.cgi?id=480546 Bruno Santos changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||bsan...@gmail.com --- Comment #2 from Bruno Santos --- *** This bug has been marked as a duplicate of bug 482015 *** -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 484620] Spectacle crashes after ending a recording
https://bugs.kde.org/show_bug.cgi?id=484620 --- Comment #1 from bruno --- this seems to happen because of a null pointer dereference here https://invent.kde.org/plasma/kpipewire/-/blob/master/src/pipewirerecord.cpp?ref_type=heads#L195 so i moved it to kpipewire instead -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 484620] Spectacle crashes after ending a recording
https://bugs.kde.org/show_bug.cgi?id=484620 bruno changed: What|Removed |Added Assignee|noaha...@gmail.com |plasma-b...@kde.org Product|Spectacle |KPipeWire Version|24.02.1 |unspecified Component|General |general CC||aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 484620] New: Spectacle crashes after ending a recording
https://bugs.kde.org/show_bug.cgi?id=484620 Bug ID: 484620 Summary: Spectacle crashes after ending a recording Classification: Applications Product: Spectacle Version: 24.02.1 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: br...@oikei.net CC: k...@david-redondo.de Target Milestone: --- SUMMARY Spectacle crashes after ending a recording. STEPS TO REPRODUCE 1. Open Spectacle 2. Go to the Recording tab 3. Click on one of "Rectangular Region", "Full Screen", "Window" 4. Select the recording area to start the recording 5. After a few seconds, press the red circle in the system tray to end the recording OBSERVED RESULT Recording properly ends and is saved to the user's Videos/Screencasts directory. EXPECTED RESULT Spectacle segfaults. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0.3 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION The crash can be reproduced every time. DrKonqi doesn't pop up after the crash, so the backtrace was gathered using gdb. Thread 172 "PipeWireProduce" received signal SIGSEGV, Segmentation fault. PipeWireRecordProduce::cleanup (this=0x5622be40) at ./src/pipewirerecord.cpp:199 (gdb) backtrace #0 PipeWireRecordProduce::cleanup (this=0x5622be40) at ./src/pipewirerecord.cpp:199 #1 0x77e2948d in PipeWireProduce::deactivate (this=0x5622be40) at ./src/pipewireproduce.cpp:134 #2 PipeWireProduce::deactivate (this=0x5622be40) at ./src/pipewireproduce.cpp:129 #3 0x74dcc9b2 in QObject::event (this=0x5622be40, e=0x55efd9c0) at ./src/corelib/kernel/qobject.cpp:1437 #4 0x76df181b in QApplicationPrivate::notify_helper (this=, receiver=0x5622be40, e=0x55efd9c0) at ./src/widgets/kernel/qapplication.cpp:3296 #5 0x74e75e08 in QCoreApplication::notifyInternal2 (receiver=0x5622be40, event=event@entry=0x55efd9c0) at ./src/corelib/kernel/qcoreapplication.cpp:1121 #6 0x74e75e4d in QCoreApplication::sendEvent (receiver=, event=event@entry=0x55efd9c0) at ./src/corelib/kernel/qcoreapplication.cpp:1539 #7 0x74e76000 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55e89c50) at ./src/corelib/kernel/qcoreapplication.cpp:1901 #8 0x74c584f7 in postEventSourceDispatch (s=0x7fff2c003600) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:243 #9 0x7231bd3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x72371258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x723193e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x74c55c30 in QEventDispatcherGlib::processEvents (this=0x7fff2c005220, flags=...) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:393 #13 0x74e7fceb in QEventLoop::exec (this=0x7fff3bffe0a0, flags=...) at ./src/corelib/global/qflags.h:34 #14 0x74d98388 in QThread::exec (this=) at ./src/corelib/global/qflags.h:74 #15 0x74d5ce7d in operator() (__closure=) at ./src/corelib/thread/qthread_unix.cpp:324 #16 (anonymous namespace)::terminate_on_exception > (t=...) at ./src/corelib/thread/qthread_unix.cpp:260 #17 QThreadPrivate::start (arg=0x5613bce0) at ./src/corelib/thread/qthread_unix.cpp:283 #18 0x74294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #19 0x74326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484560] Dual monitor setup, unable to extend to the right throught the panel applet ends in crash
https://bugs.kde.org/show_bug.cgi?id=484560 --- Comment #2 from Bruno Santos --- Created attachment 167823 --> https://bugs.kde.org/attachment.cgi?id=167823=edit Clip showing the applet not extending to the right when only the laptop screen is active -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484560] Dual monitor setup, unable to extend to the right throught the panel applet ends in crash
https://bugs.kde.org/show_bug.cgi?id=484560 --- Comment #1 from Bruno Santos --- Created attachment 167822 --> https://bugs.kde.org/attachment.cgi?id=167822=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484560] New: Dual monitor setup, unable to extend to the right throught the panel applet ends in crash
https://bugs.kde.org/show_bug.cgi?id=484560 Bug ID: 484560 Summary: Dual monitor setup, unable to extend to the right throught the panel applet ends in crash Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: bsan...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.0.2) Qt Version: 6.6.2 Frameworks Version: 6.1.0 Operating System: Linux 6.5.0-27-generic x86_64 Windowing System: X11 Distribution: KDE neon Testing Edition DrKonqi: 6.0.2 [CoredumpBackend] -- Information about the crash: While trying to extend the desktop to the right using the panel applet, nothing happens. If I unify the display output, I'm then able to extend to the right. If I change the order of the displays, or revert to using only the laptop screen I end up getting a crash. The crash can be reproduced every time. -- Backtrace (Reduced): #6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=126595372810176) at ./nptl/pthread_kill.c:44 #7 __pthread_kill_internal (signo=6, threadid=126595372810176) at ./nptl/pthread_kill.c:78 #8 __GI___pthread_kill (threadid=126595372810176, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #9 0x73234c442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #10 0x73234c4287f3 in __GI_abort () at ./stdlib/abort.c:79 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #8 from Bruno Lathuilière --- The merge between the two last version is done: https://raw.githubusercontent.com/edf-hpc/verrou/bl/test_merge_fma/valgrind.fma_amd64.diff -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #7 from Bruno Lathuilière --- Sorry I did'nt finish my message (bad keyboard shorkey ...) I think we will need new IR to take into account vectorized fma : Iop_MAdd_F64x2, Iop_MAdd_F64x4, Iop_MAdd_F32x4, Iop_MAdd_F32x8, Iop_MSub_F64x2, Iop_MSub_F64x4, Iop_MSub_F32x4, Iop_MSub_F32x8 But this is outside the scope of this patch. > > This will need a regression test as well. For the proposed patch, we do not need new tests as we modify only the backend. The test fma.c and fma4.c provides already a good coverage. Do you see something missing? In term of tests, it could be interesting to test the patches on various amd64 architecture. Do you have continuous integration with several architectures? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #6 from Bruno Lathuilière --- (In reply to Paul Floyd from comment #5) > Should we also support F16? No, there are no Iop_MAddF16 or IopMSubF16. And to my knowledge AVX512 is the only way to generate half floating-point operations. And AVX512 is not yet supported by valgrind. > Does this also work with the other permutations 132 and 231? The patch concern only the backend so we can choose the permutation. The frontend has to treat correctly all the permutations, this already tested by none/tests/fma.c. > Lastly, do packed and scalar make any difference? In the amd64 frontend the vectorized fma are unvectorized. So in the backend we do not have to treat packed version of fma. I think it would be nice to introduce new IOp in VEX : Iop_MAdd_F64x2 > This will need a regression test as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 484142] regression: ???? (calculator) key can no longer be assigned as global shortcut
https://bugs.kde.org/show_bug.cgi?id=484142 Bruno Pitrus changed: What|Removed |Added Summary|regression: |regression: |(calculator) key can no |(calculator) key can no |longer be assigned as |longer be assigned as |global shortcut |global shortcut -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 484142] New: regression: ???? (calculator) key can no longer be assigned as global shortcut
https://bugs.kde.org/show_bug.cgi?id=484142 Bug ID: 484142 Summary: regression: (calculator) key can no longer be assigned as global shortcut Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 6.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: brunopit...@hotmail.com Target Milestone: --- Since upgrading to Plasma 6, the “” key can no longer be assigned to anything in systemsettings. In addition, the existing keybinding (displayed in the ui as “Run (1)” [translated from Polish]) which i set to open Yakuake no longer does anything. According to the program `xev`, the offending key is “keycode 148 (keysym 0x1008ff1d, XF86Calculator)” SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240319 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 kglobalacceld version: 6.0.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Bruno Cornec changed: What|Removed |Added CC||br...@victoria.frmug.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #4 from Bruno Lathuilière --- I was able to test my patch https://github.com/edf-hpc/verrou/blob/master/valgrind.fma_amd64.diff with fma4 hardware : it works. I also improve the patch of "notasas" to take into account double precision (cf attachment) and it is faster than the previous patch. It should not be difficult to merge both: if we have a chance to integrate it, I can do it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #3 from Bruno Lathuilière --- Created attachment 167413 --> https://bugs.kde.org/attachment.cgi?id=167413=edit Improve the previous patch to take into account double. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483867] bigtiff no thumbnail created
https://bugs.kde.org/show_bug.cgi?id=483867 Bruno Gonçalves changed: What|Removed |Added CC||bigbr...@gmail.com --- Comment #1 from Bruno Gonçalves --- Today I also tested on BigLinux Unstable, Manjaro Testing and KDE Neon Stable, none of them have thumbnails of image files that are not 8 bit Error with Png 16 bit, Avif 10 and 12 bit, webp in general is not generating thumbnail either. The error is not limited to dolphin, it is also not working on the plasma wallpaper selection screen, my wallpapers are in tiff 10bit, only a blank screen appears, if you click it changes the wallpaper on the plasma and it works normally, just the selection screen which should use the same thumbnail system as dolphin, I suspect the problem is with the kio extras. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483251] New: “open separate terminal here” (Shift+F4 does not work
https://bugs.kde.org/show_bug.cgi?id=483251 Bug ID: 483251 Summary: “open separate terminal here” (Shift+F4 does not work Classification: Applications Product: dolphin Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: brunopit...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The “open separate terminal window here” option in Tools menu does no longer work in Dolphin 6. STEPS TO REPRODUCE 1. Run `dolphin` from a terminal (needed to see console output) 2. In the Dolphin windows, select Tools > Open separate terminal windows here OBSERVED RESULT Dolphin prints the following to stdout: ``` Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. qt.qpa.xcb: could not connect to display qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: minimal, wayland, eglfs, xcb, linuxfb, minimalegl, vkkhrdisplay, wayland-egl, offscreen, vnc. ``` EXPECTED RESULT A new window of Konsole opens SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240309 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 dolphin version: 24.02.0 konsole version: 24.02.0 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 482440] Systray not showing/hiding mail window on click
https://bugs.kde.org/show_bug.cgi?id=482440 Bruno P. changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bruno+...@patri.fr Resolution|--- |DUPLICATE --- Comment #1 from Bruno P. --- *** This bug has been marked as a duplicate of bug 475128 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 475128] akregator / kmail : can't restore / reduce to tray
https://bugs.kde.org/show_bug.cgi?id=475128 Bruno P. changed: What|Removed |Added CC||he...@rangun.de --- Comment #3 from Bruno P. --- *** Bug 482440 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 482440] Systray not showing/hiding mail window on click
https://bugs.kde.org/show_bug.cgi?id=482440 Bruno P. changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=475128 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 475128] akregator / kmail : can't restore / reduce to tray
https://bugs.kde.org/show_bug.cgi?id=475128 Bruno P. changed: What|Removed |Added CC||bruno+...@patri.fr See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482440 --- Comment #2 from Bruno P. --- Same behavior with kmail/kontact using KDE Neon User edition. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482484] Themes symlinked to other themes are shown twice in the KCM
https://bugs.kde.org/show_bug.cgi?id=482484 --- Comment #9 from bruno --- https://invent.kde.org/plasma/sddm-kcm/-/merge_requests/66 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482484] Themes symlinked to other themes are shown twice in the KCM
https://bugs.kde.org/show_bug.cgi?id=482484 --- Comment #7 from bruno --- (the (probably better?) alternative is to resolve all symlink paths and remove duplicate paths from the list) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482484] Themes symlinked to other themes are shown twice in the KCM
https://bugs.kde.org/show_bug.cgi?id=482484 --- Comment #6 from bruno --- if we want to go this route, QDir::NoSymlinks can be added to https://invent.kde.org/plasma/sddm-kcm/-/blob/master/src/themesmodel.cpp?ref_type=heads#L146 if that sounds OK, i can open a MR? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482763] New: GTK theme isn't set to Breeze after fresh install
https://bugs.kde.org/show_bug.cgi?id=482763 Bug ID: 482763 Summary: GTK theme isn't set to Breeze after fresh install Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: br...@oikei.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY GTK theme isn't set to Breeze after fresh install. STEPS TO REPRODUCE 1. Install latest User/Testing/Unstable Neon in a VM 2. Open System Settings after installation 3. Navigate to Colors & Themes > Application Style > Configure GNOME/GTK Application Style... OBSERVED RESULT The GTK Theme combo box contains an invalid empty theme that that appears to look like Adwaita and must be manually changed to Breeze in order to make apps such as Firefox fit into the rest of the desktop. EXPECTED RESULT The GTK Theme combo box already contains the default Breeze theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Same happens on the User (and although I haven't checked there, probably also Testing) Edition. Not sure if this is exactly Neon specific, I can't test on other systems right now, but if it can be reproduced elsewhere, maybe this bug should be moved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482732] New: Creating a new file on the Desktop shows a dialog with "plasmashell" title
https://bugs.kde.org/show_bug.cgi?id=482732 Bug ID: 482732 Summary: Creating a new file on the Desktop shows a dialog with "plasmashell" title Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: br...@oikei.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Creating a new file on the Desktop shows a dialog with "plasmashell" title. STEPS TO REPRODUCE 1. Right click on the Desktop 2. Navigate to Create New > Text File... OBSERVED RESULT Dialog asking for the file name has a nice user-friendly title, consistent to that of the dialog that pops up when "Folder..." is clicked in the submenu instead (having the title "New Folder"). EXPECTED RESULT Dialog's title isn't set, resulting in "plasmashell" being shown. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION / -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482584] Taskbar icons going to the far left side of the panel when hovering the mouse pointer over them
https://bugs.kde.org/show_bug.cgi?id=482584 --- Comment #1 from Bruno Magalhães --- Fixed the issue, it was due an env that i had on /etc/environment. QT_QUICK_BACKEND=software Removing this env fixed the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482584] Taskbar icons going to the far left side of the panel when hovering the mouse pointer over them
https://bugs.kde.org/show_bug.cgi?id=482584 Bruno Magalhães changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482584] New: Taskbar icons going to the far left side of the panel when hovering the mouse pointer over them
https://bugs.kde.org/show_bug.cgi?id=482584 Bug ID: 482584 Summary: Taskbar icons going to the far left side of the panel when hovering the mouse pointer over them Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: bru...@tuta.io CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 166509 --> https://bugs.kde.org/attachment.cgi?id=166509=edit Icons on the far left of the default panel SUMMARY When hovering the mouse pointer over any icon of the default panel, each icon moves to the far left side of the panel. This bugs happens on X11 and Wayland. STEPS TO REPRODUCE 1. Hover the mouse over any icon on the default panel. OBSERVED RESULT Default panel icons going to the far left when hovering the mouse pointer over them. EXPECTED RESULT Icons should stay on their position when hovering the mouse pointer over them. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I tried deleting all config files, deleting plasma itself and create a new user account, nothing seems to work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482484] Maya theme is listed twice in SDDM KCM on Neon
https://bugs.kde.org/show_bug.cgi?id=482484 --- Comment #2 from bruno --- (In reply to Nicolas Fella from comment #1) > What's the output of running "ls /usr/share/sddm/themes" and "ls > .local/share/sddm/themes"? seems normal here.. bruno@arc:~$ ls -lha /usr/share/sddm/themes total 16K drwxr-xr-x 4 root root 4,0K ožu 4 22:11 . drwxr-xr-x 7 root root 4,0K ožu 4 22:11 .. drwxr-xr-x 3 root root 4,0K ožu 5 18:59 breeze lrwxrwxrwx 1 root root 35 ožu 4 22:11 debian-theme -> /etc/alternatives/sddm-debian-theme drwxr-xr-x 6 root root 4,0K ožu 4 22:11 maya the other directory under .local doesn't exist on the system. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482015] Kup system tray icon and settings module missing on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482015 --- Comment #7 from bruno --- (In reply to Nicolas Fella from comment #6) > The reason it's missing is that it's not built against Qt6 in the released > version. > > master (optionally) builds against Qt6, but I don't know if it's in a good > enough state to be released so the last 0.9.1 is still against qt5? if you'd like, i can test a build from master of kup and let you know of any possible issues, though you probably know better than me. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482486] Backups section completely missing in System Settings as of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482486 --- Comment #2 from bruno --- didn't catch that report, thanks, sorry for the duplicate... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482486] New: Backups section completely missing in System Settings as of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482486 Bug ID: 482486 Summary: Backups section completely missing in System Settings as of Plasma 6 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: br...@oikei.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Backups section completely missing in System Settings as of Plasma 6. STEPS TO REPRODUCE 1. Open System Settings OBSERVED RESULT On the left hand side, the "Backups" section is missing. EXPECTED RESULT On the left hand side, there is a "Backups" section which displays the Kup KCM when clicked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.2.2 ADDITIONAL INFORMATION Possibly a packaging issue with the "kup-backup" package which didn't seem to be installed, though installing it didn't resolve the problem. This isn't an issue on an older installation updated from Plasma 5 to 6, but is an issue in a fresh install of Neon in a VM. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482484] New: Maya theme is listed twice in SDDM KCM on Neon
https://bugs.kde.org/show_bug.cgi?id=482484 Bug ID: 482484 Summary: Maya theme is listed twice in SDDM KCM on Neon Classification: Applications Product: systemsettings Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: br...@oikei.net CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- Created attachment 166433 --> https://bugs.kde.org/attachment.cgi?id=166433=edit An image showing the maya SDDM theme listed twice in System Settings. SUMMARY Maya theme is listed twice in SDDM KCM on Neon. STEPS TO REPRODUCE 1. After a fresh install, open System Settings 2. Navigate to Colors and Themes > Login Screen (SDDM) OBSERVED RESULT Available SDDM themes are listed correctly. EXPECTED RESULT The same maya SDDM theme is listed twice. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION An image is attached. -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 367650] ~/.fonts deprecation ; please install new fonts to $XDG_DATA_HOME/fonts ; ~/.local/share/fonts
https://bugs.kde.org/show_bug.cgi?id=367650 Bruno P. changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=480556 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 480556] Yakuake Flatpak doesn't see/can't use user-installed fonts
https://bugs.kde.org/show_bug.cgi?id=480556 Bruno P. changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=367650 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481667] Sometimes Shift doesn't work.
https://bugs.kde.org/show_bug.cgi?id=481667 bruno changed: What|Removed |Added Status|REPORTED|RESOLVED CC||br...@oikei.net Resolution|--- |WORKSFORME --- Comment #3 from bruno --- cannot reproduce on stable kde neon. perhaps an arch issue and/or your system configuration? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481972] File picker closes when scrolling
https://bugs.kde.org/show_bug.cgi?id=481972 --- Comment #10 from bruno --- confirmed fixed in neon :D -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482146] The bottom status bar incorrectly shows size as 0 bytes in trash
https://bugs.kde.org/show_bug.cgi?id=482146 --- Comment #1 from bruno --- Created attachment 166251 --> https://bugs.kde.org/attachment.cgi?id=166251=edit Image of the correct size displayed in trash when only a few files are manually selected. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482146] New: The bottom status bar incorrectly shows size as 0 bytes in trash
https://bugs.kde.org/show_bug.cgi?id=482146 Bug ID: 482146 Summary: The bottom status bar incorrectly shows size as 0 bytes in trash Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: bars: status Assignee: dolphin-bugs-n...@kde.org Reporter: br...@oikei.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 166250 --> https://bugs.kde.org/attachment.cgi?id=166250=edit Image of the incorrect size displayed in trash. SUMMARY STEPS TO REPRODUCE 1. Open Dolphin 2. Click on Trash under Places OBSERVED RESULT The bottom status bar always shows the size of the files in trash as 0 bytes. EXPECTED RESULT The bottom status bar accurately shows the size of the files in trash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION When items are manually selected, the size is calculated fine. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 bruno changed: What|Removed |Added CC||techxga...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 bruno changed: What|Removed |Added CC||br...@oikei.net --- Comment #8 from bruno --- related to https://bugs.kde.org/show_bug.cgi?id=481972 can reproduce -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481972] File picker closes when scrolling
https://bugs.kde.org/show_bug.cgi?id=481972 bruno changed: What|Removed |Added CC||br...@oikei.net --- Comment #7 from bruno --- can reproduce on stable kde neon and wayland, pretty annoying! doesn't happen when scrollbar is used -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481721] kwin_x11 compositor screen freeze (regression from kwin 5)
https://bugs.kde.org/show_bug.cgi?id=481721 --- Comment #5 from Bruno Pitrus --- (In reply to Vlad Zahorodnii from comment #4) > Does this happen on wayland session? the wayland session does not start for me at all. This is a hybrid Intel/Nvidia laptop fwiw so i'm not really interested in wayland at the moment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481715] plasma-kcminit-phase1.service crashes on startup
https://bugs.kde.org/show_bug.cgi?id=481715 --- Comment #4 from Bruno Pitrus --- (In reply to Harald Sitter from comment #3) > You'll have to check the command, not the unit, the unit just dbus invokes > the command that falls on the nose. > > something like > > journalctl --user _COMM=kcminit -b 0 Then the only entry is lut 23 16:28:57 bruno-beit kcminit[80522]: Initializing "/usr/lib64/qt6/plugins/plasma/kcms/systemsettings/kcm_mouse.so" repeated multiple times -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481721] kwin_x11 compositor screen freeze (regression from kwin 5)
https://bugs.kde.org/show_bug.cgi?id=481721 --- Comment #2 from Bruno Pitrus --- Informacje o wsparciu dla KWin: Pytając na np. https://discuss.kde.org użyj wyświetlanych tu danych. Dostarczają one informacji o obecnie uruchomionym wystąpieniu, o opcjach, które są używane, o używanym sterowniku OpenGL i o włączonych efektach. Proszę wysłać te informacje, pod tekstem wprowadzenia, przy użyciu usługi paste bin takiej jak https://paste.kde.org, aby nie zaśmiecać wątku. == Version === KWin version: 5.93.0 Qt Version: 6.6.2 Qt compile version: 6.6.2 XCB compile version: 1.16 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12101011 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.oxygen Theme: Plugin recommends border size: No onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 12 font: Trebuchet MS,12,-1,5,600,0,0,0,0,0,0,0,0,0,0,1,Semibold smallSpacing: 3 largeSpacing: 12 Output backend == Name: KWin::X11StandaloneBackend Cursor == themeName: DMZ-White themeSize: 32 Options === focusPolicy: ClickToFocus xwaylandCrashPolicy: 1 xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: 5 activationDesktopPolicy: SwitchToOtherDesktop focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: MouseRaise commandActiveTitlebar2: MouseNothing commandActiveTitlebar3: MouseOperationsMenu commandInactiveTitlebar1: MouseActivateAndRaise commandInactiveTitlebar2: MouseActivate commandInactiveTitlebar3: MouseOperationsMenu commandWindow1: MouseActivateRaiseAndPassClick commandWindow2: MouseActivateAndPassClick commandWindow3: MouseActivateAndPassClick commandWindowWheel: MouseNothing commandAll1: MouseUnrestrictedMove commandAll2: MouseToggleRaiseAndLower commandAll3: MouseUnrestrictedResize keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 2 glStrictBinding: true glStrictBindingFollowsDriver: true glPreferBufferSwap: AutoSwapStrategy glPlatformInterface: 1 windowsBlockCompositing: true allowTearing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 75 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Active screen follows mouse: yes Number of Screens: 3 Screen 0: - Name: DP3 Enabled: 1 Geometry: 1920,958,3840x2160 Scale: 1 Refresh Rate: 6 Adaptive Sync: incapable Screen 1: - Name: eDP1 Enabled: 1 Geometry: 0,2474,1920x1080 Scale: 1 Refresh Rate: 59998 Adaptive Sync: incapable Screen 2: - Name: DP1 Enabled: 1 Geometry: 5760,0,2160x3840 Scale: 1 Refresh Rate: 59996 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2) OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.3.6 OpenGL platform interface: GLX OpenGL shading language version string: 4.60 Driver: Intel GPU class: Comet Lake OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 23.3.6 X server version: 1.21.1 Linux kernel version: 6.7.5 Direct rendering: Requires strict binding: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- trackmouse screenshot outputlocator colorpicker screenedge mousemark contrast login sessionquit logout translucency windowaperture slide maximize scale morphingpopups squash fullscreen frozenapp fadingpopups dimscreen dialogparent windowview tileseditor overview highlightwindow blendchanges startupfeedback kscreen Currently Active Effects: - contrast Effect Settings: trackmouse: modifiers: mousePolling: true screenshot
[kwin] [Bug 481721] kwin_x11 compositor screen freeze (regression from kwin 5)
https://bugs.kde.org/show_bug.cgi?id=481721 --- Comment #1 from Bruno Pitrus --- +thread apply all backtrace Thread 27 (Thread 0x7f2d3a0006c0 (LWP 23911)): +backtrace #0 0x7f2d80c8effe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55fa16784bc8) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55fa16784bc8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7f2d80c8f09f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55fa16784bc8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7f2d80c91d40 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55fa16784b70, cond=0x55fa16784ba0) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=cond@entry=0x55fa16784ba0, mutex=mutex@entry=0x55fa16784b70) at pthread_cond_wait.c:618 #5 0x7f2d75f0f41b in cnd_wait (mtx=0x55fa16784b70, cond=0x55fa16784ba0) at ../src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func (input=input@entry=0x55fa13ea10f0) at ../src/util/u_queue.c:290 #7 0x7f2d75f04687 in impl_thrd_routine (p=) at ../src/c11/impl/threads_posix.c:67 #8 0x7f2d80c92bb2 in start_thread (arg=) at pthread_create.c:447 #9 0x7f2d80d1400c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 26 (Thread 0x7f2d1be006c0 (LWP 33953)): +backtrace #0 0x7f2d80c8effe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f2d612a35d0) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7f2d612a35d0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7f2d80c8f09f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f2d612a35d0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7f2d80c91d40 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f2d612a3578, cond=0x7f2d612a35a8) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=cond@entry=0x7f2d612a35a8, mutex=mutex@entry=0x7f2d612a3578) at pthread_cond_wait.c:618 #5 0x7f2d75f0f41b in cnd_wait (mtx=0x7f2d612a3578, cond=0x7f2d612a35a8) at ../src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func (input=input@entry=0x7f2c9c0256a0) at ../src/util/u_queue.c:290 #7 0x7f2d75f04687 in impl_thrd_routine (p=) at ../src/c11/impl/threads_posix.c:67 #8 0x7f2d80c92bb2 in start_thread (arg=) at pthread_create.c:447 #9 0x7f2d80d1400c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 25 (Thread 0x7f2d38c006c0 (LWP 23913)): +backtrace #0 0x7f2d80d0578f in __GI___poll (fds=0x55fa13ed6c80, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2d80515aff in g_main_context_poll_unlocked (priority=, n_fds=1, fds=0x55fa13ed6c80, timeout=, context=0x7f2c7c000c60) at ../glib/gmain.c:4653 #2 g_main_context_iterate_unlocked (context=context@entry=0x7f2c7c000c60, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4344 #3 0x7f2d8051620c in g_main_context_iteration (context=0x7f2c7c000c60, may_block=1) at ../glib/gmain.c:4414 #4 0x7f2d817a330c in QEventDispatcherGlib::processEvents (this=0x7f2c7c000b70, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #5 0x7f2d81591cbb in QEventLoop::exec (this=0x7f2d38bffa60, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:34 #6 0x7f2d81666a44 in QThread::exec (this=) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #7 0x7f2d816e5779 in operator() (__closure=) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread_unix.cpp:324 #8 (anonymous namespace)::terminate_on_exception > (t=...) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread_unix.cpp:260 #9 QThreadPrivate::start (arg=0x55fa13b91f50) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread_unix.cpp:283 #10 0x7f2d80c92bb2 in start_thread (arg=) at pthread_create.c:447 #11 0x7f2d80d1400c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 24 (Thread 0x7f2d20a006c0 (LWP 33952)): +backtrace #0 0x7f2d80c8effe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f2c9c004758) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7f2c9c004758, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=t
[kwin] [Bug 481721] New: kwin_x11 compositor screen freeze (regression from kwin 5)
https://bugs.kde.org/show_bug.cgi?id=481721 Bug ID: 481721 Summary: kwin_x11 compositor screen freeze (regression from kwin 5) Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: brunopit...@hotmail.com Target Milestone: --- SUMMARY Since updating to plasma 6, kwin_x11 compositor has started to randomly hang (entire screen freezes but reacts to clicks). Sometimes the hang goes away after a few seconds, other times pressing Alt-Shift-F12 to disable the compositor is the only way to regain a usable desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240221 (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION 1. backtrace of all threads obtained by sending SIGQUIT to kwin_x11 during a hang 2. output of `qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481715] plasma-kcminit-phase1.service crashes on startup
https://bugs.kde.org/show_bug.cgi?id=481715 --- Comment #2 from Bruno Pitrus --- (In reply to Harald Sitter from comment #1) > What's the journal output when that happens? > > The crash looks like InputBackend::implementation returns a nullptr which > shouldn't generally happen unless something is going wrong with the platform > detection. $ journalctl --user -u plasma-kcminit-phase1.service -- Boot e5b4ff55ae964175b7bde9621e382f2d -- lut 09 10:49:46 bruno-beit systemd[5698]: Starting KDE Configuration Module Initialization (Phase 1)... lut 09 10:49:46 bruno-beit qdbus[5882]: Service 'org.kde.kcminit' does not exist. lut 09 10:49:46 bruno-beit systemd[5698]: plasma-kcminit-phase1.service: Main process exited, code=exited, status=2/INVALIDARGUMENT lut 09 10:49:46 bruno-beit systemd[5698]: plasma-kcminit-phase1.service: Failed with result 'exit-code'. lut 09 10:49:46 bruno-beit systemd[5698]: Failed to start KDE Configuration Module Initialization (Phase 1). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481715] New: plasma-kcminit-phase1.service crashes on startup
https://bugs.kde.org/show_bug.cgi?id=481715 Bug ID: 481715 Summary: plasma-kcminit-phase1.service crashes on startup Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: brunopit...@hotmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY The process `/usr/bin/kcminit kcm_mouse_init kcm_touchpad_init` always crashes on launch which causes the plasma-kcminit-phase1.service unit to fail to start. plasma6-desktop and plasma6-workspace are at version 5.93.0 Backtrace: #0 kcminit () at /usr/src/debug/plasma-desktop-5.93.0/kcms/mouse/kcm/configcontainer.cpp:20 #1 0x5585df67e4d0 in KCMInit::runModule (this=, data=...) at /usr/src/debug/plasma-workspace-5.93.0/startkde/kcminit/main.cpp:63 #2 KCMInit::runModules (this=this@entry=0x7fff1ade3c50, phase=phase@entry=-1) at /usr/src/debug/plasma-workspace-5.93.0/startkde/kcminit/main.cpp:82 #3 0x5585df67c588 in KCMInit::KCMInit (args=..., this=0x7fff1ade3c50) at /usr/src/debug/plasma-workspace-5.93.0/startkde/kcminit/main.cpp:134 #4 main (argc=, argv=) at /usr/src/debug/plasma-workspace-5.93.0/startkde/kcminit/main.cpp:182 SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240221 (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 214950] New tool exp-floattrap
https://bugs.kde.org/show_bug.cgi?id=214950 --- Comment #17 from Bruno Lathuilière --- As a side product of the valgrind tool verrou, we have a similar functionality (activated by default) for all emulated rounding mode. So if the rounding-mode nearest is selected (by default), the behavior of verrou and exp-floattrap is similar. The specialized tool exp-floattrap has several advantages : - exp-floattrap deals with more IOP (by example Iop_Recip*, Iop_RSqst*, Iop_Neg* ... ). - I think (I did not check) exp-floattrap should be faster than verrou as the NaN detection is done with IR. In verrou it is done inside the dirty call to a function which replace the floating point operation. - exp-floattrap should be more portable than verrou. There one point where verrou is maybe more user friendly (concerning only the nan/inf detection). Indeed with option --libm=instrumented (not yet the default), the dynamic libm call are intercepted and so the nan/inf detection inside a libm call are ignored : there is only one detection on the result. To conclude both tools are complementary but there is overlapping, so it is good to keep in mind. As I just discovered this tool, I think it could be a good idea to add a link in this page : https://valgrind.org/downloads/variants.html -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 214950] New tool exp-floattrap
https://bugs.kde.org/show_bug.cgi?id=214950 Bruno Lathuilière changed: What|Removed |Added CC||bruno.lathuili...@edf.fr -- You are receiving this mail because: You are watching all bug changes.
