[plasmashell] [Bug 386472] Plasma crashed when connecting USB device

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #7 from Christoph Feck  ---
If this is reproducible, install debug information packages for Qt and Plasma,
and try to run plasmashell with gdb in Konsole.

Please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[plasmashell] [Bug 372574] Program launcher and system notifications disappear

[Māris Nartišs]

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

--- Comment #5 from Māris Nartišs  ---
(In reply to Alexander Mentyu from comment #4)
> Cannot reproduce this bug in:
> 
> Distribution: KDE neon Developer Edition - Stable Branches
> Plasma: 5.11.3
> Frameworks: 5.41.0
> Qt: 5.9.2
> Kernel 4.10.0-38-generic
> Type: 64-bit

Unfortunately I do not have frameworks 5.41 to test, but the issue is still
present with:
plasma-5.39.0
plasma-desktop-5.11.2
kwindowsystem-5.39.0
kwin-5.11.2
Linux kernel 4.13.1
Qt 5.9.2

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

[plasmashell] [Bug 386500] plasma crashes at clicking krunner button

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #2 from Christoph Feck  ---
Unfortunately, Arch does not provide debug information, so this report is not
useful. If you can reproduce it with a different distribution, please add a
complete backtrace.

For more information, please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[phonon-backend-gstreamer] [Bug 386580] plasma crashes by clearing trash

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|k...@davidedmundson.co.uk|dvra...@kde.org
   Target Milestone|1.0 |4.8
Product|plasmashell |phonon-backend-gstreamer
 CC||myr...@kde.org,
   ||romain.per...@gmail.com,
   ||sit...@kde.org,
   ||tdfisc...@kde.org
Version|5.8.7   |unspecified
  Component|general |general

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

[krita] [Bug 387245] New: Pen Pressure not working

[bugzilla_noreply]

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

Bug ID: 387245
   Summary: Pen Pressure not working
   Product: krita
   Version: 3.1.4
  Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: karmacreepypa...@gmail.com
  Target Milestone: ---

When I put pressure on the Tablet with the pen, it doesn't register on the
screen.

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

[krita] [Bug 381445] Brush Bug

[bugzilla_noreply]

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

--- Comment #5 from reptilli...@live.com ---
Since I can't edit -

Replace "Other people hate it." with "Some people hate the new approach."

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

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

[Silver Salonen]

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

--- Comment #23 from Silver Salonen  ---
I don't know now... to me it has really boiled down to Keyring blocking the
input. Is there something that can be done about it from KDE/Plasma side?

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

[dolphin] [Bug 386838] Dolphin doesn't update view (doesn't show new files)

[bugzilla_noreply]

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

--- Comment #10 from jeremy9...@gmail.com ---
Well it seem to work now after a kernel (and other packages but nothing related
to kde it seem) update. Will see if it happen again.

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

[okular] [Bug 387247] New: okular [12.17beta] crash upon highlighting text in pdfs

[Robby Engelmann]

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

Bug ID: 387247
   Summary: okular [12.17beta] crash upon highlighting text in
pdfs
   Product: okular
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Highlighting 5-10 textpositions in a  pdf leads to crash every time.
Unfortunately, drkonqi is not triggered here, thus I do not have a backtrace.
It is not limited to long pdfs as first thought
(https://bugs.kde.org/show_bug.cgi?id=375506)

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

[amarok] [Bug 374670] AAC transcoding is broken due to deprecated libfaac

[bugzilla_noreply]

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

--- Comment #23 from rdragonr...@gmail.com ---
I have submitted the patch the reviewboard.kde.org, but I don't know what to do
further. I am not a developer there, and don't really know much application
coding. (I can write simple C programs, but don't know how to understand large
projects like this one, aside from all the libraries and things used)

I have tested the patch; the AAC transcoding option now appears and I am fairly
sure that I tested the output on my DSi to ensure that it works. The output
file does play in a separate player on my computer.

I was unable to build the tests for the project, however. Perhaps this is why
it has been on hold for the last 5.7 months. I installed gmock/gtest via my
package manager, but have discovered that this only ships the source (and has
been this way since Ubuntu 12 or 13!), NOT the binary that Amarok wants to
build against.

How do I build gtest so that I can compile Amarok with tests enabled? I have to
assume that this issue has since come up over at KDE with this change.
(I am guessing that "make test" will then run them?)

If that isn't the issue, how do I get the patch to move along?

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

[kdeconnect] [Bug 386610] Receiving a notification from kde connect while viewing multiple desktops causes lock up (possibly all notifications)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

--- Comment #2 from Christoph Feck  ---
Please add the output of this Konsole command:

qdbus org.kde.KWin /KWin supportInformation

Adding KWin maintainer for inspection.

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

[kwin] [Bug 387244] KWin appears to crash whenever Plasma is started

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Martin Flöser  ---
Crashes in the nouveau driver. Please report to Mesa developers.

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

[kwin] [Bug 387160] Put task switchers in alphabetical order please

[Martin Flöser]

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

--- Comment #1 from Martin Flöser  ---
Why would an alphabetical order improve the usability?

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

[plasmashell] [Bug 358291] Top-level application entries missing from menu structure (only categories shown at top level)

[Christoph Feck]

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

--- Comment #5 from Christoph Feck  ---
https://phabricator.kde.org/D8816

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

[plasmashell] [Bug 386075] plasma crashes when selecting a non-existent menu in application menu bar

[Christoph Feck]

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

--- Comment #6 from Christoph Feck  ---
If you can provide the information requested in comment #5, please add it.

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

[plasmashell] [Bug 369430] QQmlDelegateModel::_q_itemsChanged - kickoff version

[Christoph Feck]

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

--- Comment #34 from Christoph Feck  ---
David, do we have an upstream ticket? Bug 386500 is with Qt 5.9.2, and is the
same backtrace.

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

[krita] [Bug 381445] Brush Bug

[bugzilla_noreply]

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

--- Comment #4 from reptilli...@live.com ---
Here's the discussion - https://forum.kde.org/viewtopic.php?f=139=140758

Some people like having to click on the engine, and then all the options are
there, and the default brush are automatically assigned to the engine. Just
like the old Krita. Other people hate it. For those who hates it, they have to
delete so many brushes, and assign names like

"1 - Pixel brush"
"2 - Smudge brush"

To get the old Krita feel in that aspect. A hybrid approach may be needed here.
The better approach would be:

One should be able to change brush engine, and the brush used automatically
changes. But, the selected for each engine is automatically used. This is the
hybrid approach to accomodate as many people as possible.

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

[konsole] [Bug 387202] Copy and Paste stop working after 47 days

[bugzilla_noreply]

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

--- Comment #2 from h...@pro-linux.de ---
Note that I don't use KDE, but LDXE and Openbox. So I don't have many KDE apps
running for a longer time. But I just checked KOrganizer and it seems to have
the same problem. I restarted it and the problem was gone. Before that,
KOrganizer probably has been running as long as the system is up, currently 151
days.

For non-KDE-apps I didn't notice such problems. JEdit, Eclipse, Palemoon,
Audacity and others are OK. So it may be a problem in KDE Frameworks 5.28 or Qt
5.7.

Regarding the time I maybe miscalculated the interval. If I remember correctly,
I restarted Konsole on October 4, and the problem occured on Nov 22. That's 49
days. It could just fit although it looks like it happened a few hours too
early ;-)

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

[plasmashell] [Bug 386630] Task manager crashes when launching with groupingAppIdBlacklist items open

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
Phabricator comment says this commit fixes the issue, but it was
(intentionally?) only CC'd, so got not closed automatically.

Please clarify, either by changing the bug status, or by adding a comment what
still needs to be done to resolve this ticket.

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

[okular] [Bug 375506] Crashing when highlighting in long document

[Robby Engelmann]

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

--- Comment #2 from Robby Engelmann  ---
Bit differently from the original description (for windows), here pdf pages are
always shown, but okular crashes after highlighting 4-6 text positions every
time.
And I do not have any custom settings applied

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

[systemsettings] [Bug 386775] Additional whitelist option to configure Baloo in the systemsettings

[PK]

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

--- Comment #3 from PK  ---
In my opinion this is not a duplicate of bug 352487. In that bug the question
is to replace the blacklist system by a whitelist system. I can see that only
whitelisting can bring problems too.
That is why I suggest to have AND the possibility to blacklist AND the
possibility to whitelist.

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

[plasmashell] [Bug 384891] Keyboard input barely works

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |DUPLICATE

--- Comment #6 from Christoph Feck  ---


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

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

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mtm...@gmail.com

--- Comment #22 from Christoph Feck  ---
*** Bug 384891 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 386473] Slow startup

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
Some people reported that disabling the Splash screen via systemsettings5
improved startup time for Plasma.

Also try a second start. For fresh users, the initial system configuration
cache (ksycoca5) has to be created, which needs to scan several system and user
folders, but it is not clear from your report how much time is actually spent
for this.

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

[plasmashell] [Bug 384248] Message appeared: Plasma has crashed

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
Different backtrace.

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

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

[plasmashell] [Bug 386499] plasma crashed after unmounting a usb key

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||heinz.wei...@hotmail.de

--- Comment #1 from Christoph Feck  ---
*** Bug 384248 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 386499] plasma crashed after unmounting a usb key

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org
  Component|general |Device Notifier

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

[plasmashell] [Bug 386551] Status & Notifications and Digital Clock can be tiled

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
These popups are also moveable with Alt+Left, while e.g. popup menus are not,
so there must be some setting that informs the window manager that these are
not regular application windows.

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

[kdevelop] [Bug 387136] configure project dialogue size wider than screen

[Jeremy W . Murphy]

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

--- Comment #3 from Jeremy W. Murphy  ---
Ah, sorry, thanks Kevin.

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

[kwin] [Bug 387160] Put task switchers in alphabetical order please

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
A clear order makes things easier to find than a random or unclear order.

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

[kdevelop] [Bug 387246] New: Add support for .gitignore like project treeview items exclusion.

[Venca B Spam]

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

Bug ID: 387246
   Summary: Add support for .gitignore like project treeview items
exclusion.
   Product: kdevelop
   Version: 5.2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: vbs...@centrum.cz
  Target Milestone: ---

This is feature request.

Add support for .gitignore like project treeview items exclusion.

Although I know there is possibility to exclude items from the project tree
view, I see it as a bit not practical for even a bit larger projects (I can
provide examples on demand) as it require too much attention from the user.

First I was thinking to ask to support .gitignore itself, but this does not
have the same business requirement base.

What about to have the same syntax as .gitignore (easy to parse and interpret)
and just add these patterns to already existing project exclusion list of
items.

Minimal use case:
- User will create .kdevignore and will populate it by its own patterns
- User will open/import CMake project and the files will be automatically
ignored.
- User still can add new excluded items which will be stored the same way as
today (in the project file).

By the way, as I am new to KDE, is there any other more suitable place to
discuss feature requests, ideas?
(I did try KDE forum but it looks a bit less crowded.)

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

[plasmashell] [Bug 379580] Wallpaper slideshow displays two consecutive images at login.

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
But this patch has not yet been applied, right?

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

[krita] [Bug 371827] [BOSTO] Pen Pressure not working

[bugzilla_noreply]

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

karmacreepypa...@gmail.com changed:

   What|Removed |Added

 CC||karmacreepypa...@gmail.com

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

[okular] [Bug 375506] Crashing when highlighting in long document

[Robby Engelmann]

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

--- Comment #1 from Robby Engelmann  ---
I also see a crash in okular (KDE apps 17.12 beta) running on the latest
Tumbleweed snapshot.
I do not have a bugtrace because drkonqi does not start. However, it also
crashes upon highlighting text in a large pdf document.

If you need more information to fix it, please let me know how to obtain them!

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

[frameworks-kcoreaddons] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[Milian Wolff]

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

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |FIXED

--- Comment #1 from Milian Wolff  ---
#12 KDirWatchPrivate::entry (this=0x6, _path=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-kcoreaddons/work/kcoreaddons-5.38.0/src/lib/io/kdirwatch.cpp:597
#13 0x7fd1d012294d in KDirWatch::contains (this=0x4f53570, _path=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-kcoreaddons/work/kcoreaddons-5.38.0/src/lib/io/kdirwatch.cpp:1967
#14 0x7fd1caf06892 in KDevelop::ProjectWatcher::addDir (this=0x4f53570,
path=..., watchModes=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kf5-kdevelop/kf5-kdevelop-devel/work/kf5-kdevelop-5/kdevplatform/project/projectwatcher.cpp:39

Are you sure the dirwatch in your project watcher class is actually still
valid? This looks like a queued event triggers a call to ProjectWatcher::addDir
which then tries to access an already-deleted KDirWatch (note the this=0x6 of
the KDirWatchPrivate). I doubt this is a bug in KDirWatch, but rather your code
that is calling it is broken.

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

[frameworks-kcoreaddons] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[RJVB]

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

--- Comment #3 from RJVB  ---
Oops, crossed comments.

Yes, the only immediate explanation I can see is that a "watchDir" signal was
delivered to my lambda after a project was unloaded (the lambda that's now
connected without explicit connection type specifier, you know what I mean).
What I don't understand is how this can have happened; the signal source should
also have been taken down when the project was being unloaded. It may have been
related to overall instability which also caused the CPU burning.

I've been running this code for weeks now and never saw this happen before. I'm
making some changes - disconnecting the "watchDir" signal explicitly in the
appropriate locations and catching QCoreApplication::aboutToQuit in
ProjectWatcher to stop the monitoring. That seems like a reasonable thing to do
anyway.

Is there anything else one can do to prevent queued signals that get delivered
after the target was deleted, handle them properly? Maybe use deleteLater() on
the watcher instance?

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

[krita] [Bug 382306] Pop-Up Palette Color Picker moves by itself when clicked

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[krita] [Bug 381177] Krita doesn't update the color wheel in the selector dialog when manually typing in 8-bit color values

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
I fixed this at the same time as I fixed the initialization of the color
dialog.

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

[plasmashell] [Bug 380089] Panel widgets in all activities

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #8 from Alexander Mentyu  ---
I can't resize the Kicker menu itself with Alt+Right click - only it's submenus
- and their sizes aren't remembered after second hover over them.

I tried to resize 'Audio Volume', 'Weather' and 'Digital Clock' widgets and
their sizes are remembered and consistent across Activities.

Positions of submenus and widgets also aren't remembered when moving them with
Alt+Left click

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

[kile] [Bug 387234] New: Disable Live Preview ignored on new files

[bugzilla_noreply]

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

Bug ID: 387234
   Summary: Disable Live Preview ignored on new files
   Product: kile
   Version: 2.9.91
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: user interface
  Assignee: michel.lud...@kdemail.net
  Reporter: wisot...@mathb.rwth-aachen.de
  Target Milestone: ---

Disabling live preview via settings->configure kile->kile->live preview->
uncheck "enable live preview" does not disable it on newly opened documents
although the corresponding area is greyed out.
Pressing the pdflatex button then compiles the document twice for the live
preview and twice for actually pressing it.
For large documents this costs unnecessary time.

To completely disable live preview you have first to enable it, disable it on
new documents and then disable it again.

The expected behaviour for "disable live preview" would be it to be completely
disabled.

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

[plasmashell] [Bug 387235] New: Notifications fail to send, causing some applications to crash.

[Mnpn]

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

Bug ID: 387235
   Summary: Notifications fail to send, causing some applications
to crash.
   Product: plasmashell
   Version: 5.11.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: mnp...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Looks like any application fails when it comes to sending notifications via the
plasma shell.

Running an alternative notification server resolves the issue temporarily. It
gives this output upon notification:
"(process:7083): GLib-CRITICAL **: g_variant_unref: assertion 'value->ref_count
> 0' failed"

This causes Discord to completely lock up, needing to be force closed with
KSysGuard.
Notify-Send doesn't do anything, it's just stuck until closed with Ctrl+C.

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

[krita] [Bug 385239] Grid docker: "linked" button is stored globally instead of per view

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kri
   ||ta/73488ec886e72f3c0cd8437e
   ||a2d899c1d26203d5
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Boudewijn Rempt  ---
Git commit 73488ec886e72f3c0cd8437ea2d899c1d26203d5 by Boudewijn Rempt.
Committed on 23/11/2017 at 10:33.
Pushed by rempt into branch 'master'.

Set the grid config of the document on the grid docker when switching between
documents

M  +0-2plugins/dockers/griddocker/grid_config_widget.cpp
M  +14   -10   plugins/dockers/griddocker/griddocker_dock.cpp

https://commits.kde.org/krita/73488ec886e72f3c0cd8437ea2d899c1d26203d5

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

[kdevelop] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[RJVB]

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

--- Comment #4 from RJVB  ---
There's something else that's fishy, I'm now pretty certain that the CPU
burning is due to an issue in the AbstractFileManagerPlugin and/or the
FileManagerListJob classes which somehow start reloading all or part of a
project continuously. Hard to tell exactly what happens but I didn't see any
trace of my ProjectWatcher class causing this directly (activating a trace in
AFMPP::dirty() doesn't print anything).

The project that's causing this is one using autoconf, and the issue started
when I made an edit to its configure.ac . Looks like this starts an infinite
loop; autoconf is apparently called automatically and since the edit is
incomplete there's an error situation somewhere which isn't handled properly.

This doesn't always cause signals to be delivered to a stale ProjectWatcher
class but it seems I do have to rethink my design a bit :-/

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

[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations

[David de Cos]

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

David de Cos  changed:

   What|Removed |Added

 CC||dde...@gmx.net

--- Comment #13 from David de Cos  ---
The bug persists in Plasma 5.11.3 / Qt 5.9.2. Setting the scaling precision to
"smooth", as Thomas suggested, worked for me.

I just want to add to Szymon's analysis (comment #11) that the behavior he
found is kind of the opposite if you have a vertical panel. In that case:

- Maximized windows are not visible.
- Windows horizontally maximized are not visible.
- Windows vertically maximized are visible.
- Unmaximized windows are not visible (this is the only one that's common to
both panel placements, if I'm not mistaken).

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

[plasmashell] [Bug 387235] Notifications fail to send, causing some applications to crash.

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from David Edmundson  ---
>"(process:7083): GLib-CRITICAL **: g_variant_unref: assertion 
>'value->ref_count > 0' failed"

If a client crashes, the client is at fault.
Please report to them.

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

[plasmashell] [Bug 387199] Folder View mouse action issue

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Kai Uwe Broulik  ---
Known issue. I have a potential fix for that which I'm not too happy about:
https://phabricator.kde.org/D8864

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

[frameworks-kcoreaddons] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[RJVB]

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

RJVB  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #2 from RJVB  ---
I have no idea how ProjectWatcher::addDir() can have been called here: it isn't
connected directly to any signals. It *is* called from a lambda, can it be that
that doesn't appear in a backtrace?

However this happened, the ProjectWatcher instance must have been stale judging
from the terminal output I saw.

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

[krita] [Bug 382065] Weird behavior with smudge brushes and selection

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Boudewijn Rempt  ---
I can confirm the issue. it was already present in the first development build,
too.

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

[krita] [Bug 366233] Brush tool no longer draws but cursor is still visible and moving

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Boudewijn Rempt  ---
I'm sorry, but there just isn't enough information to start working on this
report.

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

[krita] [Bug 386142] Touch docker (or any QML-based dockers) requires working OpenGL implementation

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[krita] [Bug 386142] Touch docker (or any QML-based dockers) requires working OpenGL implementation

[Boudewijn Rempt]

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

--- Comment #6 from Boudewijn Rempt  ---
Or we could build Qt with the qtquick software renderer...

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

[krita] [Bug 385239] Grid docker: "linked" button is stored globally instead of per view

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
Summary|x spacing on the Grid   |Grid docker: "linked"
   |Docker is the wrong number  |button is stored globally
   ||instead of per view
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Sebastian Kügler]

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

--- Comment #25 from Sebastian Kügler  ---
You can disable the kscreen background service and it won't do any automatic
configuration or reconfiguration, then you can use xrandr by hand.

I may also note that, while in your situation, nothing may have changed, we
have *numerous* reports that for many users, the situation has improved and
kscreen just works. That's not really helping you, but your view on the
situation is limited it seems, and as a result of that, you're treating
developers unfairly.

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

[kwin] [Bug 376104] Quick tile window to any screen edge or corner de-maximizes the window without tiling as a first action since plasma 5.9.0

[Till Schäfer]

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

--- Comment #28 from Till Schäfer  ---
I applied the patch here on kwin 5.11.3 running on xorg-server 1.19.5 and it
works like a charm.

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

[kdenlive] [Bug 387236] New: Library "sequences" not correctly rendered.

[Davy Bartoloni]

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

Bug ID: 387236
   Summary: Library "sequences" not correctly rendered.
   Product: kdenlive
   Version: 17.08.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: bartol...@outlook.com
  Target Milestone: ---

take a look to this video.. this happens on Windows and Linux latest version
(and probably on old versions too)

https://youtu.be/sdh03Sndrtc

placing on thelibrary a multiple video tracks sequence will not rendered right
when used.

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

[krita] [Bug 386642] Multi-threaded brushes: delay with big textures

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Boudewijn Rempt  ---
Add to https://phabricator.kde.org/T7309

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

[krita] [Bug 383909] Checkbox «Share curve across all settings» doesn’t save the curve if it’s not changed

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[krita] [Bug 375002] Using some textures corrupt brush preset

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Boudewijn Rempt  ---
I see this happening:

libpng warning: zTXt: truncated

And since the pattern is stored in the txt section of a png image, it could
just mean that this pattern is too big for libpng to handle.

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

[plasmashell] [Bug 346918] Removing the ALT+F1 shortcut for displaying Application launcher isn't saved between sessions when removed from "Global shortcuts -> plasmashell"-section

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #10 from Alexander Mentyu  ---
Can confirm this bug - Alt+F1 shortcut becomes active again after logging out
and logging in and after restarting of system

(In reply to Andreas Joseph Krogh from comment #8)
> Removing this shortcut by right-clicking on the K-menu and "Application
> Launcher Settings" -> "Keyboard shortcuts" works for me.

This method of disabling shortcut work for me

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.3
Frameworks: 5.41.0
Qt: 5.9.1
Kernel 4.10.0-38-generic
Type: 64-bit

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

[krita] [Bug 382068] Brush tips broken after exporting

[Boudewijn Rempt]

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

--- Comment #1 from Boudewijn Rempt  ---
Git commit 3da66fc9866f299597e7c37fd2f3355478c98389 by Boudewijn Rempt.
Committed on 23/11/2017 at 11:36.
Pushed by rempt into branch 'master'.

Make it possible to save gbr/gih again

These save using QIODevice, so don't tell the export manager
that it needs a filename. Also, return an error if saving
fails.

M  +6-3plugins/impex/brush/kis_brush_export.cpp
M  +0-1plugins/impex/brush/kis_brush_export.h

https://commits.kde.org/krita/3da66fc9866f299597e7c37fd2f3355478c98389

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

[krita] [Bug 385326] X-Tilt and Y-Tilt curve settings are incorrect

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Qt at least puts it in the -60 to +60 range:
http://doc.qt.io/qt-5/qtabletevent.html#xTilt

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

[frameworks-kcoreaddons] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[Milian Wolff]

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

Milian Wolff  changed:

   What|Removed |Added

 Resolution|FIXED   |WAITINGFORINFO

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

[plasmashell] [Bug 381486] Switching activity don't change focus

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #1 from Alexander Mentyu  ---
Can't reproduce this bug in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.3
Frameworks: 5.41.0
Qt: 5.9.1
Kernel 4.10.0-38-generic
Type: 64-bit

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

[krita] [Bug 385238] Floating dockers not resizable on OS X

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Boudewijn Rempt  ---
I think that the chances for the Qt guys working on this bug are remote... It's
marked as P3, so we'll need a workaround where all custom titlebar items are
removed if the docker is floating.

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

[kdevelop] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[RJVB]

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

RJVB  changed:

   What|Removed |Added

   Assignee|mp...@kde.org   |kdevelop-bugs-n...@kde.org
Product|frameworks-kcoreaddons  |kdevelop
  Component|general |general
Version|5.38.0  |5.2.0

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

[krita] [Bug 387184] hiding unhiding dialogs pulls the canvas around

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
   Platform|Other   |Mac OS X Disk Images

--- Comment #1 from Boudewijn Rempt  ---
This is an issue specific to OSX, it doesn't happen on Windows or Linux. That
probably means that it's a bug in the development framework, Qt, or the macOS
window manager, and we just cannot do anything about it ourselves :-(

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

[krita] [Bug 378802] Canvas movement hotkeys unusable until focus returns from floating docker to main window

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Boudewijn Rempt  ---
This is outside our power to change.

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

[kdevelop] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[RJVB]

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

--- Comment #5 from RJVB  ---
So... what seems to be burning CPU is a number of FileManagerListJob instances
that keep running and calling FileManagerListJob::startNextJob() which in turn
emits the watchDir signal.

What I fail to see (yet) is how emitting that signal can lead to this. Adding a
directory to the watch list doesn't have the direct effect of (re)loading that
directory, and there are no dirty signals being generated either (those could
of course cause directory reloading).

Yet, the issue goes away when I make ProjectWatcher::addDir() a stub (that
doesn't call KDirWatch::addDir()).

I could imagine how the autoconf and configure steps generate one or more
directories that should be ignored, but not how the current "stock" dirwatching
implementation isn't vulnerable to this situation.

The whole issue went away when I undid the configure.ac edit, restored the
original configure file and re-ran my configure command OUTSIDE of KDevelop.

Only to start anew as soon as I made a change to configure.ac in KDevelop,
before I even saved the file.

I'm going to see what happens when I emit the dirWatch signal only for
previously unwatched directories or from a different location, but I think the
issue goes deeper than just my new dirwatching algorithm.

It looks to me that there's an issue with the project manager being used here
which is exposed/triggered by my dirwatching algorithm.

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

[kdevelop] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Kevin Funk  ---
Which patches do you have applied anyway? You're lacking that information. We
don't have projectwatcher.cpp in our code base.

How are we supposed to try to reproduce this without that information?

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

[plasmashell] [Bug 376848] Folder View not rendering images correctly.

[Gerhard Dittes]

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

--- Comment #9 from Gerhard Dittes  ---
Hi,

any news on this?  It would be very nice to have this fixed/improved for the
upcoming version of Plasma LTS...

I see this issue every time I look at my desktop and it really feels so
obviously buggy (or amateurishly)...

Please, please increase priority! :-)

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

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #7 from Boudewijn Rempt  ---
Does it matter whether opengl or angle are enabled, or when cpu rendering is
used?

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

[krita] [Bug 386165] Krita Crash inside KisBrushMaskScalarApplicator::processScalar(()

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #3 from Boudewijn Rempt  ---
Hm, I cannot relate that back trace to anything relevant in the code...

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

[kmail2] [Bug 378011] KMail 5.4.3 Mailing list not resolved

[Axel Braun]

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

--- Comment #22 from Axel Braun  ---
still broken in 5.6.3

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Sergio]

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

--- Comment #24 from Sergio  ---
At this point, almost two years after the original report and many proud
articles such as https://lwn.net/Articles/694157/ all the issues are still
there.

If you have a laptop, and you attach it to an external screen, then close the
lid and suspend the laptop, then detach the connectors, when you eventually
attach an external screen again, kscreen ends up thinking that you re-attached
the former monitor. This is quite evident as the UI with the Display and
Monitor Settings *name* the monitor and you get the former name. For instance
if you were initially attached to a Samsung monitor, you suspend the laptop,
detach the connector, work with your laptop, then one day attach a Dell
monitor, kscreen identifies it as Samsung and applies the settings for the
Samsung monitor.

This is very bad. On some occasions with the external monitor you have the
laptop screen disabled. Then, one day you need to give a presentation, you
attach the projector, kscreen thinks it is the external monitor, switches off
your laptop display and provides to the projector some resolution that it can't
support. Et voilà, you are with no working screen at all in front of your
audience.

So, at this point the question is: is there a way to run plasma without the
full kscreen support? I.e. only having the minimal assurance that when an
external monitor is detached the display permanently goes back to the main
laptop screen, with kscreen not trying to (incorrectly) guess how it should
configure the screens?

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

[okular] [Bug 207748] LTR languages searches text backwards

[Fahad Al-Saidi]

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

--- Comment #17 from Fahad Al-Saidi  ---
this bug also effect the copying the RTL text. the copied text is reversed.

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

[kate] [Bug 387233] New: Crash when toggling plugin from kate settings

[Elvis Angelaccio]

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

Bug ID: 387233
   Summary: Crash when toggling plugin from kate settings
   Product: kate
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plugin-preview
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: elvis.angelac...@kde.org
CC: kosse...@kde.org
  Target Milestone: ---

I can reproduce it every time:

1. Go to Kate Settings -> Plugins
2. Uncheck "Document Preview" entry
3. Check "Document Preview" entry -> crash

Stacktrace:

#0  0x7fe748e9ea60 in QWidget::layout() const () from
/usr/lib/libQt5Widgets.so.5
#1  0x7fe7253061b3 in KTextEditorPreviewView::KTextEditorPreviewView
(this=0x563df5a45f80, plugin=0x7fe730006390, 
mainWindow=0x563df4e828f0) at
../addons/preview/ktexteditorpreviewview.cpp:47
#2  0x7fe7253053fb in KTextEditorPreviewPlugin::createView
(this=0x7fe730006390, mainwindow=0x563df4e828f0)
at ../addons/preview/ktexteditorpreviewplugin.cpp:42
#3  0x563df2a3558c in KatePluginManager::enablePluginGUI
(this=0x7ffd6e4990d8, item=0x563df4ea21e0, win=0x563df4e80640, config=0x0)
at ../kate/katepluginmanager.cpp:224
#4  0x563df2a34fdd in KatePluginManager::enablePluginGUI
(this=0x7ffd6e4990d8, item=0x563df4ea21e0) at ../kate/katepluginmanager.cpp:252
#5  0x563df2a90ec8 in KateConfigPluginPage::loadPlugin
(this=0x563df5a5bcc0, item=0x563df5a6a7a0)
at ../kate/kateconfigplugindialogpage.cpp:112
#6  0x563df2a90e26 in KateConfigPluginPage::stateChange
(this=0x563df5a5bcc0, item=0x563df5a6a7a0, b=true)
at ../kate/kateconfigplugindialogpage.cpp:98
#7  0x563df2a917c9 in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KateConfigPluginPage::*)(KatePluginListItem*, bool)>::call (f=
(void (KateConfigPluginPage::*)(KateConfigPluginPage * const,
KatePluginListItem *, bool)) 0x563df2a90df0
,
o=0x563df5a5bcc0, arg=0x7ffd6e495740) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:136
#8  0x563df2a91713 in QtPrivate::FunctionPointer::call, void> (f=
(void (KateConfigPluginPage::*)(KateConfigPluginPage * const,
KatePluginListItem *, bool)) 0x563df2a90df0
,
o=0x563df5a5bcc0, arg=0x7ffd6e495740) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:169
#9  0x563df2a91636 in QtPrivate::QSlotObject, void>::impl (which=1,
this_=0x563df5a8d400, r=0x563df5a5bcc0, a=0x7ffd6e495740, ret=0x0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:398
#10 0x7fe747977bbf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#11 0x563df2a7d6b2 in KatePluginListView::stateChange (this=0x563df5a5cc80,
_t1=0x563df5a6a7a0, _t2=true)
at
kate/kdeinit_kate_autogen/EWIEGA46WW/moc_kateconfigplugindialogpage.cpp:139
#12 0x563df2a90999 in KatePluginListView::stateChanged
(this=0x563df5a5cc80, item=0x563df5a6a7a0)
at ../kate/kateconfigplugindialogpage.cpp:63
#13 0x563df2a914e6 in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KatePluginListView::*)(QTreeWidgetItem*)>::call (f=
(void (KatePluginListView::*)(KatePluginListView * const, QTreeWidgetItem
*)) 0x563df2a90950 ,
o=0x563df5a5cc80, arg=0x7ffd6e4959f0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:136
#14 0x563df2a91443 in QtPrivate::FunctionPointer::call,
void> (f=
(void (KatePluginListView::*)(KatePluginListView * const, QTreeWidgetItem
*)) 0x563df2a90950 , o=0x563df5a5cc80, arg=0x7ffd6e4959f0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:169
#15 0x563df2a91366 in QtPrivate::QSlotObject,
void>::impl (which=1, this_=0x563df5a68410, r=0x563df5a5cc80, a=0x7ffd6e4959f0,
ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:398
#16 0x7fe747977bbf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#17 0x7fe749145411 in QTreeWidget::itemChanged(QTreeWidgetItem*, int) ()
from /usr/lib/libQt5Widgets.so.5
#18 0x7fe747977a96 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#19 0x7fe7478e06ad in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) ()
   from /usr/lib/libQt5Core.so.5
#20 0x7fe74914612a in ?? () from /usr/lib/libQt5Widgets.so.5
#21 0x7fe749149bb4 in QTreeWidgetItem::setData(int, int, QVariant const&)
() from /usr/lib/libQt5Widgets.so.5
#22 0x7fe7491455b6 in ?? () from /usr/lib/libQt5Widgets.so.5
#23 0x7fe7490f3f20 in 

[kate] [Bug 387233] Crash when toggling preview plugin from kate settings

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

Summary|Crash when toggling plugin  |Crash when toggling preview
   |from kate settings  |plugin from kate settings

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

[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting

[Kolya Ay]

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

Kolya Ay  changed:

   What|Removed |Added

 CC||kolya...@gmail.com

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

[kate] [Bug 387233] Crash when toggling preview plugin from kate settings

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[krita] [Bug 380116] Brushes with hsv settings and low opacity

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[krita] [Bug 386652] Overview misalignment

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #4 from Boudewijn Rempt  ---
Okay, I've managed to reproduce the issue. Not fix it, though...

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

[krita] [Bug 383398] Switching tools within Toolbox sometimes has to be done twice

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Hi Alicia,

Is this still happening with 3.3.2? I haven't been able to reproduce this issue
myself :-(

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

[krita] [Bug 381549] Enabled buttons appears greyed like disabled

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #4 from Boudewijn Rempt  ---
I only see this when switching from a dark to a light color theme. If I then
restart, I cannot reproduce.

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

[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia

[David Edmundson]

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

--- Comment #10 from David Edmundson  ---
Not yet. It requires some refactoring first.

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

[kdevelop] [Bug 387232] KDirWatch crash when calling KDW::addDir() during shutdown

[Kevin Funk]

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

--- Comment #6 from Kevin Funk  ---
René, this bug is three hours old and it already has several pages of text. Be
assured that there are very few persons having the time/motivation to read
through all of that. I did, and it's super noisy text (with very little actual
information).

Please, we don't need a live log of how you're trying to investigate this bug;
instead, do your analysis, tests, then *sum* up your findings and report them
here. It doesn't help updating bug reports on a hourly basis with your recent
brain dump.

I'm happy about your motivation to work on these issues; but the feedback needs
to be provided/presented differently.

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

[krita] [Bug 386544] When selecting a color, Krita crashes

[Boudewijn Rempt]

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

--- Comment #5 from Boudewijn Rempt  ---
Thanks for the information. The crash log is not very informative, but it tells
us that there's some kind of recursive loop in their so krita runs out of stack
space. I thought had fix the last of those for 3.3.0, though...

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

[krita] [Bug 384161] Saved onion skin opacity decreases each time Krita is opened

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[plasmashell] [Bug 375912] Global Menu is not working with GTK apps

[Kolya Ay]

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

Kolya Ay  changed:

   What|Removed |Added

 CC||kolya...@gmail.com

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

[kdevelop] [Bug 387232] New: KDirWatch crash when calling KDW::addDir() during shutdown

[RJVB]

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

Bug ID: 387232
   Summary: KDirWatch crash when calling KDW::addDir() during
shutdown
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.2.0-43-ge3df584fc9)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.38.0
Operating System: Linux 4.9.30-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I had told KDevelop to quit.

- Unusual behaviour I noticed:
KDevelop had started burning 100% CPU on one of my cores without apparent
reason so I decided to relaunch the session.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd1d5efd7c0 (LWP 27418))]

Thread 10 (Thread 0x7fd1ba1b7700 (LWP 27421)):
#0  0x7fd1cdee8c5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fd1c4bf7b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fd1c4bf964f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fd1bce45549 in QXcbEventReader::run (this=0x21ac2d0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1345
#4  0x7fd1ceab7cf9 in QThreadPrivate::start (arg=0x21ac2d0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/thread/qthread_unix.cpp:368
#5  0x7fd1c8a64184 in start_thread (arg=0x7fd1ba1b7700) at
pthread_create.c:312
#6  0x7fd1cdef5ffd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7fd1aee9b700 (LWP 27422)):
#0  0x7fd1cdee8c5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fd1c5fae081 in g_main_context_iterate.isra () from
/opt/local/lib/libglib-2.0.so.0
#2  0x7fd1c5fae18c in g_main_context_iteration () from
/opt/local/lib/libglib-2.0.so.0
#3  0x7fd1cecd559b in QEventDispatcherGlib::processEvents
(this=0x7fd1a80008c0, flags=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd1cec8117a in QEventLoop::exec (this=this@entry=0x7fd1aee9ade0,
flags=..., flags@entry=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qeventloop.cpp:212
#5  0x7fd1ceab32ab in QThread::exec (this=this@entry=0x7fd1d1775460
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/thread/qthread.cpp:507
#6  0x7fd1d1505005 in QDBusConnectionManager::run (this=0x7fd1d1775460
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbusconnection.cpp:170
#7  0x7fd1ceab7cf9 in QThreadPrivate::start (arg=0x7fd1d1775460 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/thread/qthread_unix.cpp:368
#8  0x7fd1c8a64184 in start_thread (arg=0x7fd1aee9b700) at
pthread_create.c:312
#9  0x7fd1cdef5ffd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 8 (Thread 0x7fd1a6d1b700 (LWP 27529)):
#0  0x7fd1cdee8c5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fd1c5fae081 in g_main_context_iterate.isra () from
/opt/local/lib/libglib-2.0.so.0
#2  0x7fd1c5fae18c in g_main_context_iteration () from
/opt/local/lib/libglib-2.0.so.0
#3  0x7fd1cecd559b in QEventDispatcherGlib::processEvents
(this=0x7fd1a8c0, flags=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd1cec8117a in QEventLoop::exec (this=this@entry=0x7fd1a6d1ad90,
flags=..., flags@entry=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qeventloop.cpp:212

[krita] [Bug 383066] Improvement suggestion on the deform brush engine

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME
 CC||b...@valdyas.org

--- Comment #4 from Boudewijn Rempt  ---
That's a matter of mathematics, I'm afraid.

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

[krita] [Bug 387070] Bristle engine creates artifacts when drawn on negative coords in wrap around mode

[Alvin Wong]

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

--- Comment #2 from Alvin Wong  ---
Just fyi, neither https://phabricator.kde.org/D8894 nor
https://phabricator.kde.org/D8898 seem to change anything regarding the bristle
engine,

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

[krita] [Bug 382110] Fill tool does not work if brush eraser is selected

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
   Severity|normal  |wishlist

--- Comment #3 from Boudewijn Rempt  ---
Maybe we should bite the bullet and do for blending mode what I just did for
opacity; make it a per-tool setting.

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

[krita] [Bug 386625] Problem when merging layers

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #5 from Boudewijn Rempt  ---
I usually don't have time to watch videos, I much prefer a test file and a set
of clear steps to reproduce the issue... But the reason the blending mode of
the merged set of layers is set to Normal is that the bottom-most of the merged
layers has the Normal blending mode; and that's the blending mode that's
selected for the merged result. This is consistent with other applications, so
it's not a bug in Krita.

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

[krita] [Bug 385819] Identical condition

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kri
   ||ta/c7c1f5d03c978fdf79eeaa8e
   ||39133a097f8b404d
 Resolution|--- |FIXED

--- Comment #1 from Boudewijn Rempt  ---
Git commit c7c1f5d03c978fdf79eeaa8e39133a097f8b404d by Boudewijn Rempt.
Committed on 23/11/2017 at 09:17.
Pushed by rempt into branch 'master'.

Remove identical condition in if statement

M  +1-1libs/ui/brushhud/kis_round_hud_button.cpp

https://commits.kde.org/krita/c7c1f5d03c978fdf79eeaa8e39133a097f8b404d

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

[krita] [Bug 384161] Saved onion skin opacity decreases each time Krita is opened

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kri
   ||ta/35c53e861d78b6a0b2ed7c96
   ||f99ec8ffce319075

--- Comment #1 from Boudewijn Rempt  ---
Git commit 35c53e861d78b6a0b2ed7c96f99ec8ffce319075 by Boudewijn Rempt.
Committed on 23/11/2017 at 09:17.
Pushed by rempt into branch 'master'.

Store onion skin opacity as qreal to avoid rounding errors

Because we convert onion skin opacity between a range of 0..100
and 0..255, we need to store it as a qreal and correctly round it.

M  +1-1plugins/dockers/animation/kis_equalizer_widget.h
M  +2-2plugins/dockers/animation/onion_skins_docker.cpp

https://commits.kde.org/krita/35c53e861d78b6a0b2ed7c96f99ec8ffce319075

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

[krita] [Bug 383712] Crash in master when deleting a frame.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kri
   ||ta/10135534183bd22b09e95b58
   ||7620ae083912c241

--- Comment #1 from Boudewijn Rempt  ---
Git commit 10135534183bd22b09e95b587620ae083912c241 by Boudewijn Rempt.
Committed on 23/11/2017 at 09:17.
Pushed by rempt into branch 'master'.

Check shared pointer before dereferencing.

M  +4-3plugins/dockers/animation/kis_animation_utils.cpp

https://commits.kde.org/krita/10135534183bd22b09e95b587620ae083912c241

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

[plasmashell] [Bug 381954] Desktop partially frozen when a Qt application shows a progress dialog

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #1 from Alexander Mentyu  ---
Was able to reproduce this bug once. Desktop freezes upon "Opening file..."
dialog - dragging fullscreen (Firefox) window unfroze the desktop. Cannot
reproduce this bug currently.

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

[kwin] [Bug 387026] idea: "don't change focus" hotkey

[RJVB]

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

--- Comment #4 from RJVB  ---
It's a start, not really ideal and I don't seem to have any documentation for
it at all (thanks for pointing out that I need to protect the browser, the
opposite of what I'd have expected).

I'm obliged to use "high" protection to see any effect at all and that means
browser windows not only NOT get focus when they ask for it, they're also not
being raised. As I said, that's the higher level of the feature I hope for.

Is there a way to override processing of all specific rules, either as a toggle
with a hotkey or coupled directly to a hotkey? That would also work for me, I
think, and might be a more generally useful feature to implement if it doesn't
exist yet.

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

[krita] [Bug 382225] "Regeneration Cache"

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #6 from Boudewijn Rempt  ---
Okay, this change isn't backportable, but there are 4.0 development builds
available now, so I'm closing this bug.

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

[plasmashell] [Bug 381885] Can no longer lower brightness to zero (screen backlight off)

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Kai Uwe Broulik  ---
This is intentional to keep you from accidentally making your system
inaccessible. If you want to turn off the screen, use the button to do that,
brightness zero is not turning off.

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