** Attachment added: Output from lspci -vvnn
http://launchpadlibrarian.net/19054047/lspci.txt
--
Graphical Glitches with xserver-xorg-video-radeon
https://bugs.launchpad.net/bugs/280916
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg log
http://launchpadlibrarian.net/19054056/Xorg.0.log
--
Graphical Glitches with xserver-xorg-video-radeon
https://bugs.launchpad.net/bugs/280916
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: xorg.conf
http://launchpadlibrarian.net/19054076/xorg.conf
--
Graphical Glitches with xserver-xorg-video-radeon
https://bugs.launchpad.net/bugs/280916
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: xserver-xorg-video-radeon
On my Dual screen setup i have graphical glitches with my mousepointer on the
left screen.
Please view the attached picture for an example of mousepointer corruption,
sofar it seems to only happen on the left side of the left
** Attachment added: screenpic.jpg
http://launchpadlibrarian.net/18375372/screenpic.jpg
--
Graphical Glitches with xserver-xorg-video-radeon
https://bugs.launchpad.net/bugs/280916
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Issue was resolved with final release
--
Herd 5 booting on a Compaq nx7400 fails
https://bugs.launchpad.net/bugs/92665
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
Kit has been scrapped, no longer able to test
--
Hardware issue's resolving bt878 recent kernels
https://bugs.launchpad.net/bugs/188478
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
The current version of RadeonHD (1.2.1 build2) supports the Radeon
X1950, however, on my system this does not produce the desired result.
When setting my xorg.conf file to use the radeonhd driver, my system
no longer recognises the resolution of both my displays, there is no
** Attachment added: xorg.conf
http://launchpadlibrarian.net/18346509/xorg.conf
--
RadeonHD X1950 Performance Display issue's
https://bugs.launchpad.net/bugs/280413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/18346523/Xorg.0.log.old
--
RadeonHD X1950 Performance Display issue's
https://bugs.launchpad.net/bugs/280413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi,
Quoting vjohn [EMAIL PROTECTED]:
Hi people, sorry by angry message, but I'm realy needing my onboard
network working in gnu/linux... Yesterday I have installed m$
windows in my machine to test the onboard network card (for
something it's work! hehe)
You definatly should *NOT*
I replaced the machine with said controller for some new kit, can't test
if this issue still exist.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Public bug reported:
Binary package hint: linux-image
The recent versions of linux have an incompability with PinnacleSys PCTV
Studio/Rave PCI tv-tuner cards.
There are currently two issue's, inability to select/scan tv-channels, for
which there is a work-arround (mentioned later in this
Whoops, wrong lspci output:
06:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture
(rev 11)
Subsystem: Pinnacle Systems Inc. PCTV pro (TV + FM stereo receiver)
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at 50001000 (32-bit,
@Gerard
I'm afraid you're having a different issue then i was, and it doesn't
seem related to the missing tags table as the other bug mentioned, you
could try renaming the database file to see if f-spot can make a new
file, if that works, you might have to dump your old table to text
import the
Latest updates seem to have resolved the issue for me.
--
Feisty Beta Installs ok, doesn't boot
https://bugs.launchpad.net/bugs/95280
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
Fixed it here by installing sqlite, on which f-spot seems to rely on my
end. Should this be a dependency?
--
F-spot stuck in infinite loop
https://bugs.launchpad.net/bugs/95318
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Your problems are with the old f-spot database, you seem to be lacking
the table tags.
Do this:
Go to the terminal, and type in the following command:
sqlite ~/.gnome2/f-spot/photos.db
You'll get an sql prompt, at this prompt type:
.tables
You should get a list of all tables present in the
Nope, it still doesn't work, the module for the sata controller doesn't
get loaded, i have to run /scripts/init-premount/udev by hand, only then
do i get access to the disk the lvm volumes.
After mounting the root fs to /root and killing udev can i resume
booting.
--
Feisty Beta Installs ok,
Some more tests, i undid all my modifications to the initramfs scripts
in /etc and /usr and let the system boot.
I get tossed into the initramfs box, i check for the presence of my disks in
/dev
I load the kernel modules if they are not present
i execute ./scripts/local-top/mdadm
After that
My bugreport might be related to this one, Bug #95280.
(https://launchpad.net/ubuntu/+bug/95280)
--
boot-time race condition initializing md
https://launchpad.net/bugs/75681
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Managed to get rid of the infinite loop complaining about a bad
superblock on /dev/hda, now it just loops happilly saying the md device
already has it's disks.
I suppose this means it's atleast assembling the raid.
I found an upstream bugreport about a simular issue that's apperently already
I've been doing more tests on another (less critical) machine, i believe
it's related to bug #95318.
I've encountered the following problems on said system:
- The modules for the ide sata controllers were not loaded during boot
- mdadm didn't detect the raid device present on hda and hdb
- lvm
Wrong bug, i meant bug #76708
--
Feisty Beta Installs ok, doesn't boot
https://launchpad.net/bugs/95280
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The machine is running Feisty Fawn beta, and is up to date.
The f-spot database comes from a previous edgy install (/ and /home are 2
seperate partitions).
I'm not sure how i can provide you with more info, since the application
doesn't crash (so no coredump), it just can't connect to d-bus
--
Public bug reported:
I tested the latest beta release for Feisty Fawn, i installed using the
alternative CD, installation on a SATA disk with LVM2 layout works
properly, installation went without a glitch.
Rebooting after install results in a failed boot, and the user is
dropped into the
Public bug reported:
Binary package hint: f-spot
Unable to launch f-spot, this is what i get from the console:
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to
Managed to get it to boot in the following order:
- Install a minimal system
- When the installer asks for the proxy, press F2
- Mount your system proc, then chroot into it
- edit /etc/initramfs-tools/modules
- add the following lines:
libata
pata_jmicron
ata_piix
ahci
ata_generic
- execute
Well, seems it still doesn't boot like it should, 1 out of 10 boots
it'll start up, the other times it won't.
Sometimes i see my HD, sometimes i don't.
When i do see the HD and reboot one more time it seems to boot up properly,
testing the same machine with edgy works perfectly, so i doubt it's
Public bug reported:
I have a system that was setup with Edgy to use md raid1 (mirroring) and
on top of the raid device, i use lvm2, with two partitions, the /
filesystem and /home.
When i attempt to install herd 5 on that system, it fails to detect the
already configured raid device (/dev/md0),
Public bug reported:
Binary package hint: initramfs-tools
Installing Feisty Herd 5 on an HP/Compaq nx7400 laptop seems to work,
partitioning, installing packages and bootloader all work, but after the
first stage of installation, and the system reboots, the kernel will not
find the root device.
I'll have to check, i think it gets loaded as soon as you select
Configure RAID devices tho, when partitioning manually.
The /dev/md/0 error only appears *after* i goto the Configure raid
section, prior to doing that i can still go back forth between
detecting disks and partitioning, as soon as
32 matches
Mail list logo
