[ksystemstats] [Bug 486946] Wrong amount of total disk space
https://bugs.kde.org/show_bug.cgi?id=486946 --- Comment #1 from Manuel Alcaraz --- Bug https://bugs.kde.org/show_bug.cgi?id=477983 seems to be related but I'm not sure if it's the same issue as it says that it got fixed in 6.1 (not sure if that is Frameworks version or Plasma version) -- You are receiving this mail because: You are watching all bug changes.
[ksystemstats] [Bug 486946] New: Wrong amount of total disk space
https://bugs.kde.org/show_bug.cgi?id=486946 Bug ID: 486946 Summary: Wrong amount of total disk space Classification: Frameworks and Libraries Product: ksystemstats Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: manuelalcaraz...@gmail.com CC: ahiems...@heimr.nl Target Milestone: --- SUMMARY System Monitor reports a wrong amount of total available disk space. It says that I have 2,0 TiB of total space when I only have two drives of 1 TB + 256 GB. STEPS TO REPRODUCE 1. Open System Monitor. 2. See the Disk card with the total available space. OBSERVED RESULT It shows that I have 2 TiB of total space. EXPECTED RESULT It shows that I have around 1,2-1,3 TiB of total space. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-arch1-2 (64-bit) ADDITIONAL INFORMATION df -h (loop devices removed for clarity) S.ficherosTamaño Usados Disp Uso% Montado en /dev/mapper/vg--root-lv--root 684G86G 598G 13% / devtmpfs4,0M 0 4,0M 0% /dev tmpfs16G41M 16G 1% /dev/shm efivarfs128K51K 73K 42% /sys/firmware/efi/efivars tmpfs 6,2G 9,8M 6,2G 1% /run tmpfs16G13M 16G 1% /tmp /dev/nvme0n1p2 1022M 183M 840M 18% /boot /dev/mapper/home230G 109G 120G 48% /home tmpfs 3,1G68K 3,1G 1% /run/user/1000 lsblk (loop devices removed for clarity) NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme0n1 259:00 931,5G 0 disk ├─nvme0n1p1 259:10 230G 0 part │ └─md127 9:127 0 229,9G 0 raid1 │ └─home 254:30 229,9G 0 crypt /home ├─nvme0n1p2 259:20 1G 0 part /boot └─nvme0n1p3 259:30 700G 0 part └─root254:00 700G 0 crypt ├─vg--root-lv--swap 254:1016G 0 lvm [SWAP] └─vg--root-lv--root 254:20 684G 0 lvm / nvme1n1 259:40 232,9G 0 disk └─nvme1n1p1 259:50 230G 0 part └─md127 9:127 0 229,9G 0 raid1 └─home 254:30 229,9G 0 crypt /home -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458055] Symbolic 22px System Settings KCM icons
https://bugs.kde.org/show_bug.cgi?id=458055 --- Comment #7 from Manuel de la Fuente --- (In reply to Nate Graham from comment #6) > Agreed. Let's do it. IIRC You had monochrome icons prepared here, Manuel, > right? Those were for the categories icons, not preferences, though I may have a few done already from playing around with both options. I'm indifferent on using monochrome or color icons, but we should probably just add it to the 2px icon update from Andy directly since I expect it to be done in a couple of months tops, and that way we avoid duplicating work. That'd also make it possible to coordinate the change with the categories icons so that Discover's categories on the sidebar are monochrome on the same release. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 363147] Breeze cursors should have more sizes, and support arbitrary sizes if possible
https://bugs.kde.org/show_bug.cgi?id=363147 Manuel de la Fuente changed: What|Removed |Added CC||m...@nueljl.in Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 322922] Dolphin should not store .directory files inside the actual directory to avoid cluttering and polluting the filesystem; should instead store this data in extended attributes
https://bugs.kde.org/show_bug.cgi?id=322922 Manuel C changed: What|Removed |Added CC||manuel.manu.del...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Manuel changed: What|Removed |Added CC||miaumen...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458214] Icon request: KSokoban game app icon
https://bugs.kde.org/show_bug.cgi?id=458214 Manuel de la Fuente changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/-/commi ||t/ffb120b9d0017dffce621f7f6 ||6c12733c3b99dbf --- Comment #6 from Manuel de la Fuente --- Git commit ffb120b9d0017dffce621f7f66c12733c3b99dbf by Manuel Jesús de la Fuente. Committed on 05/03/2024 at 16:45. Pushed by mdelafuente into branch 'master'. Add new icon for Skladnik A +29 -0icons/apps/48/skladnik.svg https://invent.kde.org/frameworks/breeze-icons/-/commit/ffb120b9d0017dffce621f7f66c12733c3b99dbf -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466017] Tiling Shortcut (Shift) not working with Keyboard-Layout German (Neo, QWERTZ)
https://bugs.kde.org/show_bug.cgi?id=466017 manuel changed: What|Removed |Added CC||maenje...@gmail.com --- Comment #6 from manuel --- Was surprised that tiling stopped working when changing from X11 to Wayland session. Also using Neo2 Layout. At first, thought it might be due to manual fiddling with virtual desktop config. But reverting my changes did not do anything. Then tried having Neo2 and German standard layout both available, but switching between them did not fix the issue neither. Moreover, back in X11, tiling also did not work anymore (!) until I removed layout selection and changed back to Neo2 only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461198] Wayland: Night Colour filter is restored incorrectly to reconnected display
https://bugs.kde.org/show_bug.cgi?id=461198 Manuel C changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Manuel C --- Sorry this took me a bit to come back to, with some testing it seems like this is no longer an issue on my end with Plasma 5.27.9. I did encounter another oddity where several times I couldn't re-enable night light until restarting the desktop, after some amount of toggling it in the task bar. But I'll see if I can figure out a way to reproduce this reliably, and file another issue then :> -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474234] New: Cannot edit seat / coach / class
https://bugs.kde.org/show_bug.cgi?id=474234 Bug ID: 474234 Summary: Cannot edit seat / coach / class Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: rud...@rudd-o.com Target Milestone: --- Attempting to edit a train trip's coach / seat / class fields does nothing — the blue Save button (with the floppy) at the bottom of the screen blinks when tapped, but nothing happens, and going back to the previous screen shows nothing has been saved. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474232] New: Freezes when adding PDF document to train trip
https://bugs.kde.org/show_bug.cgi?id=474232 Bug ID: 474232 Summary: Freezes when adding PDF document to train trip Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: rud...@rudd-o.com Target Milestone: --- I confirm that the application shows an ANR dialog (and a black screen) after adding a document to a train trip, however when reopening the application the document has successfully been added. Here is the traceback --- ``` type: ANR osVersion: google/raven/raven:13/TQ3A.230805.001/2023090200:user/release-keys package: org.kde.itinerary:1693993006 process: org.kde.itinerary installer: com.android.packageinstaller activity: org.kde.itinerary/.Activity cause: ANR Input dispatching timed out (b34779b org.kde.itinerary/org.kde.itinerary.Activity (server) is not responding. Waited 5005ms for FocusEvent(hasFocus=true)) info: ANR in org.kde.itinerary (org.kde.itinerary/.Activity) PID: 18602 Reason: Input dispatching timed out (b34779b org.kde.itinerary/org.kde.itinerary.Activity (server) is not responding. Waited 5005ms for FocusEvent(hasFocus=true)) Parent: org.kde.itinerary/.Activity ErrorId: 874caf0b-499f-4188-93c8-08d9e6dbd6d3 Frozen: false Load: 0.91 / 1.59 / 1.75 - Output from /proc/pressure/memory - some avg10=0.00 avg60=0.00 avg300=0.03 total=38698200 full avg10=0.00 avg60=0.00 avg300=0.01 total=14790960 - End output from /proc/pressure/memory - CPU usage from 0ms to 7999ms later (2023-09-06 19:03:07.793 to 2023-09-06 19:03:15.792): 28% 1426/system_server: 16% user + 12% kernel / faults: 48599 minor 4 major 17% 2081/com.android.systemui: 11% user + 6% kernel / faults: 39163 minor 10% 23464/com.android.inputmethod.latin: 7.5% user + 3.3% kernel / faults: 9244 minor 2 major 9.5% 18602/org.kde.itinerary: 5.2% user + 4.2% kernel / faults: 51470 minor 3.1% 2502/com.android.phone: 2.2% user + 0.8% kernel / faults: 1502 minor 16 major 3.1% 5491/sk.henrichg.phoneprofilesplus: 2% user + 1.1% kernel / faults: 985 minor 23 major 2.8% 588/surfaceflinger: 1.1% user + 1.7% kernel / faults: 294 minor 0.1% 1150/media.swcodec: 0% user + 0% kernel / faults: 8609 minor 0% 1082/media.extractor: 0% user + 0% kernel / faults: 4750 minor 1.7% 2460/com.shannon.imsservice: 1.3% user + 0.3% kernel / faults: 1020 minor 64 major 1.6% 3041/com.android.nfc: 0.8% user + 0.7% kernel / faults: 1937 minor 95 major 1.3% 3240/org.thoughtcrime.securesms: 1.1% user + 0.2% kernel / faults: 102 minor 1 major 1.1% 2322/com.android.networkstack.process: 0.6% user + 0.5% kernel / faults: 654 minor 31 major 0% 1106/media.codec: 0% user + 0% kernel / faults: 1578 minor 1% 2305/com.shannon.qualifiednetworksservice: 0.7% user + 0.2% kernel / faults: 667 minor 40 major 0% 2340/com.samsung.slsi.telephony.oem.oemrilhookservice: 0% user + 0% kernel / faults: 693 minor 57 major 0% 2409/com.android.se: 0% user + 0% kernel / faults: 753 minor 20 major 0.8% 2438/com.shannon.rcsservice: 0.6% user + 0.2% kernel / faults: 695 minor 35 major 0.7% 592/android.hardware.graphics.composer@2.4-service: 0.5% user + 0.2% kernel 0% 2362/com.google.pixel.digitalkey.timesync: 0% user + 0% kernel / faults: 703 minor 64 major 0.7% 9707/com.android.bluetooth: 0% user + 0.7% kernel / faults: 171 minor 0.6% 12/rcu_preempt: 0% user + 0.6% kernel 0.6% 1096/media.metrics: 0% user + 0.6% kernel / faults: 61 minor 0.6% 13744/.ShannonImsService: 0.2% user + 0.3% kernel / faults: 77 minor 47 major 0.5% 529/logd: 0.5% user + 0% kernel / faults: 48 minor 0.5% 545/sugov:0: 0% user + 0.5% kernel 0.5% 851/statsd: 0.1% user + 0.3% kernel / faults: 407 minor 0.5% 852/netd: 0% user + 0.5% kernel / faults: 131 minor 0.5% 954/audioserver: 0% user + 0.5% kernel / faults: 89 minor 0.5% 27498/app.vanadium.browser: 0.3% user + 0.1% kernel / faults: 65 minor 3 major 0.3% 13/rcuog/0: 0% user + 0.3% kernel 0.3% 49/rcuog/4: 0% user + 0.3% kernel 0.3% 132/sched_pmu_wq: 0% user + 0.3% kernel 0.3% 546/sugov:4: 0% user + 0.3% kernel 0.3% 738/android.hardware.power-service.pixel-libperfmgr: 0.2% user + 0.1% kernel 0% 745/tombstoned: 0% user + 0% kernel / faults: 35 minor 0.3% 979/dhd_rpm_state_t: 0% user + 0.3% kernel 0% 2478/com.samsung.slsi.telephony.oemril: 0% user + 0% kernel / faults: 666 minor 35 major 0.3% 15473/kworker/u16:1: 0% user + 0.3% kernel 0.2% 50/rcuop/4: 0% user + 0.2% kernel 0.2% 250/decon0_kthread: 0% user + 0.2% kernel 0.2% 915/android.hardware.sensors@2.1-service.multihal: 0.1% user + 0.1% kernel 0.2% 1069/cameraserver: 0% user + 0.2% kernel / faults: 98 minor 0% 1098/mediaserver: 0% user + 0% kernel / faults: 101 minor 0.2% 3024/com.qorvo.uwb.vendorservice: 0.2%
[kshisen] [Bug 473985] New: Leaderboard takes only seconds into account to rank times.
https://bugs.kde.org/show_bug.cgi?id=473985 Bug ID: 473985 Summary: Leaderboard takes only seconds into account to rank times. Classification: Applications Product: kshisen Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: schwar...@kde.org Reporter: manuel.vi...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 161306 --> https://bugs.kde.org/attachment.cgi?id=161306=edit Screenshot I have the Kshisen version 1.11.23080 that ships currently with Manjaro and I noticed the leaderboard has become a bit crazy. I now ranks plays based only on the number of elapsed seconds STEPS TO REPRODUCE 1. Play a game 2. Win 3. Watch the leaderboard OBSERVED RESULT Times are ranked according to seconds EXPECTED RESULT Times should be ranked by total duration of the game SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 472429] Icon request: New icon for wireless connection via Bluetooth
https://bugs.kde.org/show_bug.cgi?id=472429 Manuel de la Fuente changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/-/commi ||t/79b5b1404e225083febc7cd69 ||97855d29317576d --- Comment #2 from Manuel de la Fuente --- Git commit 79b5b1404e225083febc7cd6997855d29317576d by Manuel Jesús de la Fuente. Committed on 04/08/2023 at 11:48. Pushed by mdelafuente into branch 'master'. Add network-wireless-bluetooth @16px, @22px A +18 -0icons/devices/16/network-wireless-bluetooth.svg https://invent.kde.org/frameworks/breeze-icons/-/commit/79b5b1404e225083febc7cd6997855d29317576d -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409417] When using Bluetooth for internet connection, the same icon is used for the network and the bluetooth manager
https://bugs.kde.org/show_bug.cgi?id=409417 Bug 409417 depends on bug 472429, which changed state. Bug 472429 Summary: Icon request: New icon for wireless connection via Bluetooth https://bugs.kde.org/show_bug.cgi?id=472429 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 472429] Icon request: New icon for wireless connection via Bluetooth
https://bugs.kde.org/show_bug.cgi?id=472429 Manuel de la Fuente changed: What|Removed |Added Assignee|visual-des...@kde.org |m...@nueljl.in -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458214] Icon request: KSokoban game app icon
https://bugs.kde.org/show_bug.cgi?id=458214 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128
--- Comment #10 from Manuel de la Fuente ---
> They are missing.
Yeah, I linked to the (then unmerged) merge request. Now that it's merged, it's
there. I probably should've sent the other comment after merging.
Also, as far as I'm aware, the symbolic folder just acts as a folder of icon
symlinks from non standard GNOME icons to the freedesktop ones, so adding the
16px icon there makes no sense unless it's a GTK based podcast app that's
missing the icon, which if it is, would have a different name.
> I've also noted that the 16 non-symbolic has an RSS icon instead of podcast
All the `folder-podcast` icons use the RSS icon
> plus the icon has an artifact, top-left of that circle is distorted.
The 16px non-symbolic variant looks pretty normal here. Adding it to the
Dolphin `places` pane on the sidebar renders it fine
> The folder is also colored, for some reason
> It's the wrong icon for a podcast folder and it shouldn't be colored (blue
> default).
I think that's a different issue. Here's my thoughts on this:
Some of the newer `folder-${TYPE}` icons have color, which for the non
`folder-${COLOR}` icons is, in my honest opinion, not a good idea, since it's
inconsistent with the rest for no real reason. Why would an user want the RPM
folder to be red, but the Snap and Flatpak folder to be blue?
I also agree that the RSS icon isn't the right metaphor, as that is just one of
the channels where the user might've gotten the podcasts from, and doesn't
represent the concept of an actual podcast.
But still, this issue is about the missing size variants, so I stuck to adding
the missing variants for now.
I can do a MR to turn those folders monochrome/blue like the rest, and another
for changing the RSS logo to something like a microphone or another more
fitting icon, but after I'm done with the other ~35 icons for the 48px size.
It's more important to have no missing icons first.
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 --- Comment #6 from Manuel de la Fuente --- Update: added all the missing icons @ 96px in https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/273. By the way, it seems like none of the symbolic/16px are missing, including `folder-podcast`. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 471128] 48, 96, and "symbolic" directories are missing a lot of places icons
https://bugs.kde.org/show_bug.cgi?id=471128 Manuel de la Fuente changed: What|Removed |Added Assignee|visual-des...@kde.org |m...@nueljl.in -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466812] New: Scroling direction is inconsistent between horizontal and vertical scrolling when using the scroll wheels the mouse
https://bugs.kde.org/show_bug.cgi?id=466812 Bug ID: 466812 Summary: Scroling direction is inconsistent between horizontal and vertical scrolling when using the scroll wheels the mouse Classification: Plasma Product: kwin Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: deve...@manuel-voegele.de Target Milestone: --- SUMMARY When using a mouse that has a dedicated horizontal scroll wheel like the Lotitech MX Master series has, the scrolling direction of the horizontal and vertical scrolling is inconsistent. When "inverted scrolling" is disabled: Scrolling vertically moves the scrollbar in the same direction as the finger on the mouse wheel Scrolling horizontally moves the scrollbar in the *inverted* direction of the finger movement Activating "inverted scrolling" switches both options around: Scrolling vertically moves the scrollbar in the *inverted* direction of the finger movement Scrolling horizontally moves the scrollbar in the same direction as the finger on the mouse wheel EXPECTED RESULT When "inverted scrolling" is disabled, both scrolling directions should be moving the scroll bar in the direction of the finger and when "inverted scrolling" is enabled, both scroll directions should be moving the scroll bar in the direction opposed to the finger movement. I think ideally, there should be dedicated settings for "inverted vertical scrolling" and "inverted horizontal scrolling" so users can mix and match to get their ideal scrolling style. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: LENOVO Product Name: 20NFCTO1WW System Version: ThinkPad E595 ADDITIONAL INFORMATION I'm using the Logitech MX Master 3s -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 465228] Cursor center_ptr has incorrect hotspot location
https://bugs.kde.org/show_bug.cgi?id=465228 Manuel de la Fuente changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|visual-des...@kde.org |m...@nueljl.in --- Comment #4 from Manuel de la Fuente --- Created attachment 156150 --> https://bugs.kde.org/attachment.cgi?id=156150=edit new cursor theme file Hello again :D could you test this to check if it's still reproducible? Just download the .tar.gz and add it via cursor settings > install from file. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 465228] Cursor center_ptr has incorrect hotspot location
https://bugs.kde.org/show_bug.cgi?id=465228 --- Comment #2 from Manuel de la Fuente --- Yeah, that MR fixes it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 465228] Cursor center_ptr has incorrect hotspot location
https://bugs.kde.org/show_bug.cgi?id=465228 --- Comment #1 from Manuel de la Fuente --- I believe it should be fixed with https://invent.kde.org/plasma/breeze/-/merge_requests/287. Will double check later. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443024] Icons for cartridge-based video game ROM images
https://bugs.kde.org/show_bug.cgi?id=443024 Manuel de la Fuente changed: What|Removed |Added CC||m...@nueljl.in --- Comment #2 from Manuel de la Fuente --- As cool as it would be to have these, there's probably no way it's going to work for the 16 (more like 12x12) and 22 (more like 16x16) sizes unless we use a generic rom icon at smaller sizes. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 367696] breeze dark: konsole icon is barely visible
https://bugs.kde.org/show_bug.cgi?id=367696 Manuel de la Fuente changed: What|Removed |Added CC||m...@nueljl.in --- Comment #6 from Manuel de la Fuente --- The Konsole icon has, since that screenshot was taken, the usual 1px highlight and shadow, and combined with the gradient change from top-down to top-left, it has overall much better contrast. Should we close this as fixed? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432549] Screenshot icon for org.xfce.screenshooter?
https://bugs.kde.org/show_bug.cgi?id=432549 Manuel de la Fuente changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||4f818edd2ef721c74aabbdf98b8 ||b477be7686f80 Resolution|--- |FIXED --- Comment #2 from Manuel de la Fuente --- Git commit 4f818edd2ef721c74aabbdf98b8b477be7686f80 by Manuel Jesús de la Fuente. Committed on 17/01/2023 at 11:28. Pushed by mdelafuente into branch 'master'. Add XFCE4 Screenshooter symlink A +1-0icons/apps/48/org.xfce.screenshooter.svg https://invent.kde.org/frameworks/breeze-icons/commit/4f818edd2ef721c74aabbdf98b8b477be7686f80 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 429767] Add icon for "gvdesign" files
https://bugs.kde.org/show_bug.cgi?id=429767 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |UPSTREAM CC||m...@nueljl.in Status|CONFIRMED |RESOLVED --- Comment #2 from Manuel de la Fuente --- Similar to what used to happen with Godot's MIME icons, it's not part of shared-mime-info (https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/tests/mime-detection/list), so it can't be added. Also, it seems like the tool itself was bought and killed off by Corel. Marking as resolved upstream because Corel fixed it by themselves. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438886] Godot MIME icon doesn't appear to be working
https://bugs.kde.org/show_bug.cgi?id=438886 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Manuel de la Fuente --- Tested again and it works with all of the MIMEs added on the original MR. Closing... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462202] Massive VRAM leak when using tab switcher visualization with kwin_x11
https://bugs.kde.org/show_bug.cgi?id=462202 --- Comment #5 from Manuel Bärenz --- Then probably mesa 22.2 -> 22.3 resolved the issue just as in https://bugs.kde.org/show_bug.cgi?id=457847? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 265566] dolphin unsharing folders does not take effect immediately
https://bugs.kde.org/show_bug.cgi?id=265566 Manuel López-Ibáñez changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462202] Massive VRAM leak when using tab switcher visualization with kwin_x11
https://bugs.kde.org/show_bug.cgi?id=462202 --- Comment #3 from Manuel Bärenz --- (In reply to Wladimir Palant from comment #2) > It seems that this is no longer happening. Not sure which update fixed it, > but the issue is gone. Which version of KDE and Mesa are you using? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462202] Massive VRAM leak when using tab switcher visualization with kwin_x11
https://bugs.kde.org/show_bug.cgi?id=462202 Manuel Bärenz changed: What|Removed |Added CC||man...@enigmage.de --- Comment #1 from Manuel Bärenz --- I believe I'm encountering the same issue. OpenGL renderer string: RENOIR (renoir, LLVM 14.0.6, DRM 3.42, 5.15.76) Driver: RadeonSI GPU class: Vega OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 22.2.2 X server version: 1.20.14 Linux kernel version: 5.15.76 KDE-Plasma-Version: 5.26.2 KDE-Frameworks-Version:5.99.0 Qt-Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 313791] "Remove duplicates" function does not work completely
https://bugs.kde.org/show_bug.cgi?id=313791 --- Comment #20 from Manuel Ullmann --- Created attachment 154684 --> https://bugs.kde.org/attachment.cgi?id=154684=edit Icecast config for local server configuration Check the config before using it. It is not secure, but at least running on localhost. Last note: Amarok is not in the Gentoo repositories anymore, because the Qt5 migration took too long and there has been no stable release, since then. Apart from Krusader I’m not using any KDE software nowadays, so please excuse me, if I don’t open a new bug on the crash issue. As a developer I just was polite enough to report back on an old bug report. Happy debugging! :) -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 313791] "Remove duplicates" function does not work completely
https://bugs.kde.org/show_bug.cgi?id=313791 Manuel Ullmann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #19 from Manuel Ullmann --- Yes, it is still reproducible in today’s Amarok git. The issue seems to be limited to files ripped from streamripper though. So I set up a local icecast server, passed the Amarok jingle into it with ffmpeg and ripped it with streamripper. This file reproduces the issue. Please also note, that that output of streamripper always differs for the same tracks, so the database duplication detection fails. Searching for those duplicated tracks, which also have different formats in my collection via library search crashes Amarok. So it might be useful to play around with its outputs until it works. Here is the command used to stream and rip it: (ffmpeg -re -i first_run_jingle.ogg -c:a copy -content_type audio/ogg -f ogg icecast://source:hackme@localhost:8000/default &); sleep 0.1; streamripper http://localhost:8000/default -a -c I’ll attach the icecast.xml next. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 313791] "Remove duplicates" function does not work completely
https://bugs.kde.org/show_bug.cgi?id=313791 --- Comment #18 from Manuel Ullmann --- Created attachment 154683 --> https://bugs.kde.org/attachment.cgi?id=154683=edit Amarok jingle ripped from streamripper -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438886] Godot MIME icon doesn't appear to be working
https://bugs.kde.org/show_bug.cgi?id=438886 Manuel de la Fuente changed: What|Removed |Added CC||m...@nueljl.in --- Comment #6 from Manuel de la Fuente --- shared-mime-info released 2.2 ~7 months ago now, and it includes godot files (https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/tests/mime-detection/list#L892) so it should be possible to fix this now. I'll send a mr if I manage to do it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447537] task-* icons are inconsistent
https://bugs.kde.org/show_bug.cgi?id=447537 Manuel de la Fuente changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||m...@nueljl.in -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 456961] Icon for Fortran source code
https://bugs.kde.org/show_bug.cgi?id=456961 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461123] "The screen locker is broken and unlocking is not possible anymore" with console output saying "Creating a fake screen in order for Qt not to crash"
https://bugs.kde.org/show_bug.cgi?id=461123 --- Comment #17 from Clarence Manuel --- For people who upgraded to fedora 37, it seems like it was caused by a dependency issue with some qt components See https://www.reddit.com/r/Fedora/comments/yxwb7j/comment/iws29hj/ -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461123] When waking from standby or leaving the screenlocker a blackscreen shows "The screen locker is broken and unlocking is not possible anymore"
https://bugs.kde.org/show_bug.cgi?id=461123
--- Comment #12 from Clarence Manuel ---
(In reply to kingofgamesyami from comment #11)
> I have the same problem.
>
> Plasma Version: 5.26.3
> KDE Frameworks Version: 5.100.0
> Qt Version: 5.15.6
> Graphic Platform: Wayland
>
> $ /usr/libexec/kscreenlocker_greet --testing
> QSocketNotifier: Can only be used with threads started with QThread
> kscreenlocker_greet: Lockscreen QML outdated, falling back to default
> kf.kirigami: Failed to find a Kirigami platform plugin
> Segmentation fault (core dumped)
>
> Running the same through gdb reveals more information about the segfault:
>
> Thread 1 "kscreenlocker_g" received signal SIGSEGV, Segmentation fault.
> 0x77d3fda6 in QtWayland::wl_surface::object (this=0x10) at
> /usr/include/qt5/QtWaylandClient/5.15.7/QtWaylandClient/private/qwayland-
> wayland.h:637
> 637 struct ::wl_surface *object() { return m_wl_surface; }
>
> I find it strange that QtWaylandClient shows version 5.15.7 when I have qt
> 5.15.6, so I ran dnf list installed qt5*, everything is 5.15.6-1.fc37 except
> the following:
>
> qt5-qtfeedback.x86_64 @ 20180903gita14bd0b-5.fc37
> qt5-qtwebengine.x86_64 @ 5.15.10-2.fc37
> qt5-qtwebengine-freeworld.x86_64 @ 5.15.10-2.fc37
> qt5-qtwebkit.x86_64 @ 5.212.0-0.68.alpha4.fc37
> qt5-srpm-macros.noarch @ 5.15.7-1.fc37
I tried the same and I got the same output with gdb
[New Thread 0x7fffc67fc6c0 (LWP 5124)]
[New Thread 0x7fffb24bf6c0 (LWP 5135)]
kf.kirigami: Failed to find a Kirigami platform plugin
[New Thread 0x7fffb1cbe6c0 (LWP 5136)]
[New Thread 0x7fffb14bd6c0 (LWP 5137)]
[Thread 0x7fffb14bd6c0 (LWP 5137) exited]
[Thread 0x7fffb1cbe6c0 (LWP 5136) exited]
Thread 1 "kscreenlocker_g" received signal SIGSEGV, Segmentation fault.
0x77d3bda6 in QtWayland::wl_surface::object (this=0x10) at
/usr/include/qt5/QtWaylandClient/5.15.7/QtWaylandClient/private/qwayland-wayland.h:637
637 struct ::wl_surface *object() { return m_wl_surface; }
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 461123] When waking from standby or leaving the screenlocker a blackscreen shows "The screen locker is broken and unlocking is not possible anymore"
https://bugs.kde.org/show_bug.cgi?id=461123 Clarence Manuel changed: What|Removed |Added CC||rencedm...@gmail.com Platform|Debian stable |Fedora RPMs Version|5.25.0 |5.26.3 --- Comment #10 from Clarence Manuel --- I have this issue as well. The shutdown and restart button on the UI doesn't work either. I have to use the terminal for shutting down or rebooting. Running `usr/libexec/kscreenlocker_greet --testing` gives this output: ``` QSocketNotifier: Can only be used with threads started with QThread kf.kirigami: Failed to find a Kirigami platform plugin Segmentation fault (core dumped) ``` -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 461562] Add preferences-desktop-touchscreen icon
https://bugs.kde.org/show_bug.cgi?id=461562 Manuel de la Fuente changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||023d16aecac775b41b7df143cd5 ||bedcc94d6b243 --- Comment #2 from Manuel de la Fuente --- Git commit 023d16aecac775b41b7df143cd5bedcc94d6b243 by Manuel Jesús de la Fuente. Committed on 12/11/2022 at 17:14. Pushed by mdelafuente into branch 'master'. Add touchscreen icons to devices and preferences A +12 -0icons-dark/devices/16/input-touchscreen.svg A +12 -0icons-dark/devices/22/input-touchscreen.svg A +12 -0icons/devices/16/input-touchscreen.svg A +12 -0icons/devices/22/input-touchscreen.svg A +81 -0icons/devices/64/input-touchscreen.svg A +72 -0icons/preferences/22/preferences-desktop-touchscreen.svg A +68 -0icons/preferences/32/preferences-desktop-touchscreen.svg https://invent.kde.org/frameworks/breeze-icons/commit/023d16aecac775b41b7df143cd5bedcc94d6b243 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 338501] Monitor doesn't go to sleep when the screen is locked
https://bugs.kde.org/show_bug.cgi?id=338501 Johan Manuel changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE --- Comment #4 from Johan Manuel --- Unfortunately I don't have the right setup to try and reproduce this now, but I think this is in fact a duplicate of https://bugs.kde.org/show_bug.cgi?id=348529 as a comment above indicated, so I will close it as such. *** This bug has been marked as a duplicate of bug 348529 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 Johan Manuel changed: What|Removed |Added CC||johan.man...@live.fr --- Comment #41 from Johan Manuel --- *** Bug 338501 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461157] Wayland: Panel set to "Windows can Cover" does not release focus properly, compared to X11
https://bugs.kde.org/show_bug.cgi?id=461157 Manuel C changed: What|Removed |Added CC|manuel.manu.del...@gmail.co | |m | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461259] New: Allow assignment of modifier keys to tablet buttons on Wayland
https://bugs.kde.org/show_bug.cgi?id=461259 Bug ID: 461259 Summary: Allow assignment of modifier keys to tablet buttons on Wayland Classification: Applications Product: systemsettings Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: usability, wayland Severity: minor Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: manuel.manu.del...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 153361 --> https://bugs.kde.org/attachment.cgi?id=153361=edit Screenshot of tablet button config screen and the associated config file section SUMMARY Under X11, the kcm-wacomtablet used to allow assigning a modifier key (like Ctrl) to a tablet button. The new interface used for Wayland does not, but I was able to set this up by editing the config file manually. This binding is not properly displayed in the settings [see attachment] but works fine otherwise. EXPECTED RESULT Allow for this assignment in the config interface, and show it properly. SOFTWARE/OS VERSIONS Linux: 6.0.5-arch1-1 (64-bit) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 461198] New: Wayland: Night Colour filter is restored incorrectly to reconnected display
https://bugs.kde.org/show_bug.cgi?id=461198 Bug ID: 461198 Summary: Wayland: Night Colour filter is restored incorrectly to reconnected display Classification: Plasma Product: kdeplasma-addons Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: reproducible, wayland Severity: normal Priority: NOR Component: Night Color Control Assignee: plasma-b...@kde.org Reporter: manuel.manu.del...@gmail.com CC: kwin-bugs-n...@kde.org, vlad.zahorod...@kde.org Target Milestone: --- SUMMARY I recently switched from X11 to Wayland and found a regression with the Night Colour filter being applied incorrectly. I run a multi-monitor setup, where I usually turn off my monitor at night (when Night Colour is active). When it is reconnected the next day (when Night Colour is off), the monitor still has the Night Colour filter active. This did not happen under X11. To reset this state, I currently manually toggle Night Colour on and then back off. I also tested the reverse, (disconnect while filter off, reconnect with it on) and it still happens. I assume there is just no check if the filter still applies when the display is reconnected. STEPS TO REPRODUCE 1. Have 2 monitors 2. Turn on Night Colour 3. Disconnect, or disable the second monitor 4. Turn off Night Colour 5. Reconnect the monitor OBSERVED RESULT The reconnected display still has the blue light filter applied, while on the other one it is off EXPECTED RESULT The reconnected display has no blue light filter applied, like on the still connected display. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, Kernel 6.0.5-arch1-1 (amd64) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Graphics Platform: Wayland (1.21.0) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 375043] baloo search misses lyx files - lack of the corresponding codec (extractor) in kfilemetadata
https://bugs.kde.org/show_bug.cgi?id=375043 --- Comment #2 from manuel fernández --- It now works fine, thank you. Finds the lyx files. Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-23-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: LENOVO Product Name: 20V9 System Version: ThinkBook 13s G2 ITL fraternalmente, manuel fernández-guasti https://luz.izt.uam.mx On 29/10/22 19:37, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=375043 > > Justin Zobel changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Justin Zobel --- > Thank you for reporting this bug in KDE software. As it has been a while since > this issue was reported, can we please ask you to see if you can reproduce the > issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461157] Wayland: Panel set to "Windows can Cover" does not release focus properly, compared to X11
https://bugs.kde.org/show_bug.cgi?id=461157 Manuel C changed: What|Removed |Added CC||manuel.manu.del...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461157] Wayland: Panel set to "Windows can Cover" does not release focus properly, compared to X11
https://bugs.kde.org/show_bug.cgi?id=461157 Manuel C changed: What|Removed |Added Summary|Switching focus to a window |Wayland: Panel set to |that covers a panel, hides |"Windows can Cover" does |the panel (wayland) |not release focus properly, ||compared to X11 --- Comment #2 from Manuel C --- One more thing I found, that should probably be tacked onto this issue, since it kinda depends on the same functionality: When moving the mouse to the screen edge of the panel, it gets raised into focus. On X11, unless you click on it to raise it explicitly, it goes back to its previous position, shortly after moving the mouse off it. On Wayland, it moves to the top and stays there indefinitely, until I click on a window to cover it again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461157] Switching focus to a window that covers a panel, hides the panel (wayland)
https://bugs.kde.org/show_bug.cgi?id=461157 --- Comment #1 from Manuel C --- ADDENDUM: On X11, the panel stays open while the mouse is over it, regardles of windows covering it, and then once the mouse moves off it, after a short delay, it lowers itself to its covered position. I really hope this behaviour can be replicated in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461157] Switching focus to a window that covers a panel, hides the panel (wayland)
https://bugs.kde.org/show_bug.cgi?id=461157 Manuel C changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461157] New: Switching focus to a window that covers a panel, hides the panel (wayland)
https://bugs.kde.org/show_bug.cgi?id=461157 Bug ID: 461157 Summary: Switching focus to a window that covers a panel, hides the panel (wayland) Classification: Plasma Product: plasmashell Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: manuel.manu.del...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY I just switched from X11 to wayland, and noticed a regression: I have a panel that is set to "Windows can Cover." When switching to a window that covers this panel, either by clicking or scrolling through the on-panel task manager, the panel instantly gets covered. This didn't happen on X11, where it stayed above the window, until I move the mouse off. This means I can now no longer switch through several windows by scrolling, if one of them is maximized over the panel. I don't know if this changes this behaviour in general, but in "Window Behaviour," I have the window activation policy set to "Focus follows mouse (mouse precedence)" in addition to "Click raises active window." STEPS TO REPRODUCE 1. Set panel to "Window can cover" 2. Open any window covering the panel 3. Switch to the window, clicking on its task manager entry OBSERVED RESULT The panel instantly gets covered and looses focus EXPECTED RESULT The panel stays in focus above the window SOFTWARE/OS VERSIONS Linux: Arch Linux, Kernel 6.0.5-arch1-1 (amd64) (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Graphics Platform: Wayland (1.21.0) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447536] audio-headphones and audio-headset icons are inconsistent
https://bugs.kde.org/show_bug.cgi?id=447536 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||2a00bb6f52e6704dde7897b156f ||bc99e7be5ceef --- Comment #1 from Manuel de la Fuente --- Git commit 2a00bb6f52e6704dde7897b156fbc99e7be5ceef by Manuel Jesús de la Fuente. Committed on 28/10/2022 at 11:34. Pushed by mdelafuente into branch 'master'. Add 64px audio-headset, fix issues with 64px audio-headphones audio-headphones had the gradient overlapping the earcups and earpads, and the right earcup was misaligned. audio-headset was missing the 64px (audio-headphones was not), so it was mixing monochrome and color icons.   M +37 -48 icons/devices/64/audio-headphones.svg A +49 -0icons/devices/64/audio-headset.svg https://invent.kde.org/frameworks/breeze-icons/commit/2a00bb6f52e6704dde7897b156fbc99e7be5ceef -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458214] Icon request: KSokoban game app icon
https://bugs.kde.org/show_bug.cgi?id=458214 --- Comment #4 from Manuel de la Fuente --- So sorry, forgot about this! I'm getting back through the backlog of stuff to do (class this year is absolutely brutal). Some time ago, I sent another couple of versions to the VDG chat and we generally agreed on one of the new ones. I attempted to ping you through Telegram but the bridge may have not worked quite right then, then waited for a reply and yeah... I'll create a MR for frameworks/breeze-icons first and leave it for a bit in case you want any further tweaks, then also add it to ksokoban's repo in case it's needed there too. You should get a follow up email from this bug report with the MR link. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 329918] KDE Systrem Settings window crashes repeatably.
https://bugs.kde.org/show_bug.cgi?id=329918 Manuel Mommertz <2...@gmx.de> changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #10 from Manuel Mommertz <2...@gmx.de> --- Yes, I can reproduce with current stable version on gentoo -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 PrinterModel::updateDest (this=this@entry=0x55ff16eccba0, destItem=0x0, printer=...) at /usr/src/debug/kde-apps/print-manager-22.04.3/print-manager-22.04.3/libkcups/PrinterModel.cpp:249 #5 0x7f54aa698017 in PrinterModel::getDestsFinished (this=0x55ff16eccba0, request=0x55ff16bbdb50) at /usr/src/debug/kde-apps/print-manager-22.04.3/print-manager-22.04.3/libkcups/PrinterModel.cpp:137 #6 0x7f5528e2b22f in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f5529a6979f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #8 0x7f5528e00938 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f5528e03e2e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f5528e51143 in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7f5526b6cd5b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7f5526b6d008 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7f5526b6d0bf in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7f5528e50bf4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #15 0x7f5528dff3cb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #16 0x7f5528e07710 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #17 0x55ff15a44be0 in ?? () #18 0x7f55287a220a in __libc_start_call_main () from /lib64/libc.so.6 #19 0x7f55287a22bc in __libc_start_main () from /lib64/libc.so.6 #20 0x55ff15a454b1 in ?? () [Inferior 1 (process 24007) detached] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 444085] Popup menus from menu bar show up in wrong place.
https://bugs.kde.org/show_bug.cgi?id=444085 Manuel Schönheinz changed: What|Removed |Added CC||schoenhe...@googlemail.com --- Comment #6 from Manuel Schönheinz --- I have the same problem. It seems to be a wayland related issue since if I log in with X11 it is normal. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412478] Kdevelop crashing when trying to configure meson project
https://bugs.kde.org/show_bug.cgi?id=412478 Manuel Mommertz <2...@gmx.de> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Manuel Mommertz <2...@gmx.de> --- I tried it with version 22.04.3 and cannot reproduce it anymore. Thanks for this nice peace of software. And thanks for still taking care of this old report. :) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458214] Icon request: KSokoban game app icon
https://bugs.kde.org/show_bug.cgi?id=458214 --- Comment #1 from Manuel de la Fuente --- Created attachment 151929 --> https://bugs.kde.org/attachment.cgi?id=151929=edit List of proposals for the icon I've attached a few icons based on the original game assets, with a take on the current one too (though that one is a bit more rough). Let me know your thoughts! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458055] system setting sidebar icons should be monochrome
https://bugs.kde.org/show_bug.cgi?id=458055 --- Comment #1 from Manuel de la Fuente --- I'm pretty sure there's colorful 22px icons already: - merge(d) request https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/124 ^ has a screenshot with all the icons - repo https://invent.kde.org/frameworks/breeze-icons/-/tree/master/icons/preferences/22 - commit https://invent.kde.org/frameworks/breeze-icons/-/commit/264bb9a57dfec9ffc335315f53948e49ed37c6bb We haven't switched to 24px, at least yet -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 457930] Seemingly high ram usage
https://bugs.kde.org/show_bug.cgi?id=457930 --- Comment #2 from Manuel de la Fuente --- Created attachment 151345 --> https://bugs.kde.org/attachment.cgi?id=151345=edit Searching akonadi under the processes view -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 457930] Seemingly high ram usage
https://bugs.kde.org/show_bug.cgi?id=457930 --- Comment #1 from Manuel de la Fuente --- Created attachment 151344 --> https://bugs.kde.org/attachment.cgi?id=151344=edit System Monitor overview shows high RAM usage under Calendar Reminders -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 457930] New: Seemingly high ram usage
https://bugs.kde.org/show_bug.cgi?id=457930 Bug ID: 457930 Summary: Seemingly high ram usage Product: Reminder Daemon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@nueljl.in Target Milestone: --- Created attachment 151343 --> https://bugs.kde.org/attachment.cgi?id=151343=edit List of installed packages relating to akonadi SUMMARY Using System Monitor / Overview / Applications, 'Calendar Reminders' takes up around 300mb of ram. It's not in the processes view, so I'm guessing it's just combining everything akonadi in there. STEPS TO REPRODUCE 1. Log in 2. Open System Monitor OBSERVED RESULT Calendar Reminder takes too much RAM EXPECTED RESULT Calendar Reminder doesn't take too much RAM SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.16-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 Clarence Manuel changed: What|Removed |Added CC||rencedm...@gmail.com --- Comment #5 from Clarence Manuel --- Same thing with my PC, but for Application Launcher. I'm using Fedora 36 KDE Plasma Spin. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 436945] Request for icon for Tokodon
https://bugs.kde.org/show_bug.cgi?id=436945 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||m...@nueljl.in --- Comment #1 from Manuel de la Fuente --- fixed by @bugsbane and yourself in https://invent.kde.org/network/tokodon/-/commit/a01f35bd99433b7fa3ed36bf647d9e21d988b4aa :) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435986] Delete button in Filesystem Expose plugin configuration is nearly invisible in the light theme
https://bugs.kde.org/show_bug.cgi?id=435986 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-android/comm ||it/ecd27525795573e90d115173 ||f3a929f665d1f442 --- Comment #2 from Manuel de la Fuente --- Git commit ecd27525795573e90d115173f3a929f665d1f442 by Manuel Jesús de la Fuente. Committed on 05/02/2022 at 09:52. Pushed by mdelafuente into branch 'master'. Make trashcan icon visible M +7-2res/drawable/ic_delete.xml https://invent.kde.org/network/kdeconnect-android/commit/ecd27525795573e90d115173f3a929f665d1f442 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 448356] Yellow mimetype icons are barely visible against light backgrounds
https://bugs.kde.org/show_bug.cgi?id=448356 Manuel de la Fuente changed: What|Removed |Added CC||m...@nueljl.in --- Comment #3 from Manuel de la Fuente --- Yellow over white won't really work no matter how hard we try imho, unless we add a fill and outline or something. Maybe something like #DFAC07 could be """"passable"""", but the contrast ratio would be only 2 in the best of cases which isn't really acceptable still. Maybe we should revisit specific parts of the breeze palette or the breeze icons (combined with ken's massive updates)? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447595] Unity layout / dual screen - problem with maximized windows
https://bugs.kde.org/show_bug.cgi?id=447595 --- Comment #12 from Manuel Laggner --- I can confirm that the latest version of branch v0.10 works as expected! kudos -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447595] Unity layout / dual screen - problem with maximized windows
https://bugs.kde.org/show_bug.cgi?id=447595 --- Comment #11 from Manuel Laggner --- sorry, bad wording here. I am no maintainer - I just spoke about us users which want a unity setup in KDE plasma -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447595] Unity layout / dual screen - problem with maximized windows
https://bugs.kde.org/show_bug.cgi?id=447595 --- Comment #6 from Manuel Laggner --- the problem with plasma is that they overlap in the upper left corner and that's why we need to stick with latte... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447595] Unity layout / dual screen - problem with maximized windows
https://bugs.kde.org/show_bug.cgi?id=447595 --- Comment #4 from Manuel Laggner --- Created attachment 144935 --> https://bugs.kde.org/attachment.cgi?id=144935=edit Unity layout with latte -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447595] Unity layout / dual screen - problem with maximized windows
https://bugs.kde.org/show_bug.cgi?id=447595 --- Comment #3 from Manuel Laggner --- Created attachment 144934 --> https://bugs.kde.org/attachment.cgi?id=144934=edit Unity layout with plasma -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447595] Unity layout / dual screen - problem with maximized windows
https://bugs.kde.org/show_bug.cgi?id=447595 --- Comment #2 from Manuel Laggner --- I've just tried to reproduce the issue using plasma panels and it works there (see left_panel.png). When I try to use latte (because with default plasma panels, you cannot get a good unity layout), the maximized window goes below the left panel (see left_panel_latte.png). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447595] New: Unity layout / dual screen - problem with maximized windows
https://bugs.kde.org/show_bug.cgi?id=447595 Bug ID: 447595 Summary: Unity layout / dual screen - problem with maximized windows Product: lattedock Version: 0.10.6 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: manuel.lagg...@gmail.com Target Milestone: --- SUMMARY *** If you use the default unity layout in a dual screen setup, maximized windows go below the left panel. The same setup works in single screen setups. My screen setup is the following: LEFT: laptop screen (1920x1080) / no latte dock on that screen RIGHT: main screen (2560x1440) / Top panel and left panel When I maximize a window on the RIGHT screen, the window goes below the LEFT panel, but not below the TOP panel. *** STEPS TO REPRODUCE 1. Setup a dual monitor environment 2. make sure the RIGHT screen is the main screen containing a unity layout of latte (tested with 0.10.6) 3. maximize any application on the RIGHT (main) screen. Tested with Firefox and Dolphin OBSERVED RESULT The maximized widows go below the LEFT panel EXPECTED RESULT The maximized windows should NOT go below the LEFT panel (the same way as with the TOP panel) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.7 KDE Frameworks Version: 5.68 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 447459] Feature request: Ability to visually group tabs or change their background color
https://bugs.kde.org/show_bug.cgi?id=447459 Manuel Tancoigne changed: What|Removed |Added CC||m...@experimentslabs.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396960] Feature Request: ability to set Konsole tab background color using escape codes (like can already be done for the terminal background color)
https://bugs.kde.org/show_bug.cgi?id=396960 Manuel Tancoigne changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=447459 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 447459] New: Feature request: Ability to visually group tabs or change their background color
https://bugs.kde.org/show_bug.cgi?id=447459 Bug ID: 447459 Summary: Feature request: Ability to visually group tabs or change their background color Product: yakuake Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: m...@experimentslabs.com Target Milestone: --- Created attachment 144820 --> https://bugs.kde.org/attachment.cgi?id=144820=edit UI examples SUMMARY As a user with a lot of tabs opened, In order to quickly jump from one tab to another I want to have a visual way to spot tabs in the same "context" STEPS TO REPRODUCE I thought about a few ways to achieve this: - Tab background color: 1. Open tabs 2. Right-click on a tab (or use a keyboard shortcut) to assign one of the pre-defined contexts to the tab 3. Result: the tab background changed 4. A keyboard shortcut allows me to "jump" to the previous/next tab of the same group - Tabs groups: 1. Open tabs 2. Right-click on a tab (or use a keyboard shortcut) to assign one of the pre-defined contexts to the tab 3. Result: the tab is somewhat grouped with others of the same context 4. A keyboard shortcut allows me to "jump" from one group to another OBSERVED RESULT General workflow is improved ADDITIONAL INFORMATION If the solution of colored backgrounds is implemented, the proposed colors should be the ones from the KDE style colors to match the current user theme ? I have no Qt skills to do this myself quickly, but I'll be glad to give it a try. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396960] Feature Request: ability to set Konsole tab background color using escape codes (like can already be done for the terminal background color)
https://bugs.kde.org/show_bug.cgi?id=396960 Manuel Tancoigne changed: What|Removed |Added CC||m...@experimentslabs.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412477] meson support not working when meson is a symlink
https://bugs.kde.org/show_bug.cgi?id=412477 --- Comment #6 from Manuel Mommertz <2...@gmx.de> --- (In reply to Igor Kushnir from comment #5) > Can anyone verify that > https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/251 fixes this > issue? Yes, works perfectly! :) Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #4 from Manuel Geißer --- Created attachment 143624 --> https://bugs.kde.org/attachment.cgi?id=143624=edit Update log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #3 from Manuel Geißer --- By the way, the purple description background is really strange. That's only on X, not on Wayland, though. Is this on purpose, or should I file a separate issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #2 from Manuel Geißer --- Same problem on X - I have made you a screencast. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #1 from Manuel Geißer --- Created attachment 143622 --> https://bugs.kde.org/attachment.cgi?id=143622=edit Screencast -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Manuel Geißer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] New: Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Bug ID: 445587 Summary: Response to mouse clicks broken Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY Since today's kde/qt updates, the Overview effect does not respond to mouse clicks anymore. (This used to work correctly prior to the update.) STEPS TO REPRODUCE 1. Trigger the Overview effect (e. g. using active corner or shortcut) 2. (Left-)click on the area of a window OBSERVED RESULT Nothing happens. EXPECTED RESULT The effect should be closed and the clicked window should be shown. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Might be Wayland-only. I haven't used X since a longer time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time
https://bugs.kde.org/show_bug.cgi?id=442846 Manuel de la Fuente changed: What|Removed |Added CC||m...@nueljl.in --- Comment #8 from Manuel de la Fuente --- Can reproduce using Ryzen+Radeon. It hard locks the computer, you can't change into another TTY and can't reisub either. You can only hard reset, and that seemingly breaks both X and SDDM so you're stuck with startplasma-wayland. It still happens ever after doing a rollback with Snapper. Disabling the automatic lock screen after $i++ minutes will actually still freeze the computer. Plasmashell dies and the background is black, in my case QtWidget apps switch between the regular font and a smaller bitmap one every second. You can only move the cursor and the cursor states will actually change and UI elements in the apps themselves will switch on hover after a bit of a delay but you can't interact with anything. TTY switching and reisub still doesn't work for some reason though.) Operating System: openSUSE Tumbleweed CPU: AMD Ryzen 9 5900X GPU: AMD Radeon RX6700XT RAM: 31.6 GiB sorry for not adding more information about the software versions and such, I'll be adding it tomorrow in case it's necessary but it's the most recent stable release since it's Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 --- Comment #23 from Manuel Geißer --- > Present Windows effect is what is causing the issue here. Disabled it and I > can > see the background once again. Wow, good catch! Disabling Present Windows indeed solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Manuel changed: What|Removed |Added CC||mdom...@gmail.com Version|5.22.90 |5.23.0 --- Comment #16 from Manuel --- Please, restore the Desktop Cube switching effect. The cube effect is NECESSARY for KDE to be the KOOL Desktop Environment. Please put the Cube effect back on. My desk is not the same without it. Without excuses. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #95 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Well, actually that turns out to be wrong. It got released today (that is, in KDE Neon). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #93 from Manuel Geißer --- > What do you mean? Nate said the effect is being shipped with Plasma 5.23 > though > it "may" (which I guess is now "will") not replace it until later. Is this > wrong? The problem we're talking about is that it will take even longer for this usability issue to be fixed, due to Plasma 5.23 getting additional months of polishing and QA. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #91 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Yeah, if developers had acknowledged what an annoyance this dimming is, they could just have commented out the problematic line and release an updated package nine years ago, or they could have merged PR 885 five months ago... It appears that fixing usability issues is just regarded as an unimportant side-effect of the Present Windows replacement; primarily it's just the move to a different underlying technology. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443102] Add the icons for Syncthing and Joplin in Breeze icon set
https://bugs.kde.org/show_bug.cgi?id=443102 Manuel de la Fuente changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443102] Add the icons for Syncthing and Joplin in Breeze icon set
https://bugs.kde.org/show_bug.cgi?id=443102 --- Comment #4 from Manuel de la Fuente --- Fixed in the latest merge request. I'm guessing didn't auto close because I'm still changing my email adress in some places. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 --- Comment #4 from Manuel Geißer --- I think this is perhaps rather an issue with Qt(-Wayland) than with Kate -- A question: Is it possible to deactivate completition, or dismiss the completition history as a workaround? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #27 from Manuel Geißer --- Sure. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #25 from Manuel Geißer --- Created attachment 142205 --> https://bugs.kde.org/attachment.cgi?id=142205=edit (unrelated) okular-mupdf-backend build error -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #24 from Manuel Geißer --- So I installed the dependencies and tried to build okular-mupdf-backend (from git master), but it fails with some "Variable not declared in this scope" error. Also there have been no commits to the repository since a year. Is this backend still functional? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #23 from Manuel Geißer --- I guess you are referring to https://invent.kde.org/sandsmark/okular-mupdf-backend ? The thing is, there are multiple unofficial Okular MuPDF generators around... Moreover, why is this not officially part of Okular and not packaged in Debian, Ubuntu, and KDE Neon? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #21 from Manuel Geißer --- `grep -r mupdf` on the Okular source tree doesn't find anything, either -- You are receiving this mail because: You are watching all bug changes.
