[KPipeWire] [Bug 489434] Spectacle crashes on finishing recording with pipewire 1.2.0
https://bugs.kde.org/show_bug.cgi?id=489434 Sam changed: What|Removed |Added CC||samuel.coll...@live.co.uk -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392180] LTO build simplification: __asm__ in m_libcsetjmp.c
https://bugs.kde.org/show_bug.cgi?id=392180 Sam James changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=84861 CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 482648] With Breeze Dark icon theme and >100% display scaling, Symbolic icons are not shown
https://bugs.kde.org/show_bug.cgi?id=482648 Sam Duan changed: What|Removed |Added CC||samdu...@protonmail.com --- Comment #7 from Sam Duan --- (In reply to Nate Graham from comment #5) > I can reproduce the issue with Qt 6.7 now. I was unable to with 6.6; I fear > this is a Qt 6.7 regression somehow. > > Anyway, the steps to reproduce are now very simple: > > 1. Open Dolphin > 2. Open System Settings > Colors & Themes > Icons > Breeze Dark > Apply > 3,. Move cursor over Dolphin's Places Panel > > Boom, non-symbolic icons. Sorry to restart the conversation now, but I don't think the problem is only related to Qt 6.7 though. Using a 4k screen at 200% zooming (on Wayland) myself with openSUSE Tumbleweed, this problem can be reproduced since day one when Plasma 6.0 pushed into Tumbleweed's repo. Also the bug only affects the dark icon theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489180] plasma crashed in QtWaylandClient::QWaylandWindow::waylandScreen() when external monitor lost power
https://bugs.kde.org/show_bug.cgi?id=489180 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489657] Certain fractional scaling levels cause mouse to stick at screen edge independent of edge barrier feature
https://bugs.kde.org/show_bug.cgi?id=489657 --- Comment #10 from Sam --- Have just tested with a 125Hz mouse and couldn't reproduce the issue anywhere near as easily; I had to move the mouse extremely slowly to the point that I wouldn't notice it if I wasn't looking for it. This is quite a contrast from the 1,000Hz mouse that I've been experience the issue with, which can happen at a much higher speed, which seems to correlate with @Zamundaaa's theory. Thanks for the help everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489657] Certain fractional scaling levels cause mouse to stick at screen edge independent of edge barrier feature
https://bugs.kde.org/show_bug.cgi?id=489657 --- Comment #8 from Sam --- (In reply to Sam from comment #7) > (In reply to fanzhuyifan from comment #6) > > (In reply to Zamundaaa from comment #5) > > > This is most likely because of the fractional part in the display size, > > > the > > > two displays don't actually touch. To cross over to the other display, a > > > single mouse event has to move the cursor as far as the distance between > > > the > > > two screens. > > > In this case, with 1440p + 115% scale, the display is 2226.087 logical > > > units > > > wide, and the next one is at position 2227, so the distance is about as > > > high > > > as it can be. > > > > In this case the effect would be more noticeable with a high polling rate > > mouse. > > Ah, that makes a lot of sense! I believe I do have a higher-than-average > polling rate mouse (8000 DPI max I think, but I don't run it at that), so > I'll try playing with that this evening. In that case, would there anything > we could do to "fix" this? Perhaps by adjusting the screen boundary logic? > I'm not at all familiar with how this works, or if it's even a KDE-specific > thing. Ignore 8000 DPI, I need to learn to proof read - polling rate is 1,000 Hz. Not sure if this is super high (from a brief internet search, a lot of mice don't seem to advertise their polling rate), but I'll try with other mice I have this evening and see what happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489657] Certain fractional scaling levels cause mouse to stick at screen edge independent of edge barrier feature
https://bugs.kde.org/show_bug.cgi?id=489657 --- Comment #7 from Sam --- (In reply to fanzhuyifan from comment #6) > (In reply to Zamundaaa from comment #5) > > This is most likely because of the fractional part in the display size, the > > two displays don't actually touch. To cross over to the other display, a > > single mouse event has to move the cursor as far as the distance between the > > two screens. > > In this case, with 1440p + 115% scale, the display is 2226.087 logical units > > wide, and the next one is at position 2227, so the distance is about as high > > as it can be. > > In this case the effect would be more noticeable with a high polling rate > mouse. Ah, that makes a lot of sense! I believe I do have a higher-than-average polling rate mouse (8000 DPI max I think, but I don't run it at that), so I'll try playing with that this evening. In that case, would there anything we could do to "fix" this? Perhaps by adjusting the screen boundary logic? I'm not at all familiar with how this works, or if it's even a KDE-specific thing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489657] Certain fractional scaling levels cause mouse to stick at screen edge
https://bugs.kde.org/show_bug.cgi?id=489657 --- Comment #2 from Sam --- (In reply to fanzhuyifan from comment #1) > fwiw if the cursor is stuck at the top or at the bottom, it might be because > the two screens have different sizes, and you are trying to move the cursor > into empty space. Thanks, but that isn't the issue - both monitors are the same size and have the same fractional scaling set. Thee cursor isn't actually completely stuck, as moving the mouse faster overcomes whatever inertia is stopping it from reaching the other monitor. It's very similar behaviour to the new "edge barrier" feature, except it only happens in one direction (left monitor -> right monitor) and at specific fractional scaling levels, and it happens even when that feature is switched off (and indeed was happening before that feature existed). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489657] Certain fractional scaling levels cause mouse to stick at screen edge
https://bugs.kde.org/show_bug.cgi?id=489657 Sam changed: What|Removed |Added CC||samuel.coll...@live.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489657] New: Certain fractional scaling levels cause mouse to stick at screen edge
https://bugs.kde.org/show_bug.cgi?id=489657 Bug ID: 489657 Summary: Certain fractional scaling levels cause mouse to stick at screen edge Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: samuel.coll...@live.co.uk Target Milestone: --- SUMMARY I have a 2-monitor setup (left|right, with left as primary, both monitors 1440p) and I use a 115% fractional scaling level on both monitors (Wayland). This causes the cursor to "stick" (behaves like the new "edge barrier" feature) to the right edge of the left screen when trying to move onto my right monitor. This only happens in that direction (right->left is not sticky at all unless edge barrier is switched on, but that makes the left->right direction even stickier). This doesn't happen at 100%, 200%, or 125% scale, but does seem to happen at 110% and 120%, and a number of other scaling factors that aren't a multiple of 25 (though not all). This was also happening prior to plasma 6.1 (before the edge barrier feature was introduced). I also tested at 1080p, and whilst I don't see the same behaviour at 115%, I do at 110%, though it is a little less noticeable. STEPS TO REPRODUCE 1. Configure 2 monitors side-by-side, left primary, with one of the problematic resolution/scaling combinations (e.g. 1440p/115% or 1080p/110%) in display configuration (system settings) 2. Switch off edge barrier in screen edges (system settings) 3. Move mouse slowly from left screen onto right OBSERVED RESULT Mouse cursor gets stuck at screen border EXPECTED RESULT Mouse cursor moves freely onto right screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with Plasma 6.1.1 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[libplasma] [Bug 413481] plasmashell crashes in Plasma::FrameSvgPrivate::generateBackground() on login
https://bugs.kde.org/show_bug.cgi?id=413481 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 489169] Powerdevil crashes a lot in ddc_close_display() after update to Plasma 6.1.0
https://bugs.kde.org/show_bug.cgi?id=489169 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088 --- Comment #11 from Sam James --- Thank you very much - that works great! -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487338] Possible regression: Floating point exception
https://bugs.kde.org/show_bug.cgi?id=487338 --- Comment #11 from Sam James --- Sample files: ``` cd /tmp touch a b echo hi > b kdiff3 a b ``` -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487338] Possible regression: Floating point exception
https://bugs.kde.org/show_bug.cgi?id=487338 Sam James changed: What|Removed |Added CC||s...@gentoo.org --- Comment #10 from Sam James --- (In reply to simon from comment #9) > I can also reproduce this. Thanks, I just came here with the same backtrace and proposed patch. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 489343] 'No such file or directory' error starting dbus service for kdeconnect
https://bugs.kde.org/show_bug.cgi?id=489343 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088 --- Comment #9 from Sam James --- > But obviously we need some real test cases. I was confused by what you meant, then I checked the See Also'd bugs and saw there's no testcases there except for an artificial one :| -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473020] Qt-based software crashes in QtWaylandClient::QWaylandWindow::handleScreensChanged() when external screen powers up or down
https://bugs.kde.org/show_bug.cgi?id=473020 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476868] Enabling WCG or applying ICC "increases" window transparency
https://bugs.kde.org/show_bug.cgi?id=476868 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477017] Plasma is not properly rendered when using an ICC profile and both the contrast and blur effects
https://bugs.kde.org/show_bug.cgi?id=477017 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489229] Broken rendering with OpenGL compositing on i915
https://bugs.kde.org/show_bug.cgi?id=489229 Sam James changed: What|Removed |Added See Also||https://bugreports.qt.io/br ||owse/QTBUG-126706 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482868] Broken rendering with OpenGL compositing on i915
https://bugs.kde.org/show_bug.cgi?id=482868 Sam James changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=489229 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489229] Broken rendering with OpenGL compositing on i915
https://bugs.kde.org/show_bug.cgi?id=489229 Sam James changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482868 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489229] Broken rendering with OpenGL compositing on i915
https://bugs.kde.org/show_bug.cgi?id=489229 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088
--- Comment #7 from Sam James ---
(In reply to Mark Wielaard from comment #6)
> (In reply to Sam James from comment #5)
> > (In reply to Mark Wielaard from comment #4)
> > > See also https://bugs.kde.org/show_bug.cgi?id=391148 which comes with a
> > > patch.
> >
> > Hi Mark, thanks for looking!
> >
> > That patch seems to work:
> >
> > ```
> > ==144687== Invalid read of size 8
> > ==144687==at 0x109F43: filter (test.c:59)
> > ==144687==by 0x109F43: AnalyzeSamples (test.c:100)
> > ==144687==by 0x109366: main (test.c:167)
> > ==144687== Address 0x4637bfeabfe4bbd4 is not stack'd, malloc'd or
> > (recently) free'd
> > ==144687==
> > ==144687==
> > ==144687== Process terminating with default action of signal 11 (SIGSEGV):
> > dumping core
> > ==144687== General Protection Fault
> > ==144687==at 0x109F43: filter (test.c:59)
> > ==144687==by 0x109F43: AnalyzeSamples (test.c:100)
> > ==144687==by 0x109366: main (test.c:167)
> > ```
> > although the address looks a bit suspicious and I wasn't aware of out of
> > bounds access in the testcase, so not sure if it really is decoding fully
> > correctly?
>
> hmmm, yeah that is kind of odd. That address is so weird that it really must
> be invalid. Does the original program also try to read from that address and
> produce a SIGSEGV when not run under valgrind?
Nope!
>
> Maybe as a quick hack check you could change that DIP("vmovq %s,%s\n",
> nameXMMReg(rG), nameIReg64(rE)); in the patch to vex_printf(...)
>
> If it decodes correctly it should print vmovq %xmm12,%xmm0
>
==402260==
vmovq %xmm12,%r8
vmovq %xmm14,%r10
==402260== Invalid read of size 8
==402260==at 0x109F46: filter (test.c:59)
==402260==by 0x109F46: AnalyzeSamples (test.c:100)
==402260==by 0x109366: main (test.c:167)
==402260== Address 0x4637bfeabfe4bbd4 is not stack'd, malloc'd or (recently)
free'd
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 482868] Broken rendering with OpenGL compositing on i915
https://bugs.kde.org/show_bug.cgi?id=482868 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] When KWin is compiled with any AVX512 features, windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #34 from Sam James --- Which arm64 CPUs? (Wondering if it's a particular vectorisation thing.) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417572] vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xED 0xC5 0xF9 0x51
https://bugs.kde.org/show_bug.cgi?id=417572 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391148] Unhandled AVX instruction vmovq %xmm9,%xmm1
https://bugs.kde.org/show_bug.cgi?id=391148 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088 --- Comment #5 from Sam James --- (In reply to Mark Wielaard from comment #4) > See also https://bugs.kde.org/show_bug.cgi?id=391148 which comes with a > patch. Hi Mark, thanks for looking! That patch seems to work: ``` ==144687== Invalid read of size 8 ==144687==at 0x109F43: filter (test.c:59) ==144687==by 0x109F43: AnalyzeSamples (test.c:100) ==144687==by 0x109366: main (test.c:167) ==144687== Address 0x4637bfeabfe4bbd4 is not stack'd, malloc'd or (recently) free'd ==144687== ==144687== ==144687== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==144687== General Protection Fault ==144687==at 0x109F43: filter (test.c:59) ==144687==by 0x109F43: AnalyzeSamples (test.c:100) ==144687==by 0x109366: main (test.c:167) ``` although the address looks a bit suspicious and I wasn't aware of out of bounds access in the testcase, so not sure if it really is decoding fully correctly? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487439] SIGILL in JDK11, JDK17
https://bugs.kde.org/show_bug.cgi?id=487439 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088 --- Comment #2 from Sam James --- Note that this is also unreleased gcc and using binutils from recent trunk too. ``` $ ld --version GNU ld (Gentoo p1) 2.42.50.20240615 Copyright (C) 2024 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) a later version. This program has absolutely no warranty. ``` Again, I don't mind if the bug is junk / not a Valgrind problem :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088 --- Comment #1 from Sam James --- Created attachment 170895 --> https://bugs.kde.org/attachment.cgi?id=170895=edit foo.xz foo.xz is `test` from above (compiled binary from `test.c` attached earlier, using \gcc-15 test.c -o foo -O3 -ggdb3 -march=native -fipa-pta -fno-vect-cost-model`). On this system, -march=native is -march=znver2 (pretty much). ``` $ gcc-15 --version gcc-15 (Gentoo Hardened 15.0. p, commit e275a9e2e7e85e8c0071f7cffbd7948bc891573d) 15.0.0 20240621 (experimental) 52a82359073653e312aaa5703f7e0ce339588961 Copyright (C) 2024 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] New: Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088 Bug ID: 489088 Summary: Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8 Classification: Developer tools Product: valgrind Version: 3.24 GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: s...@gentoo.org Target Milestone: --- Created attachment 170894 --> https://bugs.kde.org/attachment.cgi?id=170894=edit test.c I hit the following when reducing a possible GCC bug (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115533). At points during my reduction of a test from flac, I got the following: ``` $ gcc-15 test.c -o foo -O3 -ggdb3 -march=native -fipa-pta -fno-vect-cost-model && valgrind ./foo ==2627495== Memcheck, a memory error detector ==2627495== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==2627495== Using Valgrind-3.24.0.GIT and LibVEX; rerun with -h for copyright info ==2627495== Command: ./foo ==2627495== vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8 vex amd64->IR: REX=0 REX.W=0 REX.R=1 REX.X=0 REX.B=0 vex amd64->IR: VEX=1 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==2627495== valgrind: Unrecognised instruction at address 0x109e00. ==2627495==at 0x109E00: filter (test.c:64) ==2627495==by 0x109E00: AnalyzeSamples (test.c:100) ==2627495==by 0x109366: main (test.c:167) ==2627495== Your program just tried to execute an instruction that Valgrind ==2627495== did not recognise. There are two possible reasons for this. ==2627495== 1. Your program has a bug and erroneously jumped to a non-code ==2627495==location. If you are running Memcheck and you just saw a ==2627495==warning about a bad jump, it's probably your program's fault. ==2627495== 2. The instruction is legitimate but Valgrind doesn't handle it, ==2627495==i.e. it's Valgrind's fault. If you think this is the case or ==2627495==you are not sure, please let us know and we'll try to fix it. ==2627495== Either way, Valgrind will now raise a SIGILL signal which will ==2627495== probably kill your program. ==2627495== ==2627495== Process terminating with default action of signal 4 (SIGILL): dumping core ==2627495== Illegal opcode at address 0x109E00 ==2627495==at 0x109E00: filter (test.c:64) ==2627495==by 0x109E00: AnalyzeSamples (test.c:100) ==2627495==by 0x109366: main (test.c:167) ``` It's possible that the program was just jumping to genuine junk, but I thought I'd report it on the off-chance it isn't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489072] Plasma, KRunner, Dr Konqi, and the lock screen crash following a screen turning off and back on (presumably at the upper edge)
https://bugs.kde.org/show_bug.cgi?id=489072 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463897] Kinetic Scrolling [Wishlist]
https://bugs.kde.org/show_bug.cgi?id=463897 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 456383] Add inertial scrolling to WheelHandler for touchpad and touchscreen scrolls
https://bugs.kde.org/show_bug.cgi?id=456383 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420925] Add kinetic scrolling on Trackpad use too
https://bugs.kde.org/show_bug.cgi?id=420925 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 474805] Creating zstd archives is NOT multi-threaded
https://bugs.kde.org/show_bug.cgi?id=474805 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 474174] Please add multithread / multicore extraction and compression
https://bugs.kde.org/show_bug.cgi?id=474174 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=488653 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453877] Allow multiple simultaneous auth methods to be used without having to fail at one of them, first via multiple PAM stacks
https://bugs.kde.org/show_bug.cgi?id=453877 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481913] My wacom pen will not align with the canvas. The pen works fine on every other part of the program but as soon as I hover it above the canvas it completely misaligns. I know the p
https://bugs.kde.org/show_bug.cgi?id=481913 sam changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||s.gorano...@gmail.com Ever confirmed|0 |1 --- Comment #6 from sam --- I have the same issue on Wacom One 13. Windows 11 Pro, 23H2, 22631.3737. The only workaround I have so I can use the tablet is to restart the driver via Wacom Center. It's strange how the pen position is correct when used over the UI and all menus, but it's with big offset over the canvas only. So my flow is: Open Krita and find out the cursor is with offset; Quit Krita (not only the document); Go to Wacom Center. Go to Settings and click Restart Driver. Sometimes it does not work with one restart so I restart it second time to be safe. Open Krita and open any document. Now pen/tablet is working properly. I seems it gets "broken" again after PC restart or something like that while the tablet is off. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487825] Dragging applet from panel to desktop is now broken, goes into stuck limbo state
https://bugs.kde.org/show_bug.cgi?id=487825 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 478426] [Wayland] Screenshot quality issues with dual monitor setup and fractional scale factor on one of them
https://bugs.kde.org/show_bug.cgi?id=478426 Sam James changed: What|Removed |Added CC||ast...@gentoo.org, ||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 485691] Ghostwriter crashes on launch
https://bugs.kde.org/show_bug.cgi?id=485691 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 260675] In dolphin one can't choose to open directory in new window with middle click
https://bugs.kde.org/show_bug.cgi?id=260675 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486966] Plasma Wayland breaks when more than ~110 windows are open
https://bugs.kde.org/show_bug.cgi?id=486966 --- Comment #5 from Sam --- Annoys me when that happens to me. Relatable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486966] Plasma Wayland breaks when more than ~110 windows are open
https://bugs.kde.org/show_bug.cgi?id=486966 --- Comment #3 from Sam --- Error occurs at roughly 60% memory utilization. Happens again with Konsole. Also at roughly 20GB of memory utilization -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486966] Plasma Wayland breaks when more than ~110 windows are open
https://bugs.kde.org/show_bug.cgi?id=486966 --- Comment #2 from Sam --- I counted windows 1 by one. I have 32 gb of ram, so memory prob isn't an issue, but ill doublecheck. Assuming one window takes 125-200 mb, that should be around 150-240 windows the system should handle (assuming system without the windows uses 2GB). Even after closing all the windows, the plasma session fails to recover without a login. I will test again soon while watching memory. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486966] New: Plasma Wayland breaks when more than ~110 windows are open
https://bugs.kde.org/show_bug.cgi?id=486966 Bug ID: 486966 Summary: Plasma Wayland breaks when more than ~110 windows are open Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: samuel.c.erik...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Plasma Wayland breaks when more than ~110 windows are open STEPS TO REPRODUCE 1. Choose a browser 2. Quarter tile the browser window 3. Spam open new windows OBSERVED RESULT Just past 100 windows, the wallpaper and taskbar dissappear and the wayland session is not able to recover until logout and log back in. EXPECTED RESULT Kwin tolerates the large number of windows or warns the user that opening more windows is not possible/recommended at this time. SOFTWARE/OS VERSIONS Operating System: TUXEDO OS 3 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-10036-tuxedo (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Attempet with both Google Chrome (Flatpak) and Firefox packaged by disto maintainer (Tuxedo Computers) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486093] -Wstrict-aliasing in tests
https://bugs.kde.org/show_bug.cgi?id=486093
--- Comment #1 from Sam James ---
As a workaround, we're building tests with:
```
emake CFLAGS="${CFLAGS} -fno-strict-aliasing" LDFLAGS="${LDFLAGS}
-Wl,-z,notext" check
```
for now.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 486093] New: -Wstrict-aliasing in tests
https://bugs.kde.org/show_bug.cgi?id=486093
Bug ID: 486093
Summary: -Wstrict-aliasing in tests
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: s...@gentoo.org
Target Milestone: ---
THere's a lot of -Wstrict-aliasing instances in the testsuite. In Gentoo, we
try to recommend people to use -Werror=strict-aliasing
-Werror=lto-type-mismatch -Werror=some-other-bits when using LTO to help find
likely runtime problems (Valgrind isn't LTO-compaitble for other reasons but
that's neither here nor there for this).
When building Valgrind with such, we get:
```
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../..
-I../../../include -I../../../coregrind -I../../../include -I../../../VEX/pub
-I../../../VEX/pub -DVGA_amd64=1 -DVGO_l
inux=1 -DVGP_amd64_linux=1 -DVGPV_amd64_linux_vanilla=1 -DVGA_SEC_x86=1
-DVGP_SEC_amd64_linux=1 -Winline -Wall -Wshadow -Wno-long-long -g
-fno-stack-protector -m64 -O -ffast-math -
mfpmath=387 -mfancy-math-387 -O3 -march=native -mtls-dialect=gnu2
-fno-semantic-interposition -pipe -fcf-protection=none
-fdiagnostics-color=always -fdiagnostics-urls=never -frecord-gcc
-switches -Wa,-O2 -Wa,-mtune=znver2 -Wstrict-aliasing -Wfree-nonheap-object
-Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wstrict-aliasing
-Wfree-nonheap-object -Werror
=lto-type-mismatch -Werror=strict-aliasing -Werror=odr
-Wbuiltin-declaration-mismatch -ggdb3 -Wformat -Wformat-security -Waddress
-Warray-bounds -Wfree-nonheap-object -Wint-to-pointer-c
ast -Wmain -Wnonnull -Wodr -Wreturn-type -Wsizeof-pointer-memaccess
-Wstrict-aliasing -Wstring-compare -Wuninitialized -Wvarargs
-fno-stack-protector -fno-harden-control-flow-redundancy
-c -o more_x87_fp-more_x87_fp.o `test -f 'more_x87_fp.c' || echo
'./'`more_x87_fp.c
make[5]: 'shr_edx' is up to date.
more_x87_fp.c: In function ‘test_fcvt’:
more_x87_fp.c:108:28: error: dereferencing type-punned pointer will break
strict-aliasing rules [-Werror=strict-aliasing]
108 | printf("a=%016llx\n", *(long long *));
|^~~
more_x87_fp.c:109:34: error: dereferencing type-punned pointer will break
strict-aliasing rules [-Werror=strict-aliasing]
109 | printf("la=%016llx %04x\n", *(long long *),
| ^~~~
more_x87_fp.c:110:12: warning: ‘la’ is used uninitialized [-Wuninitialized]
110 |*(unsigned short *)((char *)() + 8));
|^~
more_x87_fp.c:96:17: note: ‘la’ declared here
96 | long double la;
| ^~
cc1: some warnings being treated as errors
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../..
-I../../../include -I../../../coregrind -I../../../include -I../../../VEX/pub
-I../../../VEX/pub -DVGA_amd64=1 -DVGO_l
inux=1 -DVGP_amd64_linux=1 -DVGPV_amd64_linux_vanilla=1 -DVGA_SEC_x86=1
-DVGP_SEC_amd64_linux=1 -Winline -Wall -Wshadow -Wno-long-long -g
-fno-stack-protector -m32 -mmmx -msse -O3 -
march=native -mtls-dialect=gnu2 -fno-semantic-interposition -pipe
-fcf-protection=none -fdiagnostics-color=always -fdiagnostics-urls=never
-frecord-gcc-switches -Wa,-O2 -Wa,-mtune=znver
2 -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch
-Werror=strict-aliasing -Werror=odr -Wstrict-aliasing -Wfree-nonheap-object
-Werror=lto-type-mismatch -Werror=strict-
aliasing -Werror=odr -Wbuiltin-declaration-mismatch -ggdb3 -Wformat
-Wformat-security -Waddress -Warray-bounds -Wfree-nonheap-object
-Wint-to-pointer-cast -Wmain -Wnonnull -Wodr -Wretur
n-type -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstring-compare
-Wuninitialized -Wvarargs -fno-stack-protector
-fno-harden-control-flow-redundancy -c -o more_x86_fp.o more_x86_fp.c
more_x86_fp.c: In function ‘test_fcvt’:
more_x86_fp.c:98:28: error: dereferencing type-punned pointer will break
strict-aliasing rules [-Werror=strict-aliasing]
98 | printf("a=%016llx\n", *(long long *));
|^~~
more_x86_fp.c:99:34: error: dereferencing type-punned pointer will break
strict-aliasing rules [-Werror=strict-aliasing]
99 | printf("la=%016llx %04x\n", *(long long *),
| ^~~~
more_x86_fp.c:100:12: warning: ‘la’ is used uninitialized [-Wuninitialized]
100 |*(unsigned short *)((char *)() + 8));
|^~
more_x86_fp.c:86:17: note: ‘la’ declared here
86 | long double la;
| ^~
cc1: some warnings being treated as errors
```
This is with `gcc version 14.0.1 20240423 (experimental)
0c8e99e5c32be9f2604f3c330814993f29818037 (Gentoo Hardened 14.0. p,
[plasmashell] [Bug 482816] On Wayland, real-fake-session-restored application not restored onto their virtual desktops
https://bugs.kde.org/show_bug.cgi?id=482816 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336990] Chromium and Firefox does not remember their virtual desktops on session restore
https://bugs.kde.org/show_bug.cgi?id=336990 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379949] any Hyper or Super key misidentified as Meta key
https://bugs.kde.org/show_bug.cgi?id=379949 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp
https://bugs.kde.org/show_bug.cgi?id=485487 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472369] Please allow disabling resize-both-windows when quick tiling
https://bugs.kde.org/show_bug.cgi?id=472369 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- 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 Sam Birch changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad gestures should be configurable
https://bugs.kde.org/show_bug.cgi?id=402857 Sam Hathaway changed: What|Removed |Added CC||bugs.kde@munkynet.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 484002] Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm()
https://bugs.kde.org/show_bug.cgi?id=484002 Sam James changed: What|Removed |Added See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=31509 CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483617] kicker: segfault when built with clang
https://bugs.kde.org/show_bug.cgi?id=483617 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482090] Taskbar pins not saved on new Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482090 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel
https://bugs.kde.org/show_bug.cgi?id=482469 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits
https://bugs.kde.org/show_bug.cgi?id=481113 --- Comment #9 from Sam James --- Has anybody hit this on non-Gentoo yet? I haven't started looking at this yet, but it's an important factor if everyone hitting it is on Gentoo. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits
https://bugs.kde.org/show_bug.cgi?id=481113 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482757] New: Crash / Segfault on window drag
temd[910]: Started Handle legacy xembed system
tray icons.
Mar 02 11:29:07 archlinux drkonqi-coredump-launcher[83003]: Unable to find file
for pid 81800 expected at
"kcrash-metadata/kwin_wayland.0a90c8d638bb43f3b468792c3f174a99.81800.ini"
Mar 02 11:29:07 archlinux systemd[1]:
drkonqi-coredump-processor@3-82963-0.service: Deactivated successfully.
Mar 02 11:29:08 archlinux kwin_wayland[82969]: could not create a component for
"org.kde.spectacle.desktop"
Mar 02 11:29:08 archlinux kwin_wayland[82969]: OpenGL vendor string:
AMD
Mar 02 11:29:08 archlinux kwin_wayland[82969]: OpenGL renderer string:
AMD Radeon Graphics (radeonsi, rembrandt, LLVM 16.0.6, DRM 3.57,
6.7.6-arch1-2)
Mar 02 11:29:08 archlinux kwin_wayland[82969]: OpenGL version string:
4.6 (Core Profile) Mesa 24.0.2-arch1.1
Mar 02 11:29:08 archlinux kwin_wayland[82969]: OpenGL shading language version
string: 4.60
Mar 02 11:29:08 archlinux kwin_wayland[82969]: Driver:
Unknown
Mar 02 11:29:08 archlinux kwin_wayland[82969]: GPU class:
Unknown
Mar 02 11:29:08 archlinux kwin_wayland[82969]: OpenGL version:
4.6
Mar 02 11:29:08 archlinux kwin_wayland[82969]: GLSL version:
4.60
Mar 02 11:29:08 archlinux kwin_wayland[82969]: Mesa version:
24.0.2
Mar 02 11:29:08 archlinux kwin_wayland[82969]: Requires strict binding:
no
Mar 02 11:29:08 archlinux kwin_wayland[82969]: Virtual Machine:
no
Mar 02 11:29:08 archlinux kwin_wayland[82969]: Timer query support:
yes
Mar 02 11:29:08 archlinux kwin_wayland[82969]: KPackageStructure of
KPluginMetaData(pluginId:"alwaysopenonactivescreen", fileName:
"/home/sam/.local/share/kwin/scripts/alwaysopenonactivescreen/metadata.json")
does not match requested format "KWin/Script"
Mar 02 11:29:08 archlinux kwin_wayland[82969]: qt.qml.typeresolution.cycle:
Cyclic dependency detected between
"qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and
"qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
Mar 02 11:29:08 archlinux kwin_wayland[82969]: qml: Polonium INF: Polonium
started!
Mar 02 11:29:08 archlinux kwin_wayland[82969]: qml: Polonium DBG: Config is
{"debug":true,"tilePopups":false,"filterProcess":["krunner","yakuake","kded","polkit","plasmashell","org.kde.plasmashell"],"filterCaption":[""],"timerDelay":102,"keepTiledBelow":false,"borders":3,"maximizeSingle":false,"resizeAmount":10,"engineType":0,"insertionPoint":1,"rotateLayout":false}
Mar 02 11:29:08 archlinux kwin_wayland_wrapper[83113]: (WW) Option "-listen"
for file descriptors is deprecated
Mar 02 11:29:08 archlinux kwin_wayland_wrapper[83113]: Please use "-listenfd"
instead.
Mar 02 11:29:08 archlinux kwin_wayland_wrapper[83113]: (WW) Option "-listen"
for file descriptors is deprecated
Mar 02 11:29:08 archlinux kwin_wayland_wrapper[83113]: Please use "-listenfd"
instead.
Mar 02 11:29:09 archlinux kernel: [drm] Send DSC enable to synaptics
Mar 02 11:29:09 archlinux systemd[910]:
app-google\x2dchrome\x20\x283\x29-4401e9c2002c4281ab3678208c61d776.scope:
Consumed 39.184s CPU time.
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: The XKEYBOARD keymap
compiler (xkbcomp) reports:
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86CameraAccessEnable
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86CameraAccessDisable
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86CameraAccessToggle
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86NextElement
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86PreviousElement
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86AutopilotEngageToggle
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86MarkWaypoint
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86Sos
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86NavChart
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86FishingChart
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[83178]: > Warning:
Could not resolve keysym XF86SingleRangeRadar
Mar 02 11:29:09 archlinux kwin_wayland_wrapper[
[systemsettings] [Bug 482409] Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 --- Comment #8 from Sam Barrow --- (In reply to Mike from comment #7) > Sam, > Would you mind one more little task? Could you go to system > settings/printers and try adding the printer again, this time when the empty > list comes up, try clicking on each listed printer option in the list and > see if anything happens. You mean the two printers listed on the left? they both show the same thing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482409] Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 --- Comment #6 from Sam Barrow --- (In reply to Mike from comment #5) > Yes, that's perfect and kind of what I expected to see. > > The hint from your prev screeny is the msg that shows the "name was not > activatable". It looks like plasma printer manager is not properly falling > back to manual driver selection after that name failure received from > CUPS/Open Printing System. I'll see about getting that fixed up, but, > meantime, your printer is actually now configured and should work from your > applications. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482409] Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 --- Comment #4 from Sam Barrow --- (In reply to Mike from comment #3) > Okay, that is good info. In the meantime, you can add the printer using > kde-add-printer; you'll pick the driver then continue to finish. At that > point, the printer should show up in your system settings/printer manager. > > If you would, once you're at system settings/printers, click to configure > the printer (the configure button for that printer) and then click the > "Select" button for Make/Model and post a screen shot of that. It may or > may not be able to show the model, but that will be another hint for me to > check. This? Looks about the same as the add printer screen. https://imgur.com/a/At7G2lB Just to double check, I tried to add it again from system settings and it still looks like the original screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482409] Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 --- Comment #2 from Sam Barrow --- (In reply to Mike from comment #1) > Sam, > I do not see that CUPS has a driver listed for this Brother model. The > Plasma Printer Manager uses the CUPS driver list as well as the Open > Printing System to pick recommended drivers and it appears it just can't > find the driver from this source. If you have a .ppd file that came with > the drivers you installed, you should be able to install it manually, but > first let's check a couple of things: > > Can you run this command from a terminal and see if your printer can be > added? kde-add-printer --add-printer It does seem to show the drivers I have installed when I do kde-add-printer --add-printer https://imgur.com/a/JZiQyOS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482409] New: Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 Bug ID: 482409 Summary: Unclear how to add printer / button disabled Classification: Applications Product: systemsettings Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: plasma-b...@kde.org Reporter: s...@sambarrow.com CC: dantt...@gmail.com Target Milestone: --- Created attachment 166401 --> https://bugs.kde.org/attachment.cgi?id=166401=edit screenshot SUMMARY *** 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 *** Trying to add a printer, it detects it via the network but I'm not sure how to proceed from here. Drivers are installed (brother-brgenml1 on arch which I've used previously). Screenshot attached. STEPS TO REPRODUCE 1. Add a printer OBSERVED RESULT I get an empty page with a disabled button titled "select recommended driver" EXPECTED RESULT Anything. Either an error if something is not working, or a way to continue. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.7.6-arch1-2 (64-bit) (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481999] Plasma 6: Some applications like steam and quassel show a white page icon in systray
https://bugs.kde.org/show_bug.cgi?id=481999 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480296] UB in plasma-workspace's ksmserver/legacy.cpp (-Wrestrict with ::select)
https://bugs.kde.org/show_bug.cgi?id=480296 --- Comment #2 from Sam James --- I'll put it on the list and will hopefully remember ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479679] plasmashell exits with -1 on right mouse click with layershellqt: Cannot attach popup of unknown type
https://bugs.kde.org/show_bug.cgi?id=479679 --- Comment #14 from Sam James --- ... also generally worth starting downstream for such things to not bother upstream until we've tried some basic stuff like that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479679] plasmashell exits with -1 on right mouse click with layershellqt: Cannot attach popup of unknown type
https://bugs.kde.org/show_bug.cgi?id=479679 Sam James changed: What|Removed |Added CC||s...@gentoo.org --- Comment #13 from Sam James --- Please try to be explicit about what makes your system interesting when using e.g. clang, -O3, and so on. Even if things should work in such a configuration, identifying what's _different_ is important. Anyway, for runtime misbehaviour, try UBSAN and alternating compiler (so GCC if using Clang). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480522] kdeconnect plasmoid fails to compile with LTO enabled
https://bugs.kde.org/show_bug.cgi?id=480522 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480520] Krita does not compile with LTO enabled
https://bugs.kde.org/show_bug.cgi?id=480520 Sam James changed: What|Removed |Added CC||s...@gentoo.org --- Comment #2 from Sam James --- (Note that it may build with just -flto, but -Wodr warnings indicate it's unsafe, so we tell people downstream to use -Werror=odr with LTO.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480296] New: UB in plasma-workspace's ksmserver/legacy.cpp (-Wrestrict with ::select)
https://bugs.kde.org/show_bug.cgi?id=480296 Bug ID: 480296 Summary: UB in plasma-workspace's ksmserver/legacy.cpp (-Wrestrict with ::select) Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s...@gentoo.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY See https://invent.kde.org/plasma/plasma-workspace/-/blob/034205dd9dc667f6abcf8fb8a53baa6094bb4449/ksmserver/legacy.cpp#L179 where ::select is called as: >::select(fd + 1, , nullptr, , ); This triggers a warning ``` * /var/tmp/portage/kde-plasma/plasma-workspace-6.0.49./work/plasma-workspace-6.0.49./ksmserver/legacy.cpp:179:30: warning: passing argument 2 to ‘restrict’-qualified parameter aliases with argument 4 [-Wrestrict] ``` with gcc version 14.0.1 20240121 (experimental) (Gentoo Hardened 14.0.1_pre20240121 p16) at least, and it looks right. >From `select(3p`): ``` int select(int nfds, fd_set *restrict readfds, fd_set *restrict writefds, fd_set *restrict errorfds, struct timeval *restrict timeout); ``` is passed as both `readfds` and `errorfds` which is forbidden. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 480026] Screen turning off in one of various ways (idle power off, esc on lock screen, Turn Off Screen shortcut invoked over D-Bus) shuts screen off very temporarily
https://bugs.kde.org/show_bug.cgi?id=480026 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 473483] KPipeWire-based Task Manager window previews are blank on Wayland with Nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=473483 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 477478] Preview of running apps on taskbar are "empty"
https://bugs.kde.org/show_bug.cgi?id=477478 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 Sam James changed: What|Removed |Added Version|git master |5.92.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 --- Comment #5 from Sam James --- (In reply to Bug Janitor Service from comment #1) > A possibly relevant merge request was started @ > https://invent.kde.org/plasma/kwin/-/merge_requests/4862 That MR helps for me too. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- 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 Sam Dinner changed: What|Removed |Added CC||samdin...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418555] Discover gets stuck at "Fetching updates..." and shows an error message related to fwupd
https://bugs.kde.org/show_bug.cgi?id=418555 Sam Piper changed: What|Removed |Added Platform|Arch Linux |Kubuntu Version|unspecified |5.24.7 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Sam Piper --- This error started to appear about two weeks ago. It is consistent on every launch of discover. The service cannot activate and will time out after 25s. Then discover appears to function normally. Troubleshooting fwupd using systemd or any command using fwupdmgr also reproduces the error. => $ journalctl -xeu fwupd-refresh.service The process' exit code is 'exited' and its exit status is 1. Dec 29 14:42:36 thelio76 systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Subject: Unit failed Defined-By: systemd Support: http://www.ubuntu.com/support The unit fwupd-refresh.service has entered the 'failed' state with result 'exit-code'. Dec 29 14:42:36 thelio76 systemd[1]: Failed to start Refresh fwupd metadata and update motd. Subject: A start job for unit fwupd-refresh.service has failed Defined-By: systemd Support: http://www.ubuntu.com/support My System - Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 6.6.6-76060606-generic (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 62.0 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418555] Discover gets stuck at "Fetching updates..." and shows an error message related to fwupd
https://bugs.kde.org/show_bug.cgi?id=418555 Sam Piper changed: What|Removed |Added CC||spiperman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305136] File associations are broken in gtk/glib apps due to lack of /usr/share/applications/kde-mimeapps.list file installed by default
https://bugs.kde.org/show_bug.cgi?id=305136 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 337475] Add BMI2 instructions for 32-bit x86
https://bugs.kde.org/show_bug.cgi?id=337475 Sam James changed: What|Removed |Added CC||s...@gentoo.org --- Comment #3 from Sam James --- Yeah, I keep hitting this and it's a pain. I came across https://github.com/10110111/valgrind accidentally the other day and found it has some BMI patches for 32-bit, but not tried it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477817] Need to save the login credentials for Mediawiki export persistent
https://bugs.kde.org/show_bug.cgi?id=477817 --- Comment #1 from Sam Wilson --- This would be great! Especially as the username and password used should not be one's normal password, but a bot password, and so is often more laborious to use. https://www.mediawiki.org/wiki/Manual:Bot_passwords -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477817] Need to save the login credentials for Mediawiki export persistent
https://bugs.kde.org/show_bug.cgi?id=477817 Sam Wilson changed: What|Removed |Added CC||s...@samwilson.id.au -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)
https://bugs.kde.org/show_bug.cgi?id=478624 Sam James changed: What|Removed |Added See Also||http://bugs.debian.org/1057 ||693 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)
https://bugs.kde.org/show_bug.cgi?id=478624 Sam James changed: What|Removed |Added Summary|Valgrind incompatibility|Valgrind incompatibility |with binutils-2.42 on x86 |with binutils-2.42 on x86 ||with new nop patterns ||(unhandled instruction ||bytes: 0x2E 0x8D 0xB4 0x26) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86
https://bugs.kde.org/show_bug.cgi?id=478624 --- Comment #1 from Sam James --- For a testcase we probably should just have a simple assembly/byte sequence of all the "nops" used in https://sourceware.org/cgit/binutils-gdb/tree/gas/config/tc-i386.c#n1256 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] New: Valgrind incompatibility with binutils-2.42 on x86
https://bugs.kde.org/show_bug.cgi?id=478624 Bug ID: 478624 Summary: Valgrind incompatibility with binutils-2.42 on x86 Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: s...@gentoo.org CC: aurel...@aurel32.net, debfx-...@fobos.de, s...@extundo.com Target Milestone: --- [Forgive me, as I've not yet hit this myself, but reporting it based on the Debian bug after discussing it with mjw.] The upcoming binutils-2.42 release [0] seems to be incompatible with Valgrind on x86 after a commit landed [1] to emit additional nop patterns which Valgrind doesn't yet recognise. This was originally reported in Debian [2] (CC'd some of the participants whose emails I could find on here). In the linked Debian bug, Simon gives a simple reproducer w/ output: ``` 117s vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26 117s ==5711== valgrind: Unrecognised instruction at address 0x4d285c8. 117s ==5711==at 0x4D285C8: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27893: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27B0E: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27069: gss_import_name (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x486BA0F: ??? (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x485757C: gsasl_step (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x4857623: gsasl_step64 (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x10B387: ??? (in /usr/bin/gsasl) 117s ==5711==by 0x4ADE7C4: (below main) (libc_start_call_main.h:58) 117s ==5711== Your program just tried to execute an instruction that Valgrind 117s ==5711== did not recognise. There are two possible reasons for this. 117s ==5711== 1. Your program has a bug and erroneously jumped to a non-code 117s ==5711==location. If you are running Memcheck and you just saw a 117s ==5711==warning about a bad jump, it's probably your program's fault. 117s ==5711== 2. The instruction is legitimate but Valgrind doesn't handle it, 117s ==5711==i.e. it's Valgrind's fault. If you think this is the case or 117s ==5711==you are not sure, please let us know and we'll try to fix it. 117s ==5711== Either way, Valgrind will now raise a SIGILL signal which will 117s ==5711== probably kill your program. 117s ==5711== 117s ==5711== Process terminating with default action of signal 4 (SIGILL) 117s ==5711== Illegal opcode at address 0x4D285C8 117s ==5711==at 0x4D285C8: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27893: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27B0E: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27069: gss_import_name (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x486BA0F: ??? (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x485757C: gsasl_step (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x4857623: gsasl_step64 (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x10B387: ??? (in /usr/bin/gsasl) 117s ==5711==by 0x4ADE7C4: (below main) (libc_start_call_main.h:58) ``` with steps to reproduce: ``` podman run --arch 386 -it --rm debian:unstable-slim apt update apt install valgrind gsasl apt dist-upgrade valgrind --error-exitcode=1 /usr/bin/gsasl -m GSSAPI -d --no-starttls --imap no-such-domain.example 143 ``` [0] https://inbox.sourceware.org/binutils/0f118fd8-5630-4742-a353-3309e6285...@redhat.com/T/#u [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ad9f3230565ca40bfa1d9a3106272cb125f2 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057693 -- You are receiving this mail because: You are watching all bug changes.
