[opensuse-factory] Re: Tumbleweed still does not light up in Virtualbox 5.0.18
I am running the same .18 version of Virtualbox as the host for a Tumbleweed guest. This guest was installed "fresh" from the TW .iso about 3 weeks ago as a new guest. I have been updating it from the command line with zypper up. This week, I removed the virtualbox-guest-x11 (5.0.17) package from the guest and am able to finally see Plymouth and then get to KDE desktop. (Yay!) I removed the package based on this report: https://bugzilla.opensuse.org/show_bug.cgi?id=976512 I have not had time this week to determine if my issue is the same or different from this bug report. I have had no graphical desktop environment since early March when kernel 4.5 was introduced. I noticed both plymouthd and a sddm were dumping core on startup. I am a long-time openSUSE user but am new to this list and bugzilla. I am open to anyone's advice on what I could upload and where to help solve this. Hope this helps and thank you, Brian On 04/23/2016 Howard Guo wrote:
Hey fellow Tumbleweed users.
Earlier in the month I read that Virtualbox 5.0.18 will properly support Linux kernel 4.5. Now that I have upgraded to 5.0.18 and trying to boot a freshly installed 0417 tumbleweed, it still does not light up the display, same thing happens as previously on Virtualbox 5.0.16.
Any clue how to get Tumbleweed display working again?
Regards, Howard
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/23/2016 10:27 AM, Brian Mitchell wrote:
I am running the same .18 version of Virtualbox as the host for a Tumbleweed guest. This guest was installed "fresh" from the TW .iso about 3 weeks ago as a new guest. I have been updating it from the command line with zypper up. This week, I removed the virtualbox-guest-x11 (5.0.17) package from the guest and am able to finally see Plymouth and then get to KDE desktop. (Yay!)
I removed the package based on this report:
https://bugzilla.opensuse.org/show_bug.cgi?id=976512
I have not had time this week to determine if my issue is the same or different from this bug report. I have had no graphical desktop environment since early March when kernel 4.5 was introduced. I noticed both plymouthd and a sddm were dumping core on startup.
I am a long-time openSUSE user but am new to this list and bugzilla. I am open to anyone's advice on what I could upload and where to help solve this.
Hope this helps and thank you, Brian
On 04/23/2016 Howard Guo wrote:
Hey fellow Tumbleweed users.
Earlier in the month I read that Virtualbox 5.0.18 will properly support Linux kernel 4.5. Now that I have upgraded to 5.0.18 and trying to boot a freshly installed 0417 tumbleweed, it still does not light up the display, same thing happens as previously on Virtualbox 5.0.16.
Any clue how to get Tumbleweed display working again?
Regards, Howard
Howard and Bryan, I was unaware of b.o.o #976512 as it had not yet been assigned to me. Although I thought I had tested VB 5.0.17 on TW VMs with both KDE and Gnome desktops, I can confirm that X is failing to start on the KDE version. Removing the VirtualBox guest components will allow X to run, but some features will be missing. A different workaround is to edit /etc/sysconfig/displaymanager and replace "sddm" with "gdm" or "lightdm" in the DISPLAYMANAGER line. You should reinstall the VB guest packages if they have been removed. The display manager change will break autologin, but X will work. Version 5.0.18 of VB is currently building on OBS. Once it is available, the workaround should no longer be needed. At least my local build of 5.0.18 starts X in the KDE VM using sddm. BTW, it is generally better to post your replies at the bottom rather than the top. That way the reader can follow the thread in normal fashion, and not have to move down, then up. Most mailing lists prefer this method, and some even demand it. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/23/2016 01:56 PM, Larry Finger wrote:
On 04/23/2016 at 07:54 Howard Guo wrote:
Hey fellow Tumbleweed users.
Earlier in the month I read that Virtualbox 5.0.18 will properly support Linux kernel 4.5. Now that I have upgraded to 5.0.18 and trying to boot a freshly installed 0417 tumbleweed, it still does not light up the display, same thing happens as previously on Virtualbox 5.0.16.
Any clue how to get Tumbleweed display working again?
Regards, Howard
On 04/23/2016 10:27 AM, Brian Mitchell wrote:
I am running the same .18 version of Virtualbox as the host for a Tumbleweed guest. This guest was installed "fresh" from the TW .iso about 3 weeks ago as a new guest. I have been updating it from the command line with zypper up. This week, I removed the virtualbox-guest-x11 (5.0.17) package from the guest and am able to finally see Plymouth and then get to KDE desktop. (Yay!)
I removed the package based on this report:
https://bugzilla.opensuse.org/show_bug.cgi?id=976512
I have not had time this week to determine if my issue is the same or different from this bug report. I have had no graphical desktop environment since early March when kernel 4.5 was introduced. I noticed both plymouthd and a sddm were dumping core on startup.
I am a long-time openSUSE user but am new to this list and bugzilla. I am open to anyone's advice on what I could upload and where to help solve this.
Hope this helps and thank you, Brian
I was unaware of b.o.o #976512 as it had not yet been assigned to me.
Although I thought I had tested VB 5.0.17 on TW VMs with both KDE and Gnome desktops, I can confirm that X is failing to start on the KDE version. Removing the VirtualBox guest components will allow X to run, but some features will be missing. A different workaround is to edit /etc/sysconfig/displaymanager and replace "sddm" with "gdm" or "lightdm" in the DISPLAYMANAGER line. You should reinstall the VB guest packages if they have been removed. The display manager change will break autologin, but X will work. zy Version 5.0.18 of VB is currently building on OBS. Once it is available, the workaround should no longer be needed. At least my local build of 5.0.18 starts X in the KDE VM using sddm.
BTW, it is generally better to post your replies at the bottom rather than the top. That way the reader can follow the thread in normal fashion, and not have to move down, then up. Most mailing lists prefer this method, and some even demand it.
Larry
Thank you Larry. I've attempted to reorder the text of my earlier reply to put this discussion in top-down chronological order. Hopefully the formatting will come through properly. My apologies. I reinstalled virtualbox-guest-x11 (virtualbox-guest-x11-5.0.17-1.3.x86_64). I tried both "gdm" and "lightdm" as DISPLAYMANAGER in /etc/sysconfig/displaymanager. The screen would not light with either display manager. The plymouth screen would appear briefly (i.e. the TW "infinity" symbol with three dots below) then it would drop to a console login on VT1 (tty1). Looking at journalctl -b output, it is reported that plymouth-start.service failed with result core-dump with SEGV in each case. I tried grepping the journalctl -b output for gdm and lightdm. I did not see a clear indication that these logged messages like sddm does when sddm's process dumps core coming up under systemd with the virtualbox-guest-x11 package installed. I removed the virtualbox-guest-x11 package. I can boot to KDE with either "gdm" or "lightdm" or "sddm" as DISPLAYMANAGER. If there is any log output that I can provide, please let me know what would help. I can attach it to b.o.o #976512 (or elsewhere) at your direction. My TW installation is at 20160417 as a guest running in VirtualBox 5.0.18. Thanks again, Brian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/23/2016 05:16 PM, Brian Mitchell wrote:
On 04/23/2016 01:56 PM, Larry Finger wrote:
On 04/23/2016 at 07:54 Howard Guo wrote:
Hey fellow Tumbleweed users.
Earlier in the month I read that Virtualbox 5.0.18 will properly support Linux kernel 4.5. Now that I have upgraded to 5.0.18 and trying to boot a freshly installed 0417 tumbleweed, it still does not light up the display, same thing happens as previously on Virtualbox 5.0.16.
Any clue how to get Tumbleweed display working again?
Regards, Howard
On 04/23/2016 10:27 AM, Brian Mitchell wrote:
I am running the same .18 version of Virtualbox as the host for a Tumbleweed guest. This guest was installed "fresh" from the TW .iso about 3 weeks ago as a new guest. I have been updating it from the command line with zypper up. This week, I removed the virtualbox-guest-x11 (5.0.17) package from the guest and am able to finally see Plymouth and then get to KDE desktop. (Yay!)
I removed the package based on this report:
https://bugzilla.opensuse.org/show_bug.cgi?id=976512
I have not had time this week to determine if my issue is the same or different from this bug report. I have had no graphical desktop environment since early March when kernel 4.5 was introduced. I noticed both plymouthd and a sddm were dumping core on startup.
I am a long-time openSUSE user but am new to this list and bugzilla. I am open to anyone's advice on what I could upload and where to help solve this.
Hope this helps and thank you, Brian
I was unaware of b.o.o #976512 as it had not yet been assigned to me.
Although I thought I had tested VB 5.0.17 on TW VMs with both KDE and Gnome desktops, I can confirm that X is failing to start on the KDE version. Removing the VirtualBox guest components will allow X to run, but some features will be missing. A different workaround is to edit /etc/sysconfig/displaymanager and replace "sddm" with "gdm" or "lightdm" in the DISPLAYMANAGER line. You should reinstall the VB guest packages if they have been removed. The display manager change will break autologin, but X will work. zy Version 5.0.18 of VB is currently building on OBS. Once it is available, the workaround should no longer be needed. At least my local build of 5.0.18 starts X in the KDE VM using sddm.
BTW, it is generally better to post your replies at the bottom rather than the top. That way the reader can follow the thread in normal fashion, and not have to move down, then up. Most mailing lists prefer this method, and some even demand it.
Larry
Thank you Larry. I've attempted to reorder the text of my earlier reply to put this discussion in top-down chronological order. Hopefully the formatting will come through properly. My apologies.
I reinstalled virtualbox-guest-x11 (virtualbox-guest-x11-5.0.17-1.3.x86_64). I tried both "gdm" and "lightdm" as DISPLAYMANAGER in /etc/sysconfig/displaymanager. The screen would not light with either display manager. The plymouth screen would appear briefly (i.e. the TW "infinity" symbol with three dots below) then it would drop to a console login on VT1 (tty1).
Looking at journalctl -b output, it is reported that plymouth-start.service failed with result core-dump with SEGV in each case. I tried grepping the journalctl -b output for gdm and lightdm. I did not see a clear indication that these logged messages like sddm does when sddm's process dumps core coming up under systemd with the virtualbox-guest-x11 package installed.
I removed the virtualbox-guest-x11 package. I can boot to KDE with either "gdm" or "lightdm" or "sddm" as DISPLAYMANAGER.
If there is any log output that I can provide, please let me know what would help. I can attach it to b.o.o #976512 (or elsewhere) at your direction. My TW installation is at 20160417 as a guest running in VirtualBox 5.0.18.
The next time you post here or create a bug report, please state what desktop you are running in Tumbleweed. I was able to find that info from the posted log. I just posted a work around in b.o.o #976940. You need to delete file /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so as it is messing up gdm. Having that file present does not affect sddm, and the KDE desktops start OK. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks Larry, display is now working again. Regards, Howard From: Larry Finger Sent: 24 April 2016 22:35 To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Re: Tumbleweed still does not light up inVirtualbox 5.0.18 On 04/23/2016 05:16 PM, Brian Mitchell wrote:
On 04/23/2016 01:56 PM, Larry Finger wrote:
On 04/23/2016 at 07:54 Howard Guo wrote:
Hey fellow Tumbleweed users.
Earlier in the month I read that Virtualbox 5.0.18 will properly support Linux kernel 4.5. Now that I have upgraded to 5.0.18 and trying to boot a freshly installed 0417 tumbleweed, it still does not light up the display, same thing happens as previously on Virtualbox 5.0.16.
Any clue how to get Tumbleweed display working again?
Regards, Howard
On 04/23/2016 10:27 AM, Brian Mitchell wrote:
I am running the same .18 version of Virtualbox as the host for a Tumbleweed guest. This guest was installed "fresh" from the TW .iso about 3 weeks ago as a new guest. I have been updating it from the command line with zypper up. This week, I removed the virtualbox-guest-x11 (5.0.17) package from the guest and am able to finally see Plymouth and then get to KDE desktop. (Yay!)
I removed the package based on this report:
https://bugzilla.opensuse.org/show_bug.cgi?id=976512
I have not had time this week to determine if my issue is the same or different from this bug report. I have had no graphical desktop environment since early March when kernel 4.5 was introduced. I noticed both plymouthd and a sddm were dumping core on startup.
I am a long-time openSUSE user but am new to this list and bugzilla. I am open to anyone's advice on what I could upload and where to help solve this.
Hope this helps and thank you, Brian
I was unaware of b.o.o #976512 as it had not yet been assigned to me.
Although I thought I had tested VB 5.0.17 on TW VMs with both KDE and Gnome desktops, I can confirm that X is failing to start on the KDE version. Removing the VirtualBox guest components will allow X to run, but some features will be missing. A different workaround is to edit /etc/sysconfig/displaymanager and replace "sddm" with "gdm" or "lightdm" in the DISPLAYMANAGER line. You should reinstall the VB guest packages if they have been removed. The display manager change will break autologin, but X will work. zy Version 5.0.18 of VB is currently building on OBS. Once it is available, the workaround should no longer be needed. At least my local build of 5.0.18 starts X in the KDE VM using sddm.
BTW, it is generally better to post your replies at the bottom rather than the top. That way the reader can follow the thread in normal fashion, and not have to move down, then up. Most mailing lists prefer this method, and some even demand it.
Larry
Thank you Larry. I've attempted to reorder the text of my earlier reply to put this discussion in top-down chronological order. Hopefully the formatting will come through properly. My apologies.
I reinstalled virtualbox-guest-x11 (virtualbox-guest-x11-5.0.17-1.3.x86_64). I tried both "gdm" and "lightdm" as DISPLAYMANAGER in /etc/sysconfig/displaymanager. The screen would not light with either display manager. The plymouth screen would appear briefly (i.e. the TW "infinity" symbol with three dots below) then it would drop to a console login on VT1 (tty1).
Looking at journalctl -b output, it is reported that plymouth-start.service failed with result core-dump with SEGV in each case. I tried grepping the journalctl -b output for gdm and lightdm. I did not see a clear indication that these logged messages like sddm does when sddm's process dumps core coming up under systemd with the virtualbox-guest-x11 package installed.
I removed the virtualbox-guest-x11 package. I can boot to KDE with either "gdm" or "lightdm" or "sddm" as DISPLAYMANAGER.
If there is any log output that I can provide, please let me know what would help. I can attach it to b.o.o #976512 (or elsewhere) at your direction. My TW installation is at 20160417 as a guest running in VirtualBox 5.0.18.
The next time you post here or create a bug report, please state what desktop you are running in Tumbleweed. I was able to find that info from the posted log. I just posted a work around in b.o.o #976940. You need to delete file /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so as it is messing up gdm. Having that file present does not affect sddm, and the KDE desktops start OK. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Brian Mitchell -
Howard Guo -
Larry Finger