[Bug 1831495] [NEW] LVM pauses for a long time during boot for a "Generic- SD/MMC/MS PRO" with no media inserted
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 interface driver uas [1.981335] usb 1-10: new full-speed USB device number 4 using xhci_hcd [2.131529] usb 1-10: New USB device found, idVendor=8087, idProduct=0aa7, bcdDevice= 0.01 [2.131530] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.872111] scsi 6:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [2.872343] sd 6:0:0:0: Attached scsi generic sg2 type 0 [2.877942] sd 6:0:0:0: [sdb] Attached SCSI removable disk ERRORS: /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[469]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 e2scrub_reap[749]: /dev/sdb: open failed: No medium found ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lvm2 2.03.02-2ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 Date: Mon Jun 3 15:22:34 2019 InstallationDate: Installed on 2018-11-23 (191 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to eoan on 2019-05-30 (4 days ago) ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Also affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Description changed: - Boot time is greatly impacted by a non-existent media detection timer - for a SD/MMC card reader. - + 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 interface driver uas [1.981335] usb 1-10: new full-speed USB device number 4 using xhci_hcd [2.131529] usb 1-10: New USB device found, idVendor=8087, idProduct=0aa7, bcdDevice= 0.01 [2.131530] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.872111] scsi 6:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [2.872343] sd 6:0:0:0: Attached scsi generic sg2 type 0 [2.877942] sd 6:0:0:0: [sdb] Attached SCSI removable disk ERRORS: /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[469]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 e2scrub_reap[749]: /dev/sdb: open failed: No medium found ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lvm2 2.03.02-2ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 Date: Mon Jun 3 15:22:34 2019 InstallationDate: Installed on 2018-11-23 (191 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to eoan on 2019-05-30 (4 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831495 Title: LVM pauses for a long time during boot for a "Generic- SD/MMC/MS PRO" with no media inserted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1831495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48734] Re: Home permissions too open
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 account isolation techniques, by default, in Windows or macOS. I suggest that the same could be true for Ubuntu and it would hardly be noticed, except by experienced *nix $USERS, most of whom-- would already know how to twiddle the appropriate bits, if needed, to open their $HOMES. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48734] Re: Home permissions too open
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 convenience-over-privacy, by default, in this post-GDPR / Facebook & Twitter leaks / Equifax breach / Edward Snowden & Julian Assange(perhaps heroes to those of us in the USA), etc. seems to be unconscionable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48734] Re: Home permissions too open
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 Ubuntu
coming on to the radar of mainstream and mostly Microsoft-trained
admin's, we have an _opportunity_ here to create mindshare and loyalty
for migrations of huge workloads to our platform-of-choice and,
arguably, the best platform for safer and more secure computing as
opposed to having the majority of PC users in the world stay on one
company's monoculture-vision of desktop computing.
I'm attempting to spread the Gospel-of-GNU(Ubuntu) everywhere. We're on
the same team, my friend.
Obscure wiki articles and 13-year old "opinion"-marked bugs will _not_
be the first place new admins or users will find out about this issue!
Heck, I've been a Linux user since 2004("Red Hat 8"(before Fedora was
even a thing) box-set purchased at a CompUSA store), then Slackware and
an Ubuntu convert since 2012 or so. I should know better than to leave
multi-user seats unaudited for permissions after creation(or even during
by not having edited the adduser.conf file). But even I just _assumed_
that a modern desktop would surely put security ahead of convenience! I
didn't even know that this "security" issue was a "feature" till I
started setting-up multi-user local seats and even then--I may have just
started using ecryptfs as a workaround. Now--even that option is gone
from user(admin)-facing installer widgets.
Put yourself in the shoes of a new or migrating small to medium sized
business CIO or IT-manager looking to convert from the soon-to-be out-
of-service "Windows 7" in order to keep fleets of older boxes running
for daily knowledge-worker or office-productivity users who share
desktop PC's over the course of 24/7 shifts at the office. What would
you think if every system that you had installed or understood to be the
out-of-box defaults for the past few decades was based on blocking vs
allowing? And you took the risk of allowing this "Linux-
thing"(yes...this is what I have heard it called many times) only to
discover the opposite, a permissive rule set, without any warning.
Ubuntu is growing rapidly...I want to see it succeed despite it's geeks-
only reputation. I think sensible defaults are good to always be working
on(not just "opining" about in 13-year old bugs).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/48734
Title:
Home permissions too open
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829624] Re: Default permissions(0755 / umask=0022) allow other users to access files behind a password protected user account after login
*** 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. https://bugs.launchpad.net/bugs/1829624 Title: Default permissions(0755 / umask=0022) allow other users to access files behind a password protected user account after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1829624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48734] Re: Home permissions too open
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 the need to have open(r-x) $HOME dirs still needed? We've lost the 'Guest" user login since 18.04 and we've lost ecryptfs as an option in the installer. Why not just throw a simple toggle into the installer, to surface this issue, offering admins the option? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
@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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802321] Re: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting...
** 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 \ - http://download.videolan.org/pub/libdvdcss/1.4.2/libdvdcss-1.4.2.tar.bz2 \ - || /usr/bin/uscan --noconf --verbose --rename --destdir=/usr/src/libdvd-pkg --check-dirname-level=0 --force-download --download-current-version /usr/share/libdvd-pkg/debian + http://download.videolan.org/pub/libdvdcss/1.4.2/libdvdcss-1.4.2.tar.bz2 \ + || /usr/bin/uscan --noconf --verbose --rename --destdir=/usr/src/libdvd-pkg --check-dirname-level=0 --force-download --download-current-version /usr/share/libdvd-pkg/debian --2018-11-08 08:54:43-- http://download.videolan.org/pub/libdvdcss/1.4.2/libdvdcss-1.4.2.tar.bz2 Resolving download.videolan.org (download.videolan.org)... 2a01:e0d:1:3:58bf:fa02:c0de:5, 88.191.250.2 Connecting to download.videolan.org (download.videolan.org)|2a01:e0d:1:3:58bf:fa02:c0de:5|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 366824 (358K) [application/octet-stream] Saving to: ‘libdvdcss_1.4.2.orig.tar.bz2’ libdvdcss_1.4.2.orig.tar.bz2 100%[>] 358.23K 731KB/sin 0.5s 2018-11-08 08:54:44 (731 KB/s) - ‘libdvdcss_1.4.2.orig.tar.bz2’ saved [366824/366824] libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.4.2.orig.tar.bz2: OK libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... - WORKAROUND: - - $ sudo dpkg-reconfigure libdvd-pkg - libdvd-pkg: Checking orig.tar integrity... - /usr/src/libdvd-pkg/libdvdcss_1.4.2.orig.tar.bz2: OK - libdvd-pkg: Unpacking and configuring... - libdvd-pkg: Building the package... (it may take a while) - libdvd-pkg: Build log will be saved to /usr/src/libdvd-pkg/libdvdcss2_1.4.2-1~local_amd64.build - Current: = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read+ep - Bounding set =cap_chown,cap_dac_override,cap_fowner,cap_wake_alarm,cap_block_suspend,cap_audit_read - Securebits: 024/0x14/5'b10100 - secure-noroot: no (unlocked) - secure-no-suid-fixup: yes (unlocked) - secure-keep-caps: yes (unlocked) - uid=0(root) - gid=0(root) - groups=0(root) - libdvd-pkg: Installing... - Selecting previously unselected package libdvdcss-dev:amd64. - (Reading database ... 240177 files and directories currently installed.) - Preparing to unpack .../libdvdcss-dev_1.4.2-1~local_amd64.deb ... - Unpacking libdvdcss-dev:amd64 (1.4.2-1~local) ... - Selecting previously unselected package libdvdcss2:amd64. - Preparing to unpack .../libdvdcss2_1.4.2-1~local_amd64.deb ... - Unpacking libdvdcss2:amd64 (1.4.2-1~local) ... - Setting up libdvdcss2:amd64 (1.4.2-1~local) ... - Setting up libdvdcss-dev:amd64 (1.4.2-1~local) ... - Processing triggers for libc-bin (2.28-0ubuntu1) ... - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libdvd-pkg 1.4.2-1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 08:56:58 2018 InstallationDate: Installed on 2018-11-08 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: libdvd-pkg UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802321 Title: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvd-pkg/+bug/1802321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
@luca.mg: have you checked for firmware updates? My Brother DCP-L2550DW can update from the web interface in the system tools/administration tab and there have been a few updates in the last year. On Tue, May 7, 2019 at 2:45 PM luca.mg wrote: > @ PeterPall: regarding the Epson scanner, yes it could be the firmware > upload, the first root scan took time, I thought it was the scanner > warming up longer than usual and not catching up, but I allowed time and > it finally went through, so You may very well be right. I did not run > lsusb -v, just a plain lsub, but before 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. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1728012 > > Title: > Many 3rd party scanner drivers are broken by a sane change > > Status in sane-backends package in Ubuntu: > Confirmed > > Bug description: > Many scanners can no more be used since sane has changed something: > The 3rd-party plug-in the vendor provides as .deb package will still > install. But the scanner is no more recognized. > > Scanners that are affected are(besides others): >- Epson Perfection V10 >- Epson Perfection V1000 >- Epson WorkForce GT-1500 >- Brother MFC-8510DN >- Epson Perfection V33 > > It is to note that the probability that the scanner manufacturers fix > things others broke is below 100%. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libsane1 1.0.27-1~experimental2ubuntu2 > Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 > ApportVersion: 2.20.7-0ubuntu3.1 > Architecture: amd64 > Date: Fri Oct 27 12:35:52 2017 > EcryptfsInUse: Yes > SourcePackage: sane-backends > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
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 _explicitly_(to-the-letter, no exceptions)! I've tried to install a recently updated scanner driver(i.e. 01/21/2019 (0.4.7-1)) by itself as an upgrade to the currently installed one and even re-ran the setup command(i.e. Brsaneconfig4 -a name=(name your device) model=(model name) ip=xx.xx.xx.xx) for my network(Wi-Fi) DCP-L2550DW, but it does not work that way. I can't stress, enough, the apparent need to re-run the "Installer Script", exactly as shown--below, in order for everything to work! How to Install Step1. Download the tool.(linux-brprinter-installer-*.*.*-*.gz) The tool will be downloaded into the default "Download" directory. (The directory location varies depending on your Linux distribution.) e.g. /home/(LoginName)/Download Step2. Open a terminal window. Step3. Go to the directory you downloaded the file to in the last step. By using the cd command. e.g. cd Downloads Step4. Enter this command to extract the downloaded file: *Command: gunzip linux-brprinter-installer-*.*.*-*.gz* e.g. gunzip linux-brprinter-installer-2.1.1-1.gz Step5. Get superuser authorization with the "*su*" command or "*sudo su*" command. Step6. Run the tool: *Command: bash linux-brprinter-installer-*.*.*-* Brother machine name * e.g. bash linux-brprinter-installer-2.1.1-1 MFC-J880DW Step7. The driver installation will start. Follow the installation screen directions. When you see the message "Will you specify the DeviceURI ?", For USB Users: Choose N(No) For Network Users: Choose Y(Yes) and DeviceURI number. The install process may take some time. Please wait until it is complete. On Tue, May 7, 2019 at 7:41 AM PeterPall <1728...@bugs.launchpad.net> wrote: > Then perhaps uploading the firmware to the scanner can only be done as > root, for some reason. > Does the output of susb -v change after scanning for the first time? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1728012 > > Title: > Many 3rd party scanner drivers are broken by a sane change > > Status in sane-backends package in Ubuntu: > Confirmed > > Bug description: > Many scanners can no more be used since sane has changed something: > The 3rd-party plug-in the vendor provides as .deb package will still > install. But the scanner is no more recognized. > > Scanners that are affected are(besides others): >- Epson Perfection V10 >- Epson Perfection V1000 >- Epson WorkForce GT-1500 >- Brother MFC-8510DN >- Epson Perfection V33 > > It is to note that the probability that the scanner manufacturers fix > things others broke is below 100%. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libsane1 1.0.27-1~experimental2ubuntu2 > Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 > ApportVersion: 2.20.7-0ubuntu3.1 > Architecture: amd64 > Date: Fri Oct 27 12:35:52 2017 > EcryptfsInUse: Yes > SourcePackage: sane-backends > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802138]
@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. https://bugs.launchpad.net/bugs/1802138 Title: xflock4 needs a 'sleep 1' before 'xset dpms force off' to prevent backlight from immediately reactivating To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-session/+bug/1802138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826040] [NEW] examples.desktop file is not executable and only opens into default text editor(gedit)
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 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 12:46:47 2019 Dependencies: InstallationDate: Installed on 2019-04-22 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: example-content UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: example-content (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826040 Title: examples.desktop file is not executable and only opens into default text editor(gedit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/example-content/+bug/1826040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
@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 clearly related to the display manager process as it starts up the user session and is directly responsible for _causing_ the issue for me. If I use a different display manager with gnome-session(mutter), the monitor settings work correctly. To be clear: I don't care which monitor the login box widget is displayed on. I care about the monitor/display orientation _after_ I successfully login. slick-greeter = works gdm3 = not working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1728241] Re: stjerm project is abandoned(unmaintained) upstream -- please remove from archives
@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 package as seen here: https://bugs.launchpad.net/ubuntu/+source/stjerm/+bug/1727768 On Wed, Apr 17, 2019 at 2:20 PM Steve Langasek wrote: > What bugs, specifically, do you believe justify this package's removal > from the archive? > > There are only two other bug reports open against the package, neither > of which at a glance seems particularly severe. > > The package does not appear to be causing maintenance problems for the > Ubuntu release (it builds from source; it has no obsolete library > dependencies). > > It doesn't seem necessary to remove this package from the archive. > > ** Changed in: stjerm (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1728241 > > Title: > stjerm project is abandoned(unmaintained) upstream -- please remove > from archives > > Status in stjerm package in Ubuntu: > Incomplete > > Bug description: > Please remove this outdated and unmaintained package from the Ubuntu > archives due to bugs and lack of upstream maintenance. > > Upstream: https://github.com/stjerm/stjerm > > ProblemType: Bug > DistroRelease: Ubuntu 17.04 > Package: stjerm 0.16-0ubuntu2 > ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 > Uname: Linux 4.10.0-37-generic x86_64 > ApportVersion: 2.20.4-0ubuntu4.5 > Architecture: amd64 > Date: Sat Oct 28 09:48:28 2017 > EcryptfsInUse: Yes > InstallationDate: Installed on 2017-09-19 (39 days ago) > InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 > (20170412) > SourcePackage: stjerm > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/stjerm/+bug/1728241/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728241 Title: stjerm project is abandoned(unmaintained) upstream -- please remove from archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stjerm/+bug/1728241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1292398] Re: Second screen position isn't saved from one session to another
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 wireless transmitter be inducing some sort of delay or interference with the EDID detection of the monitors expected by gdm3 + gnome-session + mutter in an X11 session? 2. What is slick-greeter doing differently from gdm3 that avoids this problem? 3. Does LightDM differ from slick-greeter all that much? On Thu, Apr 18, 2019 at 07:15 Christopher Nelson wrote: > To reproduce it, try switching the order of your displays. For example, > make the display on port 0 be on the right of the display on port 1 > (instead of the "natural" order of 0=left, 1=right.) I also notice that > changing the orientation of the primary display to "portrait right" > causes problems, whereas landscape or portrait left don't. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1292398 > > Title: > Second screen position isn't saved from one session to another > > Status in elementary OS: > Fix Released > Status in GNOME Settings Daemon: > Incomplete > Status in GNOME Shell: > Confirmed > Status in Ubuntu GNOME: > Confirmed > Status in Ubuntu GNOME trusty series: > Confirmed > Status in Ubuntu GNOME xenial series: > Confirmed > Status in Ubuntu GNOME Flashback: > Confirmed > Status in Unity: > New > Status in gnome-settings-daemon package in Ubuntu: > Triaged > Status in gnome-shell package in Ubuntu: > Confirmed > Status in mutter package in Ubuntu: > Confirmed > > Bug description: > (Noticed on Ubuntu 14.04 beta 1 GNOME) > At work I have a second screen, which I prefer to virtually put on the > left side of my laptop screen. > Using gnome-control-center I can change the position of the second > without problem. > But when I disconnect the second screen (to work on another place) and > then connect it again > OR if I just power off the laptop and turn it on again, > the second screen position is set back to the default right position. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: gnome-control-center 1:3.6.3-0ubuntu53 > ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 > Uname: Linux 3.13.0-17-generic x86_64 > ApportVersion: 2.13.3-0ubuntu1 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Fri Mar 14 08:50:00 2014 > InstallationDate: Installed on 2014-03-01 (12 days ago) > InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 > (20140226) > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
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 "sudo software-properties- > gtk". Would be happy to provide any details that could be useful. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1727908 > > Title: > Software & Updates application does not permit changes on the "Other > Software" tab > > Status in gnome-shell package in Ubuntu: > Confirmed > Status in software-properties package in Ubuntu: > Confirmed > > Bug description: > > On the "Other Software" tab, I am unable to select "Canonical Partners". > Similarly, the other checkboxes on the "Other Software" can not be > clicked. > Clicking on a checkbox has no effect, and a dialog requesting the admin > password is not presented. > > However, activating or deactivating checkboxes on other tabs causes an > authorization dialog to be presented to the user. > > I experience this bug in an an Xorg session. > > sources.list and sources.list.d have the following permissions: > -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list > drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d > > All files in sources.list.d have the following permissions as this > example: > -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list > > $ lsb_release -rd > Description: Ubuntu 17.10 > Release: 17.10 > > $ apt-cache policy software-properties-gtk > software-properties-gtk: > Installed: 0.96.24.17 > Candidate: 0.96.24.17 > Version table: >*** 0.96.24.17 500 > 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 > Packages > 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 > Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: software-properties-gtk 0.96.24.17 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Uname: Linux 4.13.0-16-generic x86_64 > NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu3.1 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Thu Oct 26 22:45:09 2017 > InstallationDate: Installed on 2017-10-26 (1 days ago) > InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful > Aardvark" > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: software-properties > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625600] Re: ~/.config/monitors.xml is not applied at startup in Gnome Fallback
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: ~/.config/monitors.xml is not applied at startup in Gnome Fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1625600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] Re: 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 + numlockx(optionally) + WORKAROUND + + Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + + numlockx(optionally) + TL;DR + + Correct positioning and working of multiple displays until reboot or + shutdown and then subsequent login from gdm3. HDMI monitor(projector) + goes blank and the VGA monitor only shows 'Secondary' monitor screen + without any user visible controls or windows as they are all being + painted to the now blanked 'Primary' HDMI connected display. + + + REPRODUCTION 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 a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a FHD projector and then configuring the logical monitor layout in the "Displays" settings dialog, I can successfully create and use a multi - monitor setup in my current session. However, upon a reboot or power - cycle of the computer and a successful login from GDM(gdm3), the HDMI - goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even - though I set it as 'Primary' in the "Displays" dialog. The monitors.xml - file, attached, shows the correct layout and survives the reboot without - alteration. I am unable to see anything on the 'Primary' display, which - has incorrectly been given to the HDMI projector. Unseating the HDMI - cable does not restore the VGA to 'Primary' display automatically and I - must reboot the computer while leaving the HDMI unplugged in order to - restore my ability to see the 'Primary' display on the VGA connection. + monitor setup in my current session. + + However, after a reboot or power cycle of the computer and a successful + login from GDM(gdm3), the HDMI goes dark(blank?) and the VGA monitor + shows as 'Secondary' monitor even though I set it as 'Primary' in the + "Displays" dialog. + + The monitors.xml file, attached, shows the correct layout and survives + the reboot without alteration. + + I am unable to see anything on the 'Primary' display, which has + incorrectly been given to the HDMI projector. Unseating the HDMI cable + does not restore the VGA to 'Primary' display automatically and I must + reboot the computer while leaving the HDMI unplugged in order to restore + my ability to see the 'Primary' display on the VGA connection. + Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is repeatedly provable through multiple reboots or changes to the logical layout of the screens in the 'Displays' settings of gnome-control- center. - ERRORS(syslog) = "Failed to get current display configuration state: + + ERRORS(syslog) + + "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 - CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP - Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA - as primary monitor and HDMI(wireless Tx) as secondary to projector and - then apply custom monitor positioning using g-c-c "Displays" panel. - - RESULT = correct positioning and working of multiple displays until - reboot or shutdown and then subsequent login from gdm3. HDMI - monitor(projector) goes blank and the VGA monitor only shows 'Secondary' - monitor screen without any user visible controls or windows as they are - all being painted to the now blanked 'Primary' HDMI connected display. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: WORKAROUND Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + numlockx(optionally) TL;DR Correct positioning and working of multiple displays until reboot or shutdown and then subsequent login from gdm3. HDMI monitor(projector) goes blank and the VGA monitor only shows 'Secondary' monitor screen without any user visible contro
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown
** 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 + 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 - a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a 4K + a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a FHD projector and then configuring the logical monitor layout in the "Displays" settings dialog, I can successfully create and use a multi monitor setup in my current session. However, upon a reboot or power cycle of the computer and a successful login from GDM(gdm3), the HDMI goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even though I set it as 'Primary' in the "Displays" dialog. The monitors.xml file, attached, shows the correct layout and survives the reboot without alteration. I am unable to see anything on the 'Primary' display, which has incorrectly been given to the HDMI projector. Unseating the HDMI cable does not restore the VGA to 'Primary' display automatically and I must reboot the computer while leaving the HDMI unplugged in order to restore my ability to see the 'Primary' display on the VGA connection. Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is repeatedly provable through multiple reboots or changes to the logical layout of the screens in the 'Displays' settings of gnome-control- center. ERRORS(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until reboot or shutdown and then subsequent login from gdm3. HDMI monitor(projector) goes blank and the VGA monitor only shows 'Secondary' monitor screen without any user visible controls or windows as they are all being painted to the now blanked 'Primary' HDMI connected display. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- 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 during login after reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820423 Title: monitors.xml is not parsed or applied correctly after reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
** 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 a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a 4K projector and then configuring the logical monitor layout in the "Displays" settings dialog, I can successfully create and use a multi monitor setup in my current session. However, upon a reboot or power cycle of the computer and a successful login from GDM(gdm3), the HDMI goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even though I set it as 'Primary' in the "Displays" dialog. The monitors.xml file, attached, shows the correct layout and survives the reboot without alteration. I am unable to see anything on the 'Primary' display, which has incorrectly been given to the HDMI projector. Unseating the HDMI cable does not restore the VGA to 'Primary' display automatically and I must reboot the computer while leaving the HDMI unplugged in order to restore my ability to see the 'Primary' display on the VGA connection. Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is repeatedly provable through multiple reboots or changes to the logical layout of the screens in the 'Displays' settings of gnome-control- center. - - ERROR(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" + ERRORS(syslog) = "Failed to get current display configuration state: + GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name + "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until - reboot or shutdown and then subsequent login from gdm3, then--problems - until HDMI cable is unseated and rebooted again. + reboot or shutdown and then subsequent login from gdm3. HDMI + monitor(projector) goes blank and the VGA monitor only shows 'Secondary' + monitor screen without any user visible controls or windows as they are + all being painted to the now blanked 'Primary' HDMI connected display. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- 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 reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
@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 the issues disappears completely and the system is works across multiple reboots or changes to the monitors.xml through the "Displays" settings. This is clearly related to how GDM appears to set-up or create the user session and I would be glad to test any ideas you have to solve it while using GDM, however---after 4-hours of messing with it, I had to go with a solution that "Just Works": slick-greeter or lightdm. Please let me know what else I can provide or do to clarify this issue. -- 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 reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
** 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 - "org.gnome.Mutter.DisplayConfig" does not exist" + 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 + a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a 4K + projector and then configuring the logical monitor layout in the + "Displays" settings dialog, I can successfully create and use a multi + monitor setup in my current session. However, upon a reboot or power + cycle of the computer and a successful login from GDM(gdm3), the HDMI + goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even + though I set it as 'Primary' in the "Displays" dialog. The monitors.xml + file, attached, shows the correct layout and survives the reboot without + alteration. I am unable to see anything on the 'Primary' display, which + has incorrectly been given to the HDMI projector. Unseating the HDMI + cable does not restore the VGA to 'Primary' display automatically and I + must reboot the computer while leaving the HDMI unplugged in order to + restore my ability to see the 'Primary' display on the VGA connection. + Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is + repeatedly provable through multiple reboots or changes to the logical + layout of the screens in the 'Displays' settings of gnome-control- + center. + + + ERROR(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until - reboot or shutdown, then--problems until HDMI cable is unseated and - rebooted again. + reboot or shutdown and then subsequent login from gdm3, then--problems + until HDMI cable is unseated and rebooted again. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- 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 reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
** 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 reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760849 Title: Login screen appears on only one monitor and it's not the one I want To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1760849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
** 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 "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 + CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP + Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA + as primary monitor and HDMI(wireless Tx) as secondary to projector and + then apply custom monitor positioning using g-c-c "Displays" panel. - CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. - - - RESULT = correct positioning and working of multiple displays until reboot or shutdown, then--problems until HDMI cable is unseated and rebooted again. + RESULT = correct positioning and working of multiple displays until + reboot or shutdown, then--problems until HDMI cable is unseated and + rebooted again. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- 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 reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820423] [NEW] monitors.xml is not parsed or applied correctly after reboot or shutdown
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" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until reboot or shutdown, then--problems until HDMI cable is unseated and rebooted again. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "monitors.xml" https://bugs.launchpad.net/bugs/1820423/+attachment/5246801/+files/monitors.xml -- 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 reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067277] Re: popcon.ubuntu.com: Ubuntu Popularity Contest statistics is out of date
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067277 Title: popcon.ubuntu.com: Ubuntu Popularity Contest statistics is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1067277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
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 xorg.conf.
On Sun, Feb 17, 2019 at 1:10 PM Noise wrote:
> @bbethge, your solution worked for me. After creating xorg.conf and
> enabling intel driver screen wakes up after lock and behaviour is right.
> Xubuntu 18.10, Intel(R) HD Graphics 620 (Kaby Lake GT2).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1801609
>
> Title:
> Fails to deactivate dpms off mode after user initiated wake-up
> events(not system-suspended, just locked and dpms active)
>
> Status in xorg-server package in Ubuntu:
> Confirmed
>
> Bug description:
> Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
> and turn-off monitors(automatically or manually), but--will not wake-
> up monitors upon keyboard or mouse activity. I can type unlock
> password, blindly and then the monitors will wake and show unlocked
> session.
>
> WORKAROUND: I uninstalled light-locker, then, I installed gnome-
> screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
> if light-locker is not found or installed.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.10
> Package: light-locker (not installed)
> ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
> Uname: Linux 4.18.0-10-generic x86_64
> ApportVersion: 2.20.10-0ubuntu13
> Architecture: amd64
> CurrentDesktop: XFCE
> Date: Sun Nov 4 13:01:36 2018
> InstallationDate: Installed on 2018-11-03 (0 days ago)
> InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.2)
> SourcePackage: light-locker
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801609
Title:
Fails to deactivate dpms off mode after user initiated wake-up
events(not system-suspended, just locked and dpms active)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1769126] Re: SIMPLE-SCAN crashes when set to photo scanning
@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. "MFCL5900DW" instead of "MFC-L5900DW") can cause > crashes in some cases (namely simple-scan in photo mode). > > Fix: > > * (optional) Check "/opt/brother/scanner/brscan4/brsanenetdevice4.cfg" to > see if the configured device has an invalid model name (by > cross-referencing with the output of "brsaneconfig4 -q") > * Delete /opt/brother/scanner/brscan4/brsanenetdevice4.cfg > * Re-add the scanner with a command similar to "brsaneconfig4 -a > name=MFC-L5900DW model=MFC-L5900DW nodename=BRN3C2AF4738657" > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1769126 > > Title: > SIMPLE-SCAN crashes when set to photo scanning > > Status in simple-scan package in Ubuntu: > Confirmed > > Bug description: > WHAT I EXPECTED TO HAPPEN > I expected to scan a photo and get it showing in Simple scan alongside > the other pages scanned in text mode. > > WHAT HAPPENS INSTEAD > Simple scan crashes when set to scan images. When scan button is > pressed, the app seems to begin the scanning process, scanner takes the > page (if on the ADF), the app shows as if beginning to scan and then > suddenly disappears with no message shown. > > However if the app is launched again, the app opens immediately > showing all pages scanned up to that moment (in text mode) except for > the newly scanned photo, as if the app was always there and had never > closed. > > When set to scan text, it is ok, but page size is much larger than > actual sheet or flat-bed size (higher, actually, width is ok). > > > OS: Ubuntu 18.04LTS fresh install and updated > Sw centers sais: version 3.28.0-0ubuntu1 > (no other OS on the computer) > Multi-function printer scanner: Brother MFC-J5330DW connected to the > network (didn't try USB) > Computer: HP notebook 15-ay117ns with serial CND70308KK > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1769126/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769126 Title: SIMPLE-SCAN crashes when set to photo scanning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1769126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783895] Re: Screen locking fails on Suspend/Resume for laptop lid-switch
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 making sure that 'logind-handle-lid-switch' is set to 'false'(unchecked) and removing(purge) 'xscreensaver', I am getting good results with having 'slock' screen-locking at lid-events on my ThinkPad T450. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783895 Title: Screen locking fails on Suspend/Resume for laptop lid-switch To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-session/+bug/1783895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814815] [NEW] surf needs to depend on 'apparmor-profiles-extra' or apparmor.service fails
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 -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit apparmor.service has begun starting up. Feb 05 12:56:59 CKR-1 apparmor[609]: * Starting AppArmor profiles Feb 05 12:56:59 CKR-1 apparmor[609]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Feb 05 12:56:59 CKR-1 apparmor[609]: AppArmor parser error for /etc/apparmor.d/usr.bin.surf in /etc/apparmor.d/usr.bin.surf at line 30: Could not open 'abstractions/gstreamer' Feb 05 12:56:59 CKR-1 apparmor[609]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Feb 05 12:56:59 CKR-1 apparmor[609]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Feb 05 12:56:59 CKR-1 apparmor[609]: AppArmor parser error for /etc/apparmor.d/usr.bin.surf in /etc/apparmor.d/usr.bin.surf at line 30: Could not open 'abstractions/gstreamer' Feb 05 12:56:59 CKR-1 apparmor[609]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Feb 05 12:57:00 CKR-1 apparmor[609]:...fail! Feb 05 12:57:00 CKR-1 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Feb 05 12:57:00 CKR-1 systemd[1]: apparmor.service: Failed with result 'exit-code'. Feb 05 12:57:00 CKR-1 systemd[1]: Failed to start AppArmor initialization. -- Subject: Unit apparmor.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit apparmor.service has failed. -- -- The result is RESULT. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: surf 2.0+git20180223-1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Tue Feb 5 13:27:01 2019 InstallationDate: Installed on 2018-11-23 (73 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: surf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: surf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814815 Title: surf needs to depend on 'apparmor-profiles-extra' or apparmor.service fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/surf/+bug/1814815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814344] Re: Needs to depend on gstreamer*-plugins-bad for DVD playback in Totem
** 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 "gstreamer*-plugins-bad" was listed as "un"(uninstalled): $ dpkg -l gstreamer* un gstreamer1.0-plugins-bad:amd64 1.14.4-1ubuntu1amd64 GStreamer plugins from the "bad" set - Upon installation, DVD's began playing in the default "Videos"(Totem) - player. + After installation of gstreamer*plugins-bad, DVD's began playing in the + default "Videos"(Totem) player. Please add the "gstreamer*-plugins-bad" as a depends to the ubuntu- restricted-addons pkg. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-restricted-addons 26 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 1 15:57:14 2019 InstallationDate: Installed on 2018-11-23 (70 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-restricted-addons UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814344 Title: Needs to depend on gstreamer*-plugins-bad for DVD playback in Totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-addons/+bug/1814344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814344] [NEW] Needs to depend on gstreamer*-plugins-bad for DVD playback in Totem
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 listed as "un"(uninstalled): $ dpkg -l gstreamer* un gstreamer1.0-plugins-bad:amd64 1.14.4-1ubuntu1amd64 GStreamer plugins from the "bad" set Upon installation, DVD's began playing in the default "Videos"(Totem) player. Please add the "gstreamer*-plugins-bad" as a depends to the ubuntu- restricted-addons pkg. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-restricted-addons 26 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 1 15:57:14 2019 InstallationDate: Installed on 2018-11-23 (70 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-restricted-addons UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-restricted-addons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814344 Title: Needs to depend on gstreamer*-plugins-bad for DVD playback in Totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-addons/+bug/1814344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
[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 play . . . DVD source is required . . . ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Invalid ** Changed in: totem (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/1809044 Title: [SOLVED] DVD playback error: unable to play . . . DVD source is required . . . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788596] Re: xclock's reverseVideo draws black on black
* 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 the hierarchy of the widgets which compose xclock. In the notation below, indentation indicates hierarchical structure. The widget class name is given first, followed by the widget instance name. XClock xclock Clock clock " so, my corrected .Xresources file would be this: ~$ cat .Xresources *background: #00 *foreground: #ff XClock.Clock.majorColor:#66 XClock.Clock.minorColor:#44 XClock.Clock.hourColor: #88 XClock.Clock.minuteColor: #88 XClock.Clock.secondColor: #22 XClock*geometry:350x350-125+75 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788596 Title: xclock's reverseVideo draws black on black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/788596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788596] Re: xclock's reverseVideo draws black on black
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 XClock*geometry:350x350-125+75 See this thread for more infor: https://unix.stackexchange.com/questions/89304/facelifting-xclock-while-using-xrender-a-long-and-winding-road -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788596 Title: xclock's reverseVideo draws black on black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/788596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812594] [NEW] lubuntu-desktop needs to depend on lxlock
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. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lubuntu-desktop 0.94.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: LXDE Date: Sun Jan 20 16:34:48 2019 InstallationDate: Installed on 2019-01-20 (0 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812594 Title: lubuntu-desktop needs to depend on lxlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1812594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067277] Re: popcon.ubuntu.com: Ubuntu Popularity Contest statistics is out of date
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 Contest statistics is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1067277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067277] Re: popcon.ubuntu.com: Ubuntu Popularity Contest statistics is out of date
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 version it is in and change the bug status to Confirmed. ** Changed in: popularity-contest (Ubuntu) Status: Triaged => Incomplete -- 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 Contest statistics is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1067277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366546] Re: Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
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 version it is in and change the bug status to Confirmed. ** Changed in: grub2 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366546 Title: Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1366546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159361] Re: zoneminder not creating local unix sockets for streaming
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 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 version it is in and change the bug status to Confirmed. ** Changed in: zoneminder (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159361 Title: zoneminder not creating local unix sockets for streaming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zoneminder/+bug/1159361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711420] Re: Should be popularity-contest package a part of Ubuntu installer media?
*** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711420 Title: Should be popularity-contest package a part of Ubuntu installer media? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1711420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
@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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 788596] Re: xclock's reverseVideo draws black on black
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 background color scheme. Please see the attached screenshot, if it will come through on launchpad's bug comments. On Fri, Dec 28, 2018 at 6:44 AM Ralph Corderoy wrote: > Hi Chris, that's not what I'm seeing. Please describe what it is you > are seeing working normally, and confirm you've no .Xresources, etc., > implicitly in play. I see xclock(1) now describes hourColor, etc., and > says that reverseVideo, AKA -rv, affects their defaults. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/788596 > > Title: > xclock's reverseVideo draws black on black > > Status in x11-apps package in Ubuntu: > Fix Released > > Bug description: > Binary package hint: x11-apps > > Package x11-apps 7.5+5. When xclock is given -rv it has a black > background instead of a white one but much of the clock isn't drawn; > presumably those missing bits are still being drawn in black. > > Easy to confirm; compare `xclock' and `xclock -rv'. Adding -norender > changes the behaviour; white hands are now visible with -rv but the > clock face is still missing. With -digital no text is displayed. > > It has been like this for several releases but decades ago it used to > work just fine. I suspect the render additions are what's caused the > bugs. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/788596/+subscriptions > ** Attachment added: "Screenshot from 2018-12-28 10-30-57.png" https://bugs.launchpad.net/bugs/788596/+attachment/5225523/+files/Screenshot%20from%202018-12-28%2010-30-57.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788596 Title: xclock's reverseVideo draws black on black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/788596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835532] Re: lightdm does not keep numlock status on boot
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 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 version it is in and change the bug status to Confirmed. ** Changed in: lightdm-gtk-greeter Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/835532 Title: lightdm does not keep numlock status on boot To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/835532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835532] Re: lightdm does not keep numlock status on boot
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 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 version it is in and change the bug status to Confirmed. ** Changed in: unity-greeter (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/835532 Title: lightdm does not keep numlock status on boot To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/835532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828307] Re: Can't get out of fullscreen mode when two or more apps are fullscreen
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 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 version it is in and change the bug status to Confirmed. ** Changed in: compiz (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828307 Title: Can't get out of fullscreen mode when two or more apps are fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/828307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828307] Re: Can't get out of fullscreen mode when two or more apps are fullscreen
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 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 version it is in and change the bug status to Confirmed. ** Changed in: compiz-core Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828307 Title: Can't get out of fullscreen mode when two or more apps are fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/828307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828307] Re: Can't get out of fullscreen mode when two or more apps are fullscreen
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 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 version it is in and change the bug status to Confirmed. ** Changed in: compiz Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828307 Title: Can't get out of fullscreen mode when two or more apps are fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/828307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788596] Re: xclock's reverseVideo draws black on black
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. https://bugs.launchpad.net/bugs/788596 Title: xclock's reverseVideo draws black on black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/788596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 502920] Re: [needs-packaging] Canon UFR II driver needs packaging
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 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 version it is in and change the bug status to Confirmed. ** Changed in: ubuntu Status: Confirmed => Invalid ** Changed in: ubuntu Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/502920 Title: [needs-packaging] Canon UFR II driver needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/502920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946899] Re: 8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
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 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 version it is in and change the bug status to Confirmed. ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946899 Title: 8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/946899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946899] Re: 8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
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 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 version it is in and change the bug status to Confirmed. ** Changed in: linuxmint Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946899 Title: 8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/946899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218202] Re: numlockx does not turn num lock keyboard light on.
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. https://bugs.launchpad.net/bugs/218202 Title: numlockx does not turn num lock keyboard light on. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/218202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218202] Re: numlockx does not turn num lock keyboard light on.
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 fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect and any other logs that are relevant for this particular issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/218202 Title: numlockx does not turn num lock keyboard light on. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/218202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218202] Re: numlockx does not turn num lock keyboard light on.
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. https://bugs.launchpad.net/bugs/218202 Title: numlockx does not turn num lock keyboard light on. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/218202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218202] Re: numlockx does not turn num lock keyboard light on.
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 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 version it is in and change the bug status to Confirmed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/218202 Title: numlockx does not turn num lock keyboard light on. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/218202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
$ 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 encrypted DVDs and $ apt-cache policy ubuntu-restricted-extras libdvd-pkg ubuntu-restricted-extras: Installed: 67 Candidate: 67 Version table: *** 67 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/multiverse amd64 Packages 100 /var/lib/dpkg/status libdvd-pkg: Installed: 1.4.2-1-1 Candidate: 1.4.2-1-1 Version table: *** 1.4.2-1-1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/multiverse amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/multiverse i386 Packages 100 /var/lib/dpkg/status Does this DEBUG output help? $ totem --gst-debug-level=1 dvd:// 0:00:00.250985444 8265 0x5636e0092690 ERRORdefault totem-gst-helpers.c:61:totem_gst_message_print: message = No URI handler implemented for "dvd". 0:00:00.251019760 8265 0x5636e0092690 ERRORdefault totem-gst-helpers.c:63:totem_gst_message_print: domain = 4841 (gst-core-error-quark) 0:00:00.251027744 8265 0x5636e0092690 ERRORdefault totem-gst-helpers.c:64:totem_gst_message_print: code= 12 0:00:00.251034606 8265 0x5636e0092690 ERRORdefault totem-gst-helpers.c:65:totem_gst_message_print: debug = gsturidecodebin.c(1409): gen_source_element (): /GstPlayBin:play/GstURIDecodeBin:uridecodebin0 0:00:00.251063456 8265 0x5636e0092690 ERRORdefault totem-gst-helpers.c:66:totem_gst_message_print: source = 0:00:00.251072408 8265 0x5636e0092690 ERRORdefault totem-gst-helpers.c:67:totem_gst_message_print: uri = (NULL) ** Message: 09:03:41.473: Missing plugin: gstreamer|1.0|totem|DVD source|urisource-dvd (DVD source) (totem:8265): Totem-WARNING **: 09:03:54.700: Failed to reset the playback rate to 1.0 MPV plays DVD perfectly: $ mpv dvd:// Playing: dvd:// libdvdnav: Using dvdnav version 6.0.0 libdvdnav: DVD Title: HARRY_POTTER_SORCERERS_STONE libdvdnav: DVD Serial Number: 3716AE14 libdvdnav: DVD Title (Alternative): HARRY_POTTER_SORCERERS_STONE libdvdnav: DVD disk reports itself with Region mask 0x00fe. Regions: 1 [dvdnav] Selecting title 0. libdvdread: Attempting to retrieve all CSS keys libdvdread: This can take a _long_ time, please be patient libdvdread: Get key for /VIDEO_TS/VTS_01_0.VOB at 0x00028221 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_01_1.VOB at 0x00031e5d libdvdread: Elapsed time 0 libdvdread: Found 1 VTS's libdvdread: Elapsed time 0 [dvdnav] DVDNAV, switched to title: 1 (+) Video --vid=1 (mpeg2video 720x480 28.750fps) (+) Audio --aid=1 --alang=es (ac3 6ch 48000Hz) Audio --aid=2 --alang=en (ac3 6ch 48000Hz) Subs --sid=1 --slang=en (dvd_subtitle) Subs --sid=2 (dvd_subtitle) Subs --sid=3 --slang=es (dvd_subtitle) File tags: Title: HARRY_POTTER_SORCERERS_STONE Using hardware decoding (vaapi). AO: [pulse] 48000Hz 5.1(side) 6ch float VO: [gpu] 720x480 => 853x480 vaapi[nv12] AV: 00:00:00 / 02:32:12 (0%) A-V: 0.000 (+) Video --vid=1 (mpeg2video 720x480 28.750fps) (+) Audio --aid=1 --alang=es (ac3 6ch 48000Hz) Audio --aid=2 --alang=en (ac3 6ch 48000Hz) Subs --sid=1 --slang=en (dvd_subtitle) Subs --sid=2 (dvd_subtitle) Subs --sid=3 --slang=es (dvd_subtitle) Subs --sid=4 (*) (eia_608) On Wed, Dec 19, 2018 at 9:55 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > After installing libdvd-pkg and running: > > sudo dpkg-reconfigure libdvd-pkg > > please ensure it has also worked: > > $ dpkg -l | grep dvdcss > > which should show something like: > > ii libdvdcss-dev:amd641.4.2-1~local > amd64library for accessing encrypted DVDs - > development files > ii libdvdcss2:amd64 1.4.2-1~local > amd64library for accessing encrypted DVDs > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1809044 > > Title: > DVD playback error: unable to play . . . DVD source is required . . . > > Status in gstreamer1.0 package in Ubuntu: > New > Status in totem package in Ubuntu: > New > > Bug description: > 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." > > DVD will play normally in VLC player after installation on same > machine. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: libgstreamer1.0-0 1.14.4-1 > ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 >
Re: [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
@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.. On Wed, Dec 19, 2018 at 7:30 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > I wouldn't be surprised if MPEG-2 support was missing by default due to > licensing/patent restrictions. > > Please try this command: > > sudo apt install ubuntu-restricted-addons > > and tell us if it improves the situation. > > > ** Changed in: gstreamer1.0 (Ubuntu) >Status: New => Incomplete > > ** Changed in: totem (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1809044 > > Title: > DVD playback error: unable to play . . . DVD source is required . . . > > Status in gstreamer1.0 package in Ubuntu: > Incomplete > Status in totem package in Ubuntu: > Incomplete > > Bug description: > 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." > > DVD will play normally in VLC player after installation on same > machine. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: libgstreamer1.0-0 1.14.4-1 > ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 > Uname: Linux 4.18.0-12-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Dec 18 15:21:45 2018 > InstallationDate: Installed on 2018-11-13 (34 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gstreamer1.0 > UpgradeStatus: No upgrade log present (probably fresh install) > XorgLog: Error: [Errno 2] No such file or directory: > '/var/log/Xorg.0.log' > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions > -- 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 required . . . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
** 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 required . . . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809044] [NEW] DVD playback error: unable to play . . . DVD source is required . . .
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." DVD will play normally in VLC player after installation on same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 15:21:45 2018 InstallationDate: Installed on 2018-11-13 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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 required . . . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711538] Re: Tap-to-click does not work on the GDM login screen
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: Tap-to-click does not work on the GDM login screen To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1711538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054299] Re: Race condition in suspend scripts reveals desktop
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. https://github.com/lxqt/lxqt/issues/1515#issuecomment-425371720 and 2. https://github.com/lxqt/lxqt/issues/1515#issuecomment-435624731 ** Bug watch added: github.com/lxqt/lxqt/issues #1515 https://github.com/lxqt/lxqt/issues/1515 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054299 Title: Race condition in suspend scripts reveals desktop To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1054299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808638] Re: Tap-to-Click at login screen for principle of least astonishment (POLA)
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808638 Title: Tap-to-Click at login screen for principle of least astonishment (POLA) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1808638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808638] Re: Tap-to-Click at login screen for principle of least astonishment (POLA)
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 https://bugzilla.gnome.org/show_bug.cgi?id=785855 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=785855 Importance: Unknown Status: Unknown ** Description changed: 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. + Windows or another system which does _not_ prevent this technique. In accord with the old axiom: “You Never Get A Second Chance to Make a First Impression” – Will Rogers Let's not let this be the first negative experience that converts and first-timers run into! Tap-to-click on touchpads is enabled and works normally during the Ubiquity installer. I'm not sure if libinput is to blame, but I do notice that I frequently have to enable the tap-to-click function in gnome-settings after first login. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Dec 15 09:12:01 2018 InstallationDate: Installed on 2018-11-08 (37 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808638 Title: Tap-to-Click at login screen for principle of least astonishment (POLA) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1808638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808638] [NEW] Tap-to-Click at login screen for principle of least astonishment (POLA)
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 accord with the old axiom: “You Never Get A Second Chance to Make a First Impression” – Will Rogers Let's not let this be the first negative experience that converts and first-timers run into! Tap-to-click on touchpads is enabled and works normally during the Ubiquity installer. I'm not sure if libinput is to blame, but I do notice that I frequently have to enable the tap-to-click function in gnome-settings after first login. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Dec 15 09:12:01 2018 InstallationDate: Installed on 2018-11-08 (37 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic login tap touchpad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808638 Title: Tap-to-Click at login screen for principle of least astonishment (POLA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1808638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
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 case it provides insight or another angle to approach the resolution of this bug. BTW: the test system _was_ experiencing this bug on a clean-install of 18.10 Desktop ISO. TL;DR Adding a new variable(optional: yes) in the netplan yaml config for a static IP addy allows the "systemd-networkd-wait-online.service" to _ignore_ interfaces that may be blocking or inhibiting the proper startup of the apport-auto/whoopsie units. Steps to reproduce: 1. Disable all NetworkManager related services: $ systemctl list-unit-files | grep Net NetworkManager-dispatcher.service disabled NetworkManager-wait-online.service disabled NetworkManager.service disabled 2. Create new yaml config for static IP's on all IF's(notice the 'optional: yes' directives!): $ cat /etc/netplan/01-static-ip.yaml network: version: 2 renderer: networkd ethernets: enp2s0: optional: yes dhcp4: no dhcp6: no addresses: [192.168.1.201/24] gateway4: 192.168.1.254 nameservers: addresses: [8.8.8.8, 8.8.4.4] wifis: wlp3s0: optional: yes dhcp4: no dhcp6: no addresses: [192.168.1.202/24] gateway4: 192.168.1.254 nameservers: addresses: [8.8.8.8, 8.8.4.4] access-points: "Chez Merkle-Mac-Rainey 5 GHz": password: "BIG SECRET" 3. Reboot and confirm proper startup of all service units: $ systemctl --failed 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. $ systemctl status ● CKR-1 State: running Jobs: 0 queued Failed: 0 units Since: Thu 2018-12-06 15:02:16 CST; 22min ago HTH! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
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 support.brother.com website, etc.) Follow the instructions from the Brother download site and during the script installation to-the-letter(EXACTLY)! *** CAVEAT: use the printer I.P. addy if on a LAN and _NOT_ the auto- detected mDNS addy if you have an AT&T Fiber residential gateway such as mine(BGW210-700) which has a ".local" domain hard-coded in the DNS. This effectively kills mDNS(Avahi) broadcasts and so I'm not able to connect to the printer using that system. CUPS Connection:lpd://192.168.1.220/BINARY_P1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805039] Re: [SOLVED] Simple Scan segfaults when scanning on "Photo"(24-bit) quality.
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 "Photo"(24-bit) quality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1805039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805039] Re: Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.
*** 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 support.brother.com website, etc.) Follow the instructions from the Brother download site and during the script installation to-the-letter(EXACTLY)! *** CAVEAT: use the printer I.P. addy if on a LAN and _NOT_ the auto- detected mDNS addy if you have an AT&T Fiber residential gateway such as mine(BGW210-700) which has a ".local" domain hard-coded in the DNS. This effectively kills mDNS(Avahi) broadcasts and so I'm not able to connect to the printer using that system. i.e.: CUPS Connection:lpd://192.168.1.220/BINARY_P1 in my case. Good Luck !! ** Summary changed: - Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality. + [SOLVED] Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality. ** Summary changed: - [SOLVED] Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality. + [SOLVED] Simple Scan segfaults when scanning on "Photo"(24-bit) quality. -- 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 "Photo"(24-bit) quality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1805039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805039] Re: Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.
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
client
[+0.04s] DEBUG: app-window.vala:1715: Loading state from
/home/chris/.cache/simple-scan/state
[+0.04s] DEBUG: app-window.vala:1672: Restoring window to 600x400 pixels
[+0.04s] DEBUG: app-window.vala:1676: Restoring window to maximized
[+0.04s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0.04s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0.07s] DEBUG: scanner.vala:1461: sane_init () -> SANE_STATUS_GOOD
[+0.07s] DEBUG: scanner.vala:1467: SANE version 1.0.27
[+0.07s] DEBUG: scanner.vala:1528: Requesting redetection of scan devices
[+0.07s] DEBUG: scanner.vala:806: Processing request
[+0.14s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0.18s] DEBUG: app-window.vala:1776: Saving state to
/home/chris/.cache/simple-scan/state
[+8.26s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+8.26s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0"
vendor="Brother" model="*dcp-l2550dw" type="dcp-l2550dw"
[+9.48s] DEBUG: simple-scan.vala:455: Requesting scan at 300 dpi from device
'brother4:net1;dev0'
[+9.48s] DEBUG: scanner.vala:1576: Scanner.scan ("brother4:net1;dev0", dpi=300,
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=2159,
paper_height=2794, brightness=0, contrast=0, delay=1ms)
[+9.48s] DEBUG: scanner.vala:806: Processing request
[+10.72s] DEBUG: scanner.vala:867: sane_open ("brother4:net1;dev0") ->
SANE_STATUS_GOOD
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (0)
[+10.72s] DEBUG: scanner.vala:738: Option 0: name='(null)' title='Number of
options' type=bool size=4 cap=soft-detect
[+10.72s] DEBUG: scanner.vala:741: Description: Read-only option that
specifies how many options a specific devices supports.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (1)
[+10.72s] DEBUG: scanner.vala:738: Option 1: name='(null)' title='Mode'
type=group size=4 cap=advanced
[+10.72s] DEBUG: scanner.vala:741: Description:
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (2)
[+10.72s] DEBUG: scanner.vala:738: Option 2: name='mode' title='Scan mode'
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741: Description: Select the scan mode
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (3)
[+10.72s] DEBUG: scanner.vala:738: Option 3: name='resolution' title='Scan
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600,
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741: Description: Sets the resolution of the
scanned image.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (4)
[+10.72s] DEBUG: scanner.vala:738: Option 4: name='source' title='Scan source'
type=string size=64 values=["FlatBed", "Automatic Document Feeder(left
aligned)", "Automatic Document Feeder(left aligned,Duplex)", "Automatic
Document Feeder(centrally aligned)", "Automatic Document Feeder(centrally
aligned,Duplex)"] cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741: Description: Selects the scan source (such
as a document-feeder).
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (5)
[+10.72s] DEBUG: scanner.vala:738: Option 5: name='brightness'
title='Brightness' type=fixed size=4 unit=percent min=-50.00,
max=50.00, quant=65536 cap=soft-select,soft-detect,inactive
[+10.72s] DEBUG: scanner.vala:741: Description: Controls the brightness of
the acquired image.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (6)
[+10.72s] DEBUG: scanner.vala:738: Option 6: name='contrast' title='Contrast'
type=fixed size=4 unit=percent min=-50.00, max=50.00, quant=65536
cap=soft-select,soft-detect,inactive
[+10.72s] DEBUG: scanner.vala:741: Description: Controls the contrast of the
acquired image.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (7)
[+10.72s] DEBUG: scanner.vala:738: Option 7: name='(null)' title='Geometry'
type=group size=4 cap=advanced
[+10.72s] DEBUG: scanner.vala:741: Description:
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (8)
[+10.72s] DEBUG: scanner.vala:738: Option 8: name='tl-x' title='Top-left x'
type=fixed size=4 unit=mm min=0.00, max=215.84, quant=6553
cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741: Description: Top-left x position of scan
area.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (9)
[+10.72s] DEBUG: scanner.vala:738: Option 9: name='tl-y' title='Top-left y'
type=fixed size=4 unit=mm min=0.00, max=355.51, quant=6553
cap=
[Bug 1805039] [NEW] Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.
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
/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9: unknown key
'SYSFS{idVendor}'
Nov 25 12:43:18 CKR-1 dbus-daemon[2323]: [session uid=1000 pid=2323] Activating
via systemd: service name='org.freedesktop.portal.Desktop'
unit='xdg-desktop-portal.service' requested by ':1.106' (uid=1000 pid=6089
comm="simple-scan " label="unconfined")
Nov 25 12:43:26 CKR-1 simple-scan: io/hpmud/model.c 532: no
ther_dcp-l2550dw_series attributes found in
/usr/share/hplip/data/models/models.dat
Nov 25 12:43:26 CKR-1 simple-scan: io/hpmud/model.c 543: no
ther_dcp-l2550dw_series attributes found in
/usr/share/hplip/data/models/unreleased/unreleased.dat
Nov 25 12:43:53 CKR-1 kernel: [ 603.879672] scan-thread[6118]: segfault at 3ec
ip 7f9d432b29d2 sp 7f9d43bbd810 error 4 in
libsane-brother4.so.1.0.7[7f9d4328d000+2e000]
Nov 25 12:44:00 CKR-1 whoopsie-upload-all[6133]: Collecting info for
/var/crash/_usr_bin_simple-scan.1000.crash...
Nov 25 12:44:00 CKR-1 whoopsie-upload-all[6133]: Marking
/var/crash/_usr_bin_simple-scan.1000.crash for whoopsie upload
Nov 25 12:44:00 CKR-1 whoopsie[1825]: [12:44:00] Parsing
/var/crash/_usr_bin_simple-scan.1000.crash.
Nov 25 12:44:00 CKR-1 whoopsie[1825]: [12:44:00] Uploading
/var/crash/_usr_bin_simple-scan.1000.crash.
Nov 25 12:44:09 CKR-1 simple-scan: io/hpmud/model.c 532: no
ther_dcp-l2550dw_series attributes found in
/usr/share/hplip/data/models/models.dat
Nov 25 12:44:09 CKR-1 simple-scan: io/hpmud/model.c 543: no
ther_dcp-l2550dw_series attributes found in
/usr/share/hplip/data/models/unreleased/unreleased.dat
Nov 25 12:44:29 CKR-1 kernel: [ 640.437150] scan-thread[7013]: segfault at 3ec
ip 7f7dc012c9d2 sp 7f7dab7fd810 error 4 in
libsane-brother4.so.1.0.7[7f7dc0107000+2e000]
<...snip>
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: simple-scan 3.30.1.1-1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 25 12:44:45 2018
InstallationDate: Installed on 2018-11-23 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: HP HP Slimline Desktop PC 270-p0xx
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.35
dmi.board.asset.tag: CNV7280FKD
dmi.board.name: 82F2
dmi.board.vendor: HP
dmi.board.version: 00
dmi.chassis.asset.tag: CNV7280FKD
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnAMI:bvrF.35:bd11/01/2018:svnHP:pnHPSlimlineDesktopPC270-p0xx:pvr:rvnHP:rn82F2:rvr00:cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Desktop
dmi.product.name: HP Slimline Desktop PC 270-p0xx
dmi.product.sku: Z5N91AA#ABA
dmi.sys.vendor: HP
** Affects: simple-scan (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic
--
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:
Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1805039/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797649] Re: receive authentication canceled in terminal when changing options in "Other Software"
*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 "Other Software" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803576] [NEW] apt() needs "--abc-xyz" completions like apt-get()
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 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 15 09:43:50 2018 Dependencies: InstallationDate: Installed on 2018-11-08 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash-completion (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803576 Title: apt() needs "--abc-xyz" completions like apt-get() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1803576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
@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 (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1801609 > > Title: > Fails to deactivate dpms off mode after user initiated wake-up > events(not system-suspended, just locked and dpms active) > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > Xubuntu 18.10 with Xubuntu.desktop session running. System will lock > and turn-off monitors(automatically or manually), but--will not wake- > up monitors upon keyboard or mouse activity. I can type unlock > password, blindly and then the monitors will wake and show unlocked > session. > > WORKAROUND: I uninstalled light-locker, then, I installed gnome- > screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver > if light-locker is not found or installed. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: light-locker (not installed) > ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 > Uname: Linux 4.18.0-10-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Sun Nov 4 13:01:36 2018 > InstallationDate: Installed on 2018-11-03 (0 days ago) > InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > SourcePackage: light-locker > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802507] [NEW] "Launch Calculator" keyboard setting does not work
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 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 9 07:12:51 2018 InstallationDate: Installed on 2018-11-08 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug calculator cosmic gnome ** Also affects: gnome-calculator (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/1802507 Title: "Launch Calculator" keyboard setting does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1802507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713615] Re: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden
#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: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1713615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802321] [NEW] libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting...
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 \ || /usr/bin/uscan --noconf --verbose --rename --destdir=/usr/src/libdvd-pkg --check-dirname-level=0 --force-download --download-current-version /usr/share/libdvd-pkg/debian --2018-11-08 08:54:43-- http://download.videolan.org/pub/libdvdcss/1.4.2/libdvdcss-1.4.2.tar.bz2 Resolving download.videolan.org (download.videolan.org)... 2a01:e0d:1:3:58bf:fa02:c0de:5, 88.191.250.2 Connecting to download.videolan.org (download.videolan.org)|2a01:e0d:1:3:58bf:fa02:c0de:5|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 366824 (358K) [application/octet-stream] Saving to: ‘libdvdcss_1.4.2.orig.tar.bz2’ libdvdcss_1.4.2.orig.tar.bz2 100%[>] 358.23K 731KB/sin 0.5s 2018-11-08 08:54:44 (731 KB/s) - ‘libdvdcss_1.4.2.orig.tar.bz2’ saved [366824/366824] libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.4.2.orig.tar.bz2: OK libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... WORKAROUND: $ sudo dpkg-reconfigure libdvd-pkg libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.4.2.orig.tar.bz2: OK libdvd-pkg: Unpacking and configuring... libdvd-pkg: Building the package... (it may take a while) libdvd-pkg: Build log will be saved to /usr/src/libdvd-pkg/libdvdcss2_1.4.2-1~local_amd64.build Current: = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read+ep Bounding set =cap_chown,cap_dac_override,cap_fowner,cap_wake_alarm,cap_block_suspend,cap_audit_read Securebits: 024/0x14/5'b10100 secure-noroot: no (unlocked) secure-no-suid-fixup: yes (unlocked) secure-keep-caps: yes (unlocked) uid=0(root) gid=0(root) groups=0(root) libdvd-pkg: Installing... Selecting previously unselected package libdvdcss-dev:amd64. (Reading database ... 240177 files and directories currently installed.) Preparing to unpack .../libdvdcss-dev_1.4.2-1~local_amd64.deb ... Unpacking libdvdcss-dev:amd64 (1.4.2-1~local) ... Selecting previously unselected package libdvdcss2:amd64. Preparing to unpack .../libdvdcss2_1.4.2-1~local_amd64.deb ... Unpacking libdvdcss2:amd64 (1.4.2-1~local) ... Setting up libdvdcss2:amd64 (1.4.2-1~local) ... Setting up libdvdcss-dev:amd64 (1.4.2-1~local) ... Processing triggers for libc-bin (2.28-0ubuntu1) ... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libdvd-pkg 1.4.2-1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 08:56:58 2018 InstallationDate: Installed on 2018-11-08 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libdvd-pkg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libdvd-pkg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic dvd dvdcss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802321 Title: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvd-pkg/+bug/1802321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802138] [NEW] xflock4 needs a 'sleep 1' before 'xset dpms force off' to prevent backlight from immediately reactivating
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 vendor: LENOVO physical id: d version: 83ET82WW (1.52 ) date: 06/04/2018 size: 128KiB capacity: 8128KiB capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb biosbootspecification *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:26 memory:f000-f03f memory:e000-efff ioport:4000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xfce4-session 4.12.1-3ubuntu4 [modified: usr/bin/xflock4] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 7 10:11:37 2018 InstallationDate: Installed on 2018-11-04 (2 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic intel xubuntu ** Patch added: "sleep added." https://bugs.launchpad.net/bugs/1802138/+attachment/5210073/+files/xflock4.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802138 Title: xflock4 needs a 'sleep 1' before 'xset dpms force off' to prevent backlight from immediately reactivating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1802138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
** 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" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210058/+files/light-locker_seat0-greeter.out ** Attachment removed: "light-locker_syslog.out" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210059/+files/light-locker_syslog.out ** Attachment removed: "light-locker_x-0.out" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210060/+files/light-locker_x-0.out ** Attachment removed: "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. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
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 < 1801...@bugs.launchpad.net> wrote: > Are there any hints in the system or lightdm logs? > > /var/log/lightdm/*.log > > Also, does running "sleep 1 && xset dpms force off" in general work > properly or do you encounter the same bug? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1801609 > > Title: > Fails to deactivate dpms off mode after user initiated wake-up > events(not system-suspended, just locked and dpms active) > > Status in light-locker package in Ubuntu: > Incomplete > > Bug description: > Xubuntu 18.10 with Xubuntu.desktop session running. System will lock > and turn-off monitors(automatically or manually), but--will not wake- > up monitors upon keyboard or mouse activity. I can type unlock > password, blindly and then the monitors will wake and show unlocked > session. > > WORKAROUND: I uninstalled light-locker, then, I installed gnome- > screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver > if light-locker is not found or installed. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: light-locker (not installed) > ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 > Uname: Linux 4.18.0-10-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Sun Nov 4 13:01:36 2018 > InstallationDate: Installed on 2018-11-03 (0 days ago) > InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > SourcePackage: light-locker > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions > ** Attachment added: "light-locker_seat0-greeter.out" https://bugs.launchpad.net/bugs/1801609/+attachment/5210064/+files/light-locker_seat0-greeter.out ** Attachment added: "light-locker_x-1.out" https://bugs.launchpad.net/bugs/1801609/+attachment/5210065/+files/light-locker_x-1.out ** Attachment added: "light-locker_x-0.out" https://bugs.launchpad.net/bugs/1801609/+attachment/5210066/+files/light-locker_x-0.out ** Attachment added: "light-locker_lightdm.out" https://bugs.launchpad.net/bugs/1801609/+attachment/5210067/+files/light-locker_lightdm.out ** Attachment added: "light-locker_syslog.out" https://bugs.launchpad.net/bugs/1801609/+attachment/5210068/+files/light-locker_syslog.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
** 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. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
** 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. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
** 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. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
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" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210057/+files/light-locker_lightdm.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
** 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. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to VT-switch back to lightdm after user initiated wake-up events(not system-suspended, just locked and dpms active)
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. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to VT-switch back to lightdm after user initiated wake-up events(not system-suspended, just locked and dpms active)
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: - Fails to VT-switch back to lightdm after user initiated wake-up events(not system-suspended, just locked and dpms active) + Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801629] Re: xubuntu-core needs to depend on cryptsetup and lvm2 or 'apt autoremove' will make a LUKS+LVM encrypted root partition non-bootable
** 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 lvm2 or 'apt autoremove' will make a LUKS+LVM encrypted root partition non-bootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1801629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to VT-switch back to lightdm after user initiated wake-up events(not system-suspended, just locked)
** 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 events(not system-suspended, just locked) + Fails to VT-switch back to lightdm after user initiated wake-up events(not system-suspended, just locked and dpms active) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801609 Title: Fails to VT-switch back to lightdm after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797649] Re: receive authentication canceled in terminal when changing options in "Other Software"
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 in terminal when changing options in "Other Software" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Dual monitors(vga+HDMI) fail to wake after screen-lock(no system-suspend)
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. https://bugs.launchpad.net/bugs/1801609 Title: Dual monitors(vga+HDMI) fail to wake after screen-lock(no system- suspend) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801629] Re: xubuntu-core needs to depend on cryptsetup and lvm2 or 'apt autoremove' will make a LUKS+LVM encrypted root partition non-bootable
** 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 changed: - 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: + In a 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) root partition + was selected during the ubiquity installer wizard: $ sudo apt update && sudo apt --auto-remove full-upgrade && cat /run/reboo* The following packages will be REMOVED: - cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 + cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 <...snip> This _will_ make the system non-bootable upon restart if LUKS+LVM are - active on main drive. + active on the root partition. This would, by extension, make any auto- + mounted partitions(home, etc.) unavailable after boot as well! WORKAROUND: $ sudo apt install cryptsetup lvm2 cryptsetup is already the newest version (2:2.0.4-2ubuntu2). cryptsetup set to manually installed. lvm2 is already the newest version (2.02.176-4.1ubuntu3). lvm2 set to manually installed. <...snip> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xubuntu-core 2.227 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 4 18:20:38 2018 InstallationDate: Installed on 2018-11-04 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) -- 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 lvm2 or 'apt autoremove' will make a LUKS+LVM encrypted root partition non-bootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1801629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Dual monitors(vga+HDMI) fail to wake after screen-lock(no system-suspend)
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 screen by signaling: Ctrl+Alt+F{1,2,3,etc.}, followed by
Ctrl+Alt+F8 to regain the login screen.
Systems:
1. 2nd Gen Intel Core i3-2120 Processor (3M, 3.30GHz) w/HD2000 Graphics,
Dell Optiplex 390
2. i5-2520M(2.5GHz) Intel HD Graphics, Lenovo ThinkPad T420
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801609
Title:
Dual monitors(vga+HDMI) fail to wake after screen-lock(no system-
suspend)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746039] Re: Xubuntu needs a gui backup utility --- deja-dup or somesuch
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. https://bugs.launchpad.net/bugs/1746039 Title: Xubuntu needs a gui backup utility --- deja-dup or somesuch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1746039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744959] Re: Xubuntu needs to depend on full LibreOffice(Impress(PowerPoint), etc.)) suite for modern office needs
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744959 Title: Xubuntu needs to depend on full LibreOffice(Impress(PowerPoint), etc.)) suite for modern office needs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1744959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746556] Re: Xubuntu needs a better numlock handler at login and during user session
** 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. https://bugs.launchpad.net/bugs/1746556 Title: Xubuntu needs a better numlock handler at login and during user session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1746556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801629] [NEW] xubuntu-core needs to depend on cryptsetup and lvm2 or 'apt autoremove' will make a LUKS+LVM encrypted system non-bootable
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 update && sudo apt --auto-remove full-upgrade && cat /run/reboo* The following packages will be REMOVED: cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 <...snip> This _will_ make the system non-bootable upon restart if LUKS+LVM are active on main drive. WORKAROUND: $ sudo apt install cryptsetup lvm2 cryptsetup is already the newest version (2:2.0.4-2ubuntu2). cryptsetup set to manually installed. lvm2 is already the newest version (2.02.176-4.1ubuntu3). lvm2 set to manually installed. <...snip> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xubuntu-core 2.227 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 4 18:20:38 2018 InstallationDate: Installed on 2018-11-04 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apt cosmic luks lvm2 xubuntu ** Summary changed: - xubuntu-core needs to depend on cryptsetup and lvm2 or autoremove will make system non-bootable + xubuntu-core needs to depend on cryptsetup and lvm2 or 'apt autoremove' will make a LUKS-LVM encrypted system non-bootable ** 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 system non-bootable -- 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 lvm2 or 'apt autoremove' will make a LUKS+LVM encrypted system non-bootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1801629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
