** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/41498986/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41498987/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/41498988/Disassembly.txt
** Attachment
I also have (had?) this issue. I highly suspect that at least in my case
the problem is that I installed amd's catalyst driver for my radeon
card. Since catalyst doesn't support my card the xorg radeon driver is
used.
I got the exact same stacktrace whenrunning glxinfo. I then uninstalled
To clarify: When reloading the page with the embedded player, the volume
will be reset to zero again.
** Tags added: amd64
--
Volume of totem browser plugin on minimum
https://bugs.launchpad.net/bugs/527432
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
osd.update is broken in Lucid, but works in Karmic. Tested on lucid
live-cd dated 2010-03-07.
Not sure in which package the error lies, but the changelog for notify-
python just says it's recompiled for lucid, which makes me believe the
problem is in libnotify.
1) Lucid
2)
** Attachment added: test script for pynotify regression
http://launchpadlibrarian.net/40506436/osd_test.py
--
regression: osd.update() is broken in pynotify
https://bugs.launchpad.net/bugs/534522
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have been using nvidia-190 for a week with no crashes. Now I'm back on
nvidia-185 and had a crash just now.
Xorg: 1:7.4+3ubuntu9
Nvidia: 185.18.36-0ubuntu9
Apps running: firefox, chromium, pidgin, liferea.
Was watching a youtube-clip. I still don't know how to trigger.
Copypasted from
Public bug reported:
Binary package hint: xorg
1) 9.10 karmic
2)
xorg:
Installerad: 1:7.4+3ubuntu7
Kandidat: 1:7.4+3ubuntu7
3) nothing
4) For no apparent reason, X dies and I'm greeted with the login screen.
Naturally all work is lost, which makes this a serious issue.
This happened
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34847068/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34847069/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34847070/Dependencies.txt
**
Nvidia driver versions:
nvidia-185-libvdpau:
Installerad: 185.18.36-0ubuntu9
Kandidat: 185.18.36-0ubuntu9
nvidia-185-modaliases:
Installerad: 185.18.36-0ubuntu9
Kandidat: 185.18.36-0ubuntu9
nvidia-185-kernel-source:
Installerad: 185.18.36-0ubuntu9
Kandidat: 185.18.36-0ubuntu9
The bugreport is from the second occurence. I did not report the first
crash.
From memory this is what I had running (both times):
gimp, firefox, pidgin, terminal, hugin panorama creator.
The first time I'm not sure which app I was using, the second time I was
working in hugin.
--
Spontaneous
At the moment I use the nvidia-vdpau ppa, and that repo has it's own
mplayer-package (2:1.0~rc3+svn20090620~karmic~ppa4), which is to the
best of my knowledge unpatched regarding screensaver and font dirs (bug
#448603).
The 2:1.0~rc3+svn20090426-1ubuntu10 version works as expected for me.
sön
I notice that original bug reporter has HP with HDA Intel sound.
Coincidentally, so do I.
Do all of you have HDA Intel hardware?
Do all of you have a HP/Compaq computer?
To me this looks like a solid kernel driver/hardware issue. IMHO it
should be investigated if a driver fix is possible. If it
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: NVidia [HDA NVidia], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: richie 6214 F...m
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34072286/AlsaDevices.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/34072287/AplayDevices.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34072288/BootDmesg.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/34072289/Card0.Amixer.values.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/34072290/Card0.Codecs.codec.0.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34072292/CurrentDmesg.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34072294/Dependencies.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/34072295/PciMultimedia.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/34072296/XsessionErrors.txt
** Tags added: apport-collected
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: mplayer
1) Karmic, 9.10
2) mplayer:
Installerad: 2:1.0~rc3+svn20090426-1ubuntu10
Kandidat: 2:1.0~rc3+svn20090426-1ubuntu10
3) I played some music tracks through mplayer, and suspended the laptop. When
resuming from suspend I expected audio to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34045894/Dependencies.txt
** Attachment added: SystemConf.txt
http://launchpadlibrarian.net/34045895/SystemConf.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/34045896/XsessionErrors.txt
--
** Attachment added: lsmod.txt
http://launchpadlibrarian.net/34046083/lsmod.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: lshw.txt
http://launchpadlibrarian.net/34046242/lshw.txt
--
mplayer: alsa fail on resume
https://bugs.launchpad.net/bugs/456415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The bug is not there for me anymore, with the new version
(2:1.0~rc3+svn20090426-1ubuntu10)
--
Screensaver no longer disabled while using mplayer
https://bugs.launchpad.net/bugs/448595
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
In this thread:
http://ubuntuforums.org/showthread.php?t=1284219page=3
there is a python script that puts a simple volume control in the tray/panel.
I've also posted a more complete solution there, but it's somewhat complicated.
--
[karmic] removing pulseaudio breaks sound control
Works great now, thanks!
--
mplayer OSD no longer working
https://bugs.launchpad.net/bugs/448603
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
mån 2009-10-12 klockan 05:38 + skrev Reinhard Tartler:
Richard Jonsson richard_jons...@bredband.net writes:
What you are saying is that you can't reproduce this bug?
I think I found it by chance: It seems that the patches are not applied
on other architectures than i386. I'll
Public bug reported:
Binary package hint: acpi
1) 9.10 karmic
2) acpi 1.4-2 ** I am not sure acpi is the right package **
3) I expected intensity of the display backlight to change at least within a
second when pressing XF86MonBrightnessDown and XF86MonBrightnessUp keys.
4) Brightness changes,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33555230/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33555231/XsessionErrors.txt
--
Brightness buttons very slow
https://bugs.launchpad.net/bugs/449775
You received this bug
mån 2009-10-12 klockan 19:15 + skrev Dylan Taylor:
It could be possible that it is a system hardware limitation and not an
I disagree, since it works in prior versions of ubuntu, and other
distros, as well as windows xp.
actual bug, but I agree that the brightness should change much faster
Sorry, wrong bug #
--
brightness-keys react slowly
https://bugs.launchpad.net/bugs/286102
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
Actually, I think it's kernel-related this time around. It takes about
as long to change brightness in a terminal as using hotkeys.
# time echo 84 /proc/acpi/video/VGA/LCD/brightness
real0m0.763s
user0m0.000s
sys 0m0.000s
That wasn't the case last time around (the old bugreport).
Actually, I think it's kernel-related this time around. It takes about
as long to change brightness in a terminal as using hotkeys.
# time echo 84 /proc/acpi/video/VGA/LCD/brightness
real 0m0.763s
user 0m0.000s
sys 0m0.000s
That wasn't the case last time around (the old bugreport).
--
Public bug reported:
Binary package hint: mplayer
1) karmic, 9.10
2) mplayer:
Installerad: 2:1.0~rc3+svn20090426-1ubuntu9
Kandidat: 2:1.0~rc3+svn20090426-1ubuntu9
3) I expected to view a video without the screen going blank every once in a
while.
4) Screensaver activated after set time, but
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33441428/Dependencies.txt
** Attachment added: SystemConf.txt
http://launchpadlibrarian.net/33441429/SystemConf.txt
--
Screensaver no longer disabled while using mplayer
https://bugs.launchpad.net/bugs/448595
You
Public bug reported:
Binary package hint: mplayer
1) 9.10 karmic
2) mplayer:
Installerad: 2:1.0~rc3+svn20090426-1ubuntu9
Kandidat: 2:1.0~rc3+svn20090426-1ubuntu9
3,4) When seeking, pausing, pressing 'o'-key there should appear osd text.
There are play/pause/ff/rev symbols, but no text.
I
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33441963/Dependencies.txt
** Attachment added: SystemConf.txt
http://launchpadlibrarian.net/33441964/SystemConf.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33441965/XsessionErrors.txt
--
Public bug reported:
Binary package hint: hugin
1) karmic 9.10
2) hugin:
Installerad: 0.8.0.dfsg-2ubuntu1
Kandidat: 0.8.0.dfsg-2ubuntu1
When starting hugin nothing appears to happen. It silently quits. When
running from a terminal it reports the following and quits:
$ hugin
hugin: error
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33442765/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33442767/XsessionErrors.txt
--
Hugin depends on libboost-thread1.34
https://bugs.launchpad.net/bugs/448621
You received this
sön 2009-10-11 klockan 14:04 + skrev Reinhard Tartler:
Richard Jonsson richard_jons...@bredband.net writes:
I think the actual problem is that mplayer seeks for fonts in the user
dir, relevant lines from mplayer -msglevel=6 test.avi:
can you please retry with mplayer -msglevel=6
sön 2009-10-11 klockan 12:20 + skrev Darxus:
This issue is present in jaunty as well as in darxus's ppa.
You meant the karmic archives, not jaunty, right?
No I meant jaunty, karmic, and your ppa.
I never got it to work in jaunty, and didn't bother to research the
issue back then.
My
sön 2009-10-11 klockan 12:09 + skrev Darxus:
I can't reproduce this.
I removed all my libboost-thread packages and hugin, aptitude installed
hugin, it installed libboost-thread1.38.0, I verified that's the only
version I have installed, and hugin (0.8.0.dfsg-2ubuntu1) works.
What
sön 2009-10-11 klockan 19:09 + skrev Reinhard Tartler:
ok, this meas that for some reason, fontconfig is *not* enabled by
default for some reasons. There are a number of bugs because of this,
but this really puzzles me. I've contributed a patch upstream that
enables fontconfig by default,
Public bug reported:
Binary package hint: pulseaudio
1) Description: Ubuntu karmic (development branch)
Release:9.10
2) pulseaudio:
Installerad: 1:0.9.18-0ubuntu3
Kandidat: 1:0.9.18-0ubuntu3
3) I expect sound in zsnes, and no hangs.
4) With pulseaudio installed, starting zsnes
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33046816/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33046818/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33046819/BootDmesg.txt
**
Public bug reported:
Binary package hint: pulseaudio
1) Description: Ubuntu karmic (development branch)
Release:9.10
2)
3) Upon removal of pulseaudio I expected the volume applet to still
exist and function, as it did in jaunty.
4) Volume keys no longer work without pulseaudio
Public bug reported:
1) Description: Ubuntu karmic (development branch)
Release:9.10
2) linux-generic:
Installerad: 2.6.31.11.22
Kandidat: 2.6.31.11.22
3) No bang/click when audio hardware is being accessed
4) At least once during boot and on start of audio playback there is a
loud
** Attachment added: lspci
http://launchpadlibrarian.net/32997738/lspci
--
loud bang when start of audio playback
https://bugs.launchpad.net/bugs/442570
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I simply purged pulseaudio and the problem went away, software sound
mixing still works. No more a/v sync problems with video either. My
biased opinion is that my laptop runs cooler too, but can't confirm.
YMMV.
The command I used was sudo apt-get purge pulseaudio.
Note that this doesn't fix the
Test case 1:
1. Watch clip on youtube
2. repeat step 1, about 30% of the time it will err, and pulseaudio process
needs to be killed. Firefox will be fine if you manage to close the youtube tab.
Test case 2:
1. Watch video with mplayer cli
2. Pause mplayer for a minute or so.
3. Possibly there
Public bug reported:
Binary package hint: pulseaudio
After upgrading jaunty today, pulse (0.9.14-0ubuntu11) broke for me.
When watching a video with mplayer it usually works ok at first, but pausing
and resuming sometimes trigger this bug. Rhythmbox has this same problem too. I
can not
No, I have previously experimented with resampling-method, but that
setting got restored with the latest update. I should mention now that
after killing the pulse process I have not triggered the bug again.
--
static noise, no audio in pulseaudio 0.9.14-0ubuntu11
Ok, I just got this again. Starting a flash video clip in firefox:
pulse process at 60% and also noticed that syslogd process was at a constant
39%. Then checked /var/log/syslog and it's hammered with messages like these:
Mar 10 17:08:07 richie-laptop pulseaudio[4564]: alsa-util.c:
My locale is sweden/swedish if that helps. As this happened some time
ago my memory is faint. It could have been a cancel-button as well.
Abort/cancel are more or less synonym in my locale.
I don't know how to reproduce it, so feel free to close this bug if it
doesn't provide the info needed to
Maybe resample-method should be configurable through the sound settings
applet?
It's a huge waste to choose anything but the fastest algo when using pc
speakers which I think is quite common. When using good headphones or a
mid- to highend hifi you'd want to choose a good algo over a fast one
I see this on a geforce 6150go on a hp dv2140eu laptop. The banding goes away
after a suspend-resume cycle, and comes back after reboot.
On my screen it's equivalent to posterize a screenshot with a value of 63 which
would mean 6bpp.
Driver: 180.35
--
Gradient banding in new nvidia driver
I'm running jaunty, updated today. Still an issue, and it appears when I reboot
or when resuming from suspend2ram.
I use the proprietary nvidia driver. Not sure it this happens with the open
driver.
I don't care about this personally, but I'd think it looks kind of
creepy for a novice user, and
Public bug reported:
Binary package hint: update-manager
What actually happened:
I had previously changed/boot/grub/menu.lst and when update-manager asked what
to do when upgrading the kernel I wanted a diff view. After I was done I
clicked abort, which was'nt handled gracefully; the script
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/21724089/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/21724090/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/21724091/Dependencies.txt
**
@Leann:
I have the exact same problem as original reporter in the bug description, so
should I copy-paste original reporters bug description into a new report then?
I have reassigned my volume keys too. They didn't work at all after upgrade to
intrepid. I didn't have the issue before reassigning
The bug is very much NOT fixed at least on my system. Fully updated
intrepid, last checked minutes ago.
Can someone tell what package is responsible for osd-handling when volume is
changed?
I have filed another bugreport 286102 brightness-keys react slowly which I
believe is related, and which
With the guest-account and the theme it has assigned, it is really easy to
reproduce. Just drag the mouse-pointer over and past the
minimize/maximize/close buttons and the titlebar will distort. I can't
reproduce this on all windows, like firefox. But at least gedit and pidgin
behaves this
By following the link from your post above I found out the problem. The
actions volume up, volume down, mute had the wrong keycode
assigned to them. I have changed them now, through
System-Preferences-Keyboard Shortcuts.
For completeness I provide the info below anyway:
1. What the key *should*
1. What the key *should* do.
Key1: Brightness down, darken backlight, a sun with a down-arrow to the right
Key2: Brightness up, brighten backlight, a sun with an up-arrow to the right
2. What keycode (magic number) the key produces on your laptop.
Key1: XF86MonBrightnessDown
Key2:
This bug is still there with intrepid!
rhythmbox:
Installerad: 0.11.6svn20081008-0ubuntu3
Kandidat: 0.11.6svn20081008-0ubuntu3
It affects muting too. A laymans guess is that rhythmbox gets confused
by the mixer changes, or intercepts the keypresses and collides someway
with the global
Only gnome apps are frozen (rhythmbox, firefox, gnome-terminal). I can
choose open in the menu in kaffeine for example, and browse directories,
or executing commands in xterm. Tabbing between windows works at least
with compiz enabled.
--
Changing volume with function keys hangs the system when
I got this with firefox still alive afterwards!? I don't get it at all.
Moments earlier npviewer crashed, but video (youtube) played anyway..
wasn't aware it could recover like that.
--
firefox crashed with SIGSEGV in getenv()
https://bugs.launchpad.net/bugs/277191
You received this bug
Also have this problem. I just upgraded to intrepid and it has not
improved. For the record, about 9% usage on halfspeed on a turion tl52
1.6GHz
As a bonus when choosing alsa instead of pulseaudio in audio settings
flash breaks, possibly more. Used to work great, in kubuntu at least.
rantI don't
Public bug reported:
Since upgrading to intrepid 8.10 from hardy 8.04 titlebars on windows
gets distorted when switching windows, or sometimes when hovering
mousepointer over the titlebars. The titlebar is correctly redrawn on
next hover.
I use nvidia proprietary drivers, which I updated at the
Public bug reported:
Volume keys don't affect master volume anymore since upgrading to intrepid
8.10. Mute-key is also broken.
The above keys work just fine when using guest account, but not as a regular
user.
They worked fine in hardy 8.04. When watching a movie in mplayer, mplayer
reacted
Public bug reported:
On boot, after a kernel message about aperture above 4Gb, ignoring when I
expect the bootsplash with progressbar, I instead see a white scary screen with
vertical lines that fade in color and brightness. I've booted intrepid 3 times,
and was greeted with this behavior 2
Public bug reported:
When pressing fn+brighten, fn+darken on laptop, the brightness first gets
adjusted, then the osd pops up and restores previous setting and after a delay
changes it again. If pressing rapidly, brightness alternates between two
strengths until osd-control has caught up.
I would just like to point out that sam tygiers bug is not the same as
mine, but related ofcourse.
From sam tygiers dmesg:
[5.752349] forcedeth :00:0a.0: Invalid Mac address detected:
00:00:00:00:00:00
This card don't read an address at all, whereas my card got it
backwards. The patch I
I hope I assigned this to the right identity. This bug should be easy to
backport to a current gutsy kernel. Patch is provided at
http://lkml.org/lkml/2008/1/3/418
** Changed in: ubuntu
Assignee: (unassigned) = Kernel Bugs (kernel-bugs)
--
first eth device gets new number on resume
Bug has been confirmed on LKML, and a patch has been provided there, for
testing, which solves the issue in my case. See links below:
For a complete discussion on LKML:
http://lkml.org/lkml/2008/1/2/253
The provided patch:
http://lkml.org/lkml/2008/1/3/418
** Changed in: ubuntu
Status:
I confirm this bug. It has existed for a very long time, maybe forever.
This is particulary noticable if the system is suspended and later when
resumed For MSN, Kopete acts as if it was connected, with online
contacts showing. However sending messages is impossible. After restart
of Kopete, it is
Public bug reported:
On resume from suspend to ram, Every other time the eth0 device gets a
different number, ie eth43. This number seems to increment too.
Thus a workaround would be to suspend and resume again to get back to the name
eth0. The strange thing is that the MAC number is not that
Just noticed in that dmesg output that the mac address has a revered
byte-order. As I don't know what to do with that I'll leave the bug
here.
--
first eth device gets new number on resume
https://bugs.launchpad.net/bugs/175333
You received this bug notification because you are a member of
After some research it apperas that the forcedeth driver, which I use, has had
issues with reverse mac addresses in other contexts.
A guess is that the driver attempts to correct the address byte order on boot
up, but fails to restore on suspend, and therefore reverses the corrected
address on
82 matches
Mail list logo
