[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.
[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.
[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&action=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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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 #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 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&action=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.
[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.
[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.
[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.
[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.
[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&action=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.
[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&action=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.
[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.
[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 --- 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 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 #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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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] 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.
[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.
[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.
[kate] [Bug 455056] Kate crash when going to Settings Menu -> 'Configure Kate' option
https://bugs.kde.org/show_bug.cgi?id=455056 Bruno changed: What|Removed |Added CC||brunoparol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 455056] Kate crash when going to Settings Menu -> 'Configure Kate' option
https://bugs.kde.org/show_bug.cgi?id=455056 --- Comment #2 from Bruno --- Created attachment 150255 --> https://bugs.kde.org/attachment.cgi?id=150255&action=edit New crash information added by DrKonqi kate (22.04.1) using Qt 5.15.3 - What I was doing when the application crashed: I just tried to open the settings from Kate's menu. -- Backtrace (Reduced): #4 0x7f330852fcda in qstrcmp(QByteArray const&, QByteArray const&) () from /lib64/libQt5Core.so.5 #5 0x7f3309b36e03 in QMapData::findNode(KEntryKey const&) const () from /lib64/libKF5ConfigCore.so.5 #7 0x7f3309b367e2 in KConfigPrivate::lookupData(QByteArray const&, char const*, QFlags, bool*) const () from /lib64/libKF5ConfigCore.so.5 #8 0x7f3309b42f95 in KConfigGroup::readEntry(char const*, QString const&) const () from /lib64/libKF5ConfigCore.so.5 #9 0x7f3309b431af in KConfigGroup::readEntry(char const*, char const*) const () from /lib64/libKF5ConfigCore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 423822] No support for Portuguese accents on keyboard
https://bugs.kde.org/show_bug.cgi?id=423822 Bruno changed: What|Removed |Added CC||brunocco...@gmail.com --- Comment #2 from Bruno --- I got the same problem here. It happens only with KDE applications like KWrite. But it works well with other applications, like Firefox. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438517] New: Plasma crash when change the screen layout (wayland)
https://bugs.kde.org/show_bug.cgi?id=438517 Bug ID: 438517 Summary: Plasma crash when change the screen layout (wayland) Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: bait...@mailfence.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY My notebook is connected with an external monitor. Plasma crash when change the screen layout. STEPS TO REPRODUCE 1. Add Widget -> Add "Display Configuration" 2. open "Display configuration" widget and select "Switch to Laptop screen" or "Switch to external screen" OBSERVED RESULT Plasma crash EXPECTED RESULT screen layout change without plasma crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-73-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION Same bug in Kubuntu impish beta Application: Plasma (plasmashell), signal: Aborted [New LWP 11595] [New LWP 11607] [New LWP 11608] [New LWP 11609] [New LWP 11610] [New LWP 11643] [New LWP 11673] [New LWP 11674] [New LWP 11681] [New LWP 11687] [New LWP 11701] [New LWP 11702] [New LWP 11737] [New LWP 11738] [New LWP 11739] [New LWP 11740] [New LWP 11741] [New LWP 11742] [New LWP 11743] [New LWP 11744] [New LWP 11804] [New LWP 11806] [New LWP 11918] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f11a88bbaff in __GI___poll (fds=0x7ffcb4a0e9b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f11a4ba2ec0 (LWP 11517))] Thread 24 (Thread 0x7f110faff700 (LWP 11918)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56338ff6cf90) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56338ff6cf40, cond=0x56338ff6cf68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56338ff6cf68, mutex=0x56338ff6cf40) at pthread_cond_wait.c:638 #3 0x7f11a8c4ed5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f11aa894814 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f11aa894c89 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f11a8c48bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f11a7c0d609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f11a88c8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f116c8e2700 (LWP 11806)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563389255114) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5633892550c0, cond=0x5633892550e8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5633892550e8, mutex=0x5633892550c0) at pthread_cond_wait.c:638 #3 0x7f11a8c4ed5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f11aa894814 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f11aa894c89 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f11a8c48bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f11a7c0d609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f11a88c8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f111cd95700 (LWP 11804)): #0 0x7f11a88c85ce in epoll_wait (epfd=64, events=0x7f111cd948f0, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7f1180e66acb in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7f1180e594a4 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7f1180eabe70 in ?? () from /lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4 0x7f11a7c0d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f11a88c8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f111d7fa700 (LWP 11744)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5633821443a4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563382144350, cond=0x563382144378) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563382144378, mutex=0x563382144350) at pthread_cond_wait.c:638 #3 0x7f11a8c4ed5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1180afef40 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread
[plasmashell] [Bug 438523] New: Plasma crash after add network speed widget
https://bugs.kde.org/show_bug.cgi?id=438523 Bug ID: 438523 Summary: Plasma crash after add network speed widget Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bait...@mailfence.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. create a new user 2. Start a Plasma session on Wayland 3. Click on "add widget" and add "Network speed" widget. OBSERVED RESULT Plasma crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION This bug affect only new users. Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 9151] [New LWP 9069] [New LWP 9040] [New LWP 9041] [New LWP 9043] [New LWP 9112] [New LWP 9114] [New LWP 9115] [New LWP 8952] [New LWP 9022] [New LWP 9117] [New LWP 9113] [New LWP 9042] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f9426dff700 (LWP 9151))] [Current thread is 1 (Thread 0x7f9426dff700 (LWP 9151))] Thread 13 (Thread 0x7f9465059700 (LWP 9042)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561354e3d71c) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561354e3d6c8, cond=0x561354e3d6f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561354e3d6f0, mutex=0x561354e3d6c8) at pthread_cond_wait.c:638 #3 0x7f9466755e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f9466755a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f946b79d609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f946c45b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f94467c0700 (LWP 9113)): #0 0x7f946c44eaff in __GI___poll (fds=0x7f9438018210, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f946ad6b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f946ad6b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f946ca1cb22 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f946c9c0dcb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f946c7dabb2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f946e3643ba in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f946c7dbd4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f946b79d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f946c45b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f943e28b700 (LWP 9117)): #0 0x7f946c44eaff in __GI___poll (fds=0x7f942c006550, nfds=1, timeout=3498563) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f946ad6b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f946ad6b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f946ca1cb22 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f946c9c0dcb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f946c7dabb2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f943e78207c in KCupsConnection::run() () from /lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f946c7dbd4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f946b79d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f946c45b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f9467b59700 (LWP 9022)): #0 0x7f946c44eaff in __GI___poll (fds=0x7f9460005240, nfds=3, timeout=7611) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f946ad6b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f946ad6b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f946ca1cb22 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f946c9c0dcb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f946c7dabb2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00
[kwin] [Bug 438577] New: System freezes when i disable one screen and change compositor rendering backend
https://bugs.kde.org/show_bug.cgi?id=438577 Bug ID: 438577 Summary: System freezes when i disable one screen and change compositor rendering backend Product: kwin Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: bait...@mailfence.com Target Milestone: --- SUMMARY I have 2 monitors (notebook + external monitor). When i disable the notebook screen and change the compositor rendering backend, the system freezes. Only the mouse moves work. STEPS TO REPRODUCE 1. open "System Settings" -> "Display and Monitor" -> "Display Configuration" 2. Disable one screen 3. CHange the rendering backend (Opengl 2.0 to opengl 3.1 or vice versa). OBSERVED RESULT System freezes EXPECTED RESULT No freeze. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION Similar: https://bugs.kde.org/show_bug.cgi?id=425557 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438227] New: System Settings freeze when opened after KSystemLog
https://bugs.kde.org/show_bug.cgi?id=438227 Bug ID: 438227 Summary: System Settings freeze when opened after KSystemLog Product: systemsettings Version: 5.21.90 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bait...@mailfence.com Target Milestone: --- SUMMARY When open "System Settings" after KSystemLog, "System Settings" freeze. STEPS TO REPRODUCE 1. Open KSystemLog and enter the password 2. Open "System Settings" OBSERVED RESULT "System Settings" not respond. EXPECTED RESULT "System Settings" respond correctly. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438228] New: Additional Drivers does not open from discover
https://bugs.kde.org/show_bug.cgi?id=438228 Bug ID: 438228 Summary: Additional Drivers does not open from discover Product: Discover Version: 5.21.90 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bait...@mailfence.com CC: aleix...@kde.org Target Milestone: --- Created attachment 139095 --> https://bugs.kde.org/attachment.cgi?id=139095&action=edit Discover error message SUMMARY Impossible launch "Additional Drivers" from discover. STEPS TO REPRODUCE 1. open discover 2. search by "driver" 3. click on "Additional Drivers" 4. click on "Launch" OBSERVED RESULT Message: "Failed to start '/usr/share/applications/software-properties-drivers.lxqt.desktop'" EXPECTED RESULT Open "Additional drivers" app. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-18-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 438230] New: Skanlite not open from menu (wayland session)
https://bugs.kde.org/show_bug.cgi?id=438230 Bug ID: 438230 Summary: Skanlite not open from menu (wayland session) Product: Skanlite Version: 2.2.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: bait...@mailfence.com Target Milestone: --- SUMMARY Skanlite not open from menu (only with wayland session) STEPS TO REPRODUCE 1. open the menu 2. search by "skanlite" 3. click on "skanlite" OBSERVED RESULT Nothing EXPECTED RESULT Skanlite window opened SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic (64-bit) Graphics Platform: Wayland Processor: 1 × Intel Core Processor (Haswell, no TSX, IBRS) Memory: 1.9 GiB of RAM Graphics Processor: llvmpipe ADDITIONAL INFORMATION It is possible run Skanlite from terminal. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 438231] New: Skanlite: application icon is different for wayland
https://bugs.kde.org/show_bug.cgi?id=438231 Bug ID: 438231 Summary: Skanlite: application icon is different for wayland Product: Skanlite Version: 2.2.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: bait...@mailfence.com Target Milestone: --- SUMMARY Application icon is different for wayland. STEPS TO REPRODUCE 1. open skanlite (wayland session) 2. logout 3. start a session with X 4. open skanlite OBSERVED RESULT Different icons for wayland and X EXPECTED RESULT Same icon for both. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic (64-bit) Graphics Platform: X11 Processor: 1 × Intel Core Processor (Haswell, no TSX, IBRS) Memory: 2.9 GiB of RAM Graphics Processor: llvmpipe ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438255] New: Taskbar panel missing (wayland session)
https://bugs.kde.org/show_bug.cgi?id=438255 Bug ID: 438255 Summary: Taskbar panel missing (wayland session) Product: plasmashell Version: 5.21.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bait...@mailfence.com Target Milestone: 1.0 Created attachment 139105 --> https://bugs.kde.org/attachment.cgi?id=139105&action=edit taskbar missing SUMMARY When start a plasma session on Wayland, the taskbar is not opened. STEPS TO REPRODUCE 1. Start a Plasma session on Wayland OBSERVED RESULT Taskbar (bottom panel) is not opened. EXPECTED RESULT Taskbar opened SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-18-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438265] New: Impossible to select the primary screen (wayland session)
https://bugs.kde.org/show_bug.cgi?id=438265 Bug ID: 438265 Summary: Impossible to select the primary screen (wayland session) Product: systemsettings Version: 5.21.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: bait...@mailfence.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 139109 --> https://bugs.kde.org/attachment.cgi?id=139109&action=edit Option "primary" is not visible SUMMARY My notebook connect with an external monitor. Display configuration does not permit to select the primary screen. The option is not visible. STEPS TO REPRODUCE 1. start a plasma session on wayland 2. open "System Settings" and go to "Display and monitor"->"Display Configuration" OBSERVED RESULT The option "primary" is not visible. EXPECTED RESULT The option "primary" visible and working. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-18-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438267] New: Crash after disable the screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=438267 Bug ID: 438267 Summary: Crash after disable the screen (wayland) Product: systemsettings Version: 5.21.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: bait...@mailfence.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY My notebook is connected with an external monitor. When i disable one screen, "System Settings" app crash. STEPS TO REPRODUCE 1. start a Plasma session on Wayland 2. open "System Settings" and go to "Display and monitor"->"Display Configuration" 3. Disable one screen OBSERVED RESULT Crash EXPECTED RESULT Screen disable SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-18-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f103f956791 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #5 0x7f103d938249 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #6 0x7f103d937639 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #7 0x7f103f8c4a2e in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #8 0x7f103f8c512b in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #9 0x7f103f8c531c in wl_display_dispatch_queue_pending () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #10 0x7f103f94af83 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7f1042035670 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1042038c53 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1042039483 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f1042bf2783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f1041ffd82a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f1042057e75 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f103fc1e8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f103fc71d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f103fc1c023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f1042057274 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f1041ffc18b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f1042004674 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x556a15f7b58b in ?? () #24 0x7f1041968565 in __libc_start_main (main=0x556a15f7aa20, argc=1, argv=0x75ed8f88, init=, fini=, rtld_fini=, stack_end=0x75ed8f78) at ../csu/libc-start.c:332 #25 0x556a15f7c1ee in ?? () [Inferior 1 (process 5962) detached] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438227] System Settings freeze when opened after KSystemLog
https://bugs.kde.org/show_bug.cgi?id=438227 --- Comment #2 from Bruno --- (gdb) run Starting program: /usr/bin/systemsettings5 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x71469640 (LWP 4806)] [New Thread 0x7fffebfff640 (LWP 4807)] [New Thread 0x7fffe9be4640 (LWP 4808)] [New Thread 0x7fffe93e3640 (LWP 4809)] [New Thread 0x7fffe8be2640 (LWP 4810)] [New Thread 0x7fffdbfff640 (LWP 4811)] [New Thread 0x7fffdad94640 (LWP 4812)] [New Thread 0x7fffda593640 (LWP 4813)] [New Thread 0x7fffd9d92640 (LWP 4814)] [New Thread 0x7fffd9591640 (LWP 4815)] [New Thread 0x7fffd8b65640 (LWP 4816)] [New Thread 0x7fffbe992640 (LWP 4817)] QQmlEngine::setContextForObject(): Object already has a QQmlContext [Detaching after fork from child process 4819] [Detaching after fork from child process 4820] [New Thread 0x7fffbd4d3640 (LWP 4821)] QQmlEngine::setContextForObject(): Object already has a QQmlContext QQmlEngine::setContextForObject(): Object already has a QQmlContext bt [Thread 0x7fffd9591640 (LWP 4815) exited] [Thread 0x7fffd9d92640 (LWP 4814) exited] [Thread 0x7fffda593640 (LWP 4813) exited] [Thread 0x7fffdad94640 (LWP 4812) exited] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438228] Additional Drivers does not open from discover
https://bugs.kde.org/show_bug.cgi?id=438228 --- Comment #2 from Bruno --- Yes. [Desktop Entry] Name=Additional Drivers GenericName=Additional Drivers Comment=Configure third-party and proprietary drivers Exec=lxqt-sudo /usr/bin/software-properties-qt --open-tab=4 Icon=jockey OnlyShowIn=LXQt; Terminal=false Type=Application Categories=Settings;HardwareSettings;System; Keywords=Drivers; X-Ubuntu-Gettext-Domain=software-properties -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438228] Additional Drivers does not open from discover
https://bugs.kde.org/show_bug.cgi?id=438228 --- Comment #3 from Bruno --- Sorry, i have /usr/share/applications/software-properties-drivers-lxqt.desktop. But not /usr/share/applications/software-properties-drivers.lxqt.desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438255] Taskbar panel missing (wayland session)
https://bugs.kde.org/show_bug.cgi?id=438255 --- Comment #2 from Bruno --- 1. No. With X11 works. 2. No. 3. Nothing. Same problem. I discovered something. When i create a new user from "System Settings" and login with it, the taskbar is visible. But only on first login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430878] New: Plasma crashed on Wayland when I connected TV via HDMI
https://bugs.kde.org/show_bug.cgi?id=430878 Bug ID: 430878 Summary: Plasma crashed on Wayland when I connected TV via HDMI Product: plasmashell Version: 5.20.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bmeze...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.4) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.10.1-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I have just finished logging a fresh user, connected the TV via HDMI and changed the TV active port. The session was restored automatically with the crash report notice. - Unusual behavior I noticed: Worked fine on X11 either with native or custom resolution on notebook display without crashes. Wayland sessions seems to break in a unrecoverable way if I try a custom resolution on the notebook display. Already got two users totally unable to start wayland (and full wayland) sessions. Reseting config files didn't restore wayland to said users. Couldn't get a creash report for this. - Custom settings of the application: HDMI port custom resolution added to kernel cmd line. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f15a675c890 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55ebb3f272d0, registry=0x55ebb04dc410, id=45, interface=..., version=2) at global/qwaylandclientextension.cpp:67 #5 0x7f15a67454b2 in QtWaylandClient::QWaylandDisplay::registry_global (this=, id=45, interface=..., version=2) at qwaylanddisplay.cpp:396 #6 0x7f15a6765c46 in QtWayland::wl_registry::handle_global (data=0x55ebb04d9040, object=, name=45, interface=0x55ebb177c170 "org_kde_kwin_outputdevice", version=2) at qwayland-wayland.cpp:94 #7 0x7f15a6e0342d in ffi_call_unix64 () at ../src/x86/unix64.S:106 #8 0x7f15a6dff4f9 in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:669 #9 0x7f15a82fe8fe in wl_closure_invoke (closure=closure@entry=0x55ebb177c090, target=, target@entry=0x55ebb04dc410, opcode=opcode@entry=0, data=, flags=) at src/connection.c:1018 #10 0x7f15a82fefcb in dispatch_event (display=0x55ebb04dce20, queue=, queue=) at src/wayland-client.c:1445 #11 0x7f15a82ff19c in dispatch_queue (queue=0x55ebb04dcef0, display=0x55ebb04dce20) at src/wayland-client.c:1591 #12 wl_display_dispatch_queue_pending (display=0x55ebb04dce20, queue=0x55ebb04dcef0) at src/wayland-client.c:1833 #13 0x7f15a82ff1ec in wl_display_dispatch_pending (display=) at src/wayland-client.c:1896 #14 0x7f15a6744df3 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55ebb04d9030) at qwaylanddisplay.cpp:221 #15 0x7f15a8a778a0 in doActivate (sender=0x55ebb0540960, signal_index=4, argv=0x7ffe9b3161b0, argv@entry=0x0) at kernel/qobject.cpp:3898 #16 0x7f15a8a70bc0 in QMetaObject::activate (sender=sender@entry=0x55ebb0540960, m=m@entry=0x7f15a8d250e0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #17 0x7f15a8a3de23 in QAbstractEventDispatcher::awake (this=this@entry=0x55ebb0540960) at .moc/moc_qabstracteventdispatcher.cpp:149 #18 0x7f15a8a9881c in QEventDispatcherGlib::processEvents (this=0x55ebb0540960, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #19 0x7f15a8a3fc4b in QEventLoop::exec (this=this@entry=0x7ffe9b3162d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #20 0x7f15a8a47ec0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #21 0x55ebae94f082 in main (argc=, argv=0x7ffe9b3164f0) at /usr/src/debug/plasma5-workspace-5.20.4-1.1.x86_64/shell/main.cpp:252 [Inferior 1 (process 12014) detached] The reporter indicates this bug may be a duplicate of or related to bug 422418. Possible duplicates by query: bug 429342, bug 428420, bug 422418, bug 419060, bug 418477. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489852] New: System Settings crash after click on "Sound" menu
https://bugs.kde.org/show_bug.cgi?id=489852 Bug ID: 489852 Summary: System Settings crash after click on "Sound" menu Classification: Applications Product: systemsettings Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tuxb...@tutamail.com Target Milestone: --- SUMMARY System Settings crash after click on "Sound" menu STEPS TO REPRODUCE 1. open the system settings 2. click on "Sound" 3. click on "Display & Monitor" 4. repeat the steps 2 and 3 until the app crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Testing with KDE Plasma 6.1.3 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION inxi -F System: Host: teste-x450lcp Kernel: 6.5.0-41-generic x86_64 bits: 64 Desktop: KDE Plasma 6.1.3 Distro: KDE neon 22.04 Testing Edition Machine: Type: Laptop System: ASUSTeK product: X450LCP v: 1.0 serial: E3N0B201534412A Mobo: ASUSTeK model: X450LCP v: 1.0 serial: BSN12345678901234567 UEFI: American Megatrends v: X450LCP.209 date: 04/18/2019 Battery: ID-1: BAT0 charge: 962.7 Wh (99.5%) condition: 967.5/32.6 Wh (2971.5%) volts: 14.8 min: 14.8 CPU: Info: dual core model: Intel Core i5-4200U bits: 64 type: MT MCP cache: L2: 512 KiB Speed (MHz): avg: 1397 min/max: 800/2600 cores: 1: 1596 2: 1596 3: 1596 4: 800 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] driver: nouveau v: kernel Device-3: Chicony USB2.0 HD UVC WebCam type: USB driver: uvcvideo Display: server: X.Org v: 1.23.2.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1: 2560x1440~60Hz 2: 1708x960~60Hz OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2) v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2 Audio: Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel Device-2: Intel 8 Series HD Audio driver: snd_hda_intel Sound Server-1: ALSA v: k6.5.0-41-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: bc:ee:7b:b2:f4:ad Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci IF: wlp3s0f0 state: down mac: 48:5a:b6:05:b4:6d Bluetooth: Device-1: Ralink RT3290 Bluetooth driver: N/A Drives: Local Storage: total: 223.57 GiB used: 11.99 GiB (5.4%) ID-1: /dev/sda vendor: Western Digital model: WDS240G2G0A-00JH30 size: 223.57 GiB Partition: ID-1: / size: 103.07 GiB used: 11.98 GiB (11.6%) fs: ext4 dev: /dev/sda4 ID-2: /boot/efi size: 511 MiB used: 11.9 MiB (2.3%) fs: vfat dev: /dev/sda1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 44.0 C mobo: N/A Fan Speeds (RPM): cpu: 3300 Info: Processes: 214 Uptime: 3h 3m Memory: 9.59 GiB used: 4.56 GiB (47.6%) Shell: Sudo inxi: 3.3.13 Backtrace #0 operator() (__closure=0x56350c60) at ./src/qmlmodels/qqmldelegatemodel.cpp:1871 #1 QtPrivate::FunctorCall, QtPrivate::List<>, void, QQmlDelegateModel::_q_modelAboutToBeReset():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:137 #2 QtPrivate::FunctorCallable >::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:345 #3 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) ( which=, this_=0x56350c50, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:555 #4 0x7526355e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:469 #5 doActivate (sender=0x58019630, signal_index=21, argv=0x7fff7d70) at ./src/corelib/kernel/qobject.cpp:4078 #6 0x7511cac1 in QAbstractItemModel::modelReset (this=, _t1=...) at ./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1112 #7 0x7506755c in QSortFilterProxyModel::setSourceModel (this=0x58019630, sourceModel=) at ./src/corelib/itemmodels/qsortfilterproxymodel.cpp:2102 #8 0x7fffc55a624a in KSortFilterProxyModel::setSourceModel (this=0x58019630, model=0x567cc110) at ./src/qml/ksortfilterproxymodel.cpp:94 #9 0x7514b69f in QAbstractProxyModelPrivate::setModelForwarder (sourceModel=, this=0x576efa50) at ./src/corelib/itemmodels/qabstractproxymodel_p.h:40 #10 QObjectCompatProperty::bindingWrapper (type=..., dataPtr=0x576efb20, binding=...) at ./src/corelib/kernel/qproperty_p.h:534 #11 0x7520f42d in QPropertyBindingPrivate::evaluateRecursiv
[systemsettings] [Bug 489852] System Settings crash after click on "Sound" menu
https://bugs.kde.org/show_bug.cgi?id=489852 --- Comment #1 from Bruno --- Maybe, this bug is fixed in QT 6.7.2. View: https://bugs.kde.org/show_bug.cgi?id=487904#c34 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488965] KCMs with any InlineMessages or a KNewStuff dialog break in System Settings but work in KCMShell6: Cannot assign object of type "TP.IconPropertiesGroup" to property of ty
https://bugs.kde.org/show_bug.cgi?id=488965 Bruno changed: What|Removed |Added CC||tuxb...@tutamail.com --- Comment #18 from Bruno --- Same bug with Opensuse Tumbleweed. qrc:/kcm/kcm_keys/main.qml:66 Type Kirigami.InlineMessage unavailable file:///usr/lib64/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type KT.InlineMessage unavailable qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign object of type "TP.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_64*" as the former is neither the same as the latter nor a sub-class of it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 490514] New: Theme not aplied on configure button - Brightness and color widget
https://bugs.kde.org/show_bug.cgi?id=490514 Bug ID: 490514 Summary: Theme not aplied on configure button - Brightness and color widget Classification: Plasma Product: Breeze Version: 6.1.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color scheme Assignee: plasma-b...@kde.org Reporter: tuxb...@tutamail.com Target Milestone: --- Created attachment 171795 --> https://bugs.kde.org/attachment.cgi?id=171795&action=edit Wrong theme applied to configure button SUMMARY The configure button inside “Brightness and color“ don\t receive the new color after changing the theme. STEPS TO REPRODUCE 1. open system settings 2. change the theme from breeze dark to breeze (or breeze to breeze dark) 3. open the “Brightness and color“ widget OBSERVED RESULT “Configure“ button with wrong theme. EXPECTED RESULT Button with correct theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse tumbleweed KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 490514] Theme not applied on configure button - Brightness and color widget
https://bugs.kde.org/show_bug.cgi?id=490514 Bruno changed: What|Removed |Added Summary|Theme not aplied on |Theme not applied on |configure button - |configure button - |Brightness and color widget |Brightness and color widget -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 490514] Theme not applied on configure button - Brightness and color widget
https://bugs.kde.org/show_bug.cgi?id=490514 Bruno changed: What|Removed |Added Version|6.1.2 |6.1.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383944] Kdeinit5 needs restart after Dolphin is closed after some manipulation on files
https://bugs.kde.org/show_bug.cgi?id=383944 --- Comment #5 from bruno --- No it doesn't, that was some time ago ! Am I supposed to close this case in some way? -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 422722] New: ID3 tags not recognized on v3.8.3
https://bugs.kde.org/show_bug.cgi?id=422722 Bug ID: 422722 Summary: ID3 tags not recognized on v3.8.3 Product: kid3 Version: 3.8.x Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: brunodigle...@gmail.com Target Milestone: --- Created attachment 129181 --> https://bugs.kde.org/attachment.cgi?id=129181&action=edit screenshot and test file SUMMARY STEPS TO REPRODUCE Open the "test.mp3" attached file OBSERVED RESULT ID3 tags not read with version 3.8.3, OK on version v 3.6.2 EXPECTED RESULT SOFTWARE/OS VERSIONS macOS: Mojave ADDITIONAL INFORMATION See screenshot attached -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 422722] ID3 tags not recognized on v3.8.3
https://bugs.kde.org/show_bug.cgi?id=422722 --- Comment #1 from Bruno --- This seem to be a one shot random bug. After reporting it, I've tried again and everything was OK on both versions... Don't waste your time on this. My apologies and thank you for the GREAT software :) -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 422722] ID3 tags not recognized on v3.8.3
https://bugs.kde.org/show_bug.cgi?id=422722 --- Comment #2 from Bruno --- Well... I's still occurring randomly on v3.8.3 ... Annoying :( I will take a try to other versions. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 422722] ID3 tags not recognized on v3.8.3
https://bugs.kde.org/show_bug.cgi?id=422722 Bruno changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Bruno --- (In reply to Urs Fleisch from comment #3) > I tried to reproduce this both on Linux and on macOS, but the tags are > always read. Is it possible that the file is locked by another application - > a behavior which I would rather expect from Windows? > > For MP3 files with ID3v2.3.0 tags, you have the option of using two > libraries: TagLib (the default) or id3lib. You could try to switch to the > other library in the Plugins tab of the preferences (and restart Kid3 > afterwards). > > A more advanced examination would involve monitoring Kid3 using dtruss or a > similar tool and check what exactly is going on. This should also reveal > errors occurring when accessing the file. Hello Urs, Today no way to reproduce the issue... As soon as it occurs I will take a try by following your instructions. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 396371] New: Umbrello stopped during Code Importing Progress
https://bugs.kde.org/show_bug.cgi?id=396371 Bug ID: 396371 Summary: Umbrello stopped during Code Importing Progress Product: umbrello Version: unspecified Platform: MacPorts Packages OS: OS X Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: bruno.fal...@msn.com Target Milestone: --- Application: umbrello (2.14.3) KDE Platform Version: 4.14.3 Qt Version: 4.8.7 Operating System: Darwin 17.6.0 x86_64 Distribution (Platform): MacPorts Packages -- Information about the crash: - What I was doing when the application crashed: Umbrello just stopped after I clicked the button to import codes and generate the Class Diagram. The crash can be reproduced every time. -- Backtrace: Application: Umbrello UML Modeller (umbrello), signal: Segmentation fault: 11 (lldb) process attach --pid 12725 Process 12725 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP frame #0: 0x7fff612fe232 libsystem_kernel.dylib`__wait4 + 10 libsystem_kernel.dylib`__wait4: -> 0x7fff612fe232 <+10>: jae0x7fff612fe23c; <+20> 0x7fff612fe234 <+12>: movq %rax, %rdi 0x7fff612fe237 <+15>: jmp0x7fff612f4b25; cerror 0x7fff612fe23c <+20>: retq Target 0: (umbrello) stopped. Executable module set to "/Applications/MacPorts/KDE4/umbrello.app/Contents/MacOS/umbrello". Architecture set to: x86_64h-apple-macosx. (lldb) set set term-width 200 (lldb) thread info thread #1: tid = 0x705c5b, 0x7fff612fe232 libsystem_kernel.dylib`__wait4 + 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP (lldb) bt all * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP * frame #0: 0x7fff612fe232 libsystem_kernel.dylib`__wait4 + 10 frame #1: 0x00010b82563e libkdeui.5.dylib`KCrash::startProcess(int, char const**, bool) + 264 frame #2: 0x00010b8249b3 libkdeui.5.dylib`KCrash::defaultCrashHandler(int) + 1050 frame #3: 0x7fff614bbf5a libsystem_platform.dylib`_sigtramp + 26 frame #4: 0x00010a7a430a umbrello`AST::getEndPosition(int*, int*) const + 10 frame #5: 0x00010a7e75c6 umbrello`Parser::parseDeclarationInternal(std::__1::auto_ptr&) + 4726 frame #6: 0x00010a7f8547 umbrello`Parser::parseMemberSpecification(std::__1::auto_ptr&) + 4007 frame #7: 0x00010a7e4ebc umbrello`Parser::parseClassSpecifier(std::__1::auto_ptr&) + 796 frame #8: 0x00010a7dda53 umbrello`Parser::parseDeclaration(std::__1::auto_ptr&) + 307 frame #9: 0x00010a7dd461 umbrello`Parser::parseTranslationUnit(KSharedPtr&) + 401 frame #10: 0x00010a7b559d umbrello`Driver::ParseHelper::parse() + 205 frame #11: 0x00010a7b6638 umbrello`Driver::parseFile(QString const&, bool, bool, bool) + 392 frame #12: 0x00010a83fa59 umbrello`CppImport::parseFile(QString const&) + 169 frame #13: 0x00010a7965b1 umbrello`CodeImpThread::run() + 433 frame #14: 0x00010a7944bd umbrello`CodeImpStatusPage::importCodeFile(bool) + 941 frame #15: 0x00010c14bdaa QtCore`QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2074 frame #16: 0x00010c150852 QtCore`QSingleShotTimer::timerEvent(QTimerEvent*) + 50 frame #17: 0x00010c146ecc QtCore`QObject::event(QEvent*) + 172 frame #18: 0x00010c752f2b QtGui`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251 frame #19: 0x00010c754473 QtGui`QApplication::notify(QObject*, QEvent*) + 323 frame #20: 0x00010c132a71 QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 113 frame #21: 0x00010c7053b7 QtGui`QEventDispatcherMacPrivate::activateTimer(__CFRunLoopTimer*, void*) + 199 frame #22: 0x7fff393a9064 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 frame #23: 0x7fff393a8cd7 CoreFoundation`__CFRunLoopDoTimer + 1095 frame #24: 0x7fff393a87da CoreFoundation`__CFRunLoopDoTimers + 346 frame #25: 0x7fff3939fdab CoreFoundation`__CFRunLoopRun + 2427 frame #26: 0x7fff3939f1a3 CoreFoundation`CFRunLoopRunSpecific + 483 frame #27: 0x7fff38685d96 HIToolbox`RunCurrentEventLoopInMode + 286 frame #28: 0x7fff38685a0f HIToolbox`ReceiveNextEventCommon + 366 frame #29: 0x7fff38685884 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 64 frame #30: 0x7fff36937a73 AppKit`_DPSNextEvent + 2085 frame #31: 0x7fff370cde34 AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044 frame #32: 0x00010c706b9e QtGui`QEventDispatcherMac::processEvents(QFlags) + 1710 frame #33: 0x00010c12fa8e QtCore`QEventLoop::exec(QFlags) + 478 frame #34: 0x00010cba4e44 QtGui`QDialog::exec() + 244 frame #35: 0x00010aa65886 umbre
[konsole] [Bug 386740] konsole crashes for no reason
https://bugs.kde.org/show_bug.cgi?id=386740 bruno changed: What|Removed |Added CC||bagonzalez...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386740] konsole crashes for no reason
https://bugs.kde.org/show_bug.cgi?id=386740 --- Comment #7 from bruno --- Created attachment 111046 --> https://bugs.kde.org/attachment.cgi?id=111046&action=edit New crash information added by DrKonqi konsole (16.04.3) using Qt 5.6.1 - What I was doing when the application crashed: I was working with Jupyter Notebook, and I loaded this from the konsole when the console crashed, this is the 4 or 5 time that this append, since I made the update on linux mint -- Backtrace (Reduced): #6 0x7f24656a0428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f24656a202a in __GI_abort () at abort.c:89 #8 0x7f2462067f41 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #10 0x7f2462282719 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2462b8aafc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383944] Kdeinit5 needs restart after Dolphin is closed after some manipulation on files
https://bugs.kde.org/show_bug.cgi?id=383944 --- Comment #3 from bruno --- This bug is still there by the way -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 383944] New: Dolhin crashes at random after some manipulation on files
https://bugs.kde.org/show_bug.cgi?id=383944 Bug ID: 383944 Summary: Dolhin crashes at random after some manipulation on files Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: l...@free.fr Target Milestone: --- Application: kdeinit5 (16.12.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.43-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: This happens since upgrade to Mageia 6 noyau : 4.9.43-desktop-1.mga6 arch: 64-bit Bureau : KDE Plasma The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f62f85c8800 (LWP 5465))] Thread 4 (Thread 0x7f62d9413700 (LWP 5468)): #0 0x7f62f3776241 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #1 0x7f62f3776bc3 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f62f3776d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f62f7108e2b in QEventDispatcherGlib::processEvents (this=0x7f62cc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f62f70b449a in QEventLoop::exec (this=this@entry=0x7f62d9412de0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #5 0x7f62f6eee3bc in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f62f6ef2ff9 in QThreadPrivate::start (arg=0x1a357a0) at thread/qthread_unix.cpp:365 #7 0x7f62f44c566d in start_thread () from /lib64/libpthread.so.0 #8 0x7f62f6b89e4d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f62db05e700 (LWP 5467)): #0 0x7f62f44cda7a in __lll_unlock_wake () from /lib64/libpthread.so.0 #1 0x7f62f44c8f2f in pthread_mutex_unlock () from /lib64/libpthread.so.0 #2 0x7f62f4f04015 in ?? () from /usr/lib64/nvidia-current/libGL.so.1 #3 0x7f62f4f096eb in ?? () from /usr/lib64/nvidia-current/libGL.so.1 #4 0x7f62f27ea0f1 in ?? () from /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.59 #5 0x7f62f37ba690 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #6 0x7f62f377679e in g_main_context_check () from /lib64/libglib-2.0.so.0 #7 0x7f62f3776c38 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #8 0x7f62f3776d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #9 0x7f62f7108e2b in QEventDispatcherGlib::processEvents (this=0x7f62d40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #10 0x7f62f70b449a in QEventLoop::exec (this=this@entry=0x7f62db05ddb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #11 0x7f62f6eee3bc in QThread::exec (this=this@entry=0x7f62f8560d40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #12 0x7f62f84ef635 in QDBusConnectionManager::run (this=0x7f62f8560d40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #13 0x7f62f6ef2ff9 in QThreadPrivate::start (arg=0x7f62f8560d40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:365 #14 0x7f62f44c566d in start_thread () from /lib64/libpthread.so.0 #15 0x7f62f6b89e4d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f62e0d43700 (LWP 5466)): #0 0x7f62f6b7e00d in poll () from /lib64/libc.so.6 #1 0x7f62f7ac7902 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f62f7ac9657 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f62e3a14be9 in QXcbEventReader::run (this=0x14bd6c0) at qxcbconnection.cpp:1331 #4 0x7f62f6ef2ff9 in QThreadPrivate::start (arg=0x14bd6c0) at thread/qthread_unix.cpp:365 #5 0x7f62f44c566d in start_thread () from /lib64/libpthread.so.0 #6 0x7f62f6b89e4d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f62f85c8800 (LWP 5465)): [KCrash Handler] #6 0x7f62f6ac7818 in raise () from /lib64/libc.so.6 #7 0x7f62f6ac8f2a in abort () from /lib64/libc.so.6 #8 0x7f62f6edaf6e in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1648 #9 QMessageLogger::fatal (this=this@entry=0x7fff3b171d30, msg=msg@entry=0x7f62f85486a8 "Internal error: got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") at global/qlogging.cpp:790 #10 0x7f62f84fa739 in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=) at qdbusintegrator.cpp:940 #11 0x7f62f70e23aa in QObject::event (this=0x170b0f0, e=) at kernel/qobject.cpp:1256 #12 0x7f62f596dd0c in QApplicationPrivate::notify_helper (this=, receiver=0x170b0f0, e=0x7f62d400fd10) at kernel/qapplication.cpp:3804 #13 0x7f62f5972e76 in QApplic
[kde] [Bug 383944] Kdeinit5 needs restart after Dolphin is closed after some manipulation on files
https://bugs.kde.org/show_bug.cgi?id=383944 bruno changed: What|Removed |Added Summary|Dolhin crashes at random|Kdeinit5 needs restart |after some manipulation on |after Dolphin is closed |files |after some manipulation on ||files --- Comment #1 from bruno --- Another report Application: kdeinit5 (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5d6a119800 (LWP 3248))] Thread 2 (Thread 0x7f5d50c5d700 (LWP 3250)): [KCrash Handler] #6 0x7f5d68618818 in raise () from /lib64/libc.so.6 #7 0x7f5d68619f2a in abort () from /lib64/libc.so.6 #8 0x7f5d6865743a in __libc_message () from /lib64/libc.so.6 #9 0x7f5d6865e246 in malloc_consolidate () from /lib64/libc.so.6 #10 0x7f5d68661b27 in _int_malloc () from /lib64/libc.so.6 #11 0x7f5d686645b3 in calloc () from /lib64/libc.so.6 #12 0x7f5d6433b3e3 in ?? () from /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.59 #13 0x7f5d652cced1 in g_malloc0 () from /lib64/libglib-2.0.so.0 #14 0x7f5d652e593d in g_slice_free1 () from /lib64/libglib-2.0.so.0 #15 0x7f5d660153d9 in __nptl_deallocate_tsd.part.4 () from /lib64/libpthread.so.0 #16 0x7f5d66016809 in start_thread () from /lib64/libpthread.so.0 #17 0x7f5d686dae4d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5d6a119800 (LWP 3248)): #0 0x7f5d686e832b in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f5d686607d5 in _int_free () from /lib64/libc.so.6 #2 0x7f5d68663db8 in free () from /lib64/libc.so.6 #3 0x7f5d68a45241 in QArrayData::deallocate (data=, objectSize=, alignment=) at tools/qarraydata.cpp:142 #4 0x7f5d68c187e8 in QTypedArrayData::deallocate (data=0x7f5d4400c6f0) at ../../src/corelib/tools/qarraydata.h:222 #5 QVector::freeData (this=, x=0x7f5d4400c6f0) at ../../src/corelib/tools/qvector.h:522 #6 QVector::~QVector (this=, __in_chrg=) at ../../src/corelib/tools/qvector.h:69 #7 (anonymous namespace)::Q_QGS_customTypes::Holder::~Holder (this=, __in_chrg=) at kernel/qmetatype.cpp:570 #8 0x7f5d6861b7af in __cxa_finalize () from /lib64/libc.so.6 #9 0x7f5d68a165f3 in __do_global_dtors_aux () from /lib64/libQt5Core.so.5 #10 0x7ffe716ea7a0 in ?? () #11 0x7f5d69fd5a17 in _dl_fini () from /lib64/ld-linux-x86-64.so.2 Backtrace stopped: frame did not save the PC -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 371697] New: kmail 16.08.2 save sieve script after edit lead to crash
https://bugs.kde.org/show_bug.cgi?id=371697 Bug ID: 371697 Summary: kmail 16.08.2 save sieve script after edit lead to crash Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.8.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was editing (adding rules) to my sieve script. When I click the ok button the indicator apps said script upload successful. and right after that when the account list should be closed, the application completely crash. my autosieve file on server was correctly uploaded, and a .sos copy of previous state was created. Server is dovecot 2.2.25 -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e8b502e00 (LWP 1997))] Thread 50 (Thread 0x7f0c811a3700 (LWP 9099)): #0 0x7f0e88336ad9 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f0e7c43d12a in g_cond_wait_until (cond=cond@entry=0x160e418, mutex=mutex@entry=0x160e410, end_time=end_time@entry=81361281793) at gthread-posix.c:1442 #2 0x7f0e7c3cbc69 in g_async_queue_pop_intern_unlocked (queue=queue@entry=0x160e410, wait=wait@entry=1, end_time=end_time@entry=81361281793) at gasyncqueue.c:422 #3 0x7f0e7c3cc28c in g_async_queue_timeout_pop (queue=0x160e410, timeout=timeout@entry=1500) at gasyncqueue.c:543 #4 0x7f0e7c41fc8d in g_thread_pool_thread_proxy () at gthreadpool.c:167 #5 0x7f0e7c41fc8d in g_thread_pool_thread_proxy (data=) at gthreadpool.c:364 #6 0x7f0e7c41f1c5 in g_thread_proxy (data=0x7f0c78003590) at gthread.c:784 #7 0x7f0e7e1cd454 in start_thread (arg=0x7f0c811a3700) at pthread_create.c:333 #8 0x7f0e8833b39f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 49 (Thread 0x7f0c9700 (LWP 8791)): #0 0x7f0e7c43cea9 in g_mutex_lock (mutex=mutex@entry=0x7f0c98000990) at gthread-posix.c:1336 #1 0x7f0e7c3f6d85 in g_main_context_prepare (context=context@entry=0x7f0c98000990, priority=priority@entry=0x7f0c9fffeb40) at gmain.c:3504 #2 0x7f0e7c3f779b in g_main_context_iterate (context=context@entry=0x7f0c98000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3909 #3 0x7f0e7c3f798c in g_main_context_iteration (context=0x7f0c98000990, may_block=may_block@entry=1) at gmain.c:3990 #4 0x7f0e88e6879b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0c980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f0e88e121ea in QEventLoop::exec(QFlags) (this=this@entry=0x7f0c9fffec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f0e88c408b3 in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f0e88c45558 in QThreadPrivate::start(void*) (arg=0x40be570) at thread/qthread_unix.cpp:344 #8 0x7f0e7e1cd454 in start_thread (arg=0x7f0c9700) at pthread_create.c:333 #9 0x7f0e8833b39f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 48 (Thread 0x7f0cc4cbb700 (LWP 8790)): #0 0x7f0e8833268d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0e7c3f7876 in g_main_context_iterate (priority=, n_fds=1, fds=0x7f0ca4002e20, timeout=, context=0x7f0ca4000990) at gmain.c:4228 #2 0x7f0e7c3f7876 in g_main_context_iterate (context=context@entry=0x7f0ca4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3924 #3 0x7f0e7c3f798c in g_main_context_iteration (context=0x7f0ca4000990, may_block=may_block@entry=1) at gmain.c:3990 #4 0x7f0e88e6879b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0ca40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f0e88e121ea in QEventLoop::exec(QFlags) (this=this@entry=0x7f0cc4cbac80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f0e88c408b3 in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f0e88c45558 in QThreadPrivate::start(void*) (arg=0x15370920) at thread/qthread_unix.cpp:344 #8 0x7f0e7e1cd454 in start_thread (arg=0x7f0cc4cbb700) at pthread_create.c:333 #9 0x7f0e8833b39f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 47 (Thread 0x7f0cc54bc700 (LWP 8789)): #0 0x7f0e7c43cea9 in g_mutex_lock (mutex=mutex@entry=0x7f0ca990) at gthread-posix.c:1336 #1 0x7f0e7c3f6d85 in g_main_context_prepare (context=context@entry=0x7f0ca990, priority=priority@entry=0x7f0cc54bbb40) at gmain.c:3504 #2 0x7f0e7c3f779b in g_ma
[kmail2] [Bug 371697] kmail 16.08.2 save sieve script after edit lead to crash
https://bugs.kde.org/show_bug.cgi?id=371697
--- Comment #2 from Bruno Friedmann ---
Laurent anything else I can retry (full gdb session but only with the useful
component ?)
The only relative sieve events in xsession-erros:-0.log I found are
log_kmanagersieve: "session2" No job for reporting this error message! "Could
not connect to host Unknown error."
QVariant(QString, "Product.get.versions") (QVariant(QVariantMap,
QMap(("products", QVariant(QVariantList, (QVariant(QVariantMap,
QMap(("components", QVariant(QVariantList, (QVariant(QVariantMap,
QMap(("default_assigned_to", QVariant(QString,
"kdepim-b...@kde.org"))("default_qa_contact", QVariant(QString,
""))("description", QVariant(QString, "KMail 2 - commands and actions: Actions
that operate on mails, usually those found in the context menu of the mail
viewer or mail list"))("flag_types", QVariant(QVariantMap, QMap(("attachment",
QVariant(QVariantList, ()))("bug", QVariant(QVariantList,
(QVariant(QVariantMap, QMap(("cc_list", QVariant(QString, ""))("description",
QVariant(QString, "Allows to set flags to bug fixes that need to be
backported."))("grant_group", QVariant(int, 6))("id", QVariant(int,
23))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, false))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString, "Backport"))("sort_key",
QVariant(int, 1, QVariant(QVariantMap, QMap(("cc_list", QVariant(QString,
""))("description", QVariant(QString, "All wishes submitted originating from
the forum Brainstorm"))("grant_group", QVariant(int, 7))("id", QVariant(int,
21))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, true))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString, "Brainstorm"))("request_group",
QVariant(int, 7))("sort_key", QVariant(int, 1, QVariant(QVariantMap,
QMap(("cc_list", QVariant(QString, ""))("description", QVariant(QString, "Bugs
that are not obvious on all setups, only reproducible in very uncommon
settings"))("grant_group", QVariant(int, 6))("id", QVariant(int,
24))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, false))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString, "corner_case"))("sort_key",
QVariant(int, 1, QVariant(QVariantMap, QMap(("cc_list", QVariant(QString,
""))("description", QVariant(QString, "the strings are not
translatable"))("grant_group", QVariant(int, 6))("id", QVariant(int,
20))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, true))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString,
"Translation_missing"))("request_group", QVariant(int, 7))("sort_key",
QVariant(int, 1, QVariant(QVariantMap, QMap(("cc_list", QVariant(QString,
"kde-usabil...@kde.org"))("description", QVariant(QString, "This flag should be
added to all reports that are usability issues"))("grant_group", QVariant(int,
6))("id", QVariant(int, 4))("is_active", QVariant(bool,
true))("is_multiplicable", QVariant(bool, true))("is_requestable",
QVariant(bool, true))("is_requesteeble", QVariant(bool, true))("name",
QVariant(QString, "Usability"))("request_group", QVariant(int, 6))("sort_key",
QVariant(int, 1))("id", QVariant(int, 1591))("is_active",
QVariant(bool, true))("name", QVariant(QString, "commands and
actions"))("sort_key", QVariant(int, 0, QVariant(QVariantMap,
QMap(("default_assigned_to", QVariant(QString,
"kdepim-b...@kde.org"))("default_qa_contact", QVariant(QString,
""))("description", QVariant(QString, "KMail 2 - composer: Everything related
to the composer GUI, including the recipient picker"))("flag_types",
QVariant(QVariantMap, QMap(("attachment", QVariant(QVariantList, ()))("bug",
QVariant(QVariantList, (QVariant(QVariantMap, QMap(("cc_list",
QVariant(QString, ""))("description", QVariant(QString, "Allows to set flags t
[kmail2] [Bug 371006] Printed website uses wrong encoding
https://bugs.kde.org/show_bug.cgi?id=371006 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #1 from Bruno Friedmann --- It's even worse, if the message is text + html. You select view html + image in messageviewer and decide to print it (Maybe an invoice like what paypal send) the print in browser take only the text part. not the last state of messageviewer. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 371006] Printed website uses wrong encoding
https://bugs.kde.org/show_bug.cgi?id=371006 --- Comment #3 from Bruno Friedmann --- What about the new complete integration again directly in kmail ? is it for 16.12 ? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer
https://bugs.kde.org/show_bug.cgi?id=353240 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #6 from Bruno Friedmann --- Created attachment 102213 --> https://bugs.kde.org/attachment.cgi?id=102213&action=edit Month view in HiDPI Dates are cropped, but my xorg dpi is fixed at 192dpi and fonts in systemsettings are also forced to 192dpi. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 355767] KRunner searches for words inside files, but does not find the file that matches the words provided
https://bugs.kde.org/show_bug.cgi?id=355767 Bruno Léon changed: What|Removed |Added CC||bruno.l...@nividic.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 449435] falkon crashes after clicking a link in apdf file
https://bugs.kde.org/show_bug.cgi?id=449435 --- Comment #1 from Bruno Pitrus --- Created attachment 146425 --> https://bugs.kde.org/attachment.cgi?id=146425&action=edit New crash information added by DrKonqi falkon (3.2.0) using Qt 5.15.2 - What I was doing when the application crashed: I have a similar issue. I tried middle-clicking a link in pdf file and the attached crash happens everytime. When left-clicking, the page is opened in same window as expected, but the address bar does not register this. -- Backtrace (Reduced): #5 0x7f6ef41375e0 in QtWebEngineCore::WebContentsDelegateQt::webEngineSettings (this=) at /usr/src/debug/libqt5-qtwebengine-5.15.8-1.1.x86_64/src/core/web_contents_delegate_qt.cpp:879 #6 QtWebEngineCore::ContentBrowserClientQt::CanCreateWindow (this=, opener=, opener_url=..., opener_top_level_frame_url=..., source_origin=..., container_type=, target_url=..., referrer=..., frame_name=..., disposition=WindowOpenDisposition::NEW_FOREGROUND_TAB, features=..., user_gesture=true, opener_suppressed=false, no_javascript_access=0x7ffd35b66957) at /usr/src/debug/libqt5-qtwebengine-5.15.8-1.1.x86_64/src/core/content_browser_client_qt.cpp:744 #7 0x7f6ef8948d2e in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at ../../3rdparty/chromium/content/browser/renderer_host/render_frame_host_impl.cc:4974 #8 0x7f6ef4bbbeed in content::mojom::FrameHostStubDispatch::AcceptWithResponder () at gen/content/common/frame.mojom.cc:7074 #9 0x7f6ef89211af in content::mojom::FrameHostStub >::AcceptWithResponder () at gen/content/common/frame.mojom.h:1025 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 449435] falkon crashes after clicking a link in apdf file
https://bugs.kde.org/show_bug.cgi?id=449435 Bruno Pitrus changed: What|Removed |Added CC||brunopit...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 443586] akonadi_ews_resource crashes when trying to sync hotmail contacts.
https://bugs.kde.org/show_bug.cgi?id=443586 Bruno Pitrus changed: What|Removed |Added Assignee|kdepim-b...@kde.org |kri...@op.pl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449869] New: systemsettings crash when applying configuration to screen and countdown don't popup
https://bugs.kde.org/show_bug.cgi?id=449869
Bug ID: 449869
Summary: systemsettings crash when applying configuration to
screen and countdown don't popup
Product: systemsettings
Version: 5.23.5
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: br...@ioda-net.ch
Target Milestone: ---
Application: systemsettings5 (5.23.5)
Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.16.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I was configuring my second screen, placement right of, position bottom, not
primary.
hit the apply button and the crash occur.
The changes were applied (I mean the screen are configured) but the crash was
there.
I'm using nvidia, and xorg.
Maybe related to 447199
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6 QSharedPointer::data (this=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:301
#7 QSharedPointer::operator-> (this=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:307
#8 KScreen::Config::clone (this=0x0) at
/usr/src/debug/libkscreen2-5.23.5-1.1.x86_64/src/config.cpp:205
#9 0x7f45bc5f4a28 in ConfigHandler::revertConfig (this=0x55e12090b200) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/kcm/config_handler.h:45
#10 KCMKScreen::revertSettings (this=0x55e118a94190) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/kcm/kcm.cpp:99
#11 KCMKScreen::qt_static_metacall (_o=0x55e118a94190, _c=,
_id=, _a=) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/build/kcm/kcm_kscreen_autogen/EWIEGA46WW/moc_kcm.cpp:223
#12 0x7f45bc5f5ebb in KCMKScreen::qt_metacall (this=0x55e118a94190,
_c=QMetaObject::InvokeMetaMethod, _id=22, _a=0x7ffd0a1bf700) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/build/kcm/kcm_kscreen_autogen/EWIEGA46WW/moc_kcm.cpp:425
#13 0x7f45d43bf1cd in QQmlObjectOrGadget::metacall
(this=this@entry=0x7ffd0a1bf940, type=type@entry=QMetaObject::InvokeMetaMethod,
index=, argv=argv@entry=0x7ffd0a1bf700) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/qml/qqmlobjectorgadget.cpp:51
#14 0x7f45d429cd4e in CallMethod (callType=QMetaObject::InvokeMetaMethod,
callArgs=0x7f459cb1d6f0, engine=0x55e11899c660, argTypes=0x0, argCount=0,
returnType=43, index=, object=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1319
#15 CallPrecise (object=..., data=..., engine=engine@entry=0x55e11899c660,
callArgs=callArgs@entry=0x7f459cb1d6f0,
callType=callType@entry=QMetaObject::InvokeMetaMethod) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1573
#16 0x7f45d429ffdb in CallOverloaded (callType=,
propertyCache=, callArgs=, engine=, data=..., object=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1645
#17 QV4::QObjectMethod::callInternal (this=,
thisObject=, argv=, argc=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:2133
#18 0x7f45d42bcc43 in QV4::FunctionObject::call (argc=,
argv=, thisObject=, this=) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4functionobject_p.h:202
#19 QV4::Moth::VME::interpret (frame=0x7ffd0a1bfc00, engine=0x55e11899c660,
code=0x7f459cb1d6a8 "") at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:754
#20 0x7f45d42bf917 in QV4::Moth::VME::exec
(frame=frame@entry=0x7ffd0a1bfc00, engine=engine@entry=0x55e11899c660) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:463
#21 0x7f45d4252d3e in QV4::Function::call (this=this@entry=0x55e1185689c0,
thisObject=, argv=argv@entry=0x7f459cb1d670, argc=, context=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4function.cpp:69
#22 0x7f45d43d9b45 in QQmlJavaScriptExpression::evaluate
(this=this@entry=0x55e118505e10, callData=callData@entry=0x7f459cb1d640,
isUndefined=isUndefined@entry=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/qml/qqmljavascriptexpression.cpp:212
#23 0x7f45d438b8ab in QQmlBoundSignalExpression::evaluate (this=, a=) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4jscall_p.h:95
#24 0x7f45d438ca98 in QQmlBoundSignal_callback (e=0x55e118505e80,
[i18n] [Bug 449338] In the Appearance section of system settings, the last two subsections are named the same
https://bugs.kde.org/show_bug.cgi?id=449338 Bruno P. changed: What|Removed |Added CC||bruno+...@patri.fr --- Comment #4 from Bruno P. --- Here's a suggestion for french translators : - the first entry “Splash Screen” is the splash screen displayed just after login ton graphical session. It should be “Écran d'ouverture de session” or shorter, “Écran de session” in french; - second entry “Boot Splash Screen” is the splash screen displayed at boot. It should be “Écran de démarrage” The same should apply to buttons “Get new (boot) splash screen” HTH -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 449954] New: Elisa crashs while scrolling in album view
https://bugs.kde.org/show_bug.cgi?id=449954 Bug ID: 449954 Summary: Elisa crashs while scrolling in album view Product: Elisa Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: brunoguedes.n...@gmail.com Target Milestone: --- Application: elisa (22.03.70) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-28-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.24.80 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: If I open Elisa on the Album view and scroll down it crashs. If before I start scrolling I change the sorting method at least once it stops crashing until I shutdown the computer. Then when I turn it on again it will crash again. happens in X11 and Wayland The crash can be reproduced sometimes. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [New LWP 9106] [New LWP 9109] [New LWP 9114] [New LWP 9112] [New LWP 9110] [New LWP 9131] [New LWP 9113] [New LWP 9115] [New LWP 9150] [New LWP 9116] [New LWP 9130] [New LWP 9125] [New LWP 9141] [New LWP 9118] [New LWP 9133] [New LWP 9117] [New LWP 9111] [New LWP 9148] [New LWP 9120] [New LWP 9128] [New LWP 9132] [New LWP 9147] [New LWP 9138] [New LWP 9137] [New LWP 9143] [New LWP 9139] [New LWP 9140] [New LWP 9149] [New LWP 9142] [New LWP 9134] [New LWP 9121] [New LWP 9119] [New LWP 9135] [New LWP 9145] [New LWP 9129] [New LWP 9127] [New LWP 9126] [New LWP 9123] [New LWP 9136] [New LWP 9144] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/elisa'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7efccbe269c0 (LWP 9106))] __preamble__ [Current thread is 1 (Thread 0x7efccbe269c0 (LWP 9106))] Thread 40 (Thread 0x7efc58bf9700 (LWP 9144)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7efc58bf8b50, clockid=, expected=0, futex_word=0x7efc7402ef50) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7efc58bf8b50, clockid=, mutex=0x7efc7402ef00, cond=0x7efc7402ef28) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7efc7402ef28, mutex=0x7efc7402ef00, abstime=0x7efc58bf8b50) at pthread_cond_wait.c:656 #3 0x7efcd098 in QWaitConditionPrivate::wait_relative (this=0x7efc7402ef00, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x7efc7402ef00) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x7efc740059a0, mutex=mutex@entry=0x55b78eb54b68, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7efcd0963b71 in QThreadPoolThread::run (this=0x7efc74005990) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7efcd0960543 in QThreadPrivate::start (arg=0x7efc74005990) at thread/qthread_unix.cpp:331 #8 0x7efccf805609 in start_thread (arg=) at pthread_create.c:477 #9 0x7efcd05e0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 39 (Thread 0x7efc627fc700 (LWP 9136)): #0 0x7efcd05d3aff in __GI___poll (fds=0x7efc3c005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7efccec8c36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efccec8c4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efcd0ba19f2 in QEventDispatcherGlib::processEvents (this=0x7efc3c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7efcd0b45c9b in QEventLoop::exec (this=this@entry=0x7efc627fbbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7efcd095f362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7efcd0960543 in QThreadPrivate::start (arg=0x55b78f7f9ab0) at thread/qthread_unix.cpp:331 #7 0x7efccf805609 in start_thread (arg=) at pthread_create.c:477 #8 0x7efcd05e0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 38 (Thread 0x7efc8effd700 (LWP 9123)): #0 0x7efcd05d3aff in __GI___poll (fds=0x7efc78004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7efccec8c36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efccec8c4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efcd0ba19f2 in QEventDispatcherGlib::processEvents (this=0x7efc78000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7efcd0b45c9b in QEventLoop::exec (this=this@entry=0x7efc8effcbc0, flags=..., fl
[Akonadi] [Bug 450428] New: akonadi repeatedly crashes when displaying e-mails
https://bugs.kde.org/show_bug.cgi?id=450428 Bug ID: 450428 Summary: akonadi repeatedly crashes when displaying e-mails Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: b...@schwarzwald-software.de Target Milestone: --- Application: akonadiserver (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-150300.59.49-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.3" -- Information about the crash: - What I was doing when the application crashed: Started kmail Fetched new mails, configured are 5 POP accounts Automatic filtering seemed to work Double clicked on a new mail The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 qHash (key=..., seed=541514072) at tools/qhash.cpp:239 #5 0x5596534831cb in QHash::findNode (this=this@entry=0x559654258098, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:934 #6 0x55965348383a in QHash::remove (this=this@entry=0x559654258098, akey=...) at /usr/include/qt5/QtCore/qhash.h:806 #7 0x55965348088f in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x559654258060, request=0x7f1f5418c900, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/itemretrievalmanager.cpp:179 #8 0x7f1fecea4fcf in QtPrivate::QSlotObjectBase::call (a=0x7f1fe1405700, r=0x559654258060, this=0x7f1fdc01c150) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #9 QMetaObject::activate (sender=sender@entry=0x7f1fdc01fb90, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f1fe1405700) at kernel/qobject.cpp:3784 #10 0x7f1fecea55c7 in QMetaObject::activate (sender=sender@entry=0x7f1fdc01fb90, m=m@entry=0x5596537701c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f1fe1405700) at kernel/qobject.cpp:3657 #11 0x5596534d1784 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x7f1fdc01fb90, _t1=, _t2=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:135 #12 0x55965348400e in Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7f1fdc01fb90, watcher=) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/itemretrievaljob.cpp:76 #13 0x7f1fecea4fcf in QtPrivate::QSlotObjectBase::call (a=0x7f1fe14058f0, r=0x7f1fdc01fb90, this=0x7f1fcc007400) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #14 QMetaObject::activate (sender=0x7f1f5405b900, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f1fe14058f0) at kernel/qobject.cpp:3784 #15 0x7f1fecea55c7 in QMetaObject::activate (sender=, m=m@entry=0x7f1fed7fe5c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f1fe14058f0) at kernel/qobject.cpp:3657 #16 0x7f1fed5e1dcf in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:157 #17 0x7f1fecea5a62 in QObject::event (this=0x7f1f5405b900, e=) at kernel/qobject.cpp:1261 #18 0x7f1fece75391 in doNotify (event=0x7f1fdc01f4a0, receiver=0x7f1f5405b900) at kernel/qcoreapplication.cpp:1178 #19 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1164 #20 QCoreApplication::notifyInternal2 (receiver=0x7f1f5405b900, event=0x7f1fdc01f4a0) at kernel/qcoreapplication.cpp:1088 #21 0x7f1fece7557e in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7f1fdc01f4a0) at kernel/qcoreapplication.cpp:1476 #22 0x7f1fece77f67 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55965426c2f0) at kernel/qcoreapplication.cpp:1825 #23 0x7f1fece78508 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1679 #24 0x7f1feced2e13 in postEventSourceDispatch (s=0x7f1fcc004bc0) at kernel/qeventdispatcher_glib.cpp:276 #25 0x7f1fe8981694 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x7f1fe8981a30 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x7f1fe8981abc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x7f1feced242f in QEventDispatcherGlib::processEvents (this=0x7f1fcc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #29 0x7f1fece735fa in QEventLoop::exec (this=this@entry=0x7f1fe1405ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #30 0x7f1fecc9898a in QThread::exec (this=) at thread/qthread.cpp:531 #31 0x7f1f
[kwin] [Bug 454792] New: Is it possible to stop rendering all the windows that are behind the windows in fullscreen?
https://bugs.kde.org/show_bug.cgi?id=454792 Bug ID: 454792 Summary: Is it possible to stop rendering all the windows that are behind the windows in fullscreen? Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bigbr...@gmail.com Target Milestone: --- Is it possible to stop rendering all the windows that are behind the windows in fullscreen? The reason is that, for example, if a video is playing on youtube in the browser and a game is open in full screen, the video continues to render and consume more processing than it should, but if you minimize the browser the rendering of the video stops and keep only the audio. I noticed it first playing Street Fighter, I noticed that the FPS was lower when I had some video playing on youtube while I was playing, so I tried to leave it minimized and it didn't lose FPS. So I tested it with OBS Studio, I left it recording the browser with a video playing on Youtube, when I minimized the window, OBS started recording a static image. I believe this is not really a bug, but an implementation of this type can help many people who have started to play using Linux -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454915] New: Discover freezes when selecting the about menu
https://bugs.kde.org/show_bug.cgi?id=454915 Bug ID: 454915 Summary: Discover freezes when selecting the about menu Product: Discover Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: lenno...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open discover 2. Select "About" menu option on the left 3. OBSERVED RESULT CPU usage increases and plasma-discover remains top of the list when running "Top" in konsole. Discover becomes non responsive to any clicks appart from minimise window and close EXPECTED RESULT Displays the about menu items and cpu usage dosen't shoot up to 100% and the hyperlinks and item in the discover windows are clickable and function as well as being able to then select anther menu item in Discover (i.e. Settings) and it changes to that menu item SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE spin - 5.24.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.93 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466254] Error while installing package 'libjpeg.so.8.2.2' - latest release
https://bugs.kde.org/show_bug.cgi?id=466254 Bruno Santos changed: What|Removed |Added CC||bsan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #49 from Bruno Friedmann --- I've been "forced" to move now to wayland to get the per screen scale factor as it will never be implemented on X11. But loosing restore session is a pain. It seems we miss a global review on plasma development, with clear objectives for each release, to make all users (and developers) happy. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397083] Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe
https://bugs.kde.org/show_bug.cgi?id=397083
Bruno Haible changed:
What|Removed |Added
CC||br...@clisp.org
--- Comment #2 from Bruno Haible ---
I'm still seeing this on Ubuntu 22.04, with valgrind 3.18.1.
= foo.c
#include
#include
int main ()
{
wchar_t *s = (wchar_t *) malloc (8 * sizeof (wchar_t));
s[0] = '-';
s[1] = 'N';
s[2] = 'A';
s[3] = 'N';
s[4] = ' ';
s[5] = '3';
s[6] = '3';
s[7] = '\0';
return wmemcmp (s + 1, L"NAN", 3) == 0;
}
===
$ gcc -ggdb foo.c
$ valgrind ./a.out
==2109475== Memcheck, a memory error detector
==2109475== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2109475== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==2109475== Command: ./a.out
==2109475==
==2109475== Invalid read of size 32
==2109475==at 0x4A1C55D: __wmemcmp_avx2_movbe (memcmp-avx2-movbe.S:413)
==2109475==by 0x10920D: main (foo.c:15)
==2109475== Address 0x4aa6044 is 4 bytes inside a block of size 32 alloc'd
==2109475==at 0x4848899: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==2109475==by 0x10917E: main (foo.c:6)
==2109475==
...
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 397083] Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe
https://bugs.kde.org/show_bug.cgi?id=397083 Bruno Haible changed: What|Removed |Added Version|3.13.0 |3.18.1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 424044] long double issue: isinf(strtold("+inf", NULL)) != 1
https://bugs.kde.org/show_bug.cgi?id=424044
Bruno Haible changed:
What|Removed |Added
Platform|unspecified |Ubuntu
Version|unspecified |3.18.1
CC||br...@clisp.org
--- Comment #1 from Bruno Haible ---
The problem is with the isinf call. In this test case
#include
#include
long double x;
int main ()
{
x = 1.0L / 0.0L;
printf ("%d %La %d\n", !!isinf (x), x, 33);
return 0;
}
we have two isinf calls:
1) in main,
2) inside glibc's fprintf routines, more exactly in
glibc/stdio-common/printf_fphex.c, macro PRINTF_FPHEX_FETCH, line 109.
Both return 1 when run natively, but 0 when run under valgrind.
$ ./a.out
1 inf 33
$ valgrind ./a.out
0 0x8p+16381 33
Valgrind version: 3.18.1
Architecture: x86_64
OS: Linux 5.15.0 (Ubuntu 22.04)
GCC: 11.3
CPU: AMD Ryzen 7 4800U
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 457070] Crash when closing dolphin
https://bugs.kde.org/show_bug.cgi?id=457070 Bruno Hivert changed: What|Removed |Added CC||prun...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457070] Crash when closing dolphin
https://bugs.kde.org/show_bug.cgi?id=457070 --- Comment #1 from Bruno Hivert --- Created attachment 152074 --> https://bugs.kde.org/attachment.cgi?id=152074&action=edit New crash information added by DrKonqi dolphin (19.12.3) using Qt 5.12.8 - What I was doing when the application crashed: I had another directory open in a split tab, and closed the split tab -- Backtrace (Reduced): #8 0x7fe8915a88ac in UpdateItemStatesThread::run (this=0x563dd298db40) at ./src/views/versioncontrol/updateitemstatesthread.cpp:54 #9 0x7fe88f40f9d2 in QThreadPrivate::start (arg=0x563dd298db40) at thread/qthread_unix.cpp:361 #10 0x7fe88de60609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fe89171f133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397083] Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe
https://bugs.kde.org/show_bug.cgi?id=397083 --- Comment #7 from Bruno Haible --- (In reply to Paul Floyd from comment #5) > Created attachment 158110 [details] There's a small issue here: ISO C allows all possible wchar_t values to occur in the arrays passed to wmemcmp(), and requires that the comparison be done w.r.t. the order in the underlying integer type 'wchar_t'. For more on this topic, please see https://www.openwall.com/lists/musl/2023/04/18/5 and https://lists.gnu.org/archive/html/bug-gnulib/2023-04/msg00145.html . Regarding your patch, this means that the line Int res = a0 - b0; \ should be replaced with something that does not assume that a0 and b0 are in the range 0..INT_MAX. For example, Int res = (a0 > b0) - (a0 < b0); (This expression on the right-hand side has the noce property that it does not produce conditional jumps with GCC. See https://lists.gnu.org/archive/html/bug-gnulib/2020-07/msg00109.html .) Additionally, watch out: wchar_t is signed (i.e. equivalent to int32_t) on most platforms. However it is unsigned (i.e. equivalent to uint32_t) on arm64 platforms (on glibc, musl libc, FreeBSD, but not on macOS). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397083] Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe
https://bugs.kde.org/show_bug.cgi?id=397083 --- Comment #14 from Bruno Haible --- (In reply to Paul Floyd from comment #13) > I left wmemcmp alone and just added a simple wmemchr wrapper, Linux only. Actually, looking at your commit, you left wmemchr alone and added a simple wmemcmp wrapper. Thanks! That should solve my issue. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error
https://bugs.kde.org/show_bug.cgi?id=469599 Bruno P. changed: What|Removed |Added CC||bruno+...@patri.fr --- Comment #20 from Bruno P. --- As workaround you could downgrade the package libkf5textautocorrection1 to previous versio. Here's the command for kde neon user edition : sudo apt install libkf5textautocorrection1=1.2.0-0xneon+22.04+jammy+release+build1 It seems that we need the next KDE gear update (ktextaddons 1.3) : https://kde.org/announcements/changelogs/gear/23.04.1/ -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error
https://bugs.kde.org/show_bug.cgi?id=469599 Bruno P. changed: What|Removed |Added CC|bruno+...@patri.fr | -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415956] Akonadi 19.12.x crash when socket file for connection to postgresql database disappear
https://bugs.kde.org/show_bug.cgi?id=415956 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Bruno Friedmann --- Seems fixed with actual version Version 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422433] akonadi constanly crash when updating database (due to rollback)
https://bugs.kde.org/show_bug.cgi?id=422433 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bruno Friedmann --- Works at least with openSUSE Tumbleweed - 20220930 Linux 5.19.12-1-default x86_64 GNU/Linux nvidia: 515.65.01 Qt: 5.15.6 KDE Frameworks: 5.98.0 Plasma: 5.25.5 kmail2 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
