Public bug reported:
Binary package hint: update-manager
Hi,
The upgrade to 8.10 went wroing, and the upgrade asked me to report this
bug and to include the /var/log/dist-upgrade files (included) ...
** Affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
** Attachment added: dist-upgrade-no-so-good-sj.tar.gz
http://launchpadlibrarian.net/19518069/dist-upgrade-no-so-good-sj.tar.gz
--
update-manager: Could not install the upgrades
https://bugs.launchpad.net/bugs/296037
You received this bug notification because you are a member of Ubuntu
Bugs,
... and this is the screendump asking to report this.
Could be related to aiccu blocking the upgrade, see my bug report
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/296036
** Attachment added: Screenshot-Untitled Window - not good.png
I ran dpkg --configure -a afterwards, which said Setting up aiccu,
which took 30 minutes ... !
[EMAIL PROTECTED]:~$ sudo time dpkg --configure -a
Setting up aiccu (20070115-9) ...
Warning: Couldn't find global Tunnel Brokers List, please check your DNS
settings and read the FAQ.
Warning:
Public bug reported:
The 8.04 to 8.10 upgrade-process get blocked while upgrading /
configuring aiccu. I think aiccu-conf want to talk to screen, which is
not succesfull. Or something like that.
Workaround: Ctrl - C
Remark: I've earlier reported a bug with strange (config) aiccu stuff.
See
I ran dpkg --configure -a afterwards, which said Setting up aiccu,
which took 30 minutes ... !
[EMAIL PROTECTED]:~$ sudo time dpkg --configure -a
Setting up aiccu (20070115-9) ...
Warning: Couldn't find global Tunnel Brokers List, please check your DNS
settings and read the FAQ.
Warning:
** Attachment added: screendump of the hanging Upgrade process
http://launchpadlibrarian.net/19517998/Screenshot-Distribution%20Upgrade-3%20-%20hangs%20on%20aiccu%20-%202.png
--
upgrade to 8.10 blocked by aiccu
https://bugs.launchpad.net/bugs/296036
You received this bug notification
What's 2.6.27-7.12? Is that an Ubuntu kernel, or a Linux kernel?
I'm now running 2.6.27-7-generic #1 SMP Fri Oct 17 22:24:21 UTC 2008 i686
GNU/Linux (without the .12), and there are no further updates available. Is
that the version that has fixed the bug for you? I can't tell right away
because
Bryce,
So: if I download the beta of Intrepid
http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-beta-desktop-amd64.iso,
burn it and live-boot it, then activatte fglrx, I should have the new
version that I should test?
Sander
On Wed, Oct 15, 2008 at 12:23 AM, Bryce Harrington
[EMAIL
[EMAIL PROTECTED]:~$
On Sat, Oct 18, 2008 at 10:42 AM, Sander Jonkers - GMX
[EMAIL PROTECTED]wrote:
Bryce,
So: if I download the beta of Intrepid
http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-beta-desktop-amd64.iso,
burn it and live-boot it, then activatte fglrx, I should have the new
.
Sander
On Sat, Oct 18, 2008 at 8:42 AM, Sander Jonkers - GMX [EMAIL PROTECTED]wrote:
Bryce,
So: if I download the beta of Intrepid
http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-beta-desktop-amd64.iso,
burn it and live-boot it, then activatte fglrx, I should have the new
version that I
On Thu, Oct 16, 2008 at 10:41 AM, Alexey Balmashnov
[EMAIL PROTECTED] wrote:
Matt Zimmerman wrote:
Can anyone else confirm, as stated in the bug description, that the problem
appeared between 2.6.27-1 and 2.6.27-2?
I don't remember that I ever used 2.6.27-1 kernel. Is there a simple way
No, not with me. At first I had the idea it was related to a cold versus a
warm reboot, but now my hypothesis is that the halts happen randomly, with a
50 - 70% chance.
So the workaround of blacklist modprobe is very useful; it saves a lot a
time.
--
[regression] 2.6.27-7 sometimes fails to
I tested it a few times, and even with the Wifi switch turned off, the boot
process halts sometimes. :-(
Sander
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs,
As described, I blacklisted iwl3945 in /etc/modprobe.d/blacklist and added
the modprobe to /etc/rc.local. Result: 3 succesful boots, no hanging boots.
Does this mean we have a workaround?
If loading of iwl3945 is not a problem in the end of the boot process
(/etc/rc.local), does this mean there
Sebastian,
If you do not blacklist, do you see errors on the boot screen (the dmesg)?
Because on my setup, the boot progress just stops after loading/activating
the iwl driver; I see no error messages at all.
FWIW: I believe (but I am not yet sure) that when I switch off the wifi
button before
It's my experience with 2.6.27-4-generic that 1) wifi works with WEP, but 2)
Ubuntu does not remember the WEP key: on all (two) WEP networks I connect
to, I have to type the WEP each time after logon, whereas WPA networks
passwords are remembered.
On Fri, Oct 10, 2008 at 10:16 PM, Ralph Janke
Update: the halt seems to be a bit random: a 50 - 75% change it halts. I've
seen random halts in the previous weeks, too. So it's not hard-related to
2.6.27-6-generic
I've now been able to boot yesterday's 2.6.27-6-generic. And today's
2.6.27-7-generic works too; no halts so far.
I've removed
*** This bug is a duplicate of bug 263059 ***
https://bugs.launchpad.net/bugs/263059
It indeed looks the same.
Thanks
On Sat, Oct 11, 2008 at 8:32 PM, Achim [EMAIL PROTECTED] wrote:
*** This bug is a duplicate of bug 263059 ***
https://bugs.launchpad.net/bugs/263059
** This bug has
As my machine had become unusable and did not see an update coming in,
I've installed a fresh copy of 8.10 beta, and the mouse is fine now.
--
[intrepid] mouse and keyboard stop working under gdm and gnome
https://bugs.launchpad.net/bugs/254840
You received this bug notification because you are
Public bug reported:
Ubuntu 8.10 Beta:
With today's 2.6.27-6-generic, my boot halts at:
iwl3945 tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945 :05:00.0: PCI INT A disabled
See included picture of my screen during boot.
With yesterday's 2.6.27-4-generic, everything was OK. I
** Attachment added: 2.6.27-6-generic---halts.jpg
http://launchpadlibrarian.net/18419563/2.6.27-6-generic---halts.jpg
--
8.10 beta 2.6.27-6-generic halts on iwl3945 :05:00.0: PCI INT A disabled
https://bugs.launchpad.net/bugs/281447
You received this bug notification because you are a
The dmesg of the non-halted, old 2.6.27-4-generic
** Attachment added: dmesg-2.6.27-4-generic.txt
http://launchpadlibrarian.net/18419660/dmesg-2.6.27-4-generic.txt
--
8.10 beta 2.6.27-6-generic halts on iwl3945 :05:00.0: PCI INT A disabled
https://bugs.launchpad.net/bugs/281447
You
After today's 100 MB update, my mouse is intermittently not working
(Ubuntu 8.10 intrepid ibex): I can move the mouse for about 20 - 30
seconds, and then it won't move for a few minutes, after which I can
move the mouse for about 20-30 seconds, etc.
This happens to both my USB mouse and my
Timo,
I tried booting the older kernels in the GRUB list, with the same
effect.
Do you know the other bug number?
Thanks,
Sander
On Tue, Oct 7, 2008 at 10:39 PM, Timo Aaltonen
[EMAIL PROTECTED]wrote:
sander: that sounds more like a kernel bug to me. This bug has been
fixed some time ago. If
I'm using Ubuntu (not Kubuntu) Intrepid alpha 6, so I guess I'm not using
kwd anymore?
Sander
On Sun, Sep 28, 2008 at 2:28 PM, Hew McLachlan [EMAIL PROTECTED]wrote:
Thanks for your report. Do you still experience this issue with
Intrepid?
** Changed in: compiz (Ubuntu)
Status: New =
On Sun, Sep 28, 2008 at 3:50 PM, Hew McLachlan
[EMAIL PROTECTED]wrote:
Thanks for your response. We are closing this bug report because it
lacks the information we need to investigate the problem, as described
in the previous comments.
So, after 15 (!) months of silence after my bug report,
I did two more live boots, and both were successful. So I can't reproduce
the problem. Can I cancel my bug report?
On Mon, Sep 22, 2008 at 12:50 PM, Sander Jonkers - GMX
[EMAIL PROTECTED]wrote:
Strange: a did another live boot (without any special boot / graphics
options), and that boot went
Strange: a did another live boot (without any special boot / graphics
options), and that boot went OK and showed a correct X screen.
More testing to do.
Sander
On Fri, Sep 19, 2008 at 4:05 PM, Timo Aaltonen [EMAIL PROTECTED]wrote:
can you change the VT with ctrl-alt-F1? Do that while usplash
Public bug reported:
Binary package hint: xorg
I'm trying out the live CD of Kubuntu 8.10 64-bit Alpha 5 (Intrepid
Ibex):
With a normal boot, I get the splash screen with the moving progess bar, and
after a few minutes ... nothing. Just a black screen.
With a Safe Graphics boot, I do get a X
** Attachment added: dmesg.kubuntu-8.10-alpha5.txt
http://launchpadlibrarian.net/17665347/dmesg.kubuntu-8.10-alpha5.txt
--
only X server when booting Safe Graphics Mode with 64-bit Kubuntu 8.10 Alpha 5
Intrepid Ibex
https://bugs.launchpad.net/bugs/271072
You received this bug notification
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16662190/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/16662191/DpkgTerminalLog.gz
--
package aiccu 20070115-7 failed to install/upgrade: subprocess
post-installation script
Public bug reported:
Binary package hint: aiccu
Ubuntu is telling it's a crash, and thus a halt like in
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/104590
The strange thing: afterwards, aiccu is installed.
So doesn't look like a prio 1 bug. ;-)
ProblemType: Package
Architecture: i386
Oh, that's right: I filled out some bogus account info, because all the
correct info was in an aiccu.conf I had saved somewhere else.
And: it's was Ubuntu that said something had crashed and wanted to report
it. I hadn't noticed it myself.
So, as I said, lowest (if any) prio you can imagine.
Jason,
Thanks for this workaround: I can now connect to my WEP AP.
FYI: I installed Ubuntu 8.04.1 which only has the faulty software, so you
can not choose the older kernel anymore to connect to a WEP AO. Quite a
serious Ubuntu bug IMHO.
Sander
[EMAIL PROTECTED]:~$ sudo apt-get install
Dereck,
How do you know it's a Compiz problem? I thougth it could be ati-driver or
gdm related?
Sander
On Tue, Jun 10, 2008 at 1:44 PM, Dereck Wonnacott [EMAIL PROTECTED]
wrote:
** Changed in: compiz (Ubuntu)
Sourcepackagename: None = compiz
--
fglrx X crash / restart
Still the same problem with today's newest kernel Ubuntu 8.04, kernel
2.6.24-19-generic: can't connect to WEP2. I still need to boot into
good old Ubuntu 8.04, kernel 2.6.22-14-generic from the boot options
to have my Centrino connected to my WEP AP.
BTW: With kernel 2.6.24-19, the network
The bug is still there: with today's upgrade to kernel
2.6.24-19-generic, the default boot was incorrectly pointing to memtest
on position 10, which before the kernel upgrade was the pointer to
WindowsXP (which was my default before the kernel upgrade).
[EMAIL PROTECTED]:~$ egrep -i -e default -e
Trying to find a workaround (other than editing /boot/grub/menu.lst) I
tried this:
[EMAIL PROTECTED]:~$ sudo grub-set-default 12
[sudo] password for sander:
Searching for GRUB installation directory ... found: /boot/grub
[EMAIL PROTECTED]:~$
But, alas, that does not work as default stays on 10
One more try to find a solution or workaround for this: I changed the
value of the menu.lst parameter default from a number to saved. I
hope that this option will select the Windows XP title as the default
boot option as the Windows XP title has savedefault in it's list.
The first boot shows
Public bug reported:
My X server crashed: the screen turned black, there were a few lines of ASCII
output, and then a new X session (including logon) was created. syslog below.
Hardware: Athlon X2, onboard ATI X1250 GPU, running Ubuntu 8.04 64-bit with
proprietary video driver.
[EMAIL
** Attachment added: xorg.conf
http://launchpadlibrarian.net/15167003/xorg.conf
--
fglrx X crash / restart
https://bugs.launchpad.net/bugs/238763
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here's /var/log/Xorg.0.log
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/15167027/Xorg.0.log
--
fglrx X crash / restart
https://bugs.launchpad.net/bugs/238763
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
and here's /var/log/Xorg.0.log.old
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/15167028/Xorg.0.log.old
--
fglrx X crash / restart
https://bugs.launchpad.net/bugs/238763
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After upgrading to 8.04, my Centrino Wifi suddenly can't connect to my
WEP AccessPoint anymore. I can connect to the neighbour's WPA2
AccessPoint. And if I plug in an Orinoco Gold PCMCIA card, I can make
the connection to my WEP AP. Under 7.10 everything worked OK. It's a
** Attachment added: lsmod.txt
http://launchpadlibrarian.net/13964346/lsmod.txt
--
8.04: Centrino Wifi WEP not working, WPA2 ok
https://bugs.launchpad.net/bugs/223111
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
and the lsmod with the *Orinoco*.
** Attachment added: lsmod-with-orinico-and-succesfull-WEP.txt
http://launchpadlibrarian.net/13964728/lsmod-with-orinico-and-succesfull-WEP.txt
--
8.04: Centrino Wifi WEP not working, WPA2 ok
https://bugs.launchpad.net/bugs/223111
You received this bug
FWIW, here's syslog when succesfully using the WEP connection via the
Orinoco (not the onboard Centrino). It proofs the WEP connection is
working.
** Attachment added: syslog-with-orinico-and-succesfull-WEP.txt
http://launchpadlibrarian.net/13964704/syslog-with-orinico-and-succesfull-WEP.txt
My bug report could be related to
https://bugs.launchpad.net/ubuntu/+bug/183619
--
8.04: Centrino Wifi WEP not working, WPA2 ok
https://bugs.launchpad.net/bugs/223111
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi, it seems I've reported (about) the same bug here:
https://bugs.launchpad.net/ubuntu/+bug/223111 : I can't connect to a WEP
AccessPoint with my Centrino, and/but I can connect to a WPA2
AccessPoint.
My work around so far: boot the older kernel 2.6.22-14-generic. Then
everything works again
I found a workaround: the 8.04 boot menu offers an older kernel
(2.6.22-14-generic). If I choose that kernel, my Centrino Wifi / WLAN
connects without any problem to my WEP AccessPoint.
syslog included as attachment
lsmod copied below
stuff from menu.lst:
[EMAIL PROTECTED]:~$ grep -e ^title
Public bug reported:
There's a bug in the upgrade procedure to Ubuntu 8.04 when changing the
menu.lst and the default boot option is after the inserterted boot
option:
The upgrade procedure apparently inserts two new kernels options
(2.6.24-16) in the beginning of menu.lst, but it keeps the
Louis-Dominique,
My machine is indeed quite different: it's a desktop with a CRT.
So I doubt I can put that machine to sleep.
Sander
On Sat, Apr 26, 2008 at 7:17 PM, Louis-Dominique Dubeau [EMAIL PROTECTED]
wrote:
Sander, I'm experiencing a problem which looks similar to yours but my
PS: I've upgraded to 8.04 by inserting the Alternate CD.
--
Upgrade to 8.04 does not change value of 'default' boot option if inserted
kernels are before default boot option
https://bugs.launchpad.net/bugs/222660
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
In the last two days I had two Xorg locks: my monitor turns off, it
apparantly gets no signal anymore. CTRl-ALT-BackSpace and CTRL-ALT-F1
does not result in anything: the screens stays turned off (and thus
black)
I have never had any lock-ups before the two in the last two
** Attachment added: xorg.conf
http://launchpadlibrarian.net/13556147/xorg.conf
--
Hardy Heron: screen turns off, Xorg 100%
https://bugs.launchpad.net/bugs/219285
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
de top output looks garbled. Therefor I've included top as an attachment
** Attachment added: top.txt
http://launchpadlibrarian.net/13556291/top.txt
--
Hardy Heron: screen turns off, Xorg 100%
https://bugs.launchpad.net/bugs/219285
You received this bug notification because you are a member
John,
I'm the OP and here's my question:
For which reason *exactly* are you closing this bug report?
1) Because Flash is closed source?
If so, I guess no further bug reports are needed. Well, that is, as long as
flash stays closed source, which it probably will.
2) Because others are
Oh, wait: my bug report was before your advice for one-report-per-crash
on April 11. You can ignore my previous post. Since your advice on April
11, I'm opening a bug report per crash.
Sorry for the misunderstanding.
--
npviewer.bin crashed with SIGSEGV in pthread_mutex_lock()
John,
As described on the page you gave, I tried to install firefox-dbg, but I got
an error (see below). Looking further, firefox-2-dbg does exist, but will
also install firefox-2, which I don't want. firefox-3-dbg does not exist.
Tips how to proceed?
Sander
[EMAIL PROTECTED]:~$ sudo apt-get
`GTK_IS_WIDGET (widget)' failed
(npviewer.bin:7196): Gtk-CRITICAL **: gtk_widget_destroy: assertion
`GTK_IS_WIDGET (widget)' failed
(npviewer.bin:7196): Gtk-CRITICAL **: gtk_widget_destroy: assertion
`GTK_IS_WIDGET (widget)' failed
On Sun, Apr 13, 2008 at 9:21 PM, Sander Jonkers - GMX [EMAIL PROTECTED
Ludwig,
Can you reproduce the crash? Because I tried, I don't see anything happening
when visiting, moving-away-from and/or closing nytimes.com
On Sun, Apr 13, 2008 at 10:14 PM, Ludwig [EMAIL PROTECTED] wrote:
still crashing with hardy fully updated as of now, when leaving
nytimes.com page
After today's updates + reboot, the problem seems to be gone:
[EMAIL PROTECTED]:~$ wget http://[::1]/
--11:25:43-- http://[::1]/
= `index.html'
Connecting to ::1:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 45 [text/html]
Here's the output of netstat -l -t. It looks like the 'www'-port is only
on tcp, whereas other services are connected to tcp6 (meaning ipv6 and
ipv4?).
[EMAIL PROTECTED]:~$ netstat -l -t
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
On goold old Ubuntu 7.10 everythings works OK and Apache listens to
IPv6:
[EMAIL PROTECTED]:~$ netstat -t -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp0 0 localhost:ipp *:*
Same crash here on Ubuntu Hardy Heron AMD64 running on Athlon X2 3600+.
AFAIK I have npviewer.bin updated with
http://launchpadlibrarian.net/12234800/nspluginwrapper_0.9.91.5-2ubuntu1_amd64.deb
(as described in
https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/141613),
but maybe a
On Mon, Apr 7, 2008 at 3:07 AM, Majord51 [EMAIL PROTECTED] wrote:
Juksu wrote:
Unlike Tomas Fryda, I am still getting these crashes With Firefox-3.0b5
I had stopped getting these crashes for a while, but they started up
again today after updating.
Same here: the crashed have started
Public bug reported:
Binary package hint: apache
Apache on Hardy Heron suddenly has lost it's IPv6 connectivity. This must have
happened between [05/Apr/2008:15:46:35 +0200] and now (April 5, 23:59), and
probably by a software update.
Apache is now only listening on it's IPv4 interface. I
My bug report was dated Feb 9, so I hope all updates have solved this.
--
npviewer.bin crashed with SIGSEGV in g_type_check_instance_cast()
https://bugs.launchpad.net/bugs/190439
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 204840 ***
https://bugs.launchpad.net/bugs/204840
Public bug reported:
Binary package hint: totem
Trying to watch the video clip on
http://www.novatv.nl/index.cfm?ln=nlfuseaction=videoaudio.detailsreportage_id=5899selectArchiveDay=2
I selected Real and
*** This bug is a duplicate of bug 204840 ***
https://bugs.launchpad.net/bugs/204840
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/12850824/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12850826/Dependencies.txt
** Attachment added:
Charles,
I think I haven't seen any transmission crashes since then.
Sander
--
transmission crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/188638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Never mind my last post; I get the same error message when trying to
install another package, so the install error message is probably not
related to npviewer.bin. Probably time for a fresh install of Hardy
Heron Alpha.
[EMAIL PROTECTED]:~$ sudo apt-get install clutch
*** glibc detected ***
Public bug reported:
Binary package hint: ubiquity
Disclaimer: This is my personal opinion
The Ubuntu 8.04 Hardy Heron AMD64 Alpha 6 installer asks for your
location (Where are you): you have to point it on the map. In Alpha 4
(and maybe 5) this was easy: point and click. However, with Alpha 6,
1) I have the same crashes of npviewer.bin.
2) When I try to install the nspluginwrapper_0.9.91.5-2ubuntu1_amd64.deb, that
install itself goes wrong. See below.
Platform: Ubuntu 8.04 AMD64 Alpha upgraded, running on an Athlon X2
3600+
Tips?
[EMAIL PROTECTED]:~$ locate npviewer
*** This bug is a duplicate of bug 200338 ***
https://bugs.launchpad.net/bugs/200338
Same here: after today's update (+restart) of Hardy Heron Alpha, the
sound is gone. The upper bar shows a loudspeaker with some red symbol in
it, saying
The volume control did not find any elements and/or
This bug fix is done in jockey. So: Is KDE(4) using jockey-gtk? I would
think not as jockey-gtk is defined as GNOME user interface and desktop
integration for driver management. Based on this I would say it's a
GNOME / Ubuntu package, and not used in KDE / Kubuntu.
Easy check: can you run sudo
*** This bug is a duplicate of bug 194963 ***
https://bugs.launchpad.net/bugs/194963
(@Timo:)
It's my experience that 'sudo dpkg-reconfigure xserver-xorg' does not
work for fglrx. I use 'sudo jockey-gtk' instead to (de)activate the
fglrx driver. You need to reboot after changes changes to
Aha: jockey-gtk launches the prop.driver activation. I didn't know that.
Thanks.
The relevant jockey file is probably
/usr/share/jockey/handlers/fglrx.py . That file contains the relevant
key words 'fglrx' and 'glx'. And it does *not* contain a
Screen-Default-Depth-24 line: exactly the behaviour
Good news:
I've added the line
self.xorg_conf.getSections('Screen')[0].defaultdepth = 24 to
/usr/share/jockey/handlers/fglrx.py (included), compiled the .py to
.pyc, and now 'sudo jockey-gtk' adds the needed line Defaultdepth
24. So: it works!
I think I will also remove the annoying Composite 0
and here's the compiled /usr/share/jockey/handlers/fglrx.pyc
** Attachment added: fglrx.pyc
http://launchpadlibrarian.net/12352406/fglrx.pyc
--
ATI Driver not working on Compaq V2321US (Xpress200)
https://bugs.launchpad.net/bugs/194963
You received this bug notification because you are a
I have posted a patched fglrx.py + instruction on:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.24/+bug/194963/comments/21
It solves two fglrx-xorg.conf problems for me:
1) no screen output due to the missing DefaultDepth 24
2) disabling Compiz because of the Composite
This must be the ultimate fglrx.py:
1) Defaultdepth24 is added to the Screen-Section of xorg.conf
AND
2) the unnecessary and unwanted Composite 0 option is not put into xorg.conf
in order to enable Compiz
To compile the .py to .pyc, I did this (note the working directory, and
note the
Good news: I found the solution:
Just add Defaultdepth24 to the the part Section Screen of the
xorg.conf generated by Ubuntu for the ATI / fglrx config, and everything
works!
So, in xorg.conf generated for fglrx, change
Section Screen
Identifier Default Screen
Monitor
I had a futher look at dexconf:
Ubuntu 7.10's dexconf does write a DefaultDepth line, with value
$DISPLAY_DEFAULT_DEPTH
In Ubuntu 8.04's dexconf, that line is gone. Well, there *is* a line
DefaultDepth24, but it's only written if $QEMU_KVM is true, so within
QEMU VM's. Not for fglrx.
So,
I can confirm this bug, even in 8.04 Alpha 5. (The xorg.conf of Ubuntu
7.10 is OK.)
This bug is the root cause of the bugs reported on
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.24/+bug/194963 and https://bugs.launchpad.net/ubuntu/+source
I reported Bug #195918, which has been declared a duplicate of this Bug
#194963: both about the ATI prop.driver causing no output at all.
I found a *workaround* for this ATI / fglrx / xorg.conf bug:
Short description: use the fglrx xorg.conf of Ubuntu 7.10 on Ubuntu 8.04
Long description:
or: fglrx-driver
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Sourcepackagename: None = linux-restricted-modules-2.6.24
--
ATI prop.driver on Hardy 64bit result in no screen output
https://bugs.launchpad.net/bugs/195918
You received this bug notification because you are a member of
Here's Xorg.0.log---prop.driver-no-screen.fglrx / Xorg.0.log
** Attachment added: Xorg.0.log---prop.driver-no-screen.fglrx
http://launchpadlibrarian.net/12262121/Xorg.0.log---prop.driver-no-screen.fglrx
--
ATI prop.driver on Hardy 64bit result in no screen output
To get fresh and shiny log files, I installed a fresh Ubuntu 8.04
(64-bit), installed ssh-server, activated the prop.driver (fglrx),
rebooted, and then remotely logged on to get dmesg, Xorg.0.log.old,
Xorg.0.log and xorg.conf. I will at those files with the filenames
below:
[EMAIL PROTECTED]:~$
Here's dmesg / dmesg.fglrx.no-screen
[EMAIL PROTECTED]:~$ cat dmesg.fglrx.no-screen | grep fg
[ 33.230601] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies,
Starnberg, GERMANY' taints kernel.
[ 33.329257] [fglrx] Maximum main memory to use for locked dma buffers: 3737
MBytes.
And here's xorg.conf---prop.driver-no-screen.fglrx / xorg.conf
** Attachment added: xorg.conf---prop.driver-no-screen.fglrx
http://launchpadlibrarian.net/12262158/xorg.conf---prop.driver-no-screen.fglrx
--
ATI prop.driver on Hardy 64bit result in no screen output
Public bug reported:
Hardware: Asus M2A-VM HDMI, with onboard ATI GPU: Integrated ATI Radeon
X1250-based graphics
The installation of Ubuntu 8.04 Hardy Heron Alpha 5 64-bit goes perfect.
After reboot + first login, the proprietary driver is offered. After
installation of that prop.driver
** Attachment added: xorg.conf
http://launchpadlibrarian.net/12242057/xorg.conf
--
ATI prop.driver on Hardy 64bit result in no screen output
https://bugs.launchpad.net/bugs/195918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
To check it's not 64-bit related, I installed 8.04 hardy alpha 5 i386,
with the same results: activating the ATI prop.driver (fglrx) followed
by a reboot, results in no screen output at all; the monitor on/off
light goes into orange blinking mode instead of steady green light.
So: it's not 64-bit
Public bug reported:
Binary package hint: totem
No idea; I even didn't knw totem/gstreamer was running at all.
ProblemType: Crash
Architecture: amd64
Date: Sun Feb 17 08:51:29 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/totem-gstreamer-video-thumbnailer
NonfreeKernelModules: cdrom
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12045328/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/12045329/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/12045330/ProcMaps.txt
** Attachment
Pedro,
I will follow the valgrind instructions and see what happens.
However: the bug is 12 days old. Maybe transmission updates have
already solved it. I will start using transmission again to see what
happens.
Thanks,
Sander
--
transmission crashed with SIGSEGV in g_slice_alloc()
Same crash here on Ubuntu 8.04 AMD64 Alpha 4 with all updates installed.
[EMAIL PROTECTED]:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu hardy (development branch)
[EMAIL PROTECTED]:~$
--
npviewer.bin crashed with SIGSEGV in
Out of curiosity:
Was the bug already known, or was it new?
And what was the root cause of the curious behaviour?
Sander
On Feb 4, 2008 7:27 PM, Michael Vogt [EMAIL PROTECTED] wrote:
Thanks for your bugreport.
This is fixed in my local tree and will be part of the next upload.
**
301 - 400 of 428 matches
Mail list logo
