[kmail2] [Bug 489610] New: XOAUTH2 with 2FA requires daily re-authentication for SMTP

2024-07-02 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=489610

Bug ID: 489610
   Summary: XOAUTH2 with 2FA requires daily re-authentication for
SMTP
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: mull...@adelie.io
  Target Milestone: ---

SUMMARY
When using XOAUTH2 with two-factor authentication for an Outlook account,
outgoing email fails after some period of time and a re-authentication is
required to send mail again. Incoming mail with IMAP seems to work fine.
Outgoing mail works as expected for some period of time after authenticating
with 2FA. 


STEPS TO REPRODUCE
1. Set up SMTP with 2FA and XOAUTH2
2. Wait an unknown period of time
3. Try to send an email

OBSERVED RESULT
Authentication for the outgoing mail fails.

EXPECTED RESULT
Outgoing mail should send without issue.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux
(available in About System)
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kmail: 24.05.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 471019] White line flickers above application launcher when it launches or closes

2023-12-23 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=471019

Aaron  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Aaron  ---
(In reply to Nate Graham from comment #1)
> Does this reproduce in Fedora 39?

Nope.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 486042] New: Show hidden icons invisible.

2024-04-23 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=486042

Bug ID: 486042
   Summary: Show hidden icons invisible.
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: aaron...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Created attachment 168850
  --> https://bugs.kde.org/attachment.cgi?id=168850&action=edit
Screenshot of invisible window, where hidden icons were supposed to be shown.

STEPS TO REPRODUCE
1. Fresh install plasma on arch (sudo pacman -S plasma) reboot after
2. Login after fresh install
3. click "show invisible icons" button.

OBSERVED RESULT
Window is missing, with a tiny icon instead.

EXPECTED RESULT
Show hidden icons.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Reddit discussion
https://www.reddit.com/r/kde/comments/1cbgn75/show_hidden_icons_invisible_plasma_604/

-- 
You are receiving this mail because:
You are watching all bug changes.

[krdc] [Bug 454016] New: VNC scaling toggle not working

2022-05-18 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=454016

Bug ID: 454016
   Summary: VNC scaling toggle not working
   Product: krdc
   Version: 22.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: VNC
  Assignee: uwol...@kde.org
  Reporter: kde@aarontc.com
CC: aa...@kde.org
  Target Milestone: ---

Created attachment 148976
  --> https://bugs.kde.org/attachment.cgi?id=148976&action=edit
Screenshot of problem

SUMMARY
When connected to a VNC host with krdc, clicking "Scale" on the toolbar in
previous versions would cause the remote display image to be expanded or
reduced to fit the size of the krdc window. As of this version, toggling the
"Scale" button on the toolbar has no visible effect.


STEPS TO REPRODUCE
1. Connect to a VNC host at a lower resolution than the host machine
2. Click "Scale" button on toolbar


OBSERVED RESULT
Observe no change in size of remote display (image remains tiny and centered in
the krdc window)

EXPECTED RESULT

Remote display image is scaled up to fill the krdc window, while retaining the
original aspect ratio.


SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

OS: Linux (x86_64) release 5.17.6-arch1-1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 451406] Missing icons with last AppImage

2022-03-19 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=451406

Aaron  changed:

   What|Removed |Added

 CC||aaro...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 451406] Missing icons with last AppImage

2022-03-20 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=451406

--- Comment #2 from Aaron  ---
Created attachment 147633
  --> https://bugs.kde.org/attachment.cgi?id=147633&action=edit
kdenlive 21.12.3 settings

I have both options recommended selected, and I have no icons visible.  If I
launch 21.12.2, all the icons are visible again.  This is on PopOS 21.10

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 451406] Missing icons with last AppImage

2022-03-20 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=451406

--- Comment #4 from Aaron  ---
I deleted the file:

```
$ rm ~/.config/kdenlive-appimagerc
$ ./kdenlive-21.12.3-x86_64.AppImage
```

And relaunched the appimage, but the result is the same as the attached
screenshot with no icons.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 451406] Missing icons with last AppImage

2022-03-20 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=451406

--- Comment #5 from Aaron  ---
It looks like it can't find the theme based on the logging:

```
./kdenlive-21.12.3-x86_64.AppImage 
=== /// CANNOT ACCESS SPEECH DICTIONARIES FOLDER
Icon theme "breeze-dark" not found.
Icon theme "breeze" not found.
Starting render server
mlt_repository_init: failed to dlopen
/tmp/.mount_kdenli5iEAfw/usr/lib/mlt-7/libmltgdk.so
  (/lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: g_memdup2)
profilePath from $MLT_PROFILES_PATH: 
"/tmp/.mount_kdenli5iEAfw/usr/share/mlt-7/profiles/"
meltPath from KdenliveSetting::rendererPath: 
"/tmp/.mount_kdenli5iEAfw/usr/share/mlt-7/profiles/"
meltPath from profilePath/.../bin: 
"/tmp/.mount_kdenli5iEAfw/usr/share/mlt-7/profiles/"
Invalid metadata for  "avcolour_space"
Failed to parse "avcolour_space"
Invalid metadata for  "avcolor_space"
Failed to parse "avcolor_space"
Invalid metadata for  "avdeinterlace"
Failed to parse "avdeinterlace"
Invalid metadata for  "swscale"
Failed to parse "swscale"
Invalid metadata for  "swresample"
Failed to parse "swresample"
Invalid metadata for  "audiochannels"
Failed to parse "audiochannels"
Invalid metadata for  "audioconvert"
Failed to parse "audioconvert"
Invalid metadata for  "imageconvert"
Failed to parse "imageconvert"
Invalid metadata for  "glsl.manager"
Failed to parse "glsl.manager"
Invalid metadata for  "movit.convert"
Failed to parse "movit.convert"
Invalid metadata for  "movit.crop"
Failed to parse "movit.crop"
Invalid metadata for  "movit.resample"
Failed to parse "movit.resample"
Invalid metadata for  "movit.resize"
Failed to parse "movit.resize"
Invalid metadata for  "telecide"
Failed to parse "telecide"
Invalid metadata for  "deinterlace"
Failed to parse "deinterlace"
plugin not available: "avfilter.acompressor"
plugin not available: "avfilter.aecho"
plugin not available: "avfilter.agate"
plugin not available: "avfilter.atadenoise"
plugin not available: "avfilter.bs2b"
plugin not available: "avfilter.bwdif"
plugin not available: "avfilter.deblock"
plugin not available: "avfilter.dedot"
plugin not available: "avfilter.deflate"
plugin not available: "avfilter.derain"
plugin not available: "avfilter.doubleweave"
plugin not available: "avfilter.field"
plugin not available: "avfilter.framestep"
plugin not available: "avfilter.fspp"
plugin not available: "avfilter.graphmonitor"
plugin not available: "avfilter.hqdn3d"
plugin not available: "avfilter.inflate"
plugin not available: "avfilter.lagfun"
plugin not available: "avfilter.loudnorm"
plugin not available: "avfilter.random"
plugin not available: "avfilter.removegrain"
plugin not available: "avfilter.separatefields"
plugin not available: "avfilter.shuffleplanes"
plugin not available: "avfilter.sofalizer"
plugin not available: "avfilter.sr"
plugin not available: "avfilter.tmix"
plugin not available: "avfilter.w3fdif"
plugin not available: "avfilter.weave"
plugin not available: "avfilter.yadif"
plugin not available: "frei0r.baltan"
plugin not available: "frei0r.bgsubtract0r"
plugin not available: "frei0r.delay0r"
plugin not available: "frei0r.delaygrab"
plugin not available: "frei0r.lightgraffiti"
plugin not available: "frei0r.lightgraffiti"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "movit.unsharp_mask"
plugin not available: "region"
plugin not available: "timewarp"
plugin not available: "region"
ALSA lib
/home/appimage/Craft/BC/linux-centos_64-gcc/build/libs/libasound2/work/alsa-lib-1.2.5.1/src/conf.c:4499:(snd_config_update_r)
Cannot access file
/home/appimage/Craft/BC/linux-centos_64-gcc/share/alsa/alsa.conf
no alsa devices available
qrc:/qml/SceneToolBar.qml:190:21: QML Image: Failed to get image from provider:
image://icon/transform-move-horizontal
qrc:/qml/SceneToolBar.qml:168:21: QML Image: Failed to get image from provider:
image:

[kdenlive] [Bug 451406] Missing icons with last AppImage

2022-03-20 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=451406

--- Comment #8 from Aaron  ---
Created attachment 147638
  --> https://bugs.kde.org/attachment.cgi?id=147638&action=edit
help -> reset configuration

It appears to fix some of the icons, but not all of them.  (see attached
screenshot)

logs:

```
./kdenlive-21.12.3-x86_64.AppImage
=== /// CANNOT ACCESS SPEECH DICTIONARIES FOLDER
Icon theme "breeze" not found.
Starting render server
mlt_repository_init: failed to dlopen
/tmp/.mount_kdenlisCNNSP/usr/lib/mlt-7/libmltgdk.so
  (/lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: g_memdup2)
profilePath from $MLT_PROFILES_PATH: 
"/tmp/.mount_kdenlisCNNSP/usr/share/mlt-7/profiles/"
meltPath from KdenliveSetting::rendererPath: 
"/tmp/.mount_kdenlisCNNSP/usr/share/mlt-7/profiles/"
meltPath from profilePath/.../bin: 
"/tmp/.mount_kdenlisCNNSP/usr/share/mlt-7/profiles/"
Invalid metadata for  "avcolour_space"
Failed to parse "avcolour_space"
Invalid metadata for  "avcolor_space"
Failed to parse "avcolor_space"
Invalid metadata for  "avdeinterlace"
Failed to parse "avdeinterlace"
Invalid metadata for  "swscale"
Failed to parse "swscale"
Invalid metadata for  "swresample"
Failed to parse "swresample"
Invalid metadata for  "audiochannels"
Failed to parse "audiochannels"
Invalid metadata for  "audioconvert"
Failed to parse "audioconvert"
Invalid metadata for  "imageconvert"
Failed to parse "imageconvert"
Invalid metadata for  "glsl.manager"
Failed to parse "glsl.manager"
Invalid metadata for  "movit.convert"
Failed to parse "movit.convert"
Invalid metadata for  "movit.crop"
Failed to parse "movit.crop"
Invalid metadata for  "movit.resample"
Failed to parse "movit.resample"
Invalid metadata for  "movit.resize"
Failed to parse "movit.resize"
Invalid metadata for  "telecide"
Failed to parse "telecide"
Invalid metadata for  "deinterlace"
Failed to parse "deinterlace"
plugin not available: "avfilter.acompressor"
plugin not available: "avfilter.aecho"
plugin not available: "avfilter.agate"
plugin not available: "avfilter.atadenoise"
plugin not available: "avfilter.bs2b"
plugin not available: "avfilter.bwdif"
plugin not available: "avfilter.deblock"
plugin not available: "avfilter.dedot"
plugin not available: "avfilter.deflate"
plugin not available: "avfilter.derain"
plugin not available: "avfilter.doubleweave"
plugin not available: "avfilter.field"
plugin not available: "avfilter.framestep"
plugin not available: "avfilter.fspp"
plugin not available: "avfilter.graphmonitor"
plugin not available: "avfilter.hqdn3d"
plugin not available: "avfilter.inflate"
plugin not available: "avfilter.lagfun"
plugin not available: "avfilter.loudnorm"
plugin not available: "avfilter.random"
plugin not available: "avfilter.removegrain"
plugin not available: "avfilter.separatefields"
plugin not available: "avfilter.shuffleplanes"
plugin not available: "avfilter.sofalizer"
plugin not available: "avfilter.sr"
plugin not available: "avfilter.tmix"
plugin not available: "avfilter.w3fdif"
plugin not available: "avfilter.weave"
plugin not available: "avfilter.yadif"
plugin not available: "frei0r.baltan"
plugin not available: "frei0r.bgsubtract0r"
plugin not available: "frei0r.delay0r"
plugin not available: "frei0r.delaygrab"
plugin not available: "frei0r.lightgraffiti"
plugin not available: "frei0r.lightgraffiti"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "ladspa"
plugin not available: "movit.unsharp_mask"
plugin not available: "region"
plugin not available: "timewarp"
plugin not available: "region"
ALSA lib
/home/appimage/Craft/BC/linux-centos_64-gcc/build/libs/libasound2/work/alsa-lib-1.2.5.1/src/conf.c:4499:(snd_config_update_r)
Cannot access file
/home/appimage/Craft/BC/linux-centos_64-gcc/share/alsa/alsa.conf
no alsa devices available
qrc:/qml/SceneToolBar.qml:190:21: QML Image: Failed to get image from provi

[krita] [Bug 439521] New: zoom does not work properly

2021-07-05 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=439521

Bug ID: 439521
   Summary: zoom does not work properly
   Product: krita
   Version: 4.4.5
  Platform: Compiled Sources
OS: Microsoft Windows
Status: REPORTED
  Severity: task
  Priority: NOR
 Component: Shortcuts and Canvas Input Settings
  Assignee: krita-bugs-n...@kde.org
  Reporter: gameacc3...@gmail.com
  Target Milestone: ---

if i use the zoom shortcut 4,5or6 the canvas rotates even thoug these shortcuts
are tured of

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 478950] New: Time remap shows image still in project monitor instead of actual frame

2023-12-23 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=478950

Bug ID: 478950
   Summary: Time remap shows image still in project monitor
instead of actual frame
Classification: Applications
   Product: kdenlive
   Version: 23.08.4
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: j...@kdenlive.org
  Reporter: aaro...@gmail.com
  Target Milestone: ---

Created attachment 164411
  --> https://bugs.kde.org/attachment.cgi?id=164411&action=edit
In the clip monitor on the left is the frame that should be shown, but the
project monitor on the right only shows the first frame no matter where you try
to add a keyframe in the time remapping windo

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
***
As of 23.08.3 (and also in the latest release, 23.08.4), the system monitor
only shows the first frame in the project monitor when adding keyframes in the
Time Remapping panel.  After adding a keyframe and playing it back then going
back to the time remapping panel, clicking around will show the correct frame
again.

When I rolled back to 23.08.2 I don't have this particular issue.

STEPS TO REPRODUCE
1. Add a clip to the timeline.
2. Right click and enable time remapping.
3. In the time remapping panel click in the source clip "timeline" area to
choose a point for a keyframe

OBSERVED RESULT
The frame shown in the project monitor is the first frame

EXPECTED RESULT
The frame shown in the project monitor is the frame in the timeline where
clicked.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

Another user commenting on the issue:
https://discuss.kde.org/t/kdenlive-23-08-3-released/7150/5

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 475305] New: Firefox not opening from shortcut

2023-10-06 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=475305

Bug ID: 475305
   Summary: Firefox not opening from shortcut
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: aaronjwoodbri...@gmail.com
  Target Milestone: ---

firefox launches from the app menu, but when launched from a shortcut it makes
the whole screen black for a second and dose not open

kde version: latest

qt version: 6.5.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 475305] Firefox not opening from shortcut

2023-10-07 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=475305

--- Comment #3 from Aaron  ---
(In reply to Nicolas Fella from comment #2)
> Are you using Fedora?

yes fedora kde

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 475305] Firefox not opening from shortcut

2023-10-07 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=475305

--- Comment #4 from Aaron  ---
(In reply to Ben Bonacci from comment #1)

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.5-200.fc38.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: A520I AC
System Version: -CF 

the attachment is on the original post

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 475305] Firefox not opening from shortcut

2023-10-07 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=475305

--- Comment #5 from Aaron  ---
Created attachment 162154
  --> https://bugs.kde.org/attachment.cgi?id=162154&action=edit
black screen

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 477003] New: Oauth not working

2023-11-14 Thread aaron
https://bugs.kde.org/show_bug.cgi?id=477003

Bug ID: 477003
   Summary: Oauth not working
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Plugin-WebService-OneDrive
  Assignee: digikam-bugs-n...@kde.org
  Reporter: aa...@garcia.ltd
  Target Milestone: ---

Created attachment 163158
  --> https://bugs.kde.org/attachment.cgi?id=163158&action=edit
screen shots showing my one drive account all working and it not working

SUMMARY
***
Connection to my Onedrive does not work,

I get told at the sign-in page in Red - "That Microsoft doesn't exist. Enter a
different account  or get a new one"

***


STEPS TO REPRODUCE

1. Create a Azure active directory domain, e.g. "mydomain.com" 
2. Create a user account e.g. myn...@mydomain.com 
3. check one drive works with myn...@mydomain.com
4. open digikam and attempt to use the Export function with myn...@mydomain.com 
- Fails.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 477003] Oauth not working

2023-11-14 Thread aaron
https://bugs.kde.org/show_bug.cgi?id=477003

aa...@garcia.ltd  changed:

   What|Removed |Added

 CC||aa...@garcia.ltd

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 477003] OneDrive Oauth not working

2023-11-14 Thread aaron
https://bugs.kde.org/show_bug.cgi?id=477003

--- Comment #2 from aa...@garcia.ltd  ---
my investigation shows its because I use one drive for business (as I have work
account with 5TB of storage), 

your connector looks to be designed to only work with one drive domestic
(non-work accounts) e.g. per...@hotmail.com or per...@outlook.com

I think the one drive IDP / API different when connected to a work account.

https://powerusers.microsoft.com/t5/Using-Flows/MS-Account-Doesn-t-Exist-when-signing-into-OneDrive/td-p/393619
https://www.multcloud.com/tutorials/onedrive-vs-onedrive-for-business--rc.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 476335] New: for one name the "unconfirmed" is two rows but the upper row does not show correctly may be the bottom 10% of it.

2023-10-30 Thread aaron
https://bugs.kde.org/show_bug.cgi?id=476335

Bug ID: 476335
   Summary: for one name the "unconfirmed"  is two rows but the
upper row does not show correctly may be the bottom
10% of it.
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Microsoft Windows
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: aa...@garcia.ltd
  Target Milestone: ---

Created attachment 162734
  --> https://bugs.kde.org/attachment.cgi?id=162734&action=edit
UI not drawing the faces correctly

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. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
my system is busy at the mo doing a re-finger print 
digikam version 8.1.0
Images: 
GIF: 2
HEIF: 11621
JPG: 447369
PNG: 8045
PSD: 6950
RAW-CR2: 2428
RAW-CRW: 978
TIFF: 108
WEBP: 1
total: 477502
: 
Videos: 
3GP: 34
AVI: 3041
MOV: 19782
MP4: 2560
MPEG: 379
total: 25796
: 
Total Items: 503298
Albums: 4665
Tags: 218
: 
Database backend: QSQLITE
Database Path: C:/Live-Photos_DB/
Database locale: UTF-8

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 476347] New: Snap to assistant option fail

2023-10-30 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=476347

Bug ID: 476347
   Summary: Snap to assistant option fail
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Tool/Assistants
  Assignee: krita-bugs-n...@kde.org
  Reporter: abchrusn...@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. toggle snap to assistant tickbox
2. attempt to draw 
3. 

OBSERVED RESULT
so two different things that were each unexpected were happening. 
first: when toggling "snap to assistant" the brush wasn't drawing or was only
drawing sporadically
second: when toggling "snap to assistant" to the ticked i.e. "on" position and
when the brush was drawing, the line did not snap to the assistant. 


EXPECTED RESULT
both behaviors were deviations from the last time I opened the program--which
was also the last time I opened this file. Nothing was changed by me, short of
toggling the "snap to assistant" option on and off and switching between
brushes. The tools worked as expected previously; furthermore, they worked
properly again after closing the program and restarting it. This led me to
believe it might be a bug. 

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 423883] New: Graphic Tablet configuration does not show shortcut buttons tab

2020-07-04 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=423883

Bug ID: 423883
   Summary: Graphic Tablet configuration does not show shortcut
buttons tab
   Product: systemsettings
   Version: 5.18.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcmshell
  Assignee: plasma-b...@kde.org
  Reporter: aaron.oldenb...@protonmail.com
  Target Milestone: ---

SUMMARY

I am using a small Wacom Intuos Drawing tablet, which the Graphic Tablet
configuration System Settings Module reads as Wacom Intuos S P [0374]. The
module is currently showing me three tabs, for General, Stylus, and Tablet. It
is not showing the tab for modifying shortcut buttons.

This is the third time I've installed Manjaro KDE edition, and the first time
that tab has not shown up. I believe it was there when I first installed, and
subsequently disappeared.


STEPS TO REPRODUCE
1. Plug in this type of tablet (or make system think it's plugged in)
2. Open Graphic Tablet settings.
3. Create new profile for Krita
4. Try to go to button shortcuts tab.

OBSERVED RESULT

The tab is not visible.

EXPECTED RESULT

I should be able to click the tab and assign my tablet's buttons.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro with kernel 5.4.44-1
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

It is possible that it is misreading my tablet as one that does not have
buttons.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 424160] New: "Pause media players when suspending" un-pauses already-paused music

2020-07-13 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=424160

Bug ID: 424160
   Summary: "Pause media players when suspending" un-pauses
already-paused music
   Product: systemsettings
   Version: 5.18.5
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: aaron.oldenb...@protonmail.com
  Target Milestone: ---

SUMMARY

When "Pause media players when suspending" is enabled, and current music
playing is paused, suspending will un-pause the music, then pause it again.
Upon resuming, the music will be un-paused.


STEPS TO REPRODUCE
1. Play music with a player that can be paused/un-paused through the system.
2. Pause the music.
3. In Advanced Power Management Settings, set "Pause media players when
suspending" to "enabled".
4. Suspend the computer.
5. Resume

OBSERVED RESULT

Paused music plays for a second while suspending, then is paused again. Upon
resuming, music automatically plays.


EXPECTED RESULT

Paused music stays paused after step 2 and does not resume.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.4.44-1-Manjaro
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

My current workaround is to turn off the "pause media players when suspending"
option. If I manually pause before suspending, then I have no problems. 

This sounds related to 423317, but does not just involve Android.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 424160] "Pause media players when suspending" un-pauses already-paused music

2020-07-13 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=424160

--- Comment #2 from Aaron  ---
(In reply to David Edmundson from comment #1)
> Can you confirm which media player(s) this happens with?

It happens with Google Play Music Desktop Player and YouTube Music Desktop.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 429739] New: choosing workspace through top menu system doesn't do anything

2020-11-27 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=429739

Bug ID: 429739
   Summary: choosing workspace through top menu system doesn't do
anything
   Product: krita
   Version: 4.4.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: aaron.oldenb...@protonmail.com
  Target Milestone: ---

SUMMARY

Choosing a workspace through the menu system doesn't result in any changes. 

STEPS TO REPRODUCE
1. Go to the Window menu -> Workspaces
2. Choose something other than the current workspace, like Animation

OBSERVED RESULT

Nothing happens

EXPECTED RESULT

Switch workspaces, similar to functionality of Choose Workspaces button in
upper-right hand corner.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro, 5.7.19-2 kernel
(available in About System)
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 429739] choosing workspace through top menu system doesn't do anything

2020-11-28 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=429739

--- Comment #2 from Aaron  ---
Looks like it's working now for me, too. I'm not sure what fixed it. I had
already done a couple of application restarts. I did run the most recent set of
updates today, though I don't think they included Krita, and restarted my
system. It's the distribution package.

Thanks for checking it out.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 478033] EWS accounts unusable - constantly lose authentication

2024-09-12 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=478033

Aaron  changed:

   What|Removed |Added

 CC||mull...@adelie.io

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail

2024-08-19 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=457233

Aaron  changed:

   What|Removed |Added

 CC||mull...@adelie.io

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

2020-02-17 Thread aaron
https://bugs.kde.org/show_bug.cgi?id=401677

aaron  changed:

   What|Removed |Added

 CC||skarlup...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #39 from aaron  ---
Samsung Galexy S9
Android 10
Samsung Messages 11.0.00.291
KDEConnect Android App 1.13.7

Gnome Version: 3.34.2
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=19.0.0
DISTRIB_CODENAME=Kyria
DISTRIB_DESCRIPTION="Manjaro Linux"

GSConnect 31
Legacy Message Support = Disabled


I am able to view and send text messages from messaging menu.  I can see full
chat history and contacts. I can respond to messages and view conversation
scroll-back. 

Previously I could only see or reply to a sms message via the notification
pop-up.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 418649] New: Plasma discover crashes after opening. Fedora 32

2020-03-08 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=418649

Bug ID: 418649
   Summary: Plasma discover crashes after opening. Fedora 32
   Product: Discover
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: aaron...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.18.2)

Qt Version: 5.13.2
Frameworks Version: 5.67.0
Operating System: Linux 5.6.0-0.rc4.git0.1.fc32.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 32 (KDE Plasma)

-- Information about the crash:
plasma-discover 
qrc:/qml/Feedback.qml:2:1: module "org.kde.userfeedback" is not installed
invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config
group not found! Check your KNS3 installation."
adding empty sources model QStandardItemModel(0x55f1ac33aff0)
org.kde.plasma.discover: couldn't open file
"/home/.cache/discover/featured-5.9.json" "No such file or directory"
org.kde.plasma.discover: couldn't open file
"/home/.cache/discover/featured-5.9.json" "No such file or directory"
org.kde.plasma.discover: couldn't open file
"/home/.cache/discover/featured-5.9.json" "No such file or directory"
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
free(): double free detected in tcache 2
KCrash: Application 'plasma-discover' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

[1]+  Stopped plasma-discover
[@Lenovo ~]$ QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 22 and type 'Read', disabling...

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f44974e0dc0 (LWP 4361))]

Thread 27 (Thread 0x7f43fdffb700 (LWP 4390)):
#0  0x7f449a8681c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f449b7684d9 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt5Core.so.5
#2  0x7f449b7685fb in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#3  0x7f449b7665e3 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#4  0x7f449b7629b6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f449a861432 in start_thread () from /lib64/libpthread.so.0
#6  0x7f449b3e9833 in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f43fe7fc700 (LWP 4389)):
#0  0x7f449a8681c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f449b7684d9 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt5Core.so.5
#2  0x7f449b7685fb in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#3  0x7f449b7665e3 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#4  0x7f449b7629b6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f449a861432 in start_thread () from /lib64/libpthread.so.0
#6  0x7f449b3e9833 in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f43feffd700 (LWP 4388)):
#0  0x7f449b3de9cf in poll () from /lib64/libc.so.6
#1  0x7f4499f19a8d in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#2  0x7f4499f19bc3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f449b938b93 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f449b8ec1db in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f449b7616e7 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f449b7629b6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f449a861432 in start_thread () from /lib64/libpthread.so.0
#8  0x7f449b3e9833 in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7f43ff7fe700 (LWP 4387)):
#0  0x7fff927c7ac5 in clock_gettime ()
#1  0x7f449b3b06b5 in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6
#2  0x7f449b938415 in qt_gettime() () from /lib64/libQt5Core.so.5
#3  0x7f449b936d5d in QTimerInfoList::updateCurrentTime() () from
/lib64/libQt5Core.so.5
#4  0x7f449b938eb5 in timerSourceCheck(_GSource*) () from
/lib64/libQt5Core.so.5
#5  0x7f4499f19499 in g_main_context_check () from /lib64/libglib-2.0.so.0
#6  0x7f4499f19a33 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#7  0x7f4499f19bc3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#8  0x7f449b938b93 in
QEventDispatcherGlib::processEvents(

[kscreenlocker] [Bug 419299] New: [kscreenlocker] spaming "kscreenlocker_greet[9912]: Could not create AF_NETLINK socket"

2020-03-27 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=419299

Bug ID: 419299
   Summary: [kscreenlocker] spaming "kscreenlocker_greet[9912]:
Could not create AF_NETLINK socket"
   Product: kscreenlocker
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: aaron...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

Created attachment 127046
  --> https://bugs.kde.org/attachment.cgi?id=127046&action=edit
journalctl -p 3 -xb log after unlocking

SUMMARY:
After locking and unlocking the screen, I have permission errors for Could not
create AF_NETLINK socket

STEPS TO REPRODUCE:
1. Fresh install of Plasma.
2. Lock the screen and then unlock.
3. observe journalctl -p 3 -xb 

OBSERVED RESULT:
Many lines of "Could not create AF_NETLINK socket (Operation not permitted)"

EXPECTED RESULT:


SOFTWARE/OS VERSIONS
Archlinux 

KDE Plasma: 5.18.3-1
(available in About System)
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 358823] Cannot configure sendmail (postfix) as the outgoing mail transport

2018-09-23 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=358823

Aaron  changed:

   What|Removed |Added

 CC||spudd5...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmailtransport] [Bug 399003] New: Cannot configure sendmail (postfix) as the outgoing mail transport

2018-09-23 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=399003

Bug ID: 399003
   Summary: Cannot configure sendmail (postfix) as the outgoing
mail transport
   Product: kmailtransport
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: spudd5...@gmail.com
CC: k...@fietze-home.de, kdepim-b...@kde.org,
mon...@kde.org, psychon...@nothingisreal.com,
roucaries.bastien+b...@gmail.com, spudd5...@gmail.com
Depends on: 358823
  Target Milestone: ---

+++ This bug was initially created as a clone of Bug #358823 +++


SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

EXPECTED RESULT


ACTUAL RESULT


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Since the update to kdepim 15.x I can no longer use a properly working postfix
installation and the binary "sendmail".

This has the disadvantage to be forced to configure postfaix *and* kmail2's
SMTP in parallel, or to enable SMTP on the local postfix installation.



Reproducible: Always


Actual Results:  
"Failed to transport message".



kmail2 5.1.1
kdepim 15.12.1
openSUSE Tumbleweed
postfix 2.11.7, properly working on the command line (mail) and with other MUAs


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=358823
[Bug 358823] Cannot configure sendmail (postfix) as the outgoing mail transport
-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 358823] Cannot configure sendmail (postfix) as the outgoing mail transport

2018-09-23 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=358823

Aaron  changed:

   What|Removed |Added

 Blocks||399003


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=399003
[Bug 399003] Cannot configure sendmail (postfix) as the outgoing mail transport
-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 492489] Akonadi EWS agent cannot sync in background

2024-09-30 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=492489

Aaron  changed:

   What|Removed |Added

 CC||mull...@adelie.io

--- Comment #1 from Aaron  ---
I think your "Observed" and "Expected" results may be backwards. 

However, I'm seeing the same behavior with version 6.1.2 on Gentoo. Also, I
also can see the "org.kde.pim.ews: Streaming request timeout - restarting"
messages recurring in the log at the set polling interval. Manual mail checks
work however. For what it's worth, I also have an IMAP account configured that
seems to poll without issue. Only automatic polling EWS is broken.

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 496313] Sent messages cannot be edited more than once.

2024-11-18 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=496313

--- Comment #4 from Aaron  ---
(In reply to James Graham from comment #1)
> So editing using the hover button should always work, this is because the
> issue is the way in which Matrix handles edits. They're actually their own
> events, they just get hidden by Neochat.

Perhaps it is the UI that is failing here using the hover button, rather than
how Neochat is actually handling the edit. On the second edit just using the
hover button, the original text is not displayed in the edit, just the "check"
and "x" buttons.

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 496313] New: Sent messages cannot be edited more than once.

2024-11-15 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=496313

Bug ID: 496313
   Summary: Sent messages cannot be edited more than once.
Classification: Applications
   Product: NeoChat
   Version: 24.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: mull...@adelie.io
CC: c...@carlschwan.eu, j...@redstrate.com
  Target Milestone: ---

SUMMARY

Sent message can be edited without issue one time, either using s/g replacement
or the edit button on the message. However, editing the message a second time
fails with both methods. The s/g replacement for the second edit simply shows
no change. Using the edit button for the second edit does not display original
text to edit (although adding a new message in place of the original seems to
be allowed). When using the s/g replacement method exclusively, the second
failed edit attempt will cause the message to disappear for the user on other
clients (Element). The recipient will receive the first edit.

STEPS TO REPRODUCE
1.  Send a message
2.  Edit the message
3.  Edit the message again (particularly with s/g)
4. Try to edit the message again

OBSERVED RESULT
Depending upon the number of edit attempts, subsequent edits are either simply
not applied, or the message disappears for the sender on other Matrix clients
(Element). The recipient only receives the first edit.

EXPECTED RESULT
One expects all subsequent edits to work as the first.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.3

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 469312] Window focus and alt-tab are broken with Activities

2025-01-01 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=469312

--- Comment #5 from Aaron  ---
So, I was able to fix this behavior in my case by removing a kde file, but
unfortunately I'm not exactly sure which file it was. I think it was removing
the ~/.config/kdeglobals file, but of course I could be mistaken. However,
removing some configuration file fixed the issue in my case. I wish I had more
information, or that I had the forethought at the time to save the old version
of that file for comparison.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 351701] akonadi resources doesn't wait for kwallet with gpg key to open

2025-02-05 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=351701

Aaron  changed:

   What|Removed |Added

 CC||mull...@adelie.io

--- Comment #10 from Aaron  ---
When using  Oauth2 authentication with Office365, this bug tends to cause me to
go through the entire authentication process for MS Exchange every time I log
in. As a temporary measure, disabling automatic connection to the network
interface seems to provide time to unlock Kwallet (GPG). This is very annoying,
but not as annoying as going through the Office365 Oauth2 authentication
process at every login.

It seems Akonadi resources will wait for the network will come up, just not for
Kwallet to open. Can the functionality already built into Akonadi that waits
for network be extended to wait for Kwallet?

Akonadi Server Version: 6.2.3 (24.08.3)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 501226] Bug fix

2025-03-08 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

--- Comment #9 from Aaron  ---
Sorry that system is gone not installing anymore got frustrated useing 
everything the latest update is the problem. get rid of it problems 
gone. I am not a long user of linux i just need to work like it did for 
8 months ago. Thanks for all your time i am back on system before friday 
. isent in the kde bug tool service report. set my

problem reporting to the max and let it send in what it need. Thanks fro 
your time.

On 3/8/25 5:19 PM, cwo wrote:
> https://bugs.kde.org/show_bug.cgi?id=501226
>
> --- Comment #8 from cwo  ---
> (In reply to Aaron from comment #7)
>> PID: 10990(kwin_wayland)
>>  UID: 1000 (anichols)
>>  GID: 1000 (anichols)
>>   Signal: 11 (SEGV)
>>Timestamp: Sat 2025-03-08 13:47:41 CST (12min ago)
> This looks like the correct crash, but you did not actually include the
> backtrace. Please follow the instructions in the link I gave you, including 
> the
> "coredumpctl gdb [paste the number]". As it is, your report contains nothing 
> we
> can use to identify what the cause of the crash might be.
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 501226] New: Bug fix

2025-03-08 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

Bug ID: 501226
   Summary: Bug fix
Classification: Plasma
   Product: kwin
   Version: git-stable-Plasma/6.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ac...@live.com
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Upgrade to new version 6.3.2.1-2.fc41
2. open up Pika Backup, Backup, k3b and Brasero.
3. 

OBSERVED RESULT
Tell me kwin crashes after update

EXPECTED RESULT
not installing kwin-wayland
Upgrade to new version 6.3.2.1-2.fc41
Release notes:
Kwin 6.3.2.1 crash fix

SOFTWARE/OS VERSIONS
Windows: Fedora 41
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version:  6.3.2.1
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 501226] Bug fix

2025-03-08 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

--- Comment #5 from Aaron  ---
Thu 2025-02-20 17:12:51 CST  5612 1000 1000 SIGABRT missing 
  /usr/bin/systemsettings >
Thu 2025-02-20 17:30:56 CST  7196 1000 1000 SIGSEGV missing 
  /usr/libexec/kinfocenter-opengl-helper >
Thu 2025-02-20 18:06:34 CST  9019 1000 1000 SIGABRT missing 
  /usr/bin/systemsettings >
Thu 2025-02-20 18:14:22 CST 10526 1000 1000 SIGABRT missing 
  /usr/bin/systemsettings >
Fri 2025-02-21 22:25:22 CST  8344 1000 1000 SIGSEGV missing 
  /usr/libexec/kinfocenter-opengl-helper >
Sat 2025-02-22 06:38:37 CST  3957 1000 1000 SIGSEGV present 
  /usr/bin/epsonscan2 >
Sat 2025-02-22 08:17:52 CST  7267 1000 1000 SIGSEGV present 
  /snap/facebook-webapp/1/usr/bin/webapp-conta>
Sat 2025-02-22 08:25:12 CST  9838 1000 1000 SIGSEGV present 
  /snap/facebook-webapp/1/usr/bin/webapp-conta>
Sat 2025-02-22 21:17:27 CST  3133 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Mon 2025-02-24 19:19:11 CST  3038 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Wed 2025-02-26 18:02:50 CST  4352 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Thu 2025-02-27 18:03:31 CST  4276 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Thu 2025-02-27 18:32:24 CST  9994 1000 1000 SIGSEGV present 
  /usr/bin/epsonscan2 >
Sat 2025-03-01 01:46:28 CST  3221 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover >
Sat 2025-03-01 02:04:03 CST  4515 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover >
Sat 2025-03-01 02:32:17 CST  4955 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover >
Sat 2025-03-08 13:40:41 CST  1938 1000 1000 SIGSEGV 
inaccessible/usr/bin/kwin_wayland >
Sat 2025-03-08 13:40:41 CST  3012 1000 1000 SIGSEGV present 
  /usr/libexec/kf6/kioworker >
Sat 2025-03-08 13:43:14 CST  5705 1000 1000 SIGSEGV 
inaccessible/usr/bin/kwin_wayland >
Sat 2025-03-08 13:44:27 CST  7382 1000 1000 SIGSEGV 
inaccessible/usr/bin/kwin_wayland >
Sat 2025-03-08 13:44:27 CST  7788 1000 1000 SIGSEGV present 
  /usr/libexec/kf6/kioworker >
Sat 2025-03-08 13:45:00 CST  8272 1000 1000 SIGSEGV 
inaccessible/usr/bin/kwin_wayland >
Sat 2025-03-08 13:45:00 CST  8656 1000 1000 SIGSEGV present 
  /usr/libexec/kf6/kioworker >
Sat 2025-03-08 13:46:49 CST  9042 1000 1000 SIGSEGV 
inaccessible/usr/bin/kwin_wayland >
Sat 2025-03-08 13:47:05 CST  9853 1000 1000 SIGSEGV 
inaccessible/usr/bin/kwin_wayland >
Sat 2025-03-08 13:47:22 CST 10405 1000 1000 SIGSEGV 
inaccessible/usr/bin/kwin_wayland >
lines 1-27


On 3/8/25 1:32 PM, cwo wrote:
> https://bugs.kde.org/show_bug.cgi?id=501226
>
> --- Comment #4 from cwo ---
> That's not the actual backtrace, just a list of crashes that you had (and the
> newest one was from a week ago).
>
> Can you be a bit more explicit about what the problem is? Mayb I'm
> misunderstanding you.
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 501226] Bug fix

2025-03-08 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

--- Comment #6 from Aaron  ---
PID: 8656(kioworker)
    UID: 1000 (anichols)
    GID: 1000 (anichols)
     Signal: 11 (SEGV)
  Timestamp: Sat 2025-03-08 13:45:00 CST (20min ago)
   Command Line: /usr/libexec/kf6/kioworker
/usr/lib64/qt6/plugins/kf6/kio/thumbnail.so thumbnail "" local:/run
/user/1000/plasmashellELonuA.3.kioworker.socket
     Executable: /usr/libexec/kf6/kioworker
Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
   Unit:user@1000.service
  User Unit: plasma-plasmashell.service
  Slice: user-1000.slice
  Owner UID: 1000 (anichols)
    Boot ID: c70917c5b2184e2d8abb6dc184e33e85
     Machine ID: c99faaa31c1941d49beb2fb61b176b8d
   Hostname: fedora
    Storage:
/var/lib/systemd/coredump/core.kioworker.1000.c70917c5b2184e2d8abb6dc184e33e85.8656.1741463100
00.zst (present)
   Size on Disk: 2.7M
    Package: kf6-kio/6.11.0-1.fc41
   build-id: b3951d9b63769127528bfe762f068f3b96cdff44
    Message: Process 8656 (kioworker) of user 1000 dumped core.

     Module [dso] from rpm mesa-25.0.0-2.fc41.x86_64
     Module libwebpmux.so.3 from rpm libwebp-1.5.0-1.fc41.x86_64
     Module libwebpdemux.so.2 from rpm
libwebp-1.5.0-1.fc41.x86_64
     Module libqwebp.so from rpm
qt6-qtimageformats-6.8.2-1.fc41.x86_64
     Module libqwbmp.so from rpm
qt6-qtimageformats-6.8.2-1.fc41.x86_64
     Module libjbig.so.2.1 from rpm jbigkit-2.1-30.fc41.x86_64
     Module libLerc.so.4 from rpm liblerc-4.0.0-7.fc41.x86_64
     Module libwebp.so.7 from rpm libwebp-1.5.0-1.fc41.x86_64
     Module libtiff.so.6 from rpm libtiff-4.6.0-6.fc41.x86_64
     Module libqtiff.so from rpm
qt6-qtimageformats-6.8.2-1.fc41.x86_64
     Module libmng.so.2 from rpm libmng-2.0.3-22.fc41.x86_64
     Module libqmng.so from rpm
qt6-qtimageformats-6.8.2-1.fc41.x86_64
     Module libqicns.so from rpm
qt6-qtimageformats-6.8.2-1.fc41.x86_64
     Module kimg_xcf.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_tga.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_sct.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_rgb.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module liblcms2.so.2 from rpm lcms2-2.16-4.fc41.x86_64
     Module libjasper.so.7 from rpm jasper-4.2.3-2.fc41.x86_64
     Module libraw.so.23 from rpm LibRaw-0.21.3-1.fc41.x86_64
     Module kimg_raw.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_ras.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_qoi.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_pxr.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_psd.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_pic.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_pfm.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_pcx.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_ora.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_kra.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module libjxl_cms.so.0.10 from rpm
jpegxl-0.10.4-1.fc41.x86_64
     Module libjxl_threads.so.0.10 from rpm
jpegxl-0.10.4-1.fc41.x86_64
     Module libjxl.so.0.10 from rpm jpegxl-0.10.4-1.fc41.x86_64
     Module kimg_jxl.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_jp2.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module libbrotlienc.so.1 from rpm brotli-1.1.0-5.fc41.x86_64
     Module libsharpyuv.so.0 from rpm libwebp-1.5.0-1.fc41.x86_64
     Module libopenh264.so.7 from rpm
openh264-2.4.1-2.fc41.x86_64
     Module libopenjp2.so.7 from rpm openjpeg-2.5.3-6.fc41.x86_64
     Module libheif.so.1 from rpm libheif-1.19.5-3.fc41.x86_64
     Module kimg_heif.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module kimg_hdr.so from rpm
kf6-kimageformats-6.11.0-1.fc41.x86_64
     Module libdeflate.so.0 from rpm
libdeflate-1.23-1.fc41.x86_64
     Module libOpenEXRCore-3_2.so.31 from rpm
openexr-3.2.4-3.fc41.x86_64
     Module libIlmThread-3_2.so.31 from rpm
openexr-3.2.4-3.fc41.x86_64
     Module libImath-3_1.so.29 from rpm
imath-3.1.12-1.fc41.x86_64
     Module libIex-3_2.so.31 from rpm openexr-3.2.4-3.fc41.x86_64
     Module libOpenEXR-3_2.so.31 from rpm
openexr-3.

[kwin] [Bug 501226] Bug fix

2025-03-08 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

--- Comment #7 from Aaron  ---
PID: 10990(kwin_wayland)
    UID: 1000 (anichols)
    GID: 1000 (anichols)
     Signal: 11 (SEGV)
  Timestamp: Sat 2025-03-08 13:47:41 CST (12min ago)
   Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0
--xwayland-fd 8 --xwayland-fd 9 --xway
land-display :0 --xwayland-xauthority /run/user/1000/xauth_fBzyXO --xwayland
     Executable: /usr/bin/kwin_wayland
Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service
   Unit:user@1000.service
  User Unit: plasma-kwin_wayland.service
  Slice: user-1000.slice
  Owner UID: 1000 (anichols)
    Boot ID: c70917c5b2184e2d8abb6dc184e33e85
     Machine ID: c99faaa31c1941d49beb2fb61b176b8d
   Hostname: fedora
    Storage:
/var/lib/systemd/coredump/core.kwin_wayland.1000.c70917c5b2184e2d8abb6dc184e33e85.10990.174146
326100.zst (inaccessible)
    Package: kwin/6.3.2.1-2.fc41
   build-id: 7189160b0c3b62d5edef7f5b11dbd9bf2fd5ce53
    Message: Process 10990 (kwin_wayland) of user 1000 dumped core.

     Module [dso] from rpm qt6-qtsensors-6.8.2-1.fc41.x86_64
     Module libqsvg.so from rpm qt6-qtsvg-6.8.2-1.fc41.x86_64
     Module libjpeg.so.62 from rpm
libjpeg-turbo-3.0.2-3.fc41.x86_64
     Module libqjpeg.so from rpm qt6-qtbase-6.8.2-3.fc41.x86_64
     Module libqico.so from rpm qt6-qtbase-6.8.2-3.fc41.x86_64
     Module libqgif.so from rpm qt6-qtbase-6.8.2-3.fc41.x86_64
     Module libKF6SonnetCore.so.6 from rpm
kf6-sonnet-6.11.0-1.fc41.x86_64
     Module libsonnetquickplugin.so from rpm
kf6-sonnet-6.11.0-1.fc41.x86_64
     Module liborg_kde_desktop_private.so from rpm
kf6-qqc2-desktop-style-6.11.0-1.fc41.x86_64
     Module libqqc2desktopstyleplugin.so from rpm
kf6-qqc2-desktop-style-6.11.0-1.fc41.x86_64
     Module libKirigamiPrivate.so.6 from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiPrivateplugin.so from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libSPIRV-Tools-opt.so from rpm
spirv-tools-2024.4-1.fc41.x86_64
     Module libQt6ShaderTools.so.6 from rpm
qt6-qtshadertools-6.8.2-1.fc41.x86_64
     Module libqtgraphicaleffectsprivateplugin.so from rpm
qt6-qt5compat-6.8.2-1.fc41.x86_64
     Module libquickwindowplugin.so from rpm
qt6-qtdeclarative-6.8.2-1.fc41.x86_64
     Module liborg_kde_desktop.so from rpm
kf6-qqc2-desktop-style-6.11.0-1.fc41.x86_64
     Module libQt6QuickControls2Basic.so.6 from rpm
qt6-qtdeclarative-6.8.2-1.fc41.x86_64
     Module libqtquickcontrols2basicstyleplugin.so from rpm
qt6-qtdeclarative-6.8.2-1.fc41.x86_64
     Module libqtquickcontrols2plugin.so from rpm
qt6-qtdeclarative-6.8.2-1.fc41.x86_64
     Module libcorebindingsplugin.so from rpm
kf6-ksvg-6.11.0-1.fc41.x86_64
     Module libPlasma.so.6 from rpm libplasma-6.3.2-1.fc41.x86_64
     Module libPlasmaQuick.so.6 from rpm
libplasma-6.3.2-1.fc41.x86_64
     Module libqtquicktemplates2plugin.so from rpm
qt6-qtdeclarative-6.8.2-1.fc41.x86_64
     Module libKF6KCMUtilsCore.so.6 from rpm
kf6-kcmutils-6.11.0-1.fc41.x86_64
     Module libKF6KCMUtilsQuick.so.6 from rpm
kf6-kcmutils-6.11.0-1.fc41.x86_64
     Module libkcmutilsqmlplugin.so from rpm
kf6-kcmutils-6.11.0-1.fc41.x86_64
     Module libplasmaextracomponentsplugin.so from rpm
libplasma-6.3.2-1.fc41.x86_64
     Module liborg_kde_plasmacomponents3.so from rpm
libplasma-6.3.2-1.fc41.x86_64
     Module libKF6ItemModels.so.6 from rpm
kf6-kitemmodels-6.11.0-1.fc41.x86_64
     Module libKF6Runner.so.6 from rpm
kf6-krunner-6.11.0-1.fc41.x86_64
     Module libmilouqmlplugin.so from rpm
plasma-milou-6.3.2-1.fc41.x86_64
     Module libeffectsplugin.so from rpm
kwin-6.3.2.1-2.fc41.x86_64
     Module libKirigamiLayouts.so.6 from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiLayoutsplugin.so from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiDialogs.so.6 from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiDialogsplugin.so from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiDelegates.so.6 from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiDelegatesplugin.so from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiPrimitives.so.6 from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigamiPrimitivesplugin.so from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64
     Module libKirigami.so.6 from rpm
kf6-kirigami-6.11.0-1.fc41.x86_64

[kwin] [Bug 501226] Bug fix

2025-03-08 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

--- Comment #2 from Aaron  ---
Thu 2025-02-20 17:12:51 CST  5612 1000 1000 SIGABRT missing 
  /usr/bin/systemsettings >
Thu 2025-02-20 17:30:56 CST  7196 1000 1000 SIGSEGV missing 
  /usr/libexec/kinfocenter-opengl-helper >
Thu 2025-02-20 18:06:34 CST  9019 1000 1000 SIGABRT missing 
  /usr/bin/systemsettings >
Thu 2025-02-20 18:14:22 CST 10526 1000 1000 SIGABRT missing 
  /usr/bin/systemsettings >
Fri 2025-02-21 22:25:22 CST  8344 1000 1000 SIGSEGV missing 
  /usr/libexec/kinfocenter-opengl-helper >
Sat 2025-02-22 06:38:37 CST  3957 1000 1000 SIGSEGV present 
  /usr/bin/epsonscan2 >
Sat 2025-02-22 08:17:52 CST  7267 1000 1000 SIGSEGV present 
  /snap/facebook-webapp/1/usr/bin/webapp-container>
Sat 2025-02-22 08:25:12 CST  9838 1000 1000 SIGSEGV present 
  /snap/facebook-webapp/1/usr/bin/webapp-container>
Sat 2025-02-22 21:17:27 CST  3133 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Mon 2025-02-24 19:19:11 CST  3038 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Wed 2025-02-26 18:02:50 CST  4352 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Thu 2025-02-27 18:03:31 CST  4276 1000 1000 SIGSEGV present 
  /usr/libexec/kinfocenter-opengl-helper >
Thu 2025-02-27 18:32:24 CST  9994 1000 1000 SIGSEGV present 
  /usr/bin/epsonscan2 >
Sat 2025-03-01 01:46:28 CST  3221 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover >
Sat 2025-03-01 02:04:03 CST  4515 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover >
Sat 2025-03-01 02:32:17 CST  4955 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover >
lines 1-17/17 (END)


On 3/8/25 7:28 AM, cwo wrote:
> https://bugs.kde.org/show_bug.cgi?id=501226
>
> cwo changed:
>
> What|Removed |Added
> 
>   Status|REPORTED|NEEDSINFO
>   CC||cwo@posteo.net
>   Resolution|--- |BACKTRACE
>
> --- Comment #1 from cwo ---
>
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. Can you please attach a backtrace of the crash using the coredumpctl
> command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
>
> Thanks!
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 501226] Bug fix

2025-03-09 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

--- Comment #10 from Aaron  ---
Thanks for all you did today new update came out fixed everything. Grate 
job on all love kde and fedora 41.

On 3/8/25 6:02 PM, Aaron Nichols wrote:
> Sorry that system is gone not installing anymore got frustrated useing 
> everything the latest update is the problem. get rid of it problems 
> gone. I am not a long user of linux i just need to work like it did 
> for 8 months ago. Thanks for all your time i am back on system before 
> friday . isent in the kde bug tool service report. set my
>
> problem reporting to the max and let it send in what it need. Thanks 
> fro your time.
>
> On 3/8/25 5:19 PM, cwo wrote:
>> https://bugs.kde.org/show_bug.cgi?id=501226
>>
>> --- Comment #8 from cwo  ---
>> (In reply to Aaron from comment #7)
>>> PID: 10990(kwin_wayland)
>>>      UID: 1000 (anichols)
>>>      GID: 1000 (anichols)
>>>       Signal: 11 (SEGV)
>>>    Timestamp: Sat 2025-03-08 13:47:41 CST (12min ago)
>> This looks like the correct crash, but you did not actually include the
>> backtrace. Please follow the instructions in the link I gave you, 
>> including the
>> "coredumpctl gdb [paste the number]". As it is, your report contains 
>> nothing we
>> can use to identify what the cause of the crash might be.
>>

-- 
You are receiving this mail because:
You are watching all bug changes.

[krdc] [Bug 485094] When click Scale button image disappears

2025-04-09 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=485094

Aaron  changed:

   What|Removed |Added

 CC|kde@aarontc.com |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 501226] Bug fix

2025-03-15 Thread Aaron
https://bugs.kde.org/show_bug.cgi?id=501226

--- Comment #3 from Aaron  ---
Fedora 41 threads are complaining with the updates

crashing desktops I used rescuezilla went to before the update and none 
of the updates are on my computer running good for now.

kwin-common

Upgrade to new version 6.3.2.1-2.fc41 Release notes:

Kwin 6.3.2.1 crash fix


  kwin-libs

Upgrade to new version 6.3.2.1-2.fc41 Release notes:

Kwin 6.3.2.1 crash fix


  kwin-wayland

Upgrade to new version 6.3.2.1-2.fc41 Release notes:

Kwin 6.3.2.1 crash fix


  kwin

Upgrade to new version 6.3.2.1-2.fc41 Release notes:

Kwin 6.3.2.1 crash fix

On 3/8/25 7:28 AM, cwo wrote:
> https://bugs.kde.org/show_bug.cgi?id=501226
>
> cwo changed:
>
> What|Removed |Added
> 
>   Status|REPORTED|NEEDSINFO
>   CC||cwo@posteo.net
>   Resolution|--- |BACKTRACE
>
> --- Comment #1 from cwo ---
>
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. Can you please attach a backtrace of the crash using the coredumpctl
> command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
>
> Thanks!
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 372754] New: ksmserver-logout-greeter segfault with nvidia 375.10

2016-11-21 Thread Aaron Digulla
https://bugs.kde.org/show_bug.cgi?id=372754

Bug ID: 372754
   Summary: ksmserver-logout-greeter segfault with nvidia 375.10
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Look & Feel package
  Assignee: plasma-b...@kde.org
  Reporter: digu...@hepe.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Can't logout or restart anymore. When I select "logoff", KDE asks me what I
want to do *again* (plus 30 Second timeout). Then something crashes. Here is
the log:

Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:68
#7  0x7ffaa247ce1c in ?? () from /usr/lib64/libGLX_nvidia.so.0
#8  0x7ffaa2453dc8 in ?? () from /usr/lib64/libGLX_nvidia.so.0
#9  0x7ffa997ffe89 in ?? () from /usr/lib64/libEGL.so.1
#10 0x7ffabe2c3238 in _dl_fini () at dl-fini.c:257
#11 0x7ffab9f8b139 in __run_exit_handlers (status=0, listp=0x7ffaba2f15a0
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#12 0x7ffab9f8b185 in __GI_exit (status=) at exit.c:104
#13 0x7ffab9f746ec in __libc_start_main (main=0x405e80 ,
argc=6, argv=0x7ffe1bc9c7b8, init=, fini=,
rtld_fini=, stack_end=0x7ffe1bc9c7a8) at libc-start.c:323
#14 0x00406339 in _start () at ../sysdeps/x86_64/start.S:118

This is with the NVIDIA binary driver version 375.10 (I have a ASUS 1050 Ti
with Pascal architecture).

This worked yesterday; it started to fail after updating these packages:

MozillaFirefox-translations-common-50.0-39.2.x86_64 Mo 21 Nov 2016 20:22:50 CET
MozillaFirefox-50.0-39.2.x86_64   Mo 21 Nov 2016 20:22:48 CET
libqt5-qtwebengine-5.6.1-4.2.x86_64   Mo 21 Nov 2016 20:22:45 CET
mozilla-nss-3.26.2-32.1.x86_64Mo 21 Nov 2016 20:22:43 CET
Mesa-libGL-devel-11.2.2-155.1.x86_64  Mo 21 Nov 2016 20:22:43 CET
Mesa-libEGL-devel-11.2.2-155.1.x86_64 Mo 21 Nov 2016 20:22:43 CET
xorg-x11-Xvnc-1.6.0-3.1.x86_64Mo 21 Nov 2016 20:22:42 CET
sg3_utils-1.43-4.1.x86_64 Mo 21 Nov 2016 20:22:42 CET
pciutils-3.2.1-11.1.x86_64Mo 21 Nov 2016 20:22:42 CET
Mesa-libGL1-32bit-11.2.2-155.1.x86_64 Mo 21 Nov 2016 20:22:42 CET
Mesa-libGL1-11.2.2-155.1.x86_64   Mo 21 Nov 2016 20:22:42 CET
Mesa-libEGL1-32bit-11.2.2-155.1.x86_64Mo 21 Nov 2016 20:22:42 CET
Mesa-libEGL1-11.2.2-155.1.x86_64  Mo 21 Nov 2016 20:22:42 CET
libvdpau_va_gl1-0.4.2-3.1.x86_64  Mo 21 Nov 2016 20:22:42 CET
libsoftokn3-3.26.2-32.1.x86_64Mo 21 Nov 2016 20:22:42 CET
libKF5Su5-lang-5.26.0-3.1.noarch  Mo 21 Nov 2016 20:22:42 CET
timezone-2016i-31.1.x86_64Mo 21 Nov 2016 20:22:41 CET
tigervnc-1.6.0-3.1.x86_64 Mo 21 Nov 2016 20:22:41 CET
Mesa-libGLESv2-2-11.2.2-155.1.x86_64  Mo 21 Nov 2016 20:22:41 CET
Mesa-dri-nouveau-11.2.2-155.1.x86_64  Mo 21 Nov 2016 20:22:41 CET
libKF5Su5-5.26.0-3.1.x86_64   Mo 21 Nov 2016 20:22:41 CET
shadow-4.2.1-4.1.x86_64   Mo 21 Nov 2016 20:22:40 CET
mozilla-nss-certs-3.26.2-32.1.x86_64  Mo 21 Nov 2016 20:22:40 CET
libwayland-egl1-11.2.2-155.1.x86_64   Mo 21 Nov 2016 20:22:40 CET
libvdpau_nouveau-11.2.2-155.1.x86_64  Mo 21 Nov 2016 20:22:40 CET
libsgutils2-2-1.43-4.1.x86_64 Mo 21 Nov 2016 20:22:40 CET
libpci3-3.2.1-11.1.x86_64 Mo 21 Nov 2016 20:22:40 CET
libjasper1-32bit-1.900.14-167.1.x86_64Mo 21 Nov 2016 20:22:40 CET
libjasper1-1.900.14-167.1.x86_64  Mo 21 Nov 2016 20:22:40 CET
libgbm1-32bit-11.2.2-155.1.x86_64 Mo 21 Nov 2016 20:22:40 CET
libgbm1-11.2.2-155.1.x86_64   Mo 21 Nov 2016 20:22:40 CET
Mesa-libva-11.2.2-155.1.x86_64Mo 21 Nov 2016 20:22:39 CET
Mesa-libglapi0-32bit-11.2.2-155.1.x86_64  Mo 21 Nov 2016 20:22:39 CET
Mesa-libglapi0-11.2.2-155.1.x86_64Mo 21 Nov 2016 20:22:39 CET
Mesa-32bit-11.2.2-155.1.x86_64Mo 21 Nov 2016 20:22:39 CET
libXvnc1-1.6.0-3.1.x86_64 Mo 21 Nov 2016 20:22:39 CET
libfreebl3-3.26.2-32.1.x86_64 Mo 21 Nov 2016 20:22:39 CET
libesmtp-1.0.6-19.1.x86_64Mo 21 Nov 2016 20:22:39 CET
Mesa-11.2.2-155.1.x86_64  Mo 21 Nov 2016 20:22:38 CET

I can reboot from the console. It feels like this is a bug somewhere in the 3D
code of Mesa and NVIDIA but I don't know how to proceed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 372754] ksmserver-logout-greeter segfault with nvidia 375.10

2016-11-21 Thread Aaron Digulla
https://bugs.kde.org/show_bug.cgi?id=372754

Aaron Digulla  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Aaron Digulla  ---
Upgrading to NVIDIA 375.*20* fixes the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 372938] New: merge imported operations wrong warning about different amounts

2016-11-25 Thread Aaron Wolf
https://bugs.kde.org/show_bug.cgi?id=372938

Bug ID: 372938
   Summary: merge imported operations wrong warning about
different amounts
   Product: skrooge
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: wolft...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

I had a split entry that had several categories, when I tried to merge that
with the corresponding imported operation, I got a warning asking about forcing
the merge since the amounts were different. But the amounts were exactly the
same.

I'm using Skrooge 2.5 in KDE Neon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 373054] New: Lots of crashes at login and logout with this version of KDE and openSUSE Leap 42.2

2016-11-28 Thread Aaron Digulla
https://bugs.kde.org/show_bug.cgi?id=373054

Bug ID: 373054
   Summary: Lots of crashes at login and logout with this version
of KDE and openSUSE Leap 42.2
   Product: kwin
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: digu...@hepe.com
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.27-2-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
3D driver: NVidia 375.20
nouveau is disabled.
I'm having a lot of problems lately with openSUSE Leap 42.2 and KDE. It feels
that every package update breaks the 3D libraries in some way.

My guess is that there is a bug somewhere between the kernel, the NVIDIA driver
and KDE. KDE apps like kwin, kmix, sddm-greeter (whatever that is) crash when I
restart or when I try to log out.

The log out is especially bad since after the update, I have to switch to the
console to reboot since the "hey, I want to leave" dialog (sddm-greeter?)
crashes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3872f86940 (LWP 2803))]

Thread 2 (Thread 0x7f3853fff700 (LWP 2819)):
#0  0x7f38726edb03 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f386fdc0849 in qt_safe_select (nfds=8, fdread=0x7f384c000a78,
fdwrite=0x7f384c000d08, fdexcept=0x7f384c000f98, orig_timeout=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f386fdc20c3 in QEventDispatcherUNIXPrivate::doSelect
(this=this@entry=0x7f384c0008e0, flags=..., flags@entry=..., timeout=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#3  0x7f386fdc2527 in QEventDispatcherUNIX::processEvents
(this=0x7f384c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#4  0x7f386fd71fdb in QEventLoop::exec (this=this@entry=0x7f3853ffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f386fbacf1a in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7f386997f1d5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f386fbb19e9 in QThreadPrivate::start (arg=0x7f3869be7ce0) at
thread/qthread_unix.cpp:341
#8  0x7f38729b6734 in start_thread (arg=0x7f3853fff700) at
pthread_create.c:334
#9  0x7f38726f4d3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f3872f86940 (LWP 2803)):
[KCrash Handler]
#6  0x7f38729c0490 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#7  __lll_unlock_elision (lock=0x7f3852def008, private=128) at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#8  0x7f387163bc2b in KSharedDataCache::Private::unlock (this=0x212f9e0) at
/usr/src/debug/kcoreaddons-5.26.0/src/lib/caching/kshareddatacache.cpp:1226
#9  KSharedDataCache::Private::CacheLocker::~CacheLocker (this=, __in_chrg=) at
/usr/src/debug/kcoreaddons-5.26.0/src/lib/caching/kshareddatacache.cpp:1298
#10 KSharedDataCache::find (this=0x212d4d0, key=...,
destination=destination@entry=0x7ffc8cfa2740) at
/usr/src/debug/kcoreaddons-5.26.0/src/lib/caching/kshareddatacache.cpp:1580
#11 0x7f3866e35998 in KIconLoaderPrivate::findCachedPixmapWithPath
(this=0x212cc70, key=..., data=..., path=...) at
/usr/src/debug/kiconthemes-5.26.0/src/kiconloader.cpp:984
#12 0x7f3866e368a0 in KIconLoader::loadIcon (this=0x7f386704ccd0
<(anonymous namespace)::Q_QGS_globalIconLoader::innerFunction()::holder>,
_name=..., group=group@entry=KIconLoader::Desktop, size=16, state=0,
overlays=..., path_store=path_store@entry=0x0,
canReturnNull=canReturnNull@entry=false) at
/usr/src/debug/kiconthemes-5.26.0/src/kiconloader.cpp:1277
#13 0x7f3866e2dc78 in KIconEngine::pixmap (this=, size=...,
mode=, state=) at
/usr/src/debug/kiconthemes-5.26.0/src/kiconengine.cpp:102
#14 0x7f3870342839 in QIcon::pixmap (this=this@entry=0x7ffc8cfa2ae0,
window=window@entry=0x0, size=..., mode=mode@entry=QIcon::Normal,
state=state@entry=QIcon::Off) at image/qicon.cpp:839
#15 0x7f38703428da in QIcon::pixmap (this=this@entry=0x7ffc8cfa2ae0,
size=..., mode=mode@entry=QIcon::Normal, state=state@entry=QIcon::Off) at
image/qicon.cpp:775
#16 0x7f3851fc034c in QIcon::pixmap (state=QIcon::Off, mode=QIcon::Normal,
h=16, w=16, this=0x7ffc8cfa2ae0) at /usr/include/qt5/QtGui/qicon.h:77
#17 KWindowSystemPrivateX11::iconFromNetWinInfo (this=,
width=16, height=16, scale=, flags=,
info=0x23c1b20) at
/usr/src/debug/kwindowsystem-5.26.0/src/platforms/xcb/kwindowsystem.cpp:772
#18 0x7f38713b0e02 in KWindowSystem::icon (win=8388616,
width=width@entry=16, height=height@entry=16, scale=scale@entry=true,
flags=flags@entry=12, info=0x23c1b20) at
/usr/src/debug/kwindowsystem-5.26.0/src/kwindowsystem.cpp:512
#19 0x7f3872

[frameworks-kcoreaddons] [Bug 373054] Lots of crashes at login and logout with this version of KDE and openSUSE Leap 42.2

2016-11-29 Thread Aaron Digulla
https://bugs.kde.org/show_bug.cgi?id=373054

--- Comment #2 from Aaron Digulla  ---
I have 100GB free on /home and 160GB on root.

My guess is that this is the /home file system which could be corrupt. Any idea
which folder? ~/.kde4/?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 373265] New: Crash after closing Firefox

2016-12-04 Thread Aaron Digulla
https://bugs.kde.org/show_bug.cgi?id=373265

Bug ID: 373265
   Summary: Crash after closing Firefox
   Product: plasmashell
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: digu...@hepe.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.27-2-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
I just restarted Firefox when the plasma bar suddenly vanished.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd8e742a8c0 (LWP 11488))]

Thread 29 (Thread 0x7fd794fbd700 (LWP 7611)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fd8e124665b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x977d560) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x7cc0a30,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7fd8e513e4eb in ?? () from /usr/lib64/libQt5Quick.so.5
#4  0x7fd8e513e995 in ?? () from /usr/lib64/libQt5Quick.so.5
#5  0x7fd8e12459e9 in QThreadPrivate::start (arg=0x7cc09b0) at
thread/qthread_unix.cpp:341
#6  0x7fd8e035a734 in start_thread (arg=0x7fd794fbd700) at
pthread_create.c:334
#7  0x7fd8e0b59d3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 28 (Thread 0x7fd7abffe700 (LWP 27077)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fd8e124665b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x4004250) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x5f91fd0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7fd8e513e4eb in ?? () from /usr/lib64/libQt5Quick.so.5
#4  0x7fd8e513e995 in ?? () from /usr/lib64/libQt5Quick.so.5
#5  0x7fd8e12459e9 in QThreadPrivate::start (arg=0x5f91f50) at
thread/qthread_unix.cpp:341
#6  0x7fd8e035a734 in start_thread (arg=0x7fd7abffe700) at
pthread_create.c:334
#7  0x7fd8e0b59d3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 27 (Thread 0x7fd7c1724700 (LWP 27076)):
#0  0x7fd8d76e1a7d in ?? () from
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#1  0x7fd8d76e2bed in ?? () from
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7fd8d76e2fad in ?? () from
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#3  0x7fd8d76e384a in ?? () from
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#4  0x7fd8d7f5fa14 in pa_mainloop_dispatch () from /usr/lib64/libpulse.so.0
#5  0x7fd8d7f5fdea in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0
#6  0x7fd8d7f5fe90 in pa_mainloop_run () from /usr/lib64/libpulse.so.0
#7  0x7fd8d7f6e006 in ?? () from /usr/lib64/libpulse.so.0
#8  0x7fd8d76f3408 in ?? () from
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#9  0x7fd8e035a734 in start_thread (arg=0x7fd7c1724700) at
pthread_create.c:334
#10 0x7fd8e0b59d3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fd7c08c7700 (LWP 27074)):
#0  0x7fd8dd25a7b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fd8dd219205 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd8dd21942c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd8e145832b in QEventDispatcherGlib::processEvents
(this=0x7fd79c011500, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fd8e1405fdb in QEventLoop::exec (this=this@entry=0x7fd7c08c6cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fd8e1240f1a in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7fd8e454c9b8 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7fd8e12459e9 in QThreadPrivate::start (arg=0x573da20) at
thread/qthread_unix.cpp:341
#8  0x7fd8e035a734 in start_thread (arg=0x7fd7c08c7700) at
pthread_create.c:334
#9  0x7fd8e0b59d3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7fd7ab5f0700 (LWP 26818)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fd8e124665b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x588b530) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x570b800,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7fd8e513e4eb in ?? () from /usr/lib64/libQt5Quick.so.5
#4  0x7fd8e513e995 in ?? () from /usr/lib64/l

[Discover] [Bug 449813] New: Adding repos causes apt to error out about gpg key

2022-02-08 Thread Aaron Honeycutt
https://bugs.kde.org/show_bug.cgi?id=449813

Bug ID: 449813
   Summary: Adding repos causes apt to error out about gpg key
   Product: Discover
   Version: 5.24.0
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PackageKit
  Assignee: lei...@leinir.dk
  Reporter: aaronhoneyc...@kubuntu.org
CC: aleix...@kde.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
***

Adding a PPA/repo using Software Sources does not add the GPG key so apt errors
out. This maybe an issue with a Ubuntu package but I'm not sure.

STEPS TO REPRODUCE
1. Open Discover then click Settings
2. Click Software Sources then click Other software
3. Use the Add button to add a repo like:

https://dl.google.com/linux/chrome/deb/

OBSERVED RESULT

When you run updates apt is not happy as it is missing the GPG key to use the
repo securely.

EXPECTED RESULT

When you run updates everything is happy.

SOFTWARE/OS VERSIONS
Linux: 5.15.0-18-generic
(available in About System)
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 449813] Adding repos causes apt to error out about gpg key

2022-02-11 Thread Aaron Honeycutt
https://bugs.kde.org/show_bug.cgi?id=449813

--- Comment #2 from Aaron Honeycutt  ---
It was tough to tell if this is a Ubuntu issue or upstream. Having a UI would
be good indeed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 450686] New: Kate window always opens too small

2022-02-21 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=450686

Bug ID: 450686
   Summary: Kate window always opens too small
   Product: kate
   Version: 21.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

SUMMARY
For some reason, every time I create a new kate session, kate opens in a corner
of my screen and the window is far too small to use. I do not see any overrides
 There are no special window settings or application settings as far as I can
tell.

I might add that my desktop setup consists of two 1920x1200 displays and two
3840x2160 displays. The primary displays are the 3840x2160 screens and this is
where new sessions are created.

I do not see this issue with other KDE applications.

STEPS TO REPRODUCE
1.  Start a new KDE session, i.e. on the command line "kate -n"

OBSERVED RESULT
Kate appears in a corner of the screen and defaults to only 20 columns.

EXPECTED RESULT
I expect a reasonably sized Kate window that can display at least 80 columns
without having to resize it.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: OpenSUSE 15.3
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version:  5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

It appears that these settings are stored in the anonymous session, though even
though I resize the window before closing the new settings do not seem to take
effect. If I manually edit the file it still reverts to the old settings,
though I have not tried closing all instances of Kate and I have many active
instances since I'm in the middle of several big projects.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 450733] New: Suggest new file name dialog broken

2022-02-22 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=450733

Bug ID: 450733
   Summary: Suggest new file name dialog broken
   Product: kdevelop
   Version: 5.7.211201
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: file tree
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

SUMMARY
In my projects tree, I am trying to copy and paste a file in the same
directory. It complains that it would overwrite the file with itself and says,
"Please enter a new file name:" with the file name highlighted.

In the notifications section on my display, it says it is Copying with pause,
stop, and play.

In the dialog, however, it will not accept any keyboard or mouse input, so I
cannot suggest a new name. The only way I can proceed is to hit the stop button
in the notification, which effectively cancels the operation.

STEPS TO REPRODUCE
1.  In the Projects, right-click a file and select "Copy"
2.  Right-click on the same folder and select "Paste"
3. Attempt to suggest a new name for the file.

OBSERVED RESULT
Input into the dialog is prevented until the notification has gone away,
however, the only way to finish the notification is to select stop, canceling
the entire operation.

EXPECTED RESULT
I expect to be able to type in a new filename

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: OpenSUSE 15.3
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 450733] Suggest new file name dialog broken

2022-02-22 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=450733

Aaron Williams  changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

-- 
You are receiving this mail because:
You are watching all bug changes.

[okteta] [Bug 450826] New: Add additional decoding of 16, 32, and 64-bits on left-side

2022-02-25 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=450826

Bug ID: 450826
   Summary: Add additional decoding of 16, 32, and 64-bits on
left-side
   Product: okteta
   Version: 0.26.6
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kosse...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

SUMMARY
It would be nice if the data could be displayed as groups of 16, 32, or 64-bits
on the left-hand side rather than clicking on the right to see the decoding
table with options for little or big endian.

I often have to look at data files that contain 32 or 64-bit values. Bonus
points if it can export that in text format.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 452941] Crashes when wide window opened

2022-05-26 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=452941

--- Comment #9 from Aaron Williams  ---
I am using OpenSUSE. The problem is that when this happens it's almost
impossible to get a backtrace since the desktop becomes unusable, and using gdb
becomes very problematic when this happens.

I do have debug symbols installed.

(In reply to Bug Janitor Service from comment #8)
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least
> 15 days. Please provide the requested information as soon as
> possible and set the bug status as REPORTED. Due to regular bug
> tracker maintenance, if the bug is still in NEEDSINFO status with
> no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
> due to lack of needed information.
> 
> For more information about our bug triaging procedures please read the
> wiki located here:
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> 
> If you have already provided the requested information, please
> mark the bug as REPORTED so that the KDE team knows that the bug is
> ready to be confirmed.
> 
> Thank you for helping us make KDE software even better for everyone!

(In reply to Nate Graham from comment #7)
> It's missing a bunch of debug symbols. What distro are you using?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 454430] New: Copy paste file will not accept input

2022-05-26 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=454430

Bug ID: 454430
   Summary: Copy paste file will not accept input
   Product: kdevelop
   Version: 5.8.220401
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

SUMMARY
In the project view, it is impossible to copy and paste a file into the same
directory.  When I attempt to paste the file, a dialog pops up asking me to
choose a new name. This dialog does not respond to mouse or keyboard input,
requiring me to kill KDevelop.

STEPS TO REPRODUCE
1.  Right-click on a file in the Projects tree
2.  Select Copy
3.  Right click in that same directory and select Paste
4. Attempt to change the filename or click cancel or anything else.

OBSERVED RESULT


EXPECTED RESULT
I expect to be able to type in a new filename to rename the new file.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  Latest
KDE Frameworks Version: 5.94.0
Qt Version:  5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 454446] New: The album art and song descriptions don't match what is actually played

2022-05-26 Thread Aaron Miller
https://bugs.kde.org/show_bug.cgi?id=454446

Bug ID: 454446
   Summary: The album art and song descriptions don't match what
is actually played
   Product: Elisa
   Version: 22.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: kdeaa...@iforgotmy.name
  Target Milestone: ---

Created attachment 149238
  --> https://bugs.kde.org/attachment.cgi?id=149238&action=edit
album art doesn't match its title and artist

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. I'm not sure how it got in this state
2. Browse albums
3. Play a song from an album

OBSERVED RESULT
For step 2, there will be album art for album A that appears with the album
title of album B.
For step 3, it will say it's playing song A but it's actually playing song B.

EXPECTED RESULT
Album art matches the actual albums.
Song titles match the song contents.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 454446] The album art and song descriptions don't match what is actually played

2022-05-26 Thread Aaron Miller
https://bugs.kde.org/show_bug.cgi?id=454446

--- Comment #1 from Aaron Miller  ---
I should add that the music is on an exfat filesystem. Not sure if that
matters.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 454462] New: Editor is extremely laggy

2022-05-26 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=454462

Bug ID: 454462
   Summary: Editor is extremely laggy
   Product: kdevelop
   Version: 5.8.220401
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

SUMMARY
While editing my C projects the editor is often extremely laggy, sometimes
taking seconds to catch up.
This is running on a 12 core machine with 128GiB of RAM with all data on an
nVME SSD.

STEPS TO REPRODUCE
1.  Open a moderately sized C project
2.  Edit C files
3.  Experience frequent lag in the editor

OBSERVED RESULT
I observe very noticeable lag frequently in the editor, perhaps related to the
code completion. I have Clazy Levels 0 and 1 enabled. This is using the C
custom script formatter using Clang Format.

EXPECTED RESULT
I expect the editor to respond quickly like previous releases

I am also wondering if this is related to the problem which causes KDevelop to
hang when shutting down where a database appears to be getting corrupted.

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.

[kdevelop] [Bug 454462] Editor is extremely laggy

2022-05-31 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=454462

--- Comment #2 from Aaron Williams  ---
One thing I see is that it is constantly rescanning the project and I see
several stuck kdevelop processes consuming 100% of the CPU. I think this may be
related to another bug in KDevelop where it fails to shutdown and consumes 100%
of the CPU. I am also experiencing that known bug. If I had to guess, it's due
to the background scanner not shutting down properly. Every time the editor
stutters it started another parsing episode.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 454462] Editor is extremely laggy

2022-06-01 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=454462

--- Comment #4 from Aaron Williams  ---
yes. It is still laggy with frequent reparsing with two more processes stuck at
100%

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 465644] New: Screen no longer locks after inactivity, when external monitor unplugged and plugged back in.

2023-02-12 Thread Aaron Miller
https://bugs.kde.org/show_bug.cgi?id=465644

Bug ID: 465644
   Summary: Screen no longer locks after inactivity, when external
monitor unplugged and plugged back in.
Classification: Plasma
   Product: kscreenlocker
   Version: 5.26.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kdeaa...@iforgotmy.name
  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. Start with a 4K monitor plugged into a laptop, with the 4K monitor screen
area to the upper-left of the laptop screen area (desktop is extended).
2. Observe that screen locks after N minutes of inactivity, where N is
specified in settings.
3. Unplug monitor and plug it back in.

OBSERVED RESULT
Screen does not lock after any duration of user inactivity. Screen only locks
with Cmd-L, as far as I can tell.

EXPECTED RESULT
Screen locks after N minutes of inactivity, where N is specified in settings.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.26.5, Manjaro
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Samsung 4K monitor

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 415770] Environment variable 'GTK2_RC_FILES' is ignored

2023-02-19 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=415770

Rocket Aaron  changed:

   What|Removed |Added

 CC||i...@rocka.me

--- Comment #8 from Rocket Aaron  ---
I can reproduce it too, on Plasma 5.27.0. After some experiment, I think I've
figured out what's happening.

gmenu-dbusmenu-proxy hardcoded gtkrcPath as `QDir::homePath() +
QLatin1String("/.gtkrc-2.0")`, but it's not creating the file if it's not
present. kde-gtk-config's `Gtk2ConfigEditor::removeLegacyStrings()` is the
cause:
https://github.com/KDE/kde-gtk-config/blob/4a9185dbc67543544f7010cf39e6c87af44aeca8/kded/config_editor/gtk2.cpp#L54
it uses `Utils::readFileContents(QFile &file)`
https://github.com/KDE/kde-gtk-config/blob/4a9185dbc67543544f7010cf39e6c87af44aeca8/kded/config_editor/utils.cpp#L19
which calls `file.open(QIODevice::ReadWrite | QIODevice::Text)`
and the mode `ReadWrite` means to create the file if it's not exist:
https://doc.qt.io/qt-5/qfile.html#open

So at startup, kde-gtk-config launches and a empty `~/.gtkrc-2.0` file is
created, then gmenu-dbusmenu-proxy watchs the file creation
https://github.com/KDE/plasma-workspace/blob/89d1f0e07955427a083cbc5af34e0ae9fdcdaad4/gmenu-dbusmenu-proxy/menuproxy.cpp#L106
and write the content to the file.

If gmenu-dbusmenu-proxy is disabled, it would simply results an empty
`~/.gtkrc-2.0` file, as this bug describes:
https://bugs.kde.org/show_bug.cgi?id=417534

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 415770] Environment variable 'GTK2_RC_FILES' is ignored

2023-02-19 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=415770

Rocket Aaron  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 417534] Empty ~/.gtkrc-2.0 file is created every time I login

2023-02-19 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=417534

--- Comment #10 from Rocket Aaron  ---
I think I've found the cause of this bug, see
https://bugs.kde.org/show_bug.cgi?id=415770#c8

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts

2023-02-19 Thread Aaron Rainbolt
https://bugs.kde.org/show_bug.cgi?id=454946

--- Comment #34 from Aaron Rainbolt  ---
After much fiddling, diffing, bisecting, and fighting, the code change that
fixed this bug has finally been found. And it is...

https://invent.kde.org/plasma/plasma-workspace/-/commit/d8c6f30cfe66a3e6bc05ba0b2ced7c5ffaf1a871

Of all the code changes I would imagine that would have fixed this, that was
not what I expected. However, that's what `git bisect` finally gave me. I was
able to test this change (albeit with quite a bit of extra changes to try and
make things compatible) on Plasma/5.24 and can confirm that this does indeed
fix the bug, so this isn't a fluke - this is the fixing change.

Here's my current attempt at backporting the above commit to Plasma/5.24:
https://invent.kde.org/arraybolt/plasma-workspace/-/commit/cf7703e1019fe7fdc92edb4cc30388d87612fbf1
I don't know if all of the changes here are necessary, but I do know that
Plasma appears to still work after doing that, and that I can change global
themes without having plasmashell crash after applying this change, rebuilding,
and installing Ubuntu's plasma-workspace package.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 466388] New: Crash when using git->revert

2023-02-24 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=466388

Bug ID: 466388
   Summary: Crash when using git->revert
Classification: Applications
   Product: kdevelop
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: VCS: Git
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aar...@doofus.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.  Open a file under GIT version control
2.  Start editing file, don't need to save
3.  Right click and select "git->revert"


OBSERVED RESULT
Crash
Application: KDevelop (kdevelop), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  0x7fe85fb6872d in QWeakPointer::~QWeakPointer()
(this=, __in_chrg=) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:566
#7  QWeakPointer::operator=(QWeakPointer&&) (other=, this=0x563da5394550) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:592
#8  QWeakPointer::assign(QObject*) (ptr=0x0,
this=0x563da5394550) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:675
#9  QPointer::operator=(QAction*) (p=0x0, this=0x563da5394550) at
../../include/QtCore/../../src/corelib/kernel/qpointer.h:74
#10 QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool)
(this=this@entry=0x563da5394250, action=action@entry=0x563d93419a40,
action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at
widgets/qmenu.cpp:1475
#11 0x7fe85fb6943d in QMenu::mouseReleaseEvent(QMouseEvent*)
(this=, e=0x7ffcf42055c0) at widgets/qmenu.cpp:2966
#12 0x7fe85fa26d68 in QWidget::event(QEvent*)
(this=this@entry=0x563dd753e790, event=event@entry=0x7ffcf42055c0) at
kernel/qwidget.cpp:9045
#13 0x7fe85fb6b6db in QMenu::event(QEvent*) (this=0x563dd753e790,
e=0x7ffcf42055c0) at widgets/qmenu.cpp:3088
#14 0x7fe85f9e64fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x563d919a3b00, receiver=receiver@entry=0x563dd753e790,
e=e@entry=0x7ffcf42055c0) at kernel/qapplication.cpp:3640
#15 0x7fe85f9ed837 in QApplication::notify(QObject*, QEvent*)
(this=, receiver=0x563dd753e790, e=0x7ffcf42055c0) at
kernel/qapplication.cpp:3084
#16 0x7fe85ecdf043 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x563dd753e790, event=0x7ffcf42055c0) at
kernel/qcoreapplication.cpp:1064
#17 0x7fe85ecdf22e in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=receiver@entry=0x563dd753e790,
event=event@entry=0x7ffcf42055c0) at kernel/qcoreapplication.cpp:1474
#18 0x7fe85f9ec83f in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool)
(receiver=0x563dd753e790, event=event@entry=0x7ffcf42055c0, alienWidget=0x0,
nativeWidget=0x563dd753e790, buttonDown=buttonDown@entry=0x7fe85ff07330
, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2622
#19 0x7fe85fa419b1 in QWidgetWindow::handleMouseEvent(QMouseEvent*)
(this=this@entry=0x563dc2887f10, event=event@entry=0x7ffcf4205a10) at
kernel/qwidgetwindow.cpp:580
#20 0x7fe85fa445bd in QWidgetWindow::event(QEvent*) (this=0x563dc2887f10,
event=0x7ffcf4205a10) at kernel/qwidgetwindow.cpp:300
#21 0x7fe85f9e64fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x563d919a3b00, receiver=receiver@entry=0x563dc2887f10,
e=e@entry=0x7ffcf4205a10) at kernel/qapplication.cpp:3640
#22 0x7fe85f9ed2bf in QApplication::notify(QObject*, QEvent*)
(this=, receiver=0x563dc2887f10, e=0x7ffcf4205a10) at
kernel/qapplication.cpp:3164
#23 0x7fe85ecdf043 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x563dc2887f10, event=0x7ffcf4205a10) at
kernel/qcoreapplication.cpp:1064
#24 0x7fe85ecdf22e in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=receiver@entry=0x563dc2887f10,
event=event@entry=0x7ffcf4205a10) at kernel/qcoreapplication.cpp:1474
#25 0x7fe85f1fcdeb in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
(e=0x563dcc908f70) at kernel/qguiapplication.cpp:2285
#26 0x7fe85f1fe095 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
(e=e@entry=0x563dcc908f70) at kernel/qguiapplication.cpp:2005
#27 0x7fe85f1d4b8b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#28 0x7fe83c17350a in xcbSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at qxcbeventdispatcher.cpp:105
#29 0x7fe85859482b in g_main_dispatch (context=0x563d919b7cc0) at
../glib

[plasmashell] [Bug 466406] New: In plasma wayland session, clipboard action menu has a title bar

2023-02-25 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466406

Bug ID: 466406
   Summary: In plasma wayland session, clipboard action menu has a
title bar
Classification: Plasma
   Product: plasmashell
   Version: 5.27.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Clipboard
  Assignee: plasma-b...@kde.org
  Reporter: i...@rocka.me
  Target Milestone: 1.0

Created attachment 156709
  --> https://bugs.kde.org/attachment.cgi?id=156709&action=edit
Clipboard action menu with title bar above it

SUMMARY
In plasma wayland session, clipboard action menu has a title bar above it, but
on Xorg it doesn't.

STEPS TO REPRODUCE
1. Click "Clipboard" icon on systray to open it's popup, then click "Configure
Clipboard..." to open it's settings dialog
2. In "Action Menu" section, make sure "Include MIME actions" is checked
3. Copy some URL, like https://bugs.kde.org/ , then press Meta+Ctrl+R to open
the action menu

OBSERVED RESULT
Clipboard action menu has a title bar above it

EXPECTED RESULT
No title bar above the menu

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8+kde+r181-1

ADDITIONAL INFORMATION
This also happens when clipboard action menu automatically popups up on certain
clipboard content.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466406] In plasma wayland session, clipboard action menu has a title bar

2023-02-25 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466406

Rocket Aaron  changed:

   What|Removed |Added

 CC||i...@rocka.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 466447] New: In plasma wayland session, Spectacle's Rectangular Region Selection magnifier zooms in wrong position when display scaling is enabled

2023-02-25 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466447

Bug ID: 466447
   Summary: In plasma wayland session, Spectacle's Rectangular
Region Selection magnifier zooms in wrong position
when display scaling is enabled
Classification: Applications
   Product: Spectacle
   Version: 22.12.2
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: i...@rocka.me
CC: k...@david-redondo.de
  Target Milestone: ---

Created attachment 156742
  --> https://bugs.kde.org/attachment.cgi?id=156742&action=edit
The magnifier zooms in wrong position, likely 50% of the actual coordinate

SUMMARY
In plasma wayland session, Spectacle's Rectangular Region Selection magnifier
zooms in wrong position when display scaling is enabled. In my case, I've set
the display sacle to 200%.


STEPS TO REPRODUCE
1. In plasma wayland session, enable display scaling via "System Settings -
Display and Monitor - Display Configuration - Scale", set Scale to 200%
2. Open Spectacle, click "Configure...", in "General" section, make sure
"Rectangular Region Selection - Show magnifier" is enabled
3. Click "Take a New Screenshot" with Area set to "Rectangular Region"
4. Click and drag to draw a selection rectangle

OBSERVED RESULT
The magnifier zooms in wrong position, likely 50% of the actual coordinate

EXPECTED RESULT
The magnifier zooms in under cursor

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8+kde+r181-1

ADDITIONAL INFORMATION
The magnifier zooms in under cursor in Xorg

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 466447] In plasma wayland session, Spectacle's Rectangular Region Selection magnifier zooms in wrong position when display scaling is enabled

2023-02-25 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466447

Rocket Aaron  changed:

   What|Removed |Added

 CC||i...@rocka.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 466450] New: In System Settings' Window Rules page, window property dialog jitters when scrolling with scroll bar

2023-02-25 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466450

Bug ID: 466450
   Summary: In System Settings' Window Rules page, window property
dialog jitters when scrolling with scroll bar
Classification: Applications
   Product: systemsettings
   Version: 5.27.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwinrules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: i...@rocka.me
CC: isma...@gmail.com, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 156745
  --> https://bugs.kde.org/attachment.cgi?id=156745&action=edit
scroll bar and dialog content jitters up and down

SUMMARY
In "System Settings - Workspace - Window Management - Window Rules" page, when
editing or creating rules, "Add property to the rule" dialog would jitter when
scrolling using mouse to drag the scroll bar.


STEPS TO REPRODUCE
1. Open "System Settings - Workspace - Window Management - Window Rules", and
click "Add New..." button
2. In the newly opened "New window settings" page, click "Add Property..."
button 
3. Try scrolling down the "Add property to the rule" dialog using mouse to drag
the scroll bar

OBSERVED RESULT
The scroll bar and dialog content jitters up and down

EXPECTED RESULT
The scroll bar and dialog content scrolls down smoothly

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8+kde+r181-1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 466450] In System Settings' Window Rules page, window property dialog jitters when scrolling with scroll bar

2023-02-25 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466450

Rocket Aaron  changed:

   What|Removed |Added

 CC||i...@rocka.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466458] New: In plasma wayland session, "Telegram Desktop"'s icon pinned in task manager disappears when window closed

2023-02-26 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466458

Bug ID: 466458
   Summary: In plasma wayland session, "Telegram Desktop"'s icon
pinned in task manager disappears when window closed
Classification: Plasma
   Product: plasmashell
   Version: 5.27.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: i...@rocka.me
  Target Milestone: 1.0

Created attachment 156751
  --> https://bugs.kde.org/attachment.cgi?id=156751&action=edit
pinned icon disappears then appears again

SUMMARY
In plasma wayland session, "Telegram Desktop"'s icon pinned in task manager
disappears when its window was closed, if you have selected any chat after
openning the window.
The window's title would change to the contact name when you select a chat,
maybe that's the cause ...


STEPS TO REPRODUCE
1. Install telegram-desktop (version 4.6.5, from https://desktop.telegram.org/
)
2. Launch the app, login, pin it's icon to Icons-Only task manager
3. Click that pinned icon to open its main window, then select any chat
4. Close the window

OBSERVED RESULT
The pinned icon disappears in Icons-Only task manager, then appears again after
several seconds.

EXPECTED RESULT
The pinned icon should not disappear.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8+kde+r181-1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466458] In plasma wayland session, "Telegram Desktop"'s icon pinned in task manager disappears when window closed

2023-02-26 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466458

Rocket Aaron  changed:

   What|Removed |Added

 CC||i...@rocka.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466460] New: In plasma wayland session, left click "Screen casting" tray icon shows context menu with title bar in center of the screen

2023-02-26 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466460

Bug ID: 466460
   Summary: In plasma wayland session, left click "Screen casting"
tray icon shows context menu with title bar in center
of the screen
Classification: Plasma
   Product: plasmashell
   Version: 5.27.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: i...@rocka.me
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY
When using OBS "Screen Capture (Pipewire)" source to record the screen, there
would be a "Screen casting" tray icon in the system tray. Left click on the
icon would show it's context menu with title bar, in center of the entire
screen, rather than next to the tray icon itself. However, right click the tray
icon shows it's menu next to the icon as expected.

The "menu" can even be resized by draging the corner, just like a normal
window. And it shows "Protal" as title, when resized wide enough.


STEPS TO REPRODUCE
1. In OBS Studio ( https://obsproject.com/download ), add a "Screen Capture
(Pipewire)" source
2. In the new "Screen Sharing - Portal" dialog, select any screen to capture,
then click "Share", "OK"
3. Once capture started, left click the "Screen casting" tray icon

OBSERVED RESULT
A "context menu" but with title bar, shows in the center of the screen.

EXPECTED RESULT
The menu shows near the tray icon, without title bar.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8+kde+r181-1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466460] In plasma wayland session, left click "Screen casting" tray icon shows context menu with title bar in center of the screen

2023-02-26 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466460

Rocket Aaron  changed:

   What|Removed |Added

 CC||i...@rocka.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466460] In plasma wayland session, left click "Screen casting" tray icon shows context menu with title bar in center of the screen

2023-02-26 Thread Rocket Aaron
https://bugs.kde.org/show_bug.cgi?id=466460

--- Comment #1 from Rocket Aaron  ---
Created attachment 156752
  --> https://bugs.kde.org/attachment.cgi?id=156752&action=edit
context menu with title bar in center of the screen

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 466469] New: kdeconnect-sms crashes (SIGSEGV)

2023-02-26 Thread Aaron Blasko
https://bugs.kde.org/show_bug.cgi?id=466469

Bug ID: 466469
   Summary: kdeconnect-sms crashes (SIGSEGV)
Classification: Applications
   Product: kdeconnect
   Version: 22.12.2
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: messaging-application
  Assignee: si...@ergotech.com
  Reporter: blaskoazzolaaa...@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. Run`kdeconnect-sms` or open the desktop file

OBSERVED RESULT
A window pops up and immediatly closes (no rendered content)

EXPECTED RESULT
Should open correctly

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.1.12 (zen)
KDE Plasma Version: - (i3wm)
KDE Frameworks Version: - (i3wm)
Qt Version: 5.15.8 - 6.4.2

ADDITIONAL INFORMATION
program stderr:
```
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "(C)
2018-2022, KDE Connect Team" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "SMS
Instant Messaging" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "KDE
Connect SMS" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Simon
Redman" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Aleix
Pol Gonzalez" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Nicolas
Fella" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "id"
msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Select
a device" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid:
"message" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Send a
message" msgid_plural: "" msgctxt: ""
qrc:/qml/ConversationList.qml:26:9: QML MouseArea: Detected anchors on an item
that is managed by a layout. This is undefined behavior; use Layout.alignment
instead.
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML
MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML
MouseArea: Binding loop detected for property "implicitHeight"
fish: Job 1, 'kdeconnect-sms' terminated by signal SIGSEGV (Address boundary
error)
```

running in gdb or valgrind hangs (https://i.imgur.com/jG9hpf7.png)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 466469] kdeconnect-sms crashes (SIGSEGV)

2023-02-26 Thread Aaron Blasko
https://bugs.kde.org/show_bug.cgi?id=466469

--- Comment #2 from Aaron Blasko  ---
No crash helper appears after the short-lived window appears.

Here is what I got using the method you reccomended:
```
Core was generated by `kdeconnect-sms'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f115ee15970 in ?? () from /usr/lib/libQt5Widgets.so.5
[Current thread is 1 (Thread 0x7f115a00e880 (LWP 2435013))]
(gdb) bt
#0  0x7f115ee15970 in  ()
at /usr/lib/libQt5Widgets.so.5
#1  0x7f115ee1cd3e in  ()
at /usr/lib/libQt5Widgets.so.5
#2  0x7f11501512e8 in  ()
at
/usr/lib/qt/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so
#3  0x7f115fc4746a in QQuickWindowPrivate::polishItems() () at
/usr/lib/libQt5Quick.so.5
#4  0x7f115fc0233b in  ()
at /usr/lib/libQt5Quick.so.5
#5  0x7f115fc032c1 in  ()
at /usr/lib/libQt5Quick.so.5
#6  0x7f115e555947 in QWindow::event(QEvent*) ()
at /usr/lib/libQt5Gui.so.5
#7  0x7f115ed78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
at /usr/lib/libQt5Widgets.so.5
#8  0x7f115e08df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#9  0x7f115e549804 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() at /usr/lib/libQt5Gui.so.5
#10 0x7f115e528885 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#11 0x7f1159b2e8d0 in  ()
at /usr/lib/libQt5XcbQpa.so.5
#12 0x7f115d11682b in g_main_context_dispatch ()
at /usr/lib/libglib-2.0.so.0
#13 0x7f115d16dcc9 in  ()
at /usr/lib/libglib-2.0.so.0
#14 0x7f115d1150e2 in g_main_context_iteration ()
at /usr/lib/libglib-2.0.so.0
#15 0x7f115e0d8c6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#16 0x7f115e0866ec in
QEventLoop::exec(QFlags) ()
at /usr/lib/libQt5Core.so.5
#17 0x7f115e091219 in QCoreApplication::exec() ()
at /usr/lib/libQt5Core.so.5
#18 0x55835c9147b5 in  ()
#19 0x7f115f83c790 in  () at /usr/lib/libc.so.6
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 466513] New: corrupted settings while uninstalled from under it, suggest backup or detection

2023-02-27 Thread Aaron Peterson
https://bugs.kde.org/show_bug.cgi?id=466513

Bug ID: 466513
   Summary: corrupted settings while uninstalled from under it,
suggest backup or detection
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: FreeBSD Ports
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: alpeter...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1.  run desktop-installer from a sudo inside konsole (ill advised)
2.  I think there was a dependency failure about a transcode library, and that
freaked the script out, and after attempting to install turbo jpeg for ports
instead of pkg  ( I realize now that I did not install it from ports, we
probably need to add that to the platform options, or someone can move it to
other)
3. it started to uninstall stuff, I thought it was just deleting downloaded
files, but nope, konsole crashed, and all the other applications crashed too, 
just left with a plasma shell that could log out.
4. Reinstall KDE5  (pkg install kde5)
5 -- observe
6, move the .dbus .kde and .config folders to another location.
7. login with KDE X11 session, and it is back to a default install.

OBSERVED RESULT
After reinstalling, all the desktop icons were corrupted, and the list of
applications in the launcher were corrupted.

EXPECTED RESULT
A.  Errors instead of vanishing apps... but we can't control everything when
root yanks stuff out from under us...
B.  An uncorrupted version of settings that just work when the applications are
reinstalled.
C. some sort of detection and re-running of  the initial program that scans and
catalogs applications and configures toolbars and panels. -- A dialog that
says:  Corrupt settings detected, restore to system default?  and copies the
corrupted settings to a spot that could be restored if uncorrupted.
D. Human readable settings... I know from in the past, I tried to set up a lab
to have KDE configured like a kiosk, and KDE likes to save binary blobs and
stuff in the configuration files.


SOFTWARE/OS VERSIONS
latest from freeBSD13.1 as of  Sunday 2/26/2023
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5
KDE Frameworks Version: 5
Qt Version: 5

ADDITIONAL INFORMATION
This is actually fairly important for keeping the system reliable.  Detecting
faults and being able to recover shouldn't be too hard, hopefully not used
often, but people like to bork their systems.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 466538] New: Cannot add email account

2023-02-27 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=466538

Bug ID: 466538
   Summary: Cannot add email account
Classification: Applications
   Product: kontact
   Version: 5.22.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

Created attachment 156792
  --> https://bugs.kde.org/attachment.cgi?id=156792&action=edit
Akonadi error log

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. Click Settings
2. Click Accounts
3. Click Receiving
4. Click Add
5. Click Add Mail Account

OBSERVED RESULT
Nothing happens, no dialog to add an email account

EXPECTED RESULT
I expect to be able to add an IMAP account

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Akonadi was started. I had an IMAP email account but Akonadi was not updating
recent emails. I nuked .local/share/akonadi to try and fix it. This did not, so
I nuked the IMAP account and now I cannot recreate it. Something is broken
preventing an email account from being added.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 466538] Cannot add email account

2023-02-27 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=466538

Aaron Williams  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Aaron Williams  ---
I had a hidden dialog for creating an account that prevented it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 466469] kdeconnect-sms crashes (SIGSEGV)

2023-03-12 Thread Aaron Blasko
https://bugs.kde.org/show_bug.cgi?id=466469

Aaron Blasko  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 467550] New: baloo does not exclude folders under an excluded folder

2023-03-18 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=467550

Bug ID: 467550
   Summary: baloo does not exclude folders under an excluded
folder
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: aar...@doofus.org
  Target Milestone: ---

Created attachment 157406
  --> https://bugs.kde.org/attachment.cgi?id=157406&action=edit
File containing folders to be excluded

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. Install a large software package, i.e. Qt.
2. Start baloo
3.  In a window run balooctl monitor
4. Run the command 'balooctl config add excludeFilters /home/[user]/Qt
5. Watch baloo continue to index in that folder

OBSERVED RESULT
Baloo will continue to index files in the excluded folder, even after
restarting baloo. The folder is included in baloofilerc  exclude
folders[$e]=$HOME/Qt/

EXPECTED RESULT
I expect Baloo to exclude any folders in the excluded folder list

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: OpenSUSE 15.4/5.104.0
(available in About System)
KDE Plasma Version: 21.8.29
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I have some very large trees that should be excluded from Baloo indexing in
part due to the sheer size, i.e. Qt source code, but this appears to be broken.
For example, I want to exclude /home/username/Qt and all folders underneath it,
however even though this folder is in the exclude list, Baloo happily continues
to index this. I have well over 1,000,000 files in the excluded trees and this
is consuming a significant amount of processing, memory, and disk space to
index.
Another bug claims that this is the expected behavior, which IMO is completely
broken. There must be a way to be able to exclude large trees of files from
Baloo!!!

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 442292] 21.08.1: test suite is failing

2023-03-19 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=442292

Aaron Williams  changed:

   What|Removed |Added

 CC||aar...@doofus.org

--- Comment #5 from Aaron Williams  ---
I am hitting this bug. The last time I debugged this it turned out to be due to
multiple threads attempting to do the same thing at the same time. Two threads
attempt to move Akonadi.error to Akonadi.error.old at the same time and this
fails. The code needs to be fixed to handle this by either adding a lock or not
failing.
The problem is in akInit() and it is caused by multiple instances attempting to
start at the same time.
I.e. with two processes:
P1 sees old file exists
P2 sees old file exists
P1 deletes old file
P2 attempts to delete old file, fails due to P1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 442292] 21.08.1: test suite is failing

2023-03-19 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=442292

--- Comment #6 from Aaron Williams  ---
Never mind, I'm getting a permission denied error for removing
Akonadi.error.old which I cannot explain. The file permissionss are 644 and the
file and path are correct. The only odd thing in my configuration is that the
.local and .config directories are symlinks from my home directory to a SSD.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 442292] 21.08.1: test suite is failing

2023-03-19 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=442292

--- Comment #7 from Aaron Williams  ---
My permission problem was unrelated and due to apparmor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmailtransport] [Bug 464540] akonadi crashes on startup

2023-03-19 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=464540

Aaron Williams  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from Aaron Williams  ---
This was due to me changing .local to a symbolic link to a SSD and AppArmor
complaining.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 442292] 21.08.1: test suite is failing

2023-03-22 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=442292

--- Comment #10 from Aaron Williams  ---
(In reply to kloczek from comment #9)
> (In reply to Aaron Williams from comment #5)
> > I am hitting this bug. The last time I debugged this it turned out to be due
> > to multiple threads attempting to do the same thing at the same time. Two
> > threads attempt to move Akonadi.error to Akonadi.error.old at the same time
> > and this fails. The code needs to be fixed to handle this by either adding a
> > lock or not failing.
> > The problem is in akInit() and it is caused by multiple instances attempting
> > to start at the same time.
> > I.e. with two processes:
> > P1 sees old file exists
> > P2 sees old file exists
> > P1 deletes old file
> > P2 attempts to delete old file, fails due to P1.
> 
> IIRC in cmake it is possible to specyfy that some some units must be
> serialised.

As I stated above, I traced the root cause to app-armor due to the fact that my
.home directory was a symlink to a SSD. I was mistaken in thinking it might be
due to some parallel issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 467790] New: Crashes every time I clear scrollback and reset

2023-03-25 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=467790

Bug ID: 467790
   Summary: Crashes every time I clear scrollback and reset
Classification: Applications
   Product: konsole
   Version: 23.03.80
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: keyboard
  Assignee: konsole-de...@kde.org
  Reporter: aar...@doofus.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
***
I have Ctrl+Shift+K set up to clear scrollback and reset.

STEPS TO REPRODUCE
1. Open Konsole
2. Type ++k
3. Watch it crash

OBSERVED RESULT
Crash

EXPECTED RESULT
This used to work.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: OpenSUSE 15.4
(available in About System)
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I did see some strange behavior. When I logged in after the last update some of
my konsole settings seem to have changed. The menu bar disappeared and the tabs
moved from the bottom to the top.
I was able to fix this, however.

Application: Konsole (konsole), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  Konsole::SessionController::updateCodecAction (this=0x561189c533a0,
codec=0x0) at
/usr/src/debug/konsole-23.03.80-lp154.1.1.x86_64/src/session/SessionController.cpp:996
#7  0x7f634ca5da3b in QtPrivate::QSlotObjectBase::call (a=0x7ffe0b0db070,
r=0x561189c533a0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate (sender=0x561189e639c0, signal_index=8,
argv=0x7ffe0b0db070) at kernel/qobject.cpp:3923
#9  0x7f634ca56eb2 in QMetaObject::activate
(sender=sender@entry=0x561189e639c0, m=m@entry=0x7f634de4d3c0
,
local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7ffe0b0db070)
at kernel/qobject.cpp:3983
#10 0x7f634dce9422 in Konsole::Session::sessionCodecChanged
(this=this@entry=0x561189e639c0, _t1=) at
/usr/src/debug/konsole-23.03.80-lp154.1.1.x86_64/build/src/konsoleprivate_autogen/ZNMSKYHDQK/moc_Session.cpp:737
#11 0x7f634dd9ee34 in Konsole::Session::setCodec
(this=this@entry=0x561189e639c0, codec=) at
/usr/src/debug/konsole-23.03.80-lp154.1.1.x86_64/src/session/Session.cpp:234
#12 0x7f634ddad54c in Konsole::SessionController::clearHistoryAndReset
(this=0x561189c533a0) at
/usr/src/debug/konsole-23.03.80-lp154.1.1.x86_64/src/session/SessionController.cpp:1805
#13 0x7f634ca5da3b in QtPrivate::QSlotObjectBase::call (a=0x7ffe0b0db200,
r=0x561189c533a0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate (sender=0x561189c78c00, signal_index=4,
argv=0x7ffe0b0db200) at kernel/qobject.cpp:3923
#15 0x7f634ca56eb2 in QMetaObject::activate
(sender=sender@entry=0x561189c78c00, m=m@entry=0x7f634db7cd40
, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffe0b0db200) at kernel/qobject.cpp:3983
#16 0x7f634d68cf82 in QAction::triggered (this=this@entry=0x561189c78c00,
_t1=) at .moc/moc_qaction.cpp:376
#17 0x7f634d68f5cc in QAction::activate (this=0x561189c78c00,
event=) at kernel/qaction.cpp:1161
#18 0x7f634d68ff61 in QAction::event (this=, e=) at kernel/qaction.cpp:1086
#19 0x7f634d69353c in QApplicationPrivate::notify_helper
(this=this@entry=0x561189771dc0, receiver=receiver@entry=0x561189c78c00,
e=e@entry=0x7ffe0b0db560) at kernel/qapplication.cpp:3640
#20 0x7f634d69a2ff in QApplication::notify (this=,
receiver=0x561189c78c00, e=0x7ffe0b0db560) at kernel/qapplication.cpp:3164
#21 0x7f634ca20043 in QCoreApplication::notifyInternal2
(receiver=0x561189c78c00, event=0x7ffe0b0db560) at
kernel/qcoreapplication.cpp:1064
#22 0x7f634cf6cac6 in QShortcutMap::dispatchEvent
(this=this@entry=0x561189771e88, e=e@entry=0x7ffe0b0db620) at
kernel/qshortcutmap.cpp:675
#23 0x7f634cf6d53a in QShortcutMap::tryShortcut
(this=this@entry=0x561189771e88, e=e@entry=0x7ffe0b0db620) at
kernel/qshortcutmap.cpp:343
#24 0x7f634cf19503 in QWindowSystemInterface::handleShortcutEvent
(window=, window@entry=0x561189abacb0, timestamp=224004209,
keyCode=75, modifiers=..., nativeScanCode=45, nativeVirtualKey=75,
nativeModifiers=21, text=..., autorepeat=false, count=1) at
kernel/qwindowsysteminterface.cpp:477
#25 0x7f634cf3a687 in QGuiApplicationPrivate::processKeyEvent
(e=0x561189e53fa0) at kernel/qguiapplication.cpp:2398
#26 0x7f634cf3f075 in QGuiApplicationPrivate::processWindowSystemEvent
(e=e@entry=0x561189e53fa0) at kernel/qguiapplication.cpp:2011
#27 0x7f634cf15b8b in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#28 0x7f633fbf665a in xcbSourceDispatch (source=) at
qxcbevent

[konsole] [Bug 467790] Crashes every time I clear scrollback and reset

2023-03-25 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=467790

--- Comment #1 from Aaron Williams  ---
Created attachment 157574
  --> https://bugs.kde.org/attachment.cgi?id=157574&action=edit
konsolerc configuration file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 467790] Crashes every time I clear scrollback and reset

2023-03-25 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=467790

--- Comment #2 from Aaron Williams  ---
Created attachment 157575
  --> https://bugs.kde.org/attachment.cgi?id=157575&action=edit
Session that crashed (all crash)

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 467790] Crashes every time I clear scrollback and reset

2023-03-25 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=467790

--- Comment #3 from Aaron Williams  ---
Created attachment 157576
  --> https://bugs.kde.org/attachment.cgi?id=157576&action=edit
Default Profile I use

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 467790] Crashes every time I clear scrollback and reset

2023-03-25 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=467790

--- Comment #4 from Aaron Williams  ---
Created attachment 157577
  --> https://bugs.kde.org/attachment.cgi?id=157577&action=edit
konsoleui file

-- 
You are receiving this mail because:
You are watching all bug changes.

  1   2   3   4   5   6   7   8   9   >