Public bug reported:
I'm using "Files" 3.36.3-stable on Ubuntu 20.04. When writing large
amounts of data to USB HDD it can take up to a minute to fully flush the
data to HDD.
"Files" provides a button for unmounting of my USB HDD. When I click
this button unmount is started with "Unmounting usbdi
Which is the tracking issue for the required focal (20.04) kernel update
to fix this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873052
Title:
Showing two cursors after login
To manage noti
** Also affects: light-themes (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/1760818
Title:
gedit and gnome-calculator transparency/graphics corru
A the moment I can see following solutions:
(1)
Make the lvchange_activate function in
/usr/share/initramfs-tools/scripts/local-top/lvm2 a while loop which executes
the "lvchange" command repeatedly until the root LV appears
(2)
Utilize udevd to create the LV devices while wait-for-root is wait
Public bug reported:
On my system the root filesystem is located on a logical volume. I have
constant boot delay of 30 seconds. My current conclusion is that this
problem exists due to lvm performing the initramfs-tools local-top
initialization incorrectly.
According to initramfs-tools(8):
local-
For some reason (I cannot remember) my root filesystem node "/" had the
owner set to my user. I guess this used to work for some time. And some
change in mutter or related packages made this break.
Changed back owner to root.root and system is now starting properly.
Don't know what to say about th
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1806257/+attachment/5218200/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806257
The gigabytes of log messages consist only of messages like this:
Dec 2 17:08:33 host gnome-shell[3869]: failed to bind to
/tmp/.X11-unix/X1293301: Datei oder Verzeichnis nicht gefunden
Dec 2 17:08:33 host gnome-shell[3869]: failed to bind to
/tmp/.X11-unix/X1293302: Datei oder Verzeichnis nic
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1806257/+attachment/5218199/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1806257/+attachment/5218198/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806257
Public bug reported:
Since the latest mutter upgrade mutter:amd64 3.28.3-2~ubuntu18.04.1 to
3.28.3-2~ubuntu18.04.2 the login screen can no longer be reached.
Following symptoms are observed
* keypresses are not registered; cannot even toggle NUM/CAPS lock
* gnome-shell taking 100% CPU
* logging g
What needs to be done to get the fixed version into bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770391
Title:
Ubuntu 18.04 josm: No valid JVM found
To manage notifications about this bug
Seems to be tracked in https://github.com/lxc/lxc/issues/2612 .
** Bug watch added: LXC bug tracker #2612
https://github.com/lxc/lxc/issues/2612
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/177528
lxc-copy is no longer working for me since this "SRU".
Command used:
lxc-copy -n bionic-template -N bionic-new -s
Gives in strace:
ioctl(4, BTRFS_IOC_SNAP_CREATE_V2, {fd=0, flags=0, name="rootfs"}) = -1 EXDEV
(Invalid cross-device link)
Apparently the "fd=0" is wrong. I guess that commit
9d
It is really a sad affair here. As far as I know Linux does not provide
a explicit means to limit the amount of memory an application can use.
The only reliable ulimit one can set is the virtual size limit. It feels
also strange that DejaDup pulls a full web-browser into its background
daemon. And
This seems to be a general problem with ModemManager. I have a
completely different modem (Huawei E392) and it fails in the same way.
Furthermore, the workaround steps described in the report itself do also
work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
Upgrade from 14.04 to 16.04 finishes, but is not 100% complete since
upgrade of gcc-doc package fails.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gcc-doc 4:4.8.2-1ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_
Installed version 346 on my machine (Ubuntu 14.04.2 LTS, linux
3.13.0-58-generic x86_64). There was a minor problem with nvidia-opencl-
icd-346-updates not removing nvidia-opencl-icd-331 and having a
conflicting file. Solved this problem by removing the conflicting
package.
There was no report of
The nvidia-340 package does not exist on the latest LTS (14.04).
user@host:~$ sudo apt-get install nvidia-340
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package nvidia-340
--
You received this bug notification because you a
Confirmed on 14.04.1. I'm irritated that security related bugs can have
"low" priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/505278
Title:
ssh-add -D deleting all identities does not work.
Looking at the constructor mnt_rule::mnt_rule() in
apparmor-2.8.95~2430/parser/mount.c:394, I cannot find where flags and
inv_flags are initialized. So depending on the heap - in particular when
not zero-initialized anymore - apparmor loading fails randomly.
--
You received this bug notification
I suffered from the fglrx SRU in 12.04 too. Being forced to fix the
problem I tried the saucy enablement stack
(https://wiki.ubuntu.com/Kernel/LTSEnablementStack). In order for radeon
to work properly, fglrx has to be uninstalled. I had to blacklist the
vesafb driver, otherwise I'd get a GPU lockup
Ok, ignore for now my previous two posts. The two machines "reliably"
producing "mount: / is busy" have the packet "plymouth-x11" installed.
When uninstalling this packet on these machines the error goes away.
At the moment I suspect that those cases which can be solved by means of
disabling the "
Another observation: When I activate "plymouth:debug" according to
https://wiki.ubuntu.com/Plymouth#Enabling_Debugging , unmounting root
also fails when running ubuntu 12.04 within a virtual machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I made two discoveries:
* I can also reproduce this problem on my single "good" system if I plug an USB
bluetooth stick
* It appears that "pre-start" in "/etc/init/plymouth-stop.conf" is not executed
at all on shutdown
So this might be an indication for some kind of timing problem.
--
You rece
I don't have fglrx-experimental-13 installed. According to "apt-cache
show fglrx-updates" the current version is "2:13.125-0ubuntu0.0.1".
Interestingly it shows also the older version "2:8.960-0ubuntu1".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
The device in question is "01:05.0 0300: 1002:9712"
** Attachment added: "output of "lcpci -n""
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+attachment/3973713/+files/lspci-n.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I am on ubuntu 12.04.04 LTS. This update causes a severe regression for
me. The "[AMD/ATI] RS880M [Mobility Radeon HD 4225/4250]" is not
supported by the fglrx version 13 driver!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Upgrade fails also for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257857
Title:
cgroup-lite fails to install in container in precise
To manage notifications about this bug go to:
https://bu
I'm not saying that the problem is easy to solve, but currently
errors.ubuntu.com do not solve it for me. I get the message:
"Sorry, you are not a member of a group that is allowed to see the data
from error reports. A non-disclosure agreement is being written that
will allow for wider access."
I
What is the new bug number for dealing with the DNS lookup delay at
startup then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/592176
Title:
A first document opens very slowly
To manage notificati
Let me summarize how I see the current status
* plymouth does not exit at shutdown, reason not known yet
* plymouth has open files due to dconf, it is unclear if this was intended in
the design
* system cannot remount ro due to open file(s)
Additional note: I experience now the "/ is busy" on two
I am seeing the same problem with 12.04. Configuring with TwinView (i.e.
one large desktop on both monitors) works, but configuring for "Separate
X screen" exhibits the problem described in the bug report.
** Changed in: compiz (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
Could it be possible that these memory mappings are read/write?
plymouthd 10958 root mem REG8,5 440 14729257
/root/.config/dconf/user
plymouthd 10958 root mem REG8,51 557098
/root/.cache/dconf/user
--
You received this bug notificati
Comment #5 contains some debug output, including the list of open files
after shutdown.
I also cannot reproduce this behavior with my desktop-pc. But my laptop
(eee-PC) always has this problem when shutting down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I found that instead of 'killall' it is also possible to invoke
"/bin/plymouth quit". So it seems that plymouth is still honoring quit
requests. Why it doesn't honor the first quit request (or if there is
any quit request) is beyond my knowledge.
--
You received this bug notification because you
There is no need to test this with the newest release, since I already
reported success with oneiric. But to my knowledge, the problem still
exists with the previous LTS release (10.04) which is still in support.
It is really a pity that one cannot report bugs on specific ubuntu (LTS)
releases.
Ne
Some further internal notes:
1) The "fix" mentioned in Comment #17 is already included with Precise
2) gtk_init_check() is called before (!) the fork by gui_mch_init_check() in
gui_gtk_x11.c. My guess is that gtk_init_check() has to be called after the
fork (i.e. in the child process) in order fo
Until this is solved, I'll put a "set guioptions+=f" into my vimrc. Gvim
will then occupy the console, but I can regain the console easily with
"CTRL-Z" and "bg". This is also the same behavior every other X11
application has when started from the console.
--
You received this bug notification be
"Known to work" is something completely different than "supported".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736930
Title:
NM frequently disconnects mobile broadband and refuses to reconnect --
Ubuntu 12.04
Suspend/Resome apparently still broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/93273
Title:
ICE1712 sound does not work after S3/S4-resume
To manage notifications about this bug
Is there a chance that this will get an SRU for lucid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document lost by power outage
(became 0 b
Right now I tested sending files with 3.0.0-18.31 on oneiric and am
happy to report that it works now. yay :)
Just to be sure I did also a test with the previous kernel (3.0.0-17.30)
where it failed as expected.
** Tags removed: verification-needed-oneiric
** Tags added: verification-done-oneiric
Yes, Tom is right. In order to avoid the problem I reinstalled my system
from scratch and did not install the faulty package.
Nevertheless, I tried oneiric-proposed with a virtual machine and the
faulty package.
# BEFORE INSTALL OF turboprint
eduard@qemu-oneiric:~$ ls /etc/rc6.d
K20speech-dispatc
Could the importance of this bug be set to high? Ubuntu is basically
unusable, when you have to reboot on every disconnect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/566812
Title:
USB Modem wont
I can confirm this problem with Exchange Server 2010 on Ubuntu 10.04.3,
thunderbird 3.1.15+build1+nobinonly-0ubuntu0.10.04.1
** Changed in: thunderbird (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Bug watch added: Mozilla Bugzilla #390795
https://bugzilla.mozilla.org/show_bug.cgi?id=390795
** Also affects: thunderbird via
https://bugzilla.mozilla.org/show_bug.cgi?id=390795
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Libreoffice is in the "main" section and the _default_ ubuntu office
application. Not taking this bug seriously will give Ubuntu a very bad
PR! This IMHO includes setting the importance to Critical ASAP.
As a side note/question: What about the operating system level
workaround mentioned in Bug #31
According to http://oss.sgi.com/archives/xfs/2011-08/msg00379.html the
attached patch is supposed to fix the problem.
** Patch added: "Patch from kernel git repository"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/830846/+attachment/2597707/+files/0001-xfs-skip-writeback-from-reclaim-c
Well, in some sense udev _is_ the user, because it has to wait for the
events which create the /dev/mapper/vg-lv and /dev/lg/lv nodes. This
resembles the same problem wich causes udevcomplete_all in my comment
#11 not to work reliably. The hang is gone, but there is still the
problem of some /dev/m
As a highly experimental means to get the system back working one can
try to:
sudo mv /etc/rc6.d/S01reboot /etc/rc6.d/S90reboot
sudo mv /etc/rc6.d/S01umountroot /etc/rc6.d/S60umountroot
and do a "sudo reboot" afterwards. Please be aware that the other
scripts remain reordered, but it should be en
The same what Steve said for vmware is also true for turboprint:
"*destroys* the shutdown sequence of the system."
You could try to fiddle with the '/run' symlinks and manually correct
the script order. But IMHO the only reliable way to get the script order
"back" is to make a fresh Oneiric instal
Maybe it makes sense to put also the 3rd party "turboprint" package in
the affected package list for the release-notes (See Bug #811675)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
According to a pointer from Steve Langasek and the manpage of initramfs-
tools(5) one can do:
/sbin/frobnicate "/dev/mapper/frobb" || panic "Frobnication failed"
which translates to
udevadm control --exit || panic "udev exit failed (http://some-wiki-
page)"
for the init-bottom/udevd script. Thi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872250
Title:
if init-bottom/udev fails, system silently fails to boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
This is a follow-up report on Bug #818177. If during the initramfs phase of a
boot the init-bottom/udev script fails, the system will not (properly) boot.
This report is not about fixing this potential problem, but about the fact that
the user is not informed explicitly eno
So for /dev/dm-* nodes already existing, the symlinks are not created.
Even with having 'udevadm trigger --action=add' invoked by
/etc/init/udevtrigger.conf when the rootfs-udevd is running.
We could try to make initramfs-udevd process the queued events by means of
removing the
event_queu
The "udevadm control --exit" fix was not supposed to fix this bug. I
still have the (occasional) 60 seconds hang at boot. It is just that
'/dev' is now moved to rootfs, enabling the filesystems to be mounted
rw.
The very same lvm process which waits for the semaphore is the process
which set it to
> (I would prefer not to just '|| true' the udevadm call, though, since I
> think having to occasionally reboot the machine again is better than being
> left with extra udev processes running around doing who-knows-what on the
> system.)
Very valid point. But wouldn't it then be better in the case
Many thanks. My LVM system now starts successfully, albeit still showing
the 60s hang occasionally. Even the supposed-to-be-affected logical
volume is mounted correctly. Just the "/sbin/lvm vgchange -a y" persists
in the process list, but this apparently does not harm.
One additional note I want t
So, maybe we just put a
udevadm control --exit || pkill udevd || true
in the init-bottom/udev and close this bug ;)
The occasional 60s boot delay will stay, some stray udev RUN commands might
remain in memory, but Oneiric is at least supposed to start properly.
Nevertheless, I'd be very interes
I have to withdraw my Comment #71. At that time I did not have yet the
new initial-ramdisk installed. Having it installed, gives me always an
read-only rootfs.
And I think, I have also found the reason. The scripts in the initial
ramdisk are executed with "set -e". In this case your pkill fails an
I guess james point is that if you happen to have a rather complete set
of device nodes from a really old installation in /dev, this might
help you in the case when the devtmpfs cannot be moved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just for the record (I do have an LVM setup): Installing the PPA with
pkill enabled still gives me a read-only root filesystem (after 60s
timeout). Don't know how this will turn out for the cases without LVM
(i.e. without vgscan hanging).
--
You received this bug notification because you are a me
Hmmm, I guess the original report of this bug is not for a netbook, but
a server. Still I see this in the BootDmesg.txt attached to this bug:
[3.521410] input: ATEN CS1308 V1.2.114 as
/devices/pci:00/:00:1d.2/usb4/4-1/4-1.1/4-1.1:1.1/input/input4
[3.521587] generic-usb 0003:0557:
I've read all the comments in this bug thoroughly, and for every log
file which has timestamps in it, there appears to be the 60s delay
caused by the udev exit timeout on "hanging" children. If that is true,
then even when adding pkill to the initrd scripts, there will still be
the 60s delay on boo
I see the problem in vim creating the gtk menu before the fork(). With
the original gtk menu this is no problem. But appmenu-gtk creates the
menu using dbus. Probably, the dbus connection for the global menu
creation does not survive the fork(). Or, if the dbus connection
survives the fork, it migh
So far, I'm a bit hesitant to test the patch. I assume that the patch
will work because the "mapper-task-completion-event" will just be
processed by the 2nd udevd. There would only be a small time window
of(~1ms) during exit of the 1st udevd, where the completion event might
be lost, causing the sc
Could someone please have a look at what I have written in Comment 7 of
Bug #802626 and check if it might apply to this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833891
Title:
lvscan often
Public bug reported:
When creating the fstab, the discard option is not activated for SSDs
with TRIM support. But for performance reasons, it would be very
important to be activated.
1) lsb_release -rd
Description:Ubuntu oneiric (development branch)
Release:11.10
2) apt-cache policy
My guess: the observations wrt empathy reported in the last comments are
due to Bug #828756.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742889
Title:
DigiCert certificates should be included in U
For me, after update to compiz 1:0.9.5.94+bzr20110919-0ubuntu1 I did not
have the problem described in this bug anymore. Is there a separate fix
in unity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I activated CONFIG_USB_XHCI_HCD_DEBUGGING and get following kernel
messages:
[ 45.051446] xhci_hcd :07:00.0: xHCI host not responding to stop endpoint
command.
[ 45.051450] xhci_hcd :07:00.0: Assuming host is dying, halting host.
[ 45.089635] xhci_hcd :07:00.0: Non-responsive xH
That is true, bug is back again :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/828756
Title:
getting "connection is untrusted" warnings
To manage notifications about this bug go to:
https
I'm not completely sure, but it appeared like that I got the error fixed
by means of reinstalling all gnome-keyring packages. I have the
suspicion that the /etc/pam.d/common-* files might be created with the
wrong contents. For those people which still have the bug, can you make
a backup of /etc/pa
IMHO the gtk-logout-helper crash must not be mixed up with the other
symptom described in comment 18 and 19. I've also experienced failing to
shutdown, and think it is probably already documented in Bug #838792 and
Bug #660120.
(N.B: I have the feeling that neither indicator-session nor gnome-
ses
I get a
gnome-session[5722]: WARNING: Unable to stop system: Not Authorized
in my .xsession-errors file. Maybe this is related to #660120?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838792
Title:
Here is my output. I executed the command, and my system did just log
out instead of shutting down.
Looks like there are no indications on what went wrong in the log file.
** Attachment added: "gtk-logout.log"
https://bugs.launchpad.net/unity-foundations/+bug/838792/+attachment/2409493/+files
*** This bug is a duplicate of bug 849073 ***
https://bugs.launchpad.net/bugs/849073
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849362
Title:
update-manager
*** This bug is a duplicate of bug 839740 ***
https://bugs.launchpad.net/bugs/839740
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/840835
Title:
zeitgeist-daem
Since a few weeks, the empty window problem has gone for me. Can you
please check if the problem still exists with the newest oneiric and set
the status back to confirmed?
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
Also managed to reproduce this issue with libreoffice 1:3.4.2-2ubuntu3
in current oneiric.
** Also affects: libreoffice (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.
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835666
Title:
software-center-gtk3 crashed with TypeError in _button3_action():
gobject `GtkImageMenuItem' doesn't su
This is likely a duplicate of #802527
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/831055
Title:
alt-tab raises one window and focuses another
To manage notifications about this bug go to:
https:/
Mine looks slightly different:
$ sudo ls /var/lib/lightdm/ -al
insgesamt 48
drwxr-x--- 10 lightdm lightdm 4096 2011-08-26 20:08 .
drwxr-xr-x 61 rootroot4096 2011-08-25 21:19 ..
drwx-- 3 lightdm lightdm 4096 2011-08-11 20:31 .cache
drwx-- 4 lightdm lightdm 4096 2011-08-11 20:31 .c
Crash still occurs with unity-greeter 0.0.5-0ubuntu2 after upgrade and
system restart. In fact, apport directly forwarded me to this bug page
(again).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8325
Please take as an example #829741 and #827164 (both public) which were
filed as a duplicate of #832029 (private!) by "Apport retracing
service". The reminder window in the two original bug says that it is a
duplicate, and you should only comment when you think it is wrong. But
without seeing the "m
In my opinion, there is a fundamental problem wrt interworking between
udev and lvm during the init phase. Looking at scripts and source code I
found nothing which prevents the following to happen:
1) kernel boots with initial ramdisk
2) udevd of initial ramdisk is started by initrd.img/scripts/in
In /boot/initrd.img-3.0.0-8-generic/scripts/init-bottom/udev I see these
two lines:
# Stop udevd, we'll miss a few events while we run init, but we catch up
udevadm control --exit
Just a wild speculation, because I haven't yet digged into the
interactions between kernel and udevd, but the semapho
I managed to obtain a logfile from the lvm command when it hangs:
libdm-deptree.c:941 Resuming phenom-data2 (253:0)
libdm-common.c:1153 Udev cookie 0xd4d0511 (semid 0) created
libdm-common.c:1166 Udev cookie 0xd4d0511 (semid 0) incremented
libdm-common.c:1054 Udev cookie 0xd4d0511 (semid 0
*** This bug is a duplicate of bug 827164 ***
https://bugs.launchpad.net/bugs/827164
** This bug has been marked a duplicate of bug 827164
oneconf-query crashed with DBusException in __new__():
org.freedesktop.DBus.Error.NoServer: Failed to connect to socket
/tmp/dbus-L6CdrvOMam: Connect
The update came a few minutes too late. Already fixed in unity-2d
4.0.0-0-ubuntu2.
** Changed in: unity-2d (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/829
There appears to be a version restriction wrt libnux:
$ sudo apt-get install unity-2d-panel
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you
Here is a "me too" posting.
My system:
* three harddisks
* WD 750GB
* WD 150GB (raptor)
* OCZ Vertex3 120GB
* one volume group on the WD 750GB HDD
* one LV within VG to be mounted at boot (via fstab)
* root filesystem is on the Vertex3 SSD. Maybe there is a timing issue, the SSD
is quite fa
Bug reproducable with HDD installation of oneiric. gnome-disk-utility
3.0.2-1ubuntu1 still gives error message:
Error unmounting: umount exited with exit code 1: helper failed with:
umount: only root can unmount /dev/mapper/vg-data2 from /mnt/data2
** Changed in: gnome-disk-utility (Ubuntu)
I installed 0.3.1-0ubuntu2 but restart is still missing in the
SessionMenu. Maybe you should call the menu entry "Shut Down/Restart"
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/815077
Title:
*** This bug is a duplicate of bug 743724 ***
https://bugs.launchpad.net/bugs/743724
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814214
Title:
gvfs-gdu-volume
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813034
Title:
zeitgeist-daemon crashed with LookupError in remove_from_connection():
<_zeitgeist.engine.remote.Remote
This bug is likely related to #807306
I my case the problem was "umountroot" not being called at system
shutdown due to wrongly renumbered init scripts caused by a broken 3rd
party package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.edge.launchpad.net/bugs/783097/+attachment/2216461/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
1 - 100 of 149 matches
Mail list logo
