[Touch-packages] [Bug 1992701] Re: Issue with opening module dependency file
Update to keep it alive ** Changed in: kmod (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1992701 Title: Issue with opening module dependency file Status in kmod package in Ubuntu: New Bug description: Tested on: Trusty, Xenial (used as recovery system) I'm unable to manage (modprobe, insmod) modules due following error: "modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'" I don't know why, but it seem like in the libkmod.c was a bug that attempt to load an old kernel after it got upgraded (replaced with) a newer one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1992701/+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 1992701] Re: Issue with opening module dependency file
The system id started up as a LiveCD from a burned out ISO.nl After upgrading thr kernel, there was no 4eboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1992701 Title: Issue with opening module dependency file Status in kmod package in Ubuntu: Incomplete Bug description: Tested on: Trusty, Xenial (used as recovery system) I'm unable to manage (modprobe, insmod) modules due following error: "modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'" I don't know why, but it seem like in the libkmod.c was a bug that attempt to load an old kernel after it got upgraded (replaced with) a newer one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1992701/+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 1992701] [NEW] Issue with opening module dependency file
Public bug reported: Tested on: Trusty, Xenial (used as recovery system) I'm unable to manage (modprobe, insmod) modules due following error: "modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'" I don't know why, but it seem like in the libkmod.c was a bug that attempt to load an old kernel after it got upgraded (replaced with) a newer one. ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Tags: kmod ** Attachment added: "Screenshoot of the error message in terminal" https://bugs.launchpad.net/bugs/1992701/+attachment/5623647/+files/kmod_error.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1992701 Title: Issue with opening module dependency file Status in kmod package in Ubuntu: New Bug description: Tested on: Trusty, Xenial (used as recovery system) I'm unable to manage (modprobe, insmod) modules due following error: "modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'" I don't know why, but it seem like in the libkmod.c was a bug that attempt to load an old kernel after it got upgraded (replaced with) a newer one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1992701/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit
Hello, any idea when the fix will land in jammy? -- 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/1970634 Title: FTBFS: mariadb fails to start due to low MEMLOCK limit Status in mariadb-10.6 package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that included io_uring support because upstream were doing a build time test for io_uring (and I think still are), which is wrong because it should be done at runtime since the lack of io_uring availablity at build time doesn't tell us about its availablity at runtime. But then the Launchpad builders got updated to a newer release and therefore a newer kernel that supported it. AIUI, that's how we ended up with a successful build in the Jammy release pocket (of 10.6). I think the lp builders are using the focal hwe kernel 5.4.0-something let me check that build log But then something changed that caused this current FTBFS, and I haven't tracked down what that is. hm, both are 10.6.7 release and proposed What puzzles me is that if the root cause is a memlock rlimit issue then why did it work before? So since there's a contradiction somewhere, maybe one or more of my "facts" above is wrong. this is the current failure 2022-04-14 8:11:49 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked limit, ulimit -l, or https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd (262144 bytes required) and ulimit -l confirms that the limit is lower Max locked memory 6553665536 bytes just 64kbytes Yeah but then how did the release pocket build work? either the limit was different back then or ... stuff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
I've checked it - compression setting was also not taken into account on my installation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
I've got 16GB of RAM. It's a pretty new laptop - LG Gram 17Z90p Before my changes initrd had size 118MB, after changes: 27MB. file command output was: ASCII cpio archive (SVR4 with no CRC) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1861250] Re: Apparmor error failed to start profiles
I found the same issue in my dmesg output. Here is outupt of suggested command # apparmor_parser -r /etc/apparmor.d/ AppArmor parser error for /etc/apparmor.d/ in profile /etc/apparmor.d//usr.sbin.cups-browsed at line 23: syntax error, unexpected TOK_CLOSE, expecting TOK_ID or TOK_END_OF_RULE Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1861250 Title: Apparmor error failed to start profiles Status in apparmor package in Ubuntu: Confirmed Bug description: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/lightdm/lightdm-guest-session /usr/lib/lightdm/lightdm-guest-session//chromium /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/ippusbxd /usr/sbin/tcpdump /usr/share/hplip/plugin.py /usr/share/hplip/sendfax.py /usr/share/hplip/setup.py /usr/share/hplip/systray.py /usr/share/hplip/toolbox.py libreoffice-senddoc libreoffice-soffice//gpg libreoffice-xpdfimport lsb_release man_filter man_groff nvidia_modprobe nvidia_modprobe//kmod snap-update-ns.core snap-update-ns.gnome-calculator snap-update-ns.gnome-characters snap-update-ns.gnome-logs snap-update-ns.gnome-system-monitor snap.core.hook.configure snap.gnome-calculator.gnome-calculator snap.gnome-characters.gnome-characters snap.gnome-logs.gnome-logs snap.gnome-system-monitor.gnome-system-monitor system_tor 2 profiles are in complain mode. libreoffice-oopslash libreoffice-soffice 3 processes have profiles defined. 3 processes are in enforce mode. /usr/lib/telepathy/mission-control-5 (3090) /usr/sbin/cupsd (1646) /usr/bin/tor (1861) system_tor 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. lee@lee-desktop:~$ 2.sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ 3.sudo rm -rf /etc/apparmor.d/cache/* 4. sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ Thanks, Lee ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 23:19:19 2020 InstallationDate: Installed on 2013-08-08 (2365 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1861250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1951827] Re: APT crashes with Segmentation fault
This was only a informative bug report because Ubuntu and Debian share many common packages. This bug has appeared suddenly and without any warning or possibility to backtrack, so it would be good that Ubuntu dev team was aware of it. Have a nice day ;-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1951827 Title: APT crashes with Segmentation fault Status in apt package in Ubuntu: Incomplete Bug description: **System:** - OS Type: Linux - OS: Debian 10 - APT / APT-utils version: 2.24 **Bug description:** When trying to execute apt commands from the command line, apt crashes with the Segmentation fault error and nothing more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1951827/+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 1950181] [NEW] package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1
Public bug reported: no additional details ProblemType: Package DistroRelease: Ubuntu 21.10 Package: usbmuxd 1.1.1-2build1 ProcVersionSignature: Ubuntu 5.11.0-40.44-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 8 16:23:50 2021 ErrorMessage: installed usbmuxd package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: usbmuxd Title: package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to impish on 2021-11-08 (0 days ago) ** Affects: usbmuxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1950181 Title: package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1 Status in usbmuxd package in Ubuntu: New Bug description: no additional details ProblemType: Package DistroRelease: Ubuntu 21.10 Package: usbmuxd 1.1.1-2build1 ProcVersionSignature: Ubuntu 5.11.0-40.44-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 8 16:23:50 2021 ErrorMessage: installed usbmuxd package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: usbmuxd Title: package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to impish on 2021-11-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1950181/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
I have similar messages in journalctl: Package: linux-firmware Version: 1.197.3 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:1 pasid:32778, for process vivaldi-bin pid 1673 thread vivaldi-bi:cs0 pid 1699) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x80010114 from client 0x12 (VMC) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00105631 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:1 pasid:32778, for process vivaldi-bin pid 1673 thread vivaldi-bi:cs0 pid 1699) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800101188000 from client 0x12 (VMC) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00105631 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:1 pasid:32778, for process vivaldi-bin pid 1673 thread vivaldi-bi:cs0 pid 1699) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800101189000 from client 0x12 (VMC) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00105631 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that
[Touch-packages] [Bug 1941788] [NEW] amdgpu page fault in journalctl
Public bug reported: This is what I am having in the jouralctl logs: Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800100a44000 from client 0x12 (VMC) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013a from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013c8000 from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013a2000 from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013c9000 from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
[Touch-packages] [Bug 1922686] Re: Can't log in every time lightdm Xubuntu 20.04.2.1
** Changed in: lightdm (Ubuntu) Assignee: Amigo Ventero (ventero1) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1922686 Title: Can't log in every time lightdm Xubuntu 20.04.2.1 Status in lightdm package in Ubuntu: New Bug description: I select my username on the login screen, enter my password, the password field becomes inactive and nothing happens. If I try a second time by switching to "other user" and then back to myself, filling in the password again, it sometimes logs in and other times prints a message saying login failed. Then I have to restart via the console, which also takes an unreasonable amount of time. Also, there is a mysterious "Guest" account that I didn't create, which is not in the user list, and also requires a password, which I couldn't find anywhere on the internet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1922686/+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 1921920] Re: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session.
** Changed in: xubuntu-meta (Ubuntu) Assignee: Amigo Ventero (ventero1) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1921920 Title: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session. Status in lightdm package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: I cannot log out, shut down or restart from an activated temporary guest session. Only via tty or REISUB. Clicking anything in the logout/restart/shutdown GUI dialog window will only result in the message "An error occurred while logging out" GDBus.Error:org.freedesktop.Dbus.Error.InvalidArgs: Type ofmessage, "(yb)", does not match expected type "(b)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1921920/+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 1936847] Re: [amd] Xorg crashed on wakeup from suspend
** Description changed: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. + + On a different occasion, my Xorg log file also included (same as bug + 1780677): + + (WW) xf86CloseConsole: KDSETMODE failed: Input/output error + (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error + (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error + (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed - virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed + virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed + virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Renoir [17aa:5081] + Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Installed on 2021-07-08 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1000BCK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic root=UUID=72a1caf7-a182-459a-b685-43fc66697294 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET63W(1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000BCK 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.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR1BET63W(1.32):bd04/12/2021:br1.32:efr1.32:svnLENOVO:pn20Y1000BCK:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1000BCK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000BCK dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. + + This happens when I disconnect dock station after suspend (tested with + Dell WD19s and Lenovo ThinkPad USB-C Dock Gen2). On a different occasion, my Xorg log file also included (same as bug 1780677): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5081] InstallationDate:
[Touch-packages] [Bug 1936847] [NEW] [amd] Xorg crashed on wakeup from suspend
Public bug reported: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. On a different occasion, my Xorg log file also included (same as bug 1780677): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Installed on 2021-07-08 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1000BCK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic root=UUID=72a1caf7-a182-459a-b685-43fc66697294 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET63W(1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000BCK 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.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR1BET63W(1.32):bd04/12/2021:br1.32:efr1.32:svnLENOVO:pn20Y1000BCK:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1000BCK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000BCK dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1936847 Title: [amd] Xorg crashed on wakeup from suspend Status in xorg package in Ubuntu: New Bug description: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. On a different occasion, my Xorg log file also included (same as bug 1780677): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Installed on 2021-07-08 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1000BCK
[Touch-packages] [Bug 1780677] Re: X session crash after resuming from suspend
Still no fix ? I have just installed clean Ubuntu 20.04 an this exact thing is happening to me. It took me hours just to find this bug report... 沈 ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) -- 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/1780677 Title: X session crash after resuming from suspend Status in xorg-server package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7 First I suspended my laptop, while a few applications were running (Firefox, Chrome and some others much smaller). A couple of hours later, I opened the lid and expected the Gnome session would resume. What happened instead was a crash of the X server, then the login page was shown again and a new Gnome session started: the old session got killed! In the Xorg.0.log.old file I found this, not sure if related: [ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0 [ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [ 21189.338] (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una 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 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 8 23:03:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidia, 390.48, 4.15.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc] InstallationDate: Installed on 2018-06-21 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+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 1926783] [NEW] [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched and distorted
Public bug reported: It works normally when playing youtube videos, only audio files on PC are a problem. Also, kernel 5.8.0-50-generic does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 5.11.13 Uname: Linux 5.11.0-7614-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1518 F pulseaudio /dev/snd/controlC2: michal 1518 F pulseaudio /dev/snd/controlC1: michal 1518 F pulseaudio /dev/snd/pcmC1D0p: michal 1518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Apr 30 17:05:38 2021 InstallationDate: Installed on 2021-01-31 (89 days ago) InstallationMedia: SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1926783 Title: [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched and distorted Status in pulseaudio package in Ubuntu: New Bug description: It works normally when playing youtube videos, only audio files on PC are a problem. Also, kernel 5.8.0-50-generic does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 5.11.13 Uname: Linux 5.11.0-7614-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1518 F pulseaudio /dev/snd/controlC2: michal 1518 F pulseaudio /dev/snd/controlC1: michal 1518 F pulseaudio /dev/snd/pcmC1D0p: michal 1518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Apr 30 17:05:38 2021 InstallationDate: Installed on 2021-01-31 (89 days ago) InstallationMedia: SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B
[Touch-packages] [Bug 1912659] [NEW] [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] losing the sound
Public bug reported: alsa force-reload + reboot helps, but only temporarily (similar to Bug #1874689) Unplugging and plugging in the headphones again results in losing the sound. During the time I was reporting the bug, the sound was OK. I unplugged and plugged the headphones in -> no sound. Quite surprisingly, when I finished the bug reporting, the sound was back. Using Ubuntu 20.04 LTS. I have quite a new desktop, so some newer hardware may be responsible for the issues ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 17:20:23 2021 InstallationDate: Installed on 2020-07-02 (203 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: led 21 10:23:45 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") led 21 10:23:46 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20a dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20a:bd06/16/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1912659 Title: [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] losing the sound Status in alsa-driver package in Ubuntu: New Bug description: alsa force-reload + reboot helps, but only temporarily (similar to Bug #1874689) Unplugging and plugging in the headphones again results in losing the sound. During the time I was reporting the bug, the sound was OK. I unplugged and plugged the headphones in -> no sound. Quite surprisingly, when I finished the bug reporting, the sound was back. Using Ubuntu 20.04 LTS. I have quite a new desktop, so some newer hardware may be responsible for the issues ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 17:20:23 2021 InstallationDate: Installed on 2020-07-02 (203 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: led 21 10:23:45 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") led 21 10:23:46 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [X570 UD, Realtek ALC887-VD, Green Headphone
[Touch-packages] [Bug 1874689] Re: alsa force-reload needed to fix my sound after upgrade to 20.04
Also affected. Having Ubuntu 20.04 LTS (the default flavor). lspci -v (yes, I have 2 gpus) 04:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) Subsystem: NVIDIA Corporation TU116 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 135 Memory at fa08 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 09:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) Subsystem: NVIDIA Corporation TU116 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 136 Memory at fc08 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Subsystem: Gigabyte Technology Co., Ltd Starship/Matisse HD Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 138 Memory at fc40 (32-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 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/1874689 Title: alsa force-reload needed to fix my sound after upgrade to 20.04 Status in Ubuntu MATE: New Status in alsa-driver package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Mate 18.04 LTS to Ubuntu Mate 20.04 LTS "sudo alsa force-reload" is needed to fix my sound. I upgraded yesterday (23rd) before the official announcements of 20.04 LTS. Using "do-release-upgrade -d". I'm not sure yet how often I have to run "sudo alsa force-reload". When I have no sound a reboot is not a guranteed fix although it worked once. Booting into a Ubuntu Desktop 20.04 LTS gets working sounds each time I tried. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874689/+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 1904602] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1904602/+attachment/5435798/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties Status in software-properties package in Ubuntu: Incomplete Bug description: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair Package: software-properties-gtk 0.99.3 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+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 1904602] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1904602/+attachment/5435797/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties Status in software-properties package in Ubuntu: Incomplete Bug description: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair Package: software-properties-gtk 0.99.3 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+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 1904602] Re: Strange crash of Software Properties
Including a pastebin of the *.crash file: https://pastebin.com/dr8G0C6E ** Tags added: apport-collected groovy ** Description changed: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. - Ubuntu version: 20.04 and above (it does apply also to the same version - of lUbuntu) + Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.455 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair + Package: software-properties-gtk 0.99.3 + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 + Tags: groovy + Uname: Linux 5.8.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties Status in software-properties package in Ubuntu: Incomplete Bug description: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair Package: software-properties-gtk 0.99.3 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+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 1904602] [NEW] Strange crash of Software Properties
Public bug reported: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "unusual application behaviour" https://bugs.launchpad.net/bugs/1904602/+attachment/5435192/+files/Screenshot%20from%202020-11-17%2017-28-17.png ** Description changed: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. + + Ubuntu version: 20.04 and above (it does apply also to the same version + of lUbuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties Status in software-properties package in Ubuntu: New Bug description: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
# diff --git a/softwareproperties/qt/SoftwarePropertiesQt.py
b/softwareproperties/qt/SoftwarePropertiesQt.p
diff: unrecognized option '--git'
diff: Try 'diff --help' for more information.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1865906] Re: software-properties-* import key issue
@Chris Guiver (guiverc): After opening in the terminal (as root) the given by you command, I had received a authorization link to Launchpad. After opening it (I was already logged in into my account), I saw the Launchpad page with following message: The information on this page is private. Michal Dziczkowski (mdziczkowski) • Launchpad.net Not allowed here Sorry, you don't have permission to access this page or the information in this page is not shared with you. You are logged in as Michal Dziczkowski. == Please fix it asap, else I won't be able to send the required information's from apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1865906 Title: software-properties-* import key issue Status in lubuntu-meta package in Ubuntu: Incomplete Status in software-properties package in Ubuntu: Confirmed Bug description: My system: Lubuntu 19.04 run from Live-CD (from the original ISO image) Note: Followig issue apply to both software-properties: Qt and KDE run from LiveCD. After opening thru the console (as root) the software-properties, switching to the "Authentication" tab and pressing the "Import key file", I recieve following error output: # software-properties-qt QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Trackback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 712, in add_key_clicked url = KUrl.fromPath(home) NameError: name 'KUrl' is not defined = same happens with software-properties-kde. When I'm trying to check their version, I'll get following output: # software-properties-qt -v QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime- root' software-properties-qt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1865906/+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 1857902] Re: Thread-safety bugs in package libpoppler-glib8
There is better fix https://gitlab.freedesktop.org/poppler/poppler/merge_requests/494 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1857902 Title: Thread-safety bugs in package libpoppler-glib8 Status in poppler package in Ubuntu: Triaged Bug description: There are these bugs in libpoppler-glib8: https://gitlab.freedesktop.org/poppler/poppler/issues/845 https://gitlab.freedesktop.org/poppler/poppler/issues/846 The first is about sharing cairo_font_face_t instances in multiple threads which is not thread-safe. The second is about accessing global linked list struct without proper synchronisation mechanism. Due to these two bugs poppler+cairo cannot be used for rendering multiple documents in multiple threads. The second may be potentially security vulnerability for applications that use poppler+cairo in multiple threads due to writes to potentially uninitialised pointer. I noticed that poppler source package contains a lot of patches from ubuntu updates. Would be possible to add patch to this problem to ubuntu (and also debian) updates? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1857902/+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 1834318] Re: Warning from Google about Ubuntu
So to report this as a bug, I need to wait until Ubuntu stops working with Google account? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1834318 Title: Warning from Google about Ubuntu Status in gnome-online-accounts package in Ubuntu: Invalid Bug description: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1834318/+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 1834318] [NEW] Warning from Google about Ubuntu
Public bug reported: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: Invalid ** Attachment added: "google-ubuntu.png" https://bugs.launchpad.net/bugs/1834318/+attachment/5273452/+files/google-ubuntu.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1834318 Title: Warning from Google about Ubuntu Status in gnome-online-accounts package in Ubuntu: Invalid Bug description: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1834318/+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 1607696] Re: Version string missing in libjpeg.pc
Package which contains this libjpeg.pc is libjpeg-turbo8-dev:
prefix=/usr
exec_prefix=${prefix}
libdir=${prefix}/lib/x86_64-linux-gnu
includedir=${prefix}/include
Name: libjpeg
Description: JPEG image codec
Version:
Libs: -L${libdir} -ljpeg
Cflags: -I${includedir}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1607696
Title:
Version string missing in libjpeg.pc
Status in libjpeg-turbo package in Ubuntu:
Confirmed
Bug description:
Proper pkg-config files are installed if I build libjpeg-turbo myself.
The description in the pkg-config file shipped by Ubuntu is also
different from what is in upstream so I assume this is caused by
Ubuntu (/Debian?) patching in a custom pkg-config file before they
were included upstream in https://github.com/libjpeg-turbo/libjpeg-
turbo/pull/53 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1607696/+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 1766503] Re: ibus-* randomly use high CPU
OK. I got it. In my case processes starts in similar way /tmp/XXX-XXX... that's was suspicious after search info about similar cases I found this: https://ubuntuforums.org/showthread.php?t=2389313 https://www.reddit.com/r/Addons4Kodi/comments/8eto78/people_using_unofficial_kodi_addon_on_linux/ Please check if ~/.config/autostart/dbus-daemon.desktop exists. After cleaning ~/.config/autostart/ folder situation is better also i found suspicious inictl file in ~/.cache/fontconfig I will check files with ClamAV but this will take some time. For now CPU usage looks good for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
*** This bug is a duplicate of bug 1768610 *** https://bugs.launchpad.net/bugs/1768610 Yes, happened to me also. Kubuntu 18.04.1 Yesterday (Nov 27) suddenly (after auto upgrade of the system) nvidia stopped working (switched to nouveau, probably). Upgraded to Kubuntu 18.10 This actually made the situation even worse - stuck on 640x480 resolution. Had nvidia-390 installed at the moment, but the system wasn't using it. After some looking around, installed: sudo apt install nvidia-dkms-410 xserver-xorg-video-nvidia-410 nvidia- kernel-source-410 which made the situation look better: resolution was again native (1920x1200) and nvidia-settings launched and showed 410 driver running. But in the Steam games, it showed that llvm driver was being used. And games such as Wolfenstein New Order (uses proton wine) didn't even launch. After some more fiddling around, actually using the Kubuntu GUI tool (System Settings > Driver Manager > Nvidia > 410) fixed the situation. Apparently the GUI tool does it somehow better than installing the nvidia package manually. -- 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/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about
[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU
Same here. If i open system monitor or htop app sysctrl or ibus disappear and cpu goes back to normal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 Also had this problem after upgrade 18.04.1 -> 18.10. I do *NOT* have timidity installed. alsa force-reload works as temporary fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1787824] Re: "rfkill: input handler disabled" boot time 11 seconds.
same here, this occured after updating from 17 to 18: :~$ systemd-analyze Startup finished in 9.891s (firmware) + 2.196s (loader) + 33.839s (kernel) + 22.189s (userspace) = 1min 8.115s graphical.target reached after 22.184s in userspace :~$ systemd-analyze blame 20.698s plymouth-quit-wait.service 1.304s tor@default.service 781ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device 694ms fwupd.service 485ms snapd.service 294ms dev-loop0.device 274ms systemd-logind.service 272ms dev-loop10.device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1787824 Title: "rfkill: input handler disabled" boot time 11 seconds. Status in util-linux package in Ubuntu: Incomplete Bug description: My computer is slowly opening, I looked at the output of dmesg and at 11th I get this post. What i need to do? thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rfkill 2.31.1-0.4ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 19:44:21 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libsmartcols1 2.31.1-0.4ubuntu3.1 InstallationDate: Installed on 2018-08-18 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1787824/+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 1792734] [NEW] package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64
Public bug reported: Couldn't install package: libjpeg8_8d1-2_amd64.deb. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libjpeg8 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libjpeg8:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 15 16:29:10 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libjpeg-turbo8 1.5.2-0ubuntu5.18.04.1 multiarch-support 2.27-3ubuntu1 DpkgTerminalLog: Preparing to unpack .../libjpeg8_8d1-2_amd64.deb ... Unpacking libjpeg8:amd64 (8d1-2) over (8c-2ubuntu8) ... dpkg: error processing archive /home/meme/Dropbox/kydpdict/deb 64/libjpeg8_8d1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 DuplicateSignature: package:libjpeg8:8c-2ubuntu8 Unpacking libjpeg8:amd64 (8d1-2) over (8c-2ubuntu8) ... dpkg: error processing archive /home/meme/Dropbox/kydpdict/deb 64/libjpeg8_8d1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 InstallationDate: Installed on 2018-09-13 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libjpeg8-empty Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg8-empty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1792734 Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 Status in libjpeg8-empty package in Ubuntu: New Bug description: Couldn't install package: libjpeg8_8d1-2_amd64.deb. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libjpeg8 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libjpeg8:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 15 16:29:10 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libjpeg-turbo8 1.5.2-0ubuntu5.18.04.1 multiarch-support 2.27-3ubuntu1 DpkgTerminalLog: Preparing to unpack .../libjpeg8_8d1-2_amd64.deb ... Unpacking libjpeg8:amd64 (8d1-2) over (8c-2ubuntu8) ... dpkg: error processing archive /home/meme/Dropbox/kydpdict/deb 64/libjpeg8_8d1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 DuplicateSignature: package:libjpeg8:8c-2ubuntu8 Unpacking libjpeg8:amd64 (8d1-2) over (8c-2ubuntu8) ... dpkg: error processing archive /home/meme/Dropbox/kydpdict/deb 64/libjpeg8_8d1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 InstallationDate: Installed on 2018-09-13 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libjpeg8-empty Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1792734/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1792008] [NEW] Sound on HP Spectre 13 x360-ae0xxnc crackling and buzz on speaker if use earphones.
Public bug reported: Ubuntu 18.04.1, kernel 4.18.5-041805-generic, audio codec ALC295. Speaker work only under keyboard, but fine. But if I connect earphones, speakers buzz. After removing earphones, sound from left speaker is distorted (metal soud). Logout doesn't correct this issues, only restart. Sound in earphones is clear and good in any cases. I tested various kernels, but no solve this bug. In Windows 10 sound work fine without any side effect on quality of the sound. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info" https://bugs.launchpad.net/bugs/1792008/+attachment/5187692/+files/alsa-info -- 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/1792008 Title: Sound on HP Spectre 13 x360-ae0xxnc crackling and buzz on speaker if use earphones. Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu 18.04.1, kernel 4.18.5-041805-generic, audio codec ALC295. Speaker work only under keyboard, but fine. But if I connect earphones, speakers buzz. After removing earphones, sound from left speaker is distorted (metal soud). Logout doesn't correct this issues, only restart. Sound in earphones is clear and good in any cases. I tested various kernels, but no solve this bug. In Windows 10 sound work fine without any side effect on quality of the sound. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1792008/+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 1788400] [NEW] package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být přeinstalován.
Public bug reported: Problem for update. I not install for update and not search update. Error for Secure (8). ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libdca0:amd64 0.0.5-10 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 19 21:09:24 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 ErrorMessage: balík je ve velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být přeinstalován. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libdca Title: package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být přeinstalován. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libdca (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdca in Ubuntu. https://bugs.launchpad.net/bugs/1788400 Title: package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být přeinstalován. Status in libdca package in Ubuntu: New Bug description: Problem for update. I not install for update and not search update. Error for Secure (8). ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libdca0:amd64 0.0.5-10 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 19 21:09:24 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 ErrorMessage: balík je ve velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být přeinstalován. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libdca Title: package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být přeinstalován. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdca/+bug/1788400/+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 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy
I am not sure this was fixed, or maybe I just hardly misunderstand that.
Under current Bionic (software-properties-common 0.96.24.32.3) I still
can't retrieve keys via env-var defined `http_proxy`.
# echo $http_proxy
http://1.2.3.4:3128
# echo $https_proxy
http://1.2.3.4:3128
# apt-key adv --recv-keys AB1C1EF6EDB5746803FE13E00F6DD8135234BF2B
Executing: /tmp/apt-key-gpghome.tj9ezR01dk/gpg.1.sh --recv-keys
AB1C1EF6EDB5746803FE13E00F6DD8135234BF2B
gpg: keyserver receive failed: Connection timed out
What it does (when stracing it) is
```
...
stat("/tmp/apt-key-gpghome.xI4xFLcUnH/S.dirmngr", {st_mode=S_IFSOCK|0700,
st_size=0, ...}) = 0
connect(3, {sa_family=AF_UNIX,
sun_path="/tmp/apt-key-gpghome.xI4xFLcUnH/S.dirmngr"}, 43) = 0
read(3, "# ", 1002) = 2
read(3, "Home: /tmp/apt-key-gpghome.xI4xF"..., 1000) = 37
read(3, "\n", 963) = 1
read(3, "# ", 1002) = 2
read(3, "Config: [none]", 1000) = 14
read(3, "\n", 986) = 1
read(3, "OK ", 1002)= 3
read(3, "Dirmngr 2.2.4 at your service", 999) = 29
read(3, "\n", 970) = 1
write(3, "GETINFO version", 15) = 15
write(3, "\n", 1) = 1
read(3, "D 2.2.4\n", 1002) = 8
read(3, "OK", 1002) = 2
read(3, "\n", 1000) = 1
write(3, "KEYSERVER --clear http://keyserv;..., 49) = 49
write(3, "\n", 1) = 1
read(3, "OK", 1002) = 2
read(3, "\n", 1000) = 1
write(3, "KS_GET -- 0xAB1C1EF6EDB5746803FE"..., 52) = 52
write(3, "\n", 1) = 1
read(3, "ERR 167805060 Connection timed o"..., 1002) = 44
```
dirmngr manpage makes me think that `http_proxy` env var is ignored by
default and I need to explicitly add `honor-http-proxy` option to
dirmngr, but the problem is that apt-key creates the homedir with a
random name so I can't use any system-wide setting.
I know I can work this around with `--keyserver-options http-
proxy=http://1.2.3.4:3128/` but this is not what I should do, the system
should take care itself.
This is really a pain-in-the-ass issue for in-corporate-network
automation developers; we just need to use standard tools for adding apt
repositories, not working this around.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1433761
Title:
apt-key and add-apt-repository don't honor Acquire::http::Proxy
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
When setting the proxy server globally on the system for the APT
package manager, add-apt-repository ignores the setting. This issue is
present on all versions of Debian that I have tested.
# cat /etc/apt/apt.conf.d/80proxy
Acquire::http::proxy "http://w.x.y.z:/;;
# apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
--homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring
/etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com
--recv-keys 5A9A06AEF9CB8DB0
gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error
This has serious repercussions. Unattended installs such as juju,
maas, etc are all affected for anyone who is working behind a proxy.
This is the case for most enterprise environments where such maas and
juju setups will be tested out, and as such has great repercussions
for Canonical as a viable supplier of OpenStack environments: if your
product fails to install, you're not going to get the business.
Considering that:
* The setting to use already exists in /etc/apt/apt.conf and that all other
tools use this correctly
* The serious impact of this issue for downstream projects and Debian usage
in the enterprise
* The long time this issue has been standing and has affected people
I suggest that this either
1) be fixed, or
2) the apt-key and add-apt-repository programs are renamed so that it is made
clear they are not part of the APT suite of programs and therefor cannot be
trusted to behave as if they were part of APT.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1433761/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1771111] [NEW] Freezes on Thinkpad R500
Public bug reported: Problem with black boxes on screen, freezing mouse, random freezes (1-2s). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 BootLog: /dev/sda1: clean, 586416/5447680 files, 15738435/21777920 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 14 14:36:13 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e5] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e5] InstallationDate: Installed on 2017-11-12 (182 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 271434G PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=0b74ca14-9767-4eca-95ac-fcbedc338d77 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7YET50WW (1.20 ) dmi.board.name: 271434G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7YET50WW(1.20):bd10/30/2008:svnLENOVO:pn271434G:pvrThinkPadR500:rvnLENOVO:rn271434G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad R500 dmi.product.name: 271434G dmi.product.version: ThinkPad R500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages ubuntu wayland-session -- 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/177 Title: Freezes on Thinkpad R500 Status in xorg package in Ubuntu: New Bug description: Problem with black boxes on screen, freezing mouse, random freezes (1-2s). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 BootLog: /dev/sda1: clean, 586416/5447680 files, 15738435/21777920 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 14 14:36:13 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e5] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e5] InstallationDate: Installed on 2017-11-12 (182 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 271434G PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=0b74ca14-9767-4eca-95ac-fcbedc338d77 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7YET50WW (1.20 ) dmi.board.name: 271434G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Touch-packages] [Bug 1731068] [NEW] With NVIDIA proprietary drivers, initial login screan appears only on mouse movement
Public bug reported: After installing the proprietary NVIDIA driver (384) I've been faced with a black screen after reboot. It turned out, that when I moved the mouse, the login screen appeared. The screen goes black immediately when I stop moving the mouse. I can normally put the password in on the black screen and go on with my life, but, you know, it doesn't look stable :) After I get the system up from sleeping (which didn't work earlier but suddenly started working) the log in screen in displayed normally. My system (Alienware 15 R3) has Intel's i7-7820HK and NVIDIA's GeForce GTX 1070 Mobile 8GB ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-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 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .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. ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 BootLog: /dev/sda2: clean, 200420/61046784 files, 6117516/244157440 blocks CompositorRunning: None CurrentDesktop: KDE Date: Wed Nov 8 23:43:20 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Subsystem: Dell Device [1028:0774] NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:07c0] InstallationDate: Installed on 2017-11-04 (4 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:58c2 Realtek Semiconductor Corp. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 187c:0530 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware 15 R3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=32edfbb9-d0bb-495a-9313-48b5ee124d2b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2017 dmi.bios.vendor: Alienware dmi.bios.version: 1.1.8 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.1.8:bd06/09/2017:svnAlienware:pnAlienware15R3:pvr1.1.8:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.version: 1.1.8 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful kubuntu -- 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/1731068 Title: With NVIDIA proprietary drivers, initial login screan appears only on mouse movement Status in xorg package in Ubuntu: New Bug description: After installing the proprietary NVIDIA driver (384) I've been faced with a black screen after reboot. It turned out, that when I moved the mouse, the login screen appeared. The screen goes black immediately when I stop moving the mouse. I can normally put the password in on the black screen and go on with my life, but, you know, it doesn't look stable :) After I get the system up from sleeping (which didn't work earlier but suddenly started working) the log in screen in displayed normally. My system
[Touch-packages] [Bug 1720751] [NEW] Error message hidden behind modal dialog
Public bug reported: Ubuntu 17.10 Beta running live from USB When Settings app crashed there was a modal dialog visible. Unfortunately the error message about the crash showed up behind that dialog. Screenshot attached. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2017-10-02 08-31-08.png" https://bugs.launchpad.net/bugs/1720751/+attachment/4960354/+files/Screenshot%20from%202017-10-02%2008-31-08.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720751 Title: Error message hidden behind modal dialog Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 17.10 Beta running live from USB When Settings app crashed there was a modal dialog visible. Unfortunately the error message about the crash showed up behind that dialog. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720751/+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 1720698] [NEW] Different height for window top bar in one app
Public bug reported: Ubuntu 17.10 Beta running live from USB I admit I have no idea how that "top bar" decoration of windows is called. Is it "tittle bar" or "tool bar"? Anyway I'm talking about that dark part with minimize and close buttons on it. I noticed the height of that bar is different if there's no additional buttons and different if there is an extra button or two. For example in the Settings app go to Details and switch between Users and Default Application tabs. When you're in Users tab you will see Add User button in the top bar. There's no button in the top bar of Default Application. When you switch between those two tabs you will notice that the top bar for Users tab has bigger height. And that gives visually unpleasant effect of interface jumping up and down when switching tabs. Short video attached. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screencast from 10-01-2017 10:22:21 PM.webm" https://bugs.launchpad.net/bugs/1720698/+attachment/4960144/+files/Screencast%20from%2010-01-2017%2010%3A22%3A21%20PM.webm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720698 Title: Different height for window top bar in one app Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 17.10 Beta running live from USB I admit I have no idea how that "top bar" decoration of windows is called. Is it "tittle bar" or "tool bar"? Anyway I'm talking about that dark part with minimize and close buttons on it. I noticed the height of that bar is different if there's no additional buttons and different if there is an extra button or two. For example in the Settings app go to Details and switch between Users and Default Application tabs. When you're in Users tab you will see Add User button in the top bar. There's no button in the top bar of Default Application. When you switch between those two tabs you will notice that the top bar for Users tab has bigger height. And that gives visually unpleasant effect of interface jumping up and down when switching tabs. Short video attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720698/+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 1720697] [NEW] Some elements in calendar popup don't stay in the same place
Public bug reported: Ubuntu 17.10 Beta running live from USB Steps to reproduce: 1. Click the time indicator in the top centre of the screen 2. Move between months in the calendar popup Expected result: View changes without visual glitches What happens instead: Sometimes both the "No event" icon and the vertical divider move right and left on the screen Short video attached. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screencast from 10-01-2017 10:12:22 PM.webm" https://bugs.launchpad.net/bugs/1720697/+attachment/4960143/+files/Screencast%20from%2010-01-2017%2010%3A12%3A22%20PM.webm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720697 Title: Some elements in calendar popup don't stay in the same place Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 17.10 Beta running live from USB Steps to reproduce: 1. Click the time indicator in the top centre of the screen 2. Move between months in the calendar popup Expected result: View changes without visual glitches What happens instead: Sometimes both the "No event" icon and the vertical divider move right and left on the screen Short video attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720697/+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 1720696] [NEW] Sound volume notification jumps left and right when changing volume
Public bug reported: Ubuntu 17.10 Beta running live from USB Steps to reproduce: 1. Place the mouse cursor over the volume icon in the top right corner of the screen 2. Turn the mouse wheel You will notice quite big notification bubble at the bottom centre of the screen. When you're turning the mouse wheel the notification is showing the volume level. Expected result: The notification stays in one place all the time I change the volume level What happens instead: For some volume values the notification jumps left and right on the screen Short video attached. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screencast from 10-01-2017 10:00:30 PM.webm" https://bugs.launchpad.net/bugs/1720696/+attachment/4960142/+files/Screencast%20from%2010-01-2017%2010%3A00%3A30%20PM.webm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720696 Title: Sound volume notification jumps left and right when changing volume Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 17.10 Beta running live from USB Steps to reproduce: 1. Place the mouse cursor over the volume icon in the top right corner of the screen 2. Turn the mouse wheel You will notice quite big notification bubble at the bottom centre of the screen. When you're turning the mouse wheel the notification is showing the volume level. Expected result: The notification stays in one place all the time I change the volume level What happens instead: For some volume values the notification jumps left and right on the screen Short video attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720696/+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 1720695] [NEW] Two different icons for sound volume
Public bug reported: Ubuntu 17.10 Beta running live from USB The "sound volume" icon in the top right corner of the screen is different from the icon in the popup dialog. Screenshot attached. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2017-10-01 21-52-41.png" https://bugs.launchpad.net/bugs/1720695/+attachment/4960138/+files/Screenshot%20from%202017-10-01%2021-52-41.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720695 Title: Two different icons for sound volume Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 17.10 Beta running live from USB The "sound volume" icon in the top right corner of the screen is different from the icon in the popup dialog. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720695/+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 158392] Re: Ubuntu need a dark theme and background
the MATE themes include a plain dark theme. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/158392 Title: Ubuntu need a dark theme and background Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-themes There is no Ubuntu theme with dark background in the theme package that is installed by default. There are the special high contrast themes that do not look well on hardware that provides sufficient contrast, and there is the Darklooks modification of Clearlooks that is in the extra themes. Darklooks is usable and does have dark background but it looks somewhat bland since it has no colors. Themes with dark background are useful because some screen defects manifest more noticeably when dark text is rendered on light background making the text harder to read. Also I find too light backgrounds tiring for my eyes. Another reason to use dark background might be that it probably saves energy on most CRT screens ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/158392/+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 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml
Can we have this in OTA15? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1618007 Title: Invalid property assignment in ActivityIndicatorStyle.qml Status in Canonical System Image: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: I get file:///usr/lib/x86_64-linux- gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24 Invalid property assignment: "implicitHeight" is a read-only property To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618007/+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 1580290] Re: First tab is always reloaded when the session is restored
Hi, I've just tested this version on my Ubuntu desktop running 16.04LTS. The bug seems to be fixed :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1580290 Title: First tab is always reloaded when the session is restored Status in Canonical System Image: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app source package in Xenial: Fix Committed Bug description: bq M10 rc-proposed OS build 100 If I have few tabs open and in the first tab is a youtube video, it will start playing even if that tap is in the background after restarting the Browser. Steps to reproduce: 1. Start Browser 2. Open a tab with a youtube video in it, for example http://summit.ubuntu.com/uos-1605/meeting/22651/convergent-ubuntu-apps 3. Open few more tabs with other websites 4. If necessary move the tab with the video so it's the first from the left 5. Select any other tab 6. Close Browser 7. Start Browser again Expected result: I don't hear the sound from the video in the background tab. What happens instead: I hear the sound from the video in the background tab. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580290/+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 1648435] Re: 5 useless buttons on the lock-screen
** Attachment added: "idea for numeric OSK on tablet" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+attachment/4790709/+files/OSK-M10.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648435 Title: 5 useless buttons on the lock-screen Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: bq e4.5 OTA-14 In the case I use '4-digit passcode' for 'Lock security', the new keyboard visible on the lock screen has 5 buttons out of 18 (counting 'Cancel' and 'Emergency') which do not have any use. I marked them on the attached screenshot. The same keyboard appears when I create or change the 4-digit passcode in System Settings. IMO it'd be better to remove those useless buttons, and possibly rearrange the useful ones. That could make it look better and provide better/bigger touch target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+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 1648435] Re: 5 useless buttons on the lock-screen
@bogdanke8, @zyga, thanks for your kind words :) >From what I've looked in the source code, to achieve this effect there need to >be changes in: 1. Greeter Prompt http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/qml/Greeter/GreeterPrompt.qml 2. Keyboard for numbers: http://bazaar.launchpad.net/~phablet-team/ubuntu-keyboard/trunk/view/head:/qml/languages/Keyboard_numbers.qml Of course I could be wrong :) Let's wait for UX team decision first though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648435 Title: 5 useless buttons on the lock-screen Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: bq e4.5 OTA-14 In the case I use '4-digit passcode' for 'Lock security', the new keyboard visible on the lock screen has 5 buttons out of 18 (counting 'Cancel' and 'Emergency') which do not have any use. I marked them on the attached screenshot. The same keyboard appears when I create or change the 4-digit passcode in System Settings. IMO it'd be better to remove those useless buttons, and possibly rearrange the useful ones. That could make it look better and provide better/bigger touch target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+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 1648435] Re: 5 useless buttons on the lock-screen
Possible design with added transparency for 'cool' factor ;) ** Attachment added: "OSK.svg.png" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+attachment/4789311/+files/OSK.svg.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648435 Title: 5 useless buttons on the lock-screen Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: New Bug description: bq e4.5 OTA-14 In the case I use '4-digit passcode' for 'Lock security', the new keyboard visible on the lock screen has 5 buttons out of 18 (counting 'Cancel' and 'Emergency') which do not have any use. I marked them on the attached screenshot. The same keyboard appears when I create or change the 4-digit passcode in System Settings. IMO it'd be better to remove those useless buttons, and possibly rearrange the useful ones. That could make it look better and provide better/bigger touch target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+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 1648593] Re: Keyboard usualy not showing up in apps after unlocking the screen
bq M10 rc-proposed I had this situation with Telegram today. Can't reproduce it now though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648593 Title: Keyboard usualy not showing up in apps after unlocking the screen Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Hello, for the last month or even more I am experiencing this weird bug with OSK not popping up after putting my phone to "sleep", that is locking the screen and then unlocking it. It mostly happens with Telegram to me, as that is one particular app that I keep running all the time, but I've experienced this in other apps (including my own) as well and therefore expect it not to be related to Telegram at all. Steps to reproduce: 1. Open any app (like Telegram) - OSK should pop up and work upon clicking on any input 2. Lock the device (shut the screen down) -- The length of the phone being asleep seems to have little influence on the actual OSK keyboard behaviour - it seems to be pretty much random -- 3. Unlock the device 4. Switch to the previously opened app if you are not there already Sometimes it is hard for me to reproduce this while other times I seem to be bumping into this every time I unlock the screen - so it is not something I've seen once or twice in my life but is pretty much common. To fix this behaviour switching out of the app and back to it again usually works, though sometimes restarting the app is the only way to get the OSK working. I am on rc-proposed, MX4 Thank you very much for looking into this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1648593/+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 1646758] Re: Can't update an app
My output: phablet@ubuntu-phablet:~$ click list | grep youtube youtube-web.mateo-salta 0.8 com.ubuntu.scopes.youtube 1.5.1-152 phablet@ubuntu-phablet:~$ ls -la ~/.local/share/ubuntu-download-manager/Downloads/ total 8 drwxrwxr-x 2 phablet phablet 4096 Nov 28 17:16 . drwxrwxr-x 6 phablet phablet 4096 Nov 29 09:55 .. phablet@ubuntu-phablet:~$ So the youtube app is not updated as the newest version is 0.9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1646758 Title: Can't update an app Status in ubuntu-download-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed r243 When trying to update an app this morning, I got an error about destination path not being writable. The app is YouTube by Mateo Salta. Screenshot with the error attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1646758/+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 1645915] Re: Launcher always shown, also in lock screen and tablet mode
bq M10 rc-proposed r243 For me the launcher is always shown only in 'desktop' mode. -- 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/1645915 Title: Launcher always shown, also in lock screen and tablet mode Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Incomplete Bug description: Using frieza. Test case. - Pair a Bluetooth mouse and keyboard. - Make sure the tablet runs in desktop mode. - Open System Settings > Launcher (may need the silo that enables this). - Enable "Always show". - Lock the screen. Expected result. - Launcher is not shown in the lock screen. Also, in tablet mode, the launcher is also always shown. current build number: 91 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645915/+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 1641720] Re: Selecting a day does not display all day event for that day
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641720 Title: Selecting a day does not display all day event for that day Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Fix Released Bug description: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641720/+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 1641722] Re: Tapping a day often results in selecting not the day I wanted to
thanks, reported bug #1644366 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1641722 Title: Tapping a day often results in selecting not the day I wanted to Status in ubuntu-settings-components package in Ubuntu: Fix Released Bug description: bq M10 rc-proposed silo #2195 Many times when testing after tapping a day I ended up selecting a day which was below or above the day I was aiming for. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1641722/+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 1641720] Re: Selecting a day does not display all day event for that day
I updated to today's rc-proposed on M10 (r236) and this bug is still present. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641720 Title: Selecting a day does not display all day event for that day Status in indicator-datetime package in Ubuntu: Fix Released Bug description: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641720/+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 1641722] Re: Tapping a day often results in selecting not the day I wanted to
Thanks for the hard work guys! Glad to see lots of the bugs got fixed in today's rc-proposed. Unfortunately this bug still is happening for me. The space between rows is too small and I still hit a day which is above or below the day I want to tap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1641722 Title: Tapping a day often results in selecting not the day I wanted to Status in ubuntu-settings-components package in Ubuntu: Fix Released Bug description: bq M10 rc-proposed silo #2195 Many times when testing after tapping a day I ended up selecting a day which was below or above the day I was aiming for. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1641722/+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 1641726] Re: Tapping a day displays all day event from previous day
I tested with a normal event and it's fine. Only the all-day events show up from the day before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641726 Title: Tapping a day displays all day event from previous day Status in indicator-datetime package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed silo #2195 When I tap on a day there are some events displayed, also from the day before. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641726/+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 1641726] Re: Tapping a day displays all day event from previous day
I believe I already have it set to that. Please see the screenshot attached. BTW many thanks for taking care of these bugs so quickly! ** Attachment added: "screenshot20161115_185918972.png" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641726/+attachment/479/+files/screenshot20161115_185918972.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641726 Title: Tapping a day displays all day event from previous day Status in indicator-datetime package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed silo #2195 When I tap on a day there are some events displayed, also from the day before. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641726/+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 1641728] [NEW] Tapping a day to unselect it shows more events than was there before
Public bug reported: bq M10 rc-proposed silo #2195 I tap a day to see events related to day day, the day is selected (color changed to blue). Then I tap that day again to 'unselect' it. The list of events is longer than was before tapping that day in the first place. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641728 Title: Tapping a day to unselect it shows more events than was there before Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 I tap a day to see events related to day day, the day is selected (color changed to blue). Then I tap that day again to 'unselect' it. The list of events is longer than was before tapping that day in the first place. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641728/+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 1641726] [NEW] Tapping a day displays all day event from previous day
Public bug reported: bq M10 rc-proposed silo #2195 When I tap on a day there are some events displayed, also from the day before. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641726 Title: Tapping a day displays all day event from previous day Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 When I tap on a day there are some events displayed, also from the day before. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641726/+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 1641731] [NEW] Selecting a day displays more results than expected
Public bug reported: bq M10 rc-proposed silo #2195 When I tap a day I expect to see events for that day only but I can see results from the future too. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641731 Title: Selecting a day displays more results than expected Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 When I tap a day I expect to see events for that day only but I can see results from the future too. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641731/+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 1641720] [NEW] Selecting a day does not display all day event for that day
Public bug reported: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641720 Title: Selecting a day does not display all day event for that day Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641720/+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 1641721] [NEW] Tapping on a day near to the screen edge switches to the next month
Public bug reported: bq M10 rc-proposed silo #2195 Many times when testing after clicking a day on the right hand side (Sundays in my case), the view switched to the next month. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641721 Title: Tapping on a day near to the screen edge switches to the next month Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 Many times when testing after clicking a day on the right hand side (Sundays in my case), the view switched to the next month. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641721/+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 1641722] [NEW] Tapping a day often results in selecting not the day I wanted to
Public bug reported: bq M10 rc-proposed silo #2195 Many times when testing after tapping a day I ended up selecting a day which was below or above the day I was aiming for. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641722 Title: Tapping a day often results in selecting not the day I wanted to Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 Many times when testing after tapping a day I ended up selecting a day which was below or above the day I was aiming for. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641722/+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 1641724] [NEW] Tapping the month name has no effect
Public bug reported: bq M10 rc-proposed silo #2195 I would expect that tapping the month name would display events for that month. Unfortunately the month name is not clickable. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641724 Title: Tapping the month name has no effect Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 I would expect that tapping the month name would display events for that month. Unfortunately the month name is not clickable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641724/+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 1641719] [NEW] Opacity for weekend days same as for other days
Public bug reported: bq M10 rc-proposed silo #2195 When I pull down the calendar indicator, I see the opacity (or maybe color) for weekend days is different than for other work days. But when I switch to next month, the opacity is the same for all days. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1641719 Title: Opacity for weekend days same as for other days Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 When I pull down the calendar indicator, I see the opacity (or maybe color) for weekend days is different than for other work days. But when I switch to next month, the opacity is the same for all days. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641719/+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 1637157] Re: App geometry cache gets corrupted
** Attachment added: "windowstatestorage.sqlite" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637157/+attachment/4776083/+files/windowstatestorage.sqlite -- 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/1637157 Title: App geometry cache gets corrupted Status in unity8 package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637157/+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 1637157] Re: App geometry cache gets corrupted
I have just reflashed my tablet :/ As soon as I get the issue, I will attach the file. -- 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/1637157 Title: App geometry cache gets corrupted Status in unity8 package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637157/+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 1637157] Re: Default app window size in desktop mode is too small
Marking the bug again as "New". Still I get this issue after a while. Can't find a good way to reproduce though. ** Changed in: unity8 (Ubuntu) Status: Invalid => New -- 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/1637157 Title: Default app window size in desktop mode is too small Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637157/+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 1637258] Re: Side stage hides after rotating
I agree, it is a bit subjective. I spoke with @mzanetti yesterday and we both have the same opinion as you. Reported bug #1641072 -- 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/1637258 Title: Side stage hides after rotating Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: bq M10 rc-proposed r219 Steps to reproduce: 1. Open an app 2. Put it in the side stage 3. Rotate the tablet to portrait At this point you should see the app which was in the side stage on the whole screen 4. Rotate the tablet back to landscape Expected result: The app is visible in the side stage What happens instead: The side stage is closed but the app still has focus as its name is visible in the top bar (screenshot attached) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1637258/+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 1641072] [NEW] Side stage not restored after rotation
Public bug reported: bq M10 silo #2177 Steps to reproduce: 1. In landscape add an app to the side stage 2. Make sure the side stage is not focused 3. Rotate to portrait and back to landscape Expected result: Both the side stage and main app are visible, like before rotation What happens instead: Only the main app is visible, the side stage is hidden I understand this behaviour could be intentional but imo it'd be better if the side stage was restored even if the app there was not focused. My reasons: rotation could be made by accident (for example when carrying the device), even if I intentionally made the rotation, I don't expect to lose my windows arrangement. ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1641072 Title: Side stage not restored after rotation Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: bq M10 silo #2177 Steps to reproduce: 1. In landscape add an app to the side stage 2. Make sure the side stage is not focused 3. Rotate to portrait and back to landscape Expected result: Both the side stage and main app are visible, like before rotation What happens instead: Only the main app is visible, the side stage is hidden I understand this behaviour could be intentional but imo it'd be better if the side stage was restored even if the app there was not focused. My reasons: rotation could be made by accident (for example when carrying the device), even if I intentionally made the rotation, I don't expect to lose my windows arrangement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1641072/+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 1637258] Re: Side stage hides after rotating
Thanks for the quick fix! I've installed silo #2177 with this and other bug fixes. I have one question regarding this issue though. When using silo #2177, I noticed the app is visible in the side stage after rotation only if that app is focused. But if an app is in the side stage and the main app is focused, after rotating to portrait and back to landscape, the side stage is hidden. I'm not sure if that's by design or not? -- 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/1637258 Title: Side stage hides after rotating Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: bq M10 rc-proposed r219 Steps to reproduce: 1. Open an app 2. Put it in the side stage 3. Rotate the tablet to portrait At this point you should see the app which was in the side stage on the whole screen 4. Rotate the tablet back to landscape Expected result: The app is visible in the side stage What happens instead: The side stage is closed but the app still has focus as its name is visible in the top bar (screenshot attached) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1637258/+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 1580290] Re: First tab is always reloaded when the session is restored
Hi. I'm not sure how can I do the testing as that bug was affecting me on Ubuntu tablet. I don't use this app on Ubuntu desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1580290 Title: First tab is always reloaded when the session is restored Status in Canonical System Image: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app source package in Xenial: Fix Committed Bug description: bq M10 rc-proposed OS build 100 If I have few tabs open and in the first tab is a youtube video, it will start playing even if that tap is in the background after restarting the Browser. Steps to reproduce: 1. Start Browser 2. Open a tab with a youtube video in it, for example http://summit.ubuntu.com/uos-1605/meeting/22651/convergent-ubuntu-apps 3. Open few more tabs with other websites 4. If necessary move the tab with the video so it's the first from the left 5. Select any other tab 6. Close Browser 7. Start Browser again Expected result: I don't hear the sound from the video in the background tab. What happens instead: I hear the sound from the video in the background tab. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580290/+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 1637155] Re: Only one tap to unmaximize window
I hade a chance to test the tablet connected to a TV via HDMI cable. I used the tablet's screen as a touchpad. And I believe the issue with one tap to unmaximize wasn't there. I had to do double tap to go out of maximized window. -- 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/1637155 Title: Only one tap to unmaximize window Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: bq M10 rc-proposed r219 In desktop mode you need double tap to maximize an app window. But when the window is maximized to get it back to previous state it takes only one tap. I believe it should also be double tap. With only one tap you can't reveal window controls when it's maximized because after tapping it unaximize immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1637155/+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 1637996] Re: app switcher not responsive
On M10 tablet I notice some lag after swiping an app from the spread. Sometimes it takes about 2 seconds to 'align' the rest of the apps in the spread after an app was swiped away. -- 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/1637996 Title: app switcher not responsive Status in unity8 package in Ubuntu: Confirmed Bug description: MX4 running 451 After some period of use, the switched frequently becomes unresponsive, either it does not reveal right away on a right edge gesture, or when revealed selecting an app does nothing for some seconds. When in this state it is inconsistent, will work a few times, then not work. This regressed with the new implementation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637996/+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 1458336] Re: Allow users to decide which apps can display anything in the circle
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1458336 Title: Allow users to decide which apps can display anything in the circle Status in Canonical System Image: New Status in libusermetrics package in Ubuntu: Confirmed Bug description: Currently a user has no control over which apps can display stuff in the circle. Potentially an app could show there something what a user do not want. It would be nice to have for example setting (like for notifications) which apps are allowed to use the circle. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458336/+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 1637712] [NEW] Pixelated icon in notification bubble
Public bug reported: bq M10 rc-proposed r220 and bq e4.5 OTA13 Icon visible in the notification bubble looks pixelated. Screenshot attached. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161029_104649102.png" https://bugs.launchpad.net/bugs/1637712/+attachment/4769311/+files/screenshot20161029_104649102.png -- 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/1637712 Title: Pixelated icon in notification bubble Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r220 and bq e4.5 OTA13 Icon visible in the notification bubble looks pixelated. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637712/+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 1637523] [NEW] App from side stage loses focus when switching to desktop mode
Public bug reported: bq M10 rc-proposed r220 Steps to reproduce: 1. Open an app 2. Move it to the side stage 3. Switch to desktop mode Expected result: The app stays focused, on top of scopes What happens instead: The app is under scopes. Scopes are focused. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1637523 Title: App from side stage loses focus when switching to desktop mode Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r220 Steps to reproduce: 1. Open an app 2. Move it to the side stage 3. Switch to desktop mode Expected result: The app stays focused, on top of scopes What happens instead: The app is under scopes. Scopes are focused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637523/+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 1637502] [NEW] Keyboard stays on screen when doing spread
Public bug reported: bq M10 rc-proposed r220 If the OSK is visible and I'm starting to do swipe from the right, I expect OSK to hide. Meanwhile the OSK hides only when the spread is complete and I take my finger off the screen. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1637502 Title: Keyboard stays on screen when doing spread Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r220 If the OSK is visible and I'm starting to do swipe from the right, I expect OSK to hide. Meanwhile the OSK hides only when the spread is complete and I take my finger off the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637502/+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 1590801] Re: Selecting app icon does not show running app in side stage
Looks like this is fixed in r219 -- 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/1590801 Title: Selecting app icon does not show running app in side stage Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Run an app like settings, put in side stage, hide the app There are two cases: Select the icon from the launcher Nothing happens Select the icon from the dash Firs time nothing happens Select it again The app appears in the side stage rc-proposed M10 I expect bug #1583795 s related To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590801/+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 1583795] Re: Indicator does not lead to setting when settings are docked in side stage
Looks like this is fixed in r219 -- 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/1583795 Title: Indicator does not lead to setting when settings are docked in side stage Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: If the M10 tablet is in tablet mode and the settings app is docked in side stage. The settings app is in background. So it is not active. I touch the buttery settings indicator. What i expect: 1. The indicator section is closed 2. The settings app opens in the side and shows the battery part of the settings app. What happens: 1. The indicator section stays opened 2. If i close the indicator section, the settings app stays in the background. 3. If i take the settings app into the foreground( by swipping from the right edge to the left endge and touch onto the settings app, the empty side stage is shown for a short time and them the settings app appears in the side stage. Ubuntu version on the device: r109 If you dismiss the indicator and touch the dash, the correct settings page immediately displays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583795/+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 1587333] Re: When spread open, launched apps are in background
Looks like it's fixed in r219. -- 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/1587333 Title: When spread open, launched apps are in background Status in unity8 package in Ubuntu: In Progress Bug description: If you have the spread open and then launch a new application from the launcher, that new app is behind the most recently used app before this one. It should be in front as it was most recently launched. Steps to reproduce:- On a bq m10 running latest rc-proposed 1. Open a few apps 2. Swipe in from right to open the spread 3. Short swipe in from left to open launcher 4. Launch another app Expected behaviour:- App selected in step 4 is launched, spread closes, and that app comes to the front Actual behaviour:- App which was previously at the front is brought to front and newly launched app is behind it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1587333/+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 1637281] Re: issue with what to do when the sidestage empties
I'm on rc-proposed r220 and I cannot reproduce this issue. When I remove an app from the side stage, the side stage closes itself. -- 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/1637281 Title: issue with what to do when the sidestage empties Status in unity8 package in Ubuntu: New Bug description: STORY: You open the music player play some music, you move the player to the side stage and open the webbrowser to do some work, you find browsing albums easier in main stage so you drag the music app back out to find an album. STEPS: prerequisite frieza with some music on it 1. Open the music player 2. Set some music playing 3. three finger drag the music app to the side stage 4. Open the browser 5. Note the browser adjusts it's size to match the sidestage 6. Drag the Music app back out of side stage 7. at this point the player control are now under the sidestage EXPECTED: I either expect the windows to remain resized to fit the available screen or for the side stage to close upon emptying. ACTUAL: The empty sidestage covers the right hand side of the application under it meaning you have to close the stage in order to interact with that portion of the screen. This is very demonstratable on music app on the Frieza Tablet due to the convergent design of music app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637281/+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 1585278] Re: Browser window does not fill the screen width when starting
With the new Unity 8 on bq M10 rc-proposed r219 the issue seems to be gone. I can't reproduce it with the Browser app or with any other app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1585278 Title: Browser window does not fill the screen width when starting Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed r112 When staring Browser app in landscape first I see splash screen, then the Browser window which is squared and then the complete Browser window with tabs opened. For the beter UX the second step should be skipped or that window should take the full width of the tablet. Screenshot of the problem attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1585278/+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 1637261] [NEW] App window goes off screen after rotating
Public bug reported: bq M10 rc-proposed r219 Steps to reproduce: 1. Switch to desktop mode 2. In landscape open for example the Clock app 3. Move the Clock app window to the right 4. Rotate the tablet What happens: The Clock app window is off screen, not visible. Maybe would be better if app windows x and y values were relative to the screen width, height and not absolute like they are now. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1637261 Title: App window goes off screen after rotating Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 Steps to reproduce: 1. Switch to desktop mode 2. In landscape open for example the Clock app 3. Move the Clock app window to the right 4. Rotate the tablet What happens: The Clock app window is off screen, not visible. Maybe would be better if app windows x and y values were relative to the screen width, height and not absolute like they are now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637261/+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 1637258] [NEW] Side stage hides after rotating
Public bug reported: bq M10 rc-proposed r219 Steps to reproduce: 1. Open an app 2. Put it in the side stage 3. Rotate the tablet to portrait At this point you should see the app which was in the side stage on the whole screen 4. Rotate the tablet back to landscape Expected result: The app is visible in the side stage What happens instead: The side stage is closed but the app still has focus as its name is visible in the top bar (screenshot attached) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161027_172149214.png" https://bugs.launchpad.net/bugs/1637258/+attachment/4768277/+files/screenshot20161027_172149214.png -- 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/1637258 Title: Side stage hides after rotating Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 Steps to reproduce: 1. Open an app 2. Put it in the side stage 3. Rotate the tablet to portrait At this point you should see the app which was in the side stage on the whole screen 4. Rotate the tablet back to landscape Expected result: The app is visible in the side stage What happens instead: The side stage is closed but the app still has focus as its name is visible in the top bar (screenshot attached) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637258/+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 1637157] Re: Default app window size in desktop mode is too small
** Changed in: unity8 (Ubuntu) Status: Incomplete => Invalid -- 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/1637157 Title: Default app window size in desktop mode is too small Status in unity8 package in Ubuntu: Invalid Bug description: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637157/+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 1579017] Re: Camera app "invisible" in apps spread
After updating rc-proposed today to version r219, I can say it's no longer the problem. When the apps are in the spread state, the background is no longer black but instead the wallpaper is visible. Also under each app I can see its icon and name. For me this bug is fixed. -- 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/1579017 Title: Camera app "invisible" in apps spread Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed OS build number r97 Camera app is not visible when in apps spread Please see the screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1579017/+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 1574599] Re: Side stage stays open even if it's empty
Looks like it's no longer a problem. Using bq M10 rc-proposed r219. -- 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/1574599 Title: Side stage stays open even if it's empty Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Confirmed Bug description: bq M10 OTA-10.1 Steps to reproduce: 1. add an app to the side stage 2. remove that app from the side stage Expected results: The side stage closes itself What happens instead: The side stage stays open and displays information how to add applications to it. You have to manually close the side stage. I think showing that information when a user already knows how to put an app in the side stage is a bit pointless. Screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1574599/+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 1579017] Re: Camera app "invisible" in apps spread
** Attachment added: "Camera app clearly visible (r219)" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1579017/+attachment/4768252/+files/screenshot20161027_163914654.png -- 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/1579017 Title: Camera app "invisible" in apps spread Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed OS build number r97 Camera app is not visible when in apps spread Please see the screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1579017/+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 1637249] [NEW] Removing app from the spread closes the spread
Public bug reported: bq M10 rc-proposed r219 Steps to reproduce 1 open 3 apps 2 put one of them in the side stage 3 do the spread 4 swipe out the app which was in the side stage Expected result The spread stays What happens instead The spread closes and only one app is visible What I've noticed: if you swipe an app which was not in the side stage, the spread stays just fine. Also if there is more than one app in the side stage and you swipe one of them, the spread stays. It seems it closes only if there's one app in the side stage. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1637249 Title: Removing app from the spread closes the spread Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 Steps to reproduce 1 open 3 apps 2 put one of them in the side stage 3 do the spread 4 swipe out the app which was in the side stage Expected result The spread stays What happens instead The spread closes and only one app is visible What I've noticed: if you swipe an app which was not in the side stage, the spread stays just fine. Also if there is more than one app in the side stage and you swipe one of them, the spread stays. It seems it closes only if there's one app in the side stage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637249/+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 1637209] [NEW] Side stage handle bar and its shadow cover main app
Public bug reported: bq M10 rc-proposed r219 The vertical 'handle' of the side stage and its shadow cover part of the main app window. Screenshot attached. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161027_144527108.png" https://bugs.launchpad.net/bugs/1637209/+attachment/4768230/+files/screenshot20161027_144527108.png -- 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/1637209 Title: Side stage handle bar and its shadow cover main app Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 The vertical 'handle' of the side stage and its shadow cover part of the main app window. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637209/+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 1637205] [NEW] Side stage available in portrait
Public bug reported: bq M10 rc-proposed r219 It is possible to create the side stage in when the tablet is in portrait orientation. 1. Turn the tablet to portrait 2. Open an app 3. Use 3 fingers drag to move the app to the side stage Result attached ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161027_143854699.png" https://bugs.launchpad.net/bugs/1637205/+attachment/4768228/+files/screenshot20161027_143854699.png -- 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/1637205 Title: Side stage available in portrait Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 It is possible to create the side stage in when the tablet is in portrait orientation. 1. Turn the tablet to portrait 2. Open an app 3. Use 3 fingers drag to move the app to the side stage Result attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637205/+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 1637157] Re: Default app window size in desktop mode is too small
After removing that file and restarting the tablet, I no longer see this problem. -- 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/1637157 Title: Default app window size in desktop mode is too small Status in unity8 package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637157/+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 1637159] Re: After unmaximizing app window it lands in a different place than it was before maximizing
short video about the problem: https://youtu.be/7IW37TRDnQg -- 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/1637159 Title: After unmaximizing app window it lands in a different place than it was before maximizing Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 Steps to reproduce: 1. Switch to desktop mode 2. Open an app, Dekko in my case 3. Double tap app title bar to maximize 4. Tap the app title bar to unmaximize Expected result: App is in the same place as before maximizing What happens instead: App window is in different place, sometimes off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637159/+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 1637159] [NEW] After unmaximizing app window it lands in a different place than it was before maximizing
Public bug reported: bq M10 rc-proposed r219 Steps to reproduce: 1. Switch to desktop mode 2. Open an app, Dekko in my case 3. Double tap app title bar to maximize 4. Tap the app title bar to unmaximize Expected result: App is in the same place as before maximizing What happens instead: App window is in different place, sometimes off screen ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1637159 Title: After unmaximizing app window it lands in a different place than it was before maximizing Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 Steps to reproduce: 1. Switch to desktop mode 2. Open an app, Dekko in my case 3. Double tap app title bar to maximize 4. Tap the app title bar to unmaximize Expected result: App is in the same place as before maximizing What happens instead: App window is in different place, sometimes off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637159/+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 1637155] [NEW] Only one tap to unmaximize window
Public bug reported: bq M10 rc-proposed r219 In desktop mode you need double tap to maximize an app window. But when the window is maximized to get it back to previous state it takes only one tap. I believe it should also be double tap. With only one tap you can't reveal window controls when it's maximized because after tapping it unaximize immediately. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1637155 Title: Only one tap to unmaximize window Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 In desktop mode you need double tap to maximize an app window. But when the window is maximized to get it back to previous state it takes only one tap. I believe it should also be double tap. With only one tap you can't reveal window controls when it's maximized because after tapping it unaximize immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637155/+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 1637157] [NEW] Default app window size in desktop mode is too small
Public bug reported: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161027_120104080.png" https://bugs.launchpad.net/bugs/1637157/+attachment/4768191/+files/screenshot20161027_120104080.png -- 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/1637157 Title: Default app window size in desktop mode is too small Status in unity8 package in Ubuntu: New Bug description: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1637157/+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
