[Bug 213086] Re: firefox 3.0b5 goes uninterruptible for a few seconds during normal browsing
I can confirm this happens on a regular 32 bit system as well, HP dv6000 with a fully updated hardy and FF 3b5. Only started happening in the last 2/3 days (April 20th ish) and I've been on Hardy Beta for weeks, keeping up with all updates. -- firefox 3.0b5 goes uninterruptible for a few seconds during normal browsing https://bugs.launchpad.net/bugs/213086 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213086] Re: firefox 3.0b5 goes uninterruptible for a few seconds during normal browsing
Additionally, Firefox 3b5 was working fine before the 20th, and works fine on my Windows Box at work, so I'm reluctant to blame the bug on Firefox. -- firefox 3.0b5 goes uninterruptible for a few seconds during normal browsing https://bugs.launchpad.net/bugs/213086 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 533109] Re: Icon missing for notification flash when indicator applet isn't used.
daspooky's fix isn't right. In case it isn't clear, in the notification area, when you receive a message, the green circle state of the blink is there, but the other state is not. I believe the other state is a little white speech bubble. With that fix, it's just the green circle the whole time, there's no blink. I don't understand why...the symlink is correct and has the right icon, but it isn't working. -- Icon missing for notification flash when indicator applet isn't used. https://bugs.launchpad.net/bugs/533109 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392015] Re: Cannot export banshee playlist
I have been getting this error. I ran Banshee from the command line with --debug-addins trying to see the output, and I no longer got the error. I close banshee and re-open it normally, no error. -- Cannot export banshee playlist https://bugs.launchpad.net/bugs/392015 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857789] Re: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt.
Thank you, I will mark it. ** Also affects: subiquity 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/1857789 Title: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1857789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857789] Re: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt.
The problem is, once I got it fixed I proceeded with the server as I needed to get it into production. I don't have any similar hardware to re-create this on. I'll check the media tonight, but the last install I ran was fixed using manual partitioning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857789 Title: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1857789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586054] Re: package tomcat8 8.0.32-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I just want to indicate that this issue is still happening on Ubuntu Server 16.10. Bryn Jeffries root cause does seem to be likely. Nevertheless, here's my debugging info in case it's useful: Result of "sudo apt-get install tomcat8" Selecting previously unselected package tomcat8. (Reading database ... 322097 files and directories currently installed.) Preparing to unpack .../tomcat8_8.0.32-1ubuntu1.2_all.deb ... Unpacking tomcat8 (8.0.32-1ubuntu1.2) ... Processing triggers for systemd (229-4ubuntu13) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up tomcat8 (8.0.32-1ubuntu1.2) ... Creating config file /etc/default/tomcat8 with new version Adding system user `tomcat8' (UID 142) ... Adding new user `tomcat8' (UID 142) with group `tomcat8' ... Not creating home directory `/usr/share/tomcat8'. Creating config file /etc/logrotate.d/tomcat8 with new version Job for tomcat8.service failed because the control process exited with error code. See "systemctl status tomcat8.service" and "journalctl -xe" for details. invoke-rc.d: initscript tomcat8, action "start" failed. dpkg: error processing package tomcat8 (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (229-4ubuntu13) ... Processing triggers for ureadahead (0.100.0-19) ... Errors were encountered while processing: tomcat8 E: Sub-process /usr/bin/dpkg returned an error code (1) Output of "systemctl status tomcat8.service": ● tomcat8.service - LSB: Start Tomcat. Loaded: loaded (/etc/init.d/tomcat8; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2017-01-18 13:21:14 PST; 1min 53s ago Docs: man:systemd-sysv-generator(8) Jan 18 13:21:09 sr66-blade systemd[1]: Starting LSB: Start Tomcat Jan 18 13:21:09 sr66-blade tomcat8[22023]: * Starting Tomcat servlet engine tomcat8 Jan 18 13:21:14 sr66-blade tomcat8[22023]:...fail! Jan 18 13:21:14 sr66-blade systemd[1]: tomcat8.service: Control process exited, code=exited status=1 Jan 18 13:21:14 sr66-blade systemd[1]: Failed to start LSB: Start Tomcat.. Jan 18 13:21:14 sr66-blade systemd[1]: tomcat8.service: Unit entered failed state. Jan 18 13:21:14 sr66-blade systemd[1]: tomcat8.service: Failed with result 'exit-code'. Relevant output of "journalctl -xe": Jan 18 13:21:09 sr66-blade systemd[1]: Starting LSB: Start Tomcat -- Subject: Unit tomcat8.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tomcat8.service has begun starting up. Jan 18 13:21:09 sr66-blade tomcat8[22023]: * Starting Tomcat servlet engine tomcat8 Jan 18 13:21:14 sr66-blade tomcat8[22023]:...fail! Jan 18 13:21:14 sr66-blade systemd[1]: tomcat8.service: Control process exited, code=exited status=1 Jan 18 13:21:14 sr66-blade systemd[1]: Failed to start LSB: Start Tomcat.. -- Subject: Unit tomcat8.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tomcat8.service has failed. -- -- The result is failed. Jan 18 13:21:14 sr66-blade systemd[1]: tomcat8.service: Unit entered failed state. Jan 18 13:21:14 sr66-blade systemd[1]: tomcat8.service: Failed with result 'exit-code'. Jan 18 13:21:14 sr66-blade systemd[1]: Reloading Content in /var/log/tomcat8/catalina.out -Djava.endorsed.dirs=/usr/share/tomcat8/endorsed is not supported. Endorsed standards and standalone APIs in modular form will be supported via the concept of upgradeable modules. Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586054 Title: package tomcat8 8.0.32-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1586054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463263] [NEW] X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
Public bug reported:
More detail posted here:
http://ubuntuforums.org/showthread.php?t=2281659&p=13300597
surfrock66@sr66-blade:~$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04
I performed an in-place upgrade from 14.10 -> 15.04. Now, GTK apps will
not X11 forward. I was under the impression that Mir would not be in
place until 15.10 which was when I would have probably held back on
upgrading; I believe that other gtk packages have been modified with
hooks in preparation to support Mir, and that these updates have broken
X11 forwarding
Some sample command output from the client I am using to connect from:
surfrock66@sr66-blade:/$ easytag
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(easytag:13278): Gtk-WARNING **: cannot open display:
surfrock66@sr66-blade:/$ baobab
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
surfrock66@sr66-blade:/$ gedit
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(gedit:13348): Gtk-WARNING **: cannot open display:
The server does have an X session running, and I can X11 forward from
other devices so I know my client (X11 server) works.
I've done some research:
http://ubuntuforums.org/showthread.php?t=2266456
http://ubuntuforums.org/showthread.php?t=2256737
x2go still works, but X11 forwarding was a huge part of my workflow and
I'm extremely ticked off, I've been trying to troubleshoot it since the
day 15.04 came out.
Host server is my home server; a Dell poweredge SC 1425 in my server
closet.
I ran tried from 3 clients, got the same results on each:
Debian Sid laptop over the LAN, ssh session using a shortcut created when
it was working on 14.10
Windows work laptop using Cygwin over the WAN, ssh session using a shortcut
created when it was working on 14.10
Windows work laptop using MobaXterm over the WAN, fresh ssh session.
All 3 clients can successfully run an X11 forwarded client from another
computer (all 3 were my System76 desktop running from my house)
I have an alias to connect to my server; the command is "ssh -p -X
IP" and in that, "echo $DISPLAY" returns a blank line. If I get into the
server over x2go or VNC, "echo $DISPLAY" returns :0.
On my laptop (the client machine, with the X11 Server):
surfrock66@sr66-darter:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
On the server (the X11 client):
surfrock66@sr66-blade:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
>From this client laptop, I invoke X-11 forwarded apps in 2 ways; the
aliased ssh connection string, and from a shortcut in my awesomeWM menu.
Here's the strings for both (I blocked the port numbers):
# SSH Shortcuts
alias hda='ssh -p -X hda.surfrock66.com'
alias mc='ssh -p teh3l3m3...@mc.teh3l3m3nts.com'
alias sr66-darter='ssh -p -X 192.168.1.65'
alias sr66-dell='ssh -p -X 192.168.1.47'
#alias sr66-hp='ssh -p 192.168.1.10'
alias sr66-hp='ssh -p -X sr66-hp.hda.surfrock66.com'
alias sr66-nas='ssh -p surfrock66@192.168.1.36'
alias sr76='ssh -p -X sr76.hda.surfrock66.com'
All of them are initiating client sessions that should permit X11
forwarding. Now for the AwesomeWM shortcuts:
myhdaforwardedapps = {
{ "Baobab", "xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
baobab'" },
{ "EasyTag", "xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
easytag'" },
{ "File Manager", "xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
pcmanfm'" },
{ "Terminator", "xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
terminator'" },
}
All of these shortcuts worked before the upgrade.
I am happy to provide any additional information.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: forwarding mir x11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463263
Title:
X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from
14.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1463263/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463263] Re: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
The following mir-related packages are installed: surfrock66@sr66-blade:~/.scripts$ dpkg --get-selections | grep -v deinstall | grep -i mir libmirclient8:amd64 install libmircommon3:amd64 install libmirprotobuf0:amd64 install mir-client-platform-mesa2:amd64 install ** Package changed: ubuntu => mir (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463263 Title: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1463263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463263] Re: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
I kind of suspected Mir was the wrong package, but I had to choose something and it was the closest I could come up with. What package could it be then? This is a change with the upgrade, and it's something trying to hook to mir. It's still broken. X11 forwarding is broken in Ubuntu Server 15.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463263 Title: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1463263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463263] Re: ssh-based X11 forwarding" not working in 15.04 following upgrade from 14.10
** Summary changed: - X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10 + ssh-based X11 forwarding" not working in 15.04 following upgrade from 14.10 ** Summary changed: - ssh-based X11 forwarding" not working in 15.04 following upgrade from 14.10 + ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463263 Title: ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1463263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463263] Re: ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10
Following some feedback here: http://ubuntuforums.org/showthread.php?t=2281659&p=13301326#post13301326 Setup: * remote surfrock66@192.168.1.22 (x-client) * local 192.168.1.65 with X-server running Steps: 1) ssh into a remote system - ssh -p 669 surfrock66@192.168.1.22 2) xhost + 192.168.1.22 # from local machine .65 3) export DISPLAY=192.168.1.65; xterm -sb & Output: surfrock66@sr66-blade:~$ export DISPLAY=192.168.1.65 surfrock66@sr66-blade:~$ xterm -sb & [1] 7050 surfrock66@sr66-blade:~$ xterm: Xt error: Can't open display: 192.168.1.65 These systems are on the same subnet connected to the SAME, unmanaged, switch. No firewalls enabled on either the client or server. Seems, according to the suggestion in that thread, that it's an X11 bug. I will mark it as such. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463263 Title: ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1463263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463263] Re: ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10
** Project changed: mir => xorg-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463263 Title: ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1463263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405424] Re: mod_xml2enc not available
** Package changed: ocsinventory-server (Ubuntu) => apache2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405424 Title: mod_xml2enc not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1405424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522601] [NEW] Querying autofs (systemd-managed nfs) mounts causes kernel hang
Public bug reported: This is Ubuntu Server Wily, fully up to date, on a Dell PowerEdge SC1425. System:Host: sr66-blade Kernel: 4.2.0-19-generic x86_64 (64 bit gcc: 5.2.1) Console: tty dm: lightdm Distro: Ubuntu 15.10 wily I do not know if this is an NFS, autofs, systemd, kernel-related, or something else bug. I have 7 NFS mounts in my /home/surfrock66 directory which come from a FreeNAS NFS server. These have worked fine for years. I recently switched these mounts from NFS to systemd-managed NFS (which as I understand, converts them to autofs). /home/surfrock66/.bitcoinbackup /home/surfrock66/.healtheducation /home/surfrock66/.litecoinbackup /home/surfrock66/.sr66_nas_documents /home/surfrock66/.sr66_nas_music /home/surfrock66/.sr66_nas_pictures /home/surfrock66/Videos These mounts APPEAR to mount correctly and work semi-normally; I have scripts that do automated copies from local folders to there and they succeed. However, if I log into ssh from my account, everything is fine, I end up in /home/surfrock66. if I cd into /home/surfrock66/Downloads and do a ls, I see everything fine. If I then "cd /home/surfrock66" and do an ls...the system COMPLETELY hangs. I cannot open another ssh session. Oddly enough, the web server still responds, and things like subsonic appear to continue working. If I go to an actual keyboard/mouse, I cannot do anything other than wiggle the mouse, no applications launch and I can't switch windows. If I'm tailing syslog in another session, this is the last message I see: Dec 3 13:28:30 sr66-blade kernel: [ 6840.240134] INFO: task ls:2353 blocked for more than 120 seconds. Dec 3 13:28:30 sr66-blade kernel: [ 6840.240143] Not tainted 4.2.0-19-generic #23-Ubuntu Dec 3 13:28:30 sr66-blade kernel: [ 6840.240146] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Dec 3 13:28:30 sr66-blade kernel: [ 6840.240149] ls D 88041fd96640 0 2353 1 0x0004 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240157] 880356147988 0082 88040d66b200 88040c334b00 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240163] 880356147978 880356148000 8800da135da0 8800da135d98 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240168] 88040c334b00 880407422700 8803561479a8 817ec197 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240173] Call Trace: Dec 3 13:28:30 sr66-blade kernel: [ 6840.240186] [] schedule+0x37/0x80 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240191] [] schedule_timeout+0x189/0x250 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240199] [] ? finish_wait+0x59/0x70 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240204] [] ? mutex_lock+0x16/0x40 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240216] [] ? autofs4_wait+0x470/0x860 [autofs4] Dec 3 13:28:30 sr66-blade kernel: [ 6840.240220] [] wait_for_completion+0xb3/0x140 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240225] [] ? wake_up_q+0x70/0x70 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240231] [] autofs4_expire_wait+0x77/0x110 [autofs4] Dec 3 13:28:30 sr66-blade kernel: [ 6840.240235] [] do_expire_wait+0x19b/0x1d0 [autofs4] Dec 3 13:28:30 sr66-blade kernel: [ 6840.240240] [] autofs4_d_manage+0x72/0x190 [autofs4] Dec 3 13:28:30 sr66-blade kernel: [ 6840.240245] [] follow_managed+0x9a/0x2e0 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240248] [] lookup_fast+0x133/0x340 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240252] [] walk_component+0x49/0x2a0 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240255] [] path_lookupat+0x5d/0x110 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240258] [] filename_lookup+0xa9/0x180 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240262] [] ? vfs_getxattr+0x90/0xb0 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240266] [] ? getxattr+0x181/0x200 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240270] [] ? kmem_cache_alloc+0x187/0x200 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240273] [] ? getname_flags+0x56/0x1f0 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240277] [] user_path_at_empty+0x3a/0x50 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240281] [] vfs_fstatat+0x66/0xc0 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240285] [] SYSC_newlstat+0x31/0x60 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240288] [] ? path_getxattr+0x71/0xb0 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240292] [] SyS_newlstat+0xe/0x10 Dec 3 13:28:30 sr66-blade kernel: [ 6840.240296] [] entry_SYSCALL_64_fastpath+0x16/0x75 I have not found a software recovery out of this, it's required a hard poweroff/poweron each time. Here's my /etc/fstab entries UUID=12f7b347-791a-4b95-a9d7-45c726449c51 / ext4errors=remount-ro 0 1 # swap was on /dev/md0 during installation UUID=346555f2-5deb-429b-aee3-cbf91162090b none
[Bug 1857789] [NEW] Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt.
Public bug reported: I am attempting to install Ubuntu Server on a Dell Poweredge R710 server. There is a single RAID-5 volume group. This is a similar hardware configuration to other servers I have successfully deployed (with older releases, all are LTS). I am booting into Legacy mode, not UEFI. I have downloaded the latest Ubuntu Server 19.10 installer as of 12/22/2019. When installing the OS using the default options in the GUI, the install completes "successfully" but immediately boots to GRUB rescue. When going through the installer choosing to update the installer as prompted, again the system boots to GRUB rescue. All partitioning is done accepting the defaults. If I download the most up to date Ubuntu 18.04.3 LTS installer, the system installs and boots fine. Packages update and everything is peachy. If I upgrade to the latest release using do-release-upgrade, the upgrade "completes" successfully, but then immediately boots to GRUB rescue. I can boot into a live environment and chroot into the system and it works fine. My installs, in testing, accept all defaults especially in terms of those related to partitioning. I am not very experienced working in GRUB, so everything after this comes from these guides: https://askubuntu.com/questions/232215/stuck-in-grub-rescue-mode https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/ https://help.ubuntu.com/community/Grub2/Troubleshooting When I ls, I get the following: (hd0) (hd0,gpt2) (hd0,gpt1) If I do "ls (hd0,gpt2)/" I get the contents of my root file system. Inside here, /boot and /boot/grub appear fully populated. If I do "ls (hd0,gpt1)/" I get "Error, unknown file system". When I do "set" I see the following relevant entries: prefix=(hd0,gpt2)/boot/grub root=hd0,gpt2 These appear to be correct. If I do the following, I can get the system to boot to initramfs prompt but not the actual system: insmod normal normal insmod linux linux /vmlinuz root=/dev/sda1 ro initrd /initrd.img boot I have verified that the vmlinuz and initrd.img are there. At this point as far as I can tell, something in the default configuration of Ubuntu Server 19.10 renders the OS un-bootable through GRUB. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: grub server ** Description changed: I am attempting to install Ubuntu Server on a Dell Poweredge R710 server. There is a single RAID-5 volume group. This is a similar hardware configuration to other servers I have successfully deployed (with older releases, all are LTS). I am booting into Legacy mode, not UEFI. I have downloaded the latest Ubuntu Server 19.10 installer as of 12/22/2019. When installing the OS using the default options in the GUI, the install completes "successfully" but immediately boots to GRUB rescue. When going through the installer choosing to update the installer as prompted, again the system boots to GRUB rescue. All partitioning is done accepting the defaults. If I download the most up to date Ubuntu 18.04.3 LTS installer, the system installs and boots fine. Packages update and everything is peachy. If I upgrade to the latest release using do-release-upgrade, the upgrade "completes" successfully, but then immediately boots to GRUB rescue. I can boot into a live environment and chroot into the system and it works fine. My installs, in testing, accept all defaults especially in terms of those related to partitioning. I am not very experienced working in GRUB, so everything after this comes from these guides: https://askubuntu.com/questions/232215/stuck-in-grub-rescue-mode https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/ https://help.ubuntu.com/community/Grub2/Troubleshooting When I ls, I get the following: (hd0) (hd0,gpt2) (hd0,gpt1) If I do "ls (hd0,gpt2)/" I get the contents of my root file system. Inside here, /boot and /boot/grub appear fully populated. If I do "ls (hd0,gpt1)/" I get "Error, unknown file system". When I do "set" I see the following relevant entries: prefix=(hd0,gpt2)/boot/grub root=hd0,gpt2 These appear to be correct. If I do the following, I can get the system - to boot to initramfs prompt: + to boot to initramfs prompt but not the actual system: insmod normal normal insmod linux linux /vmlinuz root=/dev/sda1 ro initrd /initrd.img boot I have verified that the vmlinuz and initrd.img are there. At this point as far as I can tell, something in the default configuration of Ubuntu Server 19.10 renders the OS un-bootable through GRUB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857789 Title: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857789/+subscriptions
[Bug 1857789] Re: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt.
Apologies but I cannot find a way to identify the Ubuntu Server installer by package name; I believe there is a partitioning issue in the installer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857789 Title: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857789] Re: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt.
I believe the partitions are being created in the wrong order. By manually partitioning, I have been able to get a bootable system with the following created in lsblk: sda 8:00 3.7T 0 disk ├─sda1 8:10 1M 0 part └─sda2 8:20 3.7T 0 part / When I was in a chroot environment on the non-booting default partition scheme, the 1M partition was at the end of the drive as sda2. I believe the installer is partitioning the drive incorrectly when accepting the defaults. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857789 Title: Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1985971] Re: Broken domain adminstrator check on ubiquity installer for AD join
Any progress on this? Our company uses admin accounts prefixed with numbers (0 for desktop admin, 1 for server admin, etc). This is still active in the newest releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1985971 Title: Broken domain adminstrator check on ubiquity installer for AD join To manage notifications about this bug go to: https://bugs.launchpad.net/ubiquity/+bug/1985971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
