[Bug 292421]

2013-02-03 Thread klondike
I think this was fixed at some point of time but I forgot to close this bug. Even if it wasn't fixed I don't have access to the hardware anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/292421 Ti

[Bug 292421] Re: [RV530 x1650] Black screen after updating

2010-08-15 Thread klondike
You can try this xorg.conf. Simply backup the one at /etc/X11/xorg.conf and copy it there. If it works then post a new bug asking for a hal rule being added to solve this on your card. ** Attachment added: "example conf with ATOMTVOut" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-vi

[Bug 506284] Re: libcanberra-gtk-module.so: undefined symbol: gtk_widget_get_window

2010-03-26 Thread klondike
** Changed in: libcanberra (Ubuntu) Status: New => Invalid -- libcanberra-gtk-module.so: undefined symbol: gtk_widget_get_window https://bugs.launchpad.net/bugs/506284 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bug

[Bug 506284] Re: libcanberra-gtk-module.so: undefined symbol: gtk_widget_get_window

2010-03-26 Thread klondike
This bug is easy to fix. The problem is that you are mixing libraries from the shipped version and the non shipped version. Simply install the mm version of your gtk libraries :D and that should fix it. (Note the name can change between versions) install: libglibmm-2.4-1c2a libgnomecanvasmm-2.6-1

[Bug 292421] Re: [RV530 x1650] Black screen after updating

2009-03-13 Thread klondike
I'm sorry bryce I was really busy this weeks with various assignments, I'm subscribing right now and sending the data :) -- [RV530 x1650] Black screen after updating https://bugs.launchpad.net/bugs/292421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscri

[Bug 292421] Re: [RV530 x1650] Black screen after updating

2009-02-28 Thread klondike
Still happens with Jaunty ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => Confirmed -- [RV530 x1650] Black screen after updating https://bugs.launchpad.net/bugs/292421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 292421] Re: [RV530 x1650] Black screen after updating

2009-02-28 Thread klondike
Here is the info you requested and a bit more just in case: *Xorg.0.log the X log file *good2.txt the output of radeontool when using vesa (works) *bad2.txt the output of radeontool when using the radeon driver (doesn't work). Feel free to link the bug upstream so I subscribe. ** Attachment added

[Bug 292421] Re: [RV530 x1650] Black screen after updating

2009-02-25 Thread klondike
Ok I'll try to do so this weekend. -- [RV530 x1650] Black screen after updating https://bugs.launchpad.net/bugs/292421 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 https://list

[Bug 292421] Re: [RV530 x1650] Black screen after updating

2009-02-20 Thread klondike
After following the steps on the wiki and ensuring fglrx was fully uninstalled the issue remains. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Invalid => New -- [RV530 x1650] Black screen after updating https://bugs.launchpad.net/bugs/292421 You received this bug notification be

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2009-02-17 Thread klondike
Updated info ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => New -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/292421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2009-02-17 Thread klondike
Well bryce, here you have a tar.gz with the outputs. Those are the contents: regdump_vesa.txt (using vesa which is what I'm using now and seems to work fine) regdump_bad.txt (using radeon after vesa, fails) regdump_good.txt (using fglrx, killing the Xserver then using radeon, seems to work fine)

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-25 Thread klondike
Hi, I suppose you're using the fglrx drivers. If so, you should try using the non proprietary, radeon drivers, and opening another bug. To get a terminal you can try pressing ctrl+alt+f1 -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/292421 You received

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-09 Thread klondike
And the diff betwen the logs just in case. To the left the log when it works and to the right the log when it doesn't ** Attachment added: "Logs diff" http://launchpadlibrarian.net/19512089/Xorg.log.diff -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-09 Thread klondike
Of course, here it is. ** Attachment added: "log Without DRI and working" http://launchpadlibrarian.net/19512037/Xorg.0.log ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => Confirmed -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.ne

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-08 Thread klondike
I have noted the following differences when it not works: Output 68 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0xdfffd000 0xdfffd000 (II) RADEON(0): M

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-08 Thread klondike
This is the log ** Attachment added: "Xorg.log with no dri" http://launchpadlibrarian.net/19491991/Xorg.log.nodri -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/292421 You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-05 Thread klondike
Tried but to no avail. Right now I have modified my kdm so it starts the X with fglrx waits a bit for it to crash then starts with radeon, But it shouldn't be this way :( -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/292421 You received this bug notific

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-03 Thread klondike
In case it helps, this is my Xorg.conf although when using the default conf the behavior is still the same. ** Attachment added: "xorg.conf" http://launchpadlibrarian.net/19305978/xorg.conf -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/292421 You r

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-03 Thread klondike
This is the log after using fglrx then restarting the xserver (as t also fails) and then using the radeon module. I tried not putting the BUSID option to see the problem wasn't there. Right now I think it can be an incorrect card intialization problem (as when using fglrx I see what seems a core d

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-02 Thread klondike
Misteriously after probing fglrx an then falling back to radeon, the thing seemed to work. Maybe it has something to do with the PCI device identification done on this Xorg config or to a bad card initialization. I'll keep trying. -- Black screen with Ati Radeon X1650 Pro after updating https://b

[Bug 188713] Re: STR and Standby don't work properly

2008-11-02 Thread klondike
After upgrading to 2.6.27 the bug not only remains but gets worse. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- STR and Standby don't work properly https://bugs.launchpad.net/bugs/188713 You received this bug notification because you are a member of Ubuntu Bugs, which is sub

[Bug 188713] Re: STR and Standby don't work properly

2008-11-02 Thread klondike
On 2.6.27 Suspend to disk also stopped working. And both block the Xserver. ** Attachment added: "Messages.log including the two suspend tries" http://launchpadlibrarian.net/19226812/messages -- STR and Standby don't work properly https://bugs.launchpad.net/bugs/188713 You received this bug n

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-01 Thread klondike
** Attachment added: "Xorg log" http://launchpadlibrarian.net/19206912/Xorg.1.log -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/292421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubu

[Bug 292421] Re: Black screen with Ati Radeon X1650 Pro after updating

2008-11-01 Thread klondike
** Attachment added: "lspci" http://launchpadlibrarian.net/19206887/lspci -- Black screen with Ati Radeon X1650 Pro after updating https://bugs.launchpad.net/bugs/292421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 292421] [NEW] Black screen with Ati Radeon X1650 Pro after updating

2008-11-01 Thread klondike
Public bug reported: After updating to 8.10 the Xserver wasn't unable to display anything (putting my monitor into sleep mode). The Xorg logs don't show anything strange. ** Affects: xserver-xorg-driver-ati (Ubuntu) Importance: Undecided Status: New -- Black screen with Ati Radeo

[Bug 271563] Re: Verlihub plugins fail to compile

2008-09-17 Thread klondike
** Attachment added: "The corrected verlihub_config file" http://launchpadlibrarian.net/17713645/verlihub_config -- Verlihub plugins fail to compile https://bugs.launchpad.net/bugs/271563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 271563] [NEW] Verlihub plugins fail to compile

2008-09-17 Thread klondike
Public bug reported: Binary package hint: verlihub Compilation of verlihub plugins fails due to a bad library parameter. When compiling, plugins usually call "/usr/bin/verlihub_config" to get the proper CFLAGS, but verlihub_config returns a bad library dir flag for verlihub libs as they are plac

[Bug 204481] Re: darkice sound is cut after 1 minute

2008-03-26 Thread klondike
After a few checks the error seemed to be related with snd-aloop. So I'll change this to invalid and close the bug :) ** Changed in: darkice (Ubuntu) Status: New => Invalid -- darkice sound is cut after 1 minute https://bugs.launchpad.net/bugs/204481 You received this bug notification bec

[Bug 204481] [NEW] darkice sound is cut after 1 minute

2008-03-20 Thread klondike
Public bug reported: Binary package hint: darkice Release : Ubuntu Hardy Heron (8.04) devel Packet version: 0.18.1-1 0 (also retiried to compile it only with alsa and ogg and the version management system one to no avail). Expected behaviour: The sound being captured is played smoothly thorugh i

[Bug 188713] Re: STR and Standby don't work properly

2008-02-03 Thread klondike
tarball of /proc/acpi (It gave me some errors when trying to do it). ** Attachment added: "procacpi.tar.gz" http://launchpadlibrarian.net/11744716/procacpi.tar.gz -- STR and Standby don't work properly https://bugs.launchpad.net/bugs/188713 You received this bug notification because you are a

[Bug 188713] Re: STR and Standby don't work properly

2008-02-03 Thread klondike
Result of uname -a: Linux KDK 2.6.22.9-core2duo #1 SMP Thu Jan 31 19:23:05 CET 2008 i686 GNU/Linux Attached output of sudo dmidecode: ** Attachment added: "dmidec" http://launchpadlibrarian.net/11744710/dmidec -- STR and Standby don't work properly https://bugs.launchpad.net/bugs/188713 You

[Bug 188713] Re: STR and Standby don't work properly

2008-02-03 Thread klondike
lspci -vvnn output ** Attachment added: "lspcivvnn" http://launchpadlibrarian.net/11744680/lspcivvnn -- STR and Standby don't work properly https://bugs.launchpad.net/bugs/188713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu.

[Bug 188713] Re: STR and Standby don't work properly

2008-02-03 Thread klondike
messages output when trying to STR ** Attachment added: "dmesg2" http://launchpadlibrarian.net/11744669/dmesg2 -- STR and Standby don't work properly https://bugs.launchpad.net/bugs/188713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 188713] Re: STR and Standby don't work properly

2008-02-03 Thread klondike
dmesg output when trying to standby ** Attachment added: "dmesg1" http://launchpadlibrarian.net/11744656/dmesg1 -- STR and Standby don't work properly https://bugs.launchpad.net/bugs/188713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact fo

[Bug 188713] [NEW] STR and Standby don't work properly

2008-02-03 Thread klondike
Public bug reported: I have an asus P5W DH Deluxe which seems to be the cause of the failure: when suspending, the drive sdb doesn't seems to accept the command and the suspension is halted. This drive is created by the motherboard and it's usage is still unknown to me anyway, It made the boot get

[Bug 185183] Re: Konqueror hangs when using webdavs the charset is manually changed

2008-01-22 Thread klondike
Seems to be related with bug #113560 -- Konqueror hangs when using webdavs the charset is manually changed https://bugs.launchpad.net/bugs/185183 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-b

[Bug 185183] Konqueror hangs when using webdavs the charset is manually changed

2008-01-22 Thread klondike
Public bug reported: Steps to reproduce: 1- Connect to a secure webdav server. 2- Change the charset used. 3- Konqueror hangs. This happens always with the latest version (3.5.8) available from the 7.10 repos. If you need more data please request for it. ** Affects: kdebase (Ubuntu) Import

[Bug 141038] Re: Modprobe hangs the system until killed due to the amount of memory used by it

2007-10-18 Thread klondike
It seems it finally was solved, I close it. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New => Fix Committed -- Modprobe hangs the system until killed due to the amount of memory used by it https://bugs.launchpad.net/bugs/141038 You received this bug notification because you are a

[Bug 152184] Re: MSI P965 motherboard

2007-10-18 Thread klondike
On a console, you can get one by pressing alt+F2 -- MSI P965 motherboard https://bugs.launchpad.net/bugs/152184 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

[Bug 126113] Re: Hard drive connected on JMicron PATA does not work

2007-10-15 Thread klondike
Try this on a console: $ sudo rmmod pata_jmicron $ sudo modprobe pata_jmicron As for me it solves the problem an the disks are detected and functional, I haven't though experimented much trouble with my cd drive after upgrading to feisty, but I can't certify this :( -- Hard drive connected on JM

[Bug 152184] Re: MSI P965 motherboard

2007-10-15 Thread klondike
Try this: $ sudo rmmod pata_jmicron $ sudo modprobe pata_jmicron As for me it solves the problem an the disks are detected and functional. I think it may have something to see with the initrd and a conflict between the generic_ata and the jmicron_ata modules, but 'm not too sure. -- MSI P965 mot

[Bug 57502] Re: JMicron PATA/SATA Controller does not work

2007-10-15 Thread klondike
Using an alternate with alt+F2 I can confirm it works on my box but having installed before the ubuntu version. -- JMicron PATA/SATA Controller does not work https://bugs.launchpad.net/bugs/57502 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact

[Bug 57502] Re: JMicron PATA/SATA Controller does not work

2007-10-10 Thread klondike
Try this: $ sudo rmmod pata_jmicron $ sudo modprobe pata_jmicron As for me it solves the problem an the disks are detected and functional. may it have something to see with the initrd? -- JMicron PATA/SATA Controller does not work https://bugs.launchpad.net/bugs/57502 You received this bug notif

[Bug 141038] Re: Modprobe hangs the system until killed due to the amount of memory used by it

2007-10-05 Thread klondike
Reopened since it has nothing to see with the version ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Incomplete => New -- Modprobe hangs the system until killed due to the amount of memory used by it https://bugs.launchpad.net/bugs/141038 You received this bug notification because yo

[Bug 141038] Re: Modprobe hangs the system until killed due to the amount of memory used by it

2007-10-05 Thread klondike
Yes, it happens again with gutsy. Also after upgrade I have lost support for my intel hda card but I may open another bug for that issue. Any idea where to look for info. (Attached the new dmesg) ** Attachment added: "dmesg" http://launchpadlibrarian.net/9833774/dmesg ** Also affects: linux

[Bug 141038] Re: Modprobe hangs the system until killed due to the amount of memory used by it

2007-09-19 Thread klondike
** Attachment added: "lspci" http://launchpadlibrarian.net/9381927/lspci -- Modprobe hangs the system until killed due to the amount of memory used by it https://bugs.launchpad.net/bugs/141038 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact

[Bug 141038] Modprobe hangs the system until killed due to the amount of memory used by it

2007-09-19 Thread klondike
Public bug reported: When I run "modprobe cx88-dvb" the system hangs until the proccess is killed. It seems to be due to some sort of recursive function since it's killed due to a lack of memory. Here is the dmesg output ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided

[Bug 141038] Re: Modprobe hangs the system until killed due to the amount of memory used by it

2007-09-19 Thread klondike
** Attachment added: "dmesg" http://launchpadlibrarian.net/9381925/dmesg -- Modprobe hangs the system until killed due to the amount of memory used by it https://bugs.launchpad.net/bugs/141038 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact