[kwin] [Bug 389337] Several issues with mouse pointer

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

  Component|wayland-generic |input
  Flags||Wayland+, X11-

--- Comment #3 from Martin Flöser  ---
In future please create one bug report per issue. Otherwise it becomes
impossible to track.

The first issue is not in KWin: KWin is not responsible for the cursors shown.
This is up to the applications.

The second issue falls into KWin area, though I'm not able to reproduce.

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

[krita] [Bug 389338] Crash when using Document::createFilterLayer

[bugzilla_noreply]

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

nickelbac...@gmail.com changed:

   What|Removed |Added

 CC||nickelbac...@gmail.com

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

[kwin] [Bug 389334] Fullscreen shortcut overrides programs with built in shortcut (like chromium)

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Martin Flöser  ---
This is a bug in Chromium. The window manager tells the window that it has been
put to fullscreen. It should adjust to the fullscreen user interface in that
case. Please compare to firefox where this works without any problems.

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

[kwin] [Bug 389333] AppMenu hidden in fullscreen

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

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

[krita] [Bug 389338] New: Crash when using Document::createFilterLayer

[Boudewijn Rempt]

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

Bug ID: 389338
   Summary: Crash when using Document::createFilterLayer
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: b...@valdyas.org
  Target Milestone: ---

from krita import *
d = Krita.instance().activeDocument()
d.createFilterLayer("test", "invert", InfoObject(), Selection())

Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f87f8715900 (LWP 27683))]

Thread 5 (Thread 0x7f87ace83700 (LWP 27690)):
#0  0x7f87f4eec74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f87ececf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f87ececf49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f87f5a296cb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f87f59d1e2a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f87f57fa8f4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f87d5d2fd25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f87f57ff709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f87ee4c86ba in start_thread (arg=0x7f87ace83700) at
pthread_create.c:333
#9  0x7f87f4ef841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f87b88a1700 (LWP 27689)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f87f580065b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f87f694684a in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x7f87f57ff709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f87ee4c86ba in start_thread (arg=0x7f87b88a1700) at
pthread_create.c:333
#5  0x7f87f4ef841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f87b80a0700 (LWP 27687)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f87f580065b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f87f57f95ff in QSemaphore::tryAcquire(int, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f87f28e3116 in KisTileDataSwapper::waitForWork() () from
/home/boud/dev/i/lib/x86_64-linux-gnu/libkritaimage.so.16
#4  0x7f87f28e3132 in KisTileDataSwapper::run() () from
/home/boud/dev/i/lib/x86_64-linux-gnu/libkritaimage.so.16
#5  0x7f87f57ff709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f87ee4c86ba in start_thread (arg=0x7f87b80a0700) at
pthread_create.c:333
#7  0x7f87f4ef841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f87d07fa700 (LWP 27685)):
#0  0x7f87f4eec74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f87ececf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f87ececf49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f87f5a296cb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f87f59d1e2a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f87f57fa8f4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f87ee6f4315 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f87f57ff709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f87ee4c86ba in start_thread (arg=0x7f87d07fa700) at
pthread_create.c:333
#9  0x7f87f4ef841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f87f8715900 (LWP 27683)):
[KCrash Handler]
#6  0x7f87f29cfa39 in KisBaseProcessor::defaultConfiguration() const ()
from /home/boud/dev/i/lib/x86_64-linux-gnu/libkritaimage.so.16
#7  0x7f87b4fff751 in Document::createFillLayer(QString const&, QString,
InfoObject&, Selection&) () from
/home/boud/dev/i/lib/x86_64-linux-gnu/libkritalibkis.so.16
#8  0x7f87b47aae2b in meth_Document_createFillLayer () from
/home/boud/dev/i/lib/x86_64-linux-gnu/krita-python-libs/PyKrita/krita.so
#9  0x7f87b5323039 in PyCFunction_Call () from
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#10 0x7f87b542f1b5 in PyEval_EvalFrameEx () from
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#11 0x7f87b54bfcac in ?? () from
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#12 0x7f87b54bfd83 in PyEval_EvalCodeEx () from
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0

[kmymoney] [Bug 388963] qif importer fails with "you need to call KMyMoneySettings::instance before using"

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kmy
   ||money/2d3c8b6e981b135be8a0a
   ||206b998539fbacdb689
 Resolution|--- |FIXED

--- Comment #1 from Thomas Baumgart  ---
Git commit 2d3c8b6e981b135be8a0a206b998539fbacdb689 by Thomas Baumgart.
Committed on 23/01/2018 at 07:12.
Pushed by tbaumgart into branch '5.0'.

Force usage of global settings in plugins

Since the plugins are shared objects also, we need to inject the global
settings object in the same way as has been implemented with commit
5a1b6235c8ed0775f9f7ade3f274678c1ddfa268

M  +3-0kmymoney/pluginloader.cpp
M  +6-0kmymoney/plugins/checkprinting/checkprinting.cpp
M  +2-0kmymoney/plugins/checkprinting/checkprinting.h
M  +7-0kmymoney/plugins/csv/export/csvexporter.cpp
M  +2-0kmymoney/plugins/csv/export/csvexporter.h
M  +6-0kmymoney/plugins/csv/import/csvimporter.cpp
M  +2-0kmymoney/plugins/csv/import/csvimporter.h
M  +6-0kmymoney/plugins/gnc/import/gncimporter.cpp
M  +3-1kmymoney/plugins/gnc/import/gncimporter.h
M  +6-0kmymoney/plugins/icalendar/export/icalendarexporter.cpp
M  +2-0kmymoney/plugins/icalendar/export/icalendarexporter.h
M  +6-0kmymoney/plugins/kbanking/kbanking.cpp
M  +2-0kmymoney/plugins/kbanking/kbanking.h
M  +3-0kmymoney/plugins/kmymoneyplugin.h
M  +6-0kmymoney/plugins/ofx/import/ofximporter.cpp
M  +3-1kmymoney/plugins/ofx/import/ofximporter.h
M  +7-0kmymoney/plugins/qif/export/qifexporter.cpp
M  +3-1kmymoney/plugins/qif/export/qifexporter.h
M  +6-0kmymoney/plugins/qif/import/qifimporter.cpp
M  +3-1kmymoney/plugins/qif/import/qifimporter.h
M  +6-0kmymoney/plugins/reconciliationreport/reconciliationreport.cpp
M  +2-0kmymoney/plugins/reconciliationreport/reconciliationreport.h
M  +6-0kmymoney/plugins/weboob/weboob.cpp
M  +2-0kmymoney/plugins/weboob/weboob.h

https://commits.kde.org/kmymoney/2d3c8b6e981b135be8a0a206b998539fbacdb689

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

[plasmashell] [Bug 387988] Folder view allows duplicated delete dialog

[bugzilla_noreply]

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

capitaine.k...@hotmail.fr changed:

   What|Removed |Added

 CC||capitaine.k...@hotmail.fr

--- Comment #2 from capitaine.k...@hotmail.fr ---
confirmed on my Kubuntu 17.10. another dialog appears instead of bringing back
the focus on the current one.

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

[kwin] [Bug 389232] Random Kwin crash after update.

[Tony]

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

--- Comment #2 from Tony  ---
(In reply to Fabian Vogt from comment #1)
> openQA found this as well but it worked again on the next build. Is this
> still an issue?

Haven't experienced the crash again. I've updated to each one of the snapshots
that have being release after i reported the bug, in tumbleweed.

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

[kwin] [Bug 389337] Several issues with mouse pointer

[Safa Alfulaij]

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

--- Comment #2 from Safa Alfulaij  ---
Created attachment 110070
  --> https://bugs.kde.org/attachment.cgi?id=110070=edit
Information from KWin

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

[kwin] [Bug 389337] Several issues with mouse pointer

[Safa Alfulaij]

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

--- Comment #1 from Safa Alfulaij  ---
Created attachment 110069
  --> https://bugs.kde.org/attachment.cgi?id=110069=edit
Cursor size in KCM

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

[kwin] [Bug 389337] New: Several issues with mouse pointer

[Safa Alfulaij]

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

Bug ID: 389337
   Summary: Several issues with mouse pointer
   Product: kwin
   Version: 5.11.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: safa1996alful...@gmail.com
  Target Milestone: ---

Created attachment 110068
  --> https://bugs.kde.org/attachment.cgi?id=110068=edit
The blinking cursor on the top-left

1. The pointer size isn't correct while it's on normal Qt widgets/QML. It is
appearing as 36 instead of 24. The size changes when moving the pointer from
the widget area to the title bar area, and it is correctly sized in GTK
applications (Testing FireFox here). I have the setting on “Resolution
dependent” in the cursors KCM.

2. Moving the cursor between any surface and another shows it as a blink in the
top-left area. This happens when moving it from application area to Plasma,
from application area to title bar and from title bar to Plasma. (Check the
attached video, sorry for the lighting.)
This is true also for context menus.

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

[kwin] [Bug 389222] [Wayland] Context menu opens behing plasma panel

[Safa Alfulaij]

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

Safa Alfulaij  changed:

   What|Removed |Added

 CC||safa1996alful...@gmail.com

--- Comment #2 from Safa Alfulaij  ---
I faced this exact thing here. As a note, if the small hidden popup panel is
shown, context menus are above the panel.

Also, if the popup panel isn't shown, clicking somewhere else in Plasma
(desktop, kicker/kickoff, etc will not hide it. Only opening new windows will
hide it.

And also if there are any opened window, only the context menus of the shown
applets in the system tray (not any other, not the clock, task manager,
kicker/kickoff) will appear on the top-left corner. This is only if the small
hidden popup panel is not shown.

To note also, one can have the small panel opened, and open all the context
menus starting from left, and new  ones won't hide older. Not sure if this
exists in X11.

I have Plasma 5.11 on Arch Linux

Shall I open different issues for this? :)

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

[kile] [Bug 364238] cite command not showing bibliography entries

[Michel Ludwig]

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

--- Comment #7 from Michel Ludwig  ---
(In reply to S. Umar from comment #6)
> As seen in the image I am still seeing this with the git just pulled (after
> the biblatex.cwl fi correction). I use revtex style that uses natbib and I
> am on Fedora Linux.

Are you working with Kile projects or just with a single file?

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

[kcalcore] [Bug 389336] New: current mDirtyFields handling in IncidenceBase implementation causes issues with event revision counts (iCal SEQUENCE property)

[Jochen Trumpf]

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

Bug ID: 389336
   Summary: current mDirtyFields handling in IncidenceBase
implementation causes issues with event revision
counts (iCal SEQUENCE property)
   Product: kcalcore
   Version: git
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: jochen.tru...@anu.edu.au
  Target Milestone: ---

To reproduce the issue:

1) Accept an event invitation from kmail that you are not the organizer of (not
sure if this is really necessary but it is the case that I fully tracked down).
2) Edit the event in korganizer and be careful to ONLY add an alarm.
3) Get the event organizer to send you an event update, for example, with a
changed location.
4) Observe how the location change is shown in "reverse logic".
5) Try to accept the changed invitation and get the "This is not an update"
error.

What happens under the hood:

Step 2) above should not lead to an increment of the event revision (iCal
SEQUENCE property). At least that is the intent of the
allowedModificationsWithoutRevisionUpdate logic in
akonadi-calendar/incidencechanger.cpp lines 1022ff.

Two things are going wrong, though, and if you watch the actual akonadi payload
(e.g. in akonadiconsole), you will see that the revision gets incremented
TWICE!

So by the time the organizer sends an update, the local copy is seemingly
newer, leading to the incorrect display in kmail as well as the error in Steps
4) resp. 5) above.

One of the revision count increments is caused by lines 657ff in
incidenceeditor/incidencedialog.cpp. This seems to be an unconditional
increment in this context and I have no idea why it would be there. It appears
to preclude any form of "smart" handling of changes within akonadi.

The other revision count increment is due to a failure of the
allowedModificationsWithoutRevisionUpdate logic mentioned above. In that
function, the dirtyFields() call on the incidence returns many more fields than
just IncidenceBase::FieldLastModified and IncidenceBase::FieldAlarms. On my
machine it lists a total of 10 fields, including FieldRevision due to the
previous increment in incidencedialog.cpp.

The issue seems to be that some of the modifier methods in IncidenceBase and
its children set the respective dirty flag even if the value of the property
has not changed. For example, setOrganizer in IncidenceBase does not check the
previous value and setSecrecy in Incidence or setTransparency in Event fail
similarly. On the other hand, some of the set methods do this correctly, for
example setUid in IncidenceBase. On my machine, I have observed incorrect
behavior for Description, Recurrence, Attachment, Secrecy, Transparency,
Attendees, and Organizer (and possibly for Alarms and Revision as well, but
that might be confounded with the other issues described here).

Additionally, toggling the alarm on the event (e.g. via the context menu in
korganizer) seems to set IncidenceBase::FieldUnknown in dirtyFields() where it
should probably be FieldAlarms. With FieldUnknown, toggling the alarm causes
similar issues as described here.  

While you are fixing this, the logic in
allowedModificationsWithoutRevisionUpdate should probably be expanded to also
allow modifications of Categories (not 100% sure about this but I would think
that categories are a local property given that they map to akonadi tags). Many
people are colour-coding their agendas using (local) categories and in the
current implementation that breaks invitation updates.

I am more than happy to try suggested fixes if needed.

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

[plasmashell] [Bug 386656] [Feature request] Circular avatar

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kmag] [Bug 389325] kmag bug

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

Summary|kag bug |kmag bug

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

[kmag] [Bug 389325] kag bug

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

--- Comment #1 from Burkhard Lueck  ---
please be more specific what is "bad" for you and add info about your system /
distribution

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

[korganizer] [Bug 352214] Event is not displayed in the UI if the invitation list contains the creator's email address with PARTSTAT=NEEDS-ACTION (or maybe anything else than PARTSTAT=ACCEPTED?)

[Jochen Trumpf]

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

Jochen Trumpf  changed:

   What|Removed |Added

 CC||jochen.tru...@anu.edu.au

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

[KScreen] [Bug 388218] Desktop scaling is applied twice in Scale Display preview

[Lastique]

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

--- Comment #9 from Lastique  ---
Created attachment 110067
  --> https://bugs.kde.org/attachment.cgi?id=110067=edit
Scaling dialog when system is booted with ratio 1.7 and the ratio is 1.0

And here is a screenshot from the system that is still booted with scale ratio
1.7 but the slider in the dialog have been moved to 1.0. Notice that the
preview elements are roughly the same size as the rest of the UI (i.e. are
actually 1.7 times larger than they would normally be with scale ratio 1.0).

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

[KScreen] [Bug 388218] Desktop scaling is applied twice in Scale Display preview

[Lastique]

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

Lastique  changed:

   What|Removed |Added

 Attachment #110065|0   |1
is obsolete||

--- Comment #8 from Lastique  ---
Created attachment 110066
  --> https://bugs.kde.org/attachment.cgi?id=110066=edit
Scaling dialog when system is booted with ratio 1.7 and the ratio is 1.7

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

[Discover] [Bug 389321] ApplicationPage is overwhelming with more than 3 screenshots at a time

[Aleix Pol]

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

--- Comment #3 from Aleix Pol  ---
Nate contacted in private asking for a frame. Here's with a frame. :)

1 screenshot:
https://i.imgur.com/e4C68qk.png

several:
https://i.imgur.com/1FDMuNp.png

several, no frame:
https://i.imgur.com/fAuLEXR.png

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

[KScreen] [Bug 388218] Desktop scaling is applied twice in Scale Display preview

[Lastique]

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

--- Comment #7 from Lastique  ---
Created attachment 110065
  --> https://bugs.kde.org/attachment.cgi?id=110065=edit
Scaling dialog when system is booted with ratio 1.7 and the ratio is 1.7

Here is a screenshot taken from the system booted with scale ratio 1.7 and the
scale ratio in the dialog is 1.7 too (i.e. unchanged since boot). You can see
that the preview elements are noticeably larger than the rest of the interface.

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

[KScreen] [Bug 388218] Desktop scaling is applied twice in Scale Display preview

[Lastique]

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

Lastique  changed:

   What|Removed |Added

 Attachment #109513|0   |1
is obsolete||

--- Comment #6 from Lastique  ---
Created attachment 110064
  --> https://bugs.kde.org/attachment.cgi?id=110064=edit
Logs collected for scale ratio 1.0 and 1.7

Here are the collected logs. After I enabled the logs I first booted the system
with 1.0 scale ratio. You can find the collected logs and settings for this
boot time in the 1.0 subfolder.

I started the kcm_shell and changed the scale ratio to 1.7 and then rebooted.
Logs and settings from after that reboot are in the 1.7 subfolder. While booted
with 1.7 scale ratio, I started kcm_shell again (the bug was apparent) and
changed the scale ratio back to 1.0.

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

[Discover] [Bug 389321] ApplicationPage is overwhelming with more than 3 screenshots at a time

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

Summary|Put screenshot thumbnails   |ApplicationPage is
   |in a horizontal scrollview  |overwhelming with more than
   |when they don't all fit on  |3 screenshots at a time
   |one line|
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Aleix Pol  ---
To be honest, I'm not very fond of how everything intertwines:
https://i.imgur.com/7hUZbZ4.png

I'd say it would be better to just have a + that opened the popup or so.

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

[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO

[Peter Eszlari]

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

--- Comment #24 from Peter Eszlari  ---
(In reply to David Edmundson from comment #22)
> I'm not doing anything else on this issue, closing this bug.

Does this mean, this will never become the default for X11? After some testing,
I could find any problems with it and it improves the look of plasma greatly.
(It seems not to apply to kwin's context menu icons, should I file new bug for
that?)

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

[plasmashell] [Bug 379759] Device items not properly collapsing

[Dr . Chapatin]

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

--- Comment #4 from Dr. Chapatin  ---
plasma 5.12 beta is affected on Arch Linux.

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

[plasmashell] [Bug 389330] Plasma popup notifications sometimes get pushed "behind the desktop"

[Antonio Russo]

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

Antonio Russo  changed:

   What|Removed |Added

   Severity|minor   |wishlist

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

[plasmashell] [Bug 389330] Plasma popup notifications sometimes get pushed "behind the desktop"

[Antonio Russo]

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

Antonio Russo  changed:

   What|Removed |Added

   Severity|normal  |minor

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

[plasmashell] [Bug 389330] Plasma popup notifications sometimes get pushed "behind the desktop"

[Antonio Russo]

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

--- Comment #1 from Antonio Russo  ---
Sorry, to reproduce this, you need, in .config/kwinrc:

[Compositing]
HiddenPreviews=4

Also, you might need to somewhat rapidly swap around opening the status and
notifications window and changing to other desktops.

I'm not even sure why I had that setting in kwinrc to begin with, so I'm going
to lower this priority a lot.

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

[okular] [Bug 389216] Export Markdown to PDF segfaults

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/oku
   ||lar/4a80d3f963b9acf901ed98d
   ||b7f24fd354e8e986f

--- Comment #5 from Albert Astals Cid  ---
Git commit 4a80d3f963b9acf901ed98db7f24fd354e8e986f by Albert Astals Cid.
Committed on 22/01/2018 at 23:37.
Pushed by aacid into branch 'Applications/17.12'.

Fix crash when exporting

We had a off by one from when we removed the document archive option from the
export menu.

M  +1-1part.cpp

https://commits.kde.org/okular/4a80d3f963b9acf901ed98db7f24fd354e8e986f

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

[okular] [Bug 389216] Export Markdown to PDF segfaults

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #4 from Albert Astals Cid  ---
Yes, and now the comment about html make sense too, it's the same problem, no
need to open a new bug, sorry i misunderstood.

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

[systemsettings] [Bug 388754] System Settings crashes when "Font Management" is selected

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[plasmashell] [Bug 389335] Audio randomly "disconnects" from pulseaudio server

[Isaac]

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

Isaac  changed:

   What|Removed |Added

 CC||isaacalich8...@gmail.com

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

[systemsettings] [Bug 364746] Crash when accessing 'Font Management' inside Fonts section of 'Settings'

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||goldma...@gmail.com

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

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

[plasmashell] [Bug 389335] New: Audio randomly "disconnects" from pulseaudio server

[Isaac]

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

Bug ID: 389335
   Summary: Audio randomly "disconnects" from pulseaudio server
   Product: plasmashell
   Version: 5.11.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Media Player
  Assignee: k...@privat.broulik.de
  Reporter: isaacalich8...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 110063
  --> https://bugs.kde.org/attachment.cgi?id=110063=edit
A picture of the audio volume setup dialog.

Unsure if this is a duplicate or if I'm even posting in the right place, but
seemingly at random intervals, KDE seems to "disconnect" from the pulseaudio
server, most of the time after I've left my PC unattended for a while, but
rebooting fixes it.

When it disconnects I'm unable to adjust the volume, but music through spotify
+ media keys still work just fine, and I can hear it out of my speakers.

I'm using a Ryzen 5 1600 w/ ALC1220 audio codec, and a GTX 1070 w/ proprietary
drivers, sound coming through the back of the motherboard.

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

[plasmashell] [Bug 389215] Panel doesn't fit correctly in the bottom of the screen, breaking Fitt's law

[Cqoicebordel]

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

--- Comment #5 from Cqoicebordel  ---
The attachment 110061 is actually my taskbar. If I try to move it from the
bottom to a side, and then back, this gap happens. And only killing and
restarting plasmashell solves the issue.

But without any action from me, the corners of the taskbar seems a little bit
rounded, as you can see in attachment 110062. And that is the bottom left of my
screen, so at that pixel, the launcher isn't accessible.

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

[plasmashell] [Bug 389215] Panel doesn't fit correctly in the bottom of the screen, breaking Fitt's law

[Cqoicebordel]

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

Cqoicebordel  changed:

   What|Removed |Added

 CC||david.bar...@wanadoo.fr

--- Comment #4 from Cqoicebordel  ---
Created attachment 110062
  --> https://bugs.kde.org/attachment.cgi?id=110062=edit
Corners of the taskbar

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

[plasmashell] [Bug 388681] Plasma crashes after right-click on the Kicker's element (an app shortcut for example)

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
If this is reproducible, please add a backtrace with debug symbols. For help,
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.

[kwin] [Bug 389334] New: Fullscreen shortcut overrides programs with built in shortcut (like chromium)

[zeta]

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

Bug ID: 389334
   Summary: Fullscreen shortcut overrides programs with built in
shortcut (like chromium)
   Product: kwin
   Version: 5.11.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: franciscodezuvi...@gmail.com
  Target Milestone: ---

I binded fullscreen to F11, to enjoy fullscreeness in every program.

Global Shortcuts -> SystemSettings -> Make Window Fullscreen

However, chromium still displays all the toolbars in fullscreen mode, because
the F11 shortcut is overriden by KWIN's binding.

I understand this may be the "correct" behavior, but it hurtts usability.

How can we get more fine grained controll over shortcuts? example:

A) exceptions
B) allow triggering of both actions when a global shorcuts conflicts an app's
shortcut

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

[okular] [Bug 367071] no text

[Christoph Feck]

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

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

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

[plasma4] [Bug 191889] Digital clock widget on the panel is usually too wide

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||pointedst...@zoho.com

--- Comment #11 from Nate Graham  ---
No longer an issue in Plasma 5.

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

[KScreen] [Bug 388218] Desktop scaling is applied twice in Scale Display preview

[Christoph Feck]

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

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

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

[plasmashell] [Bug 389215] Panel doesn't fit correctly in the bottom of the screen, breaking Fitt's law

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Created attachment 110061
  --> https://bugs.kde.org/attachment.cgi?id=110061=edit
Another occurrence of the issue

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

[plasmashell] [Bug 389215] Panel doesn't fit correctly in the bottom of the screen, breaking Fitt's law

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Panel doesn't fit correctly |Panel doesn't fit correctly
   |in the bottom of the screen |in the bottom of the
   ||screen, breaking Fitt's law
   Keywords||usability
   Severity|minor   |normal

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

[ktorrent] [Bug 383127] KTorrent crash while closing

[bugzilla_noreply]

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

pmarget...@gmail.com changed:

   What|Removed |Added

 CC||pmarget...@gmail.com

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

[kwin] [Bug 389333] New: AppMenu hidden in fullscreen

[zeta]

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

Bug ID: 389333
   Summary: AppMenu hidden in fullscreen
   Product: kwin
   Version: 5.11.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: appmenu
  Assignee: kwin-bugs-n...@kde.org
  Reporter: franciscodezuvi...@gmail.com
  Target Milestone: ---

- configure Window menu integration in window decorations
- get any program that opens the File menu with alt+F
- go to fullscreen
- activate the file menu
(nothing happens)
- exit fullscree
(now the menu is visible)

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

[plasmashell] [Bug 389215] Panel doesn't fit correctly in the bottom of the screen

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Nate Graham  ---
Got another report of this issue:
https://pointieststick.wordpress.com/2018/01/20/this-week-in-usability-and-productivity-part-2/comment-page-1/#comment-167

The reporter originally had a single pixel in the corner from the desktop, but
after moving the panel, now has the same issue outlined here--there's a line of
pixels from the desktop on the bottom of his panel. He can reproduce the issue
using KWin or OpenBox as the WM and is using the standard Breeze theme.

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

[okular] [Bug 389332] Okular ignores printer colour settings

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
URL||https://bugreports.qt.io/br
   ||owse/QTBUG-54464
 CC||pointedst...@zoho.com

--- Comment #2 from Nate Graham  ---
This was caused by a Qt bug that has already been fixed:
https://bugreports.qt.io/browse/QTBUG-54464.

Once Fedora provides you Qt 5.11 (targeted for 3/15/2018:
https://wiki.qt.io/Qt_5.11_Release) or backports the fix to Qt 5.9 or 5.10,
then, the bug will be fixed for you.

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

[okular] [Bug 388615] PDf which does not display correctly

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Albert Astals Cid  ---
Your poppler is almost 2 years old and since it works for me and Yuri i'll
close this works.

If you get a new poppler and it still fails please reopen this bug.

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

[okular] [Bug 389332] New: Okular ignores printer colour settings

[Germano Massullo]

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

Bug ID: 389332
   Summary: Okular ignores printer colour settings
   Product: okular
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: germano.massu...@gmail.com
  Target Milestone: ---

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

In Okular, when you open print menu, and you select "grayscale" option, Okular
will still print using colours

okular-17.08.1-1.fc27.x86_64

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

[okular] [Bug 389332] Okular ignores printer colour settings

[Germano Massullo]

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

--- Comment #1 from Germano Massullo  ---
Created attachment 110060
  --> https://bugs.kde.org/attachment.cgi?id=110060=edit
cups.log

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

[gwenview] [Bug 389331] Changes to shortcuts only reflected after restart in some situations

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[gwenview] [Bug 389331] New: Changes to shortcuts only reflected after restart in some situations

[Henrik Fehlauer]

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

Bug ID: 389331
   Summary: Changes to shortcuts only reflected after restart in
some situations
   Product: gwenview
   Version: 17.12.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: rk...@lab12.net
  Target Milestone: ---

After restoring the default shortcut for Quit and switching to View mode, the
old shortcut still works.

Detailed STR:
- Start Gwenview (Start Page should show).
- Open shortcut config dialog, set ⎋ as shortcut for Quit, Reassign → OK.
- ⎋ to close Gwenview.
- Restart Gwenview, open shortcut config dialog again, reset shortcuts:
Defaults → OK.
- Switch modes (e.g. either from Start Page to Browse, or from Browse to View
etc), press ⎋.
- ER: Default action, e.g. mode switch or no action.
- AR: Gwenview closes. (After an additional restart this does not occur
anymore, though).

This seems to occur only if view mode was never active.

There's also a similar issue, when setting ⎋ for Quit and then switching to
View mode: The shortcut is not working (no Quit, no Browse mode).

Very strange - maybe a bug inside KActionCollection or in Gwenview's handling
of it?

(Copied from various comments in https://phabricator.kde.org/D9943)

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

[Breeze] [Bug 389311] disk quota icon in breeze-icons

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[frameworks-baloo] [Bug 389299] Memory Leak when using the search function

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
  Component|general |Baloo File Daemon
Product|plasmashell |frameworks-baloo
   Target Milestone|1.0 |---
Version|5.11.5  |5.42.0
   Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com

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

[plasmashell] [Bug 386656] [Feature request] Circular avatar

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #6 from Nate Graham  ---
I think the idea here is to automatically crop square images to a circle, which
is what the Breeze themes for KScreenLocker and SDDM do. Right now there's an
inconsistency, because Kickoff uses square avatars instead. We should decide on
a single one (circle or square) and use that everywhere.

My vote is for a circle, FWIW.

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

[plasmashell] [Bug 386656] [Feature request] Circular avatar

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
*** Bug 388943 has been marked as a duplicate of this bug. ***

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

[kuser] [Bug 388943] Keep Consistent Shape to Represent User

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---


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

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

[kile] [Bug 389312] failed to save file on samba share, writes empty file instead.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
If looks like you're running Kile with Unity, GNOME, XFCE, MATE, or Cinnamon,
instead of KDE Plasma, right? I ask because based on the path, Kile is
attempting to use a path to the Samba share that's provided by GNOME's GVFS
instead of KDE's KIO.

Can you run the following terminal commands and send the output?

echo "Test" >
"/run/user/1000/gvfs/smb-share:server=mr-server,share=mr-share/_DOKUMENTATION_/MFA-datasheet/test.txt"

cat
"/run/user/1000/gvfs/smb-share:server=mr-server,share=mr-share/_DOKUMENTATION_/MFA-datasheet/test.txt"


If test.txt cannot be created or has no content, that means the path itself is
invalid or not mounted with correct permissions, which is the fault of GVFS or
Ubuntu, and not Kile.

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

[Cqoicebordel]

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

Cqoicebordel  changed:

   What|Removed |Added

 CC||david.bar...@wanadoo.fr

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

[plasmashell] [Bug 389323] Notifications not displayed correctly when message contains

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 389329] 4k HiDPI wayland 2x display scaling issues

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 389330] Plasma popup notifications sometimes get pushed "behind the desktop"

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kile] [Bug 364238] cite command not showing bibliography entries

[S . Umar]

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

--- Comment #6 from S. Umar  ---
As seen in the image I am still seeing this with the git just pulled (after the
biblatex.cwl fi correction). I use revtex style that uses natbib and I am on
Fedora Linux.

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

[kdeconnect] [Bug 389315] [feature request] Filter android receive notifications

[Albert Vaca]

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

--- Comment #1 from Albert Vaca  ---
As of now you can't filter specific notifications, but you can filter entire
apps from the plugin settings in your phone.

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

[kile] [Bug 364238] cite command not showing bibliography entries

[S . Umar]

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

--- Comment #5 from S. Umar  ---
Created attachment 110058
  --> https://bugs.kde.org/attachment.cgi?id=110058=edit
screen image

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

[plasmashell] [Bug 389330] New: Plasma popup notifications sometimes get pushed "behind the desktop"

[Antonio Russo]

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

Bug ID: 389330
   Summary: Plasma popup notifications sometimes get pushed
"behind the desktop"
   Product: plasmashell
   Version: 5.10.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: antonio.e.ru...@gmail.com
  Target Milestone: 1.0

Steps to reproduce:

0. Have a panel with an attached notification window (e.g., the system tray,
"Status and Notifications").

1. Switch to desktop 1.

2. Activate that panel-window (e.g., the status and notification section). It
should be visible as expected.

3. Change desktop using kwin's "Switch to Desktop 2" keybinding (default is
Ctrl-F2). The panel-window should disappear.

4. Change back to desktop 1. Try opening any panel-window again. It won't be
visible (this is the bug).

If you use the "toggle present windows (current desktop)" (default Ctrl-F9),
you'll see a blank window, which represents the panel-window that isn't
visible. Clicking on it raises it, and brings plasmashell back into a
reasonable state.

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

[plasmashell] [Bug 389329] 4k HiDPI wayland 2x display scaling issues

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
1) Those apps are probably running in X. There are very few apps that fall into
the valley of having both have high DPI support and aren't being ported to
wayland. It's an issue that will solve itself by the time wayland is
mainstream.

2) There's another bug report for that somewhere

3) I don't understand, can you include a screenshot. Ideally as a new report.

4) What do you mean by tiling? Can you include a screenshot

5) As in you can only see the top left quarter when fullscreen?
If so will be fixed soon with the new xdg-output and new xwayland.

If you mean something else, please include a screenshot.

As for the rest, duly noted. I'm happy to fix any bugs, but I'm not going to
revert any defaults. 

Your ideas miss some key aspects of how things work, and why they can't be done
the way you suggest.
You can follow more on the threads of the wayland mailing list.

>So instead using a 2x scale, we need a 0.5x scale for peasant displays

If the app is scaling at 2x, and on a 1x screen, that's *exactly* what happens.
If the app can't scale to 2x then you're not in a position to halfscale it.

You can't just assume bodge "scaling" with font DPI, because an app has no way
to report whether it's following that or not.. and we can't add a protcol for
that into existing applications. 


 >I think things like QT_SCALE_FACTOR should be only used for mitigation of
legacy applications.

That would mean kwrite would be tiny?

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

[digikam] [Bug 389179] Error creating mysql db for internel server (mysql_install_db)

[Tobias Philipp]

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

--- Comment #3 from Tobias Philipp  ---
Created attachment 110057
  --> https://bugs.kde.org/attachment.cgi?id=110057=edit
First run dialog with mysql binaries found

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

[digikam] [Bug 389179] Error creating mysql db for internel server (mysql_install_db)

[Tobias Philipp]

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

--- Comment #2 from Tobias Philipp  ---
Hi,

sorry for the late answer...

I deleted the previously generated config files and data directories and
started from scratch.
The first run dialog shows that he is finding the binaris correct. but i set
them nevertheless through the file picker dialog.
Nothing changed, same error.
How a said in the first comment, if i run the mysql_install_db with the
arguments given in the error message from digikam in a console window, i get an
error message from mysql_install_db. i think, digikam is getting the same error
message...

Aattached the screenshot with the mysql binaris found by the first run dialog,
bevore i set them.

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

[plasmashell] [Bug 389329] New: 4k HiDPI wayland 2x display scaling issues

[bugzilla_noreply]

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

Bug ID: 389329
   Summary: 4k HiDPI wayland 2x display scaling issues
   Product: plasmashell
   Version: 5.11.95
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: bug2...@wolke7.net
  Target Milestone: 1.0

I'm running the plasma-5.12 branch from the kde overlay (with qt 5.10). My
Notebook has an 15.6" 4k screen. And on wayland I run into the fallout of the
new scaling feature:
http://blog.davidedmundson.co.uk/blog/kwin_and_scaling/

Some of the issues:

1) Many applications which respect the screens resolution and scale well, are
rendered with half resolution. It looks worse than a 1080p screen, where it is
possible to enable sub pixel rendering for fonts.

2) The mouse pointer size changes depending on the window type, it shrinks to
the half size above scaled up applications.

3) Kicker: The Application menu has much higher spacing between the items.

4) Tiling is ok for scaled up applications (like dia, chrome ...) But
completely messed up for application which run on the native resolution (like
kwrite):
  Top Left corner: Almost maximized in top left
  Left: Similar layout
  Bottom Left: Similar size, but half of the window below the screen

  Bottom right: Only the upper left quarter is visible (centered on bottom
right corner)
  Right: Only left half is visible
  Top right: Similar to Right
For me it looks like these tiled applications windows are twice as large as
they should be.

5) Full screen applications/games like sauerbraten: Not usable at all. Only the
upper left quarter scaled by 2.
In window mode the mouse is not passed through. Without the ability to aim, it
is quite unfair (maybe unrelated)

I suggest to set the default scaling for the upcoming plasma-5.12 back to 1x

While writing this bug report I have switched it back to 1x scaling and set the
font DPI to 192. This setup give a much better 4k support. Some old legacy
application don't scale correctly (like dia or imagej), but it would be much
better to have fixes per window or application, than breaking the whole
desktop.

In future it might be a good idea to not assume that a screen has 96DPI. It
would be much better to respect the values from the EDID. In case of notebook
screen a correction might be a good idea, as they are typically a little closer
than regular screens. 
The DPI override should move from the font configuration to each display. Maybe
 the display with the the highest DPI can be used as rendering resolutions. 
For other lower resolution display it would be better to downscale. But in that
case even sub pixel rendering can help, to preserve as much information as
possible.
So instead using a 2x scale, we need a 0.5x scale for peasant displays (or 0.33
for cloning too a 720p projector)

For legacy applications it would be nice to have an 2x scaling (which also
fakes a 96dpi pixel size) Nice to have in the compositor would be an optional
pixel art scaling algorithm like hq2x or 2xsai.

I think things like QT_SCALE_FACTOR should be only used for mitigation of
legacy applications. Try to force a 2x scaling onto other applications will
bring us crappy scaling for the next 5 years. After that it repeats with 8k
notebook screens.

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

[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget

[Nate Graham]

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

--- Comment #32 from Nate Graham  ---
Thanks a lot for the investigation and analysis, Matt! If you do happen to
pinpoint the issue, you're welcome to submit a patch using
http://phabricator.kde.org/. More information is available at
https://community.kde.org/Get_Involved/development.

If you need a hand with anything, don't hesitate to let me know.

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

[kdenlive] [Bug 386772] XFCE4: GUI font too large on 144 dpi display and no way to change its size in preferences

[bugzilla_noreply]

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

lda...@tuffmail.com changed:

   What|Removed |Added

 CC||lda...@tuffmail.com

--- Comment #2 from lda...@tuffmail.com ---
I had the opposite problem, that fonts were too small, and are fine for me at
144 dpi.   Nothing I tried would change the font size, including
systemsettings5 or qt5ct.  I ended up bodging it with this wrapper script to
start kdenlive, to set the dpi to 144 then reset it afterwards:

#!/bin/bash

dpi=`xdpyinfo | grep resolution | awk '{print $2}' | cut -f 1 -d x`
xrandr --dpi 144
(sleep 5 ; xrandr --dpi $dpi) &
kdenlive $@

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

[okular] [Bug 358061] [Usability] Improved/consistent mechanism to add/modify inline note

[Tobias Deiminger]

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

Tobias Deiminger  changed:

   What|Removed |Added

 CC||haxti...@posteo.de

--- Comment #2 from Tobias Deiminger  ---
+1 for inline editable (WYSIWYG) notes.

This would IMO require new API methods to render single annotations
individually on poppler side.

Atm, poppler renders (slices of) pages. An inline editable note needed to
trigger page rendering for each key stroke. This is a bit heavy considering
processing time. Even if we only rendered the relevant page slice there'd still
be overhead during rendering. Plus the corresponding Okular code would look
ugly. There was a related bug for moving inline notes:
https://bugs.kde.org/show_bug.cgi?id=333981. It's currently solved by only
drawing an empty rectangle, which is obviously not an option during editing:) 

This is a matching wish on the poppler list:
https://lists.freedesktop.org/archives/poppler/2017-April/012165.html. I guess
it currently lacks interest and patches. Maybe we can bump and patch a bit?

As a bonus, https://bugs.kde.org/show_bug.cgi?id=325119 should get solved "for
free".

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

[amarok] [Bug 389328] New: Enabling recursive scan folders locks up / crashes Amarok

[Ski]

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

Bug ID: 389328
   Summary: Enabling recursive scan folders locks up / crashes
Amarok
   Product: amarok
   Version: 2.8.90 (2.9 beta)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Collections/Local
  Assignee: amarok-bugs-d...@kde.org
  Reporter: linuxst...@dski.net
CC: ma...@laitl.cz, ralf-eng...@gmx.de
  Target Milestone: 2.9

Sound system: phonon-gstreamer

Despite a clean install of Linux/KDE5, I have noticed this bug is still around
(it's been in previous versions of Amarok, but I only recently got a KDE
account to report it).

Go to Configure Amarok > Local Collection.

Enable "Scan folders recursively", it hard locks up Amarok, you have to do a
kill -9 (or xkill) to get to restart Amarok. If you played songs before the
lockup, all the stats will be lost.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED
   Severity|normal  |major

--- Comment #284 from Nate Graham  ---
I'll see if I can bring some more attention to this issue.

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

[amarok] [Bug 389327] New: Amarok does not play last second(s) of tracks, affects played stats and last.fm scrobbling

[Ski]

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

Bug ID: 389327
   Summary: Amarok does not play last second(s) of tracks, affects
played stats and last.fm scrobbling
   Product: amarok
   Version: 2.8.90 (2.9 beta)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Playback
  Assignee: amarok-bugs-d...@kde.org
  Reporter: linuxst...@dski.net
CC: ma...@laitl.cz
  Target Milestone: 2.9

Sound system backend: Phonon-gstreamer

With a clean install of Linux / KDE5, Amarok does not play songs to the very
end of the track, it is especially noticeable when tracks are continuous -
there's no gapless playback. The problem causes two problems:

1. When playing tracks, the statistics of being played are not necessarily
logged into the database (I use MariaDB, although the version that uses
Amarok's own database has the same result). If you queue songs, or play songs
normally, the ONLY song guaranteed to be logged into the database as played /
date / time etc, is the very last track, which usually plays right to the very
end of the track.

I have played a few new tracks a few times, but they are not being logged as
having ever been played because the tracks do not play to the end, The tracks
are in the database correctly.


2. Because of the problem described in 1, this is affecting last.FM scrobbling.
What happens is, a track plays, the details are sent to Last.FM as "now
playing..." and you can see that on your Last.FM stats page. Then when you
refresh your stats page on Last.FM when the next track starts playing, the
track you were playing is deleted - it is registering as a user interrupted
track, so it is not logged as having been played. Again, the one track that
does get logged, is the very last track you play - it plays to the end.

I have tracks on a tablet to test Last.FM using VLC, there is no problem with
the Last.FM account, all tracks played on the tablet are logged, so it is
definitely an Amarok problem.

As a further test. I have queued just one track and let that play. It plays to
the end, and it does get logged into Last/M stats properly as having been
played. So the problem is with the tracks being cut short.

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

[krita] [Bug 355971] Onion skin doesn't work

[bugzilla_noreply]

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

--- Comment #4 from kittyangel2...@gmail.com ---
(In reply to steven from comment #0)
> When I turn on onion skin in the timeline or in the layers nothing happens.
> I have two different drawings in frame 1 and 2 and I can't see the previous
> one.
> Version 2.9.9 Animation Beta
> Linux 3.14.0
> Crouton
> Ubuntu 14.04 LTS
> Chromebook 15 (2015)
> 16Gig Ram
> Intel HD Graphics
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1.create a new file
> 2.Create a new frame and draw
> 3.Move to the next frame, create a new frame and draw
> 4. Turn on the onion skin(light bulb is on)
> 5. I only see the current drawing 
> 
> Actual Results:  
> Nothing happens
> 
> Expected Results:  
> I should see the previous frame slightly transparent

I have the same issue

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

[krita] [Bug 355971] Onion skin doesn't work

[bugzilla_noreply]

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

kittyangel2...@gmail.com changed:

   What|Removed |Added

 CC||kittyangel2...@gmail.com

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

[Discover] [Bug 389321] Put screenshot thumbnails in a horizontal scrollview when they don't all fit on one line

[Andres Betts]

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

Andres Betts  changed:

   What|Removed |Added

 CC||anditosan1...@gmail.com

--- Comment #1 from Andres Betts  ---
I support this idea! It goes in line with what most app stores will do and it
also helps the user make a quicker decision to install or not install.

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

[dolphin] [Bug 388594] Dolphin crash trying to close it

[Ski]

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

--- Comment #9 from Ski  ---
Whatever the problem is, it seems to be triggered by somehow interacting
between KDE5 and the nVidia driver, I have so far not seen any crash of Dolphin
using the free Nouveau driver.

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

[kile] [Bug 299282] Kile live preview crashed on file open

[Michel Ludwig]

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

Michel Ludwig  changed:

   What|Removed |Added

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

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

[kdev-python] [Bug 389326] New: lambda function crashes background parser

[Brian DeRocher]

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

Bug ID: 389326
   Summary: lambda function crashes background parser
   Product: kdev-python
   Version: 5.2.1
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@svenbrauch.de
  Reporter: br...@derocher.org
CC: m...@svenbrauch.de
  Target Milestone: ---

mkdir ve
virtualenv ve
cd ve
pip install pylint

Create a new project in KDevelop and watch it crash.

The root cause is in
ve/lib/python2.7/site-packages/pylint/test/functional/inherit_non_class.py,
line 24

class Bad1(lambda abc: 42): # [inherit-non-class]
""" Can't inherit from lambda. """

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

[kmag] [Bug 389325] New: kag bug

[bugzilla_noreply]

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

Bug ID: 389325
   Summary: kag bug
   Product: kmag
   Version: 1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sar...@users.sourceforge.net
  Reporter: nih...@libero.it
  Target Milestone: ---

In full screen the application is bad.
But also in all other case the application seem working bad.

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

[kile] [Bug 170080] Allow collapsing of tables and sections

[Michel Ludwig]

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

Michel Ludwig  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

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

[kile] [Bug 315461] kile crashes on exit

[Michel Ludwig]

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

Michel Ludwig  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from Michel Ludwig  ---
Can you check whether this problem still occurs in Kile 3.0 beta 1?

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

[kile] [Bug 364238] cite command not showing bibliography entries

[Michel Ludwig]

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

Michel Ludwig  changed:

   What|Removed |Added

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

--- Comment #4 from Michel Ludwig  ---
I cannot reproduce this problem any more on the master branch
('832ddf9e4623ca04bad27ecd76b7197f7ee01e43').

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

[telepathy] [Bug 364111] Can't configure a Google account for KDE telepathy

[Paul S]

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

Paul S  changed:

   What|Removed |Added

 CC||ps...@comcast.net

--- Comment #30 from Paul S  ---
Same issue on Kubuntu 17.10, with Plasma version 5.11.95, frameworks version
5.42.0, QT version 5.9.1

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

[plasmashell] [Bug 389324] New: Tasks shown don't match Filters

[Max Schettler]

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

Bug ID: 389324
   Summary: Tasks shown don't match Filters
   Product: plasmashell
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: max.schett...@posteo.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

When using the Task Manager with Wayland, the Filters are not applied
correctly:
The 'Show only tasks from the current desktop' Filter is never activated, even
when enabled in the settings. Only when enabling 'Show only tasks from the
current screen' the tasks from different Desktops are not shown, I assume since
the screens from different desktops are always considered to be different.

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

[plasmashell] [Bug 389323] Notifications not displayed correctly when message contains

[Lastique]

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

Lastique  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

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

[plasmashell] [Bug 389323] New: Notifications not displayed correctly when message contains

[Lastique]

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

Bug ID: 389323
   Summary: Notifications not displayed correctly when message
contains <
   Product: plasmashell
   Version: 5.10.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: andy...@mail.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Try executing the following command:

notify-send "abcd 

[kdevelop] [Bug 389322] New: c++ structured bindings crash kdevelop

[Kenneth Ingham]

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

Bug ID: 389322
   Summary: c++ structured bindings crash kdevelop
   Product: kdevelop
   Version: 5.1.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kdeb...@i-pi.com
  Target Milestone: ---

Application: kdevelop (5.1.2)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.14-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I have a class member returning a std::tuple.  When I tried to type:
auto [a, b] = method(arg)
it crashed when typing the =

These are structured bindings that are a part of the C++17 standard.  You can
find an example here:
https://eli.thegreenplace.net/2016/returning-multiple-values-from-functions-in-c/
http://en.cppreference.com/w/cpp/language/structured_binding

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6a2aad5900 (LWP 16005))]

Thread 17 (Thread 0x7f69c0ff9700 (LWP 16190)):
#0  0x7f6a1f0446f9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f6a1effeb5c in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f6a1efff0f0 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f6a1efff25c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f6a2812257b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f6a280c94aa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f6a27ef08da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f6a25a17abf in  () at /usr/lib64/libKDevPlatformLanguage.so.10
#8  0x7f6a27ef58d0 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f6a2130e558 in start_thread () at /lib64/libpthread.so.0
#10 0x7f6a277f66df in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f699f7fe700 (LWP 16148)):
#0  0x7f6a277ebf2b in poll () at /lib64/libc.so.6
#1  0x7f6a1efff149 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6a1efff25c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6a2812257b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f6a280c94aa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f6a27ef08da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f6a27ef58d0 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f6a2130e558 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6a277f66df in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f69c27fc700 (LWP 16117)):
#0  0x7f6a2131482d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6a27ef6c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f6a1c604ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f6a1c608b28 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f6a1c603cfd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f6a1c606a6b in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f6a27ef58d0 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f6a2130e558 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6a277f66df in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f69c2ffd700 (LWP 16116)):
[KCrash Handler]
#6  0x7f69e85514db in  () at /usr/lib64/libclang.so.5
#7  0x7f69e855152d in  () at /usr/lib64/libclang.so.5
#8  0x7f69e9244e9a in  () at /usr/lib64/libclang.so.5
#9  0x7f69e9246816 in  () at /usr/lib64/libclang.so.5
#10 0x7f69e924aedb in  () at /usr/lib64/libclang.so.5
#11 0x7f69e9244ba5 in  () at /usr/lib64/libclang.so.5
#12 0x7f69e9244122 in  () at /usr/lib64/libclang.so.5
#13 0x7f69e9269da1 in  () at /usr/lib64/libclang.so.5
#14 0x7f69e92134bd in  () at /usr/lib64/libclang.so.5
#15 0x7f69e92732cc in  () at /usr/lib64/libclang.so.5
#16 0x7f69e928b9e7 in  () at /usr/lib64/libclang.so.5
#17 0x7f69e9225b98 in  () at /usr/lib64/libclang.so.5
#18 0x7f69e8545730 in  () at /usr/lib64/libclang.so.5
#19 0x7f69e84cb107 in clang_getCursorDefinition () at
/usr/lib64/libclang.so.5
#20 0x7f69e84caf4d in clang_isCursorDefinition () at
/usr/lib64/libclang.so.5
#21 0x7f69e98cad95 in  () at /usr/lib64/libKDevClangPrivate.so.27
#22 0x7f69e98d5ff9 in  () at /usr/lib64/libKDevClangPrivate.so.27
#23 0x7f69e84bc3f4 in  () at /usr/lib64/libclang.so.5
#24 0x7f69e84be5a6 in  () at 

[kwin] [Bug 387313] Flickering on Wayland with Kmail or Systemsettings

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 CC||mar...@harrisonland.co.uk

--- Comment #20 from Martin Flöser  ---
*** Bug 389053 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 389053] Graphical glitches with Webkit renderers on Wayland

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #3 from Martin Flöser  ---
No, it's a bug in KWin.

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

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

[kwin] [Bug 389316] Language switch does not work properly with xwayland apps

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

  Flags||Wayland+, X11-

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

[kwin] [Bug 389316] Language switch does not work properly with xwayland apps

[Martin Flöser]

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

--- Comment #1 from Martin Flöser  ---
How do you switch layouts? Do you use a shortcut set in the keymap options or
the global shortcut (ctrl+alt+k) provided by Plasma?

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Summary|Scrolling is faster |Dolphin scrolls faster in
   |comparing with other|icon mode than other Qt/KDE
   |softwares   |software

--- Comment #5 from Nate Graham  ---
Think I figured out the issue, thanks to a commenter on my blog
(https://pointieststick.wordpress.com/2018/01/20/this-week-in-usability-and-productivity-part-2/comment-page-1/#comment-158).
Dolphin respects the global setting for number of lines to scroll per tick
(which I think translates into touchpad scroll speed, too), but in icon view,
each line of icons is a line, so the lines are much taller than we'd expect.

Perhaps we should normalize the height of a line before scrolling that many
lines

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

[Discover] [Bug 389321] Put screenshot thumbnails in a horizontal scrollview when they don't all fit on one line

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Put screenshot thumbnails   |Put screenshot thumbnails
   |into horizontal scrollview  |in a horizontal scrollview
   ||when they don't all fit on
   ||one line

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

[Discover] [Bug 389321] New: Put screenshot thumbnails into horizontal scrollview

[Nate Graham]

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

Bug ID: 389321
   Summary: Put screenshot thumbnails into horizontal scrollview
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

[Discover from git Plasma/5.12 branch]

Right now, when there are more than about 2 or 3 screenshots on Discover's app
page, they tile and create more rows. This looks fine as long as the window is
large and the screenshots are all the same size
(https://i.imgur.com/Rrr6WoC.png), but any deviation from this makes the window
look ugly or crowded: https://i.imgur.com/NnRYjFo.jpg2)

VDG would like to see the screenshot thumbnails put into a horizontal
scrollview instead of creating more rows.

As a part of this, once there will only ever be one row, it might be reasonable
to increase the height of the thumbnails to `Kirigami.Units.gridUnit * 8` or
maybe even 9
(https://cgit.kde.org/discover.git/tree/discover/qml/ApplicationScreenshots.qml?h=Plasma/5.12#n124)

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