Unfortunately I must say I've moved on from using both Ubuntu and the
affected card within the last 10 years. Maybe one of the several other
affected people can provide some feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay... So I'm pretty angry right now so this might turn out somewhat rantish,
but please bear with me:
I just updated to Maverick to see how that's comming along. Well, turns out
that this 3 year old bug still persist.
We have had workarounds for this from almost the beginning. A IMHO quite
Had this issue to after doing an upgrade today (which makes me think that this
was not fixed by now as Ken Walker suggest).
However just logging out and back in did make Thunderbird start properly. I
wonder if this has to do with some leftover process (I was running Thunderbird
during the
I haven't really tested this (and it might be worthwhile if someone around his
sound card before Tuesday could ;)), but last time I checked the workaround
from #30 did only fix /playback/ on this card.
Obviously recording with this card is also a big factor, and speaking for
myself I'd even
This is indeed solved in Karmic and Lucid.
--
Volume multimedia keys stop working after first use
https://bugs.launchpad.net/bugs/345195
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have personally switched to the new PA based Volume thingy now. It
seams to me that the Volume Applet has now been completely removed,
which means it can't not work. I still think forcing PA on people is
bad, but I suspect this should be closed.
--
No volume control applet
ianc - You are right. Somehow the line in my 90-pulseaudio.rules got
messed up (even though I did carefully put it back everytime pulseaudio
was updated).
Any chance we can get that in the packages? As I understand it this
makes it at least work a bit (actually all I personally need works),
which
Public bug reported:
I got this while running a system upgrade and doing quite some other
stuff (transmission, gajim, kaffeine were all running). I have no real
clue what the immediate cause of this might be.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/32255585/AlsaDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/32255586/ArecordDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/32255589/BootDmesg.txt
**
FWIW what I wrote in #30 is what is currently working for me (as in it gives me
Analog Output. I have no inputs though.)
The fact this is necessary is AFAICT is caused by a change in pulseaudio, but
they blame it on ALSA.
What is described in the bug linked from #35 had worked for me giving me
After a update of the package AND a reboot this is fixed. I'm going to
assume it was fixed by some change that seems unrelated as I didn't see
anything that would fix something like this.
** Changed in: pulseaudio (Ubuntu)
Status: New = Fix Released
--
Sound played through pulseaudio is
Correction:
I just noticed it, but this only happens as long as Kaffeine is running. Before
and a while after sound (from other applications) is fine.
Also it now is more of a buzzing then cracks.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Released = New
--
Sound played through
I get this following log with pulseaudio - from opening to closing
kaffeine.
** Attachment added: buzz.log
http://launchpadlibrarian.net/32149932/buzz.log
--
Sound played through pulseaudio is overlayed with loud cracks
https://bugs.launchpad.net/bugs/433307
You received this bug
And again correction :( :
It now seems to me that this happens with any application as soon as I change
the volume. Also it's very loud (louder then it used to be at the same alsa
levels of the card anyway) even at 2%.
Sorry for the noise, maybe the log is still helpful though.
--
Sound played
I haven't had time to test knarf'spatch, but starting with
PULSE_NO_SIMD=1 pulseaudio - fixes this for me too. Feel free to
mark this as a duplicate if thathatman's bug 428519 turns out to be the
same thing that knarf found a workaround for.
--
Sound played through pulseaudio is overlayed
I haven't had time to test knarf'spatch, but starting with
PULSE_NO_SIMD=1 pulseaudio - fixes this for me too. Feel free to
mark this as a duplicate if thathatman's bug 428619 turns out to be the
same thing that knarf found a workaround for.
--
Sound played through pulseaudio is overlayed
Public bug reported:
When playing sound through pulseaudio I hear a loud cracking noise over the
actual sound.
The card is a M-Audio Audiophie 24/96 using a ICE1712 chipset.
Playback directly through Alsa is fine.
cat /proc/asound/cards:
0 [M2496 ]: ICE1712 - M Audio Audiophile 24/96
This is getting really frustrating.
The fix from the upstream Pulseaudio ticket had worked for me to get around
this, but with the newest version from the PPA I only get digital outputs
again. (needless to say I use the analog ones. So no sound for me again :( )
--
Pulseaudio fails to
The new version (1:0.9.16~test6-55-g1200-0ubuntu1~ubuntuaudiodev1) in
the ubuntu-audio-dev ppa fixes this for me.
--
pulseaudio crashed with SIGILL in pa_volume_memchunk()
https://bugs.launchpad.net/bugs/418448
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Valgrind result
** Attachment added: valgrind.log
http://launchpadlibrarian.net/31008508/valgrind.log
--
pulseaudio crashed with SIGILL in pa_volume_memchunk()
https://bugs.launchpad.net/bugs/418448
You received this bug notification because you are a member of Ubuntu
Bugs, which is
gdb result. I hope I got this one right, otherwise just ask.
** Attachment added: gdb-pulseaudio.txt
http://launchpadlibrarian.net/31008523/gdb-pulseaudio.txt
--
pulseaudio crashed with SIGILL in pa_volume_memchunk()
https://bugs.launchpad.net/bugs/418448
You received this bug notification
Here is the backtrace.
** Attachment added: gdb-pulseaudio.txt
http://launchpadlibrarian.net/30976501/gdb-pulseaudio.txt
--
Pulseaudio crashes with illegal hardware instruction
https://bugs.launchpad.net/bugs/419176
You received this bug notification because you are a member of Ubuntu
Bugs,
I can reproduce this with the version currently in karmic and even with
conduit-trunk in the PPA.
Most reliable way to do so seems to be adding Network as a source.
--
conduit crashed with IndexError in on_iter_n_children()
https://bugs.launchpad.net/bugs/349254
You received this bug
I can reproduce this with the version currently in karmic and even with
conduit-trunk in the PPA.
Most reliable way to do so seems to be adding Network as a source.
--
conduit crashed with IndexError in on_iter_n_children()
https://bugs.launchpad.net/bugs/349254
You received this bug
Public bug reported:
Binary package hint: pulseaudio
This is on an up to date karmic with pulseaudio 1:0.9.16~test6-3-g57e1-0ubuntu1.
Whenever I try to play any audio pulseaudio crahes with the following:
illegal hardware instruction (core dumped) pulseaudio -vv
There is nothing suspicious in
** Summary changed:
- Pulseaudio fails to initialize Audiophile 2496
+ Pulseaudio fails to initialize ICE1712 chipsets
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the very same problem (same error messages) trying to do duplex
printing with Evince.
--
pdf printing on karmic fails: pdftopdf crashed on signal 11
https://bugs.launchpad.net/bugs/407344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The PPA packages are exactly the same. Works as long as front:0 has only 2
channels and tsched=0 is specified.
Otherwise it fails to open any output (the card is detected though).
--
Pulseaudio fails to initialize Audiophile 2496
https://bugs.launchpad.net/bugs/178442
You received this bug
Tada and it's a pulseaduio problem again:
Since tsched=0 has been removed from the default config pulseaudio doesn't
work any longer even with the above change. It claims there is no plug:front:0
even though I can play sound through that device using mplayer just fine.
Adding back tsched=0
The reason pulseaudio right now doesn't work with this card is that it expects
a front device that has only 2 channels.
A possible fix for this is changing it's definition to:
ICE1712.pcm.front.0 {
@args [ CARD ]
@args.CARD {
type string
}
type
This is great, because now I have no clue how to configure my
.asoundrc.asoundconf so that it uses pulse instead of the soundcard directly :/
I think asoundconf is still very useful even with pulse. Also there may be
people who prefer not using pulseaudio (even if this seems to be unbelievable
I don't know how you got the idea it was fixed.
I never actually tried Jaunty without the workaround but testing Karmic with
the default default.pa this bug is still alive and kicking. I really hope this
will finally be fixed for Karmic stable.
** Changed in: pulseaudio (Ubuntu)
Status:
FWIW: I don't think this is really fixed already, because it depends on
#344936. And as discussion in that Bug report indicates the Recommends
filed should say python-indicate and not indicate-python.
--
[jaunty] Use indicator-applet for new messages
https://bugs.launchpad.net/bugs/340213
You
Maybe it is unrelated, but I get the same behaviour when an autostart
action should occur (e.g. When I insert a DVD or CD in my drive).
--
Starting File Manager windows open uncontrollably
https://bugs.launchpad.net/bugs/325973
You received this bug notification because you are a member of
Update: In jaunty pulseaudio can now initialize the card, but sound only
comes out of the right speaker. The workaround posted here is therefore
still needed.
silly_rantThis is after over a year after reporting the bug and there
are 6 duplicates. I wonder why some people think pulseaudio
It also doesn't work on ICE1712.
Possible hint: all those cards don't have a Master volume control (in ALSA)
AFAIK.
--
gnome-sound-properties freez
https://bugs.launchpad.net/bugs/345550
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes indeed I mean the Volume Applet.
I had previously asked here: http://ubuntuforums.org/showthread.php?t=1099180
There are some people with the same problem that claim even a reinstall didn't
fix this.
(I'm also not really willing to reinstall my system just to get a volume
applet. This is not
Public bug reported:
This is on a up to date Ubuntu jaunty installation:
Ever since updating to jaunty I have had a strange problem with the volume
control multimedia keys.
I can use them once just fine. And they work as long as the notification
showing the status of the volume is visible. As
Public bug reported:
In current jaunty I can't get any volume applet to display any longer. Adding a
mixer applet to the panel does work (There is a mixer_applet2 running in ps
aux), but nothing is displayed in the panel.
As for the new pulseaudio based volume control I keep hearing about. I
fixed with 11.24
** Changed in: linux (Ubuntu)
Status: New = Fix Released
--
Backlight broken for HP Compaq 6715b in Linux 2.6.27-11.23
https://bugs.launchpad.net/bugs/317131
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
This is on a completely upgraded Ubuntu using ubuntu-proposed repository.
The linux-image package version 2.6.27-11.23 breaks controlling the backlight
on my HP Compaq 6715b.
It is just shown as unsupported by the gnome-applet, and also in
/proc/acpi/video/C*/backlight.
FWIW I have the same issue with cheese, but ekiga can use the camera
just fine, so this might not be a kernel issue.
--
GSPCA driver no longer works
https://bugs.launchpad.net/bugs/270618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hah, really wonder how that black line slipped in there.
Anyway here is a new version that closes this ticket and has no extra blanks
(hopefully).
** Attachment added: gajimV3.diff
http://launchpadlibrarian.net/17733820/gajimV3.diff
--
nautilus-sendto is build without Gajim support
So I take it that there is no syntax for referencing a bug without
closing it?
** Attachment added: gajimV4.diff
http://launchpadlibrarian.net/17734759/gajimV4.diff
--
nautilus-sendto is build without Gajim support
https://bugs.launchpad.net/bugs/261166
You received this bug notification
I have not tested it, because I'm not actively using boa any more, but just
from looking at the init script the situation is still exactly the same.
Both restart and reload send SIGHUP, but restart should kill and restart boa.
--
Boa can't restart or reload
https://bugs.launchpad.net/bugs/46908
Public bug reported:
Binary package hint: python-gtk2-dev
There is no pygtk-codegen-2.0 in python-gtk2-dev in intrepid any more, because
upstream moved to using pygobjects codegen which has been renamed to
pygobject-codgen-2.0 (or that is my understanding).
Upstream SVN has a compatibility
I can, it's not necessarily a good idea though ;)
The new patch I attached gets control(.in) and rules closer to the debian
version again, there are still differences though, due to the fact that Debian
has Icedove and Ubuntu has Thunderbird. Also adding --with-gajim=/usr back is
purely to be
In that case I'd beg you to just remove the check for gajim.png from the
configure script in a patch. Which would remove the need to build-depend on
gajim, but still enable building the plugin.
The file is not needed during build time and as the plugin will only load when
gajim is running
Attaching a debdiff that should fix the issue.
** Attachment added: Remove check for gajim.png from configure script
http://launchpadlibrarian.net/17086882/gajim.diff
--
nautilus-sendto is build without Gajim support
https://bugs.launchpad.net/bugs/261166
You received this bug notification
Public bug reported:
Binary package hint: nautilus-sendto
nautilus-sendto should build-depend on Gajim like it does in Debian.
This is because the configure script checks whether to build the gajim plugin
based on the existence of /usr/share/pixmaps/gajim.png.
I noticed Gajim was removed from
This must have been fixed somewhere along the way. I've seen such
dialogs in the meantime and they didn't have that error any more.
** Changed in: update-manager (Ubuntu)
Status: Incomplete = Fix Released
--
Reboot required dialog has ↵ characters in addition to newlines in german
Shutting down on low battery hasn't ever worked for me in hardy.
This is the output of g-p-m while on batterie till the system turns of because
the batterie is completely drained.
** Attachment added: gpm.debug.log.txt
http://launchpadlibrarian.net/14454099/gpm.debug.log.txt
--
[Gutsy]
Same with bcm4312 (rev. 02). It worked fine with 2.6.24-12 but in 2.6.25-15 -16
it's broken, but that seems to be bug #212933.
Is that by chance your problem too ettorevi?
--
[Hardy]Recent kernel update to 2.6.24-11 breaks b43 (with bcm4312)
https://bugs.launchpad.net/bugs/197959
You received
Could anybody actually shed some light on this for me?
Somehow it all is very confusing.
The patch seems to be meant to make bcm4311 cards work, but at the same time
breaks bcm4312 cards (that is what I was able to get from the bugs. some places
also say different things I guess it is very easy
As far as I can tell 4.80.53.0 is the correct version for the 2.6.24 kernel's
b43 module.
As of know neither version (4.80.53.0; 4.150.10.5) works for me. Prior to
upgrading to 2.6.24-15 (I skipped some version though) everything worked fine
using firmware version 4.80.53.0.
--
[Hardy] B43
Confirming as per comments and own experience.
This was working in earlier 2.6.24 packages, so I don't think we need 2.6.25 to
get working b43.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
2.6.24-15-generic kernel traceback ssb wireless b43
Same here. Since upgrading to nm 0.6.6-0ubuntu3 I get a apport crash report on
every boot that points me to this bug.
But nm works without any problems, this is just a apport inconvenience for me
as of now.
--
[apport] NetworkManager crashed with signal 5 in main()
I think the new problem is actually the one documented in Bug #204868
(including a fix).
Well actually it is reported in like 20 bugs, which are all linked in a wild
net of duplicate marks, but #204868 is the only one to include a patch (which
works).
--
[iwl4965] wireless support broken
That workaround works for me too, but I don't really get why it fails in the
first place. Everything that is given in the static configuration is already
used as a fallback by the auto-detection according to the warnings displayed.
Just to be a bit more sepcific, this two lines in
Sorry to be annoying, but I was wondering if this going to be fixed for hardy
or will be In Progress 'till hardy+1.
Beta is aproaching and this bug that renders pulseaudio (the default) useless
for a good hand full of people ist still there.
I'm sure you have more important bugs to fix, but I'd
I have neither /etc/asound.conf nor ~/.asoundrc*
asoundconf list returns:
Names of available sound cards:
M2496
UART
U0x46d0x8ad
Playing waves through aplay works fine.
--
Pulseaudio fails to initialize Audiophile 2496
https://bugs.launchpad.net/bugs/178442
You received this bug notification
Actually it's not only that the doctype is missing from
http://people.ubuntu.com/~bryce/tmp/firefox-3-js-issue.html, but this page
doesn't even have a root-element (should be a html
xmlns=http://www.w3.org/1999/xhtml;-tag in this case).
http://people.ubuntu.com/~bryce/Plots/plots-0.7.html has
Public bug reported:
Binary package hint: pulseaudio
I have a problem that makes pulseaudio unusable for me.
I noticed the only device listed by pulseaudio is my webcam (as an input device
obviously), so I tried starting pulseaudio from the command line to see what
was happening.
This resulted
I just tried and as far as I can tell this bug is not present in gutsy.
So if there is no chance to get a fix in feisty this bug should probably be
closed.
But if this chance exists there is still some work to be done tracking down the
change that fixed it.
Candidates are as far as I can tell:
Just tested it. You seem to be correct that this does not only happen with
gajim (It just was the only application I noticed this with.
I changed the summary.
** Summary changed:
- Gajim can't connect to avahi until avahi is restarted once.
+ Applications can't connect to avahi-daemon until
Public bug reported:
I've recently started using Gajim and think link-local messaging is a pretty
cool feature.
After enabling dbus in avahi's configuration and restarting avahi everything
worked just fine.
But after a reboot Gajim is complaining about avahi not running. invoke-rc.d
I just noticed a interesting twist to this bug.
When I was using 2.6.20-15-generic I got the same behaviour as most people
(Firefox crashes upon closing the last flash-using page). I recently installed
the lowlatency version of the kernel, using this Firefox hangs as soon as the
flash-plugin is
Turning off my on-board soundcard fixed this for me, too (which I think is
quite interresting, because I wasn't even using it for audio output).
It's using the snd_intel8x0 module.
--
firefox crashed -- libflashplayer.so
https://bugs.launchpad.net/bugs/104470
You received this bug notification
Sorry for the tripple comment. (wish one could edit comments)
Seems I spoke to soon. Disabling on-board sound actually brought the behaviour
I had without the lowlatency kernel back.
Firefox hangs (most of the time (as others noted there is a random component))
when closing the last flash.
--
I get some interresting behaviour, when I do hostname and hostname -f:
hostname:
myHostName
hostname -f:
hostname: Unknown host
In my /etc/hosts I have:
127.0.0.1 localhost
127.0.1.1 myHostName.localdomain.xx
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost
Public bug reported:
Binary package hint: update-manager
This bug occurs using a completely updated feisty fawn system.
Today I installed a kernel update so i got to see the Reboot Required dialog.
The german translation currently has a ↵ (in case launchpad can't process this,
this is the
Yes, sounds are turned on. Actually all settings are default if you
don't count the accounts as setting.
--
[apport] gaim crashed with SIGSEGV in gst_class_signal_emit_by_name()
https://launchpad.net/bugs/90216
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: gaim
I joined a IRC room where I got messaged by a bot.
This caused gaim to crash.
I wasn't easily able to reproduce this though.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 6 22:11:42 2007
DistroRelease: Ubuntu 7.04
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6647910/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6647911/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/6647912/Disassembly.txt
** Attachment
This packages seem to work good for me, but the minimize animation is very slow.
This has also been reported by some people on the forums:
http://www.ubuntuforums.org/showpost.php?p=2174720postcount=74
This is with a GeForce FX 5600 using the proprietary drivers, with one LCD
monitor.
I don't
** Changed in: gstreamer (upstream)
Bugwatch: GNOME Bug Tracker #353872 = GNOME Bug Tracker #334990
Status: Rejected = Unknown
--
Crashes when trying to read RealMedia Files
https://launchpad.net/bugs/56158
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: gnome-control-center
This is on a fully updated feisty installation.
I was trying to set up my M-Audio Delta Audiophile 24/69 (ICE1712) as default
soundcard using gnome-sound-properties dialogue.
It wrote both the .asoundrc and .asoundrc.asoundconf
*** This bug is a duplicate of bug 36256 ***
This is a site effect of bug #36256.
It is one of the glitches caused by gtk-qt-engine, which should always be
disabled if either xubuntu-desktop or ubuntu-desktop is installed. Right now
this does not work if kubuntu-desktop is installed first
**
Public bug reported:
Binary package hint: alsa-utils
Since I updated to Ubuntu 6.10 today my Audiophile 24/96 using the ICE1712
drivers stoped working with alsa.
According to aplay defaults.pcm.ipc_key, defaults.pcm.ipc_gid and
defaults.pcm.ipc_perm aren't set.
Setting these manually in
Actually the fix is definitely present in both dapper and edgy.
.gtkrc2.0 and .gtk_qt_engine_rc are not created by startkde if either xfce or
gnome is installed.
I could imagine that those files are created by a different script or
application.
Can you trace back the creation of those files to
You can have the issue if you installed kubuntu and then installed gnome of
xfce.
There is not issue if you install kubuntu-desktop package on xubuntu or ubuntu
Oh right, I forgot about this possiblilty.
But doesn't that basically mean that either startxfce4 and gnome-session have
to remove
I can confirm this on an up to date edgy install.
** Changed in: upstart (Ubuntu)
Status: Unconfirmed = Confirmed
--
System does not reboot
https://launchpad.net/bugs/58557
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Unfortunatly I can't upload it. I could host it on my local machine very
temporarily. So if someone want's the file just ping me on Jabber or freenode
and I'll put it online until you have it.
(Attaching it doesn't seem to work because it is to large)
--
rhythmbox segfaults when
This is a x86 system.
The file (I could actually narrow it down to 2 files that are doing this) can
be found on http://www.bluemanlibrary.com/library/cat17/page2/ as TV Total 2
(unluckiely they started to require registration).
--
rhythmbox segfaults when gstreamer0.10-ffmpeg is installed
Actually this seems to be (gstreamer-)ffmpeg crashing on some rm files
that are also in my music directory and taking rhythmbox down with it.
** Changed in: rhythmbox (Ubuntu)
Sourcepackagename: rhythmbox = gstreamer0.10-ffmpeg
--
rhythmbox segfaults when gstreamer0.10-ffmpeg is installed
Public bug reported:
Binary package hint: rhythmbox
As soon as I install gstreamer0.10-ffmpeg rhytmbox segaults (it seems this is
at the point when it rescans the library).
A backtrace in gdb shows:
#0 0xb23a53d8 in add_pixels_clamped_mmx () from
/usr/lib/gstreamer-0.10/libgstffmpeg.so
#1
The patch has definitly been committed now.
The symptoms described in the thread don't realy sound like this bug either.
--
gtk2-engines-gtk-qt causes GNOME-panel to crash upon startup and causes Gnome
to look ugly
https://launchpad.net/bugs/36256
--
kubuntu-bugs mailing list
** Bug watch added: GNOME Bug Tracker #315542
http://bugzilla.gnome.org/show_bug.cgi?id=315542
** Also affects: esound (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=315542
Importance: Unknown
Status: Unknown
--
M-Audio Delta Audiophile 2496 doesn't work properly in
88 matches
Mail list logo
