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
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
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
** Visibility changed to: Public
--
pidgin crashed with SIGSEGV in _purple_connection_destroy()
https://bugs.launchpad.net/bugs/358043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We are significantly past FeatureFreeze[1], and about to hit
FinalFreeze[2]. As I mentioned before, we can look at backporting for
Jaunty once Debian releases a package. In addition, anyone can put this
in a PPA.
[1] https://wiki.ubuntu.com/FeatureFreeze
[2] https://wiki.ubuntu.com/FinalFreeze
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
** Summary changed:
- qtstalker version bump needed
+ Please upgrade to qtstalker 0.36
** Description changed:
- Binary package hint: qtstalker
+ qtstalker 0.32 is ancient (2005-06-05). Please upgrade to the latest
+ stable version, qtstalker 0.36.
- Hi,
-
- the current official stable
As we are just a couple of days from Jaunty FinalFreeze, it's best to
wait for a sync in the Karmic cycle. We can look at backporting to
Jaunty then.
** Bug watch added: Debian Bug tracker #522514
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522514
** Also affects: nexuiz (Debian) via
** Visibility changed to: Public
** Changed in: gwibber (Ubuntu)
Status: New = Triaged
--
gwibber crashed with SIGSEGV
https://bugs.launchpad.net/bugs/345704
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
With the upstream release of nexuiz 2.5, this issue may soon become
relevant to all Ubuntu releases.
** Changed in: nexuiz (Ubuntu)
Importance: Undecided = Low
--
Nexuiz demands a user to update to a new version
https://bugs.launchpad.net/bugs/277748
You received this bug notification
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
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
vncserver was removed during hardy development, so it is not present in
the release version. The reason was dead upstream, superseded by vnc4.
--
vnc4server uses wrong font path
https://bugs.launchpad.net/bugs/3593
You received this bug notification because you are a member of Ubuntu
Bugs, which
No comment received about In Progress status, setting to Triaged
instead.
** Changed in: system-config-lvm (Ubuntu)
Status: In Progress = Triaged
--
system-config-lvm crashes on startup
https://bugs.launchpad.net/bugs/290045
You received this bug notification because you are a member of
Thanks for your report. Does the problem also occur when using metacity
(desktop effects = none), or only with compiz? If it is a compiz issue
only, can you try and isolate which plugin is causing the issue? You can
do this using compizconfig-settings-manager.
** Changed in: compiz (Ubuntu)
** Summary changed:
- please upgrade hardinfo to ver 0.5
+ Please merge hardinfo 0.5c-1 (universe) from Debian unstable (main)
** Description changed:
- Binary package hint: hardinfo
+ hardinfo (0.5c-1) unstable; urgency=low
- there is a new version out please upgrade the one in the repos'
+
Setting this back to Incomplete status, as a backtrace has been
requested but not yet provided. Again:
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
(as an attachment) to the bug report. This will greatly help
Do other users still experience this issue with up-to-date Jaunty?
** Changed in: compizconfig-settings-manager (Ubuntu)
Status: Confirmed = Incomplete
--
CompizConfig Settings Manager crashed on first use.
https://bugs.launchpad.net/bugs/128446
You received this bug notification because
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
** Summary changed:
- Please merge deluge 1.1.4+dfsg-2 from Debian unstable (main)
+ Please merge deluge 1.1.5+dfsg-1 from Debian unstable (main)
** Description changed:
- Binary package hint: deluge
+ Deluge 1.1.5 - (16 March 2009)
+ Core
+
+ * Fix config file saving when no current
Fortunately or unfortunately, depending on how you look at it, there is
a new Deluge bugfix release barely a week after the previous one. Please
merge deluge 1.1.5+dfsg-1.
Thanks for your work Andrew.
** Changed in: deluge (Ubuntu)
Status: Confirmed = New
--
Please merge deluge
Thanks for your backtrace. Unfortunately it is missing debug symbols,
and is not of the latest version. Audacity 1.3.7-2 is available in
Jaunty, the development version Ubuntu. You should be able to reproduce
this problem with either a normal Jaunty installation, or using a Jaunty
LiveCD.
Please
If it wasn't a Compiz bug then it shouldn't be marked as fixed against
that package. Marking invalid.
** Changed in: compiz (Ubuntu)
Status: Fix Released = Invalid
--
Compiz makes pinentry stay in background
https://bugs.launchpad.net/bugs/309622
You received this bug notification
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
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
Thomas, what output do you get when you run it from a terminal? Is there
a relevant .crash file in /var/crash ?
--
k3dsurf doesn't start
https://bugs.launchpad.net/bugs/295140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If someone can verify the fix in 0.36.1, it would be worth getting a
Debian sync for Jaunty (FFe required).
--
gdesklets does not start amd64
https://bugs.launchpad.net/bugs/83922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thanks for the information Thomas. .crash files should be submitted with
apport rather than attached to existing reports, so I have removed it
from this report.
Please follow these instructions to have apport report a new bug about
your crash that can be dealt with by the automatic retracer.
If
Thanks for that. You're right, it does look like the same issue. I have
attached the stacktrace here and marked the report as triaged since it
looks complete.
** Attachment added: Stacktrace.txt (retraced)
http://launchpadlibrarian.net/23779173/Stacktrace.txt
** Changed in: k3dsurf (Ubuntu)
** Attachment removed: /var/crash crash report
http://launchpadlibrarian.net/23774095/_usr_bin_k3dsurf.1000.crash
--
k3dsurf doesn't start
https://bugs.launchpad.net/bugs/295140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
No more me toos thanks, we know this problem exists. Please only
comment if you are providing new useful information about the bug.
--
Npviewer randomly freezes while surfing sites like youtube
https://bugs.launchpad.net/bugs/158126
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: deluge
Deluge 1.1.4 - (08 March 2009)
Core
* Fix displaying file errors when the torrent isn't paused
* Fix issue where torrents being check would get removed due to stop at
ratio rules
* Fix #790 tracker hosts not correct for some .uk
** Summary changed:
- Security fixes in tor 0.2.0.32 and .33
+ Security fixes in tor 0.2.0.32 .33 .34
** Description changed:
+ Tor 0.2.0.34 contains:
+
+ o Security fixes:
+ - Fix an infinite-loop bug on handling corrupt votes under certain
+ circumstances. Bugfix on
.crash files should only be submitted through apport, they should not be
attached to existing bugs.
Unless you had the relevant debug symbols installed at the time of the
crash, then it would have been an incomplete backtrace. By following the
instructions at
Public bug reported:
Binary package hint: fretsonfire
/usr/share/games/fretsonfire/game/Song.py:31: DeprecationWarning: the sha
module is deprecated; use the hashlib module instead
import sha
** Affects: fretsonfire (Ubuntu)
Importance: Low
Status: New
** Changed in:
Public bug reported:
Binary package hint: gnome-format
With gnome-format 0.1.1-0ubuntu3, the about box in the application
reports the version as being 0.1.0. This is clearly wrong.
** Affects: gnome-format (Ubuntu)
Importance: Low
Status: New
** Changed in: gnome-format (Ubuntu)
You can already do this from Applications - Sound Video - DeVeDe.
Thanks for your report, closing invalid.
** Changed in: devede (Ubuntu)
Status: New = Invalid
--
devede lacks an entry in the gnome menu
https://bugs.launchpad.net/bugs/339421
You received this bug notification because
The menu entry is there for me on up-to-date Jaunty. Please check for
the .desktop file as Robert mentioned.
** Changed in: devede (Ubuntu)
Status: New = Incomplete
--
devede lacks an entry in the gnome menu
https://bugs.launchpad.net/bugs/339421
You received this bug notification
The problem has not been fixed, I can reproduce it every time.
--
soundconverter crashed with SIGSEGV in av_metadata_get()
https://bugs.launchpad.net/bugs/331497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 335741 ***
https://bugs.launchpad.net/bugs/335741
** This bug has been marked a duplicate of bug 335741
[jaunty]python(2.6)-based apps cannot meet dependencies
--
[jaunty] python-libtorrent: Depends: python ( 2.6)
https://bugs.launchpad.net/bugs/338548
This should be retested once bug 335741 and bug 336229 relating to
python 2.6 issues have been fixed.
--
Jaunty: deluge crashes on startup
https://bugs.launchpad.net/bugs/320577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You shouldn't attach raw .crash reports, as they may contain sensitive
information. Removed attachments.
** Attachment removed: _usr_bin_compiz.real.999.crash
http://launchpadlibrarian.net/19508856/_usr_bin_compiz.real.999.crash
** Attachment removed: _usr_bin_compiz.real.1000.crash
Thanks for testing. Unfortunately there are still unresolved issues with
the python 2.6 transition. Deluge should be ready for installation and
testing once bug 338548 and bug 336229 have been fixed.
--
Deluge crashed when starting up.
https://bugs.launchpad.net/bugs/224195
You received this bug
Has anyone discovered steps that always reproduce this issue?
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
(as an attachment) to the bug report.
** Changed in: compiz (Ubuntu)
Status: Confirmed =
** Changed in: revelation (Ubuntu)
Importance: Undecided = High
Status: Confirmed = Triaged
--
Broken package : revelation depends: python ( 2.6) but 2.6.1-0ubuntu1 is to be
installed
https://bugs.launchpad.net/bugs/335854
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a .crash file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Deluge has had significant code changes with
1.1.3+dfsg-1, available in Ubuntu Jaunty. Could you please test with
this version to see if the problem still exists? You can find out more
about the development release
** Changed in: deluge (Ubuntu)
Sourcepackagename: deluge-torrent = deluge
--
sudo dpkg-reconfigure deluge-torrent, dpkg issue on wrong command
https://bugs.launchpad.net/bugs/329748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Visibility changed to: Public
--
deluged crashed with AttributeError in upgrade05()
https://bugs.launchpad.net/bugs/329579
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
Have you had a chance to test? Deluge 1.1.3+dfsg-1 is now available.
--
deluge crashed with TypeError in _on_set_connection_limit()
https://bugs.launchpad.net/bugs/324651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Thanks for your report. Please try testing with deluge 1.1.3+dfsg-1, and
if the problem still occurs, try deleting/moving your core.conf as
mentioned in the above comment.
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
Status: New = Incomplete
--
deluge crashed with
Thanks for your report. Does the problem still occur with deluge
1.1.3+dfsg-1?
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
Status: New = Incomplete
--
deluged crashed with AttributeError in upgrade05()
https://bugs.launchpad.net/bugs/329579
You received this bug
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
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
Actually I can reproduce it. Opening http://localhost:58846/ with Deluge
running causes the crash.
** Changed in: deluge (Ubuntu)
Status: Incomplete = Confirmed
** Visibility changed to: Public
--
deluged crashed with AttributeError: 'NoneType' object has no attribute 'write'
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
deluge crashed with OSError in __init__()
https://bugs.launchpad.net/bugs/333227
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
--
deluge crashed with IOError in __init__()
https://bugs.launchpad.net/bugs/333228
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
301 - 400 of 755 matches
Mail list logo
