[Bug 1947361] [NEW] 1930783
Public bug reported: for install ubuntu on the Acer nitro 5 515 55 78 arrive the problem loading x.509 certificate - 65 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 13:38:53 2021 InstallationDate: Installed on 2021-08-28 (47 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947361 Title: 1930783 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1947361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944752] Re: AER PCIe Bus Error for Asus X541UVK
Hi, I currently do not have access to a running linux system to compile and test the patch with, since the only pc that I have is my laptop affected by this bug, and I also really need windows on it for some windows-specific software for my university. So, It's not possible for me right now to test the patch. I'll leave some more specific info about my system (hoping that somebody else has the same exact machine) for anyone that is willing to test this (I'm copying this from System Information). System ModelX541UVK Processor Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz Adapter Description Intel(R) HD Graphics 620 Adapter Description NVIDIA GeForce 920MX BIOS Version/Date American Megatrends Inc. X541UVK.308, 30-Jan-18 Thanks to everyone for the help, I'll keep in touch. Riccardo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944752 Title: AER PCIe Bus Error for Asus X541UVK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944752] Re: AER PCIe Bus Error for Asus X541UVK
Ok great! If there is anything else I can do or try let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944752 Title: AER PCIe Bus Error for Asus X541UVK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
I just created the new bug report as suggested, here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944752] [NEW] AER PCIe Bus Error for Asus X541UVK
Public bug reported: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy- pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free to suggest and I'll try it and report the results. ** Affects: linux (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/1944752 Title: AER PCIe Bus Error for Asus X541UVK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same issue on my Dell 5520 When I REBOOT and the HDMI 2nd monitor is connected, splash screen freezes. _ Specs: Xubuntu 20.04 uname -r 5.8.0-59-generic lspci -vvv Graphics: :00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0a21 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 dmesg --level=err,warn [1.039745] Missing case (clock == 539440) [1.039795] WARNING: CPU: 3 PID: 193 at drivers/gpu/drm/i915/display/intel_dpll_mgr.c:2967 icl_calc_dpll_state.isra.0+0x21d/0x280 [i915] [1.039828] RIP: 0010:icl_calc_dpll_state.isra.0+0x21d/0x280 [i915] [1.039829] Code: 4c 63 c2 39 cf 74 55 48 83 c2 01 48 83 fa 08 75 e5 48 63 d7 48 c7 c6 ee b5 7f c0 48 c7 c7 e3 b4 7f c0 88 45 bf e8 ab 32 5e c8 <0f> 0b 0f b6 45 bf e9 ea fe ff ff 31 d2 be 54 00 60 00 e9 9b fe ff [1.039830] RSP: 0018:b460805eb6c8 EFLAGS: 00010282 [1.039830] RAX: RBX: a00c5795a490 RCX: 03bb [1.039831] RDX: 0001 RSI: 0086 RDI: 0247 [1.039831] RBP: b460805eb710 R08: 03bb R09: 0004 [1.039831] R10: R11: 0001 R12: a00c5795a000 [1.039832] R13: a00c5882 R14: a00c68dea800 R15: a00c5795c000 [1.039832] FS: 7f60162cc880() GS:a00c6f6c() knlGS: [1.039833] CS: 0010 DS: ES: CR0: 80050033 [1.039833] CR2: 7fff1750bec0 CR3: 00085902a002 CR4: 00760ee0 [1.039833] PKRU: 5554 [1.039834] Call Trace: [1.039857] icl_get_dplls+0x34b/0x840 [i915] [1.039870] ? drm_mode_object_get+0x2a/0x60 [drm] [1.039877] ? drm_connector_list_iter_next+0x8e/0xb0 [drm] [1.039898] intel_reserve_shared_dplls+0x24/0x60 [i915] [1.039920] hsw_crtc_compute_clock+0x5a/0x90 [i915] [1.039941] intel_atomic_check_crtcs+0x3ba/0x620 [i915] [1.039961] ? icl_put_dplls+0x6c/0xb0 [i915] [1.039980] intel_atomic_check+0xa22/0xb60 [i915] [1.039982] ? __kmalloc_track_caller+0x271/0x280 [1.040004] ? intel_crtc_duplicate_state+0x27/0xb0 [i915] [1.040011] drm_atomic_check_only+0x2c7/0x450 [drm] [1.040017] drm_atomic_commit+0x18/0x50 [drm] [1.040037] intel_modeset_init+0x456/0xae0 [i915] [1.040055] i915_driver_probe+0x275/0x500 [i915] [1.040058] ? _cond_resched+0x19/0x30 [1.040059] ? mutex_lock+0x13/0x40 [1.040077] i915_pci_probe+0x5a/0x140 [i915] [1.040080] local_pci_probe+0x48/0x80 [1.040081] pci_device_probe+0x10f/0x1b0 [1.040083] really_probe+0x159/0x3d0 [1.040084] driver_probe_device+0xe9/0x160 [1.040085] device_driver_attach+0x5d/0x70 [1.040086] __driver_attach+0x8f/0x150 [1.040087] ? device_driver_attach+0x70/0x70 [1.040087] bus_for_each_dev+0x7e/0xc0 [1.040088] driver_attach+0x1e/0x20 [1.040089] bus_add_driver+0x152/0x1f0 [1.040089] driver_register+0x74/0xd0 [1.040090] __pci_register_driver+0x54/0x60 [1.040109] i915_init+0x61/0x75 [i915] [1.040110] ? 0xc089 [1.040112] do_one_initcall+0x4a/0x200 [1.040113] ? vfree+0x2c/0x40 [1.040114] ? _cond_resched+0x19/0x30 [1.040115] ? kmem_cache_alloc_trace+0x1b0/0x240 [1.040116] do_init_module+0x62/0x250 [1.040117] load_module+0x1185/0x1390 [1.040119] ? ima_post_read_file+0x108/0x120 [1.040120] __do_sys_finit_module+0xc9/0x130 [1.040121] ? __do_sys_finit_module+0xc9/0x130 [1.040122] __x64_sys_finit_module+0x1a/0x20 [1.040123] do_syscall_64+0x49/0xc0 [1.040124] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1.040124] RIP: 0033:0x7f601684e89d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933751] [NEW] Installation crashes (not well recognized ssd disk)
Public bug reported: Ubuntu not recognize the partition table of my Sansung SSD 870EVO so installation stops on "unable to instal at mount point dev\sdc\ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckMismatches: ./dists/focal/main/binary-amd64/Packages.gz CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 27 07:44:38 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=it_IT.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933751 Title: Installation crashes (not well recognized ssd disk) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1933751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931031] [NEW] when i upgrade from version 18.04 to 20.04, an unsolvable problem occurred while calculating the progress, and the upgrade crashes
Public bug reported: when i upgrade from version 18.04 to 20.04, an unsolvable problem occurred while calculating the progress, and the upgrade crashes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Jun 6 18:57:22 2021 InstallationDate: Installed on 2018-01-29 (1223 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-06-06 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1931031 Title: when i upgrade from version 18.04 to 20.04, an unsolvable problem occurred while calculating the progress, and the upgrade crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272293] Re: [hardy] Key repeat gets randomly turned off.
This bug is still present in Ubuntu 20.04 LTS Desktop 64-bit, after 12 years. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/272293 Title: [hardy] Key repeat gets randomly turned off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/272293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Hello to all. I have the same problem, and this has affected me for a long time now. I described it in detail here, with output, videos, photos etc: https://ubuntuforums.org/showthread.php?t=2460318 I hope this adds useful information to draw attention to the bug in question. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
Hi, it seems the same problem, I removed the extra routing with the same workaround ip command and the traffic flows correctly. The upstream bug seems to be ignored, are there chances to be fixed? Regards Riccardo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1917887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
I agree that is a problem with Network Manager, maybe also affects different vpn besides OpenVPN; this same problem is present in CentOS 7 and 8. Which config do you need? I tried to draw the network scheme to help understanding my setup. Regards Riccardo ** Attachment added: "Network Scheme" https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1917887/+attachment/5475052/+files/Network%20Manager%20OpenVPN%20nested%20connections%20fail%20to%20setup%20routes%20correctly%20-%20bug%201917887%20-%201.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1917887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917887] [NEW] Network Manager OpenVPN nested connections fail to setup routes correctly
Public bug reported: Setup: Host lan: 192.168.0.238/24 Host Default gw: 192.168.0.1 ip route: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 Primary OpenVPN (check "Use this connection only for resources on its network"): server ip: public a.b.c.d OpenVPN Tunnel: 192.168.1.0/24 routes pushed: 192.168.100.0/24 First VPN works OK: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 Secondary OpenVPN (check "Use this connection only for resources on its network"): server ip: private 192.168.100.10 OpenVPN Tunnel: 192.168.20.0/24 routes pushed: 192.168.200.0/24 Second VPN Connect OK, routing table is wrong: default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is wrong, the openVPN#2 Gateway is not on the local lan Correct routing table using "sudo /usr/sbin/openvpn /path/to/config.openvpn" (same a Network Manager) default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 It seems that Network Manager add a wrong additional route not added by the openvpn bin: 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openvpn 2.4.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 12:44:39 2021 InstallationDate: Installed on 2021-02-19 (13 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - Network Manager OpenVPN nested connection fail to setup routes correctly + Network Manager OpenVPN nested connections fail to setup routes correctly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1917887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910594] [NEW] crash during the installation of Ubuntu 20.04 TLS
Public bug reported: I was installing ubuntu in dual boot with windows and it crashes during the final part of the installation process. I have a Acer Nitro 5 AN-515-44-RTF with an Nvidia GeForce 1600. I tried the installation in safe graphics mode, because it didn't let me in the normal mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Thu Jan 7 22:16:36 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910594 Title: crash during the installation of Ubuntu 20.04 TLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1910594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875845] Re: keyring cannot be unlocked if used fingerprint to login gnome session
I was about to submit this same bug... I can confirm that every time you login to your gnome session with a fingerprint you can't unlock your login keyring. It seems that the prompt asking for the password fails to appear. For example, opening seahorse and clicking "unlock" has no effect (the button becomes gray but no prompt is shown). When other software tries to access the keyring (which is still locked) no prompt is shown and the software (e.g. the browser) either gets stuck, hangs or crashes. The only workaround I found so far is to lock the session and then unlock it with the password. After that, clicking on "unlock" in seahorse will work. I guess that the password you just used to unlock the session is cached for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875845 Title: keyring cannot be unlocked if used fingerprint to login gnome session To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1875845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894403] [NEW] Rows (or columns) of pixels appear in the wrong place after rotation with jpegtran
Public bug reported: Images rotated with jpegtran have rows or columns of pixels in the wrong place. In particular: - When rotating by 90 degrees some columns of pixels from the left are moved to the right. - When rotating by 270 degrees some rows of pixels from the top are moved to the bottom. - When rotating by 180 degrees both of the issues mentioned above affect the output image. Note that the words "top", "bottom", "left" and "right" always refer to the image after the rotation. Steps to reproduce: 1. Download a random jpeg image (e.g. the Ubuntu logo) 2. Rotate it with jpegtran (e.g. by 90 degrees) 3. The image is now rotated Expected behavior: 4. Everything is in the right place Actual behavior: 4. Some rows and/or columns of pixels are in the wrong place (as explained above) Tested package version: 2.0.3-0ubuntu1.20.04.1 System release: Ubuntu 20.04.1 LTS ** Affects: libjpeg-turbo (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/1894403 Title: Rows (or columns) of pixels appear in the wrong place after rotation with jpegtran To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1894403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866619] Re: OverflowError when machine suspends and resumes after a longer while
any update on this? Seeing this basically every time we run dstat in the openstack CI an example: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_8cb/725794/6/check/ipa-tempest-bios-ipmi-direct-tinyipa-src/8cb049d/job-output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866619 Title: OverflowError when machine suspends and resumes after a longer while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1866619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888151] [NEW] Touchpad not detected in Obsidian N141ZU
Public bug reported: Touchpad not detected in Obsidian N141ZU after fresh install of Ubuntu 20.04. Touchpad does not show up in /proc/bus/input/devices (file attached). USB Mouse works correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo 1454 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 21:29:26 2020 InstallationDate: Installed on 2020-07-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: OBSIDIAN-PC N13_N140ZU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=bfa60060-8b72-4cea-a496-e88f2b99bdb7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: N13_N140ZU dmi.board.vendor: OBSIDIAN-PC dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OBSIDIAN-PC dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd12/21/2018:svnOBSIDIAN-PC:pnN13_N140ZU:pvrNotApplicable:rvnOBSIDIAN-PC:rnN13_N140ZU:rvrNotApplicable:cvnOBSIDIAN-PC:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N13_N140ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: OBSIDIAN-PC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1888151/+attachment/5394167/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888151 Title: Touchpad not detected in Obsidian N141ZU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] Re: Unable to remove disk metadata on vm
Hey Brian, I tested the new packages in our CI and I can confirm the original issues are both gone. This is a recent libvirt log file: https://1a06a6c5517c6a746e50-e807054499ce854694349e023b0ab289.ssl.cf5.rackcdn.com/716889/38/check/ironic-tempest-ipa-partition-uefi-pxe-grub2/a34d5b6/controller/logs/libvirt/libvirtd_log.txt I used the focal proposed repo: deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse universe Upgrade command: sudo apt-get -y upgrade libvirt-daemon-system libvirt-dev libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-system-systemd libvirt0 List of upgraded packages including dependencies with versions: liblzma5 amd64 5.2.4-1ubuntu1 libapt-pkg6.0 amd64 2.0.3 apt amd64 2.0.3 gir1.2-freedesktop amd64 1.64.1-1~ubuntu20.04.1 libgirepository-1.0-1 amd64 1.64.1-1~ubuntu20.04.1 gir1.2-glib-2.0 amd64 1.64.1-1~ubuntu20.04.1 xz-utils amd64 5.2.4-1ubuntu1 apt-transport-https all 2.0.3 busybox amd64 1:1.30.1-4ubuntu6.1 initramfs-tools-core all 0.136ubuntu6.1 initramfs-tools all 0.136ubuntu6.1 initramfs-tools-bin amd64 0.136ubuntu6.1 busybox-initramfs amd64 1:1.30.1-4ubuntu6.1 grub-efi-amd64-signed amd64 1.142.1+2.04-1ubuntu26 libproxy1v5 amd64 0.4.15-10ubuntu1 libvirt-dev amd64 6.0.0-0ubuntu8.1 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.1 libvirt-daemon-system amd64 6.0.0-0ubuntu8.1 libvirt-clients amd64 6.0.0-0ubuntu8.1 libvirt0 amd64 6.0.0-0ubuntu8.1 libvirt-daemon amd64 6.0.0-0ubuntu8.1 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.1 linux-libc-dev amd64 5.4.0-34.38 qemu amd64 1:4.2-3ubuntu6.2 qemu-utils amd64 1:4.2-3ubuntu6.2 qemu-system-common amd64 1:4.2-3ubuntu6.2 qemu-block-extra amd64 1:4.2-3ubuntu6.2 qemu-system-data all 1:4.2-3ubuntu6.2 qemu-kvm amd64 1:4.2-3ubuntu6.2 qemu-system-x86 amd64 1:4.2-3ubuntu6.2 qemu-system-arm amd64 1:4.2-3ubuntu6.2 qemu-system-mips amd64 1:4.2-3ubuntu6.2 qemu-system-ppc amd64 1:4.2-3ubuntu6.2 qemu-system-sparc amd64 1:4.2-3ubuntu6.2 qemu-system-s390x amd64 1:4.2-3ubuntu6.2 qemu-system-misc amd64 1:4.2-3ubuntu6.2 qemu-system amd64 1:4.2-3ubuntu6.2 rabbitmq-server all 3.8.2-0ubuntu1.1 I noticed another issue but I'm sure it was not introduced by the upgrades, it looks like no suitable block device to install an operating system can be found. I'm going to open a different bug for that as soon as I have more concrete info. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879325 Title: Unable to remove disk metadata on vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] Re: Unable to remove disk metadata on vm
Hi Christian, I ran a test in our CI with the packages: 2020-05-26 16:52:02.258571 | controller | Get:1 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-dev amd64 6.0.0-0ubuntu8.2~ppa1 [161 kB] 2020-05-26 16:52:02.486631 | controller | Get:2 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2~ppa1 [606 kB] 2020-05-26 16:52:02.806459 | controller | Get:3 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2~ppa1 [67.5 kB] 2020-05-26 16:52:03.206779 | controller | Get:4 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2~ppa1 [344 kB] 2020-05-26 16:52:03.473402 | controller | Get:5 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2~ppa1 [1,447 kB] 2020-05-26 16:52:03.857247 | controller | Get:6 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2~ppa1 [404 kB] 2020-05-26 16:52:04.151046 | controller | Get:7 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2~ppa1 [12.5 kB] The message "unable to remove disk metadata" is gone from the logs, but unfortunately I'm still seeing the same error as before in our app, so it's probably something else that is going sideways, I'll have to dig deeper on that. We're going from bionic to focal and there are more things that probably need to be changed/adjusted. I think this can be solved anyway as the original issue related to libvirt is gone. Thanks for the time spent and the help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879325 Title: Unable to remove disk metadata on vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] Re: Unable to remove disk metadata on vm
Hi Christian, thank you for your patience, I just finished testing the new package in our ci and unfortunately I'm still seeing the same message about disk metadata: 2020-05-22 09:21:40.896+: 96720: error : virProcessRunInFork:1159 : internal error: child reported (status=125): 2020-05-22 09:21:40.896+: 96720: warning : qemuBlockRemoveImageMetadata:2629 : Unable to remove disk metadata on vm node-0 from /var/lib/libvirt/images/node-0.qcow2 (disk target vda) Here you can find the complete libvirt logs: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_f9b/716889/29/check/ironic-tempest-ipa-partition-uefi-pxe-grub2/f9b3f6c/controller/logs/libvirt/libvirtd_log.txt These are the new installed packages: 2020-05-22 08:56:30.550878 | controller | Get:1 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-dev amd64 6.0.0-0ubuntu8.1 [161 kB] 2020-05-22 08:56:31.041548 | controller | Get:2 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.1 [605 kB] 2020-05-22 08:56:31.707272 | controller | Get:3 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.1 [67.5 kB] 2020-05-22 08:56:32.121898 | controller | Get:4 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.1 [344 kB] 2020-05-22 08:56:32.712179 | controller | Get:5 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.1 [1,445 kB] 2020-05-22 08:56:33.484721 | controller | Get:6 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.1 [404 kB] 2020-05-22 08:56:34.094783 | controller | Get:7 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.1 [12.5 kB] the libvirtd process has been restarted after the installation These are the complete job logs: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_f9b/716889/29/check/ironic-tempest-ipa-partition-uefi-pxe-grub2/f9b3f6c/job-output.txt Thank you again for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879325 Title: Unable to remove disk metadata on vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] Re: Unable to remove disk metadata on vm
Hi Christian, thanks for the quick answer and fix, I'll test that in our CI as soon as possible. What actually worries me is the message "unable to remove disk metadata", but I guess we'll have to wait for the CI jobs to complete to see if there was an improvement on the related error that we're seeing in our application, that is actually modifying the disk partitions. It might be a coincidence (the time stamps coincide) or hopefully it will help. I'll post an update as soon as I'm done testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879325 Title: Unable to remove disk metadata on vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] [NEW] Unable to remove disk metadata on vm
Public bug reported: We can reproduce this 100% in our CI (upstream Openstack Ironic) using Ubuntu 20.04 LTS Focal Fossa with libvirt 6.0.0 2020-05-15 10:05:50.626+: 96089: error : virSecurityManagerMoveImageMetadata:476 : this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata 2020-05-15 10:05:50.628+: 96089: error : virProcessRunInFork:1159 : internal error: child reported (status=125): this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata 2020-05-15 10:05:50.628+: 96089: warning : qemuBlockRemoveImageMetadata:2629 : Unable to remove disk metadata on vm node-0 from /var/lib/libvirt/images/node-0.qcow2 (disk target vda) complete libvirt logs: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_688/716889/26/check/ironic-tempest-ipa-partition-uefi-pxe-grub2/688814a/controller/logs/libvirt/libvirtd_log.txt This was filed upstream and fixed by: https://gitlab.com/libvirt/libvirt/-/commit/cc8c297e473afd55e5d8e35e18345d8df176059d ** Affects: libvirt (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/1879325 Title: Unable to remove disk metadata on vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
[Ubuntu 19.10] PhpStorm, snap installed, seems working well (eg. when I run a debug session it opens chromium and the launcher icons are well associated). When I open a link on Slack, also snap installed, the new window appears in the "all windows" section of the contextual menu of the Slack launcher icon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875672] Re: lubuntu 20.04 lts can't find touchpad
Okay, I enabled acpi, and now it works. I disabled it because with my laptop, asus x59gl, since lubuntu 12.04 I was forced to disable acpi or it couldn't complete the boot, so this time I did it again. Now it seems to work perfectly. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875672 Title: lubuntu 20.04 lts can't find touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875672] [NEW] lubuntu 20.04 lts can't find touchpad
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:15.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac6] (rev b1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:16.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) (prog-if 00 [Normal decode]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:17.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) (prog-if 00 [Normal decode]) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:18.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) (prog-if 00 [Normal decode]) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation MCP79 [GeForce 8200M G] [10de:086f] (rev b1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. MCP79 [GeForce 8200M G] [1043:16b2] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia 06:00.0 Network controller [0280]: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) [168c:002a] (rev 01) Subsystem: AzureWave AW-NE771 802.11bgn Wireless Mini PCIe Card [AR9281] [1a3b:1067] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath9k Kernel modules: ath9k ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo891 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:32:19 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 001 Device 003: ID 04f2:b012 Chicony Electronics Co., Ltd 1.3 MPixel UVC Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c247 Logitech, Inc. G100S Optical Gaming Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/8p, 12M |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M |__ Port 7: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: ASUSTeK Computer Inc. F5GL ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=82e68f82-5a5c-4093-ad48-c78dc165ebbc ro quiet splash acpi=off nomodeset vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F5GL dmi.board.vendor:
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
Hey Dann, thanks a lot for the thorough analysis, the reasoning makes sense. I'm just a bit sceptical because we use tinycore 9.x at the moment, with kernel 4.14, which includes the patch for the kernel panic you mentioned, it was just moved under drivers/firmware/efi/efi-bgrt.c, so I'm not sure that could be the explanation for the error. We're in the process of upgrading tinycore to 10.x which will bring in kernel 4.19, although I don't see any substantial changes in he efi-bgrt management. I wonder if there was a regression at some point, but it's unlikely. I'll let you know how it goes with tinycore 10.x, in the meantime if you have any other ideas or advice, please let me know. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
Hi, just wondering if we can provide any more info or help to be able to move forward with the investigation. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855731] [NEW] ClamAV Outpdated 0.101.4 -> 0.102.1
Public bug reported: Ubuntu eoan (all distributions seam to be affected) freshclam: Mon Dec 9 15:34:55 2019 -> ClamAV update process started at Mon Dec 9 15:34:55 2019 Mon Dec 9 15:34:55 2019 -> ^Your ClamAV installation is OUTDATED! Mon Dec 9 15:34:55 2019 -> ^Local version: 0.101.4 Recommended version: 0.102.1 Mon Dec 9 15:34:55 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav Mon Dec 9 15:34:55 2019 -> main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr) Mon Dec 9 15:34:55 2019 -> daily.cld is up to date (version: 25658, sigs: 2039116, f-level: 63, builder: raynman) Mon Dec 9 15:34:55 2019 -> bytecode.cld is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg) ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: clamav version ** Summary changed: - ClamAV Outpdated + ClamAV Outpdated 0.101.4 -> 0.102.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855731 Title: ClamAV Outpdated 0.101.4 -> 0.102.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1855731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855458] Re: cloud-init on Ubuntu 18.04 image does not run in VIO
Another workaround for people experiencing the same issue is to force the use of a config drive in OpenStack. This can be done without involving VIO admins in two ways: 1. Set property `img__config_drive` on the image to `mandatory`. 2. Pass option `--config-drive true` to `openstack server create`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855458 Title: cloud-init on Ubuntu 18.04 image does not run in VIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1855458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855458] Re: cloud-init on Ubuntu 18.04 image does not run in VIO
@ Scott thanks a lot, that is very useful! Do I understand correctly that `smbios.assetTag` is a property of the *flavor*? I cannot seem to find any image property with the same effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855458 Title: cloud-init on Ubuntu 18.04 image does not run in VIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1855458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855458] Re: cloud-init on Ubuntu 18.04 image does not run in VIO
> Looking at the output provided, all we can tell is that we're on
> VMWare, but no indication that it's OpenStack, so cloud-init can't
> reasonable expect to know that it should enable the OpenStack
> datasource.
Let me mention again that this bug was introduced in Ubuntu 18.04;
previous versions do not suffer from the same problem.
Also, if I modify the official cloud image and disable any datasource
*except* Ec2 (i.e., write `datasource_list: [ Ec2 ]` into
`/etc/cloud/cloud.cfg.d/90_dpkg.cfg`), then everything works fine.
So the issue is really `ds-identify` being too picky about when the
`Ec2` datasource is valid; from a cursory look, I can see that it just
checks if `/sys/hypervisor` contains some well-known AWS tag -- but
there are many cloud services which provide EC2-compatible metadata
(OpenNebula being another example), which would be skipped by this
logic!
> In the above dump of DMI data, is VMware Virtual Platform specific
> to VIO? and does VIO always expose metadata service?
This I do not know; I'm just a user, not a developer of the VIO
platform. But I don't see why probing for metadata sources should be
done only by looking at DMI information? EC2 metadata is handed out
by 169.254.169.254, if well-known locations for metadata are
available, then the EC2 datasource should be considered valid. (Other,
more specific, datasources can be probed earlier so they can be used
if found.)
This is a dump of the EC2 metadata that I can see from an instance in
VIO (same VM from whence the above files were extracted):
root@ubuntu:~# w3m -dump http://169.254.169.254/latest/meta-data/
ami-id
ami-launch-index
ami-manifest-path
block-device-mapping/
hostname
instance-action
instance-id
instance-type
local-hostname
local-ipv4
placement/
public-hostname
public-ipv4
public-keys/
reservation-id
security-groups
root@ubuntu:~# w3m -dump http://169.254.169.254/latest/meta-data/ami-id
ami-012a
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/ami-launch-index
0
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/ami-manifest-path
FIXME
root@ubuntu:~# w3m -dump http://169.254.169.254/latest/meta-data/hostname
test.novalocal
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/instance-action
none
root@ubuntu:~# w3m -dump http://169.254.169.254/latest/meta-data/instance-id
i-0793
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/instance-type
m1.small
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/local-hostname
test.novalocal
root@ubuntu:~# w3m -dump http://169.254.169.254/latest/meta-data/local-ipv4
172.31.33.70
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/public-hostname
test.novalocal
root@ubuntu:~# w3m -dump http://169.254.169.254/latest/meta-data/public-ipv4
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/reservation-id
r-0asb5l2b
root@ubuntu:~# w3m -dump
http://169.254.169.254/latest/meta-data/security-groups
default
Thanks,
Riccardo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855458
Title:
cloud-init on Ubuntu 18.04 image does not run in VIO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1855458/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855458] Re: cloud-init on Ubuntu 18.04 image does not run in VIO
I am providing here the additional information that were requested in https://bugs.launchpad.net/ubuntu/+source/open-vm- tools/+bug/1760776/comments/17 I'm attaching the collected cloud-init logs; here is the output of commands. The Linux kernel correctly determines the hypervisor is VMware (excerpt from `/var/log/syslog`): Dec 6 15:28:02 ubuntu kernel: [0.00] Linux version 4.15.0-72-generic (buildd@lcy01-amd64-026) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #81 -Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 (Ubuntu 4.15.0-72.81-generic 4.15.18) Dec 6 15:28:02 ubuntu kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS 0 ... Dec 6 15:28:02 ubuntu kernel: [0.00] DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 Dec 6 15:28:02 ubuntu kernel: [0.00] Hypervisor detected: VMware Dec 6 15:28:02 ubuntu kernel: [0.00] vmware: TSC freq read from hypervisor : 2399.999 MHz Dec 6 15:28:02 ubuntu kernel: [0.00] vmware: Host bus clock speed read from hypervisor : 6600 Hz Dec 6 15:28:02 ubuntu kernel: [0.00] vmware: using sched offset of 13058703528 ns Still, `/sys/hypervisor` is empty: root@ubuntu:~# sudo sh -c 'cd /sys/hypervisor && grep -r . *' grep: *: No such file or directory root@ubuntu:~# ls /sys/hypervisor/ -lA total 0 However, DMI info is there: root@ubuntu:~# sudo sh -c 'cd /sys/class/dmi/id && grep -r . *' bios_date:12/12/2018 bios_vendor:Phoenix Technologies LTD bios_version:6.00 board_name:440BX Desktop Reference Platform board_serial:None board_vendor:Intel Corporation board_version:None chassis_asset_tag:No Asset Tag chassis_serial:None chassis_type:1 chassis_vendor:No Enclosure chassis_version:N/A modalias:dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: power/runtime_active_time:0 power/runtime_active_kids:0 power/runtime_usage:0 power/runtime_status:unsupported grep: power/autosuspend_delay_ms: Input/output error power/async:disabled power/runtime_suspended_time:0 power/runtime_enabled:disabled power/control:auto product_name:VMware Virtual Platform product_serial:VMware-42 17 b1 e7 f5 b4 cf 93-5f 00 68 ae ca 46 eb 65 product_uuid:E7B11742-B4F5-93CF-5F00-68AECA46EB65 product_version:None sys_vendor:VMware, Inc. uevent:MODALIAS=dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: ** Attachment added: "Collected cloud-init logs" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1855458/+attachment/5310238/+files/cloud-init.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855458 Title: cloud-init on Ubuntu 18.04 image does not run in VIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1855458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855458] Re: cloud-init on Ubuntu 18.04 image does not run in VIO
>From the `ds-identify.log` file in the uploaded archive, one can see that `ds-identify` rejects the `Ec2` metadata source and disables `cloud-init`: Running on vmware but rpctool query returned 1: No value found is_ds_enabled(IBMCloud) = true. ec2 platform is 'Unknown'. No ds found [mode=search, notfound=disabled]. Disabled cloud-init [1] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855458 Title: cloud-init on Ubuntu 18.04 image does not run in VIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1855458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855458] [NEW] cloud-init on Ubuntu 18.04 image does not run in VIO
Public bug reported: When running the official Ubuntu 18.04 cloud image in VIO (VMware Integrated OpenStack, see [1]), data source `Ec2` is not detected as working so `cloud-init` does not run. As a result, it is impossible to log in or connect to the running image via SSH. In other words, VMs started from the official Ubuntu 18.04 images are unusable on VIO. Note that this issue was already identified as a problem with `ds- identify` (part of the `cloud-init` package) in comment #16 to bug 1760776 (see [2]): > VMWARE does not always use DatasourceOVF. When using OpenStack VIO > (Openstack on VMWARE) the ec2 datasource fallback is no longer being > used as of this more recent update. OpenStack VIO exposes user-data > on 169.254.169.254 but now we get a platform unknown However, the reply in comment #17 (see [3]) mentioned that a new bug should have been opened, which is what I'm doing now. This issue applies to the released images (e.g., https://cloud- images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg- amd64.vmdk) but also to the "daily build" images. I have also tried using different formats (VMDK, OVA, QCOW2 converted to VMDK with `qemu- img convert`) but all of them show the same issue. It does *not* apply to previous versions of Ubuntu (e.g., official cloud images of Ubuntu 16.04 boot fine). [1]: https://www.vmware.com/products/openstack.html [2]: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1760776/comments/16 [3]: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1760776/comments/17 ** Affects: open-vm-tools (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/1855458 Title: cloud-init on Ubuntu 18.04 image does not run in VIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1855458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
Hi Dann, I tried to narrow down where the failure happens and it seems it's between versions 0~20161202.7bbe0b3e-1 (Zesty) and 0~20170911.5dfba97c-1 (Aartful). Just to clarify, version 0~20161202.7bbe0b3e-1 (Zesty) seems working fine in my environment, while version 0~20170911.5dfba97c-1 (Aartful) starts giving kernel panic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
Hi Dann, I tried to narrow down where the failure happens and it seems it's between versions 0~20161202.7bbe0b3e-1 (Zesty) and 0~20170911.5dfba97c-1 (Aartful). Just to clarify, version 0~20161202.7bbe0b3e-1 (Zesty) seems working fine in my environment, while version 0~20170911.5dfba97c-1 (Aartful) starts giving kernel panic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
** Attachment added: "kernel_panic_console_log_ovmf_0~20180205.c0d9813c-2ubuntu0.1" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/530/+files/kernel_panic_console_log_ovmf_0~20180205.c0d9813c-2ubuntu0.1 ** Attachment removed: "console_log_node-0_no_ansi" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5249703/+files/console_log_node-0_no_ansi ** Attachment removed: "libvirt_xml_virtual-node-0" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5249704/+files/libvirt_xml_virtual-node-0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
** Attachment added: "success_console_log_ovmf_0~20160813.de74668f-2" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5306665/+files/success_console_log_ovmf_0~20160813.de74668f-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
** Attachment added: "libvirt_xml_virtual-node-0" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5306667/+files/libvirt_xml_virtual-node-0 ** Attachment removed: "bionic_e1000_ppa-ovmf.txt" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5265123/+files/bionic_e1000_ppa-ovmf.txt ** Attachment removed: "bionic_virtio_ppa-ovmf.txt" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5265124/+files/bionic_virtio_ppa-ovmf.txt ** Attachment removed: "bionic_virtio_xenial-ovmf.txt" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5265125/+files/bionic_virtio_xenial-ovmf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
Hi Dann, unfortunately I was diverged to other things and couldn't test again until now. I don't see your files anymore, but I did some more testing with packages up to eoan. I can confirm that the regression is between xenial and bionic versions: 0~20160813.de74668f-2 works (tested in bionic) 0~20180205.c0d9813c-2ubuntu0.1 does not work -> kernel panic (tested in bionic) ** Changed in: edk2 (Ubuntu) Status: Expired => Incomplete ** Changed in: edk2 (Ubuntu Bionic) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752207] Re: package redis-server 5:4.0.8-2 failed to install/upgrade: installed redis-server package post-installation script subprocess returned error exit status 1
Any chance the fix for this can be cherry-picked in bionic? https://github.com/antirez/redis/commit/afc4b36c1026a4fab0e6c50af09c6bd18adc17d5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752207 Title: package redis-server 5:4.0.8-2 failed to install/upgrade: installed redis-server package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1752207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
Hi Dann, Please find recent logs here: This is the correct output on bionic using virtio + ovmf package from xenial: http://logs.openstack.org/90/644590/8/gate/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/6232932/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-12:09:41_log.txt.gz Job on bionic using virtio + new package from your repo: http://logs.openstack.org/07/645507/10/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/d9a0a64/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-10:13:23_log.txt.gz Job on bionic using e1000 + new package from your repo: http://logs.openstack.org/38/648938/5/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/90c5126/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-10:08:08_log.txt.gz Please let me know if you need any more info or details. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826043] [NEW] Events spanning multiple days are displayed on the wrong day in week view
Public bug reported: In gnome-calendar week view, events spanning multiple days are shown in the wrong day. Also, the event is shown in only one day (ending at midnight). Steps to reproduce: 1. Add an event starting on Monday at 21:00 and ending on Tuesday at 06:00. 2. Switch to week view. Expected behavior: The event should be shown both on Monday and on Tuesday. In particular should be 21:00->midnight on Monday and midnight->06:00 on Tuesday. Actual behavior: 1. The event is shown on the wrong day (Wednesday). 2. The event is shown only in one day (only the part 21:00->midnight is shown) Package version: 3.28.2-0ubuntu0.18.04.1 OS version: Ubuntu 18.04.2 LTS ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Description changed: - In gnome-calendar week view events spanning multiple days are shown in + In gnome-calendar week view, events spanning multiple days are shown in the wrong day. Also, the event is shown in only one day (ending at midnight). Steps to reproduce: - 1. Add an event starting on Monday at 21:00 and ending on Tuesday at 06:00. - 2. Switch to week view. + 1. Add an event starting on Monday at 21:00 and ending on Tuesday at 06:00. + 2. Switch to week view. Expected behavior: The event should be shown both on Monday and on Tuesday. In particular should be 21:00->midnight on Monday and midnight->06:00 on Tuesday. Actual behavior: - 1. The event is shown on the wrong day (Wednesday). - 2. The event is shown only in one day (only the part 21:00->midnight is shown) + 1. The event is shown on the wrong day (Wednesday). + 2. The event is shown only in one day (only the part 21:00->midnight is shown) Package version: 3.28.2-0ubuntu0.18.04.1 OS version: Ubuntu 18.04.2 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826043 Title: Events spanning multiple days are displayed on the wrong day in week view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1826043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
@Dann: thanks for keep looking at this, I tested the new package both locally and in our CI, using virtio and e1000 drivers, but unfortunately I'm still seeing the issue where the vm can't load from ipxe. The only thing that we change for the test is the ovmf package, the rest of the configuration is exactly the same. I'm quite puzzled at this point seeing that you were actually able to correctly load from ipxe, in my case it seems the vm hangs before getting an ip during the pxeboot phase. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
@Dann: what I'm saying is that I can't reproduce the kernel panic after installing a PPA build because it doesn't load from ipxe anymore. I can't confirm or deny the issue with the kernel panic is actually fixed. If you prefer I can open another bug, although it seems a regression to me, but of course a different issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
@Dann: thanks for checking that, I did some tests and, even if I can't reproduce the kernel panic anymore, I'm seeing another issue that was also happening before with virtio, the vm is not booting on ipxe. This is the correct output on bionic using virtio + ovmf from xenial: http://logs.openstack.org/87/647687/5/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/a16650a/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-03-27-14:18:35_log.txt.gz This is a test done with virtio and the new package on bionic: http://logs.openstack.org/07/645507/7/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/2660087/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-04-01-09:57:23_log.txt.gz This is the output changing the driver to e1000 and using the default rom on bionic: http://logs.openstack.org/38/648938/1/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/c943520/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-04-01-11:01:55_log.txt.gz This is the output using e1000 driver using the rom from ipxe-qemu on bionic: http://logs.openstack.org/38/648938/2/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/1c53407/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-04-01-13:15:39_log.txt.gz I reproduced all the tests locally to confirm, also changing ipxe-qemu from bionic to xenial to understand if it was a regression in that package, but it didn't work, so I think this is another problem in recent versions of ovmf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
console log attached ** Attachment added: "console_log_node-0_no_ansi" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5249703/+files/console_log_node-0_no_ansi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] Re: UEFI in ovmf package causes kernel panic
libvirt xml of virtual node attached ** Attachment added: "libvirt_xml_virtual-node-0" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5249704/+files/libvirt_xml_virtual-node-0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)
After looking a bit more into this, it seems the issue in https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html is maybe not a real security concern, since rbash was wrongly configured. Having . in PATH is not good with rbash and that makes the whole thing flawed. So, we could say CVE-2019-9924 is just for the issue in https://lists.gnu.org/archive/html/bug-bash/2017-03/msg00077.html . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1803441 Title: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)
I don't think they are the same issue. Or, at least, the first issue was only partially fixed. I can see both Fedora 29 and Ubuntu 18.10 being still affected by the issue outlined in https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html, though they are not affected by https://lists.gnu.org/archive/html/bug- bash/2017-03/msg00077.html. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1803441 Title: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)
Is this about https://lists.gnu.org/archive/html/bug- bash/2017-03/msg00077.html ? Or about https://lists.gnu.org/archive/html /bug-bash/2017-12/msg00065.html ? Apparently, both are very old flaws. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1803441 Title: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821729] [NEW] UEFI in ovmf package causes kernel panic
Public bug reported: UBUNTU info Description:Ubuntu 18.04.1 LTS Release:18.04 PACKAGE info ovmf: Installed: 0~20180205.c0d9813c-2 Candidate: 0~20180205.c0d9813c-2 Version table: *** 0~20180205.c0d9813c-2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Expected: Virtual machines loading from the UEFI provided by the ovmf package should work fine. This is working correctly in Ubuntu Xenial with ovmf package 0~20160408.ffea0a2c-2 that provides EFI v2.60 by EDK II. What happens: Virtual machines loading from the UEFI crash with kernel panic. Provided UEFI version: EFI v2.70 by EDK II. To be able to correctly boot up a VM on bionic, we downgraded the package. Here's an example from a succesfull automated devstack job: https://review.openstack.org/647687 -> ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa ** Affects: edk2 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic edk2 ovmf qemu ubuntu uefi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805083] [NEW] package nova-common 2:13.1.4-0ubuntu4.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: package nova-common 2:13.1.4-0ubuntu4.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nova-common 2:13.1.4-0ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Nov 26 08:12:59 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-08-29 (453 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: nova Title: package nova-common 2:13.1.4-0ubuntu4.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805083 Title: package nova-common 2:13.1.4-0ubuntu4.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1805083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802269] [NEW] script `lmod.sh` in `/etc/profile.d` errors out and dumps stack trace
Public bug reported: I have just run `apt install lmod` on my Ubuntu 18.04 system. Now, starting a login shell results in the following Lua stack trace being dumped: $ exec bash -l [10:21:53] /usr/bin/lua: /usr/share/lua/5.2/posix/init.lua:29: module 'posix.ctype' not found: no field package.preload['posix.ctype'] no file '/usr/local/share/lua/5.2/posix/ctype.lua' no file '/usr/local/share/lua/5.2/posix/ctype/init.lua' no file '/usr/local/lib/lua/5.2/posix/ctype.lua' no file '/usr/local/lib/lua/5.2/posix/ctype/init.lua' no file '/usr/share/lua/5.2/posix/ctype.lua' no file '/usr/share/lua/5.2/posix/ctype/init.lua' no file './posix/ctype.lua' no file '/usr/local/lib/lua/5.2/posix/ctype.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix/ctype.so' no file '/usr/lib/lua/5.2/posix/ctype.so' no file '/usr/local/lib/lua/5.2/loadall.so' no file './posix/ctype.so' no file '/usr/local/lib/lua/5.2/posix.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix.so' no file '/usr/lib/lua/5.2/posix.so' no file '/usr/local/lib/lua/5.2/loadall.so' no file './posix.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.2/posix/init.lua:29: in main chunk [C]: in function 'require' /usr/share/lmod/lmod/libexec/addto:64: in main chunk [C]: in ? There are no custom "profile.d" scripts:: $ ls -l /etc/profile.d/ totale 40 -rw-r--r-- 1 root root 96 ago 20 01:44 01-locale-fix.sh -rw-r--r-- 1 root root 825 lug 19 12:05 apps-bin-path.sh -rw-r--r-- 1 root root 664 apr 2 2018 bash_completion.sh -rw-r--r-- 1 root root 1003 dic 29 2015 cedilla-portuguese.sh -rw-r--r-- 1 root root 652 ott 4 2017 input-method-config.sh -rwxr-xr-x 1 root root 2284 dic 22 2016 lmod.sh -rw-r--r-- 1 root root 108 set 12 2017 sysstat.sh -rw-r--r-- 1 root root 1941 ott 3 2017 vte-2.91.sh -rw-r--r-- 1 root root 954 apr 19 2018 xdg_dirs_desktop_session.sh -rw-r--r-- 1 root root 1557 ago 18 2017 Z97-byobu.sh This is the state of Lua packages on my system: $ dpkg-query -l 'lua*' Voluto=U (non noto)/I (installato)/R (rimosso)/P (rimosso totale)/H (in attesa) | Stato=Non/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(nessuno)/R (reinstallazione richiesta) (Stato,Err: maiuscolo=grave) ||/ Nome Versione ArchitetturaDescrizione +++-=-===-===-=== un lua (nessuna descrizione disponibile) ii lua-bit32:amd64 5.3.0-3 amd64 Backport of the Lua 5.2 bit32 library to Lua 5.1 ii lua-filesystem:amd64 1.6.3-1 amd64 luafilesystem library for the Lua language ii lua-json 1.3.3-2 all JSON decoder/encoder for Lua ii lua-lpeg:amd641.0.0-2 amd64 LPeg library for the Lua language ii lua-posix:amd64 33.4.0-2amd64 posix library for the Lua language ii lua-term 0.07-0.1amd64 Lua module for manipulating a terminal un lua5.1-bit32 (nessuna descrizione disponibile) un lua5.1-filesystem (nessuna descrizione disponibile) un lua5.1-json (nessuna descrizione disponibile) un lua5.1-lpeg (nessuna descrizione disponibile) un lua5.1-posix (nessuna descrizione disponibile) un lua5.1-term (nessuna descrizione disponibile) ii lua5.25.2.4-1.1build1 amd64 Simple, extensible, embeddable programming language un lua5.2-filesystem (nessuna descrizione disponibile) un lua5.2-json (nessuna descrizione disponibile) un lua5.2-lpeg
[Bug 1791523] [NEW] Samsung R522 upgrade 18.04
Public bug reported: Grafica 3d not working and slow ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 9 16:57:29 2018 DistUpgraded: 2018-09-01 19:02:40,956 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4330/4350/4550] [1002:9552] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD 4330/4350/4550] [144d:c050] InstallationDate: Installed on 2016-11-26 (651 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. R520/R522/R620 ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=31bdb755-2e2f-4809-a60f-be47f49c9484 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-01 (7 days ago) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05LL.M025.20090916.Jay dmi.board.name: R520/R522/R620 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable 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:bvnPhoenixTechnologiesLtd.:bvr05LL.M025.20090916.Jay:bd09/16/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR520/R522/R620:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR520/R522/R620:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R520/R522/R620 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Sep 1 15:19:01 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791523 Title: Samsung R522 upgrade 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1791523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785731] Re: Linux Mint 19
kernel-fixed-upstream ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Riccardo Casa (rikmac) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785731 Title: Linux Mint 19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1785731] Re: Linux Mint 19
ok, I try that wen I go home from work and let you know. tnx. Il mar 7 ago 2018, 11:11 AM Joseph Salisbury ha scritto: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.18 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1785731 > > Title: > Linux Mint 19 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Last kernel update 4.15.0-30 > CPU1 idle after kernel update. > > System:Host: iw5dgq-K53SC Kernel: 4.15.0-30-generic x86_64 bits: 64 > gcc: 7.3.0 > Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm > Distro: Linux Mint 19 Tara > Machine: Device: laptop System: ASUSTeK product: K53SC v: 1.0 serial: > N/A > Mobo: ASUSTeK model: K53SC v: 1.0 serial: N/A > BIOS: American Megatrends v: K53SC.204 date: 05/30/2011 > BatteryBAT0: charge: 48.9 Wh 96.7% condition: 50.6/56.2 Wh (90%) > volts: 12.4/10.8 > model: [MKF_CUSTOMER] [MKF_BASEBOARD_ID] serial: N/A status: > N/A > CPU: Dual core Intel Core i5-2410M (-MT-MCP-) arch: Sandy Bridge > rev.7 cache: 3072 KB > flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: > 9179 > clock speeds: min/max: 800/2900 MHz 1: 2693 MHz 2: 2694 MHz > 3: 2693 MHz 4: 2694 MHz > Graphics: Card-1: Intel 2nd Generation Core Integrated Graphics > Controller > bus-ID: 00:02.0 chip-ID: 8086:0116 > Card-2: NVIDIA GF119M [GeForce GT 520MX] bus-ID: 01:00.0 > chip-ID: 10de:1051 > Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting > (unloaded: fbdev,vesa) > Resolution: 1366x768@60.00hz > OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile > version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes > Audio: Card Intel 6 Series/C200 Series Family High Def. Audio > Controller > driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20 > Sound: Advanced Linux Sound Architecture v: k4.15.0-30-generic > Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter > (PCI-Express) > driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:002b > IF: wlp3s0 state: up mac: > Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet > Controller > driver: r8169 v: 2.3LK-NAPI port: 9000 bus-ID: 05:00.0 > chip-ID: 10ec:8168 > IF: enp5s0 state: down mac: > Drives:HDD Total Size: 240.1GB (17.9% used) > ID-1: /dev/sda model: KINGSTON_SV300S3 size: 240.1GB serial: > > Partition: ID-1: / size: 220G used: 41G (20%) fs: ext4 dev: /dev/sda1 > RAID: System: supported: N/A > No RAID devices: /proc/mdstat, md_mod kernel module present > Unused Devices: none > Sensors: System Temperatures: cpu: 84.0C mobo: N/A > Fan Speeds (in rpm): cpu: N/A > Repos: Active apt sources in file: > /etc/apt/sources.list.d/google-chrome.list > deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ > stable main > Active apt sources in file: > /etc/apt/sources.list.d/official-package-repositories.list > deb http: //mirrors.evowise.com/linuxmint/packages tara main > upstream import backport > deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic main > restricted universe multiverse > deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-updates > main restricted universe multiverse > deb http: //mirror.csclub.uwaterloo.ca/ubuntu > bionic-backports main restricted universe multiverse > deb http: //security.ubuntu.com/ubuntu/ bionic-security main > restricted universe multiverse > deb http: //archive.canonical.com/ubuntu/ bionic partner > Info: Processes: 210 Uptime: 2:20 Memory: 1566.4/7885.5MB > Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0 Client: > Unknown python3.6 client inxi: 2.3.56 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785731/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785731 Title: Linux Mint 19 To manage notifications about this bug go to:
[Bug 1785731] [NEW] Linux Mint 19
Public bug reported: Last kernel update 4.15.0-30 CPU1 idle after kernel update. System:Host: iw5dgq-K53SC Kernel: 4.15.0-30-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm Distro: Linux Mint 19 Tara Machine: Device: laptop System: ASUSTeK product: K53SC v: 1.0 serial: N/A Mobo: ASUSTeK model: K53SC v: 1.0 serial: N/A BIOS: American Megatrends v: K53SC.204 date: 05/30/2011 BatteryBAT0: charge: 48.9 Wh 96.7% condition: 50.6/56.2 Wh (90%) volts: 12.4/10.8 model: [MKF_CUSTOMER] [MKF_BASEBOARD_ID] serial: N/A status: N/A CPU: Dual core Intel Core i5-2410M (-MT-MCP-) arch: Sandy Bridge rev.7 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9179 clock speeds: min/max: 800/2900 MHz 1: 2693 MHz 2: 2694 MHz 3: 2693 MHz 4: 2694 MHz Graphics: Card-1: Intel 2nd Generation Core Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0116 Card-2: NVIDIA GF119M [GeForce GT 520MX] bus-ID: 01:00.0 chip-ID: 10de:1051 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes Audio: Card Intel 6 Series/C200 Series Family High Def. Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20 Sound: Advanced Linux Sound Architecture v: k4.15.0-30-generic Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:002b IF: wlp3s0 state: up mac: Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: 9000 bus-ID: 05:00.0 chip-ID: 10ec:8168 IF: enp5s0 state: down mac: Drives:HDD Total Size: 240.1GB (17.9% used) ID-1: /dev/sda model: KINGSTON_SV300S3 size: 240.1GB serial: Partition: ID-1: / size: 220G used: 41G (20%) fs: ext4 dev: /dev/sda1 RAID: System: supported: N/A No RAID devices: /proc/mdstat, md_mod kernel module present Unused Devices: none Sensors: System Temperatures: cpu: 84.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Repos: Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list deb http: //mirrors.evowise.com/linuxmint/packages tara main upstream import backport deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-updates main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-backports main restricted universe multiverse deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http: //archive.canonical.com/ubuntu/ bionic partner Info: Processes: 210 Uptime: 2:20 Memory: 1566.4/7885.5MB Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0 Client: Unknown python3.6 client inxi: 2.3.56 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic ** Attachment added: "sistem monitor." https://bugs.launchpad.net/bugs/1785731/+attachment/5172357/+files/Schermata%20del%202018-08-06%2021-07-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785731 Title: Linux Mint 19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664935] Re: VirtualBox crashed with SIGABRT in qt_message_fatal()
@see https://askubuntu.com/questions/1044292/virtualbox-will-not- install-on-fresh-copy-of-ubuntu-18-04 The suggested fix worked 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/1664935 Title: VirtualBox crashed with SIGABRT in qt_message_fatal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1664935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673406] Re: VirtualBox crashed with SIGABRT in QMessageLogger::fatal()
*** This bug is a duplicate of bug 1664935 *** https://bugs.launchpad.net/bugs/1664935 @see https://askubuntu.com/questions/1044292/virtualbox-will-not- install-on-fresh-copy-of-ubuntu-18-04 The suggested fix worked 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/1673406 Title: VirtualBox crashed with SIGABRT in QMessageLogger::fatal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1673406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785052] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: The error appeared on reboot after update from 16.04 to 18.04 During the version update something went wrong. A message about systemd-sysv 237-3ubuntu10.3 appeared, with the additional info that the system could be instable and that the tool will run a "dpkgsomethingelse -a". I launched the update software and i see a notification that asserts that is not possible to install all updates and invite to run a partial update. Partial version update -> 1 package is going to be removed -> systemd-shim - shim for systemd Then: Could not install 'systemd-shim' The upgrade will continue but the 'systemd-shim' package may not be in a working state. Please consider submitting a bug report about it. installed systemd-shim package post-removal script subprocess returned error exit status 2 FIX THAT WORKED FOR ME: -- cd /usr/share/dbus-1/system-services/ sudo mv org.freedesktop.systemd1.service org.freedesktop.systemd1.service.bak Then Run Update -> Run Partial Upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 2 11:21:11 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-11-09 (1726 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-02 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic 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/1785052 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
Same issue on a Dell XPS 9360 The issue seems to happen during or at the end of the files copying procedure as the partitions are correctly setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763484] [NEW] package mysql-common (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2
Public bug reported: this error is persistent. I want uninstall mysql ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-common (not installed) ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Mar 7 03:47:23 2018 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 InstallationDate: Installed on 2017-04-30 (346 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: mysql-5.7 Title: package mysql-common (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763484 Title: package mysql-common (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1763484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757115] [NEW] package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: idk what to do ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Mar 14 15:00:04 2018 Df: Dmesg: ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2017-04-05 (348 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to artful on 2017-10-22 (148 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757115 Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1757115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991688] iPhone X (64 GB)
*** This bug is a duplicate of bug 892506 *** https://bugs.launchpad.net/bugs/892506 ** Attachment added: "F2F8F66DDCF37A65.jpg" https://bugs.launchpad.net/bugs/991688/+attachment/5021600/+files/F2F8F66DDCF37A65.jpg ** Attachment added: "F2F8F66DDCF37A652.jpg" https://bugs.launchpad.net/bugs/991688/+attachment/5021601/+files/F2F8F66DDCF37A652.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991688 Title: virtualbox-dkms 4.1.2-dfsg-1ubuntu1: virtualbox kernel module failed to build [error: implicit declaration of function ‘iommu_found’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/991688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736850] [NEW] package mariadb-server-10.0 10.0.31-0ubuntu0.16.04.2 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Public bug reported: Non conosco l'errore ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mariadb-server-10.0 10.0.31-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 5 20:56:41 2017 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2017-04-30 (220 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['debian-10.0.flag', 'ib_logfile1', 'multi-master.info', 'mysql', 'performance_schema', 'ibdata1', 'phpmyadmin', 'aria_log.0001', 'ib_logfile0', 'aria_log_control'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=747d65b6-9351-443c-9a51-062f9f48a825 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: mariadb-10.0 Title: package mariadb-server-10.0 10.0.31-0ubuntu0.16.04.2 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.mysql.debian-start: [deleted] ** Affects: mariadb-10.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736850 Title: package mariadb-server-10.0 10.0.31-0ubuntu0.16.04.2 failed to install/upgrade: il sottoprocesso installato script di post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1736850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892506] ✉yay! interesting stuff
Hello friend, Look at that products I've just found! It is so interesting, you'll definitely love that)) Check this out http://www.86region.com/differ.php?UE84OTI1MDZAYnVncy5sYXVuY2hwYWQubmV0 Warmest, Riccardo Contri -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892506 Title: [Precise] virtualbox-dkms 4.1.4-dfsg-1: virtualbox kernel module failed to build (erreur: implicit declaration of function ‘iommu_found’) To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/892506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707947] Re: Profile is currently in use].
** Attachment added: "Screen Shot 2017-08-01 at 23.25.47.png" https://bugs.launchpad.net/ubuntu/+source/nova-lxd/+bug/1707947/+attachment/4925531/+files/Screen%20Shot%202017-08-01%20at%2023.25.47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707947 Title: Profile is currently in use]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova-lxd/+bug/1707947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707947] [NEW] Profile is currently in use].
Public bug reported: During the task to create a new instance I've received this issue https://cdn.pbrd.co/images/GCftcIX.png someone can me help and say me why? thanks ** Affects: nova-lxd (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/1707947 Title: Profile is currently in use]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova-lxd/+bug/1707947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701831] Re: packaudo sge libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente
i think this solved part of my problem but now when i try to compile with the gcc appears this error message: esercizio_matrice: nella funzione "_fini": (.fini+0x0): definizione multipla di "_fini" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o:(.fini+0x0): definito qui per la prima volta esercizio_matrice: nella funzione "data_start": (.data+0x0): definizione multipla di "__data_start" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crt1.o:(.data+0x0): definito qui per la prima volta esercizio_matrice: nella funzione "data_start": (.data+0x8): definizione multipla di "__dso_handle" /usr/lib/gcc/x86_64-linux-gnu/5/crtbegin.o:(.data+0x0): definito qui per la prima volta esercizio_matrice:(.rodata+0x0): definizione multipla di "_IO_stdin_used" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crt1.o:(.rodata.cst4+0x0): definito qui per la prima volta esercizio_matrice: nella funzione "_start": (.text+0x0): definizione multipla di "_start" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crt1.o:(.text+0x0): definito qui per la prima volta esercizio_matrice: nella funzione "_init": (.init+0x0): definizione multipla di "_init" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o:(.init+0x0): definito qui per la prima volta /usr/lib/gcc/x86_64-linux-gnu/5/crtend.o:(.tm_clone_table+0x0): definizione multipla di "__TMC_END__" esercizio_matrice:(.data+0x10): definito qui per la prima volta /usr/bin/ld: error in esercizio_matrice(.eh_frame); no .eh_frame_hdr table will be created. collect2: error: ld returned 1 exit status (in my other machine it compile) and before this it compiled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701831 Title: packaudo sge libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1701831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701831] [NEW] packaudo sge libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovament
Public bug reported: my release of ubuntu: Description:Ubuntu 16.04.2 LTS Release:16.04 i think this bug is correlated with this other bug: dpkg: errore nell'elaborare il pacchetto libldap-2.4-2:amd64 (--configure): il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Segnalazione apport non scritta poiché il messaggio di errore indica la presenza di un fallimento precedente. Segnalazione apport non scritta poiché il messaggio di errore indica la presenza di un fallimento precedente. Segnalazione apport non scritta poiché è stato raggiunto il valore massimo di MaxReports Segnalazione apport non scritta poiché è stato raggiunto il valore massimo di MaxReports dpkg: problemi con le dipendenze impediscono la configurazione di libaprutil1-ldap:amd64: libaprutil1-ldap:amd64 dipende da libldap-2.4-2 (>= 2.4.7); comunque: Il pacchetto libldap-2.4-2:amd64 non è ancora configurato. dpkg: errore nell'elaborare il pacchetto libaprutil1-ldap:amd64 (--configure): problemi con le dipendenze - lasciato non configurato dpkg: problemi con le dipendenze impediscono la configurazione di apache2-bin: apache2-bin dipende da libaprutil1-ldap; comunque: Il pacchetto libaprutil1-ldap:amd64 non è ancora configurato. apache2-bin dipende da libldap-2.4-2 (>= 2.4.7); comunque: Il pacchetto libldap-2.4-2:amd64 non è ancora configurato. dpkg: errore nell'elaborare il pacchetto apache2-bin (--configure): problemi con le dipendenze - lasciato non configurato dpkg: problemi con le dipendenze impediscono la configurazione di apache2: apache2 dipende da apache2-bin (= 2.4.18-2ubuntu3.3); comunque: Il pacchetto apache2-bin non è ancora configurato. dpkg: errore nell'elaborare il pacchetto apache2 (--configure): problemi con le dipendenze - lasciato non configurato dpkg: problemi con le dipendenze impediscono la configurazione di cups-browsed: cups-browsed dipende da libldap-2.4-2 (>= 2.4.7); comunque: Il pacchetto libldap-2.4-2:amd64 non è ancora configurato. dpkg: errore nell'elaborare il pacchetto cups-browsed (--configure): problemi con le dipendenze - lasciato non configurato Si sono verificati degli errori nell'elaborazione: libldap-2.4-2:amd64 libaprutil1-ldap:amd64 apache2-bin apache2 cups-browsed E: Sub-process /usr/bin/dpkg returned an error code (1) this other bug or something like this appears everytime i try to do an installation from the terminal or an upgrade. searching on internet and on askubuntu i try every possible commands given as solution but noone of these solved my problem. the other way is reformatting, but if you can help me with some solution i would be grateful. the lenguage in the errorcode is italian ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sat Jul 1 15:13:58 2017 ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2016-10-21 (253 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openldap Title: package libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701831 Title: packaudo sge libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1701831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700376] [NEW] package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I was trying to install NVIDIA binary driver ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700376 Title: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1700376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589240] Re: Gnome on-screen keyboard doesn't appear when a text field is focused
Tested the new package from -proposed and fixes the bug. Package version: 3.18.5-0ubuntu0.3. Release: xenial (Ubuntu Gnome 16.04.2). I'll restore "verification-needed" tag for other releases. ** Tags removed: verification-done ** Tags added: verification-done-xenial verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589240 Title: Gnome on-screen keyboard doesn't appear when a text field is focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1589240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589240] Re: Gnome on-screen keyboard doesn't appear when a text field is focused
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589240 Title: Gnome on-screen keyboard doesn't appear when a text field is focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1589240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991688] ☀helpful info
*** This bug is a duplicate of bug 892506 *** https://bugs.launchpad.net/bugs/892506 Hello, Look what I've just found for you, you'll be surprised, more info here http://story.dailymailserver.com Wishes, Riccardo Contri From: Bug 991688 [mailto:991...@bugs.launchpad.net] Sent: Thursday, May 18, 2017 5:55 PM To: riccardocon...@libero.it Subject: Hey I know that place... In the case I was speaking of, they weren't aware of their privilege thought that privilege doesn't exist. I was merely trying to explain the concept. We all worked at a warehouse together at the time and I was talking about privilege since I'd recently seen a white coworker basically get a slap on the wrist for something a black coworker had nearly gotten fired over. They were like, "wtf is privilege sounds like bullshit to me" and I was explaining the concept. Sent from Mail for Windows 10 ** Attachment added: "8ECAEB58287CDF806CB650C90A36E60B.jpg" https://bugs.launchpad.net/bugs/991688/+attachment/4879245/+files/8ECAEB58287CDF806CB650C90A36E60B.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991688 Title: virtualbox-dkms 4.1.2-dfsg-1ubuntu1: virtualbox kernel module failed to build [error: implicit declaration of function ‘iommu_found’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/991688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1669529] [NEW] package libkf5sonnet5-data 5.26.0-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: it didn't install them ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libkf5sonnet5-data 5.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 2 18:19:26 2017 Dependencies: DuplicateSignature: package:libkf5sonnet5-data:5.26.0-0ubuntu1 Processing triggers for libc-bin (2.24-3ubuntu2) ... dpkg: error processing package libkf5sonnet5-data (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-01-03 (58 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: sonnet Title: package libkf5sonnet5-data 5.26.0-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sonnet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669529 Title: package libkf5sonnet5-data 5.26.0-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sonnet/+bug/1669529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579708] Re: mysql maintainer scripts fail if files in /etc/mysql have been deleted locally
In my case the problem is a missing /etc/mysql/my.cnf.fallback configuration file. Possible workaround: In /var/log/apt/history.log Start-Date: 2017-01-20 10:42:27 Commandline: aptdaemon role='role-commit-packages' sender=':1.126' Upgrade: mysql-server-5.7:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), mysql-server:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), mysql-client:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), libmysqlclient20:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), libmysqlclient20:i386 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), mysql-server-core-5.7:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2017-01-20 10:42:27 In /var/log/apt/term.log Log started: 2017-01-20 10:42:27 Setting up mysql-common (5.7.17-0ubuntu0.16.04.1) ... update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't exist dpkg: error processing package mysql-common (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: mysql-common Log ended: 2017-01-20 10:42:27 So the problem for me seems to be the missing the /etc/mysql/my.cnf.fallback file. ll /etc/myql drwxr-xr-x 4 root root 4096 gen 20 10:59 ./ drwxr-xr-x 189 root root 12288 gen 19 12:44 ../ drwxr-xr-x 2 root root 4096 gen 20 09:43 conf.d/ -rw--- 1 root root 317 nov 19 10:57 debian.cnf -rwxr-xr-x 1 root root 120 ott 24 17:13 debian-start* lrwxrwxrwx 1 root root 24 nov 18 21:12 my.cnf -> /etc/alternatives/my.cnf -rw-r--r-- 1 root root 3028 nov 18 21:27 my.cnf.migrated -rw-r--r-- 1 root root 682 lug 11 2016 mysql.cnf drwxr-xr-x 2 root root 4096 nov 18 22:24 mysql.conf.d/ So, because the symlink: my.cnf -> /etc/alternatives/my.cnf points back to: /etc/alternatives/my.cnf -> /etc/mysql/mysql.cnf i assumed (crossing my fingers) that /etc/mysql/mysql.cnf should be eligible as alternative fallback: sudo cp /etc/mysql/myslq.cnf /etc/mysql/my.cnf.fallback Run again apt tool to complete the upgrade. This worked 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/1579708 Title: mysql maintainer scripts fail if files in /etc/mysql have been deleted locally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1579708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657938] Re: package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Possible workaround: In /var/log/apt/history.log Start-Date: 2017-01-20 10:42:27 Commandline: aptdaemon role='role-commit-packages' sender=':1.126' Upgrade: mysql-server-5.7:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), mysql-server:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), mysql-client:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), libmysqlclient20:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), libmysqlclient20:i386 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), mysql-server-core-5.7:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2017-01-20 10:42:27 In /var/log/apt/term.log Log started: 2017-01-20 10:42:27 Setting up mysql-common (5.7.17-0ubuntu0.16.04.1) ... update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't exist dpkg: error processing package mysql-common (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: mysql-common Log ended: 2017-01-20 10:42:27 So the problem for me seems to be the missing the /etc/mysql/my.cnf.fallback file. ll /etc/myql drwxr-xr-x 4 root root 4096 gen 20 10:59 ./ drwxr-xr-x 189 root root 12288 gen 19 12:44 ../ drwxr-xr-x 2 root root 4096 gen 20 09:43 conf.d/ -rw--- 1 root root 317 nov 19 10:57 debian.cnf -rwxr-xr-x 1 root root 120 ott 24 17:13 debian-start* lrwxrwxrwx 1 root root24 nov 18 21:12 my.cnf -> /etc/alternatives/my.cnf -rw-r--r-- 1 root root 3028 nov 18 21:27 my.cnf.migrated -rw-r--r-- 1 root root 682 lug 11 2016 mysql.cnf drwxr-xr-x 2 root root 4096 nov 18 22:24 mysql.conf.d/ So, because the symlink: my.cnf -> /etc/alternatives/my.cnf points back to: /etc/alternatives/my.cnf -> /etc/mysql/mysql.cnf i assumed (crossing my fingers) that /etc/mysql/mysql.cnf should be eligible as alternative fallback: sudo cp /etc/mysql/myslq.cnf /etc/mysql/my.cnf.fallback Run again apt tool to complete the upgrade. This worked 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/1657938 Title: package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1657938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'
Same for me, workaround #15 works (Ubuntu 16.10 Unity) after reboot. (Editing /usr/lib/systemd/user/gvfs-daemon.service requires root privileges). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633162 Title: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents' To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1633162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599357] Re: WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04
The bug shows up in these Dell Latitude models D430 i915GM D630 iGM965 D610 i915GM D530 iGM965 Ubuntu 14.04 both standard and with Xenial backports is also affected. Regards Riccardo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599357 Title: WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1599357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610317] Re: setiathome fails to start
The broken simlink /var/lib/boinc-client/projects/setiathome.berkeley.edu/setiathome_v7 -> /usr/lib/boinc-app-seti-graphics/setiathome_v7 when using setiathome_v8 should be investigated by developers. ** Changed in: boinc-app-seti (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610317 Title: setiathome fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc-app-seti/+bug/1610317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610317] Re: setiathome fails to start
Please check in a terminal: ls -al /var/lib/boinc-client/projects/setiathome.berkeley.edu If you have a broken simlink: setiathome_v7 -> /usr/lib/boinc-app-seti-graphics/setiathome_v7 please try adding: sudo ln -s /usr/lib/boinc-app-seti-graphics/setiathome_v8 setiathome_v8; sudo ln -s /usr/lib/boinc-app-seti-graphics/setiathome_graphics setiathome_graphics; sudo chown -h boinc:boinc setiathome_graphics; sudo chown -h boinc:boinc setiathome_v8; sudo service boinc-client restart; This solved the same problem in my ubuntu 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610317 Title: setiathome fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc-app-seti/+bug/1610317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620854] Re: Audio playback works in slow motion after resume from suspension
** Also affects: linux-lts-xenial (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/1620854 Title: Audio playback works in slow motion after resume from suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1620854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620854] [NEW] Audio playback works in slow motion after resume from suspension
Public bug reported: The audio playback through HDMI works in slow motion after a resume from suspension. Before the suspension the audio works as expected on both the "internal speaker" and "HDMI" output cards. When you suspend (and then resume) the system the audio playback starts acting weird through the HDMI output card. The audio is played in slow motion and you can also see that the time of playback is going on slower than the time in real life. Let me describe one of the tests I've performed. I've booted the system and started playing a song in vlc. I've opened the Ubuntu sound settings. I've selected the "HDMI" output card and the playback worked as expected. I've selected the "Internal speakers" output card and the playback worked as expected. Then I've closed vlc, suspended and then resumed the system. I've started playing a song in vlc again. I've opened the Ubuntu sound settings. I've selected the "HDMI" output card and the playback started working in slow motion: the audio was extremely slow and also the time indicator was working slowly (5 seconds of the song were played in about 10 seconds "in real life"). I've selected the "Internal speakers" output card and the playback started working as expected again. Please note that after a resume from suspension when you select the "Internal speakers" card the bug disappears and when you select the "HDMI" card the bug appears again. I've tested this bug also with videos in vlc, in a browser and in totem. The bug appears (or disappears) in the same way. The bug affects every kind of audio, including system sounds. Everything works fine before a suspension. The only way I found to restore the before-suspension behavior is a reboot. Steps to reproduce: * Make sure this is a fresh boot (never suspended since the last boot). * Play something with audio (tested with: video in browser, song in vlc and Ubuntu speaker tests). * Select "Speakers - Internal audio" as output device (Audio works as expected). * Select "HDMI - Internal audio" as output device (Audio works as expected). * Stop the audio playback. * Suspend and resume the system. * Play something again. * Select "Speakers - Internal audio" as output device (Audio works as expected). * Select "HDMI - Internal audio" as output device (The bug appears). Expected behavior: * Audio playback should work well through "Speakers - Internal audio" as output device. * Audio playback should work well through "HDMI - Internal audio" as output device. Actual behavior: * Audio playback is working well through "Speakers - Internal audio" as output device. * Audio playback is working in slow motion through "HDMI - Internal audio" as output device. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo 3492 F pulseaudio /dev/snd/controlC1: riccardo 3492 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 6 23:36:10 2016 InstallationDate: Installed on 2016-04-22 (136 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interno - HDA Intel PCH Symptom_Type: Sound works for a while, then breaks Title: [HDA-Intel - HDA Intel HDMI, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 229D dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd10/22/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.13:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 097312405F1620180 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-sound xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620854 Title: Audio playback works in slow motion after resume from suspension To manage notifications about t
[Bug 1604128] Re: [2.0RC2] Unable to add a public SSH Key due to lp1604147
after to add the maas/next and made the upgrade the situation is always the same, in attached the error when added the ssh key. ** Attachment added: "Screen Shot 2016-08-11 at 17.21.51.png" https://bugs.launchpad.net/maas/+bug/1604128/+attachment/4719144/+files/Screen%20Shot%202016-08-11%20at%2017.21.51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604128 Title: [2.0RC2] Unable to add a public SSH Key due to lp1604147 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1604128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589240] [NEW] Gnome on-screen keyboard doesn't appear when a text field is focused
Public bug reported: The gnome on-screen keyboard is hidden by default and should appear when a text field is focused. This behavior is working as expected clicking on one of the text field of the shell such as the search field in the gnome overview. Clicking on text fields not owned by the gnome-shell such as in gedit or in a terminal emulator doesn't un-hide the keyboard. Steps to reproduce the issue: * Enable the keyboard in accessibility. * Open a text editor. (I've tested with gedit) * Click on the text field/area. Expected behavior: * The keyboard should appear. Actual behavior: * The keyboard doesn't appear. Also, I think it would be useful to be able to choose: * Between the "fullscreen" mode (the default one) and a windowed mode. * Between the "show on focus" behavior and a "always shown" behavior. The "fullscreen" mode should be incompatibile with the "always shown" behavior unless there is a way to close it manually (a button on the on- screen keyboard) in order to prevent a deadlock-like situation where the keyboard is preventing us from closing itself because we can't click in a window behind it. That button already exists and has a similar behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jun 5 13:49:03 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-22 (43 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "On top: the working behavior clicking on a shell text field. On bottom: the issue clicking in the gedit text area." https://bugs.launchpad.net/bugs/1589240/+attachment/4677305/+files/keyboard_issue.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589240 Title: Gnome on-screen keyboard doesn't appear when a text field is focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1589240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585818] Re: The selection is not shown when renaming in nautilus.
Just for Your information, this bug seems to appear in 16.04 LTS. Ubuntu Gnome 15.10 with the latest updates was not affected by this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585818 Title: The selection is not shown when renaming in nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1585818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585809] Re: Searching a setting component in the gnome overview, the results are shown in the wrong localization.
** Description changed: In the gnome overview if I search a setting component (e.g. "sound") it is shown in the results but always with the English localization instead of my system language. I'm using a fresh install of Ubuntu Gnome 16.04. Steps to reproduce: - * Set a non-English system language. (I'm using Italian) - * Login again and/or if necessary restart the gnome shell. - * Search a setting category/component. (I'm trying with "audio", the Italian translation of "sound") - * You should see the results in your system language but it is always shown in English. + * Set a non-English system language. (I'm using Italian) + * Login again and/or if necessary restart the gnome shell. + * Search a setting category/component. (I'm trying with "audio", the Italian translation of "sound") + * You should see the results in your system language but they are always shown in English. Please note that the wrong localization affects only the overview. In gnome-control-center the categories are shown in the system language. Also note that this happens only with results from settings (from inside the gnome-control-center). The other results are in the right language. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 25 22:57:41 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=it_IT.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=it_IT.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585809 Title: Searching a setting component in the gnome overview, the results are shown in the wrong localization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1585809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585818] [NEW] The selection is not shown when renaming in nautilus.
Public bug reported: When you rename something in nautilus and select part of the text, the selection is not shown. Steps to reproduce: * Right click on a file or a folder and click rename. (at this time the name should be automatically selected) * If not automatically selected, manually select part of the name. Expected behavior: * selected text color should change from black to white (or from white to a brighter white if the dark theme is enabled). * selected text background color should change from white to blue (or other color) (or from dark-grey to to blue (or other color) if the dark theme is enabled). Actual behavior: * the text color is changing in the expected way. * the background color is not changing (or is set to a transparent color). In the attached screenshot I've selected only "ThisTextIsSelected" and NOT selected "ThisIsNotSelected". In the screenshot is shown the behavior with both the light and dark Adwaita theme. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 26 00:00:46 2016 GsettingsChanges: b'org.gnome.nautilus.preferences' b'sort-directories-first' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'228' b'org.gnome.nautilus.window-state' b'geometry' b"'967x757+556+239'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'RabbitVCS::age_column', 'RabbitVCS::author_column', 'RabbitVCS::revision_column', 'RabbitVCS::status_column']" InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Little screenshot of the issue using both the light and dark theme." https://bugs.launchpad.net/bugs/1585818/+attachment/4670420/+files/nautilus-selection-issue.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585818 Title: The selection is not shown when renaming in nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1585818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585809] [NEW] Searching a setting component in the gnome overview, the results are shown in the wrong localization.
Public bug reported: In the gnome overview if I search a setting component (e.g. "sound") it is shown in the results but always with the English localization instead of my system language. I'm using a fresh install of Ubuntu Gnome 16.04. Steps to reproduce: * Set a non-English system language. (I'm using Italian) * Login again and/or if necessary restart the gnome shell. * Search a setting category/component. (I'm trying with "audio", the Italian translation of "sound") * You should see the results in your system language but it is always shown in English. Please note that the wrong localization affects only the overview. In gnome-control-center the categories are shown in the system language. Also note that this happens only with results from settings (from inside the gnome-control-center). The other results are in the right language. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 25 22:57:41 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Just a screenshot. You can see that the results from settings are shown in English while other results (for example from Software) are shown in Italian as expected." https://bugs.launchpad.net/bugs/1585809/+attachment/4670407/+files/gnome-overview-localization-issue.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585809 Title: Searching a setting component in the gnome overview, the results are shown in the wrong localization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1585809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577762] Re: LTE does not work after changing operator
Actually, it is not an Ubuntu fault - my new operator does not support the same LTE frequencies my old did, and the one they use in my area isn't supported by Arale. In other cities LTE works fine. ** Changed in: ofono (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577762 Title: LTE does not work after changing operator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1577762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577762] [NEW] LTE does not work after changing operator
Public bug reported:
A week ago I changed operator keeping the same number.
Everything works ok but LTE (3G and H+ works).
These are generic parameters for configuration (it's in italian but it
should be understandable, please let me know if you need a translation):
http://mdm.wind.it/dbterminali/documenti/780//Wind-
Parametri%20Generici%20Internet.pdf
Some information that could be useful:
/usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Active = 1
IPv6.Settings = { }
AuthenticationMethod = chap
Protocol = ip
Password =
Name = WIND WEB
Preferred = 1
Username =
Type = internet
AccessPointName = internet.wind
Settings = { Address=10.173.168.115 Method=static Netmask=255.255.255.0
Interface=ccmni0 Gateway=10.173.168.115
DomainNameServers=212.52.97.25,193.70.152.25, }
[ /ril_0/context2 ]
AuthenticationMethod = chap
IPv6.Settings = { }
MessageCenter = http://mms.wind.it
Protocol = ip
Password =
Preferred = 0
Username =
AccessPointName = mms.wind
Active = 0
Settings = { }
Name = WIND MMS
Type = mms
MessageProxy = 212.245.244.100:8080
/usr/share/ofono/scripts/list-modems
[ /ril_0 ]
Type = hardware
Powered = 1
Interfaces = org.ofono.ConnectionManager org.ofono.Phonebook
org.ofono.CallBarring org.ofono.CallForwarding org.ofono.CallSettings
org.ofono.SupplementaryServices org.ofono.NetworkRegistration
org.ofono.PushNotification org.ofono.MessageManager org.ofono.MessageWaiting
org.ofono.RadioSettings org.ofono.SimManager org.ofono.CallVolume
org.ofono.VoiceCallManager org.ofono.NetworkTime
Emergency = 0
Model = Fake Modem Model
Serial = xx
Revision = MOLY.LR9.W1421.MD.LWTG.MP.V6.P11, 2014/09/10 10:16
Manufacturer = Fake Manufacturer
Features = gprs ussd net sms rat sim
Lockdown = 0
Online = 1
[ org.ofono.ConnectionManager ]
Bearer = umts
Attached = 1
Powered = 1
RoamingAllowed = 0
Suspended = 0
[ org.ofono.Phonebook ]
[ org.ofono.CallBarring ]
VoiceIncoming = disabled
VoiceOutgoing = disabled
[ org.ofono.CallForwarding ]
VoiceNotReachable = +3932348xxx
ForwardingFlagOnSim = 0
VoiceUnconditional =
VoiceBusy = +3932348xxx
VoiceNoReply = +3932348xxx
VoiceNoReplyTimeout = 30
[ org.ofono.CallSettings ]
CallingLinePresentation = enabled
CallingNamePresentation = unknown
HideCallerId = default
CallingLineRestriction = off
VoiceCallWaiting = disabled
CalledLinePresentation = disabled
ConnectedLinePresentation = unknown
ConnectedLineRestriction = unknown
[ org.ofono.SupplementaryServices ]
State = idle
[ org.ofono.NetworkRegistration ]
CellId = 174x
Technology = umts
MobileNetworkCode = 88
LocationAreaCode = 26054
Strength = 35
Status = registered
Name = I WIND
Mode = auto
MobileCountryCode = 222
[ org.ofono.PushNotification ]
[ org.ofono.MessageManager ]
UseDeliveryReports = 0
Bearer = cs-preferred
Alphabet = default
ServiceCenterAddress = +393205858500
[ org.ofono.MessageWaiting ]
VoicemailMailboxNumber =
VoicemailWaiting = 0
VoicemailMessageCount = 0
[ org.ofono.RadioSettings ]
AvailableTechnologies = gsm umts lte
TechnologyPreference = lte
FastDormancy = 1
[ org.ofono.SimManager ]
SubscriberIdentity =xxx
PinRequired = none
ServiceNumbers = [Porta i tuoi amici] = '4080' [English SMS] =
'4880809' [ChaTribu'] = '48002' [TrovaNumeri] = '892125' [Credito residuo] =
'*123#' [Ascolta SegrTel] = '4200' [Info SMS e MMS] = '48048' [Risponderie
Musicall] = '48001' [Ricarica] = '4242'
Present = 1
FixedDialing = 0
SubscriberNumbers =
MobileCountryCode = 222
Retries = [puk = 10] [pin2 = 3] [pin = 3] [puk2 = 10]
CardIdentifier = x
MobileNetworkCode = 88
PreferredLanguages = it en fr de
LockedPins =
BarredDialing = 0
[ org.ofono.CallVolume ]
SpeakerVolume = 0
Muted = 0
MicrophoneVolume = 0
[ org.ofono.VoiceCallManager ]
EmergencyNumbers = 112 911
[ org.ofono.NetworkTime ]
** Affects: ofono (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/1577762
Title:
LTE does not work after changing operator
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1577762/+subscriptions
--
ubuntu-bugs
[Bug 1510570] Re: BLE pairing fail
Hi Nahum Rozen (nahum), in Ubuntu 16.04Lts Desktop Edition that ppa doesn't work, it gves this error: W: The repository 'http://ppa.launchpad.net/guilhem-fr/bluez-autoenable/ubuntu xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1) E: Failed to fetch http://ppa.launchpad.net/guilhem-fr/bluez-autoenable/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/guilhem-fr/bluez-autoenable/ubuntu/dists/xenial/main/binary-i386/Packages 404 Not Found [IP: 91.189.95.83 80] E: Some index files failed to download. They have been ignored, or old ones used instead. any idea? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: BLE pairing fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298346] Re: Non-unique names get ($number) added before the first dot instead of the last one
The problem is in `FileNameMutex::lockFileName()` which uses fileInfo.completeSuffix()[0] to understand where put the number, which returns all letters that are at right of the first dot. Now, this makes sense, because we do not want to break the file (so we do not want to append the number) but at the same time we don't want just to insert the number at the left of the last dot, because there are extensions with two dots (as .tar.gz) We should check if we know the type of the file and add the number between the filename and the extension (Chromium does that, it creates something like "file (1).extension", otherwise do something else (left of the last dot?). I think we need to investigate how other download managers take care of this. https://doc.qt.io/qt-5/qfileinfo.html#completeSuffix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298346 Title: Non-unique names get ($number) added before the first dot instead of the last one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1298346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1550267] [NEW] colplot package does not include the actual `colplot` executable
Apparently fixed in 5.0.1-3 which is in the "xenial" repo and also installs fine on "wily". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550267 Title: colplot package does not include the actual `colplot` executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colplot/+bug/1550267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550267] [NEW] colplot package does not include the actual `colplot` executable
Public bug reported: As of version 5.0.1-1, the `colplot` package does not include the actual `colplot` executable file:: $ dpkg -L colplot /. /usr /usr/share /usr/share/man /usr/share/man/man1 /usr/share/man/man1/colplot.1.gz /usr/share/doc /usr/share/doc/collectl-utils /usr/share/doc/colplot /usr/share/doc/colplot/README.Debian /usr/share/doc/colplot/copyright /usr/share/doc/colplot/changelog.Debian.gz /usr/share/collectl /usr/share/collectl/util /usr/share/collectl/plotfiles /usr/bin /etc $ Here is the output of running `dpkg -l` which shows that `colplot` is correctly installed on my system (up-to-date "wily"):: $ dpkg -l colplot Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===-=== ii colplot 5.0.1-1 all Utility to plot performance data from collectl Thanks, Riccardo ** Affects: colplot (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/1550267 Title: colplot package does not include the actual `colplot` executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colplot/+bug/1550267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520778] Re: No way to get rid of header divider without Page component
I think is important to have such an option - for example in Falldown[0] we use MainView but we don't have any Page, and we don't want to have the divider [0]: https://uappexplorer.com/app/falldown.rpadovani -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520778 Title: No way to get rid of header divider without Page component To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1520778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459079] Re: Background image fails to load on lightdm-gtk-greeter
Hello! I think that I hit this bug too. Details: When login screen appears it has a white background, instead of the specific one i set. I tried every suggestion found on the net with no success. Until (You have to try everything) I selected the "high contrast" checkbox in the accessibility menu: magically the background shows! Obviously unchecking the box turns the background white again. My idea is that the checkbox value is inverted: the default (unchecked) setting shows high contrast instead of normal behaviour. I hope to have explained this clearly... And to have suggested a path to solution. My pc: core2quad, Ati X1600, Debian Stretch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459079 Title: Background image fails to load on lightdm-gtk-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1459079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459079] Re: Background image fails to load on lightdm-gtk-greeter
Rebooting (or even killing lightdm) resets the checkbox, so everytime the pc boots I have a white login background. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459079 Title: Background image fails to load on lightdm-gtk-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1459079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
