[Touch-packages] [Bug 1759644] [NEW] [18.04] Regression: wired network does not work upon resume from suspend
Public bug reported: After upgrade to 18.04 (bionic) I've encountered the following regression: wired network connection does not work, when system is resumed from suspend. Reloading the kernel driver module seems to help: sudo modprobe -r r8169 sudo modprobe r8169 Could this be fixed structurally? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 20:08:20 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-01-06 (811 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 ethernet 1522260260 wo 28 mrt 2018 20:04:20 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/3 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- dzente a899e56b-4048-43a8-bc38-9212d0af383b wifi 1493769143 wo 03 mei 2017 01:52:23 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp5s0 ethernet connected/org/freedesktop/NetworkManager/Devices/4 Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1759644 Title: [18.04] Regression: wired network does not work upon resume from suspend Status in network-manager package in Ubuntu: New Bug description: After upgrade to 18.04 (bionic) I've encountered the following regression: wired network connection does not work, when system is resumed from suspend. Reloading the kernel driver module seems to help: sudo modprobe -r r8169 sudo modprobe r8169 Could this be fixed structurally? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 20:08:20 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-01-06 (811 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10
Another possible duplicate: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1676547 Title: No network connectivity after upgrade from 16.04 to 16.10 Status in network-manager package in Ubuntu: In Progress Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: In Progress Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed before rebooting you should have a network connection after you reboot. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install netplan, configure to set up static network on an ethernet device using netplan. 4) Upgrade to yakkety 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1675934] Re: Screen corruption after resuming system from suspend
** Attachment added: "bug_2017-03-24_22-22-32.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+attachment/4845050/+files/bug_2017-03-24_22-22-32.png -- 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/1675934 Title: Screen corruption after resuming system from suspend Status in xorg package in Ubuntu: New Bug description: Upon resuming system from suspend I observe graphical artefacts. This is a regression, since I've noticed this behaviour only after latest updates. Rebooting system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 22:20:38 2017 DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4] InstallationDate: Installed on 2016-01-06 (442 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock 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.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Mar 23 19:44:08 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+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 1675934] [NEW] Screen corruption after resuming system from suspend
Public bug reported: Upon resuming system from suspend I observe graphical artefacts. This is a regression, since I've noticed this behaviour only after latest updates. Rebooting system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 22:20:38 2017 DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4] InstallationDate: Installed on 2016-01-06 (442 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock 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.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Mar 23 19:44:08 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial -- 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/1675934 Title: Screen corruption after resuming system from suspend Status in xorg package in Ubuntu: New Bug description: Upon resuming system from suspend I observe graphical artefacts. This is a regression, since I've noticed this behaviour only after latest updates. Rebooting system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0'
Re: [Touch-packages] [Bug 1546733] Re: Update of today screen messes up scopes layout.
+1 On Fri, Jun 3, 2016 at 3:26 AM, Anupam <1546...@bugs.launchpad.net> wrote: > just experienced once again, even after updating to OTA-11 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1546733 > > Title: > Update of today screen messes up scopes layout. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1546733 Title: Update of today screen messes up scopes layout. Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: BQ4.5, OTA9, official channel. Observed the following: * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1570040] [NEW] [Feature request] In dual-SIM configurations show SIM-card used in call list
Public bug reported: In dual-SIM configurations, when phone receives a call, SIM-card in use is being indicated. The list of calls does not show this information, however. It is only available in the call details. Providing this information in a list of calls will help user to phone back using appropriate SIM-card/phone number. Moreover, it would be logical to select the SIM card used to receive the call for placing an outgoing call. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1570040 Title: [Feature request] In dual-SIM configurations show SIM-card used in call list Status in dialer-app package in Ubuntu: New Bug description: In dual-SIM configurations, when phone receives a call, SIM-card in use is being indicated. The list of calls does not show this information, however. It is only available in the call details. Providing this information in a list of calls will help user to phone back using appropriate SIM-card/phone number. Moreover, it would be logical to select the SIM card used to receive the call for placing an outgoing call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1570040/+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
Re: [Touch-packages] [Bug 1551976] Re: Headphones not activated after unplugging/plugging-in
Puzzled... Was this instruction for me to do something??? On Wed, Mar 2, 2016 at 12:51 AM, Raymond <1551...@bugs.launchpad.net> wrote: > ports: analog-input-front-mic: Front Microphone (priority 8500, latency > offset 0 usec, available: no) properties: device.icon_name = "audio- > input-microphone" analog-input-rear-mic: Rear Microphone (priority 8200, > latency offset 0 usec, available: no) properties: device.icon_name = > "audio-input-microphone" analog-input-linein: Line In (priority 8100, > latency offset 0 usec, available: no) properties: analog-output-lineout: > Line Out (priority 9900, latency offset 0 usec, available: no) > properties: analog-output-headphones: Headphones (priority 9000, latency > offset 0 usec, available: yes) properties: device.icon_name = "audio- > headphones" iec958-stereo-output: Digital Output (S/PDIF) (priority 0, > latency offset 0 usec, available: unknown) properties: > > Seem no line out plugged, do pulseaudio switch to digial after headphone > is unplugged > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1551976 > > Title: > Headphones not activated after unplugging/plugging-in > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+subscriptions > -- 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/1551976 Title: Headphones not activated after unplugging/plugging-in Status in alsa-driver package in Ubuntu: Incomplete Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock 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.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+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 1551976] [NEW] Headphones not activated after unplugging/plugging-in
Public bug reported: Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock 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.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1551976 Title: Headphones not activated after unplugging/plugging-in Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock 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.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
Re: [Touch-packages] [Bug 1546733] Re: Update of today screen messes up scopes layout.
Interesting... Pawel: Could you please provide a couple of words, why change of status to invalid? P.S. Maybe a good idea to always provide a short rationale for change of status? On Thu, Feb 18, 2016 at 1:06 PM, Pawel Stolowski <1546...@bugs.launchpad.net > wrote: > ** Changed in: unity-scopes-shell (Ubuntu) >Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1546733 > > Title: > Update of today screen messes up scopes layout. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1546733 Title: Update of today screen messes up scopes layout. Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: BQ4.5, OTA9, official channel. Observed the following: * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1546733/+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
Re: [Touch-packages] [Bug 1546733] [NEW] Update of today screen messes up scopes layout.
Albert: No, after reboot refresh works OK. On Thursday, February 18, 2016, Albert Astals Cid < albert.ast...@canonical.com> wrote: > Alexey: If you reboot can you get > https://launchpadlibrarian.net/240240439/step01.png just by pulling down > the today scope to refresh? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1546733 > > Title: > Update of today screen messes up scopes layout. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1546733 Title: Update of today screen messes up scopes layout. Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: BQ4.5, OTA9, official channel. Observed the following: * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.
Nope, no sign of .crash files. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1546733 Title: Update of today screen messes up scopes layout. Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ4.5, OTA9, official channel. Observed the following: * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.
** Attachment added: "scope-registry.log" https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573922/+files/scope-registry.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1546733 Title: Update of today screen messes up scopes layout. Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ4.5, OTA9, official channel. Observed the following: * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.
** Attachment added: "unity8.log" https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573921/+files/unity8.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1546733 Title: Update of today screen messes up scopes layout. Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ4.5, OTA9, official channel. Observed the following: * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.
** Attachment added: "unity8-dash.log" https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573920/+files/unity8-dash.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1546733 Title: Update of today screen messes up scopes layout. Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ4.5, OTA9, official channel. Observed the following: * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1491566] Re: Shell not responsive after an incoming SMS
Wanted to apply patches from #12 and #13, but files are read-only. Looks like I miss some knowledge. Any pointers are welcome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Shell not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Incomplete Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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
Re: [Touch-packages] [Bug 1491566] Re: Greeter and edges not responsive after an incoming SMS
Actually, I tried buttons, there was no visible reaction on the presses: * volume buttons (even attempted to get a screenshot, but it is not present on the phone, so it did not work) * power button. could not even reboot the phone (or maybe have not waited long enough? pressed on it for about a minute), had to do reboot via shell The only part that still was updating on the screen - notification area. Noticed, because charging was indicated upon connection of the phone to the PC. On Fri, Sep 4, 2015 at 10:59 AM, Launchpad Bug Tracker < 1491...@bugs.launchpad.net> wrote: > Status changed to 'Confirmed' because the bug affects multiple users. > > ** Changed in: unity-system-compositor (Ubuntu) >Status: New => Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1491566 > > Title: > Greeter and edges not responsive after an incoming SMS > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Greeter and edges not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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 1491566] Re: Greeter and edges not responsive after an incoming SMS
Attaching unity8.log as advised by Pat McGowan. ** Attachment added: "unity8.log.1.gz" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1491566/+attachment/4456964/+files/unity8.log.1.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Greeter and edges not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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 1491566] Re: Greeter and edges not responsive after an incoming SMS
Observed similar issue on BQ E4.5., r25 (after OTA6 update). Dialer locked UI. Happened after dialing back via activation of dialer from missed call notification (without unlocking the phone). Dialer remains on the foreground and phone UI seems to be stuck. At the same time, icons in the notification area are being updated (clock, battery, network status), but there seem to be no way to access notification area or unlock the phone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Greeter and edges not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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
Re: [Touch-packages] [Bug 1465051] Re: Lock screen does not react on input/swipes
Once device unlocked, all functionality seems to be OK: yes, I can switch between apps/start apps using launcher, also can switch between apps/kill apps using swipe from right. On Mon, Jun 15, 2015 at 10:25 AM, Michael Zanetti michael.zane...@canonical.com wrote: Once the device is unlocked, do the edges work again? I.e. Can you switch apps using the right edge or pull in the launcher? ** Changed in: unity8 (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1465051 Title: Lock screen does not react on input/swipes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465051/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1465051 Title: Lock screen does not react on input/swipes Status in unity8 package in Ubuntu: Incomplete Bug description: Can't get to unlock: when I try to swipe away lock screen nothing happens. Can get beyond the screen using active icons in the notification area, e.g. if I select battery indicator and then options, input secret code screen gets activated and I can access the device. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Sun Jun 14 21:42:48 2015 InstallationDate: Installed on 2015-05-08 (37 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150508-031218) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465051/+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 1465051] [NEW] Lock screen does not react on input/swipes
Public bug reported: Can't get to unlock: when I try to swipe away lock screen nothing happens. Can get beyond the screen using active icons in the notification area, e.g. if I select battery indicator and then options, input secret code screen gets activated and I can access the device. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Sun Jun 14 21:42:48 2015 InstallationDate: Installed on 2015-05-08 (37 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150508-031218) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1465051 Title: Lock screen does not react on input/swipes Status in unity8 package in Ubuntu: Confirmed Bug description: Can't get to unlock: when I try to swipe away lock screen nothing happens. Can get beyond the screen using active icons in the notification area, e.g. if I select battery indicator and then options, input secret code screen gets activated and I can access the device. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Sun Jun 14 21:42:48 2015 InstallationDate: Installed on 2015-05-08 (37 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150508-031218) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465051/+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