#21 2017-03-07 20:00:20

damo

....moderator....

Registered: 2015-08-20

Posts: 6,734

Re: xfce4-notifyd

^ And you can use it for home-brewed notes, popups, reminders etc

---

Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

cpoakes

Member

Registered: 2016-12-02

Posts: 108

Re: xfce4-notifyd

To clarify, you suggest a divergence from previous backporting/porting efforts in that we/I would have to really fork the xfce4-notifyd package and maintain it against the BL changeset, which would mean a partial revert of (at least) the above-mentioned commit, and testing, or keep a legacy notiyd package, whereas until now our ports were always fresh-from-the-source packages built to get upstream bug fixes into BL.

I appreciate your POV, but in this case "fresh-from-the-source" xfce4-notifyd_0.3.4-1(stretch) has an incomplete workaround for GTK3; when it comes to square corners, it is broken. We get the upstream bug, not a fix.

I am not advocating a fork (ugh, a headache we don't want). We can create an up-ported GTK2 xfce4-notifyd package that uses unmodified jessie sources. The jessie LTS team maintains security issues for the next three years; they monitor and apply security changesets not BL devs. BL simply need compile the jessie sources on stretch (with epoch versioning) and recompile if the package receives security updates upstream in jessie LTS.

I find additional reassurances: 1) Most vulnerabilities appear in libraries. Recompiling xfce4-notifyd_0.2.4-3 on stretch utilizes libraries maintained by the stretch team and builds no libraries of its own; 2) There were no security updates applied to xfce4-notifyd in wheezy or stretch, and so far not in jessie - it seems likely the first up-port package would be the only package; and 3) the alternative dunst notification-daemon uses sources from 2014, newer isn't always better.

Assumption: I assume BL reaches EOL with jessie (not jessie LTS) because 1) there is no documentation BL receives LTS support on the website or even in the forums, and 2) that is what St. Philip did.

nobody

The Great

Registered: 2015-08-10

Posts: 3,655

Re: xfce4-notifyd

To clarify, you suggest a divergence from previous backporting/porting efforts in that we/I would have to really fork the xfce4-notifyd package and maintain it against the BL changeset, which would mean a partial revert of (at least) the above-mentioned commit, and testing, or keep a legacy notiyd package, whereas until now our ports were always fresh-from-the-source packages built to get upstream bug fixes into BL.

I appreciate your POV, but in this case "fresh-from-the-source" xfce4-notifyd_0.3.4-1(stretch) has an incomplete workaround for GTK3; when it comes to square corners, it is broken. We get the upstream bug, not a fix.

I am not advocating a fork (ugh, a headache we don't want). We can create an up-ported GTK2 xfce4-notifyd package that uses unmodified jessie sources. The jessie LTS team maintains security issues for the next three years; they monitor and apply security changesets not BL devs. BL simply need compile the jessie sources on stretch (with epoch versioning) and recompile if the package receives security updates upstream in jessie LTS.

I find additional reassurances: 1) Most vulnerabilities appear in libraries. Recompiling xfce4-notifyd_0.2.4-3 on stretch utilizes libraries maintained by the stretch team and builds no libraries of its own; 2) There were no security updates applied to xfce4-notifyd in wheezy or stretch, and so far not in jessie - it seems likely the first up-port package would be the only package; and 3) the alternative dunst notification-daemon uses sources from 2014, newer isn't always better.

Assumption: I assume BL reaches EOL with jessie (not jessie LTS) because 1) there is no documentation BL receives LTS support on the website or even in the forums, and 2) that is what St. Philip did.

Good point. I didn't think of oldstable. Need to evaluate whether to rename the package still however, as the main (Franken-)Xfce desktop still exists.

Assumption: I assume BL Hydrogen reaches EOL

Hydrogen is going to make way for Helium/Stretch, yes. There is no old-stable.

cpoakes

Member

Registered: 2016-12-02

Posts: 108

Re: xfce4-notifyd

Before I go off to play with lxqt-notificationd, anyone got any experience or comments? I like what I see in this screen shot. May be the only user of qt5 libraries in our standard packages, but I'd still like to make a size estimate including libs before ruling it out.

cpoakes

Member

Registered: 2016-12-02

Posts: 108

Re: xfce4-notifyd

Yesterday, I had a quick look at mate-notification-daemon, which is gtk2 of course and "classic", but its "themes" are binary, compiled C "modules" each of which implements the rendering layer in a themed/specific way…writing and maintaining such a theme is a bit tedious.

Binary? Ugh. Thanks for the background and rationale to avoid mate-notification-daemon.

ohnonot

...again

Registered: 2015-09-29

Posts: 5,592

Re: xfce4-notifyd

@ohnonot, I mentioned that dunst looked promising. It's stand-alone, configurable and in the repo. Post your config as a reverence, please?

sorry it took a while.
for what it's worth - my ~/.config/dunst/dunstrc - there isn't much in it really.
also i haven't been able to access either history or context menu.

[global]
font = ubuntu 11

# Allow a small subset of html markup:
#   <b>bold</b>
#   <i>italic</i>
#   <s>strikethrough</s>
#   <u>underline</u>
# 
# For a complete reference see
# <http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
# If markup is not allowed, those tags will be stripped out of the
# message.
allow_markup = yes

# The format of the message.  Possible variables are:
#   %a  appname
#   %s  summary
#   %b  body
#   %i  iconname (including its path)
#   %I  iconname (without its path)
#   %p  progress value if set ([  0%] to [100%]) or nothing
# Markup is allowed
format = "%s\n%b"

# Sort messages by urgency.
sort = yes

# Show how many messages are currently hidden (because of geometry).
indicate_hidden = no

# Alignment of message text.
# Possible values are "left", "center" and "right".
alignment = right

# The frequency with wich text that is longer than the notification
# window allows bounces back and forth.
# This option conflicts with "word_wrap".
# Set to 0 to disable.
bounce_freq = 0

# Show age of message if message is older than show_age_threshold
# seconds.
# Set to -1 to disable.
show_age_threshold = "-1"

# Split notifications into multiple lines if they don't fit into
# geometry.
word_wrap = yes

# Ignore newlines '\n' in notifications.
ignore_newline = no


# The geometry of the window:
#   [{width}]x{height}[+/-{x}+/-{y}]
# The geometry of the message window.
# The height is measured in number of notifications everything else
# in pixels.  If the width is omitted but the height is given
# ("-geometry x2"), the message window expands over the whole screen
# (dmenu-like).  If width is 0, the window expands to the longest
# message displayed.  A positive x is measured from the left, a
# negative from the right side of the screen.  Y is measured from
# the top and down respectevly.
# The width can be negative.  In this case the actual width is the
# screen width minus the width defined in within the geometry option.
geometry = "500x5-10+35"

# Shrink window if it's smaller than the width.  Will be ignored if
# width is 0.
shrink = yes

# The transparency of the window.  Range: [0; 100].
# This option will only work if a compositing windowmanager is
# present (e.g. xcompmgr, compiz, etc.).
transparency = 50

# Don't remove messages, if the user is idle (no mouse or keyboard input)
# for longer than idle_threshold seconds.
# Set to 0 to disable.
idle_threshold = 0

# Which monitor should the notifications be displayed on.
monitor = 0

# Display notification on focused monitor.  Possible modes are:
#   mouse: follow mouse pointer
#   keyboard: follow window with keyboard focus
#   none: don't follow anything
# 
# "keyboard" needs a windowmanager that exports the
# _NET_ACTIVE_WINDOW property.
# This should be the case for almost all modern windowmanagers.
# 
# If this option is set to mouse or keyboard, the monitor option
# will be ignored.
follow = mouse

# Should a notification popped up from history be sticky or timeout
# as if it would normally do.
sticky_history = yes

# Maximum amount of notifications kept in history
history_length = 20

# Display indicators for URLs (U) and actions (A).
show_indicators = yes

# The height of a single line.  If the height is smaller than the
# font height, it will get raised to the font height.
# This adds empty space above and under the text.
line_height = 0

# Draw a line of "separatpr_height" pixel height between two
# notifications.
# Set to 0 to disable.
separator_height = 2

# Padding between text and separator.
padding = 8

# Horizontal padding.
horizontal_padding = 8

# Define a color for the separator.
# possible values are:
#  * auto: dunst tries to find a color fitting to the background;
#  * foreground: use the same color as the foreground;
#  * frame: use the same color as the frame;
#  * anything else will be interpreted as a X color.
separator_color = frame

# Print a notification on startup.
# This is mainly for error detection, since dbus (re-)starts dunst
# automatically after a crash.
startup_notification = false

# dmenu path.
dmenu = dmenu -p dunst:

# Browser for opening urls in context menu.
browser = my browser

# Align icons left/right/off
icon_position = off

# Paths to default icons.
#icon_folders = /usr/share/icons/gnome/16x16/status/:/usr/share/icons/gnome/16x16/devices/

[frame]
width = 2
color = "#444444"

[shortcuts]

# Shortcuts are specified as [modifier+][modifier+]...key
# Available modifiers are "ctrl", "mod1" (the alt-key), "mod2",
# "mod3" and "mod4" (windows-key).
# Xev might be helpful to find names for keys.

# Close notification.
close = mod4+BackSpace

# Close all notifications.
close_all = mod4+mod1+BackSpace

# Redisplay last message(s).
# On the US keyboard layout "grave" is normally above TAB and left
# of "1".
history = mod4+shift+BackSpace

# Context menu.
context = mod4+Menu

[urgency_low]
# IMPORTANT: colors have to be defined in quotation marks.
# Otherwise the "#" and following would be interpreted as a comment.
background = "#222222"
foreground = "#888888"
timeout = 10

[urgency_normal]
background = "#005577"
foreground = "#bbbbbb"
timeout = 10

[urgency_critical]
background = "#900000"
foreground = "#ffffff"
timeout = 0


# Every section that isn't one of the above is interpreted as a rules to
# override settings for certain messages.
# Messages can be matched by "appname", "summary", "body", "icon", "category",
# "msg_urgency" and you can override the "timeout", "urgency", "foreground",
# "background", "new_icon" and "format".
# Shell-like globbing will get expanded.
#
# SCRIPTING
# You can specify a script that gets run when the rule matches by
# setting the "script" option.
# The script will be called as follows:
#   script appname summary body icon urgency
# where urgency can be "LOW", "NORMAL" or "CRITICAL".
# 
# NOTE: if you don't want a notification to be displayed, set the format
# to "".
# NOTE: It might be helpful to run dunst -print in a terminal in order
# to find fitting options for rules.

#[espeak]
#    summary = "*"
#    script = dunst_espeak.sh

#[script-test]
#    summary = "*script*"
#    script = dunst_test.sh

#[ignore]
#    # This notification will not be displayed
#    summary = "foobar"
#    format = ""

#[signed_on]
#    appname = Pidgin
#    summary = "*signed on*"
#    urgency = low
#
#[signed_off]
#    appname = Pidgin
#    summary = *signed off*
#    urgency = low
#
#[says]
#    appname = Pidgin
#    summary = *says*
#    urgency = critical
#
#[twitter]
#    appname = Pidgin
#    summary = *twitter.com*
#    urgency = normal

nobody

The Great

Registered: 2015-08-10

Posts: 3,655

Re: xfce4-notifyd

@ohnonot, I mentioned that dunst looked promising. It's stand-alone, configurable and in the repo. Post your config as a reverence, please?

sorry it took a while.
for what it's worth - my ~/.config/dunst/dunstrc - there isn't much in it really.
also i haven't been able to access either history or context menu.

[global]
font = ubuntu 11

# Allow a small subset of html markup:
#   <b>bold</b>
#   <i>italic</i>
#   <s>strikethrough</s>
#   <u>underline</u>
# 
# For a complete reference see
# <http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
# If markup is not allowed, those tags will be stripped out of the
# message.
allow_markup = yes

# The format of the message.  Possible variables are:
#   %a  appname
#   %s  summary
#   %b  body
#   %i  iconname (including its path)
#   %I  iconname (without its path)
#   %p  progress value if set ([  0%] to [100%]) or nothing
# Markup is allowed
format = "%s\n%b"

# Sort messages by urgency.
sort = yes

# Show how many messages are currently hidden (because of geometry).
indicate_hidden = no

# Alignment of message text.
# Possible values are "left", "center" and "right".
alignment = right

# The frequency with wich text that is longer than the notification
# window allows bounces back and forth.
# This option conflicts with "word_wrap".
# Set to 0 to disable.
bounce_freq = 0

# Show age of message if message is older than show_age_threshold
# seconds.
# Set to -1 to disable.
show_age_threshold = "-1"

# Split notifications into multiple lines if they don't fit into
# geometry.
word_wrap = yes

# Ignore newlines '\n' in notifications.
ignore_newline = no


# The geometry of the window:
#   [{width}]x{height}[+/-{x}+/-{y}]
# The geometry of the message window.
# The height is measured in number of notifications everything else
# in pixels.  If the width is omitted but the height is given
# ("-geometry x2"), the message window expands over the whole screen
# (dmenu-like).  If width is 0, the window expands to the longest
# message displayed.  A positive x is measured from the left, a
# negative from the right side of the screen.  Y is measured from
# the top and down respectevly.
# The width can be negative.  In this case the actual width is the
# screen width minus the width defined in within the geometry option.
geometry = "500x5-10+35"

# Shrink window if it's smaller than the width.  Will be ignored if
# width is 0.
shrink = yes

# The transparency of the window.  Range: [0; 100].
# This option will only work if a compositing windowmanager is
# present (e.g. xcompmgr, compiz, etc.).
transparency = 50

# Don't remove messages, if the user is idle (no mouse or keyboard input)
# for longer than idle_threshold seconds.
# Set to 0 to disable.
idle_threshold = 0

# Which monitor should the notifications be displayed on.
monitor = 0

# Display notification on focused monitor.  Possible modes are:
#   mouse: follow mouse pointer
#   keyboard: follow window with keyboard focus
#   none: don't follow anything
# 
# "keyboard" needs a windowmanager that exports the
# _NET_ACTIVE_WINDOW property.
# This should be the case for almost all modern windowmanagers.
# 
# If this option is set to mouse or keyboard, the monitor option
# will be ignored.
follow = mouse

# Should a notification popped up from history be sticky or timeout
# as if it would normally do.
sticky_history = yes

# Maximum amount of notifications kept in history
history_length = 20

# Display indicators for URLs (U) and actions (A).
show_indicators = yes

# The height of a single line.  If the height is smaller than the
# font height, it will get raised to the font height.
# This adds empty space above and under the text.
line_height = 0

# Draw a line of "separatpr_height" pixel height between two
# notifications.
# Set to 0 to disable.
separator_height = 2

# Padding between text and separator.
padding = 8

# Horizontal padding.
horizontal_padding = 8

# Define a color for the separator.
# possible values are:
#  * auto: dunst tries to find a color fitting to the background;
#  * foreground: use the same color as the foreground;
#  * frame: use the same color as the frame;
#  * anything else will be interpreted as a X color.
separator_color = frame

# Print a notification on startup.
# This is mainly for error detection, since dbus (re-)starts dunst
# automatically after a crash.
startup_notification = false

# dmenu path.
dmenu = dmenu -p dunst:

# Browser for opening urls in context menu.
browser = my browser

# Align icons left/right/off
icon_position = off

# Paths to default icons.
#icon_folders = /usr/share/icons/gnome/16x16/status/:/usr/share/icons/gnome/16x16/devices/

[frame]
width = 2
color = "#444444"

[shortcuts]

# Shortcuts are specified as [modifier+][modifier+]...key
# Available modifiers are "ctrl", "mod1" (the alt-key), "mod2",
# "mod3" and "mod4" (windows-key).
# Xev might be helpful to find names for keys.

# Close notification.
close = mod4+BackSpace

# Close all notifications.
close_all = mod4+mod1+BackSpace

# Redisplay last message(s).
# On the US keyboard layout "grave" is normally above TAB and left
# of "1".
history = mod4+shift+BackSpace

# Context menu.
context = mod4+Menu

[urgency_low]
# IMPORTANT: colors have to be defined in quotation marks.
# Otherwise the "#" and following would be interpreted as a comment.
background = "#222222"
foreground = "#888888"
timeout = 10

[urgency_normal]
background = "#005577"
foreground = "#bbbbbb"
timeout = 10

[urgency_critical]
background = "#900000"
foreground = "#ffffff"
timeout = 0


# Every section that isn't one of the above is interpreted as a rules to
# override settings for certain messages.
# Messages can be matched by "appname", "summary", "body", "icon", "category",
# "msg_urgency" and you can override the "timeout", "urgency", "foreground",
# "background", "new_icon" and "format".
# Shell-like globbing will get expanded.
#
# SCRIPTING
# You can specify a script that gets run when the rule matches by
# setting the "script" option.
# The script will be called as follows:
#   script appname summary body icon urgency
# where urgency can be "LOW", "NORMAL" or "CRITICAL".
# 
# NOTE: if you don't want a notification to be displayed, set the format
# to "".
# NOTE: It might be helpful to run dunst -print in a terminal in order
# to find fitting options for rules.

#[espeak]
#    summary = "*"
#    script = dunst_espeak.sh

#[script-test]
#    summary = "*script*"
#    script = dunst_test.sh

#[ignore]
#    # This notification will not be displayed
#    summary = "foobar"
#    format = ""

#[signed_on]
#    appname = Pidgin
#    summary = "*signed on*"
#    urgency = low
#
#[signed_off]
#    appname = Pidgin
#    summary = *signed off*
#    urgency = low
#
#[says]
#    appname = Pidgin
#    summary = *says*
#    urgency = critical
#
#[twitter]
#    appname = Pidgin
#    summary = *twitter.com*
#    urgency = normal

Well here's mine. Fairly default too.

# vim: filetype=dosini
[global]
    font = Kozuka Gothic Pro M 16

    # The format of the message. Possible variables are:
    #   %a  appname
    #   %s  summary
    #   %b  body
    #   %i  iconname (including its path)
    #   %I  iconname (without its path)
    #   %p  progress value if set ([  0%] to [100%]) or nothing
    format = "%s\n%b"

    # Sort messages by urgency
    sort = yes

    # Show how many messages are currently hidden (because of geometry)
    indicate_hidden = yes

    # alignment of message text.
    # Possible values are "left", "center" and "right"
    alignment = left

    # The frequency with wich text that is longer than the notification
    # window allows bounces back and forth.
    # This option conflicts with 'word_wrap'.
    # Set to 0 to disable
    bounce_freq = 0

    # show age of message if message is older than show_age_threshold seconds.
    # set to -1 to disable
    show_age_threshold = 60

    # split notifications into multiple lines if they don't fit into geometry
    word_wrap = yes

    # ignore newlines '\n' in notifications
    ignore_newline = no


    # the geometry of the window
    # geometry [{width}]x{height}][+/-{x}+/-{y}]
    # The geometry of the message window.
    # The height is measured in number of notifications everything else in pixels. If the width
    # is omitted but the height is given ("-geometry x2"), the message window
    # expands over the whole screen (dmenu-like). If width is 0,
    # the window expands to the longest message displayed.
    # A positive x is measured from the left, a negative from the
    # right side of the screen.  Y is measured from the top and down respectevly.
    # The width can be negative. In this case the actual width is the
    # screen width minus the width defined in within the geometry option.
    geometry = "0x40-10+10"

    # The transparency of the window. range: [0; 100]
    # This option will only work if a compositing windowmanager is present (e.g. xcompmgr, compiz, etc..)
    transparency = 10

    # Don't remove messages, if the user is idle (no mouse or keyboard input)
    # for longer than idle_threshold seconds.
    # Set to 0 to disable.
    idle_threshold = 120

    # Which monitor should the notifications be displayed on.
    monitor = 0

    # Display notification on focused monitor. Possible modes are:
    # mouse: follow mouse pointer
    # keyboard: follow window with keyboard focus
    # none: don't follow anything
    #
    # "keyboard" needs a windowmanager that exports the _NET_ACTIVE_WINDOW property.
    # This should be the case for almost all modern windowmanagers.
    #
    # If this option is set to mouse or keyboard, the monitor option will be
    # ignored.
    follow = mouse

    # should a notification popped up from history be sticky or
    # timeout as if it would normally do.
    sticky_history = yes

    # The height of a single line. If the height is smaller than the font height,
    # it will get raised to the font height.
    # This adds empty space above and under the text.
    line_height = 12

    # Draw a line of 'separatpr_height' pixel height between two notifications.
    # Set to 0 to disable
    separator_height = 2;

    # padding between text and separator
    padding = 8

    # horizontal padding
    horizontal_padding = 8

    # Define a color for the separator.
    # possible values are:
    #  * auto: dunst tries to find a color fitting to the background
    #  * foreground: use the same color as the foreground
    #  * frame: use the same color as the frame.
    #  * anything else will be interpreted as a X color
    separator_color = frame

    # print a notification on startup
    # This is mainly for error detection, since dbus (re-)starts dunst
    # automatically after a crash.
    startup_notification = false

    # dmenu path
    dmenu = /usr/bin/dmenu -p dunst:

    # browser for opening urls in context menu
    browser = /usr/bin/firefox -new-tab

[frame]
    width = 1
    color = "#5f0916"

[shortcuts]
    # shortcuts are specified as [modifier+][modifier+]...key
    # available modifiers are 'ctrl', 'mod1' (the alt-key), 'mod2', 'mod3'
    # and 'mod4' (windows-key)
    # xev might be helpful to find names for keys

    # close notification
    close = ctrl+space

    # 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

[urgency_low]
    # IMPORTANT: colors have to be defined in quotation marks.
    # Otherwise the '#' and following  would be interpreted as a comment.
    background = "#1c2126"
    foreground = "#ededed"
    timeout = 5

[urgency_normal]
    background = "#1c2126"
    foreground = "#ededed"
    timeout = 5

[urgency_critical]
    background = "#1c2126"
    foreground = "#ededed"
    timeout = 0

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,039

Website

Re: xfce4-notifyd

OK, thanks gents! I've put dunst on hold ATM as I'm having fun theming again. I'll get back to dunst after I get my latest themes up on GitHub (this weekend fo' sho'). BTW, in case you missed it, I've got dark gtk3 rocking...
https://forums.bunsenlabs.org/profile.php?id=10

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,560

Website

Re: xfce4-notifyd

@cpoakes, our policy has been to only include stable packages in our ISOs (I think yad was the one exception we made for Helium)...

A quick check shows the hydrogen ISO includes upstream versions of: compton, obmenu, and yad...

Just to clarify:
*) compton? Both the iso build configs and my own installed system indicate the standard Debian Jessie compton 0.1~beta2-1; there's a compton in the bunsen-hydrogen jessie-backports but not in bunsen-hydrogen .
*) yad, yes a backported upstream version.
*) obmenu, no, a rebuild from #!. Upstream still haven't fixed the one-word bug.
So, yes some impurity. We loosened up a bit on policy, but I don't think there's much likelihood (or need) of going back to the CrunchBang state of having a whole slew of rebuilt packages in our repo, pinned at 1001 to boot!

...diverges from the mothership, however limited. With this history, I hope the team is more chill about exceptions.

Yes, I think so... in moderation.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

cpoakes

Member

Registered: 2016-12-02

Posts: 108

Re: xfce4-notifyd

^ Moderation is usually good policy. Thx.