Reply to #20 - As an example, any flash content on www.boingboing.net
crashes in Firefox under Hardy.
http://www.boingboing.net/2010/07/05/four-lions-this-is-s.html
Other sites with flash produce the same message.
I have three flash plugins on Firefox - the old 9.0 r31, the current 9.0
r100 and
This bug also affects me. I upgraded to 3.6.6. on Hardy this morning and
noticed that any Flash content crashes the plugin. I deleted the
pluginreg.dat file (following the Firefox troubleshooting guide) as well
as upgrading to the latest adobe plugin but it still failed to work.
Funnily enough, the
term.log is an empty file
--
/media/cdrom-1/cdromupgrade: line 32: 12909 Segmentation fault
$TMPDIR/$COD ENAME --cdrom "$cddirname"
https://bugs.launchpad.net/bugs/259430
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bu
** Attachment added: "main_update_self.log"
http://launchpadlibrarian.net/18677248/main_update_self.log
--
/media/cdrom-1/cdromupgrade: line 32: 12909 Segmentation fault
$TMPDIR/$COD ENAME --cdrom "$cddirname"
https://bugs.launchpad.net/bugs/259430
You received this bug notification bec
** Attachment added: "main_pre_req.log"
http://launchpadlibrarian.net/18677245/main_pre_req.log
--
/media/cdrom-1/cdromupgrade: line 32: 12909 Segmentation fault
$TMPDIR/$COD ENAME --cdrom "$cddirname"
https://bugs.launchpad.net/bugs/259430
You received this bug notification because you
** Attachment added: "main.log"
http://launchpadlibrarian.net/18677243/main.log
--
/media/cdrom-1/cdromupgrade: line 32: 12909 Segmentation fault
$TMPDIR/$COD ENAME --cdrom "$cddirname"
https://bugs.launchpad.net/bugs/259430
You received this bug notification because you are a member of
I have encountered the same bug. Here are my set of /var/log/dist-
upgrade/* files
** Attachment added: "apt.log"
http://launchpadlibrarian.net/18677226/apt.log
--
/media/cdrom-1/cdromupgrade: line 32: 12909 Segmentation fault
$TMPDIR/$COD ENAME --cdrom "$cddirname"
https://bugs.launch
I have had this problem resolved in the last week after submitting a bug
report to the k3b developer (Sebastian Trueg). I was able to narrow the
problem to k3b due to changing my CDRW to a DVDRW drive on my PC.
Apparently there was a problem with the way k3b was communicating with
the hardware (SC
Public bug reported:
Binary package hint: kdelibs4c2a
I have been using k3b for about a month with no problems under Gnome in
Dapper which is completely up-to-date with the latest kernel and updates
to packages.
I was using it yesterday (30/3/07) and had no problem launching it from
the Gnome Ap
I believe I have the same problem in Dapper, kernel version
2.6.15-27-386. I recently installed Dapper and downloaded the latest
updates, then installed the latest k3b off the repository. k3b would not
run from the icon in the menu, nor from the command line. k3bsetup would
not run either expecting
10 matches
Mail list logo
