** Changed in: fretsonfire (Ubuntu)
Importance: Undecided = Medium
** Changed in: fretsonfire (Ubuntu)
Status: Confirmed = Triaged
--
frets on fire on jaunty crashes when i try to launch it
https://bugs.launchpad.net/bugs/357076
You received this bug notification because you are a
https://sourceforge.net/tracker/?func=detailaid=2782026group_id=182199atid=900254
** Bug watch added: SourceForge.net Tracker #2782026
http://sourceforge.net/support/tracker.php?aid=2782026
** Changed in: fretsonfire (Ubuntu)
Status: Confirmed = Triaged
--
DeprecationWarning with
Fix released upstream, should be included with 1.1.8.
--
deluge crashed with TypeError in _on_get_torrent_status()
https://bugs.launchpad.net/bugs/333256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I notice there hasn't been a duplicate report in a while. Does the
problem still occur with Jaunty release?
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Triaged = Incomplete
--
gnome-settings-daemon crashed with signal 5 in xkl_process_error()
In the absence of a specific test case, I tested opening pdf files and
performed a few standard actions.
** Tags added: verification-done
** Tags removed: verification-needed
--
2.26.1 stable update
https://bugs.launchpad.net/bugs/365072
You received this bug notification because you are a
NOT fixed with gnome-utils 2.26.0-0ubuntu1 in Jaunty.
** Description changed:
Binary package hint: baobab
OS: Ubuntu Hardy (8.04)
Package version: baobab 2.20.0.1-1ubuntu5
Mirror: Positive Internet
After telling baobab (Disk Usage Analyser - DUA) to scan a remote
partition, the
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
Tested first with gnome-applets 2.26.0-0ubuntu4, and confirmed the crash
still occurred.
Upgraded to gnome-applets 2.26.1-0ubuntu1 from jaunty-proposed, reloaded
the applet, and choosing Play DVD correctly opened totem and started
playing my DVD.
** Tags added: verification-done
** Tags removed:
Closing this bug, it appears the issue has gone.
** Changed in: libcanberra (Ubuntu)
Status: Incomplete = Invalid
--
canberra-gtk-play crashed with SIGSEGV in pa_operation_unref()
https://bugs.launchpad.net/bugs/275233
You received this bug notification because you are a member of Ubuntu
Did you follow the steps to reproduce that I added to the bug
description? The key is you need to first sort the Usage column
(ascending, arrow down), before refreshing / rescanning. It does not
depend on what you are scanning, I reproduced it with Scan Filesystem.
Really, it shouldn't be
Thanks for the new backtrace, but this looks like a different crash,
which I think needs libc6-i686-dbgsym for that (see the lines saying No
symbol table info available). Did this crash occur with a different
action?
Upstream has a new version 1.50, so it's probably worth testing with
this to see
** Bug watch added: GNOME Bug Tracker #579137
http://bugzilla.gnome.org/show_bug.cgi?id=579137
** Also affects: rhythmbox via
http://bugzilla.gnome.org/show_bug.cgi?id=579137
Importance: Unknown
Status: Unknown
** Changed in: rhythmbox (Ubuntu)
Status: New = Triaged
--
*** This bug is a duplicate of bug 349146 ***
https://bugs.launchpad.net/bugs/349146
** This bug has been marked a duplicate of bug 349146
Logout icon looks like shutdown
--
Logout icon looks like power off (shutdown)
https://bugs.launchpad.net/bugs/364512
You received this bug
Does the problem only occur with that particular amsn icon, or with
others as well? What does that icon represent, do you have some steps on
how to produce it? The icons used when opening amsn and being online are
different for me, and the problem does not occur with them. Please
ensure that you
The link worked fine for me within virtualbox. Note that it's version
specific, so that file only applies when using Intrepid.
I think the best solution would be to have a package such as virtualbox-
ose-additions (that was Suggests in virtualbox-ose), and when running
the program and the iso is
Marking as a Compiz issue since it appears to work fine with standard
Metacity. Confirming due to multiple users experiencing this.
It would be good if someone could test this with Metacity composite too.
I'm still not sure why I have different amsn icons to those in the
attached images.
**
I received this on shutdown last night. Confirming based on huge number
of duplicates.
** Visibility changed to: Public
** Changed in: usplash (Ubuntu)
Importance: Undecided = Medium
** Changed in: usplash (Ubuntu)
Status: New = Confirmed
--
usplash crashed with SIGSEGV in
Thanks, I managed to get a backtrace with break gdk_x_error; doing the
renice on user and root processes produces different looking backtraces
so I have attached both. Although strangely, I couldn't easily trigger
the issue at first. Now it's back to 100% reproduction again though.
** Attachment
** Attachment added: gdb-g-s-m.txt (root)
http://launchpadlibrarian.net/25787513/gdb-g-s-m.txt
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: rhythmbox
I tried manually sorting some tracks from the bottom of a large static
playlist, but as soon as I clicked and dragged them, the playlist
instantly scrolled near the top. This happens for any track/s in a large
(300+) static playlist that aren't
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25788708/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/25788709/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/25788710/ProcStatus.txt
** Tags added:
As I mentioned in the description, and as with bug 206583, it doesn't
seem to crash, but simply close. Apport doesn't catch anything, and
reproducing the problem in gdb doesn't produce any backtrace.
However, I expect the problem to be easily reproducible for anyone
running up-to-date Jaunty.
--
*** This bug is a duplicate of bug 206583 ***
https://bugs.launchpad.net/bugs/206583
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 206583, so it is being marked as such. Please look
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25718118/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/25718119/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/25718120/ProcStatus.txt
--
Public bug reported:
Binary package hint: gnome-system-monitor
Trying to Change Priority for any process of any owner causes g-s-m to
close with the following error shown in the terminal:
The program 'gnome-system-monitor' received an X Window System error.
This probably reflects a bug in the
Thanks for your comment Psy[H[]. I can confirm the issue you're
experiencing in the latest Jaunty, but it appears to be different in
several ways, and did not occur previously in Jaunty. I have opened a
new bug for this issue at bug #363558.
--
System Monitor crashes when lowering nice value of
This bug has been closed upstream as incomplete, so it is being closed
here as well. Please reopen either bug if you can provide the requested
information.
** Changed in: transmission (Ubuntu)
Status: Triaged = Invalid
--
transmission crashed with SIGSEGV in g_main_context_dispatch()
Could those experiencing the problem please respond to the comment at
the upstream bug.
I can't reproduce this. Is there any more information available on this
crash? Does it happen every time for the OP, or was this a one-off?
--
transmission crashed with signal 7 in bsearch()
Thanks for your report. We are closing this report as Ubuntu Jaunty
already has transmission 1.51. Please see
https://wiki.ubuntu.com/TimeBasedReleases and
https://wiki.ubuntu.com/StableReleaseUpdates for more information. The
potential DoS vulnerability is not necessarily a security issue, but
if
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
** Changed in: soundconverter (Ubuntu)
Importance: Undecided = Medium
** Changed in: soundconverter (Ubuntu)
Status: New = Triaged
--
[intrepid] soundconverter always freezes after adding a file
https://bugs.launchpad.net/bugs/263889
You received this bug notification because you are
** Summary changed:
- Please upgrade to soundconverter 1.4.2
+ Please upgrade to soundconverter 1.4.3
** Description changed:
- Binary package hint: soundconverter
-
- 2009-01-26 Gautier Portet kassoulet gmail com
-
- * src/soundconverter.py, data/soundconverter.glade:
- Add a
** Bug watch added: Debian Bug tracker #524455
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524455
** Also affects: soundconverter (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524455
Importance: Unknown
Status: Unknown
--
Please upgrade to soundconverter
Thanks for testing, confirming based on the information provided.
** Changed in: compiz (Ubuntu)
Importance: Undecided = Low
** Changed in: compiz (Ubuntu)
Status: Incomplete = Confirmed
--
Video corruption with Visual Effects set to Normal
https://bugs.launchpad.net/bugs/352344
You
Thanks for your comment. Is the problem reproducible every time? Does it
occur when using Metacity instead of Compiz? Does it occur when using
the default Human theme? What graphics driver are you using? Thanks in
advance.
** Changed in: amsn (Ubuntu)
Status: Fix Released = Incomplete
--
It looks like both changes were first included with wireshark
1.0.2-1ubuntu1. The gksu fix is important and is bug 209084. I'm not
sure about the README.source change, but it's already being applied to
wireshark 1.0.6-1ubuntu1, so to remove this from the debdiff would
actually be an additional
Proper merge patch this time, sourced from merges.ubuntu.com, includes
Ubuntu changelog entries.
** Attachment added: wireshark_1.0.7-1ubuntu1.patch
http://launchpadlibrarian.net/25530052/wireshark_1.0.7-1ubuntu1.patch
--
Please merge wireshark 1.0.7-1 (universe) from Debian unstable (main)
** Attachment added: wireshark_1.0.7-1ubuntu1.patch
http://launchpadlibrarian.net/25530080/wireshark_1.0.7-1ubuntu1.patch
** Attachment removed: wireshark_1.0.7-1ubuntu1.patch
http://launchpadlibrarian.net/25530052/wireshark_1.0.7-1ubuntu1.patch
--
Please merge wireshark 1.0.7-1
** Changed in: wireshark (Ubuntu)
Status: In Progress = Fix Committed
--
Please merge wireshark 1.0.7-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/360661
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Debian Bug tracker #524360
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524360
** Also affects: wireshark (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524360
Importance: Unknown
Status: Unknown
--
debian/control must Recommends menu to
Merge debdiff attached.
** Attachment added: wireshark_1.0.7-1ubuntu1.debdiff
http://launchpadlibrarian.net/25489648/wireshark_1.0.7-1ubuntu1.debdiff
--
Please merge wireshark 1.0.7-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/360661
You received this bug
I would expect it to be included with the next major release, 1.60. A
wishlist feature such as this isn't appropriate for a point release.
--
show thumbnails next to torrents
https://bugs.launchpad.net/bugs/183473
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Summary changed:
- new upstream version - Wireshark 1.0.7
+ Please merge wireshark 1.0.7-1 (universe) from Debian unstable (main)
** Description changed:
Binary package hint: wireshark
this version fixes a few security issues, including an arbitrary code
execution and denial of
Subscribed motu-release based on discussion on irc.
geser directhex: 66 files changed, 14757 insertions(+), 1619 deletions(-)
based on the debdiff of the Debian and Ubuntu packages
there are many small changes and one big: epan/enterprise-numbers
|10933
The problem still exists with Jaunty, even when using S99darkstat.
Starting manually still works, which is what I'm doing each session. I
tested with Debian Lenny and Darkstat works fine there, it runs on
startup like it should.
--
darkstat does not start on boot
Thanks for your backtrace. Unfortunately it is missing debug symbols.
You will need to install libglib2.0-0-dbg and libgtk2.0-0-dbg (or
-dbgsym variants) before obtaining the backtrace. Thanks again for your
help with this bug!
--
pidgin crashed with SIGSEGV upon clicking on Facebook messages
** Changed in: deluge (Ubuntu)
Status: New = Triaged
--
deluge crashed with TypeError in _on_get_torrent_status()
https://bugs.launchpad.net/bugs/333256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: Deluge bug tracker #886
http://dev.deluge-torrent.org/ticket/886
** Also affects: deluge via
http://dev.deluge-torrent.org/ticket/886
Importance: Unknown
Status: Unknown
--
deluge crashed with TypeError in _on_get_torrent_status()
** Visibility changed to: Public
--
ekiga crashed with SIGSEGV in malloc_consolidate()
https://bugs.launchpad.net/bugs/355066
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
** Visibility changed to: Public
--
xchat-gnome crashed with SIGSEGV in IA__g_main_context_dispatch()
https://bugs.launchpad.net/bugs/359895
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: GNOME Bug Tracker #578743
http://bugzilla.gnome.org/show_bug.cgi?id=578743
** Also affects: xchat-gnome via
http://bugzilla.gnome.org/show_bug.cgi?id=578743
Importance: Unknown
Status: Unknown
** Changed in: xchat-gnome (Ubuntu)
Status: New = Triaged
I was getting this in Jaunty with SuperTuxKart and Nexuiz when using
Compiz. Metacity did not have the same problem. Disabling the
screensaver, as mentioned in the previous comment, seems to have fixed
the problem when using Compiz.
** Changed in: compiz (Ubuntu)
Status: Incomplete =
** Summary changed:
- [gutsy] sdl games leave fullscreen mode without obvious reason
+ sdl games leave fullscreen mode
--
sdl games leave fullscreen mode
https://bugs.launchpad.net/bugs/155263
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
There are a large number of duplicates, but none that I can see that
have reported the problem with Jaunty. Can anyone reproduce this issue
with Jaunty? It looks to me like the problem has been fixed.
** Attachment removed: CoreDump(2).gz
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
**
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
There's no need to attach .crash files, the reporter has already
submitted it with apport.
** Attachment removed: amd64 jaunty beta crash
http://launchpadlibrarian.net/25291681/_usr_bin_olive-gtk.1000.crash
** Attachment removed: _usr_bin_olive-gtk.1000.crash
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
**
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
** Changed
Works for me with Wireshark 1.0.6 in Jaunty. Could you please test with
Jaunty to see if the problem has been resolved for you? Thanks.
** Changed in: wireshark (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: wireshark
Status: New = Incomplete
--
Open pdump file dialog not
Fixed as of 1.0.2-2.
** Changed in: wireshark (Ubuntu)
Importance: Undecided = Low
** Changed in: wireshark (Ubuntu)
Status: Confirmed = Fix Released
** Bug watch added: Debian Bug tracker #490434
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490434
** Also affects: wireshark
** Changed in: wireshark (Ubuntu)
Importance: Undecided = Wishlist
--
randpkt tool not present in wireshark install
https://bugs.launchpad.net/bugs/222715
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: wireshark (Ubuntu)
Importance: Undecided = Wishlist
--
[WISH] Open action from filemanager
https://bugs.launchpad.net/bugs/280706
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I cannot reproduce this crash with Wireshark 1.0.6 on Ubuntu Jaunty.
Could you please test if the issue still occurs for you with this
release? Thanks in advance.
** Changed in: wireshark (Ubuntu)
Importance: Undecided = Medium
** Changed in: wireshark (Ubuntu)
Status: New = Incomplete
This bug report is being closed due to your comment regarding this being
fixed with an update. For future reference you can manage the status of
your own bugs by clicking on the current status in the yellow line and
then choosing a new status in the revealed drop down box. You can learn
more about
Wireshark needs to be run as root in order to be able to read the
packets; this is simply not possible when run as a user without these
privileges. This behaviour is known and intentional, which is why the
option to run as root is there. Closing for this reason. Thanks for your
report.
** Changed
Thanks for your report. The any interface is there for me. Is this
still a problem with up-to-date Jaunty and Wireshark 1.0.6-1ubuntu1?
** Changed in: wireshark (Ubuntu)
Status: New = Incomplete
--
Virtual capture interface any is missing
https://bugs.launchpad.net/bugs/314041
You
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Have you had a chance to reproduce the issue?
--
deluge crashed with SIGSEGV in g_type_check_instance_cast()
https://bugs.launchpad.net/bugs/202396
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thanks for your report. Does the problem still occur with the latest
version of Deluge, available in Jaunty?
** Changed in: deluge-torrent (Ubuntu)
Status: New = Incomplete
--
deluge forgets settings after exit
https://bugs.launchpad.net/bugs/355904
You received this bug notification
** Package changed: deluge-torrent (Ubuntu) = deluge (Ubuntu)
--
deluge stops checking torrents after choosing add new torrents to top of the
queue option
https://bugs.launchpad.net/bugs/358531
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Visibility changed to: Public
--
deluge crashed with SIGSEGV in PyObject_SetAttr()
https://bugs.launchpad.net/bugs/347965
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
** Package changed: deluge-torrent (Ubuntu) = deluge (Ubuntu)
** Changed in: deluge (Ubuntu)
Importance: Undecided = Low
--
GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size !=
GTK_ICON_SIZE_INVALID' failed
https://bugs.launchpad.net/bugs/343759
You received this bug notification
** Visibility changed to: Public
--
deluged crashed with SIGSEGV in PyEval_EvalFrameEx()
https://bugs.launchpad.net/bugs/358396
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
** Visibility changed to: Public
--
deluge crashed with SIGSEGV in g_markup_escape_text()
https://bugs.launchpad.net/bugs/359168
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
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
deluge crashed with NoCoreError in call()
https://bugs.launchpad.net/bugs/343474
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
deluged crashed with AttributeError in _on_new_release_check()
https://bugs.launchpad.net/bugs/346692
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
deluged crashed with KeyError in on_alert_tracker_error()
https://bugs.launchpad.net/bugs/349548
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
601 - 700 of 2525 matches
Mail list logo
