Fixed in guake 0.4.0, which is now in Karmic. Thanks for your report.
** Changed in: guake (Ubuntu)
Importance: Undecided = Low
** Changed in: guake (Ubuntu)
Status: In Progress = Fix Released
** Tags removed: jaunty
--
guake should use monospace font by default
Thanks for your persistent effort William, this trace looks complete!
Marked as triaged so a developer can have a look.
** Changed in: pidgin-facebookchat (Ubuntu)
Status: Incomplete = Triaged
--
pidgin crashed with SIGSEGV upon clicking on Facebook messages (notifications)
in Pidgin
Thanks for your report. Does the problem still occur with guake 0.4.0 in
Ubuntu Karmic?
** Changed in: guake (Ubuntu)
Importance: Undecided = Medium
** Changed in: guake (Ubuntu)
Status: New = Incomplete
--
guake ImportError on start
https://bugs.launchpad.net/bugs/289054
You
Gutsy is EoL, marking Won't Fix.
** Changed in: tor (Ubuntu Gutsy)
Status: Confirmed = Won't Fix
--
Security fixes in tor 0.2.0.32 .33 .34
https://bugs.launchpad.net/bugs/321102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Nizar, please see bug 328442 for why it's been removed.
With tor 0.2.0.34 in hardy- and intrepid-proposed, the security issues
will be fixed in these releases. Marking Fix Committed.
** Changed in: tor (Ubuntu Intrepid)
Status: Confirmed = Fix Committed
** Changed in: tor (Ubuntu Hardy)
** Description changed:
Binary package hint: eclipse
- Eclipse 3.4.2 is now out - maybe we could see this in Karmic?
-
- [was: Eclipse 3.3/3.4/3.4.1 is out, maybe we could see this in
- Gutsy/Intrepid/Jaunty?]
+ Eclipse 3.4.2 is now out
--
Upgrade to Eclipse 3.4.2
** 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
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.
**
** 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
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
** 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 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
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
** 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
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
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
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
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
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
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-b...@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
** 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
--
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-b...@lists.ubuntu.com
** 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-b...@lists.ubuntu.com
** 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
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
deluged crashed with AttributeError in add()
https://bugs.launchpad.net/bugs/347554
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 ValueError in _on_get_torrent_status()
https://bugs.launchpad.net/bugs/358942
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
deluge crashed with DistributionNotFound in resolve()
https://bugs.launchpad.net/bugs/358527
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Visibility changed to: Public
** Changed in: deluge (Ubuntu)
Importance: Undecided = Medium
--
deluge crashed with NoCoreError in call()
https://bugs.launchpad.net/bugs/353717
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 _shutdown()
https://bugs.launchpad.net/bugs/351589
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
The bug status reflects the development version of Ubuntu, not previous
releases. To get a fix included in a previous release, we follow the SRU
process[1]. However, in this case we have very little information on
this crash or what it is caused by, and yours is the only report of this
issue. This
Thanks for your debdiff. However it looks like it is based on
soundconverter 1.3.2, and not 1.4.1-0ubuntu1 which is the version in the
Ubuntu archive.
In any case, Jaunty is now in FinalFreeze, so soundconverter updates
won't be made until Karmic.
--
Please upgrade to soundconverter 1.4.2
This will likely happen for Karmic.
** Changed in: virtualbox-ose (Ubuntu)
Importance: Undecided = Wishlist
--
new upstream version - VirtualBox 2.2.0
https://bugs.launchpad.net/bugs/358215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for your report. Does the problem still occur with Virtualbox
2.1.4 on up-to-date Jaunty?
** Changed in: virtualbox-ose (Ubuntu)
Importance: Undecided = Medium
** Changed in: virtualbox-ose (Ubuntu)
Status: New = Incomplete
--
Jaunty alpha-1 does not boot in virtualbox-1.5.6
Thanks for your report. Does the problem still occur with Virtualbox
2.1.4 on Jaunty?
** Changed in: virtualbox-ose (Ubuntu)
Importance: Undecided = Medium
** Changed in: virtualbox-ose (Ubuntu)
Status: New = Incomplete
--
package virtualbox-ose 1.5.0-dfsg2-1ubuntu3 failed to
Thanks for your report. Does the problem still occur with Virtualbox
2.1.4 on Jaunty?
** Changed in: virtualbox-ose (Ubuntu)
Importance: Undecided = Medium
** Changed in: virtualbox-ose (Ubuntu)
Status: New = Incomplete
--
package update-manager 1:0.87.30 failed to install/upgrade:
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'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
Brasero does not open saved Audio CD project
https://bugs.launchpad.net/bugs/301934
You received this bug notification because
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
*** This bug is a duplicate of bug 251031 ***
https://bugs.launchpad.net/bugs/251031
** This bug has been marked a duplicate of bug 251031
evolution 2.23.5 crashes on startup
--
evolution crashed upon open with SIGSEGV in camel_message_info_uint32()
https://bugs.launchpad.net/bugs/286024
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
mail-notification unable to contact evolution
https://bugs.launchpad.net/bugs/278965
You received this bug notification because
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'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
nicotine crashed with AttributeError in UrlEvent()
https://bugs.launchpad.net/bugs/127757
You received this bug notification
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
201 - 300 of 755 matches
Mail list logo
