[Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)
Hey to all! Try disabling the following in Bios - Boot Options - Network Boot - set to Disabaled. Make sure to download the latest Ubuntu 22.04 .ISO. That helped me for my ENVY x360 15 (2021)! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970127 Title: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)
I'm following as well. Affected too. Envy x360 15 2021. The previous Ubuntu versions boot correcly (21.10, 20.04). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970127 Title: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969140] Re: graphic glitches when minimizing and maximizing apps
I reported this as well, however, they think that it is issue with my device. https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1967471 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969140 Title: graphic glitches when minimizing and maximizing apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967471] [NEW] Artifacts when any window is being minimized to tray (on the second or more tries)
Public bug reported: sudo update and sudo apt full-upgrade have been performed as well. Video screen has been attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 07:36:46 2022 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Запись экрана от 01.04.2022 07:34:56.webm" https://bugs.launchpad.net/bugs/1967471/+attachment/5575524/+files/%D0%97%D0%B0%D0%BF%D0%B8%D1%81%D1%8C%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%2001.04.2022%2007%3A34%3A56.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967471 Title: Artifacts when any window is being minimized to tray (on the second or more tries) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
this is affecting me too. Filesystem Size Used Avail Use% Mounted on udev 981M 4.0K 981M 1% /dev tmpfs200M 1.1M 199M 1% /run /dev/mapper/ubuntu--vg-root 72G 7.4G 61G 11% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 997M 404K 996M 1% /run/shm none 100M 52K 100M 1% /run/user /dev/sda1236M 211M 14M 95% /boot /home/rebecca/.Private72G 7.4G 61G 11% /home/rebecca i thought that it was because my drive was full. i think its only maybe 40 gig? thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886054] Re: chromium-browser crashed with SIGABRT
Just ran into this problem myself. Occurred after debian auto updates, with first apparent symptom being that Chromium wouldn't open. Paying closer attention showed that Chromium was actually opening, but closing quickly. This led to an attempt to open Chromium from the Terminal with parameters --enable-logging --v=1 : which produced a report that included diagnosis/prescription: [13435:13435:543904710486:FATAL:shared_memory_posix.cc(176)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix Tried 'sudo chmod 1777 /dev/shm' , and the fix worked. Am able to reopen Chromium now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886054 Title: chromium-browser crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/886054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780717] Re: Using PKCS#12 file requires password for private key
Ubuntu 11.10 (Gnome) Using a pkcs#12 file from pfsense I entered a couple of random characters in the box (though the key file or server didn't require it) and I could save connect fine. Ubuntu 11.10 (XFCE) Same as above but the gui prompts for the password when trying to connect to the vpn. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780717 Title: Using PKCS#12 file requires password for private key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/780717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773841] Re: \\192.168.1.x opens http:\\192.168.1.x in firefox as opposed to smb://192.168.1.x in nautilus
Opened ubuntu 11.10, open nautils, control-L, and then tested: \\ no longer directs to firefox, it appends the path to your current focused window location ftp:// works. eg ftp://ftp.ubuntu.com scp is not correct, using ssh:// gives the desired result This can probably be closed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773841 Title: \\192.168.1.x opens http:\\192.168.1.x in firefox as opposed to smb://192.168.1.x in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/773841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
I've been trying to compile this patch into the 2.6.37rc2 mainline kernel but have run into a few issues. The reason for trying to get it up and running with .37 to resolve the well documented lag/speed issues on Maverick with the .35 kernel. So I patched the .37 toshiba.acpi with the link above and tried to compile: dsm...@pez:/usr/src/linux-2.6.37-rc2/drivers/platform/x86$ sudo make -C /usr/src/linux-headers-`uname -r` M=`pwd` modules make: Entering directory `/usr/src/linux-headers-2.6.37-020637rc2-generic' CC [M] /usr/src/linux-2.6.37-rc2/drivers/platform/x86/toshiba_acpi.o /usr/src/linux-2.6.37-rc2/drivers/platform/x86/toshiba_acpi.c:819: error: unknown field ‘ioctl’ specified in initializer /usr/src/linux-2.6.37-rc2/drivers/platform/x86/toshiba_acpi.c:820: warning: initialization from incompatible pointer type make[1]: *** [/usr/src/linux-2.6.37-rc2/drivers/platform/x86/toshiba_acpi.o] Error 1 make: *** [_module_/usr/src/linux-2.6.37-rc2/drivers/platform/x86] Error 2 make: Leaving directory `/usr/src/linux-headers-2.6.37-020637rc2-generic' Seems that ioctl variable has been removed from 2.6.37rc1. Ioctl was removed by the merging of the BKL (big kernel lock) tree. So I hacked toshiba_acpi.c a little to get it compiling from: (line 859) static int tosh_ioctl(struct inode* ip, struct file* fp, unsigned int cmd, unsigned long arg) to: static long tosh_ioctl(struct file* fp, unsigned int cmd, unsigned long arg) and also from: (line 921) .ioctl = tosh_ioctl to: .compat_ioctl = tosh_ioctl Compiles clean, inserts and loads up but I cant get access to toshet. What is interesting is I can cat /proc/toshiba dsm...@pez:/usr/src/linux-2.6.37-rc2/drivers/platform/x86$ cat /proc/toshiba 1.1 0xfcff 0.0 0.45 0x418e 0x00 Well I'm no kernel hacker and am not really sure what Im doing past here... any ideas? -- required kernel toshiba support not enabled https://bugs.launchpad.net/bugs/644898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676236] Re: Toshiba ACPI support is disabled in the new kernel
*** This bug is a duplicate of bug 644898 *** https://bugs.launchpad.net/bugs/644898 ** This bug has been marked a duplicate of bug 644898 required kernel toshiba support not enabled * You can subscribe to bug 644898 by following this link: https://bugs.launchpad.net/ubuntu/+source/toshset/+bug/644898/+subscribe -- Toshiba ACPI support is disabled in the new kernel https://bugs.launchpad.net/bugs/676236 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
I can however confirm that merging the patch back into the 2.6.35-22 version works fine. -- required kernel toshiba support not enabled https://bugs.launchpad.net/bugs/644898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
** Attachment added: 2.6.35-22-generic amd64 https://bugs.launchpad.net/ubuntu/+source/toshset/+bug/644898/+attachment/1737362/+files/toshiba_acpi.ko -- required kernel toshiba support not enabled https://bugs.launchpad.net/bugs/644898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
Same as #3 This compounded with random hard lockups. -- required kernel toshiba support not enabled https://bugs.launchpad.net/bugs/644898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606547] Re: toshiba_acpi no control of display backlight after suspend to ram
I can confirm this issue also affects the Toshiba R700. If this should be filed upstream can someone recommed where? It seems the hardware power cycle (shutdown or suspend to disk) is the only way to regain brightness control. The toshest util enables changing the brightness and turning off the backlight before a suspend to ram, but after resuming turning the backlight off and on give odd results dimming and undimming at steps untill the intensity doesn't alter. http://ubuntuforums.org/showthread.php?p=9710352 -- toshiba_acpi no control of display backlight after suspend to ram https://bugs.launchpad.net/bugs/606547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
