This issue did not affect me with 9.10 (karmic), but after wipe/new
install of 10.04 beta 2, it affects me.
Under karmic, I was using proprietary ATI drivers for Radeon Mobility
X300 (Dell Latitude D610), but these drivers do not appear to be
available with 10.04 beta 2.
CTRL-ALT-BS does not rest
ed in: fast-user-switch-applet (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs
>Status: New => Incomplete
>
> --
> Switching users resets resolution to unsupported mode
> https://bugs.launchpad.net/bugs/72229
> You received this bug notification be
Haven't tried it yet.
I was going to wait for Feisty to be released.
On 3/9/07, Erik Andrén <[EMAIL PROTECTED]> wrote:
>
> What are the results using a feisty fawn herd 5 live cd?
>
> --
> Setup video mode not supported by Dell LCD display
> https://launchpad.ne
Beryl crashed when I started it from Gnome. I would have reported it to
http://bugs.beryl-project but the Gnome bug reporter opened the
Launchpad page via Firefox and requested I report it here.
This worked in previous builds.
Please find attached crash file.
** Attachment added: "Crash file for
Public bug reported:
Binary package hint: fast-user-switch-applet
When running Ubuntu Edgy (released), switching users causes Dell 2005FPW
display to change to unsupported resolution. Result is black screen with
"Cannot display this mode" message.
No keyboard sequences have any effect (Alt +/-,
Good find - I'd never considered that the arrays might not be completed when
the reboot comes up.
However, I don't "buy" that this is the solution. Here's why:
1) If the array build wasn't complete, why does the file system not report some
sort of error when the Ubuntu installation copies all th
With the same system I was using when I posted above, I tried to run the
Edgy install DVD for both K/Ubuntu. With Edgy, it reaches the point
where X should start, then bombs back out to a curses screen stating
that there was a problem with X and would I like a detailed error
message.
If I then edi
I'm mystified. . .
I installed Ubuntu 6.10 amd64 from the alternate DVD into a VM. I setup
multiple disks with the RAID configuration I outlined earlier and -- it
WORKED.
The installation in to the VM had no trouble.
The identical installation with my physical hardware won't boot as outlined
abo
Another note:
When I install Dapper into the RAID1 configuration from scratch, it
works (as noted above). If I then upgrade from Dapper to Edgy via the
Upgrade Manager, the system continues to work -- that is, grub boots the
system fine with /boot on RAID1 device and menu.lst references /dev/md1
I don't know if this is still relevant, but I encountered the same issue
with the Dapper installer (with Ubuntu as well as Kubuntu, of course).
I wasn't looking at the LVM entry, but in order to get the RAID
configuration entry to appear during the partitioning stage of
installation, you have to c
I'm not so sure this is a grub issue (but it may be). Grub is
referencing a /dev/md1 device (which would normally be correct), but
when I boot the system with the rescue disk, there are no /dev/mdx
devices at all.
There *should* be md1 for the RAID1 /boot partition, and two others for
the RAID0 /
Public bug reported:
After successfully installing Edgy AMD64 (from scratch) and creating the
following:
/boot - RAID1
/ - RAID0
/home - RAID0
Grub errors out with "Error 15: File not found"
This is with software RAID using two SATA II disks.
Booting with recovery disk shows no /dev/
BAH! Sorry for the chaff -- it stalled again after all at 35% after
4.1GB.
Last /var/log/message entries were:
07/11/2006 01:28:26 PM beast kernel [17182486.028000] smb_get_length:
Invalid NBT packet, code=6e
07/11/2006 01:28:56 PM beast kernel [17182516.024000]
smb_add_request: request
More information -- again please also reference
http://www.ubuntuforums.org/showthread.php?t=212964.
Because I have an AMD X2 64 3800+ (dual core) I've upgraded the kernel
and related packages to 2.6.15-26-k7 #1 SMP PREEMPT.
I tried the copy again (without much hope) and it appears to actually be
Public bug reported:
Please see http://www.ubuntuforums.org/showthread.php?t=212964.
When smb share is mounted via command line:
$ sudo mount -t smbfs -o username=/ /// /mnt/
remote share is accessable for a short period of time (minutes) then
"dissappears". That is, copies from remote share to
15 matches
Mail list logo
