Your message dated Tue, 5 Jul 2016 18:24:44 +0200
with message-id
<CANnVG6=rr+f6yzkjoxd0ehw0aoaoivx7r9bvtsm9tne3m+z...@mail.gmail.com>
and subject line Re: Bug#829385: dunst not working with example config
(Warning: Unknown keyboard shortcut: ctrl+grave)
has caused the Debian Bug report #829385,
regarding dunst not working with example config (Warning: Unknown keyboard
shortcut: ctrl+grave)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
829385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829385
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dunst
Version: 1.1.0-2
Severity: important
Dear Maintainer,
dunst on Debian Testing is not working with its own example
configuration. According to the man page, this is found at
/usr/share/doc/dunst/dunstrc.example.gz . I have extracted this file and
launched dunst as follows:
> $ dunst -config dunstrc.example
> Warning: Unknown keyboard shortcut: ctrl+grave
From the example config:
> # Close all notifications.
> close_all = ctrl+shift+space
>
> # Redisplay last message(s).
> # On the US keyboard layout "grave" is normally above TAB and left
> # of "1".
> history = ctrl+grave
>
> # Context menu.
> context = ctrl+shift+period
I am not quite sure why *this exact* keyboard shortcut is causing
trouble, however the other one are working fine.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dunst depends on:
ii libc6 2.22-11
ii libcairo2 1.14.6-1+b1
ii libdbus-1-3 1.10.8-1
ii libfreetype6 2.6.3-3+b1
ii libglib2.0-0 2.48.1-1
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii libx11-6 2:1.6.3-1
ii libxdg-basedir1 1.2.0-1
ii libxext6 2:1.3.3-1
ii libxft2 2.3.2-1
ii libxinerama1 2:1.1.3-1+b1
ii libxss1 1:1.2.2-1
dunst recommends no packages.
dunst suggests no packages.
-- no debconf information
Best Regards,
Jack Henschel
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Improving the documentation is always a good idea. Please take this
upstream to https://github.com/knopwob/dunst/issues.
On Tue, Jul 5, 2016 at 10:24 AM, Jack Henschel <[email protected]> wrote:
> Hi Michael,
>
> that's interesting. I am running a 'normal', 'default' german layout,
> therefore I assumed my setup is not *that* special. Oh well.
>
> But you're right, since german keyboard don't have directl access to the
> tilde, they only have 'dead_grave' (AltGr+ and +).
>
> > $ xmodmap -pke | grep grave
> > keycode 21 = dead_acute dead_grave dead_acute dead_grave
> > dead_cedilla dead_ogonek dead_cedilla
>
> My keyboard is configured like so:
> > $ localectl status
> > System Locale: LANG=en_US.UTF-8
> > VC Keymap: n/a
> > X11 Layout: de
> > X11 Model: pc105
> > X11 Options: terminate:ctrl_alt_bksp
>
> Now, this is definitely not a bug in dunst, but maybe we could at least
> document that this key is not available on all keyboards layouts (as
> opposed to 'space' or 'shift' for example).
> A simple note in the default config should be adequate.
>
> Best regards,
> Jack Henschel
>
> On 07/05/2016 09:43 AM, Michael Stapelberg wrote:
> > control: severity -1 normal
> >
> > The error message you’re seeing is printed when dunst cannot resolve the
> > provided key symbol (“grave”) into a key code.
> >
> > Key symbols depend on your keyboard layout, and the default config of
> > dunst thus probably won’t be able to accomodate all possible layouts.
> >
> > You can use “xmodmap -pke | grep grave” to see which keys contain the
> > “grave” symbol in your current layout.
> >
> > I’m not sure with which layout dunst was developed/tested, but possible
> > fixes include changing your layout or changing your config file.
> >
> > I’m not convinced yet that there’s an actual bug here.
> >
> > On Sun, Jul 3, 2016 at 12:29 AM, Jack Henschel <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > Package: dunst
> > Version: 1.1.0-2
> > Severity: important
> >
> > Dear Maintainer,
> >
> > dunst on Debian Testing is not working with its own example
> > configuration. According to the man page, this is found at
> > /usr/share/doc/dunst/dunstrc.example.gz . I have extracted this file
> and
> > launched dunst as follows:
> >
> > > $ dunst -config dunstrc.example
> > > Warning: Unknown keyboard shortcut: ctrl+grave
> >
> > From the example config:
> >
> > > # Close all notifications.
> > > close_all = ctrl+shift+space
> > >
> > > # Redisplay last message(s).
> > > # On the US keyboard layout "grave" is normally above TAB and left
> > > # of "1".
> > > history = ctrl+grave
> > >
> > > # Context menu.
> > > context = ctrl+shift+period
> >
> > I am not quite sure why *this exact* keyboard shortcut is causing
> > trouble, however the other one are working fine.
> >
> >
> > -- System Information:
> > Debian Release: stretch/sid
> > APT prefers testing
> > APT policy: (500, 'testing')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> >
> > Versions of packages dunst depends on:
> > ii libc6 2.22-11
> > ii libcairo2 1.14.6-1+b1
> > ii libdbus-1-3 1.10.8-1
> > ii libfreetype6 2.6.3-3+b1
> > ii libglib2.0-0 2.48.1-1
> > ii libpango-1.0-0 1.40.1-1
> > ii libpangocairo-1.0-0 1.40.1-1
> > ii libx11-6 2:1.6.3-1
> > ii libxdg-basedir1 1.2.0-1
> > ii libxext6 2:1.3.3-1
> > ii libxft2 2.3.2-1
> > ii libxinerama1 2:1.1.3-1+b1
> > ii libxss1 1:1.2.2-1
> >
> > dunst recommends no packages.
> >
> > dunst suggests no packages.
> >
> > -- no debconf information
> >
> > Best Regards,
> > Jack Henschel
> >
> >
> >
> >
> > --
> > Best regards,
> > Michael
>
>
--
Best regards,
Michael
--- End Message ---
