[dolphin] [Bug 483172] Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 Mathias Hertlein changed: What|Removed |Added CC||m...@mh.cx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483162] Sometimes wrong window stacking stacking orders with NVIDIA and AMD GPUs
https://bugs.kde.org/show_bug.cgi?id=483162 Mathias Hertlein changed: What|Removed |Added CC||m...@mh.cx -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 Mathias changed: What|Removed |Added CC||mathias.baumgartinger@proto ||n.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482911] kernel: traps: kwin_wayland trap divide error ip:7483ca3c9321 sp:7ffdb043b9c0 error:0 in i965_dri.so
https://bugs.kde.org/show_bug.cgi?id=482911 --- Comment #4 from Mathias Rohnstock --- Thanks David, I've fixed the issue by switching from "mesa-amber" to "mesa", which will use "iris_dri.so" instead of "i965_dri.so". This should work for you Christoph, too. You can try "iris" by using the following command: MESA_LOADER_DRIVER_OVERRIDE=iris glxgears (make sure you have "mesa" package installed), in case you can see the spinning gears and no error get reported in console iris should work for you, too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482911] kernel: traps: kwin_wayland trap divide error ip:7483ca3c9321 sp:7ffdb043b9c0 error:0 in i965_dri.so
https://bugs.kde.org/show_bug.cgi?id=482911 --- Comment #2 from Mathias Rohnstock --- Created attachment 166861 --> https://bugs.kde.org/attachment.cgi?id=166861=edit journalctl -b from startup until first login attempt using wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482911] kernel: traps: kwin_wayland trap divide error ip:7483ca3c9321 sp:7ffdb043b9c0 error:0 in i965_dri.so
https://bugs.kde.org/show_bug.cgi?id=482911 Mathias Rohnstock changed: What|Removed |Added CC||m.rohnst...@googlemail.com --- Comment #1 from Mathias Rohnstock --- I've the same issue with my XPS 13 9343 Notebook after updating from Plasma 5.27.10 to 6.0.1. Same steps, same result - can't login using wayland (will return to SDDM after display a black screen with a prompt for about 10s), only X11 is working. Uploaded my journal log from startup until login attempt using wayland. Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.21-1-lts (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 5500 Manufacturer: Dell Inc. Product Name: XPS 13 9343 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #20 from Mathias Tillman --- Can confirm this when upgrading to 6.0 on the user branch. Looks like the whole /usr/share/dbus-1 directory is missing in the build66 package of plasma-workspace. It does exist in build65, however, so something must have happened in-between build66 and build65 that has caused it to not be included anymore. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 457006] Unable to install Calligra
https://bugs.kde.org/show_bug.cgi?id=457006 --- Comment #7 from Mathias Tillman --- (In reply to Jonathan Riddell from comment #6) > Calligra is not well maintained alas. However try now. Can confirm that it's fixed now - thanks for the quick resolution! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 457006] Unable to install Calligra
https://bugs.kde.org/show_bug.cgi?id=457006 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #5 from Mathias Tillman --- (In reply to Doug from comment #4) > I'm having this issue now with Testing. Getting a dependency resolution > fail error in Discover. > > when installing from the terminal: > > doug@testing:~$ sudo apt install calligra > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Starting pkgProblemResolver with broken count: 1 > Starting 2 pkgProblemResolver with broken count: 1 > Investigating (0) calligra-libs:amd64 < none -> > 1:3.2.1+p22.04+tstable+git20221007.0143-0 @un puN Ib > > Broken calligra-libs:amd64 Depends on calligra-data:amd64 < none | > 1:3.2.1+p22.04+tstable+git20221007.0143-0 @un uH > (>= > 1:3.2.1+p22.04+tstable+git20221007.0143-0) > Considering calligra-data:amd64 0 as a solution to calligra-libs:amd64 7 > Re-Instated calligra-data:amd64 > Broken calligra-libs:amd64 Depends on libkchart2:amd64 < none | 2.8.0-1 @un > uH > (>= 2.8.0+p22.04+tstable+git20220908.1010) > Broken calligra-libs:amd64 Depends on libm2mml0.0v5:amd64 < none | > 0.9.0-0ubuntu4 @un uH > > Considering libm2mml0.0v5:amd64 1 as a solution to calligra-libs:amd64 7 > Re-Instated libcauchy0.0v5:amd64 > Re-Instated libm2mml0.0v5:amd64 > Broken calligra-libs:amd64 Depends on libphonon4qt5experimental4:amd64 < > none | 4:4.12.0+p22.04+vstable+git20240117.0713-0 @un uH > (>= > 4:4.11.1+p22.04+tunstable+git20220919.0138) > Considering libphonon4qt5experimental4:amd64 0 as a solution to > calligra-libs:amd64 7 > Re-Instated libphonon4qt5experimental4:amd64 > Broken calligra-libs:amd64 Depends on libspnav0:amd64 < none | 0.2.3-1 @un > uH > (>= 0.2.2) > Considering libspnav0:amd64 0 as a solution to calligra-libs:amd64 7 > Re-Instated libspnav0:amd64 > Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > calligra-libs : Depends: libkchart2 (>= > 2.8.0+p22.04+tstable+git20220908.1010) but it is not going to be installed > Recommends: fonts-lyx but it is not going to be installed > Recommends: libqca2-plugins but it is not installable > Recommends: python but it is not installable > E: Unable to correct problems, you have held broken packages. Same here running the latest testing branch of Neon. It seems like on the unstable branch calligra-libs has changed the libkchart2 dependency to libkchart5-2, but on testing it's still libkchart2. This causes a dependency error since libkchart2 isn't updated by neon, whereas libkchart5-2 is. TLDR: The calligra-libs dependencies have to be changed to reference libkchart5-2 instead of libkchart2 on testing. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 479210] KRunner random crash
https://bugs.kde.org/show_bug.cgi?id=479210 --- Comment #4 from Mathias Kraus --- Don't know if it helps but I get this crash only on KDE Neon with Qt 6.6 but not on Arch with Qt 6.7. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 480166] New: krunner crashes on first use
https://bugs.kde.org/show_bug.cgi?id=480166
Bug ID: 480166
Summary: krunner crashes on first use
Classification: Plasma
Product: krunner
Version: unspecified
Platform: Neon
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: k.h...@gmx.de
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
Target Milestone: ---
Application: krunner (5.92.90)
Qt Version: 6.6.1
Frameworks Version: 5.249.0
Operating System: Linux 6.5.0-14-generic x86_64
Windowing System: Wayland
Distribution: KDE neon Testing Edition
DrKonqi: 5.92.90 [KCrashBackend]
-- Information about the crash:
I'm using Plasma 6 RC1 from KDE Neon. I updated from the user to the testing
repo and get this crashes on first use of some application, including krunner
but also similar crashes in the dolphin preview processes. It might be that my
system is corrupt or some old libraries lying around and are not updated yet.
The crash can be reproduced every time.
-- Backtrace:
Application: KRunner (krunner), signal: Segmentation fault
[KCrash Handler]
#4 QArrayDataPointer::deref() (this=0x0) at
./src/corelib/tools/qarraydatapointer.h:413
#5 QArrayDataPointer::~QArrayDataPointer() (this=0x0, this=) at ./src/corelib/tools/qarraydatapointer.h:102
#6 QList::~QList() (this=0x0, this=) at
./src/corelib/tools/qlist.h:70
#7 QtPrivate::QMetaTypeForType
>::getDtor()::{lambda(QtPrivate::QMetaTypeInterface const*,
void*)#1}::operator()(QtPrivate::QMetaTypeInterface const*, void*) const
(addr=0x0, __closure=0x0) at ./src/corelib/kernel/qmetatype.h:2438
#8 QtPrivate::QMetaTypeForType
>::getDtor()::{lambda(QtPrivate::QMetaTypeInterface const*,
void*)#1}::_FUN(QtPrivate::QMetaTypeInterface const*, void*) () at
./src/corelib/kernel/qmetatype.h:2437
#9 0x7fede1158e22 in QtWaylandClient::QWaylandWindow::createDecoration()
() at /usr/lib/x86_64-linux-gnu/libQt6WaylandClient.so.6
#10 0x7fedda8d168c in
QtWaylandClient::QWaylandGLContext::makeCurrent(QPlatformSurface*) () at
/usr/lib/x86_64-linux-gnu/libQt6WaylandEglClientHwIntegration.so.6
#11 0x7fede25d8b3e in QOpenGLContext::makeCurrent(QSurface*)
(this=0x7fed6001cd50, surface=0x78786760) at
./src/gui/kernel/qopenglcontext.cpp:661
#12 0x7fede25e3540 in QRhiGles2::ensureContext(QSurface*) const
(this=0x7fed6002c900, surface=0x78786760) at
./src/gui/rhi/qrhigles2.cpp:619
#13 0x7fede25eab2d in QRhiGles2::beginFrame(QRhiSwapChain*,
QFlags) (this=0x7fed6002c900, swapChain=0x7fed60172ad0)
at ./src/gui/rhi/qrhigles2.cpp:2028
#14 0x7fede24c1be6 in QRhi::beginFrame(QRhiSwapChain*,
QFlags) (this=0x7fed6002b470, swapChain=0x7fed60172ad0,
flags=...) at ./src/gui/rhi/qrhi.cpp:10146
#15 0x7fede3afbdff in () at /usr/lib/x86_64-linux-gnu/libQt6Quick.so.6
#16 0x7fede1d63f4d in operator() (__closure=) at
./src/corelib/thread/qthread_unix.cpp:324
#17 (anonymous
namespace)::terminate_on_exception >
(t=) at ./src/corelib/thread/qthread_unix.cpp:260
#18 QThreadPrivate::start(void*) (arg=0x5575dba981d0) at
./src/corelib/thread/qthread_unix.cpp:283
#19 0x7fede1294ac3 in start_thread (arg=) at
./nptl/pthread_create.c:442
#20 0x7fede1326850 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 32 (Thread 0x7fed43fff640 (LWP 3516) "krunner_kateses"):
#1 __GI___libc_read (fd=57, buf=0x7fed43ffe850, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2 0x7fede0686134 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fede06db19d in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fede06833e3 in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fede1d082e1 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fed4804edf0, flags=...) at
./src/corelib/kernel/qeventdispatcher_glib.cpp:395
#6 0x7fede1e6a01b in
QEventLoop::exec(QFlags) (this=0x7fed43ffea20,
flags=...) at ./src/corelib/global/qflags.h:34
#7 0x7fede1da1068 in QThread::exec() (this=) at
./src/corelib/global/qflags.h:74
#8 0x7fede1d63f4d in operator() (__closure=) at
./src/corelib/thread/qthread_unix.cpp:324
#9 (anonymous
namespace)::terminate_on_exception >
(t=) at ./src/corelib/thread/qthread_unix.cpp:260
#10 QThreadPrivate::start(void*) (arg=0x5575dbef5340) at
./src/corelib/thread/qthread_unix.cpp:283
#11 0x7fede1294ac3 in start_thread (arg=) at
./nptl/pthread_create.c:442
#12 0x7fede1326850 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 31 (Thread 0x7fed50bfe640 (LWP 3515) "unitconverter"):
#1 0x7fede06b5ef8 in g_thread_self () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fede06833d3 in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fede1d082e1 in
QEventDispatcherGlib::processEvents(QFlags)
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 --- Comment #20 from Mathias Tillman --- (In reply to Archisman Panigrahi from comment #18) > (In reply to Mathias Tillman from comment #13) > > Slight update: Seems that it doesn't like it when the width is smaller than > > the height (for a top or bottom panel) or vice-versa. The "magic" 88 pixels > > width in my previous comment was actually the same as the height - that's > > why it started working when I changed it to that. > > So I guess a simple solution would be to change the 1 pixel width/height to > > the height/width counterpart. > > How do you change this height? I could not find a file named > waylandinterface.cpp You can see what needs to be changed in the MR above: https://invent.kde.org/plasma/latte-dock/-/merge_requests/44 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438401] [Wayland] 3rd-party window decoration pixelatex/badly rendered when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=438401 --- Comment #16 from Mathias Tillman --- Was this fixed in one of the 5.27.X releases? It seems to work fine for me now on 5.27.2 anyhow. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466186] Closing VLC when a video is playing causes kwin assert error crash/restart
https://bugs.kde.org/show_bug.cgi?id=466186 Mathias Tillman changed: What|Removed |Added Summary|Closing VLC when a video is |Closing VLC when a video is |playing causes kwin wayland |playing causes kwin assert |assert error crash/restart |error crash/restart -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Both Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #21 from Mathias Tillman --- See https://invent.kde.org/plasma/kwin/-/merge_requests/3236 for a discussion about a potential fix for this issue. It does work for me, but there are some uncertainties about how to best approach it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466186] Closing VLC when a video is playing causes kwin wayland assert error crash/restart
https://bugs.kde.org/show_bug.cgi?id=466186 --- Comment #1 from Mathias Tillman --- Seems the crash also happens under X11, so it's not limited to just Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466186] New: Closing VLC when a video is playing causes kwin wayland assert error crash/restart
https://bugs.kde.org/show_bug.cgi?id=466186 Bug ID: 466186 Summary: Closing VLC when a video is playing causes kwin wayland assert error crash/restart Classification: Plasma Product: kwin Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: master.ho...@gmail.com Target Milestone: --- SUMMARY I'm experiencing a crash whenever I close VLC when a video is playing running kwin v5.27.0 (though I haven't tested earlier versions) on wayland. STEPS TO REPRODUCE 1. Play video through VLC 2. Close VLC 3. kwin wayland restarts OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Version === KWin version: 5.27.0 Qt Version: 5.15.8 Qt compile version: 5.15.8 XCB compile version: 1.14 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12201001 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.kwin.aurorae Theme: __aurorae__svg__Canta-light Plugin recommends border size: No onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 3, 4, 5 borderSize: 3 gridUnit: 10 font: Google Sans,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Output backend == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 1 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: true clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: true activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 2 glStrictBinding: false glStrictBindingFollowsDriver: true glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true latencyPolicy: renderTimeEstimator: allowTearing: 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 === Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: DP-1 Enabled: 1 Geometry: 0,0,2048x1152 Scale: 1.25 Refresh Rate: 143998 Adaptive Sync: incapable Screen 1: - Name: DP-2 Enabled: 1 Geometry: 2048,0,2048x1152 Scale: 1.25 Refresh Rate: 143998 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.49, 6.1.12-x64v1-xanmod1) OpenGL version string: 4.6 (Core Profile) Mesa 22.3.5 - kisak-mesa PPA OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: Unknown GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 22.3.5 Linux kernel version: 6.1.12 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- colorpicker outputlocator screenshot zoom kwin4_effect_logout kwin4_effect_sessionquit kwin4_effect_login slidingpopups kwin4_effect_translucency kwin4_effect_windowaperture slide kwin4_effect_squash kwin4_effect_maximize kwin4_effect_morphingpopups kwin4_effect_frozenapp kwin4_effect_fadingpopups kwin4_effect_fullscreen kwin4_effect_scale kwin4_effect_dialogparent
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #15 from Mathias Tillman --- @JonnyRobbie Do the lines go away of you disable the Blur effect? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #13 from Mathias Tillman --- Running a bisect the issue seems to be with https://invent.kde.org/plasma/kwin/-/commit/64e42bbd04e10e8b0c32bec444864ce7c64bbfc5 and that whole MR in fact. Maybe the blur code doesn't like the rounding ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #12 from Mathias Tillman --- Update: I think it may be related to the Blur effect, because I just tried turning that off and that seems to have made the lines disappear. Interestingly the lines also only appear when there's a semi-translucent window behind eg chrome or firefox. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438401] [Wayland] 3rd-party window decoration pixelatex/badly rendered when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=438401 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #10 from Mathias Tillman --- This also seems to happen on the recently released Plasma 5.27. Weirdly, for me, it doesn't appear on 150% scaling, but it does on 125%. If I change to 140% I get a horizontal line instead which appears at roughly the same place as the vertical bar when using 125%. Here's my output of the support info: == Version === KWin version: 5.27.0 Qt Version: 5.15.8 Qt compile version: 5.15.8 XCB compile version: 1.14 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12201001 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.kwin.aurorae Theme: __aurorae__svg__Canta-light Plugin recommends border size: No onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 3, 4, 5 borderSize: 3 gridUnit: 12 font: Google Sans,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 3 largeSpacing: 12 Output backend == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 1 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: true clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: true activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 2 glStrictBinding: false glStrictBindingFollowsDriver: true glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true latencyPolicy: renderTimeEstimator: allowTearing: 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 === Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: DP-1 Enabled: 1 Geometry: 0,0,2048x1152 Scale: 1.25 Refresh Rate: 143998 Adaptive Sync: incapable Screen 1: - Name: DP-2 Enabled: 1 Geometry: 2047,0,1766x994 Scale: 1.44922 Refresh Rate: 143998 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.49, 6.1.11-x64v1-xanmod1) OpenGL version string: 4.6 (Core Profile) Mesa 22.3.5 - kisak-mesa PPA OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: Unknown GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 22.3.5 X server version: 1.22.1 Linux kernel version: 6.1.11 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- colorpicker outputlocator screenshot zoom blur contrast kwin4_effect_logout kwin4_effect_sessionquit kwin4_effect_login slidingpopups kwin4_effect_translucency kwin4_effect_windowaperture slide kwin4_effect_squash kwin4_effect_maximize kwin4_effect_morphingpopups kwin4_effect_frozenapp kwin4_effect_fadingpopups kwin4_effect_fullscreen kwin4_effect_scale kwin4_effect_dialogparent desktopgrid highlightwindow overview tileseditor windowview blendchanges startupfeedback kscreen screentransform Currently Active Effects: - blur contrast Effect Settings: colorpicker: outputlocator: screenshot: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 focusTrackingEnabled: false textCaretTrackingEnabled: false focusDelay: 350
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #39 from Mathias Homann --- (In reply to Philippe Cloutier from comment #38) > Hum, thanks Mathias. But in that case, should this ticket be re-titled to be > more general (not specific to "/")? that is the weird bit - the popup usually complains about / even when / is on a SSD or NVMe and it's actually some /users/$USER or /shared/data that comes in via NFS and is dragging things down. Almost as if whatever is broken doesn't even notice that someting is mounted somewhere under /users/ or similar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Mathias Homann changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Mathias Homann changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #37 from Mathias Homann --- (In reply to Philippe Cloutier from comment #35) > (In reply to ManuelBoe from comment #34) > > The dialog described above appears when the file system is unusually slow. > > This may indicate that the hard disk is about to fail or may have other > > causes. > > This bug is unfortunately not limited to OSes hosted on HDDs. and not necessarily limited to the filesystem where the OS is installed either - in my case, $HOME and several network shares are NFS, and this bug gets triggered whenever the file server is under heavier load than usual - running AIDE, installing updates, etc. definitely NOT a "feature". a "feature" would be the option to limit whatever process fails with this message to local harddisks only. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 --- Comment #13 from Mathias Tillman --- Slight update: Seems that it doesn't like it when the width is smaller than the height (for a top or bottom panel) or vice-versa. The "magic" 88 pixels width in my previous comment was actually the same as the height - that's why it started working when I changed it to that. So I guess a simple solution would be to change the 1 pixel width/height to the height/width counterpart. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 --- Comment #12 from Mathias Tillman --- I have the same issue and I've managed to narrow the issue down to WaylandInterface::setViewStruts in app/wm/waylandinterface.cpp. The issue seems to be that the ghost window has a width (or height) of 1 pixel, and that causes it to be (I'm guessing) ignored by the wm. If I change the w->setGeometry call to use the full rect it works properly. I did some further testing, and for me the "magic" value that causes it to work is if I set the width to 88 pixels - any less than that and it won't work. Anyone know the reason for it not using the full rect for the ghost window? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 464784] New: Spectacle captures random images in a NVIDIA Prime offset rendering setup
https://bugs.kde.org/show_bug.cgi?id=464784 Bug ID: 464784 Summary: Spectacle captures random images in a NVIDIA Prime offset rendering setup Classification: Applications Product: Spectacle Version: 22.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: mathias.hom...@opensuse.org CC: k...@david-redondo.de Target Milestone: --- SUMMARY I'm using spectacle in a setup with the intel driver as primary, and a nvidia card through prime render offsetting. I have spectacle bound to the printscreen key. When I try capturing a screenshot of an "offloaded" openGL app (any game or the likes) spectacle sometimes (about half of the time) captures not the game but some other window that is also on screen. STEPS TO REPRODUCE 1. Set up a laptop with intel and nvidia prime offset redering 2. run any openGL app / game 3. try catching a screenshot of the game. OBSERVED RESULT spectacle catches a screenshot of one of the running windows but not necessarily the one running in foreground EXPECTED RESULT spectacle should take a screenshot of what is on my screen, not of what other windows would look like if they were still running in the foreground ADDITIONAL INFO SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION mathias@mio:~> inxi -G Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] driver: nvidia v: 525.85.05 Device-3: Acer HD Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 driver: X: loaded: intel,modesetting unloaded: nvidia dri: i965 gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel Xe Graphics (TGL GT2) mathias@mio:~> gamemoderun inxi -G gamemodeauto: gamemodeauto: gamemodeauto: Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] driver: nvidia v: 525.85.05 Device-3: Acer HD Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 driver: X: loaded: intel,modesetting unloaded: nvidia dri: i965 gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6.0 NVIDIA 525.85.05 renderer: NVIDIA GeForce GTX 1650 Ti with Max-Q Design/PCIe/SSE2 mathias@mio:~> Operating System: openSUSE Tumbleweed 20230123 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Prestige 14 A11SCS System Version: REV:1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 Mathias Johansson changed: What|Removed |Added CC||mathias9...@gmail.com --- Comment #20 from Mathias Johansson --- I ran into these issues (low fps on external monitor and high CPU usage when moving mouse under wayland) on my Nvidia laptop (fedora 37, KDE 5.26, Nvidia drivers v525.78, linux 6.1, i5-7300hq + GTX 1060) and after git-bisecting through different commits I landed on the aforementioned 68a54a67 "backends/drm: enable format modifiers by default" commit. When I added "KWIN_DRM_USE_MODIFIERS=0" to my /etc/environment file the lag actually did go away. (Although kwin_wayland's CPU usage does still increase up to 40% when I move my mouse on the external monitor). -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 289515] the /media command sends the song data twice
https://bugs.kde.org/show_bug.cgi?id=289515 --- Comment #6 from Mathias Homann --- Now i actually installed and tried kopete: - still broken to the point of being unusable - /media command isn't even around anymore. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 289515] the /media command sends the song data twice
https://bugs.kde.org/show_bug.cgi?id=289515 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #5 from Mathias Homann --- I have stopped using kopete when it became broken to the point of being unusable, and that was almost 10 years ago. since then there has been almost no noticeable work on kopete. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 267536] clicking the "chat" button in the "soanso came online" notification doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=267536 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Mathias Homann --- Now there are no "soandso is online" notifications anymore... so technically I can't verify this anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462512] [NVIDIA] Missing sensor information after driver update
https://bugs.kde.org/show_bug.cgi?id=462512 --- Comment #7 from Mathias Homann --- I don't think it is - the GPU sensors are there, they just return nothing but zeros. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450947] Load averages in System Monitor are not rounded or truncated
https://bugs.kde.org/show_bug.cgi?id=450947 Mathias Homann changed: What|Removed |Added Attachment #154300|Anothre screenshot showing |Another screenshot showing description|how this can lead to|how this can lead to |unusable widgets... |unusable widgets... -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450947] Load averages in System Monitor are not rounded or truncated
https://bugs.kde.org/show_bug.cgi?id=450947 --- Comment #5 from Mathias Homann --- Personally, I don't think having more than two digits after the dot on a Loadaverage display would give any meaningful information. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450947] Load averages in System Monitor are not rounded or truncated
https://bugs.kde.org/show_bug.cgi?id=450947 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #4 from Mathias Homann --- Created attachment 154300 --> https://bugs.kde.org/attachment.cgi?id=154300=edit Anothre screenshot showing how this can lead to unusable widgets... -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 400124] kopete does not automatically log in to my messenger accounts even though it is configured to do so
https://bugs.kde.org/show_bug.cgi?id=400124 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Mathias Homann --- yep, still reproduces. is kopete even still maintained? -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 400125] kopete does not save / restore the UI settings (hide menu, small toolbar icons w/o text, etc)
https://bugs.kde.org/show_bug.cgi?id=400125 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Mathias Homann --- yep, still reproduces. is kopete even still maintained? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 422853] Unable to reboot or shutdown the system when logged in with a networked user
https://bugs.kde.org/show_bug.cgi?id=422853 --- Comment #2 from Mathias Homann --- has not happened for quite some time now, and my underlying infrastructure has changed a lot by now. If noone else still reproduces this it can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462024] New: Unable to read stats of my NVidia card
https://bugs.kde.org/show_bug.cgi?id=462024 Bug ID: 462024 Summary: Unable to read stats of my NVidia card Classification: Plasma Product: plasma-systemmonitor Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY Since a few days system monitor doesn't display the stats of my GTX1050 anymore STEPS TO REPRODUCE 1. Create a sheet (or a desktop widget) that monitors something off the nvidia card, i.e. GPU 1 Temperature OBSERVED RESULT The monitor shows 0°C EXPECTED RESULT It should show the actual temperature as shown by nvidia-smi SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221117 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.8-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION NVIDIA Driver version is 525.53 and ... "it used to work", until some recent update... -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 381159] No support for direct messages longer than 160 characters
https://bugs.kde.org/show_bug.cgi?id=381159 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Mathias Homann --- to be honest, right now it looks as if direct messages dont work at all - I just sent two from my account to another test account, one of 150 and ones of 280 characters - neither of them show in neither of the two accounts when I use the website to look for them. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461540] New: Choqok does not store the "read state" of tweets anymore
https://bugs.kde.org/show_bug.cgi?id=461540 Bug ID: 461540 Summary: Choqok does not store the "read state" of tweets anymore Classification: Applications Product: choqok Version: 1.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: scarp...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Choqok does not store the "read state" of tweets anymore STEPS TO REPRODUCE 1. quit chocok with no unread tweets 2. start choqok again 3. notice how there are loads of "new" tweets again, including mentions and DMs from months ago. OBSERVED RESULT I see old tweets and mentions as "unread" even when they are months old after restarting choqok EXPECTED RESULT I expect tweets and DMs to "stay read" once I've seen them. SOFTWARE/OS VERSIONS Windows: 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.
[okular] [Bug 461511] Presentation mode always goes to the next page after 5 seconds no matter what is set in preferences
https://bugs.kde.org/show_bug.cgi?id=461511 --- Comment #1 from Mathias Homann --- oh by the way just in case it depends on the PDF file: here's the link to the one that I'm having trouble with https://www.deviantart.com/stjepan-sejic/art/Fine-print-book-1-complete-pdf-935744275 Careful tho, you might consider that PDF NSFW. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461511] New: Presentation mode always goes to the next page after 5 seconds no matter what is set in preferences
https://bugs.kde.org/show_bug.cgi?id=461511 Bug ID: 461511 Summary: Presentation mode always goes to the next page after 5 seconds no matter what is set in preferences Classification: Applications Product: okular Version: 22.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY When I use okular in presentation mode it always goes to the next page after about 5 seconds even when I turn "auto advance" off in preferences, or set it to a much longer delay STEPS TO REPRODUCE 1. open any supported file 2. start presentation mode 3. notice how the presentation advances after 5 seconds no matter what you do OBSERVED RESULT see above EXPECTED RESULT If I disable "auto advance" I expect it not to auto advance. If I set the delay to 60 seconds I expect the presentation to run at 60 seconds per slide, not 5. SOFTWARE/OS VERSIONS Windows: 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.
[systemsettings] [Bug 392748] kdeinit crashes at start
https://bugs.kde.org/show_bug.cgi?id=392748 Mathias Bavay changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392748] kdeinit crashes at start
https://bugs.kde.org/show_bug.cgi?id=392748 Mathias Bavay changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460658] New: Second Display won't work after update
https://bugs.kde.org/show_bug.cgi?id=460658 Bug ID: 460658 Summary: Second Display won't work after update Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mat8ni...@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. Update your system 2. 3. OBSERVED RESULT The second display I have won't work in KDE Plasma, only in SDDM. EXPECTED RESULT The second display will work as intended. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Hello! I have recently been having a problem with my second display, after I updated my system. When I log-in from sddm, the display goes to no signal prompt. I have found a temporary fix, and that is to delete the ~/.local/share/kscreen/ and then restart the system. Then the display works perfect, but after a little time, the fix stops working, and I have to do it again. System Logs: Hardware Information: https://clbin.com/g7B0O Boot Log: https://clbin.com/DXWN4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392748] kdeinit crashes at start
https://bugs.kde.org/show_bug.cgi?id=392748 --- Comment #9 from Mathias Bavay --- With version 5.18.8, this bug seems to be gone (I've never experience it on this version) -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 252359] Kompare could not parse some patch files
https://bugs.kde.org/show_bug.cgi?id=252359 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #19 from Mathias Homann --- There are still cases when kompare chokes on a diff - mainly when there's non-english errors embedded in it. but that's just a question of what options to pass to the diff command. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 326646] Password to unlock the kde wallet should not time out so fast
https://bugs.kde.org/show_bug.cgi?id=326646 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Mathias Homann --- ... can't you automatically close stuff that is for KDE4... -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Mathias Homann changed: What|Removed |Added Version|5.10.3 |5.21.1 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Mathias Homann --- does not reproduce anymore. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #48 from Mathias Homann --- 4 years old. this bug has disappeared and resurfaced many times since then, most likely different reasons each time. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #20 from Mathias Homann --- Bugs like this one keep disappearing and reappearing. TWO years later this specific occurence is most likely long gone. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460004] New: Dolphin crashes when unmounting external hard drive
https://bugs.kde.org/show_bug.cgi?id=460004 Bug ID: 460004 Summary: Dolphin crashes when unmounting external hard drive Classification: Applications Product: dolphin Version: 22.08.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: m...@mathias-renner.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.08.1) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-48-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I unmounted my external hard drive, which is LUKS encrypted, and dolphin crashed immediately. I did not try again, but this should not happen. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 1818799] [New LWP 1819103] [New LWP 1819205] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f04de6e199f in __GI___poll (fds=0x7fff6abf9278, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f04d9c6e640 (LWP 1818787))] Thread 4 (Thread 0x7f04bf7fe700 (LWP 1819205)): #0 __GI___libc_read (nbytes=16, buf=0x7f04bf7fd9d0, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=28, buf=0x7f04bf7fd9d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f04dc6feb2f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f04dc6b5ebe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f04dc6b6312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f04dc6b64a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f04decb2b9b in QEventDispatcherGlib::processEvents (this=0x7f04ac000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f04dec56b3b in QEventLoop::exec (this=this@entry=0x7f04bf7fdbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f04dea70342 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f04dea71543 in QThreadPrivate::start (arg=0x55aef273ee80) at thread/qthread_unix.cpp:330 #10 0x7f04dd10f609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f04de6ee133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f04d09c4700 (LWP 1819103)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55aef27d8628) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55aef27d85d8, cond=0x55aef27d8600) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55aef27d8600, mutex=0x55aef27d85d8) at pthread_cond_wait.c:647 #3 0x7f04d0e1a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f04d0e1a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f04dd10f609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f04de6ee133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f04d8e1d700 (LWP 1818799)): #0 0x7f04de6e199f in __GI___poll (fds=0x7f04d4016260, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f04dc6b636e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f04dc6b64a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f04decb2b9b in QEventDispatcherGlib::processEvents (this=0x7f04d4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f04dec56b3b in QEventLoop::exec (this=this@entry=0x7f04d8e1cbb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f04dea70342 in QThread::exec (this=this@entry=0x7f04dfd9bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f04dfd17f4b in QDBusConnectionManager::run (this=0x7f04dfd9bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7f04dea71543 in QThreadPrivate::start (arg=0x7f04dfd9bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:330 #8 0x7f04dd10f609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f04de6ee133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f04d9c6e640 (LWP 1818787)): [KCrash Handler] #4 0x55aef05a1087 in TerminalPanel::sendCdToTerminal (this=this@entry=0x55aef26efbb0, dir=..., addToHistory=addToHistory@entry=
[kontact] [Bug 416136] kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=416136 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Mathias Homann --- right now this does not reproduce. Operating System: openSUSE Tumbleweed 20221003 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 458058] New: ktorrent crashes when a magnet "data download" is done and the actual torrent starts
https://bugs.kde.org/show_bug.cgi?id=458058 Bug ID: 458058 Summary: ktorrent crashes when a magnet "data download" is done and the actual torrent starts Product: ktorrent Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: ktorrent (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I'm trying to get some downloads started, but when the "magnet process" is done and the actual torrent starts, ktorrent crashes, and when I restart it, the torrent AND the magnet download are both active, leading to the same crash in a few seconds. repeat ad nauseam. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault [KCrash Handler] #4 0x7fde0c525d7f in kt::MagnetManager::update (this=0x561c9f6819d0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/libktcore/torrent/magnetmanager.cpp:339 #5 0x561c9e903efa in kt::Core::update (this=0x561c9f64ead0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:900 #6 0x7fde0a512e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffd5f3cd0e0, r=0x561c9f64ead0, this=0x561c9f680df0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x561c9f64eaf8, signal_index=3, argv=0x7ffd5f3cd0e0) at kernel/qobject.cpp:3886 #8 0x7fde0a50c22f in QMetaObject::activate (sender=, m=m@entry=0x7fde0a7b39a0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd5f3cd0e0) at kernel/qobject.cpp:3946 #9 0x7fde0a516aca in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #10 0x7fde0a50757d in QObject::event (this=0x561c9f64eaf8, e=0x7ffd5f3cd230) at kernel/qobject.cpp:1336 #11 0x7fde0b1a541e in QApplicationPrivate::notify_helper (this=, receiver=0x561c9f64eaf8, e=0x7ffd5f3cd230) at kernel/qapplication.cpp:3637 #12 0x7fde0a4dbfb8 in QCoreApplication::notifyInternal2 (receiver=0x561c9f64eaf8, event=0x7ffd5f3cd230) at kernel/qcoreapplication.cpp:1064 #13 0x7fde0a532851 in QTimerInfoList::activateTimers (this=0x561c9f3dd3a0) at kernel/qtimerinfo_unix.cpp:643 #14 0x7fde0a5330e4 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #15 0x7fde085bfea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7fde085c0258 in ?? () from /lib64/libglib-2.0.so.0 #17 0x7fde085c02ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7fde0a533456 in QEventDispatcherGlib::processEvents (this=0x561c9f3e8840, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x7fde0a4daa2b in QEventLoop::exec (this=this@entry=0x7ffd5f3cd470, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #20 0x7fde0a4e2b96 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #21 0x561c9e8f82b9 in main (argc=, argv=) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/main.cpp:253 [Inferior 1 (process 7454) detached] The reporter indicates this bug may be a duplicate of or related to bug 458057, bug 396727. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 458057] New: Crash when a magnet torrent starts
https://bugs.kde.org/show_bug.cgi?id=458057 Bug ID: 458057 Summary: Crash when a magnet torrent starts Product: ktorrent Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: ktorrent (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I have started a magnet "download" to start a torrent, when I close the "download to" popup to actually get started ktorrent crashes. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault [KCrash Handler] #4 0x7f9088c98d74 in QListData::at (i=, this=) at /usr/include/qt5/QtCore/qlist.h:117 #5 QList::at (i=, this=) at /usr/include/qt5/QtCore/qlist.h:572 #6 kt::MagnetManager::update (this=0x55d2409ef4c0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/libktcore/torrent/magnetmanager.cpp:339 #7 0x55d23eaf9efa in kt::Core::update (this=0x55d2409b3580) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:900 #8 0x7f9086b12e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffe1d06bbf0, r=0x55d2409b3580, this=0x55d2409ee8e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x55d2409b35a8, signal_index=3, argv=0x7ffe1d06bbf0) at kernel/qobject.cpp:3886 #10 0x7f9086b0c22f in QMetaObject::activate (sender=, m=m@entry=0x7f9086db39a0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe1d06bbf0) at kernel/qobject.cpp:3946 #11 0x7f9086b16aca in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #12 0x7f9086b0757d in QObject::event (this=0x55d2409b35a8, e=0x7ffe1d06bd40) at kernel/qobject.cpp:1336 #13 0x7f90877a541e in QApplicationPrivate::notify_helper (this=, receiver=0x55d2409b35a8, e=0x7ffe1d06bd40) at kernel/qapplication.cpp:3637 #14 0x7f9086adbfb8 in QCoreApplication::notifyInternal2 (receiver=0x55d2409b35a8, event=0x7ffe1d06bd40) at kernel/qcoreapplication.cpp:1064 #15 0x7f9086b32851 in QTimerInfoList::activateTimers (this=0x55d240754860) at kernel/qtimerinfo_unix.cpp:643 #16 0x7f9086b330e4 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #17 0x7f9084dbfea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f9084dc0258 in ?? () from /lib64/libglib-2.0.so.0 #19 0x7f9084dc02ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f9086b33456 in QEventDispatcherGlib::processEvents (this=0x55d2407566a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f9086adaa2b in QEventLoop::exec (this=this@entry=0x7ffe1d06bf80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f90879ad3a7 in QDialog::exec (this=this@entry=0x7ffe1d06c110) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x55d23eafd536 in kt::FileSelectDlg::execute (location_hint=..., skip_check=0x7ffe1d06c06e, start=0x7ffe1d06c06f, tc=0x55d240f292b0, this=0x7ffe1d06c110) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/dialogs/fileselectdlg.cpp:156 #24 kt::Core::init (this=, tc=, group=..., location=..., silently=) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:235 #25 0x55d23eafdd23 in kt::Core::loadFromData (this=0x55d2409b3580, data=..., dir=..., group=..., silently=, url=...) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:320 #26 0x55d23eaff29f in kt::Core::load (this=0x55d2409b3580, data=..., url=..., group=..., savedir=...) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:469 #27 0x55d23eafb8fb in kt::Core::onMetadataDownloaded (this=0x55d2409b3580, mlink=..., data=..., options=...) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:1236 #28 0x7f9086b07760 in QObject::event (this=0x55d2409b3580, e=0x55d2418e6770) at kernel/qobject.cpp:1314 #29 0x7f90877a541e in QApplicationPrivate::notify_helper (this=, receiver=0x55d2409b3580, e=0x55d2418e6770) at kernel/qapplication.cpp:3637 #30 0x7f9086adbfb8 in QCoreApplication::notifyInternal2 (receiver=0x55d2409b3580, event=0x55d2418e6770) at kernel/qcoreapplication.cpp:1064 #31 0x7f9086adef51 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55d240662040) at kernel/qcoreapplication.cpp:1821 #32 0x7f9086b33c53 in postEventSourceDispatch (s=0x55d2407473c0) at kernel/qeventdispatcher_glib.cpp:277 #33 0x7f9084dbfea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #34 0x7f9084dc0258 in ?? () from
[kontact] [Bug 457958] New: crash on close
https://bugs.kde.org/show_bug.cgi?id=457958 Bug ID: 457958 Summary: crash on close Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.20.3 (22.04.3)) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I closed knotact with ctrl-q and it crashed. Didn't see if it happens all the time. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7face2b7d444 in QTabWidget::count() const (this=0x55b0692fced0) at widgets/qtabwidget.cpp:1212 #5 0x7fac5d60f56f in MessageList::Pane::PanePrivate::updateTabControls() () at /lib64/libKF5MessageList.so.5 #6 0x7face1d12e6f in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x77917340, r=0x55b066407c20, this=0x55b0665d04f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x55b0665ee7a0, signal_index=3, argv=0x77917340) at kernel/qobject.cpp:3886 #8 0x7face1896678 in KCoreConfigSkeleton::save() (this=0x55b0665ee7a0) at /usr/src/debug/kconfig-5.96.0-1.1.x86_64/src/core/kcoreconfigskeleton.cpp:1245 #9 0x7fac5d5bd058 in () at /lib64/libKF5MessageList.so.5 #10 0x7fac5d5bd516 in () at /lib64/libKF5MessageList.so.5 #11 0x7fac5d5e94e8 in () at /lib64/libKF5MessageList.so.5 #12 0x7fac5d617519 in MessageList::Widget::~Widget() () at /lib64/libKF5MessageList.so.5 #13 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066345780) at kernel/qobject.cpp:2104 #14 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0663d72d0, __in_chrg=) at kernel/qwidget.cpp:1522 #15 0x7face2b59f89 in QStackedWidget::~QStackedWidget() (this=0x55b0663d72d0, __in_chrg=) at widgets/qstackedwidget.cpp:147 #16 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b0664227f0) at kernel/qobject.cpp:2104 #17 0x7face29e2666 in QWidget::~QWidget() (this=0x55b066407c20, __in_chrg=) at kernel/qwidget.cpp:1522 #18 0x7fac5d97c6bd in CollectionPane::~CollectionPane() (this=0x55b066407c20, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/widgets/collectionpane.cpp:24 #19 CollectionPane::~CollectionPane() (this=0x55b066407c20, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/widgets/collectionpane.cpp:24 #20 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066378410) at kernel/qobject.cpp:2104 #21 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0666f9a90, __in_chrg=) at kernel/qwidget.cpp:1522 #22 0x7face2b55229 in QSplitter::~QSplitter() (this=0x55b0666f9a90, __in_chrg=) at widgets/qsplitter.cpp:979 #23 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066698130) at kernel/qobject.cpp:2104 #24 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0666f9a50, __in_chrg=) at kernel/qwidget.cpp:1522 #25 0x7face2b55229 in QSplitter::~QSplitter() (this=0x55b0666f9a50, __in_chrg=) at widgets/qsplitter.cpp:979 #26 0x7fac5d9c8cf3 in KMMainWidget::deleteWidgets() (this=this@entry=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:987 #27 0x7fac5d9cb9f6 in KMMainWidget::destruct() (this=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:395 #28 KMMainWidget::destruct() (this=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:384 #29 0x7facb8621c1f in KMailPart::~KMailPart() (this=0x55b0662d4640, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmail_part.cpp:89 #30 0x7facb8621d69 in KMailPart::~KMailPart() (this=0x55b0662d4640, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmail_part.cpp:92 #31 0x7face33468fe in KontactInterface::Plugin::~Plugin() (this=this@entry=0x55b0662d06b0, __vtt_parm=__vtt_parm@entry=0x7fac5dfa1b30 , this=, __vtt_parm=) at /usr/src/debug/kontactinterface-22.04.3-1.1.x86_64/src/plugin.cpp:74 #32 0x7fac5df8ed11 in KMailPlugin::~KMailPlugin() (this=0x55b0662d06b0, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kontactplugin/kmail/kmail_plugin.cpp:145 #33 0x7fac5df8ed49 in KMailPlugin::~KMailPlugin() (this=0x55b0662d06b0, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kontactplugin/kmail/kmail_plugin.cpp:145 #34 0x7face337b59e in qDeleteAll::const_iterator>(QList::const_iterator, QList::const_iterator) (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320 #35 qDeleteAll >(QList
[kalendar] [Bug 457941] New: calandar notifications still crashing
https://bugs.kde.org/show_bug.cgi?id=457941 Bug ID: 457941 Summary: calandar notifications still crashing Product: kalendar Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: mathias.hom...@opensuse.org CC: c...@carlschwan.eu Target Milestone: --- Application: kalendarac (5.20.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: still the same: i dismiss a calendar notification and i get drkonqi. The crash can be reproduced sometimes. -- Backtrace: Application: Erinnerungen (kalendarac), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=, this=, this=, __m=) at /usr/include/c++/12/bits/atomic_base.h:486 #5 QAtomicOps::loadRelaxed (_q_value=..., _q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x7f1ed25cd954) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #7 QWeakPointer::internalData (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:698 #8 QPointer::data (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qpointer.h:77 #9 QPointer::operator KNotification* (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qpointer.h:83 #10 AlarmNotification::~AlarmNotification (this=, this=) at /usr/src/debug/akonadi-calendar-22.04.3-1.1.x86_64/reminder-daemon/alarmnotification.cpp:23 #11 KalendarAlarmClient::dismiss (this=0x7ffc13c67720, notification=0x5625eff302b0) at /usr/src/debug/akonadi-calendar-22.04.3-1.1.x86_64/reminder-daemon/kalendaralarmclient.cpp:120 #12 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66ce0, r=0x7ffc13c67720, this=0x5625eff2b4b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x5625eff7c650, signal_index=9, argv=0x7ffc13c66ce0) at kernel/qobject.cpp:3886 #14 0x7f1bc410c22f in QMetaObject::activate (sender=sender@entry=0x5625eff7c650, m=m@entry=0x7f1bc50ec6a0, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #15 0x7f1bc50b4903 in KNotification::closed (this=this@entry=0x5625eff7c650) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotification.cpp:582 #16 0x7f1bc50b7817 in KNotification::textChanged (this=0x5625eff7c650) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/src/knotification.cpp:358 #17 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66e10, r=0x7f1bc50ee060 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, this=0x5625effacb20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate (sender=0x5625effad9a0, signal_index=3, argv=0x7ffc13c66e10) at kernel/qobject.cpp:3886 #19 0x7f1bc410c22f in QMetaObject::activate (sender=, m=m@entry=0x7f1bc50ec620 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc13c66e10) at kernel/qobject.cpp:3946 #20 0x7f1bc50b4aef in KNotificationPlugin::finished (this=, _t1=) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotificationplugin.cpp:173 #21 0x7f1bc50cb891 in NotifyByPopup::onNotificationClosed (this=0x5625effad9a0, dbus_id=, reason=3) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/src/notifybypopup.cpp:150 #22 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66fe0, r=0x5625effad9a0, this=0x5625effaf1b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x5625effad9d8, signal_index=5, argv=0x7ffc13c66fe0) at kernel/qobject.cpp:3886 #24 0x7f1bc410c22f in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffc13c66fe0) at kernel/qobject.cpp:3946 #25 0x7f1bc50d7599 in OrgFreedesktopNotificationsInterface::NotificationClosed (_t2=, _t1=, this=) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:287 #26 OrgFreedesktopNotificationsInterface::qt_static_metacall (_o=_o@entry=0x5625effad9d8, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7ffc13c67130) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:148 #27 0x7f1bc50d7f83 in OrgFreedesktopNotificationsInterface::qt_metacall (this=0x5625effad9d8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7ffc13c67130) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:242 #28 0x7f1bc4b6056b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=...,
[digikam] [Bug 457594] The facesengine binary should be installed to AppData\Local and not AppData\Roaming
https://bugs.kde.org/show_bug.cgi?id=457594 --- Comment #3 from Mathias --- I don’t know of a precise documentation except about the intent to roam the data (kind of obvious). Regarding the iPhone backups, I guess this is consistent because these backups are user data that can’t be regenerated easily, so syncing them to the network makes sense. The facesengine files on the other hand are more like a part of the digiKam setup (they are not changed by the software, they are more "the application" than "application data" if this makes sense). And softwares are usually installed to AppData\Local (see Atom editor, Chrome, MS Store apps, and all these softwares that no longer ask where they should be installed). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457594] New: The facesengine binary should be installed to AppData\Local and not AppData\Roaming
https://bugs.kde.org/show_bug.cgi?id=457594 Bug ID: 457594 Summary: The facesengine binary should be installed to AppData\Local and not AppData\Roaming Product: digikam Version: 7.7.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: math...@kende.fr Target Milestone: --- STEPS TO REPRODUCE 1. Do a fresh install of DigiKam 7.7.0 on MS Windows 2. Start the software OBSERVED RESULT A popup window opens to download the facesengine binaries, saying that it’s a large file (>300MB) and that it will be installed to C:\Users\TheUser\AppData\Roaming\digikam\facesengine EXPECTED RESULT The facesengine files should be installed in the AppData\Local folder instead of AppData\Roaming as the Roaming folder is meant for (small) user-generated files that will be synced to other computers on a network while the facesengine files can easily be re-downloaded if they are missing. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #34 from Mathias --- (In reply to Felix Ernst from comment #33) > (In reply to Mathias from comment #31) > > I've been using 1) single-click and 2) split screens in 3) detailed list > > view for ages, > It seems like people with this combination are disrupted the most by the > full row activation area. Full ack. And there's a pattern here I guess. In this setup you have the most information per square inch, control, speed and flexibility in sorting etc. It is not only about the probably amusing fact that people like me are used to a Midnight (or Norton;)) Commander style, detailed-listed, split view since the days before graphical UIs became common. It is about productivity. Same thing with single click: Twice as fast ;) I sincerely hope KDE and Dolphin keeps us in mind in the development. Because this is great software I am very thankful for. > > and I use the navigation buttons (up and back) > Clicking "Up" can be replaced by clicking the enclosing folder in the > location bar Not if you are using an editable location bar, like me (but this is probably something where you could actually get me to change a behaviour, because it is only one click away to switch to a clickable folder hierarchy). > I always click the "Back" button on my mouse to go "Back" without having to > change the active view first. But not everyone does this or has such mouse > side buttons so changing the active view first is necessary for many users. In fact, I do have these side buttons under my thumb and use them a lot. > > or the mouse controls a lot to navigate through my folder structure. > Not quite sure what you mean. Mouse controls work without changing the > active view first so this shouldn't have become any more difficult. I mean exactly the side button of the mouse you mentioned. And yes, I do not have to change the active view in this case because the mouse-back-button always affects the view pane that is under the cursor. Which is great and perfectly intuitive. But still: on a laptop with a touchpad but without multi-button-mouse dolphin's back-button is still needed - along with an easy way to change the active view of a split screen. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #31 from Mathias --- Another usage scenario that cries for making the old behaviour at least available as an option again: I've been using 1) single-click and 2) split screens in 3) detailed list view for ages, and I use the navigation buttons (up and back) or the mouse controls a lot to navigate through my folder structure. And for doing that I need to change focus between the two split lists a lot. And I switch between the two lists by clicking in empty areas - the biggest ones are usually those after the filenames. The small empty column at the start is - too small. So please make it an option if you don't like to revert to the old behaviour. Until this change Dolphin was such a great file manager. (Switch to double-click is not an option, than I could have stayed with Windows 25 years ago ;)) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 Mathias changed: What|Removed |Added CC||math...@public-ip.org -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 --- Comment #7 from Mathias Homann --- Created attachment 150864 --> https://bugs.kde.org/attachment.cgi?id=150864=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.5 still crashing every time I dismiss a notification. My calendar data comes from a nextcloud if that makes any difference. -- Backtrace (Reduced): #4 _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at /usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000 #5 simdEncodeAscii (end=, src=, nextAscii=, dst=) at codecs/qutfcodec.cpp:90 #6 QUtf8::convertFromUnicode (uc=, len=32617) at codecs/qutfcodec.cpp:383 #7 0x7f69fa97bd95 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5380 #8 QString::toUtf8_helper (str=...) at text/qstring.cpp:5372 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 --- Comment #3 from Mathias Homann --- Created attachment 150576 --> https://bugs.kde.org/attachment.cgi?id=150576=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.5 reminder crashes when dismissing a notification. -- Backtrace (Reduced): #4 _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at /usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000 #5 simdEncodeAscii (end=, src=, nextAscii=, dst=) at codecs/qutfcodec.cpp:90 #6 QUtf8::convertFromUnicode (uc=, len=21892) at codecs/qutfcodec.cpp:383 #7 0x7f791997bd95 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5380 #8 QString::toUtf8_helper (str=...) at text/qstring.cpp:5372 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 214950] New tool exp-floattrap
https://bugs.kde.org/show_bug.cgi?id=214950 --- Comment #15 from Mathias Fröhlich --- Good morning, I am still alive, and I am still using this tool every now and then for my own simulator stuff. Yes. I think that it is still useful, nevertheless, I hear that we are the minority here. I have not forward ported the patch for some time. The basic idea is to insert nan and inf checks at every floating point operation. So if you want to do that feel free. I can may be assist to grab the basic idea, but I have as of today not enough time to forward port in the near future. best Mathias -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] New: Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 Bug ID: 456157 Summary: Crash on dismissing a reminder Product: kalendar Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: mathias.hom...@opensuse.org CC: c...@carlschwan.eu Target Milestone: --- Application: kalendarac (5.20.2) Qt Version: 5.15.2 Frameworks Version: 5.95.0 Operating System: Linux 5.18.6-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.1 [KCrashBackend] -- Information about the crash: The reminder app crashed when I dismissed a reminder that I already had dismissed on a different device (calendar event is in a webdav calendar) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Erinnerungen (kalendarac), signal: Segmentation fault [KCrash Handler] #4 _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at /usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000 #5 simdEncodeAscii (end=, src=, nextAscii=, dst=) at codecs/qutfcodec.cpp:90 #6 QUtf8::convertFromUnicode (uc=, len=32570) at codecs/qutfcodec.cpp:383 #7 0x7f3b0d37bc75 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5376 #8 QString::toUtf8_helper (str=...) at text/qstring.cpp:5368 #9 0x7f3b0e0adeeb in QString::toUtf8() const & (this=) at /usr/include/qt5/QtCore/qstring.h:684 #10 KConfigBase::isGroupImmutable (this=0x7ffd8fb599c0, aGroup=...) at /usr/src/debug/kconfig-5.95.0-1.1.x86_64/src/core/kconfigbase.cpp:83 #11 0x7f3b0e0b6ddf in KConfigGroup::KConfigGroup (this=, master=, _group=..., this=, master=, _group=...) at /usr/src/debug/kconfig-5.95.0-1.1.x86_64/src/core/kconfiggroup.cpp:471 #12 0x55bc6df9eaf5 in KalendarAlarmClient::removeNotification (this=0x7ffd8fb5a4f0, notification=0x55bc6f122910) at /usr/src/debug/akonadi-calendar-22.04.2-1.1.x86_64/reminder-daemon/kalendaralarmclient.cpp:181 #13 KalendarAlarmClient::dismiss (this=0x7ffd8fb5a4f0, notification=0x55bc6f122910) at /usr/src/debug/akonadi-calendar-22.04.2-1.1.x86_64/reminder-daemon/kalendaralarmclient.cpp:118 #14 0x7f3b0d512b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd8fb59ab0, r=0x7ffd8fb5a4f0, this=0x55bc6f30c8b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate (sender=0x55bc6f30ca10, signal_index=9, argv=0x7ffd8fb59ab0) at kernel/qobject.cpp:3886 #16 0x7f3b0d50beff in QMetaObject::activate (sender=sender@entry=0x55bc6f30ca10, m=m@entry=0x7f3b0e5a76a0, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #17 0x7f3b0e56f903 in KNotification::closed (this=this@entry=0x55bc6f30ca10) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotification.cpp:582 #18 0x7f3b0e572817 in KNotification::textChanged (this=0x55bc6f30ca10) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/src/knotification.cpp:358 #19 0x7f3b0d512b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd8fb59be0, r=0x7f3b0e5a9060 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, this=0x55bc6f318c80) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate (sender=0x55bc6f318460, signal_index=3, argv=0x7ffd8fb59be0) at kernel/qobject.cpp:3886 #21 0x7f3b0d50beff in QMetaObject::activate (sender=, m=m@entry=0x7f3b0e5a7620 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd8fb59be0) at kernel/qobject.cpp:3946 #22 0x7f3b0e56faef in KNotificationPlugin::finished (this=, _t1=) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotificationplugin.cpp:173 #23 0x7f3b0e586891 in NotifyByPopup::onNotificationClosed (this=0x55bc6f318460, dbus_id=, reason=3) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/src/notifybypopup.cpp:150 #24 0x7f3b0d512b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd8fb59db0, r=0x55bc6f318460, this=0x55bc6f325950) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #25 doActivate (sender=0x55bc6f318498, signal_index=5, argv=0x7ffd8fb59db0) at kernel/qobject.cpp:3886 #26 0x7f3b0d50beff in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd8fb59db0) at kernel/qobject.cpp:3946 #27 0x7f3b0e592599 in OrgFreedesktopNotificationsInterface::NotificationClosed (_t2=, _t1=, this=) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/build/src/notifications_interface.moc:287 #28 OrgFreedesktopNotificationsInterface::qt_static_metacall (_o=_o@entry=0x55bc6f318498, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7ffd8fb59f00) at
[choqok] [Bug 455644] more "crash on exit"
https://bugs.kde.org/show_bug.cgi?id=455644 --- Comment #2 from Mathias Homann --- (In reply to Frédéric Brière from comment #1) > FYI, you can currently work around this bug by disabling the automatic > spellchecking option. that actually worked! -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #34 from Mathias Homann --- (In reply to Frédéric Brière from comment #33) > (In reply to Mathias Homann from comment #32) > > I have built rpms for openSUSE with those two patches, and I'm still getting > > a crash on exit every time I try. Backtrace's attached. > > Despite what it looks like, this appears to be a different bug. Could you > file a separate issue for this one? Thanks! done that: https://bugs.kde.org/show_bug.cgi?id=455644 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 455644] New: more "crash on exit"
https://bugs.kde.org/show_bug.cgi?id=455644 Bug ID: 455644 Summary: more "crash on exit" Product: choqok Version: 1.7.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: scarp...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: choqok (1.7.0) Qt Version: 5.15.2 Frameworks Version: 5.95.0 Operating System: Linux 5.18.4-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.0 [KCrashBackend] -- Information about the crash: reproduce: run choqok, press ctrl-q - it will segfault on exit. The crash can be reproduced every time. -- Backtrace: Application: Choqok (choqok), signal: Segmentation fault [KCrash Handler] #4 0xfff0 in ?? () #5 0x7f938a712b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffdf4f82c40, r=0x55ddcc0257f0, this=0x55ddcc1788d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x55ddcc0257f0, signal_index=7, argv=0x7ffdf4f82c40) at kernel/qobject.cpp:3886 #7 0x7f938a712b6c in doActivate (sender=0x55ddcc048660, signal_index=3, argv=0x7ffdf4f82d00) at kernel/qobject.cpp:3898 #8 0x7f938b59ef83 in QWidgetTextControl::qt_metacall (this=0x55ddcc048660, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffdf4f82df0) at .moc/moc_qwidgettextcontrol_p.cpp:489 #9 0x7f938a7128aa in doActivate (sender=0x55ddcc0485f0, signal_index=4, argv=0x7ffdf4f82df0) at kernel/qobject.cpp:3912 #10 0x7f938a70beff in QMetaObject::activate (sender=, m=m@entry=0x7f938b109820 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #11 0x7f938aff7f33 in QTextDocument::contentsChanged (this=) at .moc/moc_qtextdocument.cpp:427 #12 0x7f938aca931c in QTextDocumentPrivate::finishEdit (this=0x55ddcb7d5d60) at text/qtextdocument_p.cpp:1247 #13 0x7f938aca96f5 in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1203 #14 0x7f938acf4951 in QSyntaxHighlighter::setDocument (this=0x55ddcf941ab0, doc=0x0) at text/qsyntaxhighlighter.cpp:342 #15 0x7f938acf4b89 in QSyntaxHighlighter::~QSyntaxHighlighter (this=0x55ddcf941ab0, __in_chrg=) at text/qsyntaxhighlighter.cpp:324 #16 0x7f9387ffa469 in Sonnet::Highlighter::~Highlighter (this=, this=) at /usr/src/debug/sonnet-5.95.0-1.1.x86_64/src/ui/highlighter.cpp:165 #17 0x7f938a70505e in QObjectPrivate::deleteChildren (this=0x55ddcf946b40) at kernel/qobject.cpp:2104 #18 0x7f938a710bc0 in QObject::~QObject (this=this@entry=0x55ddcacf79c0, __in_chrg=) at kernel/qobject.cpp:1082 #19 0x7f9387ffaaae in Sonnet::SpellCheckDecorator::~SpellCheckDecorator (this=, this=) at /usr/src/debug/sonnet-5.95.0-1.1.x86_64/src/ui/spellcheckdecorator.cpp:225 #20 0x7f938b925de3 in KTextDecorator::~KTextDecorator (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit.cpp:32 #21 KTextDecorator::~KTextDecorator (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit.cpp:32 #22 0x7f938b91bb02 in KTextEditPrivate::~KTextEditPrivate (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit_p.h:47 #23 0x7f938b91bc29 in KTextEditPrivate::~KTextEditPrivate (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit_p.h:56 #24 0x7f938b92196b in std::default_delete::operator() (__ptr=, this=) at /usr/include/c++/12/bits/unique_ptr.h:95 #25 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #26 KTextEdit::~KTextEdit (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit.cpp:258 #27 0x7f938bfc0538 in Choqok::UI::TextEdit::~TextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/libchoqok/ui/choqoktextedit.cpp:98 #28 0x7f937c13fb63 in TwitterApiTextEdit::~TwitterApiTextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/helperlibs/twitterapihelper/twitterapitextedit.cpp:57 #29 0x7f937c4cbf8e in TwitterTextEdit::~TwitterTextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/microblogs/twitter/twittertextedit.cpp:58 #30 TwitterTextEdit::~TwitterTextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/microblogs/twitter/twittertextedit.cpp:58 #31 0x7f938a70505e in QObjectPrivate::deleteChildren (this=this@entry=0x55ddcc534bf0) at kernel/qobject.cpp:2104 #32 0x7f938b3e24b6 in QWidget::~QWidget (this=0x55ddcc5277d0, __in_chrg=) at kernel/qwidget.cpp:1522 #33 0x7f938b3e27f9 in QWidget::~QWidget (this=0x55ddcc5277d0, __in_chrg=) at kernel/qwidget.cpp:1546 #34 0x7f938a70505e in QObjectPrivate::deleteChildren (this=this@entry=0x55ddcc406390) at kernel/qobject.cpp:2104 #35 0x7f938b3e24b6 in QWidget::~QWidget
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #32 from Mathias Homann --- Created attachment 149940 --> https://bugs.kde.org/attachment.cgi?id=149940=edit New crash information added by DrKonqi choqok (1.7.0) using Qt 5.15.2 I have built rpms for openSUSE with those two patches, and I'm still getting a crash on exit every time I try. Backtrace's attached. -- Backtrace (Reduced): #5 0x7f6a60712b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffecaee5ee0, r=0x56220171b420, this=0x562201c178d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x56220171b420, signal_index=7, argv=0x7ffecaee5ee0) at kernel/qobject.cpp:3886 #7 0x7f6a60712b6c in doActivate (sender=0x562201a0c930, signal_index=3, argv=0x7ffecaee5fa0) at kernel/qobject.cpp:3898 #8 0x7f6a6159ef83 in QWidgetTextControl::qt_metacall (this=0x562201a0c930, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffecaee6090) at .moc/moc_qwidgettextcontrol_p.cpp:489 #9 0x7f6a607128aa in doActivate (sender=0x562201a0c880, signal_index=4, argv=0x7ffecaee6090) at kernel/qobject.cpp:3912 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #28 from Mathias Homann --- (In reply to Frédéric Brière from comment #27) > (In reply to Justin Zobel from comment #23) > > I can't replicate this with Choqok 1.7.0 on Fedora 36. Can everyone please > > test and confirm if the crash is still reproducible? > > This bug involves calling a method on a destroyed object, so whether or not > it will trigger a crash may depend on random factors. > > I submitted a draft merge request fixing this a long time ago, but kinda > forgot about it and left it to rot since then. My bad. It should be good > to go now. choqok 1.7.0, plasma 5.25, openSUSE Tumbleweed - still crashing. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 --- Comment #27 from Mathias Homann --- Works for me on a MSI Prestige 14 running openSUSE Tumbleweed. RPMs for Tumbleweed containing that fix can be found on OBS at https://build.opensuse.org/package/show/home:lemmy04:branches:KDE:Frameworks5/powerdevil5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455382] Setting screen brightness is not working right
https://bugs.kde.org/show_bug.cgi?id=455382 Mathias Homann changed: What|Removed |Added Summary|Setting screen brightness |Setting screen brightness |is now working right|is not working right -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455382] New: Setting screen brightness is now working right
https://bugs.kde.org/show_bug.cgi?id=455382 Bug ID: 455382 Summary: Setting screen brightness is now working right Product: plasmashell Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: plasma-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: k...@privat.broulik.de, m...@ratijas.tk Target Milestone: 1.0 SUMMARY When I try to change the screen brightness with the slider on the power applet, or the configured hotkeys, the brightness changes in leaps and bounds and never goes to 100% STEPS TO REPRODUCE 1. Upgrade to Plasma 5.25 on a laptop that supports changing the screen brightness 2. try changing the screen brightness 3. observe that changing screen brightness with the xbacklight tool works the way it should OBSERVED RESULT see above EXPECTED RESULT before plasma 5.25 this worked normally so that is what i'd expect SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220613 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.18.2-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Prestige 14 A11SCS System Version: REV:1.0 ADDITIONAL INFORMATION Running openSUSE Tumbleweed which introduced Plasma 5.25 in snapshot 20220613 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #24 from Mathias Homann --- Still crashing here. Operating System: openSUSE Tumbleweed 20220512 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.5-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 453281] New: When muted notifications are unmuted after a set time the notification sound stays muted if the unmuting happens at login
https://bugs.kde.org/show_bug.cgi?id=453281 Bug ID: 453281 Summary: When muted notifications are unmuted after a set time the notification sound stays muted if the unmuting happens at login Product: frameworks-knotifications Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Whenever I set my notifications to "silent until such time" the sound stays muted if i log out and log in only after the time when the notifications should be unmuted STEPS TO REPRODUCE 1. mute your notifications for some set time, i.e. "until tomorrow" 2. take note of the actual time when the notifications should unmute, i.e. 6:00am 3. logoff 4. stay away from that account until **after** the time from 2., then log in again OBSERVED RESULT After logging in, notifications are unmuted but the sound for notifications, for example the "pop" sound from kmix when you change volume, is **not** EXPECTED RESULT I expect **all** notifications to be unmuted, including sound SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220428 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Workaround: manually mute and then unmute notifications Fun fact: this can easily lead to believing that sound has stopped working, triggering some longish bug search o.0. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453037] New: on first start after log in, kmail starts all imap agents in "offline mode"
https://bugs.kde.org/show_bug.cgi?id=453037 Bug ID: 453037 Summary: on first start after log in, kmail starts all imap agents in "offline mode" Product: kontact Version: 5.19.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org 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. reboot or relogin to plasma 2. start kontact OBSERVED RESULT all imap connections are in offline mode EXPECTED RESULT I expect the imap ressources to be in online mode when the connection to the mailserver is available at startup time SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220424 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 187311] Kopete Accountlist duplicates entry with empty/wrong copies
https://bugs.kde.org/show_bug.cgi?id=187311 Mathias changed: What|Removed |Added CC||math...@public-ip.org --- Comment #28 from Mathias --- Still happens in 21.12.3-r1 on Gentoo Even if I remove .local/share/kopete and .config/kopeterc and start anew: - start kopete - login - see contacts (online and offline) correctly (with their display names and sorted in groups) - logout/close kopete - empty entries in contactlist.xml appear (all as meta-contacts, the only info in the entries is the hexadecimal ContactId) - after restarting kopete and logging in the contact list now includes the real entries and the new empty ones - every closing of kopete adds the exact number of existing real contacts in my contact groups as empty entries, so that the contact lists grows on every closing procedure - deleting the empty entries from the contact list is possible but useless All this has been happening for years. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432570] kwin_x11 crash randomly in KWin::SceneOpenGL::createScene()
https://bugs.kde.org/show_bug.cgi?id=432570 --- Comment #25 from Mathias Panzenböck --- Created attachment 147588 --> https://bugs.kde.org/attachment.cgi?id=147588=edit New crash information added by DrKonqi kwin_x11 (5.20.5) using Qt 5.15.2 - What I was doing when the application crashed: I was watching a video on Amazon Prime in Firefox in fullscreen (screen is 1920x1080, video is lower resolution because Amazon doesn't give us full HD under Linux). Was watching for about 47 minutes already when the issue occured. First the screen froze, then it went out of fullscreen and the video resumed, but kwin restarted without composite. -- Backtrace (Reduced): #5 0x7fca20275564 in KWin::SceneOpenGL::createScene(QObject*) () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #6 0x7fca2028441d in KWin::OpenGLFactory::create(QObject*) const () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #8 0x7fca37db703e in KWin::X11Compositor::start() () at /lib64/libkwin.so.5 #9 0x7fca37db4e57 in KWin::Compositor::reinitialize() () at /lib64/libkwin.so.5 #10 0x7fca36a81386 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 --- Comment #10 from Mathias Tillman --- (In reply to Matt from comment #8) > (In reply to David Edmundson from comment #7) > > Git commit 140c2fb20efa547cda1ff74880a7cdbcab8b5943 by David Edmundson, on > > behalf of Mathias Tillman. > > Committed on 17/03/2022 at 22:19. > > Pushed by davidedmundson into branch 'master'. > > > > effects/blur: Fix window flickering when the clip intersected with the > > current blur region. > > > > This fixes a bug introduced in > > https://invent.kde.org/plasma/kwin/-/merge_requests/2045 where it would no > > longer check if it should redraw the whole region unless the data clip > > intersected. This would lead to flickering in certain cases > > > > M +7-6src/effects/blur/blur.cpp > > > > https://invent.kde.org/plasma/kwin/commit/ > > 140c2fb20efa547cda1ff74880a7cdbcab8b5943 > > Wondering if this bug should really be resolved as fixed? > Matthias says this is a fix for something introduced in 5.24, but the issue > that was reported has been around since at least 5.18. Agreed, it probably shouldn't be marked as fixed. In hindsight I should have opened a separate issue, but since I wasn't sure of what the actual issue was, and it basically matched the flickering of the original issue, I decided to post my findings here. Perhaps this latest conversation should be split into a separate issue (that would be marked as resolved) for archiving purposes? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 --- Comment #5 from Mathias Tillman --- Created attachment 147548 --> https://bugs.kde.org/attachment.cgi?id=147548=edit Patch to fix window flickering -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Mathias Tillman changed: What|Removed |Added CC||vlad.zahorod...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #4 from Mathias Tillman --- So I've been experiencing this myself lately, but I believe the original bug is actually a separate issue, it just happens to have the same or similar results. I've done some testing myself, and it seems to have been introduced in v5.24.2. Running a bisect the faulty commit looks to be 00a8de6c011954f379fe6f0542bdc9c502de45f3 (https://invent.kde.org/plasma/kwin/-/commit/00a8de6c011954f379fe6f0542bdc9c502de45f3). I'm not sure why this would cause flickering though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432570] kwin_x11 crash randomly in KWin::SceneOpenGL::createScene()
https://bugs.kde.org/show_bug.cgi?id=432570 --- Comment #24 from Mathias Panzenböck --- Created attachment 147176 --> https://bugs.kde.org/attachment.cgi?id=147176=edit New crash information added by DrKonqi kwin_x11 (5.20.5) using Qt 5.15.2 - What I was doing when the application crashed: I watched a YouTube video in Firefox. - Unusual behavior I noticed: Image froze, no keyboard inputs registered anymore, but audio continued. I switched to a text terminal and back (Ctrl+Alt+F2 then Ctrl+Alt+F1) at which point kwin crashed, restarted and the UI was useable again, though compositing was deactivated. -- Backtrace (Reduced): #5 0x7f559ed1b564 in KWin::SceneOpenGL::createScene(QObject*) () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #6 0x7f559ed2a41d in KWin::OpenGLFactory::create(QObject*) const () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #8 0x7f55bd11903e in KWin::X11Compositor::start() () at /lib64/libkwin.so.5 #9 0x7f55bd116e57 in KWin::Compositor::reinitialize() () at /lib64/libkwin.so.5 #10 0x7f55bbde3386 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432570] kwin_x11 crash randomly in KWin::SceneOpenGL::createScene()
https://bugs.kde.org/show_bug.cgi?id=432570 Mathias Panzenböck changed: What|Removed |Added CC||grosser.meister.morti@gmx.n ||et -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 449178] KCM and Applet no longer show paired devices after turning bluetooth off and on again; have to restart plasmashell or leave/return to the KCM
https://bugs.kde.org/show_bug.cgi?id=449178 Mathias C. changed: What|Removed |Added CC||mathias.cilibe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 449239] New: kmail treats background color of plaintext emails as html mail background
https://bugs.kde.org/show_bug.cgi?id=449239 Bug ID: 449239 Summary: kmail treats background color of plaintext emails as html mail background Product: kontact Version: 5.19.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org 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. configure kmails color settings as follows: [x] Eigene farben benutzen (use own colors) [X] Farbe der ursprünglichen HTML mail nicht ändern (don't change colors in html mails) 2. open a plaintext email OBSERVED RESULT The text is colord according to the customized colors but the background of a PLAINTEXT email is switched to white, making the whole mess unreadable in my case. EXPECTED RESULT I would expect kmail to change all colors, including the background, if the mail is plaintext only. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220125 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION The problem here is using a Plasma-wide dark color scheme - you HAVE to have kmail adjust the colors, or mails will be unreadable. but there seems to be no working combination of these two options that works equally well with plaintext- and html emails. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437970] ESPAÑOL cuando entro a krita todo anda bien el problema es que cuando dibujo en la tableta el lienzo se ve borroso. solo si estoy sin zoom, porque si agrando la imagen se ve bien
https://bugs.kde.org/show_bug.cgi?id=437970 Mathias Kraus changed: What|Removed |Added Assignee|k.h...@gmx.de |krita-bugs-n...@kde.org Product|abakus |krita Component|general |* Unknown --- Comment #1 from Mathias Kraus --- Not sure if spam or real request since I don't speak Spanish. Assigned this to krita since it was mentioned in the description. Maybe someone of you understands the request. -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 446099] bug in animation
https://bugs.kde.org/show_bug.cgi?id=446099 Mathias Kraus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Mathias Kraus --- This is spam -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 445194] sports, tech, health, entertainment
https://bugs.kde.org/show_bug.cgi?id=445194 Mathias Kraus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Mathias Kraus --- This is spam -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 439632] Can I resolve the sbcglobal email login issue by changing the password?
https://bugs.kde.org/show_bug.cgi?id=439632 Mathias Kraus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Mathias Kraus --- This is spam -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 438791] idk
https://bugs.kde.org/show_bug.cgi?id=438791 Mathias Kraus changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Mathias Kraus --- This is spam -- You are receiving this mail because: You are watching all bug changes.
[Granatier] [Bug 447926] bug audio
https://bugs.kde.org/show_bug.cgi?id=447926 --- Comment #2 from Mathias Kraus --- I can confirm that it works on KDE Neon which is based on Ubuntu 20.04 but with latest KDE packages. Since there wasn't any activity on granatier lately, I agree with Albert. -- You are receiving this mail because: You are watching all bug changes.
