Public bug reported:
I upgraded to hardy beta from gutsy. After upgrading, on reboot the
system just hung and eventually dumped me into a busybox. I was able to
boot into the 2.6.22 kernel. Once there I did
update-initramfs -k 2.6.24-12-386 -u
After that I was able to boot into the 2.6.24 kerne
I have the same problem. After upgrading to Hardy Heron Beta from Gutsy,
the 2.6.24 kernel hangs and dumps me into busybox. Using the 2.6.22
boots correctly.
--
BusyBox v1.1.3 starts instead of Ubuntu Hardy (db) Kernel 2.6.24-8-generic via
update-manager -d -c Gusty2Hardy
https://bugs.launchpad.
This was fixed in an upgrade.
--
suspend only works once
https://bugs.launchpad.net/bugs/147048
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/mail
My suspend problem seems to have been fixed in the recent upgrade.
--
suspend no longer works in gutsy
https://bugs.launchpad.net/bugs/147046
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@
I have the same problem after updating today 10/4/07. Now the get the 'failed
to initialize HAL'.
My battery monitor doesn't work, nm-applet broken, and I can't start various
menus in system->preferences such as power management.
--
[gutsy] failed to initialize hal
https://bugs.launchpad.net/b
I don't know if this is related but when I log out from a session, X seems to
restart completely as I get a terminal for a moment and then the nivida logo.
When I login desktop effects are re-enabled.
Also I often have to try to open the gl desktop menu twice, as the first
time nothing seems to
Upon removing that stuff things work fine without disabling dri. Sorry
about that.
--
Disable "dri" required for x20 (Rage Mobility P/M AGP 2x). Missing symbol
drmSetServerInfo in libdri.so
https://bugs.launchpad.net/bugs/146487
You received this bug notification because you are a member of Ubun
ldd /usr/lib/xorg/modules/extensions/libdri.so | grep drm
gives
libdrm.so.2 => /usr/local/lib/libdrm.so.2 (0xb7f9)
locate libdrm.so
gives
/usr/X11R6/lib/modules/linux/libdrm.so
/usr/X11R6/lib/modules/linux/dri-old.libdrm.so
/usr/lib/libdrm.so.2
/usr/lib/libdrm.so.2.3.0
/usr/lib/libdrm.so
/
Not sure if the bug report belongs here as the hardware is different but
there seem to be many report of similar bugs so tell me if I should
report somewhere else.
I have a thinkpad x20. Up till now (dapper, edgy, feisty) I could change the
screen brightness by using
fn + home or fn+end. This bro
I have not used any proprietary drivers. It is a quite old laptop
and the graphics card is not really capable of any real 3d acceleration.
I have attached the Xorg.0.log produced with dri disabled.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/9632690/Xorg.0.log
--
Disable "
Also I will attach the Xorg.0.log.old produced without disabling dri,
(where X doesn't start).
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/9632695/Xorg.0.log.old
--
Disable "dri" required for x20. Upgraded to gutsy x windows won't start with
missing symbol drmSetServ
Just a comment.
I tested that s2ram
(from uswsusp that I compiled myself as gutsy package is broken)
is able to suspend repeatedly perfectly fine.
--
suspend only works once
https://bugs.launchpad.net/bugs/147048
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: desktop-effects
I upgraded to gutsy and was playing around with the gl desktop effects.
I wanted to turn them off because it tends to make my laptop heat up.
I can turn them off but when I reboot they are back on.
** Affects: desktop-effects (Ubuntu)
Public bug reported:
Binary package hint: gnome-power-manager
A weird bug.
After upgrading to gutsy I thought suspend was working as it did work the first
time I suspended.
However, trying to suspend again and nothing happens. What I mean is once I
power on the machine I can suspend
once. Th
Public bug reported:
Binary package hint: gnome-power-manager
Not sure if its worth reporting since I've grown accustomed to suspend breaking
ever other kernel version,
but after upgrading to gutsy suspend does not work on my inspiron 8500.
what happens is the screen momentarily blanks and the
Sorry, sorry, sorry.
THis bug should be under uswsusp
--
uswsusp does not install s2ram
https://bugs.launchpad.net/bugs/147032
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.c
Public bug reported:
I believe this is a bug. The uswsusp package for gutsy does not appear to
install the s2ram command,
it does install s2disk, and s2both.
** Affects: ubuntu
Importance: Undecided
Status: New
--
uswsusp does not install s2ram
https://bugs.launchpad.net/bugs/14
Public bug reported:
Binary package hint: uswsusp
On upgrading to gutsy, the boot process hangs. If i do ctl-alt-f1 I get
a text console and the message
resume: Could not stat resume device '/dev/mapper/hda5'
please type in full path name to try again or press ENTER to boot sysem
pressing enter
I may not be having the same issue. I have no sound at all. Not in flash or
playing wav files.
This seems to be more severe than what others are reporting
lspci -v reports
00:0b.0 Multimedia audio controller: Cirrus Logic Crystal CS4281 PCI Audio (rev
01)
Subsystem: IBM Unknown device
I figured out a fix. I had to add
Section "Module"
Disable "dri"
EndSection
to xorg.conf.
Then everything works fine.
--
Upgraded to gutsy x windows won't start with missing symbol drmSetServerInfo in
libdri.so
https://bugs.launchpad.net/bugs/146487
You received this bug notification beca
I should also add, I get the same error trying to use vesa.
--
Upgraded to gutsy x windows won't start with missing symbol drmSetServerInfo in
libdri.so
https://bugs.launchpad.net/bugs/146487
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Also first think I did was run
dpkg-reconfigure xserver-xorg and it still did not work. Attached is the
xorg.conf generated by dpkg-reconfigure.
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/9553279/xorg.conf
--
Upgraded to gutsy x windows won't start with missing symbol d
Public bug reported:
I upgraded to gutsy on a thinkpad x20. On reboot X windows won't start
the contents of /var/log/gdm/:0.log are
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0
I was able to resolve by doing
sudo apt-get clean
sudo apt-get -f install
This downloaded a new copy of the package and then it installed. Thanks.
--
package texlive 2007-10 failed to install/upgrade:
https://bugs.launchpad.net/bugs/146209
You received this bug notification because you are a m
After the installation completed (with the above errors)
I tried to do
apt-get -f install
however that also fails with
(Reading database ... 256066 files and directories currently installed.)
Unpacking texlive-latex-base (from .../texlive-latex-base_2007-10_all.deb) ...
dpkg-deb (subprocess): e
I will also attach apt.log
** Attachment added: "apt.log"
http://launchpadlibrarian.net/9529659/apt.log
--
package texlive 2007-10 failed to install/upgrade:
https://bugs.launchpad.net/bugs/146209
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/9529639/Dependencies.txt
--
package texlive 2007-10 failed to install/upgrade:
https://bugs.launchpad.net/bugs/146209
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
Binary package hint: texlive-base
When upgrading from feisty to gutsy, the upgrade process was unable to
upgrade most of the texlive packages.
>From apt.log
Errors were encountered while processing:
texlive-latex-base
texlive-latex-recommended
texlive
tetex-bin
texlive
I had the same problem upgrading to gutsy. Many of the latex pacakges
were unable to upgrade/install.
from var/log/dist-upgrade/apt.log
Errors were encountered while processing:
texlive-latex-base
texlive-latex-recommended
texlive
tetex-bin
texlive-lang-polish
texlive-latex-extra
texlive-b
I believe this is how my xorg.conf file was originally set up before I started
changing drivers around.
Anyway I added the line as described and also set POST_VIDEO=false in
acpi-support.
With these setting I get the original behavious of the bug report. I can
suspend and resume one time. T
Desktop effects are not enabled.I did enable them for a bit when I
installed but then turned them off.
--
[nvidia-glx] can suspend/resume once, suspending a second time hangs,
nvidia-glx-legacy works
https://bugs.launchpad.net/bugs/109529
You received this bug notification because you are a memb
An additional observation. If I suspend and resume with the nv drivers. On
resume switching to a virtual terminal shuts off the screen and I have to
reboot to get it back on.
As long as I stay in X windows everything is fine and I can suspend and resume
as many times as I please.
But if I do c
Using the nv drivers with acpi-support modified as above I can
suspend/resume multiple times.
Not sure if its relevant but using the nv drivers I have a different screen
resolution than with the nvidia drivers as my display
is best with a 1680x1050 resolution.
Josh
--
[nvidia-glx] can suspen
Is there a way to reset to the defaults automatically, or can you tell
me which lines to change ( I don't remember which ones I modified.)
--
can suspend/resume once, suspending a second time hangs
https://bugs.launchpad.net/bugs/109529
You received this bug notification because you are a member
Attached is my acpi-support file. I already was using POST_VIDEO=False. I had
to tweak these a bit
in particular save_vbe_state, save_video_pci_state,and POST_VIDEO. I was
following various forums until it worked.
** Attachment added: "acpi-support.current"
http://librarian.launchpad.net/748
That fixed the boot issue (suspend still doesn't work properly)
--
can suspend/resume once, suspending a second time hangs
https://bugs.launchpad.net/bugs/109529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
That fixed it.
I removed /lib/linux-restricted-modules/.nvidia_new_installed and then I
rebooted and it went into X windows with no trouble.
--
can suspend/resume once, suspending a second time hangs
https://bugs.launchpad.net/bugs/109529
You received this bug notification because you are a memb
One additional oddity. I was able to get the nvidia-glx drivers to work using
by removing the other nvidia packages with
the --purge.
However, everytime I reboot X fails to start and i have to do
rmmod nvidia
nvidia-glx-config enable
/etc/init.d/gdm start
To get X to start with the glx modules.
dpkg -l nvidia-\* | grep ii
ii nvidia-glx 1.0.9631+2.6.20.5-15.20 NVIDIA binary XFree86
4.x/X.Org driver
ii nvidia-kernel-common20051028+1ubuntu7 NVIDIA binary kernel
module common files
lspci | grep -i nv
01:00.0 VGA compatible controller: nVidia Corporation NV
** Attachment added: "xorg.conf"
http://librarian.launchpad.net/7477373/xorg.conf
--
can suspend/resume once, suspending a second time hangs
https://bugs.launchpad.net/bugs/109529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7477364/dmesg.txt
--
can suspend/resume once, suspending a second time hangs
https://bugs.launchpad.net/bugs/109529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: "Xorg.0.log"
http://librarian.launchpad.net/7477362/Xorg.0.log
--
can suspend/resume once, suspending a second time hangs
https://bugs.launchpad.net/bugs/109529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
I'm having trouble going back to the nvidia-glx drivers to produce the
log files for you, (though the nvidia-glx-legacy works fine).
I have an xorg.conf file that works fine with nvidia-glx-legacy.
If I install nvidia-glx-new using apt-get then when I reboot
X-windows fails to start
it gives
I can't suspend with the nv drivers at all.
This may be due to the fact that in order to get suspend to work with the
nividia card I had to change some things in
/etc/default/acpi-support.
When I resume from suspend with nv drivers I just get a blank screen and then
the fan goes to max indicati
This appears to actually be a bug in the newer nvidia video drivers,
the ata errors seem to be a separate problem. If I switch the nvidia-
legacy drivers than I can suspend multiple times with no problem.
Josh
--
c
Public bug reported:
I have a dell inspiron 8500 upgraded to feisty (through edgy) from dapper.
In dapper suspend/resume worked fine (once I set /etc/default/acpi-support
correctly.)
In feisty, after booting up I can suspend and resume successfully one time. If
I at any time suspend a second
Public bug reported:
As far as I can tell the vtk package went to a new version in edgy but vtkdata
did not change. The files themselves are fine its just the examples in the
newer version of vtk are looking for the directory /usr/share/VTKData while by
default vtkdata is at
/usr/share/vtkdata
I also wanted to say that it would be nice if a newer version of kismet
was in the repositories. I have a broadcom chip and it works great with
the latest kismet compiled from source. It would be nice if it was apt-
getabble.
--
kismet: UVF exception request for 2006-04-R1
https://launchpad.net/b
I thought I would report something regarding this. I had the same issue
as the orignal bug report, I could scan but not connect. Based on this
thread I compiled a 2.6.17 kernel (vanila from kernel.org ) and used the
edgy firmware and now the card works fine.
--
[atmel] breezy->dapper wifi lost: s
49 matches
Mail list logo
