[Bug 1865088] Re: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
I notice that the output from setupcon mentions loading the font twice.
That seems to correspond to this fragment of code in setupcon:
# FONTFILES
FONTFILES=''
if [ "$FONT" ]; then
for f in $FONT; do
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi
It looks to me like this will add each font file to FONTFILES twice,
once in the first line of the loop body, and once in the last.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865088
Title:
setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP:
Invalid argument"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865088] [NEW] setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
Public bug reported: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ** Attachment added: "Output from "setupcon -v test2"" https://bugs.launchpad.net/bugs/1865088/+attachment/5331723/+files/setupcon.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865088 Title: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691218] [NEW] PXELINUX always selects default option
Public bug reported: I have a DHCP/TFTP server that's used for network installations. When I tried to switch it to use the version of PXELINUX supplied with Ubuntu 16.04 (3:6.03+dfsg-11ubuntu1), I found that whatever I typed at the PXELINUX command-line, PXELINUX would boot the default image. Replacing the Ubuntu PXELINUX binaries with the official upstream binaries caused the problem to go away. More specifically, I installed /usr/lib/PXELINUX/pxelinux.0 and /usr/lib/syslinux/modules/bios/ldlinux.c32 into my /tftpboot directory. To avoid breaking the existing PXELINUX 4.03 installation, I installed pxelinux.0 as "test.0" and configured my DHCP server to provide that as a filename to my test server. I put the following configuration file in /tftpboot/pxelinux.cfg/AC1CD020 (the correct name for the IP address of my server): DEFAULT mongoose PROMPT 1 LABEL mongoose KERNEL mongoose LABEL kitten KERNEL kitten When I boot my test server, pressing [TAB] twice at the PXELINUX prompt lists both "mongoose" and "kitten" as available images, but whatever I type, PXELINUX says "Loading mongoose... failed: No such file or directory" (see attached screenshot), indicating that PXELINUX was trying to load "mongoose" every time. When I replace test.0 and ldlinux.c32 with pxelinux.0 and ldlinux.c32 from the official PXELINUX 6.03 release, I get the behaviour I expect, namely that the error message mentions the name of the image I selected. While my test involves images that don't exist, I get the same behaviour for more normal configuration files that load actual kernels. I also get the same behaviour from two different PXE implementations (VMware and a Sun Fire X4150). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pxelinux 3:6.03+dfsg-11ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 16 18:37:49 2017 Dependencies: syslinux-common 3:6.03+dfsg-11ubuntu1 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all SourcePackage: syslinux UpgradeStatus: Upgraded to xenial on 2017-05-11 (5 days ago) ** Affects: syslinux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Console screenshot demonstrating problem" https://bugs.launchpad.net/bugs/1691218/+attachment/4877699/+files/index.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691218 Title: PXELINUX always selects default option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1691218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828895] Re: Bash loses track of background children sometimes
Just a quick note: having moved some affected systems back to Ubuntu, this bug has just manifested in production on Ubuntu 16.04 LTS: /opt/dump/bin/dump_multi: line 11: wait: pid 56652 is not a child of this shell My test script above no longer demonstrates it though. I'll see if I can come up with one that does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828895 Title: Bash loses track of background children sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/828895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] Re: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias)
Tested against 4.1.0-040100rc7.201506080035. The dell-led module doesn't autoload unless I put in place the workaround modprobe.d file metioned in the original report. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1-rc7 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] Re: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias)
apport information ** Tags added: apport-collected staging ** Description changed: On my Latitude 2110, the dell_led driver is useful for controlling the LED on the lid. However, the driver doesn't load automatically on boot, and so /sys/class/leds/dell::lid doesn't exist. I can load the module manually (with sudo modprobe dell_led), or I can put this line in /etc/modprobe.d/local-dell-led.conf: alias wmi:F6E4FE6E-909D-47CB-8BAB-C9F6F2F8D396 dell_led If I do the latter, then the module loads automatically at boot. I note that modinfo dell_led says: alias: wmi:F6E4FE6E-909D-47cb-8BAB-C9F6F2F8D396 Note that the 47cb there is in lower case. I suspect that this is the cause of the problem. I also note that the hp_wmi driver has a wmi: alias with lower-case letters in, so it may require a similar fix. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33~14.04.2 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 6 16:21:39 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1641 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 SourcePackage: linux-lts-utopic UpgradeStatus: Upgraded to trusty on 2014-08-15 (112 days ago) + --- + ApportVersion: 2.14.1-0ubuntu3.11 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: bjh21 2415 F pulseaudio + CurrentDesktop: Unity + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-motts-20100121-3 + DistroRelease: Ubuntu 14.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=5f11e886-4c98-43d9-8d51-6ab48f0bff3f + InstallationDate: Installed on 2010-06-09 (1812 days ago) + InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 + MachineType: Dell Inc. Latitude 2110 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic root=UUID=a7f66818-5a12-4932-922a-b05d92593b24 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-38-generic N/A + linux-backports-modules-3.16.0-38-generic N/A + linux-firmware 1.127.12 + StagingDrivers: rts5208 + Tags: trusty staging + Uname: Linux 3.16.0-38-generic i686 + UpgradeStatus: Upgraded to trusty on 2014-08-15 (284 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark + _MarkForUpload: True + dmi.bios.date: 03/09/2010 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A00 + dmi.board.name: 0N61H4 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/09/2010:svnDellInc.:pnLatitude2110:pvr:rvnDellInc.:rn0N61H4:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Latitude 2110 + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405347/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405356/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405348/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405359/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405349/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405350/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405353/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405358/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405362/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405351/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405352/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405360/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405357/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405361/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405354/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1399952/+attachment/4405355/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428288] [NEW] dist-upgrade failed: apache2 postinst failed on absolute symlinks in mods-enabled
Public bug reported:
I tried to upgrade from 12.04 LTS to 14.04 LTS using do-release-
upgrade. The system had previously (a few minutes previously) been
upgraded from 10.04 LTS to 12.04 LTS. As far as I can tell, the first
upgrade was successful, but the second failed when trying to configure
apache2:
disable obsolete module dav_fs
Module dav_fs disabled.
disable obsolete module dav
ERROR: The following modules depend on dav and need to be disabled first:
dav_svn
dpkg: error processing package apache2 (--configure):
subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports has already been reached
…
Please report this bug in a browser at
http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug
and attach the files in /var/log/dist-upgrade/ to the bug report.
installArchives() failed
I think this is caused by the fact that I have absolute symlinks in
/etc/apache2/mods-enabled:
root@sigurd:/home/bjh21# ls -o /etc/apache2/mods-enabled/dav*
lrwxrwxrwx 1 root 36 Nov 12 2012 /etc/apache2/mods-enabled/dav.load -
/etc/apache2/mods-available/dav.load
lrwxrwxrwx 1 root 30 Nov 12 2012 /etc/apache2/mods-enabled/dav_svn.conf -
../mods-available/dav_svn.conf
lrwxrwxrwx 1 root 40 Nov 12 2012 /etc/apache2/mods-enabled/dav_svn.load -
/etc/apache2/mods-available/dav_svn.load
The code that detects obsolete modules in apache2.postinst looks like it
will (accidentally) not work with absolute symlinks:
refresh_modules()
{
if we_are_upgrading_from_wheezy $@ [ -d /etc/apache2/mods-enabled/ ]
; then
shopt -s nullglob
for link in /etc/apache2/mods-enabled/*.load ; do
target=$(readlink $link) || true
if [ -z $target ] ; then
continue
fi
module=$(basename $link | sed 's/\.load//') ||
true
if [ ! -e /etc/apache2/mods-enabled/$target ] ; then
echo disable obsolete module $module
a2dismod -m -q $module
etc.
Concatenating the symlink contents with the directory name only works
for relative symlinks. A simpler approach would be simply to check the
link for existence, which will treat broken links as non-existent:
if [ ! -e ${link} ]; then
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: Contents of /var/log/dist-upgrade, as requested by error
message
https://bugs.launchpad.net/bugs/1428288/+attachment/4334616/+files/dist-upgrade.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1428288
Title:
dist-upgrade failed: apache2 postinst failed on absolute symlinks in
mods-enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1428288/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: [Dell Latitude 2110] Clicking brightness key once increments brightness as if pressed multiple times
A workaround: the extra key events can be disabled by creating /etc/udev/hwdb.d/70-keyboard.hwdb containing: keyboard:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*2110:pvr* KEYBOARD_KEY_85=unknown # Brightness Down, also emitted by acpi-video, ignore KEYBOARD_KEY_86=unknown # Brightness Up, also emitted by acpi-video, ignore This is based on the existing rules for the Dell Inspiron 1520. If I also disable video.brightness_switch_enabled, then I get a backlight that changes brightness by one step for each keypress. I have had two rather worrying hangs while testing this, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: [Dell Latitude 2110] Clicking brightness key once increments brightness as if pressed multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] [NEW] [Dell Latitude 2110] dell_led driver does not auto-load (bad alias)
Public bug reported: On my Latitude 2110, the dell_led driver is useful for controlling the LED on the lid. However, the driver doesn't load automatically on boot, and so /sys/class/leds/dell::lid doesn't exist. I can load the module manually (with sudo modprobe dell_led), or I can put this line in /etc/modprobe.d/local-dell-led.conf: alias wmi:F6E4FE6E-909D-47CB-8BAB-C9F6F2F8D396 dell_led If I do the latter, then the module loads automatically at boot. I note that modinfo dell_led says: alias: wmi:F6E4FE6E-909D-47cb-8BAB-C9F6F2F8D396 Note that the 47cb there is in lower case. I suspect that this is the cause of the problem. I also note that the hp_wmi driver has a wmi: alias with lower-case letters in, so it may require a similar fix. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33~14.04.2 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 6 16:21:39 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1641 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 SourcePackage: linux-lts-utopic UpgradeStatus: Upgraded to trusty on 2014-08-15 (112 days ago) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399952] Re: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias)
Tested against upstream kernel 3.18.0-031800rc7-generic; driver doesn't autoload without the extra alias line. ** Tags added: kernel-bug-exists-upstream-3.18rc7 ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399952 Title: [Dell Latitude 2110] dell_led driver does not auto-load (bad alias) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1399952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392907] Re: Turn Bluetooth on or off instructions outdated
Right. Testing from a 14.10 installation image, I get a very similar menu (attached) to the 14.04 one. So I think this bug exists at least up to 14.10. My running 14.04 LTS system was first installed as 9.10, which I think may have predated Unity, and I've installed fvwm2 at some point. I don't think I've ever installed xfce, but I may have. ** Attachment added: Bluetooth menu in 14.10 https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1392907/+attachment/4274817/+files/bt1410.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392907 Title: Turn Bluetooth on or off instructions outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1392907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392907] Re: Turn Bluetooth on or off instructions outdated
My Bluetooth menu is very different from yours, as you can see from the attachment. I assume this is because things have changed since Ubuntu 14.04, and now the documentation is correct again. I'm sorry I didn't think to try a newer release before reporting the problem. ** Attachment added: Bluetooth menu on Ubuntu 14.04. https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1392907/+attachment/4274235/+files/btmenu.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392907 Title: Turn Bluetooth on or off instructions outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1392907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
I've just tested in Precise (kernel 3.2.0-72-generic) and the same problem occurs there as well. So the problem did occur in prior releases. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
Yes, I can adjust brightness. The brightness slider in the Brightness and Lock page of System Settings works perfectly. The brightness-up and brightness-down keys (Fn+Up and Fn+Down) work, but they usually change the brightness by multiple steps. It seems that this duplication of keypresses across multiple input devices may be one of the causes of this problem. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: [Dell Latitude 2110] Clicking brightness key once increments brightness as if pressed multiple times
Reported upstream: http://article.gmane.org/gmane.linux.acpi.devel/72409 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: [Dell Latitude 2110] Clicking brightness key once increments brightness as if pressed multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272500/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272512/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272509/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272502/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272504/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272501/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272511/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272510/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272508/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272506/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
apport information ** Tags added: apport-collected staging ** Description changed: According to https://wiki.ubuntu.com/Hotkeys/Troubleshooting, If the events are reported by more than one input device then report a kernel bug (Ubuntu linux package) because it should only send the event on one device. On my Latitude 2110, the brightness control keys (Fn+Up and Fn+Down) seem to appear through two different devices, /dev/input/event3 (AT Translated Set 2 keyboard) and /dev/input/event4 (Video Bus). The keys also control the screen brightness, even in a text console. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33~14.04.2 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sun Nov 30 17:02:52 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1635 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 SourcePackage: linux-lts-utopic UpgradeStatus: Upgraded to trusty on 2014-08-15 (106 days ago) + --- + ApportVersion: 2.14.1-0ubuntu3.5 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: bjh21 2495 F pulseaudio + CurrentDesktop: Unity + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-motts-20100121-3 + DistroRelease: Ubuntu 14.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=5f11e886-4c98-43d9-8d51-6ab48f0bff3f + InstallationDate: Installed on 2010-06-09 (1636 days ago) + InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 + MachineType: Dell Inc. Latitude 2110 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=a7f66818-5a12-4932-922a-b05d92593b24 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-25-generic N/A + linux-backports-modules-3.16.0-25-generic N/A + linux-firmware 1.127.8 + StagingDrivers: rts5208 + Tags: trusty staging + Uname: Linux 3.16.0-25-generic i686 + UpgradeStatus: Upgraded to trusty on 2014-08-15 (108 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark + WifiSyslog: + Dec 1 21:57:47 sole kernel: [ 713.837172] init: systemd-logind main process (504) killed by TERM signal + Dec 1 21:57:58 sole kernel: [ 724.781339] systemd-udevd[5391]: starting version 204 + _MarkForUpload: True + dmi.bios.date: 03/09/2010 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A00 + dmi.board.name: 0N61H4 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/09/2010:svnDellInc.:pnLatitude2110:pvr:rvnDellInc.:rn0N61H4:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Latitude 2110 + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272498/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272503/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272499/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272505/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
I've run the command as requested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1397699/+attachment/4272507/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
I've tested with the latest upstream kernel, and the bug exists there too. bjh21@sole:~$ uname -a Linux sole 3.18.0-031800rc7-generic #201411302035 SMP Mon Dec 1 01:58:20 UTC 2014 i686 i686 i686 GNU/Linux ** Attachment added: Output from evtest /dev/input/event3 on 3.18.0-rc7 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+attachment/4272525/+files/evtest3.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
** Attachment added: Output from evtest /dev/input/event4 on 3.18.0-rc7 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+attachment/4272526/+files/evtest4.out ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.18-rc7 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] [NEW] Dell Latitude 2110: Brightness keys come through two input devices
Public bug reported: According to https://wiki.ubuntu.com/Hotkeys/Troubleshooting, If the events are reported by more than one input device then report a kernel bug (Ubuntu linux package) because it should only send the event on one device. On my Latitude 2110, the brightness control keys (Fn+Up and Fn+Down) seem to appear through two different devices, /dev/input/event3 (AT Translated Set 2 keyboard) and /dev/input/event4 (Video Bus). The keys also control the screen brightness, even in a text console. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33~14.04.2 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sun Nov 30 17:02:52 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1635 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 SourcePackage: linux-lts-utopic UpgradeStatus: Upgraded to trusty on 2014-08-15 (106 days ago) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Attachment added: Output from evtest /dev/input/event3 https://bugs.launchpad.net/bugs/1397699/+attachment/4271442/+files/evtest3.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
** Attachment added: Output from evtest /dev/input/event4 https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+attachment/4271445/+files/evtest4.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
** Attachment added: Output from udevadm info --export-db https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+attachment/4271446/+files/udev-db.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
** Attachment added: Outut from xkbcomp -xkb :0 https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+attachment/4271449/+files/xkbcomp.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
** Attachment added: Output from setxkbmap -print https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+attachment/4271450/+files/xkbmap.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
** Attachment added: Output sudo lsinput https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+attachment/4271448/+files/lsinput.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397699] Re: Dell Latitude 2110: Brightness keys come through two input devices
** Attachment added: Output from dmesg https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+attachment/4271447/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397699 Title: Dell Latitude 2110: Brightness keys come through two input devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397142] Re: Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee
I've made a small program out of parts of bluetoothd that demonstrates this problem without the need for any special hardware. Simply compile it and run it (as root) and it will create a virtual keyboard that generates play and pause keypresses at 5.1-second intervals. If you have Rhythmbox or Banshee playing when you start the test program, the first pause will pause the media player, but the subsequent play will not re-start it. ** Attachment added: Test program to generate key events like bluetoothd does https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397142/+attachment/4270682/+files/avbtntest.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397587] [NEW] Volume display does not update when changing default sink
Public bug reported: On my laptop I often have two PulseAudio sinks, the on-board audio (alsa_output.pci-_00_1b.0.analog-stereo) and a Bluetooth speaker (bluez_sink.8C_DE_52_2F_AF_F3). I can choose the default destination for sound output using the Sound pane of System Settings, and I can separately change the volume setting of each sink using the paman application. When I adjust the volume using the sound menu, it affects the default sink. However, when I change to a different default sink, the sound menu does not update and continues displaying the volume for the previously-selected sink. Only if I change the volume setting for one of the sinks (e.g. using paman) does the sound menu update to show the new volume level. To reproduce: Find a system with more than one sound sink. Launch paman and open the Properties window for each sink. Also open the Sound pane of System Settings. Set one sink to maximum volume and one to minumum. Switch between outputs using Systems Settings, and note that the sound menu does not update to match the different volume settings of the two sinks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Nov 29 19:10:52 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1634 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 SourcePackage: indicator-sound UpgradeStatus: Upgraded to trusty on 2014-08-15 (105 days ago) ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397587 Title: Volume display does not update when changing default sink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1397587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397142] Re: Sony SRS-BTM8 play/pause key not fully effective in Banshee
A quick additional not: using xdotool key XF86AudioPlay and xdotool key XF86AudioPause works correctly, so maybe it's not all media keys that are broken and there's something odd about my Bluetooth one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Sony SRS-BTM8 play/pause key not fully effective in Banshee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798983] Re: Banshee hung when deleting an equalizer setting
Sorry for the long delay. I just noticed this bug in my list and have reproduced it with the Banshee in Ubuntu 14.04, Banshee 2.6.2: [Ubuntu 14.04.1 LTS (linux-gnu, i686) @ 2014-08-12 14:01:00 UTC]. I've attached the terminal output I get when running banshee --debug and reproducing the problem. ** Attachment added: banshee --debug output when reproducing bug https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/798983/+attachment/4270067/+files/banshee-output -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798983 Title: Banshee hung when deleting an equalizer setting To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/798983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397142] Re: Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee
** Summary changed: - Sony SRS-BTM8 play/pause key not fully effective in Banshee + Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798983] Re: Banshee hung when deleting an equalizer setting
Marked confirmed because I've supplied debug output and bug is described as really easy to trigger by someone else at https://bugzilla.gnome.org/show_bug.cgi?id=653025 ** Changed in: banshee (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798983 Title: Banshee hung when deleting an equalizer setting To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/798983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397142] [NEW] Sony SRS-BTM8 play/pause key not fully effective in Banshee
Public bug reported: I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly well with Ubuntu. It also has a play/pause button and that doesn't work so well. I think the problem lies in unity-settings- daemon. To demonstrate that the Bluetooth side is working, if I switch to a text console and run evtest /dev/input/event9, then when pressing the button I get events for KEY_PLAYCD if the speaker is not playing anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing something. However, within the Unity desktop I find that if I'm running Banshee or Rhythmbox then pressing the button successfully pauses the music, but doesn't start it playing again. If I run xev and give it the keyboard focus while testing this (so xev sees all ungrabbed keystrokes) then it sees only a KeyRelease event for XF86AudioPause, but both KeyPress and KeyRelease events for XF86AudioPlay. I've attached the full output from xev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Thu Nov 27 23:43:01 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1632 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago) ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Attachment added: xev output when pressing button with Rhythmbox playing (initially) https://bugs.launchpad.net/bugs/1397142/+attachment/4269915/+files/xev.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Sony SRS-BTM8 play/pause key not fully effective in Banshee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1395301] [NEW] Inconsistent terminology for Bluetooth pairing
Public bug reported: The Personal File Sharing Preferences window has two sections relating to Bluetooth, and those use different terminology (and user interface features) to describe Bluetooth pairing, both from one another and from the main Bluetooth settings. Under Share Files over Bluetooth, the requirement for pairing is controlled by a tickbox labelled Require remote devices to bond with this computer, while under Receive Files over Bluetooth, it's controlled by a pop-up menu labelled Accept files: with options Always and Only for set up devices. As far as I can tell from the docuementation (which disagrees slightly about how the user interface should look), these controls have equivalent effects and control whether files can be respectively browsed or sent by unpaired devices. Meanwhile, the Bluetooth indicator menu uses the phrase Set-up [sic] New Device, the Bluetooth pane of System Settings describes certain devices as Paired, and the Ubuntu Desktop Guide explains how to Connect your computer to a Bluetooth device but helpfully explains that This is also called pairing the Bluetooth devices. Personally, I think that both of these settings should be tickboxes, and their labels should both be phrased in terms of paired deviced, since that's standard Bluetooth terminology. For consistency with the Ubuntu Desktop Guide, perhaps connected would be better (but I think it's less obvious what it means). PS: I've just found the Control sharing over Bluetooth page of the Ubuntu Desktop Guide, which adds to the fun by introducing trusted devices, which are apparently yet another way of talking about paired devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Nov 22 10:53:26 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-file-share-properties InstallationDate: Installed on 2010-06-09 (1626 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 SourcePackage: gnome-user-share UpgradeStatus: Upgraded to trusty on 2014-08-15 (98 days ago) ** Affects: gnome-user-share (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1395301 Title: Inconsistent terminology for Bluetooth pairing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1395301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392907] [NEW] Turn Bluetooth on or off instructions outdated
Public bug reported: On the Turn Bluetooth on or off page of the Ubuntu Desktop Guide, I am told to click the Bluetooth icon in the menu bar and click Turn On Bluetooth. However, the Bluetooth menu doesn't have a Turn On Bluetooth entry, but instead has an entry labelled Bluetooth with an ON/OFF switch. Similarly, the note on that page refers to an entry labelled Visibility that is now labelled Visible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-docs 14.04.4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Nov 15 00:05:22 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1619 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-docs UpgradeStatus: Upgraded to trusty on 2014-08-15 (91 days ago) ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392907 Title: Turn Bluetooth on or off instructions outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1392907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326788] [NEW] debian/rules clean does not clean adequately
Public bug reported: This is a problem in the unity-lens-applications source package. According to Ubuntu policy, the clean rule in debian/rules must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target. That target in unity-lens-applications does not do this: root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 /dev/null 21 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l92 root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 debian/rules build debian/rules clean ) /dev/null 21 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l103 root@chickatrice:/tmp# rm -r unity* root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 /dev/null 21 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 files.before root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 debian/rules build debian/rules clean ) /dev/null 21 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 files.after root@chickatrice:/tmp# diff files.before files.after | grep '^' unity-lens-applications-7.1.0+13.10.20131011/tests/unit/aptd-client.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-data-cache.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/xapian-utils.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/schemas.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-utils.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-app-details.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/utils.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/purchase-info-helper.c unity-lens-applications-7.1.0+13.10.20131011/tests/unit/app-watcher.c unity-lens-applications-7.1.0+13.10.20131011/data/applications.scope unity-lens-applications-7.1.0+13.10.20131011/data/scopes.scope It looks like some of the files generating while building are not correctly removed while cleaning. This is a problem if (as I do) you want to convert the package to use the 3.0 (quilt) source format. The attached patch fixes the problem, but probably more crudely than is acceptable. ** Affects: unity-lens-applications (Ubuntu) Importance: Undecided Status: New ** Patch added: Crude fix for the problem https://bugs.launchpad.net/bugs/1326788/+attachment/4125877/+files/mcs-clean -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326788 Title: debian/rules clean does not clean adequately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1326788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326788] Re: debian/rules clean does not clean adequately
I failed to mention: this problem affects Ubuntu 14.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326788 Title: debian/rules clean does not clean adequately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1326788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326801] [NEW] debain/rules clean does not clean adequately
Public bug reported: This is a problem in the unity-scope-home source package, version 6.8.2+14.04.20131029.1-0ubuntu1 from Ubuntu 14.04 LTS. According to Ubuntu policy, the clean rule in debian/rules must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target. That target in unity-scope-home does not do this: root@chickatrice:/tmp# apt-get source unity-scope-home=6.8.2+14.04.20131029.1-0ubuntu1 /dev/null 21 root@chickatrice:/tmp# find unity-scope-home-6.8.2+14.04.20131029.1 files.before root@chickatrice:/tmp# ( cd unity-scope-home-6.8.2+14.04.20131029.1 debian/rules build debian/rules clean ) /dev/null 21 root@chickatrice:/tmp# find unity-scope-home-6.8.2+14.04.20131029.1 files.after root@chickatrice:/tmp# diff files.before files.after | grep '^' unity-scope-home-6.8.2+14.04.20131029.1/tests/unit/feedback.dump unity-scope-home-6.8.2+14.04.20131029.1/tests/unit/search.dump unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/books.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/photos.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/more_suggestions.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/applications.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/news.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/info.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/code.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/help.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/calendar.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/recipes.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/files.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/searchin.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/boxes.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/notes.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/weather.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/web.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/reference.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/video.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/music.scope unity-scope-home-6.8.2+14.04.20131029.1/data/master-scopes/graphics.scope It looks like some of the files generating while building are not correctly removed while cleaning. This is a problem if (as I do) you want to convert the package to use the 3.0 (quilt) source format. The attached patch seemed to fix the problem for me, but I now worry about the *.dump files above, which it doesn't touch. ** Affects: unity-scope-home (Ubuntu) Importance: Undecided Status: New ** Patch added: Crude patch that might fix the problem https://bugs.launchpad.net/bugs/1326801/+attachment/4125895/+files/mcs-clean -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326801 Title: debain/rules clean does not clean adequately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-home/+bug/1326801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] [NEW] Oops: unable to handle kernel paging request at 00007d7d; EIP __kmalloc_track_caller+0xab/0x1d0
Public bug reported: We just suffered a string of kernel oopses followed by a crash on one of our login servers. I've attached the log messages recorded by our syslog server. Shortly after these messages were produced, the server went dead to the network (our monitoring system detected this at 10:13:24) and when checked its display was blank and could not be woken up. Unfortunately, we don't know how to reproduce this problem, but it seems to have occurred while a user was logging in. We use a customised CIFS module to mount users' home directories, but the crash occurred before the user's home directory was mounted, so we don't think that's the cause of the problem. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-oops ** Attachment added: syslog messages from kernel oops. https://bugs.launchpad.net/bugs/1064337/+attachment/3389241/+files/snap-oops-20121009 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] Re: Oops: unable to handle kernel paging request at 00007d7d; EIP __kmalloc_track_caller+0xab/0x1d0
** Attachment added: output of uname -a (after reboot) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+attachment/3389263/+files/uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] Re: Oops: unable to handle kernel paging request at 00007d7d; EIP __kmalloc_track_caller+0xab/0x1d0
** Attachment added: Output of cat /proc/version_signature (after reboot) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+attachment/3389306/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] Re: Oops: unable to handle kernel paging request at 00007d7d; EIP __kmalloc_track_caller+0xab/0x1d0
** Attachment added: Output of lspci -vvnn (after reboot) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+attachment/3389307/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] Re: Oops: unable to handle kernel paging request at 00007d7d; EIP __kmalloc_track_caller+0xab/0x1d0
apport information ** Tags added: apport-collected precise ** Description changed: We just suffered a string of kernel oopses followed by a crash on one of our login servers. I've attached the log messages recorded by our syslog server. Shortly after these messages were produced, the server went dead to the network (our monitoring system detected this at 10:13:24) and when checked its display was blank and could not be woken up. - Unfortunately, we don't know how to reproduce this problem, but it seems - to have occurred while a user was logging in. We use a customised CIFS - module to mount users' home directories, but the crash occurred before - the user's home directory was mounted, so we don't think that's the - cause of the problem. + Unfortunately, we don't know how to reproduce this problem, but it seems to have occurred while a user was logging in. We use a customised CIFS module to mount users' home directories, but the crash occurred before the user's home directory was mounted, so we don't think that's the cause of the problem. + --- + AlsaDevices: + total 0 + crw-rw---T 1 root audio 116, 1 Oct 4 18:11 seq + crw-rw---T 1 root audio 116, 33 Oct 4 18:11 timer + AplayDevices: aplay: device_list:252: no soundcards found... + ApportVersion: 2.0.1-0ubuntu13 + Architecture: i386 + ArecordDevices: arecord: device_list:252: no soundcards found... + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 12.04 + InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423.2) + IwConfig: + eth3 no wireless extensions. + + lono wireless extensions. + + eth2 no wireless extensions. + MachineType: Intel Corporation S5500WBV + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LANGUAGE=en_GB: + TERM=xterm + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic-pae root=UUID=0126568b-a418-4a45-89a6-8d14664336b0 ro reboot=b crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.2.0-31-generic-pae N/A + linux-backports-modules-3.2.0-31-generic-pae N/A + linux-firmware1.79.1 + RfKill: + + Tags: precise + Uname: Linux 3.2.0-31-generic-pae i686 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + WifiSyslog: + + dmi.bios.date: 03/09/2012 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: S5500.86B.01.00.0061.030920121535 + dmi.board.asset.tag: + dmi.board.name: S5500WB + dmi.board.vendor: Intel Corporation + dmi.board.version: E40367-312 + dmi.chassis.asset.tag: + dmi.chassis.type: 23 + dmi.chassis.vendor: ... + dmi.chassis.version: .. + dmi.modalias: dmi:bvnIntelCorp.:bvrS5500.86B.01.00.0061.030920121535:bd03/09/2012:svnIntelCorporation:pnS5500WBV:pvr:rvnIntelCorporation:rnS5500WB:rvrE40367-312:cvn...:ct23:cvr..: + dmi.product.name: S5500WBV + dmi.product.version: + dmi.sys.vendor: Intel Corporation ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389325/+files/AcpiTables.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389326/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389327/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389328/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389329/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389330/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389331/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389332/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389333/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1064337/+attachment/3389334/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064337] Re: Oops: unable to handle kernel paging request at 00007d7d; EIP __kmalloc_track_caller+0xab/0x1d0
This bug has only occurred once on a widely-used login server. We don't know how to reproduce it, and would be reluctant to run an upstream kernel on a production server, especially given the statement regarding support at the bottom of https://wiki.ubuntu.com/Kernel/MainlineBuilds . Thus, I think we're unable to test upstream. Sorry. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064337 Title: Oops: unable to handle kernel paging request at 7d7d; EIP __kmalloc_track_caller+0xab/0x1d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950056] Re: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around
I carried on testing reboot=l for a little longer (while working on initrd scripts) and it didn't hang once, so I think it works reliably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950056 Title: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950056] Re: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around
I've tested each option five times, as before. Results below: reboot=k: hangs sometimes (1/5) reboot=t: hangs sometimes (2/5) reboot=l: works always (5/5) reboot=h: hangs sometimes (1/5) Given the rarity of hangs with other settings, I'll carry on testing reboot=l in case I just got lucky. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950056 Title: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950056] Re: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around
I've tested each option five times with the installed 32-bit kernel (3.0.0-16.29). reboot=w: hangs sometimes (3/5) reboot=k: hangs sometimes (4/5) reboot=t: hangs sometimes (3/5) reboot=p: works always (5/5) reboot=f: hangs sometimes (3/5) So only reboot=p (and reboot=b) reliably works. All the others hang on reboot about half the time. I'll test a 64-bit kernel next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950056 Title: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950056] Re: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around
I've now tested each of those options (w, k, t, p, f) five times on an Ubuntu 11.10 64-bit install image (on a USB memory stick). The kernel version was 3.0.0-12.20. In all cases, the reboot worked perfectly. To check that my test procedure was sound, I re-ran the reboot=w test using a 32-bit install image (same kernel version) and that crashed on reboot twice out of the five tests. So it looks like 64-bit kernels are not susceptible to this problem. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950056 Title: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950056] [NEW] Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around
Public bug reported: Running 11.10 on a Dell OptiPlex 780. More than half the time when I reboot (e.g. by running reboot as root), the system will hang just after displaying the now restarting message, and not reboot. Adding reboot=bios to the kernel command line seems to solve this problem: four reboots in a row have been successful. I have tried updating to the latest BIOS (revision A12), and that hasn't made any difference. This seems to be an equivalent problem to #488319 (OptiPlex 760) and #115011 (OptiPlex 745). I've found other references to the problem here: https://wiki.inf.ed.ac.uk/DICE/F13Upgrade (apparently solved by reboot=bios) http://fogproject.org/forum/threads/tftpboot-restart-problems.238/ (apparently solved by changing kernel) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-16-generic 3.0.0-16.28 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1535 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf7adc000 irq 50' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,10280420,00100400' Controls : 34 Simple ctrls : 20 Date: Thu Mar 8 16:18:22 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. OptiPlex 780 ProcEnviron: LANGUAGE=en_GB: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-16-generic root=UUID=21453ce7-2d21-43c9-bc33-a496207cee55 ro quiet splash reboot=bios vt.handoff=7 PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.0.0-16-generic N/A linux-backports-modules-3.0.0-16-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 03NVJ6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd12/09/2011:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn03NVJ6:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 oneiric staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950056 Title: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950056] Re: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950056 Title: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950056] Re: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around
I've tested this having installed linux-image-3.3.0-030300rc6-generic 3.3.0-030300rc6.201203032235. This seems to exhibit the same problem as the Ubuntu kernel: with reboot=bios everything is fine; without it the system hangs after Restarting system. ** Tags removed: needs-upstream-testing ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950056 Title: Reboot hangs on Dell OptiPlex 780 (board 03NVJ6); reboot=bios works around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828895] [NEW] Bash loses track of background children sometimes
Public bug reported: Under some circumstances (I've not worked out precisely what), bash can forget about background child processes. For instance, if the file simpletest contains: #! /bin/bash count=0 while [ $count -lt 51 ]; do count=$((count+1)) /nonexist true bgpids=$bgpids $! done for pid in $bgpids; do wait $pid done then running bash simpletest, seems to reliably report simpletest: line 13: wait: pid 28850 is not a child of this shell (with different PIDs each time, obviously). Increasing the 51 in the script increases the number of errors. Curiously, removing the call to a nonexistent program causes the problem to stop manifesting. getconf CHILD_MAX returns undefined, which I think means that Bash should support an unlimited number of unwaited children. I've observed this on two different amd64 boxes running Ubuntu 10.04 LTS, and it persisted after I upgraded the bash package to 4.2-0ubuntu4. I couldn't reproduce it on an i386 box running Ubuntu 11.04. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: bash 4.1-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-33.72-server 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-server x86_64 Architecture: amd64 Date: Thu Aug 18 17:04:23 2011 InstallationMedia: Ubuntu-Server 10.04.3 LTS Lucid Lynx - Release amd64 (20110719.2) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: bash ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828895 Title: Bash loses track of background children sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/828895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828895] Re: Bash loses track of background children sometimes
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828895 Title: Bash loses track of background children sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/828895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798983] [NEW] Banshee hung when deleting an equalizer setting
Public bug reported: Binary package hint: banshee I had downloaded two albums from Amazon, and created a new equalizer setting to try to compensate for my netbook's terrible speakers. This turned out to be impossible, so I clicked the minus-sign button in the equalizer window. This caused Banshee to hang, in that its windows no longer respond to input and don't redraw themselves. I've run ubuntu- bug against the running process. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: banshee 2.0.0-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Fri Jun 17 23:19:53 2011 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes ExecutablePath: /usr/lib/banshee/Banshee.exe InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 20100121-21:52 InterpreterPath: /usr/bin/mono ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: banshee UpgradeStatus: Upgraded to natty on 2011-04-29 (49 days ago) ** Affects: banshee (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798983 Title: Banshee hung when deleting an equalizer setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/798983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798983] Re: Banshee hung when deleting an equalizer setting
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798983 Title: Banshee hung when deleting an equalizer setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/798983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 462466] Re: Broadcom BCM4322 STA brcm80211 can't see wifi channels 11 (2.462GHz)
Possibly useful: the version of bcmwl-kernel-source from Ubuntu 10.10, 5.60.48.36+bdcom-0ubuntu5, seems to work in Ubuntu 11.04 and provide access to channel 13. This provides a workaround, at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/462466 Title: Broadcom BCM4322 STA brcm80211 can't see wifi channels 11 (2.462GHz) To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/462466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657369] Re: Mobile broadband silently disconnects when switching between 2G roaming and 3G
Unhepful update: this is still occuring with modemmanager 0.4+git.20110124t203624.00b6cce-2ubuntu1 under Ubuntu 11.04. I just encountered it with my forced-3G connection again. In case it's relevant, this was on a northbound train between Royston and Cambridge (UK). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/657369 Title: Mobile broadband silently disconnects when switching between 2G roaming and 3G -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 747343] Re: [launcher] does not autohide
On my system (which exhibits the same problem), env | grep unity shows nothing when logged in using the Ubuntu option (which seems to fall back to Unity 2D). Digging out those environment variables specifically, they are: DEFAULTS_PATH=/usr/share/gconf/gnome.default.path XDG_CONFIG_DIRS=/etc/xdg/xdg-gnome:/etc/xdg DESKTOP_SESSION=gnome MANDATORY_PATH=/usr/share/gconf/gnome.mandatory.path GDMSESSION=gnome XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/747343 Title: [launcher] does not autohide -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657369] Re: Mobile broadband silently disconnects when switching between 2G roaming and 3G
I've created a separate connection in NetworkManager that has Type set to 3G (UMTS/HSDPA), in the hope of avoiding fallback to 2G and hence avoiding this problem. Using this connection today, though, I've had the same behaviour: I get a message like this: Feb 19 11:01:49 sole modem-manager: mbm_e2nap_received: disconnected in /var/log/daemon.log, and the connection stop working but still seems to be live in the NetworkManager applet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/657369 Title: Mobile broadband silently disconnects when switching between 2G roaming and 3G -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601349] Re: Mobile broadband fails uninformatively when wireless disabled
Output from rfkill list after power-on: 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-wwan: Wireless WAN Soft blocked: no Hard blocked: no After pressing Fn+F6: 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-wwan: Wireless WAN Soft blocked: no Hard blocked: no It seems that things are slightly better now, in that in this state, the right-button menu in the NetworkManager applet has Enable Mobile Broadband unchecked and greyed-out. The left-button menu still lists my mobile broadband connection, though, and choosing it results in the unhelpful notification GSM network / Disconnected. Things get stranger if I press Fn+F6 again, in that this gives me the following from rfkill list: 0: dell-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: dell-wwan: Wireless WAN Soft blocked: no Hard blocked: no and leaves the light off. This bit probably isn't NetworkManager's fault, though. Incidentally, I'm currently running network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu3~nmt3~lucid. Since I'm now running Ubuntu 10.10, I should probably update to something newer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/601349 Title: Mobile broadband fails uninformatively when wireless disabled -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657812] Re: upgrate to 10.10 causes error ubuntu-minimal missing
I seem to have the same problem. I ran System/Administration/Update Manager and it offered an upgrade to '10.10'. I clicked the button to upgrade, and typed my password when asked. The Distribution Upgrade window got as far as Setting new software channels and said it would disable some non-standard ones (presumably the NetworkManager PPA documented at https://wiki.ubuntu.com/DebuggingModemmanager). Then I got a dialogue box saying: Invalid package information After your package information was updated the essential package 'ubuntu-minimal' can not be found anymore. This indicates a serious error, please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report. I've attached a tarball of my /var/log/dist-upgrade, since there's a directory structure there that makes attaching individual files awkward. ** Attachment added: tarfile of /var/log/dist-upgrade https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/657812/+attachment/1686172/+files/dist-upgrade.tar -- upgrate to 10.10 causes error ubuntu-minimal missing https://bugs.launchpad.net/bugs/657812 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 657812] Re: upgrate to 10.10 causes error ubuntu-minimal missing
To answer the later questions, I'm behind a fairly dull NAT router, on a network that (on a good day) supports IPv6, and I've attached the output of ls -la /var/lib/apt/lists. ** Attachment added: ls -la /var/lib/apt/lists https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/657812/+attachment/1686221/+files/lists.txt -- upgrate to 10.10 causes error ubuntu-minimal missing https://bugs.launchpad.net/bugs/657812 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
