[Bug 1266675] Re: newusers error adding more than one user
I can confirm this bug is still present in 16.04.3 single line import fine, multiple not -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1266675 Title: newusers error adding more than one user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1266675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466926] Re: reload apache2 with mpm_event cause scoreboard is full
Yes this is impacting on Xenial - when will this be backported to currently supported LTS releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466926 Title: reload apache2 with mpm_event cause scoreboard is full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers
for me the fix on #1631098 seems to work on my desktop i only have an nvidia card no laptop dual GFX hybrid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631089] Re: gdm3 depends on ubuntu--gnome-default-settings but is not listed as such in 16.04
For me on my desktop this did the trick for me (i only have an nvidia card no laptop dual GFX hybrid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631089 Title: gdm3 depends on ubuntu--gnome-default-settings but is not listed as such in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1631089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632322] Re: Computer never gets to the GDM3 login screen when nvidia- is installed
*** This bug is a duplicate of bug 1559576 *** https://bugs.launchpad.net/bugs/1559576 for me the fix on #1631098 seems to work on my desktop i only have an nvidia card no laptop dual GFX hybrid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632322 Title: Computer never gets to the GDM3 login screen when nvidia- is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1632322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
is now a bad time to say i've been apt updating for some time just fine now, my previous instructions should still be accurate: i can confirm that To fix the uboot error, you have to change the config.txt lines: # set extended DT area #device_tree_address=0x100 #device_tree_end=0x8000 device_tree_address=0x02008000 commented device_tree_end out and made sure device_tree_address was the correct value (0x02008000) fixes things for me - currently booting into 1042 i note that the flash-kernel and linux-firmware-raspi2 updates recently accounted for changing the device_tree_address but neither comment or hide device_tree_end - i suspect if you worked out the correct value for this then it would also still work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
i can confirm that To fix the uboot error, you have to change the config.txt lines: # set extended DT area #device_tree_address=0x100 #device_tree_end=0x8000 device_tree_address=0x02008000 commented device_tree_end out and made sure device_tree_address was the correct value (0x02008000) fixes things for me - currently booting into 1042 i note that the flash-kernel and linux-firmware-raspi2 updates recently accounted for changing the device_tree_address but neither comment or hide device_tree_end - i suspect if you worked out the correct value for this then it would also still work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
I also went down the root of https://bugs.launchpad.net/ubuntu/+source /linux-raspi2/+bug/1652270/comments/27 without success i note specifically also that the PPA (https://launchpad.net/~ubuntu- raspi2/+archive/ubuntu/ppa-rpi3/) has updated packages for flash-kernel and linux-firmware-raspi2 which actually rolls in the changes mentioned in #1636838 as well as extending the change further and it doesn't fix this - i suspect its barking up the right tree though - issue seems to be not the kernel but the dtb and the address references - just trying to find the correct values that work and its proving time consuming so far for my u-boot novice brain -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
for those that are are in the unbeatable state - the way to recover without data loss pending fixed kernel either mount the ubuntu raspberry pi image or write it to another SD card, copy the files from the small boot partition (i did all to be safe) e.g. boot.scr vmlinuz etc to a folder on your machine or better still to the sd card of the failing install and overwrite the original files (take a backup first) - this will allow you to reboot into the older kernel and to properly cleanup the 1038 version until its fixed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
By image i mean the one available here: https://wiki.ubuntu.com/ARM/RaspberryPi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
i note in removing these problem packages and downgrading to 1034 that there appears to be different subversions of the 1038 build root@piserver2:~# apt-get purge linux-image-4.4.0-1038-raspi2 linux-headers-4.4.0-1038-raspi2 linux-raspi2-headers-4.4.0-1038 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-1038-raspi2* linux-headers-raspi2* linux-image-4.4.0-1038-raspi2* linux-image-raspi2* linux-raspi2* linux-raspi2-headers-4.4.0-1038* 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded. After this operation, 182 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 95924 files and directories currently installed.) Removing linux-raspi2 (4.4.0.1038.37) ... Removing linux-headers-raspi2 (4.4.0.1038.37) ... Removing linux-headers-4.4.0-1038-raspi2 (4.4.0-1038.45) ... Removing linux-image-raspi2 (4.4.0.1038.37) ... Removing linux-image-4.4.0-1038-raspi2 (4.4.0-1038.45) ... where as the 1034 build the sub versions all match for the relevant packages: 4.4.0-1034.41 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
