** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/8126844/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/8126845/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/8126846/ProcStatus.txt
--
evolution
Here's the backtrace with evolution-data-server-dbgsym, evolution-
dbgsym, evolution-plugins-dbgsym, and evolution-exchange-dbgsym
installed.
** Attachment added: Backtrace
http://launchpadlibrarian.net/8139405/gdb-evolution.txt
--
evolution crashed with SIGSEGV
Tested with mp3, flac, ogg (with vorbis), mp4 (with aac), wav, wavpack,
ac3 mp2. The crossfading backend works fine on all but the wavpack.
--
Crossfading engine never starts playing wavpack files
https://bugs.launchpad.net/bugs/119044
You received this bug notification because you are a
** Attachment added: rhythmbox-debug.log
http://launchpadlibrarian.net/8009470/rhythmbox-debug.log
--
Crossfading engine never starts playing
https://bugs.launchpad.net/bugs/119044
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
Public bug reported:
Binary package hint: rhythmbox
Running Gutsy, with rhythmbox 0.11.0-0ubuntu3.
I selected the crossfading engine (Edit-Preferences-Playback), then
restart Rhythmbox. While using the crossfading backend, when I try to
play a song rhythmbox appears to never quite start
No, they're mostly wavpack flac, and a couple of mp3s.
So, looking at that bug I tried playing files from each of those types, and
both the flac mp3 files played fine. Only the wavpack files fail to play.
All the wavpack files were encoded in Banshee using GStreamer, and play fine in
both
to definitely eliminate the network as the source of the problem.
** Changed in: totem (Ubuntu)
Assignee: (unassigned) = Chris Halse Rogers
Status: Unconfirmed = Needs Info
--
unable to run avi from windows partition on separate machine, same workgroup
https://bugs.launchpad.net/bugs/119027
Thank you.
So, Totem's handling of this file is incorrect. If you have a totem crash file
in the /var/crash directory, it may be useful to attach to this bug.
If not, we can determine whether this is a bug in Totem or in the GStreamer
engine by trying to play the AVI with the following command
Is the change from needs info to unconfirmed because you have all
the needed info? If you still need more, I can install whatever extra
debugging packages you want.
Just checking, it's been a while since I posted the last valgrind logs.
--
[apport] gaim crashed with SIGSEGV in malloc() while
Fortunately, gaim is being very obliging and crashing nice and
repeatedly.
New logs, with libdbus-glib-1-2-dbgsym, libnotify1-dbgsym, and
libglib2.0-0-dbg thrown in for good measure.
** Attachment added: New, improved valgrind log
Apparently, yes :). New, debug-symbolified logs attached.
** Attachment added: Valgrind logs with gaim-dbg, libdbus-1-3-dbgsym
libnm-glib0-dbgsym installed
http://librarian.launchpad.net/7220824/valgrind-logs-gaim-dbgsym.tar.gz
--
[apport] gaim crashed with SIGSEGV in malloc() while idle
Ok, it seems that the Playing music with Banshee part of my report is
irrelevant. Gaim once again crashed in the background, with no music
playing.
Valgrind logs attached.
** Attachment added: Valgrind log
http://librarian.launchpad.net/7216261/valgrind-logs-gaim.tar.gz
--
[apport] gaim
Ok, it seems that the Playing music with Banshee part of my report is
irrelevant. Gaim once again crashed in the background, with no music
playing.
Valgrind logs attached.
** Attachment added: Valgrind log
http://librarian.launchpad.net/7216262/valgrind-logs-gaim.tar.gz
--
[apport] gaim
Public bug reported:
Binary package hint: gaim
I had just started gaim, and it was idle in the background when it
crashed.
I was playing music with Banshee using pulseaudio when this happened, if
that's at all important.
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 7
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7192927/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7192928/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7192929/Disassembly.txt
** Attachment
It looks like this bug has reverted with Feisty's Firefox (2.0.0.1
+0dfsg-0ubuntu2). Increasing the DPI in gnome-font-preferences (from
130 to 160, down to or 120) affects the UI's fonts, but not the webpage
fonts.
Tested on gmail.com, ubuntuforums.org, launchpad.net, and forum
.go-compiz.org.
501 - 516 of 516 matches
Mail list logo