[Bug 1066351] UdevLog.txt

apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1066351/+attachment/3401494/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066351 Title:

[Bug 1066351] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1066351/+attachment/3401495/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066351 Ti

[Bug 1066351] ProcEnviron.txt

apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1066351/+attachment/3401488/+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/1066351

[Bug 1066351] Re: upstart ftbfs in quantal on arm*

@Brad - logs attached, but note that this problem is not unique to my system as it can be seen on i386 and ARM systems. It also potentially affects all precise kernels I believe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://

[Bug 1066252] Re: Black screen on first login after OEM installation

Tried to reproduce with todays desktop image, but problem is now worse: - colord crashes almost immediately - once you click "continue" after entering a unique OEM id, ubiquity hangs forever. /var/log/installer/debug shows the following repeated errors: (ubiquity:3147): Gtk-CRITICAL **: gtk_wi

[Bug 1066351] Re: upstart ftbfs in quantal on arm*

** Changed in: linux (Ubuntu Quantal) 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/1066351 Title: upstart ftbfs in quantal on arm* To manage notifications ab

[Bug 1068170] [NEW] ubiquity generates gtk_widget_get_preferred_width_for_height: assertion `height >= 0' failed errors

Public bug reported: /var/log/installer/debug shows the following repeated errors: (ubiquity:3147): Gtk-CRITICAL **: gtk_widget_get_preferred_width_for_height: assertion `height >= 0' failed (ubiquity:3147): Gtk-CRITICAL **: gtk_widget_get_preferred_width_for_height: assertion `height >= 0' fail

[Bug 1066252] Re: Black screen on first login after OEM installation

Errors I saw in #4 have been logged in bug 1068170. Hang was seemingly caused by a corrupt virtual disk that I was using for testing. I've been through the OEM process and cannot recreate this issue with todays desktop image. -- You received this bug notification because you are a member of Ubu

[Bug 1056410] Re: resizing exiting drive partitions on ARM Quantal does not work

The attached syslog shows a kernel oops that looks relevant: Sep 25 19:10:05 ubuntu kernel: [ 530.711700] [ cut here ] Sep 25 19:10:05 ubuntu kernel: [ 530.711761] WARNING: at /build/buildd/linux-ti-omap4-3.5.0/block/genhd.c:1589 disk_clear_events+0xd4/0x108() Sep 25 1

[Bug 1066351] Re: upstart ftbfs in quantal on arm*

Hi Matthias - this is the issue we have seen before where a rebuild will probably work. However, I'll see if I can identify what is going on here... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/106635

[Bug 1066144] Re: arguments to dbus_server_disconnect() were incorrect

I don't believe this is an Upstart issue: The current version of Upstart does have code to call dbus_server_disconnect(), but this code is never actually run (since Upstart never "shuts down" itself). Additionally, if it were an Upstart issue, according to that log, the assertion would have failed

[Bug 1069624] Re: System failed to detect GPU.

Not an Upstart issue. ** Package changed: upstart (Ubuntu) => fglrx-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069624 Title: System failed to detect GPU. To manage notificat

[Bug 1069481] Re: external usb TOSHIBA disk could not be mounted

Not an upstart issue. Sounds like it might be a non-privileged mounting problem. ** Package changed: upstart (Ubuntu) => gvfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069481 Title: e

[Bug 888910] Re: "make check" fails in sbuild chroot

This bug has now been fixed but is not yet available in a release. *Please* do not disable the Upstart tests as they provide valuable assurance that the resulting binary will work as expected on the target system. Instead, use pbuilder(8) until this fix is available in a release. ** Changed in:

[Bug 1069897] [NEW] gdb crashes on startup if run as root via sudo and ~/.gdbinit exists

Public bug reported: If a program is run like this: $ sudo gdb ./a.out and ~/.gdbinit exists (even as an empty file), gdb will crash... $ cat crash_gdb.c #include #include #include int main(int argc, char *argv[]) { printf ("hello\n"); exit (EXIT_SUCCESS); } $ gcc -g crash_g

[Bug 997359] Re: nih uses eglibc private symbol __abort_msg

Responding to my own comment #2, I don't see why we can't change NIH to create its own '__nih_abort_msg' symbol as long as apport can be tweaked to also look for this symbol. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs

[Bug 613231] Re: Option to quiet /lib/init/upstart-jobs [RFE,PATCH]

Hi Jouko. I agree with Clint. There are just a couple of points here: - The patch no longer applies cleanly to the Ubuntu upstart package as upstart-job has changed a little. - I'd personally prefer the variables to be called ECHO (rather than ECHO_NOTE) and ECHO_ERROR since its then a smaller c

[Bug 997359] Re: nih uses eglibc private symbol __abort_msg

** Also affects: apport (Ubuntu Raring) Importance: High Status: Confirmed ** Also affects: libnih (Ubuntu Raring) Importance: High Status: Confirmed ** Changed in: libnih (Ubuntu Raring) Assignee: (unassigned) => James Hunt (jamesodhunt) -- You received this

[Bug 997359] Re: nih uses eglibc private symbol __abort_msg

** Changed in: libnih (Ubuntu Raring) Status: Confirmed => 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/997359 Title: nih uses eglibc private symbol __abort_msg To manage notif

[Bug 997359] Re: nih uses eglibc private symbol __abort_msg

NIH in Ubuntu (not yet upstream) now uses __nih_abort_msg such that apport will be able to do: (gdb) print (char *)__nih_abort_msg ... to retrieve the abort message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.la

[Bug 1072759] [NEW] sendsigs should only ignore upstart job with specify 'stop on' explicitly

Public bug reported: /etc/init.d/sendsigs currently ignores all upstart jobs, assuming Upstart will stop all associated job processes. However, this is only true if those jobs explicitly specify a 'stop on' condition, otherwise they will persist. /etc/init.d/sendsigs should be modified to only i

[Bug 1073089] [NEW] ubuntu kernel does not support gadgetfs

Public bug reported: The Ubuntu kernel does not appear to support gadgetfs: $ sudo modprobe g_mass_storage file=/tmp/fake_usb_disk FATAL: Error inserting g_mass_storage (/lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko): No such device $ ll /lib/modules/3.5.0-17-generic

[Bug 1073089] Re: ubuntu kernel does not support gadgetfs

Hi Joseph - no I don't have that package installed. ** Tags added: apport-collected running-unity ** Description changed: The Ubuntu kernel does not appear to support gadgetfs: $ sudo modprobe g_mass_storage file=/tmp/fake_usb_disk FATAL: Error inserting g_mass_storage (/lib/modules/3.

[Bug 1073089] AlsaInfo.txt

apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418630/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title:

[Bug 1073089] BootDmesg.txt

apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418631/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Titl

[Bug 1073089] CRDA.txt

apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418632/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title: ubuntu

[Bug 1073089] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418633/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089

[Bug 1073089] Dependencies.txt

apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418634/+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/1073089

[Bug 1073089] IwConfig.txt

apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418635/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title:

[Bug 1073089] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418636/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title: ubun

[Bug 1073089] Lsusb.txt

apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418637/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title: ubun

[Bug 1073089] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418638/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089

[Bug 1073089] ProcEnviron.txt

apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418639/+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/1073089

[Bug 1073089] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418640/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/107

[Bug 1073089] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418641/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089

[Bug 1073089] PulseList.txt

apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418642/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Titl

[Bug 1073089] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418644/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title: ub

[Bug 1073089] UdevLog.txt

apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418645/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title:

[Bug 1073089] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418646/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Ti

[Bug 1073089] RfKill.txt

apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1073089/+attachment/3418643/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073089 Title: ub

[Bug 1055551] [NEW] zsh can causes ps to generate error message

Public bug reported: (ps|grep foo;echo) Signal 18 (CONT) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report this bug (ps;echo) # works (ps|grep foo) # works (ps|grep foo;echo) # fails This behaviour seems to be caused by zsh since it is not observable using bash. Note too t

[Bug 1055551] Re: zsh can causes ps to generate error message

-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/101 Title: zsh can causes ps to generate error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+

[Bug 1059783] [NEW] random output when size_to_str() passed values larger than 10^28

Public bug reported: # correct output ("1 Y" or 10k yottabytes) $ python2.7 -c 'import apt_pkg; print(apt_pkg.size_to_str(10 ** 28))' |od -xc 0003031303020300a59 1 0 0 0 0 Y \n 010 # incorrect output: random output! $ python2.7 -c 'import apt_p

[Bug 1030278] Re: Quantal failed to install: ubiquity crashed in apt/progress/text.py in pulse: OverflowError: Python int too large to convert to C long

Hi Barry, Thanks for this - we seem to have collided slightly on this one! :) Now that we've got a fix in quantal, I've undone my changes, but have raised an MP for additional checks and a formal test for size_to_str(). See: lp:~jamesodhunt/python-apt/test-for-size_to_str You're right about the

[Bug 1016040] Re: apt_check.py crashed with SIGSEGV in FileName()

** Changed in: apt (Ubuntu Quantal) Assignee: (unassigned) => James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016040 Title: apt_check.py crashed with SIGSEGV

[Bug 1047837] Re: Upstart support for Zabbix services

Christian - sym links are not supported. See init(5) and http://upstart.ubuntu.com/cookbook/#symbolic-links-don-t-work-in-etc- init. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047837 Title: Upst

[Bug 1016040] Re: apt_check.py crashed with SIGSEGV in FileName()

I have not yet been able to reproduce this, but the stack trace is suggestive of either memory corruption or a pointer walking beyond the end of a list. Consider a few choice entries from the 'stat' buffer shown in debPackagesIndex::FindInCache in the stacktrace: st_nlink = 0 (impossible) st_blks

[Bug 1060249] Re: frontend crashed with signal 5 in g_node_copy_deep()

** Changed in: debconf (Ubuntu Quantal) Assignee: (unassigned) => James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060249 Title: frontend crashed with signal 5

[Bug 740390] Re: libdbus-1-3 upgrade does not respawn init, resulting in unclean shutdown

** Changed in: libnih (Ubuntu Quantal) Assignee: (unassigned) => James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740390 Title: libdbus-1-3 upgrade does not respawn i

[Bug 995036] Re: package libnih1 1.0.3-4ubuntu9 failed to install/upgrade: pre-dependency problem - not installing libnih1

*** This bug is a duplicate of bug 936109 *** https://bugs.launchpad.net/bugs/936109 ** This bug has been marked a duplicate of bug 936109 package libnih1 1.0.3-4ubuntu5 failed to install/upgrade: ErrorMessage: pre-dependency problem - not installing libnih1 -- You received this bug noti

[Bug 1061639] [NEW] Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects

Public bug reported: In precise, /etc/init.d/networking was a true SysV service script that did the following: initctl emit deconfiguring-networking In quantal, /etc/init.d/networking is now using the upstart-job symlink back to the upstart job /etc/init/networking.conf. The problem is that the

[Bug 740390] Re: libdbus-1-3 upgrade does not respawn init, resulting in unclean shutdown

@dino99: Thanks for spotting this - I too saw this in testing. I've isolated the problem - see bug 1061639. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740390 Title: libdbus-1-3 upgrade does not r

[Bug 50093] Re: Some sysctl's are ignored on boot

*** This bug is a duplicate of bug 771372 *** https://bugs.launchpad.net/bugs/771372 ** This bug has been marked a duplicate of bug 771372 procps runs too early in the boot process -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 1062202] [NEW] [SRU] libnih upgrade does not respawn init, resulting in unclean shutdown

Public bug reported: If required package libnih1 (or libnih-dbus1) are upgraded, Upstart needs to be restarted to avoid it holding open "stale" file descriptors to files in the old versions of the packages. This results in the following issues: - the shutdown sequence displays error messages. - t

[Bug 1062202] Re: [SRU] libnih upgrade does not respawn init, resulting in unclean shutdown

** Attachment added: "Diff of /etc/init.d/umountroot" https://bugs.launchpad.net/bugs/1062202/+attachment/3375437/+files/etc-init.d-umountroot.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/106

[Bug 740390] Re: libdbus-1-3 upgrade does not respawn init, resulting in unclean shutdown

I've created bug 1062202 to handle the lbnih SRU for precise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740390 Title: libdbus-1-3 upgrade does not respawn init, resulting in unclean shutdown

[Bug 1062202] Re: [SRU] libnih upgrade does not respawn init, resulting in unclean shutdown

** Changed in: libnih (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) ** Changed in: libnih (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne

[Bug 1062202] Re: [SRU] libnih upgrade does not respawn init, resulting in unclean shutdown

** Also affects: libnih (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: libnih (Ubuntu Precise) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/

[Bug 1049664] Re: libreoffice crashes on --help

I have the same problem. After installing the dbg packages... $ gdb --args /usr/lib/libreoffice/program/soffice.bin --help GNU gdb (GDB) 7.5-ubuntu Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software

[Bug 1062378] [NEW] libreoffice crashes with SIGSEGV opening some .docx files

Public bug reported: I have the dbg packages installed. See attached gdb transcript for backtrace for all threads. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 NonfreeKer

[Bug 1062378] Re: libreoffice crashes with SIGSEGV opening some .docx files

** Attachment added: "gdb-transcript.log" https://bugs.launchpad.net/bugs/1062378/+attachment/3376376/+files/gdb-transcript.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062378 Title: libre

[Bug 1063587] [NEW] autohide stops launcher from re-appearing

Public bug reported: If autohide is selected, the launcher can never be re-displayed by putting the mouse into the "reveal" area - I've tried "restore default behaviour", changing the reveal location and sensitivity to no avail. However, as soon as I disable autohide, the launcher re-appears and w

[Bug 1063587] Re: autohide stops launcher from re-appearing

** Description changed: - If autohide is selected, the launcher can never be re-displayed - I've - tried "restore default behaviour", changing the reveal location and - sensitivity to no avail. However, as soon as I disable autohide, the - launcher re-appears and works as expected. + If autohide i

[Bug 1063587] Re: autohide stops launcher from re-appearing

Hmm. After rebooting, the problem has gone away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063587 Title: autohide stops launcher from re-appearing To manage notifications about this bug go to:

[Bug 1056927] Re: 'started libvirt-bin' event occurs before libvirt networks available

The simplest idiom here is to use a 'post-start' to allow you to perform some libvirt check on its bridges: only once the post-start has completed is the 'started JOB=libvirt-bin' event emitted. ** Changed in: libvirt (Ubuntu) Assignee: James Hunt (jamesodhunt) =>

[Bug 1005766] Re: System boot hangs

** Also affects: mdadm (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/1005766 Title: System boot hangs To manage notifications about this bug go

[Bug 946663] Re: Installer stuck at "Removing conflicting operating system files..."

Unfortunately, we were not able to resolve this issue in time for the release. Even when simulating some of the disk layouts attached, I don't see the problem. However, to help us track down the cause it would be extremely useful if someone would list the *exact* steps they take to see this probl

[Bug 990102] Re: /var/log/upstart is missing

This issue might be caused by a cron job that is clearing out /var/log/? Or some logrotate configuration issue possibly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990102 Title: /var/log/upstart

[Bug 806761] Re: Feature Request: Upstart scripts for nslcd

Hi Caleb, Thanks for keeping the momentum going on this. I notice though that you are still using $K5START_LOGFILE which really isn't required now. Have you maybe attached an older version of the patch in #13 by mistake? Regarding your comment about good and bad interfaces, the Upstart 'instanc

[Bug 1021681] Re: Mounting ro while fsck on boot

Hi Eric - thanks for reporting this issue. However, something seems amiss on your system since the system should wait until fsck finishes. Please can you attach the file /var/log/boot.log from such a boot as it might give an indication as to what is going wrong. It sounds like either your disk is

[Bug 1043387] Re: Computer fails to shutdown properly nor can it restart

Thanks for confirming this Lars. I'm re-assigning this issue to the kernel team. ** Package changed: upstart (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043387 Title:

[Bug 1033336] Re: user jobs do not work

Hi Tv, Thanks for reporting. User Jobs do work, but as you have established, they are disabled by default. It is up to the administrator to enable them iff they want this feature to be available. User Job support is currently quite basic, but we have plans to enhance the feature significantly for

[Bug 1033985] [NEW] unable to install quantal on system running precise with LVMs

Public bug reported: Attempting to install quantal on a system running precise (installed from alternate CD) with LVMs results in ubiquity looping and never allowing the install to proceed: - On "Installation type" screen, select "erase Ubuntu 12.04 LTS and reinstall" - click "Install Now" - On "

[Bug 1033985] Re: unable to install quantal on system running precise with LVMs

** Attachment added: "fdisk-l.log" https://bugs.launchpad.net/bugs/1033985/+attachment/3251303/+files/fdisk-l.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033985 Title: unable to install q

[Bug 1033985] Re: unable to install quantal on system running precise with LVMs

** Attachment added: "lvdisplay.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1033985/+attachment/3251304/+files/lvdisplay.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033985

[Bug 1033985] Re: unable to install quantal on system running precise with LVMs

** Attachment added: "mount.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1033985/+attachment/3251305/+files/mount.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033985 Title:

[Bug 1033985] Re: unable to install quantal on system running precise with LVMs

** Attachment added: "pvdisplay.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1033985/+attachment/3251306/+files/pvdisplay.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033985

[Bug 1033985] Re: unable to install quantal on system running precise with LVMs

** Attachment added: "vgdisplay.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1033985/+attachment/3251307/+files/vgdisplay.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033985

[Bug 1033985] Re: unable to install quantal on system running precise with LVMs

Selecting "Something else" also gives unexpected behaviour since although it shows the VGs, nothing appears to be deletable via this screen, and each VG is shown twice with the 2nd entry indented, like this: /dev/mapper/myhost-root /dev/mapper/myhost-root /dev/mapper/myhost-swap_1 /dev/map

[Bug 980917] Re: Failed to create pty - disabling logging for job

** Description changed: + [PROBLEM] + + This bug causes Upstart to display 1 error message / job that is started + that should have its output logged (by default ''all'' jobs are thus + affected) if it is unable to create a pseudoterminal device, which is + required for Upstart job logging. + +

[Bug 1034776] Re: /sbin/start hung in __GI___poll

This is not an upstart bug, but a configuration issue: your oident.conf is invalid since: 1) OIDENT_OPTIONS is guaranteed to always be unset since you cannot source options in a pre-start and have them apply to the script stanza since each stanza is run as a separate process. 2) Since OIDENT_OPTI

[Bug 750141] Re: /etc/init.d/sendsigs should stop Upstart jobs with no stop on condition

** Description changed: Binary package hint: sysvinit - If an Upstart job has no stop on condition, Upstart won't stop any - instances of it. However, if a job has no stop on, but *does* specify - respawn we have a potential problem at shutdown since: + If an Upstart job has no 'stop on' cond

[Bug 1043395] [NEW] multiple readers of /proc/kmsg results in garbage being returned.

Public bug reported: = PROBLEM = It seems that having multiple processes read from /proc/kmsg results in corrupted data being returned. This can be demonstrated using a couple of chunks of shell run as root: # consumers for i in `seq 10`; do cat /proc/kmsg > /tmp/$i.log & done # producers for i

[Bug 1043395] Re: multiple reads of /proc/kmsg results in garbage being returned.

** Summary changed: - multiple reads of /proc/kmsg results in garbage being returned. + multiple readers of /proc/kmsg results in garbage being returned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/

[Bug 1043395] Re: multiple readers of /proc/kmsg results in garbage being returned.

After chatting to apw, this seems to be "working as designed". Excerpt from proc(5): "/proc/kmsg ... only one process should read this file." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043395 T

[Bug 1043395] Re: multiple readers of /proc/kmsg results in garbage being returned.

** Changed in: linux (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043395 Title: multiple readers of /proc/kmsg results in garbage being returned. To m

[Bug 1043387] Re: Computer fails to shutdown properly nor can it restart

Thanks for reporting this bug. Can you confirm that you computer simply fails to power-off at the end of the shutdown sequence? If so, this sounds either like a kernel bug, or a problem with your particular hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, w

[Bug 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%

** Changed in: upstart Status: Fix Committed => 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/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To man

[Bug 1047837] Re: Upstart support

These Upstart job configuration files look very good. Just a couple of points: - are the following files required? Do they apply where no default database has been configured? Or are they an oversight? zabbix-proxy-.upstart zabbix-server-.upstart - Since all the .upstart files share the same

[Bug 1011986] Re: After logout Xorg stays stuck in tty_ld

Can you confirm if mountall and/or mount.cifs are running when the system is in this state? It does appear that mount.cifs is still attempting to read the CIFS passwords directly from /dev/tty7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1011986] Re: After logout Xorg stays stuck in tty_ld

Hi Gema, The problem then is that mountall is left prompting but meantime X has started on the same tty. I don't see how mountall could be changed to deal with this scenario automatically though since the only way to signify that a particular CIFS mount requires a password is via the options speci

[Bug 1016170] Re: No login screen unless "quiet splash" removed from boot line

Hi Barry - when it hangs, does pressing Escape show anything? Also, I've updated the Plymouth wiki page so it would be interesting to know if Plymouth is runnable via the initramfs and the live system: https://wiki.ubuntu.com/Plymouth#Checking_Plymouth_Can_Run_in_the_Initramfs https://wiki.ubuntu.

[Bug 1016170] Re: No login screen unless "quiet splash" removed from boot line

Might also be useful to get a plymouth debug log (along with syslog, etc) even with "quiet splash" removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016170 Title: No login screen unless "quiet

[Bug 1018554] Re: write timestamp to console on halt/reboot/shutdown

Hi Scott, This doesn't require a change to Upstart - just create a job called "log-reboot" or similar containing something like this: - start on runlevel PREVLEVEL=2 task exec echo "rebooting `date`" > /dev/console - --

[Bug 1026681] Re: shutdown causes a reboot

Thank you for reporting this issue. It actually sounds like a kernel problem relating to your specific hardware as opposed to an issue with Upstart. Re-assigning to the Linux kernel. ** Package changed: upstart (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a me

[Bug 1025578] [NEW] espeak sound output very slow if bluez-alsa installed

Public bug reported: Running espeak if bluetooth is enabled via the panel applet and bluez- alsa is installed slows down espeak sound output *significantly*... With bluetooth disabled... $ time echo hello|espeak ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm.c:221

[Bug 1025578] Re: espeak sound output very slow if bluez-alsa installed

** Attachment added: "hci.log" https://bugs.launchpad.net/bugs/1025578/+attachment/3225849/+files/hci.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025578 Title: espeak sound output very slo

[Bug 1025578] Re: espeak sound output very slow if bluez-alsa installed

To be clear, when I say "slows down", what I actually mean is that with bluez-alsa installed and bluetooth enabled, running espeak results in a ~20 second delay, followed by espeak working correctly and playing sound at the correct pitch: speed of sound playback is not affected. -- You received t

[Bug 970638] Re: killall can't kill processes with names >15 bytes (Ubuntu 12.04)

** Summary changed: - killall can't kill processes with fairly long names (Ubuntu 12.04) + killall can't kill processes with names >15 bytes (Ubuntu 12.04) ** Summary changed: - killall can't kill processes with names >15 bytes (Ubuntu 12.04) + killall can't kill processes with names >15 bytes l

[Bug 1021164] [NEW] unity crashes disable auto-hide and cause 'Behaviour' tab to disappear from system settings -> Appearance

Public bug reported: If unity crashes, and I opt to restart it from the pop-up window, I observe the following issues: 1) Autohide is disabled. I always have autohide enabled, but this option appears to be reset on a crash. 2) 'Behaviour' tab no longer exists under System Settings -> Appearance

<    8   9   10   11   12   13   14   15   16   17   >