[kate] [Bug 413751] New: Open links in LSP tooltips
https://bugs.kde.org/show_bug.cgi?id=413751 Bug ID: 413751 Summary: Open links in LSP tooltips Product: kate Version: 19.11.70 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com Target Milestone: --- Would be nice to be able to open doc links in RLS tooltips. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 413031] libdbusmenu-qt fails to update with kdesrc-build
https://bugs.kde.org/show_bug.cgi?id=413031 Matthias Fauconneau changed: What|Removed |Added CC||matthias.fauconneau@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408943] KWin-on-libinput ignores keyboard KCM settings; uses default repeat delay/rate
https://bugs.kde.org/show_bug.cgi?id=408943 Matthias Fauconneau changed: What|Removed |Added CC||matthias.fauconneau@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 406868] baloo_file_extractor fails MTimeDB::del with MDB_BAD_TXN, constant high CPU use
https://bugs.kde.org/show_bug.cgi?id=406868 Matthias Fauconneau changed: What|Removed |Added CC||matthias.fauconneau@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 393096] New: Cannot configure Elisa
https://bugs.kde.org/show_bug.cgi?id=393096 Bug ID: 393096 Summary: Cannot configure Elisa Product: elisa Version: 0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: matthias.fauconn...@gmail.com Target Milestone: --- The service 'Elisa Local Files Indexer' does not provide an interface 'KCModule' with keyword 'kcm_elisa_local_file' The module didn't seem to be found at all until I export QT_PLUGIN_PATH=$QT_PLUGIN_PATH:/usr/lib/x86_64-linux-gnu/plugins/kcms Even then I get : Error loading plugin: "The shared library was not found." This module has no valid entry symbol at all. The reason could be that it's still using K_EXPORT_COMPONENT_FACTORY with a custom X-KDE-FactoryName which is not supported anymore (on Kubuntu 18.04 / KDE 5.44) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 375952] Gwenview crashes when opening PNG image in folder containing APNG images.
https://bugs.kde.org/show_bug.cgi?id=375952 --- Comment #8 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- I don't have those files anymore. I was opening PNGs. Gwenview crashed scanning for exiv metadata in APNGs in the same folder. Those files didn't have metadata, exiv was throwing an uncatched exception as it doesn't support APNG. IIRC. On Sun, Dec 10, 2017, 21:35 Henrik Fehlauer <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=375952 > > Henrik Fehlauer <rk...@lab12.net> changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > CC||rk...@lab12.net > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #7 from Henrik Fehlauer <rk...@lab12.net> --- > Matthias: By any chance, could you attach a zip with the minimal needed > images > / directory structure to crash Gwenview? I can't really reproduce here with > both exiv2 version 0.25 and 0.26 and some random APNGs (but they don't > contain > exiv metadata apparently, either). > > Also I noticed the APNGs weren't animated for me at all in Gwenview (in > Firefox > they were fine), are they for you? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 381152] New: Live preview flickers
https://bugs.kde.org/show_bug.cgi?id=381152 Bug ID: 381152 Summary: Live preview flickers Product: kile Version: 2.9.60 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: matthias.fauconn...@gmail.com Target Milestone: --- While I appreciate the live preview, I find the flicker when it displays a blank page while loading distracting. The old view should be kept until the new view is rendered. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 381150] New: Option to hide page bar
https://bugs.kde.org/show_bug.cgi?id=381150 Bug ID: 381150 Summary: Option to hide page bar Product: kile Version: 2.9.60 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: matthias.fauconn...@gmail.com Target Milestone: --- Okular has an option to hide page bar. I could not find it in Kile's embedded viewer. It would allow to reduce UI clutter and align the bottom of the PDF viewer with the bottom of the text editor (when the messages bar is hidden). -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 381149] New: Option to hide tabbar when a single document is opened
https://bugs.kde.org/show_bug.cgi?id=381149 Bug ID: 381149 Summary: Option to hide tabbar when a single document is opened Product: kile Version: 2.9.60 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: matthias.fauconn...@gmail.com Target Milestone: --- An option to hide tabbar when a single document is opened would reduce UI clutter and align the top of the text editor with the top of the PDF viewer. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 375952] Gwenview crashes when opening PNG image in folder containing APNG images.
https://bugs.kde.org/show_bug.cgi?id=375952 --- Comment #5 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- Just noticed, this doesnt look like a segfault but an unhandled exception. It is valid for Exiv2 to abort if it doesnt support APNGs. So it would seem issues are also Gwenview calling Exiv2 on APNGs and not catching the exception (in Exiv2ImageLoader::load or LoadingDocumentImplPrivate::loadMetaInfo), maybe there is a catch further up the (semantic) call chain, but it cannot be unwinded because of the intervening QtConcurrent threading ? On Mon, Feb 6, 2017 at 1:49 PM, Matthias Fauconneau < matthias.fauconn...@gmail.com> wrote: > As a workaround, I disabled PNG support in exiv2. > I wonder why when I open an image, Gwenview tries to load metadata of > another one though. > > On Mon, Feb 6, 2017 at 12:39 PM, Christoph Feck <bugzilla_nore...@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=375952 >> >> Christoph Feck <cf...@kde.org> changed: >> >>What|Removed |Added >> >> >> Status|NEEDSINFO |RESOLVED >> Resolution|BACKTRACE |UPSTREAM >> >> --- Comment #3 from Christoph Feck <cf...@kde.org> --- >> The crash is in libexiv2.so.14 >> >> If you know the image that it fails with, please report this issue >> directly to >> libexiv2 developers via http://dev.exiv2.org/projects/exiv2/issues >> >> -- >> You are receiving this mail because: >> You reported the bug. >> > > -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 375952] Gwenview crashes when opening PNG image in folder containing APNG images.
https://bugs.kde.org/show_bug.cgi?id=375952 --- Comment #4 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- As a workaround, I disabled PNG support in exiv2. I wonder why when I open an image, Gwenview tries to load metadata of another one though. On Mon, Feb 6, 2017 at 12:39 PM, Christoph Feck <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=375952 > > Christoph Feck <cf...@kde.org> changed: > >What|Removed |Added > > > Status|NEEDSINFO |RESOLVED > Resolution|BACKTRACE |UPSTREAM > > --- Comment #3 from Christoph Feck <cf...@kde.org> --- > The crash is in libexiv2.so.14 > > If you know the image that it fails with, please report this issue > directly to > libexiv2 developers via http://dev.exiv2.org/projects/exiv2/issues > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 375952] Gwenview crashes when opening PNG image in folder containing APNG images.
https://bugs.kde.org/show_bug.cgi?id=375952 --- Comment #2 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- Created attachment 103860 --> https://bugs.kde.org/attachment.cgi?id=103860=edit Backtrace Exiv2::PngImage::readMetadata -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 375952] New: Gwenview crashes when opening PNG image in folder containing APNG images.
https://bugs.kde.org/show_bug.cgi?id=375952 Bug ID: 375952 Summary: Gwenview crashes when opening PNG image in folder containing APNG images. Product: gwenview Version: 16.12.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com CC: myr...@kde.org Target Milestone: --- The APNG previews/opens fine in Dolphin/Gwenview. Opening a (normal) PNG file in the same folder crashes. libpng error: PNG unsigned integer out of range QImageReader::read() using format hint "apng" failed: "Unknown error" A bad Qt image decoder moved the buffer to 74 in a call to canRead()! Rewinding. Image format is actually "png" not "apng" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371229] Drag starts on window below if window dragged on closes while dragging
https://bugs.kde.org/show_bug.cgi?id=371229
--- Comment #5 from Matthias Fauconneau <matthias.fauconn...@gmail.com> ---
Thank you for the information.
So I guess it would need either an X server hack, or the application
(toolkit) should only start drags when the mouse move is after a mouse
press on its window. Actually that's what I do in my app, I wonder why is
it not the normal way applications (toolkits) handle drag starts ? maybe
some interaction with inter application drags ?
On Fri, Oct 28, 2016 at 1:04 PM, Martin Gräßlin <bugzilla_nore...@kde.org>
wrote:
> https://bugs.kde.org/show_bug.cgi?id=371229
>
> Martin Gräßlin <mgraess...@kde.org> changed:
>
>What|Removed |Added
>
>
> Resolution|WAITINGFORINFO |INVALID
> Status|NEEDSINFO |RESOLVED
>
> --- Comment #4 from Martin Gräßlin <mgraess...@kde.org> ---
> Well on X11 the window manager is not involved in that. The first drag is
> handled inside the application - the second drag as well. For the second
> application there is no chance to know what was going on.
>
> In fact as far as I understand the problem from an X11 protocol point of
> view
> everything seems fine. A pointer enter is supposed to be sent to the window
> below the cursor as soon as the other window crashes. And the window then
> reacts.
>
> On Wayland the compositor has a little bit more choice, luckily:
>
> case QEvent::MouseMove: {
> if (event->buttons() == Qt::NoButton) {
> // update pointer window only if no button is pressed
> input()->pointer()->update();
> }
>
> --
> You are receiving this mail because:
> You reported the bug.
>
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 371229] Drag starts on window below if window dragged on closes while dragging
https://bugs.kde.org/show_bug.cgi?id=371229 --- Comment #3 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- This is on X11. I guess that's a reason to use Wayland then... No workarounds are possible on X11 ? On Fri, Oct 28, 2016 at 12:46 PM, Martin Gräßlin <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=371229 > > Martin Gräßlin <mgraess...@kde.org> changed: > >What|Removed |Added > > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Martin Gräßlin <mgraess...@kde.org> --- > We need to know which windowing system is used for further investigation. > In > general: on X11 kwin cannot do anything about that. On Wayland that should > not > happen as KWin doesn't update pointer focus while a pointer button is down. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371229] New: Drag starts on window below if window dragged on closes while dragging
https://bugs.kde.org/show_bug.cgi?id=371229 Bug ID: 371229 Summary: Drag starts on window below if window dragged on closes while dragging Product: kwin Version: 5.8.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com I have a program where I drag (move the mouse while a button is pressed) to change the view. If the program closes during the drag (crashes) and I keep dragging (without releasing and pressing the mouse button again), a new drag selection starts on the window below (e.g QtCreator or KWrite). This new drag is not wanted, I would expect a drag on the next window to only occur once I release and press the button again. When dragging over the bounds of a window, the windows below correctly ignore the mouse motion, the same should happen when the window closes so long the mouse button is not released and pressed again. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366632] New windows cover full screen going below Plasma panel (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366632 --- Comment #2 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- I do not maximize or set fullscreen, the initial geometry of the window is too large and overlaps under the Plasma panel. Maybe the geometry of the maximized window was stored from a session without a panel, persists and is not clipped by KWin/Wayland. On Wed, Aug 31, 2016 at 3:01 PM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366632 > > --- Comment #1 from Martin Gräßlin <mgraess...@kde.org> --- > Just for clarification: you mean maximization and not fullscreen, right? > That > is click the maximize button and not using a fullscreen menu item. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 367080] New: Keyboard KCM crashes when checking Advanced > Configure keyboard options (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=367080 Bug ID: 367080 Summary: Keyboard KCM crashes when checking Advanced > Configure keyboard options (on Wayland) Product: systemsettings Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: ary...@gmail.com Reporter: matthias.fauconn...@gmail.com XInternAtom is called without an X connection : #0 XInternAtom #1 X11Helper::getGroupNames(_XDisplay*, XkbConfig*, X11Helper::FetchType) #2 KCMKeyboardWidget::populateWithCurrentXkbOptions #3 KCMKeyboardWidget::configureXkbOptionsChanged Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland
https://bugs.kde.org/show_bug.cgi?id=366608 --- Comment #10 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- 1) Works for me with Brightness Up (F7), Volume Down (F9) and Up (F10). But strangely Brightness Down (F6) still does not repeat. I see no difference between the keys (libinput-debug-events) and the shortcuts (Global Keyboard Shortcuts). Is there a way to gain more insight in this issue ? 2) The typically long key repeat delay still makes this suboptimal, especially in the urgent volume down case. If handling pressed shortcut on the client side (Powerdevil, KMix) is too complicated, would it be possible to skip the delay and repeat directly based on the key repeat rate ? On Mon, Aug 15, 2016 at 5:43 PM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366608 > > Martin Gräßlin <mgraess...@kde.org> changed: > >What|Removed |Added > > > Status|CONFIRMED |RESOLVED > Resolution|--- |FIXED > Latest Commit|| > http://commits.kde.org/kwin >| > |/b9c98bd2b977bd68d79240 >||ac4d60fcadc96b > > --- Comment #9 from Martin Gräßlin <mgraess...@kde.org> --- > Git commit b9c98bd2b977bd68d79240ac4d60fcadc96b by Martin Gräßlin. > Committed on 15/08/2016 at 15:39. > Pushed by graesslin into branch 'master'. > > Trigger global shortcuts also on key-repeat > > Summary: > Restores feature parity with X11. Global shortcuts need to trigger > also for repeat events. An example is the volume key or screen > brightness. > > For other shortcuts like showing yakuake it does not make sense to > trigger on repeat. Thus a long term solution is to add a flag to > global shortcuts whether the key should trigger on repeat. > > Reviewers: #kwin, #plasma_on_wayland > > Subscribers: plasma-devel, kwin > > Tags: #plasma_on_wayland, #kwin > > Differential Revision: https://phabricator.kde.org/D2413 > > M +1-1input.cpp > > http://commits.kde.org/kwin/b9c98bd2b977bd68d79240ac4d60fcadc96b > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366764] Unsupported Full Screen Mode (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366764 --- Comment #2 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- I noticed the window goes below the shell panel. When focusing away and in again, the panel is correctly hidden below the window. In this state, switching between windowed and fullscreen works correctly with regard to the panel. The issue with the decoration still remains in all cases. On Mon, Aug 15, 2016 at 7:47 AM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366764 > > Martin Gräßlin <mgraess...@kde.org> changed: > >What|Removed |Added > > > Status|UNCONFIRMED |CONFIRMED > Ever confirmed|0 |1 > > --- Comment #1 from Martin Gräßlin <mgraess...@kde.org> --- > I doubt it's a KWin bug - KWin actually handles fullscreen correctly. The > failure at least is consistent, I was able to reproduce with both Gwenview > and > KDevelop. Given https://bugreports.qt.io/browse/QTBUG-54883 I'm tempted to > blame Qt, but I'll investigate more. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366786] New: Libraw fails to build with CLang (non constant initializer narrowing)
https://bugs.kde.org/show_bug.cgi?id=366786
Bug ID: 366786
Summary: Libraw fails to build with CLang (non constant
initializer narrowing)
Product: digikam
Version: 5.1.0
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Raw-Engine
Assignee: digikam-de...@kde.org
Reporter: matthias.fauconn...@gmail.com
[ 88%] Building CXX object
libs/rawengine/libraw/CMakeFiles/libraw.dir/src/libraw_cxx.cpp.o
In file included from
/var/tmp/portage/media-gfx/digikam-5.1.0/work/digikam-5.1.0/core/libs/rawengine/libraw/src/libraw_cxx.cpp:5203:
/var/tmp/portage/media-gfx/digikam-5.1.0/work/digikam-5.1.0/core/libs/rawengine/libraw/src/../internal/libraw_x3f.cpp:1249:19:
error:
non-constant-expression cannot be narrowed from type 'int' to 'int16_t'
(aka 'short') in initializer list [-Wc++11-narrowing]
int16_t c[3] = {offset,offset,offset};
^~
/var/tmp/portage/media-gfx/digikam-5.1.0/work/digikam-5.1.0/core/libs/rawengine/libraw/src/../internal/libraw_x3f.cpp:1249:19:
note:
insert an explicit cast to silence this issue
int16_t c[3] = {offset,offset,offset};
^~
static_cast( )
/var/tmp/portage/media-gfx/digikam-5.1.0/work/digikam-5.1.0/core/libs/rawengine/libraw/src/../internal/libraw_x3f.cpp:1249:26:
error:
non-constant-expression cannot be narrowed from type 'int' to 'int16_t'
(aka 'short') in initializer list [-Wc++11-narrowing]
int16_t c[3] = {offset,offset,offset};
^~
/var/tmp/portage/media-gfx/digikam-5.1.0/work/digikam-5.1.0/core/libs/rawengine/libraw/src/../internal/libraw_x3f.cpp:1249:26:
note:
insert an explicit cast to silence this issue
int16_t c[3] = {offset,offset,offset};
^~
static_cast( )
/var/tmp/portage/media-gfx/digikam-5.1.0/work/digikam-5.1.0/core/libs/rawengine/libraw/src/../internal/libraw_x3f.cpp:1249:33:
error:
non-constant-expression cannot be narrowed from type 'int' to 'int16_t'
(aka 'short') in initializer list [-Wc++11-narrowing]
int16_t c[3] = {offset,offset,offset};
^~
/var/tmp/portage/media-gfx/digikam-5.1.0/work/digikam-5.1.0/core/libs/rawengine/libraw/src/../internal/libraw_x3f.cpp:1249:33:
note:
insert an explicit cast to silence this issue
int16_t c[3] = {offset,offset,offset};
^~
static_cast( )
P.S: Is there an option to either disable or use system libraw ?
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 366764] New: Unsupported Full Screen Mode (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366764 Bug ID: 366764 Summary: Unsupported Full Screen Mode (on Wayland) Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com Full screen mode (e.g. in Gwenview) does not work. I am not sure whether Gwenview fails to request, or KWin fails to reconfigure. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366625] Single event reported through multiple devices is not coalesced (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366625 --- Comment #4 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- Sorry, that was 1.11.0. it's notify_key:1794 On Fri, Aug 12, 2016 at 4:36 PM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366625 > > --- Comment #3 from Martin Gräßlin <mgraess...@kde.org> --- > > Weston also correctly handle this, by ignoring press on pressed keys > (input.cc:1647). > > My master checkout has only a modifier change ignore there (function > notify_modifiers). As that file is rather large: can you tell me the > function > name to look at? > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366625] Single event reported through multiple devices is not coalesced (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366625 --- Comment #2 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- Weston also correctly handle this, by ignoring press on pressed keys (input.cc:1647). I think this is the way to go for KWin too. Is there already a key state list somewhere ? If I understand correctly, the list, and filter, should be added to KeyboardInputRedirection which is the first object to receive events from all devices. On Thu, Aug 11, 2016 at 2:08 PM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366625 > > --- Comment #1 from Martin Gräßlin <mgraess...@kde.org> --- > Tricky. KWin processes events one by one, thus it doesn't know that it's > the > same key event. And I'm not aware of anything in libinput which would > allow so. > > Also we cannot just ignore all power button events as we need the events > from > there if it does not also trigger the event on the keyboard. Unfortunately > my > notebooks don't have any power button which would trigger an event... > > I see two other possibilities: > * when going through the xkb translation filter the event out if it didn't > change the state (I assume that's what XWayland does) > * make it possible to disable input devices > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366634] New: After minimization, next top window does not gain focus (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366634 Bug ID: 366634 Summary: After minimization, next top window does not gain focus (on Wayland) Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com When minimizing a window, the next top window of the stack does not gain focus. It seems to work fine if the minimized window is an X window. It also works when the previous top window is destroyed instead. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366632] New: New windows cover full screen going below Plasma panel (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366632 Bug ID: 366632 Summary: New windows cover full screen going below Plasma panel (on Wayland) Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com Whenever I open a new application instance (firefox, dolphin, konsole, kwrite, ...), its main window covers the full screen going below Plasma panel. I am not sure if it is Plasma which fails to communicate the geometry of the panels to KWin or KWin which fails to clip the window to the available non-shell area. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366625] New: Single event reported through multiple devices is not coalesced (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366625 Bug ID: 366625 Summary: Single event reported through multiple devices is not coalesced (on Wayland) Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com On my laptop, KEY_POWER is reported both through event4 (Power Button) and event6 (Keyboard). A single press triggers events from both devices. KWin forwards both events to applications without discarding duplicates. On XWayland, events are reported once so it seems to coalesce. This issue is important on compact keyboards where it is common to remap the power key, for example to Delete. I see two options to solve: - Ignore Power button devices as they are not relevant for Wayland input - Discard additional events for same key at same time from different devices Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland
https://bugs.kde.org/show_bug.cgi?id=366608 --- Comment #5 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- I think notifying release events would be a better solution since it would allow smoother/finer brightness adjustments than the low rate of key repeats. So KWin/Wayland requires non-Qt applications to link with KGlobalAccel to register shortcuts ? On Thu, Aug 11, 2016 at 7:11 AM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366608 > > --- Comment #4 from Martin Gräßlin <mgraess...@kde.org> --- > KGlobalAccel actions are only triggered on press events. There is no > additional > call when they are released. > > I played a little bit with my system and there the brightness key sends > press/release combos constantly when being hold. > > > I think not repeating global shortcuts is the correct behaviour. Still > it would make sense for PowerDevil to be notified when the shortcut is > released. > > I'm not sure how we can combine those two. I either make it ignore repeat > events or make it always trigger. To support this we would have to extend > kglobalaccel to add a flag "allow repeat". > > > Also, where is the KGlobalAccel D-Bus interface documentation ? > > Nowhere, it's an internal detail of the KGlobalAccel framework and not a > public > and stable dbus interface. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland
https://bugs.kde.org/show_bug.cgi?id=366608 --- Comment #3 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- I think not repeating global shortcuts is the correct behaviour. Still it would make sense for PowerDevil to be notified when the shortcut is released. I am not clear on how KGlobalAccel signals actions. Maybe it could just send another signal when a shortcut is released. Maybe on the condition a flag is set when setting the shortcut. I understand that disappointingly there is no plan for desktop-agnostic global shortcut registration. But at least it would be useful to have the KGlobalAccel D-Bus interface less Qt specific to allow for easier cross toolkit integration. Also, where is the KGlobalAccel D-Bus interface documentation ? On Thu, Aug 11, 2016 at 5:58 AM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366608 > > --- Comment #2 from Martin Gräßlin <mgraess...@kde.org> --- > Just checked, kwin explicitly ignores key repeat events to trigger global > shortcuts > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366611] Wrong cursor icon after opening context menu
https://bugs.kde.org/show_bug.cgi?id=366611 --- Comment #2 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- Hmm, I cannot seem to reproduce reliably. I'll try to find out the exact circumstances. On Thu, Aug 11, 2016 at 5:50 AM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366611 > > --- Comment #1 from Martin Gräßlin <mgraess...@kde.org> --- > That's with Qt windows? Is that also happening with GTK windows? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366610] Show active shadow for new focused window without flicker under Wayland
https://bugs.kde.org/show_bug.cgi?id=366610 --- Comment #2 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- Indeed, this is only with Oxygen. So switching to Breeze is a workaround for this bug. On Thu, Aug 11, 2016 at 5:49 AM, Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366610 > > --- Comment #1 from Martin Gräßlin <mgraess...@kde.org> --- > That's with Oxygen window decoration? I never saw it, might be due to > Breeze > only having a black shadow. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366611] New: Wrong cursor icon after opening context menu
https://bugs.kde.org/show_bug.cgi?id=366611 Bug ID: 366611 Summary: Wrong cursor icon after opening context menu Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com After opening a context menu, the cursor does not change to the text cursor icon when hovering text fields anymore. Moving the cursor to another window and back fixes the issue. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366610] New: Show active shadow for new focused window without flicker under Wayland
https://bugs.kde.org/show_bug.cgi?id=366610 Bug ID: 366610 Summary: Show active shadow for new focused window without flicker under Wayland Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com Opening a new window (zb an About dialog) exhibits a flickering of the shadow from inactive (black) to active (blue). Even with Instant animation and window decorations animation disabled (not sure if those settings work correctly though because Compositor changes crashes Kwin). No workarounds possible as it seems shadows cannot be disabled. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366609] New: Context menu do not close when discarded on Wayland
https://bugs.kde.org/show_bug.cgi?id=366609 Bug ID: 366609 Summary: Context menu do not close when discarded on Wayland Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: matthias.fauconn...@gmail.com CC: plasma-b...@kde.org After opening a context menu, clicking elsewhere does not close the menu. The context menus can be closed by opening and closing the Application menu. Also affects other Plasma context menus but they can be closed with right click on Plasma (not left click, or any click outside Plasma). Context menus in other applications works fine. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366608] New: Brightness keyboard action does not repeat while key is pressed under Wayland
https://bugs.kde.org/show_bug.cgi?id=366608 Bug ID: 366608 Summary: Brightness keyboard action does not repeat while key is pressed under Wayland Product: Powerdevil Version: 5.7.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: matthias.fauconn...@gmail.com When keeping a brightness up/down key pressed under Wayland, brightness level is changed only by one step. PowerDevil should smoothly increment/decrement the brightness level while the key is pressed. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 362831] Do not increase brightness when entering low battery mode
https://bugs.kde.org/show_bug.cgi?id=362831 Matthias Fauconneau <matthias.fauconn...@gmail.com> changed: What|Removed |Added CC||matthias.fauconneau@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 362830] Allow lowest brightness when using the brightness down/up buttons
https://bugs.kde.org/show_bug.cgi?id=362830 Matthias Fauconneau <matthias.fauconn...@gmail.com> changed: What|Removed |Added CC||matthias.fauconneau@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366606] New: Missing Compose key support on Wayland
https://bugs.kde.org/show_bug.cgi?id=366606 Bug ID: 366606 Summary: Missing Compose key support on Wayland Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com Composing sequences does not seem to be supported on KDE/Wayland. I am not sure which part of the software stack should be responsible for translating compose sequences into symbols. If I understood correctly, it should be handled by the compositor. But maybe a client-side input method would allow context dependent input. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366605] New: Tap-to-click missing on Wayland
https://bugs.kde.org/show_bug.cgi?id=366605 Bug ID: 366605 Summary: Tap-to-click missing on Wayland Product: kwin Version: git master Platform: Tru64 Unix Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com Tapping the trackpad does not click. libinput supports it, but it needs to be enabled. if I understand correctly, libinput leaves configuration to the application, and has no standard configuration method. KWin debug console shows tapEnabledByDefault=false. I do not know where to set this flag, if possible. I could not find any relevant option in System Settings > Mouse. So this might actually be a System Settings bug, I am not sure how the cooperation works. I understand libinput philosophy is to default to disable this feature. Maybe default to enable would be compatible with KDE philosophy. It would avoid some hassle for new configurations. It would be especially sensible on touchpads without buttons. And on devices where the default system defaults to tap-to-click (in this case a Chromebook, I assume Windows and iOS defaults to tap-to-click). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
