[Bug 245855] [NEW] Hardy Installer: 'Attempt to mount a file system with type swap...' fails
Public bug reported: Binary package hint: ubiquity Using the Hardy desktop live CD installer (x86) results in the message: "The attempt to mount a file system with type swap in LVM VG raid1, LV swap at none failed" Surely it shouldn't try to mount a swap partition? The system is configured with four 61GB PATA disks (sda, sdb, sdc, sdd). Each is configured identically from a terminal in the Live CD environment: /dev/sdX1 3,256MB, Linux raid autodetect (fd) /dev/sdX2, remainder, Linux raid autodetect (fd) mdadm is used to create two arrays: /dev/md0, RAID-1, sda1, sdb1 sdc1, sdd1 /dev/md1, RAID-5, sda2, sdb2, sdc2, sdd2 cryptsetup is used to encrypt /dev/md1 to /dev/mapper/encrypted01 LVM is used to create two physical volumes and volume groups: VG raid1 on /dev/md0 VG raid5 on /dev/mapper/encrypted01 LVM is used to create five logical volumes: /dev/mapper/raid1-boot on /dev/raid1/boot in VG raid1, size 256MB /dev/mapper/raid1-swap on /dev/raid1/swap in VG raid1, size 3GB /dev/mapper/raid5-root on /dev/raid5/root in VG raid5, size 18GB /dev/mapper/raid5-var on /dev/raid5/var in VG raid5, size 10GB /dev/mapper/raid5-home on /dev/raid5/home in VG raid5, size 110GB 33GB in VG raid5 is unallocated. Using Manual partitioning each logical volume is partitioned with a single primary partition and the appropriate file-system and mount-point is set. When the installer beings formatting the disks, it stops with the message above and then returns to the partitioning menu of the installer. I thought this might be related to bug #126328 "swap volume fails to mount" but that is marked as Fix Released. The issue may be caused by partman but it occurs in the context of the installer, thus I've assigned it to ubiquity until it has been triaged (Colin Watson probably knows this issue best). It could also be related to bug #44609 " RAID not implemented (use alternate CD instead)" ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- Hardy Installer: 'Attempt to mount a file system with type swap...' fails https://bugs.launchpad.net/bugs/245855 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 44609] Re: RAID not implemented (use alternate CD instead)
This also/still affects Hardy, but there is a work-around. First, once the Live CD has started, open a terminal and run: sudo su sed -i 's,^\( *grep -v '^/dev/md' |\),#\1,' /lib/partman/init.d/30parted | grep '/dev/md' This will allow Ubiquity's partman to report /dev/md* devices by commenting out the script statement that ignores them. Next, manually install a file-system to the md device. E.g: sudo mkfs.ext3 -L boot /dev/md0 Now when Ubiquity's partman runs in manual mode you'll see something like this in the partition list: /dev/md0 /dev/md0 ext3 256 MB 14 MB Select the indented /dev/md0, press the "Edit partition" button, set the file-system type to ext3, tick the Format check-box, and set the mount- point. Ubiquity/partman will now successfully format and install to /dev/md0 when the install is started. -- RAID not implemented (use alternate CD instead) https://bugs.launchpad.net/bugs/44609 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252262] [NEW] dpkg-source: Ubuntu maintainer check too broad
Public bug reported:
Binary package hint: dpkg
using debuild -S the operation failed with:
dpkg-source: error: Version number suggests Ubuntu changes, but
Maintainer: does not have Ubuntu address
It is caused by the test for an ubuntu.XXX email address in dpkg-source
being too broad:
if ($fields->{'Maintainer'} !~ /ubuntu/) {
if ($ENV{'DEBEMAIL'} =~ /ubuntu/) {
&error(_g('Version number suggests Ubuntu changes, but
Maintainer: does not have Ubuntu address'));
My configured email:
[EMAIL PROTECTED]
The check ought to test for "ubuntu" on the right side of the @ only:
if ($ENV{'DEBEMAIL'} =~ /[EMAIL PROTECTED]/) {
** Affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
--
dpkg-source: Ubuntu maintainer check too broad
https://bugs.launchpad.net/bugs/252262
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 252262] Re: dpkg-source: Ubuntu maintainer check too broad
I am fully aware of the use of the Maintainer field but you miss my point. The key phrase in the wiki article you reference (which I'd already reviewed before posting this bug) is: "If the Maintainer field contains an ubuntu.com email address..." The email address I use to sign packages is [EMAIL PROTECTED] This is not an ubuntu.com address *but* the over-broad test for just "ubuntu" in any part of the email addresses causes this warning when the maintainer is *not* an ubuntu.com email address. I hit the bug whilst creating a PPA bug-fix package of "blueman" which is distributed independently from its author's repository specifically for Ubuntu releases (not Debian) and thus has a 0ubuntuX version (their choice, not mine - it has project space on launchpad so is probably due to migrate there at some point). So, I updated the Maintainer field in debian/control to my own "[EMAIL PROTECTED]" email address and, of course, DEBEMAIL contains the same address. -- dpkg-source: Ubuntu maintainer check too broad https://bugs.launchpad.net/bugs/252262 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 253230] [NEW] Should it Build-Depends on libvdeplug2-dev?
Public bug reported: Binary package hint: kvm qemu, through kvm, has support for VDE2 (Virtual Distributed Ethernet). The debian package includes vde2 in its list of Suggests but the current package has no Build-Depends libvdeplug2-dev. The package is also not built with the configure option --enable-vde (obviously it would currently FTBS if it had this!) As a result the binary package does not have support for VDE and therefore the 'Suggests' vde2 is misleading. ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- Should it Build-Depends on libvdeplug2-dev? https://bugs.launchpad.net/bugs/253230 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 253230] Re: Should it Build-Depends on libvdeplug2-dev?
** Description changed: Binary package hint: kvm qemu, through kvm, has support for VDE2 (Virtual Distributed Ethernet). The debian package includes vde2 in its list of Suggests but the current package has no Build-Depends libvdeplug2-dev. + The package is also not built with the configure option --enable-vde + (obviously it would currently FTBS if it had this!) + As a result the binary package does not have support for VDE and therefore the 'Suggests' vde2 is misleading. -- Should it Build-Depends on libvdeplug2-dev? https://bugs.launchpad.net/bugs/253230 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 12296] Re: PHP5 or PHP4 for apache2-mpm-worker
Colin, I wrote a how-to "Apache 2 with FastCGI, SuExec and PHP" It possibly covers more than you need since it sets suexec up for VirtualMin's web-homes as well as the FastCGI/PHP configuration, but it is a full step-by-step-with-code guide based on my own experience. http://tjworld.net/wiki/Howto/Apache2FastCgiSuexecPhp -- PHP5 or PHP4 for apache2-mpm-worker https://bugs.launchpad.net/bugs/12296 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253588] [NEW] PXE builds not commented out as claimed in changelog
Public bug reported: Binary package hint: kvm debian/changelog claims: - Comment out PXE rom builds (etherboot is not in main at this point). But the relevant section of debian/rules is not commented out. The change was introduced with 1:69+dfsg-1ubuntu1 and looking at the kvm_69+dfsg-1ubuntu1.diff shows the code is commented out. The following release (1:70_dfsg-1ubuntu1) had the same changelog claim but the diff shows debian/rules isn't adjusted. I suspect the changelog message has been copy/pasted but debian/rules not adjusted to match. ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- PXE builds not commented out as claimed in changelog https://bugs.launchpad.net/bugs/253588 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 220871] Re: Creating a new context using the /admin interface does not commit changes.
According to the documentation this is by design, since the tomcat5.5 user does not have the necessary privileges to make the changes: /usr/share/doc/tomcat5.5/README.Debian There is a webapp for basic web-based administration of Tomcat's webapps in the tomcat5.5-admin package. You need to add one of the users in /etc/tomcat5.5/tomcat-users.xml to the manager role and probably set a better password. The "Web Application Manager" can then be accessed at http://localhost:8180/manager/html. There's also a more sophisticated administration webapp called "admin" in the same package but it can't make permanent changes to the configuration since the tomcat5.5 user does not have permission to do this in the default configuration. -- Creating a new context using the /admin interface does not commit changes. https://bugs.launchpad.net/bugs/220871 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 249293] Re: nagios-statd-client should not depend only on nagios
I think on Hardy it is slightly more serious. Unless I've missed something, Nagios v1.x isn't packaged and therefore nagios-statd-client depending in nagios rather than nagios2 effectively orphans the package (assuming the package is okay to use with nagios2, of course). ** Changed in: nagios-statd (Ubuntu) Importance: Undecided => Medium Status: New => Confirmed -- nagios-statd-client should not depend only on nagios https://bugs.launchpad.net/bugs/249293 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 249293] Re: nagios-statd-client should not depend only on nagios
Update on *why* the client depends on nagios, not nagios2. There is no specific Depends on nagios but debhelper deduces it from the path the client is installed to, which is specified in the client's .install file. I examined nagios2-common and the plug-in packages and noticed the paths for plug-ins is different to that being used by the client - I assume that is a difference between nagios v1.x and v2.x. I've altered the .install file and test-built the package and now the Depends on nagios has gone. I've uploaded the test package to my PPA so maybe you'd like to try it out with nagios2? I shall be doing the same -- nagios-statd-client should not depend only on nagios https://bugs.launchpad.net/bugs/249293 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 261026] Re: exim4 install fails with error: incompatible command-line options
This appears to be the Debian bug which has been fixed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477194 ** Changed in: exim4 (Ubuntu) Importance: Undecided => Medium Status: New => Confirmed -- exim4 install fails with error: incompatible command-line options https://bugs.launchpad.net/bugs/261026 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 261026] Re: exim4 install fails with error: incompatible command-line options
A work-around which solved it here is to edit "/etc/init.d/exim4" and
remove the quotes surrounding variables holding optional parameters
passed to start-stop-daemon, since if those variables are empty a pair
of quote-marks will be passed to start-stop-daemon.
After editing the file force apt to fix-up the packages:
sudo apt-get -f install
=== /etc/init.d/exim4 fixed start_exim() function ===
start_exim()
{
[ -e /var/run/exim4 ] || \
install -d -oDebian-exim -gDebian-exim -m750 /var/run/exim4
case ${QUEUERUNNER} in
combined)
start_daemon -p "$PIDFILE" \
"$DAEMON" -bd "-q${QFLAGS}${QUEUEINTERVAL}" \
${COMMONOPTIONS} ${QUEUERUNNEROPTIONS} ${SMTPLISTENEROPTIONS}
log_progress_msg "exim4"
;;
separate)
start_daemon -p "$PIDFILE" \
"$DAEMON" -bd ${SMTPLISTENEROPTIONS} ${COMMONOPTIONS}
log_progress_msg "exim4_listener"
start_daemon -p "$QRPIDFILE" \
"$DAEMON" -oP "$QRPIDFILE" \
"-q${QFLAGS}${QUEUEINTERVAL}" ${QUEUERUNNEROPTIONS} ${COMMONOPTIONS}
log_progress_msg "exim4_queuerunner"
;;
queueonly)
start_daemon -p "$QRPIDFILE" \
"$DAEMON" -oP "$QRPIDFILE" \
"-q${QFLAGS}${QUEUEINTERVAL}" ${QUEUERUNNEROPTIONS} ${COMMONOPTIONS}
log_progress_msg "exim4_queuerunner"
;;
no|ppp)
start_daemon -p "$PIDFILE" \
"$DAEMON" -bd ${SMTPLISTENEROPTIONS}
log_progress_msg "exim4_listener"
;;
nodaemon)
;;
esac
}
--
exim4 install fails with error: incompatible command-line options
https://bugs.launchpad.net/bugs/261026
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 262361] [NEW] Prompts for two Encryption Keys simultaneously
Public bug reported:
Binary package hint: network-manager
Network Manager 0.7 prompts for the encryption key for two APs (Access
Points) simultaneously, Also, there is no AP identifier in the
encryption key request dialog-box so the user has no idea which dialog-
box represents which AP, or even that the two dialog-boxes represent two
different APs (they may not know the physical details of the network).
In this scenario there are two APs operating (WDS) Wireless Distribution
System LAN-mode (AP + clients) on 802.11g. Being WDS, both routers are
on the same channel (in this case, 13) and both have the same BSSID,
which is hidden. AP #1 is also the network gateway.
A roaming laptop is prompted via nm-applet to connect to the network's
entry in the notify-icon's drop-down list. The icon indicates with the
first 'LED' lit it is attempting to connect to the network, and
immediately two dialog-boxes appear, overlapping each other.
Network-manager should serialise this process so that if the first
connection succeeds the second one is never attempted, and therefore no
encryption key is requested. As an enhancement it should indicate there
is more than one AP available.
$ dpkg-query -W -f='${Package} ${Version}\n' 'network-manager*'
network-manager 0.7~~svn20080807t145225+eni0-0ubuntu1~ppa1h
network-manager-gnome 0.7~~svn20080809t093015-0ubuntu1~ppa1h
network-manager-openvpn 0.7~~svn20080807t145225-0ubuntu1~ppa1h
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
Prompts for two Encryption Keys simultaneously
https://bugs.launchpad.net/bugs/262361
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 262361] Re: Prompts for two Encryption Keys simultaneously
** Description changed:
Binary package hint: network-manager
Network Manager 0.7 prompts for the encryption key for two APs (Access
- Points) simultaneously, Also, there is no AP identifier in the
- encryption key request dialog-box so the user has no idea which dialog-
- box represents which AP, or even that the two dialog-boxes represent two
+ Points) simultaneously (I haven't checked if this also affects 0.6 but
+ I'm betting it does). Also, there is no AP identifier in the encryption
+ key request dialog-box so the user has no idea which dialog-box
+ represents which AP, or even that the two dialog-boxes represent two
different APs (they may not know the physical details of the network).
In this scenario there are two APs operating (WDS) Wireless Distribution
System LAN-mode (AP + clients) on 802.11g. Being WDS, both routers are
on the same channel (in this case, 13) and both have the same BSSID,
which is hidden. AP #1 is also the network gateway.
A roaming laptop is prompted via nm-applet to connect to the network's
entry in the notify-icon's drop-down list. The icon indicates with the
first 'LED' lit it is attempting to connect to the network, and
immediately two dialog-boxes appear, overlapping each other.
Network-manager should serialise this process so that if the first
connection succeeds the second one is never attempted, and therefore no
encryption key is requested. As an enhancement it should indicate there
is more than one AP available.
$ dpkg-query -W -f='${Package} ${Version}\n' 'network-manager*'
network-manager 0.7~~svn20080807t145225+eni0-0ubuntu1~ppa1h
network-manager-gnome 0.7~~svn20080809t093015-0ubuntu1~ppa1h
network-manager-openvpn 0.7~~svn20080807t145225-0ubuntu1~ppa1h
--
Prompts for two Encryption Keys simultaneously
https://bugs.launchpad.net/bugs/262361
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 282019] Re: Wrong group ownership on files in /etc
I lost track of where this was originating and forgot to de-assign myself. Doing that now. ** Changed in: ubuntu Assignee: TJ (intuitivenipple) => (unassigned) -- Wrong group ownership on files in /etc https://bugs.launchpad.net/bugs/282019 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 218671] Re: MinY < MaxY leads to unexpected behaviour
I've added alendubri's patched version for Hardy into my PPA: https://edge.launchpad.net/~intuitivenipple/+archive?field.name_filter =xserver-xorg-input-elographics&field.status_filter=published I'm also attaching a debdiff for Hardy (1:1.1.0-3ubuntu1). ** Attachment added: "Hardy debdiff" http://launchpadlibrarian.net/19820891/xserver-xorg-input-elographics_1.1.0-3ubuntu1.debdiff -- MinY < MaxY leads to unexpected behaviour https://bugs.launchpad.net/bugs/218671 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 294339] Re: [intrepid] Live CD not booting on Intel Centrino Laptop with GME chipset - possibly ACPI
Dana, thanks for capturing the boot log - that helps immensely. Having had a look it *seems* as if the cause might be related to decoding one of the ACPI DSDT thermal zone packages. Could you extract and attach the DSDT of that system please? acpidump -b -t DSDT -o /tmp/HP-Elite-8530w.dsdt tar -czf /tmp/HP-Elite-8530w.dsdt.tar.gz -C /tmp/ HP-Elite-8530w.dsdt -- [intrepid] Live CD not booting on Intel Centrino Laptop with GME chipset - possibly ACPI https://bugs.launchpad.net/bugs/294339 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 151146] Re: Kernel Panic - not syncing: VFS after upgrade.
I've just updated an x86 system from Hardy to Intrepid and experienced the same issue. In this case the system has encrypted RAID-5 LVM volumes for /, /var/ and /home/, all opened via a LUKS cryptographic key-file on a USB flash memory device. The GRUB menu has been incorrectly updated and has no "initrd" entry for the Intrepid kernel (this might be reported as a new bug, depending on my findings). Booting the new Intrepid kernel gets stuck with this bug's error. Trying to boot the previous Hardy kernel results in GRUB reporting "Error 15: File not found", even though it has an "initrd" entry that looks (from memory) to be correct. I have to dig some more after booting from a LiveCD to discover the cause. -- Kernel Panic - not syncing: VFS after upgrade. https://bugs.launchpad.net/bugs/151146 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 151146] Re: Kernel Panic - not syncing: VFS after upgrade.
Update. I'm not sure how GRUB came to be missing the "initrd" entry for the Intrepid menu item. As I added it manually I don't feel inclined to try and track down the cause. The failure to load the Hardy kernel appears to be because the upgrade removed all the Hardy kernels but the original -19 *but* left the corresponding GRUb menu entries intact. Therefore, when I selected to boot from Hardy I picked the first item (the -22 kernel) for which the kernel and initrd files had been deleted. Selecting the -19 version allowed the system to start with the Hardy kernel. -- Kernel Panic - not syncing: VFS after upgrade. https://bugs.launchpad.net/bugs/151146 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 290935] Re: dual screen all panels end up on one screen at startup
I've cherry-picked the upstream patch and added it to the package and it will be available from my PPA for testing. -- dual screen all panels end up on one screen at startup https://bugs.launchpad.net/bugs/290935 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 290935] Re: dual screen all panels end up on one screen at startup
Debdiff for Jaunty ** Attachment added: "Use correct DISPLAY when using multiple screens" http://launchpadlibrarian.net/28166071/glib2.0_2.20.1-0ubuntu3%7Etj%7Eppa1j.debdiff -- dual screen all panels end up on one screen at startup https://bugs.launchpad.net/bugs/290935 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 278261] Re: two xscreens -> gnome panel crashes
Having just patched glib to fix bug #290935 "dual screen all panels end up on one screen at startup" I'm using dual screens again and hit this bug whilst using compiz cube and nvidia drivers. Metacity "/apps/metacity/general/compositing_manager" = false. Running gnome-panel from within gdb shows the following stack-trace when gnome-panel crashes after clicking on a custom launcher on the gnome- panel on screen 1. This doesn't crash using the 'standard' menu items on screen 1. (Screen 1 is the *second* screen). The problem seems to originate from: #21 0x7f50f90ed5b2 in gdk_window_new () from /usr/lib/libgdk-x11-2.0.so.0 ... #27 0x7f50f95a0516 in gtk_widget_realize () from /usr/lib/libgtk-x11-2.0.so.0 #28 0x0042d509 in xstuff_zoom_animate () #29 0x00442919 in launcher_launch () gdb --args gnome-panel --sync (gdb) run Starting program: /usr/bin/gnome-panel --sync [Thread debugging using libthread_db enabled] ... ** (gnome-panel:9749): DEBUG: Adding applet 40. [New Thread 0x7f50e2384950 (LWP 9796)] [New Thread 0x7f50e1b83950 (LWP 9797)] The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 18571 error_code 8 request_code 1 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGPIPE, Broken pipe. [Switching to Thread 0x7f50fad887d0 (LWP 9749)] 0x7f50f6f7022c in __libc_writev (fd=33, vector=0x1cc1d80, count=1) at ../sysdeps/unix/sysv/linux/writev.c:46 46 ../sysdeps/unix/sysv/linux/writev.c: No such file or directory. in ../sysdeps/unix/sysv/linux/writev.c (gdb) bt #0 0x7f50f6f7022c in __libc_writev (fd=33, vector=0x1cc1d80, count=1) at ../sysdeps/unix/sysv/linux/writev.c:46 #1 0x7f50f9dd84e6 in write_data_T (cnx=0x1cf9170, qw=0x7fff02dca510) at linc-connection.c:1048 #2 0x7f50f9dd99ff in link_connection_writev (cnx=0x1cf9170, vecs=0x1cc1d80, nvecs=1, opt_write_opts=0x0) at linc-connection.c:1244 #3 0x7f50f9db834e in giop_connection_close (cnx=0x1cf9170) at giop-connection.c:54 #4 0x7f50f9db8371 in giop_connection_dispose (obj=0x1cf9170) at giop-connection.c:68 #5 0x7f50f79fb690 in IA__g_object_run_dispose (object=0x1cf9170) at /tmp/buildd/glib2.0-2.20.1/gobject/gobject.c:789 #6 0x7f50f9dd7da0 in link_connections_close () at linc-connection.c:1655 #7 0x7f50f9db8919 in giop_shutdown () at giop.c:658 #8 0x7f50f9dbcf7f in CORBA_ORB_shutdown (orb=0x161d1c0, wait_for_completion=1 '\001', ev=0x7fff02dca620) at corba-orb.c:1238 #9 0x7f50f9dbd0cd in CORBA_ORB_destroy (orb=0x21, ev=0x7fff02dca620) at corba-orb.c:1257 #10 0x7f50f9dbe692 in shutdown_orb () at corba-orb.c:306 #11 0x7f50f6ec86ed in *__GI_exit (status=1) at exit.c:75 #12 0x7f50f910bc21 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #13 0x7f50f74625b4 in _XError () from /usr/lib/libX11.so.6 #14 0x7f50f74698f9 in ?? () from /usr/lib/libX11.so.6 #15 0x7f50f7469fd8 in _XReply () from /usr/lib/libX11.so.6 #16 0x7f50f745de13 in XSync () from /usr/lib/libX11.so.6 #17 0x7f50f745dfcb in ?? () from /usr/lib/libX11.so.6 #18 0x7f50f743f0cf in XDefineCursor () from /usr/lib/libX11.so.6 #19 0x7f50f9119588 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #20 0x7f50f9118f98 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #21 0x7f50f90ed5b2 in gdk_window_new () from /usr/lib/libgdk-x11-2.0.so.0 #22 0x7f50f95b04f8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #23 0x7f50f79f927d in IA__g_closure_invoke (closure=0x15e3c60, return_value=0x0, n_param_values=1, param_values=0x2199560, invocation_hint=0x7fff02dcacc0) at /tmp/buildd/glib2.0-2.20.1/gobject/gclosure.c:767 #24 0x7f50f7a0e723 in signal_emit_unlocked_R (node=0x15e3cd0, detail=0, instance=0x2162090, emission_return=0x0, instance_and_params=0x2199560) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3177 #25 0x7f50f7a10432 in IA__g_signal_emit_valist (instance=0x2162090, signal_id=, detail=0, var_args=0x7fff02dcaea0) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:2980 #26 0x7f50f7a10953 in IA__g_signal_emit (instance=0x21, signal_id=30154112, detail=1) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3037 #27 0x7f50f95a0516 in gtk_widget_realize () from /usr/lib/libgtk-x11-2.0.so.0 #28 0x0042d509 in xstuff_zoom_animate () #29 0x00442919 in launcher_launch () #30 0x7f50f79f927d in IA__g_closure_invoke (closure=0x1efefd0, return_value=0x0, n_param_values=1, param_values=0x21994a0, invocation_hint=0x7fff02dcb280) at /tmp/buildd/glib2.0-2.20.1/gobject/gclo
[Bug 278261] Re: two xscreens -> gnome panel crashes
I neglected to install the libgtk ebug symbols for the previous back- trace. Here's a summary of the key parts that I'm focusing on: #19 0x7fd66d49a588 in gdk_window_x11_set_cursor (window=0x148f960, cursor=0x0) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:2912 #20 0x7fd66d499f98 in _gdk_window_new (parent=0x105f000, attributes=0x7fff7714ce50, attributes_mask=) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:904 #21 0x7fd66d46e5b2 in IA__gdk_window_new (parent=0x105f000, attributes=0x7fff7714ce50, attributes_mask=736) at /build/buildd/gtk+2.0-2.16.1/gdk/gdkwindow.c:379 #22 0x7fd66d9314f8 in gtk_window_realize (widget=0x1ba8ea0) at /build/buildd/gtk+2.0-2.16.1/gtk/gtkwindow.c:4788 #23 0x7fd66bd7a27d in IA__g_closure_invoke (closure=0x1073160, return_value=0x0, n_param_values=1, param_values=0x1a7d340, invocation_hint=0x7fff7714d040) at /tmp/buildd/glib2.0-2.20.1/gobject/gclosure.c:767 #24 0x7fd66bd8f723 in signal_emit_unlocked_R (node=0x10731d0, detail=0, instance=0x1ba8ea0, emission_return=0x0, instance_and_params=0x1a7d340) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3177 #25 0x7fd66bd91432 in IA__g_signal_emit_valist (instance=0x1ba8ea0, signal_id=, detail=0, var_args=0x7fff7714d220) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:2980 #26 0x7fd66bd91953 in IA__g_signal_emit (instance=0x24, signal_id=24437312, detail=1) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3037 #27 0x7fd66d921516 in IA__gtk_widget_realize (widget=0x1ba8ea0) at /build/buildd/gtk+2.0-2.16.1/gtk/gtkwidget.c:3322 #28 0x0042d509 in xstuff_zoom_animate () #29 0x00442919 in launcher_launch () Looking at gdk_window_new() its parameters break down as: (gdb) print parent $18 = (GdkWindow *) 0x11c3000 (gdb) print /x attributes_mask $17 = 0x2e0 (GDK_WA_TYPE_HINT | GDK_WA_CURSOR | GDK_WA_Y | GDK_WA_X ) (gdb) print attributes->title $1 = (gchar *) 0x0 (gdb) print attributes->event_mask $2 = 64514 (gdb) print attributes->x $3 = 0 (gdb) print attributes->y $4 = 30946192 (gdb) print attributes->width $5 = 200 (gdb) print attributes->height $6 = 200 (gdb) print attributes->wclass $7 = GDK_INPUT_OUTPUT (gdb) print attributes->window_type $9 = GDK_WINDOW_TEMP (gdb) print attributes->cursor $10 = (GdkCursor *) 0x1d82560 (gdb) print attributes->wmclass_name $11 = (gchar *) 0x1d84850 "gnome-panel" (gdb) print attributes->wmclass_class $12 = (gchar *) 0x1d848a0 "Gnome-panel" (gdb) print attributes->override_redirect $13 = 18706784 (gdb) print attributes->type_hint $14 = GDK_WINDOW_TYPE_HINT_NORMAL (gdb) print /x attributes->cursor->type $28 = 0x11cffd0 Not clear what this indicates, but: #19 0x7fd66d49a588 in gdk_window_x11_set_cursor (window=0x148f960, cursor=0x0) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:2912 indicates cursor = GDK_X_CURSOR. Adding the libx11-6 debug symbols shows: #11 0x7f4c174806ed in *__GI_exit (status=1) at exit.c:75 #12 0x7f4c196c3c21 in gdk_x_error (display=, error=) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkmain-x11.c:645 #13 0x7f4c17a1a5b4 in _XError (dpy=0x1a427f0, rep=0x2672fc0) at ../../src/XlibInt.c:2931 #14 0x7f4c17a218f9 in process_responses (dpy=0x1a427f0, wait_for_first_event=0, current_error=0x7fff23383058, current_request=17837) at ../../src/xcb_io.c:207 #15 0x7f4c17a21fd8 in _XReply (dpy=0x1a427f0, rep=0x7fff233830a0, extra=0, discard=1) at ../../src/xcb_io.c:457 #16 0x7f4c17a15e13 in XSync (dpy=0x1a427f0, discard=0) at ../../src/Sync.c:48 #17 0x7f4c17a15fcb in _XSyncFunction (dpy=0x20) at ../../src/Synchro.c:37 #18 0x7f4c179f70cf in XDefineCursor (dpy=0x1a427f0, w=20972868, cursor=0) at ../../src/DefCursor.c:48 #19 0x7f4c196d1588 in gdk_window_x11_set_cursor (window=0x247e640, cursor=0x0) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:2912 -- two xscreens -> gnome panel crashes https://bugs.launchpad.net/bugs/278261 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 278261] Re: two xscreens -> gnome panel crashes
Looking at the libx11-dev package source code I see that the 'Display'
value is optimized out into a register variable, which is a pain since
that is likely key to the bug and doesn't show up in gdb output.
libx11/src/DefCursor.c:
int
XDefineCursor (
register Display *dpy,
Window w,
Cursor cursor)
{
This function is called from
gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c::gdk_window_x11_set_cursor()
if (!GDK_WINDOW_DESTROYED (window))
{
XDefineCursor (GDK_WINDOW_XDISPLAY (window),
GDK_WINDOW_XID (window),
xcursor);
if (cursor)
impl->cursor = gdk_cursor_ref (cursor);
}
Which comes from:
#define GDK_WINDOW_XDISPLAY(win) (GDK_SCREEN_X11 (GDK_WINDOW_SCREEN
(win))->xdisplay)
#define GDK_SCREEN_X11(object) (G_TYPE_CHECK_INSTANCE_CAST
((object), GDK_TYPE_SCREEN_X11, GdkScreenX11))
#define GDK_WINDOW_SCREEN(win)(GDK_DRAWABLE_IMPL_X11
(((GdkWindowObject)
win)->impl)->screen)
--
two xscreens -> gnome panel crashes
https://bugs.launchpad.net/bugs/278261
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 278261] Re: two xscreens -> gnome panel crashes
I believe I've managed to identify the issue here. It is dependent on my having correctly navigated the register variable identification. Gdb is supposed to report which register the variable is stored in using "info address dpy" but this reports "Symbol "dpy" is a variable with multiple locations" - not exactly helpful. I then looked at all the registers (info registers) and saw that rbx and rdi contained the same value. I took a leap of faith and assumed this was the dpy pointer. Examining the structure there the values seem to make sense in the context of a Display pointer (which is a typedef of the true _XDisplay). The breakpoint was triggered after trying to open a program via a custom launcher on screen 1 (DISPLAY=:0.1). In XDefineCursor(Display dpy, Window w, Cursor c) the values in the dpy structure show: (gdb) print ((Display *)$rbx)->proto_major_version $14 = 11 (gdb) print ((Display *)$rbx)->proto_minor_version $15 = 0 (gdb) print ((Display *)$rbx)->vendor $16 = 0x204cbc0 "The X.Org Foundation" (gdb) print ((Display *)$rbx)->nscreens $11 = 2 (gdb) print ((Display *)$rbx)->display_name $12 = 0x2032c50 ":0.0" (gdb) print ((Display *)$rbx)->default_screen $13 = 0 Notice that "display_name" is ":0.0" when it should be ":0.1". This suggests that the GDK_WINDOW_XDISPLAY and subsidiary macros in the GTK package are not delivering the correct result. Because the issue is limited to custom launchers on display :0.1 it looks likely the problem is higher up the call stack; most likely in gnome-panel itself. -- two xscreens -> gnome panel crashes https://bugs.launchpad.net/bugs/278261 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 390985] [NEW] 16_compiz_workspace_switcher.patch assumes single screen
Public bug reported: Binary package hint: gnome-panel This patch assumes a single-head, not multi-head monitor configuration and uses a hard-coded 'screen0' value. In some circumstances where the Compiz hsize &vsize settings on screen0 and screen1 are different this will cause unexpected and unwanted behaviour on screen . ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- 16_compiz_workspace_switcher.patch assumes single screen https://bugs.launchpad.net/bugs/390985 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 327175] Re: Sometimes loses input devices on suspend/resume: Device has changed - disabling.
I've been experiencing this recently with the Bluetooth mouse. It occurs after multiple suspend/resume cycles - I'd guess 4 or 5 cycles before it hits. The mouse associates but the cursor is no longer controlled, and Xorg.0.log shows: II) config/hal: Adding input device Bluetooth Travel Mouse (**) Bluetooth Travel Mouse: always reports core events (**) Bluetooth Travel Mouse: Device: "/dev/input/event10" (II) Bluetooth Travel Mouse: Found 8 mouse buttons (II) Bluetooth Travel Mouse: Found x and y relative axes (II) Bluetooth Travel Mouse: Configuring as mouse (**) Bluetooth Travel Mouse: YAxisMapping: buttons 4 and 5 (**) Bluetooth Travel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (EE) Too many input devices. Ignoring Bluetooth Travel Mouse (II) UnloadModule: "evdev" (EE) config/hal: NewInputDeviceRequest failed (11) -- Sometimes loses input devices on suspend/resume: Device has changed - disabling. https://bugs.launchpad.net/bugs/327175 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 333732] [NEW] Touchpad cursor trapped on screen 1
Public bug reported: Binary package hint: xserver-xorg-input-synaptics apt-cache policy xserver-xorg-input-synaptics xserver-xorg-input-synaptics: Installed: 0.99.3-2ubuntu2 Candidate: 0.99.3-2ubuntu2 Version table: *** 0.99.3-2ubuntu2 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status Sony Vaio VGN FE41Z with an integrated ALPS touchpad: [ 22.574690] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio4/input/input8 The PC is configured to use two X screens (:0.0 left, :0.1 right). The primary input device is a Bluetooth mouse which I use all the time when tethered to the desktop and using the dual screens. Investigating another user's experiences of changing sensitivity of the two input devices separately, I was using the touchpad to determine how much change there is when the gsynaptics sensitivity slider is adjusted. By chance I dragged the mouse cursor onto screen 1 using the touchpad. When I tried to drag it back to screen 0 it refused to move beyond the left edge of screen 1. More testing showed it was trapped on screen 1. If I use the Bluetooth mouse the cursor returns to screen 0 as expected. As I said earlier, I always use the mouse when tethered so I'd never noticed this before. I'm not entirely sure how this should be debugged so any 'pointers' are welcome :p ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: xserver-xorg-input-synaptics apt-cache policy xserver-xorg-input-synaptics xserver-xorg-input-synaptics: Installed: 0.99.3-2ubuntu2 Candidate: 0.99.3-2ubuntu2 Version table: *** 0.99.3-2ubuntu2 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status Sony Vaio VGN FE41Z with an integrated ALPS touchpad: [ 22.574690] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio4/input/input8 - The PC is configured to use two X screens (:0.0, :0.1). The primary - input device is a Bluetooth mouse which I use all the time when tethered - to the desktop and using the dual screens. + The PC is configured to use two X screens (:0.0 left, :0.1 right). The + primary input device is a Bluetooth mouse which I use all the time when + tethered to the desktop and using the dual screens. Investigating another user's experiences of changing sensitivity of the two input devices separately, I was using the touchpad to determine how much change there is when the gsynaptics sensitivity slider is adjusted. By chance I dragged the mouse cursor onto screen 1 using the touchpad. When I tried to drag it back to screen 0 it refused to move beyond the left edge of screen 1. More testing showed it was trapped on screen 1. If I use the Bluetooth mouse the cursor returns to screen 0 as expected. As I said earlier, I always use the mouse when tethered so I'd never noticed this before. I'm not entirely sure how this should be debugged so any 'pointers' are welcome :p -- Touchpad cursor trapped on screen 1 https://bugs.launchpad.net/bugs/333732 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 331918] Re: Clipped area for multiple X screens with different dimensions
On Tue, 2009-02-24 at 08:30 +, Danny Baumann wrote: > Also, what are your settings for the detect_outputs option on _screen > 1_? Danny, many thanks for taking the time to review this. Your question is a good one. I've previously tried enabling and disabling detect_outputs and observed no difference. Prompted by your question I've just looked closer. Because I was intrigued by where the settings are stored I opened gconf-editor and had a peek. At the same time I used CCSM to check and change values for screen 0 and screen 1. I was surprised to find the *only* screen 0 detect_outputs was changed; no entry for detect_outputs shows up for screen 1. grep -r detect_outputs ~/.gconf/* /home/tj/.gconf/apps/compiz/general/screen0/options/%gconf.xml: Experimenting further I also found that when I edit the list of outputs in CCSM, whether for screen 0 or 1, the resulting change is made only to screen 0. I left it with "detect_outputs" false and did some experiments. Looking closer at "outputs" with gconf-editor for screen 1 it reports "! This key has no schema" but shows (where from I don't know) "1024x768+0 +0" - this doesn't show up in CCSM editing the "outputs" for screen 1. I tried replacing that value using gconf-editor with "128x1024+0+0" and starting compiz on screen 1 only, but it hasn't changed the result. I then tried changing the "outputs" for screen 0 to "1280x1024+0+0" and starting compiz on screen 1 only (hoping it might be using the wrong screen options) but that didn't improve matters either. I tried adding "detect_outputs" 'true' to screen 1 options (whilst leaving screen 0 'false'): sed -i -e '//a\ \t\ ' ~/.gconf/apps/compiz/general/screen1/options/%gconf.xml Starting compiz on screen 1 only - no change. I set screen 1 "detect_outputs" to 'false' (screen 1 "outputs" is listing "1280x1024+0+0") and tried again. Hallelujah !! Finally, screen 1 fills the full 1280x1024 of the screen. I then tried starting compiz "normally" - managing both screens - and it seems to behave as it used to. So, it seems as if the issue is partly to do with CCSM? Anything else you need checking/testing, let me know. -- Clipped area for multiple X screens with different dimensions https://bugs.launchpad.net/bugs/331918 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Fridtjof, could you attach /var/log/kern.log that includes the problem. I want to see what was going on before and after the warning message. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Fridtjof, thank-you. It looks like the same cause as zippidy_josh reported. [10692.148085] sd 0:0:0:0: [sda] Starting disk [10697.032030] ata1: link is slow to respond, please be patient (ready=0) [10698.992081] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Fridtjof, zippyidy_josh, could both attach the system PCI configuration from: sudo lspci -vvnn I'm wondering if there's a common hardware device here, or whether it is an issue with the ata_piix / libata drivers. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Could both of you attach the details of the disk drive that is slow to respond? There are several potential scenarios I'm exploring: 1. Specific issues with some disk drives. Some drives take a *long* time to clear the status register after a reset. 2. Issues with the particular chipset/controllers (I notice both systems have two 82801* (ICH8/9 Family) IDE controllers 3. Issues with ata_piix driver The reports: ls -l /sys/block/sda > /tmp/report.txt sudo hdparm -I /dev/sda >> /tmp/report.txt Attach /tmp/report.txt to your reply. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
This looks to be related to a known issue with some combinations of controller and disk. The warning "link is slow to respond, please be patient" is issued in drivers/ata/libata-core.c::ata_wait_ready(). It waits for the link status to change from 0xff (no device) for up to ATA_TMOUT_FF_WAIT. Currently this is defined as 800 milliseconds in include.linux/libata.h: /* FIXME: GoVault needs 2s but we can't afford that without * parallel probing. 800ms is enough for iVDR disk * HHD424020F7SV00. Increase to 2secs when parallel probing * is in place. */ ATA_TMOUT_FF_WAIT = 800, The commit that introduced ata_wait_ready() was: commit aa2731ad9ad80ac3fca48bd1c4cf0eceede4810e Author: Tejun Heo Date: Mon Apr 7 22:47:19 2008 +0900 libata: separate out ata_wait_ready() and implement ata_wait_after_reset() Factor out waiting logic (which is common to all ATA controllers) from ata_sff_wait_ready() into ata_wait_ready(). ata_wait_ready() takes @check_ready function pointer and uses it to poll for readiness. This allows non-SFF controllers to use ata_wait_ready() to wait for link readiness. This patch also implements ata_wait_after_reset() - generic version of ata_sff_wait_after_reset() - using ata_wait_ready(). ata_sff_wait_ready() is reimplemented using ata_wait_ready() and ata_sff_check_ready(). Functionality remains the same. The associated LKML comments give more detail: http://lkml.org/lkml/2007/5/16/279 "On certain device/controller combination, 0xff status is asserted after reset and doesn't get cleared during 150ms post-reset wait. As 0xff status is interpreted as no device (for good reasons), this can lead to misdetection on such cases. This patch implements ata_wait_after_reset() which replaces the 150ms sleep and waits upto ATA_TMOUT_FF_WAIT if status is 0xff. ATA_TMOUT_FF_WAIT is currently 800ms which is enough for HHD424020F7SV00 to get detected but not enough for Quantum GoVault drive which is known to take upto 2s. Without parallel probing, spending 2s on 0xff port would incur too much delay on ata_piix's which use 0xff to indicate empty port and doesn't have SCR register, so GoVault needs to wait till parallel probing." In terms of it causing this kernel oops report it looks as if the problem is with the slow-path detection firing a false positive. There was a related bug #318978 "Hard drive in Studio XPS 13 and 16 cause a 17-18s resume time" which applied a patch (commit b65db6fd5d) to increase ATA_TMOUT_PMP_SRST_WAIT to 5 seconds. In that case it was increasing the time allowed for the soft reset. I suspect this current issue is related to that. We need to decide if we can increase ATA_TMOUT_FF_WAIT to 5 seconds. Because it is a timeout and not a delay increasing the maxmium shouldn't affect systems that don't have a slow device since it is only used if the link indicates a device is present. I've attached a patch that enables a 5 second maximum wait. I'll ask other kernel developers to look at this. ** Attachment added: "Increase ATA_TMOUT_FF_WAIT to 5 seconds" http://launchpadlibrarian.net/23125610/lp286672-increase-ATA_TMOUT_FF_WAIT-to-5-seconds.patch -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Forgot to mention my primary concern here! Although the change in the arbitrary time-out will remove the 'link is slow to respond' message it won't of itself remove the kernel oops. The ideal solution would be parallel processing for multiple devices maybe combined with some intelligence in the kernel's slow-path detection to account for situations that are mandated in specifications (in this case ATA-6 allows such delays) or imposed by hardware constraints. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Fridtjof, we're looking at this issue in more detail and thinking about back-porting the Jaunty patch from bug #318978 to test kernels for Intrepid. However we noticed that in one of your dmesg reports in comment #16 https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/286672/comments/16 It shows the in-use kernel was "2.6.28-8-generic #24-Ubuntu" which should include the patch to deal with #318978. Could you clarify which kernel versions you are experiencing this with to help us? Stefan is going to build an Intrepid test kernel with the patch incorporated and will make it available shortly. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 325238] Re: BUG: unable to handle kernel paging request
Felipe, I've spent about an hour examining the log-files and reports. Everything points to a (intermittent) hardware problem. I'm inclined to think it could be something causing a memory-mapping issue right now, but that is just a guess with no evidence to point to. Here's some things you can do to try and narrow the cause down in order of difficulty: 1. Don't use the VESA framebuffer device - I think it is a module in Hardy so you may have to remove it from the initial ram-disk as well as removing "vga=0x031b" from the kernel command-line at boot-time. 2. Add " debug" to the kernel command-line to capture more detail about the boot process in /var/log/kern.log 3. Reset BIOS to factory defaults. 4. Remove each memory module, give the contacts a wipe with rubbing alcohol or fine wet'n'dry paper and replace them firmly 5. Strip the system down to the barest possible hardware and use a live- CD. (remove additional video adaptors, non-critical PCI adapters, hard disks, etc). 6. If (5) results in a stable system that doesn't exhibit the problem, add devices back in one-by-one and boot from the live-CD after each addition. If the problem recurs after such a step you've pin-pointed the cause and proceed to figuring out a solution. -- BUG: unable to handle kernel paging request https://bugs.launchpad.net/bugs/325238 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 325238] Re: BUG: unable to handle kernel paging request
On Thu, 2009-02-26 at 20:18 +, Felipe Figueiredo wrote: > Should I post any other tests? Should this report be closed as Fix > Released, or Invalid? I'm glad to hear you've apparently solved the issue. I would recommend you keep the bug open for a couple of weeks whilst you test the system thoroughly to assure yourself this is indeed the permanent fix. Once you're satisfed change the bug status to "Invalid" (since it wasn't a bug with Ubunt/Linux) and add a comment confirming the solution. -- BUG: unable to handle kernel paging request https://bugs.launchpad.net/bugs/325238 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 287453] Re: kernel warning while suspending
Jacob, your problem looks unrelated to this bug and more serious. Please create a new bug report "BUG: scheduling while atomic: notification-da/10006/0x1001" against the "linux" package, attach the same logs you've attached here (maybe delete the attachments from this report to save confusion) and subscribe me directly to the new bug report. Please describe the scenario that causes it and whether it makes the system unstable. Make sure to report the kernel version affected using "uname -a" and "lsb_release -a". -- kernel warning while suspending https://bugs.launchpad.net/bugs/287453 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 87317] Re: Screensaver just detects idle time on one screen
Tested Aaron's patch with Jaunty and it appears to be working fine. I've repackaged the patch in a debdiff and am nominating for Jaunty. ** Attachment added: "Watch all X screens for activity" http://launchpadlibrarian.net/23174124/gnome-screensaver_2.24.0-0ubuntu5.debdiff -- Screensaver just detects idle time on one screen https://bugs.launchpad.net/bugs/87317 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 335429] Re: BUG: scheduling while atomic: notification-da/10006/0x10000001
** Changed in: linux (Ubuntu) Assignee: (unassigned) => TJ (intuitivenipple) -- BUG: scheduling while atomic: notification-da/10006/0x1001 https://bugs.launchpad.net/bugs/335429 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 287453] Re: kernel warning while suspending
** Attachment removed: "lspci.txt" http://launchpadlibrarian.net/23161853/lspci.txt ** Attachment removed: "cpuinfo.txt" http://launchpadlibrarian.net/23161849/cpuinfo.txt ** Attachment removed: "kern.log" http://launchpadlibrarian.net/23161811/kern.log -- kernel warning while suspending https://bugs.launchpad.net/bugs/287453 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 287453] Re: kernel warning while suspending
If you are experiencing this issue (kernel reporting a slow resume -
more than 5 seconds) there are several potential causes, at least two of
which are expected (1 & 2) and the warning is something of a false
positive.
1. Several devices pushing the resume time slightly beyond the arbitrary
5-second boundary
2. Hard disks taking some time to become ready - see bug #318978
3. Device(s) requesting a firmware file to be loaded whilst user-space is still
frozen (the delay will be around 60 seconds in this case) - see bug #331415
4. Some device or driver suffering specific problems with resume.
To determine if the warnings you see are 'real' problems please run this
small shell script and copy the results to a comment here.
for log in /var/log/kern.log*; do CMD="cat "; echo $log; [ !
${log##*.gz} ] && CMD="zcat "; $CMD $log | grep -n 'PM: suspend devices
took'; done
Example output:
/var/log/kern.log
/var/log/kern.log.0
3678:Feb 19 06:06:56 hephaestion kernel: [60285.296215] PM: suspend devices
took 3.752 seconds
3948:Feb 19 10:19:23 hephaestion kernel: [75478.752211] PM: suspend devices
took 3.752 seconds
/var/log/kern.log.1.gz
/var/log/kern.log.2.gz
/var/log/kern.log.3.gz
Basically, if you see a resume time close to but just over 5 seconds, it
is likely there is no real problem - it's just the kernel taking a lets-
be-cautious approach, e.g.:
PM: resume devices took 5.148 seconds
If there are no other kernel Oops messages besides the
suspend_test_finish() then you can safely ignore the warning.
--
kernel warning while suspending
https://bugs.launchpad.net/bugs/287453
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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
The only thing of note in the disk reports is that both disks are on the first PCI SATA controller and, probably more significant, both devices are Western Digital. Anecdotal reports suggest some WD drives in particular have this characteristic slow reset. Please try the Intrepid kernel Stefan has prepared and report back with the dmesg after a suspend/resume cycle. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 331415] Re: request_firmware() fails on resume from suspend
This is a small shell-script that can help identify whether a system is
affected by this bug.
for log in /var/log/kern.log*; do CMD="cat "; echo $log; [ !
${log##*.gz} ] && CMD="zcat "; $CMD $log | grep -n 'PM:
\(suspend\|resume\) devices took'; done
Example output:
var/log/kern.log
/var/log/kern.log.0
3678:Feb 19 06:06:56 hephaestion kernel: [60285.296215] PM: suspend devices
took 3.752 seconds
3830:Feb 19 06:06:57 hephaestion kernel: [60354.780958] PM: resume devices took
69.072 seconds
3948:Feb 19 10:19:23 hephaestion kernel: [75478.752211] PM: suspend devices
took 3.752 seconds
4102:Feb 19 10:19:23 hephaestion kernel: [75488.172580] PM: resume devices took
9.024 seconds
/var/log/kern.log.1.gz
/var/log/kern.log.2.gz
/var/log/kern.log.3.gz
The resume of 69 seconds shows this system is affected.
--
request_firmware() fails on resume from suspend
https://bugs.launchpad.net/bugs/331415
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 287453] Re: kernel warning while suspending
Trust me to provide an incorrect shell script! I omitted to test for the
"resume" as well as "suspend" action!
Please use this shell script instead:
for log in /var/log/kern.log*; do CMD="cat "; echo $log; [ !
${log##*.gz} ] && CMD="zcat "; $CMD $log | grep -n 'PM:
\(suspend\|resume\) devices took'; done
Example output:
var/log/kern.log
/var/log/kern.log.0
3678:Feb 19 06:06:56 hephaestion kernel: [60285.296215] PM: suspend devices
took 3.752 seconds
3830:Feb 19 06:06:57 hephaestion kernel: [60354.780958] PM: resume devices took
69.072 seconds
3948:Feb 19 10:19:23 hephaestion kernel: [75478.752211] PM: suspend devices
took 3.752 seconds
4102:Feb 19 10:19:23 hephaestion kernel: [75488.172580] PM: resume devices took
9.024 seconds
/var/log/kern.log.1.gz
/var/log/kern.log.2.gz
/var/log/kern.log.3.gz
The resume of 69 seconds shows this system is affected by bug #331415
--
kernel warning while suspending
https://bugs.launchpad.net/bugs/287453
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 335429] Re: BUG: scheduling while atomic: notification-da/10006/0x10000001
There's nothing obvious in the logs to indicate the cause of this. When the system was suspended what applications were in use? If you can reproduce this we can investigate further but if it is a one- off it will have to be assigned to the "we'll never really know" Invalid status. ** Changed in: linux (Ubuntu) Assignee: TJ (intuitivenipple) => (unassigned) -- BUG: scheduling while atomic: notification-da/10006/0x1001 https://bugs.launchpad.net/bugs/335429 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 242191] Re: Xdmx packages missing in hardy
** Changed in: xorg-server (Ubuntu Hardy) Assignee: TJ (intuitivenipple) => (unassigned) Status: In Progress => Confirmed -- Xdmx packages missing in hardy https://bugs.launchpad.net/bugs/242191 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 217849] Re: Hardy 64-bit beta and nightly alternate installation stalls
I've just taken a look at the original dmesg and noticed something which could be significant: [0.004000] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.004000] Placing software IO TLB between 0x2000 - 0x2400 Quentin, when you get the opportunity could you attach a new Jaunty dmesg captured without any workarounds in place, and also: uname -a sudo lspci -vvnn > /tmp/lspci-vvnn.log lsmod >/tmp/lsmod.log Secondly, would it be possible to try temporarily removing 2GB of RAM (I'm guessing the system has 2 x 2GB RAM modules) and seeing if the problem still occurs? With only 2GB of RAM the software bounce buffering required by Intel CPUs that have no IOMMU controller will not be used. The main test is to reduce total RAM to less than 4GB. -- Hardy 64-bit beta and nightly alternate installation stalls https://bugs.launchpad.net/bugs/217849 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 262423] Re: [intrepid] Resume from suspend does not work in 2.6.27-1
Are any users still suffering the symptoms described in the original bug report? Resume from suspend fails and triggers a normal boot. The suspend works and causes spin down and blinking suspend light. If not I propose we close this report as "Fix Released" -- [intrepid] Resume from suspend does not work in 2.6.27-1 https://bugs.launchpad.net/bugs/262423 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 267779] Re: via-rhine network adapater won't work on resume
The irqfixup solution is intended for working around broken device firmware and therefore it could be argued there isn't a bug in the kernel. Andrey also reports interesting scenarios in his Gentoo bug comments: If module is loaded and interface is down via ifconfig, then after resuming network doesn't work. If module is loaded and interface is up, then after resuming network works. If module is unloaded, I can put laptop into S3 state, the wake it up and then, after loading module, network works just fine. Are any users still suffering this bug? If so please report the kernel version(s) affected using: uname -a If not, I propose closing this bug as either 'Wont Fix" (firmware issue) or "Fix Released" (no longer experiencing the issue with regular kernel options). -- via-rhine network adapater won't work on resume https://bugs.launchpad.net/bugs/267779 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 11149] Re: snd_cs46xx does not work after suspend/resume cycle
If this is still happening on Hardy, Intrepid, or Jaunty could you please report/attach the following information: Q. Does this happen for hibernation (a.k.a. suspend to disk) ? Q. Does this happen for suspend/resume (suspend to RAM) ? If you answered Yes to either of these questions please attach /var/log/dmesg after doing a start-up, suspend/hibernate, resume cycle. Name the resulting files dmesg-hibernate.log and dmesg-suspend.log, respectively. sudo lspci -vvnn >/tmp/lspci.log uname -a lsb_release -a -- snd_cs46xx does not work after suspend/resume cycle https://bugs.launchpad.net/bugs/11149 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34155] Re: Suspend-To-Ram (S3) doesn't work on Dell Latitude C640
For those that can reproduce this could you provide the following
reports/attachments?
For both hibernate (to disk) and suspend (to RAM) gather the kern.log
files from the current start-up and the previous after a suspend/resume
and hibernate cycle. By providing the previous kern.log file we should
capture useful information even if you had to restart the PC to get to
the logs.
tar -czf kern.logs.tar.gz /var/log/kern.log{,.0}
sudo lspci -vvnn >/tmp/lspci.log
uname -a
lsb_release -a
--
Suspend-To-Ram (S3) doesn't work on Dell Latitude C640
https://bugs.launchpad.net/bugs/34155
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291017] Re: VIA VT6102 Rhine II ethernet driver crashes after suspending
*** This bug is a duplicate of bug 267779 *** https://bugs.launchpad.net/bugs/267779 This looks like a duplicate of Bug #267779 "via-rhine network adapter won't work on resume". Please take a look at that. In both big reports lspci shows: Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 74) A work-around is to add the " irqfixup" parameter to the kernel command- line. This is to try and play nicely with broken firmware in the adapter. ** This bug has been marked a duplicate of bug 267779 via-rhine network adapater won't work on resume -- VIA VT6102 Rhine II ethernet driver crashes after suspending https://bugs.launchpad.net/bugs/291017 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Fridtjof, thank-you. As already mentioned there is no real problem here. [ 110.100086] sd 0:0:0:0: [sda] Starting disk [ 114.984030] ata1: link is slow to respond, please be patient (ready=0) [ 116.216086] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 116.232336] ata1.00: configured for UDMA/133 The reason for the Warning: [ 116.506548] PM: resume devices took 7.100 seconds is that TEST_SUSPEND_SECONDS is arbitrarily set to 5 seconds. It looks as if we could increase this value slightly in order to avoid these unnecessary Warnings. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 34389] Re: Lid state is incorrect on Dell Inspiron 700m
If you're still experiencing this issue with Hardy, Intrepid or Jaunty please report/attach the following after enabling kernel debug logging. To enable kernel debug enter the GRUB menu at start-up by pressing ESCape. Highlight the kernel to boot, press "E" to edit it. Highlight the "kernel" line and press "E" to edit it. At the end of the line remove "quiet splash" and replace with " debug". Press Enter, then press "B" to boot with the changed parameters. Do a start-up, suspend, resume cycle. Attach /var/log/kern.log to a comment containing these reports: uname -a lsb_release -a -- Lid state is incorrect on Dell Inspiron 700m https://bugs.launchpad.net/bugs/34389 You received this bug notification because you are a member of Kubuntu Bugs, which is a subscriber of a duplicate bug. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 53310] Re: Wireless (ipw2200) does not work after waking up from sleep(without manually switching on).
This bug is related to the Intel ipw2200 kernel module which manages the 2200BG adapter. Tomas Hynk's PC has: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) Alex Fraser's PC has the 3945 which uses the iwl3945 module: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] nestoklon, Siddhu Warrier and yclian have Atheros wireless adapters. E.g. Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01) Tomas' original report shows the kill-switch is detected as being on: Jul 17 23:59:49 localhost kernel: [17180125.98] ipw2200: Radio Frequency Kill Switch is On: Jul 17 23:59:49 localhost kernel: [17180125.98] Kill switch must be turned off for wireless If you are using the Intel 2200BG or Intel 3945ABG and are affected by this issue in Hardy, Intrepid, or Jaunty please provide the following information with kernel debug enabled. To enable kernel debug enter the GRUB menu at start-up by pressing ESCape. Highlight the kernel to boot, press "E" to edit it. Highlight the "kernel" line and press "E" to edit it. At the end of the line remove "quiet splash" and replace with " debug". Press Enter, then press "B" to boot with the changed parameters. Do a clean start-up, suspend, resume cycle and then attach an archive containing these reports: uname -a >/tmp/version.log lsb_release -a >>/tmp/version.log sudo dmidecode -t system >/tmp/dmidecode.log lshal | sed -n '/^udi = .*rfkill/,/^udi =/ p' >/tmp/hal-rfkill.log sudo lspci -vvnn >/tmp/lspci.log tar -czf /tmp/lp53310.logs.tar.gz /tmp/version.log /tmp/dmidecode.log /var/log/kern.log /tmp/hal-rfkill.log /tmp/lspci.log Attach /tmp/lp53310.logs.tar.gz to a comment. -- Wireless (ipw2200) does not work after waking up from sleep(without manually switching on). https://bugs.launchpad.net/bugs/53310 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 44825] Re: lid state remains "closed" after suspend/resume
*** This bug is a duplicate of bug 34389 *** https://bugs.launchpad.net/bugs/34389 I'm marking this as a duplicate of #34389 "Lid state is incorrect on Dell Inspiron 700m" since the problem appears to affect several makes and models in the same way. The symptom being that after resuming the first time the lid-state reported by /proc/acpi/button/lid/LID*/state is always closed. We'll deal with the issue in that bug since it already has a number of duplicates. ** Changed in: linux (Ubuntu) Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) => (unassigned) ** This bug has been marked a duplicate of bug 34389 Lid state is incorrect on Dell Inspiron 700m -- lid state remains "closed" after suspend/resume https://bugs.launchpad.net/bugs/44825 You received this bug notification because you are a member of Kubuntu Bugs, which is a subscriber of a duplicate bug (via bug 34389). -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 34389] Re: Lid state is incorrect (closed) after resume with lid open
** Summary changed: - Lid state is incorrect on Dell Inspiron 700m + Lid state is incorrect (closed) after resume with lid open -- Lid state is incorrect (closed) after resume with lid open https://bugs.launchpad.net/bugs/34389 You received this bug notification because you are a member of Kubuntu Bugs, which is a subscriber of a duplicate bug. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 63967] Re: machine does not wake up after suspend
The key to this issue may be given by the following clue from
/var/log/kern.log:
ACPI Error (evxfevnt-0383): Could not disable RealTimeClock events [20080609]
ACPI: RTC can wake from S4
Which, if it is indicating the root cause, indicates a 'bad' ACPI DSDT.
If you're experiencing this issue with Hardy, Intrepid or Jaunty could
you please search the logs after recovering from this issue and report
the results:
grep '\(ACPI Error\|RealTimeClock\|RTC can wake\)'
/var/log/kern.log{,.0} | tee /tmp/lp63967.log
If that shows results attach /tmp/lp63967.log to this bug report.
--
machine does not wake up after suspend
https://bugs.launchpad.net/bugs/63967
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 59867] Re: Synaptics touchpad ceases functioning after suspend and resume.
Is anyone who experiences this issue able to test it with a Jaunty live- CD and suspend/resume? -- Synaptics touchpad ceases functioning after suspend and resume. https://bugs.launchpad.net/bugs/59867 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 53953] Re: change 'acerhk' to use 'autowlan=1' by default
Is anyone still affected by this issue? If so, have you tried the wistron_btns module? If trying the wistron_btns module have you tested the "force" module option? On Hardy the acerhk module is in the linux-ubuntu-modules package, not the regular kernel packages. Please report: uname -a lsb_release -a modinfo wistron_btns modinfo acerhk Both acerhk and wistron_btns are only for 32-bit kernels since they make use of calls into the system BIOS - something that can't be done with a 64-bit kernel. -- change 'acerhk' to use 'autowlan=1' by default https://bugs.launchpad.net/bugs/53953 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 77370] Re: Laptop Fan always on after resume from suspend to RAM
According to Hewlett Packard information, the ACPI FDTZ is actually the *Fan Speed* as a percentage of maximum speed. This would explain why Jesse is seeing high FDTZ values on resume coupled with fan noise. I'd like to inspect the ACPI DSDT of the affected models. I've created a shell script (pack-dsdt) to automate the collection process and attached it to this bug report. Download it to the affected PC, make the script executable, and run it: chmod a+x pack-dsdt sudo ./pack-dsdt The end-result will be a tar.gz archive in /tmp/ that can be attached to this bug report. ** Attachment added: "pack-dsdt script to collect ACPI DSDT" http://launchpadlibrarian.net/23202053/pack-dsdt -- Laptop Fan always on after resume from suspend to RAM https://bugs.launchpad.net/bugs/77370 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 95144] Re: USB does not work after suspend to RAM on IBM T42
Is anyone still experiencing this issue? If so, can you test it with a Jaunty live-CD and report back. -- USB does not work after suspend to RAM on IBM T42 https://bugs.launchpad.net/bugs/95144 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 277903] Re: Missing Operating System [message at boot]
On Sun, 2009-04-26 at 10:53 +, Anders Häggström wrote: > The output from the diagnostic MBR (the link from TJ on 2009-03-30) when > I hold CTRL-key own during boot is: "L D80 C07C HFF S3F P1 O003F > MAA55 E00". I have no clue of what that means but I hope it is valuble > for TJ. :) Here's the documentation from my mbr-diag.S source submitted to syslinux upstream: Due to the severe space constraints the output uses 1-character description codes to prefix each printed value. Values are in hexadecimal. Description Codes: L | C LBA or CHS addressing mode D drive number BIOS-reported drive number C cylinders Geometry of drive according to BIOS H heads S sectors P partition active partition number (first partition flagged active). '?' if no active partition O offsetabsolute sector offset of active partition . '' if no active partition M magic magic bytes of active partition boot sector (sector as read by BIOS). '' if no active partition. Value is reset to 0xDEAD before the sector is read to avoid inheriting the MBR magic on error E error error code returned by BIOS 'read sector' interrupt (0x02 or 0x42, int 0x13). '??' if no active partition. -- Missing Operating System [message at boot] https://bugs.launchpad.net/bugs/277903 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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
On Tue, 2009-04-21 at 18:16 +, Tormod Volden wrote: > TJ, I added the test-suspend-seconds tag to a bunch of reports which I > think are duplicates. Should I dup them, or would you like run your > launchpad mining on them first? Thanks Tormod that's really helpful. I'll run a modified script against them first and inspect them too - sometimes the logs show obvious device problems. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 293083] Re: USB startup thumb drive fails to boot
papukaija.
I think this ought to be marked Incomplete (and ask for more details)
since the original bug report is against 8.10 and reports a keyboard
error ("incorrect keyboard configuration"). It doesn't detail precisely
when that error occurs or where it comes from - is the before or after
the languages chooser, for example.
It could be an issue with syslinux (the boot-loader) or casper (the
live-CD environment) but is unlikely to be usbcreator since the image
itself was created.
It might be wise to alter the bug title to focus on the original
keyboard issue since otherwise it covers a wide range of other bugs, as
can be seen from the different causes/fixes already commented.
--
USB startup thumb drive fails to boot
https://bugs.launchpad.net/bugs/293083
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 286672] Re: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Progress Update: Currently analysing log-files collected on Launchpad to determine a suitable value for TEST_SUSPEND_SECONDS. -- WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() https://bugs.launchpad.net/bugs/286672 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 331415] Re: request_firmware() fails on resume from suspend
Progress update: I've finished a manual line-by-line analysis of every occurrence of: a) request_firmware() and relations b) each reference to a firmware file-name either explicitly or via a sprintf() format-string I've built an sqlite3 database based on the analysis that tracks every occurrence and adds references to: * kernel version * module * source-code file * line number * legal license I'm currently completing the translation from the original flat-file to full 3rd normal form. To Do: * complete the 3NF translation and verify its integrity against the flat-file * analyse each firmware_request() occurrence to determine if it is in the resume call-path * add licence references/confirmations for each firmware Wishlist: * Collect all firmware files * store md5sum of each firmware file * reference licenses on a per-md5sum basis rather than the current per-firmware-filename -- request_firmware() fails on resume from suspend https://bugs.launchpad.net/bugs/331415 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 341402] Re: apt-get: segmentation fault (jaunty)
>From the debugging we were doing on #ubuntu+1 it looks like the archive mirror update process may have been responsible for a temporary glitch in some of the files apt was relying upon. http://co.archive.ubuntu.com/ubuntu/ Index of /ubuntu [ICO] NameLast modified Size [DIR] Parent Directory- [ ] Archive-Update-in-Progress-drescher.canonical.com 12-Mar-2009 13:58 1 [ ] Archive-Update-in-Progress-syowa.canonical.com 12-Mar-2009 12:06 1 [DIR] dists/ 04-Dec-2008 22:08 - [DIR] indices/12-Mar-2009 14:03 - [ ] ls-lR.gz12-Mar-2009 13:42 6.4M [DIR] pool/ 14-Jan-2008 22:05 - [DIR] project/13-Feb-2008 14:39 - Apache/2.2.8 (Ubuntu) Server at co.archive.ubuntu.com Port 80 -- apt-get: segmentation fault (jaunty) https://bugs.launchpad.net/bugs/341402 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 292541] Re: Hotmail not working, useragent issue
Jeff you right. Please use opera because this browser is fix this problem and work more than Firefox. -- Hotmail not working, useragent issue https://bugs.launchpad.net/bugs/292541 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 292541] Re: MASTER Hotmail not working, useragent issue
To Alexander Sack after opera an updated hotmail is work but firefox ... complain with hotmail not with us. <<< What does it mean? Why Opera work? -- MASTER Hotmail not working, useragent issue https://bugs.launchpad.net/bugs/292541 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 240356] Re: package mpd 0.13.1-3ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
The needs back-porting to Hardy, where it still causes failure to remove the package. -- package mpd 0.13.1-3ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/240356 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 240356] Re: package mpd 0.13.1-3ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
A quick patch to get the Hardy package to uninstall is to edit /etc/init.d/mpd and in the mpd_stop() function edit the start-stop- daemon command-line, adding "--oknodo", so it looks like this: log_daemon_msg "Stopping $DESC" "$NAME" start-stop-daemon --stop --oknodo --quiet --retry 5 --pidfile "$PIDFILE" \ --exec $DAEMON log_end_msg $? -- package mpd 0.13.1-3ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/240356 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 240356] Re: package mpd 0.13.1-3ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
I've posted a Hardy back-port request in bug #282003 -- package mpd 0.13.1-3ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/240356 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 282019] Re: Wrong group ownership on files in /etc
Confirming on Hardy:
sudo find /etc/ -group 999 -exec ls -l {} \;
-rw-r--r-- 1 root 999 2766 2008-10-10 09:59 /etc/apt/sources.list
-rw-r--r-- 1 root 999 2961 2008-07-24 08:13 /etc/apt/sources.list~
-rw-r--r-- 1 root 999 40 2008-07-08 15:54 /etc/apt/apt.conf.d/00trustcdrom
-rw-r--r-- 1 root 999 247 2008-07-08 15:54 /etc/hosts~
-rw-r--r-- 1 root 999 3 2008-07-08 16:56 /etc/papersize
-rw-r--r-- 1 root 999 49 2008-07-08 16:55 /etc/initramfs-tools/conf.d/resume
-r--r--r-- 1 root 999 1919 2008-07-08 14:39 /etc/default/console-setup
-rw-r--r-- 1 root 999 19 2008-07-08 15:53 /etc/default/locale
-rw-r--r-- 1 root 999 343 2008-10-11 10:58 /etc/popularity-contest.conf
** Changed in: ubuntu
Importance: Undecided => Low
Assignee: (unassigned) => TJ (intuitivenipple)
Status: New => Confirmed
--
Wrong group ownership on files in /etc
https://bugs.launchpad.net/bugs/282019
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 282019] Re: Wrong group ownership on files in /etc
sudo find / -xdev -group 999 -exec ls -l {} \;
-rw-r--r-- 1 root 999 2766 2008-10-10 09:59 /etc/apt/sources.list
-rw-r--r-- 1 root 999 2961 2008-07-24 08:13 /etc/apt/sources.list~
-rw-r--r-- 1 root 999 40 2008-07-08 15:54 /etc/apt/apt.conf.d/00trustcdrom
-rw-r--r-- 1 root 999 247 2008-07-08 15:54 /etc/hosts~
-rw-r--r-- 1 root 999 3 2008-07-08 16:56 /etc/papersize
-rw-r--r-- 1 root 999 49 2008-07-08 16:55 /etc/initramfs-tools/conf.d/resume
-r--r--r-- 1 root 999 1919 2008-07-08 14:39 /etc/default/console-setup
-rw-r--r-- 1 root 999 19 2008-07-08 15:53 /etc/default/locale
-rw-r--r-- 1 root 999 343 2008-10-11 10:58 /etc/popularity-contest.conf
lrwxrwxrwx 1 root 999 11 2008-07-08 15:43 /cdrom -> media/cdrom
lrwxrwxrwx 1 root 999 6 2008-07-08 15:43 /media/cdrom -> cdrom0
total 0
--
Wrong group ownership on files in /etc
https://bugs.launchpad.net/bugs/282019
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 282019] Re: Wrong group ownership on files in /etc
sudo find /var -xdev -group 999 -exec ls -l {} \;
-rw--- 1 root root 6692 2008-07-08 01:22 casper.log
-rw-r--r-- 1 root999 304273 2008-07-08 16:57 initial-status.gz
-rw--- 1 root999 600718 2008-07-08 15:43 partman
-rw--- 1 syslog adm 207080 2008-07-08 16:57 syslog
-rw--- 1 root root 16 2008-07-08 14:37 version
-rw-r--r-- 1 root 999 304273 2008-07-08 16:57
/var/log/installer/initial-status.gz
-rw--- 1 root 999 600718 2008-07-08 15:43 /var/log/installer/partman
-rw-r--r-- 1 root 999 205 2008-07-08 15:54 /var/lib/apt/cdroms.list
-rw-r--r-- 1 root 999 36 2008-07-08 15:53 /var/lib/locales/supported.d/local
--
Wrong group ownership on files in /etc
https://bugs.launchpad.net/bugs/282019
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 145244] Re: [gutsy] libXft library - undefined symbol FT_Library_SetLcdFilter
I've just dealt with a user reporting this problem in Hardy i386. As soon as gdm tried to start gdmgreeter the log-in screen went 'mad' in his words. I connected remotely via ssh and stopped the gdm process. libcairo was reporting symbol_not_found for FT_Library_SetLcdFilter. ldd /usr/lib/libcairo.so.2 revealed that it was linked against /usr/local/lib/libfreetype.so.6 I discovered that recently the user had been trying to build an application of some sort, which had included libfreetype2. When it had been built it had installed to /usr/local/lib/ and then ldconfig had regenerated the dynamic module cache and it took preference to the system-installed version in /usr/lib/. The version in /usr/local/lib/ was much older than the version in /usr/lib/ and didn't include the FT_Library_SetLcdFilter() function. The fix was to remove the libfreetype libraries and sym-links from /usr/local/lib/ and to regenerate the linker cache using: sudo ldconfig -- [gutsy] libXft library - undefined symbol FT_Library_SetLcdFilter https://bugs.launchpad.net/bugs/145244 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 274837] [NEW] Package patches have not been applied
Public bug reported: Today I merged the latest 1.36.0 from SVN r48974 with the debian packaging from 1.34.1-4ubuntu3 for Hardy. I spent some time checking the debian/patches and removing the ones that have been included upstream. I got held up by debian/patches/03-st_mt.patch because it patches debian/rules. The problem is, the content info in the diff has no relation to the current debian/rules. That made me wonder why package- build doesn't throw an error and fail. On investigating the current 1.34.1-4ubuntu3 debian/rules I realised it doesn't have any logic to apply the patches! This seemed weird since various Ubuntu package maintainers have added patches and uploaded the new packages to the repositories. I then looked at the Intrepid package 1.34.1-11ubuntu1. In this package, quilt has been added to debian/rules and the index debian/patches/series is populated with the list of patches. So it looks like the Hardy package we're shipping has had several patches added but never actually applied, with the result that the built binaries do not contain the fixes the patches are intended to provide. ** Affects: boost (Ubuntu) Importance: High Status: Triaged ** Changed in: boost (Ubuntu) Importance: Undecided => High Status: New => Triaged Target: None => ubuntu-8.04.2 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2008-0171 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2008-0172 -- Package patches have not been applied https://bugs.launchpad.net/bugs/274837 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 274837] Re: Package patches have not been applied
Subscribed ubuntu-security since some of the patches that aren't applied are: boost (1.34.1-4ubuntu3) hardy; urgency=low * debian/patches/05_regex_fixes.patch: fix for basic_regex_parser() in boost/regex/v4/basic_regex_parser.hpp to return error on invalid repetition of next state * References CVE-2008-0171 CVE-2008-0172 http://svn.boost.org/trac/boost/changeset/42674 http://svn.boost.org/trac/boost/changeset/42745 -- Jamie Strandboge <[EMAIL PROTECTED]> Thu, 20 Mar 2008 09:03:20 -0400 -- Package patches have not been applied https://bugs.launchpad.net/bugs/274837 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 228296] Re: dscverify does not find Debian keyring
I've been affected by this too trying to use prevu to backport Intrepid packages to Hardy. I've added the ubuntu master and archive keyrings to the script, and am attaching debdiffs for the hardy and intrepid releases. devscripts (2.10.11ubuntu6) hardy; urgency=low * dscverify: Add Ubuntu keyrings (LP: #228296). -- TJ <[EMAIL PROTECTED]> Sun, 28 Sep 2008 23:00:00 +0200 devscripts (2.10.26ubuntu13) intrepid; urgency=low * dscverify: Add Ubuntu keyrings (LP: #228296). -- TJ <[EMAIL PROTECTED]> Sun, 28 Sep 2008 23:00:00 +0200 ** Attachment added: "Hardy debdiff adding Ubuntu keyrings" http://launchpadlibrarian.net/18021853/devscripts_2.10.11ubuntu6.debdiff -- dscverify does not find Debian keyring https://bugs.launchpad.net/bugs/228296 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 228296] Re: dscverify does not find Debian keyring
** Attachment added: "Intrepid debdiff adding Ubuntu keyrings" http://launchpadlibrarian.net/18021858/devscripts_2.10.26ubuntu13.debdiff -- dscverify does not find Debian keyring https://bugs.launchpad.net/bugs/228296 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 228296] Re: dscverify does not find Debian keyring
SRU Justification: Impact: Using dscverify (often embedded in other tools) fails to verify Ubuntu archive keys. The script doesn't add the Ubuntu-installed keyrings (package ubuntu- keyring) to the list of keyrings passed to gpg. testcase: Without the keyrings dscverify will fail, reporting "dscverify: can't find any Debian keyrings" Adding the keyrings to the list results in successful verification of the package. -- dscverify does not find Debian keyring https://bugs.launchpad.net/bugs/228296 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 193593] Re: Audacity effects missing
I've nominated this for Intrepid although we're past Feature-freeze. soundtouch 1.3.1 is in the repository: http://packages.ubuntu.com/intrepid/libsoundtouch1c2 I've also back-ported for Hardy both soundtouch 1.3.1 and soundtouch- enabled audacity. They are available in my repository. The user I did it for reports it works correctly. -- Audacity effects missing https://bugs.launchpad.net/bugs/193593 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
Stefan, sorry I've not been active on this for a while. I got around it by using the latest mainline kernel from my local git repository since I'm currently writing new PCI dynamic resource allocation functionality for mainline. I got caught by this bug again today with the Hardy LiveCD when finally deciding to update the laptop's primary OS from Gutsy to Hardy, doing a clean install and using LUKS encryption with key-file. If you want me to reopen the kernel bugzilla let me know. I'm doing a clean install of Hardy to the laptop (after moving the Gutsy install to a back-up system) so I'll test your kernel with that and let you know the results. -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
Stefan. I have just completed my Hardy installation. I installed " linux- image-2.6.24-19-generic_2.6.24-19.34smb5_amd64.deb " and rebooted three times with kernel /vmlinuz-2.6.24-19-generic root=/dev/mapper/VGencrypted- root ro quiet splash and all three times the system started successfully. dmesg shows: [ 20.495528] ACPI: bus type pci registered [ 20.495598] PCI: Using configuration type 1 [ 20.496713] ACPI: EC: acpi_ec_ecdt_probe() created boot_ed [ 20.496771] ACPI: EC: Look up EC in DSDT [ 20.496773] ACPI: EC: use EC in DSDT [ 20.502636] ACPI: EC: no EC._INI [ 20.504441] ACPI: Interpreter enabled [ 20.504443] ACPI: (supports S0 S3 S4 S5) [ 20.504457] ACPI: Using IOAPIC for interrupt routing [ 20.504566] ACPI: EC: acpi_boot_ec_enable() [ 20.504909] ACPI: EC: non-query interrupt received, switching to interrupt mode [ 20.508199] ACPI: EC: acpi_boot_ec_enable() successful [ 20.526852] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62 [ 20.526855] ACPI: EC: driver started in interrupt mode [ 20.526895] ACPI: PCI Root Bridge [PCI0] (:00) -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 133520] Re: Patch to auto-mount LUKS key-file encrypted volumes
I've updated the patches required for Hardy and the package(s) are available from my PPA. I've modified gnome-mount too, so when a key-file exists the password isn't requested. If the key-file isn't available when gnome-mount first looks it will display the usual gnome LUKS password request dialog. At this point insert the device with the LUKS key-file on (the location of the key-file is specified in /etc/crypttab) then without entering a password press the Connect button and the volume will be unlocked and mounted. https://launchpad.net/~intuitivenipple/+archive Packages: hal - 0.5.11~rc2-1ubuntu8.2~ppa1 gnome-mount - 0.8~svn20080225-0ubuntu5~ppa1 ** Changed in: gnome-mount (Ubuntu) Assignee: TJ (intuitivenipple) => (unassigned) Status: Triaged => Fix Released ** Changed in: hal (Ubuntu) Assignee: TJ (intuitivenipple) => (unassigned) Status: Confirmed => Fix Released -- Patch to auto-mount LUKS key-file encrypted volumes https://bugs.launchpad.net/bugs/133520 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
I've been doing a series of restarts whilst debugging a suspend-lock-up issue, and this problem has occurred several times - sometimes accompanied by a BUG soft lock-up on one of the CPUs. So it looks like the situation has improved slightly but not gone away. When I was running Gutsy I solved it by using the latest mainline kernel (2.6.25+). It's possibly worth doing a git-bisect between 2.6.24-19 and 2.6.25-rc9. I did a basic review of the commits but can't see anything obvious, but then again I may have set the criteria too narrowly: git log --pretty=medium v2.6.24..v2.6.25-rc9 -- drivers/acpi/scan.c -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
Nicolas: I've been running Vaio's for a long time and not seen major problems. The laptop currently affected by this bug is a VGN-FE41Z with Intel T7200 and Nvideo Go 7600. It has been reliable and stable. Stefan: Can you attach the source patch you're using against the current Hardy git HEAD so I can play around more intimately with it? Also, is there a mailing-list exchange on your upstream discussions about this I can review? As I said in an earlier comment, as soon as I began dropping in even the slightest debug reporting the issue went away so I left off work on it. I'm convinced we should be able to identify a change between Hardy and mainline 2.6.25-rc9 that solved this since that was the mainline version I began working with on the PCI DRA functionality where I noticed this issue had gone away. It is of course possible that the underlying issue is still there but a slight timing change hides it. That said, the issue wasn't present in Gutsy either so we have a range of known git tags to work between. -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
I've done a few restarts with 2.6.26-rc9 (Intrepid) without incident. I tried adding "acpi_serialize" to the kernel command line for 2.6.24-19 and it *seemed* to improve matters but then the system experienced a later lock which may or may-not have been related. I tried "max_cpus=1" on the basis that scheduling across SMP cores might be an issue but the failure still occurred. I've also been looking at the changes to the (Group) CPU Scheduler between 2.6.22 .. 2.6.24 and 2.6.24 .. 2.6.26 since (and specifically the differences in the kernel .config files between Gutsy, Hardy, Intrepid, and main-line). If the theory about timing is highlighting a concurrency issue, the cause might be nowhere near the ACPI code. -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
Stefan: You can find a tar.gz of most (~190) decompiled Sony Vaio DSDTs attached to my SNC analysis page at http://tjworld.net/snc/ (the Download all disassembled DSDT (.dsl) files) link). Based on the collection of DSDTs I have I did post a warning to the Ubuntu kernel mailing-list on 12 April 2008 with a list of the models I suspected would be affected, based on my earlier analysis (https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/191137/comments/28) which focused on the use of a STORE() operation in EC._REG(). VGN-AR31S-R0200J6, VGN-AR370E-R0200J6, VGN-C140G-R0030J4, VGN-C1S, VGN-C1ZB-R0034J4, VGN-C22GH-R0080J4, VGN-C240E-R0080J4, VGN-C2S-R0080J4, VGN-C2Z-R0080J4, VGN-FE11H-R0072J3, VGN-FE11H-R0074J3, VGN-FE11M-R0172J3, VGN-FE11M-R0174J3, VGN-FE21H-R0100J3, VGN-FE21M-R0130J3, VGN-FE31M, VGN-FE31M-R0170J3, VGN-FE41E-R0190J3, VGN-FE41M-R0190J3, VGN-FE41Z-R0200J3, VGN-FE45G-R0190J3, VGN-FE550G-R0074J3, VGN-FE590P-R0072J3, VGN-FE660G-R0133J3, VGN-FE670G-R0130J3, VGN-FE690-R0172J3, VGN-FE770G-R0173J3, VGN-FE830, VGN-FE870E-R0190J3, VGN-FE880EH-R0200J3, VGN-FS115M-R0104J0, VGN-FS215B-R0040J1, VGN-FS215E-R0040J1, VGN-FS285H-R0040J1, VGN-FS315E-R0084J1, VGN-FS315H-R0080J1, VGN-FS315S-R0084J1, VGN-FS660W-R0044J1, VGN-FS730W-R0080J1, VGN-FS740W-R0080J1, VGN-FS760W-R0080J1, VGN-FS965F-R0044J2, VGN-FS980-R0044J2, VGN-FZ11M-R0050J7, VGN-N130G-R0020J4, VGN-N230E-R0070J4, VGN-N31Z-R0100J4 Since then, based on more investigation, I wondered if it was more likely the NOTIFY(BAT0) might be the failure point since, if the EC is initialised before the ACPI namespace has been created then it is likely the BAT0 object hasn't been created. I generated a new DSDT that omits the Notify(BAT0) and installed it with update-initramfs. The tests I did indicated the contents of the EC_REG() method weren't the cause, though. I find it strange, however, that it seems that so far only Sony Vaio's are being reported with this issue. Maybe other makes are affected but they're not coming to our attention. In analysing the issue I did notice that there is a two second difference in the timing of calls to EC_REG() between "quiet" and verbose boot sessions. If concurrency/scheduling is the root cause of this issue that would correlate nicely. You can also find some commentary on the small DSDT change I made to fix a battery reporting issue in "ACPI: battery-technology reported as non-rechargeable" http://ubuntuforums.org/showthread.php?t=475801. -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
Stefan, it looks like we're working along the same lines - more of which
later.
Although I could re-open the bugzilla report the problem is, the first
question asked is "does this affect the latest version?" and the answer
is "NO" - not since 2.6.25-rc9 that I know about, and possibly earlier.
With that I doubt there will be much interest in solving this since
it'll be a case of "use the latest kernel".
I'd like to get a bit further in understanding the issue first.
I've attached a git-diff patch "ec_debug ACPI EC delayed printk()
messaging" against the current ubuntu-hardy HEAD (commit
135a18b9c37be8...).
It introduces buffered printk() messages via calls to ec_debug(const
char *func, const char *format, args...). It allows us to add as many
debug messages as we want without affecting the timing because they are
sent to the console immediately. It collects the messages in the buffer
and auto-flushes if it gets full and more importantly, immediately after
the 2 known code-points when the EC either succeeds or fails.
The resulting /var/log/dmesg entries need a bit of manual fix-up since
the messages are out of time-sequence and have the time-of-printing
prefixed too. It is pretty simple to use an editor to tidy it up and put
the messages back in sequence though. Here's an example of a successful
boot with 2.6.24.3 (manually built ubuntu-hardy tree). I wish there was
an easy way to capture a failed boot, but non of the Vaio's have serial
ports so we can't capture via a serial console. My usual method is to
aim the DV-camcorder at the screen and record the output - I'll try that
method later today.
It seems to show that the init_subsys for acpi_init() and
acpi_scan_init() are overlapping. I need to add additional messages to
determine which subsys is responsible for the call to
acpi_boot_ec_enable(). I'll try to make progress later today and report
back.
In the meantime, the attached patch is available if you want to drop in
your own debug tracing messages to chase down other possibilities.
[ 23.109039] ACPI: bus type pci registered
[ 23.109168] PCI: Using configuration type 1
[ 23.110342] ACPI: acpi_ec_ecdt_probe()
[ 23.110345] ACPI: EC: Look up EC in DSDT
[ 23.117192] ACPI: Interpreter enabled
[ 23.117254] ACPI: (supports S0 S3 S4 S5)
[ 23.117510] ACPI: Using IOAPIC for interrupt routing
[ 23.117676] ACPI: acpi_boot_ec_enable()
[ 23.117677] ACPI: ec_install_handlers()
[ 23.117713] ACPI: acpi_ec_space_handler()
[ 23.117714] ACPI: acpi_ec_read(, , )
[ 23.117715] ACPI: acpi_ec_transaction(, 128, , 1, , 1, 0)
[ 23.117717] ACPI: acpi_ec_wait(, 2, 0)
[ 23.117718] ACPI: acpi_ec_wait() else
[ 23.117720] ACPI: acpi_ec_transaction_unlocked(, 128, , 1,
, 1, 0)
[ 23.117723] ACPI: acpi_ec_wait(, 2, 0)
[ 23.117724] ACPI: acpi_ec_wait() else
[ 23.117940] ACPI: acpi_ec_wait(, 1, 0)
[ 23.117941] ACPI: acpi_ec_wait() else
[ 23.117999] ACPI: acpi_ec_gpe_handler()
[ 23.118002] ACPI: EC: non-query interrupt received, switching to interrupt
mode
[ 23.118310] ACPI: acpi_ec_gpe_handler()
[ 23.118322] ACPI: acpi_ec_space_handler()
[ 23.118323] ACPI: acpi_ec_read(, , )
[ 23.118324] ACPI: acpi_ec_transaction(, 128, , 1, , 1, 0)
[ 23.118325] ACPI: PCI Root Bridge [PCI0] (:00)
[ 23.140534] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
[ 23.140598] ACPI: EC: driver started in interrupt mode
My analysis of the call paths:
init/main.c::start_kernel()
init/main.c::rest_init()
init/main.c::kernel_init()
init/main.c::do_basic_setup()
init/main.c::do_initcalls()
initcall_t *call;
for (call = __initcall_start; call < __initcall_end; call++) {
$ objdump -t builds/ubuntu-hardy/vmlinux | egrep
'__initcall_(acpi_init|acpi_scan_init|acpi_ec_init)'
80624dc8 l O .initcall.init 0008 __initcall_acpi_init4
80624dd0 l O .initcall.init 0008
__initcall_acpi_scan_init4
80624dd8 l O .initcall.init 0008
__initcall_acpi_ec_init4
drivers/acpi/bus.c::acpi_init()
drivers/acpi/bus.c::acpi_bus_init()
drivers/acpi/ec.c::acpi_ec_ecdt_probe()
drivers/acpi/ec.c::make_acpi_ec()
drivers/acpi/tables/tbxface.c::acpi_get_table()
drivers/acpi/ec.c::ec_install_handlers()
if (ec->handlers_installed) return 0;
drivers/acpi/events/evxface.c::acpi_install_gpe_handler()
drivers/acpi/events/evxfevnt.c::acpi_set_gpe_type()
drivers/acpi/events/evxfevnt.c::acpi_enable_gpe()
drivers/acpi/events/evgpe.c::acpi_ev_enable_gpe()
drivers/acpi/hardware/hwgpe.c::acpi_hw_write_gpe_enable_reg()
drivers/acpi/events/evxfregn.c::acpi_install_address_space_handler()
ec->handlers_installed = 1;
}
}
}
}
subsys_initcall(acpi_init)
drivers/acpi/scan.c::acpi_scan_init()
drivers/acpi/ec.c::acpi_boot_ec_enable()
if (!boot_ec || boot_ec->handlers_installed) return 0;
drivers/acpi/ec.c::ec_install_handlers()
if (ec->handlers_installed) ret
[Bug 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
** Attachment removed: "ec_debug ACPI EC delayed printk() messaging" http://launchpadlibrarian.net/15943102/ec_debug.patch ** Attachment added: "ec_debug ACPI EC delayed printk() messaging" http://launchpadlibrarian.net/15944023/ec_debug.patch -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
** Attachment removed: "ec_debug ACPI EC delayed printk() messaging" http://launchpadlibrarian.net/15944023/ec_debug.patch -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
I've improved the ec_debug code (and attached the update) so the init subsystem is reported, and it correctly deals with potential vprintk() buffer over-runs by flushing the ec_messages buffer in blocks of no more than 1020 characters. I added a dump_stack() followed by mdelay() but even with the video camera recording it the reports scroll up the screen far too fast (and blurred) to be readable even on freeze-frame. >From a successful session however, here's the relevant part: [ 45.084736] ACPI: bus type pci registered [ 45.084867] PCI: Using configuration type 1 [ 45.086043] ACPI: EC: acpi_init acpi_ec_ecdt_probe() [ 45.086045] ACPI: EC: acpi_init make_acpi_ec() [ 45.086046] ACPI: EC: Look up EC in DSDT [ 45.092877] ACPI: Interpreter enabled [ 45.092939] ACPI: (supports S0 S3 S4 S5) [ 45.093194] ACPI: Using IOAPIC for interrupt routing [ 45.093362] ACPI: EC: acpi_scan_init acpi_boot_ec_enable() [ 45.093363] ACPI: EC: acpi_scan_init acpi_boot_ec_enable() call ec_install_handlers(boot_ec) [ 45.093364] ACPI: EC: acpi_scan_init ec_install_handlers() ec->handlers_installed=0 [ 45.093365] ACPI: EC: acpi_scan_init ec_install_handlers() acpi_install_gpe_handler() succeeded [ 45.093400] ACPI: EC: acpi_scan_init acpi_ec_space_handler() [ 45.093402] ACPI: EC: acpi_scan_init acpi_ec_read(, , ) [ 45.093403] ACPI: EC: acpi_scan_init acpi_ec_transaction(, 128, , 1, , 1, 0) [ 45.093404] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.093405] ACPI: EC: acpi_scan_init acpi_ec_wait() else [ 45.093408] ACPI: EC: acpi_scan_init acpi_ec_transaction_unlocked(, 128, , 1, , 1, 0) [ 45.093411] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.093412] ACPI: EC: acpi_scan_init acpi_ec_wait() else [ 45.093559] ACPI: EC: acpi_scan_init acpi_ec_wait(, 1, 0) [ 45.093560] ACPI: EC: acpi_scan_init acpi_ec_wait() else [ 45.093618] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.093622] ACPI: EC: non-query interrupt received, switching to interrupt mode [ 45.093930] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.093942] ACPI: EC: acpi_scan_init acpi_ec_space_handler() [ 45.093943] ACPI: EC: acpi_scan_init acpi_ec_read(, , ) [ 45.093944] ACPI: EC: acpi_scan_init acpi_ec_transaction(, 128, , 1, , 1, 0) [ 45.093945] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.093948] ACPI: EC: acpi_scan_init acpi_ec_transaction_unlocked(, 128, , 1, , 1, 0) [ 45.093951] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.094339] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.094350] ACPI: EC: acpi_scan_init acpi_ec_wait(, 1, 0) [ 45.094777] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.094800] ACPI: EC: acpi_scan_init acpi_ec_space_handler() [ 45.094801] ACPI: EC: acpi_scan_init acpi_ec_read(, , ) [ 45.094802] ACPI: EC: acpi_scan_init acpi_ec_transaction(, 128, , 1, , 1, 0) [ 45.094803] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.094806] ACPI: EC: acpi_scan_init acpi_ec_transaction_unlocked(, 128, , 1, , 1, 0) [ 45.094809] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.095173] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.095185] ACPI: EC: acpi_scan_init acpi_ec_wait(, 1, 0) [ 45.095484] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.095551] ACPI: EC: acpi_scan_init acpi_ec_space_handler() [ 45.095552] ACPI: EC: acpi_scan_init acpi_ec_read(, , ) [ 45.095553] ACPI: EC: acpi_scan_init acpi_ec_transaction(, 128, , 1, , 1, 0) [ 45.095554] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.095557] ACPI: EC: acpi_scan_init acpi_ec_transaction_unlocked(, 128, , 1, , 1, 0) [ 45.095560] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.095767] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.095778] ACPI: EC: acpi_scan_init acpi_ec_wait(, 1, 0) [ 45.096217] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.096235] ACPI: EC: acpi_scan_init acpi_ec_space_handler() [ 45.096236] ACPI: EC: acpi_scan_init acpi_ec_read(, , ) [ 45.096237] ACPI: EC: acpi_scan_init acpi_ec_transaction(, 128, , 1, , 1, 0) [ 45.096238] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.096241] ACPI: EC: acpi_scan_init acpi_ec_transaction_unlocked(, 128, , 1, , 1, 0) [ 45.096244] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.096598] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.096609] ACPI: EC: acpi_scan_init acpi_ec_wait(, 1, 0) [ 45.096925] ACPI: EC: acpi_scan_init acpi_ec_gpe_handler() [ 45.102523] ACPI: EC: acpi_scan_init acpi_ec_space_handler() [ 45.102524] ACPI: EC: acpi_scan_init acpi_ec_read(, , ) [ 45.102525] ACPI: EC: acpi_scan_init acpi_ec_transaction(, 128, , 1, , 1, 0) [ 45.102526] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.102529] ACPI: EC: acpi_scan_init acpi_ec_transaction_unlocked(, 128, , 1, , 1, 0) [ 45.102532] ACPI: EC: acpi_scan_init acpi_ec_wait(, 2, 0) [ 45.102762] ACPI: EC: acpi_scan_ini
[Bug 191137] Re: [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected
The additional debug messages were enough to pinpoint the root-cause of the issue and I had a proof-of-concept patch succeed in fixing the issue last thing yesterday. Today I worked through the commit logs from mainline and located the two commits that fix the issue in later kernels. I built and tested the kernel with those commit patches applied and couldn't provoke the bug. Then, reviewing the comments on this bug, I realised that Stefan had referred to the same two commits on 9th July but, because there was no explicit link to a test kernel in his comment, I'd somehow overlooked it and not tried them. I've currently got my PPA building kernel packages with the patches applied so that others can test the kernel easily. If/when the builds are complete please test the kernel package by adding my PPA to your apt sources: $ sudo su $ echo "deb http://ppa.launchpad.net/intuitivenipple/ubuntu hardy main" > /etc/apt/sources.list.d/intuitivenipple-ppa.list $ apt-get update $ exit Update Manager should now discover the package and offer it for installation. In case the PPA builds fail (kernel-builds are still a dark art!) I'm also building all binary packages. Once built they will be found at http://tjworld.net/ubuntu/bugs/lp191137/ For reference, the fix (if it solves everyone else's problems too) is to cherry-pick the commits: b3b233c7d948a5f55185fb5a1b248157b948a1e5 Thu Jan 10 20:50:12 2008 -0500 ACPI: EC: Some hardware requires burst mode to operate properly 3e71a87d03055de0b8c8e42aba758ee6494af083 Thu Jan 10 20:49:14 2008 -0500 ACPI: EC: Do the byte access with a fast path I was trying to figure out why they didn't get into the ubuntu-hardy tree since according to the logs there were several pulls from upstream after the commit date. Please report your experiences with this test kernel package. -- [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet' option is enabled or AC power is connected https://bugs.launchpad.net/bugs/191137 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 198292] Re: Hardy upgrade - motion halts upgrade
The revised package appears to still have problems. However, there is a newer upstream version available. I've taken the opportunity to repackage and bug-fix it. It is available from my PPA for Intrepid, Hardy, Gutsy and Feisty: http://ppa.launchpad.net/intuitivenipple/ubuntu motion (3.2.10.1-0ubuntu1~ppa3) hardy; urgency=low * Fixed init script not running process in background (default /etc/motion/motion.conf had "daemon off" via an inherited debian/rules command * Fixed init script override for location of PID file running as non-root (/var/run/motion) so it doesn't rely on the init script location coinciding with the setting in /etc/motion/motion.conf -- TJ <[EMAIL PROTECTED]> Sun, 20 Jul 2008 16:30:00 +0100 motion (3.2.10.1-0ubuntu1~ppa2) hardy; urgency=low * Fixed 64-bit pointer-to-int conversions using C99's LP64 convention * Do not start daemon during installation * Converted package to use CDBS and simple-patchsys -- TJ <[EMAIL PROTECTED]> Sun, 20 Jul 2008 15:00:00 +0100 -- Hardy upgrade - motion halts upgrade https://bugs.launchpad.net/bugs/198292 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 250355] [NEW] Add udev rules to auto-dim panel when on battery power
Public bug reported:
Binary package hint: smartdimmer
I've added a udev script to auto-dim the back-light to 50% when the
charger is removed, and return it to 100% when the charger is attached.
The file is /etc/udev/rules.d/80-smartdimmer.rules
# NVidia backlight control using smartdimmer
# Copyright July 2008, TJ <[EMAIL PROTECTED]>
# Licensed under the GNU General Public License, v2
ACTION=="change", SUBSYSTEM=="power_supply", ATTR{type}=="Battery",
ATTR{status}=="Discharging", RUN+="/usr/bin/smartdimmer -s 12"
ACTION=="change", SUBSYSTEM=="power_supply", ATTR{type}=="Battery",
ATTR{status}=="Charging", RUN+="/usr/bin/smartdimmer -s 21"
** Affects: smartdimmer (Ubuntu)
Importance: Wishlist
Status: New
** Changed in: smartdimmer (Ubuntu)
Importance: Undecided => Wishlist
--
Add udev rules to auto-dim panel when on battery power
https://bugs.launchpad.net/bugs/250355
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 198292] Re: Hardy upgrade - motion halts upgrade
@Martin: Did not test a Gutsy upgrade. Tested hardy-proposed clean install to hardy (x86_64). The proposed 'fix' of adding the -b (--background) switch to start-stop- daemon in /etc/init.d/motion for its 'start' case will only force the daemon to background the motion shell process - it doesn't deal with motion's specific behaviour of forking itself, which is what *should* happen. The problem that causes motion to launch during installation is caused by the debian/rules binary-arch: "dh_installinit" statement which would need to pass the "--no-start" argument to avoid motion starting during install. This is a *good thing* to do since the generic '/etc/motion/motion.conf' may not be configured correctly for the system's video devices. Install will succeed when motion.conf is *incorrect* since motion will exit immediately. The *reason* motion doesn't fork itself into the background is the debian/rules install: statement which uses sed to change the installed '/etc/motion/motion.conf' statement "daemon on" to "daemon off" I packaged 3.2.10-1 (a security bug-fix release) simply because I wanted the latest version and found the latest 3.2.10-1 motion-supplied package suffers the same problems as this current Ubuntu package. At that time I didn't know about this bug. I found it here only after I'd finished packaging and building the new version. I wasn't suggesting my changes/package were candidates for SRU but they're there if someone wants them. Although adding CDBS on its own may not be a reason for an SRU, I'd suggest it *is* if it is needed to apply patches to the original source when the package currently has *no* patch system at all, and source-code patches need to be applied. In this case I needed to fix a pointer-to-int conversion bug for 64-bit builds because motion makes extensive use of pointers converted to relative offsets of struct members in various 'struct context' memory spaces. All the fixes I've done are fully described in my previous comment in the Changelog quotes. -- Hardy upgrade - motion halts upgrade https://bugs.launchpad.net/bugs/198292 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
