[Bug 576648] Re: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.)

2011-08-31 Thread JimmyTheGeek
My duplicate Bug #837381 is on the Ubuntu Ultimate Oz Onyx64 build. There is a Post-Install Information folder in your /home/username folder that explains how to configure your files for restart. Once that was done, I had to sudo apt-get-install nvidia-settings, and reboot twice. Once that was

[Bug 837381] [NEW] package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build

2011-08-30 Thread JimmyTheGeek
Public bug reported: Ubuntu 11.04. Additional Drivers application seemed to download the driver, but failed on install. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: nvidia-current 270.41.06-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0 Uname: Linux 3.0.0-7-generic

[Bug 837381] Re: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build

2011-08-30 Thread JimmyTheGeek
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/837381 Title: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build To manage

[Bug 818091] [NEW] package linux-image-2.6.32-33-generic 2.6.32-33.71 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2011-07-29 Thread JimmyTheGeek
Public bug reported: Something got screwed up during an update through Update Manager, not sure exactly what. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-33-generic 2.6.32-33.71 ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18 Uname: Linux

[Bug 818091] Re: package linux-image-2.6.32-33-generic 2.6.32-33.71 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2011-07-29 Thread JimmyTheGeek
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818091 Title: package linux-image-2.6.32-33-generic 2.6.32-33.71 failed to install/upgrade: subprocess installed post-installation script returned

[Bug 725601] Re: package build-essential 11.4build1 failed to install/upgrade: cannot access archive: No such file or directory

2011-06-20 Thread JimmyTheGeek
Running the sudo apt-get clean fixed it. I guess it was a corrupted download or something. Thanks for the help! ** Changed in: build-essential (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 725601] [NEW] package build-essential 11.4build1 failed to install/upgrade: cannot access archive: No such file or directory

2011-02-26 Thread JimmyTheGeek
Public bug reported: Binary package hint: build-essential package fails to install ProblemType: Package DistroRelease: Ubuntu 10.04 Package: build-essential 11.4build1 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic x86_64

[Bug 725601] Re: package build-essential 11.4build1 failed to install/upgrade: cannot access archive: No such file or directory

2011-02-26 Thread JimmyTheGeek
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/725601 Title: package build-essential 11.4build1 failed to install/upgrade: cannot access archive: No such file or directory -- ubuntu-bugs mailing

[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

2010-10-03 Thread JimmytheGeek
SOLVED I ran into this shortly after updating 9.10, got the black box in place of login screen, following log messages in /var/log/gdm/:0-greeter.log (gnome-settings-daemon:3419): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:3419): GLib-CRITICAL **:

Re: [Bug 643578] Re: Soundcard not detected

2010-09-21 Thread JimmyTheGeek
Back up and punt. I have no volume still, and I am smart enough to do such things before I bother you busy developers with a bug. However, I have been on your side of the aisle as well, and know that the simple things are often overlooked. Jim On Mon, 2010-09-20 at 23:50 +, Luke Yelavich

[Bug 643578] [NEW] Soundcard not detected

2010-09-20 Thread JimmyTheGeek
Public bug reported: Ran Update Manager this morning and now the sound doesn't work, doesn't detect the audio chipset. All channels in alsamixer are enabled turned up. Ubuntu 10.04.1 LTS alsa-base 1.0.22.1+dfsg-0ubuntu3 linux-sound-base 1.0.22.1+dfsg-0ubuntu3 libsdl1.2debian-alsa

[Bug 643578] Re: Soundcard not detected

2010-09-20 Thread JimmyTheGeek
** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/643578/+attachment/1613609/+files/AlsaDevices.txt ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/643578/+attachment/1613610/+files/AplayDevices.txt ** Attachment added: ArecordDevices.txt

[Bug 86575] Re: amaya crashes in feisty

2008-05-01 Thread JimmytheGeek
Mine is as follows: (amaya-bin:23614): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed The program 'amaya-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'.

[Bug 86575] Re: amaya crashes in feisty

2008-05-01 Thread JimmytheGeek
Okay. I uninstalled the 9.55 that came with Shift and dpkg-ed the 10.0.1 version from http://www.w3.org/Amaya/User/BinDist.html. It works fine now. Thanks to maintainers! -- amaya crashes in feisty https://bugs.launchpad.net/bugs/86575 You received this bug notification because you are a member

[Bug 86575] Re: amaya crashes in feisty

2008-04-30 Thread JimmytheGeek
** Also affects: amaya (Fluxbuntu) Importance: Undecided Status: New -- amaya crashes in feisty https://bugs.launchpad.net/bugs/86575 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list