Public bug reported:
In newly installed Intrepid
Standard boot up results in being dumped into the busybox prompt (initramfs).
If I type exit then a normal bootup resumes.
Error hard to locate from the log files. The only suspicious entry found in
/var/log/messages:
Jul 1 12:07:46 amd64 kernel
** Attachment added: "dmesg"
http://launchpadlibrarian.net/15738184/dmesg
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
On the Ubuntu forums a workaround for this bug was posted. It consists
of passing the kernel option
rootdelay=130
at the boot.
I can confirm that this works for both systems mentioned above
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
You received this
I am still getting this problem with
cupsys 1.3.9-2ubuntu3
in intrepid fully updated (November 26)
The error message is
/usr/lib/cups/filter/pstopdf failed
The printer is a xerox pahser 6350dp with latest ppd installed
I have attached the troubleshooting file produced
** Attachment added: "t
** Changed in: cups (Ubuntu Intrepid)
Status: Fix Released => In Progress
--
"/usr/lib/cups/filter/pstopdf failed" in error_log and only blank page printed
https://bugs.launchpad.net/bugs/289759
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Till, I have attached the requested file which follows the unsuccessful
print job. I have tried the print on 3 different machines (2 i386 one
amd64) with identical results.
Martin, sorry for switching status, I will lodge a new bug report
shortly.
Richard
** Attachment added: "error_log"
http
The file was in abiword. It prints OK to a PDF file (PDF "printer") and
this will print. If I choose the generic postscript printer and save to
a postscript file (output.ps) then both gv and gs have trouble with the
file as you suspected. In particular when these apps hit the second page
which has
Public bug reported:
Binary package hint: abiword
The attached file does not print. If I print it to a postscript file
both gv and gs crash on the second page which contains a graphic. It can
be printed to the usual PDF printer file and then this will print. It
appears that abiword is producing c
** Attachment added: "math paper.abw"
http://launchpadlibrarian.net/19968170/math%20paper.abw
--
Files with graphics do not print
https://bugs.launchpad.net/bugs/302506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug *appears* to affect the intrepid version of abiword only.
--
Files with graphics do not print
https://bugs.launchpad.net/bugs/302506
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.
OK new abiword bugreport opened.
https://bugs.edge.launchpad.net/ubuntu/+source/abiword/+bug/302506
--
"/usr/lib/cups/filter/pstopdf failed" in error_log and only blank page printed
https://bugs.launchpad.net/bugs/289759
You received this bug notification because you are a member of Ubuntu
Bugs,
I am the reporter of duplicate bug 244608.
With the updated kernel 2.6.27.10.13 my system still does not boot
lspci gives
00:00.0 Host bridge: Intel Corporation E7525 Memory Controller Hub (rev 0c)
00:00.1 Class ff00: Intel Corporation E7525/E7520 Error Reporting Registers
(rev 0c)
00:02.0 PCI
Sorry I should have said I was using
kernel 2.6.27.10.20
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
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
Fixed for me in version 2.6.28-12 of the kernel. Relative to the old
kernels in 8.04 the boot time is now much faster as well.
Thanks for fixing this!
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member
I tested this on the following kernels
2.6.28-9
2.6.29-rc7
The problem remains the same for both.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have made some progress in debugging this by adding the debug option
to the grub boot line.
This produces a file /tmp/initramfs.debug which can be seen when at the
busybox prompt
This file contains the following significant line near the end:
panic ALERT! /dev/disk/by-uuid/04432635-ee53-4a9e-b
and the hardy /etc/fstab
** Attachment added: "fstab"
http://launchpadlibrarian.net/18502621/fstab
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This problem now affects two of my systems. The second system is i386
while the first (see above) was amd64. Both systems stop because the
root partition is not found. Both systems have scsi hard disks so I am
guessing this is some kind of scsi disk driver issue.
--
Intrepid Bootup dumped into bu
Problem still apparent in the release candidate version of Intrepid.
I have attached the initramfs.debug file
** Attachment added: "initramfs.debug"
http://launchpadlibrarian.net/18870310/initramfs.debug
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
Yo
I am using a 2.6.26 kernel in hardy which loads the e1000e module on a
Thinkpad X300. I have not seen any problems but as a precaution have
blacklisted the module by hand by adding the line
blacklist e1000e
to the end of the file
/etc/modprobe.d/blacklist
This prevents the module loading when
Dan,
Could you explain the fix released? Is it the latest kernel you are referring
to?
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug is in an alpha release which is using a release candidate
version of the kernel so I think your comments are too tough. Why don't
you use hardy as suggested in many places in Ubuntu documentation?
My only concern about the present bug is that it discourages testers of
alpha software who m
Problem still present as of October 5 fully updated Intrepid system.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
You received this bug notification because you are a member of Ubuntu
uname -a gives
Linux amd64 2.6.26-5-generic #1 SMP Sun Aug 3 01:26:00 UTC 2008 x86_64 GNU/Linux
dmesg attached
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/16693886/dmesg.log
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
You received
lspci -vvnn attached
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/16693893/lspci-vvnn.log
--
Intrepid Bootup dumped into busybox console
https://bugs.launchpad.net/bugs/244608
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The 2.6.28-2 kernel in intrepid does not solve this for me.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
OK I tested the 2.6.27-1 kernel and the problem persists. In addition it
is now saying it cannot find the swap partition within busybox after
typing "exit". If I press "enter" anyway (as suggested the boot appears
normal. Please let me know if you need any further tests done. I have a
suspicion gi
Some good news at last!
With the latest Jaunty kernel (2.6.28-11-generic) this problem has
disappeared. I have tried a large number of different kernels and this
is the only one since intrepid's first kernel that does not have the
problem. Let me know if you need any more information from my syste
OK I retried this with the 2.6.28-11-generic and unfortunately it is not
working so the fix I reported
does not work. It is weird that it should boot OK one time and not the next.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notifica
Still occurring in version 1:0.111.1
--
update-manager crashed with AttributeError in checkFreeSpace()
https://bugs.launchpad.net/bugs/340828
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.
I tried the kernel provided by Andy and the problem remains. I used the
amd64 version of the kernel.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: linux-source-2.6.17
On edgy the 2.6.17-2 kernel does not boot and reports error messages for
the aic79xx driver similar to those seen earlier in the dapper
development cycle (see fixed bug 14394). In particular the driver
reports missing libraries with th
This problem also occured for the aic79xx driver but was fixed in the
release 2.6.15 kernel. It reappeared in the Edgy 2.6.17 kernel. See bug
# 50684.
--
aic7xxx fails to load
https://launchpad.net/bugs/41061
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
Fix did not do the trick. Boot still freezes at the root file system
stage i.e. the same stage. I cannot record the kernel messages because
it was a hard lockup.
--
aic79xx broken
https://launchpad.net/bugs/50684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
Public bug reported:
My laptop has a dlink DWL-G650 wireless pcmcia card which was supported
by the madwifi drivers from this package in Dapper. It worked flawlessly
in Dapper but does not work with the release candidate for edgy. There
are numerous error messages in dmesg to the effect that symbo
I can confirm this and the dmesg output. This looks like a duplicate of
67601
--
Atheros support isn't working in 2.6.17-10-generic
https://launchpad.net/bugs/68139
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The Debian unstable version imposes this dependency. I compiled proper
Debian packages on Dapper using the lyx developers Debian script without
issue so I suspect the dependency is too strict but hey I am not privy
to the Debian lyx maintainers logic. I can lodge a complaint on the
Debian maintaine
Version 2.6.17-5 boots normally now.
--
aic79xx broken
https://launchpad.net/bugs/50684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 52405 ***
** This bug has been marked a duplicate of bug 52405
gnome-panel eats 50% cpu for half an hour and flickers
--
The applications menu flickers
https://launchpad.net/bugs/52942
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Confirmed here on edgy. Has been an issue for around two weeks of
updates.
** Bug 52942 has been marked a duplicate of this bug
--
gnome-panel eats 50% cpu for half an hour and flickers
https://launchpad.net/bugs/52405
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Public bug reported:
Binary package hint: linux-image-2.6.17-7-generic
System is a dual em64t xeon system.
Completely updated edgy system (September 19)
Boot appears normal until a freeze occurs which needs a hard reboot.
Last commands seen in boot messages are from the usb system but the fourth
This error also occured on previous kernel 2.6.17-7-generic but DID NOT
on the kernel before the generic one was introduced.
--
Kernel Freeze on boot
https://launchpad.net/bugs/61344
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I am booting from a Dapper /boot/grub/menu.lst and am updating
the system using chroot and aptitude on the mounted Edgy partition (/test).
Could this be the problem?
BTW the Edgy knot 2 livecd also failed to boot apparently for the same
reason.
I looked in the /boot/grub/menu.lst and found that
The boot lines were:
title Ubuntutest
root(hd0,9)
kernel /boot/vmlinuz-2.6.17-8-generic root=/dev/sda10 ro
initrd /boot/initrd.img-2.6.17-8-generic
savedefault
boot
--
Kernel Freeze on boot
https://launchpad.net/bugs/61344
--
ubuntu-bugs mailing list
ub
OK I tried knot 3 and the system booted fine.
I will reinstall my edgy partition.
Sorry for the false alarm Ben.
--
Kernel Freeze on boot
https://launchpad.net/bugs/61344
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I had a similar problem which I originally reported as a kernel issue.
After 2.6.17-7 (8 and 9) the system would not boot with the error:
Begin: Waiting for root file system
My /etc/fstab shows:
# /etc/fstab: static file system information.
#
#
proc/proc pro
Please read the thread above before commenting. evms is removed if the
standard and recommended method for upgrading feisty (i.e. upgrade-
manager) is used.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are
Confirmed that this seems to be a kernel issue. If I boot the old Feisty kernel
(2.6.20-16) the problem does not occur.
I tried the 2.6.22-14-rt kernel and the problem is still present. I read on the
kernel list that this problem has been noted and fixed in the rc series for the
2.6.23 series.
I should have added I am using the 64bit OS with emt64 dual xeon
processor.
--
Shutdown results in a reboot
https://bugs.launchpad.net/bugs/151969
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-
Tested on October 6 with fully updated gutsy system and works perfectly.
Thanks Till.
--
MASTER: Printing via HPLIP does not work any more
https://bugs.launchpad.net/bugs/147369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
Scott,
I am a bit concerned about this bug. The fix has been released (latest gutsy
update of evms) but people with current gutsy are still reporting this as an
issue. Should people check the version of evms and confirm the fix is not
working?
--
Device-mapper errors: dm-linear, lookup failed
Hmmm here is the changelog entry for upgrade-manager
- mark evms as obsolete if it is not in use
10 July 2007
And it has switched from main to universe(for fresh installs)
Wonder why this change didn't work for Manfred?
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launc
Yes the issue has not occurred again. Must have been a glitch.
--
df does not list root directory
https://bugs.launchpad.net/bugs/104190
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
Scott,
Sorry to be a pain but I am confused about this bug. It seems upgrades
to Gutsy beta from Feisty are not removing evms. Will this change when
the distro goes "live" i.e. will the changes of July 10 in update-
manager which cause evms to be removed come into effect when the distro
is release
** Also affects: update-manager (Baltix)
Importance: Undecided
Status: New
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: baltix
Sourcepackagename: update-manager => None
** Changed in: baltix
Status: New => Invalid
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You r
I have added update-manager to the affected packages list since this
*appears* to be a bug there. Any comment by this package maintainer
greatly appreciated.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are
Thanks Kees. That should solve this problem for nearly all users.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I can confirm that this is not yet fixed in update-manager on Feisty. I
upgraded my main system to the Gutsy release candidate last night (using
update-manager -d) and evms was not listed for removal. When the 2.6.22
kernel was booted this bug appeared with a vengeance preventing a boot.
the 2.6.20
Public bug reported:
I upgraded from Feisty to Gutsy on October 12 (i.e. the release
candidate) and when I click on the Logoff/switch user/lock screen/power
off icon and select Shutdown the system reboots instead of powering off.
** Affects: gnome-desktop (Ubuntu)
Importance: Undecided
Here is mine (after apt-get removal of evms and reboot in gutsy):
/dev/sda5 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock
All the following simply reboot the machine:
1) sudo shutdown -h now
2) /sbin/shutdown -h now "Shut Down via gdm."
3) Power off on the kde desktop
This sounds a bit severe and likely not a gnome issue correct?
--
Shutdown results in a reboot
https://bugs.launchpad.net/bugs/151969
You received th
Other one
** Attachment added: "gdm.conf-custom"
http://launchpadlibrarian.net/9952265/gdm.conf-custom
--
Shutdown results in a reboot
https://bugs.launchpad.net/bugs/151969
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
Files are attached
** Attachment added: "gdm.conf"
http://launchpadlibrarian.net/9952261/gdm.conf
--
Shutdown results in a reboot
https://bugs.launchpad.net/bugs/151969
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
Public bug reported:
Binary package hint: system-config-printer
A usb connected printer can be configured fine manually but does not
work when automatically detected.
In the first case the device uri used is
usb://hp/photosmart%207550?serial=CN33I4116P7E
while in the automatic case that fails
Other messages include
Sep 30 16:15:40 richard-desktop photosmart_7550?serial=CN33I4116P7E:
io/hpmud/musb.c 549: invalid product id string: Operation not permitted
Sep 30 16:15:40 richard-desktop photosmart_7550?serial=CN33I4116P7E:
io/hpmud/musb.c 1003: unable to open
hp:/usb/photosmart_7550?
After automatic and manual configuration:
HP Linux Imaging and Printing System (ver. 2.7.7)
Printer Discovery Utility ver. 3.2
Copyright (c) 2001-7 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
OK so I did this after the automatic configuration of the printer (not
the manual)
lpinfo -l -v gives:
Device: uri = socket
class = network
info = AppSocket/HP JetDirect
make-and-model = Unknown
device-id =
Device: uri = beh
class = network
info =
I notice that the uri reported by lpinfo is the one that the manual
configure of the printer picks up (see first post).This is despite the
automatic configuration already being in place
--
system-config-printer fails to automatically configure a printer
https://bugs.launchpad.net/bugs/147369
Results of the 3 tests:
1. /usr/lib/cups/backend/hp
direct hp:/usb/photosmart_7550?serial=CN33I4116P7E "HP photosmart 7550"
"HP photosmart 7550 USB CN33I4116P7E HPLIP" "MFG:HP;MDL:photosmart
7550;CLS:PRINTER;DES:photosmart 7550;SN:CN33I4116P7E;"
2. Results same as 1.
3. Printing still fails
--
I added this file (55-hpmud.rules) in /etc/udev/rules.d as root
and the problem is solved i.e. the automatically configured printer now works.
dodgy_pro does it work for you also (with the automatic configuration of the
printer I mean)?
--
system-config-printer fails to automatically configure a
An editorial ;-) (sorry about the didactic tone):
It is bugs like this that can give a distro a bad name. If I plug in my
common as dirt hp printer and the yellow dialog tells me it is
configured and ready to go and then it doesn't work your typical user
will be quite discouraged. There are 16 day
Great thanks Till!
--
system-config-printer fails to automatically configure a printer
https://bugs.launchpad.net/bugs/147369
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
Yes I have tried the permissions change as well and it works. Two problems: An
ordinary
user should not face this. Those permissions may potentially pose a security
issue in some situations.
--
xsane fails to find scanner
https://bugs.launchpad.net/bugs/181129
You received this bug notification
The update fixes the problem on my system. I note however that the
scanning function of xsane does not work for my scanner unless sane-
utils is also installed. Should this package be a compulsory dependency
of libsane (it is only recommended at present)?
--
access to usb device denied in latest
Public bug reported:
On a 64bit system the application does not open. At a terminal it just sits
waiting for some time then closes.
While waiting it consumes 90% of cpu.
I have attached an strace file.
** Affects: kompozer (Ubuntu)
Importance: Undecided
Status: New
--
(Hardy) app
** Attachment added: "kompozer.txt"
http://launchpadlibrarian.net/13408718/kompozer.txt
--
(Hardy) application does not open
https://bugs.launchpad.net/bugs/216817
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Such a delay is not present on my system and 1.5 works perfectly on
gutsy for me. I have read of similar issues on the lyx-devel mailing
list and they are usually very specific graphics problems. I suggest you
post your problem there. 1.5 uses qt4 unlike the 1.4 series which used
qt3..
--
lyx
Yes it appears so Scott. I am assuming that this part of the new hardy
hardware hardware spec is where something is amiss:
"Drop the default system groups plugdev and scanner. Enable ConsoleKit
support in hal, which assigns read/write permission to removable USB
devices with dynamic ACLs."
Taken
Upgraded to the latest kernel and the problem remains. The 'uname -a'
output is:
Linux ubuntu 2.6.24-4-generic #1 SMP Mon Jan 14 18:19:11 UTC 2008 x86_64
GNU/Linux
--
xsane fails to find scanner
https://bugs.launchpad.net/bugs/181129
You received this bug notification because you are a member of
The file
/etc/udev/rules.d/45-libsane.rules
which SHOULD be in libsane is missing on my hardy system. This would
explain this bug.
** Changed in: sane-backends (Ubuntu)
Sourcepackagename: sane-frontends => sane-backends
--
xsane fails to find scanner
https://bugs.launchpad.net/bugs/181129
You
I found this in the changelog for sane-backends
* Do not install the udev rules, since hal now provides dynamic ACLs on
device nodes. (See hardy-hardware-detection spec.)
* debian/libsane.postinst: Do not create the scanner group.
* debian/libsane.postinst: Remove obsolete udev rules on u
Since there is no longer a scanner group and the file
/etc/udev/rules.d/40-permissions.rules
sets the permissions of /dev/bus/usb (and subdirectories) to be 0664
this means only root (the group now for usb scanners?) can access the device
for writing.
If Scott Remnant the maintainer of udev i
** Also affects: udev
Importance: Undecided
Status: New
--
xsane fails to find scanner
https://bugs.launchpad.net/bugs/181129
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.
Just as a postscript on this if you do upgrade the kernel:
I noticed a couple of weeks later that my usb devices had disappeared. It took
me quite a long time to work out
that the udev files
/etc/udev/rules.d/40-permissions.rules
/etc/udev/rules.d/20-names.rules
have changed with respect to us
The bug is triggered in a straightforward way: X starts and the usual gdm login
screen appears. After the input of username and password the gdm screen stops
responding and nothing occurs. I am still able to go to a console using
ctl-alt-f2. I have attached the syslog and Xorg.0.log files.
**
Xorg.0.log file:
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/10788474/Xorg.0.log
--
[hardy] login hangs after upgrade to xorg 1.4
https://bugs.launchpad.net/bugs/172435
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
I tried the amd64 livecd for hardy alpha 1 with interesting results. The
initial screen with various options came up with no problem and I was
able to navigate options with arrow and function keys. However when I
selected *any* particular option using enter on the keyboard the cd
light started flas
My system still does not shutdown with a fully updated system (December
9). I do not dual boot.
--
Shutdown results in a reboot
https://bugs.launchpad.net/bugs/151969
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I tried kdm as well and it failed in a similar fashion although the
screen blanked out before returning to the login screen.
I have acted as a tester for Ubuntu for all releases since Warty but am unable
to proceed at this point (livecd doesn't work, kdm and gdm fail).
Any help greatly appreciate
This bug can be closed. I reinstalled gutsy and upgraded to hardy using
upgrade-manager -d and this problem does not occur. Originally I
switched to hardy very early in the hardy development cycle and used
aptitude to update and then upgrade. Some config files must have been
borked in the process.
On hardy I can confirm that the 2.6.22-14 kernel *does not* shutdown. On
the other hand the 2.6.24-1 kernel DOES shutdown with the command
sudo shutdown -h now
So it looks indeed that this is a kernel bug since the 2.6.20 kernel
worked as well.
--
Shutdown results in a reboot
https://bugs.launc
As a service to your loyal bug testers ;-) could you let me know how to
compile the restricted modules package against the 2.6.24 kernel as I
would very much like to upgrade my kernel on gutsy to remove what is a
significant inconvenience:
At present I am the only family member able to shutdown th
Public bug reported:
After the update to xorg 1.4 in hardy I am unable to login to gnome
desktop. The gdm interface allows me to enter my username and password
but after entering the password it just hangs with no action. I can use
ctl-alt-f2 to get a terminal and then a login works fine.
** Affe
If you read the first post you will see:
[This issue is fixed by removing evms: just type "sudo apt-get remove
evms" in a console.]
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs,
Scott Remnant posted a wiki entry on the situation:
https://wiki.ubuntu.com/Evms
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
I installed
linux-image-2.6.24-2-generic_2.6.24-2.3_amd64.deb
linux-restricted-modules-2.6.24-2-generic_2.6.24.2-2.7_amd64.deb
linux-restricted-modules-common_2.6.24.2-2.7_all.deb
from hardy on a gutsy system and things appear fine. In particular the nvidia
driver works well as
does shutdown. So
Just to add that this new kernel is quite noticeably zippier on my dual
Xeon emt64 system. Nice bonus! Linus must have done something right
between 22 and 24 ;-)
--
Shutdown results in a reboot
https://bugs.launchpad.net/bugs/151969
You received this bug notification because you are a member of U
Public bug reported:
In hardy (1/7/08) xsane reports no scanner as ordinary user. As root the
scanner is located. This bug has occurred previously when it was a
permissions setting issue generated by udev
** Affects: sane-frontends (Ubuntu)
Importance: Undecided
Status: New
--
xsa
Public bug reported:
In gutsy the new 2.6.22-4-generic kernel produces the following error
message repreatedly:
May 19 10:10:16 richard-desktop kernel: [ 227.338011] device-mapper: table:
254:1: linear: dm-linear: Device lookup failed
May 19 10:10:16 richard-desktop kernel: [ 227.338017] devic
1 - 100 of 165 matches
Mail list logo
