Attaching a simple patch that targets adduser. Please consider it for quick
inclusion for the next release to stop creating broken user accounts.
* Re-enables EXTRA_GROUPS="users".
* Its not proposing a new behavior (change) but re-enables standard (and prior)
bahaviour.
* If an admin does not
*** This bug is a duplicate of bug 549117 ***
https://bugs.launchpad.net/bugs/549117
** This bug has been marked a duplicate of bug 549117
users are not added to "users" group (empty, broken behaviour)
--
users are not added to "users" group
https://bugs.launchpad.net/bugs/253103
You rece
Forgot to mention the reason I changed it to common-account is that
/etc/pam.d/sudo does not include common-session. This might be OK if
sudo is not considered to open a session. But having a different umask
using sudo would again not be expected and lead to wrong permissions
etc.
Maybe it is more
Public bug reported:
Binary package hint: sudo
The pam configuration seems to be incomplete in the sense that no
common-session modules are included in sudo's pam config.
(i.e. things like pam_umask and pam_env don't work with sudo)
/etc/pam.d/sudo should contain
@include common-session-noninte
Sudo seems to be patched to parse /etc/environment itself. With sudo correctly
iplementing pam sessions that hack can be reverted.
http://www.sudo.ws/bugs/show_bug.cgi?id=83
** Bug watch added: Sudo Bugzilla #83
http://www.sudo.ws/bugs/show_bug.cgi?id=83
--
common-session pam configuration n
** Summary changed:
- sudo does not use /etc/environment on interactive logins (through pam_env)
+ sudo does not read /etc/environment on interactive logins (directly, not
through pam_env)
--
sudo does not read /etc/environment on interactive logins (directly, not
through pam_env)
https://bugs
** Description changed:
Binary package hint: sudo
The pam configuration seems to be incomplete in the sense that no
common-session modules are included in sudo's pam config.
- (i.e. things like pam_umask and pam_env don't work with sudo)
+ (i.e. things like pam_umask, limits and pam_en
explicit workaround commands using esmtp:
#apt-get install esmtp procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d
%T\'
--
mdadm monitor feature broken, not depending on local MTA/MDA or using
wall/notify-send
https://bugs.launchpad.net/bugs/535417
You rece
last line needs to address for esmtprc of course:
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \|
/usr/bin/procmail -d %T\' >> /etc/esmtprc
--
mdadm monitor feature broken, not depending on local MTA/MDA or using
wall/notify-send
https://bugs.launchpad.net/bugs/535417
You received this
Nice you found that out, Sami!
Are your arrays taged with your hostname? From Bug #252345 mdadm
--incremental seems to block members with non-matching homehost tag and
does not seem to have an option to disable that. (Or comprehend the
--auto-update-homehost option as a workaround with the possibl
@Sami, with that directory created in initramfs, your setup is now
working without any mdadm.conf ARRAY lines, right?
--
[karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
https://bugs.launchpad.net/bugs/136252
You received this bug notification because you are a member of
@Sami (newly subscribed): Some previous comments relate to you.
--
[karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
https://bugs.launchpad.net/bugs/136252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Note that starting all incomplete array indiscriminately is not a good
idea in general.
i.e. on boot, start only selected arrays degraded that are known to be
needed.
--
--incremental --scan --run does not start anything
https://bugs.launchpad.net/bugs/244808
You received this bug notification b
*** This bug is a duplicate of bug 136252 ***
https://bugs.launchpad.net/bugs/136252
** This bug has been marked a duplicate of bug 136252
[karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
--
boot fails: mdadm not looking for UUIDs but hostname in superblocks
htt
Adopting from #226484 (now a duplicate of this one):
This is a bug with mdadm --incremental not doing hotplug, because it
looks for permission to do so in mdadm.conf.
On hotplug systems mdadm.conf should not have to contain any specific
references, to make things clear and for backwards compatib
** Summary changed:
- [karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
+ [karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
(boot fails)
** Description changed:
Binary package hint: mdadm
Hi,
I could not boot from my /dev/md1 -> /dev
Public bug reported:
Binary package hint: gksu
During login seahorse/gdm/pam? seems to open "login.keyring", but gksu always
saves passwords to "default.keyring".
Either gksu needs to ask which keyring to use, or seahorse/gdm/pam?
needs to be able to open secondary keyrings on login. (possibly
This is with the radeon driver used here, not a dupe of #290704.
--
fast-user-switch-applet crashes system on usage
https://bugs.launchpad.net/bugs/352056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
here is a Xorg log of the crash
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/42160315/Xorg.0.log.old
--
fast-user-switch-applet crashes system on usage
https://bugs.launchpad.net/bugs/352056
You received this bug notification because you are a member of Ubuntu
Bugs, whi
It crashed when switching back to the first user.
I used the fast-user-switch-applet as user2 and then selecting the user1
(already active user) from the gdm screen.
--
fast-user-switch-applet crashes system on usage
https://bugs.launchpad.net/bugs/352056
You received this bug notification becau
** Also affects: rdesktop (Ubuntu)
Importance: Undecided
Status: New
--
unable to to copy and paste files in a rdesktop session with glipper active
https://bugs.launchpad.net/bugs/283385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
(using 9.10)
Neither forcing pciehp nor loding acpiphp made the hd connected to the
following eSATA express card reappear when it was removed and plugged in
again after booting.
02:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 AHCI
Controller (rev 03)
Note that lspci still lists the
** Also affects: policykit (Ubuntu)
Importance: Undecided
Status: New
--
policykit introduction broke unix user/group privileges
https://bugs.launchpad.net/bugs/326135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-b
** Summary changed:
- policykit introduction broke unix user/group privileges
+ policykit introduction broke unix user groups
--
policykit introduction broke unix user groups
https://bugs.launchpad.net/bugs/326135
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: ubuntu
Status: Incomplete => Confirmed
** Changed in: ubuntu
Status: Confirmed => Incomplete
--
Inaccessible directory has same emblem as read-only directory
https://bugs.launchpad.net/bugs/489977
You received this bug notification because you are a member of Ubuntu
Hm, do your user2's directories have the same permissions as mine?
Or are your directories of user2 "group writeable"? It would be OK for
them not to have a lock emblem then, if you are browsing as user1 and
member in the user2 group.
Further details on the issue I observe:
* The theme used in u
Err, it happened again, reduncancy in the system is destroyed,
cryptsetup opened a raid member and it got mounted leaving the raid
incomplet/inactive:
md3 : inactive sda7[0](S)
blkid (now again) returns TYPE="crypto_LUKS" for the raid member.
When I run "su cryptsetup isLuks" on raid members or
Public bug reported:
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 to notify during m
> it's still a bug in blkid. It's blkid that wrongly detects the LUKS
UUID on a device that's a RAID member.
Yes, your of course right, and if "cryptsetup isLuks" is itself scanning
for a luks signature (without giving RAID precedence) it got the same
bug. Can you rule that out / know for sure tha
Thank you Paul, for spreading that. I am backing up the ubuntu md raid
systems now though, and switching them to a distro that does less hectic
transitions and leaving things like raid or boot up unreliable in the
process.
--
mountall and cryptsetup will fight for the console when not using uspla
Lets think some more of signature rules.
Crypt vs Container
-> any crypt should be lower then other containers (not fs) because whaterver
is in it wouldn't be visible or is random.
Crypt vs FS
<- old fs signatuers may have remained.
RAID vs LVM-LV
<- LVs never reside on RAIDs directly (alway
** Description changed:
Binary package hint: util-linux
After the member is opened as luks device it is booted instead of the md
device, while the raid remains "inactive".
I first noticed /proc/mdstat reported the root raid as inactive
(although the system seemed to run fine!).
My current conception: (WARNING)
Both blkid and "cryptsetup isLuks" misreport a raid_member as luks when
checking devices, but blkid correctly reports RAID if the device is set
up (mounted/active) in the system as intended (after
install/update/recover).
On boot what happens depends on the order
Cool, that I didn't know from the thread my search turned up about
blkid. (increases the bug weight though)
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
The laptop-mode freeze bug actually seems fixed but status not updated.
(Bug #12483, debbugs #426548)
--
don't have any laptop-mode-tools settings in /etc/default/acpi-support
https://bugs.launchpad.net/bugs/244838
You received this bug notification because you are a member of Ubuntu
Bugs, which
Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: cisco_ipsec
Package: linux-image-2.6.31-16-generic 2.6.31-16.53
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
Uname: Linux 2.6.31-16-generic i686
UserGro
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36968589/Dependencies.txt
--
rejected 1 configuration due to insufficient available bus power
https://bugs.launchpad.net/bugs/203473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/36968590/XsessionErrors.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected
--
rejected 1 configuration due to insufficient available bus power
https://bugs.launchpad.net/b
I am not sure if devicekit is right.
If not please change to the package that provides the device detection
UI.
** Also affects: devicekit (Ubuntu)
Importance: Undecided
Status: New
--
rejected 1 configuration due to insufficient available bus power
https://bugs.launchpad.net/bugs/203
with 9.10
Same Hub here:
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
lsusb shows the flash drive (after a while), but nothing more happens.
/var/log/messages however says:
usb 1-2.3: rejected 1 configuration due to insufficient available bus power
--
usb device invi
Public bug reported:
Binary package hint: grub2
9.10
The following example used to work with grub1 to create separate rescue
boot media:
* Plugged in the USB Stick which contains a dedicated grup partition and
chainloads other (rescue) boot partitions for several installations that are on
the
I did actually copy to /media//boot/
(But I have tried it as written above with same result.)
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One error I noticed now:
grub-mkconfig is always writing to /boot/grub/device.map not honoring
the path given with for grub.cfg with -o
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of Ub
Hi, thanks for that quick response. Is there any workaround for "Cannot read
`/grub/core.img'"?
>> normally). -> Grub2 needed "grub-install /dev/sda5" to work again.
>Should never happen if both the directory given with --root-directory is
>the drive/partition you want and also the device you g
> grub-mkconfig always uses /boot.
> It doestn't have at all any support for something like --root-directory=
> of grub-install.
Hm, I took the option "-o, --output=FILE output generated config to
FILE" for it.
> Also all /etc/grub.d/* files only look in /boot/ for the kernels etc.
That might n
Ah, right, I probably just don't need to grub-mkconfig at all if /boot
is copied.
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
> you can use grub-install with --grub-setup=/bin/true
Thanks for this, and your help!
Way cleaner than copying to the rescue partition, over-mounting it to /boot and
than doing update-grub/grub-install.
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/49
Public bug reported:
9.10 ubuntu desktop CD iso put on usb stick (live-usb) and booted:
Update using synaptic failed and got reported by apport.
ProblemType: Package
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC883 Analog [
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/36978175/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/36978176/AplayDevices.txt
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/36978177/AptOrdering.txt
**
--grub-setup=/bin/true worked nice! Nailed it down to two issues now.
1)
When I used grub-mkconfig (at that time with -o
/media//boot/grub/grub.cfg" but shouldn't matter) it did create a faulty
grub.cfg however. It probably looked in /boot/grub for the device.map (as it
does not support --grub
Public bug reported:
Binary package hint: mountall
When booting from a rescue boot device, mountall prevented a successful
boot.
It was waiting for the UUID of the (potentially destroyed) /boot
partition. (different form the boot media used)
While ESC did get me a shell, I could not disable boo
* If /boot files are copied to rescue partition manually, the UUID in
the search lines in grub.cfg will not match the UUID of the rescue
partition. A --grub-root-directory option for grub-mkconfig would fix
this.
* grubenv seems to get written to (root)/grub while it is installed in
(root)/boot/gr
*** This bug is a duplicate of bug 489474 ***
https://bugs.launchpad.net/bugs/489474
Thank you. All good with that LucidBootRecovery spec.
--
mountall can not be unblocked
https://bugs.launchpad.net/bugs/498636
You received this bug notification because you are a member of Ubuntu
Bugs, which
As "mountall" already has the "waiting for device" functionality,
linking this to https://wiki.ubuntu.com/ReliableRaid that was updated
with email discussion and made to match a SpecTemplate.
** Changed in: mountall (Ubuntu)
Status: Invalid => New
--
mounts fail because degraded raid is n
Could someone give me a hint how/what I have to do, in order to install
aqbanking from lucid (version 4.1.8) in 9.10?
The package search turns out many .debs.
--
Online-Actions not working in GnuCash
https://bugs.launchpad.net/bugs/453895
You received this bug notification because you are a memb
Ok, thought of checking it in somewhere.
->blueprints?
--
mounts fail because degraded raid is not beeing started
https://bugs.launchpad.net/bugs/496461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
dowload and "dpkg -i *" of aqbanking-tools plus 5x "libaqbanking" and 1x
libaqhbci seem to do it.
--
Online-Actions not working in GnuCash
https://bugs.launchpad.net/bugs/453895
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
If policykit broke the desktop and unprivileged profiles this is a bug
with policykit not being set up to honor those unix groups.
I don't see user profiles only with respect to g-s-t. It seems usefull
also for admins not using g-s-t. As adduser is supposed to be thesystem
wide tool, even the inst
If policykit broke the desktop and unprivileged profiles this is a bug
with policykit not being set up to honor those unix groups.
It seems to merely match all users in admin group to root.
** Also affects: policykit-1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: networ
Fedora's "sandbox -X" seems to be made for this.
** Summary changed:
- wrong ownership of .Xauthority and /tmp/libgksu-xxx
+ run as different user fails (wrong ownership of .Xauthority and
/tmp/libgksu-xxx)
--
run as different user fails (wrong ownership of .Xauthority and
/tmp/libgksu-xxx)
h
Public bug reported:
Binary package hint: user-setup
/home//.Private gets currenty mounted as /home/ with
permissions set to rwx-- by default.
This is changing the default to have homedirs readable among users and
for example breaks sharing files and having ~/public_html work.
We can not as
Hi there, it's now a vfat fs plugged into a 9.10 system:
ii coreutils 7.4-2ubuntu1 The GNU core utilities
$ ls -l /media/USB/
-rwxr-xr-x 1 test.txt1
-rwxr-xr-x 1 test.txt2
$ cp /media/USB/test.txt1 .
$ ls -l
-rwxr-xr-x 1 test.txt1
$ cp --no-preserve=mode /media/USB/test.file2 .
$ ls
There is again the same error message in 9.10 when installing grub to md
device. -> Bug #462171
--
error: Running 'grub-install --no-floppy "/dev/md0"' failed.
https://bugs.launchpad.net/bugs/457687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Phil, thank you for pointing me to the xorg.conf. (your help worked out
great :)
** Description changed:
Binary package hint: xorg
There is reproducable corruption of the screen when using a Sapphire
- Radeon 4770 card with the open source radeon drivers.
+ Radeon 4770 card with the open s
Hmm, seems like adduser wants to ensure UID == UPG-GID?
Maybe g-s-t could offer to choose the next possible ID available, or
optionally override the GID and possibly mess up the system?
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You rece
Good choice I think. Cutting down the settings forced with g-s-t GUI
profiles is probably also a good measure for supporting the adduser
profiles (or any other system wide profiles).
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You received
** Summary changed:
- Ship adduser with user profiles to unify their handling by different tools
+ Ship adduser.conf as symlink to user profiles to unify their handling by
different tools
** Description changed:
Binary package hint: adduser
+ Default profiles could be shiped for admininstr
** Summary changed:
- Ship adduser.conf as symlink to user profiles to unify their handling by
different tools
+ Ship adduser.conf as symlink to a profile (provides switchable profile
feature for all frontends)
** Summary changed:
- Ship adduser.conf as symlink to a profile (provides switchabl
crased on me in 9.10
** Changed in: fast-user-switch-applet (Ubuntu)
Status: Incomplete => Confirmed
--
fast-user-switch-applet crashes system on usage
https://bugs.launchpad.net/bugs/352056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is confirmed many times by now.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** This bug is no longer a duplicate of bug 408432
[i915] 'xrandr' with no arguments garbles screen
--
intel graphics laptop crashes with external monitor
https://bugs.launchpad.net/bugs/465318
Logging into kde the errors are all over the place.
--
Occasional screen corruption with Radeon 4770
https://bugs.launchpad.net/bugs/440544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
** Summary changed:
- Occasional screen corruption with Radeon 4770
+ screen corruption with Radeon 4770
--
screen corruption with Radeon 4770
https://bugs.launchpad.net/bugs/440544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Looks like they had the same prob, but I don't understand their solutions:
http://www.phoronix.com/forums/showthread.php?t=18687
--
screen corruption with Radeon 4770
https://bugs.launchpad.net/bugs/440544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Description changed:
Binary package hint: xorg
- There is occasional corruption of the screen when using a Sapphire
- Radeon 4770 card with the open source radeon drivers. The takes the form
- of a "chequered" effect, looking a bit like a chequer board. This is
- most noticeable when the s
--- 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:
https://salsa.debian.org/freedombox-team/freedombox/-/snippe
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 recei
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.
https://bugs.launchpad.net/bugs/1
Public bug reported:
Linux provides a simple way to schedule an restart event, for example:
rtcwake -m on -s
This command avoids that rtcwake does the switching into another power state
(mode -m stays on).
The power state are thus handled by the regular pm-tools, which is more stable
especial
** Description changed:
Linux provides a simple way to schedule an restart event, for example:
rtcwake -m on -s
- This command avoids that rtcwake does the switching into another power state
(mode -m stays on).
- The power state are thus handled by the regular pm-tools, which is more
The functionality to display a status icon continuously still remains a
requirement, and this is a zenity regression.
Reducing "zenity --notification" to implement just notifications (same
as "notify-send") may be OK, but then a separate "zenity --trayicon" is
required to maintain the functionali
** Description changed:
+
+ The functionality to display a tray icon with "zenity --notification"
completely removed that functionality from zenity, instead of moving it into a
proper "zenity --trayicon" feature.
+
+ ---
Ubuntu 11.10
zenity 3.2.0-0ubuntu1
In a script I use following l
Zenity --notify (or better --trayicon Bug #884011) may just always
listen on stdin, and provide an --exit-on-click option enable user
feedback.
This would remove the asumption that --listen means to continusly
listening to commands on stdin. It would provide the calling script with
a feedback upon
** Description changed:
Binary package hint: zenity
+
+
+ Zenity --notify (or better --trayicon Bug #884011) may just always listen on
stdin, and provide an --exit-on-click option enable user feedback.
+
+ This would remove the asumption that --listen always means to endlessly
+ listen to co
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 win
** 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 functional
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 ic
** 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 receive
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
Thank you for the pointer to ConsoleKit.
Do I understand it correctly, there is no way to initiate a shutdown in
gnome that saves the session, without using the gnome-session buttons?
(I have been disapointed by gnome folks dumbing down functionality in other
areas already,
they are not just pro
** Description changed:
- Linux provides a simple way to schedule a restart event.
+ Linux provides a simple way to schedule a restart event that is
+ particularly usfull in conjuction to initiating or scheduling a shutdown
+ or suspend.
rtcwake -m on -s
- This particular command avoids t
Public bug reported:
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.
http://insights.oetiker.ch/lin
** Description changed:
Binary package hint: debian-installer
Following is a little informative text for the "set up users and
passwords" stage:
---
- It is easy for multiple users to collaborate on a debian/ubuntu system.
- Just keep in mind that access to files always depends on
The UUID of the filesystem created on a raid mirror is of course present
and identical on any member devices of the raid mirror mirror.
The raid member device (superblocks) are probably also all taged with
(another) UUID of the raid device they assemble, plus the device ID.
Mdadm seems to handle t
Surbhi, you actually have an ubuntu system on raid installed and the mapfile is
carried over?
Then please state the exact version and details and say it works for you.
If not please leave the bug filed as it was, documenting a bug in the ubuntu
mdadm package.
** Changed in: mdadm (Ubuntu)
@Surbhi
when you go around changing many bug statuses you chould probably subscribe to
mdadm bug mail in general and be careful with changes.
--
[->UUIDudev] mdadm fails to assemble raid during boot
https://bugs.launchpad.net/bugs/541058
You received this bug notification because you are a membe
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 notifi
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 Ubuntu
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 exist
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:
un
801 - 900 of 1101 matches
Mail list logo
