Sebastien - I've just come back to this bug report because I've had a
similar experience with another user who isn't getting a crash report
with Apport (even though it is enabled). It turns out that Apport
doesn't catch SIGABRT, which is what Yelp is terminating with here. I
don't know if Apport
Matthias:
Your log doesn't contain any details of the crash (the log must be from
the session directly after the crash, otherwise a good log gets rotated
in to it's place and the important information is lost), and your
problem is not related to this one. This is a bug in the NVIDIA driver,
and
Alex - Your issue doesn't even have the same symptom as those reported
here, so unless you report a separate bug report, your issue will not
get resolved.
As per
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/204996/comments/192,
will people who are still experiencing this problem and
Can I just confirm that I'm going through the same steps as you, because
I can't reproduce what you're seeing.
1) Go to Places - Connect to Server...
2) Select 'Service type = SSH', specify Server and Folder (in my case, I
specify Server=192.168.0.1 and Folder=/home/chr1s)
3) Check 'Add
Your fstab is messed up. Swap isn't mounting because the UUID specified
doesn't exist, and the UUID for your root filesystem is invalid. I can
only assume that your root filesystem is mounting due to the kernel
option specified in your menu.lst.
What is the output of 'cat /proc/cmdline'?
Thanks
Public bug reported:
If I select an audio track in Nautilus using the mouse, the audio
preview starts because the mouse pointer is over the audio track icon.
If I then press the DEL key, the track is sent to trash as expected, but
the audio preview carries on playing. The only way to stop it is
Michael: Is this fix supposed to completely fix the white screen issues,
because for me it only partially fixes the problem. I can switch between
users, have the screen lock automatically and return to the users
without seeing the white screen. But any windows that appear on the
background screen
Mario,
Thanks for the clarification. Although I think the 'upcoming' NVIDIA
release which fixes this is a long time away. We all know how long it
took them to fix the black window bug, so I don't think I shall be
getting my hopes up for them to fix it before my card becomes obsolete!
--
Blempis - I just saw a post on the Ubuntu forums here:
http://ubuntuforums.org/showpost.php?p=5052301postcount=3
This might just be due to your configuration. Could you try it please
--
Num keys not working
https://bugs.launchpad.net/bugs/231173
You received this bug notification because you
Verified that a blank window no longer appears. But it has a nasty side
effect - the 'Next' and 'Previous' buttons don't work at all as
expected. When I click 'Next' or 'Previous', I expect to see the next or
previous e-mail from my unread list appear in the window, but I don't.
It doesn't cycle
I'm still a bit confused actually. It seems that the UUID does exist,
because your root filesystem is obviously being mounted by it, but blkid
doesn't show it. What does 'sudo mount -a' say, and also 'ls -l
/dev/disk/by-uuid/'?
--
File systems mounted via UUID does not show up on file system
Right, that's useful. blkid is giving one UUID, but udev thinks it is
something else. I'll take another look at this later once I've worked
out what other information will be useful from you
--
File systems mounted via UUID does not show up on file system listings
Actually, for completeness, what is the output of 'sudo vol_id
/dev/sda1'?
Thanks
--
File systems mounted via UUID does not show up on file system listings
https://bugs.launchpad.net/bugs/235165
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thats even stranger. vol_id thinks /dev/sda1 is a FAT16 partition. What
is the output of 'sudo fdisk -l'?
--
File systems mounted via UUID does not show up on file system listings
https://bugs.launchpad.net/bugs/235165
You received this bug notification because you are a member of Ubuntu
Bugs,
Assigning to udev, confirming, and I'm going to edit the title to
something more appropriate.
Thanks
** Changed in: udev (Ubuntu)
Sourcepackagename: gnome-system-monitor = udev
Status: Incomplete = Confirmed
--
File systems mounted via UUID does not show up on file system listings
** Summary changed:
- File systems mounted via UUID does not show up on file system listings
+ vol_id detecting ext3 partition as FAT16, which conflicts with blkid
** Description changed:
- Binary package hint: gnome-system-monitor
+ Edited by Chris Coulson {
+ vol_id is reporting an EXT3
Yeah, I noticed the label of /dev/sda1 pointed it to being a Dell
partition. I don't think it should make a difference though. It's a bit
strange!
--
vol_id detecting ext3 partition as FAT16, which conflicts with blkid
https://bugs.launchpad.net/bugs/235165
You received this bug notification
Paul: As pointed out in comment 85 by Mario, the underlying problem with
the NVIDIA driver still exists, and we're going to have to wait
(possibly a very long time) for them to fix it. So, you will still see
this bug under certain use cases until the NVIDIA driver is fixed.
NVIDIA have set they
You mention DBUS in the title and HAL later on. Which one is it?
Obviously, if you restart DBUS then HAL gets restarted anyway (along
with lots of other stuff).
Why are you trying to restart DBUS anyway? It causes all sorts of
horrible problems (not just with PolicyKit). I've just tried
Are you referring to the number keys along the top row of the keyboard,
or the number key pad? If it is the pad, can you turn Num Lock on and
off? Do the keys only not work in X? (Could you try switching to a
terminal by doing CTRL+ALT+F1 and logging in, then test the keys to see
if they work).
I'm on Hardy but I just downloaded the flashplugin-
nonfree_9.0.124.0ubuntu1~gutsy1_i386.deb package, then downloaded the
Flash plugin from the same location that the Gutsy deb gets it from
(http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz)
and checked
John,
dierre is running Gutsy, and the most up-to-date flashplugin-nonfree
package is flashplugin-nonfree_9.0.124.0ubuntu1~gutsy1 which is in
gutsy-updates. I verified that the md5sum matches with this, so he
either doesn't have gutsy-updates enabled or the download is being
corrupted
--
md5sum
Ok, the md5sum will definately not check out with the version you are
trying to install. Your sources.list does suggest you have gutsy-updates
enabled though. Could you try with another mirror? (System -
Administration - Software Sources, then select another location in
'Download from').
If that
Spotted it! You only have multiverse enabled for gutsy and gutsy-
security, but not gutsy-updates - there lies your problem. I've attached
your sources.list with multiverse and universe added to gutsy-updates.
I've also corrected the commented out reference to feisty-backports as
well (now shows
I forgot to add - please comment if you have any more issues
--
md5sum mismatches in ubuntu 7.10
https://bugs.launchpad.net/bugs/231171
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
If I set my mail account preferences to PGP sign outgoing mail and
specify the PGP key I would like to use, Evolution fails to send any
messages. When I click send, the error I get is:
'Could not create message.
Because Failed to unlock secret key: 3 bad passphrases given.,
And it works if I downgrade Evolution to 2.22.1-0ubuntu3.1
--
Cannot PGP sign e-mails in Evolution
https://bugs.launchpad.net/bugs/231666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
From your /var/log/messages - 'compiz.real[19910]: segfault at 1 rip 1
rsp 7fffbd207218 error 14' - I thought you said Compiz was not used and
was uninstalled. That seems to suggest otherwise.
There is also an instance in there of Xorg crashing. Could you please
repeat the steps to make X lock
** Changed in: xorg (Ubuntu)
Assignee: Chris Coulson (chrisccoulson) = (unassigned)
--
restarting X (restarting kdm in example) and going back to VT then back to X
causes X failure (nvidia, glx-new)
https://bugs.launchpad.net/bugs/230203
You received this bug notification because you
I thought the report was clear enough already actually. Anyway:
Steps to reproduce:
1) Open Evolution and enable PGP signing for outgoing mail (Edit -
Preferences, click 'Mail Accounts' button, click,'Security' tab and then check
the button to PGP sign mail and enter a key ID)
2) Compose a new
In my case, I think I probably broke the configuration myself at some
point. My current Hardy machine has been upgraded from Gutsy which was
upgraded from Feisty, and at some point along the way I set a root
password, and then later deleted it using 'sudo passwd -d root', which
is probably what
edrangas: You're right - in my case, a simple:
'sudo passwd -l root'
...fixes my issue! I can now use the users-admin tool again.
--
users-admin won't add or delete users
https://bugs.launchpad.net/bugs/220697
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Nick - you definately can do this on Hardy if you drag the Desktop icon
from the Places menu. I agree that it should produce an error, but it
doesn't. It ends up recursively copying the desktop and its contents in
to itself repeaterdly until either the directory depth gets too deep
(filename too
Not sure why you have a problem deleting it from the trash though - I
can't repeat that. But this behaviour shouldn't happen in the first
place
** Changed in: gvfs (Ubuntu)
Sourcepackagename: None = gvfs
Status: New = Confirmed
--
Unable to delete Desktop Folder
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 101845, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively [WWW]
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
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. Please follow these instructions to have
apport report a new bug about your crash that can be dealt with by the
automatic retracer.
If you
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively [WWW]
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
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. Please follow these instructions to have
apport report a new bug about your crash that can be dealt with by the
automatic retracer.
If you
Users should only be added to the plugdev group when you check 'Access
external storage devices automatically'. Can you verify to make sure
that happens please? Users should NOT be part of the disk group, as this
gives them full read-write access to all the /dev/sdxx and /dev/hdxx raw
block
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information.
Please include the information as separate attachments:
* Output of uname -a
* uname -a uname.txt
* Output of sudo
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. Please follow these instructions to have
apport report a new bug about your crash that can be dealt with by the
automatic retracer.
If you
Confirmed. Installing fail2ban shouldn't create /var/run/fail2ban (which
is what happens at the moment), but running it should create it instead
(baring in mind that /var/run is volatile).
Steps to reproduce:
1) Install fail2ban
2) Stop fail2ban (sudo /etc/init.d/fail2ban stop)
3) Remove
Is htis actually fixed in the Ubuntu version though? Otherwise you can't
mark it as 'Fix Released'
--
Multiple windows open on double click
https://bugs.launchpad.net/bugs/234071
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yes, /var/run/fail2ban gets created at install-time by the current
package. The deb package actually contains /var/run/fail2ban as opposed
to creating it from one of the install scripts
--
Installing fail2ban doesn't create /var/run/fail2ban directory
https://bugs.launchpad.net/bugs/234076
You
Sebastien - I'm not sure it is possible to say that almost nobody is
suffering this bug in Hardy. Bare in mind that Apport is disabled by
default, so the only people who will ever notice the crash are the
people who have manually re-enabled Apport (like myself). The bug seems
to have no other
Martin - From memory, I think my machine behaves the same (I can't check
for sure until I get home tonight). I see a faded desktop instead of a
black screen if I leave the machine idle, and I see a black screen if I
lock it using CTRL+ALT+L
--
[nvidia] compiz displays white screen when locked
*** This bug is a duplicate of bug 160264 ***
https://bugs.launchpad.net/bugs/160264
Caspar - What makes you think this is a duplicate of bug 160189? The
reporters describe completely separate issues
--
compiz.real running 100% CPU after screen saver
https://bugs.launchpad.net/bugs/161112
Id2ndR - No need to confirm. If you read through this report, you'll
find that this is fixed in the packages in hardy-proposed
--
[nvidia] compiz displays white screen when locked
https://bugs.launchpad.net/bugs/160264
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 222643 ***
https://bugs.launchpad.net/bugs/222643
Jorge - I think this is actually a Nautilus/GVFS bug, as it is Nautilus
which is launching Totem when the media is inserted. Nautilus is auto-
launching in all running sessions when media is inserted (not
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
Thanks for the information. Which version of Ubuntu are you using? You
can find this out by typing the following in to a terminal:
lsb_release -rd
--
nvidia: low resolution since the last canonical update
https://bugs.launchpad.net/bugs/250999
You received this bug notification because you are
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We appreciate the difficulties you
are facing, but
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
does not yet have enough information.
Please include the following additional information (using a working kernel),
if you have not already done so (pay
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Confirmed
--
hardy-proposed: linux-image-2.6.24-20-generic freezes on boot (regression)
https://bugs.launchpad.net/bugs/251379
You received this bug notification
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
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 251344, so it is being marked as such. Please look
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
This is actually a duplicate of bug 251344
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
** This bug has been marked a duplicate of bug 251344
Hardy proposed 2.6.24-20-generic kernel
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please attach your X server configuration file
(/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the
bug report as individual uncompressed file attachments using the
Attachment: box below.
Could
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
** This bug is no longer a duplicate of bug 251614
The kernel 2.6.24.20.22 doesn't boot
** This bug has been marked a duplicate of bug 251344
Hardy proposed 2.6.24-20-generic kernel update will not
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
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 251344, so it is being marked as such. Please look
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
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 251344, so it is being marked as such. Please look
I still can't reproduce this myself. The only situation where I can get
this is if I edit a text file (which I have write permissions for) in a
directory that I don't have write permissions in. In this scenario, you
can edit the already existing file, but don't have the permissions to
create new
Thank you for taking the time to report this bug and help make Ubuntu
better. What you have described is not a bug with apt, as it is
correctly handling the dependencies of the packages that you are trying
to remove. The reason that ubuntu-desktop and GDM are removed, is
because GDM depends on
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 is this still an issue
for you? Can you try with latest Ubuntu release?
Thanks in advance.
** Changed in: apt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
did not include enough information. Please attach your X server
configuration file (/etc/X11/xorg.conf) and X server log file
(/var/log/Xorg.0.log) to the bug
Thank you for taking the time to report this bug and help make Ubuntu
better, Unfortunately, we can't fix it, because your description didn't
include enough information. Could you please provide the following
information:
1) Version of Ubuntu that you are using (type lsb_release -rd in to a
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 is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in: apt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
This bug report is being closed due to your last comment regarding this
being fixed with a configuration change. 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
Neonlight - thank you for taking the time to report this bug and help
make Ubuntu better. I am closing thie bug report, as it appears that
this is the second time you have reported this bug though. I converted
the first bug report to a question in our support tracker.
The reason I converted the
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can learn
more about finding the right package at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
Could you please post the output of the following commands please:
apt-cache policy python2.5
apt-cache policy python2.5-dev
I see that you're running the hardy-proposed testing repository. I think
that python 2.5.2-2ubuntu5 was uploaded in to proposed a while ago, but
is no longer there now.
*** This bug is a duplicate of bug 251748 ***
https://bugs.launchpad.net/bugs/251748
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 NUMBER, so it is being marked as such. Please look
python2.5 2.5.2-2ubuntu5 was uploaded to the hardy-proposed repository,
but later removed as it didn't qualify for a SRU (see bug 227686).
Therefore, the current version of python2.5 in Ubuntu 8.04.1 is
2.5.2-2ubuntu4. Because you are running the hardy-proposed repository,
you upgraded the
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
Thank you for your bug report. I can confirm this. The Alt key correctly
opens all of the other menus, except for the _File menu (for example,
Alt+E correctly opens _Edit)
** Changed in: eog (Ubuntu)
Status: New = Confirmed
--
can not access File menu with Alt-F key combo
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
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 251344, so it is being marked as such. Please look
This bug report is being closed due to your last comment regarding this
being fixed with a change of configuration. To clarify, the error
message you were getting was because gnome-session could not connect to
gnome-power-manager to retrieve the supported power states of the
machine, because
I agree 100% with what Ripps818 says. This update only went in to hardy-
proposed, which is a testing repository for updated packages. hardy-
proposed is aimed at people wanting to test updated packages, and is
designed to catch problems like this. The only users affected by this
problem are those
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We appreciate the difficulties you
are facing, but
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
*** This bug is a duplicate of bug 251991 ***
https://bugs.launchpad.net/bugs/251991
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 251991, so it is being marked as such. Please look
Makoto - you have a different problem. Your problem is that Alacarte
appears to have corrupted your users local applications.menu file. The
problem in this bug report is that some package appears to have
corrupted the system-wide applications.menu file, which is a completely
different issue.
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
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 251344, so it is being marked as such. Please look
*** This bug is a duplicate of bug 248521 ***
https://bugs.launchpad.net/bugs/248521
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 248521, so it is being marked as such. Please look
*** This bug is a duplicate of bug 248521 ***
https://bugs.launchpad.net/bugs/248521
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 248521, so it is being marked as such. Please look
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
Not a gnome-terminal bug
** Changed in: ubuntu
Sourcepackagename: gnome-terminal = None
--
updaten system
https://bugs.launchpad.net/bugs/252513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please attach your X server configuration file
(/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the
bug report as individual uncompressed file attachments using the
Attachment: box below.
**
*** This bug is a duplicate of bug 251344 ***
https://bugs.launchpad.net/bugs/251344
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 251344, so it is being marked as such. Please look
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 is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in:
*** This bug is a duplicate of bug 104570 ***
https://bugs.launchpad.net/bugs/104570
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 104570, so it is being marked as such. Please look
*** This bug is a duplicate of bug 104570 ***
https://bugs.launchpad.net/bugs/104570
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 104570, so it is being marked as such. Please look
*** This bug is a duplicate of bug 104570 ***
https://bugs.launchpad.net/bugs/104570
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 104570, so it is being marked as such. Please look
601 - 700 of 10895 matches
Mail list logo
