perhaps the dependency of fwupd-signed should be to fwupd-unsigned
instead of fwupd itself?
the fwupd-signed/jammy-proposed 1.41+1.1-3 amd64 version required fwupd
1.1-3 but only the fwupd-unsigned package has that version..
--
You received this bug notification because you are a member of
the complete message .. during a second upgrade completion attempt
Do you want to continue? [Y/n] y
Setting up openssh-client (1:8.7p1-3) ...
update-alternatives: and can't be the same
Use 'update-alternatives --help' for program usage information.
dpkg: error processing package openssh-client
grub-efi-am64-signed/bin 2.06-2ubuntu3 update works as expected .. thank
you for fixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954566
Title:
jammy-proposed grub-efi-amd64-signed 1.175+2.06
I had same EFI error: out of memory error: you need to load the kernel
first.
as I am using a "real pc" not a VM
my question now is why would "set debug=all" fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
note: booting windows partition is not affected .. only linux partitions
fail to boot when debug is off .. i.e. normal state ..
if another grub menu item is selected to boot linux w/o debug turned on
it fails as described earlier .. lack of kernel memory etc.
--
You received this bug
ok tried that .. to reduce the data spew I added: set pager=1 and set
debug=all lines to the first grub menu selection .. this turns debugging on
only if this menu is selected .. and although we got lots of output .. boot was
normal ..
if these lines were removed boot failed again .. this
filed bug #1954566
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953490
Title:
keep grub 2.06 in proposed
To manage notifications about this bug go to:
Public bug reported:
grub-efi-amd64-signed/jammy-proposed,now 1.175+2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
on boot: select a bootable partition, error appears ...kernel file not
loaded please load kernel first.. enter to continue .. hp
FYI Jammy-proposed testing issues
grub-efi-amd64-bin/jammy-proposed,now 2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
grub-efi-amd64-signed/jammy-proposed,now 1.175+2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64
So why does ubiquity not recognize that it is installing on an mbr
partitioned disk? and adjust accordingly.. seems rather wrong that the
install all fails at the install of grub .. especially as everything
else is ok..
also stealing 500 MB for an efi partition when it is not needed is
rather a
confirmed that manual partition selection install without EFI fat32 partition
present will fail on grub install .. due to install media EFI fat32 partition
being substituted into new install fstab ..
autobug report generated .. with "duplicate of bug 1922105" title
** Changed in: ubiquity
hirsute daily apr 5, 2021 xubuntu still has bug 1922105 for manual
partitioning grub fails to install if EFI partition is not present
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922571
Title:
Public bug reported:
as per bug 1922105
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.13
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
this bug appears to be fixed in xubuntu apr 5, 2021 hirsute daily build
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
fix only present if auto resize is used .. will still fail with manual
resizing.
Auto resize adds a EFI fat32 partition during the resize. this prevents
the grub install failure.
if an EFI partition is not present the installer will fail ..
--
You received this bug notification because you are
Artifacts left behind..
incomplete grub-install .. fixed with via a chroot -> grub-install
--target i386-pc /dev/sda
Reference to usbstick efi partition in fstab prevents boot .. fixed
commented out in /etc/fstab
then normal boot proceeds .. everything else appears normal
--
You received
this bug is still not dead .. this is a duplicate of other reports
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922105
Title:
Installer crashed (grub not installed) on bios/mbr based system ..
Public bug reported:
Hirsute xubuntu daily march 31,2021 pre?beta
lenova sl500 intel graphics core2
already running hirsute on another partition
This is a test install
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.12
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic
rtl8821ce package was as rtl8821ce-dkms-5.5.2.1-0ubuntu4~20.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of rtl8821ce-dkms fails with linux-5.10 kernel version and new
okay .. I installed focal 20.4.2.0 (xubuntu) along side hirsute on a
separate partition ..
used a edimax usb wireless dongle to do the install and updates of focal
..
added proposed to apt sources .. then installed rtl8821ce-dkms as well
as other updates
rebooted (without usb wi/fi) and
yes that works I now have use of the rtl8821ce wireless connection
again..
thank you!
How soon will this be merged with hirsute?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
this did not get uploaded automatically: rtl8821ce-dkms.0.crash
** Attachment added: "rtl8821ce-dkms.0.crash"
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1911605/+attachment/5454939/+files/rtl8821ce-dkms.0.crash
--
You received this bug notification because you are a member of
other newer antenna styles also unsupported by rtw88_8821ce firmware..
it appears that rtl8821ce-dkms is antenna and firmware agnostic and work
for kernels 5.8 and lower .. at least one site has a module that fixes
the symbol issue and allows compilation of an rtl8821ce module ..
It appears that firmware for rfc2 type antenna is not yet available as
per comment #2 at following link:
https://forum.siduction.org/index.php?topic=8134.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
note: same firmware appears to work for kernel 5.8 versions using
rtl8821ce-dkms .. no errors appear in dmesg ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of
problem appears to be firmware name miss-match .. according to other
reports the firmware is not up to date or older/newer chip sets are not
supported this effects wifi and bluetooth (dual function chip)
did a
modprobe -r rtw88_8821ce
modprobe rtw88_8821ce
dmesg .. tail ..
[ 208.374092]
modules are loaded but are not functioning .. dkms registration was
required with previous modules is some kind of registration required for
the newer modules?
(an alternate usb wireless nic does work so everything else is ok)
** Summary changed:
- rebuild of rtl8821ce-dkms fails with
seems there is a kernel module now for rtl8821ce ..rtw88_8821ce .. but
it does not function .. (dkms removed from system)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of
Public bug reported:
upgrade to 5.10 kernel headers causes rebuild of rtl8821ce-dkms to fail
due to missing symbols as per make.log
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: rtl8821ce-dkms 5.5.2.1-0ubuntu4
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1890978
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324
relevant info:https://bugs.launchpad.net/ubuntu/+source/grub-
installer/+bug/1890978/comments/4
--
You received this bug notification because you are a
discovered during a manual partitioning install ..
found that fstab had an entry for /boot/efi mount vfat type pointed to
the /dev/sdb2 efi partition of the install media (USB)
deleted the fstab entry..
also deleted the mount point /boot/efi as no EFI partition existed on
an MBR based system
had a quick look at the diff file between ubuntu thinderbird versions
78.2.1 and 78.2.2 .. there is a massive amount of deleted lines .. a lot
to do with twitter accounts .. is this on purpose or has something gone
amiss ..
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Happened on upgrade from 78.2.1 to 78.2.2 lost all folder views ..
Groovy .. regular updates via proposed..etc. (xubuntu flavour)
Installed thunderbird 78.2.2 from thunderbird.net into personal home
directory works properly..
so it is an ubuntu regression issue ..
** Attachment added: "Xorg.0.log for information"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1873318/+attachment/5355667/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Processor : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
Memory : 10112MB (985MB used)
-Display-
Resolution : 1600x900 pixels
OpenGL Renderer : AMD RAVEN2 (DRM 3.35.0, 5.4.0-24-generic, LLVM 9.0.1)
X11 Vendor : The X.Org Foundation
note when booting through recovery mode and then starting xubuntu the
user screen is normal no staircasing.. (different graphic driver)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873318
Title:
** Attachment added: "a view of the screen with xfwm4 running"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1873318/+attachment/5355662/+files/Screenshot_2020-04-16_13-27-01.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
This happens under xubuntu and lubuntu (if using xfwm4 as window manager
instead of openbox)
with the latest update xfwm4-4.14.1-0ubuntu1 ..
previoius version had no issues..
first happened under xubuntu installed lubuntu to determine if graphic
driver was the issue but
having multiple real installs on a computer of different versions of
linux (ubuntu spins, lts, development versions) allows testing in a real
environment .. as opposed to a vm .. was a standard practise prior to
vm's existing
--
You received this bug notification because you are a member of
I was try to reproduce the bug on the same computer .. by adding another
install .. on another partition .. that worked .. bug was reproducible
..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
When I pass the device it shuts up..
OKAY .. my initial report was bug 1872097 my original and still existing
install partition (sda5) for focal ( dec 2019) I used dpkg-reconfigure
there and of course then debconf-get-selections did not give the correct
info ..
So I created a new partition
ok: grub-install --target=x86_64-efi /dev/sda
works properly... sorry for the noise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
Title:
package grub-efi-amd64-signed 1.140+2.04-1ubuntu24
going back to the previous partition (trying to make it the default again)
I ran the following:
grub-install /dev/sda
Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device
/dev/sda2.
grub-install: warning: disk does not exist, so
opps dropped a line at the end:
grub-install: error: disk `hostdisk//dev/sda2' not found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
Title:
package grub-efi-amd64-signed
on a fresh install on a new partition of focal fossa (03/28) on
upgrading during the first boot into the install came across the same
error
did not "continue the install of grub-efi" so the disk was not altered
installed debconf-utils then ran debconf-get-selections | grep grub-efi
gave the
this crash happened to me on a fresh install of focal while doing the
first software update.
Blueman-applet was running in the panel and apparently is running again
after the crash ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From bug#1872097
Ran sudo dpkg-reconfigure grub-efi-amd64-signed
response was confusing .. but I approved the install and everything appears to
boot normally.
after installing debconf-utils ran command from comment#2 above.
sudo debconf-get-selections | grep grub-efi
grub-pc
*** This bug is a duplicate of bug 1872077 ***
https://bugs.launchpad.net/bugs/1872077
If I run dpkg-reconfigure it will install correctly .. but the
confirmation message is confusing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
still running previous version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872097
Title:
grub-efi-amd64-signed 1.140+2.04-1ubuntu24 throws an error during set-
up
To manage notifications
Public bug reported:
An upgrade to this version failed
Fails with the following ..
Setting up grub-efi-amd64-signed (1.140+2.04-1ubuntu24) ...
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate
after update .. not rebooted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860851
Title:
blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't
decode byte 0x8e in position 4:
Public bug reported:
related to bug 1870858.. similar fault different program (parole)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vlc 3.0.8-4
ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
Uname: Linux 5.4.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture:
running apt --fix-broken install
does not fix the issue:
The following additional packages will be installed:
libvte-2.91-common
The following packages will be upgraded:
libvte-2.91-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need
fixed during/ or by the linux-5.4.0-13 kernel release
** Changed in: linux-signed-5.4 (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/1860561
Title:
cpu
Public bug reported:
similar to previous issue with 5.4.0-11 cpu lockups note plymouth only
runs in terminal mode instead of graphic mode .. prior to lockups .. 22
seconds watch dog show alerts for systemd-udevd on cpu1 , [migration]
processes 1,2,3 on cpu 2,3,4 this repeats every 22 seconds
a
Public bug reported:
version linux-image-5.4.0-11-generic fails to boot at leat two cpu
lock ups 2 and plus hardware failures
version linux-image-5.4.0-9-generic works fine
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-11-generic 5.4.0-11.14
ProcVersionSignature:
Public bug reported:
system problem at login a few seconds after xfce desktop appears
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-browsed 1.26.0-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
A work around exists .. at the pause .. do you want to continue? in
another terminal manually edit /etc/apt/sources.list to change all eoan
to focal ..save then press y to proceed and everything proceeds normally
..
my comment #9 was incorrect the first list shown is eoan then the
sources are
In fact in comment #7 the first package list after opening focal.tar.gz
should be based on focal as well ..
so the focal.tar.gz appears to be a renamed eoan.tar.gz not the true
focal upgrade core.. !!!
what happened!!! .. I know the mirrors were messed-up nov 1-nov2 ..
did other files get
appears to be using eoan package sources for focal upgrade..
first check normal state of apt update to eoan for reference:
derk@zlink1 ~ $ sudo apt update
Hit:1 http://ca.archive.ubuntu.com/ubuntu eoan InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu eoan-updates InRelease
Hit:3
happened while attempting to add an app to an an existing launcher menu
list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/92787
Title:
[apport] xfce4-panel crashed with SIGSEGV in g_slice_alloc()
Fine tuning: only one extra mount is necessary .. then plymouth
finishes very quickly .. and xorg/lightdm start normally!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
lightdm
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
--
You received this bug notification because you
okay I have another solution to the timing issue .. add two partition
mounts to fstab ..
my existing sda1 disco install has /home (sda2) and /home/store1 (sda5)
mounted via fstab .. this was the original install configuration .. thus
always a mount delay ..
to test .. added the same partions
of course the sda1 partition (on the SSD) has never failed to work properly no
matter which grub source (installs on sda1,sda6,sda7,sda8,sda9) is used
plymouth always appears when sda1 boots..
this disco version was installed jan 10 with a bootstrap log date of oct 13,
2018 .. it has been
okay turned back the clock .. to a spinning metal disk previously
installed in this hardware .. ran a number of test installs all work
fine .. cosmic/bionic/disco early version disco final all work boot
normally .. always ..
thus conclusion is a SSD is very fast and can respond to requests sooner
video of sda9 boot using sda9 install of grub (native grub) .. note absence of
plymouth .. flash at top edge of screen was missed .. note brief appearance of
lightdm .. short gap then lightdm reappears .. xorg.0.log.old records the
crash .. similar to others above
xorg.0.log records
video of sda8 non-native grub boot (a disco-xubuntu iso install) sda9
has installed grub (also a disco-xubuntu iso install ) will show in
next video uploaded
note the red flash .. plymouth attempt to start .. then cursor appears
and then lightdm briefly
** Attachment added: "video of failing
I will try to do videos for you tomorrow it is getting late in the day
here ..
a brief synopsis for now ..
history: this is standard grub arrangement as "installed by default"
used to work flawlessly with multiple partitions of various linux OS's
.. It is only since early march that I noticed an
bug is still present in disco xubuntu iso "final" 04-13.1-2019
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
lightdm login screen briefly appears and then blanks out on Intel(R)
okay a previous "fresh install that was crashing plymouth
screen/lightdm/xorg was fixed by copying a known working set of netplan
conf files into /etc/netplan ..
the 01-netcfg.yaml from the "network install" uses networkd as the
renderer .. with a working network device config.. plus the
okay I stumbled across something .. the network install .. used netplan
to set-up my wifi connection to start on boot .. so as soon as systemd
networkd starts wifi is started NetworkManager thus has no access or
anyway to try for other networks.. so I tried to change this.. If I edit
the config
An additional data point for reference .. did a netboot install of
xubuntu using "daily" amd64 netboot mini.iso .. base install followed
by taskselect install of xubuntu ..
boots normally plymouth and lightdm screens appear as expected .. also
switching to foreign grub .. it still boots
okay apr 8 and apr 9 iso's have same issues kept logs of various boots
into the fresh installs .. no change in grub-source during testing was
made .. all with fresh installs
typical first boot is normal .. no crash of xorg on first start ..
second boot shows lightdm briefly then xorg crashes
third boot of same install ..
** Attachment added: "third reboot of fresh install xorg.0.log.old --
slighjtly different"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5253548/+files/Xorg.0.log.old
--
You received this bug notification because you are a
testing xubuntu-disco-daily.iso apr 06, 2019 First boot fine plymouth,
and xorg/lightdm started normally.. did a number of updates and
rebooted.
second boot plymouth not seen, xorg/lightdm appeared briefly .. then
vanished .. then reappears ..
checked xorg.0.log(s) ..
xorg.0.log .. seemed ok
just some summary thoughts in addition to point to some anomalies ..
the "failures in lightdm appear to correspond with shorter journal logs ..
so certain processes are not running as expected ..
plymouth also does not appear on the screen ..
as it needs the proper graphics support ..
--
I've been merrily switching between OS's without this kind of issue for more
than 10 years ..
the behaviour changed recently in the last 30 days ..
it was fine prior to that ..
This is a regression bug and will annoy anyone working with multiple instances
of disco xubuntu for testing..
yes
okay generated the default grub.cfg via sda6 grub-install boot instance
.. vt.handle=1 is set by default for self root boot about a minute to
boot
no change .. still no plymouth on boot but there is a flicker with
lightdm .. which restarts once video mode switch has happened ..
note all grub
whoops added the wrong attachment above it is the one including the
grub-update dialog .. instead of being the bot after the command
** Attachment added: "this one is after the grub-update .. accidental switch"
here is the journalctl boot log for sda6 /zlink4 booted by it's own
install of grub (self grub)
(it was reinstalled for this purpose .. to show it works .. however
plymouth does not show on the screen at all on boot but does on shutdown
)
now one change is addition of a vt.handoff=1 to the end
here we have a normal journalctl boot log .. notice the size .. more
entries .. about 1 minute start to finish source the partition that
always works lightdm starts normally plymouth appears on screen etc.
this one was booted by grub installed by zlink4 - on sda6 ..
** Attachment added: "zlink1
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 (using "foreign grub")
--
You received this
so why the peculiar behaviour that lightdm works when the partition
installed native grub boots the system
BUT not when a grub installed by another partition is used then lightdm
consistently crashes and the machine locks up..
BUT if i915 is added to /etc/modules in the offending partition it
a little digging and plymouth is supposed to work with drm modesetting
drivers which means i915 has to be loaded for it to work .. so not
seeing it means ..some hardware detection has failed .. is that part of
plymouth or something else?
since it works on the upgraded install on sda1 I suspect a
Kernel module will load if added to /etc/ modules .. I have my sda1
partition running kernel 5.0.0-8.9 as are the iso's tested recently .. my
sda1 partition loads i915 without using /etc/modules.. I notice that the
recent isos do not show Plymouth progress screen at startup..is that
relevant?
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
--
You received this bug notification because
now this begs the question why does kernel module i915 not auto load anymore?
i.e. the newer iso's since mid-march ..??? what got yanked out that would cause
this ??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
okay .. thought about this for a bit i915 compiled as module by default
in kernel sources.. lets force it to load..
added module i915 to /etc/modules to force loading .. it is the only
entry ..
reboot into the problem install .. and no problems .. lightdm starts and stays
going.
no flicker or
okay after rebooting via grub installed by sda1 .. as before .. red
flash (no plymouth) lightdm briefly displays login screen .. then
underline cursor then blank screen.
attached is zl10-boot2-xorg.0.log xorg.0.log.old is now the already
uploaded zl10-xorg.0.log above
a crashing time is
iso april 2 2019 tested .. adding xorg.0.log & xorg.0.log.old files from
first boot into fresh install .. There was a 1 to 2 second flicker in
lightdm appearing then blanking and then reappearing on first boot ..
have not yet rebooted into this from grub as installed by sda1 .. wanted
to save
the " surprise log file " not expected on a first boot .. with normal
xorg startup should not exist ..
** Attachment added: "zl10-xorg.0.log.old -- first boot (inital xorg-server
start which flickered lightdm?)"
xubuntu iso for daily april 1, 2019 .. no change
installed iso reboots into the install partition everything works as normal..
reboot into sda1 .. grub-install /dev/sda then update-grub then reboot .. back
into the fresh install partition ..
same behaviours as before .. red flash no visible
oh one thing I noticed and did not mention .. the plymouth screen fails
to appear (just a redish flash at top of screen) when booting from a
non-native grub for the recent daily xubuntu iso's if the native grub
is used plymouth screen appears..
for sda1 boot from any grub a plymouth screen
stranger and stranger .. if you install kernel 5.0.0-8.9 at the first
boot into any new install partition before changing any thing else .. it
does not fix the issue .. once you return sda1 to being grub master ..
neither sda7 nor sda6 will keep lightdm running ..both briefly flash
lightdm login
okay still bug present in xubuntu-disco-amd64-desktop-beta.. still uses
kernel 5.0.0-7
updating from proposed with kernel 5.0.0-8.9 it works properly
i.e. any linux os partion can be used to install grub and another partion with
linux can be
selected and boot normally
e.g. beta install is
** This bug is no longer a duplicate of bug 1819943
intel video driver not installed by default in ubuntu 19.04 (Disco) [needed
for graphics support on Intel Core 2 Duo systems]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
addional clarification .. if sda6 (recovery booted or chrooted)
installed grub then sda6 boots with some brief flashing normally. if
sda7 or sda1 (recovery booted or chrooted or a normal boot for sda1)
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
this effected only the more recent installs
you have miss understood the details in the initial report .. the system
would boot normally as long as the grub used (installed) was from the
install partition
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
** Summary changed:
- lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
--
You
1 - 100 of 124 matches
Mail list logo
