tags 791664 upstream,fixed-upstream
thanks

Hi Ansgar,


On 07/07/2015 01:19 PM, Ansgar Burchardt wrote:
> Package: needrestart
> Version: 2.1-1
> Severity: minor
> 
> The notifications by needrestart as shown in GNOME contain visible
> markup, see the attached screenshot.

according to the Desktop Notification Specification[1] GNOME's desktop
notification should drop the unsupported tags. Although using the
paragraph element works in other implementations (i.e. KDE) it was wrong
to use them in needrestart's notification script.

[1] https://developer.gnome.org/notification-spec/#markup


According to the spec[2] each line of the notification body is already a
paragraph. So there is no need for using the paragraph element at all.

[2] https://developer.gnome.org/notification-spec/#basic-design


Thanks & HTH,
Thomas

> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable'), (100, 'unstable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages needrestart depends on:
> ii  dpkg                       1.18.1
> ii  libmodule-find-perl        0.12-1
> ii  libmodule-scandeps-perl    1.19-1
> ii  libproc-processtable-perl  0.51-1
> ii  libsort-naturally-perl     1.03-1
> ii  libterm-readkey-perl       2.32-2
> ii  perl                       5.20.2-6
> 
> needrestart recommends no packages.
> 
> Versions of packages needrestart suggests:
> ii  libnotify-bin  0.7.6-2
> 
> -- no debconf information
> 


-- 

    ::  WWW:                         http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:                   xmpp:[email protected]  :::
    ::  flickr:              http://www.flickr.com/photos/laugufe/  ::


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to