[krita] [Bug 408015] Global menu doesn't work

[beojan]

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

--- Comment #50 from beojan  ---
(In reply to Guido from comment #49)
> global menu is a KDE feature and Krita is a KDE software.
> So, this is a legitimate bug.
> As far as I know, Krita is the only KDE software that has this problem with
> the global menu.

Take a look at the duplicate 45882
(https://bugs.kde.org/show_bug.cgi?id=458882). It's not really an upstream bug,
it's caused by Krita creating throwaway QApplication instances in it's startup
routine (which the Qt documentation warns against). I'm not sure if there's an
easy fix for this though.

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

[krita] [Bug 458882] Menu Bar display only if executed as root (sudo/su)

[beojan]

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

--- Comment #16 from beojan  ---
Could the main KisApplication instance be constructed earlier, so it can be
used for the probing?

Alternatively, could the probing be done without constructing a QApplication
instance (maybe by using other libraries)?

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

[krita] [Bug 458882] Menu Bar display only if executed as root (sudo/su)

[beojan]

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

beojan  changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #14 from beojan  ---
> dbus has big problems if a process creates two QApplication objects. It
> somehow latches onto the first one. And we cannot work around that, we have
> to have this probing QApplication instance. 
> 
> I don't think we can do anything about this from within Krita :-(

Why can't the global `KisApplication::instance()` be used instead of creating
an additional QApplication instance?

The Qt documentation contains this sentence as part of the QApplication
reference:

> For any GUI application using Qt, there is precisely one QApplication object, 
> no matter whether the application has 0, 1, 2 or more windows at any given 
> time.

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

[kscreenlocker] [Bug 454706] 8dbec4a153be35bcab4a1877ee524a7cbcb72e84 inappropriately shows the user the "no password unlock" screen after they supply their fingerprint

[beojan]

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

beojan  changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #5 from beojan  ---
For me the Unlock button then doesn't work, leaving me unable to unlock my
session.

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

[plasmashell] [Bug 423938] Drag and Drop files from task manager

[beojan]

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

--- Comment #5 from beojan  ---
That sounds close, though perhaps the proxy icon could also be shown in the
full task manager. That way, you don't need to restore the window before
dragging from it.

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

[plasmashell] [Bug 423938] Drag and Drop files from task manager

[beojan]

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

beojan  changed:

   What|Removed |Added

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

--- Comment #3 from beojan  ---
While the Task Manager shows applications and windows, these will often have
some file open. When this is the case (e.g. with Okular, or Calligra), dragging
and dropping from the Task Manager would drop the document open in that window.

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

[plasmashell] [Bug 423938] New: Drag and Drop files from task manager

[beojan]

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

Bug ID: 423938
   Summary: Drag and Drop files from task manager
   Product: plasmashell
   Version: 5.19.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: beo...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

It would be nice to be able to drag and drop open files from the task manager.
I'm thinking in particular of attaching an open PDF or photo to an email, or a
web form.

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

[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled

[beojan]

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

beojan  changed:

   What|Removed |Added

Version|5.12.5  |5.18.5

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

[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled

[beojan]

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

beojan  changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #11 from beojan  ---
I'm experiencing the same issue with kwin_x11 5.18.5. It persists even with
"Allow applications to block compositing" switched off.

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

[krita] [Bug 408015] Global menu doesn't work

[beojan]

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

--- Comment #45 from beojan  ---
The Plasma QPA loaded into Krita uses DBus to communicate with the Plasmoid (/
service).

Does fcitx interfere with dbus in other applications.

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

[krita] [Bug 408015] Global menu doesn't work

[beojan]

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

--- Comment #13 from beojan  ---
It's definitely the DBus issue because that's how the global menu plasmoid
communicates with the application.

Rather, there's a bug in the Plasma QPA (or in how the QPA interacts with
Krita) that must be causing the DBus problem.

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

[krita] [Bug 408015] Global menu doesn't work

[beojan]

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

--- Comment #5 from beojan  ---
The problem is that Krita's connection to the DBus session bus is suspended
when it's opened. This is probably due to this commit in Qt:
https://git.merproject.org/mer-core/qtbase/commit/1f6fa1f37a14742ddf53c753ce52d9dc048cd1dc?view=parallel
(sorry, not on Qt's own git repository because that doesn't come up in a Google
search).

In Krita, delivery isn't being unsuspended when the event loop starts. It looks
like Krita creates throwaway QApplication instances while starting up, so
perhaps this is connected to that.

This also means nothing that connects to Krita via DBus actually works.

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

[krita] [Bug 408015] Global menu doesn't work

[beojan]

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

beojan  changed:

   What|Removed |Added

 CC||beo...@gmail.com

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

[krita] [Bug 407219] No menu with global menu enabled

[beojan]

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

beojan  changed:

   What|Removed |Added

   Target Milestone|1.0 |---
  Component|general |General
   Assignee|k...@davidedmundson.co.uk|krita-bugs-n...@kde.org
Product|plasmashell |krita
Version|5.15.4  |git master

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

[plasmashell] [Bug 407219] No menu with global menu enabled

[beojan]

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

--- Comment #2 from beojan  ---
I don't know why the bug exists, but it's definitely a bug in Krita because
other Qt or KDE applications don't exhibit it.

It's a major bug because there is no menu bar *at all*. If it were simply a
case of displaying an in-window menubar, it would be a minor bug, but with no
menu bar *at all*, Krita's functionality is severely limited.

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

[plasmashell] [Bug 407219] No menu with global menu enabled

[beojan]

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

--- Comment #3 from beojan  ---
By the way, the menus work fine in Krita 4.1.8, so this is a regression.

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

[krita] [Bug 407219] New: No menu with global menu enabled

[beojan]

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

Bug ID: 407219
   Summary: No menu with global menu enabled
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

SUMMARY
No menus are shown when a global menu plasmoid is added

STEPS TO REPRODUCE
1. Add a global menu plasmoid to a Plasma panel
2. Open Krita

OBSERVED RESULT
No menubar in the plasmoid, no menubar in Krita

EXPECTED RESULT
A menubar would be displayed in the plasmoid

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.0
(available in About System)
KDE Plasma Version: 5.15
KDE Frameworks Version: 5.57
Qt Version: 5.12

ADDITIONAL INFORMATION

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

[konsole] [Bug 397669] Broken behaviour NerdFont glyphs

[beojan]

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

--- Comment #15 from beojan  ---
By the way, when I said 19.04, I meant Konsole 19.04.

I see what the problem is now. If there are ANSI escape codes between the
character and the space(s), the character is not correctly grouped with the
space(s). Escape codes should therefore probably be ignored when doing this
grouping.

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

[LabPlot2] [Bug 406805] New: Cannot access histograms within a directory structure in a ROOT file

[beojan]

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

Bug ID: 406805
   Summary: Cannot access histograms within a directory structure
in a ROOT file
   Product: LabPlot2
   Version: latest
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: beo...@gmail.com
  Target Milestone: ---

SUMMARY

The CERN ROOT file format supports a directory structure within a file. When a
file with such a structure is opened in the import dialog, only one entry is
shown for each unique histogram name, with no indication of which directory
that histogram is in.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma
(available in About System)
KDE Plasma Version: 5.15.4 
KDE Frameworks Version: 5.57
Qt Version: 5.12

ADDITIONAL INFORMATION

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

[konsole] [Bug 397669] Broken behaviour NerdFont glyphs

[beojan]

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

--- Comment #13 from beojan  ---
I've updated to 19.04, and this still doesn't always work. See the screenshot
above.

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

[konsole] [Bug 397669] Broken behaviour NerdFont glyphs

[beojan]

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

--- Comment #12 from beojan  ---
Created attachment 119551
  --> https://bugs.kde.org/attachment.cgi?id=119551=edit
Screenshot with 19.04

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

[kwin] [Bug 403038] New: KWin crashes (occasionally) when running script to minimize current open window

[beojan]

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

Bug ID: 403038
   Summary: KWin crashes (occasionally) when running script to
minimize current open window
   Product: kwin
   Version: 5.14.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.14.5)

Qt Version: 5.12.0
Frameworks Version: 5.53.0
Operating System: Linux 4.19.12-1-ck x86_64
Distribution: "Arch Linux"

-- Information about the crash:
The script is below:

```
NUM=$(qdbus org.kde.KWin /Scripting org.kde.kwin.Scripting.loadScript
/home/beojan/.local/share/plasmashell/minimize.js Minimize)
qdbus org.kde.KWin /$NUM org.kde.kwin.Scripting.run
qdbus org.kde.KWin /Scripting  org.kde.kwin.Scripting.unloadScript Minimize
```

And the KWin script is:

```
workspace.activeClient.minimized = true;
```

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7f04609ea700 (LWP 8746)):
[KCrash Handler]
#6  0x7f046bc36b60 in QRingBuffer::chop(long long) () at
/usr/lib/libQt5Core.so.5
#7  0x7f046bcc45f2 in QIODevicePrivate::read(char*, long long, bool) () at
/usr/lib/libQt5Core.so.5
#8  0x7f046bcc51fe in QIODevice::readAll() () at /usr/lib/libQt5Core.so.5
#9  0x7f046cfe105f in  () at /usr/lib/libkwin.so.5
#10 0x7f046cfe2341 in  () at /usr/lib/libkwin.so.5
#11 0x7f046bbc39a1 in  () at /usr/lib/libQt5Core.so.5
#12 0x7f046bbbf9cc in  () at /usr/lib/libQt5Core.so.5
#13 0x7f046a9a6a9d in start_thread () at /usr/lib/libpthread.so.0
#14 0x7f046d22cb23 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f0445f38700 (LWP 28495)):
#0  0x7f046a9acafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f046b6a928c in  () at /usr/lib/libQt5Script.so.5
#2  0x7f046b6a92a9 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f046a9a6a9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f046d22cb23 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f0447fff700 (LWP 28493)):
#0  0x7f046a9acafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0458b80c24 in  () at /usr/lib/dri/i965_dri.so
#2  0x7f0458b80948 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f046a9a6a9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f046d22cb23 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f045b4f0700 (LWP 28491)):
#0  0x7f046d221d16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f046bdcd46b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f046bdce94b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f046bd7a58c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f046bbbe5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f046a166b89 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f046bbbf9cc in  () at /usr/lib/libQt5Core.so.5
#7  0x7f046a9a6a9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f046d22cb23 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f04612ee700 (LWP 28413)):
#0  0x7f046d221d16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f046bdcd46b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f046bdce94b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f046bd7a58c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f046bbbe5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f0469bd3ba6 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f046bbbf9cc in  () at /usr/lib/libQt5Core.so.5
#7  0x7f046a9a6a9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f046d22cb23 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f046367b700 (LWP 28412)):
#0  0x7f046d221c21 in poll () at /usr/lib/libc.so.6
#1  0x7f046bae3630 in  () at /usr/lib/libxcb.so.1
#2  0x7f046bae52db in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f0463b7196b in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f046bbbf9cc in  () at /usr/lib/libQt5Core.so.5
#5  0x7f046a9a6a9d in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f046d22cb23 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f0463fe7840 (LWP 28362)):
#0  0x7f046a9acafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f046bae383b in  () at /usr/lib/libxcb.so.1
#2  0x7f046bae4fef in  () at /usr/lib/libxcb.so.1
#3  0x7f046bae5103 in xcb_wait_for_reply () at /us

[konsole] [Bug 397669] Broken behaviour NerdFont glyphs

[beojan]

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

beojan  changed:

   What|Removed |Added

Version|18.08.0 |18.12.0

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

[konsole] [Bug 397669] Broken behaviour NerdFont glyphs

[beojan]

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

beojan  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||beo...@gmail.com
 Ever confirmed|0   |1

--- Comment #5 from beojan  ---
It seems this is still broken in 18.12.

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

[QtCurve] [Bug 365348] Qt Quick Controls Combobox popup is unreadable

[beojan]

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

--- Comment #1 from beojan  ---
Created attachment 116544
  --> https://bugs.kde.org/attachment.cgi?id=116544=edit
Patch to "fix" issue

Draws the panel like a popup menu. I couldn't use draw it like the standard
combobox popup because that code explicitly checks that the parent is a combo
box.

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

[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5

[beojan]

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

--- Comment #20 from beojan  ---
Is the background colour still exported as a property so the decoration can
pick it up?

I'd at least like to modify Breeze so it can pick up the QtCurve background
colour.

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

[latte-dock] [Bug 401260] Can't add Window Appmenu or Global Menu to panel

[beojan]

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

--- Comment #7 from beojan  ---
I finally got it added, though it took many tries.

On the desktop, you can double click a widget in the sidebar to add it. Perhaps
you could implement that in Latte?

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

[latte-dock] [Bug 401260] Can't add Window Appmenu or Global Menu to panel

[beojan]

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

--- Comment #6 from beojan  ---
(In reply to beojan from comment #5)
> Maybe because I'm using Plasma 5.13?

Actually, no, I'm using 5.14.3

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

[latte-dock] [Bug 401260] Can't add Window Appmenu or Global Menu to panel

[beojan]

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

--- Comment #5 from beojan  ---
Maybe because I'm using Plasma 5.13?

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

[latte-dock] [Bug 401260] Can't add Window Appmenu or Global Menu to panel

[beojan]

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

--- Comment #2 from beojan  ---
No, and if I go into Dock/Panel Settings, the applet doesn't appear when I
mouse along the panel.

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

[latte-dock] [Bug 401260] New: Can't add Window Appmenu or Global Menu to panel

[beojan]

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

Bug ID: 401260
   Summary: Can't add Window Appmenu or Global Menu to panel
   Product: latte-dock
   Version: git (master)
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: containment
  Assignee: mvourla...@gmail.com
  Reporter: beo...@gmail.com
  Target Milestone: ---

I don't seem to be able to add Window Appmenu or the default global menu to a
Latte panel.
Possibly because the desktop has no menu, so these applets are zero width when
added.

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

[kscreenlocker] [Bug 398963] Background disappears instead of blurring

[beojan]

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

--- Comment #1 from beojan  ---
It appears this only happens with dark backgrounds, because the blur is very
strong and has a grey overlay.

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

[kscreenlocker] [Bug 398963] New: Background disappears instead of blurring

[beojan]

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

Bug ID: 398963
   Summary: Background disappears instead of blurring
   Product: kscreenlocker
   Version: 5.10.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: breeze-theme
  Assignee: plasma-b...@kde.org
  Reporter: beo...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

When the mouse is moved to activate the controls on the lock screen, instead of
blurring, the background fades to black.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #64 from beojan <beo...@gmail.com> ---
I noticed that years ago. It seems to be because it forces a redraw and
apparently follows a different code path.

On Thu, Apr 26, 2018, 11:01 Antonio Orefice <bugzilla_nore...@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=355935
>
> --- Comment #63 from Antonio Orefice <kokok...@gmail.com> ---
> I noticed another interesting behaviour.
> When kerning looks bad, if i open font configuration and change anything
> related to the font used for the desktop (General font), it looks nice.
> I mean, not only changing font family and back, but even font size, or
> "effects", like strikeout or underline.
> Don't know if it helps anyhow.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #61 from beojan <beo...@gmail.com> ---
It actually seems fixed (or a lot better, at least) with QQC2.

On Wed, Apr 25, 2018, 04:05 Filip <bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=355935
>
> --- Comment #60 from Filip <tyx...@gmail.com> ---
> I think what happened was I made a mistake when testing both modes and
> misreported that it happens with QtRendering as well. Either way it would
> be
> more logical to solve it upstream.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kmail2] [Bug 391419] KMail does not remember UI changes

[beojan]

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

--- Comment #2 from beojan <beo...@gmail.com> ---
Not entirely a duplicate, I'm afraid. The status column issue existed before Qt
5.10.

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

[kmail2] [Bug 391419] New: KMail does not remember UI changes

[beojan]

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

Bug ID: 391419
   Summary: KMail does not remember UI changes
   Product: kmail2
   Version: 5.7.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

After a log out cycle, KMail doesn't remember UI changes (e.g. removing the
Unread, Total, and Size column in the folder list, or resizing the status
column in the message list).

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #57 from beojan <beo...@gmail.com> ---
To reiterate, this *is* a Qt bug, but it probably won't be fixed soon. Unless
there's a reason for using NativeRendering in Plasma, simply switching to
QtRendering would fix the issue for Plasma.

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

[kmail2] [Bug 390075] New: Links that require login don't work

[beojan]

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

Bug ID: 390075
   Summary: Links that require login don't work
   Product: kmail2
   Version: 5.7.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

When clicking a link to a page that requires logging in, I receive a 403 error
or am redirected to the home page. Right clicking and copy-pasting the URL
works.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #56 from beojan <beo...@gmail.com> ---
Is there any way we could switch Plasma to use QtRendering instead of
NativeRendering?

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

[kwin] [Bug 387938] Compositing turned off on unlock

[beojan]

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

--- Comment #6 from beojan <beo...@gmail.com> ---
(In reply to Martin Flöser from comment #5)
> Sorry, but that's impossible. We don't have any code to open that dialog.

Well that's what happens.

It appears this may be linked to using an additional external display on a
laptop, since I don't experience the issue when not using such a display.

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

[kwin] [Bug 387938] Compositing turned off on unlock

[beojan]

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

--- Comment #4 from beojan <beo...@gmail.com> ---
It opened automatically.

On Dec 19, 2017 15:39, "Martin Flöser" <bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=387938
>
> --- Comment #3 from Martin Flöser <mgraess...@kde.org> ---
> But you opened that dialog, right? It did not open automatically?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kwin] [Bug 387938] Compositing turned off on unlock

[beojan]

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

--- Comment #2 from beojan <beo...@gmail.com> ---
(In reply to Martin Flöser from comment #1)
> Which config dialog is open?

The Compositor config dialog (Display and Monitor -> Compositor in System
Settings).

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

[kwin] [Bug 387938] New: Compositing turned off on unlock

[beojan]

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

Bug ID: 387938
   Summary: Compositing turned off on unlock
   Product: kwin
   Version: 5.11.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

Upon unlocking the screen, compositing gets turned off, and the config dialog
is open. If compositing is turned on again, KWin glitches until it is restarted
(kwin_x11 --replace).

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

[QtCurve] [Bug 387795] error: ‘Q_FALLTHROUGH’ was not declared in this scope

[beojan]

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

--- Comment #3 from beojan <beo...@gmail.com> ---
It turns out it's because it's a symlink to the qt5 version.

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

[QtCurve] [Bug 387795] error: ‘Q_FALLTHROUGH’ was not declared in this scope

[beojan]

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

--- Comment #2 from beojan <beo...@gmail.com> ---
Yes, it is. qt4/common/common.cpp line 242.

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

[QtCurve] [Bug 387795] error: ‘Q_FALLTHROUGH’ was not declared in this scope

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

Version|unspecified |git
   Severity|normal  |major

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

[QtCurve] [Bug 387795] New: error: ‘Q_FALLTHROUGH’ was not declared in this scope

[beojan]

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

Bug ID: 387795
   Summary: error: ‘Q_FALLTHROUGH’ was not declared in this scope
   Product: QtCurve
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: qt4
  Assignee: yyc1...@gmail.com
  Reporter: beo...@gmail.com
CC: h...@kde.org
  Target Milestone: ---

Q_FALLTHROUGH was only introduced in Qt 5.8, so it shouldn't be used in the Qt
4 version.

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

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

--- Comment #16 from beojan <beo...@gmail.com> ---
Yes, the QtCurve settings dialog is definitely doing this (specifically, it has
an MDI preview window which has a menu).

The easiest solution would be to leave MDI child window menus in the child
window. Perhaps they could be moved to the global menu iff the parent window
has no menu of its own, but I wouldn't try to combine the two menus.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #53 from beojan <beo...@gmail.com> ---
(In reply to Filip from comment #50)
> Ha, with both actually, yeah, although it's a bit worse with NativeRendering.

I take it you tried the QML file I posted? If so, could you comment on the Qt
bug, since they are clearly the ones who have to fix this.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #48 from beojan <beo...@gmail.com> ---
I see it in the spacing in the labels for "Sorting: " and "Grouping: ".

I commented out the Plasma core library in that file, so it does indeed show
this is a Qt bug.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #46 from beojan <beo...@gmail.com> ---
Created attachment 108399
  --> https://bugs.kde.org/attachment.cgi?id=108399=edit
Test QML file

I've modified the config dialog qml file for the task manager to remove all
Plasma components, and I still see the bug. 

Can the others that see this bug please confirm if it appears with this QML
file (run it with qmlscene)?

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #43 from beojan <beo...@gmail.com> ---
(In reply to Nate Graham from comment #41)
> Does this manifest *only* when using Adapta, even if everything else is set
> up as you indicate (e.g. when using the Cantarell font with no hinting)?

It appears in Plasma shell even if Breeze is used as the windeco. It appears in
the windeco with any Aurorae theme. Aurorae uses the Plasma library to draw the
decoration.

In plasma shell, it even appears in widget configuration dialogs.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #38 from beojan <beo...@gmail.com> ---
Here's the old Qt4 bug: https://bugreports.qt.io/browse/QTBUG-27257

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #37 from beojan <beo...@gmail.com> ---
(In reply to Jens Reuterberg from comment #35)
> The only way this is related to QML, Qt or Plasma is if we somehow force a
> wider gap between upper and lower case letters in the example provided (H
> and i). 

Back in the Qt4 / KDE 4 days, there was a similar bug in all Qt applications if
you used the native (X11) backend. If you switched to the raster backend, that
bug disappeared (but Plasma widgets were no longer anti-aliased). It was closed
because the native backend was deprecated, so we can't see how it was fixed.

> I don't understand why we would or why that would be visible only in a few
> fonts. 
> 
It's visible in all fonts. Some fonts just have a design which makes bad
kerning less noticeable. 

I suspect changing the font setting in System Settings triggers a redraw which
renders text on a different code path, which is why the issue disappears if you
change the font in System Settings, then change it back to the original.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #25 from beojan <beo...@gmail.com> ---
In fact, it turns out the Aurorae KWin theme uses QML components from Plasma
(specifically Plasma core), so this probably *is* a Plasma bug, rather than a
Qt bug.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

Version|5.9.5   |5.11.0

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #24 from beojan <beo...@gmail.com> ---
Yes, you'll see I reported this to the Qt bug tracker above. However, there
seems to be something about the way Plasma and Leon (really Aurorae) uses Qt
that triggers this, so the investigation needs to start with Plasma.

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

--- Comment #22 from beojan <beo...@gmail.com> ---
Created attachment 108321
  --> https://bugs.kde.org/attachment.cgi?id=108321=edit
New screenshot

Here's another screenshot demonstrating this bug on Plasma. Given the comment
above, it's possible the bug is at a deeper level (something shared between
KWin and Plasma, perhaps).

I'm using Intel integrated graphics on a 4700MQ processor, 1920x1080 using X11.

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

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

[beojan]

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

--- Comment #6 from beojan <beo...@gmail.com> ---
Plasma uses the old Ubuntu global menu protocol, which GNOME *deliberately*
broke compatibility with.

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

[calligracommon] [Bug 323143] Backspace behaves unintuitively in Tamil keyboard layout

[beojan]

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

--- Comment #11 from beojan <beo...@gmail.com> ---
In fact, there's an easy way for anyone to reproduce this without knowing
Tamil. The bug is in how Unicode combining characters are handled.

Here is a Unicode combining acute accent:  ́
Here is an 'e' followed by the above character: é

Type an e in your chosen application, then copy and paste the acute accent from
above. If you then press backspace, only the accent should be deleted. If the
bug is present, the e will also be deleted.

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

[calligracommon] [Bug 323143] Backspace behaves unintuitively in Tamil keyboard layout

[beojan]

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

--- Comment #10 from beojan <beo...@gmail.com> ---
QtCreator doesn't exhibit this bug, neither does VLC. KWrite (17.04) does.

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

[plasmashell] [Bug 375535] Global Menu Bar widget does not open menus on hover

[beojan]

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

--- Comment #12 from beojan <beo...@gmail.com> ---
If this isn't fixed for you, see the replacement QML file I posted on bug
376725 (which is really a duplicate of this one).

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

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

--- Comment #10 from beojan <beo...@gmail.com> ---
My guess is there are multiple bugs here.

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

[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5

[beojan]

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

--- Comment #15 from beojan <beo...@gmail.com> ---
Yes, it's still under development. No one seems to care about the deco right
now though.

Once you've customized your QtCurve config, you could just make an Aurorae
style to go with it.

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

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

--- Comment #8 from beojan <beo...@gmail.com> ---
*** Bug 378788 has been marked as a duplicate of this bug. ***

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

[QtCurve] [Bug 378788] Opening QtCurve settings crashes System Settings if global menu is enabled

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from beojan <beo...@gmail.com> ---


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

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

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #7 from beojan <beo...@gmail.com> ---
Here's the new backtrace with debug symbols enabled:

Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcd1fa627c0 (LWP 26324))]

Thread 3 (Thread 0x7fccfe73a700 (LWP 26327)):
#0  0x7fcd1b72937d in read () from /usr/lib/libc.so.6
#1  0x7fcd13b4de20 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fcd13b0947e in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7fcd13b09954 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7fcd13b09acc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7fcd1c05610b in QEventDispatcherGlib::processEvents
(this=0x7fccf80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fcd1bfff93a in QEventLoop::exec (this=this@entry=0x7fccfe739dc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fcd1be21ae3 in QThread::exec (this=this@entry=0x7fcd1cbe0d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#8  0x7fcd1c96c835 in QDBusConnectionManager::run (this=0x7fcd1cbe0d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:170
#9  0x7fcd1be26748 in QThreadPrivate::start (arg=0x7fcd1cbe0d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#10 0x7fcd177662e7 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7fcd1b73754f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fcd0cb75700 (LWP 26326)):
#0  0x7fcd1b72d67d in poll () from /usr/lib/libc.so.6
#1  0x7fcd17fea8e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fcd17fec679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fcd0f70b9f9 in QXcbEventReader::run (this=0x12bb020) at
qxcbconnection.cpp:1345
#4  0x7fcd1be26748 in QThreadPrivate::start (arg=0x12bb020) at
thread/qthread_unix.cpp:368
#5  0x7fcd177662e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fcd1b73754f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fcd1fa627c0 (LWP 26324)):
[KCrash Handler]
#6  0x7fcd1d403764 in QFlags::operator& (f=,
this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:142
#7  QWindow::type (this=this@entry=0x1ad92e0) at kernel/qwindow.cpp:826
#8  0x7fcd1d408dd2 in QWindow::winId (this=0x1ad92e0) at
kernel/qwindow.cpp:599
#9  0x7fcd0756dfd3 in QDBusMenuBar::unregisterMenuBar (this=0x1ad8f00) at
/home/beojan/SRC/ABS/extra/plasma-integration/src/plasma-integration-5.9.5/src/platformtheme/qdbusmenubar.cpp:222
#10 0x7fcd0756d989 in QDBusMenuBar::handleReparent (this=0x1ad8f00,
newParentWindow=0x17c6df0) at
/home/beojan/SRC/ABS/extra/plasma-integration/src/plasma-integration-5.9.5/src/platformtheme/qdbusmenubar.cpp:171
#11 0x7fcd1dd14dbc in QMenuBarPrivate::handleReparent
(this=this@entry=0x1ad8b00) at widgets/qmenubar.cpp:1362
#12 0x7fcd1dd15a95 in QMenuBar::eventFilter (this=0x1ad87f0,
object=0x1abdf70, event=0x7fffd5e18b00) at widgets/qmenubar.cpp:1462
#13 0x7fcd1c001241 in
QCoreApplicationPrivate::sendThroughObjectEventFilters
(receiver=receiver@entry=0x1abdf70, event=event@entry=0x7fffd5e18b00) at
kernel/qcoreapplication.cpp:1099
#14 0x7fcd1db983b5 in QApplicationPrivate::notify_helper (this=, receiver=0x1abdf70, e=0x7fffd5e18b00) at kernel/qapplication.cpp:3741
#15 0x7fcd1db9fbf1 in QApplication::notify (this=0x7fffd5e1acb0,
receiver=0x1abdf70, e=0x7fffd5e18b00) at kernel/qapplication.cpp:3502
#16 0x7fcd1c0014e0 in QCoreApplication::notifyInternal2
(receiver=receiver@entry=0x1abdf70, event=event@entry=0x7fffd5e18b00) at
kernel/qcoreapplication.cpp:988
#17 0x7fcd1dbe0eb6 in QCoreApplication::sendEvent (event=0x7fffd5e18b00,
receiver=0x1abdf70) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QWidget::setParent (this=this@entry=0x1abdf70,
parent=parent@entry=0x1b21cb0, f=...) at kernel/qwidget.cpp:10597
#19 0x7fcd1dbe1c4c in QWidget::setParent (this=this@entry=0x1abdf70,
parent=parent@entry=0x1b21cb0) at kernel/qwidget.cpp:10451
#20 0x7fcd1dbbb9b6 in QLayout::addChildWidget (this=this@entry=0x1b195e0,
w=w@entry=0x1abdf70) at kernel/qlayout.cpp:926
#21 0x7fcd1dbbba2f in QLayout::addWidget (this=0x1b195e0, w=0x1abdf70) at
kernel/qlayout.cpp:226
#22 0x7fcd1dcfb7bc in QMdiSubWindow::setWidget (this=this@entry=0x1b21cb0,
widget=widget@entry=0x1abdf70) at widgets/qmdisubwindow.cpp:2330
#23 0x7fcd1dcef8e3 in QMdiArea::addSubWindow (this=,
w

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

--- Comment #6 from beojan <beo...@gmail.com> ---
(In reply to Martin Flöser from comment #5)
> I'm sorry, as I do not know your distribution and do not know how exactly
> you are building I cannot provide any help.

I'm literally building from the plasma-integration tarball with CMake.

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

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

--- Comment #4 from beojan <beo...@gmail.com> ---
(In reply to Martin Flöser from comment #3)
> > There's still no debug information in KDEPlasmaPlatformTheme, but I built 
> > it in the debug configuration so I don't know why that is.
> 
> That would be the interesting part unfortunately. It's the only part in our
> code.

Can you give me instructions on how to build it with debug symbols? Setting
CMAKE_BUILD_TYPE to Debug is apparently not enough.

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

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

--- Comment #2 from beojan <beo...@gmail.com> ---
(In reply to Martin Flöser from comment #1)
> Unfortunately the backtrace is lacking debug symbols. We see it crashes, but
> not where. If you are able to reproduce, please install debug packages and
> attach an updated backtrace.

Here:

Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f022482c7c0 (LWP 27861))]

Thread 3 (Thread 0x7f0203ba8700 (LWP 27864)):
#0  0x7f02189191c9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7f02188d38b0 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f02188d3acc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f0220e2010b in QEventDispatcherGlib::processEvents
(this=0x7f01fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f0220dc993a in QEventLoop::exec (this=this@entry=0x7f0203ba7dc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f0220bebae3 in QThread::exec (this=this@entry=0x7f02219aad60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7f0221736835 in QDBusConnectionManager::run (this=0x7f02219aad60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:170
#7  0x7f0220bf0748 in QThreadPrivate::start (arg=0x7f02219aad60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#8  0x7f021c5302e7 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f022050154f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f021193f700 (LWP 27863)):
#0  0x7f02204f767d in poll () from /usr/lib/libc.so.6
#1  0x7f021cdb48e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f021cdb6679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f02144d59f9 in QXcbEventReader::run (this=0x1dbc020) at
qxcbconnection.cpp:1345
#4  0x7f0220bf0748 in QThreadPrivate::start (arg=0x1dbc020) at
thread/qthread_unix.cpp:368
#5  0x7f021c5302e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f022050154f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f022482c7c0 (LWP 27861)):
[KCrash Handler]
#6  0x7f02221cd764 in QFlags::operator& (f=,
this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:142
#7  QWindow::type (this=this@entry=0x25d9840) at kernel/qwindow.cpp:826
#8  0x7f02221d2dd2 in QWindow::winId (this=0x25d9840) at
kernel/qwindow.cpp:599
#9  0x7f02104b40a4 in ?? () from
/usr/lib/qt/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#10 0x7f02104b46fd in ?? () from
/usr/lib/qt/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#11 0x7f0222adedbc in QMenuBarPrivate::handleReparent
(this=this@entry=0x25d9120) at widgets/qmenubar.cpp:1362
#12 0x7f0222adfa95 in QMenuBar::eventFilter (this=0x25d6100,
object=0x25bd730, event=0x7ffd09bd3a00) at widgets/qmenubar.cpp:1462
#13 0x7f0220dcb241 in
QCoreApplicationPrivate::sendThroughObjectEventFilters
(receiver=receiver@entry=0x25bd730, event=event@entry=0x7ffd09bd3a00) at
kernel/qcoreapplication.cpp:1099
#14 0x7f02229623b5 in QApplicationPrivate::notify_helper (this=, receiver=0x25bd730, e=0x7ffd09bd3a00) at kernel/qapplication.cpp:3741
#15 0x7f0222969bf1 in QApplication::notify (this=0x7ffd09bd5bb0,
receiver=0x25bd730, e=0x7ffd09bd3a00) at kernel/qapplication.cpp:3502
#16 0x7f0220dcb4e0 in QCoreApplication::notifyInternal2
(receiver=receiver@entry=0x25bd730, event=event@entry=0x7ffd09bd3a00) at
kernel/qcoreapplication.cpp:988
#17 0x7f02229aaeb6 in QCoreApplication::sendEvent (event=0x7ffd09bd3a00,
receiver=0x25bd730) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QWidget::setParent (this=this@entry=0x25bd730,
parent=parent@entry=0x2624c20, f=...) at kernel/qwidget.cpp:10597
#19 0x7f02229abc4c in QWidget::setParent (this=this@entry=0x25bd730,
parent=parent@entry=0x2624c20) at kernel/qwidget.cpp:10451
#20 0x7f02229859b6 in QLayout::addChildWidget (this=this@entry=0x2622c40,
w=w@entry=0x25bd730) at kernel/qlayout.cpp:926
#21 0x7f0222985a2f in QLayout::addWidget (this=0x2622c40, w=0x25bd730) at
kernel/qlayout.cpp:226
#22 0x7f0222ac57bc in QMdiSubWindow::setWidget (this=this@entry=0x2624c20,
widget=widget@entry=0x25bd730) at widgets/qmdisubwindow.cpp:2330
#23 0x7f0222ab98e3 in QMdiArea::addSubWindow (this=,
widget=0x25bd730, windowFlags=...) at widgets/qmdiarea.cpp:1989
#24 0x7f01f9cc3f4d in QtCurveConfig::previewControlPressed() () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#25 0x7f01f9cc4069 in QtCurveConfig::setupPreview() () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#26 0x7f01f9ccf7b5 in QtCurveConfig::QtCurveConfig(QWidget*) () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#27 0x7f01f9ccf85

[plasmashell] [Bug 376725] Global menu doesn't respond to mouse hover

[beojan]

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

--- Comment #7 from beojan <beo...@gmail.com> ---
Created attachment 105444
  --> https://bugs.kde.org/attachment.cgi?id=105444=edit
qml replacement

Moving the Connections object to the root in
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/ui/main.qml fixes
this. You can use the attached file as a replacement, though it has a couple of
other changes (removing the underlining, and reducing the spacing between
menus).

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

[QtCurve] [Bug 376340] QtCurve style configure dialog crashes

[beojan]

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

--- Comment #11 from beojan <beo...@gmail.com> ---
OK, I think the bug is really in plasma-integration. I've reported it as bug
379719 (https://bugs.kde.org/show_bug.cgi?id=379719).

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

[plasmashell] [Bug 355935] Font kerning is incorrect

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

Version|5.8.0   |5.9.5

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

[plasma-integration] [Bug 379719] New: KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

Bug ID: 379719
   Summary: KDEPlasmaPlatformTheme causes a crash if an MDI Window
with a menubar is created with the global menu enabled
   Product: plasma-integration
   Version: 5.9.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

This manifests as System Settings crashing when the QtCurve config is opened:

```
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc9a18d9500 (LWP 19327))]

Thread 3 (Thread 0x7fc980ed8700 (LWP 19330)):
#0  0x7fc99d5a867d in poll () from /usr/lib/libc.so.6
#1  0x7fc9976989b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fc997698acc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fc99decf09b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fc99de788ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fc99dc9aa73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fc99e7e6125 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7fc99dc9f6d8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fc9995e02e7 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fc99d5b254f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fc98ebf1700 (LWP 19329)):
#0  0x7fc99d5a867d in poll () from /usr/lib/libc.so.6
#1  0x7fc999e648e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fc999e66679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fc991788239 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fc99dc9f6d8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fc9995e02e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fc99d5b254f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fc9a18d9500 (LWP 19327)):
[KCrash Handler]
#6  0x7fc99f27b724 in QWindow::type() const () from /usr/lib/libQt5Gui.so.5
#7  0x7fc99f280d92 in QWindow::winId() const () from
/usr/lib/libQt5Gui.so.5
#8  0x7fc98d7670a4 in ?? () from
/usr/lib/qt/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#9  0x7fc98d7676fd in ?? () from
/usr/lib/qt/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#10 0x7fc99fb87d2c in ?? () from /usr/lib/libQt5Widgets.so.5
#11 0x7fc99fb88a05 in QMenuBar::eventFilter(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#12 0x7fc99de7a1d1 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#13 0x7fc99fa0b325 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#14 0x7fc99fa12b61 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#15 0x7fc99de7a470 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#16 0x7fc99fa53e26 in QWidget::setParent(QWidget*, QFlags)
() from /usr/lib/libQt5Widgets.so.5
#17 0x7fc99fa54bbc in QWidget::setParent(QWidget*) () from
/usr/lib/libQt5Widgets.so.5
#18 0x7fc99fa2e926 in QLayout::addChildWidget(QWidget*) () from
/usr/lib/libQt5Widgets.so.5
#19 0x7fc99fa2e99f in QLayout::addWidget(QWidget*) () from
/usr/lib/libQt5Widgets.so.5
#20 0x7fc99fb6e72c in QMdiSubWindow::setWidget(QWidget*) () from
/usr/lib/libQt5Widgets.so.5
#21 0x7fc99fb62853 in QMdiArea::addSubWindow(QWidget*,
QFlags) () from /usr/lib/libQt5Widgets.so.5
#22 0x7fc977023f4d in QtCurveConfig::previewControlPressed() () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#23 0x7fc977024069 in QtCurveConfig::setupPreview() () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#24 0x7fc97702f7b5 in QtCurveConfig::QtCurveConfig(QWidget*) () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#25 0x7fc97702f851 in allocate_kstyle_config () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#26 0x7fc9772acdaf in ?? () from /usr/lib/qt/plugins/kcm_style.so
#27 0x7fc99dea60ee in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#28 0x7fc99faf3d02 in QAbstractButton::clicked(bool) () from
/usr/lib/libQt5Widgets.so.5
#29 0x7fc99faf3f54 in ?? () from /usr/lib/libQt5Widgets.so.5
#30 0x7fc99faf5347 in ?? () from /usr/lib/libQt5Widgets.so.5
#31 0x7fc99faf5524 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /usr/lib/libQt5Widgets.so.5
#32 0x7fc99fa52cd8 in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#33 0x7fc99fa0b34c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#34 0x7fc99fa138c5 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#35 

[plasmashell] [Bug 376725] Global menu doesn't respond to mouse hover

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #6 from beojan <beo...@gmail.com> ---
I don't think this is a simple glitch. If you open a menu under X11, you'll
find that hover events don't get passed through to other windows unless you
click to close the window first (this click also doesn't get passed through, of
course). The only exception is in a menubar, where hovers *do* get passed
through so this switching behaviour can be implemented. The global menu applet
isn't *really* a menubar, so this doesn't work here.

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

[kactivitymanagerd] [Bug 377353] Crash on login while using "QtCurve".

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #3 from beojan <beo...@gmail.com> ---
Similar crash. Here's my backtrace

Application: kactivitymanagerd (kactivitymanagerd), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa8eef344c0 (LWP 1833))]

Thread 2 (Thread 0x7fa8e20bb700 (LWP 1837)):
#0  0x7fa8ec7de67d in poll () from /usr/lib/libc.so.6
#1  0x7fa8ebf9c8e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fa8ebf9e679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fa8e4c519e9 in QXcbEventReader::run (this=0x1cae2f0) at
qxcbconnection.cpp:1345
#4  0x7fa8eced76b8 in QThreadPrivate::start (arg=0x1cae2f0) at
thread/qthread_unix.cpp:368
#5  0x7fa8eb4392e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fa8ec7e854f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fa8eef344c0 (LWP 1833)):
[KCrash Handler]
#6  std::__atomic_base<QMutexData*>::compare_exchange_strong
(__m2=std::memory_order_acquire, __m1=std::memory_order_acquire,
__p2=, __p1=@0x7ffd9e5e1d08: 0x0, this=0x20) at
/usr/include/c++/6.3.1/bits/atomic_base.h:752
#7  std::atomic<QMutexData*>::compare_exchange_strong
(__m2=std::memory_order_acquire, __m1=std::memory_order_acquire,
__p2=, __p1=@0x7ffd9e5e1d08: 0x0, this=0x20) at
/usr/include/c++/6.3.1/atomic:466
#8  QAtomicOps<QMutexData*>::testAndSetAcquire<QMutexData*>
(currentValue=, newValue=, expectedValue=0x0,
_q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:290
#9  QBasicAtomicPointer::testAndSetAcquire (currentValue=: , newValue=, expectedValue=0x0,
this=0x20) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:262
#10 QBasicMutex::fastTryLock (current=: ,
this=0x20) at thread/qmutex.h:101
#11 QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:224
#12 0x7fa8eda1cab7 in QMutexLocker::QMutexLocker (m=0x20, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:199
#13 QDBusConnectionManager::busConnection (this=0x0,
type=type@entry=QDBusConnection::SessionBus) at qdbusconnection.cpp:105
#14 0x7fa8eda1db7c in QDBusConnection::sessionBus () at
qdbusconnection.cpp:1169
#15 0x7fa8d5097956 in QtCurve::Style::disconnectDBus() () from
/usr/lib/qt/plugins/styles/qtcurve.so
#16 0x7fa8d50d5236 in QtCurve::StylePlugin::~StylePlugin() () from
/usr/lib/qt/plugins/styles/qtcurve.so
#17 0x7fa8ed0a65b9 in QLibraryPrivate::unload (this=this@entry=0x1d081a0,
flag=flag@entry=QLibraryPrivate::UnloadSys) at plugin/qlibrary.cpp:562
#18 0x7fa8ed09c252 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x1d012d0, __in_chrg=) at plugin/qfactoryloader.cpp:86
#19 0x7fa8ed09c379 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x1d012d0, __in_chrg=) at plugin/qfactoryloader.cpp:89
#20 0x7fa8ed0e4fd7 in QScopedPointerDeleter::cleanup
(pointer=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60
#21 QScopedPointer<QObjectData, QScopedPointerDeleter
>::~QScopedPointer (this=0x7fa8ee4ef858 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder+8>, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107
#22 QObject::~QObject (this=, __in_chrg=) at
kernel/qobject.cpp:900
#23 0x7fa8ed09b7ae in QFactoryLoader::~QFactoryLoader (this=0x7fa8ee4ef850
<(anonymous namespace)::Q_QGS_loader::innerFunction()::holder>,
__in_chrg=) at plugin/qfactoryloader.cpp:211
#24 0x7fa8ede5b389 in (anonymous namespace)::Q_QGS_loader::Holder::~Holder
(this=, __in_chrg=) at
styles/qstylefactory.cpp:66
#25 0x7fa8ec7326c0 in __run_exit_handlers () from /usr/lib/libc.so.6
#26 0x7fa8ec73271a in exit () from /usr/lib/libc.so.6
#27 0x7fa8eeba485f in
KDBusService::KDBusService(QFlags, QObject*) ()
from /usr/lib/libKF5DBusAddons.so.5
#28 0x00408e54 in ?? ()
#29 0x7fa8ec71c511 in __libc_start_main () from /usr/lib/libc.so.6
#30 0x004090ea in _start ()

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

[QtCurve] [Bug 378788] New: Opening QtCurve settings crashes System Settings if global menu is enabled

[beojan]

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

Bug ID: 378788
   Summary: Opening QtCurve settings crashes System Settings if
global menu is enabled
   Product: QtCurve
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: yyc1...@gmail.com
  Reporter: beo...@gmail.com
CC: h...@kde.org
  Target Milestone: ---

Opening QtCurve's settings crashes System Settings if the global menu is in
use.

Backtrace:

Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f30a41a57c0 (LWP 30187))]

Thread 3 (Thread 0x7f308367a700 (LWP 30190)):
#0  0x7f309fe7367d in poll () from /usr/lib/libc.so.6
#1  0x7f309826f7a6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f309826f8bc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f30a079b24b in QEventDispatcherGlib::processEvents
(this=0x7f307c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f30a0744b5a in QEventLoop::exec (this=this@entry=0x7f3083679dc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f30a0567a93 in QThread::exec (this=this@entry=0x7f30a1325d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7f30a10b1835 in QDBusConnectionManager::run (this=0x7f30a1325d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:170
#7  0x7f30a056c6b8 in QThreadPrivate::start (arg=0x7f30a1325d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#8  0x7f309beab2e7 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f309fe7d54f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f30912d0700 (LWP 30189)):
#0  0x7f309fe7367d in poll () from /usr/lib/libc.so.6
#1  0x7f309c72f8e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f309c731679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f3093e669e9 in QXcbEventReader::run (this=0xe25020) at
qxcbconnection.cpp:1345
#4  0x7f30a056c6b8 in QThreadPrivate::start (arg=0xe25020) at
thread/qthread_unix.cpp:368
#5  0x7f309beab2e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f309fe7d54f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f30a41a57c0 (LWP 30187)):
[KCrash Handler]
#6  0x7f30a1b47474 in QFlags::operator& (f=,
this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:142
#7  QWindow::type (this=this@entry=0x166fbd0) at kernel/qwindow.cpp:826
#8  0x7f30a1b4cac2 in QWindow::winId (this=0x166fbd0) at
kernel/qwindow.cpp:599
#9  0x7f308bdbe312 in ?? () from
/usr/lib/qt/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#10 0x7f308bdbe9ed in ?? () from
/usr/lib/qt/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#11 0x7f30a2458a3c in QMenuBarPrivate::handleReparent
(this=this@entry=0x166f3f0) at widgets/qmenubar.cpp:1362
#12 0x7f30a2459715 in QMenuBar::eventFilter (this=0x166f0a0,
object=0x1642320, event=0x7ffe407ce7f0) at widgets/qmenubar.cpp:1462
#13 0x7f30a0746461 in
QCoreApplicationPrivate::sendThroughObjectEventFilters
(receiver=receiver@entry=0x1642320, event=event@entry=0x7ffe407ce7f0) at
kernel/qcoreapplication.cpp:1099
#14 0x7f30a22dc385 in QApplicationPrivate::notify_helper (this=, receiver=0x1642320, e=0x7ffe407ce7f0) at kernel/qapplication.cpp:3741
#15 0x7f30a22e3bc1 in QApplication::notify (this=0x7ffe407d0970,
receiver=0x1642320, e=0x7ffe407ce7f0) at kernel/qapplication.cpp:3502
#16 0x7f30a0746700 in QCoreApplication::notifyInternal2
(receiver=receiver@entry=0x1642320, event=event@entry=0x7ffe407ce7f0) at
kernel/qcoreapplication.cpp:988
#17 0x7f30a2324d66 in QCoreApplication::sendEvent (event=0x7ffe407ce7f0,
receiver=0x1642320) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QWidget::setParent (this=this@entry=0x1642320,
parent=parent@entry=0x16980d0, f=...) at kernel/qwidget.cpp:10597
#19 0x7f30a2325afc in QWidget::setParent (this=this@entry=0x1642320,
parent=parent@entry=0x16980d0) at kernel/qwidget.cpp:10451
#20 0x7f30a22ff8f6 in QLayout::addChildWidget (this=this@entry=0x1689150,
w=w@entry=0x1642320) at kernel/qlayout.cpp:926
#21 0x7f30a22ff96f in QLayout::addWidget (this=0x1689150, w=0x1642320) at
kernel/qlayout.cpp:226
#22 0x7f30a243f43c in QMdiSubWindow::setWidget (this=this@entry=0x16980d0,
widget=widget@entry=0x1642320) at widgets/qmdisubwindow.cpp:2330
#23 0x7f30a24335a3 in QMdiArea::addSubWindow (this=,
widget=0x1642320, windowFlags=...) at widgets/qmdiarea.cpp:1989
#24 0x7f307908e2dd in QtCurveConfig::previewControlPressed() () from
/usr/lib/qt/plugins/kstyle_qtcurve5_config.so
#25 0x7f307908e3f9 in 

[kdialog] [Bug 378787] New: KDialog crashes if given unknown command line options

[beojan]

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

Bug ID: 378787
   Summary: KDialog crashes if given unknown command line options
   Product: kdialog
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: beo...@gmail.com
  Target Milestone: ---

KDialog crashes if it is given no, or unknown, command line options. The
backtrace is:

Application: kdialog (kdialog), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4892ebf000 (LWP 27369))]

Thread 2 (Thread 0x7f487ea0c700 (LWP 27370)):
#0  0x7f488ea4567d in poll () from /usr/lib/libc.so.6
#1  0x7f488b5268e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f488b528679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f4880d679e9 in QXcbEventReader::run (this=0x846f80) at
qxcbconnection.cpp:1345
#4  0x7f488f13e6b8 in QThreadPrivate::start (arg=0x846f80) at
thread/qthread_unix.cpp:368
#5  0x7f48898fe2e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f488ea4f54f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f4892ebf000 (LWP 27369)):
[KCrash Handler]
#6  std::__atomic_base::compare_exchange_strong
(__m2=std::memory_order_acquire, __m1=std::memory_order_acquire,
__p2=, __p1=@0x7fff386a0218: 0x0, this=0x20) at
/usr/include/c++/6.3.1/bits/atomic_base.h:752
#7  std::atomic::compare_exchange_strong
(__m2=std::memory_order_acquire, __m1=std::memory_order_acquire,
__p2=, __p1=@0x7fff386a0218: 0x0, this=0x20) at
/usr/include/c++/6.3.1/atomic:466
#8  QAtomicOps::testAndSetAcquire
(currentValue=, newValue=, expectedValue=0x0,
_q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:290
#9  QBasicAtomicPointer::testAndSetAcquire (currentValue=: , newValue=, expectedValue=0x0,
this=0x20) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:262
#10 QBasicMutex::fastTryLock (current=: ,
this=0x20) at thread/qmutex.h:101
#11 QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:224
#12 0x7f4890e59ab7 in QMutexLocker::QMutexLocker (m=0x20, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:199
#13 QDBusConnectionManager::busConnection (this=0x0,
type=type@entry=QDBusConnection::SessionBus) at qdbusconnection.cpp:105
#14 0x7f4890e5ab7c in QDBusConnection::sessionBus () at
qdbusconnection.cpp:1169
#15 0x7f487ca23956 in QtCurve::Style::disconnectDBus() () from
/usr/lib/qt/plugins/styles/qtcurve.so
#16 0x7f487ca61236 in QtCurve::StylePlugin::~StylePlugin() () from
/usr/lib/qt/plugins/styles/qtcurve.so
#17 0x7f488f30d5b9 in QLibraryPrivate::unload (this=this@entry=0x88a470,
flag=flag@entry=QLibraryPrivate::UnloadSys) at plugin/qlibrary.cpp:562
#18 0x7f488f303252 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x8898a0, __in_chrg=) at plugin/qfactoryloader.cpp:86
#19 0x7f488f303379 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x8898a0, __in_chrg=) at plugin/qfactoryloader.cpp:89
#20 0x7f488f34bfd7 in QScopedPointerDeleter::cleanup
(pointer=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60
#21 QScopedPointer::~QScopedPointer (this=0x7f4890706858 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder+8>, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107
#22 QObject::~QObject (this=, __in_chrg=) at
kernel/qobject.cpp:900
#23 0x7f488f3027ae in QFactoryLoader::~QFactoryLoader (this=0x7f4890706850
<(anonymous namespace)::Q_QGS_loader::innerFunction()::holder>,
__in_chrg=) at plugin/qfactoryloader.cpp:211
#24 0x7f4890072389 in (anonymous namespace)::Q_QGS_loader::Holder::~Holder
(this=, __in_chrg=) at
styles/qstylefactory.cpp:66
#25 0x7f488e9996c0 in __run_exit_handlers () from /usr/lib/libc.so.6
#26 0x7f488e99971a in exit () from /usr/lib/libc.so.6
#27 0x7f488f1f7354 in QCommandLineParser::showHelp (this=,
exitCode=0) at tools/qcommandlineparser.cpp:1036
#28 0x0040fcfa in ?? ()
#29 0x7f488e983511 in __libc_start_main () from /usr/lib/libc.so.6
#30 0x004100fa in _start ()

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

[kdialog] [Bug 375936] kdialog always crashes

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #8 from beojan <beo...@gmail.com> ---
Does anyone know which Qt commit this was fixed in? I have the crash with Qt
5.8.0, but not if I use the 5.8 branch from git, though this would require
rebuilding all Qt libraries.

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

[krita] [Bug 378657] Compilation fails due to SIP not including /usr/share/sip/PyQt5

[beojan]

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

--- Comment #6 from beojan <beo...@gmail.com> ---
The strange thing is that it *is* correctly detecting the PyQt5 directory.

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

[krita] [Bug 378657] Compilation fails due to SIP not including /usr/share/sip/PyQt5

[beojan]

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

--- Comment #4 from beojan <beo...@gmail.com> ---
They're all installed. Editing the build makefile to add `-I
/usr/share/sip/PyQt5` to the sip command line makes the build succeed.

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

[krita] [Bug 378657] Compilation fails due to SIP not including /usr/share/sip/PyQt5

[beojan]

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

--- Comment #2 from beojan <beo...@gmail.com> ---
Arch, with PyQt5 installed.

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

[krita] [Bug 378657] New: Compilation fails due to SIP not including /usr/share/sip/PyQt5

[beojan]

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

Bug ID: 378657
   Summary: Compilation fails due to SIP not including
/usr/share/sip/PyQt5
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

Compilation fails when sip is run, failing to find QtCore/QtCoremod.sip,
because it doesn't look in /usr/share/sip/PyQt5.

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

[kmail2] [Bug 378280] Add button to insert pre tag

[beojan]

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

--- Comment #4 from beojan <beo...@gmail.com> ---
(In reply to Laurent Montel from comment #3)
> Indeed we don't have it.
> But you can insert html if you want.

Yes, but a toolbar button would be easier. In particular, it would mean you can
select some text and insert  tags around it, which isn't possible with the
Insert HTML feature.

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

[QtCurve] [Bug 376057] Systemsettings crashes if QtCurve config is opened while global menu is active

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from beojan <beo...@gmail.com> ---


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

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

[QtCurve] [Bug 376340] Le impostazione crashano non appena provo ad aprire le impostazioni di QtCurve

[beojan]

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

--- Comment #9 from beojan <beo...@gmail.com> ---
*** Bug 376057 has been marked as a duplicate of this bug. ***

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

[QtCurve] [Bug 376340] Le impostazione crashano non appena provo ad aprire le impostazioni di QtCurve

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #8 from beojan <beo...@gmail.com> ---
(In reply to Yichao Yu from comment #6)
> Is the master version ok? I cannot reproduce this somehow

To reproduce, you need to turn on the global menu added in Plasma 5.9. Current
master *is* affected.

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

[kmail2] [Bug 215663] Composer/HTML mode: indentation increase doesn't work

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #8 from beojan <beo...@gmail.com> ---
(In reply to Denis Kurz from comment #7)
> This is still valid in 5.4.1. The buttons work as intended, but the tooltip
> is misleading. I can't come up with a good one, however. "Enable/disable
> bullet list" doesn't fit either, because you can also create sublists with
> this button, like this:
> 

I'd suggest Increase List Level and Decrease List Level.

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

[kmail2] [Bug 378280] Add button to insert pre tag

[beojan]

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

--- Comment #2 from beojan <beo...@gmail.com> ---
Yes,  tags in HTML mail.

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

[kmail2] [Bug 378280] New: Add button to insert pre tag

[beojan]

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

Bug ID: 378280
   Summary: Add button to insert pre tag
   Product: kmail2
   Version: 5.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: composereditor-ng
  Assignee: mon...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

Currently, there's no toolbar button to add pre tags around some text.

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

[plasmashell] [Bug 375535] Global Menu Bar widget does not open menus on hover

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #9 from beojan <beo...@gmail.com> ---
This isn't fixed in Plasma 5.9.3.

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

[frameworks-kiconthemes] [Bug 375946] Recoloring icon themes causes clash if dark plasma theme used with light window theme

[beojan]

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

--- Comment #2 from beojan <beo...@gmail.com> ---
The only thing I can think of is to add a new function to retrieve an icon
which *does* take the background and foreground color (which would also help
for the current menu item, for instance, if the selection text color is light
rather than dark).

For the current API, I would go so far as to say "don't return recolored
icons".

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

[QtCurve] [Bug 376057] New: Systemsettings crashes if QtCurve config is opened while global menu is active

[beojan]

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

Bug ID: 376057
   Summary: Systemsettings crashes if QtCurve config is opened
while global menu is active
   Product: QtCurve
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: qt5
  Assignee: yyc1...@gmail.com
  Reporter: beo...@gmail.com
CC: h...@kde.org
  Target Milestone: ---

System settings crashes if I open the QtCurve config dialog with the new Plasma
5.9 global menu active.

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

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

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #4 from beojan <beo...@gmail.com> ---
> Maybe we should ask for Qt versions of Gimp, etc?

In the case of GIMP, try Krita. It isn't technically for the same purpose, but
it may be just fine, or even better than GIMP depending on what you're using it
for.

For more basic photo editing, Digikam should also be considered.

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

[frameworks-kiconthemes] [Bug 375946] New: Recoloring icon themes causes clash if dark plasma theme used with light window theme

[beojan]

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

Bug ID: 375946
   Summary: Recoloring icon themes causes clash if dark plasma
theme used with light window theme
   Product: frameworks-kiconthemes
   Version: 5.29.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: beo...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Monochrome icons are currently recolored using the window text color. This
causes a clash if they are displayed on a background that is not window
background, such as KMail in the system tray with a dark plasma theme, or if
the toolbar uses inverted colors.

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

[ksplash] [Bug 374114] New: KSplash quits before Plasma is fully loaded

[beojan]

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

Bug ID: 374114
   Summary: KSplash quits before Plasma is fully loaded
   Product: ksplash
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: beo...@gmail.com
  Target Milestone: ---

It appears KSplash quits when Plasma *starts* loading rather than when it has
finished loading. Perhaps it's making assumptions which held in the KDE 3 era
when the desktop consisted of multiple processes, but no longer hold since
everything is drawn by plasmashell.

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

[plasmashell] [Bug 348960] Double click to open file/folders do not work with "icon" and "trash" plasmoids

[beojan]

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

--- Comment #11 from beojan <beo...@gmail.com> ---
(In reply to Hanisch from comment #10)
> (In reply to Christoph Feck from comment #9)
> > David, it is possible to ignore the second click if that is within the
> > double-click timeout. Would you accept such patch?
> 
> No, double click is double click. We will have that again.

I agree with David's comment that purely reflecting the setting for files and
folders makes the panel inconsistent. Either the behavior should be
single-click in the panel and double click on the desktop, or the second click
should be ignored.

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

[QtCurve] [Bug 368672] kdialog hangs on popup menu when using qtcurve with menu opacity less then 100

[beojan]

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

beojan <beo...@gmail.com> changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #4 from beojan <beo...@gmail.com> ---
It's not just kdialog that hangs. This happens in any file dialog, and the
entire desktop hangs until kwin is restarted.

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

[plasmashell] [Bug 370180] Widgets moved to secondary monitor upon reboot

[beojan]

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

--- Comment #8 from beojan <beo...@gmail.com> ---
(In reply to beojan from comment #7)
> I see the same issue, only it happens after locking and unlocking the screen.

But only after leaving it for a while it seems, so I can't just lock and unlock
again to get things back the way they were.

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