I have had 'rawhide' running in VirtualBox for some months. Recently an upgrade renconfigured repos - as I understand in order to make it become "Fedora 22"). So far, so good.
However, for a week I wasn't able to upgrade (using Yum Extender) with new packages due to some signing problems with packages. Yesterday I finally succedded to do so, But after the upgrades were installed and a reboot, the VM halts when it should display the login screen. It hanged forever. I noticed in another thread here that "the login screen will now use Wayland". From yet another discussion I know that Wayland will not work in VirtualBox, as it (VB) does not have drivers for the virtuaized hardware in this environment (Wayland).
1st queston: is my understanding of the problem correct? 2nd question: was this considered when deciding to use Wayland for the login screen? 3rd question: will there be/is there a workaround of some kind?
If it matters, I am using the XFCE spin. Here I find it even more strange to use Wayland for login. I think you are shooting yourself in the foot by not allowing people to try F22 in VirtualBox etc.
(besides new packets have arrived since yesterday that are not signed, it seems)
On Sun, Feb 22, 2015 at 2:02 PM, Peter Laursen jazcyk@gmail.com wrote: [snip]
I think you are shooting yourself in the foot by not allowing people to try F22 in VirtualBox etc.
Mind your language, and always assume good intentions. Nobody explicitly decided to "not allow VirtualBox" and we are not "shooting ourselves in the foot". gdm should fallback to X11 when it can't use Wayland. If this fallback does not work, it is merely a bug that should be fixed. Why don't you start by filing it in GNOME's bugzilla?
(besides new packets have arrived since yesterday that are not signed, it seems)
I assume you mean packages. This is known and happens every time we branch, packages will be signed again in the time for alpha.
I was merely asking if this was intentional or an oversight. Or if I possibly completely misunderstood what could be the reason for the problem.
As soon as the signing problem with new packages has been solved (so that Yum will let me install), I will try again and file a bug if it is still reproducible. Currently I am on a snapshot 6 days old and cannot afford the time experimenting figuring out which new packages are signed and which are not.
-- Peter
On Sun, Feb 22, 2015 at 1:10 PM, Elad Alfassa elad@fedoraproject.org wrote:
On Sun, Feb 22, 2015 at 2:02 PM, Peter Laursen jazcyk@gmail.com wrote: [snip]
I think you are shooting yourself in the foot by not allowing people to try F22 in VirtualBox etc.
Mind your language, and always assume good intentions. Nobody explicitly decided to "not allow VirtualBox" and we are not "shooting ourselves in the foot". gdm should fallback to X11 when it can't use Wayland. If this fallback does not work, it is merely a bug that should be fixed. Why don't you start by filing it in GNOME's bugzilla?
(besides new packets have arrived since yesterday that are not signed, it seems)
I assume you mean packages. This is known and happens every time we branch, packages will be signed again in the time for alpha.
-- -Elad Alfassa.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
On Sun, Feb 22, 2015 at 1:23 PM, Peter Laursen jazcyk@gmail.com wrote:
I was merely asking if this was intentional or an oversight.
No one breaks things intentionally. That makes no sense. If something does not work ... its a bug.
On Sun, 2015-02-22 at 13:23 +0100, Peter Laursen wrote:
I was merely asking if this was intentional or an oversight. Or if I possibly completely misunderstood what could be the reason for the problem.
As soon as the signing problem with new packages has been solved (so that Yum will let me install)
You can just pass --nogpgcheck . This is what Rawhide was doing for you anyway. We really ought to ship fedora-repos with gpgcheck disabled until Bodhi enablement, though, whoever does the fedora-repos package updates is out of sync with the actual releng process, it makes no sense to flip the gpgcheck switch before we're actually signing everything.
I can now identify the problem as being with one or more of the xorg-x11-* packages.
I am fully updated with the exception of * kernel 4.0 packages * ksysguard-libs (yes, I prefer Ksysguard!) * oxygen-icon-theme (none of those are signed currently) * xorg-x11-* packages. .. and it works fine. But as soon as I install xorg-x11-* packages.and reboot, the VM cannot paint the login screen.
-- Peter
On Tue, Feb 24, 2015 at 2:21 AM, Adam Williamson <adamwill@fedoraproject.org
wrote:
On Sun, 2015-02-22 at 13:23 +0100, Peter Laursen wrote:
I was merely asking if this was intentional or an oversight. Or if I possibly completely misunderstood what could be the reason for the problem.
As soon as the signing problem with new packages has been solved (so that Yum will let me install)
You can just pass --nogpgcheck . This is what Rawhide was doing for you anyway. We really ought to ship fedora-repos with gpgcheck disabled until Bodhi enablement, though, whoever does the fedora-repos package updates is out of sync with the actual releng process, it makes no sense to flip the gpgcheck switch before we're actually signing everything. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
On Wed, 2015-02-25 at 11:47 +0100, Peter Laursen wrote:
I can now identify the problem as being with one or more of the xorg- x11-* packages.
I am fully updated with the exception of
- kernel 4.0 packages
- ksysguard-libs (yes, I prefer Ksysguard!)
- oxygen-icon-theme
(none of those are signed currently)
- xorg-x11-* packages.
.. and it works fine. But as soon as I install xorg-x11-* packages.and reboot, the VM cannot paint the login screen.
If it's a 32-bit install, you're probably hitting https://bugzilla.redhat.com/show_bug.cgi?id=1195905 . Get the updated libinput.
It is 64 bit virtualized in Virtualbox 4.3.22 on Win7 host.
.-- Peter
On Wed, Feb 25, 2015 at 8:52 PM, Adam Williamson <adamwill@fedoraproject.org
wrote:
On Wed, 2015-02-25 at 11:47 +0100, Peter Laursen wrote:
I can now identify the problem as being with one or more of the xorg- x11-* packages.
I am fully updated with the exception of
- kernel 4.0 packages
- ksysguard-libs (yes, I prefer Ksysguard!)
- oxygen-icon-theme
(none of those are signed currently)
- xorg-x11-* packages.
.. and it works fine. But as soon as I install xorg-x11-* packages.and reboot, the VM cannot paint the login screen.
If it's a 32-bit install, you're probably hitting https://bugzilla.redhat.com/show_bug.cgi?id=1195905 . Get the updated libinput. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
desktop@lists.fedoraproject.org
-
Adam Williamson -
drago01 -
Elad Alfassa -
Peter Laursen