[krunner] [Bug 447405] Possibility to resize krunner window
https://bugs.kde.org/show_bug.cgi?id=447405 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #4 from Roy --- Created attachment 149367 --> https://bugs.kde.org/attachment.cgi?id=149367&action=edit How KRunner appears when enlarged I tried the solution posted on https://unix.stackexchange.com/a/638797 to no avail. It would be much appreciated if there was a way to override the font size in the UI. I've already overridden the width with a window rule that forces the "Minimum Size" property. It shows more text for each result, but the search box doesn't fill the extra space. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464592] Scrolling speed setting has no effect since Plasma 5.27 beta
https://bugs.kde.org/show_bug.cgi?id=464592 Roy changed: What|Removed |Added CC||xp...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462723] Desktop freezes for no obvious reason
https://bugs.kde.org/show_bug.cgi?id=462723 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #2 from Roy --- I've also experienced this issue in Kubuntu 22.10, on Plasma 5.27.3, Radeon graphics. Others have reported similar symptoms elsewhere: https://forum.linuxcnc.org/18-computer/40384-kde-plasma-desktop-freezes-but-machine-remains-operable https://forum.garudalinux.org/t/fixed-kde-becomes-unresponsive-but-mouse-can-still-move/11814 https://forums.opensuse.org/t/kde-freezes-randomly-and-only-the-mouse-pointer-works/127264/7 https://www.reddit.com/r/kde/comments/5gzu1l/kde_crashes_can_move_only_mouse/ For me, it seems to be more likely to occur after resuming from a long sleep (e.g. overnight). When it occurs, it's a progression; initially the desktop becomes less responsive and maybe typing or Alt + Tabbing will work a couple of times before input stops completely. The mouse is not impeded at all, it moves as smoothly as ever, but nothing is clickable. If the screen/computer goes to sleep again, I can still wake it by tapping a key, even though the X session doesn't respond to any presses. If I switch to a TTY, I can't see anything hogging resources in `top`. It's like the keyboard gets locked up by something because once I switch back to the X session with, I can no longer switch to any TTY unless I plug in an external USB keyboard. Then modifier key combinations of the built-in keyboard behave strangely in the TTY though regular characters work . If I restart the sddm service, then start a new X session, the situation is still degraded, I can type characters again, but the modifier keys on the built-in keyboard don't work properly. I have to reboot to get a working desktop again, sometimes I do Magic SysReq + REISUB because it's faster. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 464595] New: Latte dock crashes after boot.
https://bugs.kde.org/show_bug.cgi?id=464595 Bug ID: 464595 Summary: Latte dock crashes after boot. Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: royvanem...@gmail.com Target Milestone: --- Created attachment 155471 --> https://bugs.kde.org/attachment.cgi?id=155471&action=edit Latte-dock kcrash SUMMARY When booting my pc and launching an application latte-dock crashes. STEPS TO REPRODUCE 1. I boot my computer 2. Launch an application OBSERVED RESULT Latte-dock disappears and crashes after a few seconds. EXPECTED RESULT It not to crash 😅. SOFTWARE/OS VERSIONS Linux: Kubuntu 22.10 Kernel: 6.0.0 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 446333] `rz` keeps refreshing the file picker dialog
https://bugs.kde.org/show_bug.cgi?id=446333 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #1 from Roy --- I get the same thing, but running _Edit > Zmodem Upload_ from the main menu, without running `rz` first, uploads a file correctly for me. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444472] New: One-way clipboard sharing no longer works
https://bugs.kde.org/show_bug.cgi?id=72 Bug ID: 72 Summary: One-way clipboard sharing no longer works Product: kdeconnect Version: unspecified Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: roy-orbi...@devo.net.au Target Milestone: --- SUMMARY With the clipboard sharing plugin enabled on my (work) desktop, but disabled on my (personal & work) phone, I used to be able to copy text on my desktop and paste it on my phone, but keep my phone's clipboard private. Now nothing is copied to my phone. STEPS TO REPRODUCE 1. Disable clipboard plugin in Android app 2. Enable clipboard plugin in KDEConnect desktop settings 3. Copy some text on desktop OBSERVED RESULT Android clipboard content is unchanged EXPECTED RESULT Android clipboard should contain the copied text SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444472] One-way clipboard sharing no longer works
https://bugs.kde.org/show_bug.cgi?id=72 Roy changed: What|Removed |Added OS|Linux |Android 11.x -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448538] Overview effect runs at lower FPS
https://bugs.kde.org/show_bug.cgi?id=448538 Roy changed: What|Removed |Added CC||xp...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358277] Chrome apps assuming same icon from chrome browser, in Icon-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=358277 Roy changed: What|Removed |Added CC||xp...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393781] wallpaper cannot span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #4 from Roy --- What if, rather than another Positioning option as proposed in the above MR, a boolean setting was added to span screens? It could be placed at the end of this form layout so it applies to all Positioning options: https://github.com/KDE/plasma-workspace/blob/0fa3bbc4c63e84d5902e0950e4fa0559fe1988cf/wallpapers/image/imagepackage/contents/ui/config.qml#L90 If set to true, make the calculation for the wallpaper based on the dimensions of the entire desktop, rather than the single screen, then crop it to that screen's portion of the desktop based on its x, y, w & h. The exception is the Tiled option where it could simply change the offsets. It looks like the necessary dimensions are exposed: https://doc.qt.io/qt-5/qscreen.html#virtualGeometry-prop and its virtualGeometryChanged signal would allow the wallpaper to be "re-sliced" upon layout changes. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 --- Comment #3 from Roy --- Created attachment 135301 --> https://bugs.kde.org/attachment.cgi?id=135301&action=edit min size when try open menu from krusader -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 --- Comment #4 from Roy --- (In reply to Davide Gianforte from comment #1) So sorry for my late response. Please see inline for my reply. > Usually this kind of problems are related to the Qt libs, which version do > you have? [Roy] cannot find it, try search using qmake --version, but no output. > Does the menu opened near where the mouse pointer is located? [Roy] No, mouse pointer still in same position while I click the Krusader Menu > > Do you have the same issue with other programs? (I mean KDE programs - you > DE seems to be Gnome). Can you try to open the menu when the Krusader window > is not maximized? [Roy] Yes, I'm using DE Gnome. Please find additional attachment as requested. > Thank you -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 --- Comment #6 from Roy --- (In reply to Davide Gianforte from comment #5) > You can find the info from Krusader: Help - About Krusader - Libraries tab. > > Also, how many monitor do you have? I only using 1 laptop without external monitor -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 --- Comment #8 from Roy --- (In reply to Roy from comment #6) > (In reply to Davide Gianforte from comment #5) > > You can find the info from Krusader: Help - About Krusader - Libraries tab. > > > > Also, how many monitor do you have? > > I only using 1 laptop without external monitor Here is the Qt version: Qt 5.15.2 (built against 5.15.2) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 --- Comment #9 from Roy --- (In reply to Toni Asensi Esteve from comment #7) > Roy, Davide also asked you about what Qt libs version you have. You can find > it using Krusader: Help > About Krusader > Libraries tab. > > About the question "Does the menu opened near where the mouse pointer is > located?", you answered "No, mouse pointer still in same position while I > click the Krusader Menu", though he asked if ─on the screen─ the menu window > was opened in a place near the mouse pointer. Hi Toni, What I mean is mouse pointer position exactly below File word in tab list, but the menu position from File tab is far in the middle of the screen as Screenshot that I attached before. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372633] Unable to copy directory recursively from smb to mtp
https://bugs.kde.org/show_bug.cgi?id=372633 Roy changed: What|Removed |Added Status|RESOLVED|REOPENED Version|16.08.2 |19.12.3 CC||roy-orbi...@devo.net.au Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #4 from Roy --- I have encountered what could be the same underlying issue, but going in the opposite direction. In Dolphin, I have split panes with an MTP-mounted camera on one side and a Samba share on the other, moving a file directly from camera to share is impossible. The progress bar of the move notification either stalls quickly or never gets off 0, the latter being more typical. If I move the same file from camera to local drive, then local to share, it works flawlessly. The files are usually 500M - 1G, if that makes any difference. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384695] Configurable horizontal scrolling key (ALT or SHIFT) + WHEEL
https://bugs.kde.org/show_bug.cgi?id=384695 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #3 from Roy --- I'm not sure this is limited to Okular. Horizontal scrolling in many KDE settings dialogues, Dolphin, etc. is achieved with with Alt +. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372633] Unable to copy directory recursively from smb to mtp
https://bugs.kde.org/show_bug.cgi?id=372633 --- Comment #5 from Roy --- It looks like it can't access both sources in parallel, locking up upon trying. If I navigate to a folder on the smb share whilst a file is transferring from the mtp to a local drive, the smb pane will hang with a "loading" progress bar until the mtp transfer is complete. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 425179] New: Unable to find private use characters (no option to display all)
https://bugs.kde.org/show_bug.cgi?id=425179 Bug ID: 425179 Summary: Unable to find private use characters (no option to display all) Product: kcharselect Version: 19.12 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: roy-orbi...@devo.net.au Target Milestone: --- SUMMARY Difficult to browse or find particular characters, visually. STEPS TO REPRODUCE 1. Open, for example, a 'nerdfont' patched with special characters, such as Hack (from https://github.com/ryanoasis/nerd-fonts/releases/) 2. Try to locate a private use unicode character, such as, U+E0B0, by browsing through all category and block filters OBSERVED RESULT Certain characters can't be found in any combination of filters (by me, anyway), or require going through every block in every category until found. EXPECTED RESULT For all characters of a font to be accessible/visible even if the category + block is not known. Preferably be able to scroll through the entire font rather rather than be limited only to known, fixed ranges within it. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Some glyphs could only be found by learning their Unicode codepoints from another source, then typing them into the Find box. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 428348] Google Calendar synchronization setup is broken
https://bugs.kde.org/show_bug.cgi?id=428348 Roy changed: What|Removed |Added CC||royvanem...@gmail.com --- Comment #4 from Roy --- Created attachment 162020 --> https://bugs.kde.org/attachment.cgi?id=162020&action=edit google error I also can't sync with the google calendar. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 428348] Google Calendar synchronization setup is broken
https://bugs.kde.org/show_bug.cgi?id=428348 --- Comment #5 from Roy --- (In reply to Roy from comment #4) > Created attachment 162020 [details] > google error > > I also can't sync with the google calendar. OS: Kubuntu 23.04 x86_64 Kernel: 6.3.5-060305-generic Plasma: 5.27.4 Frameworks: 5.104.0 QT: 5.15.8 X11 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 247270] Option to display menubar only when holding down (or another meta-key)
https://bugs.kde.org/show_bug.cgi?id=247270 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #8 from Roy --- Over a decade later, is there another standard way to give focus to the menu bar? I haven't found one, which is a bit of a disappointment after leaving Windows. One thing to be wary of would be the Sticky Keys accessibility feature. If Lock Keys is off, pressing Alt twice would work, but with it on (the default) it would have to be a hold or something else. Best to consult with someone who relies on that feature. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] New: Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 Bug ID: 430333 Summary: Wrong position for list command for each tab in Krusader GUI Product: krusader Version: 2.7.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: x.roy@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 134043 --> https://bugs.kde.org/attachment.cgi?id=134043&action=edit screenshot krusader issue SUMMARY STEPS TO REPRODUCE 1. open Krusader 2. click File or edit or any tab in the upper list 3. The list from each tab will appear around in the middle of the screen, not below from each tab name. OBSERVED RESULT <> EXPECTED RESULT list position should below every tab name SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora ver 33 64 bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 Roy changed: What|Removed |Added CC||xp...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392164] Button for sharing clipboard content
https://bugs.kde.org/show_bug.cgi?id=392164 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #7 from Roy --- FWIW, the Android app now seems to require explicit copying of the clipboard via a user action, though I think it's a consequence of an API change for security rather than a deliberate choice. A small system toast appears that mentions which app has "pasted" (read) from the clipboard upon tapping the menu item. Prefs at both ends to choose the level of sharing is ideal, and still relevant to older Android versions. A bit related, using an app that can type passwords as a keyboard into KDE Connect's Remote Input interface is better than copy + paste, e.g. KeePassDX. -- You are receiving this mail because: You are watching all bug changes.
[ksystemstats] [Bug 490829] Use of nvidia-smi causes jittery desktop performance with GSP enabled
https://bugs.kde.org/show_bug.cgi?id=490829 Roy changed: What|Removed |Added CC||xp...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462338] New: Selecting text copies to clipboard twice with double-click
https://bugs.kde.org/show_bug.cgi?id=462338 Bug ID: 462338 Summary: Selecting text copies to clipboard twice with double-click Classification: Applications Product: konsole Version: 22.08.3 Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: roy-orbi...@devo.net.au Target Milestone: --- SUMMARY With *Copy on select* enabled in one's Konsole profile, unnecessary extra entries are created in clipboard history when beginning a selection with a double-click. STEPS TO REPRODUCE 1. Ensure the above feature is enabled in the profile's mouse settings. 2. Display two or more "words" in any terminal program separated by spaces, e.g. just typing words in your shell. 3. Select, avoiding mouse-aware program detection, by holding Shift and double-clicking the first word, but without releasing the mouse button. Drag to extend the selection to adjacent words then release the mouse button and Shift. 4. Inspect the clipboard history in Klipper. OBSERVED RESULT Two new entries are added: the final selection, and the word under where selection began. EXPECTED RESULT Only one new entry, the final selection, should be added, based on when the mouse button was released. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 461291] In-app keyboard shortcuts definitions using the Numeric Keypad keys are not possible
https://bugs.kde.org/show_bug.cgi?id=461291 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #1 from Roy --- I have experienced the same issue on Kubuntu. Was on 22.04 with Plasma 5.24, have several window-positioning shortcuts defined to use the number pad, e.g. Quick tile top right is "Meta + Num + 9". Sometime since upgrading to 22.10 with Plasma 5.26 (backported) these have broken, i.e. the existing defined shortcuts are all no-ops. If I try to (re)define any shortcut with the numpad keys, they show up as regular numbers, e.g. "Meta + 9". The ones without "Num +" conflict with default shortcuts for task manager. I can live without those, but it's a BC breakage fore sure. This may be related to but not the same as #443225, because I do not have the "Numeric keypad always enters digits (as in macOS)" compatibility option enabled. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #23 from Roy --- So what is the expected migration path for "Send keyboard input" shortcuts? I have a few to simulate missing keys from my notebook's built-in keyboard, and provide parity with some programs that are missing common shortcuts. What "application" can one add to to the other Shortcuts section that can perform equivalent actions? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 461291] In-app keyboard shortcuts definitions using the Numeric Keypad keys are not possible
https://bugs.kde.org/show_bug.cgi?id=461291 --- Comment #2 from Roy --- I forgot to add that it still works under X, I was trying out a Wayland session (but probably won't stick to it while bug 455444 exists). I also should have written bug 443225 to auto-link in the prev. comment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 --- Comment #26 from Roy --- Thanks, it looks very comprehensive for what it does, but I don't think it'll be suitable. The readme states "It is not a tool for keyboard macro's [sic] or complex event manipulation". I don't think there's a simple way to give it awareness of what the current program and its window properties are, and adjust keyboard bindings accordingly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 --- Comment #28 from Roy --- @AndrewShark I am confused as to whether you're saying it is or isn't possible. >From your comments it seems the upgrade path is to learn the intricacies of evsieve to create desired mappings, create a system- or user-level systemd service to reliably run each evsieve invocation, add some relevant commands to a file in /etc/sudoers.d/ so that one can use sudo to write toggle instructions to the FIFOs without having to authenticate each time, and then not be able to trigger said toggles automatically anyway because there's nothing to run tasks based on specific windows gaining/losing focus. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 --- Comment #13 from Roy --- (In reply to Davide Gianforte from comment #12) > Hi Roy, can you post the output of the "xrandr" command? There are several > bugs reported in Qt addressing to this issue Hi Davide, please find below output as requested: $ xrandr Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767 XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170mm 1920x1080 59.96*+ 1440x1080 59.99 1400x1050 59.98 1280x1024 59.89 1280x960 59.94 1152x864 59.96 1024x768 59.92 800x600 59.86 640x480 59.38 320x240 59.52 1680x1050 59.95 1440x900 59.89 1280x800 59.81 720x480 59.71 640x400 59.95 320x200 58.96 1600x900 59.95 1368x768 59.88 1280x720 59.86 1024x576 59.90 864x486 59.92 720x400 59.55 640x350 59.77 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378141] New: Plasma Crashing after more than 3 VPN's are in concurrent use
https://bugs.kde.org/show_bug.cgi?id=378141 Bug ID: 378141 Summary: Plasma Crashing after more than 3 VPN's are in concurrent use Product: plasmashell Version: 5.5.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: su...@getnada.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.4.0-66-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: B&E - Unusual behavior I noticed: The Entire Plasma Desktop would crash when I tried to chain,or use,more than three concurrent VPN at a time - Custom settings of the application: OpenVPN services was used (This probably is irrelevent,but I will include it anyway,) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54243ea8c0 (LWP 30644))] Thread 9 (Thread 0x7f5367fff700 (LWP 30656)): #0 0x7ffd5ecf39a9 in ?? () #1 0x7ffd5ecf3cd5 in clock_gettime () #2 0x7f541eb10c86 in __GI___clock_gettime (clock_id=1, tp=0x7f5367ffea00) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f541f29cb86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f541f421279 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f541f4217e5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f541f422bce in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f541b88b91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f541b88c2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f541b88c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f541f4237eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f541f3cab4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f541f1e7834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f5422415ed6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f541f1ec7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f541e2d96ba in start_thread (arg=0x7f5367fff700) at pthread_create.c:333 #16 0x7f541eb0282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f536e379700 (LWP 30655)): #0 0x7f541eaf6b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f541b88c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f541b88c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f541f4237eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f541f3cab4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f541f1e7834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f541f1ec7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f541e2d96ba in start_thread (arg=0x7f536e379700) at pthread_create.c:333 #8 0x7f541eb0282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f536eb9a700 (LWP 30654)): #0 0x7f541b8d0a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f541b88bdcc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f541b88c330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f541b88c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f541f4237eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f541f3cab4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f541f1e7834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f536f024035 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #8 0x7f541f1ec7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f541e2d96ba in start_thread (arg=0x7f536eb9a700) at pthread_create.c:333 #10 0x7f541eb0282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f53f5773700 (LWP 30652)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5423e34bd4 i
[dolphin] [Bug 378402] New: Doesn't register mouse clicks on second screen
https://bugs.kde.org/show_bug.cgi?id=378402 Bug ID: 378402 Summary: Doesn't register mouse clicks on second screen Product: dolphin Version: 16.12.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: maila...@gmail.com Target Milestone: --- If I move a window to my second monitor (both 4k same screens). The window panels (places, location bar etc) register clicks but not in the file listing. I can use the keyboard to move around but the mouse clicks do nothing - right or left click. If I then move the window back to my primary screen it works instantly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382786] New: KWin crashes and moves apps couple pixels higher
https://bugs.kde.org/show_bug.cgi?id=382786 Bug ID: 382786 Summary: KWin crashes and moves apps couple pixels higher Product: kwin Version: 5.10.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: maila...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.2) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.4.0-87-generic x86_64 Distribution: Maui -- Information about the crash: Just browsing firefox on 4k screen with VirtualBox open and the Virtualbox apps move up so title bars aren't visible after KWin crashes. Only effect is a screen flash and the apps have moved uo. Easily fixed by moving them down as Kwin restarts instantly The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe5cf931940 (LWP 7190))] Thread 7 (Thread 0x7fe5c502b700 (LWP 7207)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe5e34a09fb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fe5deb3447d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fe5deb34d55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fe5e349fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5df4fa6ba in start_thread (arg=0x7fe5c502b700) at pthread_create.c:333 #6 0x7fe5e58243dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fe5aa7fe700 (LWP 7202)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe5e28256f4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fe5e2825739 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fe5df4fa6ba in start_thread (arg=0x7fe5aa7fe700) at pthread_create.c:333 #4 0x7fe5e58243dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fe5b1021700 (LWP 7200)): #0 0x7fe5e57e930d in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe5e581ad54 in usleep (useconds=) at ../sysdeps/posix/usleep.c:32 #2 0x7fe5b314dc80 in ?? () from /usr/lib/x86_64-linux-gnu/dri/amdgpu_dri.so #3 0x7fe5b2879552 in ?? () from /usr/lib/x86_64-linux-gnu/dri/amdgpu_dri.so #4 0x7fe5b28795a5 in ?? () from /usr/lib/x86_64-linux-gnu/dri/amdgpu_dri.so #5 0x7fe5df4fa6ba in start_thread (arg=0x7fe5b1021700) at pthread_create.c:333 #6 0x7fe5e58243dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fe5c603c700 (LWP 7198)): #0 0x7fe5e581870d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe5e36bbaaa in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fe5e36bd392 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fe5e366b0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe5e349af64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5de668bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fe5e349fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe5df4fa6ba in start_thread (arg=0x7fe5c603c700) at pthread_create.c:333 #8 0x7fe5e58243dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fe5ccb8a700 (LWP 7194)): #0 0x7fe5e581870d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe5e36bbaaa in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fe5e36bd392 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fe5e366b0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe5e349af64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5e5e37735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fe5e349fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe5df4fa6ba in start_thread (arg=0x7fe5ccb8a700) at pthread_create.c:333 #8 0x7fe5e58243dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fe5ce685700 (LWP 7193)): #0 0x7fe5e581870d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe5e4939c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fe5e493b8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so
[kwin] [Bug 495345] Display monitor errors/issues after wake from sleep
https://bugs.kde.org/show_bug.cgi?id=495345 Roy <1q13wi...@mozmail.com> changed: What|Removed |Added Resolution|UPSTREAM|NOT A BUG --- Comment #4 from Roy <1q13wi...@mozmail.com> --- This seems to have stopped happening, closing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 495345] New: Display monitor errors/issues after wake from sleep
https://bugs.kde.org/show_bug.cgi?id=495345 Bug ID: 495345 Summary: Display monitor errors/issues after wake from sleep Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 1q13wi...@mozmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 175229 --> https://bugs.kde.org/attachment.cgi?id=175229&action=edit Screen error when window move to right side of screen SUMMARY When waking the pc from sleep, the following occurs: 1. The default lock screen wallpaper differs from what it was on the last successful reboot (not really a functional issue) 2. On logging in, the screen resolution changes from 5120x1440 to 3840x1440 3. On changing back to 5120, the 240hz option is not available anymore. It is available for all resolutions below 5120 4. The right 1/5th (ish) of the screen seems to become corrupted static when a window is place in that region. This region also seems to be variable, as in it follows specific elements of the window when moving it around. STEPS TO REPRODUCE 1. Reboot PC and login, no screen issue present, no display setting issues present 2. Send PC to sleep 3. Wake PC and login, above issues occur OBSERVED RESULT Display setting issues and visual screen region issues occur after wake from sleep. EXPECTED RESULT No issues occur, all settings remain as they were before sleep. All screen regions remain usable and free from visual error. SOFTWARE/OS VERSIONS Arch Linux 6.11.5-arch1-1 (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION The resolution change and screen region errors only started occurring after my last system update within the last week or so. These issues were not occurring before then. It is possible this is an nvidia driver update issue, but I'm not totally sure. These issues do not appear after rebooting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 495345] Display monitor errors/issues after wake from sleep
https://bugs.kde.org/show_bug.cgi?id=495345 --- Comment #3 from Roy <1q13wi...@mozmail.com> --- (In reply to Zamundaaa from comment #2) > Yeah I don't see how KWin could cause either modes disappearing or static on > the screen - it sounds a lot like the driver fails link training with the > display. Please report them to > https://forums.developer.nvidia.com/c/gpu-graphics/linux > > About > > The default lock screen wallpaper differs from what it was on the last > > successful reboot > that's odd, and might be worth reporting to kscreenlocker Yea that sounds like it tracks. I'll see if it happens again, it seems potentially intermittent. If not I'll close this in a few days. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470862] New: Krita crashing when attempting to resize or move (using transform) a very big layer stack
https://bugs.kde.org/show_bug.cgi?id=470862 Bug ID: 470862 Summary: Krita crashing when attempting to resize or move (using transform) a very big layer stack Classification: Applications Product: krita Version: 5.1.5 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: royblument...@gmail.com Target Milestone: --- Created attachment 159578 --> https://bugs.kde.org/attachment.cgi?id=159578&action=edit Krita System Details File Thank you very much indeed for Krita, and for the ability to report bugs. Here's my report. If you need to work on the file itself, here's a link to it in my Dropbox: https://www.dropbox.com/s/u6h5nc9hixwom0s/2023-05-10%20Nestle%20--%20scenes%2015%20to%2019.kra?dl=0 The layer stack probably causing the trouble is inside "15 Sustainawhat", and is titled "Room". It's the lowest stack in the cluster. SUMMARY Krita crashing when attempting to resize or move (using transform) a very big layer stack. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports The documentation on the above page says that this is irrelevant if using the appimage version of Krita, which I am using. STEPS TO REPRODUCE 1. I have a complicated multi-layer document (approx 1 gB estimated by the Krita bottom info bar -- the actual saved file is 80mb) that I'm using to create animation stop-frames. One of those layers is a top-down view of a room, containing the following layer stacks: floor, walls, furniture, people, decoration and items. The floor, walls, and furniture stacks are substantially larger than what appears in the view window. This is so I can move the view to a different part of the room, without having to redraw everything. 2. When I attempt to move or resize the overall image, which is a folder (layer stack) containing all of the lower layer stacks, the following happens... 3. The preview of the move completes. But the progress bar shows 0% for several seconds. It quickly goes to 98%. But at this point, the cursor turns to a spinning circle of death. 4. After several attempts to close the document, I reach the "force quite/wait" menu. Only "force quite" works. OBSERVED RESULT Force quit causes a loss of any work done in the session after a manual save and before the move/resize operation. Also, there is no automatic backup copy of the file. (Mine is set to autosave every minute.) EXPECTED RESULT Move/resize to complete, with no crash. Autosaves to be present in case of crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Zorin OS 16.2 SYSTEM: AMD Ryzen 5 5600g with Radeon graphics x 12 AMD Renoir 64bit X11 windowing 32gB RAM 1tb SSD KDE Plasma Version: KDE Frameworks Version: Qt Version: I can't seem to find the KDE info. When I click on the "About KDE" dialogue in Krita, it just tells me various interesting info about KDE, but not the version itself. ADDITIONAL INFORMATION Attached as a separate file is the Krita System Information for use with bug reports. I've pasted the Krita Usage Log info from this morning's session. KRITA DID NOT CLOSE CORRECTLY SESSION: 10 Jun 2023 09:16:37 +0200. Executing /tmp/.mount_krita-XJxvZ8/usr/bin/krita Krita Version: 5.1.5, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 11796 -- -- -- -- -- -- -- -- 10 Jun 2023 09:16:37 +0200: Style: fusion. Available styles: Windows, Fusion 10 Jun 2023 09:16:38 +0200: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Wed Aug 24 20:39:52 2022 10 Jun 2023 09:16:52 +0200: Importing application/x-krita to application/x-krita. Location: /home/roy/Dropbox/2023-03-09 Nestle -- 'RE' Educational Animation Series/2023-05-10 Nestle -- scenes 15 to 19.kra. Real location: /home/roy/Dropbox/2023-03-09 Nestle -- 'RE' Educational Animation Series/2023-05-10 Nestle -- scenes 15 to 19.kra. Batchmode: 0 10 Jun 2023 09:16:59 +0200: KisAppimageUpdater: update check finished. Result: 0 Exit status: 0 path: /home/roy/Applications/krita-5.1.5-x86_64_b406ba791f7a7f489e281d038c134c52.appimage output: 10 Jun 2023 09:17:02 +0200: Loaded image from application/x-krita. Size: 3200 * 1840 pixels, 4.16667 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 153 10 Jun 2023 09:21:18 +0200: Saving Document /home/roy/Dropbox/2023-03-09 Nestle -- 'RE' Educational Animation Series/2023-05-10 Nestle -- scenes 15 to 19.kra as /home/roy/Dropbox/2023-03-09 Nestle -- 'RE' Educational Animation Se
[kde] [Bug 471063] New: Apps launched from calc key breaks num lock/number pad use
https://bugs.kde.org/show_bug.cgi?id=471063 Bug ID: 471063 Summary: Apps launched from calc key breaks num lock/number pad use Classification: I don't know Product: kde Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: roy-orbit...@devo.net.au Target Milestone: --- SUMMARY When I launch apps from my Calculator key (keycode 148, keysym 0x1008ff1d, XF86Calculator), they either don't run or behave as if Num Lock is off STEPS TO REPRODUCE 1. Use keyboard with a Calculator key 2. Go to System Settings > Shortcuts and assign that key to launch an app (I used KCalc), it should show as "Launch (1)" 3. Ensure Num Lock is on 4. Press the Calc key OBSERVED RESULT Depends on app, will not launch, or launches but does not accept numeric keys, e.g. `.` behaves as Del. EXPECTED RESULT Normal launch, numeric keys produce input. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I normally have that button assigned to launch KCalc. I have Num Lock on all the time, including at boot, and haven't noticed any problems with other apps respecting number pad keys/num lock, generally. It occurs only from that type of launch; if I set and use a different shortcut, e.g. the Pause key or Ctrl + Alt + K, or launch it from KRunner or the main apps menu, it's fine. If I switch to another app and back, or toggle Num Lock off and on, the app respects Num Lock again. I tested by assigning the Calc button to launch KCharSelect. It assigns okay, but won't launch the app. The same occurs if I set it to launch Kate. Assigning it to launch Emoji Selector produces similar behaviour to Kcalc, e.g. 2, 4, 6, & 8 move the selection highlight the same way dedicated arrow keys do. I wonder if it's somehow related to bug 433645, though I am able to assign shortcuts with it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 Roy Orbitson changed: What|Removed |Added CC||roy-orbit...@devo.net.au --- Comment #268 from Roy Orbitson --- So what's the right workaround for us users while we wait for a 7yo upstream bug to be fixed, that may not even fully solve the problem? There are countless questions about it in all the fora, with mostly conflicting solutions offered. I just want my language + ISO date. I've tried several things, including a custom locale (https://unix.stackexchange.com/a/204329) which looks sensible except KDE doesn't respect it. To get "Australian-ish" in KDE, in System Settings, I have the Languages set to en_GB above en_US (because en_AU is unknown to it), then individual formats set to Australian, except the date which is Swedish. Apparently the latter disappeared for some time but now it's back (https://superuser.com/q/1162283). I tried en_001 for time formats, too. My `localectl` output is this: >System Locale: LANG=en_AU.UTF-8 > LANGUAGE=en_AU:en_GB:en > LC_TIME=en_AU.UTF-8@isodate >VC Keymap: (unset) > X11 Layout: us >X11 Model: pc105 KDE cannot/does not use these in a graphical session. Bash in Konsole (& other programs) that would function as desired with those locale settings don't get them. Their envs inherit the mishmash settings from KDE, despite KDE not using glibc locales itself. I looks like KDE sets these env vars though they can point to different translation & localisation resources depending on the program. Examples: Python (notably when using apt) will stumble on the en_001 locale, and `date +%x\ %X` produces "07/03/24 12:55:56" even though KDE assures me that en_SE's short date format is ISO. I don't change env vars via Autostart's Login & Pre-startup scripts because I think these would interfere with and/or be overridden by the selections in Region & Language that I need for GUI programs. My virtual terminals are fine. In tty6, I run `locale` and get: >LANG=en_AU.UTF-8 >LANGUAGE=en_AU:en_GB:en >LC_CTYPE="en_AU.UTF-8" >LC_NUMERIC="en_AU.UTF-8" >LC_TIME=en_AU.UTF-8@isodate >LC_COLLATE="en_AU.UTF-8" >LC_MONETARY="en_AU.UTF-8" >LC_MESSAGES="en_AU.UTF-8" >LC_PAPER="en_AU.UTF-8" >LC_NAME="en_AU.UTF-8" >LC_ADDRESS="en_AU.UTF-8" >LC_TELEPHONE="en_AU.UTF-8" >LC_MEASUREMENT="en_AU.UTF-8" >LC_IDENTIFICATION="en_AU.UTF-8" >LC_ALL= But under Konsole I get: >locale: Cannot set LC_ALL to default locale: No such file or directory >LANG=en_GB.UTF-8 >LANGUAGE=en_GB:en_US >LC_CTYPE="en_GB.UTF-8" >LC_NUMERIC=en_AU.UTF-8 >LC_TIME=en_SE.UTF-8 >LC_COLLATE="en_GB.UTF-8" >LC_MONETARY=en_AU.UTF-8 >LC_MESSAGES="en_GB.UTF-8" >LC_PAPER=en_AU.UTF-8 >LC_NAME=en_AU.UTF-8 >LC_ADDRESS=en_AU.UTF-8 >LC_TELEPHONE=en_AU.UTF-8 >LC_MEASUREMENT=en_AU.UTF-8 >LC_IDENTIFICATION=en_AU.UTF-8 >LC_ALL= I can't override the settings in .profile as shells in Konsole are not login shells. They do read .bashrc but this probably doesn't help any other programs that use glibc locales. I don't know what to do. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421018] Window size for barcode (QR code) is too small, so the bar code is hidden
https://bugs.kde.org/show_bug.cgi?id=421018 --- Comment #5 from Roy Orbitson --- As per my previous comment, my window rule also requires a substring match on the window title. Does Plasma 6 not provide a usable title for this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 Roy Orbitson changed: What|Removed |Added CC||roy-orbit...@devo.net.au --- Comment #37 from Roy Orbitson --- For a solution, instead of a single, mutable split stop, could it remember however many stops as have been created by resizing, plus an immutable 50/50 stop, so that Meta + Arrow keys could cycle through those before moving to opposite edges and adjacent screens? The resizing of adjacent windows could also be limited to only the last most recently used windows that are snapped to both an opposite edge/corner and the shared edge of the window being resized. Windows behind those would remain untouched but could, of course, be snapped to the new stop by the user. Unused stops would need to be garbage collected, otherwise there would still be the reported memory effect and the possible stops would grow out of control. For getting around the current problem, I found an accurate way to reset to 50/50 is to use KRuler: 1. snap it to a side 2. press D to change direction if 0 is not at the screen's edge 3. resize it to half your monitor resolution 4. hover your mouse over the last pixel to check its exact length 5. repeat steps 3 & 4 until it's correct It's quite a frustrating UX. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 --- Comment #45 from Roy Orbitson --- @matterhorn The problem with adding modifiers and new shortcuts as a solution is that they're not as naturally discoverable, and the Tiling Editor also uses Shift + drag. @Joe S I agree there needs to be a pref to disable adjacent window resizing for quick-tiled windows. I still think the 50:50 + self-pruning extra stops would be great & it would be immediately discoverable through existing shortcuts. The Tiling editor is good but it's not the same: windows must be dragged to snap, only one regular layout can be in effect, layouts can't be saved, and trying to emulate multiple simultaneous layouts by using overlapping floating tiles gives a pretty rough result. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 484125] New: ksmserver-logout-greeter could sync visual state to be friendlier on multi-monitor setups
https://bugs.kde.org/show_bug.cgi?id=484125 Bug ID: 484125 Summary: ksmserver-logout-greeter could sync visual state to be friendlier on multi-monitor setups Classification: Plasma Product: kscreenlocker Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: roy-orbit...@devo.net.au Target Milestone: --- SUMMARY The UX of the Shut down/Sleep/Log out screens could be greatly improved if they synchronised visual state. STEPS TO REPRODUCE 1. Press Ctrl + Alt + Del in session in a multi-monitor environment. 2. Press arrow keys or Tab. OBSERVED RESULT Which monitor gains initial focus and responds to input is not consistent, may not be where user is already looking, or not displaying output at all (e.g. in cases of multiple inputs to single display). EXPECTED RESULT All ksmserver-logout-greeter windows to respond in unison so the user is always looking at the "right" monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427279] New: Choma Key, Position And zoom And many effects are not working correctly please do something.
https://bugs.kde.org/show_bug.cgi?id=427279 Bug ID: 427279 Summary: Choma Key, Position And zoom And many effects are not working correctly please do something. Product: kdenlive Version: 20.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: sudiproy2...@gmail.com Target Milestone: --- Created attachment 132081 --> https://bugs.kde.org/attachment.cgi?id=132081&action=edit Final Unwanted REsult... You can see the black Background but I need the background video SUMMARY Choma Key, Position And zoom And many effects are not working correctly please do something. STEPS TO REPRODUCE 1. Add A background video 2. Add A green screen overlay video above the background video 3. Add chroma key effect to green screen overlay and select green screen color 4. Add Position And zoom effect to green screen overlay and scale it as the desired size. 5. Render the video to mp4 file OBSERVED RESULT You can't see the background of the background video. EXPECTED RESULT You can see the background of the background video with the green screen overlay video. SOFTWARE/OS VERSIONS Windows: 7 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.
[kde] [Bug 471063] Apps launched from calc key breaks num lock/number pad use
https://bugs.kde.org/show_bug.cgi?id=471063 --- Comment #3 from Roy Orbitson --- It only happens under X11. I didn't switch to Wayland because it misbehaved a bit for me, and because of Bug 455444 (the closing of which I disagree with). I guess I could just use an X11 session only if I need to edit those commands, but I don't enjoy closing everything I'm working on in order to do so. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446389] [WAYLAND] Kwin doesn't differentiate Meta+Num+1 from Meta+1
https://bugs.kde.org/show_bug.cgi?id=446389 Roy Orbitson changed: What|Removed |Added CC||roy-orbit...@devo.net.au --- Comment #7 from Roy Orbitson --- Possible dupe of bug 413310 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471063] Apps launched from calc key breaks num lock/number pad use
https://bugs.kde.org/show_bug.cgi?id=471063 --- Comment #5 from Roy Orbitson --- I did: "It only happens under X11". Wayland's okay. I tried using Wayland for my regular session, and was immediately reminded why I couldn't stick with it: bug 413310 breaks all the shortcuts I use for window positioning and virtual desktops. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471063] Apps launched from calc key breaks num lock/number pad use
https://bugs.kde.org/show_bug.cgi?id=471063 --- Comment #7 from Roy Orbitson --- Were you able to reproduce it? What happens from here, out of curiosity? I can live with the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470429] Screen shows as "disconnected" after switching monitor. Missing desktop background and panel.
https://bugs.kde.org/show_bug.cgi?id=470429
Roy Orbitson changed:
What|Removed |Added
CC||roy-orbit...@devo.net.au
--- Comment #2 from Roy Orbitson ---
I regularly encounter the same issue on a similar setup: two external monitors
on a notebook and the built-in monitor disabled. Physically unplugging then
reconnecting the "disconnected" display usually gets its connection status
reset.. After doing this, I sometimes need to use the Panels and Desktop
Management dialogue to move thins back to the correct monitors.
I don't know if it's a separate issue but, like bug 427278, Plasma will also
"forget" the config eventually, and at a fresh login will have incorrect
monitors enabled/disabled or has the externals as duplicates of each other,
though I've never set it that way. The login screen (sddm?) never seems to
respect these arrangement settings, and will re-enable the built-in monitor
and/or disable one of the externals.
I tried using autorandr, which applies profiles perfectly from manual
invocation, but seems to conflict with Plasma's own automatic detection. If
anyone knows how to disable Plasma's detection so I can try autorandr properly,
please tell me.
I reduce the frustration by backing up this config (after I've made any changes
and everything's arranged right):
cp -a ~/.config/plasma-org.kde.plasma{,-BACKUP}.desktop-appletsrc
When things go awry again, I log out of any graphical sessions, open a TTY
session, restore it as follows, then log in again:
cp -a ~/.config/plasma-org.kde.plasma{-BACKUP,}.desktop-appletsrc
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 440722] Delete an entry from klipper popup at mouse position with Delete key
https://bugs.kde.org/show_bug.cgi?id=440722 Roy Orbitson changed: What|Removed |Added CC||roy-orbit...@devo.net.au --- Comment #2 from Roy Orbitson --- Would really like this but there is a workaround. You can bring up the tray version with the same shortcut, whose keyboard navigation is essentially the same but the delete key works as desired thanks to the change in the previous bug. It also shows as one contiguous list unlike the contextual one that requires you to select the `...` dummy item to see the next page of items. Open the Configure System Tray dialogue, select the Entries tab, scroll down to Clipboard and and click its shortcut button to reassign Meta + V (or whatever) to that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 300532] Custom keyboard shortcuts are reset on reboot or logout – KDE 4, KDE 5
https://bugs.kde.org/show_bug.cgi?id=300532 Roy Orbitson changed: What|Removed |Added CC||roy-orbit...@devo.net.au --- Comment #46 from Roy Orbitson --- Created attachment 162069 --> https://bugs.kde.org/attachment.cgi?id=162069&action=edit Warning dialogue when assigning shortcut that was reset I think I'm encountering the same bug with a slightly different symptom. I assign Meta + V to the clipboard widget instead of the cursor-position pop-up, to work around bug 440722. After each logon, the shortcut fails. I have to reassign it even though the warning says it's already assigned to the same thing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421018] Window size for barcode (QR code) is too small, so the bar code is hidden
https://bugs.kde.org/show_bug.cgi?id=421018 Roy Orbitson changed: What|Removed |Added CC||roy-orbit...@devo.net.au --- Comment #2 from Roy Orbitson --- Since this is still an issue in current releases of Plasma, the easiest workaround is to create a window rule. While the undersized QR dialogue has focus, press Alt +F3 and go to More Actions > Configure Special Window Settings. Give it a more useful description, and edit the rule so it matches "plasmashell" for the window class, "Dialog Window" for the type, substring matches the title "Mobile Barcode" (or whatever it shows in your language). Then add properties to initially apply a position and force a minimum size, e.g. size 1280x640 and pos. 320, 220 will centre it on a 1920x1080 screen and make it large enough to show both the QR and Matrix codes. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 --- Comment #46 from Roy Orbitson --- >There's nothing to fix Well, we've gone from a point-and-click interface that allowed users to draw gestures, select specific programs & windows and neatly organise things to enhance their desktop experience to ‘you can launch programs, maybe some specific actions if the program exposes them, or you can write your own software, it's not our problem.’ KDE knows this does not have the same specificity and is not nearly as accessible to users. That's not nothing, to me. I understand that this specific KCM is not really fixable for Wayland, but it would be great if KDE could add _something_ to their roadmap. Having at least a plan for window/app targeting and a little input mapping as a nice-to-have feature would be preferable to this ‘go away’-style bug closure. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471063] Apps launched from calc key breaks num lock/number pad use
https://bugs.kde.org/show_bug.cgi?id=471063 --- Comment #1 from Roy Orbitson --- Just to make this bug even weirder, It seems to be related to use of external keyboards. If I launch from an external keyboard's Calc key, neither its numpad nor any other connected keyboard (including the one built-in to my notebook) behave as though Num Lock is on, despite all indicator lights showing it is. However, If I launch from the built-in keyboard's Calc key, its numpad will work as expected like Num Lock is on, unless I press any key on an external keyboard's numpad, then all numpads begin to behave as though Num Lock has been turned off, though the Num Lock keys have never been touched. I've also discovered the effects aren't limited to Calc key launches as I'd previously thought. If I launch KCalc from KRunner, the numpad behaves, but as soon as I press a numpad key on any other keyboard, they all begin to (mis)behave as if Num Lock is off. I've tried this with multiple external keyboards, including ones that have no Calc key. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 491924] New: Clipboard is auto-synced on connection establishment though pref is off
https://bugs.kde.org/show_bug.cgi?id=491924 Bug ID: 491924 Summary: Clipboard is auto-synced on connection establishment though pref is off Classification: Applications Product: kdeconnect Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: roy-orbit...@devo.net.au CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY On my PC, in KDE Connect's device settings for my phone, Clipboard is enabled but its setting to automatically share is off. This preference seems to be ignored when devices establish a connection on the same network. STEPS TO REPRODUCE 1. Enable clipboard sharing on PC and Android devices. Set PC to not auto share anything. 2. Ensure devices are not connected to same LAN (e.g. temporarily disable wifi on phone). 3. Wait for PC to register that it's lost the connection to the phone. 4. Copy something unique on PC, i.e. not in clipboard history, or modify the last clipboard item. 5. Connect devices to same LAN again. OBSERVED RESULT Clipboard of Android device now contains the last item copied on the desktop, despite no explicit share (hamburger menu > Send Clipboard). I actually get a standard copy popup on my phone, with share and edit options, as if I had done it there. EXPECTED RESULT No change to Android clipboard. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION The pref is respected and further copy actions aren't propagated whilst a connection is maintained. -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 410250] New: Login Failure
https://bugs.kde.org/show_bug.cgi?id=410250 Bug ID: 410250 Summary: Login Failure Product: abakus Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: developerb...@gmail.com Reporter: testerdeb...@gmail.com Target Milestone: --- Created attachment 121756 --> https://bugs.kde.org/attachment.cgi?id=121756&action=edit Login fail screenshot SUMMARY: Login Error STEPS TO REPRODUCE 1. Enter Correct Username 2. Enter Correct Password 3. Home screen opens OBSERVED RESULT: Login Failed EXPECTED RESULT: Login Successful 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.
[abakus] [Bug 410250] Login Failure
https://bugs.kde.org/show_bug.cgi?id=410250 --- Comment #2 from Debika Roy --- Okay, once you finish your urgent tasks, you can fix this error -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410929] New: "Fit to Height" shortcut not possible (possible bug, possible wishlist feature?)
https://bugs.kde.org/show_bug.cgi?id=410929 Bug ID: 410929 Summary: "Fit to Height" shortcut not possible (possible bug, possible wishlist feature?) Product: krita Version: 4.2.5 Platform: unspecified OS: All Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: royblument...@gmail.com Target Milestone: --- Created attachment 122133 --> https://bugs.kde.org/attachment.cgi?id=122133&action=edit Illustration of wide canvas showing workflow of 'fit to height' request SUMMARY Currently, Krita has the ability to "fit to width" (hotkey: 3). But it seems there isn't a way to "fit to height" of canvas. STEPS TO REPRODUCE No steps to reproduce. Functionality isn't in place yet. (Hence the possibility that this is a wishlist issue rather than a dug report.) OBSERVED RESULT No way to fit the canvas to the screen using HEIGHT as the measure. EXPECTED RESULT While working on a wide canvas (eg, 1000 pixels high by 6000 wide), I would like to press a hotkey, and have the canvas resize so that the 1000 pixels fill my screen from top to bottom, using the cursor position as the centre of the zoom. This would be similar to the current functionality of pressing the '3' key, which, in the example dimension above, would resize the screen view such that the 6000 pixel dimension would fit the screen from left to right. (One notable difference here is that the "fit to width" function zooms to the centre of the canvas, not to the centre of the cursor.) SOFTWARE/OS VERSIONS Windows: 10 Linux: Zorin 15 (As far as I know, this is in all versions. I have the same issues on my Win 10 machine, and a Linux Zorin 15 machine.) ADDITIONAL INFORMATION This functionality is needed for keeping track of where I am on a canvas. In my work as a live digital sketchnoter, I draw live interpretations of what people say in meetings and conferences. This means I usually prepare a very wide canvas, with a prepared background image, and logo and various things. This would be on the left of my canvas. Since my window is just a normal sized window, I want the height of the canvas visible. I'm attaching a pic showing roughly what I mean. In the pic, I show a very wide canvas (1000 high by 6000 pixels wide), with the Krita UI superimposed over it, showing a view that is 1000 pixels high by 2000 pixels wide. It's showing what's going on on the left hand side of the wide canvas. Over the course of a talk, I would draw something, perhaps zooming in on a detail, (eg, the speech bubble that says, "Fit to height?"), and then zoom back to the height of the canvas again so that the audience could see the "full" view (ie, 1000 by 2000 pixels). Once I'm done with that first part of the canvas, I would use the space key to drag along to the middle part of the canvas, showing the blank central portion. I would then draw in that. Zooming in and out as needed for showing details. Right now, there is no way for my to instantly hit the height. I have to manually scroll zoom to the height using my mouse wheel. In the illustration, I've also shown the centre of canvas, and the centre of cursor. Currently, the '3' key fits to width, using the centre of the canvas as the mapping point for the height. What it SHOULD ideally do for this workflow is to use the centre of cursor for the mapping, so that the zoom keeps the image in place, and just fixes the width. The "fit to height" functionality should use centre of cursor, not centre of canvas. I hope this explanation makes sense. I've marked it as minor, cos I'm sure not all users have this need. For me, it's mission critical, but for typical users, it's trivial, and probably not even needed. It would be amazing if you could do something like this though! Thanks for reading my lengthy report! Blue skies Roy -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401479] Feature request: add animations that follow the fingers when performing touchpad gestures
https://bugs.kde.org/show_bug.cgi?id=401479 Sugata Roy changed: What|Removed |Added CC||sugat...@gmail.com --- Comment #12 from Sugata Roy --- Any updates on this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 317959] access/bounce keys does not give enough adjustment
https://bugs.kde.org/show_bug.cgi?id=317959 Roy Bellingan changed: What|Removed |Added CC||ad...@seisho.us -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398977] Crash in Workspace::workspaceEvent
https://bugs.kde.org/show_bug.cgi?id=398977 Roy Bellingan changed: What|Removed |Added CC||ad...@seisho.us -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #76 from Mathieu Roy --- (In reply to ariasuni from comment #75) > Besides, this doesn’t help to get this bug resolved and annoys people > reading the comments. Would you like to help people spitting on your work? Comment about any code of conduct is unlikely to resolve anything and is surely less informative to KDE developers than comments that actually provides workaround and mention that they are disappointed to actually have to resort to such workarounds. Because that should tell to whomever cares why some long-time users could stop using KDE and, worse, stop recommending KDE to other non-geek users. You cannot ask people to feel good because simple things like what is at hand here, reported in 2004 as a sadly "often neglected feature of KDE", is still not fixed in 2018, and works perfect on other desktop environments. Reality-check: if you recommend KDE to someone, average Joe, and it turns out he as to do so much just to play a video, he will describe this KDE you recommended in way harsher terms than these recents comments here. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Mathieu Roy changed: What|Removed |Added CC||yeu...@coleumes.org -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #85 from Mathieu Roy --- Nate, you are right: we should have made a bounty/kickstarted this earlier. Way earlier. Probably we did not because many would have though it would be done anyway. That was a mistake on our part, all of us following this reports since more than a decade. This KDE bug tracking system should have an integrated kickstarter-alike system! Instead of adding ourselves to CC, we would add ourselves to a pledge, I am sure at some point we could raise some reasonable amount of cash. I personally unfortunately lost interest in KDE because that, and many other little things (I wont say what it relates to, to avoid off-topic flamewar), forced me not only to no longer use it (granted: not so meaningful, I nowadays use mostly use awesomewm - so I could deal with it and work around it) but I also was forced to make non-geek people (parents, in-laws and such) I am administering the computer of use something else because things like this had to work. But if someone is kickstarting something about it, I would donate a few coins still :-) and I am sure I would not be alone. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Mathieu Roy changed: What|Removed |Added CC|yeu...@coleumes.org,| |yeu...@gnu.org | --- Comment #91 from Mathieu Roy --- I think we can all thanks David Edmunson to remind us how important it is for the end users not to disturb too much developers, since they are clearly so devoted to fix this issue in particular. So please, agree with David Edmunson to let the developers talk about how to fix this important issue, that they cared so much about between 2004 and 201.. 2019, even though this issue does not exists on any other desktop. We should not bother them with stupid ideas as to set a bounty for it or fund development. If we pay attention what a good guy like David says, they clearly do not care of it. And this guy must matter since his statement about how happily KDE trashed massive amount of (working features) code to replace them by some-init-that-replace-all was an omen. Thanks to keep all the good work. I hope the conduct of conduct allows me to tell that KDE 1 was an improvement over Windows 98/NT 4.0. while KDE current is much less usable than Windows 10 as desktop (but even 7/8...). But who cares about the feeling of KDE 1 users, eh!? Please accept our apologies, we should never have suggested to sponsor any development. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394418] New: Software Centre has been crashed
https://bugs.kde.org/show_bug.cgi?id=394418 Bug ID: 394418 Summary: Software Centre has been crashed Product: Discover Version: 5.12.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: rudranilr...@gmail.com Target Milestone: --- Application: plasma-discover (5.12.5) (Compiled from sources) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.16.3-301.fc28.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I was trying to install Libre Office. Each and every time I was trying to install Libre Office the system crashed. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2db2953e00 (LWP 10457))] Thread 12 (Thread 0x7f2d6cb2f700 (LWP 10481)): #0 0x7f2db5d77969 in g_source_iter_next () at /lib64/libglib-2.0.so.0 #1 0x7f2db5d7a432 in g_main_context_check () at /lib64/libglib-2.0.so.0 #2 0x7f2db5d7aab0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f2db5d7ac30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f2dbd1d4c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f2dbd18312b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f2dbcfd19c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f2dbcfd611d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f2dba681564 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2dbc31331f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f2d6d360700 (LWP 10480)): #0 0x7f2dbc304374 in read () at /lib64/libc.so.6 #1 0x7f2db5dbfdd0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f2db5d7a5fb in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f2db5d7aab0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f2db5d7ac30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f2dbd1d4c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f2dbd18312b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f2dbcfd19c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f2dbcfd611d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f2dba681564 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2dbc31331f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f2d6dcd0700 (LWP 10469)): #0 0x7f2dbc304374 in read () at /lib64/libc.so.6 #1 0x7f2db5dbfdd0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f2db5d7a5fb in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f2db5d7aab0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f2db5d7ac30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f2dbd1d4c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f2dbd18312b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f2dbcfd19c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f2dbcfd611d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f2dba681564 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2dbc31331f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f2d6f2f3700 (LWP 10467)): #0 0x7f2db5dc1218 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f2db5d7a9bd in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f2db5d7ac30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f2dbd1d4c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f2dbd18312b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f2dbcfd19c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f2dbcfd611d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f2dba681564 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2dbc31331f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f2d8152a700 (LWP 10465)): #0 0x7f2dbc320ee7 in clock_gettime () at /lib64/libc.so.6 #1 0x7f2dbd1d4455 in qt_gettime() () at /lib64/libQt5Core.so.5 #2 0x7f2dbd1d2f2d in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #3 0x7f2dbd1d3339 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #4 0x7f2dbd1d48fc in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #5 0x7f2dbd1d49a2 in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5
[kdeconnect] [Bug 495189] KDE Connect's custom keyboard overlaps the gesture bar in Android 15.
https://bugs.kde.org/show_bug.cgi?id=495189 Roy Orbitson changed: What|Removed |Added Platform|Other |Android CC||roy-orbit...@devo.net.au -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470429] Screen shows as "disconnected" after switching monitor. Missing desktop background and panel.
https://bugs.kde.org/show_bug.cgi?id=470429 --- Comment #4 from Roy Orbitson --- Not me, sorry. On 6.1.5. At the time, I was using a DisplayLink-based dock. I've since switched to a Thunderbolt one due to many issues with the former. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484363] Sometimes, on a multimonitor setup, screen locker fails to unlock screen and shows "Unlock" button that does nothing
https://bugs.kde.org/show_bug.cgi?id=484363 Roy Orbitson changed: What|Removed |Added CC||roy-orbit...@devo.net.au --- Comment #5 from Roy Orbitson --- Trying to find the right bug to add to, hope this is the one as there are several open that may be related. Kubuntu, Plasma version 6.1.5, problem exhibited on two very different computers, one a HTPC with password-less login. Both will wake and not unlock. Both will allow me to interact with the greeter with mouse and keyboard. I can type my password on my notebook, but hitting enter (or clicking the `>` or `Unlock` buttons) will not unlock either machine, no matter how many times I do it. No error/invalid password is reported in the UI. It behaves as if it's waiting for me to submit the login. In both cases, I work around this by switching to a TTY and killing the `kscreenlocker_greet` process, after which switching back to the graphical console shows a fresh greeter (new PID) that works normally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484363] Sometimes screen locker fails to unlock screen and shows "Unlock" button that does nothing
https://bugs.kde.org/show_bug.cgi?id=484363 --- Comment #21 from Roy Orbitson --- @Luca76 Are you sure you need to restart the entire sddm service? Did you try my above suggestion of just killing your user's kscreenlocker_greet? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484363] Sometimes screen locker fails to unlock screen and shows "Unlock" button that does nothing
https://bugs.kde.org/show_bug.cgi?id=484363 --- Comment #14 from Roy Orbitson --- @Tobias G. That is bug 497904, which may be an annoyance but doesn't break anything. This is about being unable to log in again from the GUI, at all. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 346143] Allow all similar number to be highlighted
https://bugs.kde.org/show_bug.cgi?id=346143 Roy Wright changed: What|Removed |Added CC||r...@wright.org -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 346143] Allow all similar number to be highlighted
https://bugs.kde.org/show_bug.cgi?id=346143 --- Comment #1 from Roy Wright --- Please check if this is what you had in mind: https://invent.kde.org/games/ksudoku/-/merge_requests/39 -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 499161] Wrong error highlight
https://bugs.kde.org/show_bug.cgi?id=499161 Roy Wright changed: What|Removed |Added CC||r...@wright.org --- Comment #1 from Roy Wright --- Indicating an error cell looks OK for the attached puzzle as a "1" could be valid in both open cells to the left of the error cell. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 495189] KDE Connect's custom keyboard overlaps the gesture bar in Android 15.
https://bugs.kde.org/show_bug.cgi?id=495189 --- Comment #2 from Roy Orbitson --- If it's at all possible when correcting the layout bug, could the UI be updated so it doesn't look like Android Froyo? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484363] Sometimes screen locker fails to unlock screen and shows "Unlock" button that does nothing
https://bugs.kde.org/show_bug.cgi?id=484363 --- Comment #36 from Roy Orbitson --- @TraceyC how should we test that? For me it's an intermittent issue, and even with backports enabled I'm at least a minor version behind those, and I can't afford to muck around with my daily driver to get cutting edge versions. Why was the only workaround that doesn't toast one's entire session, i.e. killing kscreenlocker_greet, hidden as spam? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470503] New: [nvidia] Screen corruption after changing theme
https://bugs.kde.org/show_bug.cgi?id=470503 Bug ID: 470503 Summary: [nvidia] Screen corruption after changing theme Classification: Plasma Product: kwin Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: j...@devklog.net Target Milestone: --- SUMMARY When changing the global theme via system settings, say from Breeze to Breeze Dark, the screen becomes corrupted, rendering incorrect textures or compositing textures in the wrong place. STEPS TO REPRODUCE 1. Start a plasma wayland session 2. Change the global theme. OBSERVED RESULT Corrupt desktop compositing. EXPECTED RESULT Correct desktop compositing. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 Manufacturer: ASUS ADDITIONAL INFORMATION Linux: 6.3.5-arch1-1 Nvidia drivers: 530.41.03-15 Taking a screenshot with Spectacle does not show corruption, it is only on-screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470503] [nvidia] Screen corruption after changing theme
https://bugs.kde.org/show_bug.cgi?id=470503 --- Comment #1 from Jean-Francois Roy --- It is less reproducible than I initially thought. There may need to be some memory pressure or some extended use of the session for the issue to repro. I'll keep trying to figure out a reliable method. Once the system is in a bad place, it repros reliably. I have a photo I can share of it, though I had to anonymize it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470503] [nvidia] Screen corruption after changing theme
https://bugs.kde.org/show_bug.cgi?id=470503 --- Comment #2 from Jean-Francois Roy --- Created attachment 159497 --> https://bugs.kde.org/attachment.cgi?id=159497&action=edit compositor recursion -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net --- Comment #15 from Jean-Francois Roy --- For what it's worth, I get this issue with the KDE Plasma 6.0 Beta 1 release (as installed by arch's kde-unstable repo) using Wayland. I'm trying to capture logs to file a report. It does not happen with the stable KDE Plasma release. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 --- Comment #17 from Jean-Francois Roy --- > (In reply to Jean-Francois Roy from comment #15) > > For what it's worth, I get this issue with the KDE Plasma 6.0 Beta 1 release > > (as installed by arch's kde-unstable repo) using Wayland. I'm trying to > > capture logs to file a report. It does not happen with the stable KDE Plasma > > release. > See bug 477738 for that. I'll follow up in that bug or in a new bug -- my system is a desktop that never suspends. What seems to trigger it for me is powering down the displays after idle. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478515] New: Disabling "Enable menu accelerators" does not work
https://bugs.kde.org/show_bug.cgi?id=478515 Bug ID: 478515 Summary: Disabling "Enable menu accelerators" does not work Classification: Applications Product: konsole Version: 24.01.80 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: j...@devklog.net Target Milestone: --- SUMMARY The "Enable menu accelerators" option in the General settings does not seem to work. It is disabled, and yet when I do Alt-F, the Konsole find panel activates instead of sending Alt-F to my shell. You can also observe that just pressing Alt causes the underline to show up under the accelerator key/letter in the toolbar. STEPS TO REPRODUCE 1. Disable (uncheck) "Enable menu accelerators" in General settings. 2. Press Alt-F in terminal (e.g. to advance the cursor in a shell). OBSERVED RESULT Konsole find panel appears. EXPECTED RESULT Alt-F sent to the shell. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 Manufacturer: ASUS ADDITIONAL INFORMATION Using Plasma 6 beta 1 via Arch Linux kde-unstable packages. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478531] New: Energy Saving and Screen Locking disagree on lock screen time
https://bugs.kde.org/show_bug.cgi?id=478531 Bug ID: 478531 Summary: Energy Saving and Screen Locking disagree on lock screen time Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: j...@devklog.net CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 164173 --> https://bugs.kde.org/attachment.cgi?id=164173&action=edit Screen Locking SUMMARY The Screen Locking settings module disagrees with the Energy Saving module for the system's idle time after which the screen will be locked. This is very confusing. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478531] Energy Saving and Screen Locking disagree on lock screen time
https://bugs.kde.org/show_bug.cgi?id=478531 --- Comment #1 from Jean-Francois Roy --- Created attachment 164174 --> https://bugs.kde.org/attachment.cgi?id=164174&action=edit Energy Saving -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478866] Every panel is enabled in every new window in Beta 2 - Places, Information, Folders, and Terminal
https://bugs.kde.org/show_bug.cgi?id=478866 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478804] Plugins are always shown on start and unable to keep them disabled/hidden
https://bugs.kde.org/show_bug.cgi?id=478804 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 --- Comment #26 from Jean-Francois Roy --- We ideally need a solution in KWin because other applications based on Chromium are also affected and those tend to be on much slower upgrade cycles. Anything Electron (Discord, Slack, VS Code) are affected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 --- Comment #32 from Jean-Francois Roy --- (In reply to Ted Parvu from comment #31) > Found a work-a-round that is working for me. > > https://bbs.archlinux.org/viewtopic.php?pid=2166339#p2166339 Completely disabling drag and drop is a pretty hard workaround to swallow and breaks a number of web apps that rely on it. I too am frustrated when I accidentally soft-lock Chrome, but this workaround should not lessen efforts to fix kwin. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 441009] New: unable to rip and save the dvd i bought to my own media files for backup
https://bugs.kde.org/show_bug.cgi?id=441009 Bug ID: 441009 Summary: unable to rip and save the dvd i bought to my own media files for backup Product: k3b Version: 21.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: weverett...@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 140751 --> https://bugs.kde.org/attachment.cgi?id=140751&action=edit saved error text file Devices --- PLDS DVD+-RW DU-8A5LH 6D11 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 21.4.3 KDE Version: 5.83.0 Qt Version: 5.15.2 Kernel: 5.14.0-1-MANJARO Used versions --- transcode: 1.1.7 transcode --- transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team [[34;1mdvd_reader.c[0m] DVD title 1/6: 23 chapter(s), 1 angle(s), title set 1 [[34;1mdvd_reader.c[0m] title playback time: 02:12:53.10 7974 sec [[34;1mdvd_reader.c[0m] DVD title 1/6: 23 chapter(s), 1 angle(s), title set 1 [[34;1mdvd_reader.c[0m] title playback time: 02:12:53.10 7974 sec [transcode] V: auto-probing | /dev/sr0 (OK) [transcode] V: import format| MPEG 2 program stream in DVD NTSC (module=dvd) [transcode] A: auto-probing | /dev/sr0 (OK) [transcode] A: import format| AC3 in DVD NTSC (module=dvd) [transcode] V: AV demux/sync| (2) initial MPEG sequence / enforce frame rate [transcode] V: import frame | 720x480 1.50:1 encoded @ 16:9 [transcode] V: clip frame (<-) | 720x480 [transcode] V: zoom | 848x480 1.77:1 (Lanczos3) [transcode] V: bits/pixel | 0.123 (low) [transcode] V: decoding fps,frc | 23.976,1 [transcode] V: multi-pass | (mode=1) writing data (pass 1) to /home/royew/Videos/k3b_0.log [transcode] V: video format | YUV420 (4:2:0) aka I420 [transcode] A: import format| 0x2000 AC3 [48000,16,2] [transcode] A: export | disabled [transcode] V: encoding fps,frc | 23.976,1 [transcode] A: language | en [transcode] A: bytes per frame | 8008 (8008.00) [transcode] A: adjustment | 0@1000 [transcode] V: IA32/AMD64 accel | sse4a sse42 sse41 ssse3 sse3 sse2 sse mmxext mmx cmove asm [transcode] V: video buffer | 10 @ 848x480 [0x2] [transcode] A: audio buffer | 10 @ 48000x2x16 [import_dvd.so] v0.4.1 (2007-07-15) (video) DVD | (audio) MPEG/AC3/PCM [export_null.so] v0.1.2 (2001-08-17) (video) null | (audio) null [export_ffmpeg.so] v0.3.18 (2008-11-29) (video) Lavc58.134.100 | (audio) MPEG/AC3/PCM [import_dvd.so] tccat -T 1,-1,1 -i "/dev/sr0" -t dvd -d 0 | tcdemux -a 0 -x ac3 -S 0 -M 2 -d 0 | tcextract -t vob -x ac3 -a 0 -d 0 | tcdecode -x ac3 -d 0 -s 1.00,1.00,1.00 -A 0 [import_dvd.so] tccat -T 1,-1,1 -i "/dev/sr0" -t dvd -d 0 | tcdemux -s 0x80 -x mpeg2 -S 0 -M 2 -f 23.976024 -P /tmp/fileqNHHTO -d 0 | tcextract -t vob -a 0 -x mpeg2 -d 0 | tcdecode -x mpeg2 -d 0 -y yuv420p [import_dvd.so] delaying DVD access by 3 seconds [import_dvd.so] waiting... [[31;1mdemuxer.c[0m][33;1m warning[0m: (pid=1677) '0x6c696264' not yet supported [import_dvd.so] waiting... === last message repeated 2 times. === [[34;1mdecode_mpeg2.c[0m] libmpeg2 acceleration: mmxext [export_ffmpeg.so] Using FFMPEG codec 'mpeg4' (FourCC 'DIVX', MPEG4 compliant video). [export_ffmpeg.so] No profile selected [export_ffmpeg.so] Error opening configuration file ./ffmpeg.cfg: No such file or directory [export_ffmpeg.so] Starting 1 thread(s) [export_ffmpeg.so] Set display aspect ratio to input [MPEG4 encoder @ 0x5611ed7f7b00] The "rc_strategy" option is deprecated: ratecontrol method [MPEG4 encoder @ 0x5611ed7f7b00] Value 2.00 for parameter 'rc_strategy' out of range [0 - 1] [MPEG4 encoder @ 0x5611ed7f7b00] Error setting option rc_strategy to value 2. [export_ffmpeg.so] could not open FFMPEG codec [encoder.c] video export module error: init failed [transcode] failed to init encoder transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team [[34;1mdvd_reader.c[0m] DVD title 2/6: 1 chapter(s), 1 angle(s), title set 1 [[34;1mdvd_reader.c[0m] title playback time: 00:00:00.15 1 sec [[34;1mdvd_reader.c[0m] DVD title 2/6: 1 chapter(s), 1 angle(s), title set 1 [[34;1mdvd_reader.c[0m] title playback time: 00:00:00.15 1 sec [transcode] V: auto-probing | /dev/sr0 (OK) [transcode] V: import format| MPEG 2 program stream in DVD NTSC (module=d
[k3b] [Bug 441009] unable to rip and save the dvd i bought to my own media files for backup
https://bugs.kde.org/show_bug.cgi?id=441009 --- Comment #1 from Roy Everett walker --- if theres a way to resolve this im new to running linux manjaro and would probaly need stepped through it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479359] New: sddm-helper-start-wayland fails/exits after manually turn on monitors
https://bugs.kde.org/show_bug.cgi?id=479359 Bug ID: 479359 Summary: sddm-helper-start-wayland fails/exits after manually turn on monitors Classification: Plasma Product: kwin Version: 5.91.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: j...@devklog.net Target Milestone: --- # Summary I turned off my 2 monitors overnight with the computer at SDDM waiting for login and turned them back on in the morning. This led to `sddm-helper-start-wayland` to fail and SDDM to exit, leaving me with a broken/empty TTY. Logs: ``` Jan 03 06:53:58 wave5 sddm-helper-start-wayland[44348]: "kwin_core: Parse error in tiles configuration for monitor \"92e842d7-5928-5c43-884a-4912e7cc82ed\" : \"illegal value\" Creating default setup\n" Jan 03 06:53:58 wave5 sddm-greeter[44353]: Creating a fake screen in order for Qt not to crash Jan 03 06:53:58 wave5 sddm-greeter[44353]: Loading file:///usr/share/sddm/themes/breeze/Main.qml... Jan 03 06:53:58 wave5 sddm-greeter[44353]: Failed to find a Kirigami platform plugin Jan 03 06:53:58 wave5 sddm-greeter[44353]: Adding view for "" QRect(0,0 0x0) Jan 03 06:53:59 wave5 sddm-helper-start-wayland[44348]: "kwin_core: Could not find any suitable output for a layer surface\n" Jan 03 06:53:59 wave5 sddm-helper-start-wayland[44348]: wayland greeter finished 0 QProcess::NormalExit Jan 03 06:53:59 wave5 sddm-helper-start-wayland[44348]: quitting helper-start-wayland Jan 03 06:53:59 wave5 sddm-helper-start-wayland[44348]: Stopping... "kwin_wayland" Jan 03 06:53:59 wave5 sddm-helper-start-wayland[44348]: "QtDBus: cannot relay signals from parent QObject(0x55ad50323b20 \"\") unless they are emitted in the object's thread QThread(0x55ad50183238 \"libinput-connection\"). Current thread is QThread(0x55ad501328f0 \"\").\n" Jan 03 06:53:59 wave5 xdg-desktop-por[44492]: Error reading events from display: Broken pipe Jan 03 06:53:59 wave5 systemd[44295]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Jan 03 06:53:59 wave5 systemd[44295]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. Jan 03 06:53:59 wave5 sddm-helper-start-wayland[44348]: wayland compositor finished 15 QProcess::NormalExit Jan 03 06:53:59 wave5 sddm-helper-start-wayland[44348]: quitting helper-start-wayland Jan 03 06:53:59 wave5 sddm-helper[44279]: [PAM] Closing session Jan 03 06:53:59 wave5 sddm-helper[44279]: pam_unix(sddm-greeter:session): session closed for user sddm Jan 03 06:53:59 wave5 sddm-helper[44279]: [PAM] Ended. Jan 03 06:53:59 wave5 sddm[1193]: Auth: sddm-helper exited successfully Jan 03 06:53:59 wave5 systemd-logind[1050]: Session c6 logged out. Waiting for processes to exit. Jan 03 06:53:59 wave5 sddm[1193]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS Jan 03 06:53:59 wave5 systemd[1]: session-c6.scope: Deactivated successfully. ``` I had to open a console session in another TTY and restart `sddm.service`. # Configuration /etc/sddm.conf.d/10-wayland.conf ``` [General] DisplayServer=wayland GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell [Wayland] CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1 ``` /etc/sddm.conf.d/kde_settings.conf ``` [Autologin] Relogin=false Session= User= [General] HaltCommand=/usr/bin/systemctl poweroff RebootCommand=/usr/bin/systemctl reboot [Theme] Current=breeze CursorSize= CursorTheme=breeze_cursors Font=Noto Sans,10,-1,0,400,0,0,0,0,0,0,0,0,0,0,1 [Users] MaximumUid=60513 MinimumUid=1000 ``` # System info Arch Linux Linux: 6.6.9-arch1-1 Nvidia: 545.29.06 (open dkms) sddm: 0.20.0-3 Running KDE Plasma 6.0 Beta 2 from Arch kde-unstable. See also https://github.com/sddm/sddm/issues/1847 -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 479083] Fedora Kinoite - Plasma 6 beta 2 - Window thumbnails are upside down
https://bugs.kde.org/show_bug.cgi?id=479083 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 --- Comment #25 from Jean-Francois Roy --- I think I am seeing this regularly but on Wayland. If I kill kscreenlocker_greet from an ssh or tty session, I can see and use my graphical session again, without needing to unlock the session first with loginctl. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 --- Comment #27 from Jean-Francois Roy --- (In reply to Jean-Francois Roy from comment #25) > I think I am seeing this regularly but on Wayland. If I kill > kscreenlocker_greet from an ssh or tty session, I can see and use my > graphical session again, without needing to unlock the session first with > loginctl. I forgot to add that I see nothing interesting in the journal, but I don't have any extra debug logging env or flags set. -- You are receiving this mail because: You are watching all bug changes.
