Just two things that are broken with DIR_MODE=0750
(Which are still perfectly supported with the proof-of-concept
lock-down plus improved-usability script from last the post.
Independently from the additional group directories that it
introduces.)
* samba usershares
* ~/public_html
--
You
--- Avoiding the caveat of "this does not work"? ---
You may just not have thought yet of this solution that can be
implemented with little adjustment:
( Privacy by default? YES, even with improved usability! )
Here is a trial script:
Among other things the fork? at https://github.com/faf0/sct claims to
"iterate over all screens of the default display and change the color
temperature".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This report does not need any logs attatched to be complete and
confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/820895
@Marcus Overhagen: Thanks for your message. You may update the
ReliableRaid wiki page.
I found it worthwhile that I migrated my raid systems to debian, now I
am doing the same with the debian desktop howto, and welcoming the
debian tanglu project.
--
You received this bug notification because
Public bug reported:
Consider a laptop with a raid setup that consists of one internal disk
and a second external disk that resides in the laptops docking station.
Undocking the laptop during operation, causes the raid to switch into
degraded operation and the laptop is turned off afterwards.
** Description changed:
12.04.1 regression (worked before, maybe without the mentioned safety
check, but it worked)
+
+ Depends on: Bug #1166086
(re-add refers to speeding up the sync using a bitmap)
The --incremental (udev) call refuses to (re)add a temporarily
diconnected
I don't know, how it behaves with USB3.
Same data corruption as well, unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in mixed (IDE/SATA/USB/SD-card/...)
** Description changed:
Problem: md changes max_sector setting of an already running and busy md
device, when a (hotplugable) device is added or removed. However, the
device mapper and filesystem layer on top of the raid can not (always?)
cope with that.
Observations:
* bio too big
** Description changed:
12.04.1 regression (worked before, maybe without the mentioned safety
check, but it worked)
(re-add refers to speeding up the sync using a bitmap)
The --incremental (udev) call refuses to (re)add a temporarily
diconnected member back to an already restarted
** Description changed:
12.04.1 regression (worked before, maybe without the mentioned safety
check, but it worked)
(re-add refers to speeding up the sync using a bitmap)
The --incremental (udev) call refuses to (re)add a temporarily
diconnected member back to an already restarted
No updates, manually setting iso_layout=0 fixed the swapped keys for me,
so someone still needs to fix that module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043336
Title:
Swiss keyboard
** Bug watch added: Debian Bug tracker #678834
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
** Also affects: nautilus-share via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Bug watch added: Debian Bug tracker #678834
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
** Also affects: samba (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
The reserved system user nobody should never be the owner of files.
This ensures that an access granted with the least privileged nobody
user will never be able to access or even corrupt files on the system.
The nobody user may not even be suited for granting public read
** Bug watch added: Debian Bug tracker #678834
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
** Also affects: nautilus-share via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
Importance: Unknown
Status: Unknown
--
You received this bug notification because
seems fixed after the switch to usershares and usershare allow guests =
yes + map to guest = bad user
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug
** Bug watch added: Debian Bug tracker #678834
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
** Also affects: samba (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
The reserved system user nobody should never be the owner of files.
This ensures that an access granted with the least privileged nobody
user will never be able to access or even corrupt files on the system.
The nobody user may not even be suited for granting public read
*** This bug is a duplicate of bug 549117 ***
https://bugs.launchpad.net/bugs/549117
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/253103
Title:
users are not added to
What is the problem with this bug, that module acpiphp has still not
been enabled by default in ubuntu since 2009?
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Note: Bug is also present when hot-plugging USB, Firewire etc. devices.
+ Problem: md changes max_sector setting of an already running and busy md
+ device, when a (hotplugable) device is added or removed. However, the a
+ device mapper and filesystem layer on top of the
** Also affects: mdadm
Importance: Undecided
Status: New
** Changed in: mdadm
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Note: Bug is also present
** Summary changed:
- Raid1 HDD and SD card - data corruption (bio too big device md0 (248 200))
+ hot-add/remove in mixed HDD/USB/SD-card RAIDs - data corruption (bio too
big device md0 (248 200))
** Summary changed:
- hot-add/remove in mixed HDD/USB/SD-card RAIDs - data corruption (bio
This is a very severe data corrupting bug.
Thus, even if the the md devs can not fix the bio abstraction or
whatever would be necessary to support mixed interface setups, the md
module should definitely have a safeguard and make sure to return a
failure on hot add/remove under these
** Summary changed:
- hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs - data corruption (bio
too big device md0 (248 200))
+ hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs with device mapper on
top - data corruption (bio too big device md0 (248 200))
--
You received this bug
** Description changed:
Note: Bug is also present when hot-plugging USB, Firewire etc. devices.
+ Also reproducable in much more common usage as originally reported (e.g.
--add a USB (3.0 these days) drive to an already running SATA raid1 and grow
the number of devices).
---
This is
The hid_apple module will have set iso_layout=0 for some locales (all
non-US?).
** Changed in: gnome-control-center (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
set it _automatically_ of course
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043336
Title:
Swiss keyboard layout with Apple keyboard (period instead of comma)
To manage notifications about this
Hello ikus060,
could you adapt your patch to provide a configurable parameter as iso_layout
and fnmode do? (maybe see the patchwork link from last post for an example)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For a full set of keyboard workarounds see
https://aur.archlinux.org/packages/un-apple-keyboard .
A real fix will require a patches to the hid_apple kernel module that
add appropriate parameter options.
Additionally, the swapmodifiers option from this patch
As macbooks do not seem to have F13-F15 keys, also provide some alternatives.
For example, map alt-eject to SysRq.
scancodes: http://ubuntuforums.org/archive/index.php/t-762665.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
12.04.1 regression (worked before, maybe without the mentioned safety
check, but it worked)
(re-add refers to speeding up the sync using a bitmap)
The --incremental (udev) call refuses to (re)add a temporarily
diconnected member back to an already restarted
Public bug reported:
The --incremental call (as also done by udev rules) refuses to (re)add a
temporarily disconnected members back to an already restarted (active)
raid array.
# mdadm --incremental /dev/sdb1
mdadm: not adding /dev/sdb1 to active array (without --run) /dev/md/0
# mdadm
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062159
Title:
Raid is incorrectly determined as DEGRADED preventing boot in 12.04
To
It is currently a requirement to notify the sysadmin about failing disks
etc.. Bug #535417
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057889
Title:
mdadm depends on postfix
To manage
** Description changed:
Binary package hint: mdadm
- Anybody who cares about redundancy to use mdadm probably cares enough
- about redundancy to want being informed if redundancy is degraded.
+ Anybody who cares enough about redundancy to use mdadm probably cares
+ enough to want getting
This is completely unbelievable. Somebody not competent enough broke the
debian raid setup for ubuntu years ago, and the issues has still not
been resolved?
Man, fix up ubuntu mdadm to issue proper notifications (bug #535417).
Get rid of that bogus boot_degraded question (bug #539597), and
Vak, if you need more recent versions, look for a howto to set up a
debian (desktop) box with testing or sid.
These releases contain recent software with continious updates, while
still being conservative on the finishing of features, and not just
dumping them on users and forgetting about them.
Public bug reported:
http://www.spinics.net/lists/raid/msg40832.html
when booting, the system dumps
into initramfs shell with the raid array in an inactive state.
There are two problems here.
Firstly, the fact that the array doesn't assemble completely should not cause
the boot to fail. A
I am sorry I had to find out the same as Teemu for 12.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/251164
Title:
boot impossible due to missing initramfs failure hook / event driven
Public bug reported:
12.04.1 regression (worked before, maybe without the mentioned safety
check, but it worked)
(re-add refers to speeding up the sync using a bitmap)
The --incremental (udev) call refuses to (re)add a temporarily
diconnected member back to an already restarted (active) raid.
I'd suggest to report the failure to create raid partition with the
correct (equal, large enough) size as a separate bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984449
Title:
Palimpsest
PS launchpad is a waste of time, get in contact with upstrem directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984449
Title:
Palimpsest doesn't allow precisely-sized partitions
To manage
Forgot to mention: conifirmed the failure to create lage enough raid
partition when trying to extend a raid 1 with another 333MiB sized
parttion (gui shows 349 MB). Nevertheless, it worked with a 18.62GiB
(20GB) raid.
Seems like messing up with with MB and MiB (MiB being the only sane unit
as
The workarout to see the MiB size in copy/resize dialog does not work
with unknown partitions (raids containing luks).
** Description changed:
Try to recreate or clone the OS partition on another harddrive of a
different size as the original.
GParted shows only an impresize size of the
console workaround to get the size in MiB:
# parted /dev/sda unit MiB print
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985882
Title:
units shown are not equal to the units asked for creation
This is grub bug someone forward this to grub authors!
http://askubuntu.com/questions/117525/hide-grub2-menu-unless-you-hold-
down-shift-key-how-to-make-this-happen
Somehow even if HIDDEN_TIMEOUT is set to a positive value, the
shiftkey (said to be only the right-shift !!!) is said to only work
Thanks for the honest assessment. Too bad if LTS support is such that
it means to be stuck with countless bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989814
Title:
Albatross: GTK3 apps are
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address
** Tags added: patch
** Description changed:
-
- Please build the package with the --drop-cache patch available in the
tarball, to avoid filling up the io cache with not re-queried copied data. The
current behavior pushes the data of other process out of the cache and thus
slows them down.
+
Will the resizing handle in the bottom right window corner and
albatross readability fix come to the LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989814
Title:
Albatross: GTK3 apps are hard
*** This bug is a duplicate of bug 882255 ***
https://bugs.launchpad.net/bugs/882255
** Also affects: gnome-system-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-system-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
If I choose not to have a password for my operating account, every
operation fails if it needs root access. Reproducible even on a newly
set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543
Release: 11.10
+
+ Cause: The password is cleared
** Description changed:
If I choose not to have a password for my operating account, every
operation fails if it needs root access. Reproducible even on a newly
set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543
Release: 11.10
- Cause: The password is cleared
You might want to use the original debian on your server instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/158918
Title:
[-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
To
I don't think so.
My guess is that if initramfs calls
mdadm --incremental --run
it would run all arrays and not just the single array (mdX) that contains the
root filesystem.
Degrading not yet fully available non-root arrays is bad, as it may nullify the
redundancy and take hours to get the
** Changed in: shadow (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487729
Title:
/etc/login.defs propagates incorrect information
To manage
** Description changed:
Binary package hint: base-files
+
+ see https://wiki.ubuntu.com/MultiUserManagement for context
Please provide the directories /etc/skel/private (rwx--) and
/etc/skel/incoming with appropriate permissions.
In the user private group scheme used in
** Description changed:
Binary package hint: user-setup
- Set up a sgid /home/group/users directory for the users group if it
- doesn't exist, so that users are provided with a way to collaborate on
- local files.
+ see https://wiki.ubuntu.com/MultiUserManagement
+
+
+ Set up a sgid
** Description changed:
+
+ see https://wiki.ubuntu.com/MultiUserManagement
+
Let groupadd have the option to create /home/group/groupname sgid
directories.
Sgid group directories are the means for users to easily collaborate on
local files with the user private group scheme used in
This kind of information would be perfect for presentation by the
installer during the copying phase.
** Description changed:
Binary package hint: debian-installer
Following is a little informative text for the set up users and
passwords stage:
---
- The informational text
** Summary changed:
- addgroup option to create /home/group/groupname sgid directories
+ addgroup option to auto-create /home/group/new-group sgid directories
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am not sure, last time I looked (when still using ubuntu), initramfs
was not using --incremental to set up the rootfs.
The issue itself may be something worth forwarding/asking to upstream,
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Are you aware that starting all arrays degraded (what the initramfs
scripts currently have to do) is a serious bug? The replicas will
diverge, and if the non-rootfs devices become accessible later they need
to resync.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Binary package hint: mdadm
+ Proposed command: mdadm --incremental --run /dev/mdX
- Initramfs has to start (selected) md devices in degraded mode. (The ones that
contain the rootfs and swap/resume partition, if they didn't start after some
time of udev
All right, hopefully some of the stuff I filed is of help to you,
thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/251646
Title:
{upstream} missing command to start *single* arrays in
Looking at the timouts suggested in Comment #15, I think they may actually be
realizable with modular scripts. A base rootdelay script, and separate mdadm
and cryptsetup sripts (that get called by their udev rules) can halt/extend the
regular rootdelay (exported variable? named pipe?), if
I don't know if daily wake events can be programmed in the hardware real
time clock.
Yes, a small +wakup again checkbox or similar collapsible UI to enter
a date would be sufficient I guess. But if it the UI could remember the
last setting used this might already also allow daily (next day)
I believe the initramfs only sets up the rootfs, other partitions
(/home) are set up afterwards. If I remeber correct cryptsetup is called
by udev rules. In any case, that is the way it has to be, event driven,
to catch on upon (/home) devices appearing without polling loops and
sleep delays.
The udev rules don't need to prompt, the cryptsetup that gets called
will prompt. Actually, these things work quite well in the normal
system. It seems preferable to me to adjust/improve the regular tools to
be usable in initramfs as well, rather then trying to script up and
maintain! another
Since udev already provides an event driven framework in
the initramfs, why add another one?
Hmm, if you would like to realize event driven init scripts, I believe
you may be able to rework the scripts from doing linear pre...post
things to just call a watchdog script that mostly sleeps and
Thank you for testing, Phillip!
Cryptsetup support should be on the CD. But it only seemed to run in the first
boot up stage of the rescue CD and used to try to open the raid members there,
even before you set up the raids with the debian installer.
Good that it does not do that any more.
I
@alfonso: mdadm monitor will send you an email if the raid can not be
set up completely (is degraded)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/531240
Title:
silently breaking raid: root
If you still have the vm setup, you could just try to boot the text
installer media again, enter the rescue mode and see how it wants to
mount the existing raid disks (not degraded, both present) in the vm.
That's where it used to always happen. Oherwise, only occasionally
during normal reboots.
** Description changed:
The desktop environments would help saving energy, if their shutdown
dialogs could by default provide the option (button/checkbox) to
schedule a restart.
Linux provides a simple way to schedule a restart event that is
particularly usefull in conjuction with
Best way to reproduce the actual wrong opening seemed to be in a
virtualbox as in comment #42.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/531240
Title:
silently breaking raid: root raid_members
Agreed. Thank you!
** Description changed:
Try to recreate or clone the OS partition on another harddrive of a
different size as the original.
GParted shows only an impresize size of the existing partition such as
32.63GB, whereas to create the new partition the exact size in MiB is
When I had the problem I finally had to turn to CLI-parted to get the
proper numbers. Nothing a graphical tool user may like to do, but I
could work around the problem that way.
Fortunately, I was using the MiB allignment on all newer disks, so they
should have ended up to have the same size as I
Can't sectors per MiB be different on different harddisks?
But the LBA size sectors? may be the right option for below MiB alligning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985882
Title:
** Description changed:
Try to recreate or clone the OS partition on another harddrive of a
different size as the original.
GParted shows only an impresize size of the existing partition such as
32.63GB, whereas to create the new partition the exact size in MiB is
required.
Same symptoms do not mean the same cause (bug).
Many thanks for hinting to the module restriction. This bug can be
closed then. :)
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug
Thanks for the workaround! Having to look into Move/Resize before creating new
partitions is still strange, though.
I would expect the required unit numbers are available, at least in the
detailed properties of partitions.
--
You received this bug notification because you are a member of
Use case was, not to copy but create two disks with same partiton sizes
(only some of them raid partition clones).
** Description changed:
Try to recreate or clone the OS partition on another harddrive of a
different size as the original.
GParted shows only an impresize size of the
** This bug is no longer a duplicate of bug 942106
mdadm-functions missing udevadm settle (?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551719
Title:
boot delay and udev/mdadm (raid)
This can not be a duplicate of bug #942106. This is about an obsolete
kernel option for very old style kernel raid assembly. It slows mdadm
assembly down and can grab devices.
In case a patch to another bug fixes this bug too, please mark the patch
as closing multiple bugs.
** Summary changed:
I don't know how all the desktop parts work together. However, it is a
waste of resources to let your computer run only because for example you
need to access it remotely in a couple of hours/days/month, or have it
do some task. And I see many user that keep their machines running, just
because
** Description changed:
+ The desktop environments would help saving energy, if their shutdown
+ dialogs could by default provide the option (button/checkbox) to
+ schedule a restart.
+
Linux provides a simple way to schedule a restart event that is
particularly usefull in conjuction with
** Also affects: xfdesktop4 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987664
Title:
allow to set restart/resume time
To manage
Hi Peter-Alexander,
you're right, and I agree it still is a regression looking at the
--notification function alone. As far as I understand the reason for the change
was the decision for an updated semantic. Notification now only means a bubble
message, and is different from a status icon or
** Description changed:
The change in the zenity --notification behavior completely removed
the functionality to display an unobtrusive, always visible tray icon
- from zenity. Instead, that functionality should have been moved into a
+ from zenity.
+
+ For clarity, the tray icon
In any case, it would be good if you could post the issue to the upstram
bugtracker.
** Description changed:
The change in the zenity --notification behavior completely removed
the functionality to display an unobtrusive, always visible tray icon
from zenity.
For clarity, the tray
** Bug watch added: GNOME Bug Tracker #675064
https://bugzilla.gnome.org/show_bug.cgi?id=675064
** Changed in: zenity
Importance: Undecided = Unknown
** Changed in: zenity
Status: New = Unknown
** Changed in: zenity
Remote watch: None = GNOME Bug Tracker #675064
--
You received
Hi jacopoL, you set this to invalid, because you don't know about start
events?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987664
Title:
allow to set restart/resume time
To manage notifications
1 - 100 of 1115 matches
Mail list logo
