*** This bug is a duplicate of bug 708711 ***
https://bugs.launchpad.net/bugs/708711
This particular crash has already been reported and is a duplicate of bug
#708711, so is being marked as such. Please look at the other bug report to
see if there is any missing information that you can
Sadly, I no longer am able to test this. The harddisk of the notebook
died a few weeks ago, and given its age, it's very unlikely I will spend
money on a new disk for this machine.
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
This is no longer an issue. Upstream bug is still open because with KMS
the driver performs load-detect on already enabled outputs, causing
occasional screen flicker
--
[r300 KMS] modesetting not accepted by monitor
https://bugs.launchpad.net/bugs/410401
You received this bug notification
@herrmidnquer: actually, several Soundgraph remotes (including the -PAD
models) register themselves as two separate modules (see minor:0 and
minor:1 in my log above). One is the normal remote function, and the
other is the pad - a mouse-like input device with movement keys and
buttons, controlled
Public bug reported:
Binary package hint: kdemultimedia
I must say I'm more than a bit disheartened to see bugs like #121177
marked invalid, as I stumbled across this bug today for the first time,
with a fully up-to-date 10.04 install. I don't care whether the reason
is Amarok doesn't play audio
PJO wrote:
Solution here:
http://wombatdiet.net/2010/05/09/ubuntu-10-04-on-asus-1000-eee-pc/
You must have missed the part where I said my issue is not fixed with
v2.3.0 from the Ralink website. It's only the third line of my report.
** Tags removed: needs-kernel-logs
--
rt2860 cardbus
apport information
** Tags added: apport-collected
** Description changed:
This might very well be a duplicate of #496093, but I'm reporting a new bug
because:
- I'm using the pcmcia module, which no other reporter seems to have
- my issue is not fixed with v2.3.0 from the Ralink website
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/46553017/BootDmesg.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/46553021/Card0.Amixer.values.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a
apport information
** Attachment added: Card0.Amixer.info.txt
http://launchpadlibrarian.net/46553019/Card0.Amixer.info.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
http://launchpadlibrarian.net/46553124/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
http://launchpadlibrarian.net/46553032/Card0.Codecs.codec97.0.ac97.0.0.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/46553137/Lspci.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/46553138/PciMultimedia.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/46553135/CurrentDmesg.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of
apport information
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/46553136/IwConfig.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/46553142/ProcCpuinfo.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/46553144/ProcInterrupts.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/46553145/ProcModules.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/46553147/UdevDb.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/46553156/UdevLog.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/46553270/WifiSyslog.txt
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
You received this bug notification because you are a member of Ubuntu
with 2.6.34-rc4, the symptoms are exactly the same: on boot, the
association appears to succeed, and on the router I can see that an IP
address is being allocated to 00:0c:f6:37:be:29, which is the macaddress
of wlan0. But this IP address, although distributed by the server, is
never allocated on
** Tags removed: needs-upstream-testing
--
rt2860 cardbus can't connect: Association request to the driver failed
https://bugs.launchpad.net/bugs/564629
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:
This might very well be a duplicate of #496093, but I'm reporting a new bug
because:
- I'm using the pcmcia module, which no other reporter seems to have
- my issue is not fixed with v2.3.0 from the Ralink website
- I'm already using a WPA2-only access point (or I don't know
Just a quick update: the original problem (wrong signal clocks) has been
fixed upstream and the bug no longer appears with a 2.6.33 kernel
(haven't tried a .32 kernel recently). There is only a minor issue
remaining with load detection, which causes the monitors to blink when
probing outputs
Public bug reported:
Binary package hint: sysvinit
here is an excerpt from $df -h on my current karmic system:
udev 3.0G 328K 3.0G 1% /dev
none 3.0G 0 3.0G 0% /dev/shm
tmpfs 2.4G 366M 2.0G 16% /tmp
none 3.0G 212K
Martin Pitt wrote:
[...]
Right now, you can't have both xubuntu-default-settings and mythbuntu-
default-settings installed at the same time.
I'm afraid I'm just pointing out the elephant in the room here, but my
point wasn't about the *-default-settings packages: as it stands now for
karmic,
Please take care that both of you add
Provides: ubuntu-derivative-default-settings
Conflicts: ubuntu-derivative-default-settings
to avoid settings fighting each other and file-conflicting over
default.session.
I'm sorry, I don't think that is an acceptable workaround. Take a look
at what
Oh, I saw too late that this bug hasn't been updated in over a month. If
you want me to open a new bugreport instead, please let me know.
Regards,
Arno
--
Unable to change the default session for GDM
https://bugs.launchpad.net/bugs/403291
You received this bug notification because you are a
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
I think you meant xserver-xorg-video-radeon, right?
--
[r300 KMS] modesetting not accepted by monitor
https://bugs.launchpad.net/bugs/410401
You received this bug notification because you are a
Public bug reported:
current ubuntu-standard (1.154) recommends reiserfsprogs, but does not
do the same for xfsprogs. Given that Xfs and Reiserfs are equal in terms
of goal and function, I don't see a reason why they should be treated
differently.
Could xfsprogs be added to the Recommends-list
If the original request concerns the same iMon LCD display that I have,
there is no way to power down the display when the PC goes to sleep or
even poweroff. This is because my display is tied to an IR receiver that
is able to power on the machine via a button on the remote, thus the
device is
Ouch, launchpad ate my whitespace. There should be sixteen spaces
between the quotes.
--
soundgraph imon LCD not recognized
https://bugs.launchpad.net/bugs/186193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Several Soundgraph iMon models are only supported since lirc 0.8.4,
which is included in 9.04 (Jaunty). You could try using intrepid-
backports, but I'm not sure if the kernel modules are backported as
well. I'm currently using a pre-release of lirc 0.8.5, but my device
gets recognized correctly:
I ran into this same (well, appears to be same) bug with a Debian kernel
(2.6.26). See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515009
Like this bug, I have been unable to reproduce it or even stumble upon
it a second time.
** Bug watch added: Debian Bug tracker #515009
Public bug reported:
Binary package hint: initramfs-tools
After dist-upgrading to Jaunty (from Intrepid), I was unpleasantly
surprised by the kernel boot giving me a Busybox prompt in initramfs: it
failed to mount the root filesystem. Performing a 'cat
/proc/filesystems' revealed no presence of
probably just a fluke. I have another two or three systems that will
need dist-upgrading soon, will reopen if it happens again
** Changed in: initramfs-tools (Ubuntu)
Status: New = Invalid
--
initramfs: missing reiserfs module
https://bugs.launchpad.net/bugs/355341
You received this bug
As it turns out, the initramfs of both kernels (2.6.27 and 2.6.28) did not
contain any modules. I'm not sure what happened or what went wrong, but somehow
the dist-upgrade process seems to have missed the entire rebuild after modules
installation event. After booting into my system, a simple
$
Already fixed upstream
--
Multiple return values from dbus_method return multiple times the first value
https://bugs.launchpad.net/bugs/243958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Testing 2.0 would mean to try Jaunty, and I have no machines on Jaunty yet
So I moved one of my machines over to jaunty (well, only kubuntu-desktop
really) and guess what: there is no crossfade option in Amarok2! So it appears
to be fixed, isn't it?
Or am I doing something terribly wrong here?
You mean you can't reproduce it yourself? Besides, this bug is present
Hardy as well, and since that is an LTS release it should have long been
confirmed, even if it is fixed in 2.0.
Testing 2.0 would mean to try Jaunty, and I have no machines on Jaunty
yet. Will report back when I have. But
Amarok upstream here.
Welcome! Glad to know I was wrong about that.
It was reported upstream as you can see in the bugwatch at the top of this
page.
The link at the top refers to a bug report that is older than this one. To be
exact, the upstream report was closed a month before this bug
@cevatcethun : are you sure you are running 8.10 (intrepid)? In comment
257, you said that you're running 8.04, which shouldn't be affected by
this bug. So maybe you're seeing the effects of another bug?
The alsa-utils fix works for me as well. Thanks to all involved!
--
MASTER storing ALSA
*** This bug is a duplicate of bug 274995 ***
https://bugs.launchpad.net/bugs/274995
Good catch! I hadn't thought about testing ipv6 resolution. It does
explain why amixer tries to resolve localhost even though an IPv4 entry
for it exists in /etc/hosts.
Perfect. I guess the missing search
I have to agree with Robb here. I have been bitten by this bug
(#274995), but I don't have Intel HDA onboard sound - I have a Terratec
EWS88 (module snd_ice1712). So if #126140 only applies to Intel onboard
sound, it is most certainly not a duplicate of this bug.
--
MASTER storing ALSA mixer
Yes, I agree that the problem seems to be related to pulseaudio (it is
the only part of the sound system that includes networking), but I
really like pulse and don't want to uninstall it.
Aside from that, I'm really not sure what the application is doing. In
the strace above, you can see that
It seems I can't help myself :)
Here are the results:
- commenting out everything in /usr/share/alsa/pulse.conf:
amixer responds fast
- removing the mdns references in /etc/nsswitch.conf
no change. However, removing dns does work. So the bug is likely in
libnss_dns, which is part of glibc
can anyone confirm whether they have a search ... statement in
/etc/resolv.conf, and whether removing that statement fixes the delays?
It's not really a workaround, because that file will be regenerated if
you use dhcp, but it does add an additional point of information.
--
MASTER storing ALSA
It appears to be fixed in 8.10. Repeating the above command results in
noise from the speakers and this terminal output:
[EMAIL PROTECTED]:~$ gst-launch-0.10 playbin2
uri=file:///usr/share/sounds/alsa/Noise.wav
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Public bug reported:
After dist-upgrading to intrepid, Ubuntu appears to hang when shutting
down. I have traced this down to the ALSA shutdown script taking more
than a minute (!) to save sound card state. More specifically:
[EMAIL PROTECTED]:~$ time amixer -c0 -q set Mic 0% mute
real
** Attachment added: strace -r log of amixer run
http://launchpadlibrarian.net/19456415/amixer.log.gz
--
amixer timeout when muting sound card
https://bugs.launchpad.net/bugs/295136
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: output of sudo lshw
http://launchpadlibrarian.net/19456456/amix-hw.log.gz
--
amixer timeout when muting sound card
https://bugs.launchpad.net/bugs/295136
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I just found out the official live cd (ubuntu-8.10-desktop-amd64.iso)
exhibits the same behaviour on a laptop I am currently testing on; as
this is a bog-standard Sony Vaio laptop (Centrino platform, core2duo),
I'm afraid this might be a much more widespread problem than just my
system. Maybe a
** Attachment added: lshw output of Vaio laptop
http://launchpadlibrarian.net/19474256/vaio-hw.log.gz
--
amixer timeout when muting sound card
https://bugs.launchpad.net/bugs/295136
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
see #295136. The problem is actually in the amixer executable, which
gets invoked about 15 times during shutdown. The problem is reproducable
(for me) by running amixer in single-user mode. strace log can be found
in the mentioned report.
For reference, see the following note in the news section
Public bug reported:
I'm not sure this should be filed against fglrx-installer, but I'm going
to anyway, because this is where people will search first. This concerns
the latest intrepid release, that has been invalidated on purpose
because there simply is no fglrx version that works with the X
In light of the recent comments, I'm starting to see the additional
problems with having firefox as-is in main, especially with the web
services enabled by default. Indeed, like Chip pointed out, Firefox with
web services cannot be freely used without taking note of its use
restrictions. I do
I am impressed with the solution that has sprung forward, even if it is
only a mockup. I already commented on them, we'll have to wait how the
final version pans out. I'm wondering how much Canonical had a hand in
that mockup. I guess we'll never know :). Either way, it looks like the
can this possibly be a duplicate of #254671 ?
The backtrace listed above is incomplete, but it seems to be following
the same codepath as the aforementioned bug. The only difference I can
see is that this bug is not triggered automatically on login, is that
correct?
--
gnome-settings-daemon
I have found this happens with both jockey-gtk and jockey-kde on my
system (up to date as of an hour ago).
--
jockey-gtk crashed with DBusException in call_blocking()
https://bugs.launchpad.net/bugs/255889
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Has this ever been reported upstream? The closest I could come to an
upstream report is http://bugs.kde.org/show_bug.cgi?id=110814 but that
has been resolved (presumably it only fixed the issues with the
crossfade length).
I'm using the dynamic playlists quite a lot, and have crossfading set to
jnygaard wrote:
No hurry... I had to do real work myself, so I simply put in a new PCI-
based USB host adapter, and voila, disks work at full speed...
Just for clarification: are you saying that with a new card plugged in,
the old ports suddenly started playing nice to each other, or did you
According to some of the duplicates, this error appears with certain
uhci chipsets as well, however the error in those cases seems to be
error -110.
Also, I forgot to mention the workaround of disabling autosuspend. That
also seems to work for only a few people (haven't tried it myself).
--
Public bug reported:
Binary package hint: libdbus-ruby
Please take a look at upstream bug report https://trac.luon.net/ruby-
dbus/ticket/23. I filed it just minutes ago, after I got bitten by it.
The fix is relatively low-risk but has only received preliminary testing
by myself.
Any chance the
I can confirm the workaround posted above, to connect the usb-1 devices
via an external hub instead of directly on the root hub. Oddly enough,
the usb hub I am using is usb-1 only; I would have expected the
workaround to work only when using an usb-2 hub.
--
ehci_hcd module causes I/O errors in
USB events since boot sequence:
[26] both ohci and ehci drivers loaded
[27] ehci recognizes and activates LaCie external disk
[28] ohci fails to activate mouse
[160] plug-out-and-in logitech mouse; no recourse
[570] rmmod ehci-hcd
[571] ohci activates external disk on full speed
[613]
I thought I'd chime in as well. This bug is old, seeing as how Bug #54273 is
essentially the same bug. However, I have not been hit hard by this bug until
today, under:
[EMAIL PROTECTED]:~# uname -a
Linux neminis 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686
GNU/Linux
My symptoms
Public bug reported:
I'm trying to teach QuodLibet to support gapless playback, but I can't
because the playbin2 element doesn't appear to work correctly in Hardy
(the default playbin works as advertised, but doesn't support gapless):
[EMAIL PROTECTED]:~$ gst-launch-0.10 playbin2
*** This bug is a duplicate of bug 210180 ***
https://bugs.launchpad.net/bugs/210180
It would be nice if I would be allowed to view bug #210180. I understand
the user has probably marked the bug as private, but I can't confirm or
refute the duplicate status of this bug when I can't view it,
This appears to be similar to what I have seen so far on every PC that I
have upgraded from gutsy to hardy: after a dist-upgrade, GNOME only
appears to work in fail-safe mode. When I select GNOME in non-failsafe
mode, the login screen (kdm) disappears but the background stays the
blue background
it appears the bug is due to pulseaudio being wrongly configured; even
after manually starting pulseaudio (/usr/bin/esd is a wrapper for PA),
there is no daemon listening on port 16001. However, I have found that
GNOME does start after a timeout (appeared to be more than 30 seconds
though?), if
(apologies for spamming this bug)
ALSA does not work under KDE either; in KDE System Settings, the sound system
is configured to use OSS. If I switch to ALSA, I get no error messages but I
get no sound either...
[EMAIL PROTECTED]:~$ lspci -vv
00:11.5 Multimedia audio controller: VIA
Fixed for me:
[EMAIL PROTECTED]:~$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such device
[EMAIL PROTECTED]:~$ asoundconf list
Names of available sound cards:
V8237
camera
[EMAIL PROTECTED]:~$ asoundconf set-default-card V8237
And after this, both alsamixer and pulseaudio
Sadly, it is not completely fixed. It seems that gnome-session does not
start pulseaudio by itself when a user logs in. I have to login to a
terminal and manually start pulseaudio before I can login to GNOME (yes,
I can also wait for about 60 seconds, but I still won't have sound in
GNOME then).
Public bug reported:
Binary package hint: language-selector
Running a just-upgraded version of Hardy beta on i386.
The first time I started the language-selector applet, it advised me
that certain languages were incompletely installed, and I let it install
the language support files for KDE for
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/13587482/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/13587483/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/13587484/ProcStatus.txt
** Attachment
The .desktop file (/usr/share/applications/language-selector.desktop) contains
the following line:
Exec=/usr/bin/gnome-language-selector
Shoudn't this be started with gksu?
Exec=gksu /usr/bin/gnome-language-selector
--
gnome-language-selector crashed with IOError in getSystemDefaultLanguage()
It's not just fglrx. I get the same white screen when using the ati
driver. I can still log in using KDE as my window manager, but I can
only get to Gnome when I use the failsafe mode, but it's dog-slow (read
2 seconds to focus a window)
I believe this is caused by a bug in the compiz start
Forgot my hardware: it's an ATI Technologies Inc RV516 [Radeon
X1300/X1550 Series], and my system is up-to-date as of a few hours ago
(let's say March 23rd, 19h00 GMT).
I'm on 64bit, and using the fglrx driver seems to freeze my entire
system (at least the video card part). So I can't test the
the .xsession-errors file when running Gnome (white screen situation).
Some errors appear serious:
/usr/bin/compiz.real (core) - Warn: Unable to parse XML metadata from file
ccp.xml
/usr/bin/gtk-window-decorator: Screen 0 on display :0.0 already has a
decoration manager; try using the --replace
gzip'ed because of its size. I fail to notice anything of interest here.
(oh, and concerning the previous xsession-errors: I have put a set -x
line in the /usr/bin/compiz start script)
** Attachment added: Xorg.log file when running Gnome (white screen situation)
Public bug reported:
Binary package hint: hal
This is actually so very minor that I can't believe I'm actually reporting it;
there just aren't any more interesting things to report :)
A file /usr/share/doc/TODO.gz is installed by the package, while the
corresponding directory hal/ remains
contrary to what Björn Streicher wrote earlier, I have the following in
xorg.conf:
Option Composite enable
Option AccelMethod EXA
Driver ati
and VLC still crashes with a BadAlloc error (serial 476 error_code 11
request_code 146 minor_code 5)
[EMAIL PROTECTED]:~$ dpkg -s
Public bug reported:
Performed a dist-upgrade from Edgy-Feisty this morning. The upgrade went well,
but after reboot, the screen would remain blank where usually GDM would appear.
Ctrl-Alt-F[1-6] did not work, however the system was not frozen since num-lock
still toggled and Ctrl-Alt-Delete
Additional note: in 80x24 textmode, the monitor's OSD reports:
700x400, 61.5K, 70 (I assume resolution, Hrefresh, Vrefresh)
When booting with Usplash, the mode changes to
1024x1024, 64K, 60
This mode is the same when X started succesfully (as it has now)
When Usplash completes, the modeline
86 matches
Mail list logo
