from:"marc"

https://bugs.kde.org/show_bug.cgi?id=481472

Bug ID: 481472
   Summary: Graphical Glitch: Black lines appearing between rows
Classification: Applications
   Product: konsole
   Version: 22.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: mf-spam+kdebo...@posteo.de
  Target Milestone: ---

Created attachment 165907
  --> https://bugs.kde.org/attachment.cgi?id=165907=edit
Graphical glitch

SUMMARY
Konsole shows black horizontal lines after the color of a row changed
(scrolling selector in Midnight Commander). See gif.

- Fresh Debian 12 install.
- Does always happen - sometimes the glitch is not there. 

Tests with X11/Wayland and scaling:
- It seems like it does not happen in Wayland with 100% screen scaling.
- It happens, but looks different in Wayland at 125% scaling.
- It happens in X11 regardless of scaling.

STEPS TO REPRODUCE
1. Open mc in konsole
2. Scroll the highlighted row up or down

OBSERVED RESULT
Black bars appear, see attachment.

EXPECTED RESULT
No graphical glitch.


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.

[kate] [Bug 458370] The cursor is not visible when moving the cursor

https://bugs.kde.org/show_bug.cgi?id=458370

Marc Fouquet  changed:

   What|Removed |Added

 Attachment #165905|The cursor disappears while |The cursor disappears while
description|pressing the left cursot|pressing the left cursor
   |key |key

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

[kate] [Bug 458370] The cursor is not visible when moving the cursor

https://bugs.kde.org/show_bug.cgi?id=458370

--- Comment #9 from Marc Fouquet  ---
Created attachment 165905
  --> https://bugs.kde.org/attachment.cgi?id=165905=edit
The cursor disappears while pressing the left cursot key

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

[kate] [Bug 458370] The cursor is not visible when moving the cursor

https://bugs.kde.org/show_bug.cgi?id=458370

Marc Fouquet  changed:

   What|Removed |Added

 CC||mf-spam+kdebo...@posteo.de

--- Comment #8 from Marc Fouquet  ---
I have the same issue. The cursor disappears while it is moving. See gif.
Fresh Debian 12/KDE install.
Locale is German, with fcitx5.
It happens on X11 and Wayland.
It happens in 1080p and 1440p.
It happens with 100% and 125% scaling.
It happens while entering text (i.e. pressing 'a') and while moving the cursor
in the text. In my gif I just press the left cursor key.

Kate Version is 22.12.3.
KDE Plasma 5.27.5
KDE Frameworks 5.103.0
Qt 5.15.8

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

[plasmashell] [Bug 474768] 3rd-party "Power Monitor" widget sometimes crashes Plasma in TaskManager::TaskGroupingProxyModel::Private::sourceRowsAboutToBeRemoved() after waking from sleep

2024-02-08 Thread Marc Cousin

https://bugs.kde.org/show_bug.cgi?id=474768

Marc Cousin  changed:

   What|Removed |Added

 CC||cousinm...@gmail.com

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

[digikam] [Bug 480775] New: ASCII in caption

2024-02-03 Thread Deconchat Marc

https://bugs.kde.org/show_bug.cgi?id=480775

Bug ID: 480775
   Summary: ASCII in caption
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tags-Captions
  Assignee: digikam-bugs-n...@kde.org
  Reporter: deconc...@yahoo.com
  Target Milestone: ---

Created attachment 165493
  --> https://bugs.kde.org/attachment.cgi?id=165493=edit
ASCII in caption field

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
***

When caption is empty, it displays "ASCII" as  content

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

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

[kwin] [Bug 474725] Screen randomly freezes for a second

2024-01-29 Thread Marc

https://bugs.kde.org/show_bug.cgi?id=474725

--- Comment #16 from Marc  ---
For me the issue has almost disappeared somewhere at the end of
december/beginning of january. The last two weeks the screen only very rarely
froze. Maybe once every other day or so, whereas before it occurred very
frequently.

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

[plasmashell] [Bug 466320] kpipewire_logging: Window not available PipeWireSourceItem_QML_1025

2024-01-29 Thread Marc Cousin

https://bugs.kde.org/show_bug.cgi?id=466320

Marc Cousin  changed:

   What|Removed |Added

 CC||cousinm...@gmail.com

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

[plasmashell] [Bug 477045] Power Battery Applet Remaining Charge Percent not getting updated

2024-01-15 Thread Marc Cousin

https://bugs.kde.org/show_bug.cgi?id=477045

Marc Cousin  changed:

   What|Removed |Added

 CC||cousinm...@gmail.com

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

[Powerdevil] [Bug 434432] battery time estimate totally wrong

2023-11-06 Thread Marc Cousin

https://bugs.kde.org/show_bug.cgi?id=434432

--- Comment #19 from Marc Cousin  ---
I also have this exact same bug, with plasma 5.27.9 (archlinux). I've been
having it for a while, but I couldn't say how long.

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

[Powerdevil] [Bug 434432] battery time estimate totally wrong

2023-11-06 Thread Marc Cousin

https://bugs.kde.org/show_bug.cgi?id=434432

Marc Cousin  changed:

   What|Removed |Added

 CC||cousinm...@gmail.com

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

[gwenview] [Bug 476299] Open containing folder, after selecting multiple images, fails to open a single file dialog window like it use to.

2023-11-02 Thread Marc Chamberlin

https://bugs.kde.org/show_bug.cgi?id=476299

Marc Chamberlin  changed:

   What|Removed |Added

 CC||m...@marcchamberlin.com

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

[gwenview] [Bug 476299] New: Open containing folder, after selecting multiple images, fails to open a single file dialog window like it use to.

2023-10-29 Thread Marc Chamberlin

https://bugs.kde.org/show_bug.cgi?id=476299

Bug ID: 476299
   Summary: Open containing folder, after selecting multiple
images, fails to open a  single file dialog window
like it use to.
Classification: Applications
   Product: gwenview
   Version: 21.12.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: m...@marcchamberlin.com
  Target Milestone: ---

SUMMARY
Selecting multiple images, then opening the containing folder, use to open a
single dialog window showing the selected images highlighted. Now it opens
multiple dialog windows each window showing just one of the selected images
highlighted. This makes it impossible to do things like renaming the group of
selected files using the auto-incrementing file names feature.

STEPS TO REPRODUCE
1. Open Gwenview in a file directory containing multiple image files.
2. Select a number of images to be displayed all at once.
3. Right click on  any image shown, and select "Open Containing Folder"

OBSERVED RESULT
Multiple dialog windows are created,  each showing the containing folder, but
with only one file highlighted from the set of selected files.

EXPECTED RESULT
Only one dialog window should be created and opened, showing the files in the
containing folder, and with all selected files highlighted. This allows one to
treat all of the selected files at once, such as renaming them. This is the way
Gwenview has always worked in the past.

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

Operating System: openSUSE Leap 15.4
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.14.21-150400.24.88-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 530

ADDITIONAL INFORMATION

I believe this change of behavior occurred after a set of updates were applied
to my system. I have no idea however of what was updated or when the changes
were applied.

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

[kwin] [Bug 474725] Screen randomly freezes for a second

2023-10-20 Thread Marc

https://bugs.kde.org/show_bug.cgi?id=474725

Marc  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Platform|Other   |Archlinux
 CC||e...@hotmail.de
Version|master  |5.27.8
 Status|REPORTED|CONFIRMED

--- Comment #9 from Marc  ---
On my latop a Lenovo ThinkPad X1 Carbon Gen 10 this is a huge problem. These
stutters occur every couple of minutes, sometimes even multiple times per
minute and the complete system hangs for some 100ms or sometimes some seconds.

When the stutter occurs it is often the case that the keypress is repeated tens
to hundred of times. So I type, the stutter occurs and my input looks like
this.

It's beyond annoying and makes the laptop hardly usable on the STABLE KDE
VERSION 5.27.8. So this is definitely not only a master issue for Plasma 6. So
it's also affecting Qt5 (5.15.11 in my case).

To me it seems like an issue in the graphics stack. Either the Intel driver
itself or Qt. I have an Intel i7-1265U with Intel Graphics.

I assume this issue is much more common than this bug reports suggests so far.
I wasn't sure where the stutter comes from and didn't know where to report the
bug to until I stumbled on this report.

Maybe Arch users are particularly affected because they typically use the most
up to date packages and kernels. So it could indeed be a regression in some
area of the software stack.

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

[plasma-nm] [Bug 470667] Allow storing wifi password for all users by default

2023-10-15 Thread Marc Mezzarobba

https://bugs.kde.org/show_bug.cgi?id=470667

Marc Mezzarobba  changed:

   What|Removed |Added

 CC||marc+b...@mezzarobba.net

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

[kwin] [Bug 362307] Some apps do not ignore wheel event when Meta+Wheel is used to raise/lower the window

2023-09-06 Thread Marc Branchaud

https://bugs.kde.org/show_bug.cgi?id=362307

--- Comment #9 from Marc Branchaud  ---
(In reply to Marc Branchaud from comment #8)
> I am still seeing this with Plasma 5.24.7.

More specifically, on an up-to-date Kubuntu 22.04 system:

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3
Kernel Version: 5.19.0-32-generic (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 62.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2

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

[kwin] [Bug 362307] Some apps do not ignore wheel event when Meta+Wheel is used to raise/lower the window

2023-09-06 Thread Marc Branchaud

https://bugs.kde.org/show_bug.cgi?id=362307

Marc Branchaud  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|UNMAINTAINED|---
 Ever confirmed|0   |1
Version|5.5.5   |5.24.7

--- Comment #8 from Marc Branchaud  ---
I am still seeing this with Plasma 5.24.7.

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

[kmail2] [Bug 462877] KMail crashes when clicking away from a PGP signed email to another email before the signature is verified

2023-09-05 Thread Marc Joliet

https://bugs.kde.org/show_bug.cgi?id=462877

Marc Joliet  changed:

   What|Removed |Added

Summary|KMail crash when clicking   |KMail crashes when clicking
   |on an Email |away from a PGP signed
   ||email to another email
   ||before the signature is
   ||verified

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

[kmail2] [Bug 462877] KMail crash when clicking on an Email

2023-09-05 Thread Marc Joliet

https://bugs.kde.org/show_bug.cgi?id=462877

--- Comment #7 from Marc Joliet  ---
Created attachment 161434
  --> https://bugs.kde.org/attachment.cgi?id=161434=edit
New crash information added by DrKonqi

kmail (5.24.0 (23.08.0)) using Qt 5.15.10

Same reproducer as usual: click away from GPG signed email before the signature
was verified (this time coincidentally to an email that was *also* GPG signed,
in case that might make a difference).

(I guess I'm just going to keep adding these until somebody says otherwise.)

-- Backtrace (Reduced):
#4  0x7fdc99c54a3e in QVector::begin
(this=) at /usr/include/qt5/QtCore/qvector.h:220
#5  KMime::Content::headerByType (this=this@entry=0x55fe0cffe0c0,
type=0x7fdc99c6d040 "Content-Transfer-Encoding") at
/usr/src/debug/kmime-23.08.0/src/kmime_content.cpp:626
#6  0x7fdc99c558aa in
KMime::Content::header (create=true,
this=0x55fe0cffe0c0) at /usr/src/debug/kmime-23.08.0/src/kmime_content.h:681
#7  KMime::Content::contentTransferEncoding (this=this@entry=0x55fe0cffe0c0,
create=create@entry=true) at
/usr/src/debug/kmime-23.08.0/src/kmime_content.cpp:883
#8  0x7fdc99c5687f in KMime::ContentPrivate::decodeText (this=0x0,
q=q@entry=0x55fe0cffe0c0) at
/usr/src/debug/kmime-23.08.0/src/kmime_content.cpp:738

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

[kaddressbook] [Bug 472293] New: Won't open/display VCard created by Thunderbird

2023-07-15 Thread Marc Chamberlin

https://bugs.kde.org/show_bug.cgi?id=472293

Bug ID: 472293
Summary: Won't open/display VCard created by Thunderbird
Classification: Applications
Product: kaddressbook
Version: 5.19.3
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: m...@marcchamberlin.com
CC: to...@kde.org
Target Milestone: ---

SUMMARY

Can't import/display VCard from Thunderbird client email application.
***
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. Create a VCard in Thunderbird and select to attach it to emails.
2. Send a test email to yourself.
3. Click on the attached VCard to open it.
4. KAddressBook is selected, by default, for opening VCards. Click on it to
open the VCard.

OBSERVED RESULT
The KaddressBook app is started and opens of it's main dialog. Nothing is shown
about the information stored in the VCard. I did try it with Emacs to make
sure there is content in the VCard. There is, and it appears to be OK.

EXPECTED RESULT
The VCard content should be shown and automatically added to the Address Books.

SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: OpenSuSE 15.4 with KDE
(available in About System) AND WHERE IS "ABOUT SYSTEM" LOCATED IN OPENSUSE?
Please pay attention to details!
KDE Plasma Version: 5.24.4
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.

[kmail2] [Bug 462877] KMail crash when clicking on an Email

2023-07-12 Thread Marc Joliet

https://bugs.kde.org/show_bug.cgi?id=462877

--- Comment #6 from Marc Joliet  ---
Created attachment 160257
  --> https://bugs.kde.org/attachment.cgi?id=160257=edit
New crash information

I hadn't been able to reproduce the bug recently (maybe for a few weeks, but
I'm not exactly sure), so I got adventurous and stopped waiting for the first
PGP signature to be verified before looking at other emails.  But then it
happened again this week, see attached crash report.  The reproducer remains
the same: launch KMail, select a PGP signed email to read, then select a
different email to read before the first one's PGP signature has finished
verifying, and KMail should crash.

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

[kmymoney] [Bug 471072] New: Home view is blank

2023-06-15 Thread Marc

https://bugs.kde.org/show_bug.cgi?id=471072

Bug ID: 471072
   Summary: Home view is blank
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: photosnaps...@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. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
macOS: Ventura (13.4) (Mac silicon) 
Kmymoney ver 5.1.3-d7dd9f8dd

ADDITIONAL INFORMATION
Home View is blank.

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

[plasma-nm] [Bug 470148] Bond connection should offer MTU setting like wired Ethernet

2023-05-23 Thread Jean-Marc Liotier

https://bugs.kde.org/show_bug.cgi?id=470148

--- Comment #1 from Jean-Marc Liotier  ---
For proof of backend functionality I gave an 'ip' command, but should have
mentioned a 'nmcli' command instead - so here it is: ''nmcli connection modify
bond0 802-3-ethernet.mtu 9000'

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

[plasma-nm] [Bug 470149] New: Bond should be a possible VLAN parent interface

2023-05-22 Thread Jean-Marc Liotier

https://bugs.kde.org/show_bug.cgi?id=470149

Bug ID: 470149
   Summary: Bond should be a possible VLAN parent interface
Classification: Plasma
   Product: plasma-nm
   Version: 5.27.2
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@liotier.org
  Target Milestone: ---

In the "New Connection (vlan)" dialog, the "Parent interface:" drop-down
selector offers a list of the system's eligible interfaces.

Current behaviour: list of interfaces selectable as parent interface contains
only Wired Ethernet and "lo" interfaces, although a Bond interface exist.

Desired behaviour: list of interfaces selectable as parent interface should
contains Wired Ethernet, "lo" and Bond interfaces.

In Network Manager commands such as 'nmcli con add type vlan ifname bond0.123
con-name bond0.123 id 123 dev bond0' the device argument can take bonded
interfaces just as well as individual physical devices. In plasma-nm it should
be as well.

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

[plasma-nm] [Bug 470148] New: Bond connection should offer MTU setting like wired Ethernet

2023-05-22 Thread Jean-Marc Liotier

https://bugs.kde.org/show_bug.cgi?id=470148

Bug ID: 470148
   Summary: Bond connection should offer MTU setting like wired
Ethernet
Classification: Plasma
   Product: plasma-nm
   Version: 5.27.2
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@liotier.org
  Target Milestone: ---

A Wired Ethernet connection's "Wired" tab offers a "MTU:" setting field that
sets the interface's MTU.

A Bond connection offers no such field, so its MTU remains at its default 1500
even when the bonded connections are set to a higher value.

The "Bonded connections" component of a Bond connection offer a MTU setting
field to a Wired Ethernet connection, but it is irrelevant to setting the MTU
for the Bond connection.

Setting the Bond connection is possible from a console using a command such as
'ip link set bond0 mtu 9000'. That setting should be available through a "MTU:"
setting field like the one offered in the Wired Ethernet connection's "Wired"
tab.

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

[NeoChat] [Bug 468967] User completion or emoji picker do not show up

2023-05-11 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=468967

--- Comment #3 from Marc Deop  ---
I built https://invent.kde.org/network/neochat/-/merge_requests/988 at
https://copr.fedorainfracloud.org/coprs/marcdeop/neochat-git/

The issue is solved for me :-)

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

[kmail] [Bug 166521] Allow default directory for saving attachments to be customised based on both sender and file-type

2023-04-29 Thread Marc Mezzarobba

https://bugs.kde.org/show_bug.cgi?id=166521

Marc Mezzarobba  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
 CC||marc+b...@mezzarobba.net

--- Comment #3 from Marc Mezzarobba  ---
I think it is still valid. Alternatively (or in addition), it would be great if
kmail would remember the last directory used for saving an attachment from a
given sender and use it as a default location in the Save As... dialog.

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

[kmail2] [Bug 325571] option to delete all attachments

2023-04-29 Thread Marc Mezzarobba

https://bugs.kde.org/show_bug.cgi?id=325571

Marc Mezzarobba  changed:

   What|Removed |Added

 CC||marc+b...@mezzarobba.net

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

[NeoChat] [Bug 468967] New: User completion or emoji picker do not show up

2023-04-25 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=468967

Bug ID: 468967
   Summary: User completion or emoji picker do not show up
Classification: Applications
   Product: NeoChat
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: k...@marcdeop.com
CC: c...@carlschwan.eu
  Target Milestone: ---

I used to be able to type @[some letters] and a user list would show up.
Same way I used to be able to type :[some letters] and the emoji picker would
show up


STEPS TO REPRODUCE
1. type @ followed by some letters
or
1. type : followed by some letters


OBSERVED RESULT
Nothing happens

EXPECTED RESULT
A user list picker shows up
or
An emoji picker shows up

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 37
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Neochat and libquotient built from master in my COPR
https://copr.fedorainfracloud.org/coprs/marcdeop/neochat-git/

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

[plasmashell] [Bug 468613] Task Manager tooltips are inappropriately displayed on a different monitor

2023-04-20 Thread Marc Collin

https://bugs.kde.org/show_bug.cgi?id=468613

--- Comment #4 from Marc Collin  ---
When i reboot the computer that work. I turn of the monitor. I Come back x time
after... I turn on monitor. I'm login to the session. task manager tooltips are
not displayed in the right place.

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

[plasmashell] [Bug 468613] Miniature of windows is displayed on the second monitor

2023-04-17 Thread Marc Collin

https://bugs.kde.org/show_bug.cgi?id=468613

--- Comment #2 from Marc Collin  ---
can't say for the 1px overlap... but don't seem to have any overlap visually

kscreen-doctor -o

Output: 65 DP-1 enabled connected priority 1 DisplayPort Modes:
69:3840x2160@60*! 70:3840x2160@30 71:3840x2160@25 72:3840x2160@24
73:3840x2160@30 74:3840x2160@24 75:3840x2160@30 76:1920x2160@60 77:1920x1080@60
78:1920x1080@60 79:1920x1080@50 80:1920x1080@60 81:1920x1080@60 82:1920x1080@50
83:1920x1080@60 84:1680x1050@60 85:1280x1024@75 86:1280x1024@60 87:1440x900@75
88:1440x900@60 89:1280x960@60 90:1280x720@60 91:1280x720@50 92:1280x720@60
93:1024x768@75 94:1024x768@60 95:800x600@75 96:800x600@60 97:720x576@50
98:720x480@60 99:720x480@60 100:640x480@75 101:640x480@73 102:640x480@67
103:640x480@60 104:640x480@60 105:720x400@70 Geometry: 0,0 3840x2160 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 66 HDMI-1 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0
0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 67 HDMI-2 enabled connected priority 2 HDMI Modes: 78:1920x1080@60
79:1920x1080@50 80:1920x1080@60 85:1280x1024@75 86:1280x1024@60 90:1280x720@60
91:1280x720@50 92:1280x720@60 93:1024x768@75 94:1024x768@60 95:800x600@75
96:800x600@60 97:720x576@50 98:720x480@60 99:720x480@60 100:640x480@75
101:640x480@73 102:640x480@67 103:640x480@60 104:640x480@60 105:720x400@70
106:2560x1440@60*! 107:1920x1080@30 108:1920x1080@24 109:1920x1080@30
110:1920x1080@24 111:1680x1050@60 112:1600x900@60 113:1440x900@60
114:1280x800@60 115:1152x864@75 116:1024x768@70 117:832x624@75 118:800x600@72
119:800x600@56 Geometry: 3840,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr:
incapable RgbRange: unknown

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

[plasmashell] [Bug 468613] New: Miniature of windows is displayed on the second monitor

2023-04-17 Thread Marc Collin

https://bugs.kde.org/show_bug.cgi?id=468613

Bug ID: 468613
   Summary: Miniature of windows is displayed on the second
monitor
Classification: Plasma
   Product: plasmashell
   Version: 5.27.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: plasma-b...@kde.org
  Reporter: marc.col...@protonmail.com
CC: aleix...@kde.org, notm...@gmail.com
  Target Milestone: 1.0

Created attachment 158163
  --> https://bugs.kde.org/attachment.cgi?id=158163=edit
Miniature program started

SUMMARY

when i put my mouse over a application in the task bar, a miniature is
displayed but not in the same screen and not over the mouse


STEPS TO REPRODUCE
1. Open a program
2. Put your mouse over the program started
3. Check where is displayed the miniature

OBSERVED RESULT

Miniature is displayed on the second screen

EXPECTED RESULT

Miniature should displayed on the same screen, just over the icon

Miniature of the windows is displayed on the same screen

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

ADDITIONAL INFORMATION

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

[dolphin] [Bug 468167] New: Remote - fstab sshfs mounts

2023-04-05 Thread Marc Leger

https://bugs.kde.org/show_bug.cgi?id=468167

Bug ID: 468167
   Summary: Remote - fstab sshfs mounts
Classification: Applications
   Product: dolphin
   Version: 22.12.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: marc.le...@voxinteractif.com
CC: kfm-de...@kde.org
  Target Milestone: ---

I have lots of mounts in fstab with noauto as I only mount the ones that I'm
working on at a specific time.  The ones I have with nfs shows up as umounted
under "Remote" in Dolphin.  That works great.  I click on the one I need, do my
work, right click and unmount.  Perfect!

The wish I have is that this behavior would be the same for sshfs mounts in
fstab.

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

[kdenlive] [Bug 467596] Doesnt Play both audio tracks during playback

2023-03-31 Thread Marc

https://bugs.kde.org/show_bug.cgi?id=467596

Marc  changed:

   What|Removed |Added

Version|22.08.1 |22.12.3

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

[NeoChat] [Bug 467242] Search "toolbar" has the wrong size and "overlaps" onto the rooms area

2023-03-22 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=467242

--- Comment #2 from Marc Deop  ---
(In reply to Tobias Fella from comment #1)
> Have you seen this happen again? works perfectly fine here :/

Yes, I still experience the problem.

Built Neochat from git.

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

[kio-extras] [Bug 420173] thumbnail.so eats tons of memory with large GeoTiff

2023-03-21 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=420173

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #1 from Marc Deop  ---
I believe the code has now some protection against this issue.

Perhaps this can be closed?

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

[kdenlive] [Bug 467596] Doesnt Play both audio tracks during playback

2023-03-20 Thread Marc

https://bugs.kde.org/show_bug.cgi?id=467596

Marc  changed:

   What|Removed |Added

   Platform|Other   |Microsoft Windows
 OS|Other   |Microsoft Windows

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

[kdenlive] [Bug 467596] Doesnt Play both audio tracks during playback

2023-03-20 Thread Marc

https://bugs.kde.org/show_bug.cgi?id=467596

Marc  changed:

   What|Removed |Added

  Component|general |User Interface
Product|kde |kdenlive
Version|unspecified |22.08.1
   Assignee|unassigned-b...@kde.org |j...@kdenlive.org

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

[kde] [Bug 467596] New: Doesnt Play both audio tracks during playback

2023-03-19 Thread Marc

https://bugs.kde.org/show_bug.cgi?id=467596

Bug ID: 467596
   Summary: Doesnt Play both audio tracks during playback
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: lil.m...@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. record a clip with mic and desktop audio separated (captured on obs)
2. load in your clip that has 2 audio tracks 
3. preview it, it only plays desktop audio.
Note: this is only for previewing it, if the clip is in the timeline it will
play both audio's correctly through the timeline playback. This if frustrating
when trimming clips because some clips context comes through the mic audio.

OBSERVED RESULT
Only hearing desktop audio when previewing a clip

EXPECTED RESULT
Hearing both desktop and mic audio when previewing a clip

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

ADDITIONAL INFORMATION

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

[kmail2] [Bug 465825] mail viewer crashes on this message

2023-03-16 Thread Marc Mezzarobba

https://bugs.kde.org/show_bug.cgi?id=465825

--- Comment #3 from Marc Mezzarobba  ---
Thanks a lot for taking a look!

You mean that the bug is *fixed* in zxing-cpp 2.0, right? (or should I report
it there?)

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

[kwin] [Bug 448839] [NVIDIA Wayland] Screen recording and task manager's window thumbnails are black

2023-03-13 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=448839

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #19 from Marc Deop  ---
I cannot share neither windows nor screens on Firefox or Chromium. I only get a
black screen (although with a cursor).

OBS Recording *does* work as well as thumbnails.

System:
Plasma 5.27.2
Frameworks 5.104.0
Fedora RPMs
Nvidia 1070
Nvidia Drivers: 525.89.02

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

[NeoChat] [Bug 467242] New: Search "toolbar" has the wrong size and "overlaps" onto the rooms area

2023-03-12 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=467242

Bug ID: 467242
   Summary: Search "toolbar" has the wrong size and "overlaps"
onto the rooms area
Classification: Applications
   Product: NeoChat
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: k...@marcdeop.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 157213
  --> https://bugs.kde.org/attachment.cgi?id=157213=edit
overlap_onto_rooms_section

The search toolbar is a bit to big and overlaps onto the rooms area. See the
screenshot


Linux/KDE Plasma: 
KDE Plasma Version: 5.27.2 
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

I build neochat myself and make it available on my copr:
https://copr.fedorainfracloud.org/coprs/marcdeop/neochat-git/

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

[kdenetwork-filesharing] [Bug 466786] "make me a group member" button didn't work because the samba user shares group didn't contain the text "samba", but this wasn't mentioned anywhere

https://bugs.kde.org/show_bug.cgi?id=466786

--- Comment #23 from Marc Deop  ---
(In reply to Harald Sitter from comment #19)
> Yeah, I don't understand your question.
> 
> Because you can pass any old group in we need to limit the amount of garbage
> groups you can put in to abuse the system.

Let me rephrase the question then:

What makes a group name `sambausers` safer than a group name
`thisismyfavouritegroupname` ?

Either would be set by our system (in our Fedora's usecase by the
"samba-usershares" package).

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

[kdenetwork-filesharing] [Bug 466786] "make me a group member" button didn't work because the samba user shares group didn't contain the text "samba", but this wasn't mentioned anywhere

https://bugs.kde.org/show_bug.cgi?id=466786

--- Comment #18 from Marc Deop  ---
(In reply to Harald Sitter from comment #17)
> One can ask the auth helper to make the user a member of any group

That is very nice but the question remains: Why does kde need to do some
hardening via group name?

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

[kdenetwork-filesharing] [Bug 466786] "make me a group member" button didn't work because the samba user shares group didn't contain the text "samba", but this wasn't mentioned anywhere

https://bugs.kde.org/show_bug.cgi?id=466786

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #16 from Marc Deop  ---
(In reply to Harald Sitter from comment #7)
> Not sure I understand the question. Yes, we need some hardening ^^

Why does kde need to do some hardening via group name? I am not sure I
understand.

The hardening would be done by the samba administrators and deciding whether to
allow the usershares functionality and under what group (via write permissions
I think).

Or am I missing something?

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

[kwin] [Bug 466969] Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM (Wayland)

https://bugs.kde.org/show_bug.cgi?id=466969

--- Comment #10 from Marc Deop  ---
Unfortunately the patches do not seem to work for me :(

I have Frameworks 5.104.0 (with the latest re-spin), kwin 5.27.2 with added
patches
(https://download.copr.fedorainfracloud.org/results/@kdesig/kde/fedora-37-x86_64/05619797-kwin/)
the specific lines (from the spec file):
## upstream patches
Patch1:
make-sure-input-backends-are-initialised-when-the-workspace-is-set-up.patch
Patch2: show-the-input-method-even-if-it-was-dismissed.patch

I also have patched maliit-keyboard:
https://koji.fedoraproject.org/koji/taskinfo?taskID=98502688

Do we perhaps need the other commits I can see on kwin's side of things? or
perhaps other commits on maliit-keyboard?

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

[kwin] [Bug 466969] Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM (Wayland)

2023-03-08 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=466969

--- Comment #4 from Marc Deop  ---
(In reply to Aleix Pol from comment #3)
> Is it when you use the mouse that it doesn't appear? My guess is that it's
> the "was it triggered by a touch event?" feature  that is getting in the way.
> 
> I'd been trying to debug this yesterday, but I'm getting hit by an unrelated
> issue that wouldn't let me.

No. The virtual keyboard never shows when I press/click/touch the button via
mouse, touchpad or touchscreen.

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

[kwin] [Bug 466969] Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM (Wayland)

https://bugs.kde.org/show_bug.cgi?id=466969

--- Comment #1 from Marc Deop  ---
I forgot to mention this only happens on Wayland

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

[kwin] [Bug 466969] Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM (Wayland)

https://bugs.kde.org/show_bug.cgi?id=466969

Marc Deop  changed:

   What|Removed |Added

Summary|Virtual Keyboard button |Virtual Keyboard button
   |doesn't make the virtual|doesn't make the virtual
   |keyboard appear on SDDM |keyboard appear on SDDM
   ||(Wayland)

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

[plasmashell] [Bug 466968] Cannot scroll through the list of Keyboard Layouts on SDDM (with a touchscreen)

https://bugs.kde.org/show_bug.cgi?id=466968

--- Comment #2 from Marc Deop  ---
Created attachment 157090
  --> https://bugs.kde.org/attachment.cgi?id=157090=edit
layouts_list

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

[kwin] [Bug 466721] Touchscreen does not work when using kwin_wayland as compositorcommand on SDDM

https://bugs.kde.org/show_bug.cgi?id=466721

--- Comment #6 from Marc Deop  ---
I confirm it's fixed for me.

Fix available on our copr repository:
https://copr.fedorainfracloud.org/coprs/g/kdesig/kde/

I will bring it to the normal repositories with Plasma 5.27.3 next week

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

[kwin] [Bug 466969] New: Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM

2023-03-06 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=466969

Bug ID: 466969
   Summary: Virtual Keyboard button doesn't make the virtual
keyboard appear on SDDM
Classification: Plasma
   Product: kwin
   Version: 5.27.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: virtual-keyboard
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@marcdeop.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Start computer to SDDM
2. Press the "Virtual Keyboard" button on the lower left corner

OBSERVED RESULT
Nothing seems to happen

EXPECTED RESULT
The virtual keyboard shows up (same as if I touched an input field with the
touchscreen)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[kwin] [Bug 466968] New: Cannot scroll through the list of Keyboard Layouts on SDDM (with a touchscreen)

2023-03-06 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=466968

Bug ID: 466968
   Summary: Cannot scroll through the list of Keyboard Layouts on
SDDM (with a touchscreen)
Classification: Plasma
   Product: kwin
   Version: 5.27.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: libinput
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@marcdeop.com
  Target Milestone: ---

SDDM running with: CompositorCommand=kwin_wayland --no-global-shortcuts
--no-lockscreen --inputmethod maliit-keyboard --locale1

Touching on the "Keyboard Layout" button on the lower left part of the screen
shows the list of possible layouts but it's not easily scrolable with the
touchscreen.

Scrolling though the list is  only possible after making appear the "scrolling
sidebar" (is that how it's called?). However, it takes me many attempts to make
it appear and then to **select* it.

STEPS TO REPRODUCE
1. Touch the "Keyboard Layout" selector 
2. Try to scroll through the list via the touchscreen


OBSERVED RESULT
There doesn't seem to be any obvious way to scroll the list (no button, no
indicator, no two fingers, no three fingers...)

EXPECTED RESULT
To be able to scroll through the list. Ideally just with the finger/s or
alternatively with a button to go up/down the list

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[amarok] [Bug 459933] ffmpeg-5 support

2023-03-06 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=459933

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #1 from Marc Deop  ---
Possibly related: https://invent.kde.org/multimedia/amarok/-/merge_requests/45

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

[kwin] [Bug 466721] Touchscreen does not work when using kwin_wayland as compositorcommand on SDDM

2023-03-03 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=466721

--- Comment #1 from Marc Deop  ---
Something I found out and it might be relevant:

After switching to a different TTY and getting back to SDDM... now the touch
events work. Curious.

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

[kwin] [Bug 466721] New: Touchscreen does not work when using kwin_wayland as compositorcommand on SDDM

2023-03-02 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=466721

Bug ID: 466721
   Summary: Touchscreen does not work when using kwin_wayland as
compositorcommand on SDDM
Classification: Plasma
   Product: kwin
   Version: 5.27.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: libinput
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@marcdeop.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Boot the computer into SDDM on Wayland
2. Try the touchscreen... nothing happens

OBSERVED RESULT
Touching the screen doesn't seem to have any effect

EXPECTED RESULT
The touchscreen works

SOFTWARE/OS VERSIONS

Linux: 6.1.12-200.fc37.x86_64
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION:

After enabling WAYLAND_DEBUG=1 I could see this on the logs:

Mar 01 22:46:40 marc-xps15 sddm-helper-start-wayland[13601]: "kwin_libinput:
Touch down received for device with no output assigned


The CompositorCommand on SDDM is set to:
kwin_wayland --no-global-shortcuts --no-lockscreen --inputmethod
maliit-keyboard --locale1

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

[frameworks-kcoreaddons] [Bug 466562] New: Remove support for FAM ( long dead project)

2023-02-27 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=466562

Bug ID: 466562
   Summary: Remove support for FAM ( long dead project)
Classification: Frameworks and Libraries
   Product: frameworks-kcoreaddons
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: task
  Priority: NOR
 Component: general
  Assignee: mp...@kde.org
  Reporter: k...@marcdeop.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
While attempting to improve our packaging on Fedora, we noticed kcoreaddons
still has support for FAM in the CMakeLists.txt file.

This is a *LONG* dead project, same goes for it's alternatives (gamin and
others).

Perhaps it would be good to clean up the code.

I am talking about:
https://invent.kde.org/frameworks/kcoreaddons/-/blob/master/CMakeLists.txt#L52


STEPS TO REPRODUCE
1. Build kcoreaddons

OBSERVED RESULT
...
The following OPTIONAL packages have not been found:
 * FAM, File alteration notification support via a separate service,

   Provides file alteration notification facilities using a separate service.
FAM provides additional support for NFS.
...

EXPECTED RESULT
Not "warning" due to missing FAM


ADDITIONAL INFORMATION
https://web.archive.org/web/20050827205603/http://oss.sgi.com/projects/fam/doc.html
https://en.wikipedia.org/wiki/File_Alteration_Monitor

Gnome removed support: https://gitlab.gnome.org/GNOME/glib/-/issues/2614

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

[neon] [Bug 462695] Automatic DisplayPort screen dimming/sleep and system sleep stops working on Wayland

2023-02-26 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=462695

--- Comment #44 from Marc Deop  ---
(In reply to Wilson Phillips from comment #43)
> I don't understand why this is marked as closed when the problem has not
> been fixed.
> 

It's been fixed on KDE side. Nothing they can do about it.

> Running openSUSE Tumbleweed/KDE 5.27.1 and the problem still exists. I can
> switch to X11 and it works just fine. It only fails to work in Wayland. This
> is on a laptop with no external screen attached.

This is something openSUSE needs to fix the same way Neon or we (Fedora) did.

Again, everything is fine on the KDE side of things.

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

[neon] [Bug 462695] Automatic DisplayPort screen dimming/sleep and system sleep stops working on Wayland

2023-02-23 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=462695

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #40 from Marc Deop  ---
(In reply to Aleix Pol from comment #39)
> I've confirmed with the Fedora team that they also had this problem and
> they're looking into addressing it.

This has been fixed on Fedora here:
https://src.fedoraproject.org/rpms/kf5-kidletime/c/2a096ad8d7e9ab9a838156021991d86e76971117?branch=rawhide

It will take a few minutes/hours to reach the stable servers.

For those who want it **now**, you can use our COPR:
https://copr.fedorainfracloud.org/coprs/g/kdesig/kde/

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

[kwin] [Bug 456625] New rewritten Kwin results in TOTAL plasma/keyboard/mouse clicks FREEZE (Reproducible)

2023-02-22 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=456625

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #4 from Marc Deop  ---
(In reply to Nate Graham from comment #3)
> Cannot reproduce on X11 or Wayland with any of those steps FWIW. It's an
> extremely odd sequence of events to cause such a bug.

I cannot reproduce either on Fedora 37 with Plasma 5.27.1

Nvidia 1070

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

[kmail2] [Bug 465825] mail viewer crashes on this message

2023-02-16 Thread Marc Mezzarobba

https://bugs.kde.org/show_bug.cgi?id=465825

--- Comment #1 from Marc Mezzarobba  ---
Created attachment 156294
  --> https://bugs.kde.org/attachment.cgi?id=156294=edit
bracktrace

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

[kmail2] [Bug 465825] New: mail viewer crashes on this message

2023-02-16 Thread Marc Mezzarobba

https://bugs.kde.org/show_bug.cgi?id=465825

Bug ID: 465825
   Summary: mail viewer crashes on this message
Classification: Applications
   Product: kmail2
   Version: 5.22.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: marc+b...@mezzarobba.net
  Target Milestone: ---

Created attachment 156293
  --> https://bugs.kde.org/attachment.cgi?id=156293=edit
testcase

SUMMARY

kmail crashes when opening the attached message. I am not sure where to report
the bug as the backtrace suggests that KItinerary is involved.

STEPS TO REPRODUCE
1. kmail --view spam_crashing_kmail

(alternatively, put the message in some kmail folder and click on it from the
message list)

SOFTWARE/OS VERSIONS

debian sid
kmail2 5.22.2 (22.12.2)
itinerary 22.12.1
zxing 1.4.0

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

[okular] [Bug 465708] Okular crashes when reloading pdf

2023-02-16 Thread Marc van der Sluys

https://bugs.kde.org/show_bug.cgi?id=465708

--- Comment #2 from Marc van der Sluys  ---
Unfortunately, this specific document is not public yet and not mine to
share...

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

[okular] [Bug 465708] New: Okular crashes when reloading pdf

2023-02-14 Thread Marc van der Sluys

https://bugs.kde.org/show_bug.cgi?id=465708

Bug ID: 465708
   Summary: Okular crashes when reloading pdf
Classification: Applications
   Product: okular
   Version: 22.08.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: li...@vandersluys.nl
  Target Milestone: ---

Application: okular (22.08.3)
 (Compiled from sources)
Qt Version: 5.15.8
Frameworks Version: 5.99.0
Operating System: Linux 5.10.76-gentoo-r1.009 x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
Okular crashes when reloading a pdf document while it is regenerated by LaTeX.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Okular (okular), signal: Aborted

[KCrash Handler]
#4  0x7fd657be865c in __pthread_kill_implementation () from
/lib64/libc.so.6
#5  0x7fd657b9cab2 in raise () from /lib64/libc.so.6
#6  0x7fd657b87471 in abort () from /lib64/libc.so.6
#7  0x7fd61cb8535f in ?? () from /usr/lib64/libpoppler.so.126
#8  0x7fd61cc749b9 in OutlineItem::hasKids() () from
/usr/lib64/libpoppler.so.126
#9  0x7fd61cf67acf in ?? () from
/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so
#10 0x7fd61cf67e12 in ?? () from
/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so
#11 0x7fd64427039d in TOC::notifySetup(QVector const&, int)
() from /usr/lib64/qt5/plugins/okularpart.so
#12 0x7fd63c558183 in Okular::Document::openDocument(QString const&, QUrl
const&, QMimeType const&, QString const&) () from
/usr/lib64/libOkular5Core.so.10
#13 0x7fd6441cc885 in Okular::Part::doOpenFile(QMimeType const&, QString
const&, bool*) () from /usr/lib64/qt5/plugins/okularpart.so
#14 0x7fd6441cd65e in Okular::Part::openFile() () from
/usr/lib64/qt5/plugins/okularpart.so
#15 0x7fd65982d205 in ?? () from /usr/lib64/libKF5Parts.so.5
#16 0x7fd65982e2cd in KParts::ReadOnlyPart::openUrl(QUrl const&) () from
/usr/lib64/libKF5Parts.so.5
#17 0x7fd6441be31f in Okular::Part::slotAttemptReload(bool, QUrl const&) ()
from /usr/lib64/qt5/plugins/okularpart.so
#18 0x7fd6441be851 in ?? () from /usr/lib64/qt5/plugins/okularpart.so
#19 0x7fd6581fdf62 in ?? () from /usr/lib64/libQt5Core.so.5
#20 0x7fd658201f7a in QTimer::timeout(QTimer::QPrivateSignal) () from
/usr/lib64/libQt5Core.so.5
#21 0x7fd6581f5fef in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#22 0x7fd658c1872f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#23 0x7fd6581cb638 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#24 0x7fd65821ae8b in QTimerInfoList::activateTimers() () from
/usr/lib64/libQt5Core.so.5
#25 0x7fd65821b734 in ?? () from /usr/lib64/libQt5Core.so.5
#26 0x7fd6569a488b in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#27 0x7fd6569a4b38 in ?? () from /usr/lib64/libglib-2.0.so.0
#28 0x7fd6569a4bef in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#29 0x7fd65821bb2e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#30 0x7fd6581ca0c3 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#31 0x7fd6581d23c0 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#32 0x55fb96b30259 in ?? ()
#33 0x7fd657b8834a in __libc_start_call_main () from /lib64/libc.so.6
#34 0x7fd657b883fc in __libc_start_main () from /lib64/libc.so.6
#35 0x55fb96b311f1 in ?? ()
[Inferior 1 (process 32598) detached]

Reported using DrKonqi

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

[korganizer] [Bug 465625] New: KOrganizer crashes immediately after creating a calendar event

2023-02-12 Thread Marc Joliet

https://bugs.kde.org/show_bug.cgi?id=465625

Bug ID: 465625
   Summary: KOrganizer crashes immediately after creating a
calendar event
Classification: Applications
   Product: korganizer
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: mar...@gmx.de
  Target Milestone: ---

Application: korganizer (5.22.2 (22.12.2))

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.10-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
I was creating a calendar event and after finishing adding all the attributes I
wanted (reminders, tags, etc.) hit "Apply", immediately after which KOrganizer
crashed.  When I restarted it, the calendar entry had been succesfully created,
with all the attributes intact.  There are several bugs that look similar
(including one I created), but I'm not confident enough to determine whether
they are actually identical or not.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault

[KCrash Handler]
#4  QSortFilterProxyModelPrivate::proxy_to_source (this=0x558fdfd08a90,
proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:571
#5  0x7f7cfa0a7ee2 in QSortFilterProxyModel::mapToSource (proxyIndex=...,
this=0x558fe0176070) at itemmodels/qsortfilterproxymodel.cpp:3171
#6  QSortFilterProxyModelPrivate::store_persistent_indexes (this=) at itemmodels/qsortfilterproxymodel.cpp:1248
#7  0x7f7cfa0a9a3b in
QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged
(this=0x558fdfd08a90, sourceParents=..., hint=) at
itemmodels/qsortfilterproxymodel.cpp:1639
#8  0x7f7cfa11360c in doActivate (sender=0x558fe0174700,
signal_index=9, argv=0x7ffd02e1c390) at kernel/qobject.cpp:3935
#9  0x7f7cfa10c80f in QMetaObject::activate
(sender=sender@entry=0x558fe0174700, m=m@entry=0x7f7cfa3b1d40
,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffd02e1c390)
at kernel/qobject.cpp:3983
#10 0x7f7cfa0763d6 in QAbstractItemModel::layoutAboutToBeChanged
(this=this@entry=0x558fe0174700, _t1=..., _t2=,
_t2@entry=QAbstractItemModel::NoLayoutChangeHint) at
.moc/moc_qabstractitemmodel.cpp:578
#11 0x7f7cf9d7b104 in IncidenceEditorNG::AttendeeTableModel::setAttendees
(attendees=..., this=0x558fe0174700) at
/usr/src/debug/incidenceeditor-22.12.2/src/attendeetablemodel.cpp:213
#12 IncidenceEditorNG::IncidenceAttendee::load (this=0x558fe0174010,
incidence=...) at
/usr/src/debug/incidenceeditor-22.12.2/src/incidenceattendee.cpp:184
#13 0x7f7cf9d6b9ea in IncidenceEditorNG::CombinedIncidenceEditor::load
(this=this@entry=0x558fdf019b70, incidence=...) at
/usr/src/debug/incidenceeditor-22.12.2/src/combinedincidenceeditor.cpp:83
#14 0x7f7cf9dc6040 in
IncidenceEditorNG::IncidenceDialogPrivate::handleItemSaveFinish
(saveAction=IncidenceEditorNG::EditorItemManager::Create, this=0x558fdfbe44f0)
at /usr/src/debug/incidenceeditor-22.12.2/src/incidencedialog.cpp:526
#15 operator() (action=IncidenceEditorNG::EditorItemManager::Create,
__closure=) at
/usr/src/debug/incidenceeditor-22.12.2/src/incidencedialog.cpp:183
#16 QtPrivate::FunctorCall,
QtPrivate::List, void,
IncidenceEditorNG::IncidenceDialogPrivate::IncidenceDialogPrivate(Akonadi::IncidenceChanger*,
IncidenceEditorNG::IncidenceDialog*)::
>::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#17
QtPrivate::Functor,
1>::call,
void> (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#18
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#19 0x7f7cfa11338d in QtPrivate::QSlotObjectBase::call (a=0x7ffd02e1c740,
r=0x558fdfbe4f20, this=0x558fe0207fc0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate (sender=0x558fdeed10e0, signal_index=3,
argv=0x7ffd02e1c740) at kernel/qobject.cpp:3923
#21 0x7f7cfa10c80f in QMetaObject::activate
(sender=sender@entry=0x558fdeed10e0, m=m@entry=0x7f7cf9dfa8c0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd02e1c740)
at kernel/qobject.cpp:3983
#22 0x7f7cf9d6f182 in
IncidenceEditorNG::EditorItemManager::itemSaveFinished
(_t1=IncidenceEditorNG::EditorItemManager::Create, this=0x558fdeed10e0) at
/usr/src/debug/incidenceeditor-22.12.2/build/src/KF5IncidenceEditor_autogen/include/moc_editoritemmanager.cpp:171
#23 IncidenceEditorNG::ItemEditorPrivate::itemFetchResult (job=,
this=0x558fdf990aa0) at
/usr/src/debug/incidenceeditor-22.12.2/src/editoritemmanager.cpp:127
#24 operator() (job=, __closure=) at

[kmail2] [Bug 462877] KMail crash when clicking on an Email

2023-01-27 Thread Marc Joliet

https://bugs.kde.org/show_bug.cgi?id=462877

--- Comment #5 from Marc Joliet  ---
Created attachment 155711
  --> https://bugs.kde.org/attachment.cgi?id=155711=edit
New crash information added by DrKonqi

kmail (5.22.1 (22.12.1)) using Qt 5.15.8

Just adding a new backtrace to show that the bug still occurs, and it still
happens consistently when opening an email before PGP signature verification
has finished.

-- Backtrace (Reduced):
#4  0x7ffbec33d7fe in QVector::begin
(this=) at /usr/include/qt5/QtCore/qvector.h:220
#5  KMime::Content::headerByType (this=this@entry=0x56336fe6cd40,
type=0x7ffbec356046 "Content-Transfer-Encoding") at
/usr/src/debug/kmime-22.12.1/src/kmime_content.cpp:617
#6  0x7ffbec33e65a in
KMime::Content::header (create=true,
this=0x56336fe6cd40) at /usr/src/debug/kmime-22.12.1/src/kmime_content.h:681
#7  KMime::Content::contentTransferEncoding (this=0x56336fe6cd40,
create=) at
/usr/src/debug/kmime-22.12.1/src/kmime_content.cpp:874
#8  0x7ffbec33f63f in KMime::ContentPrivate::decodeText (this=0x21,
q=q@entry=0x56336fe6cd40) at
/usr/src/debug/kmime-22.12.1/src/kmime_content.cpp:729

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

[systemsettings] [Bug 464532] The Flatpak kcm is not showing my flatpak apps

2023-01-23 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=464532

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #2 from Marc Deop  ---
(In reply to Tobias Fella from comment #1)
> This happens for me for "user" installed flatpaks; "system" installed
> flatpaks do show up

My user installed flatpaks do not show either.

( on Fedora from https://copr.fedorainfracloud.org/coprs/g/kdesig/kde-beta/ )

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

[krunner] [Bug 462254] No longer starting with shortcut key

2023-01-12 Thread Marc Deop

https://bugs.kde.org/show_bug.cgi?id=462254

Marc Deop  changed:

   What|Removed |Added

 CC||k...@marcdeop.com

--- Comment #6 from Marc Deop  ---
I experience this issue as well.

If I do `strace -p $krunner_pid` I gues a **lot** of messages like:
poll([{fd=5, events=POLLIN}, {fd=13, events=POLLIN}, {fd=54, events=POLLIN},
{fd=55, events=POLLPRI}, {fd=57, events=POLLIN}, {fd=99, events=POLLIN},
{fd=114, events=POLLIN}, {fd=128, events=POLLIN}, {fd=151, events=POLLIN}], 9,
499) = 0 (Timeout)


And whenever I press the alt+space combination I guet:
sendmsg(26, {msg_name={sa_family=AF_UNIX,
sun_path="/run/systemd/journal/socket"}, msg_namelen=30,
msg_iov=[{iov_base="MESSAGE=QCommandLineParser: argu"..., iov_len=105},
{iov_base="\n", iov_len=1}, {iov_base="PRIORITY=4", iov_len=10},
{iov_base="\n", iov_len=1}, {iov_base="CODE_FUNC=unknown", iov_len=17},
{iov_base="\n", iov_len=1}, {iov_base="CODE_LINE=0", iov_len=11},
{iov_base="\n", iov_len=1}, {iov_base="CODE_FILE=unknown", iov_len=17},
{iov_base="\n", iov_len=1}, {iov_base="QT_CATEGORY=default", iov_len=19},
{iov_base="\n", iov_len=1}, {iov_base="SYSLOG_IDENTIFIER=", iov_len=18},
{iov_base="krunner", iov_len=7}, {iov_base="\n", iov_len=1}], msg_iovlen=15,
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 211
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
sendmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="J\0\0\0\2\0\24\0\1\0\0\0\0\0\0\0O\0\0\0", iov_len=20}],
msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 20


So it seems like krunner does get the keystroke but it doesn't show up...

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

[kmail2] [Bug 462877] KMail crash when clicking on an Email

2022-12-26 Thread Marc Joliet

https://bugs.kde.org/show_bug.cgi?id=462877

--- Comment #4 from Marc Joliet  ---
OK, I think I've determined the precise cause of the crashes.  They
consistently happen when:
- clicking away from an Email,
- that is signed with a PGP key,
- *before* KMail has finished verifying the signature.
If I wait for signature verification to finish, KMail does not crash.

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

[kmail2] [Bug 462877] KMail crash when clicking on an Email

2022-12-14 Thread Marc Joliet

https://bugs.kde.org/show_bug.cgi?id=462877

--- Comment #3 from Marc Joliet  ---
Created attachment 154581
  --> https://bugs.kde.org/attachment.cgi?id=154581=edit
New crash information added by DrKonqi

kmail (5.22.0 (22.12.0)) using Qt 5.15.7

So the crashes still happen, and it's really annoying.  The backtrace is a
little different, but the behaviour I encounter is the same, so I'm assuming
this is still the same bug.  This is after a recent KDE frameworks update in
OpenSuse Tumbleweed.

-- Backtrace (Reduced):
#4  0x7f076d33d7fe in QVector::begin
(this=) at /usr/include/qt5/QtCore/qvector.h:220
#5  KMime::Content::headerByType (this=this@entry=0x564c37c96040,
type=0x7f076d356046 "Content-Transfer-Encoding") at
/usr/src/debug/kmime-22.12.0/src/kmime_content.cpp:617
#6  0x7f076d33e65a in
KMime::Content::header (create=true,
this=0x564c37c96040) at /usr/src/debug/kmime-22.12.0/src/kmime_content.h:681
#7  KMime::Content::contentTransferEncoding (this=0x564c37c96040,
create=) at
/usr/src/debug/kmime-22.12.0/src/kmime_content.cpp:874
#8  0x7f076d33f63f in KMime::ContentPrivate::decodeText (this=0x30,
q=q@entry=0x564c37c96040) at
/usr/src/debug/kmime-22.12.0/src/kmime_content.cpp:729

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

[marble] [Bug 462981] Marble crashes when zooming in the Vector OSM map

https://bugs.kde.org/show_bug.cgi?id=462981

--- Comment #1 from Marc Joliet  ---
Just a quick mention of my short attempts at reproducing this: after 3-5
crashes in a row (all of which happened in less than 10 seconds after launch),
the final attempt yielded no crash, no matter how much I zoomed and scrolled,
including previously un-downloaded sections of the map.  I tried one more time
after that and it still didn't crash.  I'll keep trying sporadically, but I
feel like it's either a randomly triggered bug (e.g., a race condition), or
some underlying variable changed.  Maybe mypreviously provided backtrace is
informative enough to help narrow it down, at least.

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

[marble] [Bug 462981] New: Marble crashes when zooming in the Vector OSM map

https://bugs.kde.org/show_bug.cgi?id=462981

Bug ID: 462981
   Summary: Marble crashes when zooming in the Vector OSM map
Classification: Applications
   Product: marble
   Version: unspecified
  Platform: OpenSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: mar...@gmx.de
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.15.7
Frameworks Version: 5.100.0
Operating System: Linux 6.0.12-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.26.4 [KCrashBackend]

-- Information about the crash:
I was trying out different maps and ended up at the Vector OSM one.  After
zooming into an arbitrary area (the inner city of Oldenburg, Lower Saxony,
Germany) all the way it crashed with a SEGFAULT.  I haven't tried reproducing
it.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Marble – Virtueller Globus (marble), signal: Segmentation fault

[KCrash Handler]
#4  0x7f36fc222007 in o5mreader_readStrPair (pReader=,
tagpair=0x7f36805127c8, single=1) at
/usr/src/debug/marble-22.12.0/src/3rdparty/o5mreader/o5mreader.cpp:58
#5  0x7f36fc22654a in o5mreader_iterateRefs
(pReader=pReader@entry=0x7f3680512790, refId=refId@entry=0x0,
type=type@entry=0x0, pRole=pRole@entry=0x0) at
/usr/src/debug/marble-22.12.0/src/3rdparty/o5mreader/o5mreader.cpp:454
#6  0x7f36fc22664f in o5mreader_skipRefs (pReader=) at
/usr/src/debug/marble-22.12.0/src/3rdparty/o5mreader/o5mreader.cpp:492
#7  o5mreader_iterateTags (pReader=0x7f3680512790, pKey=0x0, pVal=0x0) at
/usr/src/debug/marble-22.12.0/src/3rdparty/o5mreader/o5mreader.cpp:294
#8  0x7f36fc21bb7c in o5mreader_skipTags (pReader=) at
/usr/src/debug/marble-22.12.0/src/3rdparty/o5mreader/o5mreader.cpp:327
#9  o5mreader_skipTags (pReader=0x7f3680512790) at
/usr/src/debug/marble-22.12.0/src/3rdparty/o5mreader/o5mreader.cpp:324
#10 o5mreader_iterateDataSet (ds=, pReader=) at
/usr/src/debug/marble-22.12.0/src/3rdparty/o5mreader/o5mreader.cpp:203
#11 Marble::OsmParser::parseO5m (filename=..., error=...) at
/usr/src/debug/marble-22.12.0/src/plugins/runner/osm/OsmParser.cpp:65
#12 0x7f36fc21db92 in Marble::OsmParser::parse (error=..., filename=...) at
/usr/src/debug/marble-22.12.0/src/plugins/runner/osm/OsmParser.cpp:37
#13 Marble::OsmRunner::parseFile (this=, fileName=...,
role=Marble::UserDocument, error=...) at
/usr/src/debug/marble-22.12.0/src/plugins/runner/osm/OsmRunner.cpp:21
#14 0x7f371bbe7f09 in Marble::TileLoader::openVectorFile(QString const&)
const [clone .isra.0] (fileName=..., this=) at
/usr/src/debug/marble-22.12.0/src/lib/marble/TileLoader.cpp:323
#15 0x7f371bbdb256 in
Marble::TileLoader::loadTileVectorData(Marble::GeoSceneVectorTileDataset
const*, Marble::TileId const&, Marble::DownloadUsage) [clone .constprop.0]
(this=0x56299ac43878, textureLayer=, tileId=...,
usage=Marble::DownloadBrowse) at
/usr/src/debug/marble-22.12.0/src/lib/marble/TileLoader.cpp:111
#16 0x7f371bae629e in non-virtual thunk to Marble::TileRunner::run() () at
/usr/src/debug/marble-22.12.0/src/lib/marble/VectorTileModel.h:36
#17 0x7f3719af93e1 in QThreadPoolThread::run (this=0x56299de6b6c0) at
thread/qthreadpool.cpp:100
#18 0x7f3719af5e3d in QThreadPrivate::start (arg=0x56299de6b6c0) at
thread/qthread_unix.cpp:330
#19 0x7f371949398d in start_thread () from /lib64/libc.so.6
#20 0x7f371951a380 in clone3 () from /lib64/libc.so.6

Thread 69 (Thread 0x7f36515096c0 (LWP 18253) "marble:gdrv0"):
#1  0x7f3719492cd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7f36fe4baa5b in cnd_wait (mtx=0x56299fe6f830, cond=0x56299fe6f858) at
../src/c11/impl/threads_posix.c:135
#3  util_queue_thread_func (input=input@entry=0x5629a108ec70) at
../src/util/u_queue.c:287
#4  0x7f36fe503f27 in impl_thrd_routine (p=) at
../src/c11/impl/threads_posix.c:67
#5  0x7f371949398d in start_thread () from /lib64/libc.so.6
#6  0x7f371951a380 in clone3 () from /lib64/libc.so.6

Thread 68 (Thread 0x7f364e5036c0 (LWP 18247) "marble:gdrv0"):
#1  0x7f3719492cd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7f36fe4baa5b in cnd_wait (mtx=0x5629a1904c40, cond=0x5629a1904c68) at
../src/c11/impl/threads_posix.c:135
#3  util_queue_thread_func (input=input@entry=0x5629a178b890) at
../src/util/u_queue.c:287
#4  0x7f36fe503f27 in impl_thrd_routine (p=) at
../src/c11/impl/threads_posix.c:67
#5  0x7f371949398d in start_thread () from /lib64/libc.so.6
#6  0x7f371951a380 in clone3 () from /lib64/libc.so.6

Thread 67 (Thread 0x7f364fd066c0 (LWP 18246) "marble:gdrv0"):
#1  0x7f3719492cd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7f36fe4baa5b in cnd_wait (mtx=0x5629a2887e30, cond=0x5629a2887e58)

[kmail2] [Bug 462877] KMail crash when clicking on an Email

https://bugs.kde.org/show_bug.cgi?id=462877

--- Comment #2 from Marc Joliet  ---
Created attachment 154539
  --> https://bugs.kde.org/attachment.cgi?id=154539=edit
New crash information added by DrKonqi

kmail (5.22.0 (22.12.0)) using Qt 5.15.7

This is one of the latest crashes.  However, I then ran "akonadictl fsck" and
"akonadictl vacuum", and immediately afterwards I was finally able to read the
emails that were triggering the crash without any visible issue.

-- Backtrace (Reduced):
#4  0x7f96609fc7fe in KMime::Content::headerByType(char const*) const ()
from /lib64/libKF5Mime.so.5
#5  0x7f96609fd65a in KMime::Content::contentTransferEncoding(bool) () from
/lib64/libKF5Mime.so.5
[...]
#7  0x7f96609fe777 in KMime::Content::decodedText(bool, bool) () from
/lib64/libKF5Mime.so.5
#8  0x7f966106ed3d in MimeTreeParser::ObjectTreeParser::extractNodeInfos
(isFirstTextPart=, curNode=0x5562b987b240, this=0x7fff079626c0)
at
/usr/src/debug/messagelib-22.12.0/mimetreeparser/src/objecttreeparser.cpp:270
#9  MimeTreeParser::ObjectTreeParser::extractNodeInfos
(this=this@entry=0x7fff079626c0, curNode=0x5562b987b240,
isFirstTextPart=isFirstTextPart@entry=true) at
/usr/src/debug/messagelib-22.12.0/mimetreeparser/src/objecttreeparser.cpp:267

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

[kmail2] [Bug 462877] KMail crash when clicking on an Email

https://bugs.kde.org/show_bug.cgi?id=462877

--- Comment #1 from Marc Joliet  ---
Created attachment 154529
  --> https://bugs.kde.org/attachment.cgi?id=154529=edit
New crash information added by DrKonqi

kmail (5.22.0 (22.12.0)) using Qt 5.15.7

This was one of many crashes I got today trying to read the same email several
times in a row.  So I suppose the bug is now at least partially reproducible.

-- Backtrace (Reduced):
#4  0x7f29caeff7fe in KMime::Content::headerByType(char const*) const ()
from /lib64/libKF5Mime.so.5
#5  0x7f29caf0065a in KMime::Content::contentTransferEncoding(bool) () from
/lib64/libKF5Mime.so.5
[...]
#7  0x7f29caf01777 in KMime::Content::decodedText(bool, bool) () from
/lib64/libKF5Mime.so.5
#8  0x7f29cb571d3d in MimeTreeParser::ObjectTreeParser::extractNodeInfos
(isFirstTextPart=, curNode=0x55ba8ec971a0, this=0x7ffccd3ab7d0)
at
/usr/src/debug/messagelib-22.12.0/mimetreeparser/src/objecttreeparser.cpp:270
#9  MimeTreeParser::ObjectTreeParser::extractNodeInfos
(this=this@entry=0x7ffccd3ab7d0, curNode=0x55ba8ec971a0,
isFirstTextPart=isFirstTextPart@entry=true) at
/usr/src/debug/messagelib-22.12.0/mimetreeparser/src/objecttreeparser.cpp:267

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

[kmail2] [Bug 462877] KMail crash when clicking on an Email