Re: [Bug 1431302] Re: gcc-4.8 does not terminate at computer shutdown
Hi Paul Sorry for a late response. I'm sure the bug can be recorded as closed. /*Alaric* using Ubuntu 16.04.4 LTS/ On 24/07/18 11:13, Paul White wrote: > Alaric, we are sorry that we do not always have the capacity to review > all reported bugs in a timely manner. You reported this bug some time > ago and there have been many changes in Ubuntu since that time. > > Presumably this problem was a one time occurrence and/or is no longer an > issue? Can the bug report now be closed? If we do not hear from you the > bug report will close itself in approximately 60 days time. > > Thank you again for helping make Ubuntu better. > > Paul White > [Ubuntu Bug Squad] > > > ** Changed in: ubuntu > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431302 Title: gcc-4.8 does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1431302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431303] Re: cc1 does not terminate at computer shutdown
Hi Paul I can't even no remember what the problem was, but given that I was using 14.04 LTS at the time, now on 16.04 LTS and about to migrate to 18.04 LTS, then I'm happy to call it closed. /*Alaric* using Ubuntu 16.04.4 LTS/ On 23/07/18 12:49, Paul White wrote: > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Presumably this problem was a one time occurrence and/or is no longer an > issue? Can the bug report now be closed? If we do not hear from you the > bug report will close itself in approximately 60 days time. > > Thank you again for helping make Ubuntu better. > > Paul White > [Ubuntu Bug Squad] > > > ** Changed in: ubuntu > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431303 Title: cc1 does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1431303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431303] Re: cc1 does not terminate at computer shutdown
It was an automated report from the system. The PC will not shut down and has to be 'hard-crashed' to switch off. On reboot it asked me to submit this bug report - along with several others - so I did. *Alaric Cundy* alaric.cu...@btinternet.com or ala...@mountnessingbridgeclub.org.uk /If you are fed up with your current operating system with its crashes, freezes, go-slows, security holes, viruses, etc - not to mention its cost - why not try the free-to-air and reliable alternative? The Ubuntu Distribution of LINUX is a complete operating system and application set that does not require special knowledge and it can be installed alongside, or instead of, your current system, or you can 'try before you install' without changing your system at all. It is particularly good for extending the working life of older computers - and all for free!/ On 12/03/15 17:56, Matthias Klose wrote: I don't see how this related to GCC ** Package changed: gcc-4.8 (Ubuntu) = ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431303 Title: cc1 does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1431303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431302] Re: gcc-4.8 does not terminate at computer shutdown
This particular desktop PC refuses to shut down (or to restart). Not even Alt+SysReq + etc works. Once, on restart after crashing out by holding down the Power button, it invited me to submit a whole host of bug reports that appeared to be linked to the failure to shut down - so I submitted them! This is just one of about 5 suggested submissions. Running under version 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431302 Title: gcc-4.8 does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1431302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431303] Re: cc1 does not terminate at computer shutdown
This particular desktop PC refuses to shut down (or to restart). Not even Alt+SysReq + etc works. Once, on restart after crashing out by holding down the Power button, it invited me to submit a whole host of bug reports that appeared to be linked to the failure to shut down - so I submitted them! This is just one of about 5 suggested submissions. Running under version 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431303 Title: cc1 does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1431303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431295] Re: as does not terminate at computer shutdown
This particular desktop PC refuses to shut down (or to restart). Not even Alt+SysReq + etc works. Once, on restart after crashing out by holding down the Power button, it invited me to submit a whole host of bug reports that appeared to be linked to the failure to shut down - so I submitted them! This is just one of about 5 suggested submissions. Running under version 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431295 Title: as does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1431295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431222] [NEW] pci_devices does not terminate at computer shutdown
Public bug reported: desktop machine fails to shut down ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Wed Mar 4 14:10:15 2015 ExecutablePath: /usr/lib/pm-utils/power.d/pci_devices InstallationDate: Installed on 2014-10-13 (149 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) InterpreterPath: /bin/dash OmitPids: 3513 563 3519 475 3620 563 3519 475 3620 PackageArchitecture: all ProcCmdline: /bin/sh /usr/lib/pm-utils/power.d/pci_devices false ProcEnviron: LC_COLLATE=C PATH=(custom, no user) SourcePackage: pm-utils Title: pci_devices does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431222 Title: pci_devices does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1431222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431222] [NEW] pci_devices does not terminate at computer shutdown
Public bug reported: desktop machine fails to shut down ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Wed Mar 4 14:10:15 2015 ExecutablePath: /usr/lib/pm-utils/power.d/pci_devices InstallationDate: Installed on 2014-10-13 (149 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) InterpreterPath: /bin/dash OmitPids: 3513 563 3519 475 3620 563 3519 475 3620 PackageArchitecture: all ProcCmdline: /bin/sh /usr/lib/pm-utils/power.d/pci_devices false ProcEnviron: LC_COLLATE=C PATH=(custom, no user) SourcePackage: pm-utils Title: pci_devices does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1431222 Title: pci_devices does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1431222/+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 1431299] [NEW] dash does not terminate at computer shutdown
Public bug reported: PC will not shut down or restart 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dash 0.5.7-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Thu Mar 12 11:12:32 2015 ExecutablePath: /bin/dash InstallationDate: Installed on 2014-10-13 (150 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) OmitPids: 15166 500 15172 435 15275 500 15172 435 15275 ProcEnviron: LC_COLLATE=C PATH=(custom, no user) LC_NUMERIC=C LANG=en_GB.UTF-8 SourcePackage: dash Title: dash does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431299 Title: dash does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1431299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431303] [NEW] cc1 does not terminate at computer shutdown
Public bug reported: PC will not shut down or restart 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cpp-4.8 4.8.2-19ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Thu Mar 12 11:12:32 2015 ExecutablePath: /usr/lib/gcc/i686-linux-gnu/4.8/cc1 InstallationDate: Installed on 2014-10-13 (150 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) OmitPids: 15166 500 15172 435 15275 500 15172 435 15275 ProcEnviron: LC_COLLATE=C PATH=(custom, no user) LANG=en_GB.UTF-8 LC_NUMERIC=C SourcePackage: gcc-4.8 Title: cc1 does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431303 Title: cc1 does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1431303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431309] [NEW] sleep does not terminate at computer shutdown
Public bug reported: PC will not shut down or restart 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: coreutils 8.21-1ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Thu Mar 12 11:12:33 2015 ExecutablePath: /bin/sleep InstallationDate: Installed on 2014-10-13 (150 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) OmitPids: 15166 500 15172 435 15275 500 15172 435 15275 ProcCmdline: sleep 3 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SourcePackage: coreutils Title: sleep does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431309 Title: sleep does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1431309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431308] [NEW] dkms does not terminate at computer shutdown
Public bug reported: PC does not shut down or restart 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dkms 2.2.0.3-1.1ubuntu5.14.04 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Thu Mar 12 11:12:32 2015 ExecutablePath: /usr/sbin/dkms InstallationDate: Installed on 2014-10-13 (150 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) InterpreterPath: /bin/bash OmitPids: 15166 500 15172 435 15275 500 15172 435 15275 PackageArchitecture: all ProcCmdline: /bin/bash /usr/sbin/dkms build -m bcmwl -v 6.30.223.248+bdcom -k 3.13.0-46-generic -a i686 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SourcePackage: dkms Title: dkms does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431308 Title: dkms does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1431308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431295] [NEW] as does not terminate at computer shutdown
Public bug reported: PC will not shut down or restart ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: binutils 2.24-5ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Thu Mar 12 11:12:33 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 zlib1g 1:1.2.8.dfsg-1ubuntu1 ExecutablePath: /usr/bin/as InstallationDate: Installed on 2014-10-13 (150 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) OmitPids: 15166 500 15172 435 15275 500 15172 435 15275 ProcCmdline: as -I /usr/src/linux-headers-3.13.0-46-generic/arch/x86/include -I arch/x86/include/generated -I include -I /usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/uapi -I arch/x86/include/generated/uapi -I /usr/src/linux-headers-3.13.0-46-generic/include/uapi -I include/generated/uapi -I ubuntu/include -I /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/include -I /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/common/include -I /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys -I /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/phy -I /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/ppr/include -I /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/bcmwifi/include --32 -mtune=generic32 -o /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/.tmp_wl_cfg80211_hybrid.o ProcEnviron: LC_COLLATE=C PATH=(custom, no user) LANG=en_GB.UTF-8 LC_NUMERIC=C SourcePackage: binutils Title: as does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431295 Title: as does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1431295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431302] [NEW] gcc-4.8 does not terminate at computer shutdown
Public bug reported: PC will not shut down or restart 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc-4.8 4.8.2-19ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Thu Mar 12 11:12:32 2015 ExecutablePath: /usr/bin/gcc-4.8 InstallationDate: Installed on 2014-10-13 (150 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) OmitPids: 15166 500 15172 435 15275 500 15172 435 15275 ProcEnviron: LC_COLLATE=C PATH=(custom, no user) LANG=en_GB.UTF-8 LC_NUMERIC=C SourcePackage: gcc-4.8 Title: gcc-4.8 does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431302 Title: gcc-4.8 does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1431302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431310] [NEW] common.postinst does not terminate at computer shutdown
Public bug reported: PC will not shut down or restart 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dkms 2.2.0.3-1.1ubuntu5.14.04 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Thu Mar 12 11:12:32 2015 ExecutablePath: /usr/lib/dkms/common.postinst InstallationDate: Installed on 2014-10-13 (150 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) InterpreterPath: /bin/dash OmitPids: 15166 500 15172 435 15275 500 15172 435 15275 PackageArchitecture: all ProcCmdline: /bin/sh /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl i686 6.30.223.141+bdcom-0ubuntu2 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SourcePackage: dkms Title: common.postinst does not terminate at computer shutdown UpgradeStatus: Upgraded to trusty on 2014-11-21 (111 days ago) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 shutdown-hang trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431310 Title: common.postinst does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1431310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247409] [NEW] Installation crashes when attempting to install on UEFI and mdadm enabled system on existing GPT partitions
Public bug reported: Could use a guide to help ensure all partitions are assigned for uefi to boot properly. From what I've seen online I have created a proper BIOS boot partition, but failed to create an EFI partition. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.26 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Date: Sat Nov 2 11:17:41 2013 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash -- LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubiquity-2.15.26 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247409 Title: Installation crashes when attempting to install on UEFI and mdadm enabled system on existing GPT partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1247409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176399] [NEW] ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
Public bug reported: Error message keeps popping up spontaneously ProblemType: Package DistroRelease: Ubuntu 12.10 Package: ndiswrapper-dkms 1.57-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 DKMSKernelVersion: 3.5.0-28-generic Date: Thu May 2 07:06:59 2013 InstallationDate: Installed on 2011-05-06 (728 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.57-1ubuntu1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build UpgradeStatus: Upgraded to quantal on 2012-10-22 (194 days ago) ** Affects: ndiswrapper (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176399 Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1176399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1023645] Re: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build [error: ‘struct kernel_stat’ has no member named ‘cpustat’]
I am not in control of these things - but I would hope so! I keep getting messages to say that it is a duplicate of some other bug that has already been reported, so it sounds as though it is being taken seriously. Alaric Cundy (alaric.cu...@btinternet.com or ala...@mountnessingbridgeclub.org.uk Sent from a pure 'Open Source' environment: Ubuntu (Linux) 12.10 Operating System, Thunderbird e-mail client, Libre Office, Firefox browser, Website management using SciTE (text editor) and bareFTP (File transfer) On 18/01/13 16:27, sam penny wrote: Is this bugfix expected to make its way into an update to Quantal at some point? What's the likely timescale for that? (I'm not all that familiar with the ubuntu release process, sorry!) Sam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1023645 Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build [error: ‘struct kernel_stat’ has no member named ‘cpustat’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1023645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101233] [NEW] ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
*** This bug is a duplicate of bug 1101167 *** https://bugs.launchpad.net/bugs/1101167 Public bug reported: I was applying a normal routine system upgrade via 'software updater' when this happened ProblemType: Package DistroRelease: Ubuntu 12.10 Package: ndiswrapper-dkms 1.57-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 DKMSKernelVersion: 3.5.0-22-generic Date: Fri Jan 18 14:56:35 2013 InstallationDate: Installed on 2011-05-06 (622 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.57-1ubuntu1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build UpgradeStatus: Upgraded to quantal on 2012-10-22 (87 days ago) ** Affects: ndiswrapper (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101233 Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1101233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092029] [NEW] ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
*** This bug is a duplicate of bug 1090675 *** https://bugs.launchpad.net/bugs/1090675 Public bug reported: Appeared as part of a routine software update on 19/12/2012 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: ndiswrapper-dkms 1.57-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 DKMSKernelVersion: 3.5.0-21-generic Date: Wed Dec 19 10:01:00 2012 InstallationDate: Installed on 2011-05-06 (592 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.57-1ubuntu1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build UpgradeStatus: Upgraded to quantal on 2012-10-22 (57 days ago) ** Affects: ndiswrapper (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092029 Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1092029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 877547] Re: dash run a command feature runs wrong command if command is typen too fast
*** This bug is a duplicate of bug 856205 *** https://bugs.launchpad.net/bugs/856205 I can confirm this bug. I realize it may not be high priority or a blocking issue, but this bug is severely aggravating. I've had to replace the dashboard as my default alt+f2 option. The reason power users love alt+f2 is that they can run their applications quickly and without any menus. Forcing the user to pause for a fraction of a second can be a difficult transition since power users have been trained in this behavior for years. This bug also has the potential to pose grave risks because it does in fact *run* the last command that a user has entered. Depending on what that application is, this bug could pose a risk to system stability. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/877547 Title: dash run a command feature runs wrong command if command is typen too fast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/877547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 871344] Re: Jockey cannot install FGLRX (AMD Graphics Driver)
I'm not sure if this is because of my chroot environment or not, but while attempting to reinstall fglrx with the command you suggested, I get several hundred lines of this: FATAL: Could not load /lib/modules/2.6.35-30-generic/modules.dep: No such file or directory Followed immediately by Loading new fglrx-8.881 DKMS files... It is likely that 2.6.35-30-generic belongs to a chroot's host Building only for 3.0.0-12-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. update-initramfs: deferring update (trigger activated) Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for gnome-menus ... Setting up fglrx-amdcccle (2:8.881-0ubuntu3) ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.0.0-12-generic Processing triggers for libc-bin ... ldconfig deferred processing now taking place Because of the Kernel complaints, I decided to do a bit more digging. Clearly CHRoot is causing the kernel version issue listed above. root@Hercules:/# uname -r 2.6.35-30-generic root@Hercules:/# ls /boot abi-3.0.0-11-generic config-3.0.0-12-generic initrd.img-3.0.0-11-generic memtest86+.bin System.map-3.0.0-12-generic vmlinuz-3.0.0-11-generic abi-3.0.0-12-generic grub initrd.img-3.0.0-12-generic memtest86+_multiboot.bin vmcoreinfo-3.0.0-11-generic vmlinuz-3.0.0-12-generic config-3.0.0-11-generic initrd.img-2.6.35-30-generic lost+found System.map-3.0.0-11-generic vmcoreinfo-3.0.0-12-generic However, it looks like it's still attempting to build for the 3.0 kernel, but fglrx appears to be missing the dependency for linux-source-3.0.0, so I'll attempt to install the sources for 3.0 and report back. On Wed, Oct 12, 2011 at 11:04 PM, Daniel van Vugt vanv...@gmail.com wrote: To clarify, I'm trying to remove Jockey from the equation. Installing fglrx directly and getting a copy of make.log will tell us exactly why fglrx is failing to install. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 871344] Re: Jockey cannot install FGLRX (AMD Graphics Driver)
After installing linux-source-3.0.0 and linux-headers-3.0.0-12-generic, the apt-get completed successfully and jockey is currently displaying a green activated icon besides the (non post-update) fglrx driver. I haven't tried restarting to test it yet because I'm going to install the post-release updates first. On Thu, Oct 13, 2011 at 10:44 AM, jro...@gmail.com jro...@gmail.com wrote: I'm not sure if this is because of my chroot environment or not, but while attempting to reinstall fglrx with the command you suggested, I get several hundred lines of this: FATAL: Could not load /lib/modules/2.6.35-30-generic/modules.dep: No such file or directory Followed immediately by Loading new fglrx-8.881 DKMS files... It is likely that 2.6.35-30-generic belongs to a chroot's host Building only for 3.0.0-12-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. update-initramfs: deferring update (trigger activated) Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for gnome-menus ... Setting up fglrx-amdcccle (2:8.881-0ubuntu3) ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.0.0-12-generic Processing triggers for libc-bin ... ldconfig deferred processing now taking place Because of the Kernel complaints, I decided to do a bit more digging. Clearly CHRoot is causing the kernel version issue listed above. root@Hercules:/# uname -r 2.6.35-30-generic root@Hercules:/# ls /boot abi-3.0.0-11-generic config-3.0.0-12-generic initrd.img-3.0.0-11-generic memtest86+.bin System.map-3.0.0-12-generic vmlinuz-3.0.0-11-generic abi-3.0.0-12-generic grub initrd.img-3.0.0-12-generic memtest86+_multiboot.bin vmcoreinfo-3.0.0-11-generic vmlinuz-3.0.0-12-generic config-3.0.0-11-generic initrd.img-2.6.35-30-generic lost+found System.map-3.0.0-11-generic vmcoreinfo-3.0.0-12-generic However, it looks like it's still attempting to build for the 3.0 kernel, but fglrx appears to be missing the dependency for linux-source-3.0.0, so I'll attempt to install the sources for 3.0 and report back. On Wed, Oct 12, 2011 at 11:04 PM, Daniel van Vugt vanv...@gmail.comwrote: To clarify, I'm trying to remove Jockey from the equation. Installing fglrx directly and getting a copy of make.log will tell us exactly why fglrx is failing to install. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 871344] Re: Jockey cannot install FGLRX (AMD Graphics Driver)
The installation of the post-release updates through jockey failed. I've attached the new log. Attempting to revert to the original package. Jockey claimed to revert to the original driver successfully, but I was unable to test the jockey based installation due (I believe) to some unreleated problems I was having with compiz. After deleting my compiz configurations (again, unrelated) and manually installing fglrx-updates, my system is up and running with fglrx enabled. It appears to me that the main issue here is that fglrx is lacking the kernel source/header dependencies. Regards, Jon On Thu, Oct 13, 2011 at 11:09 AM, jro...@gmail.com jro...@gmail.com wrote: After installing linux-source-3.0.0 and linux-headers-3.0.0-12-generic, the apt-get completed successfully and jockey is currently displaying a green activated icon besides the (non post-update) fglrx driver. I haven't tried restarting to test it yet because I'm going to install the post-release updates first. On Thu, Oct 13, 2011 at 10:44 AM, jro...@gmail.com jro...@gmail.comwrote: I'm not sure if this is because of my chroot environment or not, but while attempting to reinstall fglrx with the command you suggested, I get several hundred lines of this: FATAL: Could not load /lib/modules/2.6.35-30-generic/modules.dep: No such file or directory Followed immediately by Loading new fglrx-8.881 DKMS files... It is likely that 2.6.35-30-generic belongs to a chroot's host Building only for 3.0.0-12-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. update-initramfs: deferring update (trigger activated) Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for gnome-menus ... Setting up fglrx-amdcccle (2:8.881-0ubuntu3) ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.0.0-12-generic Processing triggers for libc-bin ... ldconfig deferred processing now taking place Because of the Kernel complaints, I decided to do a bit more digging. Clearly CHRoot is causing the kernel version issue listed above. root@Hercules:/# uname -r 2.6.35-30-generic root@Hercules:/# ls /boot abi-3.0.0-11-generic config-3.0.0-12-generic initrd.img-3.0.0-11-generic memtest86+.bin System.map-3.0.0-12-generic vmlinuz-3.0.0-11-generic abi-3.0.0-12-generic grub initrd.img-3.0.0-12-generic memtest86+_multiboot.bin vmcoreinfo-3.0.0-11-generic vmlinuz-3.0.0-12-generic config-3.0.0-11-generic initrd.img-2.6.35-30-generic lost+found System.map-3.0.0-11-generic vmcoreinfo-3.0.0-12-generic However, it looks like it's still attempting to build for the 3.0 kernel, but fglrx appears to be missing the dependency for linux-source-3.0.0, so I'll attempt to install the sources for 3.0 and report back. On Wed, Oct 12, 2011 at 11:04 PM, Daniel van Vugt vanv...@gmail.comwrote: To clarify, I'm trying to remove Jockey from the equation. Installing fglrx directly and getting a copy of make.log will tell us exactly why fglrx is failing to install. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions ** Attachment added: jockey.log https://bugs.launchpad.net/bugs/871344/+attachment/2540207/+files/jockey.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 871344] Re: Jockey cannot install FGLRX (AMD Graphics Driver)
Unfortunately I got it working through apt-get before receiving this message. I'm convinced that most of the problems were caused by the fact that the 3.0.0 kernel sources and headers were not a dependency of the fglrx or fglrx-updates packages. After installing them the apt-get commands you suggested completed successfully. Before installing them, apt complained about not having the sources available. Thanks for your help. If I find time this weekend, I'll reinstall 11.10 and try to replicate the bug on a clean system. Jon On Thu, Oct 13, 2011 at 11:00 PM, Daniel van Vugt vanv...@gmail.com wrote: Please attach make.log which can be found with this command: find /var/lib/dkms/fglrx* -name make.log But only if you continue to have problems. A log file from a working machine will not be useful. There are several bugs already logged against fglrx regarding its compatibility with different kernels. I really just want to see make.log so we can identify which of the known bugs this one is. Because it is almost certainly a duplicate of an existing bug. If this command succeeds, then you should have a working system: sudo apt-get install fglrx --reinstall If that command fails however, please find and attach make.log as requested above. Please ignore Jockey and its GUI while we are diagnosing this bug. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 871344] Re: Jockey cannot install FGLRX (AMD Graphics Driver)
Also, Let me add that the entire build folder appears to be empty. alaric@Hercules:/media/sdb7/var/lib/dkms/fglrx-updates/8.881/build$ ls -a . .. On Wed, Oct 12, 2011 at 9:29 AM, jro...@gmail.com jro...@gmail.com wrote: Hey, Sorry for the late response. I was on an extended vacation. I won't have physical access to the computer for a few hours, and because of this bug I'm currently still running Ubuntu 10.10. However, I ssh'd into the computer and managed to run the search command you provided on Sunday. Unfortunately, it didn't find anything. I can only assume that the files were cleared when I shut down the computer? What do I need to do to correctly generate that log file? alaric@Hercules:/media$ sudo mount /dev/sdb7 sdb7 alaric@Hercules:/media$ cd sdb7 alaric@Hercules:/media/sdb7$ for x in sys proc dev ; do sudo mount -B /$x $x ; done alaric@Hercules:/media/sdb7$ find var/lib/dkms/fglrx* -name make.log^C alaric@Hercules:/media/sdb7$ sudo chroot . root@Hercules:/# find /var/lib/dkms/fglrx -name make.log find: `/var/lib/dkms/fglrx': No such file or directory root@Hercules:/# find /var/lib/dkms/fglrx* -name make.log Regards, Jon Roose P.S., I have not had a chance to re-test fglrx installation since my original post. On Sun, Oct 9, 2011 at 10:37 PM, Daniel van Vugt vanv...@gmail.comwrote: In fact, you may need to use this command to find the log file: find /var/lib/dkms/fglrx* -name make.log -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 871344] Re: Jockey cannot install FGLRX (AMD Graphics Driver)
Hey, Sorry for the late response. I was on an extended vacation. I won't have physical access to the computer for a few hours, and because of this bug I'm currently still running Ubuntu 10.10. However, I ssh'd into the computer and managed to run the search command you provided on Sunday. Unfortunately, it didn't find anything. I can only assume that the files were cleared when I shut down the computer? What do I need to do to correctly generate that log file? alaric@Hercules:/media$ sudo mount /dev/sdb7 sdb7 alaric@Hercules:/media$ cd sdb7 alaric@Hercules:/media/sdb7$ for x in sys proc dev ; do sudo mount -B /$x $x ; done alaric@Hercules:/media/sdb7$ find var/lib/dkms/fglrx* -name make.log^C alaric@Hercules:/media/sdb7$ sudo chroot . root@Hercules:/# find /var/lib/dkms/fglrx -name make.log find: `/var/lib/dkms/fglrx': No such file or directory root@Hercules:/# find /var/lib/dkms/fglrx* -name make.log Regards, Jon Roose P.S., I have not had a chance to re-test fglrx installation since my original post. On Sun, Oct 9, 2011 at 10:37 PM, Daniel van Vugt vanv...@gmail.com wrote: In fact, you may need to use this command to find the log file: find /var/lib/dkms/fglrx* -name make.log -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871344] [NEW] Jockey cannot install FGLRX (AMD Graphics Driver)
Public bug reported: After installing the latest build of Oneric and updating my system, I am unable to install the FGLRX driver through jockey. It simply tells me: Sorry, installation of this driver failed. Please have a look at the log file for details: /var/log/jockey.log Because there are two separate drivers, there are two error sections in my jockey.log. Please find it attached. Other relevant information: Using a mostly clean system. I copied my home directory over from 10.10. Fully updated to the latest program versions residing on the standard repositories. My video card is an AMD Radeon 6670 HD. 01:00.0 VGA compatible controller: ATI Technologies Inc Turks XT [AMD Radeon HD 6600 Series] Regards, Alaric ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: jockey-gtk 0.9.4-0ubuntu10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 9 11:47:51 2011 MachineType: Gigabyte Technology Co., Ltd. GA-880GA-UD3H PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=590f8521-cbde-4496-9b9d-89160921adc1 ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FF dmi.board.name: GA-880GA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFF:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871344] Re: Jockey cannot install FGLRX (AMD Graphics Driver)
** Attachment added: My Jockey.log https://bugs.launchpad.net/bugs/871344/+attachment/2532760/+files/jockey.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871344 Title: Jockey cannot install FGLRX (AMD Graphics Driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/871344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737644] Re: xserver-xorg-video-radeon requires xorg-video-abi-9 but it is not installable
It appears that this problem now affects the package xserver-xorg- video-radeonhd. Could you please attempt to install the same patch on this package so that I can test my Radeon 6670HD? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737644 Title: xserver-xorg-video-radeon requires xorg-video-abi-9 but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/737644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737644] Re: xserver-xorg-video-radeon requires xorg-video-abi-9 but it is not installable
Sorry, I'm no longer certain this is the right location for this post, as I am utilizing the xorg-edgers repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737644 Title: xserver-xorg-video-radeon requires xorg-video-abi-9 but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/737644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640134] Re: cairo-dock with OpenGL crash after adding a second launch panel
This is still broken for me in Maverick. I have to start cairo-dock with the disable opengl -c argument in order to have it stay open. It crashes immediately on startup with no sign of failure, except that the dock never unhides itself. When I start cairo-dock manually with opengl (without -c) I am first put into maintenance, but when I close maintenance mode, it crashes. Here's relevant terminal output. ala...@alaric-laptop:~$ lsb_release -rd Description:Ubuntu maverick (development branch) Release:10.10 ala...@alaric-laptop:~$ apt-cache policy mesa-utils mesa-utils: Installed: 7.8.2-2ubuntu2 Candidate: 7.8.2-2ubuntu2 Version table: *** 7.8.2-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages 100 /var/lib/dpkg/status ala...@alaric-laptop:/$ lspci -nn | grep graphic -i 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) ala...@alaric-laptop:~$ apt-cache policy cairo-dock cairo-dock: Installed: 2.2.0-2-1ubuntu1~maverick Candidate: 2.2.0-2-1ubuntu1~maverick Version table: *** 2.2.0-2-1ubuntu1~maverick 0 500 http://ppa.launchpad.net/cairo-dock-team/ppa/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status 2.2.0~2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages ala...@alaric-laptop:~$ cairo-dock Cairo-Dock version: 2.2.0-2 Compiled date: Sep 18 2010 12:10:12 Running with OpenGL: 1 info on the system : Linux alaric-laptop 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux Couldn't guess if it was an applet's fault or not. It may have crashed inside the core or inside a thread Cairo-Dock version: 2.2.0-2 Compiled date: Sep 18 2010 12:10:12 Running with OpenGL: 1 showing the maintenance mode ... cairo_dock_set_status_message () on_delete_maintenance_gui () end of the maintenance mode. info on the system : Linux alaric-laptop 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux Couldn't guess if it was an applet's fault or not. It may have crashed inside the core or inside a thread Sorry, Cairo-Dock has encoutered some problems, and will quit. I upgraded my system to the Maverick beta last night, and at first all was well with opengl mode, but after apt-get upgrading the system it broke. Regards, Alaric -- cairo-dock with OpenGL crash after adding a second launch panel https://bugs.launchpad.net/bugs/640134 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 446394] Re: Connect to Hidden...select Saved Secure Connection; Connect not possible
Confirmed fixed in Lucid. -- Connect to Hidden...select Saved Secure Connection; Connect not possible https://bugs.launchpad.net/bugs/446394 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 387970] Re: cups asks for root password
I'm running Ubuntu 10.04 beta and this appears to be affecting a clean install. When I attempt to add a printer it prompts me for the root password that does not exist. I can also confirm that running gksudo rectifies the problem. For this reason, I feel system-config-printer (mine is version 1.1.91) should utilize gksudo for privelege escalation as opposed to the seemingly custom made box prompting for a root password. -- cups asks for root password https://bugs.launchpad.net/bugs/387970 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 552132] Re: gnome-appearance-properties crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Confirmed. Fix is in the repositories. Thanks for your quick work guys :) On Wed, Mar 31, 2010 at 6:17 AM, Mark m...@kempster.org wrote: Ran into this bug, updated packages, and can now launch Appearance Preferences. Thanks for the quick fix! -- gnome-appearance-properties crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/552132 You received this bug notification because you are a direct subscriber of the bug. -- gnome-appearance-properties crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/552132 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 552132] Re: gnome-appearance-properties crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Confirmed that using the appearance manager as root does not crash. Will not allow us to change settings for the primary user account though and therefore most settings are not changeable for the average user. -- gnome-appearance-properties crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/552132 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 446394] Re: Connect to Hidden...select Saved Secure Connection; Connect not possible
This problem is incredibly aggravating for average users. When is this fix going to hit the common repositories? I'm running a few fully upgraded karmic machines and all of them are experiencing these problems stemming from a release of network-manager from October (the newest available in the repositories). If this can be fixed by recompiling network-manager, could we have a link to the svn repository? I've searched for hours and can't seem to locate the source code of a newer version. On Wed, Jan 20, 2010 at 8:12 PM, Luís Silva luis.si...@axiomasoft.ptwrote: Isn't this going to get fixed in Karmic? -- Connect to Hidden...select Saved Secure Connection; Connect not possible https://bugs.launchpad.net/bugs/446394 You received this bug notification because you are a direct subscriber of a duplicate bug. -- Connect to Hidden...select Saved Secure Connection; Connect not possible https://bugs.launchpad.net/bugs/446394 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 399974] Re: 'Keep Aligned' option always resets to 'true' after desktop reload
Still an issue, fully upgraded. -- 'Keep Aligned' option always resets to 'true' after desktop reload https://bugs.launchpad.net/bugs/399974 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 443185] Re: Unable to activate Broadcom b43 after STA driver
Run apt-cache show jockey-common and post the results here. The update just hit my repository. Ran the update process about 6 hours ago and there was nothing, then a minute ago it updated jockey to the version listed above. I've also got a Inspiron 1545 and I'm about to test whether this will fix the issue or not (I installed the jockey update under VirtualBox through XP, but I'm sure plugging into the network will work just as well as for me). -- Unable to activate Broadcom b43 after STA driver https://bugs.launchpad.net/bugs/443185 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 443185] Re: Unable to activate Broadcom b43 after STA driver
B43 disappears because it is uninstalled by Jockey when switching to STA. It can be reinstalled and loaded, but will not work with network manager, and is not a bug in Jockey. STA requires a restart to update network-manager. Inspiron 1545 users, use STA, although it does still have a few bugs of its own. The update to jockey-common and jockey-gtk (0.5.5-0ubuntu2) allows STA to be loaded. It may have just today propagated through the repositories. -- Unable to activate Broadcom b43 after STA driver https://bugs.launchpad.net/bugs/443185 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 449287] Re: [karmic] Connect-to-Hidden... doesn't work for saved connections
Same here. Unable to connect to hidden wireless networks. Device Information Inspiron 1545 Network Card BCM4312 802.11b/g [14e4:4315] Network Information Security: WPA/WPA2 - Enterprise Authentication: PEAP Anonymous Identity: None CA Certificate: Thawte_Premium_Server_CA.pem Peap Version: Automatic Inner Auth: MSCHAPv2 Username: *** Password: BLANK GUI State Show Password Checkbox: Disabled, cannot change Cancel Button Enabled Connect Button Disabled It appears to me that NetworkManager is simply not retrieving the network password from the keyring because Password is greyed out. I never got a enter password for keyring prompt. -- [karmic] Connect-to-Hidden... doesn't work for saved connections https://bugs.launchpad.net/bugs/449287 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 449287] Re: [karmic] Connect-to-Hidden... doesn't work for saved connections
For more experienced users desperate for a quick fix, exchanging this attachment for the default file within the network-manager-gnome source file /src/wireless-dialog.c will allow you to edit the hidden network settings. Please keep in mind that (as you probably noticed) I have no affiliation with ubuntu except for using it as my desktop. I only added the single line is_new = true. -- [karmic] Connect-to-Hidden... doesn't work for saved connections https://bugs.launchpad.net/bugs/449287 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 449287] Re: [karmic] Connect-to-Hidden... doesn't work for saved connections
Here's the attachment ** Attachment added: wireless-dialog.c http://launchpadlibrarian.net/34379795/wireless-dialog.c -- [karmic] Connect-to-Hidden... doesn't work for saved connections https://bugs.launchpad.net/bugs/449287 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
