I hadn't experienced that issue until yesterday, but it happened to me 5
or 6 times since then. Always when pressing Ctrl+C while working in
gnome-terminal. I'm in a default Ubuntu session (wayland).
osomon@bribon:~$ LANG=C apt policy gdm3 gnome-shell gnome-terminal console-setup
gdm3:
Reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=787629
** Bug watch added: GNOME Bug Tracker #787629
https://bugzilla.gnome.org/show_bug.cgi?id=787629
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
It's done it again this morning. See attached screenshot.
Again, I have not opened the gnome-software GUI, only applied a few
updates manually with apt:
Start-Date: 2017-08-19 10:03:08
Commandline: apt dist-upgrade
Requested-By: osomon (1000)
Install: gnome-shell-extension-ubuntu-dock:amd64
Seen that this morning on a fully updated artful. Shortly after boot, a
gnome-software process started consuming 100% CPU and continued doing so for a
few hours, after which I killed it.
I had not opened the gnome-software GUI, only applied a few updates manually
with apt:
Start-Date:
The chromium bug in comment #7 is
https://bugs.chromium.org/p/chromium/issues/detail?id=442111, but from
the original bug description it doesn't appear to be the same bug as
reported by Aki.
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification because you are a
Although chromium-browser is affected by the issue, it doesn't appear to
be the cause of the issue itself (other apps like gnome-terminal appear
to be similarly affected), so I'm marking this bug invalid for chromium-
browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed =>
control.in}: updated for python3
** Changed in: gconf (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
** Changed in: gconf (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Please merge gconf 3.2.6-4 (universe) from Debian unstable (main).
** Affects: gconf (Ubuntu)
Importance: Wishlist
Assignee: Olivier Tilloy (osomon)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
`xdg-mime query filetype linux-3.2.89.tar.xz` returns nothing on artful,
whereas it returns "application/x-xz-compressed-tar" on zesty, which
explains why xdg-open takes a different code path.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
In a zesty VM, xdg-open runs file-roller, whereas in artful it runs
`run-mailcap --action=view`.
xdg-open itself hasn't changed recently though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
$ run-mailcap --action=view --debug linux-3.2.89.tar.xz
- parsing parameter "linux-3.2.89.tar.xz"
- file "linux-3.2.89.tar.xz" has encoding "xz"
- Reading mime.types file "/home/osomon/.mime.types"...
could not read "/home/osomon/.mime.types" -- No such file or directory
- Reading
When I run xdg-open, here are the processes that get spawned:
/bin/sh /usr/bin/xdg-open linux-3.2.89.tar.xz
/usr/bin/perl /usr/bin/run-mailcap --action=view linux-3.2.89.tar.xz
/usr/lib/gvfs/gvfsd-archive file=/tmp/filenaxeY1.2.89.tar
--
You received this bug notification because
Public bug reported:
I initially spotted the issue when opening a downloaded source tarball
from chromium-browser, which uses xdg-open under the covers to open
downloaded files.
Steps to reproduce:
1) wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.3.tar.xz
2) xdg-open
AFAICT everything requested by the OP is implemented in recent versions
of chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
** Branch unlinked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon
There is an upstream plan to trim the dependency of chromium on gnome-
keyring to a bare minimum, see
https://bugs.chromium.org/p/chromium/issues/detail?id=571003.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1685747/+attachment/4867210/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1685747/+attachment/4867211/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1685747/+attachment/4867212/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
Public bug reported:
Trying to file a bug with apport-cli from the crash file, but it won’t
open a browser window. So here’s a manual bug report with the crash file
attached, and retraced stacktrace:
#0 0x7f600a8c1c00 in gdk_wayland_display_get_selection
(display=display@entry=0x0) at
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1685747/+attachment/4867209/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
> I am a little unconvinced it calls startupdates at all, because then
> repeated calls would presumably eventually work and they don't?
startUpdates() is being called, but because oxide gets a position right
away (the last known one), it calls stopUpdates(), which prevents the
GPS from actually
Right, but as long as the location service doesn’t return the last known
location when updates were requested, it’s okay. There’s a specific
method for querying the last known location, and it does what it says on
the tin. Note that the last known position isn’t necessarily very
accurate either.
I just had a chat with Thomas, and it appears that the
GeoPositionInfoSource as implemented in qtubuntu-sensors always returns
the last known position first on purpose, before starting to request
updates. This is similar to what the geoclue plugin does.
However it’s not clear that this should be
The issue I’m seeing on my laptop seems to be specific to the geoclue
location plugin: the last known position is serialized on disk, and it’s
always emitted at startup, regardless of whether an update was
requested:
@Alberto: the maximumAge parameter is not exposed in the chromium
content API. See
https://cs.chromium.org/chromium/src/content/public/browser/location_provider.h.
Additionally, see my previous comment: I’m seeing the same issue on my
laptop, which is not running the location service. It looks
And to expand on this: even when requesting a single position with
getCurrentPosition, oxide calls in to
QGeoPositionInfoSource::startUpdates()¹. I wonder if there’s a bug in
QtPositioning, or maybe incorrect documentation, as on my laptop (which
doesn’t have a GPS chipset), when calling
** Package changed: webbrowser-app (Ubuntu) => oxide
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1604446
Title:
getcurrentPosition in oxide does not cause a wake up of
According to the specification¹, when the 'maximumAge' parameter of a
call to getCurrentPosition() is not explicitly set, its value defaults
to 0, which instructs the user agent to request a new position, and not
return a cached one.
However pages that call getCurrentPosition() with a maximumAge
Works here on my krillin running rc-proposed #163.
Note that it consistently failed in all applications using the location service
until I rebooted the device, and it started working again.
This is most likely a bug in location-service anyway, not in webbrowser-app.
Can you confirm that you fail
That’s puzzling because Here Maps and facebook in the browser use
exactly the same code path (they both poke at the location service
through oxide).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
It looks like the issue is with the location service that stops
reporting position updates under certain conditions (that sometimes
involve wifi networks).
I’m marking location-service affected, in the hope that someone familiar
with the location service can comment (maybe it’s a known issue?).
FWIW, here’s my experience: I flashed image #72 (14.09-proposed) onto my
krillin and tested both maps.google.com and here.com, for which I got
geolocation working. I then applied the OTA update to #73, rebooted, and
it is still working.
--
You received this bug notification because you are a
I run OSMtouch app and it is able to locate me. I do get a popup
saying No GPS available. Position is approximate but the location
on the map is roughly accurate.
I had a look at OSMtouch’s code, and this message indicates that the app
failed to get a position fix from the location service,
** Changed in: webbrowser-app
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1182658
Title:
Geolocation is not working in the
** Changed in: webbrowser-app
Status: Confirmed = In Progress
** Branch linked: lp:~osomon/webbrowser-app/geolocation-permission
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
After killing the daemon process, it is respawned automatically by
upstart, and it’s back to a normal CPU usage (0% when idle).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
Public bug reported:
On build #100.
After playing with geolocation in the browser (browsing to maps.google.com) a
few times, I found out that the location service daemon is using 100% CPU all
the time:
top - 09:06:49 up 24 min, 1 user, load average: 1.15, 2.10, 2.45
Tasks: 184 total, 1
I’m not seeing any crash file for the location service, however the
browser did crash in the course of my tests.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1240878
Marking invalid for the browser app, as I managed to get geolocation to
work several times in a row in the browser (closing the app in between
each attempt). I haven’t seen a crash of the location service either,
but I have verified that when killed it is automatically respawned by
upstart, so the
Output of strace on the daemon when it’s consuming 100% CPU:
root@ubuntu-phablet:/# strace -p `pidof ubuntu-location-serviced`
Process 6619 attached
futex(0x453ff4c8, FUTEX_WAIT, 6633, NULL
** Branch linked: lp:~thomas-voss/location-service/fix-1240878
** Changed in:
The attached branch (lp:~thomas-voss/location-service/fix-1240878)
doesn’t fix the CPU usage. I’ve installed the packages built from the
branch, rebooted, and I’m still able to reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Attaching the stacktrace obtained by attaching gdb to the running
daemon. Not very useful.
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1240878/+attachment/3880145/+files/ThreadStacktrace.txt
--
You received this bug notification
I installed libubuntu-location-service0 built from the latest trunk
(revision 40), that supposedly removes some exception throwing, however
I’m still getting a very similar stacktrace:
[…]
#9 0x400af172 in _Unwind_Resume ()
at ../../../src/libgcc/config/arm/libunwind.S:344
#10 0x42e23eee in
invoke_method_synchronously calls send_with_reply_and_block_for_at_most, which
might throw a std::runtime error.
So we need to surround this call with a try…catch block to ensure we respect
the noexcept promise.
--
You received this bug notification because you are a member of Ubuntu
Desktop
I can confirm that geolocation in the browser works with the last two
fixes applied to lp:location-service.
** Changed in: webbrowser-app (Ubuntu Saucy)
Status: Confirmed = Invalid
** Changed in: webbrowser-app
Status: Confirmed = Invalid
** Changed in: location-service (Ubuntu
Attaching a visual proof that it works :)
** Attachment added: geolocation.jpg
https://bugs.launchpad.net/webbrowser-app/+bug/1182658/+attachment/3871907/+files/geolocation.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I managed to get a partially useful stacktrace:
#0 0x40f99706 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x40fa75fe in raise () from /lib/arm-linux-gnueabihf/libc.so.6
#2 0x40fa9e1a in abort () from /lib/arm-linux-gnueabihf/libc.so.6
#3 0x40f217b4 in
I am able to reproduce the crash with a simple test program written in
C++ that uses QtLocation to retrieve the current location. The crash
happens when calling QGeoPositionInfoSource::stopUpdates() (which itself
calls
com::ubuntu::location::service::session::Stub::stop_position_updates()),
so I’d
** Branch linked: lp:~thomas-voss/location-service/fulfill-noexcept-
promise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1182658
Title:
Geolocation is not working in
For reference, I’m attaching the sources of the simple test program with
which I can reproduce the crash on a device.
** Attachment added: test-location.tar.gz
https://bugs.launchpad.net/webbrowser-app/+bug/1182658/+attachment/3868678/+files/test-location.tar.gz
--
You received this bug
I’m seeing the same as bjv, with the latest image flashed today (#83).
** Changed in: webbrowser-app
Assignee: (unassigned) = Olivier Tilloy (osomon)
** Changed in: webbrowser-app (Ubuntu Saucy)
Assignee: (unassigned) = Olivier Tilloy (osomon)
--
You received this bug notification
** Summary changed:
- Location services not working in Google Maps
+ Geolocation is not working in the browser
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1182658
Following Thomas’ advice, I tested again with my device hanging from a window,
and the test application eventually picked up the location from the GPS.
However I still can’t get it to work in the browser, so it seems the issue is
in QtWebKit itself.
Investigating now.
--
You received this bug
Note that geolocation works in webbrowser-app on the desktop, so the
issue is somewhere in the communication between the location provider
and QtWebKit on devices.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in
I wrote a simple C++ application that uses QtLocation to monitor
location updates and print them out on the console, I built it on my
device and ran it, and after a while (cold start is really slow) I got
location updates, so I can confirm that the location stack works.
--
You received this bug
When trying to use geolocation in the browser, the app sits idle for a
while, and is eventually terminated with the following:
terminate called after throwing an instance of 'std::runtime_error'
what(): Did not receive a reply. Possible causes include: the remote
application did not send a
Unfortunately I’m unable to get a useful stacktrace from the crash, so I
don’t know exactly where the crash happens.
It seems that the app fails to reach the service, for some reason.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I’m seeing the same problem. The browser prompts for authorization to
use the device’s location, but it seems the device is unable to provide
its location. I looked for satellite visibility updates in dmesg, but
couldn’t find anything relevant (`dmesg | grep -i sat` is empty).
--
You received
A recent update in quantal re-added an ICC profile and the bug re-
surfaced. Removing the profile with `xprop -root -remove _ICC_PROFILE`
fixed it again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
This crash also happens to me when opening an RPM file
(ftp://ftp.icm.edu.pl/vol/rzm2/linux-fedora-
secondary/releases/15/Everything/source/SRPMS/libsocialweb-0.25.16-1.fc15.src.rpm).
file-roller 3.5.92-0ubuntu1
12.10 fully up-to-date
--
You received this bug notification because you are a
I was observing the same issue since a recent update in precise (I have
upgraded to quantal since then and the issue persisted).
Unsetting the ICC profile as suggested by Felix in comment #14 solved the issue.
Before unsetting the ICC profile, I took the test suggested in comment
#19 (opened the
I’m seeing this issue in Natty.
It is a fresh install, my home directory is encrypted and it has
annoying consequences, such as Déjà-Dup failing to backup my home
directory because of ~/.gvfs (Transport endpoint is not connected).
And since the .gvfs folder cannot be browsed to, I can’t even add
It looks more like bug #281217 to me, although both of them are old bugs
and the situation may have improved/degraded in newer versions of
evolution. In any case, it definitely looks like a bug in evolution
itself, so I’ll change the affected project.
** Project changed: unity-2d = evolution
**
Public bug reported:
Binary package hint: gnome-control-center
In /usr/share/gnome-control-center/default-apps/gnome-default-
applications.xml (installed by capplets-data), the default entry for
banshee reads banshee-1 for the executable and the command. This
should be banshee. As a result,
The fix is trivial, it should revert the change applied to fix bug
#533888: just remove the patch 112_banshee_in_media_dropdown.patch.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
I downloaded all the source packages listed in apt’s upgrade log
attached above in a lucid chroot, and I grep’ed through in search of
mousekeys (the gconf key that controls whether mouse keys are enabled
is /desktop/gnome/accessibility/keyboard/mousekeys_enable), but this
didn’t yield any result.
A recent ugrade on my mom’s machine running lucid (lsb_release says
10.04.2) turned on the mouse keys in keyboard accessibility by default,
when they were previously disabled. This had the very annoying
consequence of the numeric keypad apparently not functioning any longer,
and only by googling
An updated patch has been committed upstream (see
http://git.gnome.org/browse/nautilus/commit/?id=ebcbb167876f8b4491af0bc86bc29015c211b3af).
--
Audio preview of CD tracks fails if totem is not installed
https://bugs.launchpad.net/bugs/607793
You received this bug notification because you are a
Sure.
--
Audio preview of CD tracks fails if totem is not installed
https://bugs.launchpad.net/bugs/607793
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Updated patch submitted upstream.
--
Audio preview of CD tracks fails if totem is not installed
https://bugs.launchpad.net/bugs/607793
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
Sure, updating the patch is on my list.
--
Audio preview of CD tracks fails if totem is not installed
https://bugs.launchpad.net/bugs/607793
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing
Public bug reported:
Binary package hint: nautilus
To perform audio preview, Nautilus uses totem-audio-preview. If not
present (i.e. if totem is not installed), it falls back on gst-
launch-0.10 with a playbin pipeline. Unfortunately playbin doesn't
understand the cdda:// URIs when trying to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52212207/Dependencies.txt
** Attachment added: usr_lib_nautilus.txt
http://launchpadlibrarian.net/52212208/usr_lib_nautilus.txt
--
Audio preview of CD tracks fails if totem is not installed
The issue is with the way nautilus builds the URI to pass to playbin.
The attached patch mimics totem's behaviour to build URIs that playbin
is happy with.
** Patch added: oem-preview-audio-cd-tracks-with-playbin.patch
** Bug watch added: GNOME Bug Tracker #624841
https://bugzilla.gnome.org/show_bug.cgi?id=624841
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=624841
Importance: Unknown
Status: Unknown
--
Audio preview of CD tracks fails if totem is not installed
I'm perfectly fine waiting for the next upload, there's no hurry
considering the importance of the bug.
--
Audio preview of CD tracks fails if totem is not installed
https://bugs.launchpad.net/bugs/607793
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Bug watch added: Debian Bug tracker #589749
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589749
** Also affects: nautilus (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589749
Importance: Unknown
Status: Unknown
--
Audio preview of CD tracks fails if totem
Tested epiphany-browser 2.30.2-1ubuntu1.1 from proposed, the user agent
string now contains Ubuntu/10.04 LTS as expected.
--
User Agent string says Debian/squeeze/sid () instead of Ubuntu/10.04 LTS
(lucid)
https://bugs.launchpad.net/bugs/578717
You received this bug notification because you are
@Luke: I followed steps 1 to 3 of the procedure for an SRU, please let
me know if more input is needed from my side.
** Description changed:
Binary package hint: epiphany-browser
In epiphany 2.30.2 in lucid, the user agent string is the following:
Mozilla/5.0 (X11; U; Linux i686;
I linked a new branch that targets Maverick.
Note that the patch could probably be made more generic using lsb_release to
dynamically fill the vendor information, but that would mean more intrusive
changes which should probably be applied upstream first.
Thanks for reviewing.
** Branch linked:
Public bug reported:
Binary package hint: epiphany-browser
In epiphany 2.30.2 in lucid, the user agent string is the following:
Mozilla/5.0 (X11; U; Linux i686; fr-fr) AppleWebKit/531.2+ (KHTML, like
Gecko) Safari/531.2+ Debian/squeeze/sid () Epiphany/2.30.2
To be compared with the user agent
The fix is pretty trivial, the information to be changed sits in
/usr/share/epiphany-browser/branding.conf.
--
User Agent string says Debian/squeeze/sid () instead of Ubuntu/10.04 (lucid)
https://bugs.launchpad.net/bugs/578717
You received this bug notification because you are a member of Ubuntu
diff /usr/share/epiphany-browser/branding.conf.orig
/usr/share/epiphany-browser/branding.conf
2,4c2,4
Vendor=Debian
VendorSub=squeeze/sid
VendorComment=
---
Vendor=Ubuntu
VendorSub=10.04
VendorComment=lucid
--
User Agent string says Debian/squeeze/sid () instead of Ubuntu/10.04 (lucid)
** Branch linked: lp:~osomon/ubuntu/lucid/epiphany-browser/user_agent
--
User Agent string says Debian/squeeze/sid () instead of Ubuntu/10.04 (lucid)
https://bugs.launchpad.net/bugs/578717
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Is this bug still valid? I can't reproduce with software center 2.0.2.
Whenever the search results list is updated, the first item is always selected,
regardless of keyboard navigation. Pressing the down key gives the focus to the
first item that was already selected.
--
From search field,
I can confirm the issue on Karmic. Note that I've had a look at the package in
Lucid, and it's not fixed there.
It seems to me that all that's needed is to add an entry for
application/vnd.openxmlformats-officedocument.presentationml.slideshow in
/usr/share/mime/packages/freedesktop.org.xml. I
IMHO, the importance of this bug should be bumped. It's easy enough to
work around it for an advanced user, either by changing the file's
extension or by selecting Open with another application, but it's just
not a reasonable solution for normal users. To them, the only conclusion
will be: Ubuntu
I reported the bug upstream
(https://bugs.freedesktop.org/show_bug.cgi?id=26276) and attached a
patch there.
** Bug watch added: freedesktop.org Bugzilla #26276
https://bugs.freedesktop.org/show_bug.cgi?id=26276
--
.ppsx (Office 2007 slideshows) files not recognized
The issue seems to be in libmms (see bug #212064).
--
Totem-GStreamer doesn't play CNN Pipeline
https://bugs.launchpad.net/bugs/97686
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Don't be :)
That's one more good reason to seriously consider upgrading my mom's machine to
Jaunty, although living 1000km from her won't help.
--
2 gb max inbox
https://bugs.launchpad.net/bugs/197290
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
Is there any chance the patched package will install fine on Gutsy, or that the
package will be backported there as well?
My Mom's computer has been running Gutsy for ages and she ran into this issue a
week ago.
--
2 gb max inbox
https://bugs.launchpad.net/bugs/197290
You received this bug
301 - 392 of 392 matches
Mail list logo
