[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

URL||https://bugreports.qt.io/br
   ||owse/QTBUG-55638

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #6 from Christian Stadelmann  ---
> Obviously the problem here is that gtk hard depends on an unreleased, not
> standardized interface. It should check whether it exists and if not either
> exit (heck one could also use X11, no need to crash just because there's a
> Wayland socket) or fall back to wl_shell as Qt does.

That's the core problem and Gtk+ people are fixing it. See
https://bugzilla.gnome.org/show_bug.cgi?id=762258

Sorry for the noise.

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

URL||https://bugzilla.gnome.org/
   ||show_bug.cgi?id=762258

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

[kwin] [Bug 359531] New: [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 359531
   Summary: [wayland] add support for xdg_shell should stop gtk3
applications from crashing
   Product: kwin
   Version: 5.5.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dah5a...@genodeftest.de

Currently, any gtk+ 3.x application (with wayland rendering backend enabled by
default) starting inside kwin+wayland will crash.


Reproducible: Always

Steps to Reproduce:
1. Run a kwin_wayland session, even a nested one works:
   $ kwin_wayland --xwayland --windowed
2. Start any gtk3 based application
   $ gnome-calculator

Actual Results:  
segfault in wl_proxy_marshal_constructor() because the proxy is NULL.

Expected Results:  
No crash

According to Oliver Fourdan (RedHat) this is because kwin@wayland doesn't
implement the xdg_shell protocol yet.

I am posting this here so nobody will wonder why gtk+ 3.x applications always
crash on start.

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 wl_proxy_marshal_constructor at src/wayland-client.c:678
 #1 gdk_wayland_window_create_xdg_surface at
../../gdk/wayland/xdg-shell-client-protocol.h:151
 #3 gdk_wayland_window_show at gdkwindow-wayland.c:1394
 #5 gdk_window_show_internal at gdkwindow.c:5013
 #6 gtk_window_map at gtkwindow.c:6099

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

[systemsettings] [Bug 359322] fontinst: improve family and style filter (serif, bold, italic, …)

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #2 from Christian Stadelmann  ---
Yes, it does have a search field (or to be exact: a filter). When running
`kcmshell5 fontinst` I see a search field on the right side above the font
preview widget. I filtered by family and style, but I think I'm missing another
category to filter by ?

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

[systemsettings] [Bug 359322] fontinst: improve family and style filter (serif, bold, italic, …)

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #4 from Christian Stadelmann  ---
Sometimes I want to know "Which serif fonts do I have installed?". That's the
use case.

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

[systemsettings] [Bug 359322] New: fontinst: improve family and style filter (serif, bold, italic, …)

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 359322
   Summary: fontinst: improve family and style filter (serif,
bold, italic, …)
   Product: systemsettings
   Version: 5.5.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: kcm_fontinst
  Assignee: unassigned-b...@kde.org
  Reporter: dah5a...@genodeftest.de

Filtering on family does only work if font name includes the property.

Reproducible: Always

Steps to Reproduce:
1. open kcmshell5 fontinst
2. look through fonts, note some serif fonts
3. search for "serif" in "Family" and "Style"
4. compare outputs

Actual Results:  
Searching for "serif" doesn't match all serif fonts. Instead only fonts are
displayed where the font name matches "serif"

Expected Results:  
Searching for "serif" should present all serif fonts.

This issue also applies to mono(space), sans( serif), …

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

[Breeze] [Bug 356395] Missing asset in gtk3 theme

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #5 from Christian Stadelmann  ---
I think this bug is correctly reported as 

Product: Breeze
Component: gtk theme

so no need for any action. Your nvidia/Xorg issues could be reported, but
probably belong to either nvidia, freedesktop.org or kernel.org.

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

[Breeze] [Bug 356395] Missing asset in gtk3 theme

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #3 from Christian Stadelmann  ---
Is there any specification which tells Gtk to provide this file? If not I think
it is not an issue in Gtk but in breeze.

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

[plasmashell] [Bug 356318] I can run wayland plasma session from terminal, not from sddm

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #1 from Christian Stadelmann  ---
Same here with Gdm on Fedora 23. I can run plasma/wayland sessions from tty
(`dbus-launch --exit-with-session startplasmacompositor`) but I cannot run them
from gdm, although it has the same command line. Running
plasma-workspace-5.5.3-4.fc23.x86_64 with qt5-qtbase-5.5.1-11.fc23.x86_64 and
gdm-3.18.2-1.fc23.x86_64.

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

[plasmashell] [Bug 356783] Text in Plasma tooltips sometimes becomes a series of smudgy blocks

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #2 from Christian Stadelmann  ---
Previous bug #355677 was closed as RESOLVED WORKSFORME.
I had the same issue sporadically appear for months with gnome-shell on X11.
There are several bug reports in Fedora's bugzilla for it:
https://bugzilla.redhat.com/show_bug.cgi?id=742776 , especially attachment
https://bugzilla.redhat.com/show_bug.cgi?id=742776#attach_550877 .
This issue has gone for me, but I don't know why. Maybe an update in some font
rendering library. You could try changing your hinting settings, that sometimes
helped.

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

[plasmashell] [Bug 356783] Text in Plasma tooltips sometimes becomes a series of smudgy blocks

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #3 from Christian Stadelmann  ---
Also have a look at bug #356680, with upstream bugs
https://bugreports.qt.io/browse/QTBUG-42386 and
https://bugreports.qt.io/browse/QTBUG-36976

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

[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #1 from Christian Stadelmann  ---
Created attachment 96810
  --> https://bugs.kde.org/attachment.cgi?id=96810=edit
software updates widget with corrupted fonts

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

[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #2 from Christian Stadelmann  ---
Created attachment 96811
  --> https://bugs.kde.org/attachment.cgi?id=96811=edit
device manager with corrupted fonts

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

[plasmashell] [Bug 354592] new clipboard applet scrolls very slow

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #3 from Christian Stadelmann  ---
This could be a duplicate of bug #355410.

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

[Breeze] [Bug 358224] breeze dark plasma look and feel: KDE4 applications are using mixed (light and dark) colors, rendering text unreadable

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

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

--- Comment #1 from Christian Stadelmann  ---
I don't know how themes did mess up so much, but this issue is now gone after
deleting and reconfiguring themes several times. I hope it'll stay that way.

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

[kgpg] [Bug 340676] KGpg should support GnuPG 2.1

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #16 from Christian Stadelmann  ---
Yes, the warning is gone with gpg2 (2.1.9).

Fedora 23's version of KGpg seems to prefer gpg 1.x over gpg2 on installation.
So this is a packaging issue. Thanks for your help and sorry for the noise! As
far as this issue affects gpg2 2.1.x, I think it can be closed.

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

[Breeze] [Bug 350682] Double-click on GTK widgets initiates window movement, breaks control of the widget

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #10 from Christian Stadelmann  ---
This issue is still present with inkscape on plasma 5.5.3.

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

[Breeze] [Bug 351099] krunner unusable with dark breeze theme

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #2 from Christian Stadelmann  ---
I am using krunner without issues. Is this issue still present for you with
plasma 5.5.3 and krunner 5.18.0?

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

[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #14 from Christian Stadelmann  ---
Can you please check whether this issue is present with different themes (e.g.
oxygen) too?

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

[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #17 from Christian Stadelmann  ---
Hm, there should be some other packages in your distro for that, but I don't
know of any other dark look and feels.

(In reply to Colin from comment #15)
> (In reply to Christian Stadelmann from comment #14)
> > Can you please check whether this issue is present with different themes
> > (e.g. oxygen) too?
> 
> It's present for all dark Desktop Themes, including Oxygen. However, I don't
> know how to choose a different Look And Feel to test. The only options under
> Look And Feel are Breeze/Breeze Dark. There's no button to install another
> Look And Feel.

Thanks. I am running into a similiar issue, but it affects different
applications. I'll link it here.

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

[Breeze] [Bug 358224] New: breeze dark plasma look and feel: KDE4 applications are using mixed (light and dark) colors, rendering text unreadable

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 358224
   Summary: breeze dark plasma look and feel: KDE4 applications
are using mixed (light and dark) colors, rendering
text unreadable
   Product: Breeze
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: dah5a...@genodeftest.de

I am running plasma 5.5.3 with breeze dark look and feel. No matter what I set
as desktop theme (Oxygen or Breeze) and no matter which widget style I choose
(Oxygen, Breeze, Fusion), some applications behave weird. They are partially
rendered with a dark breeze theme, partially rendered with a white theme that
looks like it were a Gtk 2.x theme. They are rendering fonts in lists in light
gray on very light gray. Icons are breeze symbolic icons, mostly using white
and very light colors, thus are not visible either.

I think (but I am not sure) that only KDE4/Qt4 applications are affected, but
KDE5/Qt5 applications are not. This theory is based on the following lists:

List of affected applications:
* Kleopatra
* KGpg
* KMail
* KSnapshot
* KDebugDialog
* Ark
* KOrganizer
* Okular
* Dragon Player
* KTouch
* showFoto
* digiKam
* Konqueror

List of not affected applications:
* dolphin (including preferences dialog)
* konsole (including preferences dialog)
* plasma itself including most of its widgets and widget preferences dialogs
* kwrite (including preferences dialog)
* KCalc
* KCharselect
* KAlgebra
* KSysguard
* Marble

Additional info:
This issue is somewhat similiar to bug #343369, but it affects all kinds of UI
elements, not just ComboBoxes in KCM.

I don't have any other dark desktop look and feel to test, so I can't make sure
this isn't a bug somewhere else, e.g. in Qt4's theming engine or KDE4's
widgets. Please reassign if you know better (you probably do).

Reproducible: Always

Steps to Reproduce:
1. start any of the applications listed above

Actual Results:  
Applications are partially rendered in a light, partially rendered in a black
theme. Some widgets have mixed themes, e.g. light fonts (from dark theme) and
light/white background (from light theme).

Expected Results:  
Applications should look consistent, having only one single theme.

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

[kgpg] [Bug 340676] KGpg should support GnuPG 2.1

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #13 from Christian Stadelmann  ---
Hm, my kgpg says:

kgpg(4437) GnupgBinary::setBinary: checking version of GnuPG executable "gpg"
kgpg(4437) GnupgBinary::setBinary: version is "1.4.20" 66580

and I have both gpg 1.4.20  and gpg2 2.1.9 installed. After setting the gpg
binary path to "gpg2" instead of "gpg" what it was before, this message is gone
and KGpg works fine.

Shouldn't KGpg use gnupg2 by default? Is this a packaging issue?

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

[kgpg] [Bug 340676] KGpg should support GnuPG 2.1

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #14 from Christian Stadelmann  ---
Sorry, I didn't mean "this message is gone" but meant "it now prints this:

kgpg(5082) GnupgBinary::setBinary: checking version of GnuPG executable "gpg2"
kgpg(5082) GnupgBinary::setBinary: version is "2.1.9" 131337

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

[kleopatra] [Bug 358210] New: Add support for secure checksums: SHA-2 instead of SHA-1 and MD5

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 358210
   Summary: Add support for secure checksums: SHA-2 instead of
SHA-1 and MD5
   Product: kleopatra
   Version: 2.2.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: dah5a...@genodeftest.de
CC: kdepim-b...@kde.org, m...@kde.org

Currently Kleopatra supports md5sum and sha1sum to generate checksums. Using
sha256sum and sha512sum would be highly appreciated since MD5 is known to be
broken for years and SHA-1 is very weak, its use is highly discouraged.

Reproducible: Always

Steps to Reproduce:
1. Open preferences
2. go to crypto operations, tab "File operations"
3. choose "Checksum program to use"

Actual Results:  
only md5sum (broken) and sha1sum (very weak) are available

Expected Results:  
sha256sum and sha512sum should be available. If possible (violation of
standards?) one of those commands based on SHA-2 should be default.

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

[plasmashell] [Bug 358187] New: keyboard layout always is default (en_US) in wayland plasma sessions

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 358187
   Summary: keyboard layout always is default (en_US) in wayland
plasma sessions
   Product: plasmashell
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: dah5a...@genodeftest.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Some keyboard layouts are not applied in plasma/Wayland sessions. This issue is
specific to the combination of plasma and wayland.

Reproducible: Always

Steps to Reproduce:
1. Enable de-neo2 keyboard layout
2. log in into plasma wayland session
3. test typing

Actual Results:  
default (en-US) keyboard layout is used

Expected Results:  
de-neo2 keyboard layout should be used

I don't know whether this issue is specific to de-neo2 keyboard layout.

The same setup works fine in plasma/X11 sessions, in Gnome/X11 and in
Gnome/Wayland sessions.

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

[plasmashell] [Bug 358040] New: [Application Overview] Show search field instead of text

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 358040
   Summary: [Application Overview] Show search field instead of
text
   Product: plasmashell
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: dah5a...@genodeftest.de
CC: plasma-b...@kde.org

Currently, Kicker shows a very large text in application overview ("Suchbegriff
eingeben…" in German). It shows a longer (still very large) text when typing
something ("Es wird nach »a« gesucht" in German).

I propose a different solution: Display a search field with default text ("Type
to start searching") which has focus. This UI elements can be reused and will
be re-cognized by users. Having a common GUI widget they are used to is easier
for users than haing some text to read.

Reproducible: Always

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

[plasmashell] [Bug 357985] New: [rfe] improve application search results

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 357985
   Summary: [rfe] improve application search results
   Product: plasmashell
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: dah5a...@genodeftest.de
CC: plasma-b...@kde.org

Currently there seems to be no algorithm to smartly reorder search results. If
you search for some string the first matching application will be displayed,
not the best match.

Gnome-shell activities overview does these (I think):
1. order "trailing matches" before in-name matches
2. remember frequently used applications and give them a higher priority

Reproducible: Always

Steps to Reproduce:
1. Open application search
2. type something
3. look at results
4. select application to run (mouse or keyboard)

Actual Results:  
When searching for "tor", "Designeditor" is placed first, "Tor Browser" is
placed on ~8th position.

This doesn't change even when I repeat those steps above.

Expected Results:  
When searching for "tor", "Tor Browser" is the best match and should be placed
first.

When repeatedly searching and choosing one application, this application should
be displayed first. With this I don't need to use mouse or arrow keys to select
the application I want to start.

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

[plasmashell] [Bug 357744] [wayland] startplasmacompositor fails because it cannot start qdbus for D-Bus

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #9 from Christian Stadelmann  ---
I'm not running into the crasher you see, instead startplasmacompositor is
running fine and actually starts a plasma-wayland session for me. The crash you
are seeing is something different. I guess it is an qt issue too. I am running
qt5-qtbase-5.5.1-11.fc23.x86_64. If yours is working fine with that version you
should probably report a regression to Qt5.

My issue itself is solved since I just didn't get the right command line, as
you figured out for comment #7. Thank you!

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

[systemsettings] [Bug 356530] Keyboard shortcuts should be searchable across components

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

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

[kgpg] [Bug 340676] KGpg should support GnuPG 2.1

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #11 from Christian Stadelmann  ---
(In reply to Christian Stadelmann from comment #10)
> (In reply to Rolf Eike Beer from comment #6)
> > That warning should be gone in Applications 14.12.
> 
> This warning is not gone in kgpg 15.08.3.

Sorry, I meant Kgpg 2.16.1 on KDE 4.14.14, which is what it is reporting in its
about dialog. It is packaged from KDE Applications 15.08.3 though.

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

[kgpg] [Bug 340676] KGpg should support GnuPG 2.1

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #10 from Christian Stadelmann  ---
(In reply to Rolf Eike Beer from comment #6)
> That warning should be gone in Applications 14.12.

This warning is not gone in kgpg 15.08.3.

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

[kleopatra] [Bug 341293] Kleopatra self-test should not expect gpg-agent to be running for GnuPG >= 2.1

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

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

[plasmashell] [Bug 357744] [wayland] startplasmacompositor fails because it cannot start qdbus for D-Bus

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #6 from Christian Stadelmann  ---
Hm, yes, looks like a bootstrapping problem: startplasmacompositor requires
qdbus which requires X11 which doesn't run yet because it should be started as
nested XWayland server…

This could be specific to how fedora handles X and wayland sessions running on
separate ttys.

The question is: Can dbus-daemon start without $DISPLAY and having it set
later? Or can startplasmacompositor be changed to start without dbus-daemon?

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

[frameworks-plasma] [Bug 355410] the scroll speed of QML scroll area is too slow with Libinput

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #2 from Christian Stadelmann  ---
Same issue here with plasma 5.5.3 on Fedora 23.

I'm also not sure that Plasma is to blame since this issue is also present in
dolphin and kcm. Is this a bug in Qt?

Expected number of lines scrolled, working fine in:
* Qt5 applications like ksysguard 5.5.3, kwrite 15.08.3, konsole 15.08, most
parts of KDE control center, KGpg
* Gtk2 and Gtk3 applications

Scrolls less than a single line per scroll wheel move in:
* Dolphin 15.08.1: Places panel, file list (central component), folders panel,
but NOT terminal panel
* Plasma application overview (Application Dashboard in kdeplasma-addons)
* Plasma application starter
* Plasma indicator for removable devices (enable showing all devices in
preferences to have enough devices to list)
* KDE control center, section window decoration designs

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

[Breeze] [Bug 356395] Missing asset in gtk3 theme

[Christian Stadelmann via KDE Bugzilla]

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

Christian Stadelmann  changed:

   What|Removed |Added

 CC||dah5a...@genodeftest.de

--- Comment #1 from Christian Stadelmann  ---
Same here. Starting gtk+ 3.18.x applications with horizontal scrollbars visible
will result in this error message. File
file:///usr/share/themes/Breeze-Dark/gtk-3.0/assets/scrollbar-slider-overlay-horizontal-dark.png
doesn't exist. This can be easily reproduced when just starting gedit or
nautilus and adding some content until horizontal scrollbars are shown. This
issue is not related to nvidia. This issue is not present with Gtk default
theme Adwaita.

On https://apps.fedoraproject.org/packages/adwaita-icon-theme/ you can get a
list of all assets for adwaita icon theme when clicking on "Contents".

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

[kfind] [Bug 357788] New: [rfe] Let users customize columns

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 357788
   Summary: [rfe] Let users customize columns
   Product: kfind
   Version: 2.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dah5a...@genodeftest.de

KFind displays many columns in search results: Name, Folder, Size, mtime,
permissions, first match. II don't need to see mtime, size and permissions
columns. I don't see a way to disable them.

Probably those can be disabled when changing columns in dolphin, but I want
dolphin to stay the way it is, displaying these columns.

Reproducible: Always

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

[plasmashell] [Bug 357744] [wayland] startplasmacompositor fails because it cannot start qdbus for D-Bus

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #4 from Christian Stadelmann  ---
So it should be the distro (Fedora) to change qdbus to qdbus-qt5?

$ which qdbus
/usr/bin/qdbus

$ which qdbus-qt5
/usr/bin/qdbus-qt5

`$ env | grep PATH` includes /usr/bin.

I think startplasmacompositor succeeds in finding qdbus but qdbus fails in
startplasmacompositor line 163. When run from tty both qdbus and qdbus-qt5 fail
with this error message:

Could not connect to D-Bus server: org.freedesktop.DBus.Error.NotSupported:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

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

[plasmashell] [Bug 357821] New: Application overview: support keyboard navigation

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 357821
   Summary: Application overview: support keyboard navigation
   Product: plasmashell
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: dah5a...@genodeftest.de
CC: plasma-b...@kde.org

Application overview provides barely any keyboard navigation.

Reproducible: Always

Steps to Reproduce:
1. Open application overview (alternative to application menu)
2. search for something
3. try to use keyboard to navigate between results (arrow keys) and open result
(enter)

Actual Results:  
Arrow keys don't work at all.
Using the Enter key to activate currently selected item sometimes works,
sometimes doesn't.

Expected Results:  
Applications overview should be fully keyboard-navigable.

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

[plasmashell] [Bug 357744] [wayland] startplasmacompositor fails because it cannot start qdbus for D-Bus

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #1 from Christian Stadelmann  ---
I am quite new to KDE and unsure whether this is the correct product/component.
Feel free to reassign since you probably know better than me.

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

[plasmashell] [Bug 357744] [wayland] startplasmacompositor fails because it cannot start qdbus for D-Bus

[Christian Stadelmann via KDE Bugzilla]

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

--- Comment #2 from Christian Stadelmann  ---
Running startplasmacompositor from inside a plasma session works fine, but
starts to a black window.

And btw shouldn't this be qdbus-qt5 instead of qdbus?

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