[Touch-packages] [Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04
*** This bug is a duplicate of bug 1842320 *** https://bugs.launchpad.net/bugs/1842320 I see the same when booting on Ubuntu 23.04 on LG Gram 17Z90R (32 GB RAM). Loading initial ramdisk error: out of memory Then, it complains something about zstd image being corrupted. However, after a few seconds, booting continues and everything seems to work correctly. -- 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: Confirmed Status in initramfs-tools source package in Jammy: Confirmed 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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same issue on LG Gram 17Z90R - no audio. -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen
This bug only is present on Wayland. -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: This started to happen with Ubuntu 19.10. When an animated gif is displayed in a browser, gnome-shell begins using 100% CPU on all cores. To reproduce: 1) open Firefox, or Chromium 2) load an URL where an animated gif is displayed - you can also use this direct link to https://i.stack.imgur.com/h6viz.gif 3) gnome-shell will start using 100% CPU on all cores (as long as Firefox/Chromium window is in the foreground) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 GsettingsChanges: InstallationDate: Installed on 2019-05-12 (172 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+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 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen
There is one more change I did after upgrading from 19.04 to 19.10. This is a KVM VM - and for some reason, the GUI (X) sometimes freezes after the VM is paused/saved/resumed, while SSH still works (this was also before 19.10 and behaviour did not improve in 19.10). I've changed to Wayland to see if it this kind of freezing happens there as well (so far, it doesn't). High CPU usage on all cores happens with Wayland only. I've just checked, it doesn't happen with regular X; CPU usage is normal/low there. -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen Status in gnome-shell package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in mutter package in Ubuntu: New Bug description: This started to happen with Ubuntu 19.10. When an animated gif is displayed in a browser, gnome-shell begins using 100% CPU on all cores. To reproduce: 1) open Firefox, or Chromium 2) load an URL where an animated gif is displayed - you can also use this direct link to https://i.stack.imgur.com/h6viz.gif 3) gnome-shell will start using 100% CPU on all cores (as long as Firefox/Chromium window is in the foreground) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 GsettingsChanges: InstallationDate: Installed on 2019-05-12 (172 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+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 1714301] Re: systemd-networkd hangs my boot (wireless)
I still see this issue with Ununtu 17.10 with all updates installed. -- 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/1714301 Title: systemd-networkd hangs my boot (wireless) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Fix Released Bug description: Since that systemd-networkd is enabled, my laptop doesn't boot (hangs) until I plug in an ethernet cable. Here is the journal from this boot, note the hang up until I connect my cable at 17:51:35: août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo août 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: Inva août 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting août 31 17:50:08 tidus systemd[1]: systemd-resolved-update-resolvconf.service: Start request repeated too quickly. août 31 17:50:08 tidus systemd[1]: Failed to start systemd-resolved-update-resolvconf.service. août 31 17:50:08 tidus systemd[1]: systemd-resolved-update-resolvconf.service: Failed with result 'start-limit-hit'. août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting. août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server. août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 " août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2 août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22. août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22. août 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], "/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script '/etc/Ne août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start running ordered scripts... août 31 17:50:08 tidus NetworkManager[2340]: [1504194608.6148] dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat août 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting. août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22. août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22. août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 " août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2 août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], "/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script '/etc/N août 31 17:50:08 tidus NetworkManager[2340]: [1504194608.6612] dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22. août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22. août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 " août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2 août 31 17:50:08 tidu
[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B
I'm also seeing this quite frequently on Dell Precision 5520 running Ubuntu 17.10 with Wayland: [85710.937972] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=15608 end=15609) time 761 us, min 1073, max 1079, scanline start 1035, end 1086 [87385.139517] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=115949 end=115950) time 14743 us, min 1073, max 1079, scanline start 421, end 292 When it happens, screen very often freezes for a bit. -- 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/1660619 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B Status in xorg package in Ubuntu: Confirmed Bug description: I've a dual monitor setup and I'm running latest version of kubuntu. After a few days of uptime the desktop becomes so slow that I've to reboot it. In the log I find those errors, I don't know if they are related: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max 1079, scanline start 1072, end 1080 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 31 14:06:17 2017 DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 [1462:7978] InstallationDate: Installed on 2013-04-25 (1376 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: MSI MS-7978 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Jan 28 11:57:37 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packag
[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B
I'm also seeing this quite frequently on Dell Precision 5520 running Ubuntu 17.10 with Wayland: [85710.937972] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=15608 end=15609) time 761 us, min 1073, max 1079, scanline start 1035, end 1086 [87385.139517] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=115949 end=115950) time 14743 us, min 1073, max 1079, scanline start 421, end 292 When it happens, screen very often freezes for a bit. -- 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/1660619 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B Status in xorg package in Ubuntu: Confirmed Bug description: I've a dual monitor setup and I'm running latest version of kubuntu. After a few days of uptime the desktop becomes so slow that I've to reboot it. In the log I find those errors, I don't know if they are related: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max 1079, scanline start 1072, end 1080 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 31 14:06:17 2017 DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 [1462:7978] InstallationDate: Installed on 2013-04-25 (1376 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: MSI MS-7978 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Jan 28 11:57:37 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packag
[Touch-packages] [Bug 1710353] [NEW] unable to maximize windows (doubled title bars?) in Ubuntu 17.10 alpha
Public bug reported: In Ubuntu 17.10 alpha (with Gnome being the default environment) - when compared to Unity on Ubuntu 17.04 and earlier - it is not possible to fully maximize a window. There are two title bars in Ubuntu 17.10 alpha and Gnome after a window is maximized, while we had only one title bar in Unity and earlier Ubuntu versions. Two title bars instead of one waste screen real estate and don't contain any extra information. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-desktop 1.379 Uname: Linux 4.12.2-041202-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Aug 12 19:40:16 2017 InstallationDate: Installed on 2017-04-14 (120 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty ** Attachment added: "two title bars instead of one?" https://bugs.launchpad.net/bugs/1710353/+attachment/4931151/+files/double-title-bar.png ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931155/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931154/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931153/+files/JournalErrors.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931152/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1710353 Title: unable to maximize windows (doubled title bars?) in Ubuntu 17.10 alpha Status in ubuntu-meta package in Ubuntu: New Bug description: In Ubuntu 17.10 alpha (with Gnome being the default environment) - when compared to Unity on Ubuntu 17.04 and earlier - it is not possible to fully maximize a window. There are two title bars in Ubuntu 17.10 alpha and Gnome after a window is maximized, while we had only one title bar in Unity and earlier Ubuntu versions. Two title bars instead of one waste screen real estate and don't contain any extra information. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-desktop 1.379 Uname: Linux 4.12.2-041202-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Aug 12 19:40:16 2017 InstallationDate: Installed on 2017-04-14 (120 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+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 1687212] Re: ~16 GB written to disk from power on till lightdb login screen?
** Description changed: After each system boot, iostat -m shows that the kernel has written around 16 GB to SSD disk: avg-cpu: %user %nice %system %iowait %steal %idle -9.100.00 10.062.380.00 78.47 + 9.100.00 10.062.380.00 78.47 Device:tpsMB_read/sMB_wrtn/sMB_readMB_wrtn sda 702.3216.91 1495.65182 16108 dm-0808.3615.64 1495.65168 16108 dm-1786.8215.39 0.01165 0 dm-2 10.21 0.21 1495.64 2 16107 - It's a fresh Ubuntu 17.04 installation with rootfs installed on LUKS. + It's a fresh Ubuntu 17.04 installation with rootfs installed on + encrypted LVM (selected during the installation). /proc/diskstats (https://www.kernel.org/doc/Documentation/ABI/testing /procfs-diskstats) seem to be matching the output of "iostat -m". - Please note that dm-2 is 16 GB swap (the system has 16 GB RAM): $ ls /dev/mapper/ -l total 0 crw--- 1 root root 10, 236 Apr 30 01:53 control lrwxrwxrwx 1 root root 7 Apr 30 01:53 sda3_crypt -> ../dm-0 lrwxrwxrwx 1 root root 7 Apr 30 01:53 ubuntu--vg-root -> ../dm-1 lrwxrwxrwx 1 root root 7 Apr 30 01:53 ubuntu--vg-swap_1 -> ../dm-2 - - $ cat /proc/swaps + $ cat /proc/swaps FilenameTypeSizeUsed Priority /dev/dm-2 partition 164945880 -1 - - So what seems to happen, is that the OS overwrites the whole encrypted swap partition during bootup. + So what seems to happen, is that the OS overwrites the whole encrypted + swap partition during bootup. This is very worrying, given that it's SSD disk! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 Uname: Linux 4.11.0-041100rc7-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sun Apr 30 01:57:04 2017 ExecutablePath: /lib/systemd/systemd InstallationDate: Installed on 2017-04-14 (15 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse - Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse + Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: - TERM=linux - PATH=(custom, no user) + TERM=linux + PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-041100rc7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0GPNW9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. -- 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/1687212 Title: ~16 GB written to disk from power on till lightdb login screen? Status in systemd package in Ubuntu: New Bug description: After each system boot, iostat -m shows that the kernel has written around 16 GB to SSD disk: avg-cpu: %user %nice %system %iowait %steal %idle 9.100.00 10.062.380.00 78.47 Device:tpsMB_read/sMB_wrtn/sMB_readMB_wrtn sda 702.3216.91 1495.65182 16108 dm-0808.3615.64 1495.65168 16108 dm-1786.8215.39 0.01165 0 dm-2 10.21 0.21 1495.64 2 16107 It's a fresh Ubuntu 17.04 installation with rootfs installed on encrypted LVM (selected during the installation). /proc/diskstats (https://www.kernel.org/doc/Documentation/ABI/testing /procfs-diskstats) seem to be matching the output of "iostat -m". Please note that dm-2 is 16 GB swap (the system has 16 GB RAM): $ ls /dev/mapper/ -l total 0 crw--- 1 root root 10, 236 Apr 30 01:53 control lrwxrwxrwx 1 root root 7 Apr 30 01:53 sda3_crypt -> ../dm-0 lrwxrwxrwx 1 root root
[Touch-packages] [Bug 1687212] [NEW] ~16 GB written to disk from power on till lightdb login screen?
Public bug reported: After each system boot, iostat -m shows that the kernel has written around 16 GB to SSD disk: avg-cpu: %user %nice %system %iowait %steal %idle 9.100.00 10.062.380.00 78.47 Device:tpsMB_read/sMB_wrtn/sMB_readMB_wrtn sda 702.3216.91 1495.65182 16108 dm-0808.3615.64 1495.65168 16108 dm-1786.8215.39 0.01165 0 dm-2 10.21 0.21 1495.64 2 16107 It's a fresh Ubuntu 17.04 installation with rootfs installed on LUKS. /proc/diskstats (https://www.kernel.org/doc/Documentation/ABI/testing /procfs-diskstats) seem to be matching the output of "iostat -m". Please note that dm-2 is 16 GB swap (the system has 16 GB RAM): $ ls /dev/mapper/ -l total 0 crw--- 1 root root 10, 236 Apr 30 01:53 control lrwxrwxrwx 1 root root 7 Apr 30 01:53 sda3_crypt -> ../dm-0 lrwxrwxrwx 1 root root 7 Apr 30 01:53 ubuntu--vg-root -> ../dm-1 lrwxrwxrwx 1 root root 7 Apr 30 01:53 ubuntu--vg-swap_1 -> ../dm-2 $ cat /proc/swaps FilenameTypeSizeUsedPriority /dev/dm-2 partition 164945880 -1 So what seems to happen, is that the OS overwrites the whole encrypted swap partition during bootup. This is very worrying, given that it's SSD disk! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 Uname: Linux 4.11.0-041100rc7-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sun Apr 30 01:57:04 2017 ExecutablePath: /lib/systemd/systemd InstallationDate: Installed on 2017-04-14 (15 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-041100rc7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0GPNW9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1687212 Title: ~16 GB written to disk from power on till lightdb login screen? Status in systemd package in Ubuntu: New Bug description: After each system boot, iostat -m shows that the kernel has written around 16 GB to SSD disk: avg-cpu: %user %nice %system %iowait %steal %idle 9.100.00 10.062.380.00 78.47 Device:tpsMB_read/sMB_wrtn/sMB_readMB_wrtn sda 702.3216.91 1495.65182 16108 dm-0808.3615.64 1495.65168 16108 dm-1786.8215.39 0.01165 0 dm-2 10.21 0.21 1495.64 2 16107 It's a fresh Ubuntu 17.04 installation with rootfs installed on LUKS. /proc/diskstats (https://www.kernel.org/doc/Documentation/ABI/testing /procfs-diskstats) seem to be matching the output of "iostat -m". Please note that dm-2 is 16 GB swap (the system has 16 GB RAM): $ ls /dev/mapper/ -l total 0 crw--- 1 root root 10, 236 Apr 30 01:53 control lrwxrwxrwx 1 root root 7 Apr 30 01:53 sda3_crypt -> ../dm-0 lrwxrwxrwx 1 root root 7 Apr 30 01:53 ubuntu--vg-root -> ../dm-1 lrwxrwxrwx 1 root root 7 Apr 30 01:53 ubuntu--vg-swap_1 -> ../dm-2 $ cat /proc/swaps FilenameTypeSizeUsed Priority /dev/dm-2 partition 164945880 -1 So what seems to happen, is that the OS overwrites the whole encrypted swap partition during bootup. This is very worrying, given that it's SSD disk! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 Uname: Linux 4.11.0-041100rc7-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sun Apr 30 01:57:04 2017
[Touch-packages] [Bug 992464] Re: Menu not accessible when run via ssh xforwarding
I'm still seeing this issue with Ubuntu 17.04. To reproduce: # ssh to localhost (or, any other host) ssh -X user@localhost # run a simple command like gedit or gnome-calculator gedit They run fine, unfortunately the menu is not available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/992464 Title: Menu not accessible when run via ssh xforwarding Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Symptom: When starting e.g., evince via X11 Forwarding (ssh -X), then the menu is not displayed. Test setup: A ubuntu/precise laptop and a ubuntu/precise workstation, both 64bit. --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Package: evince 3.4.0-0ubuntu1 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=43083bcc-3306-4670-9169-937fd10be832 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Tags: precise apparmor Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-03-03 (58 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin plugdev proxy sambashare sbuild To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/992464/+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 812394] Re: Disable hibernate option by default
I'm using Samsung Ativ 5 laptop. Unfortunately suspend to RAM does not work here - the laptop does suspend, but never wakes up. On the other hand, suspend to disk works fine - the laptop does suspend and wakes up correctly. Leaving a broken suspend to RAM option is a bug in my opinion, especially that the only working option of suspending to disk was removed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/812394 Title: Disable hibernate option by default Status in Ayatana Design: Fix Released Status in Pantheon Session Indicator: Invalid Status in PolicyKit: Invalid Status in “policykit-desktop-privileges” package in Ubuntu: Fix Released Status in “policykit-desktop-privileges” source package in Precise: Fix Released Bug description: - TO RE-ENABLE HIBERNATE: If the hibernate option is supported by your system and you need it, you can re-enable it as follows: https://help.ubuntu.com/12.04/ubuntu-help/power-hibernate.html You may be also interested in subscribing to the bug #882040, which tracks the implementation of a configuration tool to toggle hibernate and suspend. - I'd like to propose a change in the design of Power preferences in the GNOME control center: https://wiki.ubuntu.com/Power Instead of going through the "certification" path, we can simply disable the options about suspend/hibernate if it's not supported on the current hardware (we have API for this in upower). I think this solution is more scalable, as we do not need to maintain a database with "certified" hardware. Also, we can add a button or a informative text when suspend/hibernate doesn't work to guide the users about what to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/812394/+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
