[Bug 2058507] Re: wrapper-2.0 crashed with SIGABRT in g_assertion_message_expr()
Same problem in my laptop with Xubuntu 24. It happens at every XFCE session start. It's a fresh installation of Xubuntu 24.04.1 LTS. Attached the crash report file. ** Attachment added: "_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/2058507/+attachment/5814971/+files/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058507 Title: wrapper-2.0 crashed with SIGABRT in g_assertion_message_expr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/2058507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063207] Re: libllvm18:i386 conflicts with libllvm18
steam-libs -> mesa -> libllvm17t64-> /usr/lib/x86_64-linux-gnu/libLLVM-17.so.1 steam-libs:i386 -> mesa:i386 -> libllvm17t64:i386 -> /usr/lib/i386-linux-gnu/libLLVM-17.so.1 sudo add-apt-repository ppa:oibaf/graphics-drivers steam-libs -> mesa -> libllvm18 -> /usr/lib/llvm-18/lib/libLLVM.so.1 steam-libs:i386 -> mesa:i386 -> libllvm18:i386 -> /usr/lib/llvm-18/lib/libLLVM.so.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063207 Title: libllvm18:i386 conflicts with libllvm18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-18/+bug/2063207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063207] Re: libllvm18:i386 conflicts with libllvm18
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063207 Title: libllvm18:i386 conflicts with libllvm18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-18/+bug/2063207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060727] Re: The keyboard does not work after latest kernel update
The fix hasn't been released yet. "Fix Committed" status means the source has been updated but hasn't been released in a package. "Fix Released" status means the new package has the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060727 Title: The keyboard does not work after latest kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060727] Re: The keyboard does not work after latest kernel update
I have a Dell XPS 13 running Kubuntu 22.04. Keyboard works fine on fresh boot but the keyboard doesnt work at all after resuming from suspend. linux-image-6.5.0-27-generic is the kernel I started having the problem with. Booting an older 6.5 kernel and keyboard works again after resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060727 Title: The keyboard does not work after latest kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060120] Re: Unmet dependencies cause gparted to fail to install
That last comment 'don't forget gaps (new line) between pinning rules, w/o the gap pinning doesn't work correctly" was the cause of my issue. I now have gparted 1.5.0 installed. Thank you for responding to my issue. I now know all about app pinning - something new 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/2060120 Title: Unmet dependencies cause gparted to fail to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/2060120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060120] Re: Unmet dependencies cause gparted to fail to install
I'm afraid that approach doesn't resolve the error. Thanks though. It is interesting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060120 Title: Unmet dependencies cause gparted to fail to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/2060120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060120] [NEW] Unmet dependencies cause gparted to fail to install
Public bug reported: 1) Ubuntu Noble Numbat (development branch) Release:24.04 2) gparted 1.5.0-1 3) Expected gparted to install. 4) Install failed with 'Depends: gparted-common (= 1.5.0-1) but 1.5.0-1build2 is to be installed' 5) Output from terminal: $ sudo apt-get install gparted Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gparted : Depends: gparted-common (= 1.5.0-1) but 1.5.0-1build2 is to be installed N: Ignoring file 'ubuntu.sources.curtin.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension E: Unable to correct problems, you have held broken packages. ** Affects: gparted (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/2060120 Title: Unmet dependencies cause gparted to fail to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/2060120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976173] [NEW] 20 gig sata
Public bug reported: i have a laptop sata drive i used for a file system on windows upgraded so now its going to be my side loader, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sun May 29 02:56:37 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976173 Title: 20 gig sata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
Same for me. I try to add workaroung in #22 but May 2 15:02:12 KLINGON wpa_supplicant[10086]: SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error May 2 15:02:12 KLINGON wpa_supplicant[10086]: OpenSSL: openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929709] [NEW] Segmentation fault on launch
Public bug reported:
Ubuntu 21.04 (Canonical Gnome Desktop not flavour). Installed openbox
(3.6.1-9+deb11u1) and lxappearance (0.6.3-1) from standard repos.
Launching immediately segfaults.
Rebuilding the package still segfaults.
It seems to be having issues parsing:
/usr/share/icons/gnome/index.theme
/usr/share/icons/DMZ-Black/index.theme
These files look normal and have correct permissions.
I added a small hack to src/icon-theme.c to ignore these files and
lxappearance now works correctly but is missing these themes.
### BACKTRACE FROM GDB
Program received signal SIGSEGV, Segmentation fault.
0x7791179d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) b
Breakpoint 1 at 0x7791179d
(gdb) backtrace
#0 0x7791179d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x77911cc1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x77911f41 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x77912079 in g_key_file_load_from_file () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0xd5d4 in load_icon_themes_from_dir
(base_dir=0x5570c180 "/usr/share/icons", theme_dir=0x5570c180
"/usr/share/icons", kf=0x5570d990) at icon-theme.c:84
#5 0xd92a in load_icon_themes () at icon-theme.c:125
#6 icon_theme_init (b=b@entry=0x555d49c0) at icon-theme.c:247
#7 0xab0e in main (argc=, argv=) at
lxappearance.c:663
### HACK TO FIX ISSUE
--- lxappearance-0.6.3.orig/src/icon-theme.c
+++ lxappearance-0.6.3/src/icon-theme.c
@@ -81,7 +81,15 @@ void load_icon_themes_from_dir(const cha
theme->base_dir = base_dir;
theme->is_removable = (0 == access(base_dir, W_OK));
+// printf("%s\n", index_theme);
+if (strcmp(index_theme, "/usr/share/icons/gnome/index.theme")
== 0)
+continue;
+
+if (strcmp(index_theme,
"/usr/share/icons/DMZ-Black/index.theme") == 0)
+continue;
+
if(g_key_file_load_from_file(kf, index_theme, 0, NULL))
{
/* skip hidden ones */
if(!g_key_file_get_boolean(kf, "Icon Theme", "Hidden",
NULL))
** Affects: lxappearance (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/1929709
Title:
Segmentation fault on launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxappearance/+bug/1929709/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems
FWIW Upgrading worked fine, system boots normally and everything works apart from a Failed to start MokListXRT, out of resources message before the window manager loads. This is on a Thinkpad with EFI v2.31 by Lenovo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925010 Title: shim-signed 15.4 does not boot on EFI 1.10 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90851]
it is no longer in right-click menu. bug is fixed for good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/90851 Title: Firefox does not set KDE wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/90851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898891] Re: anacron cron.weekly error: AttributeError: module 'platform' has no attribute 'linux_distribution'
Adding a "me too". Upgraded from 18 to 20 (both LTS) and am now getting this same error (with identical traceback as above). It seems that /usr/share/software- center/softwarecenter/distro/__init__.py calls platform.linux_distribution(), which no longer exists. >From stackoverflow (where all of my knowledge of python resides), I find this, >at >https://stackoverflow.com/questions/63636697/error-module-platform-has-no-attribute-linux-distribution > : "Python 3.8 removed the "linux_distribution()" function from the platform module. It is replaced by the equivalent in the "distro" module (distro is not built-in to Python and must be installed via pip)." For me, since I don't believe I've ever once used the index built by apt-xapian-index, and it's only a recommendation, I've simply removed the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898891 Title: anacron cron.weekly error: AttributeError: module 'platform' has no attribute 'linux_distribution' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1898891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
I've upgraded 4 systems from 18.04 to 20.04, and only one has shown this behavior. Will attach an strace of the focal process. I ran the strace for approximately 30 seconds. ** Attachment added: "strace of the python focal process, while bug is occurring" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+attachment/5419188/+files/focal.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] Re: Cannot be past login screen in kernel 5.7.0-050700-rc2
I also tried fractional scaling; got the same delay. And when I tried adjusting the resolution to 1920x1080 directly with the resolution setting instead of 200% magnification, I got the delay again. So the only fast adjustment is with magnification and no fractional scaling. Attached is the System D report for the boot up. ** Attachment added: "SystemD 5.8.0-rc2 kernel bootup.odt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+attachment/5386147/+files/SystemD%205.8.0-rc2%20kernel%20bootup.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] Re: Cannot be past login screen in kernel 5.7.0-050700-rc2
This one is a bit of an improvement. Boot time to a working desktop was about 3 minutes. But most interesting was that I could change my display resolution almost instantly with a 200% magnification. Attempting to change by adjusting the resolution directly (from 3840x2160 to 2560x1440) caused the usual delay. I will post the SystemD analysis in the next message. ** Attachment added: "dmesg for 5.8.0-rc2 boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+attachment/5386109/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] Re: Cannot be past login screen in kernel 5.7.0-050700-rc2
I just tested the latest kernel, and it is worse. This time it didn't even make it to the login screen, and I let it run for 5 minutes. dmesg from that boot attempt is attached. Given the lack of success at booting kernels from 5.3 - 5.7, I'm wondering whether this 2015 iMac is going to be a viable Linux computer once the Ubuntu 4.15 LTS kernel is no longer supported. ** Attachment added: "dmesg for 5.7.0- 994 boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+attachment/5367827/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] Re: Cannot be past login screen in kernel 5.7.0-050700-rc2
I just tested rc4, and now I can no longer log in; same as with rc2. So to summarize, I cannot get past the login screen with versions rc2 and rc4, whereas I could with rc3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
5.7-rc3 boots on my iMac. It gets past the login screen (unlike rc2), but it still has the slow boot problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] Re: Cannot be past login screen in kernel 5.7.0-050700-rc2
I can report that kernel 5.7.0-050700-rc3 now boots (but very slowly). Unlike rc2, it gets past the login screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I made a separate report of the 5.7-rc2 kernel bug to ubuntu-bug linux as you requested. I will also try to monitor the upstream rc kernels and run tests on them as you have requested. I agree that the slow boot bug is likely connected to the AMD video card in my iMac, and thus to the amdgpu driver. I say that because I also have a 2011 iMac with a much older AMD Radeon video card (6770M), and it has no trouble with the 5.4 kernel in Ubuntu 20.04, nor with any of the kernels that came with 18.04, 18.10, 19.04 or 19.10. If the amdgpu powerplay failing to send message is the problem, is there an easy fix for this? I did look at the changelog for the 5.3-rc1 kernel (the first with the slow boot). There were a lot of changes related to amd and amdgpu by at least 25 people, but I have no idea how to figure out which, if any, of these changes is causing the slow boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] Re: Cannot be past login screen in kernel 5.7.0-050700-rc2
Attached is the dmesg from kernel 5.4.0.26, which boots slowly on this iMac, but at least boots all the way to a working desktop. You can contrast this to the dmesg of 5.7.0-050700-rc2, which won't boot past the login screen. ** Attachment added: "dmesg for 5.4.0-26 boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+attachment/5360986/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] [NEW] Cannot be past login screen in kernel 5.7.0-050700-rc2
Public bug reported: This is an extension of the "slow boot" bug I reported earlier [Bug 1874104]. I have been working with Jouni Mettala, and he was asking me to try the most recent kernels, including the latest in development (5.7.0-050700-rc2). This one not only boots very slowly, but also, I cannot get past the login screen. When I put in my password and hit enter, the screen just returns. I have tried this several times and encountered the same problem except only once. (Not sure why that one was different. Jouni asked me to report this as a new bug. I will attach the dmesg for the 5.7 kernel boot that wouldn't get past the login screen here. Since I can only post one attachment at a time, I will attach the dmesg for the default kernel boot (5.4.0-26) in the next message for comparison. That is a slow boot kernel, relative to any kernel in the 4.15, 5.1 and 5.2 series, but I can at least boot it on this "late 2015" 27" 5k iMac. For more information on the slow boot problem, please see Bug Report 1874104. 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mfox 2659 F pulseaudio /dev/snd/controlC0: mfox 2659 F pulseaudio /dev/snd/controlC2: mfox 2659 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 13:00:28 2020 HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a InstallationDate: Installed on 2018-05-09 (717 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. iMac17,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: \boot\vmlinuz-5.4.0-26-generic ro root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead initrd=boot\initrd.img-5.4.0-26-generic RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 176.0.0.0.0 dmi.board.name: Mac-B809C3757DA9BB8D dmi.board.vendor: Apple Inc. dmi.board.version: iMac17,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B809C3757DA9BB8D dmi.modalias: dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D: dmi.product.family: iMac17,1 dmi.product.name: iMac17,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "dmesg for 5.7.0-050700-rc2 kernel" https://bugs.launchpad.net/bugs/1875211/+attachment/5360948/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875211] Re: Cannot be past login screen in kernel 5.7.0-050700-rc2
Instructions were to include information from About in Settings. Screenshot attached. ** Attachment added: "About my late 2015 27" iMac with the kernel booting issues" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+attachment/5360987/+files/About%20my%20computer.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875211 Title: Cannot be past login screen in kernel 5.7.0-050700-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I forgot to send you the proper dmesg for the boot of kernel 5.3rc-1. It is attached. This kernel was not only slow, but it didn't pick up my wireless card. This was the only kernel I tried that did this. ** Attachment added: "dmesg for 5.3rc1 boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5360483/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I will report the login bug as a new one. As far as bisection past identifying the line of progression to identify the last kernel that works and the first one that doesn't, I looked at the further steps one would have to take and I don't think that my technical capability is up to it. I have never compiled a kernel before, and those instructions suggest that it's more complicated than just compilation. Is there anything further I can do that is less technical to help diagnose and fix this bug in the 20.04 LTS kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
It is possible to login with kernel 5.6. The bootup is slow, but it does boot and gets past the login screen. I have attached the dmesg from that boot, and will send the systemd analysis in the next message. ** Attachment added: "dmesg.0 for 5.6 boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5360468/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
Attached is the SystemD analysis for the 5.6 boot. It looks pretty similar to that of all the kernels I have tried that are 5.3 or newer. ** Attachment added: "SystemD critical chain and blame outputs: 5.6 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5360469/+files/SystemD%205.6%20kernel%20bootup.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I did the bisection and found that the bad kernels started at 5.3-rc1. The last 5.2 kernel, 5.2.21, was good. I have attached the SystemD analysis here of the boots of both kernels. You can see from it that the problem in rc1 is related to the gpu-manager service. I will attach the dmesg log of the rc1 boot in the next message. ** Attachment added: "SystemD critical chain and blame outputs: 5.3-rc1vs 5.2.21 kernels" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359788/+files/SystemD5.2.21%265.3.rc1%20kernel%20bootup.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I should add that I tested kernels 5.2.15, 5.2.18 and 5.2.20 as well. All were OK, so the good-bad line is clearly after 5.2.21. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
Here is the dmesg log for the bad boot of 5.3-rc1. ** Attachment added: "Log of 5.3-rc1 kernel boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359789/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
Finally, a second dmesg for the 5.2 kernel boot.(I'm not sure whether dmesg or dmesg.0 is the right one. ** Attachment added: "dmesg.0 for 5.2 boot (I hope)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359527/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
This time with the last fast kernel, 5.2. The bootup was slightly slower than with 4.15, but I think this might relate to snap module loading. I should also point out that the difference between kernels 4.15, 5.1 and 5.2 vs the kernels after 5.3 is more than what is indicated by the SystemD analysis. With the newer kernels there is an additional delay of about a minute from the point where I log in until I get a working desktop. Attached is the SystemD analysis for kernel 5.2 ** Attachment added: "SystemD analysis 5.2 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359509/+files/SystemD%205.2%20kernel%20bootup.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
Next is the first of two dmesg logs for the 5.2 kernel. ** Attachment added: "dmesg for 5.2 boot (I hope)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359510/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
Next, dmesg.0 ** Attachment added: "dmesg.0 for 5.3 boot (I hope)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359503/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
Next, a dmesg for that boot. Not sure which it is so I'll send two. ** Attachment added: "dmesg for 5.3 boot (I hope)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359502/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I uninstalled Virtualbox and tested kernels 5.1 and 5.2. Both showed fast boots similar to 4.15. I then tested 5.3 by downloading it from the ppa/mailine. This is where the slow boot started. I have attached two dmesg's and a systemd analysis of the critical chain and blame for kernel 5.3. I can't seem to send more than one file at a time, so I will send 3 separate messages. You can contrast this against the equivalent for kernel 5.2, which I will reboot with and send results in the next set of messages. ** Attachment added: "SystemD analysis 5.3 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359501/+files/SystemD%205.3%20kernel%20bootup.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I hope this is what you were looking for. In your message, you noted that the login bug is likely a separate issue and it could be reported as new. I thought that this is what I already did. If not, should I report it again? And with what attachments? Thanks. ** Attachment added: "dmesg.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5358452/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
Thanks for the quick reply. I installed and tested 5.7-rc2 as per instructions. The new kernel booted up to the login screen, but as slowly as 5.4.0-25. (Over 2 minutes to the login screen.) When I logged in with my password, all that happened was that I was returned to the login screen. I tried logging in three times with the same result. I don't know if this is related, but there were only four 5.7-rc2 modules that applied to my non-low latency install. Normally there is also a signed module, but there was not one present in the mainline ppa for this kernel. Would you like an additional bug report for this boot? If so, how do I do this and get it included in the existing bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874104] [NEW] Very slow boot, wake from sleep and shutdown with 5.4 kernel
Public bug reported: I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015 5k 27" iMac. The new 5.4 kernel was installed and has been updated a few times. The former LTS kernel (4.15) was retained. When I start up the computer with the new kernel, the process is very slow and it takes about 2 1/2 minutes to get to a working desktop. Doing the same startup with the old 4.15 kernel (in the 20.04 beta) takes approximately 25 seconds to a working desktop. Similarly, changing display settings, waking from sleep and shutting down the computer all take several minutes with the 5.4 kernel, vs 10-30 seconds with the 4.15 kernel. To provide more information, I tried starting up this computer with the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to the 4.15 LTS kernel. I suspect that the problem relates to the Radeon m9 390x video card in my iMac, but I have no idea what might have changed in the newer kernels to affect their compatibility with this iMac. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mfox 2497 F pulseaudio /dev/snd/controlC0: mfox 2497 F pulseaudio /dev/snd/controlC1: mfox 2497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 10:55:18 2020 HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a InstallationDate: Installed on 2018-05-09 (712 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. iMac17,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead initrd=boot\initrd.img-5.4.0-25-generic RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 176.0.0.0.0 dmi.board.name: Mac-B809C3757DA9BB8D dmi.board.vendor: Apple Inc. dmi.board.version: iMac17,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B809C3757DA9BB8D dmi.modalias: dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D: dmi.product.family: iMac17,1 dmi.product.name: iMac17,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "SystemD critical chain and blame outputs: 5.4 vs 4.15 kernel" https://bugs.launchpad.net/bugs/1874104/+attachment/5357597/+files/SystemD%20report_Ubuntu_20.04beta_late_2015_iMac.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
apport information ** Tags added: apport-collected ** Description changed: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu26 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + Dependencies: + + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-08 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + Package: linux + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 + Tags: focal + Uname: Linux 5.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1872108/+attachment/5351447/+files/ProcCpuinfoMinimal.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
** Also 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/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] [NEW] Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
Public bug reported: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ** Description changed: - Related to last comment on this issue - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677 + Related to + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: - + InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-ucm-conf 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/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866070] Re: extension not compatible with gnome-shell 3.36 (Focal Fossa)
Is it intentional, that package "gnome-shell-extension-prefs" package is no longer being installed automatically in 20.04/Gnome Shell 3.36? ** Also affects: gnome-shell (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/1866070 Title: extension not compatible with gnome-shell 3.36 (Focal Fossa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866070] Re: extension not compatible with gnome-shell 3.36 (Focal Fossa)
Maybe it is unrelated but whenever I activate any Gnome Extension on 20.04. it causes my lockscreen to enter an endless loop of crashing and restarting. This can be triggered by pressing Super+L or waiting for the timer to put the screen to sleep. As soon as you log back in, it throws you back to the lock screen. Deactivating all extensions resolves the problem. I use the aforementioned 'dash-to-panel' extension but it also happens if I remove that one and use 'gtile' for example. The issue that extension settings cannot be opened can be fixed by installing the 'gnome-shell-extension-prefs' package which apparently is not installed by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866070 Title: extension not compatible with gnome-shell 3.36 (Focal Fossa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1866070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820795] Re: Ubuntu installer crashed
Oh, forgot to mention, the second installation attempt with previous installation removed succeeded without error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820795 Title: Ubuntu installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820795] Re: Ubuntu installer crashed
Name entered was "localadmin" without the quotes Machine name was "vader-l" Don't believe I made any typos. I did a minimal install following this, but with multiple changes. I first made sure to remove the btrfs '@' subvolume and I also did a minimal install with no updates downloaded. If I had to make an educated guess I'd say it was the existing install causing conflicts. "localadmin" was a user that existed in the previous install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820795 Title: Ubuntu installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820795] [NEW] Ubuntu installer crashed
Public bug reported: Custom partition installation settings. Opted to download updates and install 3rd party drivers. Installing alongside Windows 10 and over an existing installation. Current boot partition set to be formatted as EXT4 and mounted to /boot Current root partition not formatted, selected BTRFS and mounted to / Installation crashed part way through. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.6.1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CasperVersion: 1.402 Date: Mon Mar 18 21:39:03 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.6.1 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820795 Title: Ubuntu installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site
I realize the issue reported was related to 18.04, but I am also having this same issue on 18.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760349 Title: Cannot log in to public open Wifi connection because not being redirected to login site To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1760349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798790] Re: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot
As mentioned in the above askubuntu posting, removing the nvidia driver got me past the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793731] Re: Sagemath installed via Synaptic package manager crashes from command line
See attachment re ls -l /home/dlf/.local/lib/python2.7/site- packages/six.py ** Attachment added: "sixpy" https://bugs.launchpad.net/ubuntu/+source/sagemath/+bug/1793731/+attachment/5191452/+files/sixpy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793731 Title: Sagemath installed via Synaptic package manager crashes from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sagemath/+bug/1793731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793731] Re: Sagemath installed via Synaptic package manager crashes from command line
** Package changed: ubuntu => sagemath (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793731 Title: Sagemath installed via Synaptic package manager crashes from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sagemath/+bug/1793731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793731] [NEW] Sagemath installed via Synaptic package manager crashes from command line
Public bug reported: Downloaded and installed Sagemath, Sagemath Jupyter with Synaptic pkg manager to OS Ubuntu 18. Crashes from command line. I have crash report if anyone wants to see it. Problem solved by downloading and installing directly from SageMath mirror site. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793731 Title: Sagemath installed via Synaptic package manager crashes from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1793731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793731] Re: Sagemath installed via Synaptic package manager crashes from command line
Crash report attached. ** Attachment added: "crash_report" https://bugs.launchpad.net/ubuntu/+bug/1793731/+attachment/5191389/+files/crash_report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793731 Title: Sagemath installed via Synaptic package manager crashes from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1793731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792670] Re: Kernel module cannot be built on Linux 4.17+
Hi, I’m unsure of what you mean - this is an issue with installing Virtualbox through apt on a host machine - not an issue with guest addons inside VMs. Unless I misunderstand completely, it’s also not a kernel failure: a function in the kernel was removed as part of an API change between kernel versions. I reported this as a bug because users of recent stable kernels will not be able to install Virtualbox through apt and presumably Ubuntu itself will move to one such kernel sometime in the future. ~ Fox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792670 Title: Kernel module cannot be built on Linux 4.17+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1792670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792670] [NEW] Kernel module cannot be built on Linux 4.17+
Public bug reported: Hi, Apologies in advance if I have somehow messed up the bug reporting process - I'm quite new at this. I tried to install virtualbox on a Linux 4.19-rc3-based Ubuntu machine, but virtualbox-dkms wouldn't build as it references the old pci_get_bus_and_slot() function that seems to have been removed between kernel versions 4.16 and 4.17: [...] /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciLinuxDevDetachHostDriver’: /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:92:40: error: implicit declaration of function ‘pci_get_bus_and_slot’; did you mean ‘pci_get_domain_bus_and_slot’? [-Werror=implicit-function-declaration] # define PCI_DEV_GET_SLOT(bus, devfn) pci_get_bus_and_slot(bus, devfn) [...] Editing /var/lib/dkms/virtualbox/5.2.10/source/vboxpci/linux/VBoxPci-linux.c:92 to refer to pci_get_slot(bus, devfn) instead of pci_get_bus_and_slot(bus, devfn) has fixed the compile error, though I am not sure if this is correct -- perhaps I should have used pci_get_domain_bus_and_slot(0, bus, devfn) instead. Sorry if this is already covered ground. ~ Fox --- ~$ uname -r 4.19.0-rc3-fox+ fox@humphry:~$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release: 18.04 fox@humphry:~$ apt-cache policy virtualbox-dkms virtualbox-dkms: Installed: 5.2.10-dfsg-6ubuntu18.04.1 Candidate: 5.2.10-dfsg-6ubuntu18.04.1 Version table: *** 5.2.10-dfsg-6ubuntu18.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages 100 /var/lib/dpkg/status 5.2.10-dfsg-6 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages fox@humphry:~/kernel/linux$ cat /var/lib/dkms/virtualbox/5.2.10/build/make.log DKMS make.log for virtualbox-5.2.10 for kernel 4.19.0-rc3-fox+ (x86_64) Sat 15 Sep 05:51:15 BST 2018 make: Entering directory '/home/oai/kernel/linux' CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/linux/SUPDrv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrvGip.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrvSem.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrvTracer.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPLibAll.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/alloc-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/initterm-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/memobj-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/mpnotification-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/powernotification-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/mpnotification-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/process-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/rtStrFormatKernelAddress-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/semevent-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/semeventmulti-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/semfastmutex-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/semmutex-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/spinlock-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/thread-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/thread2-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/threadctxhooks-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/timer-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/common/alloc/alloc.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/common/checksum/crc32.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/generic/semspinmutex-r0drv-generic.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/common/checksum/ipv4.o CC [M] /var/lib/dkms/vir
[Bug 1788330] [NEW] package luarocks (not installed) failed to install/upgrade: installed luarocks package post-installation script subprocess returned error exit status 1
Public bug reported: After attempting an install from instructions on https://luarocks.org/ for version 3.0.0 failed, I fell back to the version in Ubuntu's packages. This failed to install. On Ubuntu 18.04.1 LTS luarocks: Installed: (none) Candidate: 2.4.2+dfsg-1 Version table: 2.4.2+dfsg-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages ProblemType: Package DistroRelease: Ubuntu 18.04 Package: luarocks (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: lua-any:amd64: Install lua-socket:amd64: Install lua-sec:amd64: Install luarocks:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Aug 20 09:50:47 2018 ErrorMessage: installed luarocks package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-20 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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: luarocks Title: package luarocks (not installed) failed to install/upgrade: installed luarocks package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: luarocks (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788330 Title: package luarocks (not installed) failed to install/upgrade: installed luarocks package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/luarocks/+bug/1788330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781987] [NEW] Ubuntu 18.04 graphical issue with OVMF
Public bug reported: Running Ubuntu 18.04 Server virtual machine with UEFI enabled there appears to be graphical issues (pixels in wrong place). These issues can be temporarily fixed by changing the gfxmode in grub config. But from time to time Ubuntu boots into a machine that has pixels in wrong place. This problem was originally discovered when installing Ubuntu 18 on a xen hypervisor with Secure Boot enabled. My suspicion is that its a problem with OVMF and Ubuntu. Issues can also be solved by switching to vga=cirrus. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781987 Title: Ubuntu 18.04 graphical issue with OVMF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1781987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781987] Re: Ubuntu 18.04 graphical issue with OVMF
Here is a copy of a working /boot/grub/grub.cfg file that fixed a problem. When using QEMU, apply some of this config to broken one (UUIDs will not be the same for you!!) and then when grub menu appears press enter on Ubuntu option to enter non broken machine. If you let grub timeout play out and don't press enter then system will be corrupted. ** Attachment added: "grub.cfg" https://bugs.launchpad.net/ubuntu/+bug/1781987/+attachment/5164237/+files/grub.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781987 Title: Ubuntu 18.04 graphical issue with OVMF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1781987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781987] Re: Ubuntu 18.04 graphical issue with OVMF
** Attachment added: "Screenshot of graphical problem" https://bugs.launchpad.net/ubuntu/+bug/1781987/+attachment/5164236/+files/qemu.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781987 Title: Ubuntu 18.04 graphical issue with OVMF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1781987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780250] [NEW] package linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Ope
Public bug reported: This bug came up after an update and restart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 2 09:38:36 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-07-02 09:38:34 Commandline: aptdaemon role='role-commit-packages' sender=':1.317' Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26~16.04.1, automatic), linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic), linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic), linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic), linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic) Upgrade: linux-libc-dev:amd64 (4.4.0-128.154, 4.4.0-130.156), linux-image-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-signed-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-signed-image-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-headers-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46) DpkgTerminalLog: Preparing to unpack .../linux-modules-4.15.0-24-generic_4.15.0-24.26~16.04.1_amd64.deb ... Unpacking linux-modules-4.15.0-24-generic (4.15.0-24.26~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-4.15.0-24-generic_4.15.0-24.26~16.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted DuplicateSignature: package:linux-modules-4.15.0-24-generic:4.15.0-24.26~16.04.1 Unpacking linux-modules-4.15.0-24-generic (4.15.0-24.26~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-4.15.0-24-generic_4.15.0-24.26~16.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted InstallationDate: Installed on 2018-03-25 (101 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (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/1780250 Title: package linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-4.15.0-24-generic.list-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1780250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778133] [NEW] cppunit-config is missing
Public bug reported: Prior packagings of libcppunit-dev included cppunit-config which could be used to determine proper compilation and link flags. (In fact this is used by autoconf's AM_PATH_CPPUNIT to configure cppunit in auto make). This appears to be missing in bionic. daquser@bionic-beaver:~/SpecTcl/main/libtcl/exception$ cppunit-config cppunit-config: command not found While e.g on 16.04 (Xenial): daquser@xenial:~$ cppunit-config Usage: cppunit-config [OPTION]... Thanks, Ron ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcppunit-dev 1.14.0-3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 16:41:51 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libcppunit-1.14-0 1.14.0-3 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 InstallationDate: Installed on 2018-06-21 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: cppunit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cppunit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778133 Title: cppunit-config is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cppunit/+bug/1778133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777142] [NEW] package linux-image-4.13.0-45-generic 4.13.0-45.50~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-4.13.0-45-generic.list-new': Operati
Public bug reported: I don't know much, the system just sent me the message and told me to report it. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-45-generic 4.13.0-45.50~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jun 11 16:59:55 2018 DuplicateSignature: package:linux-image-4.13.0-45-generic:4.13.0-45.50~16.04.1 Unpacking linux-image-4.13.0-45-generic (4.13.0-45.50~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-4.13.0-45-generic_4.13.0-45.50~16.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-image-4.13.0-45-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-image-4.13.0-45-generic.list-new': Operation not permitted InstallationDate: Installed on 2018-03-25 (81 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-image-4.13.0-45-generic 4.13.0-45.50~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-4.13.0-45-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (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/1777142 Title: package linux-image-4.13.0-45-generic 4.13.0-45.50~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- image-4.13.0-45-generic.list-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1777142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1680224] Re: auto.smb fails on Windows administrative shares
I honestly don't know. The initial patches from April 12th of 2017 were all I needed and I haven't messed with it since. On Wed, Jun 6, 2018, 09:20 Andreas Hasenack, wrote: > @mark-fox, were those two patches the only changes you needed, or was > the change to the awk script (removing the quoting of $) also needed? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1680224 > > Title: > auto.smb fails on Windows administrative shares > > Status in autofs package in Ubuntu: > Triaged > > Bug description: > This is probably related to #385244. > > I've been unable to get a Windows administrative share (ie. C$) > mounted through Autofs. Non-administrative shares work fine. > Administrative shares are accessible with the same credentials from > other Windows 10 workstations and through smbclient on Ubuntu (16.04 > LTS) machines. Administrative shares can even be mounted using the > same credentials via mount on the command-line. However, autofs will > not mount the same shares, using the same credentials, on the same > Ubuntu machine. > > Administrative shares are listed under /cifs/WindowsHostName, but a cd > /cifs/WindowsHostname/C$ results in "-bash: cd: C$: No such file or > directory" from the shell and the following output from 'automount -f > -v': > > - > attempting to mount entry /cifs/WindowsHostname/C$ > >> Retrying with upper case share name > >> mount error(6): No such device or address > >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) > mount(generic): failed to mount //WindowsHostname/C\$ (type cifs) on > /cifs/WindowsHostname/C$ > failed to mount /cifs/WindowsHostname/C$ > - > > Notice that mount complains of failing to mount 'C\$' rather than > 'C$'. If the bit of awk script that escapes the $ is removed, it then > fails to mount 'C', which is also no good. I think if we could > actually get mount to try to mount 'C$', it would work. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733557] Re: Login screen showing Authentication Failure Switch to greeter...
This exact issue started happening to me a couple days ago. I didn't notice any apparent cause. When I click or press any key, the screen goes black for a second, then reloads with a system alert sound to the normal login screen. After a successful login, the screen flashes the "Switch to Greeter" screenshot that was attached to the original bug before successfully logging in. __uname__ Kernel: Linux Kernel Release: 4.13.0-38-generic Kernel Version: #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 Network Node Hostname: redgray Machine Hardware Name: x86_64 Processor: x86_64 Hardware Platform: x86_64 Operating System: GNU/Linux 16.04.4 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failure Switch to greeter... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
@cjjefcoat Thanks for your advice,I have meet the same issue in virtualbox after the ubuntu 14.04 kernel update to 116. After downgrade the gcc to 4.8.4, and reinstall the 116 kernel and virtualbox 5.2,it work! ** Attachment added: "Virtualbox errror info" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750937/+attachment/5064244/+files/some_info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567427] Re: gnome-shell crashes when touchscreen is touched
Anytime I have a video playing, or my laptop has been on a while, if I touch the screen all my programs close and I get logged out. Trying to turn off the screen via XINPUT does not work, disabling the touchscreen does NOTHING now that ubuntu runs on wayland. Running Ubuntu 17 right now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567427 Title: gnome-shell crashes when touchscreen is touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1567427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715268] [NEW] package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (curren
Public bug reported: I ran 'Software Updater" on 9/5 and got this result. It said "current status =half-installed" or similar language. I can only hope this this thing will boot next time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1764 F pulseaudio Date: Tue Sep 5 21:14:11 2017 ErrorMessage: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=6343e38d-c2cb-4bdc-931f-7d7de298ee9d InstallationDate: Installed on 2016-05-15 (478 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision M6300 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 dmi.sys.vendor: Dell Inc. ** Affects: linux (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/1715268 Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half- installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698599] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Thank you Joseph I executed the 3 command line steps you outlined and I think it fixed my issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698599 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699460] Re: Jetty - Service killed by signal 11
Fixed in - linux-image-3.13.0-123-generic ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699460 Title: Jetty - Service killed by signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n trusty/xenial/yakkety
I tried this so as to be ready for the next problem, but install does not like the armhf bit - wants amd64. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety Date: Fri, 07 Jul 2017 15:18:35 - @David: please continue this discussion on bug #1702633. If you don't manage to install the dbgsym package, you can still download it manually and install it (with `sudo dpkg -i`) from there: https://launchpad.net/~canonical-chromium- builds/+archive/ubuntu/stage/+build/12789789 -- You received this bug notification because you are subscribed to a duplicate bug report (1702501). https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions Police Urge Americans to Carry This With Them at All Times The Observer http://thirdpartyoffers.juno.com/TGL3131/595fd5e12543d55e13807st02vuc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial
That seems to have fixed the problem - Chromium is running as before the update. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial Date: Thu, 06 Jul 2017 20:48:42 - Thanks for the quick feedback Trent! To everyone affected by the crash, could you please try the packages in that PPA, and see if the crash goes away? sudo add-apt-repository -y ppa:osomon/chromium-fix-1702407 sudo apt update sudo apt dist-upgrade Note that packages for trusty haven't finished building yet, but should be done soon. -- You received this bug notification because you are subscribed to a duplicate bug report (1702501). https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions Police Urge Americans to Carry This With Them at All Times The Observer http://thirdpartyoffers.juno.com/TGL3131/595ea8dd137d28dc70eest03vuc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial
Turned off WiFi, Chromium browser comes up with home page (google). Seems OK. Turn on WiFi, and it crashes. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial Date: Thu, 06 Jul 2017 09:30:50 - To everyone affected by the crash (I haven't managed to reproduce it locally yet): can you please disable networking on your computer (turn off wifi) and check whether that makes chromium start normally? -- You received this bug notification because you are subscribed to a duplicate bug report (1702501). https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions How To Lose Weight Fast (Drink This Daily) Celebrity Local http://thirdpartyoffers.juno.com/TGL3131/595e29a1d367629a10cd6st04vuc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename:xenial Linux rohan-T500 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages -- Original Message -- From: actionparsnip To: rbayer...@juno.com Subject: [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 Date: Wed, 05 Jul 2017 15:47:39 - What is the output of: lsb_release -a; uname -a; apt-cache policy chromium-browser Thanks -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702501/+subscriptions Actress Reveals Hollywood Secret “Flattening� Bloated Belly ActivatedYou http://thirdpartyoffers.juno.com/TGL3131/595d29a22fbfc29a23cbest02vuc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
I cannot believe I am the only one to experience this bug. Is there anything I should try which I have not yet tried? ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702501] [NEW] chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
Public bug reported: After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got: Received signal 11 SEGV_MAPERR 0010 #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace() #1 0x7f5c4b92d80b #2 0x7f5c4bc58390 #3 0x55ae23b43dc8 #4 0x55ae23b46656 #5 0x55ae23b46df9 #6 0x55ae23b47143 #7 0x7f5c4b9a8821 #8 0x7f5c4b92eeea base::debug::TaskAnnotator::RunTask() #9 0x7f5c4b957e90 base::MessageLoop::RunTask() #10 0x7f5c4b95997d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f5c4b95a83d #12 0x7f5c4b95b300 base::MessagePumpLibevent::Run() #13 0x7f5c4b956f15 base::MessageLoop::RunHandler() #14 0x7f5c4b981628 base::RunLoop::Run() #15 0x7f5c4b9ade36 base::Thread::ThreadMain() #16 0x7f5c4b9a8726 #17 0x7f5c4bc4e6ba start_thread #18 0x7f5c352fd3dd clone r8: 002e r9: 55ae2559a6ec r10: r11: 7f5c3538af50 r12: 7f5bc6b2aff0 r13: 0008 r14: 0008 r15: 7f5bc6b2aeb0 di: si: 7f5bc6b2aeb0 bp: 7f5bc6b2af00 bx: 7f5bc6b2aeb0 dx: 0067 ax: cx: 7f5bdc1079c0 sp: 7f5bc6b2ae60 ip: 55ae23b43dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. I tried complete reinstallation, purged and removed .config/chromium. Same problem. When I restored .config/chromium from an earlier working version, it crashed with: [8159:8202:0705/102433.905625:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. Received signal 11 SEGV_MAPERR 0010 #0 0x7f3a02096425 base::debug::StackTrace::StackTrace() #1 0x7f3a0209680b #2 0x7f3a023c1390 #3 0x5604c6bcadc8 #4 0x5604c6bcd656 #5 0x5604c6bcddf9 #6 0x5604c6bce143 #7 0x7f3a02111821 #8 0x7f3a02097eea base::debug::TaskAnnotator::RunTask() #9 0x7f3a020c0e90 base::MessageLoop::RunTask() #10 0x7f3a020c297d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f3a020c383d #12 0x7f3a020c4300 base::MessagePumpLibevent::Run() #13 0x7f3a020bff15 base::MessageLoop::RunHandler() #14 0x7f3a020ea628 base::RunLoop::Run() #15 0x7f3a02116e36 base::Thread::ThreadMain() #16 0x7f3a02111726 #17 0x7f3a023b76ba start_thread #18 0x7f39eba663dd clone r8: 002e r9: 5604c86216ec r10: r11: 7f39ebaf3f50 r12: 7f39748cbff0 r13: 0008 r14: 0008 r15: 7f39748cbeb0 di: si: 7f39748cbeb0 bp: 7f39748cbf00 bx: 7f39748cbeb0 dx: 0067 ax: cx: 7f39d003a050 sp: 7f39748cbe60 ip: 5604c6bcadc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. When I open Chromium with a temporary profile, the window opens, but as soon as I enter "No thanks" to the option of signing in with Google, it crashes as above. ** Affects: chromium-browser (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/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699460] Re: Jetty - Service killed by signal 11
This issue looks to have been resolved in linux-image-3.13.0-123-generic uname -a Linux dev.ha247.co.uk 3.13.0-123-generic #172-Ubuntu SMP Mon Jun 26 18:04:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux service jetty restart * Stopping Jetty servlet engine (was reachable on http://dev.ha247.co.uk:8983/). jetty * Jetty servlet engine stopped. jetty [ OK ] * Starting Jetty servlet engine. jetty /etc/init.d/jetty: 274: /etc/init.d/jetty: /usr/sbin/rotatelogs: not found * Jetty servlet engine started, reachable on http://dev.ha247.co.uk:8983/. jetty[ OK ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699460 Title: Jetty - Service killed by signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699460] [NEW] Jetty - Service killed by signal 11
Public bug reported: Please accept my apologies if the below information is vague. Description:Ubuntu 14.04.5 LTS Release:14.04 Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39 After upgrading to linux-image-3.13.0-121-generic, jetty fails to start. /var/log/jetty/out.log shows "Service killed by signal 11" Reverting to linux-image-3.13.0-119-generic resolves the issue. Packages installed for Jetty ii jetty 6.1.26-1ubuntu1.1 all Java servlet engine and webserver ii libjetty-java 6.1.26-1ubuntu1.1 all Java servlet engine and webserver -- core libraries ii default-jdk 2:1.7-51 amd64Standard Java or Java compatible Development Kit ii openjdk-7-jdk:amd64 7u131-2.6.9-0ubuntu0.14.04.2 amd64OpenJDK Development Kit (JDK) ii openjdk-7-jre:amd64 7u131-2.6.9-0ubuntu0.14.04.2 amd64OpenJDK Java runtime, using Hotspot JIT ii openjdk-7-jre-headless:amd64 7u131-2.6.9-0ubuntu0.14.04.2 amd64OpenJDK Java runtime, using Hotspot JIT (headless) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-121-generic 3.13.0-121.170 ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39 Uname: Linux 3.13.0-121-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 21 09:41 seq crw-rw 1 root audio 116, 33 Jun 21 09:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 68.188736] random: nonblocking pool is initialized Date: Wed Jun 21 10:21:28 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-10-25 (238 days ago) InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-121-generic root=/dev/mapper/ubuntu--vg-root ro ProcModules: floppy 69418 0 - Live 0xa000 lp 17759 0 - Live 0xa004b000 parport 42348 1 lp, Live 0xa003f000 psmouse 106692 0 - Live 0xa0019000 serio_raw 13462 0 - Live 0xa0035000 RelatedPackageVersions: linux-restricted-modules-3.13.0-121-generic N/A linux-backports-modules-3.13.0-121-generic N/A linux-firmware 1.127.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699460 Title: Jetty - Service killed by signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698599] [NEW] package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: ubuntu 17.04 under vmware player on windows7 trying to set screen resolution when applying setting the error occurred uname -a Linux ubuntu 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: keeper4keys 1742 F pulseaudio Date: Sat Jun 17 16:14:53 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: lono wireless extensions. ens33 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=908533a2-3f36-4f92-9e3b-c6fa2e4b2e82 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698599 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running
I am running Ubuntu 17.04 Unity, and I get "unknown application" in Writer regardless of whether I start it up from the dock or from a document. With Calc, I only get it when starting up from a document. Not sure it matters, but my 17.04 is an upgrade from 16.10, not a fresh install. I have a laptop with 16.04 installed, and I don't get the "unknown application" bug in either Writer or Calc regardless of how I start them up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589215 Title: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1589215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680224] Re: auto.smb fails on Windows administrative shares
And the second part of the patch. ** Patch added: "Part 1/1" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+attachment/4860739/+files/patch_1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680224] Re: auto.smb fails on Windows administrative shares
Ian produced a patch that addresses the problem, at least as far as I've tested it. Whether the target is properly escaped or quoted, it works as expected. The patches (to AutoFS 5.1.2, available from git.kernel.org) are attached and will likely be integrated into AutoFS 5.1.3. ** Patch added: "Patch 0 of 1" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+attachment/4860738/+files/patch_0.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321955] Re: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB)
** Tags added: trusty ** Summary changed: - postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB) + postfixadmin requires non-existant package postgresql-server ** Summary changed: - postfixadmin requires non-existant package postgresql-server + postfixadmin requires non-existant package postgresql-server (should instead require postgresql) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321955 Title: postfixadmin requires non-existant package postgresql-server (should instead require postgresql) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321955] Re: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB)
** Changed in: postfixadmin (Ubuntu Trusty) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321955 Title: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682003] Re: postfixadmin dependencies missing mariadb
** Tags added: trusty xenial ** Changed in: postfixadmin (Ubuntu) Status: Fix Released => In Progress ** Changed in: postfixadmin (Ubuntu) Assignee: (unassigned) => Michael Fox (belldandu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682003 Title: postfixadmin dependencies missing mariadb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1682003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530625] Re: postfixadmin (Trusty) depends on outdated postgresql-server package atom.
*** This bug is a duplicate of bug 1321955 *** https://bugs.launchpad.net/bugs/1321955 ** This bug has been marked a duplicate of bug 1321955 postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530625 Title: postfixadmin (Trusty) depends on outdated postgresql-server package atom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1530625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682003] Re: postfixadmin dependencies missing mariadb
** Description changed: Ubuntu Releases affected Ubuntu 16.04.X LTS (Xenial Xerus) Ubuntu 14.04.X LTS (Trusty Tahr) Currently the package Requires either postgresql or mysql. Mariadb is a dropin replacement for mysql and is made by the same team. Currently postfixadmin will remove mariadb in favor of mysql, this is - mainly due to dependencies not being updated. This has been fixed in - Ubuntu 16.10 (Yakkety Yak). + mainly due to dependencies not being updated. + + This has been fixed in Ubuntu 16.10 (Yakkety Yak) via + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699602 Ubuntu Trusty also has a different bug for this package in that the postgresql package is named something entirely different see https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682003 Title: postfixadmin dependencies missing mariadb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1682003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600555] Re: Postfix Admin depends strictly on pg-client or mysql-client with no option for mariadb-client
*** This bug is a duplicate of bug 1682003 *** https://bugs.launchpad.net/bugs/1682003 ** This bug has been marked a duplicate of bug 1682003 postfixadmin dependencies missing mariadb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600555 Title: Postfix Admin depends strictly on pg-client or mysql-client with no option for mariadb-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1600555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682003] [NEW] postfixadmin dependencies missing mariadb
Public bug reported: Ubuntu Releases affected Ubuntu 16.04.X LTS (Xenial Xerus) Ubuntu 14.04.X LTS (Trusty Tahr) Currently the package Requires either postgresql or mysql. Mariadb is a dropin replacement for mysql and is made by the same team. Currently postfixadmin will remove mariadb in favor of mysql, this is mainly due to dependencies not being updated. This has been fixed in Ubuntu 16.10 (Yakkety Yak). Ubuntu Trusty also has a different bug for this package in that the postgresql package is named something entirely different see https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955 ** Affects: postfixadmin (Ubuntu) Importance: Undecided Status: Fix Released ** Description changed: Ubuntu Releases effected Ubuntu 16.04.X LTS (Xenial Xerus) Ubuntu 14.04.X LTS (Trusty Tahr) - Currently the package Requires either postgresql or mysql. + Currently the package Requires either postgresql or mysql. Mariadb is a dropin replacement for mysql and is made by the same team. Currently postfixadmin will remove mariadb in favor of mysql, this is mainly due to dependencies not being updated. This has been fixed in Ubuntu 16.10 (Yakkety Yak). Ubuntu Trusty also has a different bug for this package in that the - postgresql package is named something entirely different see #1321955 + postgresql package is named something entirely different see + https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955 ** Description changed: - Ubuntu Releases effected + Ubuntu Releases affected Ubuntu 16.04.X LTS (Xenial Xerus) Ubuntu 14.04.X LTS (Trusty Tahr) Currently the package Requires either postgresql or mysql. Mariadb is a dropin replacement for mysql and is made by the same team. Currently postfixadmin will remove mariadb in favor of mysql, this is mainly due to dependencies not being updated. This has been fixed in Ubuntu 16.10 (Yakkety Yak). Ubuntu Trusty also has a different bug for this package in that the postgresql package is named something entirely different see https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955 ** Changed in: postfixadmin (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682003 Title: postfixadmin dependencies missing mariadb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1682003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1321955] Re: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB)
I would rather make it less confusing for others if possible. So i will do what you said. On Apr 11, 2017 11:49 PM, "Nish Aravamudan" wrote: > As to mariadb, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778794 > is the Debian bug, and was fixed in 2.93-1, which is in 16.10 and on. > > I would suggest, I think, for clarity's sake (and to make the SRU easier > to verify) that a second bug be opened which will have tasks for 14.04 > and 16.04 for allowing mariadb and this bug be used to just fix 14.04's > postgresql-server issue. > > You are welcome, however, to use just this bug for both, I think it will > just be a bit more confusing to the SRU team. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1321955 > > Title: > postfixadmin dependencies not well defined (requires mysql-server or > postgresql, removes MariaDB) > > Status in postfixadmin package in Ubuntu: > Fix Released > Status in postfixadmin source package in Trusty: > New > > Bug description: > I have postgresql-9.3 installed (the DB server). > When I try to install postfixadmin, apt wants to install mysql-server. I > can't install it without installing mysql-server! > > It looks as if the postfixadmin requires either the package "mysql- > server" or "postgresql-server", however there is no package > "postgresql-server" in Ubuntu trusty. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+ > bug/1321955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321955 Title: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1321955] Re: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB)
I was however planning to fix both On Apr 11, 2017 11:49 PM, "Nish Aravamudan" wrote: > As to mariadb, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778794 > is the Debian bug, and was fixed in 2.93-1, which is in 16.10 and on. > > I would suggest, I think, for clarity's sake (and to make the SRU easier > to verify) that a second bug be opened which will have tasks for 14.04 > and 16.04 for allowing mariadb and this bug be used to just fix 14.04's > postgresql-server issue. > > You are welcome, however, to use just this bug for both, I think it will > just be a bit more confusing to the SRU team. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1321955 > > Title: > postfixadmin dependencies not well defined (requires mysql-server or > postgresql, removes MariaDB) > > Status in postfixadmin package in Ubuntu: > Fix Released > Status in postfixadmin source package in Trusty: > New > > Bug description: > I have postgresql-9.3 installed (the DB server). > When I try to install postfixadmin, apt wants to install mysql-server. I > can't install it without installing mysql-server! > > It looks as if the postfixadmin requires either the package "mysql- > server" or "postgresql-server", however there is no package > "postgresql-server" in Ubuntu trusty. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+ > bug/1321955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321955 Title: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321955] Re: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB)
I'm tired of this not being fixed. So i'm fixing it myself. ** Changed in: postfixadmin (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321955 Title: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321955] Re: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB)
Wow 3 years no fix ** Changed in: postfixadmin (Ubuntu) Assignee: (unassigned) => Michael Fox (belldandu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321955 Title: postfixadmin dependencies not well defined (requires mysql-server or postgresql, removes MariaDB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1321955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680224] Re: auto.smb fails on Windows administrative shares
Thanks Josh. I actually tried using ASCII codes for the characters the day I filed the report. No dice. I've managed to make contact with Ian, an (the?) autofs maintainer. He thinks he's narrowed the problem down to a particular commit. If we make any progress, I'll share it here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680224] Re: auto.smb fails on Windows administrative shares
Experimenting with this a bit, shares with spaces in their names work fine, but anything with $ or & fails. Ampersands are particularly troublesome, crashing the automounter if not escaped properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680224] [NEW] auto.smb fails on Windows administrative shares
Public bug reported: This is probably related to #385244. I've been unable to get a Windows administrative share (ie. C$) mounted through Autofs. Non-administrative shares work fine. Administrative shares are accessible with the same credentials from other Windows 10 workstations and through smbclient on Ubuntu (16.04 LTS) machines. Administrative shares can even be mounted using the same credentials via mount on the command-line. However, autofs will not mount the same shares, using the same credentials, on the same Ubuntu machine. Administrative shares are listed under /cifs/WindowsHostName, but a cd /cifs/WindowsHostname/C$ results in "-bash: cd: C$: No such file or directory" from the shell and the following output from 'automount -f -v': - attempting to mount entry /cifs/WindowsHostname/C$ >> Retrying with upper case share name >> mount error(6): No such device or address >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) mount(generic): failed to mount //WindowsHostname/C\$ (type cifs) on /cifs/WindowsHostname/C$ failed to mount /cifs/WindowsHostname/C$ - Notice that mount complains of failing to mount 'C\$' rather than 'C$'. If the bit of awk script that escapes the $ is removed, it then fails to mount 'C', which is also no good. I think if we could actually get mount to try to mount 'C$', it would work. ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Tags: autofs automount cifs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591137] Re: sudo ignores shortname aliases in sudoers file
We are experiencing the same symptoms with sudo (v1.8.16) as have been previously reported in this bug. On an Ubuntu 16.04 system short hostnames don't work in the sudoers file when the 'fqdn' option is true (as it is by default). The documentation indicates that the short form should still work with the fqdn option set. Steps to reproduce: On a system called 'ubuntu1604.example.com', put the following into sudoers: %john ubuntu1604=(root) NOPASSWD: /bin/true %john ubuntu1604.example.com=(root) NOPASSWD: /bin/false Expected outcome: sudo -l shows user 'john' is allowed to run: (root) /bin/true (root) /bin/false Actual outcome: sudo -l shows user 'john' is allowed to run: (root) /bin/false sudo -l -U john -h ubuntu1604 shows user 'john' is allowed to run: (root) /bin/false sudo -l -U test -h ubuntu1604.example.com shows user 'john' is allowed to run: (root) /bin/true (root) /bin/false -- Sudo version 1.8.16 Configure options: --prefix=/usr -v --with-all-insults --with-pam --with-fqdn --with-logging=syslog --with-logfac=authpriv --with-env-editor --with-editor=/usr/bin/editor --with-exampledir=/usr/share/doc/sudo/examples --with-timeout=15 --with-password-timeout=0 --with-passprompt=[sudo] password for %p: --without-lecture --with-tty-tickets --disable-root-mailer --enable-admin-flag --with-sendmail=/usr/sbin/sendmail --with-rundir=/var/run/sudo --mandir=/usr/share/man --libexecdir=/usr/lib/sudo --with-sssd --with-sssd-lib=/usr/lib/x86_64-linux-gnu --with-selinux --with-linux-audit Sudoers policy plugin version 1.8.16 - root@bs-ubuntu1604:~# uname -a Linux bs-ubuntu1604 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux - root@bs-ubuntu1604:~# cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 bs-ubuntu1604.ethz.ch bs-ubuntu1604 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters root@bs-ubuntu1604:~# hostname bs-ubuntu1604 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591137 Title: sudo ignores shortname aliases in sudoers file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1591137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567807] Re: nova delete doesn't work with EFI booted VMs
+1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567807 Title: nova delete doesn't work with EFI booted VMs To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1567807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527590] Re: Menu isn't shown in gedit when run with sudo
Same problem. New install of 16.04.1. $ gedit --> shows menu $ sudo gedit --> does NOT show menu $ gksudo gedit --> does NOT show menu $ sudo -i ... # gedit --> does NOT show menu This happens whether the menus are set for the title bar OR for the top of the screen. Tried reinstalling gedit. No difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527590 Title: Menu isn't shown in gedit when run with sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
