[Bug 1873026] [NEW] File manager grabs favorites folders on left
Public bug reported: Upgraded to beta release of 20.4 and Nautilus file manager now is exhibiting a problem reported in older versions. When clicking on folders in the left side window the folder will be dragged to where ever the mouse is moved. The work around is to click once move slightly then click again to release in the same spot. The other work around is to reboot and sometimes the problem goes away. I believe all this information has be sent when I did the ubuntu-bug command, but here is is again: Release: Ubuntu Focal Fossa (development branch) nautilus:Installed: 1:3.36.1.1-1ubuntu2 Expected behavior: Expected to click on "favorite" folder and be taken to the folder in the right side of screen. Actual behavior: Clicking on "favorite" folder grabbed the folder to drag where ever the cursor went. Need to click again in same place on left screen to release the folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:28:53 2020 InstallationDate: Installed on 2017-03-19 (1123 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873026 Title: File manager grabs favorites folders on left To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579542] Re: My computer reboots instead of shutdown
I have had this problem for awhile. It got worse when I upgraded from 14.04 to 16.04. I haven't tried all the workarounds above yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579542 Title: My computer reboots instead of shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532062] Re: Drives mistakenly reported as removable
** Branch linked: lp:~returntoreptar/curtin/removable-drive-fixes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1532062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1532062] Re: Drives mistakenly reported as removable
** Branch linked: lp:~returntoreptar/curtin/removable-drive-fixes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1532062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532062] Re: Drives mistakenly reported as removable
Sure no problem! I have attached the output of sudo lshw as a file, since it was a bit long. ** Attachment added: "Output of lshw on system with "removable" drives." https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1532062/+attachment/4548195/+files/lshw-output-anakin -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1532062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1532062] Re: Drives mistakenly reported as removable
Sure no problem! I have attached the output of sudo lshw as a file, since it was a bit long. ** Attachment added: "Output of lshw on system with "removable" drives." https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1532062/+attachment/4548195/+files/lshw-output-anakin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1532062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532062] Re: Drives mistakenly reported as removable
Sounds good, here is the output from: lsblk --pairs "--output=$full" /dev/sda ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0B" DISC-MAX="0B" DISC-ZERO="0" FSTYPE="" GROUP="disk" KNAME="sda" LABEL="" LOG-SEC="512" MAJ:MIN="8:0" MIN-IO="512" MODE="brw-rw" MODEL="main" MOUNTPOINT="" NAME="sda" OPT-IO="0" OWNER="root" PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128" SIZE="100G" STATE="running" TYPE="disk" UUID="" ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0B" DISC-MAX="0B" DISC-ZERO="0" FSTYPE="" GROUP="disk" KNAME="sda1" LABEL="" LOG-SEC="512" MAJ:MIN="8:1" MIN-IO="512" MODE="brw-rw" MODEL="" MOUNTPOINT="/" NAME="sda1" OPT-IO="0" OWNER="root" PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128" SIZE="100G" STATE="" TYPE="part" UUID="" And the output from lsblk --pairs "--output=$short" /dev/sda NAME="sda" MAJ:MIN="8:0" RM="1" SIZE="100G" RO="0" TYPE="disk" MOUNTPOINT="" NAME="sda1" MAJ:MIN="8:1" RM="1" SIZE="100G" RO="0" TYPE="part" MOUNTPOINT="/" I may be misreading it, however it looks to me like the initial output is telling the same story, in lsblk -l it looks to me like it has the below structure with formatting, which seems to me that it is being reported wrong all the way around. That being said I don't have any experience with lsblk so I could be completely off. NAME MAJ:MIN RM SIZERO TYPE MOUNTPOINT sda 8:0 1 100G 0 disk sda1 8:1 1 100G 0 part/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1532062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532062] Re: Drives mistakenly reported as removable
Sorry I should've known that wouldn't format correctly once I posted, I have tried to structure the lsblk -l output here: http://pastebin.com/hQktMbXg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1532062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532062] Re: Drives mistakenly reported as removable
Sure, output is below (sorry its a bit hard to structure it in an easy
to read manner here):
lsblk --bytes --pairs --output=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX
,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-
IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-
SIZE,SIZE,STATE,TYPE,UUID
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0" DISC-MAX="0" DISC-ZERO="0" FSTYPE=""
GROUP="disk" KNAME="sda" LABEL="" LOG-SEC="512" MAJ:MIN="8:0" MIN-IO="512"
MODE="brw-rw" MODEL="main" MOUNTPOINT="" NAME="sda" OPT-IO="0"
OWNER="root" PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128"
SIZE="107363696640" STATE="running" TYPE="disk" UUID=""
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0" DISC-MAX="0" DISC-ZERO="0" FSTYPE=""
GROUP="disk" KNAME="sda1" LABEL="" LOG-SEC="512" MAJ:MIN="8:1" MIN-IO="512"
MODE="brw-rw" MODEL="" MOUNTPOINT="/" NAME="sda1" OPT-IO="0" OWNER="root"
PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128" SIZE="107362631168" STATE=""
TYPE="part" UUID=""
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0" DISC-MAX="0" DISC-ZERO="0" FSTYPE=""
GROUP="disk" KNAME="sdb" LABEL="" LOG-SEC="512" MAJ:MIN="8:16" MIN-IO="512"
MODE="brw-rw" MODEL="storage " MOUNTPOINT="" NAME="sdb" OPT-IO="0"
OWNER="root" PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128"
SIZE="186004799488" STATE="running" TYPE="disk" UUID=""
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0" DISC-MAX="0" DISC-ZERO="0" FSTYPE=""
GROUP="disk" KNAME="sdb1" LABEL="" LOG-SEC="512" MAJ:MIN="8:17" MIN-IO="512"
MODE="brw-rw" MODEL="" MOUNTPOINT="/var/lib/ceph/osd/ceph-0" NAME="sdb1"
OPT-IO="0" OWNER="root" PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128"
SIZE="184929992192" STATE="" TYPE="part" UUID=""
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0" DISC-MAX="0" DISC-ZERO="0" FSTYPE=""
GROUP="disk" KNAME="sdb2" LABEL="" LOG-SEC="512" MAJ:MIN="8:18" MIN-IO="512"
MODE="brw-rw" MODEL="" MOUNTPOINT="" NAME="sdb2" OPT-IO="0" OWNER="root"
PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128" SIZE="1072693760" STATE=""
TYPE="part" UUID=""
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0" DISC-MAX="0" DISC-ZERO="0" FSTYPE=""
GROUP="cdrom" KNAME="sr0" LABEL="" LOG-SEC="512" MAJ:MIN="11:0" MIN-IO="512"
MODE="brw-rw" MODEL="UJDA780 DVD/CDRW" MOUNTPOINT="" NAME="sr0" OPT-IO="0"
OWNER="root" PHY-SEC="512" RM="1" RO="0" ROTA="1" RQ-SIZE="128"
SIZE="1073741312" STATE="running" TYPE="rom" UUID=""
output of sudo python -c 'import json, curtin.block;
print(json.dumps(curtin.block._lsblock(), indent=1))'
{
"sdb2": {
"GROUP": "disk",
"OPT-IO": "0",
"DISC-MAX": "0",
"LABEL": "",
"MODEL": "",
"RQ-SIZE": "128",
"MODE": "brw-rw",
"ROTA": "1",
"RM": "1",
"RO": "0",
"device_path": "/dev/sdb2",
"DISC-ZERO": "0",
"UUID": "",
"STATE": "",
"MOUNTPOINT": "",
"FSTYPE": "",
"SIZE": "1072693760",
"MAJ:MIN": "8:18",
"DISC-GRAN": "0",
"NAME": "sdb2",
"LOG-SEC": "512",
"DISC-ALN": "0",
"ALIGNMENT": "0",
"MIN-IO": "512",
"OWNER": "root",
"KNAME": "sdb2",
"TYPE": "part",
"PHY-SEC": "512"
},
"sdb1": {
"GROUP": "disk",
"OPT-IO": "0",
"DISC-MAX": "0",
"LABEL": "",
"MODEL": "",
"RQ-SIZE": "128",
"MODE": "brw-rw",
"ROTA": "1",
"RM": "1",
"RO": "0",
"device_path": "/dev/sdb1",
"DISC-ZERO": "0",
"UUID": "3a32991b-299a-471f-b5b0-63962dd84936",
"STATE": "",
"MOUNTPOINT": "/var/lib/ceph/osd/ceph-0",
"FSTYPE": "xfs",
"SIZE": "184929992192",
"MAJ:MIN": "8:17",
"DISC-GRAN": "0",
"NAME": "sdb1",
"LOG-SEC": "512",
"DISC-ALN": "0",
"ALIGNMENT": "0",
"MIN-IO": "512",
"OWNER": "root",
"KNAME": "sdb1",
"TYPE": "part",
"PHY-SEC": "512"
},
"sr0": {
"GROUP": "cdrom",
"OPT-IO": "0",
"DISC-MAX": "0",
"LABEL": "",
"MODEL": "UJDA780 DVD/CDRW",
"RQ-SIZE": "128",
"MODE": "brw-rw",
"ROTA": "1",
"RM": "1",
"RO": "0",
"device_path": "/dev/sr0",
"DISC-ZERO": "0",
"UUID": "",
"STATE": "running",
"MOUNTPOINT": "",
"FSTYPE": "",
"SIZE": "1073741312",
"MAJ:MIN": "11:0",
"DISC-GRAN": "0",
"NAME": "sr0",
"LOG-SEC": "512",
"DISC-ALN": "0",
"ALIGNMENT": "0",
"MIN-IO": "512",
"OWNER": "root",
"KNAME": "sr0",
"TYPE": "rom",
"PHY-SEC": "512"
},
"sda": {
"GROUP": "disk",
"OPT-IO": "0",
"DISC-MAX": "0",
"LABEL": "",
"MODEL": "main",
"RQ-SIZE": "128",
"MODE": "brw-rw",
"ROTA": "1",
"RM": "1",
"RO": "0",
"device_path": "/dev/sda",
"DISC-ZERO": "0",
"UUID": "",
"STATE": "running",
"MOUNTPOINT": "",
"FSTYPE": "",
"SIZE": "107363696640",
"MAJ:MIN": "8:0",
"DISC-GRAN": "0",
"NAME": "sda",
"LOG-SEC": "512",
"DISC-ALN": "0",
"ALIGNMENT": "0",
"MIN-IO": "512",
"OWNER": "root",
"KNAME": "sda",
"TYPE": "disk",
"PHY-SEC": "512"
},
"sdb": {
"GROUP": "disk",
"OPT-IO": "0",
"DISC-MAX": "0",
"LABEL": "",
"MODEL": "storage ",
[Bug 1532062] [NEW] Drives mistakenly reported as removable
Public bug reported: I have multiple servers which report their drives are removable, even though the drives are the main drives in the device (/dev/sda, /dev/sdb, etc). One of such machines (an IBM system x3650 M1) I have pulled a report from lsblk and lshw below and included them. These are configured using the RAID controller that came with the machine. I can provide any other information needed. I am seeing the same on a HP proliant DL100 g2. In this case the removable tag is triggering a problem with curtin since curtin currently refuses to install to drives reported as removable by lsblk. output of: lsblk -l NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:01 100G 0 disk sda1 8:11 100G 0 part / sdb8:16 1 173.2G 0 disk sdb1 8:17 1 172.2G 0 part /var/lib/ceph/osd/ceph-0 sdb2 8:18 1 1023M 0 part sr0 11:01 1024M 0 rom output of: sudo lshw -class disk *-disk:0 description: SCSI Disk physical id: 0.0.0 bus info: scsi@2:0.0.0 logical name: /dev/sda size: 99GiB (107GB) capabilities: partitioned partitioned:dos configuration: sectorsize=512 *-disk:1 description: SCSI Disk physical id: 0.1.0 bus info: scsi@2:0.1.0 logical name: /dev/sdb size: 173GiB (186GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: guid=66a282c8-da87-4502-902d-ce5c7b4da275 sectorsize=512 *-disk:2 UNCLAIMED description: SCSI Disk physical id: 1.0.0 bus info: scsi@2:1.0.0 *-disk:3 UNCLAIMED description: SCSI Disk physical id: 1.1.0 bus info: scsi@2:1.1.0 *-cdrom description: DVD reader product: UJDA780 DVD/CDRW vendor: MATSHITA physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/cdrom logical name: /dev/sr0 version: CA21 capabilities: removable audio cd-r cd-rw dvd configuration: ansiversion=5 status=nodisc ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1532062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363703] [NEW] package sysv-rc 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgrade fro 14.04 to 14.10 (32bit) via upgrade-manager -d ProblemType: Package DistroRelease: Ubuntu 14.10 Package: sysv-rc 2.88dsf-41ubuntu18 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 Date: Sat Aug 30 16:12:04 2014 DuplicateSignature: package:sysv-rc:2.88dsf-41ubuntu18:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all SourcePackage: sysvinit Title: package sysv-rc 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-08-31 (0 days ago) ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 need-duplicate-check utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363703 Title: package sysv-rc 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1363703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832507] Re: console.log grows indefinitely
I've just read through this thread with a view to wether we should release a related OSSN. From what I can tell, no fix was ever agreed on, is this likely to change? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 832507] Re: console.log grows indefinitely
I've just read through this thread with a view to wether we should release a related OSSN. From what I can tell, no fix was ever agreed on, is this likely to change? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696690] Re: pulse sometimes fails to initialise with webcam (w/ USB mic) plugged in.
I am also seeing this behavior with a logitech HD Webcam C310. I am running ubuntu 12.10 and am receiving the same initialization failed error. As soon as I unplugged my webcam I regained the ability to use my speakers, and that ability remained even after plugging the webcam back in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696690 Title: pulse sometimes fails to initialise with webcam (w/ USB mic) plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/696690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037208] Re: Chromium WEB Browser WM crash with Gnome, KDE, or Unity
I installed the latest nvidia driver NVIDIA-Linux-x86_64-304.37, and now chrome does NOT crash, but thunderbird does. This bug needs to be moved from chromium-browser category to Xorg category. Stack trace looks similar to the one that I provided earlier. [ 4995.657] (EE) Backtrace: [ 4995.657] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f7e830108c6] [ 4995.657] (EE) 1: /usr/bin/X (0x7f7e82e68000+0x1ac6f9) [0x7f7e830146f9] [ 4995.657] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f7e8218e000+0xfcb0) [0x7f7e8219dcb0] [ 4995.657] (EE) [ 4995.657] (EE) Segmentation fault at address 0x0 [ 4995.657] Fatal server error: [ 4995.657] Caught signal 11 (Segmentation fault). Server aborting [ 4995.657] [ 4995.657] (EE) Please consult the The X.Org Foundation support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037208 Title: Chromium WEB Browser WM crash with Gnome, KDE, or Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1037208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037208] Re: Chromium WEB Browser WM crash with Gnome, KDE, or Unity
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** No longer affects: chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037208 Title: Chromium WEB Browser WM crash with Gnome, KDE, or Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1037208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037208] [NEW] Chromium WEB Browser WM crash with Gnome, KDE, or Unity
Public bug reported: Regardless of Window Manager used: Gmome, KDE, or Unity, starting up chromium-browser crashes the WM. When crah occurs, I get the login prompt. I do not see this issue with firefox or Thunderbird. [ 20451.022] (**) NVIDIA(0): enabled on all display devices.) [ 23179.031] [ 23179.031] Backtrace: [ 23179.051] 0: /usr/bin/X (xorg_backtrace+0x36) [0x7eff2b6d1686] [ 23179.051] 1: /usr/bin/X (0x7eff2b556000+0x17f38a) [0x7eff2b6d538a] [ 23179.051] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7eff2a87c000+0xfcb0) [0x7eff2a88bcb0] [ 23179.051] [ 23179.051] Segmentation fault at address (nil) [ 23179.051] Caught signal 11 (Segmentation fault). Server aborting [ 23179.051] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 23179.051] Please also check the log file at /var/log/Xorg.0.log for additional information. [ 23179.051] [ 23179.056] (II) evdev: Video Bus: Close [ 23179.056] (II) UnloadModule: evdev [ 23179.056] (II) evdev: Power Button: Close [ 23179.056] (II) UnloadModule: evdev [ 23179.057] (II) evdev: Sleep Button: Close [ 23179.057] (II) UnloadModule: evdev [ 23179.057] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Close [ 23179.057] (II) UnloadModule: evdev [ 23179.057] (II) evdev: AT Translated Set 2 keyboard: Close [ 23179.057] (II) UnloadModule: evdev [ 23179.058] (II) evdev: DualPoint Stick: Close [ 23179.058] (II) UnloadModule: evdev [ 23179.060] (II) UnloadModule: synaptics [ 23179.061] (II) evdev: Dell WMI hotkeys: Close [ 23179.061] (II) UnloadModule: evdev [ 23181.543] ddxSigGiveUp: Closing log [ 23181.543] Server terminated with error (1). Closing log file. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037208 Title: Chromium WEB Browser WM crash with Gnome, KDE, or Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1037208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037208] Re: Chromium WEB Browser WM crash with Gnome, KDE, or Unity
** Attachment added: Complete Xorg log file https://bugs.launchpad.net/bugs/1037208/+attachment/3262547/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037208 Title: Chromium WEB Browser WM crash with Gnome, KDE, or Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1037208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037208] Re: Chromium WEB Browser WM crash with Gnome, KDE, or Unity
File attachement is from: dmidecode SysInfo.txt ** Attachment added: Output from dmidecode https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1037208/+attachment/3262548/+files/SysInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037208 Title: Chromium WEB Browser WM crash with Gnome, KDE, or Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1037208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037208] Re: Chromium WEB Browser WM crash with Gnome, KDE, or Unity
** Description changed: - Regardless of Window Manager used: Gmome, KDE, or Unity, starting up chromium-browser crashes the WM. When crah occurs, - I get the login prompt. I do not see this issue with firefox or Thunderbird. - + This Window manager crash occurs in Quantal release (12.10) + Regardless of Window Manager used: Gmome, KDE, or Unity, starting up chromium-browser crashes the WM. When crash occurs, I get the login prompt. I do not see this issue with firefox or Thunderbird. Crash appears to be triggered only by chromium-browser application start up. I have tested this with my user account and as Guest, and crash occurs in both cases. [ 20451.022] (**) NVIDIA(0): enabled on all display devices.) - [ 23179.031] + [ 23179.031] [ 23179.031] Backtrace: [ 23179.051] 0: /usr/bin/X (xorg_backtrace+0x36) [0x7eff2b6d1686] [ 23179.051] 1: /usr/bin/X (0x7eff2b556000+0x17f38a) [0x7eff2b6d538a] [ 23179.051] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7eff2a87c000+0xfcb0) [0x7eff2a88bcb0] - [ 23179.051] + [ 23179.051] [ 23179.051] Segmentation fault at address (nil) - [ 23179.051] + [ 23179.051] Caught signal 11 (Segmentation fault). Server aborting - [ 23179.051] - Please consult the The X.Org Foundation support - at http://wiki.x.org - for help. + [ 23179.051] + Please consult the The X.Org Foundation support + at http://wiki.x.org + for help. [ 23179.051] Please also check the log file at /var/log/Xorg.0.log for additional information. - [ 23179.051] + [ 23179.051] [ 23179.056] (II) evdev: Video Bus: Close [ 23179.056] (II) UnloadModule: evdev [ 23179.056] (II) evdev: Power Button: Close [ 23179.056] (II) UnloadModule: evdev [ 23179.057] (II) evdev: Sleep Button: Close [ 23179.057] (II) UnloadModule: evdev [ 23179.057] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Close [ 23179.057] (II) UnloadModule: evdev [ 23179.057] (II) evdev: AT Translated Set 2 keyboard: Close [ 23179.057] (II) UnloadModule: evdev [ 23179.058] (II) evdev: DualPoint Stick: Close [ 23179.058] (II) UnloadModule: evdev [ 23179.060] (II) UnloadModule: synaptics [ 23179.061] (II) evdev: Dell WMI hotkeys: Close [ 23179.061] (II) UnloadModule: evdev [ 23181.543] ddxSigGiveUp: Closing log [ 23181.543] Server terminated with error (1). Closing log file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037208 Title: Chromium WEB Browser WM crash with Gnome, KDE, or Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1037208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 396818] Re: openssl s_client behaves strangely without CAPath
openssl s_client is typically used for testing / verify certificates - as it states in the man pages, this should only be used for testing. There's no use case that I can see for using s_client without at least one CA certificate. The default behaviour of openssl in fedora is to use the system installed CA bundle, which is what any user would expect. At the very least openssl should warn you that you're attempting to connect without using any CA files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/396818 Title: openssl s_client behaves strangely without CAPath To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/396818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779849] Re: dbus-daemon consumes 100% CPU
I added the following 2 lines to /etc/security/limits.conf file, and I have not experienced the 100% CPU saturation issue with dbus_daemon for 17 days: * softnofile 65536 * hardnofile 65536 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779849 Title: dbus-daemon consumes 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/779849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677148] Re: KDE crash occurs randomly within minutes of login
This appears to be a nVidia driver bug. The work around is to add the following lines to the xorg.conf file until the driver bug is fixed by nVidia. Section Extensions Option Composite Disable EndSection # Xorg.0.log fragments [55.774] (II) NVIDIA dlloader X Driver 270.41.19 Mon May 16 23:33:05 PDT 2011 [55.774] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [55.774] (--) using VT number 8 [57.152] (II) NVIDIA(0): NVIDIA GPU Quadro FX 580 (G96GL) at PCI:2:0:0 (GPU-0) [57.492] (II) Module evdev: vendor=X.Org Foundation [57.492]compiled for 1.10.0.902, module version = 2.6.0 [57.492]Module class: X.Org XInput Driver [57.492]ABI class: X.Org XInput driver, version 12.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677148 Title: KDE crash occurs randomly within minutes of login -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 677148] Re: KDE crash occurs randomly within minutes of login
Please don't close this bug! I have the latest natty packages installed and the bug is still present. I am able to reproduce at will by simply resizing a konsole window, or a xterm window, or a gnome-terminal, or a System Monitor using TwinView. Please let me know what debug information I can add to this bug report to resolve. Regards, Robert On Fri, May 20, 2011 at 7:10 AM, bugbot 677...@bugs.launchpad.net wrote: We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help. ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/677148 Title: KDE crash occurs randomly within minutes of login To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/677148/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677148 Title: KDE crash occurs randomly within minutes of login -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779849] Re: dbus-daemon consumes 100% CPU
I am experiencing the same issue. I have the latest KDE/natty installs, and I believe this 100% CPU saturation was triggered, when I was moving between folders in Thunderbird 3.10, thunderbird had hung. Yup, sure enough I just killed thunderbird, and dbus-daemon is no longer at 100% CPU utilization. After starting thunderbird the dbus-daemon process goes back to 100% CPU utilization. I have tried this 3 times, and the starting/running of thunderbird is clearly related to the 100 CPU utilization of the dbus-daemon process. I'm going to reboot the system now, and I will update this bug report when the system comes back up. Here is the output from top: Tasks: 175 total, 3 running, 172 sleeping, 0 stopped, 0 zombie Cpu(s): 36.3%us, 19.0%sy, 0.8%ni, 43.9%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 4115008k total, 3981604k used, 133404k free, 195052k buffers Swap: 9933820k total,88628k used, 9845192k free, 1892864k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 32191 rclark20 0 30076 27m 988 R 100 0.7 3133:53 dbus-daemon 32046 root 20 0 285m 241m 35m S4 6.0 133:28.81 Xorg 32268 rclark20 0 417m 87m 38m S2 2.2 95:24.72 kwin 32286 rclark20 0 334m 60m 24m S2 1.5 9:43.30 plasma-desktop 32283 rclark20 0 298m 34m 12m R2 0.9 323:37.38 knotify4 13884 rclark25 5 201m 72m 19m S1 1.8 150:21.93 chromium-browse 18329 rclark20 0 535m 20m 13m S1 0.5 80:53.04 gnome-system-mo 13840 rclark20 0 644m 127m 33m S0 3.2 17:13.71 chromium-browse 13871 rclark20 0 182m 60m 18m S0 1.5 7:58.63 chromium-browse 13951 rclark20 0 300m 36m 19m S0 0.9 66:17.23 chromium-browse 14034 rclark20 0 1129m 306m 32m S0 7.6 29:07.21 firefox-bin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779849 Title: dbus-daemon consumes 100% CPU -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779849] Re: dbus-daemon consumes 100% CPU
Following up on the previous comment of mine. As I was closing down google-chrome, firefox Tomboy with Thunderbird 3.10 still running, I noticed the the dbus-daemon utilization had returned to near 0% I don't think that the other Apps shutting down had anything to do with the the dbus-daemon utilization returning to 0%, as navigating mail folders in Thunderbird certainly appears to have triggered the dbus_daemon CPU process utilization of 100%. I have rebooted the machine, and will keep an eye on the System Monitor window to see if dbus-daemon hist 100% -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779849 Title: dbus-daemon consumes 100% CPU -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 677148] Re: KDE crash occurs randomly within minutes of login
Yes, I'm not able to run apport-collect at this time, as I am using the machine at work, and it is not a good time to do this. Below is more information about the bug that may help in debug. The Xorg.5.log file is attached. The manifestation of the bug has changed in that, I am able to use KDE after the nvidia driver was recently updated. However, a native konsole, gnome-terminal, and xterm resize will cause a system freeze. Ctrl Alt F2 will not work. I need to telnet in from another machine to reboot. So instead of a random crash/freeze, I can cause the crash/freeze to occur at will. The following applications when run natively do NOT cause the system to crash/freeze: Firefox google-chrome dolphin okular tomboy thunderbird and miramar system-settings libreOffice eclipse A remote konsole, gnome-terminal, xterm resize do NOT cause the freeze issue. That is I run the command on a remote systems, with the DISPLAY environment variable set to my natty system. I can only reproduce this issue on a dual screen setup. I have 2 other machines with natty and KDE, and they do NOT exhibit this problem. I think the original bug report listed the graphics card, but I will list it here. nVidia quardo FX 580 I hope to have some timer next week to run apport-collect immediately after a crash/freeze. Robert On Wed, Apr 27, 2011 at 9:14 PM, bugbot 677...@bugs.launchpad.net wrote: Hey Robert, Hi, have you had a chance to test if this bug is still present in natty? If it does (and if you're the original reporter), please boot into natty and run the command: apport-collect bug-number which will update the bug with fresh logs and tag the bug as affecting natty. (It is best to run this right after reproducing the problem.) ** Changed in: xorg-server (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/677148 Title: KDE crash occurs randomly within minutes of login To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/677148/+subscribe ** Attachment added: Xorg.5.log https://bugs.launchpad.net/bugs/677148/+attachment/2096501/+files/Xorg.5.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677148 Title: KDE crash occurs randomly within minutes of login -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726343] Re: on login to xfce desktop, orca opens a terminal window with an error message
Also seeing this in Alpha 3 kubuntu on three machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726343 Title: on login to xfce desktop, orca opens a terminal window with an error message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 721921] Re: kernel crash when Cisco VPN client is started
Hi Jeremy, Thanks for responding to this bug. I have not had time to get the upstream kernel. I will try the 2.6.38-5-generic kernel this evening, and see if that works. Robert On Tue, Feb 22, 2011 at 8:07 AM, Jeremy Foshee 721...@bugs.launchpad.netwrote: Hi Robert, If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results. Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] ** Tags added: kj-triage ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/721921 Title: kernel crash when Cisco VPN client is started To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/721921/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721921 Title: kernel crash when Cisco VPN client is started -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721921] [NEW] kernel crash when Cisco VPN client is started
Public bug reported: Ubuntu natty release 11.04 Alpha2; uname -a output: Linux zac-laptop 2.6.38-4-generic #31-Ubuntu SMP Wed Feb 16 23:44:48 UTC 2011 i686 i686 i386 GNU/Linux Starting the Cisco VPN client with: /etc/init.d/vpnclient_init start will instantly crash the kernel. The Cisco VPN client source config.h file has the following entry: #define BUILDVER_STRING 4.8.02 (0030) This source woks fine in Ubuntu 10.10 with all kernels. Please refer to the attached file for the kernel stack trace, and the boot log. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-4-generic 2.6.38-4.31 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Uname: Linux 2.6.38-4-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rac1595 F pulseaudio /dev/snd/pcmC0D0p: rac1595 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdc44 irq 44' Mixer name : 'Realtek ALC861-VD' Components : 'HDA:10ec0862,11790104,0011 HDA:11c11040,11790001,00100200' Controls : 19 Simple ctrls : 12 Date: Sat Feb 19 13:14:39 2011 HibernationDevice: RESUME=UUID=838c7a6c-00f9-4c96-b83a-9502ab5ee178 Lsusb: Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite A135 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US LC_MESSAGES=en_US.UTF-8 SHELL=/bin/tcsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-4-generic root=UUID=0558cd80-78d9-40eb-8fe8-979d0dcceaaa ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-4-generic N/A linux-backports-modules-2.6.38-4-generic N/A linux-firmware 1.47 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux dmi.bios.date: 01/12/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: IAKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd01/12/2009:svnTOSHIBA:pnSatelliteA135:pvrPSAD0U-0N600N:rvnTOSHIBA:rnIAKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A135 dmi.product.version: PSAD0U-0N600N dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 kernel-net natty needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721921 Title: kernel crash when Cisco VPN client is started -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721921] Re: kernel crash when Cisco VPN client is started
** Attachment added: kern.log file showing the stack and boot messages https://bugs.launchpad.net/bugs/721921/+attachment/1860701/+files/cisco_vpn_crash_kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721921 Title: kernel crash when Cisco VPN client is started -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705747] [NEW] package python3 3.2~b2-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgrading from 10.10, and subsequent apt-get calls exhibit this issue. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: python3 3.2~b2-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37 Uname: Linux 2.6.37-12-generic i686 Architecture: i386 Date: Thu Jan 20 22:47:23 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all SourcePackage: python3-defaults Title: package python3 3.2~b2-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package 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/705747 Title: package python3 3.2~b2-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705747] Re: package python3 3.2~b2-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705747 Title: package python3 3.2~b2-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701160] [NEW] /usr/bin/xterm is not functional in natty
Public bug reported: I have the latest natty Alpha update, and when I open /usr/bin/xterm with compiz enabled under the classic Ubuntu Desktop, the xterm opens up with a title bar and a border, and the test area shows my background un-obscured. I do not see a shell prompt, and typing exit does not work in this window. None of the title bar buttons work either. I am able to raise and lower this window from the task bar, but that is the only functionality that I can get with this xterm. Bothe konsole and gnome-terminal appear to function properly. The hardware is a DELL laptop Latitiude D830 with a: [21.902] (II) NVIDIA(0): NVIDIA GPU Quadro NVS 135M (G86GL) at PCI:1:0:0 (GPU-0) Please see attached Xorg.0.log file for further X environment and nvidia driver information. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701160 Title: /usr/bin/xterm is not functional in natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701160] Re: /usr/bin/xterm is not functional in natty
** Attachment added: Xorg.0.log https://bugs.launchpad.net/bugs/701160/+attachment/1790353/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701160 Title: /usr/bin/xterm is not functional in natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 699915] [NEW] package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1 failed to install/upgrade: bcmwl kernel module failed to build
Public bug reported: This error occurred when running update-manager. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 Uname: Linux 2.6.37-11-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Fri Jan 7 09:11:19 2011 ErrorMessage: bcmwl kernel module failed to build InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113) PackageVersion: 5.100.82.38+bdcom-0ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1 failed to install/upgrade: bcmwl kernel module failed to build ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package 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/699915 Title: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1 failed to install/upgrade: bcmwl kernel module failed to build -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 699915] Re: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1 failed to install/upgrade: bcmwl kernel module failed to build
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/699915 Title: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1 failed to install/upgrade: bcmwl kernel module failed to build -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 698170] [NEW] class 'aptdaemon.lock.LockFailedError':
Public bug reported:
Binary package hint: aptdaemon
Crash occurred when running Update Manager.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.40+bzr529-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic i686
NonfreeKernelModules: nvidia wl
Annotation: Applying software changes failed
Architecture: i386
Date: Thu Jan 6 07:55:05 2011
DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
PackageArchitecture: all
SourcePackage: aptdaemon
Title: class 'aptdaemon.lock.LockFailedError':
TransactionDepends: [[], [], [], [], [], [], []]
TransactionKwargs: {}
TransactionLocale: en_US.UTF8
TransactionPackages: [[dbus.String(u'libfolks-telepathy19'),
dbus.String(u'libfolks19')], [], [], [], [dbus.String(u'e2fslibs'),
dbus.String(u'e2fsprogs'), dbus.String(u'empathy'),
dbus.String(u'empathy-common'), dbus.String(u'gnome-system-tools'),
dbus.String(u'gstreamer0.10-nice'), dbus.String(u'launchpad-integration'),
dbus.String(u'libcomerr2'), dbus.String(u'libglib2.0-0'),
dbus.String(u'libglib2.0-bin'), dbus.String(u'libglib2.0-data'),
dbus.String(u'liblaunchpad-integration-common'),
dbus.String(u'liblaunchpad-integration1'),
dbus.String(u'liblaunchpad-integration1.0-cil'),
dbus.String(u'liblpint-bonobo0'), dbus.String(u'libnice0'),
dbus.String(u'libss2'), dbus.String(u'linux-libc-dev'),
dbus.String(u'nautilus-sendto-empathy'),
dbus.String(u'python-launchpad-integration'), dbus.String(u'ubufox'),
dbus.String(u'ubuntu-mono'), dbus.String(u'xul-ext-ubufox'),
dbus.String(u'yelp')], []]
TransactionRole: role-commit-packages
** Affects: aptdaemon (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-crash 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/698170
Title:
class 'aptdaemon.lock.LockFailedError':
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 698170] Re: class 'aptdaemon.lock.LockFailedError':
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/698170 Title: class 'aptdaemon.lock.LockFailedError': -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677148] [NEW] KDE crash occurs randomly within minutes of login
Public bug reported: Binary package hint: xorg The bug causes the KDE window manager to crash, and the gdm login screen to appear after the crash. Running the exact set of applications under Gnome does NOT crash. Therefore this bug is specific to KDE, and may be related to using dual displays with Twinview enabled. I did not see this problem with KDE/Twinview in 10.04, but in 10.10 it randomly crashes. I am not able to reproduce the crash at will. It will occur randomly within a few minutes of starting the KDE session. I will attach the .xsession-errors and file to this bug report. Here is the grep -i fatal .xsession-errors.old output: [akonadiserver] FATAL ERROR: Upgrade failed kded4: Fatal IO error: client killed knotify4: Fatal IO error: client killed bluedevil-monolithic: Fatal IO error: client killed krunner: Fatal IO error: client killed kbluetooth: Fatal IO error: client killed polkit-kde-authentication-agent-1: Fatal IO error: client killed kglobalaccel: Fatal IO error: client killed plasma-desktop: Fatal IO error: client killed kdeinit4: Fatal IO error: client killed kwin: Fatal IO error: client killed kaccess: Fatal IO error: client killed ksmserver: Fatal IO error: client killed xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server :0.0 [/usr/bin/nepomukservicestub] nepomukservicestub: Fatal IO error: client killed [/usr/bin/nepomukservicestub] nepomukservicestub: Fatal IO error: client killed Eclipse: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. firefox-bin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. thunderbird-bin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. [/usr/bin/nepomukservicestub] nepomukservicestub: Fatal IO error: client killed [/usr/bin/nepomukservicestub] nepomukservicestub: Fatal IO error: client killed [/usr/bin/nepomukservicestub] nepomukservicestub: Fatal IO error: client killed [/usr/bin/nepomukservicestub] nepomukservicestub: Fatal IO error: client killed xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server :0.0 korgac: Fatal IO error: client killed klipper: Fatal IO error: client killed printer-applet: Fatal IO error: client killed [/usr/bin/akonadi_birthdays_resource] akonadi_birthdays_resource: Fatal IO error: client killed [/usr/bin/akonadi_ical_resource] akonadi_ical_resource: Fatal IO error: client killed kmix: Fatal IO error: client killed [/usr/bin/akonadi_maildir_resource] akonadi_maildir_resource: Fatal IO error: client killed [/usr/bin/akonadi_nepomuk_contact_feeder] akonadi_nepomuk_contact_feeder: Fatal IO error: client killed [/usr/bin/akonadi_kabc_resource] akonadi_kabc_resource: Fatal IO error: client killed [/usr/bin/akonadi_maildispatcher_agent] akonadi_maildispatcher_agent: Fatal IO error: client killed ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4 Uname: Linux 2.6.35-22-generic-pae i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 260.19.06 Mon Sep 13 06:35:06 PDT 2010 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) Architecture: i386 Date: Thu Nov 18 10:57:37 2010 DkmsStatus: nvidia-current, 260.19.06, 2.6.35-22-generic, i686: installed nvidia-current, 260.19.06, 2.6.35-22-generic-pae, i686: installed InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MachineType: Dell Inc. Precision WorkStation T3500 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=a35db284-f34c-4977-bac9-9c2fab0f9134 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/tcsh SourcePackage: xorg Symptom: display Title: Xorg crash dmi.bios.date: 09/09/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XPDFK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/09/2009:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn0XPDFK:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T3500 dmi.sys.vendor: Dell Inc. system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-22-generic-pae ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug crash i386 maverick -- KDE crash occurs randomly within minutes of login https://bugs.launchpad.net/bugs/677148 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 677148] Re: kded4: Fatal IO error: client killed
** Attachment added: xsession-errors https://bugs.launchpad.net/bugs/677148/+attachment/1737486/+files/xsession-errors -- KDE crash occurs randomly within minutes of login https://bugs.launchpad.net/bugs/677148 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 677148] Re: kded4: Fatal IO error: client killed
** Attachment added: Xorg.0.log.old https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/677148/+attachment/1737511/+files/Xorg.0.log.old ** Summary changed: - kded4: Fatal IO error: client killed + KDE crash occurs randomly within minutes of login -- KDE crash occurs randomly within minutes of login https://bugs.launchpad.net/bugs/677148 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 641297] Re: kded crashes at login
I have removed all of the obex modules, but KDE still crashes at login. If it matters, I'm running a Win7 64 ultimate VirtualBox 3.2.8 host, with Meerkat. Meerkat is at the latest release as of 2010.09.18 -- kded crashes at login https://bugs.launchpad.net/bugs/641297 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 641297] Re: kded crashes at login
Please find attached the .xsession-errors file that was rename to KDE_xsession_errors. ** Attachment added: KDE_xsession-errors https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/641297/+attachment/1604054/+files/KDE_xsession-errors -- kded crashes at login https://bugs.launchpad.net/bugs/641297 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 620015] Re: KDE freezes when starting gvim
The bug appears to have been fixed after I updated today (2010.09.14). The most significant update appeared to be the kernel, but I don't know if this was the root cause. This bug report can be removed/deleted. Thanks! -- KDE freezes when starting gvim https://bugs.launchpad.net/bugs/620015 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 620015] Re: KDE freezes when starting gvim
With the Beta release of Ubuntu 10.10, the KDE crash behavior has changed with regard to this bug. This bug is NOT specific to gvim/vim under Ubuntu 10.10/KDE. It is easily reproducible as follows: Start KDE, and run ANY client X application (xterm, konsole, gvim, ) that resides on a Red Hat 4 (RHEL4) host machine. The result is that KDE crashes, and the systems returns back to the login prompt. Local X client applications do not crash KDE. Running the same set of applications under Ubuntu 10.10 Gnome does not cause a crash. There are no errors listed in the /var/log/Xorg.* files. -- KDE freezes when starting gvim https://bugs.launchpad.net/bugs/620015 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 620015] Re: KDE freezes when starting gvim
The work around here is to start gvim with the --nofork option. -- KDE freezes when starting gvim https://bugs.launchpad.net/bugs/620015 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 620015] [NEW] KDE freezes when starting gvim
Public bug reported: Binary package hint: vim When I start the gvim application under KDE, the screen turns black, and only the mouse pomter is visivble. To resolve the issue, I have to ssh in, and sudo /etc/init.d/gdm restart twice. Killim the gvim process does NOT solve the problem. I have reviewed the various log files in /var/log, but I did not find any errors/warnings related to this hang. I have not tried gvim with Gnome to see if it causes the same issue. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: vim (not installed) ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed Aug 18 10:56:45 2010 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: LANGUAGE= LANG=en_US.utf8 SHELL=/bin/tcsh SourcePackage: vim ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- KDE freezes when starting gvim https://bugs.launchpad.net/bugs/620015 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
No commands needed. Just attach the 2 files that Martin requested. =Robert On 4/16/07, Mark Anton [EMAIL PROTECTED] wrote: I will be happy to, but I won't be able to until tonight when I get home to that computer. To get that info for you, I guess I need to type those commands in the terminal, right? On 4/16/07, Martin Pitt [EMAIL PROTECTED] wrote: Mark, can you please attach your /etc/network/interfaces and /var/log/daemon.log (after a fresh boot) here? -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
My previous comments stating that this bug was fixed, were premature. Apparently a recent update has caused the issue to return. I have the latest updates, and the original problem has re-appeared. Additional information, which may require separate bug reports: 1) my Gigabit PCMCIA card, a Trendnet TEG-PCBUSR, now comes up in 10MB mode. This previously worked reliably in feisty at 100MB and 1000MB. It always woked at 100MB and 1000MB in Edgy. 2) my 802.11g Netgear PCMCIA wireless card no longer comes up properly at boot time. Rebooting sometimes allows the card/network to come up. This also worked reliably in Edgy. I will provide more details on issues 1 and 2 above, when I can do more testing. Robert -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
This issue was apparently fixed through one of the feisty updates. I have not had any Ethernet configuration at startup up issues for over a week now. I consider this bug Fixed. Thanks Ubuntu Team! -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
I do not see this problem if fsck runs at boot time. This leads me to believe that this is a timing problem at boot time. I'm aware that changes were made to improve boot times in feisty. Since I never saw this problem in edgy, suspect the boot optimization(s) in feisty is causing the problem. I think the automatic fsck after 30 boots, gives the ethernet setup enough time to complete before other network steps are done. Others feisty users may not see this, because they are running on newer/faster hardware. Portion of /proc/cpuinfo cpu MHz : 746.793 cache size : 256 KB bogomips: 1494.79 -- Ethernet interface not configured at boot time https://launchpad.net/bugs/94095 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Ethernet interface not configured at boot time
Public bug reported: I recently did an upgrade from Ubuntu 6.10 to Ubuntu 7.04, and after booting or rebooting, my network is not configured. With 6.10, I had no issues with Wired or Wireless interfaces. For this bug report, only the wired interface is installed in my DELL Inspiron 5000e. After booting, the Active Connection Information popup has zeroes for all of the address and mask fields. If I double click on the network icon in the top panel then the network is configured. Output from: 'uname -a' Linux rac-laptop 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux Output from: 'cat /etc/lsb-release' DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.04 DISTRIB_CODENAME=feisty DISTRIB_DESCRIPTION=Ubuntu feisty (development branch) ### # Here is the output of ifconfig after booting: ### eth0 Link encap:Ethernet HWaddr 00:01:02:79:11:47 inet6 addr: fe80::201:2ff:fe79:1147/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:96 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6940 (6.7 KiB) TX bytes:8837 (8.6 KiB) Interrupt:11 Base address:0xa000 eth0:avah Link encap:Ethernet HWaddr 00:01:02:79:11:47 inet addr:169.254.3.24 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:11 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:100 (100.0 b) TX bytes:100 (100.0 b) ### # After double clicking the network icon in the top panel: ### eth0 Link encap:Ethernet HWaddr 00:01:02:79:11:47 inet addr:10.19.67.13 Bcast:10.19.67.255 Mask:255.255.254.0 inet6 addr: fe80::201:2ff:fe79:1147/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:336 errors:0 dropped:0 overruns:0 frame:0 TX packets:172 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:27372 (26.7 KiB) TX bytes:23429 (22.8 KiB) Interrupt:11 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:100 (100.0 b) TX bytes:100 (100.0 b) ### # /var/log/syslog: ### Mar 20 06:19:40 rac-laptop kernel: [ 30.084000] 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html Mar 20 06:19:40 rac-laptop kernel: [ 30.084000] :02:00.0: 3Com PCI 3CCFE575CT Tornado CardBus at d8a0c000. Mar 20 06:19:40 rac-laptop kernel: [ 30.084000] PCI: Setting latency timer of device :02:00.0 to 64 Mar 20 06:19:40 rac-laptop kernel: [ 30.596000] ACPI: PCI Interrupt :00:08.0[A] - Link [LNKD] - GSI 5 (level, low) - IRQ 5 Mar 20 06:19:40 rac-laptop kernel: [ 30.96] eth0: setting half-duplex. Mar 20 06:19:40 rac-laptop kernel: [ 31.204000] es1968: clocking to 48000 Mar 20 06:19:40 rac-laptop kernel: [ 31.34] Linux video capture interface: v2.00 Mar 20 06:19:40 rac-laptop kernel: [ 31.592000] lp0: using parport0 (interrupt-driven). Mar 20 06:19:40 rac-laptop kernel: [ 31.664000] Adding 746980k swap on /dev/disk/by-uuid/b82e1171-1d16-486b-b605-22207aef8915. Prio rity:-1 extents:1 across:746980k Mar 20 06:19:40 rac-laptop kernel: [ 31.80] EXT3 FS on sda1, internal journal Mar 20 06:19:40 rac-laptop kernel: [ 32.388000] NET: Registered protocol family 17 Mar 20 06:19:40 rac-laptop kernel: [ 33.96] eth0: setting full-duplex. Mar 20 06:19:41 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 Mar 20 06:19:46 rac-laptop dhcdbd: Started up. Mar 20 06:19:46 rac-laptop NetworkManager: information^Istarting... Mar 20 06:19:46 rac-laptop NetworkManager: information^Ieth0: Device is fully-supported using driver '3c59x'. Mar 20 06:19:46 rac-laptop NetworkManager: information^Inm_device_init(): waiting for device's worker thread to start Mar 20 06:19:46 rac-laptop NetworkManager: information^Inm_device_init(): device's worker thread started, continuing. Mar 20 06:19:46 rac-laptop NetworkManager: information^INow
