** Changed in: mesa (Ubuntu)
Milestone: None => ubuntu-18.04.1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Login screen never appears on early generation
"Wayland sessions" are a feature of the mutter package. So reassigning
there.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Someone please test:
https://packages.debian.org/sid/amd64/plymouth/download
If that fixes the problem then we know how to proceed.
** Summary changed:
- Ubuntu 18.04: gdm3 does not switch to graphics after update
+ Boot process hangs indefinitely. Never finishes.
** Changed in: plymouth
Using Ubuntu 18.10 here I can't seem to reproduce the problem. When I set:
Settings > Devices > Screen Display > Orientation
it works even in Wayland sessions.
Can you please describe in more detail what you are doing and what's not
working?
** Changed in: mutter (Ubuntu)
Status: New =>
I can't seem to reproduce the problem on 16.04 here.
Can you provide a screenshot of what you see?
** Changed in: gedit (Ubuntu)
Status: New => Incomplete
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Summary changed:
- Wayland sessions (including the login screen itself) don't start up on older
Intel GPUs (pre-Sandy Bridge)
+ Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
--
You received this bug notification because you are a member of Ubuntu
Desktop
You have been subscribed to a public bug:
When I use a Wayland session I am unable to use either Portrait mode.
I have the same problem at work using my Intel Integrated Video on my
Lenovo X230 laptop.
Given that both AMD and Intel are broken, it looks to be a regression of
some sort.
Bug #1779827 appears to be a duplicate of this.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1774957 ***
https://bugs.launchpad.net/bugs/1774957
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1774957, so it is being marked as such. Please
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
** Also affects: gdm3 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
Importance: Unknown
Status: Unknown
**
Comment #34 indeed sounds like the problem.
Does installing this package fix the bug?;
https://packages.debian.org/sid/amd64/plymouth/download
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Yousef, Canonical should and does notify people of known problems in the
release notes [1]. We only failed/forgot to mention this one and its
workaround in the release notes. Although scrolling up, it appears
nobody figured out what the workaround was until after 18.04 was
released. And even then
Public bug reported:
Dear all,
I figure out that login credentials, located in gnome-keyring, can be
easily compromised.
Linux based on Gnome basically uses ‘gnome-keyring’ as their backend to
store login credentials in a secure manner. Specifically, google-chrome
browser, network-manager and
This also affects 18.04 (updated to July 5, 2018)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724921
Title:
VLANs get incorrectly listed under Bluetooth
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Correction, I believe this is actually a bug in dbus. gnome-terminal,
and others are not setting as it should, but as far as I
know, dbus cannot support in a systemd environment due to
the limitations mentioned in #21.
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
This is a bug in every GNOME application that uses systemctl --user to
start itself. There is currently no sane fix because systemd is missing
a feature of upstart, umask inheritance. GNOME could abuse systemd's
instantiated services feature to pass the umask through this but this
would be far
https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.32-2ubuntu1
** Changed in: gtk+2.0 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
Same here. Ubuntu 18.04 on Dell E7440.
I was forced to switch to switch to lightdm, because gdm3 simply won't start.
Here're some logs:
Jul 06 00:04:07 HOSTNAME dbus-daemon[2769]: [session uid=116 pid=2769]
Activating service name='org.gnome.ScreenSaver' requested by ':1.12' (uid=116
pid=2771
Thx @ckrainey
Maybe the problem is attached to media-keys plugin of gsd:
settings - devices - keyboard - launchers - launch calculator
--> (in this case) falsely using command 'org.gnome.Calculator.desktop' or
'gnome-calculator.desktop'
Using a custom shortcut with command 'gnome-calculator'
This bug was fixed in the package evolution-data-server -
3.28.3-0ubuntu1
---
evolution-data-server (3.28.3-0ubuntu1) cosmic; urgency=medium
* New upstream version (lp: #1769637)
-- Sebastien Bacher Thu, 05 Jul 2018 17:34:36
+0200
** Changed in: evolution-data-server (Ubuntu)
Thanks @mottenkiller.
I've marked my bug, https://bugs.launchpad.net/ubuntu/+source/gnome-
settings-daemon/+bug/1773589, as a duplicate of yours since you actually
uncovered the mechanics of the problem.
** Package changed: apache2 (Ubuntu) => gnome-settings-daemon (Ubuntu)
--
You received
*** This bug is a duplicate of bug 1780308 ***
https://bugs.launchpad.net/bugs/1780308
** This bug has been marked a duplicate of bug 1780308
calculator does not start using special-key on keyboard
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
You have been subscribed to a public bug:
Hi,
just installed 18.04 on my desktop.
Using the calculator-special-key on my keyboard calculator does not start. :(
Using the menu the calc just starts as expected.
Looking for an error in gnome-logs, I found this one:
gsd-media-keys
Could not find
Have a look at this bug:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1780308
Maybe it's the same problem and the workaround also works for you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
This bug was fixed in the package gnome-calendar -
3.28.2-0ubuntu0.18.04.1
---
gnome-calendar (3.28.2-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream version (lp: #1768555)
* Remove the patch included in the new version
-- Sebastien Bacher Fri, 25 May 2018 13:29:11
The verification of the Stable Release Update for gnome-calendar 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
Oh, Ubuntu does boot on such hardware just fine. And seeing how well it
works I'd feel guilty of wasting money and polluting the environment
when buying newer hardware.
It does not boot all up into native Wayland. Nevertheless, one can run
X11 just fine.
How to turn Wayland off? Key is to
Installed linux-headers-4.15.0-23-generic, now dkms runs properly.
Re-tested w/ 4.15.0-23-generic: gdm3 STILL does not come up, just bounces
between black screen and the systemd progress messages.
So, going back to 4.15.0-23-generic does NOT solve the original issue.
I will continue w/ haveged
I'm facing the same problem on my Intel Core 2 duo E8500 with G33
graphics Ubuntu 18.04 can't boot
shouldn't canonical at least notified us that Bionic Beaver doesn't work
on old hardware so no one tries it ??
--
You received this bug notification because you are a member of Ubuntu
Desktop
This bug was fixed in the package gnome-control-center -
1:3.28.2-0ubuntu1
---
gnome-control-center (1:3.28.2-0ubuntu1) cosmic; urgency=medium
* New bugfix version (lp: #1780280)
* debian/patches/0006-build-Fix-USER_DIR_MODE-value-in-config.h.patch,
It affected lightdm as well. I run unity in 18.04 and use lighdm and the
boot time has gone from 4 secs to 4 minutes with 4.15.0-24. Brad's
workaround(#21) by installing haveged also works for lightdm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Processing triggers for linux-image-4.15.0-23-generic (4.15.0-23.25) ...
/etc/kernel/postinst.d/dkms:
Error! Your kernel headers for kernel 4.15.0-23-generic cannot be found.
Please install the linux-headers-4.15.0-23-generic package,
or use the --kernelsourcedir option to tell DKMS where it's
Going back to kernel 4.15.0-23 DOES NOT solve the gdm3 issue.
Hence the issue I reported is not solved.
Has for the _workaround_ of using lightdm in 4.15.0-23, yes, it boots faster
HOWEVER, once I installed 4.15.0-23 the bcmwl DID NOT GET BUILT/INSTALLED which
is also VERY bad, as _no WIFI_.
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
systemd. This problem was most recently seen with package version
237-3ubuntu10.1, the problem page at
https://errors.ubuntu.com/problem/4777e6fde202e742f2c75166680733e4c83a8674
contains more
Public bug reported:
Upstream released bugfix version 2.0.4. Please SRU to Bionic.
https://gitlab.gnome.org/GNOME/tracker/blob/master/NEWS
NEW in 2.0.4 - 2018-06-25
=
* libtracker-miner: Fix event emission order of the root folder when
a recursive directory is
** Summary changed:
- Update evolution-data-server to 3.28.2
+ Update evolution-data-server to 3.28.3
** Changed in: evolution-data-server (Ubuntu)
Status: Fix Released => Fix Committed
** Description changed:
Impact
==
evolution-data-server (e-d-s) has released a new stable
*** This bug is a duplicate of bug 106060 ***
https://bugs.launchpad.net/bugs/106060
http://real.emilyhaggerty.com
Greg Clark
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1163107
Title:
Wacom
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1730250
Title:
Location
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/172
Title:
control-center
I agree with monkeybrain2012. The question that must then be raised is
how this breakage got into an Ubuntu software update for the masses
almost 2 months after it was known that a kernel change had broken gdm3
login, and after commits for the underlying issues had been created in
debian.
--
You
This bug was fixed in the package gnome-disk-utility - 3.28.3-0ubuntu1
---
gnome-disk-utility (3.28.3-0ubuntu1) cosmic; urgency=medium
* New bugfix update (lp: #1780267)
-- Sebastien Bacher Thu, 05 Jul 2018 16:23:19
+0200
** Changed in: gnome-disk-utility (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
Public bug reported:
* Impact
That's part of the GNOME 3.28.2 stable updates, the details on the changes are
there
http://ftp.acc.umu.se/pub/gnome/sources/gnome-control-center/3.28/gnome-control-center-3.28.2.news
* Test case
Open all the panels and use the settings, things should keep working
Public bug reported:
* Impact
That's part of GNOME stable updates, the changes from 2. and 3 are
http://ftp.acc.umu.se/pub/gnome/sources/gnome-disk-utility/3.28/gnome-disk-utility-3.28.2.news
http://ftp.acc.umu.se/pub/gnome/sources/gnome-disk-utility/3.28/gnome-disk-utility-3.28.3.news
* Test
Public bug reported:
* Impact
That's part of GNOME stable updates, the changes from 2. and 3 are
http://ftp.acc.umu.se/pub/gnome/sources/gnome-disk-utility/3.28/gnome-disk-utility-3.28.2.news
http://ftp.acc.umu.se/pub/gnome/sources/gnome-disk-utility/3.28/gnome-disk-utility-3.28.3.news
* Test
Public bug reported:
On opening the attached file, gedit recognises it incorrectly as some
asian-specific encoding, even though the file is plain ASCII.
Ubuntu version:
Description:Ubuntu 16.04.4 LTS
Release:16.04
Gedit package version:
gedit:
Installed: 3.18.3-0ubuntu4
This is GNOME Shell on the screenshot, not GNOME Panel.
** Package changed: gnome-panel (Ubuntu) => gnome-shell (Ubuntu)
** Project changed: gnome-panel => gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
** Package changed: ubuntu => gnome-panel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1780078
Title:
Gnome 3 system menu is missing entries (sometimes)
To manage
You have been subscribed to a public bug:
On a newly upgraded Ubuntu 18.04 with Gnome 3.28, the system menu on the
right in the top panel is missing entries, if booted with an ethernet
connection. If booted without ethernet (with or without wifi) all the
entries are there.
Replicable: yes
How
** Changed in: gnome-pilot
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/15046
Title:
Gnome-pilot does not start by default
To manage
** Changed in: f-spot
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/231485
Title:
There is no easy way to get a photo's location in the file system.
To manage
** Changed in: mutter
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1724439
Title:
gnome-shell crashed with SIGSEGV in
I think it might be this bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
** Bug watch added: Debian Bug tracker #897572
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I can report a very similar experience after the update to kernel *-24.
The difference with my machine - a barebook Clevo packaged by Pioneer Computers
Australia -
is that no keyboarding, usb mouse, or touchpad use reproducably reduces the
hang time by plymouth to less than an average 90seconds.
Public bug reported:
Upstream released a bugfix 1.36.2 as part of gnome-3.28. Please SRU to
Bionic.
https://gitlab.gnome.org/GNOME/gvfs/blob/gnome-3-28/NEWS
Major changes in 1.36.2
===
* udisks2: Remove optical disc volumes/mounts if drive disappears
* daemon: Prevent
Although I might be wrong about bug bug 1727356 here. Your CPU is newer
than other people experiencing that.
Maybe see bug 1779476 instead. What happens if you wait a few minutes?
Does it eventually come up?
And what happens if you wiggle the mouse while waiting? Does it come up
sooner?
--
You
Or just:
sudo lsof | grep /dev/random
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
To manage
This command should tell you the suspicious process ID(s):
sudo ls -l /proc/*/fd/* | grep /dev/random
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1779476
Title:
Ubuntu 18.04:
Sorry, my mistake. Recent kernel changes may be the trigger of this
problem but would not be the root cause. If there is any process
blocking waiting for entropy then that's the real issue. Because they
are blocking waiting indefinitely for something that might theoretically
take forever. And
Can confirm this with GDM, without haveged, on a Lenovo Thinkpad S440:
- with kernel 4.15.0-24, GDM comes up after several minutes
- if I wiggle the touchpad, in a dozen seconds
- with kernel 4.15.0-23, immediately (no issue)
Strangely, I recall that when I first experienced this issue a couple
** Changed in: gjs (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1778660
Title:
Upgrade gjs to version 1.53.3
To manage
Also, after removing haveged, please try some older kernels:
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
and try to find the two versions closest together where one works and
the other does not.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
In trying to identify the source of the problem we will need people to
temporarily remove haveged.
Next, please reproduce the issue and just leave the machine running. Do
the graphics eventually come up after a few minutes of waiting? Please
also repeat the test but wiggle the mouse/touchpad
That's good news.
Although this bug is primarily owned by njsf so we'll wait to see what
he says. I want to make sure the original reporter is actually
experiencing the same problems as are being discussed now.
--
You received this bug notification because you are a member of Ubuntu
Desktop
68 matches
Mail list logo
