[Bug 1919431] [NEW] Installtion crashed on grub - Dual boot option
Public bug reported: While setting up grub the installer crashed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 17 11:09:11 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_ZA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919431 Title: Installtion crashed on grub - Dual boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1919431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913940] Re: Wifi keeps disconnecting and reconnecting all the time
Hi, any sign that this issue is being looked at? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913940 Title: Wifi keeps disconnecting and reconnecting all the time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919008] Re: 'Extract here' for .zip files not working as intended.
Yes, as it's a security update it probably got autoinstalled. Do you still get the issue? Could you attach an example of problematic file to the bug? The dpkg -s command you are using is invalid, the argument is a package name not a version, so it would be $ dpkg -s libgnome-autoar-0-0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919008 Title: 'Extract here' for .zip files not working as intended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1919008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919426] Re: WIFI card disappear when booting with an USB device plugged
** Description changed: + -on Ubuntu 20.04- WIFI card disappear when booting with an USB device plugged. There is no WIFI connection anymore, not at all. If I go under System> Networks I get only Ethernet connections and ethernet device. Wifi card device is not even shown or recognized, it looks like I don't have even plugged in/installed. If you boot the laptop with an usb mouse for example this happens all the time. So I am forced to boot the laptop disconencting all the devices and then after I logged in, Wifi will be there working and only then I can connect my mouse or USB devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919426 Title: WIFI card disappear when booting with an USB device plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1919426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919429] [NEW] Impossible Login: if dual screen is active, mouse is locked only in one monitor, the wrong one
Public bug reported: Impossible Login ubuntu 20.04 : if dual screen is active with an HDMI cable and set to extended desktop mode (that means that I have two screens displaying a part of the same big dekstop,and not duplicated) mouse is locked only in one monitor, the wrong one. This means that at login time, I get my Avatar with the password area in the second screen, and I get the purple ubuntu wallpaper and the mouse pointer on my Laptop screen instead. Then when I try to move the mouse from the Laptop screen to the second external screen mouse is stucked at the border and doesnt jump to the other screen so I can't click on the second screen and login. The only way to login is to disconnect the second monitor so the login aerea comes back in my laptop screen, then login in and then connect the monitor again. Also keep in mind that I set my laptop screen as the main one, and the external as secondary so at login time it's wrong that i get the main login aerea in the secondary screen instead. That is a bug too, but the main is concern is that I can't even move the mouse there to login. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919429 Title: Impossible Login: if dual screen is active, mouse is locked only in one monitor, the wrong one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917409] Re: neutron-l3-agents won't become active
*** This bug is a duplicate of bug 1883089 *** https://bugs.launchpad.net/bugs/1883089 ** This bug has been marked a duplicate of bug 1883089 [L3] floating IP failed to bind due to no agent gateway port(fip-ns) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917409 Title: neutron-l3-agents won't become active To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1917409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918884] Re: .zfs snapshot directory is not accessible when snapdir=visible
Reported state can be worked around, although I still think, that even without zfsutils-linux installed system should be able to access .zfs ditectory. ** Changed in: zfs-fuse (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918884 Title: .zfs snapshot directory is not accessible when snapdir=visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-fuse/+bug/1918884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918884] Re: .zfs snapshot directory is not accessible when snapdir=visible
It seems that lack of "zfsutils-linux" leads to behavior described above. After ___ apt install zfsutils-linux reboot zpool import pool1 -f ___ situation does look like this: ___ dpkg -l | grep zf ii libzfs2linux 0.8.3-1ubuntu12.6 amd64OpenZFS filesystem library for Linux rc zfs-fuse 0.7.0-20 amd64ZFS on FUSE ii zfs-zed 0.8.3-1ubuntu12.6 amd64OpenZFS Event Daemon ii zfsnap 1.11.1-5.1all Automatic snapshot creation and removal for ZFS ii zfsutils-linux 0.8.3-1ubuntu12.6 amd64command-line tools to manage OpenZFS filesystems ___ ls -la /var/lib/postgresql/ total 30 drwxr-xr-x 4 postgres postgres5 Mar 10 15:32 . drwxr-xr-x 45 root root 4096 Mar 17 08:32 .. drwxr-xr-x 3 postgres postgres3 Mar 10 15:29 12 -rw--- 1 postgres postgres5 Mar 10 15:32 .bash_history -rw--- 1 postgres postgres 29 Mar 10 15:32 .psql_history drwxrwxrwx 1 root root0 Mar 17 08:38 .zfs ___ cd /var/lib/postgresql/.zfs/ :/var/lib/postgresql/.zfs# ___ Situation is now good enough for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918884 Title: .zfs snapshot directory is not accessible when snapdir=visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-fuse/+bug/1918884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919248] Re: Nvidia driver never usable if Ubuntu was installed in safe graphics mode
*** This bug is a duplicate of bug 1919285 *** https://bugs.launchpad.net/bugs/1919285 ** This bug has been marked a duplicate of bug 1919285 Nvidia driver not loaded, resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919248 Title: Nvidia driver never usable if Ubuntu was installed in safe graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1919248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919285] Re: Nvidia driver not loaded, low resolution and no acceleration, since kernel 5.8.0-45.51
** Summary changed: - Nvidia driver not loaded, resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 + Nvidia driver not loaded, low resolution and no acceleration, since kernel 5.8.0-45.51 ** Summary changed: - Nvidia driver not loaded, low resolution and no acceleration, since kernel 5.8.0-45.51 + Nvidia kernel driver not loaded, low resolution and no acceleration, since kernel 5.8.0-45.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919285 Title: Nvidia kernel driver not loaded, low resolution and no acceleration, since kernel 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919425] [NEW] Xorg freeze
Public bug reported: I've been getting freezes on Ubunyu 20.04 on my Dell Latitude 7420 laptop with a secondary display connected through a WD19 Dell dock. I'm on the supposedly-certified 5.6.0-1048-oem kernel, have tried 5.8 and 5.10 without much success (other types of freezes). Some freezes lock up the machine hard with no way to ssh in or check anything and no logs. The one below I was able to ssh in and dump dmesg, rebooting via ssh froze and I had to do a hard reboot. [ 7557.306199] BUG: unable to handle page fault for address: 8ceca8900758 [ 7557.306206] #PF: supervisor write access in kernel mode [ 7557.306209] #PF: error_code(0x0002) - not-present page [ 7557.306211] PGD 39601067 P4D 39601067 PUD 0 [ 7557.306217] Oops: 0002 [#1] SMP NOPTI [ 7557.306221] CPU: 4 PID: 6181 Comm: chrome Tainted: GW O 5.6.0-1048-oem #52-Ubuntu [ 7557.306223] Hardware name: Dell Inc. Latitude 7420/095TWY, BIOS 1.3.5 01/18/2021 [ 7557.306231] RIP: 0010:remove_wait_queue+0x25/0x50 [ 7557.306235] Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc 53 48 89 f3 e8 f9 e2 a1 00 48 8b 53 18 4c 89 e7 48 89 c6 48 8b 43 20 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 43 18 48 [ 7557.306237] RSP: 0018:b14e015cba78 EFLAGS: 00010046 [ 7557.306240] RAX: 8caca8900750 RBX: b14e015cbc80 RCX: 0001 [ 7557.306242] RDX: 8ceca8900750 RSI: 0282 RDI: 8caca8900748 [ 7557.306244] RBP: b14e015cba88 R08: 8cac52a2c000 R09: 0003 [ 7557.306245] R10: 0084 R11: fffb159a R12: 8caca8900748 [ 7557.306247] R13: R14: b14e015cbc70 R15: 0001 [ 7557.306250] FS: 7f137ff04d80() GS:8cacaf70() knlGS: [ 7557.306252] CS: 0010 DS: ES: CR0: 80050033 [ 7557.306254] CR2: 8ceca8900758 CR3: 0007ee554005 CR4: 00760ee0 [ 7557.306255] PKRU: 5554 [ 7557.306257] Call Trace: [ 7557.306265] poll_freewait+0x42/0xa0 [ 7557.306268] do_sys_poll+0x480/0x520 [ 7557.306275] ? poll_select_finish+0x210/0x210 [ 7557.306278] ? poll_select_finish+0x210/0x210 [ 7557.306282] ? poll_select_finish+0x210/0x210 [ 7557.306284] ? poll_select_finish+0x210/0x210 [ 7557.306287] ? poll_select_finish+0x210/0x210 [ 7557.306292] ? fput+0x13/0x15 [ 7557.306296] ? __sys_sendto+0x153/0x190 [ 7557.306300] ? __fget_light+0x62/0x80 [ 7557.306303] ? fput+0x13/0x15 [ 7557.306306] ? __sys_recvmsg+0x88/0xa0 [ 7557.306310] ? ktime_get_ts64+0x4c/0xe0 [ 7557.306313] __x64_sys_poll+0xa5/0x140 [ 7557.306319] do_syscall_64+0x57/0x1b0 [ 7557.306324] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 7557.306328] RIP: 0033:0x7f1381360aff [ 7557.306330] Code: 54 24 1c 48 89 74 24 10 48 89 7c 24 08 e8 79 1c f8 ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 48 8b 7c 24 08 b8 07 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2b 44 89 c7 89 44 24 08 e8 ad 1c f8 ff 8b 44 [ 7557.306332] RSP: 002b:7fff0cd693d0 EFLAGS: 0293 ORIG_RAX: 0007 [ 7557.306335] RAX: ffda RBX: 7f13828e60d0 RCX: 7f1381360aff [ 7557.306336] RDX: 0ea1 RSI: 0005 RDI: 377ea82ca210 [ 7557.306338] RBP: 377ea82ca210 R08: R09: 0001 [ 7557.306339] R10: 377ea8b40460 R11: 0293 R12: 0005 [ 7557.306341] R13: 7fff0cd69414 R14: 0ea1 R15: 377ea6d9bd10 [ 7557.306346] Modules linked in: rfcomm vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_realtek snd_hda_codec_generic snd_soc_acpi dell_laptop mei_hdcp intel_rapl_msr ledtrig_audio snd_hda_intel snd_intel_dspcfg x86_pkg_temp_thermal intel_powerclamp soundwire_intel soundwire_generic_allocation coretemp soundwire_cadence snd_hda_codec kvm_intel kvm snd_hda_core soundwire_bus dell_wmi intel_cstate snd_soc_core snd_compress dell_smbios ac97_bus serio_raw snd_pcm_dmaengine dcdbas snd_usb_audio dell_wmi_descriptor snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event wmi_bmof uvcvideo snd_rawmidi videobuf2_vmalloc snd_seq videobuf2_memops snd_seq_device snd_timer videobuf2_v4l2 joydev btusb cdc_ether snd input_leds videobuf2_common [ 7557.306386] btrtl usbnet soundcore btbcm iwlmvm videodev btintel mac80211 r8152 mc libarc4 mii bluetooth ecdh_generic ecc iwlwifi hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_als hid_sensor_trigger cfg80211 industrialio_triggered_buffer kfifo_buf mei_me hid_sensor_iio_common industrialio ucsi_acpi mei hid_multitouch processor_thermal_device intel_rapl_common cros_ec_ishtp typec_ucsi cros_ec intel_soc_dts_iosf typec soc_button_array int3403_thermal int340x_thermal_zone mac_hid int3400_thermal acpi_tad acpi_thermal_rel acpi_pad
[Bug 1919426] [NEW] WIFI card disappear when booting with an USB device plugged
Public bug reported: WIFI card disappear when booting with an USB device plugged. There is no WIFI connection anymore, not at all. If I go under System> Networks I get only Ethernet connections and ethernet device. Wifi card device is not even shown or recognized, it looks like I don't have even plugged in/installed. If you boot the laptop with an usb mouse for example this happens all the time. So I am forced to boot the laptop disconencting all the devices and then after I logged in, Wifi will be there working and only then I can connect my mouse or USB devices. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919426 Title: WIFI card disappear when booting with an USB device plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1919426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919174] Re: nvidia drivers will not load
*** This bug is a duplicate of bug 1919285 *** https://bugs.launchpad.net/bugs/1919285 ** This bug has been marked a duplicate of bug 1919285 Nvidia driver not loaded, resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919174 Title: nvidia drivers will not load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1919174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916554] Re: Cirrus Audio Codec CS8409/CS42L42 support
I copied comment #61 to bug 1918378 instead. Patches proposed in this bug is already in linux-next, so there is no reason to revise them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916554 Title: Cirrus Audio Codec CS8409/CS42L42 support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1916554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919248] Re: Nvidia driver never usable if Ubuntu was installed in safe graphics mode
Actually I suspect the problem here is kernel update 5.8.0-45.51 (which you would avoid briefly on a fresh reinstall). Please check to see if this is the same as bug 1919285 (meaning using an older kernel like 5.8.0-44 fixes it). ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919248 Title: Nvidia driver never usable if Ubuntu was installed in safe graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1919248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919285] Re: Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51~20.04.1-generic
** Summary changed: - Nvidia resolution is stuck at 640x480 since kernel 5.8.0-45.51~20.04.1-generic + Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51~20.04.1-generic ** Summary changed: - Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51~20.04.1-generic + Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 ** Tags added: groovy ** Summary changed: - Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 + Nvidia driver not loaded, resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919285 Title: Nvidia driver not loaded, resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919335] Re: FTBFS (test fail with sigbus) on armhf in Hirsute
** Changed in: netgen (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919335 Title: FTBFS (test fail with sigbus) on armhf in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/netgen/+bug/1919335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919407] Re: display bug, incorrect resolution
*** This bug is a duplicate of bug 1919285 *** https://bugs.launchpad.net/bugs/1919285 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1919285, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1919285 Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919407 Title: display bug, incorrect resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1919407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919412] Re: display, resolution bug
*** This bug is a duplicate of bug 1919285 *** https://bugs.launchpad.net/bugs/1919285 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1919285, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1919285 Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919412 Title: display, resolution bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1919412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899951] Re: Problemi nell'aggiornamento a Ubuntu 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899951 Title: Problemi nell'aggiornamento a Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918378] Re: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted
Copied from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916554/comments/61: Comments from CirrusLogic: " New set of patches have been accepted to ALSA upstream: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git branch for-next. Commits IDs are: ALSA: hda/cirrus: Make CS8409 driver more generic by using fixups. 9f8de3b7d789693008b65a4849bc444e81fcfe5a ALSA: hda/cirrus: Fix CS42L42 Headset Mic volume control name 61a9aba19f4482984dc7ec5c04c54bf51166cff2 ALSA: hda/cirrus: Cleanup patch_cirrus.c code. fb3447d5842b71ec960da1b8a3ca5ee5f46a5327 ALSA: hda/cirrus: Add error handling into CS8409 I2C functions " -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918378 Title: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919407] Re: display bug, incorrect resolution
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919407 Title: display bug, incorrect resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1919407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919412] Re: display, resolution bug
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919412 Title: display, resolution bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1919412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919420] Re: On s390x interactive subiquity from the 20.04.2 ISO crashes on keyboard selection screen breaking install
** Tags added: s390x subiquity ** Tags removed: subiquity ** Tags added: installer ** Package changed: linux (Ubuntu) => subiquity ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919420 Title: [Ubuntu 20.04] On s390x interactive subiquity from the 20.04.2 ISO crashes on keyboard selection screen breaking install To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1919420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Also affects: cloud-archive/victoria Importance: Undecided Status: New ** Changed in: cloud-archive/wallaby Status: New => Triaged ** Changed in: cloud-archive/victoria Status: New => Triaged ** Changed in: cloud-archive/ussuri Status: New => Triaged ** Changed in: cloud-archive/wallaby Status: Triaged => Fix Released ** Changed in: cloud-archive/victoria Importance: Undecided => High ** Changed in: cloud-archive/ussuri Importance: Undecided => High ** Changed in: cloud-archive/wallaby Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915829 Title: FQDN / hostname recorded in OVSDB is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916988] Re: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade
Problem persists on 5.8.0-45-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916988 Title: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919420] Installer Log
Default Comment by Bridge ** Attachment added: "Installer Log" https://bugs.launchpad.net/bugs/1919420/+attachment/5477502/+files/1615893588.260006905.ui.crash ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919420 Title: On s390x interactive subiquity from the 20.04.2 ISO crashes on keyboard selection screen breaking install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919420] [NEW] On s390x interactive subiquity from the 20.04.2 ISO crashes on keyboard selection screen breaking install
Public bug reported: I tried to install Ubuntu 20.04.2 from the ISO image "ubuntu-20.04.2 -live-server-s390x.iso" available at http://cdimage.ubuntu.com/ubuntu/releases/20.04.2/release/ on an LPAR. For this I used the "Load from ISO image" panel on the HMC with the "/ubuntu.ins" file. I then used the manual network config dialog to configure a qeth network device and loaded the ISO image from the URL: http://cdimage.ubuntu.com/ubuntu/releases/20.04.2/release/ubuntu-20.04.2-live-server-s390x.iso This all worked nicely (Thanks for bringing back the manual network configuration!) and gave me a subiquity installer available via "ssh installer@" as well as on the "Integrated ASCII Console". In the first installer step I chose "English" as the language, then the next step is the keyboard layout but there the installer immediately shows a "Sorry the installer encountered an internal error" dialog (both via SSH and the integrated ASCII console). The "Continue" button doesn't get me further and "Sent to Canonical" then completely crashes the installer (which at least restarts). I've used the same installation flow successfully with the Ubuntu 20.10 ISO image. So I don't think I'm doing something wrong. I also collected a the crash log which I've attached. I think the relevant part here might be the following: 2021-03-16 11:19:31,460 INFO subiquity:119 Arguments passed: ['/snap/subiquity/2278/usr/bin/subiquity'] 2021-03-16 11:19:31,460 DEBUG subiquitycore.screen:133 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device') 2021-03-16 11:19:31,461 DEBUG asyncio:54 Using selector: EpollSelector 2021-03-16 11:19:31,464 DEBUG subiquity.signals:50 connect_signal: l10n:language-selected -> KeyboardController.language_selected 2021-03-16 11:19:31,465 DEBUG subiquitycore.core:92 known signals: ['l10n:language-selected'] 2021-03-16 11:19:31,465 DEBUG subiquitycore.core:120 starting controllers 2021-03-16 11:19:31,465 DEBUG subiquitycore.core:123 controllers started 2021-03-16 11:19:31,465 DEBUG subiquitycore.screen:133 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device') 2021-03-16 11:19:31,466 DEBUG subiquity/Progress/_wait_status:107 start: 2021-03-16 11:19:31,467 INFO subiquity/Welcome:107 start: starting UI 2021-03-16 11:19:31,468 DEBUG subiquitycore.screen:133 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device') 2021-03-16 11:19:31,468 DEBUG subiquitycore.screen:133 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device') 2021-03-16 11:19:31,468 DEBUG subiquitycore.screen:133 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device') 2021-03-16 11:19:31,468 DEBUG subiquitycore.screen:133 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device') 2021-03-16 11:19:31,468 DEBUG subiquitycore.screen:133 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device') So I'm guessing the code is probing for a keyboard but we don't have any or even usb so something fails. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192018 severity-high targetmilestone-inin20042 ** Tags added: architecture-s39064 bugnameltc-192018 severity-high targetmilestone-inin20042 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919420 Title: On s390x interactive subiquity from the 20.04.2 ISO crashes on keyboard selection screen breaking install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919341] Re: kernel package linux-headers-5.11.0-11-generic is not supported
Solved by: xtables-addons-common: 3.13-1ubuntu2 xtables-addons-dkms: 3.13-1ubuntu2 Preparing to unpack .../xtables-addons-common_3.13-1ubuntu2_amd64.deb ... Unpacking xtables-addons-common (3.13-1ubuntu2) over (3.13-1) ... Preparing to unpack .../xtables-addons-dkms_3.13-1ubuntu2_all.deb ... ... Building initial module for 5.11.0-11-generic Done. xt_ACCOUNT.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ compat_xtables.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_pknock.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_CHAOS.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DELUDE.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DHCPMAC.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DNETMAP.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ECHO.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_IPMARK.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_LOGMARK.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_PROTO.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_SYSRQ.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_TARPIT.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_condition.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_fuzzy.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_geoip.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_iface.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ipp2p.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ipv4options.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_length2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_lscan.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_psd.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_quota2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ depmod DKMS:
[Bug 1919008] Re: 'Extract here' for .zip files not working as intended.
Here it is - ii libgnome-autoar-0-0:amd64 0.2.3-2ubuntu0.2 amd64Archives integration support for GNOME Does this mean it is already installed? I executed 'dpkg -s 0.2.3-2ubuntu0.2 | grep version' yesterday and it said - "dpkg-query: package '0.2.3-2ubuntu0.2' is not installed and no information is available" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919008 Title: 'Extract here' for .zip files not working as intended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1919008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable
** Description changed: + [ Impact ] + The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open- vSwitch` table in the local OVSDB. This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system. In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system. As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time. + Examples of downstream issues can be viewed in bug 1896630 and bug + 1912844 comment #26. + + [ Test Case ] + + 1) Use MAAS 2.9, configure a machine with Open vSwitch bridge for networking and deploy. + 2) Confirm that without the change the hostname recorded in Open vSwitch is `ubuntu`. + 3) Add a PPA with the updated Open vSwitch package to MAAS. + 4) Re-deploy and confirm that the hostname recorded in Open vSwitch matches the FQDN as provided by MAAS. + + [ Regression potential ] + + Minimal, the update uses the exact same methods to accomplish the end + result of recording the hostname as before, we have only re-ordered when + the events occur to ensure successful operation. + + [ Other Info ] + A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`. An example of downstream issues can be viewed in bug 1896630. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915829 Title: FQDN / hostname recorded in OVSDB is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1915829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919415] [NEW] No warning when sync and async both are missing
Public bug reported: In commit d7425178eb9c828ace36b80ec3871cd9e168ff4f, The xlog was removed from support/nfs/exports.c, but utils/exportfs/exports.man was notouched for this change. Please update the doc if it's intended. ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919415 Title: No warning when sync and async both are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1919415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
open-vm-tools fixed in open-vm-tools (2:11.2.5-2ubuntu1) hirsute; urgency=medium * d/p/fix-FTFBS-glib2.0-2.66.3.patch: fix FTBFS with glib2.0 >=2.66.3 -- Christian Ehrhardt Mon, 08 Mar 2021 12:12:35 +0100 ** Changed in: open-vm-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916705 Title: glib2.0 >=2.67.3 breaks include from an extern C context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919098] Re: Netplan not linked to networkmanager
~$ head -n5 /etc/apt/sources.list # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://nl.archive.ubuntu.com/ubuntu groovy main restricted # deb-src http://nl.archive.ubuntu.com/ubuntu groovy main restricted ~$ sudo cat /var/log/installer/media-info Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 (20201022) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919098 Title: Netplan not linked to networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1919098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable
** Merge proposal linked: https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/399763 ** Merge proposal linked: https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/399764 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915829 Title: FQDN / hostname recorded in OVSDB is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1915829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919098] Re: Netplan not linked to networkmanager
There is no installation image named "ubuntu-mate-server 20-10". What was exact name? You are right. it was late that day. almost midnight after finishing a 12 hour workday. it is the ubuntu-20.10-live-server-amd64.iso that i used to install. i may jumped to early to a conclusion based on a previus version of the ubuntu-mate-"version"-desktop-amd64.iso so i tested the ubuntu- mate-20.10-desktop-amd64.iso where it was solved. this may be not in the installer but the package named ubuntu-mate- desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919098 Title: Netplan not linked to networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1919098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919413] [NEW] Kolourpaint: x seconds Freeze on save and every keystroke
Public bug reported: Consequence of this bug: Unable to (properly) use save function of Kolourpaint Steps to reproduce: - Open Kolourpaint - Press Ctrl+S for saving it - Dialog opens - Expected: I can type in a name and save - Actual: Kolourpaint freezes for many seconds (10? 30?). Then I can press one or two letters, that are shown, then Kolourpaint freezes again for many seconds. Workaround: - Save the file in the default location under a random name (e.g. "a"), use the default image format. - Rename and convert in another program. lsb_release -rd Description:Ubuntu 20.10 Release:20.10 apt-cache policy kolourpaint kolourpaint: Installed: 4:20.08.1-0ubuntu1 Candidate: 4:20.08.1-0ubuntu1 Version table: *** 4:20.08.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: kolourpaint 4:20.08.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 17 15:47:52 2021 SourcePackage: kolourpaint UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kolourpaint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919413 Title: Kolourpaint: x seconds Freeze on save and every keystroke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kolourpaint/+bug/1919413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919412] [NEW] display, resolution bug
Public bug reported: Since last update the screen resolution is as it it was without graphic acceleration ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 17 02:25:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2872] InstallationDate: Installed on 2021-03-17 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=9215bf81-3d3a-4dd5-9a7c-acc1e8bf480e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4601:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXPLUS:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919412 Title: display, resolution bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1919412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919404] Re: Desktop icon shadows are broken at scale 200%
** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #119 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/119 ** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/119 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919404 Title: Desktop icon shadows are broken at scale 200% To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919408] Re: Xorg freeze
Thanks for the bug report. Firstly, you seem to have an AMD Radeon GPU, but the Nvidia driver is installed. Please uninstall the Nvidia driver in case that is causing problems. Secondly, next time a crash happens please: 1. Wait 10 seconds 2. Reboot 3. Run this command: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. Finally, please check the system for crashes by following all of the steps listed in: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919408 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1919408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918723] Re: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] subsystem [8086:0034]: iwlwifi crash when running a software AC
** Tags added: hwe-networking-wifi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918723 Title: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] subsystem [8086:0034]: iwlwifi crash when running a software AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
