Public bug reported:
That's part of fixing bug #1732780 and making files listed in the
desktop overview for the LTS (which is currently not working and a
regression over Unity or upstream GNOME).
The proposed change uses "locate" as a backend (same as unity was doing), the
corresponding patch
David, that bug was for the version of libreoffice in the ubuntu
archive.
The snap is a different thing altogether. With it, you should be able to
access your files under /media by issuing the following command in a
terminal:
snap connect libreoffice:removable-media
Files in other locations
I also had this problem, and the newtwork was NOT down, and my distribution is
supported (Ubuntu 17.10). I have an HP LaserJet P1102.
I had to download the plugin manually and select it from hp-setup.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Yes, this is present in 17.10.
** Tags added: artful
** Changed in: appmenu-qt (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-session (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is
I have just updated Ubuntu 17.10 and LibreOffice 6.0.1.1 snap1, Rebooted my PC
(even though it did not ask for it. Tested and still do not have access to my
media/Acer files, access denied. Works fine in home directory. Also tried a
libreoffice spread sheet file (with macros) in my home
This bug was fixed in the package nautilus - 1:3.26.2-0ubuntu1
---
nautilus (1:3.26.2-0ubuntu1) bionic; urgency=medium
* New upstream version
* debian/patches/git_fat_chars.patch:
- list ‘\’ and ‘|’ as non valid on fat filesystems
*
This bug was fixed in the package gnome-software - 3.27.90-1ubuntu1
---
gnome-software (3.27.90-1ubuntu1) bionic; urgency=medium
* Merge with Debian, remaining changes:
+ debian/patches/*.patch: Various Ubuntu changes from ubuntu-master
branch - see patch headers for more
This bug was fixed in the package unity-control-center -
15.04.0+18.04.20180216-0ubuntu1
---
unity-control-center (15.04.0+18.04.20180216-0ubuntu1) bionic; urgency=medium
[ Khurshid Alam ]
* Import gnome online-accounts panel into unity-control-center (LP:
#1747897)
--
This bug was fixed in the package unity -
7.5.0+18.04.20180221.1-0ubuntu1
---
unity (7.5.0+18.04.20180221.1-0ubuntu1) bionic; urgency=medium
* Unity use track_obj to safely connect to UScreen and Settings
signals (LP: #1748330) (LP: #1748330)
* CairoBaseWindow: don't try to
** Changed in: webkit-open-source
Status: Unknown => Won't Fix
** Changed in: webkit-open-source
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to epiphany-browser in Ubuntu.
** Changed in: gnome-shell (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Confirmed
** Changed in: mutter (Ubuntu)
See also bug 1728342
** Package changed: linux (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I installed updates today and now have the same problem. After login, I
see the desktop but no dash, no launcher, no alt tab, etc.
Running:
* ubuntu 16:04
* 4.4.0-116-generic
* xserver-xorg-core: 2:1.18.4-0ubuntu0.7
* libegl1-mesa:amd64/xenial-updates 17.2.8-0ubuntu0~16.04.1 uptodate
--
You
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1752680
Title:
Night light does not work in some
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Thanks @vanvugt for keeping me organized; I have moved my issue
(https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/74) here:
https://lists.debian.org/debian-user/2018/03/msg00021.html
--
You received this bug notification because you are a member of Desktop
Packages, which is
mate-terminal and terminator have the same problem. The checkboxes for
'allow bold text' can be clicked but they do nothing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
Filed an upstream bug, at long last, in the Gnome bugtracker at
https://bugzilla.gnome.org/show_bug.cgi?id=793977
** Bug watch added: GNOME Bug Tracker #793977
https://bugzilla.gnome.org/show_bug.cgi?id=793977
** Also affects: network-manager via
Mesa is slowly getting there...
https://www.phoronix.com/scan.php?page=news_item=Intel-Lands-EGL-Ctx-
Priority
Hopefully radeon and nouveau will catch up too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
/org/gnome/terminal/legacy/profiles//allow-bold is set to false in
dconf, but the terminal continues to display boldface, rendering some
fixed-width fonts barely readable.
$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
$
Okay, so...why isn't this a priority bugfix? I love gnome, don't get me
wrong, but when I can't even autoconnect to my VPN like I did countless
times in the past few years running Ubuntu on Unity without compromising
the security of my system something is wrong. There needs to be an
option - and a
Oops. I wasn't testing the new packages yet. I guess we're waiting on:
gst-plugins-base1.0 (1.13.1-1) experimental; urgency=medium
** Changed in: gst-plugins-base1.0 (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Desktop
Thanks Laney. It was in the back of my mind -- I knew upstream had done
a fix identical to mine, but they just moved it. I had not stopped to go
looking for it...
I can verify everything seems to be working with the latest bionic
updates.
** Also affects: gst-plugins-base1.0 (Ubuntu)
I would like to find out if this is a problem in libinput.
Can you please try installing Unity (package 'unity-session')? Then log
in to Unity and tell us if the problem also occurs there?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Changed in: libinput (Ubuntu)
*** This bug is a duplicate of bug 1752053 ***
https://bugs.launchpad.net/bugs/1752053
Current "fix" / workaround, per my own post in #1752053:
I managed to fix my setup by using the Graphics Drivers PPA
(https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) and
forcing the install of
Please also look in /var/crash for any crash files.
If you find some then:
1. Apply the workaround described in bug 994921.
2. Run: ubuntu-bug /var/crash/YOURFILE.crash
3. Tell us here the ID of the newly created bug(s).
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1752431
When reporting bugs in the future please use apport by using 'ubuntu-
** Tags added: noclick
** Summary changed:
- Regression: left mouse button stops working
+ Left mouse button gets stuck down (in software), usually after suspend/resume
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libinput (Ubuntu)
This bug was fixed in the package gnome-themes-standard -
3.18.0-2ubuntu2
---
gnome-themes-standard (3.18.0-2ubuntu2) xenial; urgency=medium
* Use HighContrast icons for the HighContrast theme. (LP: #1644662)
-- Dariusz Gadomski Thu, 08 Feb 2018
I didn't have a reliable way of reproducing exactly this scenario, so I
can't definitively say whether or not it's still present (I'm currently
running 17.10). I have experienced similar GUI hangs (but ssh still
responds) in 17.10, but not specifically while watching an embedded
youtube video in
This bug was fixed in the package bamf -
0.5.3~bzr0+16.04.20180209-0ubuntu1
---
bamf (0.5.3~bzr0+16.04.20180209-0ubuntu1) xenial; urgency=medium
* bamf-window: read snap and flatpak IDs and use it to guess desktop-
id (LP: #1747802)
-- Marco Trevisan (Treviño)
The verification of the Stable Release Update for bamf has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
** Also affects: hplip
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1752727
Title:
hp-plugin fails to download plugin
Status in HPLIP:
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
I appreciate the reminder, but Ubuntu Bionic is still under development
and has not been officially released. Does it make sense to recommend
installing pre-release software right now? Perhaps it's better to
suggest installing it when it's actually released.
--
You received this bug notification
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
** Changed in: libpam-ldap (Ubuntu)
Status: Invalid => Incomplete
** Changed in: libpam-ldap (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
I had various issues with my XPS 9550 related to 3,5 jack. I hope kernel
4.14+ can fix it, but it is not officially supported for now. I tried to
install both 4.14 and 4.15 and got a ton of errors. Any suggestions on
how to proceed? Does anyone know when 4.14 becomes recommended?
--
You received
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
dino99, please don't recommend that users use Ubuntu 18.04 now. It's not
even officially in beta yet.
Also, there's no reason to recommend that users use the minimal install
option for this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1752512 ***
https://bugs.launchpad.net/bugs/1752512
@Brian Launchpad did not list #1752512 as possible duplicate for me, so
I didn't notice. marked as a duplicate now
** This bug has been marked a duplicate of bug 1752512
Plugin download failes with
I figured out why the simple test didn't work - when I first installed
Ubuntu 18.04, gnome-terminal wouldn't accept any keyboard input, I
assumed it was just a pre-alpha bug and installed terminator.
Installing terminator switched itself to the default including launching
with ctrl-alt-t , and
*** This bug is a duplicate of bug 1752512 ***
https://bugs.launchpad.net/bugs/1752512
You did read other recent bug reports, didn't you? How does yours differ
from #1752512, #1749690 and #1749573 or add new information?
Cheers,
Brian.
--
You received this bug notification because you
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
My apologies. I didn't think about an issue from nearly a year ago. I'll
be honest, I just worked around the issue by using the graphics drivers
PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
1 - 100 of 234 matches
Mail list logo