*** This bug is a duplicate of bug 1378627 ***
https://bugs.launchpad.net/bugs/1378627
Public bug reported:
chromium-browser 37.0.2062.94-0ubuntu1~pkg1065 on Lubuntu Utopic amd64
sometimes crashes on launch. This happens at least daily, but somewhat
less than half the time the browser is
Public bug reported:
Xorg (xserver-xorg 1:7.7+1ubuntu8) crashed on an Ubuntu MATE (Utopic)
amd64 system. Apport informed me of the crash when I logged in. I had
just logged out and back in.
At the time I was using this system to verify the correct behavior of
pam_env.so against another system on
Public bug reported:
In chromium-browser 36.0.1985.125-0ubuntu2 on my Utopic i386 system
(fully up to date as of this report), some pages always cause the
browser to crash.
chrome://settings is one of these pages (which makes effective browser
usage difficult).
ProblemType: Crash
Public bug reported:
On a Saucy i386 system, Apport informed me Chromium had crashed. Flash
had crashed recently, so this may be a common Flash crash. But I'm not
sure yet, so I'm submitting this bug report. Unfortunately I don't have
much information beyond what's provided in the Apport-attached
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:
chromium-browser 31.0.1650.63-0ubuntu0.13.10.1~20131204.1 crashed on
Lubuntu Saucy i386 while running in the background. I was not
interacting directly with Chromium at or within several minutes of the
time of the crash. This might be bug 926143.
ProblemType: Crash
*** This bug is a duplicate of bug 1222782 ***
https://bugs.launchpad.net/bugs/1222782
Public bug reported:
Transmission crashed on a Lubuntu Saucy i386 system (transmission
/transmission-gtk 2.82-0ubuntu1). I am unsure of the circumstances
surrounding the crash. I was seeding a number of
Public bug reported:
Xorg crashed on Saucy amd64. Unfortunately I am unsure of the
circumstances surrounding this crash; if it were not for Apport, I would
probably not be aware of it. This suggests the crash may have occurred
during at login or logout.
ProblemType: Crash
DistroRelease: Ubuntu
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:
On a Lubuntu i386 system running Transmission with the GTK+ frontend,
transmission crashed while seeding some torrents. There did not appear
to be any user interaction that triggered this crash.
This somewhat resembles bug 453428. To a lesser extent this resembles
bug 630679
As BlueCase says, this will likely occur again and again from time to
time as services have similar problems, and this is fixable in gnome-
cocntrol-center-signon. Probably the best thing to do would be for
someone who was able to reproduce this before it was fixed on Facebook's
side to file a new
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
Public bug reported:
I logged into a Unity session on a Quantal i386 system with old hardware
--an Nvidia GeForce 5200 graphics card. The screen flickered yellowish,
then went to black. There was no visible interface. I restarted lightdm
to get back to the graphical login screen. Soon after, I
** Description changed:
- I logged into a Unity session on a Quantal i386 system with old hardware
- --an Nvidia GeForce 5200 graphics card. The screen flickered yellowish,
- then went to black. There was no visible interface. I restarted lightdm
- to get back to the graphical login screen. Soon
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1078993
Title:
[System Product Name, ATI RS880 HDMI, audio
Are you logged in as Guest? There are a lot of Permission denied
errors in the information sent by Apport, sometimes even when trying to
access information that's available even to limited users (but not
necessarily available to Guest). And the error from when Apport tried to
run fuser with pkexec
*** 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
@Charlie Kravetz
It looks like the recent change from Triaged to Fix Released was in error.
Since only triagers/developers can set Triaged status, it looks like it falls
on you to fix this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
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 Desktop
Packages, 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
@Gunnar Hjalmarsson
Unlike this bug, bug 659060 is a crash and resembles bug 507062. What does that
have to do with this bug?
--
You received this bug notification because you are a member of Desktop
** Attachment added: history.log
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/888209/+attachment/2591026/+files/history.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
I've just reported bug 888209. I think it is the same bug as this, but I
am not sure, because there are a couple of other steps in the stack
trace.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
The symbolic retrace makes this look like it is a duplicate of bug
869453, as originally suspected. However, there are some extra steps in
the stack trace, so I am not completely sure.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@Gunnar Hjalmarsson
It is definitely meaningful to distinguish between hanging and crashing. It is
always meaningful, because in a hang (construed in the broadest sense of the
term), a program continues running indefinitely without doing anything, whereas
in a crash, it terminates abnormally.
*** 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:
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
Why is this bug believed to be a duplicate of bug 507062? This looks
like a hang or deadlock, whereas bug 507062 is a crash.
--
You received this bug notification because you are a member of Desktop
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/887189
Title:
gnome-panel crashed with SIGABRT in __kernel_vsyscall()
Status in “gnome-panel”
** 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
Can you provide detailed steps for reproducing this bug (as you had done
in possibly related bug 882740), and also apport-collect this bug (you
should only need to run apport-collect 882748 once)? Once all this
information is added, you can change this bug's status back from
Incomplete to New.
**
This might turn out not to be a bug, but let's keep this open (but
Incomplete, pending the investigation going on in
https://answers.launchpad.net/ubuntu/+source/firefox/+question/155919).
Please open a Terminal window and run apport-collect 777177 to
automatically attach important information to
Sorry, I don't how how I missed that.
Since you tested for that at the outset, why did you reopen this bug?
This bug was specifically about all audio not working in Firefox, not
just Flash audio not working.
Unless you have some reason to think there is a particularly strong
similarity between
I don't want to get into an argument about who should apologize,
especially since the matter is quite trivial. But I still think it's me.
;-) Reopening this bug (you did that), while probably wrong, resulted in
progress on your issue (and was easily remedied). Failing to read a
significant part of
@Andrew Golding
Is this behavior similar to what you saw at
https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/171131?
Does this problem occur in more than one session type? If it is happening with
Ubuntu as the session type (selected from the gear menu on the graphical
Marking Fix Released, since this bug report was never actually closed
before, but the problem is reported
(https://bugs.launchpad.net/ubuntu/+source/software-
center/+bug/852378/comments/3) to be fixed in Oneiric.
** Changed in: software-center (Ubuntu)
Status: New = Fix Released
--
You
The attached logs indicate that this was a crash in libreoffice. Please
enable Apport crash reporting
(https://wiki.ubuntu.com/Apport#How_to_enable_apport), then reproduce
the problem (i.e., open the file again to trigger the crash). Apport
will then automatically gather information and give you
@svenmeir
In addition to what you have described, do you get video but not audio with
http://camendesign.com/code/video_for_everybody/test.html? (See bug 858466.) If
so, then you probably have the same problem setiamon was having, and this bug
(bug 874834, not bug 858466 which is actually
@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
apport-collection does not extract data from the running process (which
is unlike invoking ubuntu-bug with the PID, which does). Therefore, so
long as you are still running the same version of banshee and you have
not changed its configuration or related configuration on your system,
it should
** Also affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: deja-dup (Ubuntu)
Status: New = Incomplete
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Please run apport-collect 882740 on the affected system. This is
important because, in duplicate bug 595600, responders were unable to
reproduce the problem, even with the same banshee version and Ubuntu
release. It seems likely that this might happen here as well (since this
is probably the same
@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 Desktop
Packages, 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 Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/795332
Is this bug produced precisely as described in bug 595600? If so, then
you should mark this bug a duplicate of bug 595600, after changing bug
595600's status from Invalid to New. Otherwise, you should either
comment in that bug (if this bug is produced very differently, such that
they are not
@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 is not a bug in Firefox and is probably not a bug at all. If there
is a bug causing the problem, it will be more useful to file a new
report. Therefore, the automatically set Invalid status was correct; I
am restoring it. If you are convinced I am mistaken, then please feel
free to change the
This also occurs in Precise (see duplicate bug 880038).
** Tags added: precise
--
You received this bug notification because you are a member of Desktop
Packages, 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 Desktop
Packages, 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()
Status in File Roller:
This also affects Precise (see duplicate bug 879953).
** Tags added: precise
--
You received this bug notification because you are a member of Desktop
Packages, 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 Desktop
Packages, 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
@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
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
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 Desktop
Packages,
*** 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 Desktop
Packages, 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
Public bug reported:
On a fully updated Precise i386 system (obtained by replacing oneiric
with precise in sources.list, dist-upgrading, and rebooting) in a Unity
2D session with a screen resolution of 800x600, firefox
8.0~b4+build1-0ubuntu1 displayed a security warning message box that was
too
** Attachment added: firefox-8-security-warning.png
https://bugs.launchpad.net/bugs/879959/+attachment/2566506/+files/firefox-8-security-warning.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
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 Desktop
Packages, 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
** Changed in: yelp (Ubuntu)
Status: Expired = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, 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 Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/858466
Title:
Ubuntu 11.10 Audio Problems with Browsers.
Status in “firefox” package in Ubuntu:
Confirmed
There are some complexities in the way this bug is presenting, so let's
get a greater depth and breadth of information about your experiences.
@Michel Steinbusch
What package versions of each browser do you have installed? Do you have sound
on the web via mechanisms other than Flash, for example
Since you've eliminated what was apparently an necessary condition for
the problem and, in your present configuration, can no longer perform
testing or furnish information necessary to make this bug report ready
for a developer to work on, and there is no one else who has indicated
they are
@Brian
Is the description in this bug It takes 20 seconds to finish loading. It takes
a couple of seconds... your experience, or is it taken from
https://answers.launchpad.net/ubuntu/+source/software-center/+question/174730?
Those appear to be the words of Charles Pergiel. If this is your
** Tags added: oneiric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/409706
Title:
gnome-help excessive CPU usage
Status in “yelp” package in Ubuntu:
Confirmed
Bug description:
@Roland
Can you post a link to the relevant page on AskUbuntu.com, in case (either now
or at some point in the future) there are more useful details or discussion
there?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in
** 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 Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/872074
*** 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
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 Desktop
Packages, which
*** This bug is a duplicate of bug 802271 ***
https://bugs.launchpad.net/bugs/802271
@Richard Stellingwerff
This bug is a duplicate of bug 802271, so you should post there instead. Your
post here will likely be unseen, and ignored to the extent to which it is seen.
It is strange that you
(1) I'm attaching the output from pastebin.com so that it remains
accessible, and so that it is easier to work with.
(2) I'm changing this back from Confirmed to New since it looks like
that change was by mistake; specifically, that it involved an incorrect
understanding of what the Confirmed
*** 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 Desktop
Packages, 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 Desktop
Packages, 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.
** Attachment added: stalled-banshee-importing.png
https://bugs.launchpad.net/bugs/859120/+attachment/2459539/+files/stalled-banshee-importing.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
Public bug reported:
I attempted to import a very large music library (over 55,000 filesystem
entries, including folders, consisting mostly of .mp3 and .flac files
with some other formats, and taking up about 470 GiB, mounted via
smbmount via a remote Samba share) into banshee 2.2.0-1ubuntu2 on
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 Desktop
Packages, 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()
Status in
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
1 - 100 of 102 matches
Mail list logo
