[Touch-packages] [Bug 1826516] Re: bluetooh mouse lag when use bluetooth hedphones
** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1826516 Title: bluetooh mouse lag when use bluetooth hedphones Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have Microsoft Sculpt Comfort Mouse (bluettoh) and it works. When i connect my bluetooth heaset (plantronics PLT 50) mouse cursor lags terribly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 09:19:08 2019 InstallationDate: Installed on 2018-12-22 (124 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20LW000YPB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.9-050009-generic root=UUID=74c51606-28cc-4d8f-91ac-c1d0dfd082c3 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW000YPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET54W(1.31):bd01/21/2019:svnLENOVO:pn20LW000YPB:pvrThinkPadL580:rvnLENOVO:rn20LW000YPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW000YPB dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:21:6B:EA:3C:5F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:21050738 acl:78587 sco:377825 events:21982 errors:0 TX bytes:19896288 acl:159 sco:377811 commands:5333 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2019-04-15T07:00:56.250208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1826516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751144] Re: xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1751144 Title: xorg Status in xorg package in Ubuntu: Incomplete Bug description: xorg ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-35-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 22 15:33:01 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 6450 [1028:2120] Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 6450 [1028:2120] MachineType: Dell Inc. OptiPlex 990 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-35-generic root=/dev/mapper/ubuntu--gnome--vg-root ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.89+git20180214.e75e0ea2-0ubuntu0ricotz~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~git20180214+18.0.1e173463-0ubuntu0ricotz~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~git20180214+18.0.1e173463-0ubuntu0ricotz~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770792] Re: Clean up sync blacklist
[Expired for ubuntu-meta (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1770792 Title: Clean up sync blacklist Status in ubuntu-meta package in Ubuntu: Expired Bug description: I am attaching a bzr branch here. Because the sync blacklist is a "junk" bzr repository, Launchpad isn't letting me make a merge proposal for it. I think it makes the blacklist easier to read and use if we get rid of all the old entries. I went through and verified that these removals were removed from Debian. There are a few exceptions (gdm3 and openssl1.0) which didn't need to be blacklisted anymore. I mostly ignored the Mozilla extensions. The Mozilla situation is interesting this year, but I'll save that discussion for later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1770792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832967] Re: /etc/resolv.conf does not include the local domain name
> This is also described here: https://askubuntu.com/a/1041631/326601 That describes an unrelated issue. ** Description changed: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. - - This is also described here: https://askubuntu.com/a/1041631/326601 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1832967 Title: /etc/resolv.conf does not include the local domain name Status in resolvconf package in Ubuntu: Incomplete Bug description: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1832967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832967] Re: /etc/resolv.conf does not include the local domain name
> When I rebooted my system after an update, `/etc/resolv.conf` was > symlinked to `/run/resolvconf/resolv.conf` That is as expected, if you have the resolvconf package installed. > That file did not have my local domain name in the search even though > it is supplied by the dhcp server. The systemd resolv.conf file (in > `/run/systemd/resolve/resolv.conf`) had the correct search information. What are the contents of /run/resolvconf/interface/ on this system? ** Changed in: resolvconf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1832967 Title: /etc/resolv.conf does not include the local domain name Status in resolvconf package in Ubuntu: Incomplete Bug description: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1832967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832967] Re: /etc/resolv.conf does not include the local domain name
In particular, note that /lib/systemd/system/resolvconf-pull- resolved.{service,path} are meant to populate /run/resolvconf/interface /systemd-resolved using the contents of /run/systemd/resolve/stub- resolv.conf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1832967 Title: /etc/resolv.conf does not include the local domain name Status in resolvconf package in Ubuntu: Incomplete Bug description: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1832967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833025] [NEW] bcache partition within fstab prevents from booting
Public bug reported: Almost every boot attempt drops to initramfs prompt, requiring me to type echo /dev/sdb >/sys/fs/bcache/register. Logs showing that attempt to register caching device via udev rules was made, but failed with code == 1. Looks like an regression were introduced in upstream (systemd 240) which breaks the order of udev commands. Here is an upstream bug https://github.com/systemd/systemd/issues/11368 And here is a patch for this issue https://github.com/systemd/systemd/pull/11891 Can you, please merge this patch to disco branch? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833025 Title: bcache partition within fstab prevents from booting Status in systemd package in Ubuntu: New Bug description: Almost every boot attempt drops to initramfs prompt, requiring me to type echo /dev/sdb >/sys/fs/bcache/register. Logs showing that attempt to register caching device via udev rules was made, but failed with code == 1. Looks like an regression were introduced in upstream (systemd 240) which breaks the order of udev commands. Here is an upstream bug https://github.com/systemd/systemd/issues/11368 And here is a patch for this issue https://github.com/systemd/systemd/pull/11891 Can you, please merge this patch to disco branch? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832959] Re: Wrong cursor size after screensaver
** Tags added: cursor hidpi ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Wrong cursor size after screensaver + [hidpi] Cursor is too small after screensaver ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1832959 Title: [hidpi] Cursor is too small after screensaver Status in gnome-shell package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi all, I have a HiDPI screen (2880x1620) with 2x scaling (default). Everything worked well for months until some of the upgrades broke something. The problem is with cursor size. It has 2x or even 4x less size (very small) after returning from screensaver/locking screen. So, for example, if i suspend and then resume my laptop or just lock the screen and then type the password to unlock. Curiously, but the problem becomes fixed if i take a screenshot by pressing Print Screen. In this case the cursor size immediately becomes the correct size. Some more tips: 1. If i press Ctrl-Alt-F1 (where the gdm is running) the cursor has correct size. 2. If i then press Ctrl-Alt-F2 and switch back to my current session, it again becomes 2x-4x less size. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 00:24:41 2019 DistUpgraded: 2019-04-02 21:54:52,265 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 430.26, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor Integrated Graphics Controller [1462:10fd] Subsystem: Micro-Star International Co., Ltd. [MSI] GK104M [GeForce GTX 870M] [1462:10fd] InstallationDate: Installed on 2018-11-13 (214 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Micro-Star International Co., Ltd. GS60 2PE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=bc6d974d-dac7-4fef-a6ad-c78c6be040e4 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-02 (74 days ago) dmi.bios.date: 05/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.106:bd05/13/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GS60 2PE dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759008] Re: Revert automatic suspend by default for bionic?
This bug is closed. If you have any issues at all then please open a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1759008 Title: Revert automatic suspend by default for bionic? Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Bionic: Fix Released Bug description: GNOME 3.28 has turned Automatic Suspend on by default and set it to 20 minutes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa I generally think this is a good thing. There are a few issues though. 1. The computer will still suspend even if there are remote users logged in or the computer is being used as a server for files, printers, etc. 2. Some software doesn't set inhibit correctly. ~ahasenack mentioned he was using the Spotify Snap and the computer suspend after 20 minutes. (Maybe Spotify needs to use the screen-inhibit-control snap interface.) 3. Even if it does set inhibit, there is a report that the computer will suspend as soon as the inhibit is removed if there is no other activity. (Imagine a movie playing. At the end of the movie, the computer goes to sleep immediately.) More details and proposed fix at https://bugzilla.gnome.org/show_bug.cgi?id=705942#c21 4. There is no GUI way to change this setting for the login screen yet. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22 5. Some users think that desktop computers should be always running unless told otherwise. Personally, I don't give this argument much weight at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1759008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session
On brainwash's suggestion (IRC #xubuntu-devel) I disabled UPower's Lid handling with /etc/UPower/UPower.conf: IgnoreLid=true After six suspend-resume cycles this does seem to have prevented the issue. *However* I then noticed that in the x-p-m dialog, General tab, the options to control the Lid Close policy are completely missing - which isn't really a solution. This just seems to confirm the bug here is in the interactions of x-p-m /light-locker and logind. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833010] [NEW] PCI/internal sound card not detected
Public bug reported: Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william1931 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 22:29:12 2019 InstallationDate: Installed on 2019-06-14 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: LINX1010B.R22.03.010 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrLINX1010B.R22.03.010:bd07/24/2015:svnLINX:pnLINX1010B:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: LINX1010B dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: LINX ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1833010 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william1931 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 22:29:12 2019 InstallationDate: Installed on 2019-06-14 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: LINX1010B.R22.03.010 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrLINX1010B.R22.03.010:bd07/24/2015:svnLINX:pnLINX1010B:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: LINX1010B dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: LINX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822380] Re: Thunar right-click menu not expanded
A workaround is not a proper fix. Would it not make more sense to revert the GTK commit which broke the menu behavior? ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1822380 Title: Thunar right-click menu not expanded Status in GTK+: New Status in Thunar File Manager: Fix Released Status in gtk+3.0 package in Ubuntu: New Status in thunar package in Ubuntu: Fix Released Bug description: Submitting this bug report with the SRU template, but hopefully we can go ahead have this uploaded before the final images have been built. [Impact] * The "Create Document" submenu in Thunar does not expand to a usable length. * The submenu is displayed at just a few pixels tall, enough to see menu items as you scroll, but not enough to read any item. * This breaks a standard use case for file managers: creating new files. * The proposed upload fixes the bug by loading the menu items synchronously, making the menu load with the items already populated instead of having to redraw once the items are added. * The patch provided comes from the upstream maintainer. [Test Case] * Open Thunar. * Right click in the blank space (not on an item). * Move the cursor to the "Create Document" menu. * Bug Present: The submenu is displayed but short, and no items are visible. * Bug Resolved: The submenu is displayed, items present in the ~/Templates folder are displayed. [Regression Potential] * Regression potential is minimal: * The modified code affects only the drawing of the submenu items. * The submenu is already ununsable, no items are displayed. * Some limited testing has already been completed: * 2 users confirmed the patch fixes the issue on the upstream bug report. * 2 Xubuntu team members (bluesabre, Unit193) have also confirmed the patch and no regressions. [Original Report] In Thunar, when I right click to create a new file, the menu shows up so small that I can't see the options. I have rebooted and the problem persists. Haven't checked other file managers yet. Running Xubuntu 19.04 (Development Branch), Thunar 1.8.4. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunar 1.8.4-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 16:41:29 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: thunar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1822380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session
And it gets weirder... with supend-lock disabled AND leaving x-p-m dialog box on screen whilst suspending the LCD always gets enabled on resume! I tried leaving other application windows open but those don't have the same effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session
Update: Disabling x-p-m Security > Lock screen when system is going to sleep causes the LCD to be blank resume for the 1st cycle. This definitely feels like some weird interaction with x-p-m, light- locker, and logind. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session
I've done some more tests with another clean install of 19.04; The only user setting I changed was on x-p-m for Laptop Lid Closed, On Battery = suspend. 1st suspend=resume cycle is fine; user session re-appears after unlocking with password *BUT* 2nd suspend-resume cycle turns the LCD panel off after unlocking with password (greeter with password dialog is show, LCD is turned off as soon as session is unlocked. This is repeatable via using a TTY to "sudo systemctl restart lightdm" So it seems as if there's some runtime option getting mixed up here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833001] [NEW] openssl should register libraries/restart-without-asking template or handle gracefully when it is missing
Public bug reported: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing ** Affects: openssl (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Changed in: openssl (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833001 Title: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing Status in openssl package in Ubuntu: New Bug description: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1833001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832964] Re: Suggested fix/enhancement for wireless-tools.if-pre-up script
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930585 ** Bug watch added: Debian Bug tracker #930585 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930585 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wireless-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832964 Title: Suggested fix/enhancement for wireless-tools.if-pre-up script Status in wireless-tools package in Ubuntu: New Bug description: I've been experiencing an issue with my wireless card and ifup relating to this script. I have a fix for it and thought the devs here might be interested. This is the issue: If a setting fails to be applied, the script brings the card up and then tries to apply the setting again. This is fine, but it leaves the card up. Later on in the ifup process other scripts try to access the card and if the card is up it will respond that it's busy and ifup fails. My solution has been to alter the wireless-tools if-pre-up script so that it ends by running ifconfig down in this case. Here is the patch: --- ./wireless-tools.if-pre-up2017-04-22 10:15:05.0 -0400 +++ ./wireless-tools 2019-06-03 22:39:24.314725863 -0400 @@ -6,7 +6,7 @@ exit 0 fi -# check if this is a 802.11 device we're supposed to be effecting +# check if this is a 802.11 device we're supposed to be affecting case "${IF_WIRELESS:-enable}" in wireless-tools|iwconfig) # *we* and not some other 802.11 tool should be used @@ -140,4 +140,5 @@ FAIL= ifconfig "$IFACE" up apply_settings + ifconfig "$IFACE" down fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/1832964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp