[dolphin] [Bug 322922] Dolphin should not store .directory files inside the actual directory to avoid cluttering and polluting the filesystem; should instead use ~/.local/share/dolphin/view_propertie
https://bugs.kde.org/show_bug.cgi?id=322922 Buck Shockley changed: What|Removed |Added CC||darkwingbuc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401579] Folders in recent documents show unknown icon
https://bugs.kde.org/show_bug.cgi?id=401579 --- Comment #4 from Buck Shockley --- This still occurs in the following software versions with the Breeze theme. KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404188] Visual glitch when shading window
https://bugs.kde.org/show_bug.cgi?id=404188 --- Comment #7 from Buck Shockley --- Issue does not occur with the "Oxygen" or "Plastik" window decorations. KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.14.5 Qt Version: 5.12.1 Qt compile version: 5.12.1 XCB compile version: 1.13.1 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12003000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 7, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,5,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Platform == Name: KWin::X11StandalonePlatform Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: true placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: true maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 99 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: DP-1 Geometry: 1920,0,1920x1080 Scale: 1 Refresh Rate: 60 Screen 1: - Name: DP-5 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 970/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 415.27 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 415.27 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.20.3 Linux kernel version: 4.20.7 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom kwin4_effect_maximize kwin4_effect_fade kwin4_effect_windowaperture kwin4_effect_dialogparent kwin4_effect_logout kwin4_effect_translucency kwin4_effect_frozenapp kwin4_effect_morphingpopups kwin4_effect_login slidingpopups slide screenshot scale minimizeanimation glide flipswitch desktopgrid cube coverswitch colorpicker presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay
[kwin] [Bug 404188] Visual glitch when shading window
https://bugs.kde.org/show_bug.cgi?id=404188 --- Comment #4 from Buck Shockley --- (In reply to Vlad Zagorodniy from comment #3) > If you select "No Borders" in System Settings > Application Style > Window > Decorations > Border Size, does this issue occur? Yes -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404188] Visual glitch when shading window
https://bugs.kde.org/show_bug.cgi?id=404188 --- Comment #2 from Buck Shockley --- https://paste.kde.org/pbovbtnkc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404188] New: Visual glitch when shading window
https://bugs.kde.org/show_bug.cgi?id=404188 Bug ID: 404188 Summary: Visual glitch when shading window Product: kwin Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Created attachment 117973 --> https://bugs.kde.org/attachment.cgi?id=117973=edit Screenshot of visual glitch When shading a window, there is a small rectangle under the length of the window before the shadow is properly rendered by the compositor. See screenshot Operating System: Manjaro Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.7-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Driver: nvidia 415.27 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 403126] New: Ksysguard crashed when scrolling to the bottom then closing it
https://bugs.kde.org/show_bug.cgi?id=403126 Bug ID: 403126 Summary: Ksysguard crashed when scrolling to the bottom then closing it Product: ksysguard Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Application: ksysguard (5.14.4) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.20.0-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I had opened Ksysguard and scrolled to the bottom of the list to check if wineserver had been killed properly then tried to close it and I was alerted to a crash. The crash does not seem to be reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdf02ee4240 (LWP 23739))] Thread 3 (Thread 0x7fdefb59c700 (LWP 23742)): #0 0x7fdf0e6b9c21 in poll () at /usr/lib/libc.so.6 #1 0x7fdf08121540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fdf0812162e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fdf0cdf35c4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fdf0cd9c58c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fdf0cbe05c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fdf0d104ba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fdf0cbe19cc in () at /usr/lib/libQt5Core.so.5 #8 0x7fdf089eba9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fdf0e6c4b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fdf02edd700 (LWP 23740)): #0 0x7fdf089f1afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdf0ca49cd1 in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:864 #2 0x7fdf0ca49cd1 in std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7fdf0b883f54 in () at /usr/lib/libQt5WebKit.so.5 #4 0x7fdf0b884079 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7fdf0ca50063 in std::execute_native_thread_routine(void*) (__p=0x564a2e46ccb0) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:80 #6 0x7fdf089eba9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fdf0e6c4b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fdf02ee4240 (LWP 23739)): [KCrash Handler] #6 0x7fdf0cc61326 in operator==(QString const&, QString const&) () at /usr/lib/libQt5Core.so.5 #7 0x7fdf0d9c5138 in QLabel::setText(QString const&) () at /usr/lib/libQt5Widgets.so.5 #8 0x7fdf0e7fde15 in () at /usr/lib/libkdeinit5_ksysguard.so #9 0x7fdf0e4705b9 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/libksgrd.so.7 #10 0x7fdf0e477cd0 in () at /usr/lib/libksgrd.so.7 #11 0x7fdf0cdc83e0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7fdf0cd3106b in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7fdf0cd36cc4 in () at /usr/lib/libQt5Core.so.5 #14 0x7fdf0cd37120 in () at /usr/lib/libQt5Core.so.5 #15 0x7fdf0cdc828c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #16 0x7fdf0cdd3eea in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #17 0x7fdf0cdd4242 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #18 0x7fdf0d892e34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7fdf0d89a671 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7fdf0cd9d8f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7fdf0cdf4226 in () at /usr/lib/libQt5Core.so.5 #22 0x7fdf0811fa2f in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #23 0x7fdf081215e9 in () at /usr/lib/libglib-2.0.so.0 #24 0x7fdf0812162e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #25 0x7fdf0cdf35a9 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7fdf0cd9c58c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #27 0x7fdf0cda4896 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #28 0x7fdf0e7ffc23 in kdemain () at /usr/lib/libkdeinit5_ksysguard.so #29 0x7fdf0e5ed223 in __libc_start_main () at /usr/lib/libc.so.6 #30 0x564a2e26905e in
[Powerdevil] [Bug 403047] New: Inhibit powersaving for fullscreen applications
https://bugs.kde.org/show_bug.cgi?id=403047 Bug ID: 403047 Summary: Inhibit powersaving for fullscreen applications Product: Powerdevil Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Right now, power saving only inhibits for media players. I have to use the Caffeine Plus plasmoid to correctly inhibit power saving in situations for playing games with controllers. Power management should also have an option to inhibit when any full screen application is running -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402567] Kwin compositor crashes consistently when awakening from suspend
https://bugs.kde.org/show_bug.cgi?id=402567 --- Comment #3 from Buck Shockley --- My system has since upgrade to kernel 4.20 with Qt version 5.12 and KDE Frameworks 5.53. Bug still persists. See attached backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402567] Kwin compositor crashes consistently when awakening from suspend
https://bugs.kde.org/show_bug.cgi?id=402567 --- Comment #2 from Buck Shockley --- Created attachment 117190 --> https://bugs.kde.org/attachment.cgi?id=117190=edit Kwin backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402567] New: Kwin compositor crashes consistently when awakening from suspend
https://bugs.kde.org/show_bug.cgi?id=402567 Bug ID: 402567 Summary: Kwin compositor crashes consistently when awakening from suspend Product: kwin Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- SUMMARY Kwin compositor crashes when awakening from suspend, visually corrupting the lock screen STEPS TO REPRODUCE 1. Suspend 2. Wake up computer OBSERVED RESULT Compositor will crash and restart, showing either a black screen or a visually corrupted background for the lock screen. Some visual corruption occasionally follows to the desktop EXPECTED RESULT Compositor does not crash SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.14.4 Qt Version: 5.11.2 KDE Frameworks Version: 5.52.0 Kernel Version: 4.19.12-2-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION Using nvidia driver version 415.25. Using OpenGL 3.1 rendering backend in Compositor settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401579] New: Folders in recent documents show unknown icon
https://bugs.kde.org/show_bug.cgi?id=401579 Bug ID: 401579 Summary: Folders in recent documents show unknown icon Product: plasmashell Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: darkwingbuc...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 116587 --> https://bugs.kde.org/attachment.cgi?id=116587=edit Screenshot showing the icons Right-clicking on Dolphin and other applications that show recent documents shows them with generic icons. Only happens for folders when right-clicking on Dolphin and text/.conf files when right-clicking on Kate. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 4.19.5 (available in About System) KDE Plasma Version: 5.14.4 Qt Version: 5.11.2 KDE Frameworks Version: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 400676] New: Cannot change color theme
https://bugs.kde.org/show_bug.cgi?id=400676 Bug ID: 400676 Summary: Cannot change color theme Product: kate Version: 18.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- SUMMARY Kate does not change the color scheme, either through the Settings menu or Configure window STEPS TO REPRODUCE 1. Open Kate 2. Try to change the color theme OBSERVED RESULT The color theme does not change, instead sticking to the default theme EXPECTED RESULT The color theme changes to the desired option SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION N/a -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400000] New: Text for dependencies listing is corrupted and unreadable
https://bugs.kde.org/show_bug.cgi?id=40 Bug ID: 40 Summary: Text for dependencies listing is corrupted and unreadable Product: Discover Version: 5.14.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Created attachment 115735 --> https://bugs.kde.org/attachment.cgi?id=115735=edit Broken text in Discover The text when looking at package dependencies is unreadable. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399813] New: Download progress not displayed for individual updates when updating
https://bugs.kde.org/show_bug.cgi?id=399813 Bug ID: 399813 Summary: Download progress not displayed for individual updates when updating Product: Discover Version: 5.14.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- SUMMARY Download progress on a specific update is not shown when updating in Manjaro Linux STEPS TO REPRODUCE 1. Start a system update through Discover OBSERVED RESULT Progress bars for individual updates are not shown when downloading, but are shown again when installing EXPECTED RESULT Progress bars for individual updates are shown for both downloads and installs SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379432] Folder label length in folder view decreases with icon size
https://bugs.kde.org/show_bug.cgi?id=379432 Buck Shockley changed: What|Removed |Added CC||darkwingbuc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399498] Desktop filenames wrap / truncation really weird
https://bugs.kde.org/show_bug.cgi?id=399498 Buck Shockley changed: What|Removed |Added CC||darkwingbuc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397257] Two entries for Adapta, neither can be removed
https://bugs.kde.org/show_bug.cgi?id=397257 --- Comment #3 from Buck Shockley --- (In reply to Nate Graham from comment #1) > Did you use Discover to install them in the first place? Yes. I had two updates available both for the two Adaptas. Installing them finally allowed me to remove them. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 397996] Missing icons for korganizer (appointment-recurring and appointment-reminder)
https://bugs.kde.org/show_bug.cgi?id=397996 Buck Shockley changed: What|Removed |Added CC||darkwingbuc...@gmail.com --- Comment #1 from Buck Shockley --- See #397989 for context -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397989] Icons missing in agenda view
https://bugs.kde.org/show_bug.cgi?id=397989 --- Comment #2 from Buck Shockley --- (In reply to Laurent Montel from comment #1) > Do you use korganizer on kde or gnome ? This is on KDE Plasma 5.13.4. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397989] New: Icons missing in agenda view
https://bugs.kde.org/show_bug.cgi?id=397989 Bug ID: 397989 Summary: Icons missing in agenda view Product: korganizer Version: 5.9.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-b...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Created attachment 114660 --> https://bugs.kde.org/attachment.cgi?id=114660=edit Screenshot of problem When viewing an event in the KOrganizer Agenda view, the icons denoting (presumably) that the event has a reminder and is recurring will be missing, instead replaced with generic icons. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 397292] Occasional delay when opening image file
https://bugs.kde.org/show_bug.cgi?id=397292 --- Comment #3 from Buck Shockley --- > How are you opening the image? Both double-clicking it in Dolphin and opening it through a terminal cause the same issue. > What is delayed exactly, opening of Gwenview, opening the image, displaying > the image, general unresponsiveness of the whole computer? Gwenview opening. Switching between images works fine and the Gwenview program is snappy afterwards, but opening Gwenview seems to slow down. > Do you experience the delay also when switching to that image? No. Switching images works fine once the program is opened. I initially thought it was that image, then I widened the scope to images that were on a 1TB HDD mounted in my home folder as opposed to my SSD mounted at /, but it seems to happen with every image on my PC. After a reboot, the problem seems to have gone away. I'm going to see if it happens again after prolonged uptime. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 397292] Occasional delay when opening image file
https://bugs.kde.org/show_bug.cgi?id=397292 --- Comment #1 from Buck Shockley --- Created attachment 114382 --> https://bugs.kde.org/attachment.cgi?id=114382=edit Picture that causes Gwenview to lag Actually, this image seems to consistently cause Gwenview to lag -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 397292] New: Occasional delay when opening image file
https://bugs.kde.org/show_bug.cgi?id=397292 Bug ID: 397292 Summary: Occasional delay when opening image file Product: gwenview Version: 18.04.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Gwenview sometimes delays when opening an image file. There's no specific image file, it's random. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397257] New: Two entries for Adapta, neither can be removed
https://bugs.kde.org/show_bug.cgi?id=397257 Bug ID: 397257 Summary: Two entries for Adapta, neither can be removed Product: Discover Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: KNewStuff Backend Assignee: aleix...@kde.org Reporter: darkwingbuc...@gmail.com CC: lei...@leinir.dk Target Milestone: --- Created attachment 114369 --> https://bugs.kde.org/attachment.cgi?id=114369=edit Screenshot of Installed list I have two entries for Adapta KDE in my Discover Installed listing but it doesn't do anything when I try to remove them. The program cannot be closed and there are no entries for them in System Settings. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 343688] Show desktop notifications on lock screen
https://bugs.kde.org/show_bug.cgi?id=343688 --- Comment #7 from Buck Shockley <darkwingbuc...@gmail.com> --- I'd also like to see this implemented into KDE, bringing a feature from other OSes and some DEs to Plasma. Due to security concerns, we can make this toggleable or just show the applications that sent notifications instead of the full detail, i.e. "3 Notifications from Thunderbird" "5 Notifications from Discord" "24 Updates Available" etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392939] New: Plasma crashes when changing desktop settings in activity that isn't "default"
https://bugs.kde.org/show_bug.cgi?id=392939 Bug ID: 392939 Summary: Plasma crashes when changing desktop settings in activity that isn't "default" Product: plasmashell Version: 5.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: darkwingbuc...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.3) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.14.31-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Opening a new activity, moving windows there, and changing desktop properties. Specifically, I was changing the layout from folder view to desktop (which caused a crash) then trying to set the wallpaper to slideshow mode (which caused another crash). - Custom settings of the application: Using Latte-dock plasmoid with Redshift, Thermal Monitor, and Resources Monitor widgets. I have two panels in Latte. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1d10ec9800 (LWP 23005))] Thread 11 (Thread 0x7f1c43bff700 (LWP 23029)): #0 0x7f1d09ce73bd in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1d0ab27fac in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1d0e91b49a in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f1d0e91b924 in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f1d0ab26acd in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f1d09ce108c in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f1d0a42ee7f in clone () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7f1c49233700 (LWP 23028)): #0 0x7f1d09ce73bd in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1d0ab27fac in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1d0e91b49a in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f1d0e91b924 in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f1d0ab26acd in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f1d09ce108c in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f1d0a42ee7f in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f1c4affe700 (LWP 23015)): #0 0x7f1d09ce73bd in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1d0ab27fac in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1d0e91b49a in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f1d0e91b924 in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f1d0ab26acd in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f1d09ce108c in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f1d0a42ee7f in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1c53296700 (LWP 23014)): #0 0x7f1d09ce73bd in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1d0ab27fac in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f1d0e91b49a in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f1d0e91b924 in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f1d0ab26acd in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f1d09ce108c in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f1d0a42ee7f in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1c5937c700 (LWP 23011)): #0 0x7f1d0a4203d8 in read () from /usr/lib/libc.so.6 #1 0x7f1d04d3c7d1 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1d04cf6ac8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f1d04cf6f96 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f1d04cf710e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f1d0ad70264 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1d0ad1232b in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f1d0ab2172e in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f1d0e89950b in ?? () from /usr/lib/libQt5Quick.so.5 #9 0x7f1d0ab26acd in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f1d09ce108c in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f1d0a42ee7f in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f1ceab79700 (LWP 23010)): #0 0x7f1d09ce73bd in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1d105b8f77 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f1d105b8fb9 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f1d09ce108c in start_thread () from /usr/lib/libpthread.so.0 #4
[konsole] [Bug 392674] Konsole is always maximized
https://bugs.kde.org/show_bug.cgi?id=392674 --- Comment #4 from Buck Shockley <darkwingbuc...@gmail.com> --- I've triple checked my KWin rules and my Konsole configurations. Nothing should be causing this behavior. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392674] Konsole is always maximized
https://bugs.kde.org/show_bug.cgi?id=392674 --- Comment #2 from Buck Shockley <darkwingbuc...@gmail.com> --- No, it does not happen on a different user account -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392674] New: Konsole is always maximized
https://bugs.kde.org/show_bug.cgi?id=392674 Bug ID: 392674 Summary: Konsole is always maximized Product: konsole Version: 17.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Konsole always opens maximized, regardless of default size settings in Konsole settings or even KWin settings. Forcing the window size has been the only way I can get Konsole to not open maximized. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 343688] Show desktop notifications on lock screen
https://bugs.kde.org/show_bug.cgi?id=343688 Buck Shockley <darkwingbuc...@gmail.com> changed: What|Removed |Added CC||darkwingbuc...@gmail.com --- Comment #6 from Buck Shockley <darkwingbuc...@gmail.com> --- This report is rather old, but I would like to see this in a future version of Plasma 5. Modern desktop OS's like Mac OS and Windows 10 both implement this feature and even some Linux DE's like GNOME. It could be togglable for privacy reasons, but I would like the option. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385206] New: Resizing windows is very laggy
https://bugs.kde.org/show_bug.cgi?id=385206 Bug ID: 385206 Summary: Resizing windows is very laggy Product: kwin Version: 5.10.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- If I resize a window without enabling the Resize Window effect in Desktop Effects, the resizing effect is very jerky and laggy, but if I DO enable it (so that windows are resized with a texture instead of in real time), the resizing effect is smooth. Running Nvidia 375.82. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384020] New: Show desktop cube on only one monitor
https://bugs.kde.org/show_bug.cgi?id=384020 Bug ID: 384020 Summary: Show desktop cube on only one monitor Product: kwin Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Having the cube stretched between two monitors is annoying. I think it would look really nice if you could isolate the entire cube to one monitor when the hotkey is pressed. I realize this may be similar to bug 302149 but instead of giving each monitor its own cube, I want the entire cube to only appear on one monitor. It will look better without being stretched as much, especially when the monitors are two different resolutions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381105] Crash in uncontrolledAnimationFinished
https://bugs.kde.org/show_bug.cgi?id=381105 --- Comment #33 from Buck Shockley <darkwingbuc...@gmail.com> --- Created attachment 107202 --> https://bugs.kde.org/attachment.cgi?id=107202=edit New crash information added by DrKonqi plasmashell (5.10.4) using Qt 5.9.1 - What I was doing when the application crashed: Changing wallpaper and scaling options in Desktop Settings. -- Backtrace (Reduced): #5 0x in () #6 0x7f3950fb9489 in QSequentialAnimationGroupJob::uncontrolledAnimationFinished(QAbstractAnimationJob*) () at /usr/lib/libQt5Qml.so.5 #7 0x7f3950fb6c47 in QAbstractAnimationJob::finished() () at /usr/lib/libQt5Qml.so.5 #8 0x7f3950fb77bc in QAbstractAnimationJob::setState(QAbstractAnimationJob::State) () at /usr/lib/libQt5Qml.so.5 #9 0x7f3950fb7ab8 in QAbstractAnimationJob::setCurrentTime(int) () at /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381105] Crash in uncontrolledAnimationFinished
https://bugs.kde.org/show_bug.cgi?id=381105 Buck Shockley <darkwingbuc...@gmail.com> changed: What|Removed |Added CC||darkwingbuc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382485] OpenGL 2 compositing setup failed
https://bugs.kde.org/show_bug.cgi?id=382485 --- Comment #8 from Buck Shockley <darkwingbuc...@gmail.com> --- This may be a stupid question, but I noticed a couple other things sometimes popping up at the exact same time in journalctl: Jul 31 23:49:01 buck-pc kernel: NVRM: Xid (PCI::01:00): 31, Ch 0030, engmask 0101, intr 1000 Jul 31 23:49:01 buck-pc kwin_x11[1006]: Error loading text-to-speech plug-in "flite" Jul 31 23:49:01 buck-pc kwin_x11[1006]: kwin_core: OpenGL 2 compositing setup failed Jul 31 23:49:01 buck-pc kwin_x11[1006]: kwin_core: Failed to initialize compositing, compositing disabled The Arch wiki says the NVRM bit is related to hardware acceleration in Flash and a reddit post on /r/kde described an identical log output, even with the flite error. Could this be related to bug 381870? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382485] OpenGL 2 compositing setup failed
https://bugs.kde.org/show_bug.cgi?id=382485 --- Comment #7 from Buck Shockley <darkwingbuc...@gmail.com> --- (In reply to Yannick from comment #6) > Ok, forget what I said in my previous comment... > > I just had the same issue with the OpenGL 3.1 backend (starting Steam will > disable kwin compositing, and it won't enable it again). Every time I've had this problem, it's been directly related to Steam. It happened just now when trying to launch TF2 after it crashed. Exact same error in journalctl. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382485] OpenGL 2 compositing setup failed
https://bugs.kde.org/show_bug.cgi?id=382485 --- Comment #2 from Buck Shockley <darkwingbuc...@gmail.com> --- Yes, nvidia 375.66 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382485] New: OpenGL 2 compositing setup failed
https://bugs.kde.org/show_bug.cgi?id=382485 Bug ID: 382485 Summary: OpenGL 2 compositing setup failed Product: kwin Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- KWin fails to enable compositing after running applications that block/stop compositing. These are the errors that appear in journalctl: Jul 18 23:35:55 buck-pc kwin_x11[1044]: kwin_core: OpenGL 2 compositing setup failed Jul 18 23:35:55 buck-pc kwin_x11[1044]: kwin_core: Failed to initialize compositing, compositing disabled Jul 18 23:42:55 buck-pc kwin_x11[1044]: kwin_core: OpenGL 2 compositing setup failed Jul 18 23:42:55 buck-pc kwin_x11[1044]: kwin_core: Failed to initialize compositing, compositing disabled Jul 18 23:42:59 buck-pc kwin_x11[1044]: kwin_core: OpenGL 2 compositing setup failed Jul 18 23:42:59 buck-pc kwin_x11[1044]: kwin_core: Failed to initialize compositing, compositing disabled Jul 18 23:43:01 buck-pc kwin_x11[1044]: kwin_core: OpenGL 2 compositing setup failed Jul 18 23:43:01 buck-pc kwin_x11[1044]: kwin_core: Failed to initialize compositing, compositing disabled I'm not able to re-enable compositing under any circumstances without rebooting. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 382309] I/O error when burning anything
https://bugs.kde.org/show_bug.cgi?id=382309 --- Comment #1 from Buck Shockley <darkwingbuc...@gmail.com> --- Console output: "Preparing data" "Determining maximum writing speed" (K3b::AudioMaxSpeedJob) throughput: 61891 ( 1774560 / 27 ) (K3b::AudioMaxSpeedJob) throughput: 57765 ( 1774560 / 29 ) (K3b::AudioMaxSpeedJob) throughput: 64184 ( 1774560 / 26 ) (K3b::AudioMaxSpeedJob) throughput: 64184 ( 1774560 / 26 ) (K3b::AudioMaxSpeedJob) throughput: 66652 ( 1774560 / 25 ) (K3b::AudioMaxSpeedJob) throughput: 66652 ( 1774560 / 25 ) (K3b::AudioMaxSpeedJob) max speed: 57765 (K3b::InfFileWriter) could not open file "/tmp/tmp.mJerXJJp21/k3b_audio_0_01.inf" (K3b::AudioJob) could not write inf-files. received finished signal! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 382309] New: I/O error when burning anything
https://bugs.kde.org/show_bug.cgi?id=382309 Bug ID: 382309 Summary: I/O error when burning anything Product: k3b Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: darkwingbuc...@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Debug info: Devices --- TSSTcorp CDDVDW SE-S084D TS02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 17.4.2 KDE Version: 5.34.0 Qt Version: 5.9.0 Kernel: 4.9.35-1-MANJARO When trying to burn anything, K3b gives an I/O Error in the burn window. There is still free space left on the hard drive and on the disc I'm burning to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382285] New: KWin crash while installing Steam with Wine
https://bugs.kde.org/show_bug.cgi?id=382285 Bug ID: 382285 Summary: KWin crash while installing Steam with Wine Product: kwin Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.9.35-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Installing Steam through Wine and PlayOnLinux. I was testing some different settings and had probably installed it three times until it crashed. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe852c0d840 (LWP 1084))] Thread 7 (Thread 0x7fe81fd93700 (LWP 24808)): [KCrash Handler] #5 0x7fe85259d670 in raise () at /usr/lib/libc.so.6 #6 0x7fe85259ed00 in abort () at /usr/lib/libc.so.6 #7 0x7fe84fa23807 in () at /usr/lib/libQt5Core.so.5 #8 0x7fe83248da23 in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #9 0x7fe84fc4157f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #10 0x7fe84fcbe767 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #11 0x7fe84fc4e008 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7fe84fc41e2b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7fe85093d46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fe850944cf4 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7fe84fc12b98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7fe84fc69bae in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #17 0x7fe84fc67dc2 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7fe84fc1121a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7fe84fa3340a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #21 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #22 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fe831026700 (LWP 21572)): #0 0x7fe84b80339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe84fa390eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe84ac0f8d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fe84ac0fd3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #5 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fe81e829700 (LWP 1194)): #0 0x7fe84b80339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe84eb91ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fe84eb91b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe82bfff700 (LWP 1152)): #0 0x7fe85264d326 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe84fc66471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe84fc67b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe84fc1121a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe84fa3340a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe84a51d645 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe832eb1700 (LWP 1129)): #0 0x7fe85264d326 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe84fc66471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe84fc67b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe84fc1121a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe84fa3340a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe8496c2d45 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe8526571ef in clone () at
[kwin] [Bug 382112] New: KWin crash when closing Chromium notification
https://bugs.kde.org/show_bug.cgi?id=382112 Bug ID: 382112 Summary: KWin crash when closing Chromium notification Product: kwin Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.9.35-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Closing a Chromium notification from Scrap.TF. Upon closing, the compositor stopped working and KWin crashed. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb57d7ee840 (LWP 1061))] Thread 7 (Thread 0x7fb4b358c700 (LWP 22796)): #0 0x7fb5763e439d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb57a61a0eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb5757f08d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fb5757f0d3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb57a618cbd in () at /usr/lib/libQt5Core.so.5 #5 0x7fb5763de297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb57d2381ef in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fb54622c700 (LWP 22771)): [KCrash Handler] #5 0x7fb57d17e670 in raise () at /usr/lib/libc.so.6 #6 0x7fb57d17fd00 in abort () at /usr/lib/libc.so.6 #7 0x7fb57a604807 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb5610f5a23 in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #9 0x7fb57a82257f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #10 0x7fb57a89f767 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #11 0x7fb57a82f008 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7fb57a822e2b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7fb57b51e46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fb57b525cf4 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7fb57a7f3b98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7fb57a84abae in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #17 0x7fb57a848dc2 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7fb57a7f221a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7fb57a61440a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7fb57a618cbd in () at /usr/lib/libQt5Core.so.5 #21 0x7fb5763de297 in start_thread () at /usr/lib/libpthread.so.0 #22 0x7fb57d2381ef in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fb545241700 (LWP 1164)): #0 0x7fb5763e439d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb579772ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fb579772b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fb5763de297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb57d2381ef in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fb55b7fe700 (LWP 1123)): #0 0x7fb57d22e326 in ppoll () at /usr/lib/libc.so.6 #1 0x7fb57a847471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fb57a848b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fb57a7f221a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb57a61440a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fb5750fe645 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fb57a618cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fb5763de297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb57d2381ef in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb561b19700 (LWP 1077)): #0 0x7fb57d22e326 in ppoll () at /usr/lib/libc.so.6 #1 0x7fb57a847471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fb57a848b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fb57a7f221a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb57a61440a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fb5742a3d45 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fb57a618cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fb5763de297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb57d2381ef in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb563c94700 (LWP 1064)): #0
[digikam] [Bug 381705] New: Allow use of only partial metadata with other options being static
https://bugs.kde.org/show_bug.cgi?id=381705 Bug ID: 381705 Summary: Allow use of only partial metadata with other options being static Product: digikam Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: BatchQueueManager-Tool-LensDistortion Assignee: digikam-de...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- When using the Lens Distortion tool in Image Editor, you have the option to fill in the blanks for lens and manufacturers for when Digikam can't scrape all the proper metadata. In my case, I have a Nikon D3400 with the kit 18-55mm lens. The problem is that Digikam doesn't recognize the D3400 model and the camera doesn't properly record lens metadata. Since I'm processing pictures that all come from the same camera and lens, would it be possible to have an option added where Digikam uses metadata for certain, reliable options (focal length, aperture, etc.) and manually set other ones? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 379610] New: Allow sending SMS from Plasmoid
https://bugs.kde.org/show_bug.cgi?id=379610 Bug ID: 379610 Summary: Allow sending SMS from Plasmoid Product: kdeconnect Version: 1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: darkwingbuc...@gmail.com Target Milestone: --- KDE Connect plasmoid can reply to incoming SMS notifications, but can't send them. This can be done through a terminal prompt and through the indicator on GTK desktops, but not from the plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 374085] no button to answer to an sms
https://bugs.kde.org/show_bug.cgi?id=374085 Buck Shockley <darkwingbuc...@gmail.com> changed: What|Removed |Added CC||darkwingbuc...@gmail.com --- Comment #6 from Buck Shockley <darkwingbuc...@gmail.com> --- Possible solution: In the KDE Connect app on Android, go to the "Plugin settings" menu then the options for Notification sync. Unselect your SMS app (in my case: Textra). Make sure the "Send SMS" and "Telephony notifier" options are CHECKED in plugin settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378641] New: Plasma crashed after moving panel to top of screen from bottom
https://bugs.kde.org/show_bug.cgi?id=378641 Bug ID: 378641 Summary: Plasma crashed after moving panel to top of screen from bottom Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: darkwingbuc...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.9.20-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Moving panel from bottom screen edge to top screen edge. I also had two Chromium windows open, one floating on one monitor and the other fullscreened on a secondary monitor. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f68d833e800 (LWP 1041))] Thread 30 (Thread 0x7f2798ab4700 (LWP 5520)): #0 0x7ffdfede5af0 in clock_gettime () #1 0x7f68d1a15826 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f68d2324201 in () at /usr/lib/libQt5Core.so.5 #3 0x7f68d23229c9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f68d2322f75 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f68d232463e in () at /usr/lib/libQt5Core.so.5 #6 0x7f68cc7e3c8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7f68cc7e46cb in () at /usr/lib/libglib-2.0.so.0 #8 0x7f68cc7e48bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7f68d232506b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7f68d22ce89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7f68d20f0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7f68d5228025 in () at /usr/lib/libQt5Qml.so.5 #13 0x7f68d20f56d8 in () at /usr/lib/libQt5Core.so.5 #14 0x7f68d0faa2e7 in start_thread () at /usr/lib/libpthread.so.0 #15 0x7f68d1a0854f in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f279bfff700 (LWP 30025)): #0 0x7f68d0fb0756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f68d20f658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f68d5e4d665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f68d5e4df72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f68d20f56d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f68d0faa2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f68d1a0854f in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f279b7fe700 (LWP 30024)): #0 0x7f68d19fe67d in poll () at /usr/lib/libc.so.6 #1 0x7f68c65f2ee1 in () at /usr/lib/libpulse.so.0 #2 0x7f68c65e46f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f68c65e4d8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f68c65e4e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f68c65f2e29 in () at /usr/lib/libpulse.so.0 #6 0x7f68c5f82fe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7f68d0faa2e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f68d1a0854f in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f2799d8d700 (LWP 30023)): #0 0x7f68cc829e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f68cc7e3c99 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f68cc7e46cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7f68cc7e48bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f68d232506b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f68d22ce89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f68d20f0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f68d5228025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f68d20f56d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f68d0faa2e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f68d1a0854f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f67a6ffe700 (LWP 14625)): #0 0x7f68d0fb0756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f68d20f658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f68d5e4d665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f68d5e4df72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f68d20f56d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f68d0faa2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f68d1a0854f in clone () at
[plasma4] [Bug 197980] Highlight Window: Short delay before highlighting
https://bugs.kde.org/show_bug.cgi?id=197980 Buck Shockley <darkwingbuc...@gmail.com> changed: What|Removed |Added CC||darkwingbuc...@gmail.com --- Comment #13 from Buck Shockley <darkwingbuc...@gmail.com> --- 5.9.x, still no delay, not even a configurable one. Delay does not need to be that long, but the instantaneous effect is jarring. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 376189] Unable to create io-slave. Cannot talk to klauncher: Not connected to D-Bus server
https://bugs.kde.org/show_bug.cgi?id=376189 --- Comment #5 from Buck Shockley <darkwingbuc...@gmail.com> --- (In reply to stephane from comment #3) > I arrive to replicate the bug. > it seems to come that arch dbus package is build without > "--enable-x11-autolaunch" Can you make a bug report for Arch, then? You seem to know more about the problem than I do. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 376189] Unable to create io-slave. Cannot talk to klauncher: Not connected to D-Bus server
https://bugs.kde.org/show_bug.cgi?id=376189 --- Comment #2 from Buck Shockley <darkwingbuc...@gmail.com> --- Running it with sudo causes the problem to not occur. If it helps, running it normally gives me a prompt from KDE su. This is the command it says is being executed: KDE_FULL_SESSION=true XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/partitionmanager --dontsu -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 376189] New: Unable to create io-slave. Cannot talk to klauncher: Not connected to D-Bus server
https://bugs.kde.org/show_bug.cgi?id=376189 Bug ID: 376189 Summary: Unable to create io-slave. Cannot talk to klauncher: Not connected to D-Bus server Product: partitionmanager Version: 3.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: darkwingbuc...@gmail.com Target Milestone: --- How to reproduce: 1. Open KDE Partition Manger from the Application Launcher or running partitionmanager in Konsole 2. Right click on any unmounted partition and select "Edit Mount Point..." 3. In the Path field, click "Select..." 4. The following error will appear twice: "Unable to create io-slave. Cannot talk to klauncher: Not connected to D-Bus server" Running in Konsole gives no output. Running dbus-launch partitionmanager also causes the same problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375460] New: Panel doesn't disappear when using Steam Big Picture
https://bugs.kde.org/show_bug.cgi?id=375460 Bug ID: 375460 Summary: Panel doesn't disappear when using Steam Big Picture Product: plasmashell Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: 1.0 If you enter Steam Big Picture, the panel disappears fine, but if you open and close a game, there's a delay between when the game closes and when Big Picture reappears. When that happens, the panel won't disappear unless Big Picture is closed and opened again, so it just sits on top of Big Picture. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373478] Dolphin does not run if launched via sudo
https://bugs.kde.org/show_bug.cgi?id=373478 --- Comment #2 from Buck Shockley <darkwingbuc...@gmail.com> --- (In reply to Elvis Angelaccio from comment #1) > Have you tried with 'kdesu dbus-launch dolphin'? Yes, that command works. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373478] New: Dolphin does not run if launched via sudo
https://bugs.kde.org/show_bug.cgi?id=373478 Bug ID: 373478 Summary: Dolphin does not run if launched via sudo Product: dolphin Version: 16.08.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Running the command 'sudo dolphin' in Konsole will print out the following: [buck@archie ~]$ sudo dolphin [sudo] password for buck: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' "Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport $(dbus-launch)" This is 100% reproducible. Running printed command (export $(dbus-launch)) does nothing. Opening with KDE su results in the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373200] New: KWin crashes when removing ISO from Virtualbox drive
https://bugs.kde.org/show_bug.cgi?id=373200 Bug ID: 373200 Summary: KWin crashes when removing ISO from Virtualbox drive Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was creating a Fedora VM in Virtualbox when I had to close the VM and unmount the Fedora ISO, removing it from the virtual drive. After removing it, KWin crashed and restarted. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe801749840 (LWP 813))] Thread 13 (Thread 0x7fe716686700 (LWP 8029)): #0 0x7fe7fa42410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe7fe60bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe7f9845395 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fe7f9845c8a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe7fe60ad78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fe7fa41e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe8011907df in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fe717687700 (LWP 8028)): #0 0x7fe801187551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe7fe834ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe7fe8363b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe7fe7e323a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe7fe6060f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe7f917c2d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fe7fe60ad78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fe7fa41e454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe8011907df in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fe726144700 (LWP 32556)): #0 0x7fe7fa42410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe7fe60bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe7f9845395 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fe7f9845c8a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe7fe60ad78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fe7fa41e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe8011907df in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fe7d700 (LWP 32553)): #0 0x7fe7fe8362b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #1 0x7fe7fe7e323a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #2 0x7fe7fe6060f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #3 0x7fe7f917c2d5 in () at /usr/lib/libQt5Qml.so.5 #4 0x7fe7fe60ad78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fe7fa41e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe8011907df in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fe7de7fd700 (LWP 21213)): #0 0x7fe801187551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe7fe834ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe7fe8363b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe7fe7e323a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe7fe6060f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe7f917c2d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fe7fe60ad78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fe7fa41e454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe8011907df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fe7c969e700 (LWP 10035)): #0 0x7fe7fa42410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe7fe60bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe7f9845395 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fe7f9845c8a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe7fe60ad78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fe7fa41e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe8011907df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fe7325da700 (LWP 7373)): #0 0x7fe7fa42410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe7fe60bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe7f9845395 in () at
[kwin] [Bug 372541] New: Allow for blurring of transparent elements
https://bugs.kde.org/show_bug.cgi?id=372541 Bug ID: 372541 Summary: Allow for blurring of transparent elements Product: kwin Version: 5.8.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Kwin, currently, has no setting for allow the background of transparent windows to be blurred, despite this functionality already existing. The panels, popups, Application Launcher menu, and Krunner are already blurred, but it is impossible to blur windows like Konsole, despite transparency being an option. I am aware a blur option already exists in Desktop Effects, but it only works for the aforementioned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372542] New: Allow for greater transparency control
https://bugs.kde.org/show_bug.cgi?id=372542 Bug ID: 372542 Summary: Allow for greater transparency control Product: plasmashell Version: 5.8.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: darkwingbuc...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Allow for users to control the transparency levels of panels and plasmoids. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369202] New: Allow speeding up of the animation for the Glide effect
https://bugs.kde.org/show_bug.cgi?id=369202 Bug ID: 369202 Summary: Allow speeding up of the animation for the Glide effect Product: kwin Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com The Glide effect doesn't allow for the timing of the animation to be changed, and right now it feels really slow. In addition to gliding in and out and the angle of the glide, the speed should also be a variable. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365797] Second monitor distorts when being adjusted
https://bugs.kde.org/show_bug.cgi?id=365797 --- Comment #9 from Buck Shockley <darkwingbuc...@gmail.com> --- (In reply to Martin Gräßlin from comment #8) > That looks all fine: > * xorg log doesn't have warnings > * kwin debug output is correct - it detected the screens as printed in xorg > log, compositor is active and happy > * glxinfo doesn't show any "bad" limits > > My assumption currently is that also Plasma (and other applications) get the > graphics reset from the NVIDIA driver. If that's the case you don't need to > restart the complete session. A > kquitapp5 plasmashell > plasmashell > > from e.g. KRunner should also fix it. See Comment 3. I don't know why, but a complete session restart works. However, I just realized, the only way to make the screen reset after restarting the session is disabling the Kscreen 2 startup service. I don't know if that is impacting these results. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365797] Second monitor distorts when being adjusted
https://bugs.kde.org/show_bug.cgi?id=365797 --- Comment #7 from Buck Shockley <darkwingbuc...@gmail.com> --- I changed my display settings to force the problem to happen and this is the output: https://paste.kde.org/pr1fgg136 The very bottom line is, what I believe to be, the display changing. This is the output for the qdbus command: https://paste.kde.org/ppkhz0euu And this is the output for the glxinfo command: https://paste.kde.org/ppjm68tkt Both of the commands were run while the issue was occurring. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365797] Second monitor distorts when being adjusted
https://bugs.kde.org/show_bug.cgi?id=365797 --- Comment #5 from Buck Shockley <darkwingbuc...@gmail.com> --- (In reply to Martin Gräßlin from comment #4) > can you try to disable compositing with Alt+Shift+F12 when the problem > occurs? Does that fix the problem? No. When I changed my display settings to cause the problem, KDE notified me that compositing settings had been reset due to a change in configuration. Pressing Alt+Shift+F12 would make it so nothing on my screen was movable or even usable. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365797] Second monitor distorts when being adjusted
https://bugs.kde.org/show_bug.cgi?id=365797 --- Comment #3 from Buck Shockley <darkwingbuc...@gmail.com> --- Killing plasmashell doesn't work, the entire session has to be terminated. Output of kscreen-console bug: https://paste.kde.org/puowkrpni Output of kcmshell5 kcm_kscreen: https://paste.kde.org/pcl9lp8v6 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365797] Second monitor distorts when being adjusted
https://bugs.kde.org/show_bug.cgi?id=365797 --- Comment #2 from Buck Shockley <darkwingbuc...@gmail.com> --- Created attachment 100154 --> https://bugs.kde.org/attachment.cgi?id=100154=edit kscreen .local file -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 Buck Shockley <darkwingbuc...@gmail.com> changed: What|Removed |Added CC||darkwingbuc...@gmail.com --- Comment #16 from Buck Shockley <darkwingbuc...@gmail.com> --- I too have this bug, but do not have debug symbols (Arch Linux). (In reply to Martin Gräßlin from comment #11) > All the backtraces we have currently are lacking debug symbols. Could > someone please upload a backtrace with a backtrace with full debug symbols? > > Also could someone still hitting this problem paste the output of: > qdbus org.kde.KWin /KWin supportInformation This is my output: https://paste.kde.org/pfsvzyk54 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365797] New: Second monitor distorts when being adjusted
https://bugs.kde.org/show_bug.cgi?id=365797 Bug ID: 365797 Summary: Second monitor distorts when being adjusted Product: KScreen Version: 5.7.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: darkwingbuc...@gmail.com In Kscreen, trying to change the positioning, resolution, or nearly any setting of my secondary monitor causes the image displayed on the second monitor to be forcibly skewed, with the image of Plasma being stretched past the bounds of the monitor and black space is shown on the edges. If this happens, I have to end my session and log back in to Plasma to fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365311] Right-click menus appear above the task manager entry to the left of the clicked item
https://bugs.kde.org/show_bug.cgi?id=365311 --- Comment #2 from Buck Shockley <darkwingbuc...@gmail.com> --- (In reply to Eike Hein from comment #1) > Do you have the latest version of KF5? There were fixes to menu positoning. It would seem not, but the bug did not occur until updating to Plasma 5.7. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365311] New: Right-click menus appear above the task manager entry to the left of the clicked item
https://bugs.kde.org/show_bug.cgi?id=365311 Bug ID: 365311 Summary: Right-click menus appear above the task manager entry to the left of the clicked item Product: plasmashell Version: 5.7.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: darkwingbuc...@gmail.com CC: plasma-b...@kde.org When right-clicking on an entry in the task manager, the contextual menu will appear one item to the left of the item that was clicked on. When clicking the left-most item, the menu will appear on the monitor to the left in a dual-monitor setup. In the icon-only variant of the task manager, all menus will appear on the left monitor unless several windows are opened. Reproducible: Always Steps to Reproduce: 1. Open at least two windows. 2. Right click on one in the task manager. Actual Results: The application menu will appear to the left of its spot on the task manager. Expected Results: The application menu should open directly above its entry in the task manager. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356783] Text in Plasma tooltips sometimes becomes a series of smudgy blocks
https://bugs.kde.org/show_bug.cgi?id=356783 --- Comment #5 from Buck Shockley <darkwingbuc...@gmail.com> --- Created attachment 97925 --> https://bugs.kde.org/attachment.cgi?id=97925=edit Screenshot (showing both monitors) with the blocky text -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356783] Text in Plasma tooltips sometimes becomes a series of smudgy blocks
https://bugs.kde.org/show_bug.cgi?id=356783 Buck Shockley <darkwingbuc...@gmail.com> changed: What|Removed |Added CC||darkwingbuc...@gmail.com --- Comment #4 from Buck Shockley <darkwingbuc...@gmail.com> --- This also happens to me, but usually in the Menu as opposed to anywhere else. This is on the latest Nvidia drivers. -- You are receiving this mail because: You are watching all bug changes.
