[plasmashell] [Bug 486624] New: Mounting drives increases CPU usage until hitting 100%

[Maarten Steevens]

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

Bug ID: 486624
   Summary: Mounting drives increases CPU usage until hitting 100%
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Disks & Devices
  Assignee: plasma-b...@kde.org
  Reporter: maaste...@gmail.com
  Target Milestone: 1.0

Created attachment 169212
  --> https://bugs.kde.org/attachment.cgi?id=169212=edit
Screenshot showing plasmashell at 103% cpu usage. Usually it's somewhere around
1%.

SUMMARY
I have been playing around with microcontrollers such as the Raspberry Pi Pico
recently and noticed that every time I plug in the board and mount it to flash
a new uf2 file my cpu usage increases. After mounting it several times to flash
new builds the cpu usage increases to 100% percent making plasma practically
unusable. At that point I restart plasmashell and then the cycle begins again
until it reaches 100%. So it appears that plasma is maybe not really keeping
track of the device disappearing upon it being flashed causing it to keep track
of many devices that are no longer there?

STEPS TO REPRODUCE
Not sure how reproducable this will be but it happens every time on my system.
1. Mount a USB mass storage device (in my case the Raspberry Pi Pico)
2. Place a uf2 file on the board resulting in it disappearing  (Maybe just
unplugging will also work, but I feel like the disappearing part might actually
be what causes the issue with plasma keeping track of a device that's no longer
there.)
3. Unplug and mount again
4. Go back to step 1, repeat this for a while

OBSERVED RESULT
The cpu usage of plasmashell will be 100%.

EXPECTED RESULT
No increase in cpu usage, cpu usage should not increase when mounting devices
and later unmounting  them.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-25-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: HP
Product Name: HP ProBook 450 G6

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

[krita] [Bug 485582] Animation plays from wrong frame after setting playhead during playback.

[Maarten]

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

--- Comment #2 from Maarten  ---
(In reply to Emmet O'Neill from comment #1)
> Hi Maarten, thanks for the bug report. 
> I've been able to reproduce this bug on the latest master branch, so I'm
> confirming it.
> 
> I think this is an edge case to do with changing the play head while the
> animation is playing.

Hi Emmet, Thanks for your response and great to see it's being picked up.

I don't think this is an edge case as it's not happening while the animation is
playing, but also happens when the animation is not playing. Please see video.

Thanks again!

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

[krita] [Bug 485582] New: Krita plays from wrong frame after setting playhead

[Maarten]

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

Bug ID: 485582
   Summary: Krita plays from wrong frame after setting playhead
Classification: Applications
   Product: krita
   Version: 5.2.2
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

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

SUMMARY
Timeline uses wrong start frame after positioning play head.

STEPS TO REPRODUCE
Please see video in attachment
1. Play
2. Stop
3. Position playhead on a frame
4. Play

OBSERVED RESULT
See that krita does not play from the frame where the playhead is

EXPECTED RESULT
Play from selected frame.

SOFTWARE/OS VERSIONS
Windows: 11 pro
Krita: 5.2.2

ADDITIONAL INFORMATION
Please see video in attachment

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

[kded-appmenu] [Bug 484879] Hovering over the app launcher menu button in a vertical panel, the name of an app (in this case “anydesk”) appears

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Maarten  ---


*** This bug has been marked as a duplicate of bug 433079 ***

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

[plasmashell] [Bug 433079] On Wayland container windows created by XEmbedSNIProxy are not stacked below root window

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 CC||m_bec...@mailbox.org

--- Comment #34 from Maarten  ---
*** Bug 484879 has been marked as a duplicate of this bug. ***

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

[kded-appmenu] [Bug 484879] Hovering over the app launcher menu button in a vertical panel, the name of an app (in this case “anydesk”) appears

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 CC||m_bec...@mailbox.org

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

[kded-appmenu] [Bug 484879] New: Hovering over the app launcher menu button in a vertical panel, the name of an app (in this case “anydesk”) appears

[Maarten]

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

Bug ID: 484879
   Summary: Hovering over the app launcher menu button in a
vertical panel, the name of an app (in this case
“anydesk”) appears
Classification: Plasma
   Product: kded-appmenu
   Version: 6.0.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: export
  Assignee: plasma-b...@kde.org
  Reporter: m_bec...@mailbox.org
  Target Milestone: ---

Created attachment 168026
  --> https://bugs.kde.org/attachment.cgi?id=168026=edit
Vertical panel with app popup after hovering the app menu

SUMMARY
When I hover over the app launcher menu button in a vertical panel, the name of
an app (in this case “anydesk”) appears (see attachment) and if I click it
opens. This is annoying, when I want to open the app menu, but click on the app
icon that shouldn’t be there.

I switched also to the horizontal panel, in that case I didn't see this
behavior.

Also, when deactivating "anydesk" completely, this behavior stopps. So, either
this is a "anydesk" problem or a strange behavior of the vertical panel in
combination with "anydesk"

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Recent OpenSuse Tumbleweed
(available in About System)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

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

[kscreenlocker] [Bug 448211] Sessions are breaking all the time when starting from standby on Debian with Wayland - it shows a black screen with "the screen locker is broken"

[Maarten Steevens]

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

Maarten Steevens  changed:

   What|Removed |Added

 CC||maaste...@gmail.com

--- Comment #5 from Maarten Steevens  ---
I was hoping it might be fixed in plasma 6.0 because wayland is now the
default. But the bug still occurs to this day with plasma 6.0.2 on kde neon.
The steps posted to reproduce the bug where you unplug a monitor while your
laptop sleeps are still valid. I run into this issue multiple times every day
(basically every time I wake up my laptop). In my case it happens because my
external monitor (connect over usb-c) wakes up slightly too slow so it's
practically the same thing as if it was unplugged when waking it from sleep.
One trick I sometimes use is to manually wake up my monitor by pressing one of
its buttons and then waking up my laptop.

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

[Discover] [Bug 481932] "Unable to create KIO worker. Unknown protocol 'appstream'." error when using "Get " feature

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 CC||maaste...@gmail.com

--- Comment #15 from Maarten  ---
Interestingly, the fix provided in plasma 6.0.1 actually seems to break kde
neon. I just upgraded my kde neon installation from plasma 5 to 6.0.2 and
kickoff was not showing any applications and the task manager on my panel was
also not working. So I searched around found this bug report and manually
reverted this change
(https://invent.kde.org/plasma/plasma-desktop/-/commit/54506e2b1405f5b5e8dade766b0ad63355e88f74)
and then everything started working again.

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

[krita] [Bug 473368] 'Export current palette to file' doesn't work

[Maarten]

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

Maarten  changed:

   What|Removed |Added

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

--- Comment #5 from Maarten  ---
Fixed in 5.2.0

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

[krita] [Bug 473368] 'Export current palette to file' doesn't work

[Maarten]

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

--- Comment #4 from Maarten  ---
(In reply to Freya Lupen from comment #3)
> They may seem different, but both issues have the same cause.
> Could you confirm whether it's fixed on 5.2.0-beta2?

Yes confirmed. Both export as well as import work on the beta

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

[krita] [Bug 473368] 'Export current palette to file' doesn't work

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|DUPLICATE   |---
 Status|RESOLVED|REOPENED

--- Comment #2 from Maarten  ---
I'm sorry, but I don't think this is a duplicate:

I had found that other thread here, but that is not about the same issue;

The other issue was about Krita creating an empty palette file, but even that
isn't happening here; NO file is created here. Nothing happens.

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

[krita] [Bug 473368] New: 'Export current palette to file' doesn't work

[Maarten]

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

Bug ID: 473368
   Summary: 'Export current palette to file' doesn't work
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

Created attachment 160952
  --> https://bugs.kde.org/attachment.cgi?id=160952=edit
Export button in Palette docker

SUMMARY
After hitting 'Export current palette to file' and hitting the Save-button
after choosing a path and using the automatically generated filename (from the
palette name), nothing happens. Changing the filename doesn't help.


STEPS TO REPRODUCE
See Summary and screenshot

OBSERVED RESULT
Nothing happens. File is not created

EXPECTED RESULT
Palette file created on disk.

SOFTWARE/OS VERSIONS
Windows: 11
KDE Frameworks Version: KDE Frameworks 5: LGPLv2.1+
Qt Version: Qt: GPLv2 + GPLv3 + LGPLv2.1 + LGPLv3

ADDITIONAL INFORMATION
See attachment

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

[frameworks-kio] [Bug 423031] [Wayland] Modifier keys to move (shift), copy (ctrl) and create a link (ctrl+shift) don't work if pressed after I start to drag the file/folder

[Maarten Bezemer]

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

Maarten Bezemer  changed:

   What|Removed |Added

 CC||maarten.beze...@gmail.com

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

[konqueror] [Bug 385119] Focus location bar on startup

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Maarten ter Huurne  ---
I can no longer reproduce the problem with Konqueror 22.08.3.

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

[krita] [Bug 446506] Onion Skin Artifacts

[Maarten]

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

--- Comment #4 from Maarten  ---
(In reply to vanyossi from comment #3)
> This is probably related to other tiling canvas artifacts. Setting  to
> confirmed

Having seen the artifacts in other places (outside of onion skinning) too, I
think you might be right as it looks the same

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

[krita] [Bug 459455] [request] please add multiple frames when multiple frame-slots are selected

[Maarten]

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

--- Comment #6 from Maarten  ---
(In reply to vanyossi from comment #5)
> Git commit ae8371b9b310164c4db99c03c7da0c8e844e9519 by Ivan Yossi.

Thanks for all your work Vanyossi! Looking forward to it!

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

[krita] [Bug 459524] Implement undo/redo in KoColorSet

[Maarten]

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

--- Comment #8 from Maarten  ---
(In reply to Halla Rempt from comment #7)
> And now it's lead to me refactoring a hairy bit of tangled-up code, but I'm
> still working on it!

Thanks for the updates and your efforts! I'm sure after all the refactoring
it's even better and more easy to maintain! ;)

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

[krita] [Bug 459455] [request] please add multiple frames when multiple frame-slots are selected

[Maarten]

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

--- Comment #4 from Maarten  ---
I'm forgetting one important thing which is probably even the most important
one which is making the current workflow unrealistic:

We seldom know the amount of frames to make blank or overwrite. And even if we
think we know the amount we will  still check it first before overwriting other
work to be 100% sure we don't loose existing frames.

It's pretty time consuming and error prone, but I think even unrealistic in
lots of cases, to count frames in the timeline to know what number to fill in
here. Try counting 50 frames in the timeline without making an error... And
than you can be happy if you don't need to scroll the timeline. AND rely on
your counting afterwards, because if you made a mistake, you loose work.

I think this workflow counts to much on straight ahead animation (adding frames
after the last frame). But most animators work with "pose to pose" methods most
of the time (so create keyframes on the important poses, and than start to fill
in the frames within that range.

When animating "straight ahead" it's not really an issue to insert just a
number of frames. But when adding the blanks within we must have an exact frame
count to not overwrite the already added keyframes. So this makes this method
not very realistic in real world usages when using pose-to-pose.

Hope this makes sense.

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

[krita] [Bug 459455] [request] please add multiple frames when multiple frame-slots are selected

[Maarten]

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

--- Comment #3 from Maarten  ---
(In reply to vanyossi from comment #1)
> To insert multiple keyframes: right click frame ->  Keyframe -> Insert
> Multiple Keyframes. This adds a given number of frames with a step value.

Thanks. I didn't find that one before.
By looking at it now tbh I don't think that one is very intuitive and takes
quite some thinking when using it which IMO shouldn't be necesary. With this
one:
- First we have to click three times to get to the menu
- Than we need to make sure the direction is set well (left or right)
- Than we need to make sure the timing is understood AND set well (btw for some
reason I don't get it was set to 10 here, while I would expect 1 to be default.
If it's doing what I think it's doing that is)
- We have to manually set the amount of frames to add... it doesn't look at the
amount of frames selected

This is also prone to errors, because when set something wrong (we like to work
fast and it's easy to have something wrong in this dialog as we need to think
about it), we should hope there's an undo level for it or we saved our work.

But most important thing: This is a looot of actions needed just to insert some
blank frames, while this could be way easier by the thing I requested: 
- click the button (or keyboard shortcut) to insert blank frames on the
selected frames. (only 1 action, could be controlled by a single keyboard
shortcut, no need to think about it so not prone to errors and everything is
visual, hard to make a mistake with this)


> However I do see why it feels akward that "add blank keyframe" does not act
> over the selection.

Thanks! Hope this could be added. This is a very often used action here and the
above described list of actions needed now is not very convenient for such a
simple task IMO.

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

[krita] [Bug 459524] Implement undo/redo in KoColorSet

[Maarten]

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

--- Comment #5 from Maarten  ---
@halla Rempt  You are amazing! Thank you!

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

[krita] [Bug 459524] Undo doesn't work after adding a new swatch to the palette by clicking on an empty swatch/palette slot

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 CC||i...@wigglepixel.nl

--- Comment #2 from Maarten  ---
(In reply to Halla Rempt from comment #1)
> Yes, the undo system only works on the image, not on other things in Krita.
> However, your feature request is a valid one. I cannot promise we can do
> anything about this anytime soon, though, since it would be complicated to
> implement an undo stack in the colorset class.

Thanks for the feedback. Completely understandable. It would be nice, but if
it's a lot of work for you guys to change this no worries, than I just get used
to it. It's a minor thing. Have a nice day!

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

[krita] [Bug 459550] New: [request] Please add a setting to enable/configure context aware tools in toolbox in preferences

[Maarten]

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

Bug ID: 459550
   Summary: [request] Please add a setting to enable/configure
context aware tools in toolbox in preferences
Classification: Applications
   Product: krita
   Version: 5.1.1
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

Created attachment 152355
  --> https://bugs.kde.org/attachment.cgi?id=152355=edit
example open toonz setting

I find it confusing and am constantly looking for the right tool on the layer
I'm working on. It happened a lot that I wasn't sure what tool to use to move
for instance just to find out (again) I picked a vector layer tool and got that
message again. After having this lots of times now I was wondering why these
tools aren't grayed out or hidden when on a different layer type. And if we
could switch this behaviour on or off somewhere.

So I asked this if there's a setting for it currently on the Krita reddit
channel. The response I got was that it used to be built the way I would expect
it to be (tools hidden or shown depending on the active layer type). But that
that behaviour was removed later by complaints of people who found that
confusing.

I personally don't get why it would be confusing if tools are visually disabled
(grayed out) if we cannot use them on a layer and think it's convenient, but
that's me with my preferences. I understand other people can have other
preferences and perspectives.

SOLUTION?
That's why I link the way the OpenTools software solved this exact same thing:
they added a single dropdown box in the preferences so each user could decide
for her-/himself what to set it to. Which I think is a great solution for
everybody. It prevents that this discussion stays for people who wants it this
way vs other people who want it that way I'd say.

These are the preferences OpenTools (and Tahoma2D) added in that dropdown:
- Default (= show all tools always, nothing grayed out, nothing hidden)
- Enable tools for layer only (so other tools are still visible and on the same
spot, but grayed out to indicate they're disabled)
- Show tools for layer only (so other tools are hidden and so don't fill up the
space, no placeholders, smaller toolset)

Just for the record because you probably know all ins and outs of the full code
base; Knu2l on the Krita channel on Reddit pointed out that the code to make
buttons visible/invisible in Krita is still present in there, so just to pass
this through;
https://invent.kde.org/graphics/krita/-/blob/master/libs/ui/toolbox/KoToolBox.cpp#L199

STEPS TO REPRODUCE
1. Switch to another type of layer
2. Look in the toolbox; still looking the same :)
3. Try a tool that's not possible for the current active layer
4. Think; oh no... I picked a wrong tool again :) I wished this ...-tool
(mostly vector for me) wouldn't show up when working with  (mostly raster for
me these days)
5. Find the right tool for the job

(see attachment)

BTW, not sure if this would be possible, but OpenTools also re-uses the same
buttons for different layer types. So a brush tool is available in the vector
layer type, but also in the raster layer types, while underwater is a
completely different tool and brush engine. But probably you're already doing
this. Not sure about that and it's getting late here :)

EXPECTED RESULT
Hoping for a way to configure this. That OpenToonz way would be marvelous and
would offer a setting for everybodies' taste!

Affinity Designer and Affinity Photo solved this challenge by having different
persona's (= modes) that switches the full view from raster to vector or visa
versa. So you either have all vector tools or raster tools and manually should
switch to them.

Also just looked at Moho (Animation software); they also have a (always)
content aware toolbox, so only show the tools possible for the selected layer
type.

BTW Don't get me wrong; I really love the GUI of Krita. Everything is so
intuitive and at the right place. Pretty impressive!

SOFTWARE/OS VERSIONS
Windows: 10

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

[krita] [Bug 459455] New: [request] please add multiple frames when multiple frame-slots are selected

[Maarten]

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

Bug ID: 459455
   Summary: [request] please add multiple frames when multiple
frame-slots are selected
Classification: Applications
   Product: krita
   Version: 5.1.1
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

Created attachment 152272
  --> https://bugs.kde.org/attachment.cgi?id=152272=edit
insert multiple frames at once-request

When creating frame-by-frame animations in Krita I think it's a nice workflow
to first add blank frames before creating the drawings. For one because it's
easy to forget to add a blank frame before drawing (happened to me a lot) and
than we're not drawing in a frame and have to do all kinds of tricks to get
that drawing into a frame or start over again.

To insert multiple blank frames tho we now have to:
- click a frame-slot
- click the 'insert blank frame' button (or assign a custom shortcut key and do
it with a keystroke? didn't try that yet)
And do this with all frames we wish to add. So adding just 6 frame is 12 clicks
and it adds up when creating longer animations.

It would be a lot easier and way faster if we could use the 'insert blank
frame' button on a multi-selection to insert multiple blank frames at once
(please see video in attachment).

Thanks in advance!

SOFTWARE/OS VERSIONS
Windows: 10

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

[krita] [Bug 459435] [Request] Workspaces directly reachable as buttons in (custom) toolbar

[Maarten]

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

Maarten  changed:

   What|Removed |Added

Summary|[Request]   |[Request] Workspaces
   ||directly reachable as
   ||buttons in (custom) toolbar

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

[krita] [Bug 459435] New: [Request]

[Maarten]

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

Bug ID: 459435
   Summary: [Request]
Classification: Applications
   Product: krita
   Version: 5.1.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

No big thing, just a little request: it's fantastic we have workspaces. It
speeds up the workflow  a lot. It would be great if we could even directly
click on a button in a (custom) toolbar on top to switch directly to a
workspace with just one click. Right now we have to click three times every
time we want to switch to another workspace (in my case from Animation to
Drawing and back):

- Click the workspaces button on the top-right corner
- Click on the wanted workspace to select it
- Close the workspaces dialog

It would be a lot faster if we could have a button for each workspace (or
drag'n'drop these) directly on the toolbar to instantly switch to it. Perhaps
it would be possible to add the workspaces as an option to drag unto a custom
toolbar?

SOFTWARE/OS VERSIONS
Windows:  10

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

[krita] [Bug 459261] Changing the keyboard shortcut for panning/pan tool doesn't work and throws issues

[Maarten]

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

--- Comment #3 from Maarten  ---
(In reply to Wojtek Trybus from comment #2)
> Keyboard shortcuts are only related to one-time actions like setting
> something. Those longer actions that include pen input like zooming and
> panning are specified in settings>configure krita>canvas inputs.

You guys are amazing. Completely understandable it's built this way and for
this use case perfect as it is. Just changed it in the canvas inputs and now it
works as expected! This made my day as now I can use spacebar in all animation
software used here!

Thanks for the quick response and all your hard work and have a nice day!

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

[krita] [Bug 459261] Changing the keyboard shortcut for panning/pan tool doesn't work and throws issues

[Maarten]

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

--- Comment #1 from Maarten  ---
Ah, I think I misunderstood this keyboard shortcut entry.
I see now when hitting Ctrl+Space it IS infact switching to the PAN TOOL, but
it's not the pan tool what I'm after to do with that shortcut, but PANNING,
what is normally done with hitting the Spacebar.

It's starting to look like the SPACEBAR to pan-behaviour (and the ctrl+Space
behaviour to zoom in/out) are hard coded.

This isn't only causing conflicts now when using space and ctrl+space as
keystrokes for other things, but this way it doesn't seem to be possible to
change these keyboard shortcuts for panning and zooming to other key strokes.

If that's the case guess this issue is more of a feature request (although
still a conflict) to make the keyboard shortcuts for panning and zooming
configurable so we can use the Spacebar shortcut for 'play/stop' instead. As
that's a pretty common stroke to start and stop animation in animation tools.

So please, make the keystrokes for panning and zooming the canvas configurable!

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

[krita] [Bug 458997] 'Start numbering at' doesn't work when rendering to image sequence

[Maarten]

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

--- Comment #5 from Maarten  ---
(In reply to Eoin O'Neill from comment #4)
> Hi Marteen,
> 
> No worries, thanks again for reporting the bug. If you want to test it out
> earlier, you can try out one of Krita's nightly version(s).

See it's present in 5.1.1, which I just installed. You guys are faster than the
light! Thanks for this!

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

[krita] [Bug 459261] New: Changing the keyboard shortcut for panning/pan tool doesn't work and throws issues

[Maarten]

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

Bug ID: 459261
   Summary: Changing the keyboard shortcut for panning/pan tool
doesn't work and throws issues
Classification: Unclassified
   Product: krita
   Version: 5.1.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

Created attachment 152143
  --> https://bugs.kde.org/attachment.cgi?id=152143=edit
ctrl+space is only connected to the 'pan tool', but still it does something
else and the pan tool is still controlled by the space bar

Changing keyboard shortcut for PANNING the canvas doesn't work and does strange
things.

STEPS TO REPRODUCE
1. Settings --> Configure Krita -->Keyboard shortcuts
2. Change the keyboard shortcut for 'Pan Tool' to 'Ctrl+Space'
3. Click OK
4. Keep SPACE pressed and LMB-drag the canvas --> the keyboard shortcut is
still just SPACE, while it should be CTRL+SPACE as we've just changed that.
Ctrl+Space shows some zoom tool.
5. Restart Krita
6. Keep SPACE pressed and LMB-drag the canvas --> still doesn't work with
Ctrl+Space

7. Settings --> Configure Krita -->Keyboard shortcuts 
8. Search for 'Space' --> nothing similar to 'panning' is connected to this
shortcut anymore (I have SPACE connected to 'Play / Pause animation' and that's
why I need to change the shortcut for panning)
9. Search for 'Ctrl+Space' --> 'Ctrl+Space' is only connected to the Pan tool,
just as we like it. So there is no conflict with another tool and neither it's
connected to some zoom-tool.

OBSERVED RESULT
See above.

EXPECTED RESULT
- When settings `ctrl+space` to the pan tool panning should not be controlled
by just hitting space bar anymore. Also ctrl+space should not trigger some
zoom-tool, but do the panning of the canvas, as that's the keyboard shortcut we
set it to

WHY
This is important, because I, like lots of animators / motion designers, are
used to start/stop animations with the spacebar. So when setting the spacebar
to play/stop it should not handle panning anymore as that's conflicting in the
workflow.

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
Great to see the 5.1.1 version fixed the long wait at startup! Very nice! And
keep up the great work

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

[krita] [Bug 458997] 'Start numbering at' doesn't work when rendering to image sequence

[Maarten]

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

--- Comment #3 from Maarten  ---
Wow, great work and nice to see you picked this up so soon! Thanks for that!
It's nice to be able to start our frames from a given number soon! Thanks again

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

[krita] [Bug 458862] Issues and feature requests regarding animation (timeline / onion skinning)

[Maarten]

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

--- Comment #2 from Maarten  ---
Hi Eoin,

No worries. I understand that it's best to split items and I normally do, but
this time it were a little bit too many for the time I had so, as an exception,
posted them in one thread. Understand why you ask and I Will mention other
things per item from now on.

**SYNCHRONISATION**

>> This doesn't sound right, it shouldn't be possible as the image itself is 
>> the only keeper of time (a layer and another layer cannot have different 
>> "current times", for example.) Can you provide an example project for this? 
>> Are you positive you haven't misaligned two keyframe positions in the 
>> timeline docker?

I woult think the same, but it really happened. Mostly frames are synchronized,
but sometimes they're not. Look in the video I created during the making of an
animation. At around 7 seconds of the video below on youtube (when the drawn
body comes in), the beak is not playing synchronized with the body. While this
WAS working when just manually stepping to the next frame. So frames are show
differently when playing an animation compared to when stepping through the
frames one by one. You can clearly see in the video that later on suddenly the
exact same beak (unchanged) is (somewhat?) synchronized again with the body.

https://youtu.be/iuyUtVQAj5E?t=7


**FIXED START/END FRAMES**

>> For the record, this is configurable as it's something we know users have 
>> differing opinions on. You can turn this off in unchecking `Settings > 
>> Configure Krita... > General > Miscellaneous  > Adapt Playback Range to 
>> Keyframes` I think an argument could be made that this setting should be 
>> made easier to find. Some users do actually prefer to have some adaptability 
>> to playback range (particularly, new users who just want a frame to render 
>> at a certain time, for instance.)

Thanks! That was exactly what I was looking for, but couldn't find. That did
the trick.

> This is also a setting, though more cleanly presented in the GUI as the "drop 
> frames" button. Generally speaking, animators like to keep frame time 
> consistency so stopping when the computer slows down is not ideal when it 
> comes animation. So, for example, frame 20 would either always occurs at 
> 0.8333 seconds or is skipped when it misses that deadline in favor of the 
> next immediate frame (when the computer is next available.) You can disable 
> this by unchecking the `drop frames` button on the animation title bar.

Yeah, I found that one after posting the issue here. Sorry for not mentioning
this. BTW It's practically impossible to see if this button is selected (at
least when in dark mode). It could use way better contrast at least in that
theme as you just cannot notice it's on or off.

For the rest basically the 'cycle onion skin' option was the one I really
missed, besides being able to copy and paste parts of one keyframe to another.
Both are overly complicated and time consuming now and I missed them a lot.


But especially for free software you guys did a very great job and I can't
complain. Also great that you react to this thread so soon already! There are
always things that can be better, but I love the brushes and just love the
overal feeling of using Krita. Keep up the great work!

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

[krita] [Bug 458999] Issues with Wacom Tablet display range: when moving pen canvas-region gets skipped

[Maarten]

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

--- Comment #2 from Maarten  ---
BTW At the time this pen screen range was broken, the mouse just functioned as
expected so didn't have this issue. Only the wacom pen had the issue

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

[krita] [Bug 458999] Issues with Wacom Tablet display range: when moving pen canvas-region gets skipped

[Maarten]

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

--- Comment #1 from Maarten  ---
Created attachment 151984
  --> https://bugs.kde.org/attachment.cgi?id=151984=edit
screen range issue

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

[krita] [Bug 458999] New: Issues with Wacom Tablet display range: when moving pen canvas-region gets skipped

[Maarten]

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

Bug ID: 458999
   Summary: Issues with Wacom Tablet display range: when moving
pen canvas-region gets skipped
   Product: krita
   Version: 5.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tablets (tablet issues are only very rarely bugs in
Krita!)
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

SUMMARY
Issues with Wacom Tablet display range: when moving pen canvas-region gets
skipped (see video).
Normally Wacom Intuos 4 is working fine in Krita and I've been working for days
in the same setup. Yesterday I shut down the computer, today I started the
computer again and suddenly the display region is not working again in Krita
anymore. I'm working in the exact same file, with the exact same settings and
no Windows update was applied in the mean time. So I would expect this to keep
working, but it didn't.

Reloading the file in Krita didn't fix this. Restarting Krita didn't fix this.
Opening a new file in Krita didn't fix this. Opening OBS Studio next to Krita
changed the issue tho; the 'skipped screen region' moved when OBS STudio was
open. When closing OBS Studio again the same issue was back again.

I needed to completely restart the PC to get it to work as expected again. This
tablet has no issues and works perfectly fine in other graphics software, like
Affinity, Blender, animation tools etc. 

STEPS TO REPRODUCE
? Feels completely random and instable. A week long it works completely
fine, also after turning off and on the computer, another day it's suddenly
broken without anything changed on the system, file or Krita.

OBSERVED RESULT
See video

EXPECTED RESULT
Keep working

SOFTWARE/OS VERSIONS
Windows: 10
Krita: 5.1.0

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

[krita] [Bug 458997] New: 'Start numbering at' doesn't work when rendering to image sequence

[Maarten]

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

Bug ID: 458997
   Summary: 'Start numbering at' doesn't work when rendering to
image sequence
   Product: krita
   Version: 5.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

SUMMARY
'Start numbering at' doesn't work when rendering to image sequence


STEPS TO REPRODUCE - TEST 1
1. Create a frame-by-frame animation starting from frame 24 and ending at frame
45 (for example. not starting at 0 or 1)
2. File --> Render Animation
3. Leave 'Start numbering at' at 0 to start output numbering on frame 0
4. Click 'OK' to render
5. Watch result in Windows Explorer: See that the frame numbers aren't starting
at 0, but at frame 24 as the original keyframe number on the timeline. So it
ignored the 'start numbering at' setting.

STEPS TO REPRODUCE - TEST 2
1. Create a frame-by-frame animation starting from frame 24 and ending at frame
45 (for example. not starting at 0 or 1)
2. File --> Render Animation
3. Leave 'Start numbering at' at 1 to start output numbering on frame 1
4. Click 'OK' to render
5. Watch result in Windows Explorer: See that the frame numbers aren't starting
at 1, but at frame 24 as the original keyframe number on the timeline. So it
ignored the 'start numbering at' setting.

STEPS TO REPRODUCE - TEST 3
1. Create a frame-by-frame animation starting from frame 24 and ending at frame
45 (for example. not starting at 0 or 1)
2. File --> Render Animation
3. Leave 'Start numbering at' at 2 to start output numbering on frame 2
4. Click 'OK' to render
5. Watch result in Windows Explorer: See that the frame numbers aren't starting
at 2, but at frame 24 as the original keyframe number on the timeline. So it
ignored the 'start numbering at' setting.

OBSERVED RESULT
See above

EXPECTED RESULT
Image sequence to start at given frame number as set in 'start numbering at'

SOFTWARE/OS VERSIONS
Windows:  10
Krita: 5.1.0

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

[krita] [Bug 458862] New: Issues and feature requests regarding animation (timeline / onion skinning)

[Maarten]

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

Bug ID: 458862
   Summary: Issues and feature requests regarding animation
(timeline / onion skinning)
   Product: krita
   Version: 5.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@wigglepixel.nl
  Target Milestone: ---

ISSUES

* Layers aren't synchronized while playing
When playing an animation consisting multiple layers with keyframes these
layers don't synchronise but seem to be individual instances playing
individually at a different speed/refresh rate. This is obviously not what we
want when creating frame by frame animations and makes the preview of
animations unreliable.

* Double onion skins, when just one is requested
Having onion skins turned on for showing oninon skinning on previous frame only
it happens a lot that more onion from-skins are shown. So more than one. When
this happens switching to another frame in the timeline and back again fixes it
(redraws) by showing just the wanted onion skin.

* Sync issues between layers in timeline and layers in layer panel
It happened a few times here now that actions applied to layers shown in the
timeline docker don't match with the same layers in the layers docker causing
wrong layers to be edited. When knowing more about when exactly this happens
I'll let you know.

* Timeline is skipping keyframes
While playing often keyframes are skipped while playing. They aren't only
skipped in the display of the timeline view, but also in the viewport the frame
is not shown. This makes previewing animations unreliable.

(* Glitches in the onion skinning, but already mentioned in
https://bugs.kde.org/show_bug.cgi?id=446506)

--

FEATURE REQUESTS

* Please keep start and end frames fixed
When working with animations it's pretty frustrating to constantly see the
start and end frames of the timeline loop change 'automatically'. I guess this
got automatically changed when adding frames before the current start frame or
after the end frame, but we never want these start and end framenumbers to loop
to automatically change. It's frustrating the workflow now, is prone to errors
and so time consuming when this should be easy to solve: just keep the start
and end framenumbers fixed until we manually change it. if we'd like to have a
different view range we would easily change the framenumbers ourselves for that
single time we'd like to have a different range.

* Please add a checkbox/switch to toggle repeat/loop of the timeline on or off
Often we don't want to preview our animations looped, but there seem to be no
way to turn looping off other than changing the end-frame (which we'd like to
keep the same, as other times we do want to loop the same animation while
previewing)

* Please add a way to cycle onion skinning
When creating looping animations there's no way now to see the onion skin of
the last frame when working on the first frame and visa versa. This is
important to see when creating looping animations as the last frame comes
before the first frame and the first frame comes after the last frame. We
should see the onion skinning of these frames of the 'other side' to be able to
make seamless loops. That's impossible now. We can copy these frames by hand,
but that's tedious and far from an ideal workflow as we need to add frames we
don't want to add, need to apply changes everytime to the other frames etc.

SOFTWARE/OS VERSIONS
Windows:  10
Krita: 5.1.0

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

[krita] [Bug 446506] Onion Skin Artifacts

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 CC||i...@wigglepixel.nl

--- Comment #2 from Maarten  ---
Can confirm this. Happens here in v5.1.0

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

[korganizer] [Bug 437853] New: Google calendar refuses invite sent to different mail address

[Maarten ter Huurne]

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

Bug ID: 437853
   Summary: Google calendar refuses invite sent to different mail
address
   Product: korganizer
   Version: 5.17.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: import/export
  Assignee: kdepim-b...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

SUMMARY

I received an invite as an ICS file on my main mail address, which is not a
GMail address. I wanted to add it to my Google Calendar (different account, but
both configured in Kontact), so I could access it from my Android phone.
KOrganizer reported "1 incidence was imported successfully" in a blue bar at
the bottom of the screen. However, the event wasn't added to the calendar.

STEPS TO REPRODUCE
1. Create an ICS file with a non-Google e-mail address as the attendee.
2. Try to add that event to a Google calendar.

OBSERVED RESULT

In the logging of Akonadi, I found this:

org.kde.kgapi: Bad request, Google replied '
"{\"error\":{\"errors\":[{\"domain\":\"calendar\",\"reason\":\"participantIsNeitherOrganizerNorAttendee\",\"message\":\"The
owner of the calendar must either be the organizer or an attendee of an event
that is imported.\"}],\"code\":400,\"message\":\"The owner of the calendar must
either be the organizer or an attendee of an event that is imported.\"}}" '
org.kde.pim.google: Got error: KGAPI2::EventCreateJob(0x564b09f142f0) "Bad
request."

EXPECTED RESULT

Ideally, KOrganizer would rewrite the attendee field to match the e-mail
address that is tied to the calendar, when the attendee is a different mail
identity of the user.

In any case, KOrganizer should not report a successful import when Google's
server rejected the API call.

SOFTWARE/OS VERSIONS
Linux distro: openSUSE Tumbleweed
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 21.04.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[kmail2] [Bug 404250] dark theme => unreadable mail

[Maarten Billemont]

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

Maarten Billemont  changed:

   What|Removed |Added

 CC||lhun...@lyndir.com

--- Comment #15 from Maarten Billemont  ---
(In reply to Laurent Montel from comment #8)
> So you can't :)
> We can't change dynamically the color from the original mail which forces
> color.

I should like to add that other email clients, such as macOS' Mail appear to
remove background:white styles from the original email so as to make them
compatible with the client's native background.

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

[konsole] [Bug 371776] Konsole crash when opening lots of Konsoles

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from Maarten ter Huurne  ---
I ran `for i in $(seq 0 20); do konsole -e 'sleep 3' &  done` a dozen times and
couldn't trigger any crashes.

I have a different PC and a fresh install of openSUSE compared to 2016 though,
so I don't know if this means the issue was fixed or my new PC is just not able
to reproduce it.

In any case, Konsole hasn't crashed for me in ages while I use it every day. So
I'll close the bug.

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

[konsole] [Bug 89299] prevent paste of newline characters

[Maarten ter Huurne]

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

--- Comment #59 from Maarten ter Huurne  ---
(In reply to Andreas Nordal from comment #58)
> Nobody mentioning bracketed paste?

I had never heard of it until you mentioned it.

I enabled it in ~/.inputrc and now bash indeed waits for an explicit Enter
before executing anything. This is awesome!

Why isn't this enabled by default in shells and/or readline?

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

[akregator] [Bug 414086] Icon for Atom feed ignored

[Maarten ter Huurne]

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

--- Comment #2 from Maarten ter Huurne  ---
Awesome!

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

[akregator] [Bug 414086] Icon for Atom feed ignored

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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

[akregator] [Bug 414086] New: Icon for Atom feed ignored

[Maarten ter Huurne]

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

Bug ID: 414086
   Summary: Icon for Atom feed ignored
   Product: akregator
   Version: 5.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: feed parser
  Assignee: kdepim-b...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

SUMMARY

If I add an Atom feed, the icon at the URL inside  tag is not displayed.

STEPS TO REPRODUCE

1. Add feed: https://nasauber.de/blog/weblog.xml

I borrowed this URL from bug 111507. It looks like the problem described in the
third comment of that bug is still present.

OBSERVED RESULT

A generic icon (globe) is displayed in front of the feed's entry.

When I test with my own feeds, the feed's icon URL is not even fetched from the
web server. However, a fetch of "/favicon.ico" is attempted (result: 404) by
the user agent "Konqueror/5", unlike the feed itself which is fetched by user
agent "Akregator/5.12.3".

EXPECTED RESULT

The feed's icon is displayed in front of the feed's entry.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.1
(available in About System)
KDE Plasma Version: 5.17.2
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.1

ADDITIONAL INFORMATION

Some Atom feeds do display icons for me, but I suspect these are loaded using
the hardcoded "/favicon.ico" URL instead of from the URL in the  tag.

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

[kile] [Bug 290678] syntax highlighting not working in complicated equation environment

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Maarten  ---
Didn't have problems in later versions

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

[k3b] [Bug 263213] DVD ripping stops due to problems with ffmpeg

[Maarten]

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

Maarten  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Maarten  ---
No problems observed in later versions

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

[kmix] [Bug 370650] Crash on session restore

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from Maarten ter Huurne  ---
This issue doesn't happen anymore for me. I don't remember exactly when it
stopped happening though.

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

[ktorrent] [Bug 320305] Crash while running in the background

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Maarten ter Huurne  ---
This crash likely depended on particular network traffic or timing; it's not
something that I can reproduce even if the bug would still be there.

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

[konqueror] [Bug 301937] Crash while editing message in Google Groups

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Maarten ter Huurne  ---
It's likely both khtml and the Google Groups code have changed significantly
since 2012, so I'm not going to bother to try to reproduce this.

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

[kate] [Bug 302096] Crash while deleting lines

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from Maarten ter Huurne  ---
I don't have a way to reproduce it and the backtrace is 6 years old now, so
I'll close it.

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

[Akonadi] [Bug 387393] akonadiserver 17.08.03 crashed during idle

[Maarten ter Huurne]

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

--- Comment #6 from Maarten ter Huurne  ---
Created attachment 114970
  --> https://bugs.kde.org/attachment.cgi?id=114970=edit
New crash information added by DrKonqi

akonadiserver (5.7.3) using Qt 5.9.4

- What I was doing when the application crashed:

I wasn't interacting with akonadi at all when it crashed. It might have been
fetching mail in the background. Kontact was open.

I never had this problem until I few days ago, but now there are two crashes. I
wonder if this is a coincidence or a recent change increased the chance of this
crash occurring. The last system (openSUSE Leap 15) update on 2018-09-12
installed the following packages:

nvidia-gfxG04-kmp-default|390.87_k4.12.14_lp150.11-lp150.10.1|x86_64
nvidia-glG04|390.87-lp150.10.1|x86_64
nvidia-computeG04|390.87-lp150.10.1|x86_64
x11-video-nvidiaG04|390.87-lp150.10.1|x86_64
discover|5.12.6-lp150.2.3.1|x86_64
kde-user-manager|5.12.6-lp150.2.3.1|x86_64
kinfocenter5|5.12.6-lp150.3.3.1|x86_64
kscreen5|5.12.6-lp150.2.3.1|x86_64
kscreenlocker|5.12.6-lp150.2.3.1|x86_64
libKScreenLocker5|5.12.6-lp150.2.3.1|x86_64
libksysguard5|5.12.6-lp150.2.3.1|x86_64
libksysguard5-helper|5.12.6-lp150.2.3.1|x86_64
metatheme-breeze-common|5.12.6-lp150.2.3.1|x86_64
milou5|5.12.6-lp150.2.3.1|x86_64
plasma-nm5|5.12.6-lp150.3.3.1|x86_64
plasma5-addons|5.12.6-lp150.2.3.1|x86_64
plasma5-integration-plugin|5.12.6-lp150.2.3.1|x86_64
discover-lang|5.12.6-lp150.2.3.1|noarch
kde-user-manager-lang|5.12.6-lp150.2.3.1|noarch
kinfocenter5-lang|5.12.6-lp150.3.3.1|noarch
kscreen5-lang|5.12.6-lp150.2.3.1|noarch
kscreenlocker-lang|5.12.6-lp150.2.3.1|noarch
kwin5|5.12.6-lp150.2.3.1|x86_64
libksysguard5-lang|5.12.6-lp150.2.3.1|noarch
gtk3-metatheme-breeze|5.12.6-lp150.2.3.1|noarch
milou5-lang|5.12.6-lp150.2.3.1|noarch
plasma-nm5-lang|5.12.6-lp150.3.3.1|noarch
plasma5-addons-lang|5.12.6-lp150.2.3.1|noarch
plasma5-integration-plugin-lang|5.12.6-lp150.2.3.1|noarch
kwin5-lang|5.12.6-lp150.2.3.1|noarch
plasma5-workspace-libs|5.12.6-lp150.2.3.1|x86_64
ksysguard5|5.12.6-lp150.2.3.1|x86_64
gtk2-metatheme-breeze|5.12.6-lp150.2.3.1|noarch
plasma-nm5-pptp|5.12.6-lp150.3.3.1|x86_64
plasma-nm5-openvpn|5.12.6-lp150.3.3.1|x86_64
plasma-nm5-openconnect|5.12.6-lp150.3.3.1|x86_64
plasma5-workspace|5.12.6-lp150.2.3.1|x86_64
khotkeys5|5.12.6-lp150.2.3.1|x86_64
ksysguard5-lang|5.12.6-lp150.2.3.1|noarch
plasma5-workspace-lang|5.12.6-lp150.2.3.1|noarch
khotkeys5-lang|5.12.6-lp150.2.3.1|noarch
plasma5-desktop|5.12.6-lp150.3.3.1|x86_64
plasma5-desktop-lang|5.12.6-lp150.3.3.1|noarch
plasma5-session|5.12.6-lp150.2.3.1|noarch
plasma5-session-wayland|5.12.6-lp150.2.3.1|noarch

While there are several KDE packages in that list, I don't think akonadiserver
would depends on the listed packages.

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7f30d3ea26c1 in __GI_abort () at abort.c:79
[...]
#9  0x7f30d3eeac43 in malloc_printerr (action=,
str=0x7f30d3fed5d8 "double free or corruption (!prev)", ptr=,
ar_ptr=) at malloc.c:5428
#10 0x7f30d3eec549 in _int_free (av=av@entry=0x7f30d421fc20 ,
p=, p@entry=0x564dce831ce0, have_lock=have_lock@entry=1) at
malloc.c:4170
#11 0x7f30d3eef250 in _int_realloc (av=av@entry=0x7f30d421fc20
, oldp=oldp@entry=0x564dce831ce0, oldsize=oldsize@entry=4128,
nb=8208) at malloc.c:4676

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

[drkonqi] [Bug 248807] Report with a long backtrace can't be sent (bugzilla 65k limit per comment)

[Maarten ter Huurne]

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

--- Comment #15 from Maarten ter Huurne  ---
(In reply to Alexander Mentyu from comment #14)
> Possible solutions:
> 1. Add option to paste whole backtrace in paste.kde.org service and insert
> link into description.
> 2. Add option to paste whole backtrace in attachment.
> 3. Paste beginning of backtrace in attachment/paste.kde.org and rest with
> max available characters in description/comment.

A variation of option 3:

4. Put the backtrace of the crashed thread in the comment and attach the
backtrace of all threads.

I think in most cases only the backtrace of the thread that actually crashed is
relevant, but for the few cases where other threads are relevant, it would be
nice to have access to the full backtrace dump.

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

[Akonadi] [Bug 398571] akonadiserver assert on realloc

[Maarten ter Huurne]

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

--- Comment #1 from Maarten ter Huurne  ---
Possible duplicate of bug 387393.

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

[Akonadi] [Bug 398571] New: akonadiserver assert on realloc

[Maarten ter Huurne]

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

Bug ID: 398571
   Summary: akonadiserver assert on realloc
   Product: Akonadi
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

Created attachment 114929
  --> https://bugs.kde.org/attachment.cgi?id=114929=edit
crash report from drkonqi

I had Kontact open with the KMail module enabled, but Akregator was the
currently focused module. I wasn't interacting with Kontact at all, in fact I
wasn't even behind the PC when the crash happened.

At first glance this backtrace looks a lot like the one from the bug I marked
as possible duplicate, but I'll leave the final judgement on that to someone
more familiar with the code.

The system wasn't low on memory, so that wouldn't be a reason for realloc to
fail.

(drkonqi failed to submit this bug because the backtrace took the comments over
64 kB and bugzilla refused to accept the report; please fix this as it's been a
pain for years and is probably causing you to miss out on useful bug reports)

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

[Akonadi] [Bug 387393] akonadiserver 17.08.03 crashed during idle

[Maarten ter Huurne]

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

Maarten ter Huurne  changed:

   What|Removed |Added

 CC||maar...@treewalker.org

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

[systemsettings] [Bug 344588] 'Regional Setting - Formats - Region' setting behaves unexpected

[Maarten ter Huurne]

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

--- Comment #12 from Maarten ter Huurne  ---
The LANG environment variable assumes that the user will always want the
application language and the regional settings to match. This assumption is
wrong for people who prefer application language to be English and regional
settings from their own country. In particular computer-savvy people who know
all the terminology in English but may find the translated terminology
confusing. My estimate would be that a lot of KDE users who are not native
English speakers fall into this category.

So please... don't set LANG.

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

[ktorrent] [Bug 388383] New: KTorrent crashes when changing path to store the data

[Maarten Bezemer]

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

Bug ID: 388383
   Summary: KTorrent crashes when changing path to store the data
   Product: ktorrent
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: maarten.beze...@gmail.com
  Target Milestone: ---

Application: ktorrent (5.1.0)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.9-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
Suddenly KTorrent started to crash when I edit the path where to store the data
(after opening a magnet link).

Note that I manually edit tha path using the input field (as this much faster
due to the auto-complete using the filesystem).

A second try, after restarting KTorrent, also failed.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7faa0b136800 (LWP 3343))]

Thread 25 (Thread 0x7fa9a54da700 (LWP 3389)):
#0  0x7faa0444ce29 in syscall () at /usr/lib/libc.so.6
#1  0x7faa03aa75dd in  () at /usr/lib/libglib-2.0.so.0
#2  0x7faa03a3354f in  () at /usr/lib/libglib-2.0.so.0
#3  0x7faa041441b8 in __nptl_deallocate_tsd.part.5 () at
/usr/lib/libpthread.so.0
#4  0x7faa041451dd in start_thread () at /usr/lib/libpthread.so.0
#5  0x7faa0445242f in clone () at /usr/lib/libc.so.6

Thread 24 (Thread 0x7fa9a7fff700 (LWP 3370)):
#0  0x7faa0414b38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7faa050af00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7faa09bcfbcc in  () at /usr/lib/libKF5Torrent.so.6
#3  0x7faa050adb2d in  () at /usr/lib/libQt5Core.so.5
#4  0x7faa0414508a in start_thread () at /usr/lib/libpthread.so.0
#5  0x7faa0445242f in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7fa9b49f4700 (LWP 3369)):
#0  0x7faa050a4dd9 in QMutex::unlock() () at /usr/lib/libQt5Core.so.5
#1  0x7faa09bc5a87 in  () at /usr/lib/libKF5Torrent.so.6
#2  0x7faa09bcba92 in  () at /usr/lib/libKF5Torrent.so.6
#3  0x7faa09bcbb66 in  () at /usr/lib/libKF5Torrent.so.6
#4  0x7faa09bcc449 in  () at /usr/lib/libKF5Torrent.so.6
#5  0x7faa050adb2d in  () at /usr/lib/libQt5Core.so.5
#6  0x7faa0414508a in start_thread () at /usr/lib/libpthread.so.0
#7  0x7faa0445242f in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7fa9b51f5700 (LWP 3368)):
#0  0x7faa0444ce29 in syscall () at /usr/lib/libc.so.6
#1  0x7faa050a4af6 in QBasicMutex::lockInternal() () at
/usr/lib/libQt5Core.so.5
#2  0x7faa050a4e54 in  () at /usr/lib/libQt5Core.so.5
#3  0x7faa09bcc22e in  () at /usr/lib/libKF5Torrent.so.6
#4  0x7faa09bcc449 in  () at /usr/lib/libKF5Torrent.so.6
#5  0x7faa050adb2d in  () at /usr/lib/libQt5Core.so.5
#6  0x7faa0414508a in start_thread () at /usr/lib/libpthread.so.0
#7  0x7faa0445242f in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7fa9b63bb700 (LWP 3365)):
#0  0x7faa0444ce29 in syscall () at /usr/lib/libc.so.6
#1  0x7faa03aa75dd in  () at /usr/lib/libglib-2.0.so.0
#2  0x7faa03a3354f in  () at /usr/lib/libglib-2.0.so.0
#3  0x7faa041441b8 in __nptl_deallocate_tsd.part.5 () at
/usr/lib/libpthread.so.0
#4  0x7faa041451dd in start_thread () at /usr/lib/libpthread.so.0
#5  0x7faa0445242f in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7fa9b6ffd700 (LWP 3364)):
#0  0x7faa0444ce29 in syscall () at /usr/lib/libc.so.6
#1  0x7faa03aa75dd in  () at /usr/lib/libglib-2.0.so.0
#2  0x7faa03a3354f in  () at /usr/lib/libglib-2.0.so.0
#3  0x7faa041441b8 in __nptl_deallocate_tsd.part.5 () at
/usr/lib/libpthread.so.0
#4  0x7faa041451dd in start_thread () at /usr/lib/libpthread.so.0
#5  0x7faa0445242f in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fa9b77fe700 (LWP 3363)):
#0  0x7faa0444ce29 in syscall () at /usr/lib/libc.so.6
#1  0x7faa03aa75dd in  () at /usr/lib/libglib-2.0.so.0
#2  0x7faa03a3354f in  () at /usr/lib/libglib-2.0.so.0
#3  0x7faa041441b8 in __nptl_deallocate_tsd.part.5 () at
/usr/lib/libpthread.so.0
#4  0x7faa041451dd in start_thread () at /usr/lib/libpthread.so.0
#5  0x7faa0445242f in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7fa9b7fff700 (LWP 3362)):
#0  0x7faa0414b6cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7faa050aeec1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7faa050aad91 in  () at /usr/lib/libQt5Core.so.5
#3  0x7faa050adb2d in  () at /usr/lib/libQt5Core.so.5
#4  0x7faa0414508a in start_thread () at /usr/lib/libpthread.so.0
#5  0x7faa0445242f in clone () at 

[frameworks-kio] [Bug 374420] Various kioslaves do not write correct dates

[Maarten ter Huurne]

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

Maarten ter Huurne <maar...@treewalker.org> changed:

   What|Removed |Added

 CC||maar...@treewalker.org

--- Comment #2 from Maarten ter Huurne <maar...@treewalker.org> ---
I'm seeing 2106-02-07 07:28 pop up a lot lately, after switching Konqueror and
KDE PIM to KDE5. For example, files downloaded from Konqueror and some entries
in my Akregator feeds.

I'm using KDE Frameworks 5.38.0 from openSUSE.

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

[kate] [Bug 385117] Python indentation indents too often since recent update

[Maarten ter Huurne]

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

--- Comment #3 from Maarten ter Huurne <maar...@treewalker.org> ---
I did test that exact fragment in Kate when I filed the bug. However, when I
try to reproduce it now, Kate doesn't indent the third line. So there must be
some yet unknown factor that makes this bad indentation trigger.

I created the fragment inside the larger source file that I was editing at that
moment, so it is possible either the context is relevant or some unseen state
in Kate matters.

The indent happened when I typed the '+', so not one of the letters mentioned
in the other bug.

I expect the problem will occur again, since it wasn't the first time it
happened when I filed the bug. When it does, I'll try to figure out what is
relevant about the context or state to be able to reproduce this.

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

[konqueror] [Bug 385119] New: Focus location bar on startup

[Maarten ter Huurne]

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

Bug ID: 385119
   Summary: Focus location bar on startup
   Product: konqueror
   Version: 5.0.97
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

When Konqueror 4.x opened a new window, I could immediately start typing a URL
or web shortcut in the location bar. With Konqueror 5.x, I have to hit F6
first, to put the input focus on the location bar. Given how often I open a
browser window on the average day, it would really help me if the locaton bar
would be automatically focused again. Maybe not for all URLs, but at least for
"about:" and "about:blank".

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

[kate] [Bug 385117] New: Python indentation indents too often since recent update

[Maarten ter Huurne]

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

Bug ID: 385117
   Summary: Python indentation indents too often since recent
update
   Product: kate
   Version: 17.08.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: indentation
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

I've been using Kate with Python projects for a long time, but since a recent
update it hasn't been functioning well.

The problem is that it will often indent a line to line up with the line above
it. For languages like C this would be desired, but since in Python the end of
a block is identified by the indentation level decreasing, an editor should
never change the indentation of an existing line, since it changes the meaning
of the code being edited.

For example, if I start with this code fragment:

if x == 0:
foo()
y = x

and I then add "+ 1" to the third line, Kate will indent it like this:

if x == 0:
foo()
y = x + 1

which incorrectly pulls the third line into the if's body.

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

[Akonadi] [Bug 383003] New: Crash in mail filter agent

[Maarten ter Huurne]

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

Bug ID: 383003
   Summary: Crash in mail filter agent
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Mail Filter Agent
  Assignee: kdepim-b...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

Application: akonadi_mailfilter_agent (4.14)
KDE Platform Version: 4.14.25
Qt Version: 4.8.6
Operating System: Linux 4.4.73-18.17-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:

I was going through my spam box and found a few mails that shouldn't have been
flagged as spam. So I created new filter rules to make sure mails from those
senders would never be put in the spam box. Then I applied the filters to them
using Ctrl-J.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Mail Filter Agent (akonadi_mailfilter_agent), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f52065e3d27 in MailCommon::SearchPattern::asString() const
(this=0x699f058) at /usr/include/QtCore/qlist.h:102
#7  0x7f52065e3d27 in MailCommon::SearchPattern::asString() const
(this=0x699f058) at /usr/include/QtCore/qlist.h:272
#8  0x7f52065e3d27 in MailCommon::SearchPattern::asString() const
(this=0x699f058) at
/usr/src/debug/kdepim-4.14.10/mailcommon/search/searchpattern.cpp:290
#9  0x0040fbe0 in FilterManager::Private::isMatching(Akonadi::Item
const&, MailCommon::MailFilter const*) (this=, item=...,
filter=filter@entry=0x699f050) at
/usr/src/debug/kdepim-4.14.10/agents/mailfilteragent/filtermanager.cpp:245
#10 0x004129aa in FilterManager::process(QList
const&, Akonadi::Item const&, bool, FilterManager::FilterSet, bool, QString
const&) (this=0xebeda0, mailFilters=..., item=...,
needsFullPayload=needsFullPayload@entry=true,
set=set@entry=FilterManager::Explicit, account=account@entry=false,
accountId=...) at
/usr/src/debug/kdepim-4.14.10/agents/mailfilteragent/filtermanager.cpp:508
#11 0x0041301d in
FilterManager::Private::slotItemsFetchedForFilter(QList const&)
(this=0xeef850, items=...) at
/usr/src/debug/kdepim-4.14.10/agents/mailfilteragent/filtermanager.cpp:131
#12 0x004152ad in FilterManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _id=,
_a=, _c=) at
/usr/src/debug/kdepim-4.14.10/build/agents/mailfilteragent/moc_filtermanager.cpp:76
#13 0x7f5205ee50ea in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#14 0x7f5204d04122 in
Akonadi::ItemFetchJob::itemsReceived(QList const&)
(this=this@entry=0x45201c0, _t1=...) at
/usr/src/debug/kdepimlibs-4.14.10/build/akonadi/moc_itemfetchjob.cpp:114
#15 0x7f5204d059bb in Akonadi::ItemFetchJobPrivate::aboutToFinish()
(this=) at
/usr/src/debug/kdepimlibs-4.14.10/akonadi/itemfetchjob.cpp:79
#16 0x7f5204d059bb in Akonadi::ItemFetchJobPrivate::aboutToFinish()
(this=) at
/usr/src/debug/kdepimlibs-4.14.10/akonadi/itemfetchjob.cpp:69
#17 0x7f5204d1801b in Akonadi::JobPrivate::delayedEmitResult()
(this=) at /usr/src/debug/kdepimlibs-4.14.10/akonadi/job.cpp:164
#18 0x7f5205ee948e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#19 0x7f5202e9a6fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#20 0x7f5202ea0c3d in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#21 0x7f5204076e3a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#22 0x7f5205ed117d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#23 0x7f5205ed444d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#24 0x7f5205efe7ee in  () at /usr/lib64/libQtCore.so.4
#25 0x7f51feeef134 in g_main_context_dispatch (context=0xb94240) at
gmain.c:3154
#26 0x7f51feeef134 in g_main_context_dispatch
(context=context@entry=0xb94240) at gmain.c:3769
#27 0x7f51feeef388 in g_main_context_iterate
(context=context@entry=0xb94240, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3840
#28 0x7f51feeef42c in g_main_context_iteration (context=0xb94240,
may_block=1) at gmain.c:3901
#29 0x7f5205efdfae in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#30 0x7f5202f37606 in  () at /usr/lib64/libQtGui.so.4
#31 0x7f5205ecfd3f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#32 0x7f5205ed0035 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#33 0x7f5205ed5489 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#34 0x7f5204c586a3 in 

[kontact] [Bug 266673] Crash after clicking systray icon

[Maarten ter Huurne]

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

Maarten ter Huurne <maar...@treewalker.org> changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #10 from Maarten ter Huurne <maar...@treewalker.org> ---
This is not a bug I'd be able to reproduce: it's something that happened one
time and I submitted it in the hope the backtrace would be useful. But by now
the code would have changed so much that investigating the backtrace is
probably not worth the effort. I'll close the bug.

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

[kmix] [Bug 371804] New: Crash when processing DBUS message

[Maarten ter Huurne]

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

Bug ID: 371804
   Summary: Crash when processing DBUS message
   Product: kmix
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

Application: kmix (4.6)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I was scrolling in a web page in Konqueror, not interacting with kmix at all.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMix (kmix), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f44672a1800 (LWP 12269))]

Thread 2 (Thread 0x7f445377c700 (LWP 12270)):
#0  0x7f4466b6cbfd in poll () from /lib64/libc.so.6
#1  0x7f445df1de64 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f444c010950, timeout=-1, context=0x7f444c001b00) at gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7f444c001b00,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3803
#3  0x7f445df1df7c in g_main_context_iteration (context=0x7f444c001b00,
may_block=1) at gmain.c:3869
#4  0x7f44627a6f4b in QEventDispatcherGlib::processEvents
(this=0x7f444c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f446275689b in QEventLoop::exec (this=this@entry=0x7f445377bda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7f446259d02a in QThread::exec (this=this@entry=0x7f4463d7ad00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#7  0x7f4463b13aa5 in QDBusConnectionManager::run (this=0x7f4463d7ad00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:196
#8  0x7f44625a1859 in QThreadPrivate::start (arg=0x7f4463d7ad00 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
#9  0x7f445eabe0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f4466b7502d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f44672a1800 (LWP 12269)):
[KCrash Handler]
#6  std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/4.8/bits/atomic_base.h:496
#7  QAtomicOps::load (_q_value=...) at
../../src/corelib/arch/qatomic_cxx11.h:103
#8  QBasicAtomicInteger::load (this=0x0) at
../../src/corelib/thread/qbasicatomic.h:99
#9  QtPrivate::RefCount::deref (this=0x0) at
../../src/corelib/tools/qrefcount.h:66
#10 QString::~QString (this=0x7f444c0531e8, __in_chrg=) at
../../src/corelib/tools/qstring.h:1075
#11 QList::node_destruct (this=, to=0x7f444c0531e8,
from=0x7f444c013808) at ../../src/corelib/tools/qlist.h:492
#12 QList::dealloc (this=, data=0x7f444c0137c0) at
../../src/corelib/tools/qlist.h:861
#13 QList::~QList (this=, __in_chrg=) at
../../src/corelib/tools/qlist.h:823
#14 0x7f446279bf35 in QStringList::~QStringList (this=0x7f444c0008c0,
__in_chrg=) at ../../src/corelib/tools/qstringlist.h:100
#15 v_clear (d=0x7f444c0008c0) at
../../src/corelib/kernel/qvariant_p.h:175
#16 QVariantDestructor<(anonymous
namespace)::CoreTypesFilter>::FilteredDestructor::FilteredDestructor (d=0x7f444c0008c0, this=) at
../../src/corelib/kernel/qvariant_p.h:380
#17 QVariantDestructor<(anonymous
namespace)::CoreTypesFilter>::delegate (this=)
at ../../src/corelib/kernel/qvariant_p.h:406
#18 QMetaTypeSwitcher::switcher > (data=0x0, type=,
logic=) at ../../src/corelib/kernel/qmetatypeswitcher_p.h:74
#19 (anonymous namespace)::clear (d=0x7f444c0008c0) at kernel/qvariant.cpp:119
#20 0x7f4463b1636c in QList::node_destruct (this=,
to=0x7f444c00e2d8, from=0x7f444c00e2d0) at ../../src/corelib/tools/qlist.h:490
#21 QList::dealloc (data=0x7f444c00e2c0, this=) at
../../src/corelib/tools/qlist.h:861
#22 0x7f4463b2a96b in QDBusMessage::~QDBusMessage (this=,
__in_chrg=) at qdbusmessage.cpp:571
#23 0x7f4463b25f9c in QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent
(this=0x7f444c013710, __in_chrg=) at qdbusintegrator_p.h:103
#24 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x7f444c013710,
__in_chrg=) at qdbusintegrator_p.h:103
#25 0x7f446275a62c in QScopedPointerDeleter::cleanup
(pointer=0x7f444c013710) at ../../src/corelib/tools/qscopedpointer.h:60
#26 QScopedPointer::~QScopedPointer
(this=, __in_chrg=) at
../../src/corelib/tools/qscopedpointer.h:107
#27 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x84bcb0) at

[konsole] [Bug 369050] Konsole crashs randomly.

[Maarten ter Huurne]

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

--- Comment #16 from Maarten ter Huurne <maar...@treewalker.org> ---
I haven't found a reliable way yet to reproduce the crash, but I did observe
some things that might be useful.

One time Konsole crashed very shortly after a new e-mail came in and the new
mail notification was displayed.

If I keep opening lots of Konsole instances via a button in the panel, at some
point they all crash at the same time. This seems to happen more often if I
don't allow Konsole to be grouped in the task bar, but I'm not sure if this is
a rule or a coincidence.

I have been monitoring the DBUS session and system bus to see if there is any
particular type of message that triggers this crash. There was no activity on
the system bus when Konsole crashed, but lots of activity on the session bus,
so I wasn't able to pin-point any particular message.

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

[plasmashell] [Bug 371777] New: Memory leak when closing applications?

[Maarten ter Huurne]

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

Bug ID: 371777
   Summary: Memory leak when closing applications?
   Product: plasmashell
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: maar...@treewalker.org
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 101847
  --> https://bugs.kde.org/attachment.cgi?id=101847=edit
cat /proc/`pidof plasmashell`/smaps

To reproduce:
- allow Konsole instances to be grouped
- open 100 (or any other big number) instances of Konsole
- open top or systemmonitor and sort by memory size
- close all Konsole instances by closing the group
- watch the memory consumption of plasmashell rise as the Konsole instances
exit

After repeating this a few times, I have a plasmashell instance that takes up
1.4 GB of memory. I'll attach the output of "cat /proc/`pidof
plasmashell`/smaps". It shows 1 GB of memory is occupied by the heap.

The strange thing is that the memory consumption rises when closing Konsole
instances, not when opening them.

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

[drkonqi] [Bug 366004] drkonqi crash when I cancel installation of debug packages

[Maarten ter Huurne]

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

Maarten ter Huurne <maar...@treewalker.org> changed:

   What|Removed |Added

 CC||maar...@treewalker.org

--- Comment #4 from Maarten ter Huurne <maar...@treewalker.org> ---
I just had a crash of drkonqi after installation of debug packages seemed to
hang and I pressed the Cancel button. It told me in a pop-up that the
installation had failed, then immediately after I closed the pop-up it crashed.

I'm running drkonqi 5.8.2 on openSUSE 42.1 from the OBS.

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

[konsole] [Bug 371776] Konsole crash when opening lots of Konsoles

[Maarten ter Huurne]

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

--- Comment #1 from Maarten ter Huurne <maar...@treewalker.org> ---
Note that for this particular crash, only one Konsole instance crashed, not
dozens of them at the same time. So it may not be the same bug after all.

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

[konsole] [Bug 371776] New: Konsole crash when opening lots of Konsoles

[Maarten ter Huurne]

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

Bug ID: 371776
   Summary: Konsole crash when opening lots of Konsoles
   Product: konsole
   Version: 15.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: maar...@treewalker.org
  Target Milestone: ---

Application: konsole (15.12.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I was trying to find a way to reproduce bug 369050. I noticed that when I keep
starting lots of Konsole instances (between 10 and 100), eventually they all
crash during the startup of another instance.

However, the backtrace from this crash is different from bug 369050; there
seems to be a heap corruption (that's the only way I can explain a crash on
malloc, since the system wasn't out of memory). So I don't know whether heap
corruption is the root cause for both crashes and just manifests in different
ways, or whether it is two separate bugs.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff5ca52f800 (LWP 18579))]

Thread 2 (Thread 0x7ff5b6a3c700 (LWP 18580)):
#0  QMutex::lock (this=this@entry=0x21688d0) at thread/qmutex.cpp:225
#1  0x7ff5c64afe75 in QMutexLocker::QMutexLocker (m=0x21688d0,
this=) at ../../src/corelib/thread/qmutex.h:137
#2  QThreadData::canWaitLocked (this=0x21688a0) at
../../src/corelib/thread/qthread_p.h:253
#3  postEventSourcePrepare (s=0x7ff5b0003600,
timeout=timeout@entry=0x7ff5b6a3bbe4) at kernel/qeventdispatcher_glib.cpp:259
#4  0x7ff5bf2f34ad in g_main_context_prepare
(context=context@entry=0x7ff5b0001b00, priority=priority@entry=0x7ff5b6a3bc68)
at gmain.c:3410
#5  0x7ff5bf2f3d80 in g_main_context_iterate
(context=context@entry=0x7ff5b0001b00, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3788
#6  0x7ff5bf2f3f7c in g_main_context_iteration (context=0x7ff5b0001b00,
may_block=1) at gmain.c:3869
#7  0x7ff5c64aff4b in QEventDispatcherGlib::processEvents
(this=0x7ff5b8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#8  0x7ff5c645f89b in QEventLoop::exec (this=this@entry=0x7ff5b6a3bda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#9  0x7ff5c62a602a in QThread::exec (this=this@entry=0x7ff5c48e4d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#10 0x7ff5c467daa5 in QDBusConnectionManager::run (this=0x7ff5c48e4d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:196
#11 0x7ff5c62aa859 in QThreadPrivate::start (arg=0x7ff5c48e4d00 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
#12 0x7ff5c0fcd0a4 in start_thread () from /lib64/libpthread.so.0
#13 0x7ff5c9e7502d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ff5ca52f800 (LWP 18579)):
[KCrash Handler]
#6  0x7ff5c9dc50c7 in raise () from /lib64/libc.so.6
#7  0x7ff5c9dc6478 in abort () from /lib64/libc.so.6
#8  0x7ff5c9e02784 in __libc_message () from /lib64/libc.so.6
#9  0x7ff5c9e08026 in malloc_printerr () from /lib64/libc.so.6
#10 0x7ff5c9e082e2 in malloc_consolidate () from /lib64/libc.so.6
#11 0x7ff5c9e08cfb in _int_free () from /lib64/libc.so.6
#12 0x7ff5c646362c in QScopedPointerDeleter::cleanup
(pointer=0x7ff5b000d000) at ../../src/corelib/tools/qscopedpointer.h:60
#13 QScopedPointer::~QScopedPointer
(this=, __in_chrg=) at
../../src/corelib/tools/qscopedpointer.h:107
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x2153770) at
kernel/qcoreapplication.cpp:1646
#15 0x7ff5c6463b68 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1503
#16 0x7ff5c64b06e3 in postEventSourceDispatch (s=0x21caff0) at
kernel/qeventdispatcher_glib.cpp:276
#17 0x7ff5bf2f3c84 in g_main_dispatch (context=0x7ff5b0002450) at
gmain.c:3122
#18 g_main_context_dispatch (context=context@entry=0x7ff5b0002450) at
gmain.c:3737
#19 0x7ff5bf2f3ed8 in g_main_context_iterate
(context=context@entry=0x7ff5b0002450, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3808
#20 0x7ff5bf2f3f7c in g_main_context_iteration (context=0x7ff5b0002450,
may_block=1) at gmain.c:3869
#21 0x7ff5c64aff2c in QEventDispatcherGlib::processEvents (this=0x216c0c0,
flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7ff5c645f89b in 

[konsole] [Bug 369050] Konsole crashs randomly.

[Maarten ter Huurne via KDE Bugzilla]

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

Maarten ter Huurne <maar...@treewalker.org> changed:

   What|Removed |Added

 CC||maar...@treewalker.org

--- Comment #2 from Maarten ter Huurne <maar...@treewalker.org> ---
I had a crash of Konsole today with a very similar backtrace. However, I had
seen that backtrace before, when kmix crashed, which I reported as bug 370650.
So I think it's a problem in a library rather than in Konsole itself, but I
don't know which library to file it on.

Application: konsole (15.12.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

Thread 1 (Thread 0x7ff55aef1800 (LWP 2888)):
[KCrash Handler]
#6  0x7ff55a7870c7 in raise () from /lib64/libc.so.6
#7  0x7ff55a788478 in abort () from /lib64/libc.so.6
#8  0x7ff556c57c7e in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1680
#9  QMessageLogger::fatal (this=this@entry=0x7ffe718dfcb0,
msg=msg@entry=0x7ff5550907b0 "Internal error: got invalid meta type %d (%s)
when trying to convert to meta type %d (%s)") at global/qlogging.cpp:793
#10 0x7ff5550497f4 in QDBusConnectionPrivate::deliverCall
(this=0x7ff5400039c0, object=0x2562680, msg=..., metaTypes=..., slotIdx=11) at
qdbusintegrator.cpp:948
#11 0x7ff556e4cdc6 in QObject::event (this=0x2562680, e=) at
kernel/qobject.cpp:1263
#12 0x7ff557adaa9c in QApplicationPrivate::notify_helper (this=, receiver=0x2562680, e=0x7ff54000c230) at kernel/qapplication.cpp:3799
#13 0x7ff557ae1a20 in QApplication::notify (this=0x7ffe718e0470,
receiver=0x2562680, e=0x7ff54000c230) at kernel/qapplication.cpp:3556
#14 0x7ff556e235c5 in QCoreApplication::notifyInternal2
(receiver=0x2562680, event=event@entry=0x7ff54000c230) at
kernel/qcoreapplication.cpp:988
#15 0x7ff556e25623 in QCoreApplication::sendEvent (event=0x7ff54000c230,
receiver=) at kernel/qcoreapplication.h:231
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x2217eb0) at
kernel/qcoreapplication.cpp:1649
#17 0x7ff556e25b68 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1503
#18 0x7ff556e726e3 in postEventSourceDispatch (s=0x229c3c0) at
kernel/qeventdispatcher_glib.cpp:276
#19 0x7ff54fcb5c84 in g_main_dispatch (context=0x7ff540002450) at
gmain.c:3122
#20 g_main_context_dispatch (context=context@entry=0x7ff540002450) at
gmain.c:3737
#21 0x7ff54fcb5ed8 in g_main_context_iterate
(context=context@entry=0x7ff540002450, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3808
#22 0x7ff54fcb5f7c in g_main_context_iteration (context=0x7ff540002450,
may_block=1) at gmain.c:3869
#23 0x7ff556e71f2c in QEventDispatcherGlib::processEvents (this=0x222df80,
flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x7ff556e2189b in QEventLoop::exec (this=this@entry=0x7ffe718e0330,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#25 0x7ff556e29696 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1261
#26 0x7ff55ab22e87 in kdemain () from /usr/lib64/libkdeinit5_konsole.so
#27 0x7ff55a773b25 in __libc_start_main () from /lib64/libc.so.6
#28 0x004007ee in _start ()

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

[kmix] [Bug 370650] Crash on session restore

[Maarten ter Huurne via KDE Bugzilla]

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

--- Comment #6 from Maarten ter Huurne <maar...@treewalker.org> ---
I had a crash of Konsole with a very similar backtrace (also "Internal error:
got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") and
found bug 369050, which reports what looks like the same problem. So I think
it's a bug in a library rather than the application, but I don't know which
package it should be filed on.

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

[kmix] [Bug 370650] Crash on session restore

[Maarten ter Huurne via KDE Bugzilla]

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

--- Comment #4 from Maarten ter Huurne <maar...@treewalker.org> ---
(In reply to Jeff Hodd from comment #3)
> Please let me know if this should be filed as a new bug for korgac vs. kmix.
> It's certainly very possible that the issue is related to session management
> and is not necessarily application-specific.

Looking at the backtraces, I think it's a different issue: the cause of the
crash is different (abort vs segfault) and the functions on the stack are
different as well (event vs disconnect). So please open a separate bug report
for it.

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

[kmix] [Bug 370650] New: Crash on session restore

[Maarten ter Huurne via KDE Bugzilla]

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

Bug ID: 370650
   Summary: Crash on session restore
   Product: kmix
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: maar...@treewalker.org

Application: kmix (4.6)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I have kmix running all the time. In the past this meant that it would get
automatically started as part of the session restore. However, since a few
months, kmix won't restore for some reason. Today I noticed an icon that
indicated that kmix had crashed. I think it may also have crashed those other
times it didn't start, but either I didn't notice or crash reporting for system
tray apps didn't exist or work back then.

I didn't interact with kmix in any way during the session restore. For example,
I didn't press any media keys like volume +/- on my keyboard.

The crash can be reproduced every time.

-- Backtrace:
Application: KMix (kmix), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0b44765800 (LWP 2535))]

Thread 3 (Thread 0x7f0b297eb700 (LWP 2537)):
#0  0x7f0b44030bfd in poll () from /lib64/libc.so.6
#1  0x7f0b3a1b8422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f0b3a1ba00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f0b2bd4e469 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f0b3fa65859 in QThreadPrivate::start (arg=0xaea0d0) at
thread/qthread_unix.cpp:344
#5  0x7f0b3bf820a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f0b4403902d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f0b30c40700 (LWP 2536)):
#0  0x7f0b4402cccd in read () from /lib64/libc.so.6
#1  0x7f0b3562b073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.44
#2  0x7f0b3b422b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f0b3b3e1999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f0b3b3e1df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f0b3b3e1f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f0b3fc6af4b in QEventDispatcherGlib::processEvents
(this=0x7f0b2c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f0b3fc1a89b in QEventLoop::exec (this=this@entry=0x7f0b30c3fda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#8  0x7f0b3fa6102a in QThread::exec (this=this@entry=0x7f0b4123ed00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#9  0x7f0b40fd7aa5 in QDBusConnectionManager::run (this=0x7f0b4123ed00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:196
#10 0x7f0b3fa65859 in QThreadPrivate::start (arg=0x7f0b4123ed00 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
#11 0x7f0b3bf820a4 in start_thread () from /lib64/libpthread.so.0
#12 0x7f0b4403902d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0b44765800 (LWP 2535)):
[KCrash Handler]
#6  0x7f0b43f890c7 in raise () from /lib64/libc.so.6
#7  0x7f0b43f8a478 in abort () from /lib64/libc.so.6
#8  0x7f0b3fa50c7e in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1680
#9  QMessageLogger::fatal (this=this@entry=0x7fff5f39f0c0,
msg=msg@entry=0x7f0b410287b0 "Internal error: got invalid meta type %d (%s)
when trying to convert to meta type %d (%s)") at global/qlogging.cpp:793
#10 0x7f0b40fe17f4 in QDBusConnectionPrivate::deliverCall
(this=0x7f0b2c0039c0, object=0xea5830, msg=..., metaTypes=..., slotIdx=10) at
qdbusintegrator.cpp:948
#11 0x7f0b3fc45dc6 in QObject::event (this=0xea5830, e=) at
kernel/qobject.cpp:1263
#12 0x7f0b408d3a9c in QApplicationPrivate::notify_helper (this=, receiver=0xea5830, e=0x7f0b2c015e00) at kernel/qapplication.cpp:3799
#13 0x7f0b408daa20 in QApplication::notify (this=0xab2010,
receiver=0xea5830, e=0x7f0b2c015e00) at kernel/qapplication.cpp:3556
#14 0x7f0b3fc1c5c5 in QCoreApplication::notifyInternal2 (receiver=0xea5830,
event=event@entry=0x7f0b2c015e00) at kernel/qcoreapplication.cpp:988
#15 0x7f0b3fc1e623 in QCoreApplication::sendEvent (event=0x7f0b2c015e00,
receiver=) at kernel/qcoreapplication.h:231
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0xa9e470) at
kernel/qcoreapplication.cpp:1649
#17 0x7f0b3fc1eb68 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1503
#18 0x7f0b3fc6b6e3 in 

[konqueror] [Bug 361385] Konqueror crash using host libthread_db library "/lib64/libthread_db.so.1"

[Maarten ter Huurne via KDE Bugzilla]

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

Maarten ter Huurne <maar...@treewalker.org> changed:

   What|Removed |Added

 CC||maar...@treewalker.org

--- Comment #1 from Maarten ter Huurne <maar...@treewalker.org> ---
I had a very similar problem. It didn't happen if I started konqueror with an
empty home directory, so I reduced the home dir contents until I found the
culprit: ~/.cache/gstreamer-1.0/registry.x86_64.bin. You could try to remove
that file and see if it solves the problem for you as well.

For me the problem started happening after I updated gstreamer, using packages
from Packman instead of the openSUSE project. So I don't know if the problem is
the new version or that the gstreamer build was configured differently, but it
might be one of those two.

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

[systemsettings] [Bug 344588] 'Regional Setting - Formats - Region' setting behaves unexpected

[Maarten ter Huurne via KDE Bugzilla]

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

Maarten ter Huurne <maar...@treewalker.org> changed:

   What|Removed |Added

 CC||maar...@treewalker.org

--- Comment #10 from Maarten ter Huurne <maar...@treewalker.org> ---
I'm running into the same problem: in KDE's settings, under Translations I set
Preferred Languages: American English, while under Formats I set Region:
Nederland - Nederlands (nl_NL). However, I get Dutch output from some programs
now, for example Make.

As Dennis wrote, the cause seems to be ~/.config/plasma-locale-settings.sh
which sets LANG to nl_NL. If I unset LANG, Make returns to printing English
messages.

POSIX.1-2008 describes LANG as:
This variable shall determine the locale category for native language, local
customs, and coded character set in the absence of the LC_ALL and other LC_*
(LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, LC_TIME)
environment variables. This can be used by applications to determine the
language to use for error messages and instructions, collating sequences, date
formats, and so on.

Since this definition mixes up language and regional settings, which should be
two entirely separate things, in my opinion it's best to not set LANG at all.

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

[kate] [Bug 356786] KWrite crashes attempting Open, from menu or toolbar.

[Maarten via KDE Bugzilla]

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

--- Comment #7 from Maarten <maarten@gmail.com> ---
(In reply to Kåre Särs from comment #6)
> even if this might be older...
> 
> *** This bug has been marked as a duplicate of bug 356840 ***

I see no 'open' button when following the instructions of bug 35684, so cannot
test if this causes the same behaviour. Am using KDE.

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

[kate] [Bug 356786] KWrite crashes attempting Open, from menu or toolbar.

[Maarten via KDE Bugzilla]

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

--- Comment #5 from Maarten <maarten@gmail.com> ---
happens to me regularly on up-to-date F23. 'Open recent' causes no crashes.

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

[kate] [Bug 356786] KWrite crashes attempting Open, from menu or toolbar.

[Maarten via KDE Bugzilla]

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

Maarten <maarten@gmail.com> changed:

   What|Removed |Added

 CC|    |maarten@gmail.com

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