[KRdp] [Bug 489748] New: Text input from the client is one character behind at all times on the server.
https://bugs.kde.org/show_bug.cgi?id=489748 Bug ID: 489748 Summary: Text input from the client is one character behind at all times on the server. Classification: Plasma Product: KRdp Version: 6.1.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mikesmith929+...@hotmail.com CC: ahiems...@heimr.nl 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 When connected to the KRDP server, from a windows 10 remote desktop client, any text inputted from the client is one character behind visually on the server. This unfortunately randomly happens while in a session. At first it's fine but after a random event or time all text input is one character behind. STEPS TO REPRODUCE 1. Connect to the server. 2. Use the server for a time. 3. OBSERVED RESULT When you type in the Konsole (as an example) text will be lagged by one character. EXPECTED RESULT When you type on the server all characters get displayed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.7-200.fc40.x86_64 (64-bit) ADDITIONAL INFORMATION It's as if the character is stuck in some kind of buffer. Perhaps some text graphical buffer or maybe just no update is the graphics refresh is initiated for the last character typed? I'm at a loss. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488857] Enabling autostart KRDP requires user interaction
https://bugs.kde.org/show_bug.cgi?id=488857 Mike Smith changed: What|Removed |Added CC||mikesmith929+...@hotmail.co ||m --- Comment #4 from Mike Smith --- (In reply to wolfyrion from comment #0) > > SUMMARY > KRDP - Enabling autostart requires user interaction at startup > > STEPS TO REPRODUCE > 1. Go to Settings - Remote Desktop -> enable autostart on login > 2. > 3. Can confirm this also does not Autostart on login for me if I have "Autostart on login" checked off. Yet the "Enable RDP server" is not toggled ON. It is OFF. Using Plasma version 6.1.1 Frameworks version: 6.3.0 QT Version: 6.7.1 Kernel Version: 6.9.7-200.fc40.x86_64 (64-bit) Graphics: Wayland -- 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.1
https://bugs.kde.org/show_bug.cgi?id=488653 Mike Pagano changed: What|Removed |Added CC||mpag...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 489097] krdpserver crashes when a connection comes from Remote Desktop Windows 11
https://bugs.kde.org/show_bug.cgi?id=489097 --- Comment #6 from Mike Smith --- (In reply to dalewyn from comment #5) > (In reply to Mike Smith from comment #4) > > Hey Gaël would you mind sharing your RDP setting for the client? I ask > > because I can connect from WIndows 11 and Windows 10 RDP client but only if > > "Persistent bitmap caching" is turned off on the client. > > > > You can find that setting if you click on the "Show Options" dropdown and go > > to the Experience tab of Remote Desktop Connection (clinet side). > > > > Can you confirm if that is active or inactive in your test? > > Not Gael, but I followed your suggestion and got a different error code > about a protocol error on my Windows 11 RDP client. > Googling that led me to a suggestion to drop the color resolution down. > > So after disabling bitmap caching as you suggested and dropping the color > resolution down from 32-bit to 16-bit, I got it to connect. The actual video > feed looks like garbage, but it does work in a very janky sense. Ok I've seen this before also. This time it's server side. On your krdp server in Fedora what do you have the "video quality" set to? I suspect it's in the middle? Set it to the highest quality. You should then be able to connect with 32-bit colour on the client. Report back :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
https://bugs.kde.org/show_bug.cgi?id=488187 --- Comment #20 from Mike Clarke --- I updated all my packages today, this took Plasma from 6.0.5 to 6.1.0 and I am now able to shutdown from KDE without any problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469426] Cannot move windows past left or top of desktop
https://bugs.kde.org/show_bug.cgi?id=469426 --- Comment #15 from mike wyatt --- @dofficialgman which version of Plasma / KDE are you using? I'm on Arch / aarch64, and this issue seems to be fixed on 6.0 / 6.1. Tested on both X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488614] New: Unable to shutdown, logout, restart or hibernate from the KDE menu
https://bugs.kde.org/show_bug.cgi?id=488614 Bug ID: 488614 Summary: Unable to shutdown, logout, restart or hibernate from the KDE menu Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jmc-...@milibyte.co.uk Target Milestone: --- Following a recent upgrade I'm no longer able to shutdown, logout, restart or hibernate from the KDE menu. The screen goes blank but the mouse pointer remains on screen and still responds to movement of the mouse but not to any button presses. At this stage I need to press and hold the power button to shutdown. The problem appears to be related to plasma-workspace-x11 which was upgraded to plasma-workspace-x11-6.0.5.1-1.fc40.x86_64. If I switch over to using wayland instead X11 I can shutdown from KDE but this isn't a usable workaround for me because one of the useful features of keepasxc isn't available with wayland. I am still able to shutdown from the command line with 'shutdown -P' instead of using the KDEE menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 5590 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488454] Ghosting with Chromium window
https://bugs.kde.org/show_bug.cgi?id=488454 --- Comment #2 from Mike Lothian --- https://photos.app.goo.gl/YdXud43B4tuba9649 is the video of kicker -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488454] New: Ghosting with Chromium window
https://bugs.kde.org/show_bug.cgi?id=488454 Bug ID: 488454 Summary: Ghosting with Chromium window Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m...@fireburn.co.uk Target Milestone: --- I've seen this issue since switching to wayland back before the Mega Release, I mentioned it on IRC but wasn't sure if it was a bug in kwin, the graphics drivers or a hardware issue I'm certain it's not monitor burn in - it changes too much and it often flickers I'm currently running Qt 6.7.1 KF from Git, and Plasma from Git, I've seen this going all the way back from before MR6 and Qt 6.6 The ghosting remains even after Chromium is closed and it's a Wayland enabled chromium (so there's no Xwayland involved) Screenshots using Spectacle don't show the artefacts, I'm attaching a video but I'm not sure you can really see the flickering but you can see the Chromium tool bar I've also seen strange things with the kicker menu but I'm not sure if that's related or not, it's like it pauses before displaying the final frame unless you move the cursor I'll try and film that too -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488454] Ghosting with Chromium window
https://bugs.kde.org/show_bug.cgi?id=488454 --- Comment #1 from Mike Lothian --- https://photos.app.goo.gl/TxfRFoMJYtH4o6Ew8 as the 14MB video was too big -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488454] Ghosting with Chromium window
https://bugs.kde.org/show_bug.cgi?id=488454 --- Comment #3 from Mike Lothian --- Here's my graphics info: name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: AMD (0x1002) Device: AMD Radeon Graphics (radeonsi, renoir, ACO, DRM 3.57, 6.10.0-rc2-tip+) (0x1638) Version: 24.2.0 Accelerated: yes Video memory: 512MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 Memory info (GL_ATI_meminfo): VBO free memory - total: 107 MB, largest block: 107 MB VBO free aux. memory - total: 30944 MB, largest block: 30944 MB Texture free memory - total: 107 MB, largest block: 107 MB Texture free aux. memory - total: 30944 MB, largest block: 30944 MB Renderbuffer free memory - total: 107 MB, largest block: 107 MB Renderbuffer free aux. memory - total: 30944 MB, largest block: 30944 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 512 MB Total available memory: 32353 MB Currently available dedicated video memory: 107 MB OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon Graphics (radeonsi, renoir, ACO, DRM 3.57, 6.10.0-rc2-tip+) OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.2.0-devel (git-8a4e530f9d) OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.2.0-devel (git-8a4e530f9d) OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.2.0-devel (git-8a4e530f9d) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #9 from Mike --- Yeah, please do. I see in the log where the crash happened and that code has changed, though I'm not really sure if that's the cause. Either way, I am unable to reproduce the crash on 6.0.5, 6.1 or master. Fedora 40 KDE VM is hosed too so I'll have a look in a few days. Meantime, any way you can test with 6.1 with Fedora? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 Mike changed: What|Removed |Added Version Fixed In||6.2 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/print-manager/-/commit/9 ||0f3daa4fb814bbc9222b6b68d6e ||e3e896da94ae --- Comment #7 from Mike --- Git commit 90f3daa4fb814bbc9222b6b68d6ee3e896da94ae by Mike Noe. Committed on 11/06/2024 at 19:42. Pushed by noee into branch 'master'. kcm/[core,qml]: Cleanup Manual Config/Remote printer search qml: Add contextual help for the manual config options. For printer host search, don't populate list with "local" printers. Also, handle CUPS results and errors for remote printer search. core: Don't emit remotePrintersLoaded if there is a CUPS error FIXED-IN: 6.2 M +1-2src/kcm/printermanager.cpp M +20 -13 src/kcm/ui/components/ManualUri.qml https://invent.kde.org/plasma/print-manager/-/commit/90f3daa4fb814bbc9222b6b68d6ee3e896da94ae -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488274] Printer kcm doesn't display printer name
https://bugs.kde.org/show_bug.cgi?id=488274 --- Comment #5 from Mike --- Okay, I think I see what you mean now, didn't quite understand earlier. It appears that apps with printer dialogs (either standardized or not) are using the printer name (queue_name) in the list of displayed printers. Many appear to also display the description either in the list or once the printer is selected. But some don't show the description at all. Kind of two issues here: 1. Apps with custom printer dialogs could be updated to show printer description in some way. 2. We can add a tooltip or a label of some sort to the main print manager view to show the queue name. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488274] Printer kcm doesn't display printer name
https://bugs.kde.org/show_bug.cgi?id=488274 --- Comment #3 from Mike --- It was a UX decision made when moving to Plasma6 that the printer name (queue name) would be a secondary item going forward and the Description would be the forward-facing display for the printer, because this is something the user can customize. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #3 from Mike --- FYI, there are a few UI/UX changes coming in 6.1 regarding the buttons you mention, but yeah, it is not totally clear about the address, so we'll add some help text and a message regarding searching results, etc. to help with the UX. Regarding system-config-printer, yes it provides an alternative GUI, but printer manager only uses the driver services convenience features (Dbus), which allow for grouping physical devices and recommending "best" drivers when configuring a printer. What is strange, however, is that you are not forced to authenticate when you choose "Add Printer". Are you running as root or some other elevated user? This could also explain crashes in System Settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #1 from Mike --- When you select Add Printer, are you prompted to authenticate? Also, do you have the package system-config-printer installed? Can you post the output from the command: `lpinfo -v` (You may have to elevate privileges) Note: The search button on "Manual Config" asks CUPS for printers at the host address. If you know the printer address, you just type it in and choose "Continue". If the address is just a scheme, CUPS returns local printers by default, which we should probably ignore as it is bit confusing. As far as the crashing, this is something unusual. You can turn on debugging for the printer manager in KDebugSettings. Search "print" and enable Full Debug for kcm and libkcups. You can than watch the log in a terminal with `journalctl --user -f` to help narrow down what is crashing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 --- Comment #53 from Mike Lothian --- Is it worth raising a bug with libinput -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487631] Calendar pressing Next skips 3 months
https://bugs.kde.org/show_bug.cgi?id=487631 --- Comment #2 from Mike Lothian --- I don't have it enabled, no -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487631] New: Calander pressing Next skips 3 months
https://bugs.kde.org/show_bug.cgi?id=487631 Bug ID: 487631 Summary: Calander pressing Next skips 3 months Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: m...@fireburn.co.uk Target Milestone: 1.0 When I press the next button instead of moving to the next month, it skips three, you can manually select one of the skipped months, but pressing Next or previous still skips 3 months from the new date Qt 6.7.1 Frameworks from Git main Plasma from Git main -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 --- Comment #7 from Mike Lothian --- Scrolling is very slow, taking 30 seconds or so to go down the page, and using quite a lot of CPU too, is there a way to see what's causing it? This is probably all wayland related but it's the only app I've seen misbehave -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 337974] wish: support multiple instances of the same printer (with different defaults)
https://bugs.kde.org/show_bug.cgi?id=337974 Mike changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||noeero...@gmail.com --- Comment #3 from Mike --- This is possible with current Print Manager, it just requires that you set up a printer again, changing the queue name each time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344398] printing config asks for root authorization twice
https://bugs.kde.org/show_bug.cgi?id=344398 Mike changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486167] Install of Epson ET-8550 network printer won't complete - Printer not discovered on network
https://bugs.kde.org/show_bug.cgi?id=486167 --- Comment #5 from Mike --- (In reply to wal9 from comment #4) > (In reply to Mike from comment #3) > > Can you remove the printer and try again, this time choose the "Driverless" > > option when displayed? > > I could not remove printer in system settings. > > If you cannot remove the printer from System Settings, you can try from the > > CUPS web GUI, `localhost:631`. > > From CUPS I removed the printer, then installed one 8550 using IPP > > Everywhere, installed another using driverless. > EPSON_ET-8550-CC (Idle, Accepting Jobs, Shared) > Description: EPSON ET-8550-CC > Location: Local Printer > Driver: EPSON ET-8550 Series, driverless, 2.0.0 (color, 2-sided > printing) > Connection: > dnssd://EPSON%20ET-8550%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4- > a45f-64c6d2579453 > Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=one-sided > Printed color page from CUPS and can view the print que from the system > settings. From system settings I still cannot remove any printers, just So, when click the configure button for the printer, you should be asked to authenticate, then you'll be at the printer settings page where there is a "Remove" option at the top. When you click that Remove option, nothing happens? > pause and resume. When I print a page and choose a printer, all previously > installed printers, even removed ones are available to choose. This is going to be specific to the application you print from and might actually be that CUPS is "remembering" deleted printers and returning them as options for the apps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485771] Desktop icons disappear after icon update (including the trash icon)
https://bugs.kde.org/show_bug.cgi?id=485771 Mike Koss changed: What|Removed |Added CC||michaelrk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409741] Print resolution is not saved in printer properties
https://bugs.kde.org/show_bug.cgi?id=409741 Mike changed: What|Removed |Added Version Fixed In||6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486067] Keyboard brightness no longer showing up
https://bugs.kde.org/show_bug.cgi?id=486067 --- Comment #3 from Mike Lothian --- If I restart sddm everything then works fine, is this some sort of race issue during first boot? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486391] QMplay2 crashes when using Vaapi on Wayland
https://bugs.kde.org/show_bug.cgi?id=486391 Mike Lothian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Mike Lothian --- It does indeed, feel free to add my: Tested-by: Mike Lothian -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486391] QMplay2 crashes when using Vaapi on Wayland
https://bugs.kde.org/show_bug.cgi?id=486391 --- Comment #3 from Mike Lothian --- Created attachment 169082 --> https://bugs.kde.org/attachment.cgi?id=169082=edit WAYLAND_DEBUG=1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486391] QMplay2 crashes when using Vaapi on Wayland
https://bugs.kde.org/show_bug.cgi?id=486391
--- Comment #2 from Mike Lothian ---
I have a feeling its related to the vulkan-{header,loader,etc etc} being
updated to 1.3.280
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 486391] QMplay2 crashes when using Vaapi on Wayland
https://bugs.kde.org/show_bug.cgi?id=486391 Mike Lothian changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/mesa/mesa/-/issues/1109 ||7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486391] New: QMplay2 crashes when using Vaapi on Wayland
https://bugs.kde.org/show_bug.cgi?id=486391 Bug ID: 486391 Summary: QMplay2 crashes when using Vaapi on Wayland Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m...@fireburn.co.uk Target Milestone: --- This is using Plasma 6.1 git, KF6 git, Mesa git and QMplay2 from git QMPlay2 libva info: VA-API version 1.21.0 libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_21 libva info: va_openDriver() returns 0 VA-API :: Initialized device: renderD129 wp_linux_drm_syncobj_surface_v1@107: error 4: explicit sync is used, but no acquire point is set [01 May 2024 11:04:45.448] The Wayland connection experienced a fatal error: Protocol error This appears to be triggered by the landing of https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28874 The error message about the no acquire point I think is from the much older https://invent.kde.org/plasma/kwin/-/merge_requests/4693 I'm raising a bug with the Mesa folk too, but I'm not 100% sure if this is a Mesa, Kwin or QMplay2 bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485811] The Trash disappears from the desktop after being emptied and until plasmashell restart
https://bugs.kde.org/show_bug.cgi?id=485811 --- Comment #7 from Mike Koss --- I'm having this same problem on one computer, but on another computer with the same desktop setup, I can't reproduce the bug. Here is the system info for the PC where I am encountering the problem: 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.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: HP Product Name: OMEN by HP 40L Gaming Desktop GT21-0xxx And here's the info for the one without the problem: 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.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Dell Inc. Product Name: Dell G15 5535 System Version: 1.2.0 If anyone knows a way in which I might be able to probe both of these to figure out why this bug is coming up on the HP but not the Dell, let me know and I'll be happy to report any results. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485811] The Trash disappears from the desktop after being emptied and until plasmashell restart
https://bugs.kde.org/show_bug.cgi?id=485811 Mike Koss changed: What|Removed |Added CC||michaelrk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 mike cirioli changed: What|Removed |Added CC||cirioli.s...@gmail.com --- Comment #20 from mike cirioli --- chrome Version 124.0.6367.91 (Official Build) (64-bit) on kwin 6.04 - I can reproduce this issue by simply dragging any page element in chrome. The issue is present for both wayland and x11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 486312] New: When there is a color change in the text the two characters at the end overlap
https://bugs.kde.org/show_bug.cgi?id=486312 Bug ID: 486312 Summary: When there is a color change in the text the two characters at the end overlap Classification: Applications Product: konsole Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mike.johns...@q.com Target Milestone: --- Created attachment 169011 --> https://bugs.kde.org/attachment.cgi?id=169011=edit A partial screen shot showing the window title and the bug SUMMARY When there is a color change in the text the two characters at the end overlap STEPS TO REPRODUCE 1. start a konsole window running bash 2. execute the following command: ps -ef |egrep $USER 3. OBSERVED RESULT the 'e' in mike overlaps the following character EXPECTED RESULT the spacing after the 'e' is the same as other characters SOFTWARE/OS VERSIONS Linux - Fedora 40 ADDITIONAL INFORMATION I noticed this using VNC. I tried on a straight terminal and got the same result -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 --- Comment #5 from Mike Lothian --- I spoke too soon, if you scoll those two files then close kdiff3 you get the following segfault: Process 560661 stopped * thread #1, name = 'kdiff3', stop reason = signal SIGSEGV: address not mapped to object (fault address: 0x88) frame #0: 0x74606190 libQt6WaylandClient.so.6`QtWaylandClient::QWaylandShmBackingStore::resize(QSize const&) + 848 libQt6WaylandClient.so.6`QtWaylandClient::QWaylandShmBackingStore::resize: -> 0x74606190 <+848>: cmpb $0x0, 0x88(%rcx) 0x74606197 <+855>: je 0x746061f0 ; <+944> 0x74606199 <+857>: cmpq $0x0, 0x80(%rcx) 0x746061a1 <+865>: je 0x746061f0 ; <+944> (lldb) bt * thread #1, name = 'kdiff3', stop reason = signal SIGSEGV: address not mapped to object (fault address: 0x88) * frame #0: 0x74606190 libQt6WaylandClient.so.6`QtWaylandClient::QWaylandShmBackingStore::resize(QSize const&) + 848 frame #1: 0x74605ce2 libQt6WaylandClient.so.6`QtWaylandClient::QWaylandShmBackingStore::beginPaint(QRegion const&) + 82 frame #2: 0x76790361 libQt6Gui.so.6`QBackingStore::beginPaint(QRegion const&) + 433 frame #3: 0x776e4ee2 libQt6Widgets.so.6`QWidgetRepaintManager::paintAndFlush() + 4514 frame #4: 0x776c90bc libQt6Widgets.so.6`QWidgetRepaintManager::sync() + 284 frame #5: 0x776be70f libQt6Widgets.so.6`QWidget::event(QEvent*) + 2671 frame #6: 0x77546412 libQt6Widgets.so.6`QMainWindow::event(QEvent*) + 962 frame #7: 0x77ecdde2 libKF6XmlGui.so.6`KMainWindow::event(QEvent*) + 4530 frame #8: 0x77f0f4fb libKF6XmlGui.so.6`KXmlGuiWindow::event(QEvent*) + 43 frame #9: 0x7769061e libQt6Widgets.so.6`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 302 frame #10: 0x776920ae libQt6Widgets.so.6`QApplication::notify(QObject*, QEvent*) + 494 frame #11: 0x76133f57 libQt6Core.so.6`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 183 frame #12: 0x776e2b07 libQt6Widgets.so.6`QWidgetRepaintManager::sendUpdateRequest(QWidget*, QWidgetRepaintManager::UpdateTime) + 743 frame #13: 0x777373b7 libQt6Widgets.so.6`void QWidgetRepaintManager::markDirty(QRect const&, QWidget*, QWidgetRepaintManager::UpdateTime, QWidgetRepaintManager::BufferState) + 1447 frame #14: 0x776de31b libQt6Widgets.so.6`QWidget::repaint() + 187 frame #15: 0x55672e4b kdiff3`DiffTextWindowFrame::setFirstLine(this=0x5615b3f0, firstLine=) at difftextwindow.cpp:2036:21 frame #16: 0x760dda8f libQt6Core.so.6`___lldb_unnamed_symbol13786 + 1279 frame #17: 0x55609593 kdiff3`DiffTextWindow::firstLineChanged(this=, _t1=LineRef @ 0x7fffc24c) at moc_difftextwindow.cpp:431:5 frame #18: 0x55674606 kdiff3`DiffTextWindow::setFirstLine(this=0x5615dba0, firstLine=LineRef @ rbp) at difftextwindow.cpp:503:12 frame #19: 0x760dda8f libQt6Core.so.6`___lldb_unnamed_symbol13786 + 1279 frame #20: 0x775e838f libQt6Widgets.so.6`QAbstractSlider::setValue(int) + 319 frame #21: 0x7762537c libQt6Widgets.so.6`___lldb_unnamed_symbol22374 + 380 frame #22: 0x7758bc18 libQt6Widgets.so.6`QScrollBar::wheelEvent(QWheelEvent*) + 136 frame #23: 0x776be5d4 libQt6Widgets.so.6`QWidget::event(QEvent*) + 2356 frame #24: 0x7758bb58 libQt6Widgets.so.6`QScrollBar::event(QEvent*) + 504 frame #25: 0x7769061e libQt6Widgets.so.6`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 302 frame #26: 0x776920ae libQt6Widgets.so.6`QApplication::notify(QObject*, QEvent*) + 494 frame #27: 0x76133f57 libQt6Core.so.6`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 183 frame #28: 0x776be5d4 libQt6Widgets.so.6`QWidget::event(QEvent*) + 2356 frame #29: 0x7769061e libQt6Widgets.so.6`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 302 frame #30: 0x77693488 libQt6Widgets.so.6`QApplication::notify(QObject*, QEvent*) + 5576 frame #31: 0x76133f57 libQt6Core.so.6`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 183 frame #32: 0x776e95b1 libQt6Widgets.so.6`___lldb_unnamed_symbol23787 + 929 frame #33: 0x776e6c82 libQt6Widgets.so.6`___lldb_unnamed_symbol23778 + 338 frame #34: 0x7769061e libQt6Widgets.so.6`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 302 frame #35: 0x776920ae libQt6Widgets.so.6`QApplication::notify(QObject*, QEvent*) + 494 frame #36: 0x76133f57 libQt6Core.so.6`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 183 frame #37: 0x7671675d libQt6Gui.so.6`QGuiApplicationPrivate::processWheelEvent(QWindowSystemInterfacePrivate::WheelEvent*) + 541 frame #38: 0x76778f1a libQt6Gui.so.6`Q
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 Mike Lothian changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Mike Lothian --- I've just retested master, it's all looking good now thanks That's everything now migrated to Qt6 and working on my system :D Thanks again -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486292] New: Screen switches off when gaming with a joypad
https://bugs.kde.org/show_bug.cgi?id=486292 Bug ID: 486292 Summary: Screen switches off when gaming with a joypad Classification: Plasma Product: Powerdevil Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@fireburn.co.uk CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- The default idle settings for screen dimming and switching off kick in when gaming using a joypad (usb connected Switch controller) on steam This is a regression from X11 Plasma5 but I'm not sure if this is an issue with Wayland only, 6.0 or plasma 6.1 git Should steam/wine be doing something to inhibit this? Should powerdevil be ignoring the timeouts when running a full screen app? Or should powerdevil be monitoring the other input devices for button presses as well as keyboard and mouse? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486167] Install of Epson ET-8550 network printer won't complete - Printer not discovered on network
https://bugs.kde.org/show_bug.cgi?id=486167 --- Comment #3 from Mike --- Can you remove the printer and try again, this time choose the "Driverless" option when displayed? If you cannot remove the printer from System Settings, you can try from the CUPS web GUI, `localhost:631`. I have seen cases where the files in /etc/cups/ssl had to be removed and the cups service restarted before the printer would leave the "Paused" state. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486167] Install of Epson ET-8550 network printer won't complete - Printer not discovered on network
https://bugs.kde.org/show_bug.cgi?id=486167 --- Comment #1 from Mike --- How is the printer connected? Wireless or USB? Do you have entries in `/etc/cups/ssl`? Can you run `lpinfo -v` and paste the output here? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 459058] Fails to create printer without feedback for incorrect URI
https://bugs.kde.org/show_bug.cgi?id=459058 Mike changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/print-manager/-/commit/4 ||4cb896226a0b74aacef2868c4e0 ||1f8b208ab94d Version Fixed In|6.0.0 |6.1 --- Comment #2 from Mike --- Git commit 44cb896226a0b74aacef2868c4e01f8b208ab94d by Mike Noe. Committed on 25/04/2024 at 20:13. Pushed by noee into branch 'master'. kcm/qml: Add LPD device setup component This device support is brought forward from the legacy add-printer app. Related: bug 450154, bug 403189 FIXED-IN: 6.1 M +3-1src/kcm/ui/FindPrinter.qml A +95 -0src/kcm/ui/components/Lpd.qml [License: GPL(v2.0+)] https://invent.kde.org/plasma/print-manager/-/commit/44cb896226a0b74aacef2868c4e01f8b208ab94d -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 450154] LPD printer discovered but address/queue fields are empty
https://bugs.kde.org/show_bug.cgi?id=450154 Mike changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.1 Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/print-manager/-/commit/4 ||4cb896226a0b74aacef2868c4e0 ||1f8b208ab94d --- Comment #3 from Mike --- Git commit 44cb896226a0b74aacef2868c4e01f8b208ab94d by Mike Noe. Committed on 25/04/2024 at 20:13. Pushed by noee into branch 'master'. kcm/qml: Add LPD device setup component This device support is brought forward from the legacy add-printer app. Related: bug 459058, bug 403189 FIXED-IN: 6.1 M +3-1src/kcm/ui/FindPrinter.qml A +95 -0src/kcm/ui/components/Lpd.qml [License: GPL(v2.0+)] https://invent.kde.org/plasma/print-manager/-/commit/44cb896226a0b74aacef2868c4e01f8b208ab94d -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 403189] Print queue not added to the connection
https://bugs.kde.org/show_bug.cgi?id=403189 Mike changed: What|Removed |Added Version Fixed In|6.0.0 |6.1 Status|NEEDSINFO |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/print-manager/-/commit/4 ||4cb896226a0b74aacef2868c4e0 ||1f8b208ab94d --- Comment #2 from Mike --- Git commit 44cb896226a0b74aacef2868c4e01f8b208ab94d by Mike Noe. Committed on 25/04/2024 at 20:13. Pushed by noee into branch 'master'. kcm/qml: Add LPD device setup component This device support is brought forward from the legacy add-printer app. Related: bug 450154, bug 459058 FIXED-IN: 6.1 M +3-1src/kcm/ui/FindPrinter.qml A +95 -0src/kcm/ui/components/Lpd.qml [License: GPL(v2.0+)] https://invent.kde.org/plasma/print-manager/-/commit/44cb896226a0b74aacef2868c4e01f8b208ab94d -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486067] Keyboard brightness no longer showing up
https://bugs.kde.org/show_bug.cgi?id=486067 --- Comment #2 from Mike Lothian --- I'm still able to use https://github.com/wroberts/rogauracore to control the brightness and colours etc -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486067] Keyboard brightness no longer showing up
https://bugs.kde.org/show_bug.cgi?id=486067 --- Comment #1 from Mike Lothian --- Created attachment 168864 --> https://bugs.kde.org/attachment.cgi?id=168864=edit Full journalctl -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486067] New: Keyboard brightness no longer showing up
https://bugs.kde.org/show_bug.cgi?id=486067
Bug ID: 486067
Summary: Keyboard brightness no longer showing up
Classification: Plasma
Product: Powerdevil
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: m...@fireburn.co.uk
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
Target Milestone: ---
Using Qt 6.7.0, KF6 from git along with Plasma6 from Git, this certainly used
to work
journalctl -b | grep -i "bright\|keyboard"
Apr 24 12:31:12 axion.fireburn.co.uk kernel: atkbd serio0: Failed to deactivate
keyboard on isa0060/serio0
Apr 24 12:31:12 axion.fireburn.co.uk kernel: asus 0003:0B05:1866.0002:
input,hiddev0,hidraw1: USB HID v1.10 Keyboard [ASUSTek Computer Inc. N-KEY
Device] on usb-:08:00.3-3/input0
Apr 24 12:31:12 axion.fireburn.co.uk kernel: atkbd serio0: Failed to enable
keyboard on isa0060/serio0
Apr 24 12:31:12 axion.fireburn.co.uk kernel: input: AT Translated Set 2
keyboard as /devices/platform/i8042/serio0/input/input4
Apr 24 12:31:12 axion.fireburn.co.uk systemd[1]: Starting Load/Save Screen
Backlight Brightness of backlight:amdgpu_bl1...
Apr 24 12:31:12 axion.fireburn.co.uk systemd[1]: Starting Load/Save Screen
Backlight Brightness of leds:asus::kbd_backlight...
Apr 24 12:31:12 axion.fireburn.co.uk systemd[1]: Finished Load/Save Screen
Backlight Brightness of backlight:amdgpu_bl1.
Apr 24 12:31:12 axion.fireburn.co.uk systemd[1]: Finished Load/Save Screen
Backlight Brightness of leds:asus::kbd_backlight.
Apr 24 12:31:12 axion.fireburn.co.uk systemd-logind[436]: Watching system
buttons on /dev/input/event10 (Asus Keyboard)
Apr 24 12:31:12 axion.fireburn.co.uk systemd-logind[436]: Watching system
buttons on /dev/input/event13 (AT Translated Set 2 keyboard)
Apr 24 12:31:15 axion.fireburn.co.uk kwin_wayland_wrapper[660]: The XKEYBOARD
keymap compiler (xkbcomp) reports:
Apr 24 12:31:18 axion.fireburn.co.uk plasmashell[724]: error getting max
keyboard brightness via dbus
QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path
'/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'")
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/PopupDialog.qml:21:18:
QML ScrollView: ScrollView only supports Flickable types as its contentItem
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]: QQmlExpression:
Expression
file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:26:5
depends on non-NOTIFYable properties:
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]:
KeyboardColorControl::supported
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]: QQmlExpression:
Expression
file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:77:21
depends on non-NOTIFYable properties:
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]:
KeyboardColorControl::enabled
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]: QQmlExpression:
Expression
file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:64:21
depends on non-NOTIFYable properties:
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]:
KeyboardColorControl::enabled
Apr 24 12:31:24 axion.fireburn.co.uk plasmashell[724]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:67:21:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 467685] cupsDoAuthentication() immediately fails without prompting a password
https://bugs.kde.org/show_bug.cgi?id=467685 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Version Fixed In||6.0.0 Resolution|--- |FIXED --- Comment #2 from Mike --- We believe this is fixed in the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335287] cnijnet URI for Canon printer is not accepted as valid
https://bugs.kde.org/show_bug.cgi?id=335287 Mike changed: What|Removed |Added Resolution|--- |FIXED CC||noeero...@gmail.com Status|REPORTED|NEEDSINFO Version Fixed In||6.0.0 --- Comment #6 from Mike --- We believe this is fixed in the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 403189] Print queue not added to the connection
https://bugs.kde.org/show_bug.cgi?id=403189 Mike changed: What|Removed |Added Version Fixed In||6.0.0 Resolution|--- |FIXED Status|REPORTED|NEEDSINFO CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe this is fixed in the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 459058] Fails to create printer without feedback for incorrect URI
https://bugs.kde.org/show_bug.cgi?id=459058 Mike changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.0.0 CC||noeero...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from Mike --- We believe this issue to be resolved with Plasma6, can you try again with Plasma6 and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 434856] Cannot save custom settings in printer dialog
https://bugs.kde.org/show_bug.cgi?id=434856 Mike changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #8 from Mike --- Ok, yes, that appears to be an issue with Okular then. After Print Manager configures a printer, it's then up to the apps to decided if/how to use the settings and if those settings would be saved for the app across sessions. I would suggest opening an bug report on Okular to continue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486012] New: SDDM Themes brake my login screen
https://bugs.kde.org/show_bug.cgi?id=486012 Bug ID: 486012 Summary: SDDM Themes brake my login screen Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: bailey.m2...@proton.me CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- Every time I use any SDDM theme I get a black screen with a cursor and can't login or anything else. I then have to boot into a live usb like fedora or POP go into the /user/share/sddm/themes and delete whatever theme I tried to use so that it goes back to the default theme. this happens regardless of the theme I use. The themes that come with the KDE plasma 6 install. it happens on my laptop and my desktop computers both running Arch. STEPS TO REPRODUCE 1. add any theme 2. 3. OBSERVED RESULT everything works fine until the next boot and I just get a black screen with a _ in the top right corner and the cursor and it just stays stuck like that. I am using an HP Pavilion Desktop TP01-2xxx, Kernel: 6.8.7-arch1-1 DE: Plasma 6.0.4 Theme: Breeze-Dark [GTK2], Breeze [GTK3] Icons: Gruvbox [GTK2/3] CPU: AMD Ryzen 5 5600G with Radeon Graphics (12) @ 3.900GHz GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series Memory: 4859MiB / 11292MiB The laptop is a Lenovo Thinkpad T560 with an NVIDIA GPU and the hardened kernel everything else is the same -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 --- Comment #2 from Mike Lothian --- I've attached the two files which trigger the problem for me -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 --- Comment #1 from Mike Lothian --- Created attachment 168831 --> https://bugs.kde.org/attachment.cgi?id=168831=edit Second file -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] New: kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 Bug ID: 485999 Summary: kdiff3 segaborts when comparing two files Classification: Applications Product: kdiff3 Version: 1.11.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: m...@fireburn.co.uk Target Milestone: --- Created attachment 168830 --> https://bugs.kde.org/attachment.cgi?id=168830=edit First file Qt 6.7.0 KF6 from Git kdiff3 from Git (lldb) run Process 1098029 launched: '/usr/bin/kdiff3' (x86_64) org.kde.kdiff3: Loading A: "/home/fireburn/dmesg.axion" org.kde.kdiff3: Loading B: "/home/fireburn/dmesg.txt" org.kde.kdiff3: Diff: A <-> B org.kde.kdiff3: Linediff: A <-> B org.kde.kdiff3: Enter: calcDiff3LineListUsingAB org.kde.kdiff3: Leave: calcDiff3LineListUsingAB terminate called after throwing an instance of 'std::system_error' what(): converted signed value too small: negative overflow error Process 1098029 stopped * thread #1, name = 'kdiff3', stop reason = signal SIGABRT frame #0: 0x762bf86c libc.so.6`___lldb_unnamed_symbol3697 + 268 libc.so.6`___lldb_unnamed_symbol3697: -> 0x762bf86c <+268>: movl %eax, %ebx 0x762bf86e <+270>: negl %ebx 0x762bf870 <+272>: cmpl $0xf000, %eax ; imm = 0xF000 0x762bf875 <+277>: movl $0x0, %eax (lldb) bt * thread #1, name = 'kdiff3', stop reason = signal SIGABRT * frame #0: 0x762bf86c libc.so.6`___lldb_unnamed_symbol3697 + 268 frame #1: 0x7626be66 libc.so.6`raise + 22 frame #2: 0x762538b7 libc.so.6`abort + 215 frame #3: 0x758a4c7b libstdc++.so.6`___lldb_unnamed_symbol7333 + 98 frame #4: 0x758b8eec libstdc++.so.6`___lldb_unnamed_symbol7788 + 12 frame #5: 0x758b8f57 libstdc++.so.6`std::terminate() + 23 frame #6: 0x5560fabf kdiff3`__clang_call_terminate + 15 frame #7: 0x5567559f kdiff3`getBestFirstLine(LineRef, int, LineRef, int) [inlined] LineRef::operator=(this=, lineIn=) at LineRef.h:51:21 frame #8: 0x55675581 kdiff3`getBestFirstLine(line=LineRef @ scalar, nofLines=1559, firstLine=LineRef @ scalar, visibleLines=14) at difftextwindow.cpp:0 frame #9: 0x556756ab kdiff3`DiffTextWindow::setFastSelectorRange(this=0x5615a6c0, line1=, nofLines=) at difftextwindow.cpp:595:32 frame #10: 0x760dda8f libQt6Core.so.6`___lldb_unnamed_symbol13786 + 1279 frame #11: 0x5560ccd1 kdiff3`MergeResultWindow::setFastSelectorRange(this=, _t1=LineRef @ 0x7fffc46c, _t2=1559) at moc_mergeresultwindow.cpp:574:5 frame #12: 0x556ad3f3 kdiff3`MergeResultWindow::setFastSelector(this=0x55c804c0, i=std::__cxx11::list >::iterator @ scalar) at mergeresultwindow.cpp:788:12 frame #13: 0x556a63a2 kdiff3`MergeResultWindow::merge(bool, e_SrcSelector, bool, bool) [inlined] MergeResultWindow::go(this=0x55c804c0, eDir=eUp, eEndPoint=eEnd) at mergeresultwindow.cpp:548:5 frame #14: 0x556a6364 kdiff3`MergeResultWindow::merge(bool, e_SrcSelector, bool, bool) [inlined] MergeResultWindow::slotGoTop(this=0x55c804c0) at mergeresultwindow.cpp:658:5 frame #15: 0x556a6364 kdiff3`MergeResultWindow::merge(this=0x55c804c0, bAutoSolve=, defaultSelector=, bConflictsOnly=false, bWhiteSpaceOnly=) at mergeresultwindow.cpp:397:5 frame #16: 0x556a5d8c kdiff3`MergeResultWindow::init(this=0x55c804c0, pLineDataA=, sizeA=LineRef @ 0x7fffc5c8, pLineDataB=, sizeB=LineRef @ 0x7fffc5cc, pLineDataC=, sizeC=LineRef @ 0x7fffc620, pDiff3LineList=0x5597a388, pTotalDiffStatus=0x55a9ac50, bAutoSolve=true) at mergeresultwindow.cpp:132:5 frame #17: 0x5565f1b0 kdiff3`KDiff3App::mainInit(this=0x55979fe0, pTotalDiffStatus=, inFlags=) at pdiff.cpp:377:27 frame #18: 0x5563193c kdiff3`KDiff3App::completeInit(QString const&, QString const&, QString const&) [inlined] KDiff3App::doFileCompare(this=0x55979fe0) at kdiff3.cpp:595:5 frame #19: 0x55631908 kdiff3`KDiff3App::completeInit(this=0x55979fe0, fn1=, fn2=, fn3=) at kdiff3.cpp:646:13 frame #20: 0x5561d3e0 kdiff3`KDiff3Shell::KDiff3Shell(this=0x55a07850, fn1=0x7fffcb68, fn2=0x7fffcb50, fn3=0x7fffcb38) at kdiff3_shell.cpp:39:15 frame #21: 0x5561c629 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [inlined] main::$_0::operator()(this=0x55982d30) const at main.cpp:192:21 frame #22: 0x5561c587 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [inlined] QtPrivate::FunctorCall, QtPrivate::List<>, void,
[kdiff3] [Bug 484988] SEGABRT in Kdiff3 with Qt 6.6+ when opening files
https://bugs.kde.org/show_bug.cgi?id=484988 --- Comment #8 from Mike Lothian --- I'm still seeing a failure on master: (lldb) run Process 1098029 launched: '/usr/bin/kdiff3' (x86_64) org.kde.kdiff3: Loading A: "/home/fireburn/dmesg.axion" org.kde.kdiff3: Loading B: "/home/fireburn/dmesg.txt" org.kde.kdiff3: Diff: A <-> B org.kde.kdiff3: Linediff: A <-> B org.kde.kdiff3: Enter: calcDiff3LineListUsingAB org.kde.kdiff3: Leave: calcDiff3LineListUsingAB terminate called after throwing an instance of 'std::system_error' what(): converted signed value too small: negative overflow error Process 1098029 stopped * thread #1, name = 'kdiff3', stop reason = signal SIGABRT frame #0: 0x762bf86c libc.so.6`___lldb_unnamed_symbol3697 + 268 libc.so.6`___lldb_unnamed_symbol3697: -> 0x762bf86c <+268>: movl %eax, %ebx 0x762bf86e <+270>: negl %ebx 0x762bf870 <+272>: cmpl $0xf000, %eax ; imm = 0xF000 0x762bf875 <+277>: movl $0x0, %eax (lldb) bt * thread #1, name = 'kdiff3', stop reason = signal SIGABRT * frame #0: 0x762bf86c libc.so.6`___lldb_unnamed_symbol3697 + 268 frame #1: 0x7626be66 libc.so.6`raise + 22 frame #2: 0x762538b7 libc.so.6`abort + 215 frame #3: 0x758a4c7b libstdc++.so.6`___lldb_unnamed_symbol7333 + 98 frame #4: 0x758b8eec libstdc++.so.6`___lldb_unnamed_symbol7788 + 12 frame #5: 0x758b8f57 libstdc++.so.6`std::terminate() + 23 frame #6: 0x5560fabf kdiff3`__clang_call_terminate + 15 frame #7: 0x5567559f kdiff3`getBestFirstLine(LineRef, int, LineRef, int) [inlined] LineRef::operator=(this=, lineIn=) at LineRef.h:51:21 frame #8: 0x55675581 kdiff3`getBestFirstLine(line=LineRef @ scalar, nofLines=1559, firstLine=LineRef @ scalar, visibleLines=14) at difftextwindow.cpp:0 frame #9: 0x556756ab kdiff3`DiffTextWindow::setFastSelectorRange(this=0x5615a6c0, line1=, nofLines=) at difftextwindow.cpp:595:32 frame #10: 0x760dda8f libQt6Core.so.6`___lldb_unnamed_symbol13786 + 1279 frame #11: 0x5560ccd1 kdiff3`MergeResultWindow::setFastSelectorRange(this=, _t1=LineRef @ 0x7fffc46c, _t2=1559) at moc_mergeresultwindow.cpp:574:5 frame #12: 0x556ad3f3 kdiff3`MergeResultWindow::setFastSelector(this=0x55c804c0, i=std::__cxx11::list >::iterator @ scalar) at mergeresultwindow.cpp:788:12 frame #13: 0x556a63a2 kdiff3`MergeResultWindow::merge(bool, e_SrcSelector, bool, bool) [inlined] MergeResultWindow::go(this=0x55c804c0, eDir=eUp, eEndPoint=eEnd) at mergeresultwindow.cpp:548:5 frame #14: 0x556a6364 kdiff3`MergeResultWindow::merge(bool, e_SrcSelector, bool, bool) [inlined] MergeResultWindow::slotGoTop(this=0x55c804c0) at mergeresultwindow.cpp:658:5 frame #15: 0x556a6364 kdiff3`MergeResultWindow::merge(this=0x55c804c0, bAutoSolve=, defaultSelector=, bConflictsOnly=false, bWhiteSpaceOnly=) at mergeresultwindow.cpp:397:5 frame #16: 0x556a5d8c kdiff3`MergeResultWindow::init(this=0x55c804c0, pLineDataA=, sizeA=LineRef @ 0x7fffc5c8, pLineDataB=, sizeB=LineRef @ 0x7fffc5cc, pLineDataC=, sizeC=LineRef @ 0x7fffc620, pDiff3LineList=0x5597a388, pTotalDiffStatus=0x55a9ac50, bAutoSolve=true) at mergeresultwindow.cpp:132:5 frame #17: 0x5565f1b0 kdiff3`KDiff3App::mainInit(this=0x55979fe0, pTotalDiffStatus=, inFlags=) at pdiff.cpp:377:27 frame #18: 0x5563193c kdiff3`KDiff3App::completeInit(QString const&, QString const&, QString const&) [inlined] KDiff3App::doFileCompare(this=0x55979fe0) at kdiff3.cpp:595:5 frame #19: 0x55631908 kdiff3`KDiff3App::completeInit(this=0x55979fe0, fn1=, fn2=, fn3=) at kdiff3.cpp:646:13 frame #20: 0x5561d3e0 kdiff3`KDiff3Shell::KDiff3Shell(this=0x55a07850, fn1=0x7fffcb68, fn2=0x7fffcb50, fn3=0x7fffcb38) at kdiff3_shell.cpp:39:15 frame #21: 0x5561c629 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [inlined] main::$_0::operator()(this=0x55982d30) const at main.cpp:192:21 frame #22: 0x5561c587 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [inlined] QtPrivate::FunctorCall, QtPrivate::List<>, void, main::$_0>::call(f=0x55982d30, arg=) at qobjectdefs_impl.h:137:13 frame #23: 0x5561c587 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [inlined] void QtPrivate::FunctorCallable::call, void>(f=0x55982d30, (null)=, arg=) at qobjectdefs_impl.h:345:13 frame #24: 0x5561c587 kdiff3`QtPrivate::QCallableObject, void>::impl(which=, this
[print-manager] [Bug 427307] Strange behavior of module 'Printers--System Settings'
https://bugs.kde.org/show_bug.cgi?id=427307 Mike changed: What|Removed |Added Version Fixed In||6.0.0 Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480219] Unable to autodiscover printer: hp deskjet plus 4100
https://bugs.kde.org/show_bug.cgi?id=480219 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from Mike --- If you cannot get Plasma6 to discover this printer, you can make sure that the following packages are installed: - hplip - hplip-hpijs and try again. If that doesn't work, you get the ip address of the printer on your network and use the Print Manager manual config and enter the address: ipp://printer-address:631/ipp/print, select a driver for the printer and see if that works. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335956] Adding discovered network printer dialog shows URI in dropdown instead of human-friendly name
https://bugs.kde.org/show_bug.cgi?id=335956 Mike changed: What|Removed |Added Version Fixed In||6.0.0 Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #6 from Mike --- We believe that Plasma6 resolves this issue. Can you try with Plasma6 and report back? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 327660] Printer installation seems OK but systems hangs waiting for printer to be "free"
https://bugs.kde.org/show_bug.cgi?id=327660 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Version Fixed In||6.0.0 Resolution|--- |FIXED --- Comment #4 from Mike --- We believe this to be fixed in Plasma6. Please try again and report back. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449743] Changing Media Type doesn't work
https://bugs.kde.org/show_bug.cgi?id=449743 Mike changed: What|Removed |Added Version Fixed In||6.0.0 Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Mike --- (In reply to Mike from comment #1) > We believe these issues to be solved in later Plasma5 and Plasma6 just > released. Please try again if you can and report back. Thx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478495] Printer manager doesn't show IP address of printer
https://bugs.kde.org/show_bug.cgi?id=478495 Mike changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 CC||noeero...@gmail.com Assignee|plasma-b...@kde.org |noeero...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 469132] KDE Plasma Printer for HP Colorjet refused to set duplex printer, while Gnome GTK prints duplex w/o
https://bugs.kde.org/show_bug.cgi?id=469132 Mike changed: What|Removed |Added Assignee|dantt...@gmail.com |okular-de...@kde.org Component|applet |general CC||noeero...@gmail.com Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Product|print-manager |okular --- Comment #1 from Mike --- I think this is a problem in okular, not printer setup. Please check with the latest versions in Plasma6. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484988] SEGABRT in Kdiff3 with Qt 6.6+ when opening files
https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #5 from Mike Lothian ---
I got a backtrace from kdiff3
git mergetool
Merging:
kcms/mouse/CMakeLists.txt
Normal merge conflict for 'kcms/mouse/CMakeLists.txt':
{local}: modified file
{remote}: modified file
(lldb) target create "kdiff3"
Current executable set to '/usr/bin/kdiff3' (x86_64).
(lldb) settings set -- target.run-args "--auto" "--L1"
"kcms/mouse/CMakeLists.txt (Base)" "--L2" "kcms/mouse/CMakeLists.txt (Local)"
"--L3" "kcms/mouse/CMakeLists.txt (Remote)" "-o" "kcms/mouse/CMakeLists.txt"
"./kcms/mouse/CMakeLists_BASE_1741404.txt"
"./kcms/mouse/CMakeLists_LOCAL_1741404.txt"
"./kcms/mouse/CMakeLists_REMOTE_1741404.txt"
(lldb) run
org.kde.kdiff3: Diff: A <-> B
org.kde.kdiff3: Linediff: A <-> B
org.kde.kdiff3: Enter: calcDiff3LineListUsingAB
org.kde.kdiff3: Leave: calcDiff3LineListUsingAB
Process 1741515 launched: '/usr/bin/kdiff3' (x86_64)
Process 1741515 stopped and restarted: thread 2 received signal: SIGCHLD
Process 1741515 stopped
* thread #1, name = 'kdiff3', stop reason = signal SIGSEGV: address not mapped
to object (fault address: 0x8)
frame #0: 0x761095b4 libQt6Core.so.6`QIODevice::isOpen() const + 4
libQt6Core.so.6`QIODevice::isOpen:
-> 0x761095b4 <+4>: movq 0x8(%rdi), %rax
0x761095b8 <+8>: cmpl $0x0, 0x180(%rax)
0x761095bf <+15>: setne %al
0x761095c2 <+18>: retq
(lldb) bt
* thread #1, name = 'kdiff3', stop reason = signal SIGSEGV: address not mapped
to object (fault address: 0x8)
* frame #0: 0x761095b4 libQt6Core.so.6`QIODevice::isOpen() const + 4
frame #1: 0x556c2d6c
kdiff3`FileAccess::writeFile(this=0x7fffc520,
pSrcBuffer=0x75d0aa80, length=0) at fileaccess.cpp:865:9
frame #2: 0x556b66d5
kdiff3`MergeResultWindow::saveDocument(this=0x56130830,
fileName=, encoding=, eLineEndStyle=) at
mergeresultwindow.cpp:2689:25
frame #3: 0x55631369
kdiff3`KDiff3App::completeInit(this=0x559aa0d0, fn1=,
fn2=, fn3=) at kdiff3.cpp:688:54
frame #4: 0x5561c3c0
kdiff3`KDiff3Shell::KDiff3Shell(this=0x5599d540,
fn1=0x7fffc948, fn2=0x7fffc930, fn3=0x7fffc918) at
kdiff3_shell.cpp:39:15
frame #5: 0x5561b609 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) [inlined] main::$_0::operator()(this=0x55b2f600) const
at main.cpp:196:21
frame #6: 0x5561b567 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) [inlined] QtPrivate::FunctorCall,
QtPrivate::List<>, void, main::$_0>::call(f=0x55b2f600,
arg=) at qobjectdefs_impl.h:137:13
frame #7: 0x5561b567 kdiff3`QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) [inlined] void
QtPrivate::FunctorCallable::call,
void>(f=0x55b2f600, (null)=, arg=) at
qobjectdefs_impl.h:345:13
frame #8: 0x5561b567 kdiff3`QtPrivate::QCallableObject, void>::impl(which=, this_=0x55b2f5f0,
r=, a=, ret=) at
qobjectdefs_impl.h:555:21
frame #9: 0x76084f6c libQt6Core.so.6`QObject::event(QEvent*) + 636
frame #10: 0x76714d47
libQt6Gui.so.6`QGuiApplication::event(QEvent*) + 711
frame #11: 0x7768d9a8
libQt6Widgets.so.6`QApplication::event(QEvent*) + 520
frame #12: 0x7769061e
libQt6Widgets.so.6`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 302
frame #13: 0x776920ae
libQt6Widgets.so.6`QApplication::notify(QObject*, QEvent*) + 494
frame #14: 0x76133f57
libQt6Core.so.6`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 183
frame #15: 0x7613572e
libQt6Core.so.6`QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
QThreadData*) + 526
frame #16: 0x75ecb2d7 libQt6Core.so.6`___lldb_unnamed_symbol10036 +
23
frame #17: 0x74f49602 libglib-2.0.so.0`___lldb_unnamed_symbol2489 +
482
frame #18: 0x74fb6588 libglib-2.0.so.0`___lldb_unnamed_symbol2747 +
600
frame #19: 0x74f488ac libglib-2.0.so.0`g_main_context_iteration +
44
frame #20: 0x75eb61c4
libQt6Core.so.6`QEventDispatcherGlib::processEvents(QFlags)
+ 100
frame #21: 0x76134ba6
libQt6Core.so.6`QEventLoop::exec(QFlags) + 550
frame #22: 0x761347e8 libQt6Core.so.6`QCoreApplication::exec() +
136
frame #23: 0x55619a69 kdiff3`main(argc=13, argv=) at
main.cpp:199:21
frame #24: 0x76256f46 libc.so.6`___lldb_unnamed_symbol3280 + 134
frame #25: 0x76256ff9 libc.so.6`__libc_start_main + 137
frame #26: 0x556073c5 kdiff3`_start + 37
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 395383] Settings are not saved in printer global settings
https://bugs.kde.org/show_bug.cgi?id=395383 Mike changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |FIXED --- Comment #8 from Mike --- (In reply to Mike from comment #7) > We believe these issues to be solved in later Plasma5 and Plasma6 just > released. Please try again if you can and report back. Thx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484609] Unable to see all information in KDE System Settings while using fractional scaling. No scroll bar function to allow access when it exceeds display window.
https://bugs.kde.org/show_bug.cgi?id=484609 Mike changed: What|Removed |Added Version Fixed In||6.0.4 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409741] Print resolution is not saved in printer properties
https://bugs.kde.org/show_bug.cgi?id=409741 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Mike --- (In reply to Mike from comment #1) > Can you try this in Plasma6? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484609] Unable to see all information in KDE System Settings while using fractional scaling. No scroll bar function to allow access when it exceeds display window.
https://bugs.kde.org/show_bug.cgi?id=484609 Mike changed: What|Removed |Added Status|ASSIGNED|CONFIRMED Component|general |kcm_printer_manager -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484609] Unable to see all information in KDE System Settings while using fractional scaling. No scroll bar function to allow access when it exceeds display window.
https://bugs.kde.org/show_bug.cgi?id=484609 Mike changed: What|Removed |Added Ever confirmed|0 |1 Assignee|plasma-b...@kde.org |noeero...@gmail.com CC||noeero...@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 314801] Adding dns-sd printer as remote instead of local
https://bugs.kde.org/show_bug.cgi?id=314801 Mike changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||noeero...@gmail.com Resolution|--- |INTENTIONAL --- Comment #9 from Mike --- Fixed in Plasma6 and otherwise, going forward with IPP Everywhere and CUPSv3, PPDs will be supported only as legacy. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 414658] KDE does no longer print except text files with Kate since Plasma 5.17.3
https://bugs.kde.org/show_bug.cgi?id=414658 Mike changed: What|Removed |Added CC||noeero...@gmail.com Version Fixed In||6.0.4 Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #10 from Mike --- Can you test this again with Plasma6 and report back? We believe this is fixed in Plasma6. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 424942] Cannot add printer via GUI
https://bugs.kde.org/show_bug.cgi?id=424942 Mike changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||6.0.4 --- Comment #9 from Mike --- I think all Plasma5 versions will have this problem, in some scenarios. Should be fixed in Plasma6. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 438897] I can't add my Epson xp-342 printer on arch
https://bugs.kde.org/show_bug.cgi?id=438897 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Mike --- (In reply to Mike from comment #1) > We believe this is fixed in a later version of Plasma5 and the recently > released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 340133] Error message in case of missing system-config-printer should be more clear / a warning instead
https://bugs.kde.org/show_bug.cgi?id=340133 Mike changed: What|Removed |Added Version Fixed In||6.0.4 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||noeero...@gmail.com --- Comment #2 from Mike --- Fix with MR https://invent.kde.org/plasma/print-manager/-/commit/ab7c5e31debfd179209a85ae442000f3a2b0a57f -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 341780] when adding printer error "Failed to group devices"
https://bugs.kde.org/show_bug.cgi?id=341780 Mike changed: What|Removed |Added Status|REOPENED|RESOLVED CC||noeero...@gmail.com Resolution|--- |FIXED Version Fixed In||6.0.4 --- Comment #8 from Mike --- Fix with MR https://invent.kde.org/plasma/print-manager/-/commit/ab7c5e31debfd179209a85ae442000f3a2b0a57f -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485089] Dolphin crashes on start
https://bugs.kde.org/show_bug.cgi?id=485089 Mike Lothian changed: What|Removed |Added CC||m...@fireburn.co.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394480] Installing HP printers that require proprietary plugin
https://bugs.kde.org/show_bug.cgi?id=394480 Mike changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Mike --- Then, yeah, let's close this -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 459708] Having to press Shift to see secondary functionality unnecessarily hides it
https://bugs.kde.org/show_bug.cgi?id=459708 --- Comment #4 from Mike H --- First of all, I'm not certain why my bug was closed as a duplicate of a much less detailed bug one year later. I believe that one should have been closed instead. Second, the resolution to promote square root still does not address the UX issue of not understanding what 'shift' implies. The shift button should have some special text styling or button background color that is different from every other button. Perhaps Italicized and a different color for example. At the very least a different color. Then, every single button that is affected by the shift should have superscript text, perhaps italicized, But definitely the same color as chosen for the shift button, that displays what the secondary feature of the button is. I linked a descriptive picture of a TI-36 calculator previously in this bug that denotes how its second function key has the different color and the text on the buttons denotes both features, one being the italicized feature. It does however appear that Casio calls their second function button the shift key like K-Calc. I have never owned a Casio calculator and only today decided to start looking at Texas instruments's competition. https://upload.wikimedia.org/wikipedia/commons/f/fc/Casio_algebra_fx_2.0_plus.PNG shows how Casio has a shift button that is orange and superscript text above every shiftable function button that shows its secondary function. Instead of hiding behind an opaque layer change for the button, or entire text replacement, I don't know how it is done, both values somehow need to be displayed on the button. Concurrently. While it does currently mimic casio's naming, I also still think that the naming of shift is ambiguous even with UX contextual clue improvements, so renaming to 'second function' '2nd func' something like that, might also be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406336] Kde-print -manger doesn't accept user/password
https://bugs.kde.org/show_bug.cgi?id=406336 Mike changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #2 from Mike --- (In reply to Mike from comment #1) > We believe this has been fixed in the lastest Plasma5 and the recently > released Plasma6. Can you try again and report back? Thx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446417] network printer will not be added despite being discoverable.
https://bugs.kde.org/show_bug.cgi?id=446417 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Mike --- (In reply to Mike from comment #1) > We believe these issues to be solved in later Plasma5 and Plasma6 just > released. Please try again if you can and report back. Thx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468065] Print Color Mode option changes do not persist.
https://bugs.kde.org/show_bug.cgi?id=468065 Mike changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #2 from Mike --- (In reply to Mike from comment #1) > Can you try this in Plasma6? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 470522] Automatically recognized printers of the CUPS server disappear again.
https://bugs.kde.org/show_bug.cgi?id=470522 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Mike --- (In reply to Mike from comment #1) > We believe this is fixed in a later version of Plasma5 and the recently > released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 427307] Strange behavior of module 'Printers--System Settings'
https://bugs.kde.org/show_bug.cgi?id=427307 Mike changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #2 from Mike --- (In reply to Mike from comment #1) > We believe this is fixed in a later version of Plasma5 and the recently > released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 349556] Dialog asking for username/password pops up regularly without obvious reason and effect
https://bugs.kde.org/show_bug.cgi?id=349556 Mike changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #4 from Mike --- (In reply to Mike from comment #3) > We believe this is fixed in a later version of Plasma5 and the recently > released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 434856] Cannot save custom settings in printer dialog
https://bugs.kde.org/show_bug.cgi?id=434856 Mike changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Mike --- (In reply to Mike from comment #1) > We believe this is fixed in a later version of Plasma5 and the recently > released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 320326] Mark system-config-printer as an optional runtime dependency in CMake
https://bugs.kde.org/show_bug.cgi?id=320326 Mike changed: What|Removed |Added Version Fixed In|6.0.0 |6.0.4 -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 320326] Mark system-config-printer as an optional runtime dependency in CMake
https://bugs.kde.org/show_bug.cgi?id=320326 Mike changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||6.0.0 CC||noeero...@gmail.com Resolution|--- |FIXED --- Comment #10 from Mike --- While not made a runtime dependency, we have updated the readme and the Plasma6 (6.0.4) version will handle the scenario when s-c-p fails or is not installed. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 470522] Automatically recognized printers of the CUPS server disappear again.
https://bugs.kde.org/show_bug.cgi?id=470522 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe this is fixed in a later version of Plasma5 and the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 438897] I can't add my Epson xp-342 printer on arch
https://bugs.kde.org/show_bug.cgi?id=438897 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe this is fixed in a later version of Plasma5 and the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 452900] "Printer Options" page is not adaptive
https://bugs.kde.org/show_bug.cgi?id=452900 Mike changed: What|Removed |Added CC||noeero...@gmail.com Resolution|--- |FIXED Version Fixed In||6.0.0 Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 434856] Cannot save custom settings in printer dialog
https://bugs.kde.org/show_bug.cgi?id=434856 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe this is fixed in a later version of Plasma5 and the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 427307] Strange behavior of module 'Printers--System Settings'
https://bugs.kde.org/show_bug.cgi?id=427307 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe this is fixed in a later version of Plasma5 and the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 349556] Dialog asking for username/password pops up regularly without obvious reason and effect
https://bugs.kde.org/show_bug.cgi?id=349556 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #3 from Mike --- We believe this is fixed in a later version of Plasma5 and the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 424942] Cannot add printer via GUI
https://bugs.kde.org/show_bug.cgi?id=424942 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #6 from Mike --- We believe this is fixed in a later version of Plasma5 and the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 453703] Plasmashell keeps crashing while CUPS is running
https://bugs.kde.org/show_bug.cgi?id=453703 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #7 from Mike --- We believe this is fixed in a later version of Plasma5 and the recently released Plasma6. Can you retest this and report back? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406336] Kde-print -manger doesn't accept user/password
https://bugs.kde.org/show_bug.cgi?id=406336 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe this has been fixed in the lastest Plasma5 and the recently released Plasma6. Can you try again and report back? Thx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407672] printer changes not saved when clicking "Apply"
https://bugs.kde.org/show_bug.cgi?id=407672 Mike changed: What|Removed |Added Version Fixed In||5.x-6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449743] Changing Media Type doesn't work
https://bugs.kde.org/show_bug.cgi?id=449743 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe these issues to be solved in later Plasma5 and Plasma6 just released. Please try again if you can and report back. Thx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446417] network printer will not be added despite being discoverable.
https://bugs.kde.org/show_bug.cgi?id=446417 Mike changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #1 from Mike --- We believe these issues to be solved in later Plasma5 and Plasma6 just released. Please try again if you can and report back. Thx -- You are receiving this mail because: You are watching all bug changes.
