Public bug reported:
I am running 3 monitors under wayland.
2x 1440p monitors at 1x scale (one of these is my primary display)
1x 4k laptop at 2x scale
The majority apps seem to not get correct scaling on the 2x display.
gnome-control-center is the one that seems to work correctly. Things
like
OK after digging further through the logs, it seems that at some point
NetworkManager lost the vpn "HMAC Authentication" Cipher setting.
not sure if this was caused during the Dist upgrade or switching to IWD.
I will report further on this once I upgrade second laptop to Groovy.
--
You received
** Description changed:
Since upgrading to groovy my openvpn connection out to our corporate is
not working.
I was testing Iwd but have now reverted to wpa_supplicant.
- Connection to the vpn succeeds and routing table gets setup no traffic
- is flowing over the connection and I get
Public bug reported:
Since upgrading to groovy my openvpn connection out to our corporate is
not working.
I was testing Iwd but have now reverted to wpa_supplicant.
Connection to the vpn succeeds and routing table gets setup no traffic
is flowing over the connection and I get the following
** Attachment added: "sources.list from focal lp sbuild chroot"
https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1872163/+attachment/5351720/+files/sources.list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
At some stage fairly recently my Focal schroots have broken due to the
sources.list file that is now included. I will attach this file, however
it looks like the standard distro source.list file vs the single liner
version I have in my eoan schroots.
Reverting to a single
** Changed in: ubuntu-gnome-default-settings (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868721
Title:
Unknown Tag in
** Summary changed:
- Use "monospace 11" instead of "ubuntu mono 13"
+ Use "Source Code Pro 11" instead of "ubuntu mono 13"
** Description changed:
+ The default upstream GNOME font is "Source Code Pro" these days.
+
+ Will consider switching to this once its packaged in Debian/Ubuntu.
+
+ ==
The default upstream GNOME font is "Source Code Pro" these days.
Would consider switching to this but it is not currently packaged in
Debian/Ubuntu.
** Bug watch added: Debian Bug tracker #736681
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736681
** Also affects: debian via
This has been switched to the default Ubuntu themes starting with Focal
20.04
** Changed in: ubuntu-gnome
Milestone: yakkety => None
** Changed in: ubuntu-gnome-default-settings (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: ubuntu-gnome
Status: Triaged => Won't Fix
--
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new
** Changed in: ubuntu-gnome
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652539
Title:
Ubuntu GNOME should install flatpak by default
To manage
This has been fixed since the 16.10.1 release of this package.
** Changed in: ubuntu-gnome-default-settings (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this probably just needs configuration
https://www.fosslinux.com/4216/how-to-automount-hard-disk-partitions-in-
ubuntu.htm
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
That is not a vanilla GNOME desktop session you are running there.
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842267
we have switched to the default Ubuntu grub/plymouth themes in focal
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616511
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu
This package is intended to provide a vanilla/upstream GNOME experience.
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Clocks does as of atleast 3.36 have a background service now. Alarms
will work after closing the app, however from my testing they do not
currently work after a reboot even though the service is running (prior
to relaunching the app).
--
You received this bug notification because you are a
: Sun, 05 Apr 2020 16:20:39 +1000
Changed-By: Tim Lunn
Maintainer: Ubuntu GNOME Developers
https://launchpad.net/ubuntu/+source/ubuntu-gnome-meta/0.86
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870902
Title:
Switch to default Ubuntu plymouth theme
To manage
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869315
Title:
Log-in screen is wrongly themed in Ubuntu 20.04
there was some discussions around this in LP: #1764596.
No one ever stepped up to do the work though, I don't have time to work
on it but happy to sponsor patches.
** Changed in: ubuntu-gnome-meta (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you
I have uploaded a fix for this. should filter through to the archive in
the next day or so.
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With the recent upgrades of plymouth in Ubuntu 20.04 the old Ubuntu
GNOME plymouth theme is a bit flaky on some systems.
I am going to switch the vanilla-gnome-desktop to use the Ubuntu
plymouth theme, to ease maintenance.
new installs will get the Ubuntu theme.
upgrades
*** This bug is a duplicate of bug 1868914 ***
https://bugs.launchpad.net/bugs/1868914
** This bug has been marked a duplicate of bug 1868914
package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1868914 ***
https://bugs.launchpad.net/bugs/1868914
** This bug has been marked a duplicate of bug 1868914
package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
~focal4 update on ppa should fix gdm3 theme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868914
Title:
package vanilla-gnome-default-settings 18.10.1 failed to
install/upgrade: installed
Caleb, try the package from my PPA, that is the archive version you are
removing which is known to be broken currently. That should resolve
install/removal issues.
There are still issues with gdm3 using ubuntu theme and plymouth boot
logo is missing (probably will remove the old ubuntu gnome boot
Thanks for your bug report.
I am working on update to this package that includes a fix for this
issue.
You can test from my ppa for now ppa:darkxst/ppa, will upload to the
main archives after a bit more testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
Thanks for your bug report. This package was originally Ubuntu-Gnome default
settings and at that time contained a small selection of overrides we chose to
keep for that project.
It would probably worth reviewing the remaining overrides as a larger
collective and perhaps there are others
The Ubuntu-gnome seeds can be found here:
https://code.launchpad.net/~ubuntu-gnome-dev/ubuntu-seeds/+git/ubuntu-gnome
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764596
Title:
I had the same issue a few weeks ago, now however with 3.31.92 (on
Disco) I do get the configuration dropdown when selecting my HDMI Audio
device. It came up blank initially, but appears to have saved the
correct setting since.
--
You received this bug notification because you are a member of
Hi Peter,
Thanks for your bug report.
I was one of the original authors the system-monitor extension however
no longer actively involved in the project. gnome-shell extensions are
not supported by Canonical/Ubuntu (unless they are installed in the
default session) or GNOME. You would need to
Probably the tracker patch needs to be updated, there seem to be a
couple of new modules using tracker that didnt exist when I wrote that
patch.
Upstream last I check only supports optional tracker at build time. Not
run-time detection like we did in distro patches in Ubuntu.
--
You received
** Bug watch added: Debian Bug tracker #908800
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800
** Also affects: nautilus via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
thumbnailers are working fine for me, both tiff and jpg, perhaps there
is still a missing dependency, that is normally otherwise pulled in by
vanilla-gnome-desktop. I generally only test gnome3-staging on systems
with that meta package.
Can you file a separate bug for nautilus not starting
can you try reinstall tracker 2.1.3 and see if that file exists on your
filesystem? If it doesnt please run apport-collect which should
colllect your dpkg/apt logs.
see this page for manually getting backtraces
https://wiki.ubuntu.com/DebuggingProgramCrash
On 12/09/18 18:06, Harry wrote:
> I
Hi Harry,
Thank you for your bug report.
I am running nautilus 3.30 with tracker 2.1.3 on two system and they
are both working, so we will need some more info. Thumbnails are working
also
That default.rule file does exist in the tracker 2.1.3-1~cosmic1
package, is it not installed on
Yes have been testing on cosmic.
they are both on gnome3-team/gnome3-staging ppa. Tracker is at 2.1.3
there, but has already my patch that was the only change in 2.1.4.
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+sourcepub/9389719/+listing-archive-extra
Public bug reported:
To go along with GNOME 3.30
This can now be synced from Debian as there is no remaining delta.
gnome-contacts is not seeded in any flavours.
** Affects: gnome-contacts (Ubuntu)
Importance: Wishlist
Status: New
** Tags: upgrade-software-version
--
You
Public bug reported:
To go along with the rest of GNOME 3.30
Both tracker and tracker-miners 2.1.4 will be synced from Debian.
tracker is not installed by default on any Ubuntu Flavours, but does
provide an important part of the GNOME-Shell experience.
These releases bring lots of fixes and a
Hugh, that is a different bug, please file a new bug for that using
`ubuntu-bug gnome-session`.
also you should be installing vanilla-gnome-desktop rather than ubuntu-
gnome-desktop (which will transition you to the new ubuntu gnome-shell
experience). Although I expect you would still see the
What did you upgrade from? I think the banner would be set in
/etc/gdm3/greeter.dconf-defaults these days
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774215
Title:
adding a security banner key
*** This bug is a duplicate of bug 1770909 ***
https://bugs.launchpad.net/bugs/1770909
** This bug has been marked a duplicate of bug 1770909
reorder keybindings to show upstream defaults in gnome-control-center
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1770909 ***
https://bugs.launchpad.net/bugs/1770909
** This bug has been marked a duplicate of bug 1770909
reorder keybindings to show upstream defaults in gnome-control-center
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
We have some keybinding overrides that add alternatives
to WM actions. These were apparently inherited from Unity.
in some cases the alternate keybinding is listed before the upstream
default. Which causes the alternate keybinding to be displayed in gnome-
control-center
Public bug reported:
We have some keybinding overrides that add alternatives
to WM actions. These were apparently inherited from Unity.
in some cases the alternate keybinding is listed before the upstream
default. Which causes the alternate keybinding to be displayed in gnome-
control-center
Public bug reported:
We have some keybinding overrides that add alternatives
to WM actions. These were apparently inherited from Unity.
in some cases the alternate keybinding is listed before the upstream
default. Which causes the alternate keybinding to be displayed in gnome-
control-center
the gdm greeter/login screen and the lock screen are mostly independent.
The gdm greeter runs its own instance of gnome-shell running in a
special gdm mode.
The lock screen is drawn by the current gnome-shell session and thus
uses the current gnome-shell theme.
What gnome-shell theme are you
I have tested the package in proposed and it installs correctly as
expected.
vanilla-gnome-desktop has always depended on gnome-session, and vanilla-
gnome-default-settings is pretty tightly coupled to vanilla-gnome-
desktop, you wouldnt normally install it manually, but rather vanilla-
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
There is a fix pending for this bug waiting on SRU approval.
https://launchpadlibrarian.net/367853119/ubuntu-gnome-default-settings_18.04.0_source.changes
The recommended workaround in the interim would be:
apt-get install gnome-session
apt-get install vanilla-gnome-desktop
(don't try and
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
Bogdan, there is a fix pending on bug 1761014 (which this bug is marked
a duplicate of)
https://launchpadlibrarian.net/367853119/ubuntu-gnome-default-
settings_18.04.0_source.changes
--
You received this
** Changed in: ubuntu-gnome-default-settings (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761014
Title:
package vanilla-gnome-default-settings
** Description changed:
- Installing this package failed with an error setting an alternative to a
- CSS file
+ [Impact]
+ vanilla-gnome-default-settings will fail to install, if gnome-session has not
been configured yet, since that package installs the upstream gdm3 css
alternative
-
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
*** This bug is a duplicate of bug 1761014 ***
https://bugs.launchpad.net/bugs/1761014
** This bug has been marked a duplicate of bug 1761014
package vanilla-gnome-default-settings 17.10.4 failed to install/upgrade:
installed vanilla-gnome-default-settings package post-installation script
The bzr branch is the source for generating the meta package (vanilla-
gnome-desktop)
The source package ubuntu-gnome-meta, has an 'update' script that reads
the seed from bzr and generates the package lists that are used by
germinate to produce the final meta packages.
So the basic process is
Hi Michael,
I would be happy for apps to be downgraded to Recommends, if you have a look
at the seed[1] alot are already marked recommends (Recommends are the ones
marked like "* (gnome-weather)". Overall the selection that are marked
Recommends is a little inconsistent and this could
** Changed in: ubuntu-gnome-meta (Ubuntu)
Status: New => Confirmed
** Changed in: ubuntu-gnome-meta (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
also includes libzip 1.5.1 release from today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674057
Title:
[FFe] upgrade libzip to version 1.5.0
To manage notifications about this bug go to:
I landed this in a silo, at Laney's request.
https://bileto.ubuntu.com/#/ticket/3230
ignition-fuel-tools:s390x is dep wait, as it also is in the archive,
everything else built fine on all arches.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is
Changing back to confirmed, we still need to work out what to do with
smbpasswd.
** Changed in: nautilus-share (Ubuntu Bionic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- [UIFe] Delete the password for the live session on all flavors
+ Delete the password for the live session on all flavors
** Description changed:
- UI Freeze Justification
-
+
A historical Ubuntu GNOME bug fix deleted the password for the
** Description changed:
- Right now, only when gdm3 is installed is a systemd unit created to run
- passwd -d. This is preferable over having a blank password because it
- provides consistency between Desktop and flavors, and it makes it
- quicker to use a tty (and less confusing for people who
Packaging should be good to go now, pending FFe approval. All remaining
debian/patches are upstream cherry-picks that will be included in next
upstream release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have created a transition tracker (copied from Debian)
http://people.canonical.com/~ubuntu-archive/transitions/html/libzip.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674057
Title:
[FFe]
** Description changed:
Feature Freeze Justification
This release fixes to two CVE's and most notably has removed its custom AES
crypto implementation with using openssl libraries. It is for the security
reasons I am requesting this FFe this late in the cycle.
I have manually tested this editing initramfs and it seems to work.
[Test Case]
1. Login to a tty should not require you to press "enter" at the password:
prompt (for blank password)
2. Under gnome-shell you should not be able to lock the screen with
or through the user menu
** Patch
I have been liasing with upstream to sort of the few remaining issues,
they have been super responsive, and for the the most part those are
fixed upstream, I will update the packaging with upstream fixes once I
get back into range of a power point! in the next day or three.
--
You received this
- sed -i '/^[UG]ID_MIN/s/\<1000$/ 999/' /root/etc/login.defs
That ensures the gdm greeter will display the live user, it should remain gdm
specific.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Feature Freeze Justification
This release fixes to two CVE's and most notably has removed its custom AES
crypto implementation with using openssl libraries. It is for the security
reasons I am requesting this FFe this late in the cycle.
** Bug watch added: Debian Bug tracker #894813
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894813
** Also affects: libzip (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894813
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Description changed:
Feature Freeze Justification
This release fixes to two CVE's and most notably has removed its custom AES
crypto implementation with using openssl libraries. It is for the security
reasons I am requesting this FFe this late in the cycle.
** Description changed:
Feature Freeze Justification
This release fixes to two CVE's and most notably has removed its custom AES
crypto implementation with using openssl libraries. It is for the security
reasons I am requesting this FFe this late in the cycle.
** Patch added: "debdiff against version 1.3.2 in Debian experimental"
https://bugs.launchpad.net/ubuntu/+source/libzip/+bug/1674057/+attachment/5101199/+files/libzip_1.5.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Please consider upgrading libzip to the newest version (currently 1.20).
- It comes with important changes (details here:
- https://nih.at/libzip/NEWS.html) and also it's used by ark since commit
- ee74c157daf3604277ffcf10d2a89b2b59556dd7:
+ Feature Freeze Justification
** Summary changed:
- [needs packaging] upgrade libzip to version 1.20
+ [FFe] upgrade libzip to version 1.5.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674057
Title:
[FFe] upgrade libzip to
>From a quick look not sure how feasible this is to get into Bionic this
late in the cycle?
Quick Summary of changes (https://libzip.org/news/):
- There is a 1.3.2 build in Debian experimental, but hasnt progressed into
unstable yet
- A couple of CVE fixes (these should probably be
OP said that this also affects Xubuntu and Lubuntu so its not likely
only gnome-settings-daemon involved here, since neither of them use it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758647
With the removal of the pam-smbpass module there is no longer any
syncing of Ubuntu/System accounts into Samba. This means to get password
protected shares working after installing samba the user would need to
run:
sudo smbpasswd -a
Keeping in mind that there is password sync the other way (on
hmm, did they change it to alt+, ? atleast that is what it seems to be
on my system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758950
Title:
Ctrl+, keyboard shortcut doesn't work in bionic
To
I would also, but don't think that is likely to happen in time for
bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754803
Title:
[FFe] Disable telepathy support in gnome-contacts
To manage
/var/log/gdm is still used as a fallback in case journald is unavailable
or disabled. Unless upstream remove that I don't think we should remove
it from the packaging.
** Changed in: gdm3 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
gdm still runs under wayland by default. It is the "Ubuntu" login
session that defaults to Xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756061
Title:
'/var/log/gdm3/': Permission denied
To
gdm logs to systemd journal these days.
You need to enable debugging in /etc/gdm3/custom.conf to get any useful logs
though
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756061
Title:
Here is a patch to fix vanilla-gnome task. Had to jump through a few
hoops to generate it, since lubuntu does not have a bionic seed
apparently, so the debian/rules update target is broken.
** Patch added: "tasksel-fix-vanilla-gnome.debdiff"
98 matches
Mail list logo