Public bug reported:
Boot time is greatly impacted by a media detection timer for a SD/MMC
card reader with no media inserted.
DEVICE:
[1.857492] scsi host6: usb-storage 1-9:1.0
[1.857539] usbcore: registered new interface driver usb-storage
[1.858178] usbcore: registered new
It has been my experience, lately, that individuals or families sharing
a computer have a single login account, i.e. "Family", etc.. This is
probably due to the perception by such simple-needs $USER's or their
family I.T. guru, that--it is the easiest way to overcome the reasonable
and appropriate
If I invite you into my house(physical), then I don't expect you to go
through my filing cabinets or closets, when I'm not looking, without
explicitly giving you those "permissions(0755)".
"Good fences make good neighbours" and "Locks keep out only the honest"
are equally true.
Placing
Whoa...Robbie, I'm just looking out for all the new user's and admin's
that are coming in from other platforms that could reasonably be
surprised by this and not Unix/Linux veteran's who broke their teeth
with vi on Slackware, etc..
Believe it or not, with WSL-2 and other notable advancements of
*** This bug is a duplicate of bug 48734 ***
https://bugs.launchpad.net/bugs/48734
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wow! Approaching 13-years and counting on this bug. Neat.
Desktop Linux: The principle of least astonishment (POLA) should
_always_ be priority-one with Security. Open $HOME's are a surprise to
me and everyone I know.
Now that cloud storage has taken the desktop users of the world by
storm, is
@macbreeze you might want to open a bug for the xfce4-session package or
the xubuntu meta package as this one is targeting the gnome-shell
package. LightDM has settings in /etc/lightdm for overriding which
monitor is used for the login widget and xrandr tool may help in the
session after login.
** Description changed:
+ WORKAROUND:
+
+ $ sudo dpkg-reconfigure libdvd-pkg
+
+
ERROR:
libdvd-pkg: Downloading orig source...
I: libdvdcss_1.4.2
/usr/bin/wget --tries=3 --timeout=40 --read-timeout=40 --continue -O
libdvdcss_1.4.2.orig.tar.bz2 \
-
e the root scan the scanner was
> detected as an epkowa driven unknown model, after the root scan it is
> detected with the proper model name.
>
> @ Chris Rainey: regarding the Brother MFP, I can confirm that I ran the
> installer script and not the available deb packages.
>
> --
Just a reminder to those of us using Brother DCP or MFP's: I repeatedly
find that the only way to properly install the printer and scanner drivers
is to use the "Installer Script"(i.e. 09/13/2018
(2.2.1-1)) provided on the model downloads page(see below) and to follow
the directions given
@Simon: apologies, if your previous comment is directed at me. I'm
currently on Ubuntu 19.04(Gnome 3) without a proper XFCE4 installation
to test this on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
~$ file examples.desktop
examples.desktop: UTF-8 Unicode text
Does not open or spawn content in: /usr/share/example-content/
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: example-content 50
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux
@vanvugt: not sure if #136 is directed at my comment in #135, but the
_only_ way to produce the problem is to logout or reboot which naturally
involves the display manager. Again, the problem goes away, for my case,
simply by using a different display manager, as stated in #131.
The problem is
@Steve Langasek please see my original bug for the details of why I believe
this package should be removed unless upstream will update to latest
released version:
https://bugs.launchpad.net/ubuntu/+source/stjerm/+bug/1717013
I followed directions given by Jeremy Bicha to request removal of the
Our setup:
1. Older GPU(Integrated Intel® HD Graphics 2000)
2. Always using some sort of display multiplexer(splitter) on VGA out to
dual TV’s, previously, now only single local monitor on VGA and 4K
Tx(wireless) on HDMI out to a projector, currently.
Thoughts:
1. Could the splitter or
I find that primary(left-clicking) up to 15 or 20+ times _eventually_
spawns the pkexec-gui box.
On Wed, Mar 20, 2019 at 9:26 AM Bjoern H. <1727...@bugs.launchpad.net>
wrote:
> I have this issue both in 18.10 and 19.04. Using arrows and space does
> not work, the only workaround I've found is
Another workaround, here:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423
Use slick-greeter(lightdm), etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625600
Title:
** Description changed:
- WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
- screensaver + numlockx(optionally)
+ WORKAROUND
+
+ Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver +
+ numlockx(optionally)
+
TL;DR
+
+ Correct positioning and
** Summary changed:
- monitors.xml is not parsed or applied correctly after reboot or shutdown
+ monitors.xml is not parsed or applied correctly during login after reboot or
shutdown
** Description changed:
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
screensaver
** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #474
https://gitlab.gnome.org/GNOME/gdm/issues/474
** Also affects: gdm via
https://gitlab.gnome.org/GNOME/gdm/issues/474
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
** Description changed:
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
screensaver + numlockx(optionally)
TL;DR
After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
monitor to the VGA port of a DELL Optiplex 390 desktop tower, connecting
@seb128 I have edited the bug description to provide more information on
how the issue is triggered. The bug occurs during the handoff of gdm3
---> gnome-shell(mutter?) _after_ login. The issue is repeatedly and
consistently triggered until GDM(gdm3) is replaced by LightDM(slick-
greeter) and then
** Description changed:
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
screensaver + numlockx(optionally)
- ERROR(syslog) = "Failed to get current display configuration state:
- GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
-
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820423
Title:
monitors.xml is not parsed or applied correctly after
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
screensaver + numlockx(optionally)
Greeter will auto-appear on whichever screen your mouse is on or moves
to, dynamically.
See: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423
--
You received this bug
** Description changed:
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
- screensaver
+ screensaver + numlockx(optionally)
ERROR(syslog) = "Failed to get current display configuration state:
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
WORKAROUND FOR UBUNTU 18.10(clean install):
Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver +
numlockx(optionally)
See: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
screensaver
ERROR(syslog) = "Failed to get current display configuration state:
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
"org.gnome.Mutter.DisplayConfig" does not exist"
Agreed. And with the latest versions of Ubuntu proper collecting
telemetry at first login, I wonder if this tool should simply be removed
from the archives or is somebody still using it for development
purposes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
More info here, as well:
If I only set the "Switch off after" Display setting to >1 Minute and leave
the other settings("Blank after" and "Put to sleep after") at 0(Never),
then the display wakes up normally!
This was tested on the originally affected system(s) and required no
customized
@Forrest Voight: Awesome write-up. Thanks!
On Sat, Feb 16, 2019 at 3:05 AM Forrest Voight
wrote:
> I looked into this issue at length and posted a write-up here:
> http://forre.st/brother_printer
>
> The gist of it is that setting up a Brother printer with an invalid
> model name (e.g.
OK, just circling back around to this as of today, 02/07/2019:
It appears that just by having Xscreensaver installed, although disabled
in the autostart items of the session manager, can inhibit the use of
the other items further down in the /usr/bin/xflock4 script(i.e. slock).
So . . . after
Public bug reported:
surf "Suggests: apparmor, apparmor-profiles-extra", but it needs to
depend on 'apparmor-profiles-extra' or the service unit fails to start:
Feb 05 12:56:59 CKR-1 systemd[1]: Starting AppArmor initialization...
-- Subject: Unit apparmor.service has begun start-up
--
** Description changed:
After a clean install of 18.10, ubuntu-restricted-extras(which depends
on this pkg) and libdvd-pkg, I am unable to play an encrypted DVD movie.
I assumed that all needed packages would be installed at this point, but
I came to find out that
Public bug reported:
After a clean install of 18.10, ubuntu-restricted-extras(which depends
on this pkg) and libdvd-pkg, I am unable to play an encrypted DVD movie.
I assumed that all needed packages would be installed at this point, but
I came to find out that "gstreamer*-plugins-bad" was
[SOLVED]
Just needed to:
$ sudo apt install gstreamer1.0-plugins-bad
I'm not sure why this isn't included in the restricted-extras or libdvd-pkg
depends?
** Summary changed:
- DVD playback error: unable to play . . . DVD source is required . . .
+ [SOLVED] DVD playback error: unable to
* CORRECTION * It is necessary to specify the class or instance for
correct application of preferences when logging in to a fresh session
due to the app defaults in:
/etc/X11/app-defaults/XClock*
>From the xclock man page:
"WIDGETS
In order to specify resources, it is useful to know
Here's my current resource file for what I like at the moment:
~$ cat .Xresources
*background: #00
*foreground: #ff
XClock*majorColor: #66
XClock*minorColor: #44
XClock*hourColor: #88
XClock*minuteColor: #88
XClock*secondColor: #22
Public bug reported:
lubuntu-desktop needs to depend on lxlock since lxhotkey is pre-
configured to call it via 'Ctrl-Alt-l' by default after a clean install
of "Lubintu 18.04.1".
It is confusing to a new user that no setting of a HotKey for
'lxsession-default lock' works out-of-the-box.
http://popcon.ubuntu.com/ is updating as of: Last generated on Mon Dec
31 01:30:12 2018 UTC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067277
Title:
popcon.ubuntu.com: Ubuntu Popularity
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
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
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
*** This bug is a duplicate of bug 1067277 ***
https://bugs.launchpad.net/bugs/1067277
** This bug has been marked a duplicate of bug 1067277
popcon.ubuntu.com: Ubuntu Popularity Contest statistics is out of date
--
You received this bug notification because you are a member of Ubuntu
@David Henningsson (diwic): we haven't heard from you on this bug in
over 3-years. If you are still tracking this issue here and would like
to keep doing so, please change the 'Status' of this bug to 'Confirmed'.
Thanks!
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Incomplete
I'm using a stock Ubuntu 18.10 installation(although I'm using the openbox
window-manager) in an Xorg display server session. When I fire up a
gnome-terminal and type:
$ xclock -rv
I get a reversed video xclock which has all hands visible and appears to be
the 'reverse' of a standard xclock
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
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
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
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
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in
Seems to be working normally and without any workarounds in Ubuntu
18.10.
** Changed in: x11-apps (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
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
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
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
https://cgit.freedesktop.org/xorg/xserver/commit/?id=45fb3a934dc0db51584aba37c2f9d73deff9191d
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been
https://cgit.freedesktop.org/xorg/xserver/commit/?id=45fb3a934dc0db51584aba37c2f9d73deff9191d
** Changed in: numlockx (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
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
$ dpkg -l | grep dvdcss
ii libdvdcss-dev:amd64 1.4.2-1~local
amd64library for accessing encrypted DVDs -
development files
ii libdvdcss2:amd64 1.4.2-1~local
amd64library for accessing
@Daniel: sorry . . . forgot to mention that ubuntu-restricted-extras(which
depends on *-addons) _is_ installed. I also ensured that all other
dependencies are installed according to:
https://help.ubuntu.com/stable/ubuntu-help/video-dvd-restricted.html.en
This definitely feels like a regression..
** Also affects: totem (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809044
Title:
DVD playback error: unable to play . . . DVD source is
Public bug reported:
Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards,
to complete compilation.
Inserted known-good DVD and clicked on "Open in Videos" which launched
the Totem player.
Error msg: "Unable to play the file, DVD source is required, but is not
installed."
Upstream bug-watch(Launchpad does not track GitLab, so here it is):
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/124
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711538
Title:
Just some additional thoughts brought to you by the work of the fella's
over at the LXQt project on this same issue:
TL;DR: systemd-logind may not be inhibiting long enough for screen-
lockers to complete. Variable adjustments can be made.
1.
Migrated upstream to: https://gitlab.gnome.org/GNOME/gsettings-desktop-
schemas/issues/4
** Changed in: gdm
Importance: Medium => Undecided
** Changed in: gdm
Status: Expired => New
** Changed in: gdm
Remote watch: GNOME Bug Tracker #785855 => None
--
You received this bug
As Launchpad has _not_ been updated to track GNOME bugs which have been
migrated to GitLab, I'm posting an upstream bug which can also be
tracked for this issue:
https://gitlab.gnome.org/GNOME/gdm/issues/325
** Bug watch added: GNOME Bug Tracker #785855
Public bug reported:
I've observed many end-users who are confused by the lack of ability to
"Tap-to-Click" on their touchpads at the login screen after boot(and
screen-lock?). Most---if not all, of these users are migrating from MS
Windows or another system which does prevent this technique.
In
I just figured-out how to get "apport-autoreport.service",
"whoopsie.service" & "systemd-networkd-wait-online.service" starting
correctly on a networkd(netplan)-only(NetworkManager.service _disabled_
system) desktop which uses WiFi and a static-ip on Ubuntu 18.10 Desktop.
I'm commenting here in
All that was needed for my Brother DCP-L2550DW was to 'apt purge' the
manually installed drivers:
$ sudo apt --auto-remove purge brscan4 dcpl2550dwpdrv
Then *BE SURE* to use the Brother installer script:
linux-brprinter-installer-2.2.1-1.gz
(or whatever your current version is from the
See comment #3
** Changed in: simple-scan (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/1805039
Title:
[SOLVED] Simple Scan segfaults when scanning on
***
SOLVED !!
***
All that was needed was to 'apt purge' the manually installed drivers:
$ sudo apt --auto-remove purge brscan4 dcpl2550dwpdrv
Then *BE SURE* to use the Brother installer script:
linux-brprinter-installer-2.2.1-1.gz
(or whatever your current version is from the
Output from simple-scan run in debug mode:
$ simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:638: Starting Simple Scan 3.30.1.1, PID=29211
(simple-scan:29211): Gtk-WARNING **: 14:56:04.684: Failed to register client:
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register
Public bug reported:
Simple Scan seg-faults when scanning at 24-bit(Photo) depth using the
latest driver for my:
Model: Brother DCP-L2550DW
Driver: brscan4-0.4.6-1.amd64.deb
$ grep -i scan /var/log/syslog
Nov 25 12:42:45 CKR-1 systemd-udevd[496]: Invalid rule
*WORKAROUND* in Ubuntu 18.10:
$ sudo -i
# software-properties-gtk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797649
Title:
receive authentication canceled in terminal when changing options in
Public bug reported:
I've switched from using "apt-get ..." to just "apt ..." for cli package
management. apt-get will auto-complete an option such as "apt-get
--auto..." but apt, alone, will not.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bash-completion 1:2.8-1ubuntu1
@Theo: Thanks for your help.
On Fri, Nov 9, 2018 at 10:15 AM Theo Linkspfeifer <
1801...@bugs.launchpad.net> wrote:
> I did not spot anything relevant in your log files either.
>
> Sadly, no idea how to debug this further also.
>
> ** Package changed: light-locker (Ubuntu) => xorg-server
Public bug reported:
Keyboard setting for "Launch Calculator" does _not_ work for snap
installed "gnome-calculator".
WORKAROUND:
$sudo apt install gnome-calculator && sudo snap remove gnome-calculator
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.30.1-1ubuntu2
#17 works on clean install of 18.10.
** Also affects: ubuntu-restricted-extras (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713615
Title:
Public bug reported:
ERROR:
libdvd-pkg: Downloading orig source...
I: libdvdcss_1.4.2
/usr/bin/wget --tries=3 --timeout=40 --read-timeout=40 --continue -O
libdvdcss_1.4.2.orig.tar.bz2 \
http://download.videolan.org/pub/libdvdcss/1.4.2/libdvdcss-1.4.2.tar.bz2 \
||
Public bug reported:
Without a 'sleep 1' before +dpms command, slock or xtrlock, etc. will
cause a laptop backlight to immediately reactivate.
description: Notebook
product: 4180AP3
vendor: LENOVO
version: ThinkPad T420
*-firmware
description: BIOS
** Attachment removed: "light-locker_lightdm.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210057/+files/light-locker_lightdm.out
** Attachment removed: "light-locker_seat0-greeter.out"
lightdm & syslog(relevant sections only), attached. I saw nothing
suspicious, although the lightdm.log seemed to have the most relevant
entries.
Also,
$ sleep 1 && xset dpms force off
works normally and as expected.
On Tue, Nov 6, 2018 at 11:56 AM Theo Linkspfeifer <
** Attachment added: "light-locker_x-0.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210060/+files/light-locker_x-0.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "light-locker_x-1.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210061/+files/light-locker_x-1.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "light-locker_syslog.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210059/+files/light-locker_syslog.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
lightdm & syslog(relevant sections only), attached. I saw nothing
suspicious, although the lightdm.log seemed to have the most relevant
entries.
Also,
$ sleep 1 && xset dpms force off
works normally and as expected.
** Attachment added: "light-locker_lightdm.out"
** Attachment added: "light-locker_seat0-greeter.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210058/+files/light-locker_seat0-greeter.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Theo, thanks for the follow-up. In answer to your question:
YES! "dm-tool lock" produces exact same result.
$ killall light-locker
$ dm-tool lock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, upon reflection, it would seem that the actual issue is _not_ a
failure to switch to VT8, as I can blindly enter passwd and return to
session. It would seem that the video driver is simply not coming out of
+dpms mode. I will update the title to better reflect that.
** Summary changed:
-
** Also affects: ubuntu-mate-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801629
Title:
xubuntu-core needs to depend on cryptsetup and
** Summary changed:
- Dual monitors(vga+HDMI) fail to wake after screen-lock(no system-suspend)
+ Fails to VT-switch back to lightdm after user initiated wake-up events(not
system-suspended, just locked)
** Summary changed:
- Fails to VT-switch back to lightdm after user initiated wake-up
Works as expected in Xubuntu 18.10. Must be something in the ubuntu-
session policykit/PAM/systemd auth?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797649
Title:
receive authentication canceled
S looking forward to Sean's xfce4-screensaver @ https://github.com
/xfce-mirror/xfce4-screensaver !!
If you are reading this, please help test this *new* program.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- xubuntu-core needs to depend on cryptsetup and lvm2 or 'apt autoremove' will
make a LUKS+LVM encrypted system non-bootable
+ xubuntu-core needs to depend on cryptsetup and lvm2 or 'apt autoremove' will
make a LUKS+LVM encrypted root partition non-bootable
** Description
Confirming that this problem exists on two different systems. Both
systems(desktop and laptop) are using an Intel video card year 2009 or
newer.
Additionally, it would seem that the real issue is that light-locker or
some sub-system is not switching the display back to VT-8, as I can wake
the
Ok. I've added deja-dup to my Xubuntu 18.04 installs and I can confirm
that it integrates well and works. Seems to me like it would be a safe
addition to the Xubuntu desktop recommends.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Xubuntu needs to depend on full LibreOffice suite for modern office needs
+ Xubuntu needs to depend on full LibreOffice(Impress(PowerPoint), etc.)) suite
for modern office needs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- Xubuntu needs a better num lock handler at login and during user session
+ Xubuntu needs a better numlock handler at login and during user session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In a fresh/clean install of Xubuntu 18.10, if an unsuspecting user runs
'apt autoremove', it will remove 'cryptsetup' and 'lvm2' making the
system non-bootable at next restart if an encrypted(LUKS+LVM) drive was
selected during the ubiquity installer wizard:
$ sudo apt
1 - 100 of 199 matches
Mail list logo
