[Bug 309790] [NEW] nvidia-glx-71 fails to compile module
Public bug reported: Binary package hint: nvidia-glx-71 When installing nvidia-glx-71 (71.86.04-0ubuntu10), the post- installation compilation of the module produces this error: ubu...@ubuntu:~$ sudo apt-get install nvidia-glx-71 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: dkms fakeroot nvidia-71-kernel-source nvidia-settings patch Suggested packages: diff-doc The following NEW packages will be installed: dkms fakeroot nvidia-71-kernel-source nvidia-glx-71 nvidia-settings patch 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 5295kB/5509kB of archives. After this operation, 18.0MB of additional disk space will be used. Do you want to continue [Y/n]? Y Get:1 http://archive.ubuntu.com intrepid/main dkms 2.0.20.4-0ubuntu2 [55.5kB] Get:2 http://archive.ubuntu.com intrepid/restricted nvidia-71-kernel-source 71.86.04-0ubuntu10 [1419kB] Get:3 http://archive.ubuntu.com intrepid/restricted nvidia-glx-71 71.86.04-0ubuntu10 [3042kB] Get:4 http://archive.ubuntu.com intrepid/main nvidia-settings 177.78-0ubuntu2 [778kB] Fetched 5295kB in 44s (119kB/s) Selecting previously deselected package dkms. (Reading database ... 102335 files and directories currently installed.) Unpacking dkms (from .../dkms_2.0.20.4-0ubuntu2_all.deb) ... Selecting previously deselected package fakeroot. Unpacking fakeroot (from .../fakeroot_1.9.5ubuntu1_i386.deb) ... Selecting previously deselected package nvidia-71-kernel-source. Unpacking nvidia-71-kernel-source (from .../nvidia-71-kernel-source_71.86.04-0ubuntu10_i386.deb) ... Selecting previously deselected package nvidia-glx-71. Unpacking nvidia-glx-71 (from .../nvidia-glx-71_71.86.04-0ubuntu10_i386.deb) ... Selecting previously deselected package nvidia-settings. Unpacking nvidia-settings (from .../nvidia-settings_177.78-0ubuntu2_i386.deb) ... Selecting previously deselected package patch. Unpacking patch (from .../p/patch/patch_2.5.9-5_i386.deb) ... Processing triggers for man-db ... Setting up dkms (2.0.20.4-0ubuntu2) ... * Running DKMS auto installation service for kernel 2.6.27-7-generic[ OK ] Setting up fakeroot (1.9.5ubuntu1) ... Setting up nvidia-71-kernel-source (71.86.04-0ubuntu10) ... Removing all DKMS Modules Done. Adding Module to DKMS build system driver version= 71.86.04 Doing initial module build Error! Bad return status for module build on kernel: 2.6.27-7-generic (i686) Consult the make.log in the build directory /var/lib/dkms/nvidia/71.86.04/build/ for more information. Installing initial module Error! Could not locate nvidia.ko for module nvidia in the DKMS tree. You must run a dkms build for kernel 2.6.27-7-generic (i686) first. Done. Setting up nvidia-glx-71 (71.86.04-0ubuntu10) ... Setting up nvidia-settings (177.78-0ubuntu2) ... Setting up patch (2.5.9-5) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place This same build error occurs when I attempt to use nVidia's own installer, so it may be their bug against the newer kernel. lspci reports my nVidia card: 01:00.0 VGA compatible controller: nVidia Corporation NV15BR [GeForce2 Ultra, Bladerunner] (rev a4) which should reportedly be supported by the nvidia-glx-71 package. nvidia-detector returns none, which is obviously wrong, but documented elsewhere (on bug #292749). I first encountered this problem on an upgraded installation of 8.10. I have since replicated it on the 8.10 live CD (since I didn't trust that I had removed all traces of the old, manually-installed driver.) It occurs under both 2.6.27-7-generic and 2.6.27-10-generic. ** Affects: nvidia-graphics-drivers-71 (Ubuntu) Importance: Undecided Status: New -- nvidia-glx-71 fails to compile module https://bugs.launchpad.net/bugs/309790 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 309790] Re: nvidia-glx-71 fails to compile module
** Attachment added: Output of the failed build. http://launchpadlibrarian.net/20581723/make.log -- nvidia-glx-71 fails to compile module https://bugs.launchpad.net/bugs/309790 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 102511] Re: apt throws bzip2/gzip errors for duplicated sources.list entries or duplicated componenes (race condition?)
I agree with Ulrik: I have also never modified my sources.list except via the Synaptic interface. -- apt throws bzip2/gzip errors for duplicated sources.list entries or duplicated componenes (race condition?) https://bugs.launchpad.net/bugs/102511 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 108214] Re: cannot execute programs/scripts from USB drives
This is the opposite bug to #60722. Since USB drives that must interface with Windows are formatted with FAT, they lose all permission data, including the executable permission. Hence, when a FAT drive is mounted, either all the files must be marked as executable, or none. If they are all marked as executable, Nautilus will ask the user whether to Open or Execute the file when double-clicked, which is irritating and confusing for new users. I understand that this may not be an issue in KDE, but whatever change is made will affect both desktops. As I see it, it makes more sense to leave everything marked as non- executable and risk annoying advanced users (presumably, you can execute it using sh from the command line) rather than confusing new users. -- cannot execute programs/scripts from USB drives https://bugs.launchpad.net/bugs/108214 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 108214] Re: cannot execute programs/scripts from USB drives
I agree -- filesystems that support the execute bit should work, which is a bug. I did not realize you were talking about non-FAT drives... perhaps you could add reiserfs or ext to the bug description so this is clearer? -- cannot execute programs/scripts from USB drives https://bugs.launchpad.net/bugs/108214 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 86882] Re: lighttpd and apache2 conflict and break edgy upgrade
No, I was serious! I'm used to certain other open source projects that don't care about bugs, but I'll leave those unnamed. Thanks again for your work making Ubuntu even better. -- lighttpd and apache2 conflict and break edgy upgrade https://launchpad.net/bugs/86882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86882] Re: lighttpd and apache2 conflict and break edgy upgrade
Thanks for the quick resolution of this! -- lighttpd and apache2 conflict and break edgy upgrade https://launchpad.net/bugs/86882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86882] Re: lighttpd and apache2 conflict and break edgy upgrade
Attaching logs. ** Attachment added: Main upgrade log http://librarian.launchpad.net/6494655/main.log -- lighttpd and apache2 conflict and break edgy upgrade https://launchpad.net/bugs/86882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86882] Re: lighttpd and apache2 conflict and break edgy upgrade
Attaching logs. ** Attachment added: Term log http://librarian.launchpad.net/6494656/term.log -- lighttpd and apache2 conflict and break edgy upgrade https://launchpad.net/bugs/86882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86882] Re: lighttpd and apache2 conflict and break edgy upgrade
Attaching logs. ** Attachment added: apt upgrade log http://librarian.launchpad.net/6494650/apt.log -- lighttpd and apache2 conflict and break edgy upgrade https://launchpad.net/bugs/86882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86882] lighttpd and apache2 conflict and break edgy upgrade
Public bug reported: This bug results from having both lighttpd and apache2 installed prior to running the upgrade to Edgy. When lighttpd is updated, the installation script restarts the server. However, if you choose to replace the configuration file (the only option other than cancel), lighttpd will attempt to restart listening on port 80, which fails because apache2 has already claimed that port. This [fail] causes the installer to bring up an error dialog stating that the upgrade has failed. If left open, the installation continues successfully in the background, but once you click Close, it stops and warns you that you may have an unusable system. Everything appears fine, though. This is a strange problem, but lighttpd and apache2 *can* coexist if configured correctly. Presumably, the fix to simply not fail the install, since there is no real failure. Specifically, I used sudo update-manager -c -d to perform the update, and the contents of /var/log/dist-upgrades are attached. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- lighttpd and apache2 conflict and break edgy upgrade https://launchpad.net/bugs/86882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60722] Re: Set better umasks for FAT filesystems (USB drives etc)
The executable bit being set also causes Nautilus to ask the user what to do (Open or Execute) when a user double-clicks a file on a FAT USB disk. This can be confusing for users unfamiliar with executable permissions who simply expect the file to open in its associated program. -- Set better umasks for FAT filesystems (USB drives etc) https://launchpad.net/bugs/60722 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
