Any of us may close the report by changing its status from New to
Invalid. But I think there may be value to this report: as I mentioned
on AU (http://askubuntu.com/questions/439801/man-command-does-not-work-
with-yelp?noredirect=1#comment574556_439839), I'm not sure why the
legacy behavior cannot
Public bug reported:
In a Saucy amd64 system I opened a .tar.xz archive (which I'd previously
created myself on another system with tar cf ... followed by xz -9v
...) and double-clicked on the single folder it contained, to view its
contents in file-roller itself before performing any
*** This bug is a duplicate of bug 723841 ***
https://bugs.launchpad.net/bugs/723841
Comparison of symbolic stack traces indicates this is bug 723841. Other
descriptive information supports this (see the description of that bug
and of various duplicates). As for the different title, there may
*** This bug is a duplicate of bug 723841 ***
https://bugs.launchpad.net/bugs/723841
Comparison of the stack trace here to
https://bugs.launchpad.net/ubuntu/+source/file-
roller/+bug/723841/comments/3, in combination with the similarity in
circumstances triggering the crash, is sufficient to
Public bug reported:
I was viewing a couple folders of video files in pcmanfm on a Lubuntu
11.10 i386 system. One folder was of .mkv files; the other was of .avi
files. Nothing seemed to go wrong--pcmanfm did not itself crash, and all
the files were properly thumbnailed. I was not using Totem
*** This bug is a duplicate of bug 172416 ***
https://bugs.launchpad.net/bugs/172416
@Kushal
This is happening because eog uncritically assumes filetype from filename. Most
other modern image viewers look inside the image file to figure out what kind
of image it is, which is why they do not
*** This bug is a duplicate of bug 172416 ***
https://bugs.launchpad.net/bugs/172416
@Kushal
It is no longer necessary for you to attach any files or provide anymore
information--there is already a bug for this (bug 172416), and I'm setting this
as a duplicate of it.
** This bug has been
The original reporter (Kushal) indicates that this bug still occurs with
Precise, so I am changing this back from Expired to New.
@Kushal
Can you attach a few .png images (or at least one) that cause this problem on
your system, and a few .png images (or at least one) that do not? Such
Fixed x64 tag to amd64 (the correct architecture name for any 64-bit
x86-compatible PC or Mac) and added names of all the Ubuntu releases in
the duplicates.
** Tags removed: x64
** Tags added: amd64 lucid maverick natty oneiric
--
You received this bug notification because you are a member of
I still have this in Unity 2D as well, in Precise, still as described in
bug 808918. (I haven't tested in Oneiric in a while.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/827414
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
This is almost certainly bug 507062, see
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/507062/comments/94.
** This bug has been marked a duplicate of bug 507062
synaptic assert failure: synaptic:
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
This is almost certainly bug 507062, see
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/507062/comments/94.
** This bug has been marked a duplicate of bug 507062
synaptic assert failure: synaptic:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/887189
Title:
gnome-panel crashed with SIGABRT in __kernel_vsyscall()
To manage notifications
** Description changed:
On a Precise i386 system with ubuntu-desktop 1.245, gnome-session-
fallback 3.2.1-0ubuntu1, and gnome-panel 1:3.2.0-0ubuntu1, I had
installed gnome-session-fallback (which installed gnome-panel as a
dependency) while in a Unity 2D session, and then I had logged out
@Erasmo
Thank you for your proposed fix/workaround for this bug.
This bug does not meet the criteria for the Opinion status. From the
description, it appears to be a real bug (assuming it can be
reproduced), and no reason has been provided for it not to be. See
https://wiki.ubuntu.com/Bugs/Status
@Cristian Aravena
This crash is in nautilus, rather than file-roller. Are you sure you are
experiencing the same bug?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/795332
Title:
@Cristian Aravena
Sorry, please disregard my previous post. I was confusing this with another,
different bug. Again, my apologies.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
@Valezan
After you continue investigating the matter, it would be useful (whether or not
you ind a solution) to report it as a bug -- it probably is one. (Of course,
you might choose not to file a big, which is your prerogative -- there exists
no obligation to do so.)
--
You received this bug
*** This bug is a duplicate of bug 796076 ***
https://bugs.launchpad.net/bugs/796076
I don't dispute that this bug is a duplicate of bug 796076, but I am
posting here to address some advice from david6 which is potentially
dangerous if applied.
It is a bad idea to run graphical programs that
This also occurs in Precise (see duplicate bug 880038).
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/796076
Title:
When run as root [gksudo gedit whatever]
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/723841
Title:
file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
To manage notifications
This also affects Precise (see duplicate bug 879953).
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/878486
Title:
gsd-printer crashed with
*** This bug is a duplicate of bug 878486 ***
https://bugs.launchpad.net/bugs/878486
Now that bug 878486 is public, comparison of this bug's stack trace
indicates that it is the same bug. Since that bug has been marked
Triaged and submitted upstream (and has more people watching it, due to
*** This bug is a duplicate of bug 878486 ***
https://bugs.launchpad.net/bugs/878486
(Bug 878486 also has a more complete symbolic retrace.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
@Raphael Camus
Also, you indicated that you upgraded from Ubuntu 10.04 to Ubuntu 11.10. But a
direct upgrade from 10.04 to 11.10 is not supported. Did you upgrade from 10.04
to 10.10, and then to 11.04, and then to 11.10? Or did you upgrade using some
other manner? Or are you actually not
The central (and possibly only) element of this bug as it is described
by Raphael Camus is the absence of window borders--windows cannot be
resized, moved, or maximized/minimized. That indicates that the problem
is with the window manager. The problem occurs in GNOME Classic, which
uses metacity
@Raphael Camus
Unless you disagree with the above analysis, then assuming you still have a
system that is affected by this bug, please provide more information about the
metacity setup on the affected system by opening a Terminal window on it and
running apport-collect 877735 (without the
** Bug watch added: Red Hat Bugzilla #747318
https://bugzilla.redhat.com/show_bug.cgi?id=747318
** Also affects: gnome-settings-daemon (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=747318
Importance: Unknown
Status: Unknown
--
You received this bug notification
@Valezan
No problem. Have you filed a bug about this (different) problem that is
affecting you? (If you do so, please read
https://help.ubuntu.com/community/ReportingBugs carefully first.) I'm not sure
what package *your* bug is in, so you might want to ask and see if anybody
knows what
Thanks, that is useful information. And yes, it would still be helpful
for you to run apport-collect 877735. In addition, can you attach an
archive of your ~/.local/share/applications folder (the version with
which the problem does occur)? All this can certainly be provided
tomorrow--there is no
I reported bug 879953, which looks similar to this bug, and which was
automatically marked as a duplicate of private bug 878486. Can someone
with access to bug 878486 look and see if it is the same as this bug?
--
You received this bug notification because you are a member of Ubuntu
Desktop
*** This bug is a duplicate of bug 827414 ***
https://bugs.launchpad.net/bugs/827414
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/808918
Title:
gedit
*** This bug is a duplicate of bug 878486 ***
https://bugs.launchpad.net/bugs/878486
** Visibility changed to: Public
** Description changed:
On a fully updated Precise i386 system (obtained by replacing oneiric
with precise in sources.list, dist-upgrading, and rebooting) running on
Similar bug 808918 has been marked as a duplicate of this bug, but the
behavior is a bit different and it persists even though this bug has
been fixed (it seems reliably reproducible on a fully updated Precise
system), so I suspect that it is not really a duplicate. I have
commented in bug 808918
*** This bug is a duplicate of bug 827414 ***
https://bugs.launchpad.net/bugs/827414
I suspect that this may *not* be a duplicate of bug 827414. This just
happened with on a fully updated Precise i386 system (obtained by
replacing oneiric with precise in sources.list, dist-upgrading, and
Public bug reported:
On a fully updated Precise i386 system (obtained by replacing oneiric
with precise in sources.list, dist-upgrading, and rebooting) with gedit
3.2.1-0ubuntu1, I created a test file and opened it in gedit:
ek@Gnar:~$ echo test foo
ek@Gnar:~$ gedit foo
This behaved exactly as
** Attachment added: gksu-gedit-extra-new-document.png
https://bugs.launchpad.net/bugs/880038/+attachment/2567004/+files/gksu-gedit-extra-new-document.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
The upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=636431) has been
marked as a duplicate of upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=644011. That bug is RESOLVED with
status OBSOLETE, since it is believed not to occur on a GNOME 3 system
(developer David King said:
For technical assistance, you may want to post a question
(https://answers.launchpad.net/ubuntu/+source/nautilus/+addquestion for
questions about your camera;
https://answers.launchpad.net/ubuntu/+source/firefox/+addquestion for
questions about your web browser).
As for this bug, are you able to
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/876799
Title:
gnome-panel crashed with SIGABRT in __kernel_vsyscall()
To manage notifications
** Changed in: yelp (Ubuntu)
Status: Expired = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/446211
Title:
yelp doesn't show some line breaks in alltray man page
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/409706
Title:
gnome-help excessive CPU usage
To manage notifications about this bug go to:
** Summary changed:
- Can't load pictures from new Koday Camera to unbutu
+ Can't load pictures from new Kodak Camera to Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
*** This bug is a duplicate of bug 784519 ***
https://bugs.launchpad.net/bugs/784519
It looks like bug 784519 should have been marked back to New from
Incomplete when you provided the information that the bug did not affect
terminator. This would have prevented it expiring. I will change that
*** This bug is a duplicate of bug 784519 ***
https://bugs.launchpad.net/bugs/784519
I have read and considered in more detail, and since the answer was not
definitive, I will mark bug 784519 back to Incomplete instead,
resubscribe Pedro Villavicencio, and ask what if any additional
Also, there is someone who is interested in writing a patch for this,
though I am at this point unsure if there is enough information
available to fix the bug. (See
https://answers.launchpad.net/ubuntu/+source/gnome-
terminal/+question/173876, specifically post #4.)
--
You received this bug
Duplicate bug 865407 indicates that the original poster is/was still
interested in working on this bug. Is there any more information that
can be provided to make progress here? (Marking back from Expired to
Incomplete.)
Also, can anyone check and see if this bug occurs on Oneiric?
** Changed
@Josh Burghandy
On the affected machine, please open a Terminal window (Ctrl+Alt+T) and run
this command:
apport-collect 871133
After doing so, please verify that information was automatically attached to
this bug report and that the apport-collected tag was automatically added
(please do *not*
If it can, then in addition to searching for and reporting the bug on
the openSUSE's tracker, it would also be useful to search for and report
it against gnome-terminal upstream (on the GNOME bug tracker).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 795332 ***
https://bugs.launchpad.net/bugs/795332
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 795332
nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb()
--
You received this bug notification
I've found that this still occurs with nautilus 1:3.1.92-0ubuntu3 (see
duplicate bug 859622).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/795332
Title:
nautilus crashed with
*** This bug is a duplicate of bug 839828 ***
https://bugs.launchpad.net/bugs/839828
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/858887
Title:
*** This bug is a duplicate of bug 839828 ***
https://bugs.launchpad.net/bugs/839828
This is /var/log/dpkg.log from, which includes entries from the upgrade
operation during which this crash occurred.
** Attachment added: dpkg.log
*** This bug is a duplicate of bug 839828 ***
https://bugs.launchpad.net/bugs/839828
In case it is useful, here is the Terminal text from the upgrade
operation. It is not complete, but it should contain the relevant
entries.
** Attachment added: PartialAptTerminalLog.txt
I got this bug after an update that had not completed successfully, and
the crash occurred every time I tried launching gnome-terminal. Then I
ran sudo apt-get -f install, and now I am able to launch gnome-
terminal without problems. In the upstream bug
I am able to reproduce this problem in IRC in empathy 3.1.92-0ubuntu1 on
an Oneiric i386 system in a 3D Unity session, so no, this is not fixed.
(I have not tested with other session types, but I will do so on
request.) It occurs in an IRC channel window but not in an AIM chat
window.
I reported bug 853618, which is a duplicate of this bug and contains a
more complete stack trace. Like this bug, I do not yet know if it can be
reproduced with gnome-settings-daemon 3.1.92. (I do not know what
specific steps triggered the bug in the first place, so it would be
difficult for me to
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/853618
Title:
gnome-settings-daemon crashed with SIGSEGV in call_in_idle_cb()
To
This is no longer occurring for me, running yelp 3.0.0-0ubuntu2 on Natty
amd64. Does the suggestion to requested a fix in -backports apply only
to Lucid and Maverick? (Has this bug ever actually affected Natty, since
Natty's release?)
--
You received this bug notification because you are a
Public bug reported:
I was updating an Oneiric i386 system in a 3D Unity session from the
command-line (in gnome-terminal) with sudo apt-get dist-upgrade (and
also accessing Launchpad using Chromium for an unrelated reason, which I
doubt is relevant) when suddenly X.org terminated. I switch to
** Attachment added: .xsession-errors.old
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/828993/+attachment/2289914/+files/.xsession-errors.old
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
** Description changed:
I was updating an Oneiric i386 system in a 3D Unity session from the
command-line (in gnome-terminal) with sudo apt-get dist-upgrade (and
also accessing Launchpad using Chromium for an unrelated reason, which I
doubt is relevant) when suddenly X.org terminated. I
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/828993/+attachment/2289924/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
** Description changed:
I was updating an Oneiric i386 system in a 3D Unity session from the
command-line (in gnome-terminal) with sudo apt-get dist-upgrade (and
also accessing Launchpad using Chromium for an unrelated reason, which I
doubt is relevant) when suddenly X.org terminated. I
I have a system with Oneiric i386 installed, with yelp 3.1.2-0ubuntu1
and alltray 0.71b-1, so I tested it on that. (I doubt this problem is
machine-specific, and in any case, the machine on which I had previously
produced this problem is a VM which I have since deleted.) I was not
able to produce
Since it is very difficult for me to produce this bug by running gedit
from the Terminal (or by any means other than from unity-2d-places),
Jean-Baptiste Lallement will probably have to obtain the strace log.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Should this be set back from In Progress to Triaged?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/723841
Title:
file-roller crashed with SIGSEGV in
This may be due to a kernel problem as discussed in
https://answers.launchpad.net/ubuntu/+source/gnome-
nettool/+question/165390, but this is not a kernel bug report (it
contains no information about your kernel and is not really written as a
bug report at all, and it does not conform to the
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/819821
Title:
users-admin crashed with signal 5 in do_pre_parse_initialization()
To
I am able to reproduce this bug on Oneiric with gnome-system-tools
2.32.0-0ubuntu7 (also on an i386 system running 3D Unity, but there is
no reason to think this bug does not affect all Oneiric systems).
I mention this even though the bug has already been confirmed and marked
triaged because,
*** This bug is a duplicate of bug 789333 ***
https://bugs.launchpad.net/bugs/789333
I am not sure Apport retracing service is correct in marking this as a
duplicate of bug 789333, since bug 789333 is currently being considered
to be a GNOME3 PPA bug and this bug is not a GNOME3 PPA bug. See
Apport retracing service has marked bug 819821, which is *not* a GNOME3
PPA bug (c.f. similar bug 814060 which is also not a GNOME3 PPA bug), as
a duplicate of this bug (and removed all the useful attachments). Should
I reverse that operation and manually attach a stack trace to bug
819821? Or
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/819879
Title:
time-admin crashed with signal 5 in do_pre_parse_initialization()
To
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/819889
Title:
network-admin crashed with signal 5 in do_pre_parse_initialization()
To
*** This bug is a duplicate of bug 818990 ***
https://bugs.launchpad.net/bugs/818990
** Description changed:
Like shares-admin (bug 814060) and users-admin (bug 819821), which are
- provided by binary package gnome-system-tools, time-admin, which is
- provided by binary package
To clarify my motivation in https://bugs.launchpad.net/ubuntu/+source
/gnome-system-tools/+bug/814060/comments/6:
The original bug report here sought to report both the users-admin and
shares-admin crashes, but it characterized the executables as two
scripts, whereas in fact they are separate ELF
*** This bug is a duplicate of bug 814060 ***
https://bugs.launchpad.net/bugs/814060
** This bug is no longer a duplicate of bug 789333
users-admin crashes on start because of mixed GTK2 and 3 symbols
** This bug has been marked a duplicate of bug 814060
shares-admin crashed with signal
I'm going to take that as indicating that it was not a mistake to have
considered the related shares-admin and users-admin crashes as the same
bug (even though the crashes are not in the same binary, as the wording
in this bug report had implied). So I'll mark bug 819821 as a duplicate
of this
@iLugo
I cannot speak for Martin Pitt, nor for Canonical, but I believe I can explain
why this bug is (and should be) of Medium rather than High importance.
Importance for bugs in Ubuntu is assigned according to the priority in
the Ubuntu project as a whole, and the effect of the bugs on Ubuntu
@Ryan
Are you still experiencing this problem? If not, you can mark this bug as
Invalid (or just leave it Expired). If so, can you provide the information
requested in
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/775590/comments/11?
--
You received this bug notification because you are
Public bug reported:
In a unity-2d session on an Oneiric i386 system with gedit
3.1.1-0ubuntu4 and unity-2d/unity-2d-places 3.8.10-0ubuntu2, running
gedit from unity-2d-places (by clicking the home button, typing in
gedit, and clicking Text Editor in the search results; or by pressing
Alt+F2,
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/808918
Title:
gedit usually sleeps indefinitely when launched by unity-2d-places
To manage notifications about this bug go to:
** Description changed:
In a unity-2d session on an Oneiric i386 system with gedit
3.1.1-0ubuntu4 and unity-2d/unity-2d-places 3.8.10-0ubuntu2, running
gedit from unity-2d-places (by clicking the home button, typing in
gedit, and clicking Text Editor in the search results; or by pressing
No, I have not experienced this anytime recently.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/795382
Title:
gnome-power-manager crashed with SIGSEGV in
@alainpannetier
You have misunderstood. Non-administrators cannot create user accounts (nor can
they perform other administrative tasks). Being root is not the same thing as
being an administrator. And the security model you are misunderstanding does
not apply to Linux-based operating systems
** Description changed:
In a 3D Unity session on the Oneiric i386 20110629 daily-live, I opened
the Network control panel in gnome-control-center 1:3.0.2-1ubuntu5 by
using Unity to search for network and clicking on the search result
called Network. I configured a network connection with
This bug has a good stack trace, is indicated to affect 18 people, and
has 32 duplicates (one of which, bug 757653, is indicated to affect 10
people, which might or might not overlap with the 18 people here). The
bug has been extensively discussed and the circumstance under which it
occurs are at
*** This bug is a duplicate of bug 607999 ***
https://bugs.launchpad.net/bugs/607999
In case anyone is wondering, the reason this bug is a duplicate of bug
607999 is because this bug was re-reported as bug 797712, and bug 797712
has just been found to be a duplicate of bug 607999. In the
This bug is still happening with Oneiric i386 (see duplicate bug
797712)--this happens every time I start a Lubuntu Desktop session on a
Lubuntu Oneiric system. Also tagging powerpc (from duplicate bug
608486).
@sam tygier
You can manually (re)enable apport on a stable system. See
No, because you have not posted the results of performing the testing
described in the second-to-last paragraph of
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/796088/comments/1.
(You appear simply to have run apport-collect three more times, which
doesn't add any more information that
** Visibility changed to: Public
** Description changed:
I updated and rebooted an Oneiric i386 system (gnome-control-center
- 1:3.0.2-1ubuntu4, deja-dup 19.2.1-0ubuntu1), and after a short time, I
- was asked if I wanted to configure backup settings. I clicked yes
- (actually I don't remember
*** This bug is a duplicate of bug 788710 ***
https://bugs.launchpad.net/bugs/788710
Manual inspection of the original stack trace in this report reveals
that this is the same as bug 788710. (Comparing to the stack trace in
duplicate bug 796497 is most illustrative.)
** This bug has been
This still occurs on the same machine running brasero 2.32.1-0ubuntu2 on
Natty amd64. The error message is exactly the same. This is with the
same hardware (including the same internal burner) and media type as
before (the DVD+R is from the same spindle). The log of the new burn
attempt is
ek@Apok:~$ uname -a
Linux Apok 2.6.38-10-generic #44-Ubuntu SMP Thu Jun 2 21:32:22 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux
** Attachment added: lspci.natty.txt
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178658/+files/lspci.natty.txt
--
You received this bug
** Attachment added: lshw.natty.txt
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178659/+files/lshw.natty.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
** Attachment added: lsmod.natty.txt
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178660/+files/lsmod.natty.txt
** Tags added: natty
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
In case it's relevant, similar (quite possibly identical) bug 746958
does still occur on Natty.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/700975
Title:
Power calibration area
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/800065
Title:
gnome-settings-daemon crashed with SIGSEGV
To manage notifications
*** This bug is a duplicate of bug 800065 ***
https://bugs.launchpad.net/bugs/800065
** This bug has been marked a duplicate of bug 800065
gnome-settings-daemon crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
*** This bug is a duplicate of bug 800065 ***
https://bugs.launchpad.net/bugs/800065
** This bug is no longer a duplicate of bug 798722
gnome-settings-daemon crashed with SIGSEGV
** This bug has been marked a duplicate of bug 800065
gnome-settings-daemon crashed with SIGSEGV
--
You
1 - 100 of 313 matches
Mail list logo
