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-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
l
** 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 ar
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 to
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 updat
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 successful
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 bo
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-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
lightdm login screen briefly appears and then blanks out on In
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 01-netw
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 fi
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 normall
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 whil
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 memb
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 ..
--
You
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 it
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 in
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"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/525
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 o
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 bug
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 all
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 c
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?
On
** 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 y
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-X,
which is subscribed to xorg-server in Ubuntu.
https:/
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 reveale
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
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?)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/52
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 pl
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 appear
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 sc
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 o
** 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-X,
which is subscribed to xorg in 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)
insta
*** 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 received
this bug was filed from sda6 partition..
with this command and the following errors generated
ubuntu-bug
cat: /var/log/lightdm/x-0-greeter.log: No such file or directory
cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory
(/usr/lib/firefox/firefox:5674): dconf-WARNING **: 11:31:0
Public bug reported:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..
back ground .. PC is lenovo sl 500 with evo860 SSD drive
3 partio
Public bug reported:
install proceeded normally (manual partitioning) on reboot failed to
start X session .. rebooted to grub selection screen chose rescue mode
.. from the choices menu ran some checks then did updates install .. all
of the xorg-server files were installed automaticly .. then sele
Same problem here with 4 1050TI cards. Installed 18.04, installed 390
driver, system doesn't boot anymore
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot g
Public bug reported:
Using Xubuntu 18.04 daily on Notebook
product: 80UD (LENOVO_MT_80UD_BU_idea_FM_Lenovo ideapad 110-15ISK)
vendor: LENOVO
version: Lenovo ideapad 110-15ISK
serial: MP16LZHW
width: 64 bits
Linux Xubuntu-18-04 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:2
Hello,
Sadly I also encounter the same problem for HD 3690/3850, I am running
Ubuntu 14.10.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/859101
Title:
fglrx 2:8.881-0ubuntu2: fglrx
** Attachment added: "/var/log/Xorg.0.log.old showing "EQ overflowing" messages"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1072840/+attachment/3417864/+files/Xorg.0.log.old
** Package changed: xorg (Ubuntu) => fglrx-installer (Ubuntu)
--
You received this bug notification because y
Public bug reported:
As requested in Bug #1063156 I open a separate report here.
After the screen of my laptop goes into powersave mode, often the
computer hangs with the screen in powersave mode. Nothing can be done
anymore except for using the SysRq magic keys to reboot the computer. It
happens
Can I execute this command as well?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1063156
Title:
(EE) [mi] EQ overflowing. Additional events will be discarded until
existing event
Same problem, indeed nothing can be done anymore except for using the
SysRq magic keys to reboot the computer. It happens about half of the
times for me when I leave my computer and come back after an hour.
I noticed that it seems to help to lock the screen manually before
leaving, but I am not su
#301 - Steve... Yes, I have removed all my USB devices, including USB
speakers and USB wireless Logitech mouse, and so far so good. (I also
plugged the USB speakers back briefly, causing a freeze within a minute
or two). "So far so good" = +- 2 hours of video streaming, which, like
I say, other
For me, it's still not solved. Ubuntu 12.04 (up-to-date) logged me out
when I tried to intall something in Software Center.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/77
I have the same problem on an ASUS U35JC-A1 with the intel i915 driver.
I attached the Xorg log.
** Attachment added: "Xorg log file of failed start"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/780961/+attachment/2138171/+files/Xorg.0.log.old
--
You received this bug notificat
I have the same problem - I believe it stems from having multiple mouse
configurations that may be active at the same time. I need multiple
configurations since I switch to an external mouse when docking my
laptop. For most people, ensuring there is only one pointer "InputClass"
in xorg.conf.d shou
@Geir Ove Myhr
How difficult is it to build an Ubuntu kernel package?
Because I still have the machine that had this problem, but I am not really
using it anymore. So it is free for testing. But I fear I already upgraded it
to Maverick. (Is there also a way to build the older kernel in Maverick?)
Note that this doesn't seem to be radeon specific : there are now
already two reports with nvidia gfx cards as well
--
[Radeon] [Lucid] [mi] EQ overflowing. The server is probably stuck in an
infinite loop
https://bugs.launchpad.net/bugs/567696
You received this bug notification because you are
Same problem here.
The Xorg.0.log:
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-27-server i686 Ubuntu
Current Operating System: Linux nuuk 2.6.32-25-generic #44-Ubuntu SMP Fri Sep
17 20:26:08 UTC 2010 i686
Kernel command lin
@papukaija Thanks
@sacevedo: Your xorg.conf and lspci shows you're using nvidia
proprietary drivers, with regards to that see
http://www.phoronix.com/scan.php?page=news_item&px=ODQyNQ it's the
latest info I found. Furthermore you may want to try the FIRST step of
http://duopetalflower.blogspot.com
d.
PS: There was no "splash" argument in grub only "quiet" I removed it, did not
help. I never really see plymouth anyhow.
PPS: If only this pc supported usb-boot... :-/
Regards,
Willem
--
Nouveau driver works horrible on Nvidia Geforce2
https://bugs.launchpad.net/bugs/596402
Yo
Think I've got the same problem, I will edit grub ASAP. Using nouveau as
my driver I tested the following:
Normal Lucid: System hang after startx.
Lucid with "xorg-edgers" PPA: System hang after startx.
Lucid with "xorg-edgers" and "kernel-ppa" PPAs: System hang after startx and
in recovery mode
I was having the same problem, but after switching to a newer kernel found in:
https://launchpad.net/~brian-rogers/+archive/experimental
Which was proposed here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/476817
I am not having any problems anymore. It boots normal, n
Hi Brian,
Well at 16-04-2010 the standard Lucid still crashed. Well it reverted to low
graphics mode.
Using your ppa, with the new kernel makes it work fine, I don't know if that
can be of any help for the Lucid release... Maybe 10.4.1?
--
[i855] [i855] [karmic] X freezes with intel 855GM vide
Hi Brian,
Just now moved to lucid. And I can confirm that this fix works.
With normal lucid, I was thrown to low graphics mode each time.
The new kernel seems to work fine.
--
[i855] [i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug
@geomar:
The freezes mentioned here are related to the Intel video driver in combination
with the X version.
If you experience other freezes please open a separate bug report.
The fixes you mention in #31 do not help with the freeze reported in this bug
report.
--
[i855] [i855] [karmic] X freez
I retried with nomodeset kernel option
Stock kernel + xserver-xorg-video-intel - 3:2.6.3-0ubuntu9.4backtrack1
the libdrm was: libdrm - 1:2.4.5-0ubuntu4backtrack1
And it froze, though ssh was luckily available!
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bu
@Brian
No, did not try that, because I had to use nomodeset before to get this to work
(with the vesa driver).
But will try again, with nomodeset tomorrow.
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification because yo
Oops sorry, the intel driver version was: xserver-xorg-video-intel -
3:2.6.3-0ubuntu9.4backtrack1 the libdrm was:
libdrm - 1:2.4.5-0ubuntu4backtrack1
Installed all i386 files from both packages.
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You
libdrm - 1:2.4.5-0ubuntu4backtrack1 combined with: xserver-xorg-video-intel -
3:2.7.0-1ubuntu1backtrack1
using stock karmic kernel: ubuntu logo shows, the screen flickers and freezes
black. ssh works.
using the 599 kernel actually does the same, but no ssh!
--
[i855] [karmic] X freezes with in
Using the option "Tiling" "false" does not make a difference it froze at login
screen. (ssh worked)
Will now try to revert to the older libdrm versions and intel video drivers as
instructed by Brian Rogers.
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs
OK, I have just tried https://launchpad.net/~brian-rogers/+archive
/graphics-testing
I have the following packages installed:
1:2.4.11-2+karmic3
5:2.8.0-2-gb0aa94f
Using the standard karmic kernel 2.6.31.17.30
Still produces the freeze.
--
[i855] [karmic] X freezes with intel 855GM/82945G vid
@17
I have today tried to 599 and 600 version.
599 works fine, 600 introduces the bug.
I will look at #18 tomorrow.
--
[i855] [karmic] X freezes with intel 855GM/82945G videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification because you are a member of Ubuntu-X,
which
Actually, using nomodeset and the vesa driver as explained in
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/447892
works better, than the acpi=off. My sound now works and the power button
doesn't switch it off immediately.
--
[i855] [karmic] X freezes with intel 855GM/
OK, tried with latest xorg-edgers ppa and updates installed with the 2.6.32-rc7
kernel (removed the acpi=off kernel option).
There is *some* progress. The system starts and GDM works. (as before) However
when in the gnome session it freezes (as before). However, I am able to switch
between tty's
OK, I did try just upgrading the kernel, which didn't help.
I have tried 2.6.32-rc7 from the mainline kernels. However, the description of
xorg-edgers worries me. This the laptop that I work on, so I rather have a non
freezing X, without sound, 3D acceleration, than a non working laptop.
Could I
I actually tried tonight and it works!
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
__
So the kernel option acpi=off will actually get you a working (not
freezing) system? If so, thanks for this work-around! (Will try
tomorrow)
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification because you are a member o
As the status is still incomplete, could someone tell me what
information I can gather to help you guys track the bug?
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification because you are a member of Ubuntu-X,
which is s
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/35360118/Xorg.0.log.old
--
[karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vide
xorg.log as requested.
Will also post Xorg.log.old
** Attachment added: "latest xorg.log"
http://launchpadlibrarian.net/35360112/Xorg.0.log
--
[karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification because you are a member of Ub
78 matches
Mail list logo
