[Bug 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan
Sorry I lumped so much text into one box. I must have been asleep at the wheel. I was just setting up another of these today with 18.04.1 and it's also effected but I know Xenial worked fine out-of-box so I'm just guessing (with inadequate studying) that the change to GNOME as default resulted in slightly different dependencies? It is indeed a low priority bug, or I'm almost hesitant to call it a true bug since apparently it effects a very limited number of older laptops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845898 Title: Unable to set touchpad Edge Scrolling in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan
Sorry for the delay. I performed a fresh install of 20191014 last night, then updated it this AM so we'd be working with an out-of-box experience. After the update and a reboot I opened System Settings > Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to- click to off while also changing Edge Scrolling to ON. Opening Test Your Settings indicates that the changes were applied correctly but immediately after closing System Settings the Edge Scrolling setting reverts to off. That can be verified both by the touchpad behavior and reopening the Mouse & Touchpad settings UI. The other settings changes "stick" as they should. lance@lance-e6400:~$ journalctl -b 0 -- Logs begin at Mon 2019-10-14 22:46:09 CDT, end at Tue 2019-10-15 15:42:44 CDT Oct 15 15:33:49 lance-e6400 kernel: microcode: microcode updated early to revisi Oct 15 15:33:49 lance-e6400 kernel: Linux version 5.3.0-18-generic (buildd@lcy01 Oct 15 15:33:49 lance-e6400 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0 Oct 15 15:33:49 lance-e6400 kernel: KERNEL supported cpus: Oct 15 15:33:49 lance-e6400 kernel: Intel GenuineIntel Oct 15 15:33:49 lance-e6400 kernel: AMD AuthenticAMD Oct 15 15:33:49 lance-e6400 kernel: Hygon HygonGenuine Oct 15 15:33:49 lance-e6400 kernel: Centaur CentaurHauls Oct 15 15:33:49 lance-e6400 kernel: zhaoxin Shanghai Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x8 Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SS Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Enabled xstate features 0x3, contex Oct 15 15:33:49 lance-e6400 kernel: BIOS-provided physical RAM map: Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0009f000-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0010-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04d400-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04f400-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xf800-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfec0-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed18000-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed2-0x000 For the rest of this I attached a Logitech M317 mouse. Here's the requested output with out-of-box settings: lance@lance-e6400:~$ sudo libinput list-devices [sudo] password for lance: Device: Video Bus Kernel: /dev/input/event8 Group:1 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Power Button Kernel: /dev/input/event1 Group:2 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Lid Switch Kernel: /dev/input/event0 Group:3 Seat: seat0, default Capabilities: switch Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Sleep Button Kernel: /dev/input/event2 Group:4 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: HID 413c:8157 Kernel: /dev/input/event4 Group:5 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: HDA Intel Dock Mic Kernel: /dev/input/event9 Group:6 Seat: seat0, default Capabilities: Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none
[Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing
** Tags added: eoan gnome-panel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743686 Title: File system folder in nautilus Artful/Bionic flashback session does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1743686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845898] [NEW] Unable to set touchpad Edge Scrolling in Eoan
Public bug reported: After installing the Eoan Beta on a Dell Latitude E6400 attempting to set touchpad Edge Scrolling was unsuccessful. It actually seemed to work as long as the System Settings window was left open but as soon as the window is closed the Edge Scrolling setting reverts to off. I did however find that simply installing the package 'xserver-xorg- input-synaptics' solves the problem. In fact it adds the additional setting option of Two Finger Scrolling to the control center UI. I'm not sure if that package should be installed by default or not? Steps to reproduce are simple: (1) Install Ubuntu Eoan on a laptop (could possibly work with a keyboard with an incorporated touchpad). (2) Open Gnome Control Center (System Settings) and go to Devices > Mouse & Touchpad. (3) Select Edge Scrolling and you'll notice the "button" turn green. Close System Settings. (4) Reopen System Settings and you'll see Edge Scrolling has turned off again. (5) Install 'xserver-xorg-input-synaptics' and then reboot. (6) Repeat the above steps and you'll find that setting Edge Scrolling is successful even after closing System Settings. Additionally you'll find that a new Two Finger Scrolling option has been added to the UI. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 29 22:15:09 2019 InstallationDate: Installed on 2019-09-30 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) 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-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845898 Title: Unable to set touchpad Edge Scrolling in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input
I will follow up ASAP. The plot continues to thicken. I tried a different set of hardware today with a B43 chipset and it didn't seem to be effected. But that board has only DVI and VGA outputs whereas the effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI so now I ran another range of tests using DVI on the effected board and was unable to reproduce. So this appears to effect a very selective subset of 10 to 12 year old hardware. Must be Intel X4500 graphics with HDMI connection and possibly only the G43 chipset. So it's the absolute corneriest of corner issues I've ever encountered. And the workaround couldn't be any simpler - just remove the "quiet splash" boot parameter and all seems well (both boot to and logout to gdm3 screen). BTW ASAP may be rather slow in coming because I have a few medical procedures scheduled in the next few weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input
Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just displays a blank page. Also applying the workaround from bug 994921 does not result in creating a crash report. I started testing Ubuntu Disco 20190416 tonight and knowing what I know now I can say with certainty that the easiest way to reproduce this bug (on effected hardware) is to perform a fresh install choosing NOT to auto-login. Then the first boot will be OK but each subsequent boot will produce a black screen - that is the gdm3 login screen never appears and it's not possible to enter a TTY. But once "quiet splash" is removed via grub the system boots as it should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input
Based on those most recent results I ran "dpkg-reconfigure grub-pc" and removed "quiet splash". Now it boots to the gdm3 screen every time. So maybe something to do with how plymouth hands off the boot process to gdm3? Or how quickly that hand off is completed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
This was tricky but I finally got a successful boot (following several failed boots) using gdm3 by selecting the kernel with "e" from grub and then removing 'quiet splash'. So I hope this is more helpful. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256203/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
Method used to collect this info: (1) Fresh installed 20190413.2 choosing not to auto-login. (2) Rebooted after install and surprisingly gdm3 appeared as it should so I booted to desktop and just rebooted. (3) That reboot failed as had been the previous case - just a black screen, totally unresponsive. (4) Performed a hard reboot with the reset button on the PC, entered recovery from grub menu, then installed lightdm, and rebooted. (5) Collected info as instructed. So there are a total of 3 boots. The first was successful - no problems. The second booted to a black screen instead of displaying gdm3 screen. Third boot was performed using lightdm. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256045/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
As requested. Definitely C2D era board (Intel DG43GT) running a Pentium Dual Core. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256044/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
Slight change in behavior testing a fresh install of 20190413.2 - if installed with auto-login switched on logout did load and give the expected choices of Ubuntu and Ubuntu w/Wayland. But if auto-login is turned off I still get a black screen on reboot. I suspect that gdm3 is not even loading because I've tried blindly opening a tty, logging in as root, and sudo reboot but nothing happens. Once again just installing lightdm (I haven't tried the old unity- greeter) gives me a working machine. By looking at the changelog nothing has changed in gdm3 so I'm unsure why the logout behavior would have improved with a 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/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824672] [NEW] Disco "check disc for defects" appears not to function
Public bug reported: Just testing the 20190413.2 image and after selecting "check disc for defects" the Ubuntu splash screen appears very briefly, no testing text is displayed, and a "no errors found" message appears in under one minute. As recently as 20190326.2 the test ran as expected displaying "scrolling" text on screen before completing and reporting a pass or fail so I doubt this was an intentional change but I could be mistaken. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: syslinux 3:6.04~git20171011.af7e95c3+dfsg1-6 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.403 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 23:43:46 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: syslinux (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/1824672 Title: Disco "check disc for defects" appears not to function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1824672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
This does appear to be hardware related because I encounter no problem on a box with Intel G41 graphics but the X4500 is a no-go with gdm3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
I found that turning auto-login off resulted in booting to a black screen so after unsuccessfully trying the nomodeset boot option I installed 'lightdm-gtk-greeter' and 'lightdm' from recovery mode which gives me a working system. I had encountered no problems with desktop behavior but this box has Intel GMA X4500 graphics (old-ish I know) so I wonder if it could be related to bug #1727356? Having installed 'gnome-shell-extensions' package from the repos I'm able to boot and run all three available sessions - Ubuntu, Ubuntu w/Wayland, and "Classic" with no apparent issues as long as I use lightdm instead of gdm3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
** Summary changed: - Ubuntu Disco logs out to black screen + Ubuntu Disco boots to or logs out to black screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] [NEW] Ubuntu Disco logs out to black screen
Public bug reported: Just testing Disco and wanted to see what login options are available after adding 'gnome-shell-extensions' and found that logging out lands me on a black screen that's unresponsive to any keyboard input. I'll test on some slightly different hardware soon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 16:18:56 2019 InstallationDate: Installed on 2019-04-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) 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) mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523 ** Affects: gdm3 (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/1824588 Title: Ubuntu Disco logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
** Description changed: This is intentionally a duplicate of bug #1817485 to collect info on a fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's default session is also effected. I just wanted to collect all pertinent logs to prove that this was in fact an unmolested install. As in the previously filed bug report once over-amplification is switched on only the volume slider in the top panel actually increases - the sound above 100%. Neither the slider in the sound settings UI or the - keyboard volume hot keys will increase the sound above 100%. + the sound above 100%. The slider in the sound settings UI will not + increase the sound above 100%. The keyboard hot-keys are also effected + in the flashback session, but NOT the default Ubuntu session. - So, in use as an HTPC, if you're streaming content in full screen and - have the sound set above 100%, when a blaring loud commercial comes on - and you turn the volume down with the keyboard hot keys you can't use - the keyboard hot-keys to return to that over-amplified state. + So if using the flashback session, in use as an HTPC, if you're + streaming content in full screen and have the sound set above 100%, when + a blaring loud commercial comes on and you turn the volume down with the + keyboard hot keys you can't use the keyboard hot-keys to return to that + over-amplified state. In the default Ubuntu session the hot-keys + function as expected. I'm attaching a screenshot. A logout is necessary for the over- amplification setting to take effect so the steps to reproduce are as follows: (1) Open System Settings > Sound (2) Toggle Over-Amplification to On (3) logout and then log back into the default session (this is required) (4) Open System Settings > Sound and toggle the volume slider to the left, then all the way to the right. (5) Click on the volume icon in the top panel and you'll see that it's only at about 66% - obviously the two should "sync" but do not ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 14:25:01 2019 InstallationDate: Installed on 2019-02-25 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
One more difference between the default and flashback sessions is that the keyboard hot-keys DO work in the default Ubuntu session, but NOT in the flashback session. So that makes this even a lower priority, and passes part of the responsibility onto the flashback devs. ** Tags added: gnome-panel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
** Description changed: This is intentionally a duplicate of bug #1817485 to collect info on a fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's default session is also effected. I just wanted to collect all pertinent logs to prove that this was in fact an unmolested install. As in the previously filed bug report once over-amplification is switched on only the volume slider in the top panel actually increases the sound above 100%. Neither the slider in the sound settings UI or the keyboard volume hot keys will increase the sound above 100%. So, in use as an HTPC, if you're streaming content in full screen and have the sound set above 100%, when a blaring loud commercial comes on and you turn the volume down with the keyboard hot keys you can't use the keyboard hot-keys to return to that over-amplified state. - I'm attaching a screenshot and I'll also update this with a full step by - step process to reproduce the bug. Either a reboot or logout is required - for the changes to take effect after switching over-amplification on (or - maybe off too). I just need to rinse-n-repeat a few times to be sure so - you won't have to waste time trying to reproduce. + I'm attaching a screenshot. A logout is necessary for the over- + amplification setting to take effect so the steps to reproduce are as + follows: + + (1) Open System Settings > Sound + (2) Toggle Over-Amplification to On + (3) logout and then log back into the default session (this is required) + (4) Open System Settings > Sound and toggle the volume slider to the left, then all the way to the right. + (5) Click on the volume icon in the top panel and you'll see that it's only at about 66% - obviously the two should "sync" but do not ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 14:25:01 2019 InstallationDate: Installed on 2019-02-25 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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: gnome-control-center 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/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
Actually only a logout is necessary for the UI and volume slider to respond to the amp change. So I'll add steps to reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817485] Re: Bionic "amplified" sound controls do not sync with volume slider
Actually this specific issue effects the default Ubuntu session as well. I did a fresh install of 18.04.2, installed updates, rebooted, and checked it out to be sure. Then I filed bug #1817625 so one or the other needs to be marked a duplicate (and changed back to "new" rather than "invalid"). I just wanted to collect all the logs so you could see I'm not pulling your leg about the default Ubuntu session being effected. I had not realized that the default Ubuntu session had a UI for over- amplification whereas flashback session does not. Since it can be set via dconf I'm unlikely to file a new bug report just for that. I should however check to be sure flashback doesn't "break" things in a default session. I just got lazy yesterday and filed this bug report from my workhorse PC rather than using my friends new HTPC. I'm going to rinse-n-repeat the steps to reproduce this in that unmolested install of Bionic. It seems that either a reboot or logout is needed after selecting over-amplification = on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817485 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] [NEW] Bionic "amplified" sound controls do not sync with volume slider
Public bug reported: This is intentionally a duplicate of bug #1817485 to collect info on a fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's default session is also effected. I just wanted to collect all pertinent logs to prove that this was in fact an unmolested install. As in the previously filed bug report once over-amplification is switched on only the volume slider in the top panel actually increases the sound above 100%. Neither the slider in the sound settings UI or the keyboard volume hot keys will increase the sound above 100%. So, in use as an HTPC, if you're streaming content in full screen and have the sound set above 100%, when a blaring loud commercial comes on and you turn the volume down with the keyboard hot keys you can't use the keyboard hot-keys to return to that over-amplified state. I'm attaching a screenshot and I'll also update this with a full step by step process to reproduce the bug. Either a reboot or logout is required for the changes to take effect after switching over-amplification on (or maybe off too). I just need to rinse-n-repeat a few times to be sure so you won't have to waste time trying to reproduce. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 14:25:01 2019 InstallationDate: Installed on 2019-02-25 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2019-02-25 14-18-10.png" https://bugs.launchpad.net/bugs/1817625/+attachment/5241665/+files/Screenshot%20from%202019-02-25%2014-18-10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817485] Re: Bionic "amplified" sound controls do not sync with volume slider
Bionic no longer displays allow above 100% in the sound settings UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817485 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817485] [NEW] Bionic "amplified" sound controls do not sync with volume slider
Public bug reported: I'm just setting up my first Bionic HTPC and I notice that if you select allow-amplified-volume in dconf that change only applies to the volume slider, not to the sound control UI. This results in the volume hot-keys not controlling sound above 100%. So if you're watching video content in full screen you must ESC, then use the volume slider, and then go back to full screen. It makes for an unwieldy process so using a different DE becomes a temptation. You can see what I'm talking about in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Sun Feb 24 14:10:03 2019 InstallationDate: Installed on 2018-01-28 (391 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-08-15 (193 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Screenshot from 2019-02-24 14-27-44.png" https://bugs.launchpad.net/bugs/1817485/+attachment/5241405/+files/Screenshot%20from%202019-02-24%2014-27-44.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817485 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816687] [NEW] Bionic pavucontrol fails to set default device if usb sink or source exists
Public bug reported: Just as the title says, if a usb sound card is in use pavucontol's settings are ignored. This appears to be an unintended result of the changes made to address bug #1702794. Specifically if you now look at /etc/pulse/default.pa you'll find this section: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif So you must comment out those three lines in order for pavucontrol device default settings to be respected if a usb sound card is plugged in at reboot or startup. It's not a big deal but I hadn't run across this in the past and couldn't find an existing bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pavucontrol 3.0-4 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Feb 19 21:05:18 2019 InstallationDate: Installed on 2018-01-28 (387 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pavucontrol UpgradeStatus: Upgraded to bionic on 2018-08-15 (188 days ago) ** Affects: pavucontrol (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816687 Title: Bionic pavucontrol fails to set default device if usb sink or source exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1816687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489147] Re: Booting live Wily image results in black screen with or without random text
Wily is long past EOL. If anyone is still experiencing this bug with a supported version it would probably be best to open a new bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489147 Title: Booting live Wily image results in black screen with or without random text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737836] Re: Standard clock applet is oversized in Artful
Will we be able to push a patch into gnome-panel 1:3.26 in Bionic since it's an LTS supported until 2023? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing
It seems to me that the most sensible approach would be to just remove the Computer button from the Places menu. Then you'd just open Home and select Other Locations. I think that would be more in keeping with the latest Nautilus redesign. I'm not at all sure but we may want to do likewise with the Network button in the Places menu because it's now also accessible via Home -> Other Locations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743686 Title: File system folder in nautilus Artful/Bionic flashback session does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1743686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737836] Re: Standard clock applet is oversized in Artful
Sorry to take so long getting back to this. Disabling "show weather" and "show temp" helps reduce that dead space but it must be done after each boot or reboot because the settings don't "stick". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754200] [NEW] Ubiquity crashed while installing Lubuntu Bionic
Public bug reported: Just performing a manual partitioning install using Lubuntu Bionic 20180306.1 amd64 and the installer crashed and generated this report. The only thing I did that may be "odd" is creating a SWAP partition during installation. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.389 Date: Wed Mar 7 18:28:04 2018 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --- JournalErrors: Error: command ['journalctl', '-b', '--priority=err', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic lubuntu ubiquity-18.04.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754200 Title: Ubiquity crashed while installing Lubuntu Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
