[Bug 1873760] [NEW] Does not work on HiDPI screens
Public bug reported: It does not take display scaling into account. So on a HiDPI screen (4k in my case) it measures only half the amount of pixels. ** Affects: screenruler (Ubuntu) Importance: Undecided Status: New ** Attachment added: "image.png" https://bugs.launchpad.net/bugs/1873760/+attachment/5357041/+files/image.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873760 Title: Does not work on HiDPI screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screenruler/+bug/1873760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436302] Re: python3.4 segmentation fault while running unattended-upgrade
> Python crashes are almost always caused by misbehaving extension modules. I understand it may not be caused by python itself. I've added the unattended-upgrades package to the affects list. ** Also affects: unattended-upgrades (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/1436302 Title: python3.4 segmentation fault while running unattended-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1436302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436302] [NEW] python3.4 segmentation fault while running unattended-upgrade
Public bug reported: We run 'unattended-upgrade -d' from cron and have seen regular core dumps. Below is some gdb output for one case: (gdb) where #0 _int_malloc (av=av@entry=0x7fd4362de760 , bytes=bytes@entry=193) at malloc.c:3489 #1 0x7fd435fa17e1 in _int_realloc (av=0x7fd4362de760 , oldp=0xd6fe30, oldsize=144, nb=208) at malloc.c:4286 #2 0x7fd435fa2fc9 in _GI__libc_realloc (oldmem=0xd6fe40, bytes=200) at malloc.c:3029 #3 0x004851cd in PyMem_Realloc (new_size=, ptr=) at ../Objects/obmalloc.c:308 #4 list_resize.7991 (self=0x7fd436549e48, newsize=17) at ../Objects/listobject.c:63 #5 0x00485269 in app1 (v=0x7fd435306288, self=0x7fd436549e48) at ../Objects/listobject.c:294 #6 PyList_Append (op=op@entry=0x7fd436549e48, newitem=newitem@entry=0x7fd435306288) at ../Objects/listobject.c:306 #7 0x005bf7a9 in PyImport_Cleanup () at ../Python/import.c:464 #8 0x005bf945 in Py_Finalize.part.6.32879 () at ../Python/pythonrun.c:616 #9 0x0060cb12 in Py_Finalize () at ../Python/pythonrun.c:564 #10 Py_Main (argc=argc@entry=3, argv=argv@entry=0xae6010) at ../Modules/main.c:771 #11 0x0041ec0d in main (argc=3, argv=) at ../Modules/python.c:69 Note that gdb always complains that the coredump may not match the binary I provided. However, I'm pretty sure I got the right one. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3-minimal 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Wed Mar 25 11:57:03 2015 Ec2AMI: ami-254ad452 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: r3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436302 Title: python3.4 segmentation fault while running unattended-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1436302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425897] [NEW] package plymouth-theme-ubuntu-text 0.8.8-0ubuntu17.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio
Public bug reported: some packages not installed and/or some files not removed ProblemType: Package DistroRelease: Ubuntu 14.04 Package: plymouth-theme-ubuntu-text 0.8.8-0ubuntu17.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Feb 26 12:02:34 2015 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DuplicateSignature: package:plymouth-theme-ubuntu-text:0.8.8-0ubuntu17.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-03-26 (336 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: HP-Pavilion FL360AA-ABH m9480nl ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=e583b796-0e8a-4899-9811-944481505d26 ro quiet splash vt.handoff=7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=e583b796-0e8a-4899-9811-944481505d26 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: package plymouth-theme-ubuntu-text 0.8.8-0ubuntu17.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-04-30 (301 days ago) dmi.bios.date: 09/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.30 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.30:bd09/05/2008:svnHP-Pavilion:pnFL360AA-ABHm9480nl:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: FL360AA-ABH m9480nl dmi.sys.vendor: HP-Pavilion ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425897 Title: package plymouth-theme-ubuntu-text 0.8.8-0ubuntu17.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1425897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425897] Re: package plymouth-theme-ubuntu-text 0.8.8-0ubuntu17.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
i am not an experienced user sorry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425897 Title: package plymouth-theme-ubuntu-text 0.8.8-0ubuntu17.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1425897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891825] Re: NFS client doesn't mount or mounts slow on startup on 11.10
I have an QNAP TS-239 Pro II with the NFS-server and it has an NFS Access Control (some sort of firewall ??) Network Share Name:xxx Access Right: no limit Allowed IP Address or Domain Name: x On the server side (QNAP TS-239 Pro II) nothing was changed. The only change was the change from Ubuntu 10.10 to Ubuntu 11.10. When I use the same fstab Ubuntu 11.10 as in Ubuntu 10.10 there will be an delay of almost 1 minute to mount the shares. When I add nfsvers=3, the mounting is direct at booting time as it was in Ubuntu 10.10. Examples: 192.168.1.130:/pictures /media/NAS-pictures nfs ro,hard,intr 0 0 This share is mounting in Ubuntu 11.10 after 1 minute 192.168.1.130:/pictures /media/NAS-pictures nfs ro,nfsvers=3,hard,intr 0 0 This share is mounting in Ubuntu 11.10 direct at booting. So I think it has nothing to do with an firewall. There is some change in handling of nfs shares in Ubuntu 11.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891825 Title: NFS client doesn't mount or mounts slow on startup on 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/891825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891825] Re: NFS client doesn't mount or mounts slow on startup on 11.10
Linux manual: "To mount an export using NFS version 2, use the nfs file system type and specify the nfsvers=2 mount option. To mount using NFS version 3, use the nfs file system type and specify the nfsvers=3 mount option. To mount using NFS version 4, use either the nfs file system type, with the nfsvers=4 mount option, or the nfs4 file system type." Maybe you should give a try to add nfsvers=4 to your fstab. For instance: ubuntuserver:/media/huge /media/huge nfs rsize=16384,wsize=16384,rw,nfsvers=4,auto,nolock or something like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891825 Title: NFS client doesn't mount or mounts slow on startup on 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/891825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891825] Re: NFS client doesn't mount or mounts slow on startup on 11.10
Maybe the next thing could be helpful.: I have a NAS-server (nfs3 !) and I mount on my Ubuntu desktops several shares. On Ubunt 10.10 this shares where mounted instantly at booting. Now I am using Ubuntu 11.10 I must wait 1 minute till the mounts are up. The solution for me was ad the following line to fstab: nfsvers=3 Could this be an explanation ??: Ubuntu 11.10 tries to make by default a nfs4 mount. If the server has also a nfs4 structure this would not be a problem. But is the server has nfs3 the mounting succeed only after a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891825 Title: NFS client doesn't mount or mounts slow on startup on 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/891825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711517] Re: pm-suspend doesn't respect wol settings of network interface
I forgot, i'm using Ubuntu server 10.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711517 Title: pm-suspend doesn't respect wol settings of network interface -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711517] [NEW] pm-suspend doesn't respect wol settings of network interface
Public bug reported:
Binary package hint: pm-utils
When pm-suspend it issues a "ethtool -s "${d##*/}" wol g>/dev/null 2>&1" it
disregards the fact that i've set a ethtool -s eth0 wol ug.
This causes the system to not wake up from my desired packet types.
In my quest to finding out why my system wouldn't wake from unicast I
found out that there are several locations where wol settings are done.
powernap for one has a setting (which is overruled by pm-suspend).
I think there should be a system wide config file for ethtool
(/etc/default/ethtool?) this way wol settings could be set system wide.
** Affects: pm-utils (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/711517
Title:
pm-suspend doesn't respect wol settings of network interface
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 554172] Re: CUPS and other system services not starting at boot
Hello Robbie, If you plan to dive into this quagmire now you should have a look at bug 543506 as well (if you haven't already). It was marked a duplicate of this one. In 543506, Mike Bianchi posted some lines from his logs (May 26 email): May 26 09:37:42 autoaud-broad1 init: Failed to spawn rc-sysinit main process: unable to open console: Input/output error May 26 09:37:42 autoaud-broad1 init: rc-sysinit goal changed from start to stop May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from spawned to stopping I think the 'unable to open console' message points to the core of all this. Why would /dev/console not be available? Wout On Mon, Aug 2, 2010 at 05:24, Robbie Williamson < robbie.william...@canonical.com> wrote: > To summarize the 190+ comments on this bug: > 1) There is definitely a problem that needs fixing...no arguing this. > 2) It has *something* to do with when lo0 is activated, i.e. a race > condition > 3) There are apparently a few hacky workarounds, but no fix > 4) There is no concrete evidence that this is a kernel issue > 5) There is no concrete evidence that this is an upstart issue > > This bug is officially "on the radar", so we will figure out what's > causing the issue and address it in an SRU, but it's too late for > 10.04.1. > > > ** Package changed: linux (Ubuntu) => ubuntu > > ** Changed in: ubuntu > Importance: Critical => High > > -- > CUPS and other system services not starting at boot > https://bugs.launchpad.net/bugs/554172 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in Ubuntu: Confirmed > Status in The Lucid Lynx: Confirmed > > Bug description: > Binary package hint: cups > > Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups > start to after booting to print. > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: cups 1.4.2-10 > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > NonfreeKernelModules: nvidia > Architecture: i386 > Date: Fri Apr 2 13:07:35 2010 > InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) > Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: > Connection refused > MachineType: Dell Inc. Studio XPS 1340 > Papersize: letter > PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono > (recommended) > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic > root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash > ProcEnviron: > LANG=en_US.utf8 > SHELL=/bin/bash > SourcePackage: cups > dmi.bios.date: 09/08/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A11 > dmi.board.name: 0Y279R > dmi.board.vendor: Dell Inc. > dmi.board.version: A11 > dmi.chassis.asset.tag: 1234567890 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A11 > dmi.modalias: > dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: > dmi.product.name: Studio XPS 1340 > dmi.product.version: A11 > dmi.sys.vendor: Dell Inc. > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+bug/554172/+subscribe > -- CUPS and other system services not starting at boot https://bugs.launchpad.net/bugs/554172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 554172] Re: CUPS and other system services not starting at boot
My understanding of the problem is that /dev/console exists but isn't writable. Also, it appears it becomes writable after a little while. Would waiting for /dev/console to become writable be a possible workaround? For example by adding something like this to the relevant /etc/init/* scripts: pre-start script while ! /bin/dd if=/dev/null of=/dev/console 2>/dev/null do sleep 1 done end script If that works it may even be possible to restore the 'console output' lines (though this depends on whether they take effect after pre-start is executed). Note that this will hang if /dev/console does not become writable!! Another way to accomplish the above would be to create a /etc/init/console-ready job with the above pre-start section. Jobs that require /dev/console to be writable could then be made dependent on console-ready. I'd try the above myself but I've moved to Debian after too many issues with Ubuntu 10.04. Sad as generally I really like Ubuntu. Wout On Mon, Jul 19, 2010 at 22:26, Mike Bianchi <554...@bugs.launchpad.net>wrote: > On Mon, Jul 19, 2010 at 08:04:03PM -, phireph0x wrote: > > The workaround described in > > http://ubuntuforums.org/showpost.php?p=9480172&postcount=20 doesn't work > > for me. I still have services that don't start on system reboot. > > See > > https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/99 > and > > https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/81 > > Did you follow those instructions? > > -- > CUPS and other system services not starting at boot > https://bugs.launchpad.net/bugs/554172 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in “linux” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: cups > > Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups > start to after booting to print. > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: cups 1.4.2-10 > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > NonfreeKernelModules: nvidia > Architecture: i386 > Date: Fri Apr 2 13:07:35 2010 > InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) > Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: > Connection refused > MachineType: Dell Inc. Studio XPS 1340 > Papersize: letter > PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono > (recommended) > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic > root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash > ProcEnviron: > LANG=en_US.utf8 > SHELL=/bin/bash > SourcePackage: cups > dmi.bios.date: 09/08/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A11 > dmi.board.name: 0Y279R > dmi.board.vendor: Dell Inc. > dmi.board.version: A11 > dmi.chassis.asset.tag: 1234567890 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A11 > dmi.modalias: > dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: > dmi.product.name: Studio XPS 1340 > dmi.product.version: A11 > dmi.sys.vendor: Dell Inc. > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/+subscribe > -- CUPS and other system services not starting at boot https://bugs.launchpad.net/bugs/554172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 554172] Re: CUPS and other system services not starting at boot
On Thu, Jul 1, 2010 at 11:09, Michael Goetze wrote: > On 07/01/2010 10:18 AM, Wout wrote: > > So /dev/console exists but isn't immediately "ready for work". It appears > it > > becomes fully functional later (otherwise it would not be possible to > start > > the failing services manually). > > Can we figure out at what point /dev/console becomes functional? > > > > In the meantime two workarounds seem doable, both assuming /dev/console > > doesn't depend on anything started during boot: > > 1. A boot script that doesn't complete until /dev/console works, make > > rc/rc-sysinit boot sequence depend on it. > > 2. A patch in upstart that waits until /dev/console works. > > > > Any thoughts? > > I think if Scott's analysis is correct then the correct solution would > be to have the kernel buffer anything received on /dev/console until > it's ready to display it. > > That's why I wrote workaround not solution. > Anyone for reassigning this bug to the kernel? > > Regards, > Michael > > -- > CUPS and other system services not starting at boot > https://bugs.launchpad.net/bugs/554172 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in “upstart” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: cups > > Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups > start to after booting to print. > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: cups 1.4.2-10 > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > NonfreeKernelModules: nvidia > Architecture: i386 > Date: Fri Apr 2 13:07:35 2010 > InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) > Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: > Connection refused > MachineType: Dell Inc. Studio XPS 1340 > Papersize: letter > PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono > (recommended) > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic > root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash > ProcEnviron: > LANG=en_US.utf8 > SHELL=/bin/bash > SourcePackage: cups > dmi.bios.date: 09/08/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A11 > dmi.board.name: 0Y279R > dmi.board.vendor: Dell Inc. > dmi.board.version: A11 > dmi.chassis.asset.tag: 1234567890 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A11 > dmi.modalias: > dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: > dmi.product.name: Studio XPS 1340 > dmi.product.version: A11 > dmi.sys.vendor: Dell Inc. > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/554172/+subscribe > -- CUPS and other system services not starting at boot https://bugs.launchpad.net/bugs/554172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 554172] Re: CUPS and other system services not starting at boot
So /dev/console exists but isn't immediately "ready for work". It appears it becomes fully functional later (otherwise it would not be possible to start the failing services manually). Can we figure out at what point /dev/console becomes functional? In the meantime two workarounds seem doable, both assuming /dev/console doesn't depend on anything started during boot: 1. A boot script that doesn't complete until /dev/console works, make rc/rc-sysinit boot sequence depend on it. 2. A patch in upstart that waits until /dev/console works. Any thoughts? Wout On Mon, Jun 28, 2010 at 18:43, Scott James Remnant wrote: > My understanding of this bug is that System V services fail to start > because the rc-sysinit or rc jobs fail because /dev/console cannot be > opened. A workaround appears to be to comment out "console output" from > those jobs. > > I also understand that in all cases, /dev/console actually exists -- > it's a fundamental node that always exists in the devtmpfs filesystem, > and is created by the initramfs for a tmpfs-on-/dev filesystem. In the > case where neither of these is used, the node must exist on the root > filesystem and is created as part of the installer process. > > And since it exists, but returns an error when it's being opened, this > strongly implies some kind of kernel bug. > > -- > CUPS and other system services not starting at boot > https://bugs.launchpad.net/bugs/554172 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in “upstart” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: cups > > Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups > start to after booting to print. > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: cups 1.4.2-10 > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > NonfreeKernelModules: nvidia > Architecture: i386 > Date: Fri Apr 2 13:07:35 2010 > InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) > Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: > Connection refused > MachineType: Dell Inc. Studio XPS 1340 > Papersize: letter > PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono > (recommended) > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic > root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash > ProcEnviron: > LANG=en_US.utf8 > SHELL=/bin/bash > SourcePackage: cups > dmi.bios.date: 09/08/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A11 > dmi.board.name: 0Y279R > dmi.board.vendor: Dell Inc. > dmi.board.version: A11 > dmi.chassis.asset.tag: 1234567890 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A11 > dmi.modalias: > dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: > dmi.product.name: Studio XPS 1340 > dmi.product.version: A11 > dmi.sys.vendor: Dell Inc. > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/554172/+subscribe > -- CUPS and other system services not starting at boot https://bugs.launchpad.net/bugs/554172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Upstart not starting jobs on boot
A long way back in this thread it was reported that the below message would appear in /var/log/messages when upstart had problems running /etc/rc.sysinit. Is anyone still seeing this? init: Failed to spawn rc-sysinit main process: unable to open console: Input/output error Wout On Mon, May 17, 2010 at 09:57, Pascal W. wrote: > I'm also experiencing this problem on a fresh 10.04 desktop > installation. > > Quite often non of my installed services (dropbear ssh, tightvncserver > and sabnzbd) are started. This is very annoying to me because my Ubuntu > box is running headless. > > -- > Upstart not starting jobs on boot > https://bugs.launchpad.net/bugs/543506 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “upstart” package in Ubuntu: New > > Bug description: > Binary package hint: upstart > > On Lucid with: > > # apt-cache policy upstart > upstart: > Installed: 0.6.5-4 > Candidate: 0.6.5-4 > Version table: > *** 0.6.5-4 0 >500 http://apt.interlinx.bc.ca lucid/main Packages >100 /var/lib/dpkg/status > > during boot, upstart just seems to stop starting jobs. A number of jobs > are started but all of the jobs that should be started never gets complete. > I end up (though having a job that starts a shell on a tty) having to > manually: > > # service ssh start > # service rc-sysinit start > (at least) > > to get the system up into a semblance of a multi-user run-level. > > I'd be happy to provide more information but I'm at a bit of a loss as to > how to debug this situation. > > FWIW, my "debug shell" job which gives me a shell that I can debug upstart > from is: > > description "Start a debug shell" > > start on startup > > expect fork > > script >exec /root/open -c 12 /bin/bash > end script > > I have no doubt it's probably not 100% correct as I'm really only just > cribbing it up from what I can see in other jobs. Hopefully I have not > exacerbated the problem with that job. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/+subscribe > -- Upstart not starting jobs on boot https://bugs.launchpad.net/bugs/543506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Upstart not starting jobs on boot
Thanks for the message! I have the same spawn rc message in my logs. I see that in /etc/init/rc.conf it mentions 'console output' which makes upstart try to open the console. That fails. Probably a race condition. Possibly /dev/console is not yet available when upstart wants to start rc? I see you have a ticket open for this so no need for me to add anything (a relief seeing how hostile Ubuntu appears to be to bug reporting). Kind regards, Wout On Sun, Apr 25, 2010 at 19:29, David wrote: > I've encountered the same problem with Mythbuntu 10.04 with all updates > installed. I recognized it because lirc sometimes started and sometimes not. > After some investigation I saw the following line in my syslog: > init: Failed to spawn rc main process: unable to open console: Input/output > error > > apt-cache policy upstart > upstart: > Installiert: 0.6.5-6 > Kandidat: 0.6.5-6 > Versions-Tabelle: > *** 0.6.5-6 0 >500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages > 100 /var/lib/dpkg/status > > -- > Upstart not starting jobs on boot > https://bugs.launchpad.net/bugs/543506 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “upstart” package in Ubuntu: New > > Bug description: > Binary package hint: upstart > > On Lucid with: > > # apt-cache policy upstart > upstart: > Installed: 0.6.5-4 > Candidate: 0.6.5-4 > Version table: > *** 0.6.5-4 0 >500 http://apt.interlinx.bc.ca lucid/main Packages >100 /var/lib/dpkg/status > > during boot, upstart just seems to stop starting jobs. A number of jobs > are started but all of the jobs that should be started never gets complete. > I end up (though having a job that starts a shell on a tty) having to > manually: > > # service ssh start > # service rc-sysinit start > (at least) > > to get the system up into a semblance of a multi-user run-level. > > I'd be happy to provide more information but I'm at a bit of a loss as to > how to debug this situation. > > FWIW, my "debug shell" job which gives me a shell that I can debug upstart > from is: > > description "Start a debug shell" > > start on startup > > expect fork > > script >exec /root/open -c 12 /bin/bash > end script > > I have no doubt it's probably not 100% correct as I'm really only just > cribbing it up from what I can see in other jobs. Hopefully I have not > exacerbated the problem with that job. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/+subscribe > -- Upstart not starting jobs on boot https://bugs.launchpad.net/bugs/543506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Upstart not starting jobs on boot
This is on 10.04 with all available updates installed. Running non standard kernel (2.6.33-020633-generic) for hardware support. ** Changed in: upstart (Ubuntu) Status: Invalid => New -- Upstart not starting jobs on boot https://bugs.launchpad.net/bugs/543506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Upstart not starting jobs on boot
Boot scripts under /etc/rc2.d seem to be run sometimes and other times not. I found this problem as /etc/rc2.d/S99rc.local was not executed. To verify I added a logger statement (logger "Running rc.local") as the first command in rc.local some weeks ago (I should have filed this bug earlier but applications like apport and launchpad make this a very frustrating experience). Checking /var/log/syslog I find the log entry from rc.local for some boots but not for others. It is not only rc.local that is not executed. The /etc/rc2.d /S20virtualbox-ose script is also not always run. This becomes blatantly obvious as VirtualBox can't run VMs in those cases and I have to run the virtualbox-ose script manually. These cases seem to coincide (so both virtualbox-ose and rc.local are either both run or both not run). This morning rc.local and virtualbox-ose were not run. I ran virtualbox-ose manually later. This is the output of 'initctl list' after about 5 hours of uptime: alsa-mixer-save stop/waiting avahi-daemon start/running, process 3403 mountall-net stop/waiting rc stop/waiting rpc_pipefs stop/waiting rsyslog start/running, process 3286 tty4 start/running, process 3506 udev start/running, process 2903 upstart-udev-bridge start/running, process 2883 ureadahead-other stop/waiting apport stop/waiting console-setup stop/waiting hwclock-save stop/waiting irqbalance stop/waiting plymouth-log stop/waiting tty5 start/running, process 3509 statd start/running, process 3454 atd start/running, process 3526 dbus start/running, process 3375 failsafe-x stop/waiting plymouth stop/waiting portmap start/running, process 3415 ssh start/running, process 3313 control-alt-delete stop/waiting hwclock stop/waiting network-manager start/running, process 3453 module-init-tools stop/waiting bridge-network-interface (vboxnet0) start/running bridge-network-interface (lo) start/running bridge-network-interface (eth0) start/running bridge-network-interface (wlan0) start/running cron start/running, process 3527 gdm start/running, process 3579 mountall stop/waiting acpid start/running, process 3522 plymouth-stop start/running rcS stop/waiting ufw start/running mounted-varrun stop/waiting rc-sysinit stop/waiting anacron stop/waiting tty2 start/running, process 3515 udevtrigger stop/waiting mounted-dev stop/waiting tty3 start/running, process 3516 udev-finish stop/waiting hostname stop/waiting mountall-reboot stop/waiting gssd stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting network-interface (vboxnet0) start/running network-interface (lo) start/running network-interface (eth0) start/running network-interface (wlan0) start/running plymouth-splash stop/waiting tty1 start/running, process 3920 udevmonitor stop/waiting dmesg stop/waiting network-interface-security start/running networking stop/waiting procps stop/waiting tty6 start/running, process 3518 idmapd stop/waiting ureadahead stop/waiting Let me know if you need more info. -- Upstart not starting jobs on boot https://bugs.launchpad.net/bugs/543506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258771] Re: Using -usbdevice host: slows the guest OS down to a crawl
Thanks Matt, will do. -- Using -usbdevice host: slows the guest OS down to a crawl https://bugs.launchpad.net/bugs/258771 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258771] Re: Using -usbdevice host: slows the guest OS down to a crawl
I tried connecting several different devices to my Microsoft Windows 7 Virtual Machine. non of them working. Among them: - USB Mass storage device *When inserting the device in my laptop it doesn't show up in nautilus on the host when added to a vm. (Something is going right). It doesn't show up in the guest os' Windows Explorer. (somethings not going right) - HTC winmo phone * Nothing happens at all. I've enabled USB access in apparmor.: /etc/apparmor.d/abstractions/libvirt-qemu # WARNING: uncommenting these gives the guest direct access to host hardware. # This is required for USB pass through but is a security risk. You have been # warned. /sys/bus/usb/devices/ r, /sys/devices/*/*/usb[0-9]*/** r, /dev/bus/usb/*/[0-9]* rw, qemu-kvm - QEMU PC emulator version 0.12.3 "uname -a": Linux laptop-24 2.6.32-17-generic #26-Ubuntu SMP Sat Mar 20 02:23:45 UTC 2010 x86_64 GNU/Linux libvirtd --version: libvirtd (libvirt) 0.7.5 virt-manager: version 0.8.2 I am available for testing new packages -- Using -usbdevice host: slows the guest OS down to a crawl https://bugs.launchpad.net/bugs/258771 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279778] Re: Intrepid Live CD - Partition Fail - Resize operation failure
I resized in vista and then did install on the empy space , this worked for me -- Intrepid Live CD - Partition Fail - Resize operation failure https://bugs.launchpad.net/bugs/279778 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286303] Re: Intrepid: ASUS X53Sa Realtek ALC660-VD low volume
easy fix that worked to fix my low sound / volume level in intrepid was. pulseaudio - k (kill the pulse audio server) alsamixer , now it shows all controls instead of just the master fix the volume restart -- Intrepid: ASUS X53Sa Realtek ALC660-VD low volume https://bugs.launchpad.net/bugs/286303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279778] Re: Intrepid Live CD - Partition Fail - Resize operation failure
I have a Dell M1330 , with a standard (dell) Vista home premium on it. I tried installing ubuntu 8.10 64bit and got stuk in exactly the same spot (resizing 0%) . On rebooting , my vista had to do a chkdsk. If I tried installing after the error occured without starting vista and running chkdsk. No partitions were detected anymore. My wife has the same laptop , only I installed HArdy on that one a few months ago without any problems. Should I go with a fresh Hardy install and then imediatly upgrade it ? -- Intrepid Live CD - Partition Fail - Resize operation failure https://bugs.launchpad.net/bugs/279778 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
