[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
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 "Available to all users" have a different cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 805087] Re: Dash and launcher appear underneath windows
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/805087 Title: Dash and launcher appear underneath windows To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/805087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742889] Re: DigiCert certificates should be included in Ubuntu
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 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/742889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257857] Re: cgroup-lite fails to install in container in precise
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://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1257857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings
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 doubt I will be eligible for viewing sensitive data. The main problem is still that when observing a problem I have no means of checking if it already has been filed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764414 Title: private master bugs are confusing and lead to more duplicate filings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505278] Re: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?
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. Also, why are all identities auto-added? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/505278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465706] Re: SRU: New upstream releases of nvidia for 14.04.3
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 a failed dkms build and my machine did reboot into X11 successfully. I guess the "real" test will be when the next kernel update is released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465706 Title: SRU: New upstream releases of nvidia for 14.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1465706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295774] Re: ERROR processing policydb rules for profile lxc-container-default, failed to load
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295774 Title: ERROR processing policydb rules for profile lxc-container-default, failed to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1295774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262238] Re: [SRU] Add support for the lts-saucy stack
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://bugs.launchpad.net/bugs/1262238 Title: [SRU] Add support for the lts-saucy stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262238] Re: [SRU] Add support for the lts-saucy stack
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262238 Title: [SRU] Add support for the lts-saucy stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262238] Re: [SRU] Add support for the lts-saucy stack
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262238 Title: [SRU] Add support for the lts-saucy stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276379] Re: fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some "legacy" devices (Radeon HD 2000 3000 4000)
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 during boot. WARNING: fglrx-8.x is incompatible with the saucy stack! In order to operate fglrx-8.x after experimenting with the saucy enablement stack, one has to downgrade back to the precise stack (kernel+X11+mesa). I was positively surprised by the performance of the open source radeon driver in saucy. 3D unity performance is on par with the fglrx, while things which did not work before (e.g. DVI output on docking station) work now like a charm. I don't do gaming on the laptop, so I can't tell how well the open source radeon driver performs with 3D in general. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276379 Title: fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some "legacy" devices (Radeon HD 2000 3000 4000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1276379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
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 of three of my systems. This gives me the feeling that this is probably a widespread problem among ubuntu users. Nevertheless, most users are likely not aware of this since they only use the (unity) GUI which does nowhere report this problem! I don't know what the root cause of this problem is, but the only currently known symptom (cause) is that plymouthd does not exit at shutdown.Therefore I'm setting back the status to confirmed. ** Changed in: plymouth (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776499] Re: gvim gets no global menu, timeout warning on the console
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776499 Title: gvim gets no global menu, timeout warning on the console To manage notifications about this bug go to: https://bugs.launchpad.net/dbusmenu/+bug/776499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776499] Re: gvim gets no global menu, timeout warning on the console
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 for the dbusmenu to succeed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776499 Title: gvim gets no global menu, timeout warning on the console To manage notifications about this bug go to: https://bugs.launchpad.net/dbusmenu/+bug/776499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783097] Re: USB 3.0 devices not working behind USB 3.0 HUBs
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. Nevertheless, since I can use my USB3.0 equipment to the full extend I'm marking this as fixed. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/783097 Title: USB 3.0 devices not working behind USB 3.0 HUBs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/783097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93273] Re: ICE1712 sound does not work after S3/S4-resume
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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/93273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736930] Re: NM frequently disconnects mobile broadband and refuses to reconnect -- Huawei E156G, E620
"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 -- Huawei E156G, E620 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/736930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 592176] Re: A first document opens very slowly
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 notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/592176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 829301] Re: Broken dependencies - ubuntu-desktop : Depends: unity-2d
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 are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: unity-2d-panel : Depends: libnux-1.0-0 (< 1.2.2) but 1.2.2-0ubuntu1 is to be installed Depends: libunity-2d-private0 (= 4.0.0-0ubuntu1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ** Also affects: unity-2d (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/829301 Title: Broken dependencies - ubuntu-desktop : Depends: unity-2d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/829301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 829301] Re: Broken dependencies - ubuntu-desktop : Depends: unity-2d
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/829301 Title: Broken dependencies - ubuntu-desktop : Depends: unity-2d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/829301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 829741] Re: oneconf-query crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-QQ7Qelw2V1: Connection refused
*** 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: Connection refused ** 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/829741 Title: oneconf-query crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp /dbus-QQ7Qelw2V1: Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oneconf/+bug/829741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: boot hangs at initrd
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) incremented libdm-common.c:1226 Udev cookie 0xd4d0511 (semid 0) assigned to dm_task type 5 with flags 0x0 ioctl/libdm-iface.c:1821 dm resume (253:0) NF [16384] libdm-common.c:828 phenom-data2: Stacking NODE_READ_AHEAD 256 (flags=1) libdm-common.c:1081 Udev cookie 0xd4d0511 (semid 0) decremented libdm-common.c:1276 Udev cookie 0xd4d0511 (semid 0): Waiting for zero Obviously, lvm waits for udev to decrement the device-mapper task semaphore. A strange observation is that when looking at "ps ax" the PID(s) of udevd (437,829,839) suggest that udevd was started after the lvm tool (pid 355). Maybe there is a small time window when udevd is not able to perform the semaphore decrementation. ** Attachment added: "output of "ps ax" when "lvm vgchange -a y" hangs" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+attachment/2296618/+files/ps-ax.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: boot hangs at initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: boot hangs at initrd
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 semaphore decrementation event might be lost when transitioning from the initrd-udevd to the rootfs-udevd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: boot hangs at initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: boot hangs at initrd
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/init-top/udev 3) udevd handles the initial events of the block devices (partitions) produced by "udevadm trigger --action=add ..." invoked by "initrd.img/scripts/init-top/udev". Please note that this is executed in the background using "&". 4) /lib/udev/rules.d/85-lvm2.rules intercepts add events for LVM partitions and issues "watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'" 5) "lvm vgchange -a y" sends a LV resume request to the device-mapper in the kernel and waits for completition notification by udevd via semaphore 6) initrd.img/scripts/init-bottom/udev gets executed which invokes "udevadm control --exit". After this point, the initrd-udevd is not handling events anymore. 7) kernel delivers the mapper-task-completion-event to udevd which does not handle events anymore, and therefore does not decrement the semaphore 8) having already waited 60 seconds (event_timeout) for "watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'" to complete, udevd just gives up and continues termination 9) according to udev-173/udev/udevd.c:1631 the remaining queued events (including the semaphore decrement) are discarded by means of "event_queue_cleanup". 10) after termination of udevd "udevadm control --exit" also terminates and the boot process continues In the end, the rootfs-udevd does not see the semaphore decrement event anymore, so "lvm vgscan -a y" still hangs. Some other bugs like #631795 #797226 #581566 might be related to this timing problem. Also adding udev to the bug. Please set to invalid if e.g. lvm is required to wait for the logical volume setup to finish in initrd.img/scripts/init-premount/lvm2. ** Also affects: udev (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/802626 Title: boot hangs at initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings
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 "master" bug report this is not possible. Furthermore it is strange that (judging from the bug numbers) "Apport retracing service" prefers the newer+private bug in favor of the older+public bug reports in this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764414 Title: private master bugs are confusing and lead to more duplicate filings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 885991] Re: no window manager on second screen for dual head mode
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/885991 Title: no window manager on second screen for dual head mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/885991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
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: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
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 install, and not install the buggy package again, until the package provider fixed it. -- 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: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
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 enough to be able to backup your data. E.g. on halt, the harddisks will not be unmounted properly. -- 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: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864051] [NEW] TRIM support not enabled for SSDs
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 partman-target N: Unable to locate package partman-target 3) What you expected to happen Partitions on disk devices with TRIM support entered in fstab with the 'discard' mount option 4) What happened instead Partitions on disk devices are always entered without the 'discard' option in fstab I hope this is the right package; I found no other package generating the fstab. ** Affects: partman-target (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/864051 Title: TRIM support not enabled for SSDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-target/+bug/864051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 833891] Re: lvscan often times out during boot
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 times out during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/833891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 833891] Re: lvscan often times out during boot
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 scan to hang. And due to deamonizing, this would probably go unnoticed for the whole system uptime. Actually your pointer to bug 818177 is relevant. In comment 19 steve is proposing a solution for the problem I described. -- 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 times out during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/833891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776499] Re: gvim gets no global menu, timeout warning on the console
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 might be that the ongoing dbus transaction (i.e. the menu creation) does not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776499 Title: gvim gets no global menu, timeout warning on the console To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/776499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' does not kill udevd worker threads
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 boot, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' does not kill udevd worker threads
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:2261.0004: input,hidraw3: USB HID v1.10 Mouse [ATEN CS1308 V1.2.114] on usb-:00:1d.2-1.1/input1 [ 63.200054] bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.1.fw" [ 63.200148] bnx2 :03:00.0: PCI INT A disabled Isn't this the 60s wait from "udevadm control --exit"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' does not kill udevd worker threads
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849362] Re: update-manager crashed with TypeError in confirmChanges(): glib.markup_escape_text() takes at most 1 argument (2 given)
*** 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 crashed with TypeError in confirmChanges(): glib.markup_escape_text() takes at most 1 argument (2 given) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/849362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828756] Re: getting "connection is untrusted" warnings
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://bugs.launchpad.net/ubuntu/+source/empathy/+bug/828756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: vgchange may deadlock in initramfs when VG present that's not used for rootfs
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/mapper nodes missing (see comment #12). On the other hand, with the current behavior of udev waiting is pointless, because udevd immediately aborts event processing, and afterwards waits for vgchange to complete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: vgchange may deadlock in initramfs when VG present that's not used for rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597092] Re: palimpsest cannot unmount partition in fstab
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) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/597092 Title: palimpsest cannot unmount partition in fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/597092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: boot hangs at initrd
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 fast. Symtoms on my host * Only happens occasionally on boot; mostly after a cold-start * my system boots after a delay of about 60s, but my root partition is still mounted read-only * aside from root, none of the other partitions in fstab is mounted * X11 does not start (because of read-only mount) * I can login, but /home is not mounted * like with the original reporter, "vgchange -a y" hangs. I found it to hang in "semtimedop". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: boot hangs at initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' does not kill udevd worker threads
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 Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' does not kill udevd worker threads
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 and aborts the execution of init-bottom/udev. And in the "normal" case, init-bottom/udev aborts because "udevadm control --exit" reports by means of its return value that, after timeout (yes, udevadm has its own timeout of 60s!), the exit failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' does not kill udevd worker threads
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 interested to see what causes udevd to hang in an non-LVM setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' times out while udevd waits for an already-dead thread
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 to make: I'd set the udevadm-control timeout at least to 70 seconds. The epoll_wait timeout is reset every time something happens. So if the "settle time" is bigger than 1 second, the total timeout would be more than 61 seconds of udevadm-control. Setting the timeout to 70 seconds, gives us at least 10 seconds "settle time". My conclusion is that "udevadm control --exit" (introduced in april) is still a bit immature, and further races might wait to happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' times out while udevd waits for an already-dead thread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818177] Re: boot failures because 'udevadm exit' times out while udevd waits for an already-dead thread
> (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 of udevadm- control failing to do something which gets 100% attention of the user, and with an explicit diagnosis message describing the problem? Simply not moving '/dev' to rootfs, and letting the failed boot to reach its "fate", seems to be a bit too obscure for me. Being an "expert user", I would also like to have the busybox-shell for the failure case 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/818177 Title: boot failures because 'udevadm exit' times out while udevd waits for an already-dead thread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: vgchange may deadlock in initramfs when VG present that's not used for rootfs
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 1. It waits for udevd to call the 55-dm.rules rule
ENV{DM_COOKIE}=="?*", RUN+="/sbin/dmsetup udevcomplete $env{DM_COOKIE}"
to be processed. But since udevd is not accepting events after "udevadm
control --exit", and any event, which arrived before closing the netlink
socket, is discarded, 'vgchange -a y' waits forever.
Reading the documentation of dmsetup, I found the udevcomplete_all
option. This might be a means to finish hanging 'vgchange -a y'
processes, and could be called from within a init-bottom script of
initramfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802626
Title:
vgchange may deadlock in initramfs when VG present that's not used for
rootfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: vgchange may deadlock in initramfs when VG present that's not used for rootfs
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_queue_cleanup(udev, EVENT_QUEUED); from the main loop. This would not eliminate the potential of hanging, but in theory it should at least avoid events being lost. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: vgchange may deadlock in initramfs when VG present that's not used for rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872250] [NEW] if init-bottom/udev fails, system silently fails to boot
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 enough about this critical event. Potential results: * filesystems not mounted properly (See Bug #870031) * System does boot, but unknown side-effects happen. Due to lack of (flashy) reporting, identifying the root-cause (init-bottom/udev) might turn out to be hard * Logs of bug reports filed to the wrong packages ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: udev 173-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 CustomUdevRuleFiles: ws444pc.rules Date: Tue Oct 11 14:09:18 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=77149c3f-f2f2-40f8-a4f7-44d69f3f186b ro SourcePackage: udev UpgradeStatus: Upgraded to oneiric on 2011-09-13 (27 days ago) dmi.bios.date: 11/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1406 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A32-MVP DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1406:bd11/21/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A32-MVPDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- 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/+source/udev/+bug/872250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872250] Re: if init-bottom/udev fails, system silently fails to boot
-- 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/+source/udev/+bug/872250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872250] Re: if init-bottom/udev fails, system silently fails to boot
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. This could be considered to be a fix for this bug. There is still the question of extending the scope of this bug. IMHO any failure within the initramfs phase is worth a 'panic'. This would even make the point of adding 'panic' to the call_scripts function within scripts/functions for cases when a called script returns with error code. (N.B. For testing, I tried to unconditionally call 'panic' in init- bottom/udev, but it just said something like "panic: command not found". The system did boot normally!) -- 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/+source/udev/+bug/872250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872044] Re: Bluetooth 'Send files' returns permission denied error
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872044 Title: Bluetooth 'Send files' returns permission denied error To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/872044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 817326] Re: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync
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 #317781, has it been removed from the linux kernel? -- 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 bytes long) - LibreOffice should call fsync To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220991] Re: Thunderbird corrupts attachments from IMAP exchange server
** 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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/220991 Title: Thunderbird corrupts attachments from IMAP exchange server To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/220991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220991] Re: Thunderbird corrupts attachments from IMAP exchange server
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 to Ubuntu. https://bugs.launchpad.net/bugs/220991 Title: Thunderbird corrupts attachments from IMAP exchange server To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/220991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566812] Re: USB Modem wont connect after modem hangup
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 connect after modem hangup To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/566812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830846] Re: Ubuntu 10.04.2 (2.6.32-32-server) random kernel panic on xfs write
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-context.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830846 Title: Ubuntu 10.04.2 (2.6.32-32-server) random kernel panic on xfs write To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/830846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775543] Re: xhci_hcd: Timeout while waiting for a slot - Issue with USB3 hard disk on 11.04 x86_64
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 xHCI host is not halting. [ 45.089636] xhci_hcd :07:00.0: Completing active URBs anyway. [ 45.089656] xhci_hcd :07:00.0: HC died; cleaning up [ 57.950270] xhci_hcd :07:00.0: Timeout while waiting for a slot [ 108.170035] xhci_hcd :07:00.0: Timeout while waiting for a slot Device is the same as for the original submitter: 07:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) (prog-if 30 [XHCI]) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775543 Title: xhci_hcd: Timeout while waiting for a slot - Issue with USB3 hard disk on 11.04 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/775543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 817326] Re: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync
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 bytes long) - LibreOffice should call fsync To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832533] Re: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()
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/832533 Title: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance() To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/832533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832533] Re: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()
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 .config drwx-- 3 lightdm lightdm 4096 2011-08-11 20:31 .dbus -rw--- 1 lightdm lightdm 16 2011-08-11 20:31 .esd_auth drwxr-xr-x 2 lightdm lightdm 4096 2011-08-25 21:18 .fontconfig drwx-- 2 lightdm lightdm 4096 2011-08-26 20:08 .gconf drwx-- 2 lightdm lightdm 4096 2011-08-11 20:31 .gvfs drwxrwxr-x 3 lightdm lightdm 4096 2011-08-26 19:59 .local drwx-- 2 lightdm lightdm 4096 2011-08-26 20:08 .pulse -rw--- 1 lightdm lightdm 256 2011-08-11 20:31 .pulse-cookie -rw--- 1 lightdm lightdm0 2011-08-26 20:08 .Xauthority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832533 Title: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance() To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/832533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
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-dispatcherREADME S31umountnfs.sh S60umountroot K20unattended-upgrades S20sendsigs S35networkingS90reboot K74bluetoothS30urandom S40umountf # AFTER INSTALL OF turboprint 2.21-1 eduard@qemu-oneiric:~$ ls /etc/rc6.d K01speech-dispatcherREADME S01sendsigs S01umountroot K01unattended-upgrades S01networking S01umountfs S02urandom K02bluetoothS01reboot S01umountnfs.sh # AFTER ACTIVATION OF oneiric-proposed eduard@qemu-oneiric:~$ ls /etc/rc6.d K01speech-dispatcherREADME S20sendsigs S60umountroot K01unattended-upgrades S01networking S31umountnfs.sh S90reboot K02bluetoothS02urandom S40umountfs Apparently, not all scripts are restored, but the most important are. On a further note, i can confirm that insserv is not in the search path anymore, and calling it from bash reports that insserv is not installed. (This might be a bit misleading, but personally I don't care) -- 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: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248870] Re: [upstream] Autosave causes document to scroll back to cursor position
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.launchpad.net/bugs/248870 Title: [upstream] Autosave causes document to scroll back to cursor position To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/248870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 814623] Re: on resume thunderbird shows an empty account window
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/814623 Title: on resume thunderbird shows an empty account window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/814623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 840835] Re: zeitgeist-daemon crashed with RuntimeError in _check_index(): basic_string::assign
*** 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-daemon crashed with RuntimeError in _check_index(): basic_string::assign To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/840835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838792] Re: "Restart" logs out, even when there are no other people logged in
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/gtk-logout.log -- 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: "Restart" logs out, even when there are no other people logged in To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/838792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838792] Re: "Restart" logs out, even when there are no other people logged in
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: "Restart" logs out, even when there are no other people logged in To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/838792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839325] Re: [ Oneiric i386 b1 ] gtk-logout-helper crashed with signal 5 in __libc_start_main()
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- session are responsible for the bug, and there is a different common root cause.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839325 Title: [ Oneiric i386 b1 ] gtk-logout-helper crashed with signal 5 in __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/839325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838792] Re: "Restart" logs out, even when there are no other people logged in
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/pam.d and try a "sudo pam-auth-update --package"? -- 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: "Restart" logs out, even when there are no other people logged in To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/838792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 831055] Re: alt-tab raises one window and focuses another
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://bugs.launchpad.net/ubuntu/+source/unity/+bug/831055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835666] Re: software-center-gtk3 crashed with TypeError in _button3_action(): gobject `GtkImageMenuItem' doesn't support property `stock_id'
** 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 support property `stock_id' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/835666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770391] Re: Ubuntu 18.04 josm: No valid JVM found
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 go to: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/1770391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806257] ProcCpuinfoMinimal.txt
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/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806257] Dependencies.txt
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 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806257] [NEW] gnome-shell excessive logging cannot bind to x11-unix
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 gigabytes of messages to syslog * power-button does work and system shuts down when pressed --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-12-29 (1069 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: mutter 3.28.3-2~ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-17 (287 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: 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 gigabytes of messages to syslog * power-button does work and system shuts down when pressed + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2015-12-29 (1069 days ago) + InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + Package: mutter 3.28.3-2~ubuntu18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-39-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-02-17 (287 days ago) + UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806257] ProcEnviron.txt
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 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806257] Re: gnome-shell excessive logging cannot bind to x11-unix
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 nicht gefunden Downgrading the mutter package makes the error go away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806257] Re: gnome-shell excessive logging cannot bind to x11-unix
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 the system failing in such an obscure way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()
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 furthermore that this web browser is not initialized on demand, but unconditionally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751460 Title: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacageoperator() To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592514] Re: 3G usb Card - mmcli and network manager broken compatibility
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592514 Title: 3G usb Card - mmcli and network manager broken compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807499] [NEW] 30 seconds boot delay when root fs is on lvm
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-top OR nfs-top After these scripts have been executed, the root device node is expected to be present (local) or the network interface is expected to be usable (NFS). But what /usr/share/initramfs-tools/scripts/local-top/lvm2 is simply try to activate the requested root volume by means of scanning the (at that moment) available block devices. What happens on my system is that local-top/lvm2 is executed before the pv block device (SATA-SSD) shows up. Then initramfs-tools calls the wait-for-root executable which waits for the root device node notification via udev. This has a (minimum) timeout of 30 seconds configured. This timeout is exceeded since nothing will make the root volume device to be created. Then later (I guess in local-block) the root volume device is created (since the pv is available). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 8 13:52:06 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807499 Title: 30 seconds boot delay when root fs is on lvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1807499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807499] Re: 30 seconds boot delay when root fs is on lvm
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 waiting for the
root LV to appear. A hack for doing so is to replace in
/lib/udev/rules.d/69-lvm-metad.rules the line 96
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor --activate ay", GOTO="lvm_end"
with
ACTION!="remove", RUN+="/sbin/lvm pvscan --cache $major:$minor --activate ay"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807499
Title:
30 seconds boot delay when root fs is on lvm
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1807499/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775283] Re: SRU of LXC 3.0.1 (upstream bugfix release)
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
9de31d5a1394fd0bed495fa7cde5e625a1d64b48 made this break. Can this SRU
be reverted for now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775283
Title:
SRU of LXC 3.0.1 (upstream bugfix release)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1775283/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775283] Re: SRU of LXC 3.0.1 (upstream bugfix release)
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/1775283 Title: SRU of LXC 3.0.1 (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1775283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783097] Re: USB 3.0 devices not working behind USB 3.0 HUBs
For experiment, I upgraded now my natty (test) install to oneiric (11.10). Oneiric uses linux-image-2.6.39-2, and is therefore supposed to contain the patch. The result: as suspected, the USB 3.0 HUB works! I can now mount and read/write the USB 3.0 HDDs connected to the HUB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783097 Title: USB 3.0 devices not working behind USB 3.0 HUBs -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765230] Re: long sleep in boot process
Another very strange observation: When I disable "Legacy USB Support" in BIOS the "sleep" does not happen! BIOS Config: Advanced -> USB Configuration -> Legacy USB Support -> Disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765230 Title: long sleep in boot process -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765230] Re: long sleep in boot process
Before everybody stumbling upon this bug disables "legacy USB support" one WARNING: This feature is required to boot from USB storage (sticks, cdrom, etc.), and (AFAIK) to be able to change BIOS settings using an USB keyboard. The main reason for posting the information was to provide another piece of information which might help identifying the root cause for the bug. If disabling "legacy USB support" does not harm you, it is nevertheless a viable solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765230 Title: long sleep in boot process -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 377175] Re: Volume Up button locks screen
I see two possibilities why the Macally keyboard locks the screen. Either it emits Usage ID 0xF9 on HID Usage Page 0x07 (Keyboard), or it emits Usage ID 0x19e on HID Usage Page 0x0C (Consumer). In order to verify this theory, it might be useful to have a look at the HID descriptor and the HID events. Depending on the results, special quirk handling of the keyboard might be added to the linux kernel and/or gnome-screensaver gets a option to ignore the (fake) "lock screen" key. HOWTO: 1. get the USB vendor+product ID using lsusb > lsusb Search for the line with the Macally Keyboard (e.g. I get "Bus 001 Device 007: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard" for my keyboard, so the vendor:id is 046a:0023) 2. look at the device descriptors > cd /sys/kernel/debug/hid > ls (I have here four entries, my keyboard makes up two of them 0003:046A:0023.0002 and 0003:046A:0023.0003; notice the matching vendor:id 046a:0023) > sudo cat $YOUR_DEVICE1/rdesc > sudo cat $YOUR_DEVICE2/rdesc 3. look at the events of the keys (Please be aware that the following records all your keypresses, so don't enter passwords or other sensitive information if you intend to post the event log to the bug report! Entering the password for "sudo" is ok, because it asks the password _before_ running the command) 3.1 first device > sudo cat $YOUR_DEVICE1/events press the volume up key exit with CTRL-C 3.2 second device > sudo cat $YOUR_DEVICE2/events press the volume up key again exit with CTRL-C Please find attached the output from my keyboard. It is only for demonstration purposes, because when connected via USB my keyboard does not exhibit the "lock screen" bug. ** Attachment added: "Out from hid-debug console session" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/377175/+attachment/2145520/+files/hid-debug-cherry.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/377175 Title: Volume Up button locks screen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730488] Re: [Lucid] xf86ScaleAxis problems with high resolution devices
I see a '[drm] failed to load kernel module "i915"' in your log file. What dmesg output do you get when you try "modprobe i915"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730488 Title: [Lucid] xf86ScaleAxis problems with high resolution devices -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 377175] Re: Volume Up button locks screen
** Also affects: gnome-screensaver (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/377175 Title: Volume Up button locks screen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 377175] Re: Volume Up button locks screen
Launching "dbus-monitor --system" and pressing the button gives signal sender=:1.12 -> dest=(null destination) serial=2054 path=/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input; interface=org.freedesktop.Hal.Device; member=Condition string "ButtonPressed" string "coffee" In gnome-screensaver/src/gs-listener-dbus.c there is a hard-coded(!) handler for the "coffee" button which instruct gnome-screensaver (i.e. itself) to lock the screen. Apparently, unrelated buttons are mapped by HAL to the "coffee" button. E.g. I have the problem with my Cherry CyMotion master linux keyboard, when I press the "Copy" key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/377175 Title: Volume Up button locks screen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 377175] Re: Volume Up button locks screen
Further information: I use the Keyboard (Cherry CyMotion Master Linux) in PS/2 mode on a docking station of an HP notebook. In "/usr/share/hal/fdi/information/30-keymap-hp.fdi" the scancode of the copy key (e00a) is mapped to "screenlock". In the same directory, mappings for several other computer manufacturers are provided. And since gnome-screensaver listens on "screenlock" (which is identical to "coffee"), the screensaver is started when the "copy" key is pressed. I use the same keyboard on a different computer (non-HP) and there the behavior is not observed, since the manufacturer string does not match in "30-keymap-hp.fdi" and the scancode (e00a) is not set. This is not directly related to the Macally keyboard since it is connected by means of USB, but somehow on kernel level keycode 152 (KEY_COFFEE) is likely to be generated, which completely bypasses the X11 key handling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/377175 Title: Volume Up button locks screen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765230] Re: long sleep in boot process
Confirmation from my side: 07f4beb0b5bbfaf36a64aa00d59e670ec578a95a fixes the problem also on my M3A32-MVP. So it is very likely that the fix will be included in the next LTS. WRT natty: The patch is apparently small enough for a SRU. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765230 Title: long sleep in boot process -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
