Can someone with a clue take another look at this? I also came from
Debian and am using JFS (a supported option via the alternate installer)
and this bug renders my system unbootable from battery on unclean
shutdown. It is a bug, plain and simple. fsck needs to be run on every
boot, on battery o
I also ran into this issue. Installed using Jaunty alternate, selected
JFS filesystem, and whenever the system does not shut down properly,
none of my partitions will mount on next boot. JFS requires an fsck
before mounting after an unclean mount. fstab option to fsck should be
respected, with a
The bug is in /etc/init.d/checkfs.sh (initscripts); fixing "affects"
package.
** Package changed: acpi-support (Ubuntu) => sysvinit (Ubuntu)
--
System unusable on battery after incomplete shutdown
https://bugs.launchpad.net/bugs/316200
You received this bug notification because you are a member
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
** This bug has been marked a duplicate of bug 42121
Looks like symlinks for umountnfs and umoutfs is wrong
--
Can't shutdown because an NFS share isn't being unmounted
https://bugs.launchpad.net/bugs/11890
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
There is a bug here, but your assertion that it should interpret "start"
as "unmount" is incorrect -- from sysv-rc README.runlevels (same applies
for rc0.d):
"Then the /etc/rc6.d/SXX scripts will be execute
Changing the S to K makes the nfs unmount happen earlier during the
shutdown process, which seems to solve this issue for some, but not for
me. However, this bug was fixed a better way in Debian, which should
solve the issue for all. See bug report and patch here:
http://bugs.debian.org/cgi-bin/b
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
** This bug is no longer a duplicate of bug 128316
n-m should not tear down interfaces during shutdown
** This bug has been marked a duplicate of bug 42121
Symlinks for umountnfs / sendsigs wrong: hang on
** Summary changed:
- Looks like symlinks for umountnfs and umoutfs is wrong
+ Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
There may be a more general issue here with network manager behavior,
but the specific issue raised by the reporter is a duplicate of bug
#42121 -- marking as duplicate.
** This bug has been marked a duplicate
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
See bug #105831 for a report relating to the network manager behavior.
--
n-m should not tear down interfaces during shutdown
https://bugs.launchpad.net/bugs/128316
You received this bug notification because y
** This bug is no longer a duplicate of bug 128316
n-m should not tear down interfaces during shutdown
--
network updates kills ssh session used for updates
https://bugs.launchpad.net/bugs/105831
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
Please file separate bug reports for each issue still occurring so they
can be fixed. This section is for bug reporting + resolution, not
support. Thanks!
** Changed in: ubuntu
Status: New => Invalid
--
7.04 QA problems
https://bugs.launchpad.net/bugs/127538
You received this bug notifi
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
Thanks for following up on your report. I understand your concern, but
the issue in your description -- CIFS unmount hanging on shutdown -- is
the same as the previously reported bug #42121. This can occur in
Public bug reported:
Binary package hint: cupsys-driver-gutenprint
Using Kubuntu Hardy 8.04 release. Regression from Kubuntu Edgy 6.10
LTS.
Epson Stylus Photo R320 connected via USB, using either Gutenprint 5.0
or gutenprint-ijs-5.0, fails to eject the paper after the last page is
printed. If
Public bug reported:
Binary package hint: linux-image-2.6.20-15-generic
With a degraded RAID 5 array, certain I/O loads and the CFQ scheduler
selected, a kernel panic results after a period of time (<30 mins),
locking up the system hard.
The kernel panic (only visible when X is not started) show
Public bug reported:
Binary package hint: libgnomeui-common
libgnomeui-common (2.16.1-0ubuntu2) does not have gconf2 listed as a
package dependency. However, without the gconf2 package installed, the
libgnomeui-common install fails with:
Setting up libgnomeui-common (2.16.1-0ubuntu2) ...
/var/l
Actually, more likely the gconf-schemas line should not be in the
libgnomeui-common.postinst. It is not present in Debian's libgnomeui-
common package, and a comment on the Ubuntu package indicates the line
was added automatically by dh_gconf.
--
libgnomeui-common should depend on gconf2
https:/
I have exactly the same problem, except with jfs. Also using latest
Karmic. It's only happened once in about 30 boots, so I'm guessing it's
a race condition somewhere.
--
unknown filesystem type 'xfs'
https://bugs.launchpad.net/bugs/432620
You received this bug notification because you are a me
18 matches
Mail list logo
