Notifications using --listen should allow clicking to remove the icon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zenity |
Expired
|
Medium
|
|||
zenity (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: zenity
Zenity --notification (or better --trayicon Bug #884011) may just always listen on stdin, and provide an --exit-on-click option to enable user feedback.
This would remove the asumption that --listen always means to endlessly listen to commands on stdin. It would provide the calling script with feedback upon user action (zenity exits), while being able to modify the status.
Ideally, zenity could also accept an "exit" or "quit" command on stdin, in addition to Ctrl-C or closing the file descriptor.
---
The follwing issues that got mixed into this report seem fixed, or are intended behavior:
"zenity --notification --listen" can't show multi lines tooltip.
But as cmd line parameter is works fine: zenity --notification --text $'line1\nline2'
"zenity --notification" does not have command line parameter for "message"
This does not work: zenity --notification --title hi
Also this does not work: echo 'message:hi' | zenity --notification
But this works: echo 'message:hi' | zenity --notification --listen
"zenity --notification --listen" does not exit (does nothing) on click on notification icon
But without "--listen", when notification icon is clicked, zenity does exit.
"zenity --notification" man page does not tell about icon and message, does not explain about tooltip.
Man page say only: "--text" set the notification text (message or tooltip?)
description: | updated |
Changed in zenity: | |
status: | Unknown → New |
Changed in zenity: | |
importance: | Unknown → Medium |
Changed in zenity: | |
status: | New → Expired |
description: | updated |
description: | updated |
description: | updated |
please only describe one bug per report, the listen issue is known upstream and you can track it here: http:// bugzilla. gnome.org/ show_bug. cgi?id= 559848 and yes you need to open separate reports for each problem described.