[dolphin] [Bug 483571] [Regression] Dolphin Incompatible with Alliance for Open Media (AOM) Compressed AVIF files (but OK for some others).
https://bugs.kde.org/show_bug.cgi?id=483571 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #1 from Sadi --- Worse here. I can't see any preview, thumbnail, nothing in Dolphin and GwenView, but Krita can open. All associated packages (and even more are) have been installed: kimageformats, libavif-bin, libavif-gdk-pixbuf, libavif15, libavif16, shared-mime-info) Dolphin version: 23.08.1 Operating System: Debian Trixie (Testing) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 485596] Crashing after a short while unless Waveform pane is disabled
https://bugs.kde.org/show_bug.cgi?id=485596 --- Comment #2 from Sadi --- (In reply to Mladen Milinkovic, Max from comment #1) Thanks; it seems you're right. I've just tested the appimages at "https://subtitlecomposer.kde.org/download.html;. The stable version had the same problem, but the latest git development version worked without any such problem. -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 485596] New: Crashing after a short while unless Waveform pane is disabled
https://bugs.kde.org/show_bug.cgi?id=485596 Bug ID: 485596 Summary: Crashing after a short while unless Waveform pane is disabled Classification: Applications Product: subtitlecomposer Version: 0.8.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: max...@smoothware.net Reporter: sadiyumu...@gmail.com Target Milestone: --- SUMMARY If I start to edit a subtitle file Subtitle Composer crashes when I move forward by scrolling in the "Media player" pane or by clicking on different lines of the subtitle file in the main pane. However, it doesn't crash if the application is used without enabling the "Waveform", and sufficing to hear the audio simply from the "Media player" pane. SOFTWARE/OS VERSIONS Operating System: Debian 13 (Trixie/testing branch) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION: Terminal output is provided below. Loaded SpeechPlugin "PocketSphinx" from "/usr/lib/x86_64-linux-gnu/subtitlecomposer/pocketsphinxasr.so" qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2889, resource id: 15094468, major code: 40 (TranslateCoords), minor code: 0 Input #0, srt, from '.srt': Duration: N/A, bitrate: N/A Stream #0:0: Subtitle: subrip [AVIOContext @ 0x55914515cc80] Statistics: 58739 bytes read, 0 seeks Input #0, matroska,webm, from '.webm': Metadata: ENCODER : Lavf60.3.100 Duration: 01:55:10.37, start: 0.00, bitrate: 309 kb/s Stream #0:0(eng): Video: vp9 (Profile 0), 1 reference frame, yuv420p(tv, smpte170m/bt470bg/bt709), 576x360, SAR 1:1 DAR 8:5, 25 fps, 25 tbr, 1k tbn (default) Metadata: DURATION: 01:55:10.32000 Stream #0:1(eng): Audio: opus, 48000 Hz, stereo, fltp, delay 312 (default) Metadata: DURATION: 01:55:10.36800 [W][25724.400560] pw.conf | [ conf.c: 1016 try_load_conf()] can't load config client-rt.conf: No such file or directory [E][25724.400637] pw.conf | [ conf.c: 1045 pw_conf_load_conf_for_context()] can't load config client-rt.conf: No such file or directory [ALSOFT] (EE) Failed to create PipeWire event context (errno: 2) GL API: OpenGL Desktop 4.6 (compiled for OpenGL Desktop) OpenGL version: 4.6 (Compatibility Profile) Mesa 23.3.5-1 GLSL version: 4.60 Input #0, matroska,webm, from '.webm': Metadata: ENCODER : Lavf60.3.100 Duration: 01:55:10.37, start: 0.00, bitrate: 309 kb/s Stream #0:0(eng): Video: vp9 (Profile 0), 1 reference frame, yuv420p(tv, smpte170m/bt470bg/bt709), 576x360, SAR 1:1 DAR 8:5, 25 fps, 25 tbr, 1k tbn (default) Metadata: DURATION: 01:55:10.32000 Stream #0:1(eng): Audio: opus, 48000 Hz, stereo, fltp, delay 312 (default) Metadata: DURATION: 01:55:10.36800 [opus @ 0x559145016f80] Could not update timestamps for skipped samples. Color range: tv(1); primaries: bt470bg(5); xfer: bt709(1); space: smpte170m(6); depth: 8 30 -- exe=/usr/bin/subtitlecomposer 13 -- platform=xcb 11 -- display=:0 25 -- appname=subtitlecomposer 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=37317 17 -- appversion=0.8.0 30 -- programname=Subtitle Composer 31 -- bugaddress=sub...@bugs.kde.org KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = subtitlecomposer path = /usr/bin pid = 37317 KCrash: Arguments: /usr/bin/subtitlecomposer KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi Error reading packet Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor Invalid write to eventfd: Bad file descriptor Code should not be reached at ../src/pulsecore/fdsem.c:188, function pa_fdsem_post(). Aborting. Unable to start Dr. Konqi Re-raising signal for core dump handling. [1]37317 IOT instruction (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472674] Media Player applet should become more full-featured (e.g. show the control buttons) when placed on a thick enough panel
https://bugs.kde.org/show_bug.cgi?id=472674 --- Comment #3 from Sadi --- Created attachment 168251 --> https://bugs.kde.org/attachment.cgi?id=168251=edit Media Player with KDE Connect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472674] Media Player applet should become more full-featured (e.g. show the control buttons) when placed on a thick enough panel
https://bugs.kde.org/show_bug.cgi?id=472674 --- Comment #2 from Sadi --- I'd like to add one more feature to the wishlist: transferring album art (instead of the currently used KDE Connect icon) from KDE Connect when it's the current/active media player displayed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484746] New: Media Player applet inactive state is buggy
https://bugs.kde.org/show_bug.cgi?id=484746 Bug ID: 484746 Summary: Media Player applet inactive state is buggy Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 167935 --> https://bugs.kde.org/attachment.cgi?id=167935=edit Inactive state of Media Player and Media Player Plus widgets SUMMARY I've stopped using the Media Player widget that comes as part of KDE Plasma, and switched to the Media Player+ widget because I think it's what KDE Plasma's default Media Player widget should be. It not only offers a better, more feature-rich, and customizable interface for wider panels (e.g. a sidebar on the right edge of the screen), but also behaves and looks better (and not buggy) when inactive. When inactive, KDE Plasma's integrated Media Player widget not only displays a large symbolic icon (media-play-stop or media-playback-paused), but also fails to display the context menu (Show Alternatives / Add Widgets / Enter Edit Mode), which must be a BUG. In that state, Media Player+ however not only displays the expected context menu, including an option to configure the widget, but also it doesn't display such a meaningless large symbolic icon in the place reserved for album art, keeping it blank with only a caption "No media playing" below. I hope KDE Plasma developers team takes some action about the future development of this widget as part of KDE Plasma in view of this. SOFTWARE/OS VERSIONS Debian Trixie KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481624] Icons-only Task Manager fails to display custom Actions properly
https://bugs.kde.org/show_bug.cgi?id=481624 --- Comment #2 from Sadi --- (In reply to Nate Graham from comment #1) > After you make your changes in step 4, are you remembering to run > `kbuildsycoca5` and then restart Plasma? These steps are required whenever > you make manual changes to the .desktop files of any of your apps. Oh, sorry, I didn't know that! It even warns about any errors in .desktop files! My problem is solved now, thanks. However, FYI, this problem still exists for "systemsettings.desktop" only, but I've got around it by using "kdesystemsettings.desktop" instead. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481624] New: Icons-only Task Manager fails to display custom Actions properly
https://bugs.kde.org/show_bug.cgi?id=481624 Bug ID: 481624 Summary: Icons-only Task Manager fails to display custom Actions properly Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY *** I use the Icons-only Task Manager applet as one of the main components of my desktop and panel layout, displaying not only some frequently used apps but other apps, scripts, etc. in the same category. For instance, adding Elisa with custom Actions to make Kdenlive, Kid3, Subtitle Composer, etc. available in the context menu as well by either pinning or drag-n-drop... However, this no longer works with some apps: it started first with "System Settings" and then "Elisa". Another problem that has arisen recently is that when I change custom Actions or even just their order, the context menu of the app icon pinned to the Icons-only Task Manager fails to update for a long time (hours or even days), and I can't figure out how and when it finally decides to update. *** STEPS TO REPRODUCE 1. Copy the .desktop files "org.kde.discover.desktop", "org.kde.dolphin.desktop", "org.kde.elisa.desktop" and "systemsettings.desktop" to "~/.local/applications/". 2. Add some customs Actions, including other apps in more or less the same category to the newly created local files. 3. Add these apps to the Icons-only Task Manager on a panel either by running and pinning or by drag-n-drop. 4. Next, make some changes like adding, removing some custom Actions, and changing their order. OBSERVED RESULT 1. Custom Actions added to "org.kde.elisa.desktop" and "systemsettings.desktop" don't take effect after step 3, although they can be seen in the context menu displayed when the .desktop file is right-clicked. 2. Custom Actions in "org.kde.discover.desktop" and "org.kde.dolphin.desktop" are displayed, but changes made later don't take effect promptly after step 4, although they can be seen in the context menu displayed when the .desktop file is right-clicked. EXPECTED RESULT 1. It should be possible to add custom Actions to all .desktop files even if they include their own default Actions displayed in the context menu. 2. All changes in the Actions in .desktop files should be reflected in its context menu. SOFTWARE/OS VERSIONS Operating System: Debian Trixie/Testing KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434116] De-maximizing a window that was maximized on launch positions it according to the placement mode even if the window wants to position itself
https://bugs.kde.org/show_bug.cgi?id=434116 Sadi changed: What|Removed |Added CC|sadiyumu...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477623] Default setting in Mouse Actions section of Desktop Folder Settings
https://bugs.kde.org/show_bug.cgi?id=477623 --- Comment #2 from Sadi --- (In reply to Nate Graham from comment #1) Thanks! I look forward to using Plasma 6 soon. :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477623] New: Default setting in Mouse Actions section of Desktop Folder Settings
https://bugs.kde.org/show_bug.cgi?id=477623 Bug ID: 477623 Summary: Default setting in Mouse Actions section of Desktop Folder Settings Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 If you wish to open Application Launcher upon clicking anywhere on the Desktop, for example, by pressing the Middle-Button of the mouse, you would normally right click on the Desktop, and select "Configure Desktop and Wallpaper...", go to "Mouse Actions", click "Add Action", press the Middle-Button of your mouse, and then select "Application Launcher" - that's all. After this, when you press the middle-button of your mouse on the Desktop, you'll see the Application Launcher menu displayed, but a little differently then you would normally expect: your applications are listed with their generic names (e.g. several apps listed simply as "Web Browser", which you can distinguish only with their different icons), and probably sorted according to the alphabetical order of their names, which might be another confusing factor. This can be fixed by going back to that configuration window, clicking on the settings button to the right of the Application Launcher, and selecting "Show application by name", which the only setting available, but unfortunately left deselected. IMHO it would be much better if this setting could be selected/enabled by default. Operating System: Debian Testing KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428180] A shell script to rename files, which works perfectly in terminal, leaves a leading space in filename
https://bugs.kde.org/show_bug.cgi?id=428180
--- Comment #13 from Sadi ---
(In reply to fanzhuyifan from comment #12)
Oh, thank you so much!
I've revised my script as per your advice, and it's working perfectly now:
for filename in "${@}"; do
source_dir="$(dirname "$filename")"
source_file="$(basename "$filename")"
cd "$source_dir"
rename 's/[*\n<|>[\]]/ /g; s/\?//g; s/!//g; s/"//g; s/\\/ /g; s/ ,/,/g;
s/:/-/g; s/\s\s*/ /g; s/^\s\s*//; s/\s\s*\./\./g; '"s/'//g" "$source_file"
done
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 471981] Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 --- Comment #14 from Sadi --- (In reply to Nate Graham from comment #13) > Ok, let us know if and when you're able to provide the requested info. > Thanks! Oh, I think I did provide the requested info above...or did I miss anything? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471981] Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 --- Comment #12 from Sadi --- (In reply to Nate Graham from comment #11) Thanks... I'll also continue trying to find what's getting in the way of SDDM while it's possible to log into Wayland from the command line. It's not a priority for me though as Wayland is still very far from being ready for my daily use. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471981] Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 --- Comment #10 from Sadi --- (In reply to Nate Graham from comment #9) I removed those 3 lines from "~/.config/environment.d/user.conf", and restarted the computer, but nothing changed unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471981] Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 --- Comment #8 from Sadi --- (In reply to Nate Graham from comment #7) Below is the output of `diff Env-NewUser.txt Env-Me.txt`. I sorted the text alphabetically, and removed differences of user name and id in order to simplify the comparison. 0a1 > CLUTTER_IM_MODULE=ibus 9a11,12 > GTK_IM_MODULE=ibus > GTK_MODULES=gail:atk-bridge 12,13c15,17 < INVOCATION_ID=a59daf71f3094834bd645a3672d3fda9 < JOURNAL_STREAM=8:387821 --- > IM_CONFIG_PHASE=1 > INVOCATION_ID=37ca9e6b1c58415585b66ba928d126ad > JOURNAL_STREAM=8:27510 14a19 > KDE_FORK_SLAVES=1 18c23 < KONSOLE_DBUS_SERVICE=:1.39 --- > KONSOLE_DBUS_SERVICE=:1.92 38,39c43,44 < MANAGERPID=37900 < MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service/memory.pressure --- > MANAGERPID=1396 > MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kglobalaccel.service/memory.pressure 40a46 > MOZ_USE_XINPUT2=1 44a51,52 > PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket > PAPERSIZE=a4 50a59,60 > QT_EXCLUDE_GENERIC_BEARER=1 > QT_IM_MODULE=ibus 52d61 < SESSION_MANAGER=local/Kdebian:@/tmp/.ICE-unix/38040,unix/Kdebian:/tmp/.ICE-unix/38040 54c63 < SHELL_SESSION_ID=4363399071c7460299a95587a4e59369 --- > SHELL_SESSION_ID=1371aac3e41d4f319eee902e3a7c08a1 56,58c65,67 < SSH_AGENT_PID=37968 < SSH_AUTH_SOCK=/tmp/ssh-RKJrPtE0vVb7/agent.37930 < SYSTEMD_EXEC_PID=38083 --- > SSH_AGENT_PID=1469 > SSH_AUTH_SOCK=/tmp/ssh-hiKLb8oiPlMX/agent.1416 > SYSTEMD_EXEC_PID=1714 61,62c70,71 < WINDOWID=52428813 < XAUTHORITY=/tmp/xauth_FHdwYK --- > WINDOWID=96469005 > XAUTHORITY=/tmp/xauth_tQLYBE 66a76 > XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share/:/usr/share/ 72,73c82,83 < XDG_SESSION_ID=71 < XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session32 --- > XDG_SESSION_ID=1 > XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 75a86 > XMODIFIERS=@im=ibus -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471981] Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 --- Comment #6 from Sadi --- (In reply to Nate Graham from comment #4) No, it behaves exactly the same after I log out, or restart, or shut down the computer. It seems the problem is somewhere in my home directory (maybe a user configuration file in ~/.config directory?) but I can't think of anything that I've made there which might prevent launching a Wayland session... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471981] Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 --- Comment #5 from Sadi --- (In reply to Vlad Zahorodnii from comment #3) 1. Yes, a Konsole window did open. 2. I might have modified several system files, but I don't think they're related with this, and the fact that I can log in to a Wayland session when I create a new user might support this assumption. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431165] Consistent Titlebar and Notification OSD Header look and behavior
https://bugs.kde.org/show_bug.cgi?id=431165 --- Comment #3 from Sadi --- When the time comes for this, I hope the position of such buttons (including tab close buttons) can also follow the titlebar button layout, so that they move to the left when the user chooses "Mac-style" titlebar button layout. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471981] Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 --- Comment #2 from Sadi --- This time I experienced something new: Although SDDM still refuses to launch a Wayland session for me (but not any other newly created user), when I switched to terminal with Ctrl+Alt+F3 from SDDM login screen, and entered the command "XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland" I was surprised to find myself in a Wayland session with all my startup apps, customization, settings etc. working - except the panels! I don't know if it's the right thing to do, but I then went on using the Meta key to launch Konsole. The command "echo $DEBUGINFOD_URLS" successfully displayed "https://debuginfod.debian.net; this time, and the command "gdb /usr/bin/startplasma-wayland" also worked, asking "Enable debuginfod for this session? (y or [n])", and then "Downloading separate debug info for" many items. This was followed with the following (slightly abbreviated) terminal output: [New Thread 0x703ff6c0 (LWP 12161)] [Detaching after fork from child process 12163] [Detaching after fork from child process 12183] kdeinit5: Shutting down running client. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 12217, result = 0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :1 Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_mouse.so" Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so" org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0 Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_touchpad.so" Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_kgamma.so" Xlib XKB extension major= 1 minor= 0 kde.xembedsniproxy: failed to claim ownership of Systray Manager kde.dbusmenuproxy: Failed to register DBus service "org.kde.plasma.gmenu_dbusmenu_proxy" Themes not available. Install qt-material if you want to change GUI's appearance: pip3 install qt-material. Checking screens: available: (QScreen(0x55658770, name="eDP-1")) redundant: QHash((QScreen(0x5565a930, name="DP-1"), QScreen(0x55658770, name="eDP-1"))) fake: QSet() all: (QScreen(0x5565a930, name="DP-1"), QScreen(0x55658770, name="eDP-1")) DevTools listening on ws://127.0.0.1:38887/devtools/browser/8f4a80ad-0825-4467-b105-821d25f7b006 DesktopNotifications not available (install python3-notify2): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. exception loading ipasn db: No module named 'pyasn' Install python3-pyasn to display IP's network name. DesktopNotifications not available (install python3-notify2): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. I then opened a new tab in Konsole and entered the command "coredumpctl --reverse" which displayed the following (TIME and SIZE columns removed), with no kwin_wayland crash: PID UID GID SIG COREFILE EXE 7346 1000 1000 SIGTRAP present /walc 6241 1000 1000 SIGABRT present /tmp/.mount_WALC3wzHqC/walc 6211 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6183 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6179 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 6139 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 6095 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6089 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 5807 1000 1000 SIGABRT present /usr/lib/insync/insync 6057 1000 1000 SIGABRT present /usr/bin/plasmashell 6059 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 6020 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6018 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 5923 1000 1000 SIGABRT present /usr/bin/plasmashell 5973 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 5908 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 5640 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 5662 1000 1000 SIGABRT present /usr/bin/python3.11 5831 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 5650 1000 1000 SIGABRT present /us
[plasmashell] [Bug 473714] Global Menu sometimes shows menu from non-active app
https://bugs.kde.org/show_bug.cgi?id=473714 --- Comment #7 from Sadi --- Created attachment 161620 --> https://bugs.kde.org/attachment.cgi?id=161620=edit MacOS Ventura with the same orphan menu problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473714] Global Menu sometimes shows menu from non-active app
https://bugs.kde.org/show_bug.cgi?id=473714 --- Comment #6 from Sadi --- I've just noticed that MacOS 13 (Ventura) oddly has the same problem, too - if this means anything. ;-) -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 452905] kdialog --progressbar doesn't show completed status and custom icon
https://bugs.kde.org/show_bug.cgi?id=452905 --- Comment #2 from Sadi --- I can confirm that icon problem is still with us. It's odd to see X-Window icon here. However, I haven't experienced the other problem. The use of kdialog progressbar is too complicated for me, but I have produced a kind of template copied below from one of the examples of its successful use I've seen somewhere. I don't know why but this doesn't work with ZSH shell although it works with BASH shell. progress=$(kdialog --icon "globe" --title "Test" --progressbar "Starting..."); qdbus $progress Set "" maximum 4 > /dev/null; qdbus $progress Set "" value 1 > /dev/null; qdbus $progress setLabelText "Step 1/4" > /dev/null; sleep 2 qdbus $progress Set "" value 2 > /dev/null; qdbus $progress setLabelText "Step 2/4" > /dev/null; sleep 2 qdbus $progress Set "" value 3 > /dev/null; qdbus $progress setLabelText "Step 3/4" > /dev/null; sleep 2 qdbus $progress Set "" value 4 > /dev/null; qdbus $progress setLabelText "Completed!" > /dev/null; sleep 2 qdbus $progress close > /dev/null; - Operating System: Debian Testing KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 452905] kdialog --progressbar doesn't show completed status and custom icon
https://bugs.kde.org/show_bug.cgi?id=452905 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #1 from Sadi --- Created attachment 161299 --> https://bugs.kde.org/attachment.cgi?id=161299=edit kdialog progressbar vs msgbox icon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473714] Global Menu sometimes shows menu from non-active app
https://bugs.kde.org/show_bug.cgi?id=473714 --- Comment #4 from Sadi --- Created attachment 161256 --> https://bugs.kde.org/attachment.cgi?id=161256=edit Window Title displaying Elisa only when its window is active -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473714] Global Menu sometimes shows menu from non-active app
https://bugs.kde.org/show_bug.cgi?id=473714 --- Comment #3 from Sadi --- Created attachment 161255 --> https://bugs.kde.org/attachment.cgi?id=161255=edit Global Menu still showing Elisa menu after it's minimized while Window Title area becomes blank -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473714] Global Menu sometimes shows menu from non-active app
https://bugs.kde.org/show_bug.cgi?id=473714 --- Comment #2 from Sadi --- (In reply to Nate Graham from comment #1) > When it's in this state, is another app active? Or is Plasma itself active? Case 1: AFAIK it happens only during login when Elisa starts from an autostart script that merely launches the app, waits 2 seconds, and then executes: xdotool windowminimize `xdotool getactivewindow` At this time there's no active app window, although there are some other apps minimized or closed to system tray (unfortunately Elisa doesn't have these features ; -) Naturally, it doesn't happen when Elisa minimized resulting in another open app window automatically takes over the active state. Case 2: It happens when there is another app window open. Apparently, Global Menu applet either doesn't realize that Synaptic is the new active app window, or wrongly decides to keep the previous active app menu because it can't get any menu information from Synaptic. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 473714] New: Global Menu sometimes shows menu from non-active app
https://bugs.kde.org/show_bug.cgi?id=473714 Bug ID: 473714 Summary: Global Menu sometimes shows menu from non-active app Classification: Plasma Product: kdeplasma-addons Version: 5.27.7 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com Target Milestone: --- This has been around for some time actually, and there are two different problems probably related to the same issue. 1) I have a startup script that launches Elisa and then immediately minimizes its window upon login. But the Global Menu applet still displays its menu. However, Window Title applet doesn't do that, e.g. after Elisa is minimized, its title goes off. 2) Sometimes Global Menu displays the previous active app menu when it can't show any menu from the current, which happens with some (not all) GTK apps, like Synaptic Package Manager. For instance, when I launch Synaptic while there's an active Dolphin window, Global Menu still displays its menu when the active window is Synaptic. However, Window Title applet doesn't do that, e.g. it replaces Dolphin with Synaptic Package Manager, while the menu following this title is from Dolphin window behind the active Synaptic app window. SOFTWARE/OS VERSIONS Operating System: Debian Testing KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472739] New: Rendering dialog box autoclose option
https://bugs.kde.org/show_bug.cgi?id=472739 Bug ID: 472739 Summary: Rendering dialog box autoclose option Classification: Applications Product: kdenlive Version: 23.04.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: sadiyumu...@gmail.com Target Milestone: --- Kdenlive rendering dialog box features an option to shutdown computer after renderings, which is a very good idea for cases when renderings will take a long time. However, I think it's also a good idea to offer a similar option to close the dialog box, and even another option to quit the application after renderings, for cases such as rendering a short video clip to continue working on more videos in the app after it's completed, or rendering a video clip as the last project in the app where the user has nothing to do in the app after the rendering is completed, and therefore can even switch to other tasks during rendering, expecting merely a notification that rendering has been completed. SOFTWARE/OS VERSIONS Operating System: Debian Testing KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 472674] New: Media Player applet behavior on desktop vs panel
https://bugs.kde.org/show_bug.cgi?id=472674 Bug ID: 472674 Summary: Media Player applet behavior on desktop vs panel Classification: Plasma Product: kdeplasma-addons Version: 5.27.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com Target Milestone: --- Created attachment 160544 --> https://bugs.kde.org/attachment.cgi?id=160544=edit Media Player widget on Desktop and Sidebar SUMMARY *** This widget displays very functional and good-looking on desktop, but it's not like that on a panel, e.g. on my right panel (sidebar) below Analog Clock, Calculator etc. As seen in the screenshot, the progress bar and media control buttons are omitted (available only in context menu) when it's added to a relatively wide panel, although they are displayed on desktop even in a smaller height. One can't get them even by increasing the panel width because the height also increases proportionally, making it impossible to use on a panel with other similar widgets. I think it would be very nice if we could get the progress bar and media control buttons underneath the song title and artist when the widget is used in a large panel like that. *** SOFTWARE/OS VERSIONS Operating System: Debian Testing KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 472671] New: Calculator applet minimum width and height values
https://bugs.kde.org/show_bug.cgi?id=472671 Bug ID: 472671 Summary: Calculator applet minimum width and height values Classification: Plasma Product: kdeplasma-addons Version: 5.27.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calculator Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com Target Milestone: --- SUMMARY *** This handy widget works as expected from anywhere on the desktop, but it seems there's a problem with display and scaling. When added to desktop, it's displayed initially as an icon, although one would expect it to appear at least in its minimum size, which can only be attained by resizing it. My problem is with its use in the right panel (sidebar) where I have also analog clock, media player etc. I couldn't reduce the width of that panel below 226 px because the calculator widget would immediately switch to an icon below that width. After replacing the "Layout.minimumWidth/Height" values in "/usr/share/plasma/plasmoids/org.kde.plasma.calculator/contents/ui/calculator.qml" with 200 and 210, respectively, I could reduce panel width down to 215 px. I think it should be possible to have a full display of this applet in a much smaller scale, which would be very useful in some cases. *** SOFTWARE/OS VERSIONS Operating System: Debian Testing KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469672] Blank screen after login. Wayland only.
https://bugs.kde.org/show_bug.cgi?id=469672 --- Comment #14 from Sadi --- Sorry, it seems I was lost somewhere there - so I tried again to obtain a backtrace. 1. From SDDM, I was again pushed back immediately (sometimes seeing a black screen for a second, and/or hearing the login sound). 2. I then switched to terminal, and executed these commands: export QT_LOGGING_RULES="kwin_*.debug=true" startplasma-wayland > ~/startplasma-wayland.log 2>&1 The result was the same, with this output: Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. 3. There the command "coredumpctl --reverse" didn't return any results, but "sudo coredumpctl --reverse" did, but the list didn't include either "kwin" or "wayland". The closest thing I saw was "plasmashell". I can copy here the output of command "sudo coredump gdb if it makes sense. The abbreviated list: /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/bin/gmenudbusmenuproxy /usr/bin/plasmashell /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/lib/insync/insync /usr/bin/gmenudbusmenuproxy /usr/bin/xembedsniproxy /usr/bin/plasmashell /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/bin/gmenudbusmenuproxy /usr/bin/python3.11 /usr/bin/gmenudbusmenuproxy /usr/bin/plasmashell /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/bin/kaccess /usr/bin/kup-daemon /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd /usr/bin/gmenudbusmenuproxy /usr/bin/ksmserver /usr/bin/kded5 4. I then tried the command "XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland", which let me login to Plasma Wayland session. I tried to obtain a backtrace from there by launching Konsole, and executing the command "sudo coredumpctl --reverse" with the same result: no "kwin" or "wayland". I can also copy here the output of command "sudo coredump gdb for "plasmashell" if it makes sense. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469672] Blank screen after login. Wayland only.
https://bugs.kde.org/show_bug.cgi?id=469672 --- Comment #12 from Sadi --- (In reply to Nate Graham from comment #11) > I'm afraid we still need a backtrace. Sorry, can you tell me how to get that backtrace? -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 436082] displaying progress of package actions in a dialog box
https://bugs.kde.org/show_bug.cgi?id=436082 Sadi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Sadi --- It seems we can consider Muon dead, and close this bug now. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 447543] Muon fails to uninstall all dependencies
https://bugs.kde.org/show_bug.cgi?id=447543 Sadi changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #1 from Sadi --- It seems we can consider Muon dead, and close this bug now. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 437195] Muon shows 23 packages as locked although they are not
https://bugs.kde.org/show_bug.cgi?id=437195 Sadi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Sadi --- It seems we can consider Muon dead, and close this bug now. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 436875] Muon doesn't handle package description text properly
https://bugs.kde.org/show_bug.cgi?id=436875 Sadi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #2 from Sadi --- It seems we can consider Muon dead, and close this bug now. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 436622] inconsistent icons
https://bugs.kde.org/show_bug.cgi?id=436622 Sadi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #2 from Sadi --- It seems we can consider Muon dead, and close this bug now. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468206] Dolphin Places panel context menu theming issue
https://bugs.kde.org/show_bug.cgi?id=468206 Sadi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Sadi --- Thanks, this has been resolved now. == Operating System: Debian Testing KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471981] New: Can't login to Wayland session anymore
https://bugs.kde.org/show_bug.cgi?id=471981 Bug ID: 471981 Summary: Can't login to Wayland session anymore Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 For some time now I've been testing Wayland once a month or so in order to see the progress made, and if I can switch to it for regular use. However, the other day I found myself immediately thrown back to SDDM login screen as if the file "usr/bin/startplasma-wayland" was missing. The contents of file "~/.local/share/wayland-session.log": Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. A newly created user can login to Wayland session, and the file "~/.local/share/wayland-session.log" is empty there. However, after logging out and repeating my Wayland login failure, that empty log file is also filled with the same contents as mine after successful Wayland login. Disabling all startup apps and scripts makes no difference. Adding the same desktop layout including the same third party widgets as well as startup apps and scripts doesn't prevent the new user to log in to Wayland session either. The terminal command "XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland" or "dbus-run-session startplasma-wayland" sometimes briefly displays black screen and even plays the login sound with the following output: dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 ' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1 requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.kde.KSplash' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=79371 Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by 1.3' (uid=1000 pid=7964 comm="/usr/bin/kwin_wayland_wrapper --xwayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemdi' failed: Process org.freedesktop.systemdi exited with status 1
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #65 from Sadi --- Has anyone tried the third-party alternative? https://github.com/zzag/kwin-effects-cube -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469672] Blank screen after login. Wayland only.
https://bugs.kde.org/show_bug.cgi?id=469672 --- Comment #9 from Sadi --- Sorry, I forgot to add that the command "XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland" or "dbus-run-session startplasma-wayland" does launch the wayland session for me as well, but produces the following terminal output: == dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 ' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1 requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.kde.KSplash' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=79371 Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by 1.3' (uid=1000 pid=7964 comm="/usr/bin/kwin_wayland_wrapper --xwayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemdi' failed: Process org.freedesktop.systemdi exited with status 1 kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid=7977, result = 0 No backend specified, automatically choosing drm The Wayland connection broke. Did the Wayland compositor die?f0 "") unless they are emitted in the object's thread QThread (0x55ba74a45218 "libinput-connection"). Current thread is QThread(0x55ba749f1b70").handled with .catch(). To termina The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? Gdk-Message: 17:00:53.965: Lost connection to Wayland compositor. The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469672] Blank screen after login. Wayland only.
https://bugs.kde.org/show_bug.cgi?id=469672 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #8 from Sadi --- I've been testing Wayland from time to time to see the progress for some time. Yesterday I've encountered the same problem, although no important change took place in my system configuration after the last successful login to Wayland session one or two weeks ago. When I create a new user, I can login to Wayland session, with nothing in "~/.local/share/wayland-session.log". Oddly, after logging out, I can see the same content in that file as in mine after Wayland login failure (see below). Disabling all startup apps and scripts had no effect. Adding the same desktop layout including the same third party widgets to the new user session didn't cause any problems either. ~/.local/share/wayland-session.log: === Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. I get the same output from the following command: === export QT_LOGGING_RULES="kwin_*.debug=true" startplasma-wayland > ~/startplasma-wayland.log 2>&1 SOFTWARE/OS VERSIONS Operating System: Kdebian 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 471187] New: Image saving name - additional feature to include date
https://bugs.kde.org/show_bug.cgi?id=471187 Bug ID: 471187 Summary: Image saving name - additional feature to include date Classification: Applications Product: Skanlite Version: 22.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: sadiyumu...@gmail.com Target Milestone: --- Skanlite Settings offer users to set a name, and a format for saving images. There is a four-digit (hard-coded) number between these two. I think it would be great if it were possible to include also the current date somewhere here. For instance, something like "$(date +'%Y-%m-%d')" or "-MM-dd" etc... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470877] New: Titlebar buttons settings do not apply fully
https://bugs.kde.org/show_bug.cgi?id=470877 Bug ID: 470877 Summary: Titlebar buttons settings do not apply fully Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_kwindecoration Assignee: kwin-bugs-n...@kde.org Reporter: sadiyumu...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 159583 --> https://bugs.kde.org/attachment.cgi?id=159583=edit close buttons in tabs and notifications inconsistent with titlebar close buttons SUMMARY *** KDE Plasma offers an option to move titlebar buttons (close, minimize, maximize) to the left edge as in Mac OS, but it seems this move does not take effect fully throughout the system. Certain elements like tabs in app windows as well as notifications still display close buttons at the right edge. They are not "titlebar buttons" but at least for ease of use one normally expects these buttons to follow the same pattern. This may also be true for the close button of notifications which are white on red circle unlike those in titlebars and tabs. *** SOFTWARE/OS VERSIONS Operating System: Debian 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469274] New: logout scripts are executed a bit too late
https://bugs.kde.org/show_bug.cgi?id=469274 Bug ID: 469274 Summary: logout scripts are executed a bit too late Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: nicolas.fe...@gmx.de Reporter: sadiyumu...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** I have a logout script to check if there are any files that I forgot in several temporary folders before logging out. This logout script was skipped when I choose to restart automatically during Discover offline updates, which has been fixed recently. However, maybe in connection with this fix, my logout script is executed now after (I think) plasmashell is terminated, so if there are some files that I forgot in those temporary folders, Dolphin opens such a folder to take some action but without any window decoration, menu, or even shortcut keys working, which makes it difficult to quit at the end. *** STEPS TO REPRODUCE 1. Use a logout script that will open, say, "/tmp" with Dolphin 2. Close any Dolphin window, and log out OBSERVED RESULT The system terminates plasmashell first (I think), and then exectues the logout script, opening a Dolphin window displaying the contents of "/tmp" folder, but without titlebar, menu, shortcut keys etc. EXPECTED RESULT The logout script should be executed before plasmashell is terminated. SOFTWARE/OS VERSIONS Operating System: SparkyLinux 7 (Debian Testing/Bookworm) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467770] [Feature Request] System Activity widget
https://bugs.kde.org/show_bug.cgi?id=467770 --- Comment #1 from Sadi --- I'm happy to report that this has now been provided by this third party plasmoid: https://www.opendesktop.org/p/2022038 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 468682] New: update result report
https://bugs.kde.org/show_bug.cgi?id=468682 Bug ID: 468682 Summary: update result report Classification: Applications Product: apper Version: 1.0.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: sadiyumu...@gmail.com Target Milestone: --- Created attachment 158213 --> https://bugs.kde.org/attachment.cgi?id=158213=edit Apper updates completion report Apper shows a system status report after software updates. The first line: Your system is up to date The second line: Verified ... day(s) and Y hour(s) ago It's this second line that's confusing, which might be caused by a bug. It's odd that just after completing a system update operation, and confirming that the system is now up to date, Apper then goes on to say this was verified a long time ago. Perhaps I don't understand what this actually means (sorry), or perhaps, there's no need for such a second line at all... Operating System: SparkyLinux 7 (Debian Testing/Bookworm) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468206] New: Dolphin Places panel context menu theming issue
https://bugs.kde.org/show_bug.cgi?id=468206 Bug ID: 468206 Summary: Dolphin Places panel context menu theming issue Classification: Applications Product: dolphin Version: 22.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sadiyumu...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 157900 --> https://bugs.kde.org/attachment.cgi?id=157900=edit Dolphin context menus - in Places panel and otherwise I don't know when this started, but it must be within the past couple of months: the context menu that pops up when one right clicks on the Places panel on the left appears out of place, disregarding the theme -as seen in the screenshot displaying the two types of context menus existing in Dolphin now. This doesn't occur in any of the other panels (Folders, Information, Terminal) or in the main window pane. Operating System: Debian Testing/Bookworm KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467770] New: [Feature Request] System Activity widget
https://bugs.kde.org/show_bug.cgi?id=467770 Bug ID: 467770 Summary: [Feature Request] System Activity widget Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 It would be very handy if we could have a widget showing top x processes using CPU, something like a very limited version of "System Activity". It may only have an option to limit the number of processes (including all processes). I don't think such a widget should also include filtering options (All/System/User/Own Processes or Programs Only) as in System Activity. It may perhaps allow the user to launch System Activity by clicking the widget. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 466953] New: kinfocenter seems to report its own package version instead of KDE Plasma version reported by plasmashell
https://bugs.kde.org/show_bug.cgi?id=466953 Bug ID: 466953 Summary: kinfocenter seems to report its own package version instead of KDE Plasma version reported by plasmashell Classification: Applications Product: kinfocenter Version: 5.26.90 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY *** KDE Plasma version 5.26.90 might be virtually the same as 5.27.0, but nonetheless I think Info Center should display the same version as the output of command "plasmashell --version", which is currently 5.27.0 in Debian Bookworm (testing) repositories (like most packages from plasma-desktop to to kde-cli-tools) although some packages like kinfocenter are at version 5.26.90 *** SOFTWARE/OS VERSIONS Operating System: SparkyLinux 7 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 444976] Dolphin does not generate preview of .heic images
https://bugs.kde.org/show_bug.cgi?id=444976 --- Comment #15 from Sadi --- I've just checked, and now I can see heic thumbnails! Unfortunately, I don't know how and when it happened - maybe after I switched from KDE neon to Sparky KDE, based directly on Debian testing. Operating System: SparkyLinux 7 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 kio-extras: 22.12.2-1 libheif1: 1.14.2-1 heif-thumbnailer: not installed! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color do not take effect immediately in GTK apps using Breeze GTK theme; they need to be restarted
https://bugs.kde.org/show_bug.cgi?id=456874 --- Comment #9 from Sadi --- This appears to have been resolved now for all apps like Brave and Thunderbird other than Dolphin - failing to refresh folder color automatically when accent color changes due to wallpaper change slideshow. Operating System: SparkyLinux 7 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457215] Opacity of the Plasma panels should be tweakable in a granular way
https://bugs.kde.org/show_bug.cgi?id=457215 --- Comment #5 from Sadi --- I wish it were possible to enable/disable blur effect, set different levels of transparency for each panel (instead of being dependent on one background.svg) like other panel settings (width, height, visibility, opacity etc.). I hope developers consider this at least for the future. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461939] Plasma panel items don't change color like titlebars and others in keeping with the new dynamic accent color
https://bugs.kde.org/show_bug.cgi?id=461939 --- Comment #6 from Sadi --- For anyone who is interested, it seems there are two possible workarounds to get rid of this inconsistency: 1. When using dynamic accent color from current wallpaper (plus using wallpaper slideshow), inconsistency can be prevented by choosing a custom tinted color scheme with the option "Make window titlebars accent-colored" unchecked (which stops changing titlebar foreground color between black and white). 2. A more complex workaround can be implemented by running a script in the background which detects change of titlebar foreground color between black and white in file "~/.config/kdeglobals", section "[WM]", line "activeForeground=", and changes plasma theme as well as icon theme (e.g. by creating a custom icon theme that only includes alternative panel/status icons) between dark and light whenever its value changes between "0,0,0" and "255,255,255". However, such a script making use of inotifywait command, for example, doesn't work well, probably because it creates too much of a burden for plasmashell. Therefore, I had to give up on this, and choose the first workaround at the end. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461939] Plasma panel items don't change color like titlebars and others in keeping with the new dynamic accent color
https://bugs.kde.org/show_bug.cgi?id=461939 --- Comment #5 from Sadi --- I'm sorry for taking your time regarding this "very niche customization" as you call it. I've actually stopped using latte-dock very recently, seeing that plasma panels have come so close to offering the same features. It seems the only missing ones now are (1) this "adaptive color", and (2) zoom effect in "Icons-Only Task Manager". Especially after the latest dynamic accent color feature, the first one is much more important that the fancy zoom effect. Could you perhaps give me a tip for detecting from the command line when the new dynamic accent color from current wallpaper result in change of color in window title/menu/tool bars? I could then use a script that changes the plasma theme colors in keeping with it... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461939] Plasma panel items don't change color like titlebars and others in keeping with the new dynamic accent color
https://bugs.kde.org/show_bug.cgi?id=461939 Sadi changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461939] Plasma panel items don't change color like titlebars and others in keeping with the new dynamic accent color
https://bugs.kde.org/show_bug.cgi?id=461939 --- Comment #3 from Sadi --- I think at least this might be considered as a new feature to be added in the future to "More Options..." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461939] Plasma panel items don't change color like titlebars and others in keeping with the new dynamic accent color
https://bugs.kde.org/show_bug.cgi?id=461939 --- Comment #2 from Sadi --- (In reply to veggero from comment #1) > Plasma panels follow the normal background color of windows, not the accent > color. You can basically consider plasma panels as the content of a window. > This means that it's only appropriate for them to use the same font color as > window's content, which is black in both screenshots. Then wouldn't it be better to change this, and make panels handle colors in keeping with title/menu/toolbars, instead of the current behavior like main app windows??? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425957] Search by filename returns no results inside symlinked directory
https://bugs.kde.org/show_bug.cgi?id=425957 --- Comment #4 from Sadi --- Created attachment 153899 --> https://bugs.kde.org/attachment.cgi?id=153899=edit a possible Dolphin settings navigation option for symlinked folders It seems we need an additional option in Dolphin Settings > Configure Dolphin > Navigation, like this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425957] Search by filename returns no results inside symlinked directory
https://bugs.kde.org/show_bug.cgi?id=425957 Sadi changed: What|Removed |Added Summary|Search by filename returns |Search by filename returns |no results inside symlinked |no results inside symlinked |directory from one |directory |partition to another| -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425957] Search by filename returns no results inside symlinked directory from one partition to another
https://bugs.kde.org/show_bug.cgi?id=425957 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #3 from Sadi --- Apparently, this is because files are being indexed according to their real location only, so no duplicate entries are being created to include the same files also with their symlinked path. I guess a solution for this longstanding problem could be; letting Dolphin open a symlinked directory using its real path instead of the current "virtual" path, which creates this frustrating search problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461939] New: Plasma panel items don't change color like titlebars and others in keeping with the new dynamic accent color
https://bugs.kde.org/show_bug.cgi?id=461939 Bug ID: 461939 Summary: Plasma panel items don't change color like titlebars and others in keeping with the new dynamic accent color Classification: Plasma Product: plasmashell Version: 5.26.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 153824 --> https://bugs.kde.org/attachment.cgi?id=153824=edit Items on translucent top panel and dolphin window with dynamic accent color SUMMARY *** The new color scheme option to use accent color from current wallpaper is a great addition to the appearance. I love it especially when used with wallpaper type slideshow . Depending on the accent color change, titlebar texts and other items change color smartly between black and white so that they remain visible. However, items on the panel(s) remain indifferent to this dynamic accent color change, unfortunately, and this creates a visibility problem in the case of panel translucency. *** STEPS TO REPRODUCE 1. Add widgets "Window Title" an "Global Menu" to the default panel, and move it to the top. 2. Create a special wallpaper folder with some light and dark colored images. 3. Choose "Use accent color: From current wallpaper" in System Settings:Appearence:Colors and "Wallpaper type:Slideshow" in Configure Desktop and Wallpaper...:Wallpaper, and the wallpaper folder created above. OBSERVED RESULT When the accent color used from current wallpaper is dark, titlebar text and some other items (inc. monochrome icons) smartly change to white, but similar items on the panel remain black, therefore hard to see in some places. EXPECTED RESULT All text and monochrome icons the panel should change between black and white like those in app windows titlebar etc. SOFTWARE/OS VERSIONS Operating System: SparkyLinux 7 (based on Debian Testing) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461197] New: English mistranslation in showfoto undo cache free space warning
https://bugs.kde.org/show_bug.cgi?id=461197 Bug ID: 461197 Summary: English mistranslation in showfoto undo cache free space warning Classification: Applications Product: digikam Version: 7.7.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Showfoto-Core Assignee: digikam-bugs-n...@kde.org Reporter: sadiyumu...@gmail.com Target Milestone: --- SUMMARY *** When there's less than 2 GB free space where ~/.cache/showfoto/ directory is located, the following message is displayed: The free disk space in the path "/home/$USER/.cache/showfoto/" for the undo cache file is inferior to 2 GiB! Undo cache is now disabled! Please replace "inferior to" with "less than" ;-) *** SOFTWARE/OS VERSIONS Operating System: SparkyLinux 7 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460891] plasmashell started crashing sometimes after the latest batch of upgrades
https://bugs.kde.org/show_bug.cgi?id=460891 --- Comment #3 from Sadi --- I hope this backtrace (produced after installing plasma-workspace-dbg and plasma-desktop-dbg) is good enough, although I can still see that flat "Install Debug Symbols" button at the top. -- Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7fb9832eedc4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb940e0e3ad in PlaceholderModel::reset (this=0x558e813f2960) at ./applets/kicker/plugin/placeholdermodel.cpp:234 #7 0x7fb9832eedf8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb9832e7f23 in QObject::destroyed(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb9832ed0d7 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb940e07ad4 in KAStatsFavoritesModel::Private::~Private (this=0x558e813f6860, __in_chrg=) at ./applets/kicker/plugin/kastatsfavoritesmodel.cpp:60 #11 KAStatsFavoritesModel::Private::~Private (this=0x558e813f6860, __in_chrg=) at ./applets/kicker/plugin/kastatsfavoritesmodel.cpp:60 #12 0x7fb940e01595 in KAStatsFavoritesModel::~KAStatsFavoritesModel (this=0x558e813f2960, __in_chrg=) at ./applets/kicker/plugin/kastatsfavoritesmodel.cpp:472 #13 KAStatsFavoritesModel::~KAStatsFavoritesModel (this=0x558e813f2960, __in_chrg=) at ./applets/kicker/plugin/kastatsfavoritesmodel.cpp:473 #14 0x7fb9832e1e0e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fb9832ece96 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fb940e11cd9 in QQmlPrivate::QQmlElement::~QQmlElement (this=0x558e8078f220, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:144 #17 QQmlPrivate::QQmlElement::~QQmlElement (this=0x558e8078f220, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:144 #18 0x7fb9832e1e0e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fb9832ece96 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb984eaf859 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7fb98521e4ba in KDeclarative::QmlObject::~QmlObject() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #22 0x7fb98521f22d in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #23 0x7fb9832e1e0e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fb9832ece96 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fb97463d3dd in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #26 0x7fb9832e1e0e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb9832ece96 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fb974637ded in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #29 0x7fb9852c9a88 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #30 0x7fb9852c9c8d in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #31 0x7fb9852b3c16 in Plasma::Applet::~Applet() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #32 0x7fb9852b3c3d in Plasma::Applet::~Applet() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #33 0x7fb9832e1e0e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fb9832ece96 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7fb9852b96dd in Plasma::Containment::~Containment() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #36 0x558e7dbb40a0 in ShellCorona::~ShellCorona (this=0x558e7fde3280, __in_chrg=) at ./shell/shellcorona.cpp:288 #37 0x558e7dbb441d in ShellCorona::~ShellCorona (this=0x558e7fde3280, __in_chrg=) at ./shell/shellcorona.cpp:290 #38 0x7fb9832e4573 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x7fb983fbe763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #40 0x7fb9832b6fea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x7fb9832ba0d7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #42 0x7fb9832bdebc in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #43 0x558e7db83834 in main (argc=, argv=) at ./shell/main.cpp:233 [Inferior 1 (process 1813) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460891] plasmashell started crashing sometimes after the latest batch of upgrades
https://bugs.kde.org/show_bug.cgi?id=460891
--- Comment #2 from Sadi ---
For Debug Symbols I first tried the following steps (maybe this is another bug
that should be reported separately) before manually installing the
plasma-workspace-dbg and plasma-desktop-dbg, the result of which will be coming
soon:
The KDE Crash Handler > Install Debug Symbols > Add Missing Sources
This resulted in an error dialog box saying "An error occurred during
installation Failed to obtain authentication." and displaying the following
details:
[] ("neon-repositories-ubuntu-ddebs")
[] "[repository::system/package/os/org.kde.neon.com.ubuntu.ddebs/*]> name:
Ubuntu Debug Symbols | summary: Debug Symbols for Ubuntu | package:
neon-repositories-ubuntu-ddebs"
[] ("org.kde.neon.com.ubuntu.ddebs") 1
[] files: ("/usr/bin/plasmashell", "/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Widgets.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libKF5Plasma.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libKF5Plasma.so.5",
"/lib/x86_64-linux-gnu/libKF5Plasma.so.5",
"/lib/x86_64-linux-gnu/libKF5Plasma.so.5",
"/lib/x86_64-linux-gnu/libKF5Plasma.so.5",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libKF5Declarative.so.5",
"/lib/x86_64-linux-gnu/libKF5Declarative.so.5",
"/lib/x86_64-linux-gnu/libQt5Quick.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so",
"/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/lib/x86_64-linux-gnu/libQt5Core.so.5",
"/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so",
"/lib/x86_64-linux-gnu/libQt5Core.so.5")
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 460891] New: plasmashell started crashing sometimes after the latest batch of upgrades
https://bugs.kde.org/show_bug.cgi?id=460891 Bug ID: 460891 Summary: plasmashell started crashing sometimes after the latest batch of upgrades Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.26.0) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 5.15.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.26 DrKonqi: 5.26.0 [KCrashBackend] -- Information about the crash: I've begun seeing this after latest batch of upgrades (about 100MB) on 20 or 21 October 2022. 1) Sometimes plasmashell crashes once or several times with a notification in the system tray, and it automatically recovers. Sometimes it constantly keeps crashing and recovering in the background until I manually execute te "plasmashell --replace" command via a custom keyboard shortcut, after which it won't reoccur for a long time. 2) During such automatically repeated instances of crash and refresh, I see all open windows and panels "flashing". 3) This occurs sometimes after the usual login with the usual startup apps (Elisa playing music in the bacground, and third parts WhatsDesk starting a WhatsApp desktop session and Insync syncing my Google Drive files) when I haven't done anything yet. Sometimes it happens when I have only Dolpih open, browsing my files; sometimes it happens while I'm using my web browser. I don't think that this is somehow related with any other apps I'm running. I think it's most likely that there's a new bug in the latest batch of upgrades. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1824] [New LWP 1884] [New LWP 1919] [New LWP 1971] [New LWP 1974] [New LWP 2006] [New LWP 2007] [New LWP 2008] [New LWP 2138] [New LWP 2177] [New LWP 2178] [New LWP 2182] [New LWP 2183] [New LWP 2442] [New LWP 2443] [New LWP 2527] [New LWP 2528] [New LWP 2556] [New LWP 2557] [New LWP 6759] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f91bea8199f in __GI___poll (fds=0x7ffd43d80f78, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 python sentry-sdk not installed :( [Current thread is 1 (Thread 0x7f91bab8e2c0 (LWP 1809))] Thread 21 (Thread 0x7f9165ffb700 (LWP 6759)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f9165ffab50, clockid=, expected=0, futex_word=0x55c4193aad30) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f9165ffab50, clockid=, mutex=0x55c4193aace0, cond=0x55c4193aad08) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55c4193aad08, mutex=0x55c4193aace0, abstime=0x7f9165ffab50) at pthread_cond_wait.c:665 #3 0x7f91bee17578 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f91bee14a91 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f91bee11543 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f91be640609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f91bea8e133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f9126dbd700 (LWP 2557)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c41bf74944) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c41bf748f0, cond=0x55c41bf74918) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c41bf74918, mutex=0x55c41bf748f0) at pthread_cond_wait.c:647 #3 0x7f91bee175eb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f91c0ab6394 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f91c0ab6809 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f91bee11543 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f91be640609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f91bea8e133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f912658c700 (LWP 2556)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c41c1e40c0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c41c1e4070, cond=0x55c41c1e4098) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c41c1e4098, mutex=0x55c41c1e4070) at pthread_cond_wait.c:647 #3 0x7f91b263a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f91b263a1eb in ?? () from
[systemsettings] [Bug 460704] Unicode is not working in sample address display
https://bugs.kde.org/show_bug.cgi?id=460704 --- Comment #7 from Sadi --- localectl list-locales: C.UTF-8 en_AG.UTF-8 en_AU.UTF-8 en_BW.UTF-8 en_CA.UTF-8 en_DK.UTF-8 en_GB.UTF-8 en_HK.UTF-8 en_IE.UTF-8 en_IL.UTF-8 en_IN.UTF-8 en_NG.UTF-8 en_NZ.UTF-8 en_PH.UTF-8 en_SG.UTF-8 en_US.UTF-8 en_ZA.UTF-8 en_ZM.UTF-8 en_ZW.UTF-8 tr_CY.UTF-8 tr_TR.UTF-8 locale: LANG=en_US.UTF-8 LANGUAGE=en_US LC_CTYPE=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=C LC_COLLATE=tr_TR.UTF-8 LC_MONETARY=C LC_MESSAGES=en_US.UTF-8 LC_PAPER=C LC_NAME=C LC_ADDRESS=C LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=C LC_IDENTIFICATION=en_US.UTF-8 LC_ALL= -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460704] Unicode is not working in sample address display
https://bugs.kde.org/show_bug.cgi?id=460704 --- Comment #3 from Sadi --- Created attachment 153055 --> https://bugs.kde.org/attachment.cgi?id=153055=edit Screenshot of Unicode issue in sample addresses -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460704] Unicode is not working in sample address display
https://bugs.kde.org/show_bug.cgi?id=460704 --- Comment #2 from Sadi --- (In reply to Nate Graham from comment #1) > What font are you using? I'm using Roboto but I don't think it's related with the font I choose because (a) I can see the character "umlaut u" (and other similar ones) in the heading, and (b) this didn't change when I applied others fonts like Noto Sans or Inter. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460704] New: Unicode is not working in sample address display
https://bugs.kde.org/show_bug.cgi?id=460704 Bug ID: 460704 Summary: Unicode is not working in sample address display Classification: Applications Product: systemsettings Version: 5.26.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_regionandlang Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY *** The sample address shown in "Region & Language - System Settings" displays country name as "Trkiye" *** EXPECTED RESULT The country name should be displayed "Türkiye"; it seems there's a problem with Unicode characters there. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 460419] New: Gwenview message while saving an edited image does not use current theme
https://bugs.kde.org/show_bug.cgi?id=460419 Bug ID: 460419 Summary: Gwenview message while saving an edited image does not use current theme Classification: Applications Product: gwenview Version: 22.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: sadiyumu...@gmail.com Target Milestone: --- Created attachment 152803 --> https://bugs.kde.org/attachment.cgi?id=152803=edit Gwenview status message while saving an edited image SUMMARY *** Whenever I edit an image and then save it, and if the file size is not too small to take some time to save it, a status message appears above the image preview (see screenshot) in a (default/fallback?) style different from the current theme, even if it's the default Breeze theme, which looks quite out of place. *** SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION In fact, this issue has been always there (for several years at least), but I'm just reporting it now. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 444976] Dolphin does not generate preview of .heic images
https://bugs.kde.org/show_bug.cgi?id=444976 Sadi changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||sadiyumu...@gmail.com Resolution|FIXED |--- --- Comment #10 from Sadi --- This is a problem I've had all the time, and just didn't bother. I wonder why I still have it although this is declared "Resolved" and "Fixed" here? Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 kio-extras installed version: 4:22.08.1-0xneon+20.04+focal+release+build62 heif-thumbnailer & libheif1 installed version: 1.6.1-1build1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color do not take effect immediately in GTK apps using Breeze GTK theme; they need to be restarted
https://bugs.kde.org/show_bug.cgi?id=456874 --- Comment #8 from Sadi --- Correction: Sorry, my previous observations of other apps using GTK+ theme, like LibreOffice and Thunderbird, were apparently misleading probably due to a hardly noticeable color change. I can now confirm that this bug affects them all, although clicking on Thunderbird tab bar doesn't refresh it like Brave browser. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color do not take effect immediately in GTK apps using Breeze GTK theme; they need to be restarted
https://bugs.kde.org/show_bug.cgi?id=456874 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #7 from Sadi --- Created attachment 152528 --> https://bugs.kde.org/attachment.cgi?id=152528=edit screenshot of Brave browser I experience a similar problem in the header (tab) bar of Brave web browser using system GTK+ theme: sometimes its color changes only partially, sometimes it doesn't change at all, until I click on it. Hovering on it also causes a similar partial color change, again until I click on it (as seen in the screenshot). However, I don't see this in other apps using GTK theme like LibreOffice, Thunderbird, Palemoon web browser, etc. This might be due to each app using GTK+ theme in some different way so that some do experience this problem while some don't??? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455812] "Use accent color from current wallpaper" causes visual glitches when the wallpaper is automatically changed by a slideshow
https://bugs.kde.org/show_bug.cgi?id=455812 --- Comment #9 from Sadi --- Created attachment 152523 --> https://bugs.kde.org/attachment.cgi?id=152523=edit Visual glitches in the header (tab) bar of Brave web browser with system GTK+ theme -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455812] "Use accent color from current wallpaper" causes visual glitches when the wallpaper is automatically changed by a slideshow
https://bugs.kde.org/show_bug.cgi?id=455812 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #8 from Sadi --- I don't know if this could be related to bug 414097 which is about the icon color of some folders in Dolphin not automatically changing with accent color changes. Other than that, I also experience visual glitches in the header (tab) bar of Brave web browser with system GTK+ theme. Sometimes its color changes only partially, sometimes it doesn't change at all, until I click on it. Hovering on it also causes a similar partial change, again until I click on it (as seen in the screenshot attached). This doesn't happen in other apps using GTK theme like LibreOffice, Thunderbird, Palemoon web browser, etc. Note: I would very much prefer living with these minor visual glitches to losing this very attractive dynamic accent color feature though. ;-) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414097] Preview folder icons not repainted automatically after color scheme change
https://bugs.kde.org/show_bug.cgi?id=414097 --- Comment #9 from Sadi --- Created attachment 152521 --> https://bugs.kde.org/attachment.cgi?id=152521=edit dolphin window displaying folders not refreshed whether containing file previews or not -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414097] Preview folder icons not repainted automatically after color scheme change
https://bugs.kde.org/show_bug.cgi?id=414097 Sadi changed: What|Removed |Added CC||sadiyumu...@gmail.com --- Comment #8 from Sadi --- In my case this is true also for folders with file previews as can be seen in screenshot-3 added by me. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 459381] KDialog odd behavior escaping exclamation mark
https://bugs.kde.org/show_bug.cgi?id=459381 --- Comment #2 from Sadi --- (In reply to Brad Hards from comment #1) > This is not a KDialog issue. > > The difference in behaviour is due to using different shells. If you want to > have bash behaviour in your shell script, run it in bash (not dash or > whatever other shell you are using). I use zsh but this behavior doesn't change even if it's named *.sh and its first line is like this: #!/usr/bin/env bash I ruled out that because KDialog --progressbar doesn't work with zsh but it works if I do as above. BTW, is the progress bar issue also zsh issue, and not KDialog issue? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 459381] New: KDialog odd behavior escaping exclamation mark
https://bugs.kde.org/show_bug.cgi?id=459381 Bug ID: 459381 Summary: KDialog odd behavior escaping exclamation mark Classification: Unclassified Product: kdialog Version: 22.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: sadiyumu...@gmail.com Target Milestone: --- SUMMARY *** KDialog displays escaped exclamation mark from terminal but not from a shell script. *** STEPS TO REPRODUCE 1. Enter a terminal command like this: kdialog --title "Conversion" --passivepopup "The file has been \"converted\" now\!" 2. Copy and paste this command into an empty executable shell script file, and run the script file from the terminal. OBSERVED RESULT 1. Terminal command results in this message text, as expected: The file has been "converted" now! 2. The script, however, results in this message text: The file has been "converted" now\! Additionally, the following terminal message appears: Unrecognized escape sequence \! EXPECTED RESULT Escaping the exclamation mark like other characters (e.g. double quotation mark) should work in script files as well as entering it directly in terminal. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456004] Terminal background color transparency lost
https://bugs.kde.org/show_bug.cgi?id=456004 --- Comment #2 from Sadi --- (In reply to axel.wikstrom from comment #1) > Having the same issue, and also with Konsole itself. The transparency setting > is not saved. Konsole transparency problem might be different. I don't have it with version 22.08.0 in KDE neon 5.25.5. Indeed I'm beginning to suspect that Dolphin developers might have decided to apply Dolphin-specific appearance settings to all panels, including the terminal panel, instead of applying Konsole's appearance settings inside Dolphin window. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458843] New: dialog-information icon is not displayed in kdialog passivepopups
https://bugs.kde.org/show_bug.cgi?id=458843 Bug ID: 458843 Summary: dialog-information icon is not displayed in kdialog passivepopups Product: Breeze Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: sadiyumu...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 151892 --> https://bugs.kde.org/attachment.cgi?id=151892=edit Screenshot of "dialog-*" icons in KDialogs SUMMARY *** I've just noticed that dialog-information icon is not displayed in kdialog passivepopups while all the others in that icon set "dialog-*.svg" are displayed as expected. *** STEPS TO REPRODUCE Enter these commands in a terminal window: kdialog --icon "dialog-error" --title "dialog-error icon" --passivepopup "Displayed" & kdialog --icon "dialog-information" --title "dialog-information icon" --passivepopup "NOT Displayed" & kdialog --icon "dialog-positive" --title "dialog-positive icon" --passivepopup "Displayed" & kdialog --icon "dialog-question" --title "dialog-question icon" --passivepopup "Displayed" & kdialog --icon "dialog-warning" --title "dialog-warning icon" --passivepopup "Displayed" & kdialog --title "Test" --msgbox "dialog-information icon is displayed" OBSERVED RESULT All those icons are displayed in kdialog passivepopups with only one exception: dialog-information. However, it is displayed in kdialog msgbox irrespective of icon option there. EXPECTED RESULT The icon "dialog-information" should be displayed in kdialog passivepopups as well. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458092] Dolphin does not display previews for plain text files if their extension is ".log"
https://bugs.kde.org/show_bug.cgi?id=458092 --- Comment #2 from Sadi --- Tested (In reply to Méven Car from comment #1) > I don't reproduce this issue. Might this issue be KDE-neon-specific or fixed somehow in KDE Plasma 5.25.80 / KDE Frameworks 5.98.0 under Kubuntu? Tested again this time in a newly created user session: same Tested again this time in a KDE neon live session: same Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458092] Dolphin does not display previews for plain text files if their extension is ".log"
https://bugs.kde.org/show_bug.cgi?id=458092 Sadi changed: What|Removed |Added Summary|Dolphin does not display|Dolphin does not display |previews for plain text |previews for plain text |files if their extension is |files if their extension is |"log" |".log" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458092] New: Dolphin does not display previews for plain text files if their extension is "log"
https://bugs.kde.org/show_bug.cgi?id=458092 Bug ID: 458092 Summary: Dolphin does not display previews for plain text files if their extension is "log" Product: dolphin Version: 22.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sadiyumu...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Dolphin nicely displays previews of many file types selected by user in Settings as thumbnails, but when text files are selected almost all plain text files are displayed with some exceptions, like those with extension "log". The same file can be previewed as expected if the extension ".log" is removed or appended with ".txt" Such behavior may be understandable for extensions like ".bak", ".old", ".eml", ".html", ".xml" etc. but I think files with extension ".log" should be treated the same as ".txt". SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457295] From flexible spacer to flexible panel length
https://bugs.kde.org/show_bug.cgi?id=457295 --- Comment #7 from Sadi --- (In reply to Nate Graham from comment #6) OK, thank you very much. Just wanted to make sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457295] From flexible spacer to flexible panel length
https://bugs.kde.org/show_bug.cgi?id=457295 --- Comment #5 from Sadi --- Created attachment 151079 --> https://bugs.kde.org/attachment.cgi?id=151079=edit latte-dock top-left panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457295] From flexible spacer to flexible panel length
https://bugs.kde.org/show_bug.cgi?id=457295 --- Comment #4 from Sadi --- (In reply to Nate Graham from comment #3) Thanks. So you're saying that this requires some change in the widgets, and not the plasma panel, but I just want to confirm this, because those widgets already behave like that in latte-dock, which made me think in the first place that this is panel related. I'm adding an attachment showing a latte-dock top-left panel containing Application Launcher, Window Title, and Window AppMenu widgets, which only displays the first one when there's no window in focus, and the other two with varying length up to a set maximum point otherwise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457295] From flexible spacer to flexible panel length
https://bugs.kde.org/show_bug.cgi?id=457295 --- Comment #2 from Sadi --- (In reply to Nate Graham from comment #1) > You can already do this by setting the minimum panel size to be smaller then > the maximum panel size and then removing the flexible spacer item entirely. > Its purpose is really to create extra space between widgets, so there's > never a reason to add one at the beginning or end of a panel. Yes, but this gives a static panel length. As I've tried to explain, in a scenario where you have, for example, a top right panel with system tray, etc., and a top center panel with date and time, and a top left panel with application launcher, window title and global menu, your top left panel will need a flexible length because of the varying space requirements especially for the global menu. Your suggestion causes the panel to display sometimes a big empty space, and sometimes the menu can't fit in at the right end. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457296] option to enable accent color feature for each panel
https://bugs.kde.org/show_bug.cgi?id=457296 --- Comment #2 from Sadi --- (In reply to Nate Graham from comment #1) > Panels already respect the accent color if the Plasma theme allows it. If > the Plasma theme doesn't, then it won't. The bug in your screenshot is > caused by using a Plasma theme with hardcoded colors. I chose a different plasma theme just to have more transparency in my panels. I've just tested the Breeze plasma theme; it is the same. And the customized glassy plasma theme I use consts of only those files in addition to a metadata.desktop file containing no color values except ContrastEffect, BlurBehindEffect, and AdaptiveTransparency: background.svg button.svgz checkmarks.svgz panel-background.svg tasks.svg tooltip.svg viewitem.svg -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457343] Adaptive wallpaper accent color feature isn't working in Krita
https://bugs.kde.org/show_bug.cgi?id=457343 --- Comment #4 from Sadi --- (In reply to Halla Rempt from comment #3) > Set KRITA_NO_STYLE_OVERRIDE=ON, then Krita will be able to use the breeze > widget style. This style is disabled by default in 5.0.8 because it's buggy, > and fusion doesn't support this feature. Breeze is buggy? But this solution makes Krita out of place (looks like an alien app) in KDE Plasma DE. Is this something that can be added somewhere by users? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457343] Adaptive wallpaper accent color feature isn't working in Krita
https://bugs.kde.org/show_bug.cgi?id=457343 --- Comment #2 from Sadi --- (In reply to wolthera from comment #1) > while I can confirm, I have no idea what we'd need to do to fix this. If I may try to make a wild guess (as a user with no programming skills!), I think Krita's "Themes" component might be in need of some overhauling so as to bring it in line with other apps. For example, Kate has "Color Scheme", and Konsole has "Window Color scheme" (under Settings), and by default the "Default" option is selected. I think it means "just follow the global color scheme". When I click even the "Breeze Light Tinted" option there, things like title bar, tool bar etc. all become grey. So I guess static original color values are used in that case. I also guess "Default" options stops app-specific color settings, and lets the global system settings take control. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457343] New: Adaptive wallpaper accent color feature isn't working in Krita
https://bugs.kde.org/show_bug.cgi?id=457343 Bug ID: 457343 Summary: Adaptive wallpaper accent color feature isn't working in Krita Product: krita Version: 5.0.8 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: sadiyumu...@gmail.com Target Milestone: --- Krita does not conform with the latest KDE Plasma adaptive wallpaper accent color feature (after selecting the right/current color scheme via its menu (Settings > Themes > Breeze Light Tinted), although even GTK apps at least display the title bar with correct colors. Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457296] New: option to enable accent color feature for each panel
https://bugs.kde.org/show_bug.cgi?id=457296 Bug ID: 457296 Summary: option to enable accent color feature for each panel Product: plasmashell Version: 5.25.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 150997 --> https://bugs.kde.org/attachment.cgi?id=150997=edit different text and icon colors in panel and window title/tool bar It would be great to have an option for each panel/dock to include the new accent color feature as well, displaying black or white text and icons in line with the titlebars and toolbars. This would eliminate the "inconsistency" in the screenshot attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457295] New: From flexible spacer to flexible panel length
https://bugs.kde.org/show_bug.cgi?id=457295 Bug ID: 457295 Summary: From flexible spacer to flexible panel length Product: plasmashell Version: 5.25.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Spacer Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com Target Milestone: 1.0 It would be great if flexible spacer were a little more flexible by fading out completely any space not used (i.e. effectively resizing the panel) when it's positioned at the beginning or end of a panel. This will enable, for example, a panel/dock including only Application Launcher, Window Title, and Window AppMenu (or Global Menu) widgets to be as long as the first widget icon only when there’s no app window in focus, and as long as it is necessary to display the menu bar when an app window is in focus), as in Latte Dock. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457294] New: Setting transparency level for each panel/dock
https://bugs.kde.org/show_bug.cgi?id=457294 Bug ID: 457294 Summary: Setting transparency level for each panel/dock Product: plasmashell Version: 5.25.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: sadiyumu...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 It would be great if we could set different transparency level for each panel/dock on desktop, which it seems is controlled mostly by an image (e.g. panel-background.svg) in the plasma theme, applied to all panels. This feature will enable a desktop configuration, for example, consisting of a top panel with some or no transparency, a side panel with some transparency, and a dock with full transparency. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 425073] Can't configure software sources through Muon package manager
https://bugs.kde.org/show_bug.cgi?id=425073 Sadi changed: What|Removed |Added CC|sadiyumu...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456004] New: Terminal background color transparency lost
https://bugs.kde.org/show_bug.cgi?id=456004 Bug ID: 456004 Summary: Terminal background color transparency lost Product: dolphin Version: 22.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: sadiyumu...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 150181 --> https://bugs.kde.org/attachment.cgi?id=150181=edit Dolphin terminal panel warning message SUMMARY *** Following the upgrade to Plasma 5.25 the Terminal panel in Dolphin no longer displays the background color transparency although it has been set in the current profile and effective in Konsole window. *** STEPS TO REPRODUCE 1. Konsole > Settings > Edit Current Profile... > Appearance > Edit > Background color transparency: 50% 2. Dolphin > F4 OBSERVED RESULT Dolphin's terminal panel has no background color transparency, and if you right click in terminal panel, and select "Edit Current Profile..." and then "Appearance", an odd warning message appears as shown in the screenshot attached. EXPECTED RESULT Dolphin's terminal panel should have the same settings as in a regular Konsole window. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] [systemd boot] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #108 from Sadi --- (In reply to Nicolas Fella from comment #107) > (In reply to Nate Graham from comment #106) > > No, it's just that the systemd boot feature (which was turned on by default > > in Plasma 5.25) introduces a race condition that causes a bug with the > > existing functionality to play the startup sound. So people who opted in > > before 5.25 experienced this bug, then we failed to fix it in time, now > > everyone whose distro uses systemd and who hasn't explicitly opted out is > > experiencing it. > > It's the other way around. Using systemd-boot *fixes* the issue, that's why > for most people it appears fixed Does this mean that I still have the same issue going on after upgrading KDE neon from 5.24 to 5.25 because *systemd boot feature wasn't turned on* somehow during the upgrade process? How can I turn it on at least to check and confirm this please? Thank you. -- You are receiving this mail because: You are watching all bug changes.
