[systemsettings] [Bug 415364] Implement feature to disable touchpad when mouse is plugged in when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 Cameron Smith changed: What|Removed |Added CC||cameronsmith...@gmail.com --- Comment #26 from Cameron Smith --- Bump for this issue. It seems that libinput has supported disable device on external mouse plugin for a while now (https://wayland.freedesktop.org/libinput/doc/latest/configuration.html#send-events-mode), so it would be awesome to see it implemented in KDE 6! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488295] Graphic artifact visible behind floating panel in plasmashell
https://bugs.kde.org/show_bug.cgi?id=488295 Cameron Smith changed: What|Removed |Added CC||cameronsmith...@gmail.com --- Comment #8 from Cameron Smith --- Can reproduce this bug on my ThinkPad T480s laptop, wayland session, Arch Linux. Curiously, this is NOT present on my AMD/Nvidia main pc, only my intel/intel laptop. Not sure what's going on there, but for interest's/debugging's sake my pc without the issue is: Plasma: 6.0.5 KDE Frameworks: 6.3.0 Qt: 6.7.1 Kernel: 6.9.4 CPU: AMD Ryzen 5 GPU: Nvidia Quadro RTX 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482222] When using a touchscreen, using multi-finger touch gestures causes the desktop to misbehave
https://bugs.kde.org/show_bug.cgi?id=48 --- Comment #11 from Cameron Smith --- Bug Condition Update: (Full discussion at https://discuss.kde.org/t/3-finger-gestures-on-touchscreen-bug/15956/2) I have noticed this bug is only present when attempting to use 3-finger gestures on a bare desktop background, and is NOT present when a gesture is started on top of an application window or even the task manager (tricky to pull off on a small touchscreen :D)! Can confirm the bug is still 100% present when used on any blank desktop wallpaper areas, and no changes as far as I can see. This is simply me noticing the bug is only present in more specific circumstances than I was previously aware. Can anyone else reproduce this behaviour? It would be awesome to narrow the bug constraints down a little further! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393781] wallpaper cannot span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 Cameron Smith changed: What|Removed |Added Platform|Ubuntu |Arch Linux CC||cameronsmith...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482222] When using a touchscreen, using multi-finger touch gestures causes the desktop to misbehave
https://bugs.kde.org/show_bug.cgi?id=48 Cameron Smith changed: What|Removed |Added CC||cameronsmith...@gmail.com --- Comment #7 from Cameron Smith --- I was just about to report this bug (see my entry in KDE Discuss, https://discuss.kde.org/t/3-finger-gestures-on-touchscreen-bug/15956), but found that this is exactly the bug I'm experiencing to a T. SUMMARY I’ve found a bug that I can easily replicate on my laptop that flummoxes me: When using 3-finger swipes to switch desktops or open overview on my touchscreen, edit mode is entered (initially) and subsequent attempts to use 3-fingered gestures cause a selection rectangle to be opened on my desktop (wherever the mouse is positioned). Note that this is NOT an issue with touchpad gestures (flawless), just my touchscreen. STEPS TO REPRODUCE 1. Use 3-finger gestures on the touchscreen → forcibly enter edit mode. 2. Exit edit mode, try to use gestures again → edit mode this time is not entered, but a selection rectangle is permanently shown on the desktop which follows the mouse (even without pressing either mouse button). - Notably, once this selection rectangle is present, 3-finger gestures on the touchscreen are flawless. 3. The only way to remove this selection rectangle is to either log out or to use the selection rectangle to actually select something on the desktop. This does remove it, however… 4. Once the selection rectangle is removed, using 3-finger gestures on the touchscreen begins step #1 all over again. OBSERVED RESULT - 3-finger gestures on touchscreen cause edit mode and a persistent selection box that follows the mouse. EXPECTED RESULT - (Only) switch virtual desktops, open overview/grid view. SOFTWARE/OS VERSIONS - Wayland session - Plasma: 6.0.4 - KDE framework: 6.2.0 - Qt version: 6.7.0 - OS: Arch Linux, 6.9.1 kernel HARDWARE - T480s ThinkPad - CPU: Intel i5-8th gen - GPU: Intel Mesa UHD 620 - RAM: 16GB ADDITIONAL INFORMATION At least one other user has been able to replicate this problem (https://discuss.kde.org/t/3-finger-gestures-on-touchscreen-bug/15956). Notably both instances are using Lenovo touchscreen laptops. I am additionally using 150% fractional scaling, but I suspect this is irrelevant. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 485670] New: Konqueror crashes upon clicking a bookmark folder from the bookmark toolbar
https://bugs.kde.org/show_bug.cgi?id=485670 Bug ID: 485670 Summary: Konqueror crashes upon clicking a bookmark folder from the bookmark toolbar Classification: Applications Product: konqueror Version: 24.02.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bookmarks Assignee: konq-b...@kde.org Reporter: cmrnt...@gmail.com Target Milestone: --- SUMMARY Just as the title says, konqueror crashes with a segfault when a bookmark folder listed in the toolbar is clicked. STEPS TO REPRODUCE 1. Open konqueror 2. Create a bookmark folder and add some bookmarks to it 3. Go to Settings-->Toolbars shown and turn enable bookmark toolbar to be shown 4. Click a bookmark folder from the bookmark toolbar. Steps 2 and 3 can be skipped if a bookmark folder already exists and the toolbar is shown. Bookmark folders and their contents can be accessed without a crash from the application Bookmark menu. OBSERVED RESULT Konqueror segfaults. EXPECTED RESULT Bookmark folder opens to show bookmarks contained within it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.0.3 (available in About System) KDE Plasma Version: 6.03 KDE Frameworks Version: 6.1 Qt Version: 6.7 ADDITIONAL INFORMATION KCrash: Application 'konqueror' crashing... crashRecursionCounter = 2 Segmentation fault (core dumped) Core available upon request. -- 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 Cameron Smith changed: What|Removed |Added CC||cameronsmith...@gmail.com --- Comment #29 from Cameron Smith --- I made a post a few days back regarding this bug (https://discuss.kde.org/t/kde-6-upgrade-broke-fonts-in-wayland/13254) and am delighted to report that setting the "QT_SCALE_FACTOR_ROUNDING_POLICY" environment variable to "RoundPreferFloor" indeed seems to fix all issues I had. Hopefully this can be resolved in a release soon, as it seems (to me at least) to be a straightforward fix. I've got no idea what implications setting this variable might have on niche situations elsewhere in KDE, but so far all good on my end. Thanks Nate for the solution! My setup: Thinkpad T480s Arch linux KDE 6.0.3 Wayland session (ofc) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464395] Screen flashes between all white and what should be displayed after return from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=464395 --- Comment #8 from Cameron Tanner --- White screen flashing is reported by others, see https://wiki.archlinux.org/title/Laptop/HP#EliteBook_U82_family_(835_G9/845_G9/865_G9/845_G10). The recommendation to disable scatter-gather with the kernel boot parameter amdgpu.sg_display=0 addresses the issue for me on the most recent opensuse tumbleweed. Recommendation: Close, upstream bug https://gitlab.freedesktop.org/drm/amd/-/issues/2354#note_1829617. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464395] Screen flashes between all white and what should be displayed after return from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=464395 --- Comment #7 from Cameron Tanner --- kwin environment variables influences this bug. Setting KWIN_COMPOSE=O2 or X makes the bug go away. The combination of KWIN_COMPOSE=O2ES and KWIN_OPENGL_INTERFACE=EGL makes the bug active. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464395] Screen flashes between all white and what should be displayed after return from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=464395 --- Comment #6 from Cameron Tanner --- Correction from above post: * The bug does NOT happen in lx-qt. The laptop primary and external monitor work fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464395] Screen flashes between all white and what should be displayed after return from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=464395 --- Comment #4 from Cameron Tanner --- May be related to https://gitlab.freedesktop.org/drm/amd/-/issues/2354. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464395] Screen flashes between all white and what should be displayed after return from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=464395 --- Comment #3 from Cameron Tanner --- The bug at least seems related to a driver. The bug can be made to go away by turning off glamor 2D acceleration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464395] Screen flashes between all white and what should be displayed after return from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=464395 --- Comment #2 from Cameron Tanner --- (In reply to Nate Graham from comment #1) > I would suspect a graphics driver bug, but I'm moving this to KWin to see if > the KWin devs have any ideas. There is some new information to report on symptoms. * Flickering between White and the regular display contents is also provoked by connecting the laptop to an external monitor using the HDMI connector. The primary display goes blank regardless of the the lid being open or closed. Plasma only detects the external monitor once the hdmi cable is connected. There are no options to extend or replicate the display contents between the laptop and external monitor. I am wondering if the white screen flickering is repetitive probing of the display in an attempt to identify. * The bug does happen in lx-qt. The laptop primary and external monitor work fine. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 464395] New: Screen flashes between all white and what should be displayed after return from Screen Energy Saving
https://bugs.kde.org/show_bug.cgi?id=464395 Bug ID: 464395 Summary: Screen flashes between all white and what should be displayed after return from Screen Energy Saving Classification: Plasma Product: kscreenlocker Version: 5.26.5 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: cmrnt...@gmail.com Target Milestone: --- SUMMARY *** Screen flashes between all white and the actual display contents after returning from "Screen Energy Saving". *** STEPS TO REPRODUCE 1. Turn on "Screen Energy Saving" within the Power Management tab of the plasma Desktop Configure app. This is the default. 2. Let the computer sit idle until Screen Energy Saving is activated. 3. Start using the computer again. OBSERVED RESULT Screen flashes between all white and what it should display. Pointer movements seem to correlate with the flashing. Leaving the mouse motionless can give either an all white or normal result. Flashing begins again if the pointer is moved. Repeating the process will eventually lead to a screen that is all white all the time. EXPECTED RESULT Computer returns to normal display after return from Screen Energy Saving mode. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuSE TW, Kernel 6.1.4 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101 Qt Version: 5.15 ADDITIONAL INFORMATION This appears to be hardware specific. The computer that displays the bug is an HP Elitebook 845 G9 with an AMD Ryzen 7 processor and integrated gpu. The bug is not present on an older HP Elitebook 820 G2 with an Intel Broadwell Core i7. There are no errors in dmesg. I do not see any errors in journalctl. The bug is not activated by opening and closing the laptop lid which also turns off the display. The computer never crashes when the bug is provoked. The bug does not seem to be provoked by kscreenlocker. It is possible to switch to a VT console. A normal screen is recovered by killing X and allowing it to restart. It is not clear that this is a plasma/kde bug. The computer has been "live" for days now and MS windows runs fine and seemingly rule out a hardware malfunction. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463051] Krita crash or close when I make a new canva for animation
https://bugs.kde.org/show_bug.cgi?id=463051 --- Comment #8 from Cameron --- Oh well, I already change the Krita settings on the Krita preferences and the program doesn't crash anymore when I create the new canva. But thank you for the help! El 15/12/2022 15:02, "Ralek Kolemios" escribió: https://bugs.kde.org/show_bug.cgi?id=463051 Ralek Kolemios changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Ralek Kolemios --- Alrighty, I'm not seeing anything so far that would cause a crash under normal circumstances, and I can't seem to reproduce it on my end. In Krita, can you go to Help > Show Krita Log and then click 'save to file' and upload that? Did turning off 'Canvas Graphics Acceleration' in Settings > Configure > Display help? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463051] Krita crash or close when I make a new canva for animation
https://bugs.kde.org/show_bug.cgi?id=463051 --- Comment #3 from Cameron --- Created attachment 154591 --> https://bugs.kde.org/attachment.cgi?id=154591=edit image.png --- Comment #4 from Cameron --- Created attachment 154592 --> https://bugs.kde.org/attachment.cgi?id=154592=edit image.png --- Comment #5 from Cameron --- Created attachment 154593 --> https://bugs.kde.org/attachment.cgi?id=154593=edit image.png -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463051] Krita crash or close when I make a new canva for animation
https://bugs.kde.org/show_bug.cgi?id=463051 --- Comment #2 from Cameron --- Well, the program looks like this before going to crash [image: image.png] And then I going to do the new Canva and I put the information [image: image.png] But when I click on "create", the button going to gray like this [image: image.png] And then the program closes [image: image.png] But I'll check the Krita preferences and change the settings to see if I can fix the problem! El mié, 14 dic 2022 a la(s) 18:01, Ralek Kolemios (bugzilla_nore...@kde.org) escribió: > https://bugs.kde.org/show_bug.cgi?id=463051 > > Ralek Kolemios changed: > >What|Removed |Added > > > CC||i...@ralek.art > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Ralek Kolemios --- > Hey there! Unfortunately to help we're going to need a bit more > information. > Some of the most useful stuff you can give would be a crash report, see > this > link for how to do that: > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports > > The next best thing would be to be as specific as possible. Can you > provide a > screen cap of the 'create new' screen before the crash? What sort of > hardware > does your laptop have on it? > > Personally this sounds like a GPU canvas acceleration problem. Can you go > into > your Krita settings and find "canvas acceleration" and set it to > 'software' and > see if the problem persists? > > Any more information you can provide will be helpful, thanks. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463051] New: Krita crash or close when I make a new canva for animation
https://bugs.kde.org/show_bug.cgi?id=463051 Bug ID: 463051 Summary: Krita crash or close when I make a new canva for animation Classification: Applications Product: krita Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: cameronmoon241...@gmail.com Target Milestone: --- 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 *** STEPS TO REPRODUCE 1. Open Krita 2. Click on new canva and put dimention information 3. Click on create OBSERVED RESULT The Krita program crash when I trying to do a new canva. EXPECTED RESULT I want to see the new Canva I created, but doesn't happend. SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I donwloaded the new version of Krita program (5.1.3) on my laptop, and when I tried to do a new canva for do an animation for Tik Tok, the program crashed after I put the dimentions information. I don't know why is happening, but I hope you guys can help me with this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 357868] Closing laptop lid doesn't result in suspend
https://bugs.kde.org/show_bug.cgi?id=357868 Cameron changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #7 from Cameron --- I believe this is the bug that was fixed many years ago. It was related to "null displays" in Qt. Qt was never supposed to return null displays during this era or something like that, but many more cases were being found. It has long since been resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450637] Wayland: Menus in LibreOffice are shown as decorated separate windows when LibreOffice window was not focussed
https://bugs.kde.org/show_bug.cgi?id=450637 Cameron changed: What|Removed |Added CC||cameron...@yagowap.com --- Comment #2 from Cameron --- Confirm behavior on openSUSE Tumbleweed running Wayland. Behavior of dialog windows is present in all LO applications, and even in settings menus. I think this may be the DocumentFoundation bug ID for this: 144585 https://bugs.documentfoundation.org/show_bug.cgi?id=144585 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 444832] New: Panel can auto show underneath yakuake, but will not auto hide
https://bugs.kde.org/show_bug.cgi?id=444832 Bug ID: 444832 Summary: Panel can auto show underneath yakuake, but will not auto hide Product: yakuake Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: k...@ccontour.com Target Milestone: --- SUMMARY The panel widget continues to stay visible when the mouse bumps the top of the screen while yakuake is open STEPS TO REPRODUCE 1. 100% width yakuake (probably optional) 2. Set up a panel at the top of the screen, and visibility set to auto hide 3. Open yakuake 4. Move mouse to top of screen, then back to the center of the screen 5. Close yakuake OBSERVED RESULT Panel is visible. Can quickly mouseover it to hide again EXPECTED RESULT Either of these would be valid - Panel should never have shown in the first place (yakuake is rendered above it) - Panel should have automatically hidden after mouse left (it was able to show after all) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The glow from the panel as the mouse approaches the top of the screen prior to showing IS visible OVER yakuake. Just not the panel. Unclear if this is a bug, but it's a related interaction -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 444797] Window trying to center between displays
https://bugs.kde.org/show_bug.cgi?id=444797 --- Comment #1 from Cameron --- Created attachment 143111 --> https://bugs.kde.org/attachment.cgi?id=143111=edit yakuake at 100% size / width, with content on 2 displays -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 444797] New: Window trying to center between displays
https://bugs.kde.org/show_bug.cgi?id=444797 Bug ID: 444797 Summary: Window trying to center between displays Product: yakuake Version: 21.08.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: k...@ccontour.com Target Milestone: --- Created attachment 143110 --> https://bugs.kde.org/attachment.cgi?id=143110=edit yakuake window centered between 2 displays, with display arrangement settings visible SUMMARY Yakuake is incorrectly centering the window when using in a multi display setup. I am using a laptop, with an external monitor. While the laptop screen is closed, everything works as expected. When height / width is set to 100%, the window will take up the correct monitor + position most of the time (using the global open keybind). It will frequently shift the open position to be partly on each display. When height / width is set to 70%, the yakuake will hug the left side of the right display (still not correctly centered), but does not cross between displays like 100% does. STEPS TO REPRODUCE No special steps. Just multi monitor + global activate button OBSERVED RESULT See attached screenshot EXPECTED RESULT The window should correctly center itself on the desired display the same way that happens in single displays. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436283] access violation in ZN22KisFrameDataSerializer23estimateFrameUniquenessERKNS_5FrameES2_d
https://bugs.kde.org/show_bug.cgi?id=436283 William Cameron changed: What|Removed |Added CC||gnomor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436283] New: access violation in ZN22KisFrameDataSerializer23estimateFrameUniquenessERKNS_5FrameES2_d
https://bugs.kde.org/show_bug.cgi?id=436283 Bug ID: 436283 Summary: access violation in ZN22KisFrameDataSerializer23estimateFrameUniquenessERK NS_5FrameES2_d Product: krita Version: 4.4.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: gnomor...@gmail.com Target Milestone: --- SUMMARY submitting on behalf of partner who experienced this issue, i found crashdumps in by localappdata for krita due to a nullptr access violation in memcmp called by ZN22KisFrameDataSerializer23estimateFrameUniquenessERKNS_5FrameES2_d (3320.1fe0): Access violation - code c005 (first/second chance not available) // shows comparison was a nullptr 7ffe`c349ce22 3a0411 cmp al,byte ptr [rcx+rdx] ds:`=?? stack: 0b `005f35e8 7ffe`43891942 msvcrt!memcmp+0x32 0c `005f35f0 7ffe`43898460 libkritaui!ZN22KisFrameDataSerializer23estimateFrameUniquenessERKNS_5FrameES2_d+0x182 0d `005f3690 7ffe`43898c15 libkritaui!ZN18KisFrameCacheStore9saveFrameEi12KisSharedPtrI19KisOpenGLUpdateInfoERK5QRect+0x8b0 0e `005f37a0 7ffe`4387d4ee libkritaui!ZN20KisFrameCacheSwapper9saveFrameEi12KisSharedPtrI19KisOpenGLUpdateInfoERK5QRect+0x25 0f `005f37e0 7ffe`4387fe7b libkritaui!ZN22KisAnimationFrameCache21addConvertedFrameDataE12KisSharedPtrI19KisOpenGLUpdateInfoEi+0x1ce 10 `005f38c0 7ffe`438a34ae libkritaui!ZN29KisAsyncAnimationRendererBaseD0Ev+0x4ab process dump attached. STEPS TO REPRODUCE reproduction is intermittent 1. create 50 odd unique frames 2. press play on the animation OBSERVED RESULT nullptr access violation in memcmp EXPECTED RESULT no exception, animation plays Krita Version: 4.4.3 Languages: en_US, en Hidpi: true Qt Version (compiled): 5.12.9 Version (loaded): 5.12.9 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19042 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (Intel(R) UHD Graphics Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true Hardware Information GPU Acceleration: auto Memory: 16201 Mb Number of Cores: 12 Swap Location: C:/Users/William/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/William/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: TRY_OPENGL Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Model: Refresh Rate: 240 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415662] Dismissing Pop-Up Notification Crashed Plasma
https://bugs.kde.org/show_bug.cgi?id=415662 Cameron changed: What|Removed |Added CC||cameron...@yagowap.com --- Comment #2 from Cameron --- (In reply to Nate Graham from comment #1) > Does this still happen to you in either Plasma 5.18 (the current LTS > version) or Plasma 5.21 (the latest released version)? Nate I had to re-look at this old bug to see! I have moved systems, but still use KDE Plasma with Signal flatpak, and have received one or two Segfaults, but none of them have resulted in either application failure or graphical freezes (I didn't look closely at what exactly was throwing the error), without the notification I would not have known anything went wrong. I'll see if I can replicate it and post to this bug-tracking ID next time it happens. The graphical bug as described here has not occurred since that I remember, and not at all in >5.19 versions of Plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433540] Wayland cursor hiding via setting NULL cursor surface is broken
https://bugs.kde.org/show_bug.cgi?id=433540 --- Comment #4 from Cameron Gutman --- Aha! I was staring at these logs and never noticed the missing serial. Thanks for your help. This is now fixed in SDL - https://github.com/libsdl-org/SDL/commit/8c5b7af2d2f317c42c5437aa4b4dc7c3f5a06057 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433540] Wayland cursor hiding via setting NULL cursor surface is broken
https://bugs.kde.org/show_bug.cgi?id=433540 --- Comment #1 from Cameron Gutman --- Created attachment 136115 --> https://bugs.kde.org/attachment.cgi?id=136115=edit WAYLAND_DEBUG=client log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433540] New: Wayland cursor hiding via setting NULL cursor surface is broken
https://bugs.kde.org/show_bug.cgi?id=433540 Bug ID: 433540 Summary: Wayland cursor hiding via setting NULL cursor surface is broken Product: kwin Version: 5.21.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: cameron.gut...@gmail.com Target Milestone: --- Created attachment 136114 --> https://bugs.kde.org/attachment.cgi?id=136114=edit Test code SUMMARY Wayland-based applications which try to hide the mouse cursor by calling wl_pointer_set_cursor() with a NULL surface do not result in the cursor being hidden with KWin. This cursor hiding behavior is explicitly documented in the Wayland protocol [0] and works properly on Mutter and Sway. [0]: https://github.com/wayland-project/wayland/blob/70f1c83fd9380bf40d904b2806c2af07e688e960/protocol/wayland.xml#L1886 STEPS TO REPRODUCE 1. Build the attached SDL2 sample code - On my Fedora and Krypton systems, the following works (assuming SDL2-devel is installed): gcc -I/usr/include/SDL2 -lSDL2 -o mouse_hide mouse_hide.c 2. Run the test code in a Wayland Plasma session OBSERVED RESULT The cursor is not hidden when it is over the test app's window. The KDE default cursor is displayed instead. EXPECTED RESULT The cursor should be hidden when it is over the test app's window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Krypton KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION SDL bug report: https://github.com/libsdl-org/SDL/issues/3576 See attached WAYLAND_DEBUG=client log. Particularly the lines where the cursor surface is set to NULL, such as what happens handling the wl_pointer enter event: [2845237.141] wl_pointer@15.enter(255, wl_surface@21, 3.00, 321.00) [2845237.278] -> wl_pointer@15.set_cursor(0, nil, 0, 0) Let me know if there is anything else I can do to help. If you believe SDL's behavior is somehow at fault here, I can work on patches to fix it. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 412194] New: Keystrokes are not conveyed to input field
https://bugs.kde.org/show_bug.cgi?id=412194 Bug ID: 412194 Summary: Keystrokes are not conveyed to input field Product: konqueror Version: 5.0.97 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: cmrnt...@gmail.com Target Milestone: --- SUMMARY Keystrokes are not conveyed into the entry fields of webpages. STEPS TO REPRODUCE 1. Open Konqueror (or Falkon) 2. Load a webpage like google.com or bugs.kde.org 3. Type in the search field or attempt to enter login name, respectively OBSERVED RESULT Keystrokes are not conveyed to the field. EXPECTED RESULT The field should become populated with the keystrokes. SOFTWARE/OS VERSION Operating System: openSUSE Tumbleweed 20190916 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 Kernel Version: 5.2.14-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz Memory: 31.1 GiB of RAM ADDITIONAL INFORMATION Falkon is also affected by this bug. The bug does not appear consistently. On some runs of Konqueror of Falkon, it does not manifest but in others it does. Closing the browser or tab and restarting or opening a new tab sometimes "fixes" the problem temporarily. Typing in a google.com search field when the bug is active will bring up google's search suggestions, but keystrokes do not show and the enter key cannot be pressed. Pasting text into the field works normally and allows the field to receive keyboard input. The computer is a laptop and is happens on both built-in and usb keyboards. Filed under Konqueror since this is where the bug is manifest. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 411026] New: Maintain Absolute Sidebar Size On Window Resize
https://bugs.kde.org/show_bug.cgi?id=411026 Bug ID: 411026 Summary: Maintain Absolute Sidebar Size On Window Resize Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: cameron.g.rodg...@gmail.com Target Milestone: --- When the Okular window is resized, the sidebar maintains its size relative to window size. IE, if I have deliberately changed the sidebar to 200px in width, and I make the window twice as wide, the sidebar will become 400px wide. This is an undesirable behavior, as the user is likely resizing the window to get a wider view of the rendered PDF contents, and they have already decided that the sidebar is as wide as needed for viewing, e.g., a table of contents. Instead, the size of the sidebar should be absolute, and not change when the window is resized. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411025] New: Remove Dimming Effect on Windows, Move Title Bars
https://bugs.kde.org/show_bug.cgi?id=411025 Bug ID: 411025 Summary: Remove Dimming Effect on Windows, Move Title Bars Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: cameron.g.rodg...@gmail.com Target Milestone: --- The dimming effect on windows in the Present Windows effect makes it harder to immediately recognize their contents, as they have less contrast with the dimmed background. This is compounded by the location of title bars (if they're enabled), right in the middle of the windows, obscuring their contents. The title bar location also makes the title bars harder to read too. Here are some screenshots of similar effects in GNOME, Windows 10, and MacOS: https://upload.wikimedia.org/wikipedia/en/c/c2/Shows_Overview_mode_%28%22Activities%22%29_in_GNOME_3.8.png https://images.techhive.com/images/article/2015/07/taskview-100598415-orig.png https://cdn.arstechnica.net/2011/07/04/lion/mission-control-big.png As you can see, the dimming (if present) is not applied to the windows, and the title bars are either to the bottom or top. This is better for readability. I think that at very least, an option to apply this setting in the effect would improve KDE's looks and usability. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410824] New: Pen barrel button + drag reverts back to selected tool with XP-Pen Artist 15.6
https://bugs.kde.org/show_bug.cgi?id=410824 Bug ID: 410824 Summary: Pen barrel button + drag reverts back to selected tool with XP-Pen Artist 15.6 Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: theban...@gmail.com Target Milestone: --- SUMMARY In previous drawing programs, I map the space bar to a button on the pen barrel, so that holding the button activates the move tool and I can then scroll by dragging on the screen, but I am having trouble making this work in Krita. STEPS TO REPRODUCE 1. Windows 10/Krita 4.2.5/XP-Pen Artist 15.6 2. Set either button on pen barrel to "space" 3. With any tool selected (most obvious with the brush tool), hold the pen barrel button down 4. Attempt to scroll by dragging pen across screen OBSERVED RESULT While holding the pen barrel button, the cursor turns into the move tool icon, as expected. However, upon dragging, the brush tool is activated again and it just draws on the screen. EXPECTED RESULT The canvas should scroll, as if the space bar was held down. SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 404878] Plasma browser extension causes black screen for gotomeeting screen sharing
https://bugs.kde.org/show_bug.cgi?id=404878 Cameron Seader changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from Cameron Seader --- (In reply to Cameron Seader from comment #7) > (In reply to Kai Uwe Broulik from comment #6) > > I just uploaded an update for p-b-i to Chrome store (version 1.5), can you > > try with that? I did some fixes to make media controls less breaking for > > websites. > > Yes. Will try right now. This update seems to fix it. I can now do screen sharing without issue when this extension is enabled. Thank You! -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 404878] Plasma browser extension causes black screen for gotomeeting screen sharing
https://bugs.kde.org/show_bug.cgi?id=404878 --- Comment #7 from Cameron Seader --- (In reply to Kai Uwe Broulik from comment #6) > I just uploaded an update for p-b-i to Chrome store (version 1.5), can you > try with that? I did some fixes to make media controls less breaking for > websites. Yes. Will try right now. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 404878] Plasma browser extension causes black screen for gotomeeting screen sharing
https://bugs.kde.org/show_bug.cgi?id=404878 --- Comment #5 from Cameron Seader --- (In reply to Kai Uwe Broulik from comment #4) > I just tried gotomeeting trial and while there is some general wonkiness of > screen share not workig when joining a meeting with screenshare already > running I cannot attribute it to this extension, I tried both the 1.4 on the > store as well as my local git master checkout, as well as without the > extension. > Screen sharing the entire screen works just fine in all three cases. Not sure what to tell ya. My experience is just the opposite. I suppose it could be another extension that it has a problem with. The Hunt continues. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 404878] Plasma browser extension causes black screen for gotomeeting screen sharing
https://bugs.kde.org/show_bug.cgi?id=404878
--- Comment #2 from Cameron Seader ---
(In reply to Kai Uwe Broulik from comment #1)
> Do you see any suspicious output on Developer Console (Ctrl+Shift+I)?
Here is the console message i get
--snip--
sessionEntry.js:1 2019-02-28T15:14:59.926Z [log] rtc-client
{message: "[DualStack] publish in Mcs mode."}
message: "[DualStack] publish in Mcs mode."
__proto__: Object
{rtcClientAttributes: {…}}
sessionEntry.js:1 2019-02-28T15:14:59.931Z [log] rtc-client
{message: "presenter_api_meta_data", data: {…}}
data:
hardwareConcurrency: 8
presenterAPIOptions:
browserInfo: {browserType: 2, version: 72}
byteByByteCompare: false
cacheDepth: 15
disableThrottling: false
frameStatsPercent: 5
numWorkers: 8
resizeTimeout: 100
statsCallback: ƒ (t)
statsPrecision: 2
statsPushInterval: 6
tileHeight: 128
tileWidth: 176
unicolorEnabled: true
useCache: true
__proto__: Object
__proto__: Object
message: "presenter_api_meta_data"
__proto__:
constructor: ƒ Object()
hasOwnProperty: ƒ hasOwnProperty()
isPrototypeOf: ƒ isPrototypeOf()
propertyIsEnumerable: ƒ propertyIsEnumerable()
toLocaleString: ƒ toLocaleString()
toString: ƒ toString()
valueOf: ƒ valueOf()
__defineGetter__: ƒ __defineGetter__()
__defineSetter__: ƒ __defineSetter__()
__lookupGetter__: ƒ __lookupGetter__()
__lookupSetter__: ƒ __lookupSetter__()
get __proto__: ƒ __proto__()
set __proto__: ƒ __proto__()
{rtcClientAttributes: {…}}
rtcClientAttributes:
ga_id_participant_mcs: "141"
__proto__: Object
__proto__: Object
sessionEntry.js:1 2019-02-28T15:14:59.937Z [log] started presenting
--snip--
There are no errors in the console when the sharing is started, but the screen
is black with the plasma extension enabled.
> Do you have "Enhanced Media Controls" enabled in extension settings?
If this is what you mean
chrome://flags/#enable-modern-media-controls
Mine is all defaults
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-browser-integration] [Bug 404878] New: Plasma browser extension causes black screen for gotomeeting screen sharing
https://bugs.kde.org/show_bug.cgi?id=404878 Bug ID: 404878 Summary: Plasma browser extension causes black screen for gotomeeting screen sharing Product: plasma-browser-integration Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: csea...@novell.com Target Milestone: --- I used Gotomeeting heavily and when I run a meeting from Chrome browser and want to share my screen I am unable to do so if this extension is enabled. If I disable the extension and then open the meeting in the browser then I am working again. STEPS TO REPRODUCE 1. Install Plasma Extension 2. Run a gotomeeting and share your screen, Everyone sees a black screen share image. 3. disable Plasma Extension, Everything working again with gotomeeting OBSERVED RESULT Black screen when screen sharing in gotomeeting EXPECTED RESULT Screen sharing of my entire screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed latest 20190225 (available in About System) KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 402542] Failed copy from mtp with large number of files and large amount of data
https://bugs.kde.org/show_bug.cgi?id=402542 --- Comment #1 from Cameron Tanner --- Not easy to reproduce. Worked the third and forth times. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 402542] New: Failed copy from mtp with large number of files and large amount of data
https://bugs.kde.org/show_bug.cgi?id=402542 Bug ID: 402542 Summary: Failed copy from mtp with large number of files and large amount of data Product: kio-extras Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: MTP Assignee: elvis.angelac...@kde.org Reporter: cmrnt...@gmail.com Target Milestone: --- Started dolphin, used mtp to enter folders on andoid cell phone, selected 602 files comprising 16.3 GB of data, mostly images, copied and then pasted into an empty folder on desktop. Due to the amount of data, the job took a long time. System became slow to respond so I decided to be patient and let the job finsish. While waiting, the screensaver started. Attempt to log in failed despite entering the correct password and screensaver crashed leaving only a mouse pointer. Crtl-Alt-F1 to log in as root, top showed high cpu usage 12+, but no job registered more than 20% of cpu. Eventually even the root terminal became unresponsive leaving power button reboot as the only option. STEPS TO REPRODUCE 1. Plug in android phone with USB-C connector 2. Start dolphin 3. Click phone icon in panel to left for mtp access to its files 4. Navigate to mtp:/V30S/Internal storage/DCIM/Camera/ 5. Select a large number of files 6. Copy files 7. Paste files into an empty folder on the desktop OBSERVED RESULT System slows progressively and eventually is unresponsive requiring a hard restart. EXPECTED RESULT Files copied successively to destination folder SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuSE (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53 Qt Version: 5.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 179245] groupwise IM does not hold the saved password.
https://bugs.kde.org/show_bug.cgi?id=179245 --- Comment #4 from Cameron Seader --- This bug is no longer relevant. Please Close. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 179246] Jabber/ Google Talk error after kde4 workspace crash
https://bugs.kde.org/show_bug.cgi?id=179246 --- Comment #8 from Cameron Seader --- Close as this is no longer relevant -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380246] Krita SegFaults and Crashes - Reported "There must be an inconsistency in the walkers happened!"
https://bugs.kde.org/show_bug.cgi?id=380246 Cameron Ibrahim <camibr...@gmail.com> changed: What|Removed |Added Version|3.1.3-rc|3.1.3 --- Comment #2 from Cameron Ibrahim <camibr...@gmail.com> --- (In reply to mvowada from comment #1) > Hi, Cameron, does it happen always in your case? > It seems I'm not able to reproduce this on Ubuntu with Krita 3.1.4 > appimage... No. It happened twice in one session, but has not happened since I filled the bug report. I cannot say for certain what I did to cause the crash. Perhaps because I had meant to hit Ctrl-Z, it arises from hitting both Ctrl-Z and Ctrl-X at the same time? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380246] New: Krita SegFaults and Crashes - Reported "There must be an inconsistency in the walkers happened!"
https://bugs.kde.org/show_bug.cgi?id=380246 Bug ID: 380246 Summary: Krita SegFaults and Crashes - Reported "There must be an inconsistency in the walkers happened!" Product: krita Version: 3.1.3-rc Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: camibr...@gmail.com Target Milestone: --- Created attachment 105728 --> https://bugs.kde.org/attachment.cgi?id=105728=edit A log of the krita's output following the crash. While using the lasso selection tool, I accidentally hit Ctrl-X rather than Ctrl-Z. This caused krita to crash, due to a segmentation fault based on the output. It complained first that "The walker hasn't reached the root layer", then that "There must be an inconsistency in the walkers happened!". I have included the output that resulted from the crash. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 377370] New: On screen display shows volume instead of the song when using command line arguments to switch the song.
https://bugs.kde.org/show_bug.cgi?id=377370 Bug ID: 377370 Summary: On screen display shows volume instead of the song when using command line arguments to switch the song. Product: amarok Version: 2.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Notifications Assignee: amarok-bugs-d...@kde.org Reporter: cren...@gmail.com Target Milestone: 2.9 Reproduce steps: While playing a song, use amarok -r or amarok -f to switch the song. Expected result: The next song's name is shown in the on screen display. Actual result: The current volume is shown in the on screen display. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365939] New: Task manager does not show text in vertical panel
https://bugs.kde.org/show_bug.cgi?id=365939 Bug ID: 365939 Summary: Task manager does not show text in vertical panel Product: plasmashell Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: cmrnt...@gmail.com CC: plasma-b...@kde.org Just as the title says, the task manager does not show text next to the application icon in a vertical panel. The expected behavior occurs with a horizontal panel. The text can be made to appear by going into system setting and performing an action that updates icons or the desktop theme. However, text will not appear for applications launched afterwards. Reproducible: Always Steps to Reproduce: 1.Set up a vertical panel with task manager 2.Make sure the task manager is set to "Switch between running applications" 3.Launch an application Actual Results: Icon associated with application appears in the task manager Expected Results: Icon and text associated with the application should both appear. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 357868] Closing laptop lid doesn't result in suspend
https://bugs.kde.org/show_bug.cgi?id=357868 --- Comment #3 from Cameron <c...@neo-zeon.de> --- I assumed it was merged because this started working for me (I'm currently using 5.5.4-0ubuntu1~ubuntu15.10~ppa1). Only issue is now the screen goes to sleep even with an external monitor attached. There's an option you can set that tells kscreen to suspend even if an external monitor is attached... I triple checked that this option is unset, so the system going to sleep when I close the lid with an external monitor is definitely a bug and should probably be filed separately once I have the time. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 360044] New: Online updater finds data but doesn't understand it.
https://bugs.kde.org/show_bug.cgi?id=360044 Bug ID: 360044 Summary: Online updater finds data but doesn't understand it. Product: kmymoney4 Version: 4.7.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: camb...@tiscali.co.uk INVP.L (Investec stock) appears on Yahoo UK with a current price and time stamp. The online updater finds the data but says it has no price or no date. Similar outcome with a fund. GB0032494576.L (Aviva Investors Higher Inc Pls A GBP Inc) Reproducible: Always Steps to Reproduce: 1.Create stock / fund and set relevant lookup ID and set to Yahoo UK 2.Run Online Price Update 3. Actual Results: 1) INVP.L (Investec stock) Message on price up date popup: Failed to retrieve a quote for INVP.L from Yahoo UK. Press No to remove the online price source from this security permanently, Yes to continue updating this security during future price updates or Cancel to stop the current update operation. Status on "Update Stock and Currency Prices" dialogue: Fetching URL http://uk.finance.yahoo.com/d/quotes.csv?s=INVP.L=sl1d3... Symbol found: "INVP.L" Price found: 488.80 (488.8) Unable to update price for INVP.L (no price or no date) 2) GB0032494576.L (Aviva Investors Higher Inc Pls A GBP Inc) Message on price up date popup: Failed to retrieve a quote for GB0032494576.l from Yahoo UK. Press No to remove the online price source from this security permanently, Yes to continue updating this security during future price updates or Cancel to stop the current update operation. Status on "Update Stock and Currency Prices" dialogue: Fetching URL http://uk.finance.yahoo.com/d/quotes.csv?s=GB0032494576.l=sl1d3... Symbol found: "GB0032494576.l" Price found: 55. (55) Unable to update price for GB0032494576.l (no price or no date) Expected Results: Since the page isn't displaying a date, should the application not assume 'today' and interpret the price data. Similar outcome with a fund. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 357868] New: Closing laptop lid doesn't result in suspend
https://bugs.kde.org/show_bug.cgi?id=357868 Bug ID: 357868 Summary: Closing laptop lid doesn't result in suspend Product: KScreen Version: 5.4.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: dvra...@kde.org Reporter: c...@neo-zeon.de Closing the lid of the laptop doesn't result in suspend. The issue is caused by kscreen thinking that the monitor type is unknown. "unknown" type monitors are counted as external (see line 233 at https://github.com/KDE/powerdevil/blob/master/daemon/actions/bundled/handlebuttonevents.cpp) and thus the system won't suspend with the lid closed when an "external" monitor is attached. Configuring power management to ignore externally attached monitors will allow the system to suspend on a laptop lid closed, but then the laptop will of course sleep when the lid is closed even when an external monitor is attached. The best work around is to select "suspend" from the "Power / Session" menu under the application menu. ~/.xsession-errors shows the following when the lid is closed and : "powerdevil: Lid action was suppressed because an external monitor is present" xrandr seems to report the display type correctly looking at the output of 'kscreen-console bug'. The output for 'QT_LOGGING_RULES="*" kscreen-console bug': START: Requesting Config kscreen: launcherDataAvailable: "org.kde.KScreen.Backend.XRandR" kscreen: Launcher finished with exit code 1 , status 0 kscreen: Service for requested backend already running kscreen: Primary output changed from KScreen::Output(Id: 446 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 446 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 446 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 446 , Name: "HDMI-0" ) ( "HDMI-0" ) Received config. Took 76 milliseconds xrandr --verbose== Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 16384 x 16384 HDMI-0 connected primary 1920x1200+0+0 (0x1bf) normal (normal left inverted right x axis y axis) 518mm x 324mm Identifier: 0x1be Timestamp: 1304363 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 1 0 2 3 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 000010ac7aa053544737 1718010380342078eaee95a3544c9926 0f5054a1080081408180a940b300d1c0 010101010101283c80a070b023403020 36000644211a00ff00594d59 4831343633374754530a00fc0044 454c4c2055323431324d0a2000fd 00323d1e5311000a20202020202000ed BorderDimensions: 4 supported: 4 Border: 0 0 0 0 range: (0, 65535) SignalFormat: TMDS supported: TMDS ConnectorType: HDMI ConnectorNumber: 4 _ConnectorLocation: 4 1920x1200 (0x1bf) 154.000MHz +HSync -VSync *current +preferred h: width 1920 start 1968 end 2000 total 2080 skew0 clock 74.04KHz v: height 1200 start 1203 end 1209 total 1235 clock 59.95Hz 1920x1080 (0x1c0) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1680x1050 (0x1c1) 146.250MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew0 clock 65.29KHz v: height 1050 start 1053 end 1059 total 1089 clock 59.95Hz 1600x1200 (0x1c2) 162.000MHz +HSync +VSync h: width 1600 start 1664 end 1856 total 2160 skew0 clock 75.00KHz v: height 1200 start 1201 end 1204 total 1250 clock 60.00Hz 1280x1024 (0x1c3) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1280x960 (0x1c4) 108.000MHz +HSync +VSync h: width 1280 start 1376 end 1488 total 1800 skew0 clock 60.00KHz v: height 960 start 961 end 964 total 1000 clock 60.00Hz 1024x768 (0x1c5) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 800x600 (0x1c6) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 640x480 (0x1c7) 25.175MHz -HSync -VSync h:
[amarok] [Bug 356427] New: Amarok will not start
https://bugs.kde.org/show_bug.cgi?id=356427 Bug ID: 356427 Summary: Amarok will not start Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: chippypr...@gmail.com Application: amarok (2.8.0) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.6-2-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Trying to open a file from an external drive Previously to this crash Amarok would find files but not play them - Custom settings of the application: Clean install of Opensuse with additional repositries for packman, google-chrome-stable, steam http://software.opensuse.org/ymp/openSUSE:Leap:42.1:NonFree/standard/steam.ymp?base=openSUSE%3ALeap%3A42.1=steam, and multimedia codecs found here http://opensuse-community.org/codecs-kde.ymp The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Bus error Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f59f48800 (LWP 18058))] Thread 17 (Thread 0x7f1f37c68700 (LWP 18061)): #0 0x7f1f56ca6789 in syscall () from /lib64/libc.so.6 #1 0x7f1f5113ca1c in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f31fbfacd in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #3 0x7f1f47f96279 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #4 0x7f1f5112050c in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f5111fb85 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #7 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f1f361e7700 (LWP 18062)): #0 0x7f1f56ca6789 in syscall () from /lib64/libc.so.6 #1 0x7f1f5113ca1c in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f31fbfacd in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #3 0x7f1f47f96279 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #4 0x7f1f5112050c in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f5111fb85 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #7 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f1f2bfff700 (LWP 18063)): #0 0x7f1f54ded408 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1f33b54e2a in ?? () from /usr/lib64/libmysqld.so.18 #2 0x7f1f33b4d236 in ?? () from /usr/lib64/libmysqld.so.18 #3 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f1f2b7fe700 (LWP 18064)): #0 0x7f1f54ded408 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1f572f6c64 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x7f1f58fb817e in AbstractDirectoryWatcher::run() () from /usr/lib64/libamaroklib.so.1 #3 0x7f1f53ee9542 in ?? () from /usr/lib64/libthreadweaver.so.4 #4 0x7f1f53ee96fe in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () from /usr/lib64/libthreadweaver.so.4 #5 0x7f1f53ee8f4b in ThreadWeaver::Thread::run() () from /usr/lib64/libthreadweaver.so.4 #6 0x7f1f572f679f in ?? () from /usr/lib64/libQtCore.so.4 #7 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f1f2affd700 (LWP 18065)): #0 0x7f1f56ca23cd in poll () from /lib64/libc.so.6 #1 0x7f1f510fabe4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f510facec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1f574250de in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #4 0x7f1f573f6e6f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #5 0x7f1f573f7165 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7f1f572f40bf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x7f1f573d8783 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x7f1f572f679f in ?? () from /usr/lib64/libQtCore.so.4 #9 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f1f298a6700 (LWP 18066)): #0 0x7f1f54ded05f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1f572f6c86 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x7f1f53ee76fc in ?? () from /usr/lib64/libthreadweaver.so.4 #3 0x7f1f53eea193 in ?? () from
