[Desktop-packages] [Bug 1288004] [NEW] hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem
Public bug reported: Ubuntu 13.10 Not sure which package Sound comes through hdmi sounding like a chipmunks tune. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Mar 4 18:21:58 2014 MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: gazp9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9: dmi.product.name: Gazelle Professional dmi.product.version: gazp9 dmi.sys.vendor: System76, Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1288004 Title: hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem Status in “alsa-driver” package in Ubuntu: New Bug description: Ubuntu 13.10 Not sure which package Sound comes through hdmi sounding like a chipmunks tune. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Mar 4 18:21:58 2014 MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: gazp9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9: dmi.product.name: Gazelle Professional dmi.product.version: gazp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1288004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
** Tags added: saucy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above Development fix.
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing sudo apt-get install --reinstall libc6 and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I added the following line to /etc/init/ureadahead-other.conf to disable logging for this particular Upstart job: console none This prevents the log file from keeping the file system busy. The only downside is that anything logged by ureadahead-other goes to /dev/null instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063969] Re: NVIDIA does not work with framebuffer drivers
I saw the following in the release notes for version 319.17 of the NVIDIA driver (http://www.nvidia.com/object/linux-display- amd64-319.17-driver.html): * Added initial support for restoration of efifb consoles on UEFI systems where the primary display is driven over VGA or TMDS (e.g. DVI, HDMI, or LVDS). It looks like NVIDIA is doing something about this, but their priority is UEFI systems where they have to support interoperating with a framebuffer backed console. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: NVIDIA does not work with framebuffer drivers Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
P.S. You will have to reboot 2 times after adding console none for it to work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175023] Re: .Xauthority.****** files polluting $Home
I can confirm this bug in 13.04. Also, the .Xauthority file is created with permissions of 0664 instead of the secure 0600. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1175023 Title: .Xauthority.** files polluting $Home Status in “lightdm” package in Ubuntu: Confirmed Bug description: .Xauthority.** files polluting $Home. Where '*'s are random capital alphabets and numbers of exactly 6 charater length. In Ubuntu 12.04 it was '.goutputstream' polluting $HOME, so may be it's some how related to bug 984785. ProblemType: Bug DistroRelease: Ubuntu 13.04 Uname: Linux 3.8.0-19-generic Architecture: i386 Date: Wed May 1 08:45:31 2013 InstallationMedia: Ubuntu 13.04 i386 UpgradeStatus: No upgrade ( fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1175023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
I can confirm this problem still exists in 13.04 (raring). I'm using
Daniel Eckl's patch in comment #49 to work around it, but I modified it
to only kill dhclient. It appears that dnsmasq is being terminated
properly in 13.04.
** Tags added: raring
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above Development fix.
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing sudo apt-get install --reinstall libc6 and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1181766] Re: Download speed is very slow
** Also affects: network-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1181766 Title: Download speed is very slow Status in NetworkManager: New Status in “network-manager” package in Ubuntu: New Bug description: My download speed is incredibly slow. Using speedtest.net my download speed is in the range of 20-30 Mb/s regardless of the server. Upload speed is pretty good thou. I am using Wireless connection. My router is Netgear R6300. My ISP is FiOS and I am at 75/35 plan. In comparison rebooting in Windows 7 speedtest.net is at 80 Mb/s down and 38 Mb/s up. Another strange thing I discovered is that when I look at the connection information of my wireless connection it constantly fluctiates b/w 6 Mb/s and 144 Mb/s. It never goes above 144 Mb/s. In comaprison, my Windows 7 stays at 300 Mb/s constantly pretty much. Drops to 270 rarely. I just upgraded to the latest kernel from the repository and took quite a while just to download. My adapter is Intel(R) Centrino(R) Advanced-N 6230. Attaching both tests - Ubuntu 13.04 (26 Mb/s down and 39 Mb/s up) and Windows 7 (84 Mb/s down and 39 Mb/s up). Both tests in wireless connection. And again, this is pretty much plain Ubuntu installation. I also tested it with a LiveCD, with the same horrible download speeds. OPened a thread in the Networking forum, but so far no replies... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 10:15:38 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-05 (13 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.110.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.110.0/24 dev wlan0 proto kernel scope link src 192.168.110.157 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Home 5G 9f8fc9f0-3c69-41e4-8a5a-29e2ef2f2169 802-11-wireless 1368972787 Sun 19 May 2013 10:13:07 AM EDTyes no /org/freedesktop/NetworkManager/Settings/2 Lan Connection1e91467c-0acb-46b7-a029-fe4938c6d1d1 802-3-ethernet1367768983 Sun 05 May 2013 11:49:43 AM EDTyes no /org/freedesktop/NetworkManager/Settings/1 Oracle VPN071ea473-fe32-4c06-bd28-37e7f01f8f29 vpn 0never nono /org/freedesktop/NetworkManager/Settings/0 ibahn 24e5bbc6-cc0e-48b3-b5d6-6725fb58789d 802-11-wireless 1368102132 Thu 09 May 2013 08:22:12 AM EDTyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1181766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
** Tags added: quantal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above Development fix.
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing sudo apt-get install --reinstall libc6 and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes
I can confirm this bug. I have two systems running 12.10 and both
experience this issue.
Killing dnsmasq and dhclient in the umountroot script results in a clean
shutdown on both systems.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” source package in Precise:
Fix Released
Bug description:
[Impact]
On shutdown, dhclient isn't getting reaped by NetworkManager, despite being
kept running through sendsigs so as not to disrupt remote filesystems (and
their unmounting at shutdown). dhclient may be keeping open files for its lease
files, which causes issues when unmounting /var/lib, which contains those lease
files.
[Development Fix]
Remove support for connection assumption, which is meant to bring
NetworkManager up to speed with connections that may have already be up during
a restart of the daemon. Since we don't actually restart the daemon
automatically (and instead suggest a restart of the system after upgrade) and
the advantage is minimal compared to the impact on users of this interacting
with the shutdown sequence, patch connection assumption out of the NM code and
just always take down dhclient when NM stops.
[Stable Fix]
See above Development fix.
[Test Case]
1) Shut down coputer.
2) In the shutdown process, perhaps as a post-stop script in
/etc/init/network-manager, track down open files for the dhclient pid (which
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)
[Regression Potential]
Minimal, only affects bringing NetworkManager up on a restart of the daemon
(sudo restart network-manager or /etc/init.d/network-manager restart), which
improves on the speed of this operation and avoid resetting the connection if
it's already up.
-
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing sudo apt-get install --reinstall libc6 and then
rebooting leads to:
[8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
I have reproduced this with Ubuntu 12.10 (with gnome-settings-daemon 3.4.2) as well. It displayed the usual symptom of 100% CPU usage, but then it crashed. I have attached an Apport crash report. I can reproduce this at will by turning Num Lock on, connecting to vino- server with androidVNC, and typing in a gnome-terminal window. ** Attachment added: Crash report https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/969359/+attachment/3410176/+files/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1001.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) Status in Gnome Settings Daemon: Incomplete Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” source package in Precise: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Bug description: Check comments 33 and 107 for a possible workaround. Original message: - I don't know how to reproduce this bug, but after varying amounts of normal usage of my laptop, I notice gnome-settings-daemon is consuming 100% (approx) CPU. I am not sure how to restart gnome-settings-daemon, I tried opening a terminal and running gnome-settings-daemon again but this crashes my system - my external monitor switches off and my laptop locks up. I am able to reboot with SysRq+REISUB. Sorry I cannot provide more information - it happens twice now, maybe someone can tell me how to get more information for the next time this happens. $ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 $ apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.4.0-0ubuntu2 Candidate: 3.4.0-0ubuntu2 Version table: *** 3.4.0-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 17:16:02 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063969] Re: No Plymouth Splash on Latitude E6420
Note that the warning in comment #8 also applies to the method described in comment #9 because it uses the uvesafb module. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: No Plymouth Splash on Latitude E6420 Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Triaged Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063969] Re: No Plymouth Splash on Latitude E6420
I was able to restore the splash screen: * Edit /usr/share/nvidia-current/nvidia-current.grub-gfxpayload and comment out the line that blacklists all Nvidia graphics cards * sudo update-grub-gfxpayload * sudo update-grub WARNING: You may experience graphics memory corruption, system crashes, hangs, loss of data, and other unpleasant experiences. If you are not comfortable with the risk, don't change this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: No Plymouth Splash on Latitude E6420 Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Triaged Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063969] Re: No Plymouth Splash on Latitude E6420
If you choose to use the workaround in comment #7, the Nvidia driver will yell at you in the kernel log, too: NVRM: Your system is not currently configured to drive a VGA console NVRM: on the primary VGA device. The NVIDIA Linux graphics driver NVRM: requires the use of a text-mode VGA console. Use of other console NVRM: drivers including, but not limited to, vesafb, may result in NVRM: corruption and stability problems, and is not supported. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: No Plymouth Splash on Latitude E6420 Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Triaged Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969359] Re: gnome-settings-daemon consumes 100% cpu
When gnome-settings-daemon is doing this, I find this logged to ~/.xsession-errors continually until I kill it: - (gnome-settings-daemon:2062): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed (gnome-settings-daemon:2062): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed (gnome-settings-daemon:2062): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed ** (gnome-settings-daemon:2062): WARNING **: Timeout was reached ** (gnome-settings-daemon:2062): WARNING **: Timeout was reached ** (gnome-settings-daemon:2062): WARNING **: Timeout was reached - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: gnome-settings-daemon consumes 100% cpu Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: I don't know how to reproduce this bug, but after varying amounts of normal usage of my laptop, I notice gnome-settings-daemon is consuming 100% (approx) CPU. I am not sure how to restart gnome-settings-daemon, I tried opening a terminal and running gnome-settings-daemon again but this crashes my system - my external monitor switches off and my laptop locks up. I am able to reboot with SysRq+REISUB. Sorry I cannot provide more information - it happens twice now, maybe someone can tell me how to get more information for the next time this happens. $ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 $ apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.4.0-0ubuntu2 Candidate: 3.4.0-0ubuntu2 Version table: *** 3.4.0-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 17:16:02 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/969359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
