Documentation is horribly insufficient in this regard. To quote the link
given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware
enablement). It means that from 20.04.2 release Ubuntu Desktop will gain
new major kernel versions every 6 months through to summer of 2022".
The words
I filed bug #1912032 concerning the failure of nvidia drivers to install
during a fresh installation of Ubuntu 20.04.1 because when download
updates is selected it auto-updates to a 5.8 series kernel during
installation.
--
You received this bug notification because you are a member of Desktop
I updated the bug description to better explain why I believe this is a
bug, but I left the original content below the break.
** Description changed:
Beginning about January 8th Focal users that installed Focal using
either the Ubuntu 20.04 or 20.04.1 installation media began getting
I added the packaging tag because this was a packaging error in the
20.04 and 20.04.1 images.
** Tags added: packaging
** Description changed:
+ Beginning about January 8th Focal users that installed Focal using
+ either the Ubuntu 20.04 or 20.04.1 installation media began getting
+ updated to
Unfortunately apport-collect just says "no additional info collected"
(see pic added). I presume because 'ubuntu-meta' is not an installed
package? I struggled a bit trying to decide what the best way was to
report a bug like this because it's not actually a bug in the kernel
itself, it's just
Public bug reported:
Just as the title says, the 20.04 and 20.04.1 images use the HWE version
of linux-generic resulting in upgrades to the 5.8 series kernel. This
seems to effect Ubuntu only, or I should say I checked the Kubuntu,
Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
Sorry I lumped so much text into one box. I must have been asleep at the
wheel.
I was just setting up another of these today with 18.04.1 and it's also
effected but I know Xenial worked fine out-of-box so I'm just guessing
(with inadequate studying) that the change to GNOME as default resulted
in
Sorry for the delay. I performed a fresh install of 20191014 last night,
then updated it this AM so we'd be working with an out-of-box
experience. After the update and a reboot I opened System Settings >
Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to-
click to off while also
** Tags added: eoan gnome-panel
--
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/1743686
Title:
File system folder in nautilus Artful/Bionic flashback session does
nothing
Status
Public bug reported:
After installing the Eoan Beta on a Dell Latitude E6400 attempting to
set touchpad Edge Scrolling was unsuccessful. It actually seemed to work
as long as the System Settings window was left open but as soon as the
window is closed the Edge Scrolling setting reverts to off.
I
Public bug reported:
Just testing Disco and wanted to see what login options are available
after adding 'gnome-shell-extensions' and found that logging out lands
me on a black screen that's unresponsive to any keyboard input. I'll
test on some slightly different hardware soon.
ProblemType: Bug
** Description changed:
This is intentionally a duplicate of bug #1817485 to collect info on a
fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
default session is also effected. I just wanted to collect all pertinent
logs to prove that this was in fact an unmolested
One more difference between the default and flashback sessions is that
the keyboard hot-keys DO work in the default Ubuntu session, but NOT in
the flashback session. So that makes this even a lower priority, and
passes part of the responsibility onto the flashback devs.
** Tags added: gnome-panel
** Description changed:
This is intentionally a duplicate of bug #1817485 to collect info on a
fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
default session is also effected. I just wanted to collect all pertinent
logs to prove that this was in fact an unmolested
Actually only a logout is necessary for the UI and volume slider to
respond to the amp change. So I'll add steps to reproduce.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Actually this specific issue effects the default Ubuntu session as well.
I did a fresh install of 18.04.2, installed updates, rebooted, and
checked it out to be sure. Then I filed bug #1817625 so one or the other
needs to be marked a duplicate (and changed back to "new" rather than
"invalid"). I
Public bug reported:
This is intentionally a duplicate of bug #1817485 to collect info on a
fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
default session is also effected. I just wanted to collect all pertinent
logs to prove that this was in fact an unmolested install.
Bionic no longer displays allow above 100% in the sound settings UI.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1817485
Title:
Bionic "amplified" sound controls do
Public bug reported:
I'm just setting up my first Bionic HTPC and I notice that if you select
allow-amplified-volume in dconf that change only applies to the volume
slider, not to the sound control UI. This results in the volume hot-keys
not controlling sound above 100%.
So if you're watching
It seems to me that the most sensible approach would be to just remove
the Computer button from the Places menu. Then you'd just open Home and
select Other Locations. I think that would be more in keeping with the
latest Nautilus redesign.
I'm not at all sure but we may want to do likewise with
This may or may not be worth mentioning but the reason I totally purged
lightdm was just using dpkg to change to gdm3 returns an error:
lance@lance-conroe:~$ sudo dpkg-reconfigure gdm3
[sudo] password for lance:
gdm.service is not active, cannot reload.
invoke-rc.d: initscript gdm3, action
I tested again this AM beginning with a fresh install of 20180227,
applying updates, and then installing gnome-panel. During installation I
chose to auto-login so after initially logging out and selecting
flashback w/metacity I still booted the default DE.
But that was expected behavior based on
Works properly to boot both the flashback w/metacity and GNOME Classic
sessions now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1749481
Title:
Wrong session marked as
** Tags added: bionic gnome-applets
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1737836
Title:
Standard clock applet is oversized in Artful
Status in gnome-panel package in
Public bug reported:
Go to Places > Computer, left-click to open "Files", then select File
System either by double-click or right-click + open and nothing happens.
If you go Places > Home > Other locations and select Computer the file
system opens as expected.
ProblemType: Bug
DistroRelease:
Second screenshot.
** Attachment added: "Screenshot from 2017-12-12 15-23-53.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+attachment/5021860/+files/Screenshot%20from%202017-12-12%2015-23-53.png
--
You received this bug notification because you are a member of
Public bug reported:
In Artful if the standard clock applet is used there is a dead-space to
the left of it. In my first screenshot you can see the dead-space
between the indicator-applet and the clock applet. In the second
screenshot you can see I've moved the clock applet to the left and the
"This is because you didn't first upgrade update-manager."
I figured something like that. I was convinced that it must have been an
error on my part after repeating several more tests with no issue. Chalk
that up to either too little (or too much) coffee.
--
You received this bug notification
I've run several more tests today and all seems well. I can only assume
that the failure in comment #17 was an error on my part. So I think
we're good to go.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-lts-xenial in Ubuntu.
I have no idea why I had that previous failure. I've since run two more
tests. One was a repeat test beginning with a fresh install of Ubuntu
GNOME 14.04.3 i386 (just like above) and it worked fine. I ran another
test beginning with a fresh install of Ubuntu GNOME 14.04.2 amd64 and it
also worked
I still encountered a failure beginning with Ubuntu GNOME Trusty i386
w/Vivid HWE. There was a kernel upgrade prior to performing the HWE
upgrade (most recent prior updates performed on 2016-08-07 followed by
installing update-manager from proposed):
Start-Date: 2016-08-13 09:58:41
Commandline:
@ andyczerwonka, you need to file a new bug report. Since you mention
both nVidia and Intel I assume you have hybrid graphics which presents a
whole different situation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1584509 ***
https://bugs.launchpad.net/bugs/1584509
** This bug has been marked a duplicate of bug 1584509
hybrid CDs/DVDs not mounted in xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This has no longer been an issue since 16.04 final was released so
marking it invalid.
** Changed in: unity-control-center (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Tags added: util-linux
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1577768
Title:
16.04 some dvd do not mount automatically (but do in 14.04)
Status in gvfs package in Ubuntu:
I wonder why we stopped checking regular mtab:
util-linux (2.27.1-1) unstable; urgency=medium
* Imported Upstream version 2.27.1
- among other things includes these fixes:
libmount: fix uid= and gid= translation (Closes: #801527)
libmount: (monitor) don't check for regular mtab
Might this be a duplicate of bug 1537918?
I'm far from having anything figured out but wonder if there is an issue
with UDF support in both the 4.2 and 4.4 series kernels? Or maybe this
is just a gvfs or fuse problem?
--
You received this bug notification because you are a member of Desktop
It's an umbrella rather than a specific package, so:
lance@lance-AMD-desktop:~$ apt-cache policy xorg-lts*
xserver-xorg-lts-vivid:
Installed: (none)
Candidate: 3:10
Version table:
3:10 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
xserver-xorg-lts-wily:
I suspect bug 1561420 is also a duplicate.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-lts-transitional in Ubuntu.
https://bugs.launchpad.net/bugs/1571677
Title:
upgrading caused a broken apt cache due to *-lts-vivid packages
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Kyle Brophy (kylebrophy) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1507255
Title:
I opened bug 1565780 to address the missing nautilus preferences menu in
Xenial.
--
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/1274740
Title:
Re-enable traditional titlebar on
Public bug reported:
As the title says, the nautilus preferences menu can't be accessed in
the flashback session. You can't edit a number of settings without going
to dconf-editor of playing with gsettings. Just a few examples:
#1: Can't change sort folders before files setting
#2: Can't change
In Wily if you set auto login to on during installation the first boot
would ask for a password. Then if you checked the user UI in System
Settings it said it was turned on but it wasn't. So if you toggled it
off, then rebooted, then opened the user UI again and toggled it on the
auto login would
@ Phillip Susi, if that's an indication that this bug won't be fixed in
Trusty then please change the status from Triaged to Won't fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
It's OK in Ubuntu Xenial. Do I really need to install and check Ubuntu
Wily?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1487819
Title:
Wily user UI shows auto-login off after
Since in a normal GNOME session you access "preferences" and some other
things by right-clicking on the nautilus tab in the top bar when
nautilus is open, how would that be accessible in gnome-flashback?
--
You received this bug notification because you are a member of Desktop
Packages, which is
@ Tim Lunn, there is another nautilus bug that affects both gnome-shell
and gnome-flashback, bug #1554171.
--
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/1274740
Title:
Re-enable
Sorry Tim, I forgot to mention this is a flashback problem. I brought
the issue up on their mailing list.
--
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/1274740
Title:
Re-enable
I notice that Nautilus > preferences can't be accessed in Xenial, sort
of like Nautilus should be using the Unity style menus rather than those
used by gnome-shell???
As far as I've seen ATM only Nautilus is affected by that in Xenial but
I need to have a closer look at some of the other GNOME
@ jerrylamos, which HWE stack is in use? It mostly depends on what
installation media is used (unless physical action is taken to upgrade
the HWE stack):
https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A14.04.x_Ubuntu_Kernel_Support
Based on my most recent results it seemed to
** Tags added: xenial
** Tags added: gvfs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1069964
Title:
Two processes attempt to mount blank optical discs
Status in
Xenial looks good testing Ubuntu GNOME 20160218 amd64:
ubuntu-gnome@ubuntu-gnome:~$ uname -a
Linux ubuntu-gnome 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
ubuntu-gnome@ubuntu-gnome:~$ apt-cache policy xserver-xorg-video-intel
It took a considerable amount of searching but the sna vs uxa issue does
have at least two upstream bug reports:
https://bugzilla.redhat.com/show_bug.cgi?id=1226531
https://bugzilla.redhat.com/show_bug.cgi?id=1226743
I believe that should be sufficient. It's a known issue. I'll have to
look at
Ubuntu Trusty 20160217 amd64 is still affected so I doubt that a fix
will land for 14.04.4. That will be problematic for less advanced users
affected because both the Wily and the updated Trusty images offered
from the main download page(s) will fail to work.
To me the obvious simple "workaround"
As far as reporting upstream to move the status from incomplete back to
confirmed - I have no idea what I'm doing :^(
Is this an X bug as originally thought? Or a kernel bug as now seems to
be the case? I clearly can't create a new bugzilla account and file a
bug report when I have no idea what
I took time to check Wily and the results are similar. This bug is
present with the 4.2.0-27.30 kernel but the 4.2.0-29.31 kernel is OK.
So I'm guessing the updated intel driver fails to build properly with
kernels prior to 4.2.0-29
--
You received this bug notification because you are
Looking at the 14.04.4 RC again this AM I find that the 4.2.0-29.23
kernel is OK, but this bug is present with 4.2.0-27.21. So this is
apparently not so much an X bug as a kernel bug??
AFAIK Xenial is (or at least has been) affected by this also and I'll be
testing the Beta 1 candidates next
Lubuntu Trusty is affected to a much lesser degree so I was at least
able to install it. I'm going to try the newest kernel from proposed
tomorrow.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
I changed the title to more properly represent the underlying problem.
As mentioned above I suspect this is a duplicate of (or related to)
either bug 1477593 or bug 1498146. In fact one or the other of those
might be a duplicate of the other. Currently the Wily HWE stack seems to
be working OK in
I was surprised testing the Trusty Daily Ubuntu GNOME 20160207 amd64
image to find that it works OK in a live session so just making a note
for my own use regarding version:
xserver-xorg-video-intel-lts-wily
2:2.99.917+git20150808-0ubuntu4~trusty2
--
You received this bug notification because
I believe this is just a side-effect of the nvidia driver not installing
properly with the 4.2, 4.3, or 4.4 series kernels. I found this in
JournalErrors:
Jan 29 07:26:56 username-AMD-desktop kernel: nvidia: module license 'NVIDIA'
taints kernel.
Jan 29 07:26:56 username-AMD-desktop kernel:
This only occurs if using the nvidia-304 graphics driver. It does not
occur if I use the nouveau driver. The nvidia driver also fails to
provide the proper screen resolution.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
I get this crash trying to open System Settings in Xenial. The System
Settings UI fails to open and apport takes over.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic
I'll try Unity after switching back to the nvidia driver. I've had to
use flashback w/metacity with the nouveau driver because the Unity DE
freezes within just a minute or two while using the nouveau driver.
--
You received this bug notification because you are a member of Desktop
Packages,
The default Unity DE fails to load altogether with the nvidia driver, it
just bounces right back to the login screen. Unity does load with the
nouveau driver activated but it slows to a crawl and eventually just
freezes. But that hardware has never been able to run Unity w/nouveau
(llvmpipe /
Not surprisingly this also affects the Trusty dailies based on testing
Ubuntu GNOME Trusty 20160124 amd64 since they have the Wily HWE. So the
flavors participating may want to mention it in their release notes,
recommending that users affected use the archived 14.04.1 images.
** Tags added:
Still affects Ubuntu GNOME Xenial 20160121 amd64. So I guess I'll have
to create a Bugzilla account and try to figure out their bug filing
process when I have time.
** Tags added: amd64 xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is
Yes, I think this is (or at least was) fixed in Xenial. I can't be
certain because I haven't been able to use any iso since the 4.3 series
kernel rolled out and I really need to get a fresh install working at
some point because the testing install I'm using is long in the tooth
and has been
Thanks Alberts, I see now that it's OK using the Ambiance theme but
borked in Numix so I'll give them time to catch up.
** Changed in: metacity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
This is an extremely minor issue but I notice in Xenial when using the
main menu button rather than the standard Menu Bar the username
displayed in the menu tree just displays a blank limb when you mouse
over it. A picture is worth a thousand words in this instance so I'm
Public bug reported:
In Xenial I notice with compositing switched off several apps (nautilus,
gedit, totem, gnome-tweak-tool, system-monitor & empathy) have a huge
black border as shown in the attached screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: metacity 1:3.18.1-1ubuntu2
Still affecting Ubuntu GNOME 20151020 Wily installs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1487819
Title:
Wily user UI shows auto-login off after selecting on during install
I incorrectly staed above:
"The graphics are so badly garbled I can only file this bug on an
unaffected OS where I've held back the update on just that one package
to about Alpha 2 status"
That should have said "Beta 1 status" so I'll correct that accordingly.
** Description changed:
This
Public bug reported:
This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The graphics
are so badly garbled I can only file this bug on an unaffected OS where
I've held back the update on just that one package to about Alpha 2
status:
lance@lance-INTEL-desktop:~$ apt-cache policy
This was actually a duplicate of bug #1381232.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1502570
Title:
gnome-panel indirectly installs evolution
Status in gnome-panel
Still affects Wily.
** Tags added: wily
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1443723
Title:
GNOME clock displays improper date format for US/EN locale
Status in
Still effects Wily so I updated the title and tags.
** Tags removed: utopic
** Tags added: vivid wily
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1381232
Title:
Utopic
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed = Fix
I wonder if this could be an accountsservice issue as Sebastien Bacher
discovered in bug #1245915?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1487819
Title:
Wily user UI shows
Public bug reported:
Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
spite of selecting auto-login = on during installation when the
installation is complete and after first boot opening Settings Users
the UI shows off, but auto-login is working properly and if you toggle
This does still effect Ubuntu Ubuntu Mate Wily as well as Debian Mate
Jessie. I'll try to file a Debian bug report ASAP (it'll be my first).
Anyone that has suggestions might find my forum post useful:
http://ubuntuforums.org/showthread.php?t=2280658
The challenge is trying to figure out what
Hi Tim, I assume that Nautilus (or Caja in the case of Ubuntu Mate) is
actually responsible for the media already mounted warning because if
you open dconf-editor and go to org/gnome/desktop/media-handling (or
org/mate/desktop/media-handling) and change both automount and
automount-open to false
** Tags added: caja ubuntu-mate wily
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1069964
Title:
Two processes attempt to mount blank optical discs
Status in OEM Priority Project:
** Summary changed:
- Unable to mount Blank CD-R disc. Location is already mounted.
+ Two processes attempt to mount blank optical discs
** Description changed:
+ This behavior can be reproduced using either a live USB or an installed
+ version of the effected flavors. Simply insert a blank
I've tested both the Lubuntu 20150330 i386 and amd64 images on two
totally different sets of hardware.
Both fail to boot to the live DE on this hardware:
Intel Atom CPU 230 @ 1.60GHz
Intel 82945G/GZ Integrated Graphics Controller (rev 02)
Intel N10/ICH 7 Family High Definition Audio Controller
No idea why the explanatory text disappeared with comment #24 but that's
a pic of what the screen displays when the i386 image freezes.
This pic is what the screen displays when the amd64 image freezes.
** Attachment added: freeze_amd64.JPG
** Attachment added: freeze_i386.JPG
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361870/+files/freeze_i386.JPG
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1291644 ***
https://bugs.launchpad.net/bugs/1291644
Public bug reported:
Apport just asked if I wanted to file this report after booting the
Lubuntu Vivid image. I said yes in hopes that some info may be provided
in regards to bug #1432843.
ProblemType:
Actually a variant of this still exists in Ubuntu GNOME Vivid (as of
20150318) the difference being that, instead of getting the already
mounted warning as you do in a flashback session, in a GNOME Shell
session if you click the close button on the Open with CD/DVD creator or
Eject notification as
Public bug reported:
The menus in flashback appear bloated and can't be properly edited.
Even the menus and buttons have icons settings aren't applied as they
should be. Also the Power Off and Restart menu buttons don't work so I
suspect that we're using the wrong schema?
This may be somewhat of
Other way to fix is simply to patch gnome-panel and set it to always
show images in menus.
I think that would be preferable. To me it always just looks odd that
those few objects in the tree view have no icons whereas all the other
objects do. Of course that was a change made in GNOME 2 some
It looks good now. I even started with a fresh install of the 20150302
amd64 image and tried every display manager test I could imagine. This
also fixes bug #1425779.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in
Logout works fine if I boot using the systemd boot option from the
advanced grub menu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1425779
Title:
Ubuntu GNOME Vivid logs out to a
Unlocking screen works fine if I boot using the systemd boot option from
the advanced grub menu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1425350
Title:
Ubuntu GNOME
BTW it's not hardware related as I've done two bare metal installs on
totally different hardware - one being an encrypted/LVM install and the
other using manual partitioning.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session
This is not limited to encrypted installs. I just did a plain manual
install and got the same thing.
** Summary changed:
- Ubuntu GNOME encrypted install - password won't unlock screen
+ Ubuntu GNOME Vivid - password won't unlock screen
** Description changed:
I'm testing Ubuntu GNOME Vivid
Additionally if I select logout I just go to a nearly blank screen and
can't even call a TTY, and if auto-login is turned off after entering
the password apport tries to report a bug but it's un-reportable:
lance@lance-AMD-desktop:~$ ls /var/crash
_usr_sbin_gdm.0.crash
Could bug #1421991 be
Additionally if I select logout I just go to a nearly blank screen and
can't even call a TTY, and if auto-login is turned off after entering
the password aport tries to report a bug but it's un-reportable:
lance@lance-AMD-desktop:~$ ls /var/crash
_usr_sbin_gdm.0.crash
--
You received this bug
Oops, didn't know some content had been auto-saved.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1425350
Title:
Ubuntu GNOME Vivid - password won't unlock screen
Status in
1 - 100 of 275 matches
Mail list logo
