Public bug reported:
In programming mode the calculator is primarily used for doing integer
operations.
However integer results are shown in exponential notation and the result
does NOT represent the correct integer!
Example:
- Calculate 2^40.
- The result 1.099511628×10^12 is shown which is
I noticed that 18.04.1 has been released. Has there been any progress
for providing fractional scaling (via the default GUI) like was offered
in Ubuntu 16.04?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Fine, thanks for that.
As I use Neo 2 exclusively – no other keyboard layouts – there should be
no further problems once the choice has been made.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
OpenGL interface GLX must be deselected in Compositor and EGL chosen.
GLX does causes "okular menu buttons not clickable and Firefox open menu button
dead" problem.
Select OpenGL interface EGL.
OR select XRender.
The problem lies hidden somwherw in GLX.
--
You received this bug notification
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Had same issue with 14.04 to 16.04 upgrade, I had i386 and amd64 so this worked
for me, just doing amd64 gave me an error:
wget
http://mirrors.kernel.org/ubuntu/pool/main/d/dpkg/dpkg_1.18.4ubuntu1_amd64.deb
ar -x dpkg_1.18.4ubuntu1_amd64.deb
tar -xvf data.tar.gz
wget
Uploaded fix in appstream-glib 0.5.13-1ubuntu6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1780442
Title:
Please backport fix for & in attributes
Status in Fwupd:
New
The other option would be to do it "properly" the way upstream want -
ie. to have the user be able to configure their one linkification.
I am happy to rework the patch - is there any interest in carrying this
just in Ubuntu or would the preference be to push it to Debian and get
it into Ubuntu
** Changed in: appstream-glib (Ubuntu Xenial)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: appstream-glib (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: appstream-glib (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received
The driver updates in July I think are the upgrade to Mesa 18.0.5.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags added: regression-update
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
Please run:
xev | grep -A2 Button
and then middle-click in the little white window.
If it's working then you should see button 2 events, something like:
ButtonPress event, serial 37, synthetic NO, window 0x481,
root 0x156, subw 0x0, time 1291392572, (41,108), root:(98,160),
state
Please run this command to send us more details about the system:
apport-collect 1784161
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages,
*** This bug is a duplicate of bug 1746740 ***
https://bugs.launchpad.net/bugs/1746740
It appears the fix for bug 1746740 is still missing from 18.04 so let's
keep this with that bug for now.
To verify if the fix will work for you though, please also test the
proposed fix by downloading the
Your CPU model suggests you will hit bug 1727356. Please try the
workaround from that.
** This bug has been marked a duplicate of bug 1727356
Login screen never appears on early generation Intel GPUs (Core2 and Atom
etc)
--
You received this bug notification because you are a member of
Oops, sorry. Not bug 1727356 because you are running 16.04 and Unity.
** This bug is no longer a duplicate of bug 1727356
Login screen never appears on early generation Intel GPUs (Core2 and Atom
etc)
--
You received this bug notification because you are a member of Desktop
Packages, which
Please try removing ALL gnome-shell extensions. Now does the bug still
occur?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Great insight there about RLIMIT_RTTIME.
It appears that yes indeed pulseaudio is unique in that it has a self-
imposed RLIMIT_RTTIME of 20 microseconds. That is also configured in
/etc/pulse/daemon.conf:
; rlimit-rttime = 20
Normal processes have no such limit.
It appears you should
** Changed in: alsa-driver (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1563110
Title:
No sound on Asus e200ha, intel sst
guiverc@d960-ubu2:~$ sudo cat /var/lib/whoopsie/whoopsie-id
[sudo] password for guiverc:
ceaac5c412433432f0beca83292fc33804be2fdae3b13b7fc7185e6a52d5fd6941294dff354c0cc3a5000fce6202e51c04e867a10ca60bb60b3682028253f96e
guiverc@d960-ubu2:~$ sudo apt remove light-locker caffeine
Reading package
Motion sensor problems should be reported in a different bug. Maybe to
the kernel:
ubuntu-bug linux
or maybe to the userland code:
ubuntu-bug iio-sensor-proxy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Chris Guiver:
1) To confirm, please run the following command and post the results:
sudo cat /var/lib/whoopsie/whoopsie-id
2) To confirm a WORKAROUND in 18.10, if you uninstall both light-locker
and caffeine simultaneously, is a crash still reproducible?
** Changed in: xorg (Ubuntu)
The Firefox AppArmor profile shipped in Ubuntu 18.04/bionic includes
this rule, so this should no longer be an issue.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
The Firefox AppArmor profile shipped in Ubuntu 18.04/bionic includes a
rule for /usr/share/distro-info/*.csv, so this should no longer be an
issue.
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Hello Jean-Philippe, do you still see this issue if those AppArmor
permissions are commented out?
Are you using the fglrx driver?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1553708
Has anyone observed any undesirable behavior from Firefox when access to
these mount-related DBus services is denied?
It's not clear to me why Firefox is even calling these in the first
place, and given that mounts can include NFS servers and the like, I'd
just as soon deny this access if there's
The current Firefox AppArmor profile includes the "openssl" abstraction,
which allows access to /etc/ssl/openssl.cnf. This bug should no longer
be present in Ubuntu.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
** Attachment added: "dmesg (copied after i logged in again)"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5169346/+files/dmesg.2018-07-30.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "syslog (syslog itself was too late; so prior uploaded)"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5169345/+files/syslog.1.2018-07-30
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
guiverc@d960-ubu2:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Cosmic Cuttlefish (development branch)
Release:18.10
Codename: cosmic
note: this is the same box as above; but now 18.10
a two line radeon error message appeared on the
Does this issue still occur with Firefox 60 or later? I am unable to
reproduce it on 18.04/bionic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/885211
Title:
firefox generates
I think we could really use some kind of conditional construct (IF ...
THEN ...) in AppArmor syntax. Everything being talking about here
should, ideally, be adjustable using tunables. With a debconf
configuration option, even.
Between users who want strict access control to user files, and users
For the record, Firefox 61 very much does continue to make use of
/proc//smaps (and /proc//statm) when using the about:memory
page.
I confirmed this by experimentally commenting out the AppArmor rules for
those two /proc files (motivated by comment #3 above), and subsequently
observed
** Summary changed:
- after waking from sleep i get text radeon error message then return login
screen
+ after waking from sleep i get text radeon error message then return login
screen (18.04 & 18.10)
** Description changed:
+ // this bug was reported for 18.04.
+ // I had just had it occur
I've got the same problem in Xubuntu 18.04. Two network icons appear in the
panel.
When I restart the Xfce Panel (xfce4-panel --restart), one of the two duplicate
icons goes away but it comes back especially when I resume the system after
suspend.
--
You received this bug notification because
Update to my comment #8:
The upgrade from 14.04 to 16.04 failed later again on package gconf2
dpkg: error processing package gconf2 (--configure):
dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for gconf2:
gconf2 depends on python:any;
Thanks Lonnie. Marking as "Invalid" as issue was never confirmed.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Also affected me.
In addition of doing the steps in comment #6 above, I had to do:
sudo cp libglib2.0-0_2.48.0-1ubuntu4_amd64.deb /var/cache/apt/archives/.
sudo cp ./usr/bin/dpkg /usr/bin/.
Then I could run
sudo apt-get -f install
--
You received this bug notification because you are a
This can also happen if, for some unlikely reason (like a corrupted NTFS
partition), the file system lists the same file twice. See Question
#670964
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
There is no reason to expect anything else. A live session and a fully
installed system should behave identically in this respect. My own
testing was on a fully installed Ubuntu 18.04.
** Changed in: xkeyboard-config (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
This is not a problem in Firefox 61. You can close.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1193961
Title:
Firefox fails to launch if Network Connections Aren't Established
Thanks for your reply Zlatan. Closing by marking as "Invalid" as cause
of issue was never confirmed.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
It appears that it first stops working in cups version 2.2.7 when there
is a major change in cups/auth.c.
It is still broken in the current cups github repo master branch.
I have noticed it works correctly if you disable the unix domain socket,
e.g. comment out
Listen /run/cups/cups.sock
in
I think it is done.
On Sun, Jul 29, 2018, 18:55 Paul White <1121...@bugs.launchpad.net>
wrote:
> Zlatan,
>
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug in 2013 and
> there have been many changes in Ubuntu and
Hi Srinivas,
It seems that release 18.04.1 of both Ubuntu and Lubuntu fixes this
problem, albeit with a bit of persistence, package installs, script
running, and rebooting.
The printer/scanner involved is an HP LaserJet M1132 MFP Printer/Scanner,
connected via USB cable.
Note:
I used these
Torsten,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
Anthony,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and advised that the issue resolved itself back in 2012.
We're now closing this report as being "Invalid" as the cause of the
problem was never
This log shows updated driver deployments on July 23rd coincident with
the start of the detection problems.
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784240/+attachment/5169276/+files/dpkg.log
--
You received this bug notification because you are a
This log shows that the probing detects the high resolution modes
[ 111.418] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
[ 111.418] (II) AMDGPU(0): Modeline "3840x2160"x60.0 533.25 3840 3888 3920
4000 2160 2163 2168 +hsync -vsync (133.3 kHz eP)
[ 111.418] (II)
Public bug reported:
This monitor was correctly detected and worked properly at maximum
resolution for the last 2 years, but X no longer correctly identifies
the monitor and now only proposes a maximum display resolution of
1368x768 since a recent update.
ProblemType: Bug
DistroRelease: Ubuntu
*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666
The description of bug #1181666 appears to include an ability to use
ordinary keyboard shortcuts (such as Alt-F2). This one does not. I am
indeed having this issue, but I am not able to use Alt-F2. Is
Gunnar:
Can you please make sure that NumLock is turned off when switching to Neo 2 and
let us know if that helps.
***
I tried that, and as you predicted, with NumLock turned off, the Neo 2
keyboard behaves normally.
Does that mean I can go ahead and install 18.04, and everything will be
fine?
@Ty Young,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem is no longer an issue? We'll keep this report
open awaiting any
mpb,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
It seems that your problem was fixed with the release of Chromium 51.
However, we're closing this bug report by marking it as "Invalid" as it
was never confirmed by another user.
Thank you
Islam,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2014 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Volodya,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2014 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Kai,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2014 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Colan,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2011 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
raymundolm,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2012 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue?
Lennart,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2011 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Javier,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2012 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Ian,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2012 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Zlatan,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2013 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Rev Pat,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2011 and
there have been many changes in Ubuntu and Chromium since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Somehow a +i attrib was set on the directory containing evolution and
its components. Recursively removing the +i attrib solved the problem.
No idea how it got set.
** Changed in: evolution-data-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
Thanks you for your reply.
As the cause of the bug was never confirmed I'll close this report by
marking it as "Invalid".
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Hi Mr Paul WHITE,
I vaguely remember that I reported this bug. I see it dates back to 2016.
In those days, I used to work on an HP ProBook 4540s (just as included in
the bug report)... But a very long story have I gone through ever since.
*I'm sorry I cannot tell you more about that bug.* The
The above setup work fine in Ubuntu 17.10 as well which uses cups 2.2.4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1783298
Title:
AuthInfoRequired negotiate in cups 2.2.7 in Bionic
@seb128
https://gitlab.gnome.org/GNOME/nautilus/issues/557
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1783817
Title:
Nautilus doesnt know what its doing, showing unneccesary
** Summary changed:
- recloking with nouveau driver
+ bad frequence with nvidia card (nouveau)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1782975
Title:
bad
Jason, another one from 2011 which is being closed by marking as
"Invalid" as exact cause of problem was not actually confirmed.
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Jason,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
As the exact cause of your problems was not confirmed this report is
being closed by marking "Invalid".
Thank you for helping make Ubuntu better.
Paul White
[Ubuntu Bug Squad]
**
berndhansen,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can
Phil,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2011 and
there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug report
Xwarman,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2011 and
there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
Anderson,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2011 and
there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
mrlika,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
David,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
Above comment is also directed at Chris.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/806757
Title:
package kubuntu-firefox-installer not installed failed to
install/upgrade:
Emerson,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
Jabiru,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
Tomislav,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2012 and
there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
v.miheer,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
Robert,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
qubital,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
tome,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
Ray,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug in 2012 and
there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug report
Phillip,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
Jason,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
Bruno,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
Created attachment 140871
drm/nv50: Fix backlight not working when PWM_DIV is uninitialised (v5)
Patch modified to work with 4.17.9.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
Nikki1993,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
hotalp,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this
Ubuntu & Firefox versions EOL
Reporter no longer uses Launchpad
Issue was never confirmed
So I'm marking this bug as "Invalid"
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Uqbar,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
Vivek,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
John,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug report
Yimga,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? Can this bug
1 - 100 of 103 matches
Mail list logo
