I have a brand-new Dell Precision workstation, on which I'm trying to install Fedora 23 (with my preferred desktop environment, MATE), which is turning into the most frustrating Linux install I've experienced in a long time (and I've been using Linux since before Red Hat existed).
I started with Fedora-Workstation-netinst-x86_64-23 on a thumb drive. I booted, selected automatic partitioning and MATE, and it started downloading RPMs. When it finished downloading, it rebooted. Apparently, there's a conflict between release and updates on who owns /etc/xdg/menus/mate-preferences-categoris.menu, and anaconda just crashes and reboots (not even a traceback) on an install transaction failure.
After a few passes through that before I figured out anaconda was not going to install MATE (with frustrating waits for downloads each time), I gave up and did a minimal install. Then I did a dnf groupinstall MATE, and that downloaded all the RPMs, then gave me the error about the file conflict. I tried to exclude one of the choices, use --best, etc., and nothing would solve it.
Also, when "dnf groupinstall foo" is run, even if it fails, dnf then thinks the group is installed (and so a repeated groupinstall does nothing). I had to do a groupremove first.
I just manually installed the RPMs from the dnf cache to get around the MATE brokenness, and then got systemd to do a graphical boot.
Now, when I get to the graphical login, my USB is dead. I can boot single-user mode and the keyboard works fine; as soon as the graphical login loads, USB appears dead (keyabord is like it is powered off, no Numlock, Capslock, etc.). Tried unplugging keyboard, moving it to different USB ports (directly on the computer instead of hub), etc. with no result. The fact that the keyboard works in single-user mode shows there's no hardware problem, Linux USB issue, etc.
At this point, I guess I'll roll back and try Fedora 22. If I ever get a working desktop, I'll try to file some bugs I guess. I found a BZ about anaconda that appears to match my problem (1287841). That doesn't explain the MATE conflicts in the repos, dnf groupinstall fail, or disappearing USB though.
I have a 10'year old dell laptop. I did the f23 install.. A while back.. And I run mate. I think I did a gnome install, then did the dnf install mate-desktop or something similar to that....
Sent from my iPad
On Dec 8, 2015, at 11:52 AM, Chris Adams linux@cmadams.net wrote:
I have a brand-new Dell Precision workstation, on which I'm trying to install Fedora 23 (with my preferred desktop environment, MATE), which is turning into the most frustrating Linux install I've experienced in a long time (and I've been using Linux since before Red Hat existed).
I started with Fedora-Workstation-netinst-x86_64-23 on a thumb drive. I booted, selected automatic partitioning and MATE, and it started downloading RPMs. When it finished downloading, it rebooted. Apparently, there's a conflict between release and updates on who owns /etc/xdg/menus/mate-preferences-categoris.menu, and anaconda just crashes and reboots (not even a traceback) on an install transaction failure.
After a few passes through that before I figured out anaconda was not going to install MATE (with frustrating waits for downloads each time), I gave up and did a minimal install. Then I did a dnf groupinstall MATE, and that downloaded all the RPMs, then gave me the error about the file conflict. I tried to exclude one of the choices, use --best, etc., and nothing would solve it.
Also, when "dnf groupinstall foo" is run, even if it fails, dnf then thinks the group is installed (and so a repeated groupinstall does nothing). I had to do a groupremove first.
I just manually installed the RPMs from the dnf cache to get around the MATE brokenness, and then got systemd to do a graphical boot.
Now, when I get to the graphical login, my USB is dead. I can boot single-user mode and the keyboard works fine; as soon as the graphical login loads, USB appears dead (keyabord is like it is powered off, no Numlock, Capslock, etc.). Tried unplugging keyboard, moving it to different USB ports (directly on the computer instead of hub), etc. with no result. The fact that the keyboard works in single-user mode shows there's no hardware problem, Linux USB issue, etc.
At this point, I guess I'll roll back and try Fedora 22. If I ever get a working desktop, I'll try to file some bugs I guess. I found a BZ about anaconda that appears to match my problem (1287841). That doesn't explain the MATE conflicts in the repos, dnf groupinstall fail, or disappearing USB though.
-- Chris Adams linux@cmadams.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Tue, Dec 08, 2015 at 10:52:12AM -0600, Chris Adams wrote:
I started with Fedora-Workstation-netinst-x86_64-23 on a thumb drive. I booted, selected automatic partitioning and MATE, and it started downloading RPMs. When it finished downloading, it rebooted. Apparently, there's a conflict between release and updates on who owns /etc/xdg/menus/mate-preferences-categoris.menu, and anaconda just crashes and reboots (not even a traceback) on an install transaction failure.
Ouch. Is this with updates repository enabled, or not?
After a few passes through that before I figured out anaconda was not going to install MATE (with frustrating waits for downloads each time), I gave up and did a minimal install. Then I did a dnf groupinstall MATE, and that downloaded all the RPMs, then gave me the error about the file conflict. I tried to exclude one of the choices, use --best, etc., and nothing would solve it.
Yeah, if there's a conflict between packages that are all dependencies, no flags will help. The RPMs need to be fixed.
Now, when I get to the graphical login, my USB is dead. I can boot single-user mode and the keyboard works fine; as soon as the graphical login loads, USB appears dead (keyabord is like it is powered off, no Numlock, Capslock, etc.). Tried unplugging keyboard, moving it to different USB ports (directly on the computer instead of hub), etc. with no result. The fact that the keyboard works in single-user mode shows there's no hardware problem, Linux USB issue, etc.
This, and the above, probably needs to be brought up with the MATE Compiz spin team, and possibly MATE upstream. The spins page gives #fedora-mate as a place to talk with the developers (as well as this list, although I'm not sure I've seen the developers active here).
On Dec 8, 2015 10:52 AM, "Chris Adams" linux@cmadams.net wrote:
Now, when I get to the graphical login, my USB is dead. I can boot single-user mode and the keyboard works fine; as soon as the graphical login loads, USB appears dead (keyabord is like it is powered off, no Numlock, Capslock, etc.). Tried unplugging keyboard, moving it to different USB ports (directly on the computer instead of hub), etc. with no result. The fact that the keyboard works in single-user mode shows there's no hardware problem, Linux USB issue, etc.
Just for fun, a long time ago I did a minimal install and notice this, on single-user mode keyboard and mouse seems to not work, and also I make a mistake by setting as default graphical instead of multi-user, then when the computer reboots I was not able even to poweroff the computer.
On single-user mode do a search for a package "libinput" or something like "xorg-libinput", also search for something like "xorg-xkb", not sure but once of this make the trick. Install one by one and see which of them fix the problem.
Do not set graphical mode as default, because if this don't solve the problem you will not able to do something else, always run a startx fron single user session to see if the keyboard is working on graphical login. Also install a login, lightdm is the default for Mate, in case it is not already installed.
Seems like a weak/bad dependency solving from a "not yet a production software, buggy and experimental"... dnf. Recently a friend faced the same proble when he did a minimal install.
Once upon a time, Matthew Miller mattdm@fedoraproject.org said:
On Tue, Dec 08, 2015 at 10:52:12AM -0600, Chris Adams wrote:
I started with Fedora-Workstation-netinst-x86_64-23 on a thumb drive. I booted, selected automatic partitioning and MATE, and it started downloading RPMs. When it finished downloading, it rebooted. Apparently, there's a conflict between release and updates on who owns /etc/xdg/menus/mate-preferences-categoris.menu, and anaconda just crashes and reboots (not even a traceback) on an install transaction failure.
Ouch. Is this with updates repository enabled, or not?
I believe I tried it without updates enabled, but I'm not sure now.
I was also fighting with getting anaconda to use a proxy (weird office Cisco firewall issue slowing downloads from the Internet dramatically, but a local proxy outside the firewall works fine). It is very unclear that if you use "closest mirror" that specifying a proxy on the same screen has no effect; it has to be done on the boot command line (there's a BZ for this but was closed as WONTFIX IIRC; IMHO there should at least be a warning).
Yeah, if there's a conflict between packages that are all dependencies, no flags will help. The RPMs need to be fixed.
Definitely; the combination of that plus an anaconda bug just rebooting made it seriously frustrating to figure out though.
Now, when I get to the graphical login, my USB is dead. I can boot single-user mode and the keyboard works fine; as soon as the graphical login loads, USB appears dead (keyabord is like it is powered off, no Numlock, Capslock, etc.). Tried unplugging keyboard, moving it to different USB ports (directly on the computer instead of hub), etc. with no result. The fact that the keyboard works in single-user mode shows there's no hardware problem, Linux USB issue, etc.
This, and the above, probably needs to be brought up with the MATE Compiz spin team, and possibly MATE upstream. The spins page gives #fedora-mate as a place to talk with the developers (as well as this list, although I'm not sure I've seen the developers active here).
I will try to go back and find the conflicting packages, see which was in updates, and file a bug (I made an IRC account but haven't used it in a long time).
I did finally get the system going by using the MATE live spin image (and then loading updates) - no USB issue there. I've just always used the netinst image (CD, USB, or PXE booted).
Now everything but my Bluetooth works, but I think that's a issue with a near-brand-new chip (Intel 8260 wifi+BT), the Linux kernel driver, and firmware (hopefully F23 will get Linux 4.3 soon and that'll help).
On 12/09/2015 10:59 AM, Chris Adams wrote:
Once upon a time, Matthew Miller mattdm@fedoraproject.org said:
On Tue, Dec 08, 2015 at 10:52:12AM -0600, Chris Adams wrote:
I started with Fedora-Workstation-netinst-x86_64-23 on a thumb drive. I booted, selected automatic partitioning and MATE, and it started downloading RPMs. When it finished downloading, it rebooted. Apparently, there's a conflict between release and updates on who owns /etc/xdg/menus/mate-preferences-categoris.menu, and anaconda just crashes and reboots (not even a traceback) on an install transaction failure.
Ouch. Is this with updates repository enabled, or not?
I believe I tried it without updates enabled, but I'm not sure now.
I was also fighting with getting anaconda to use a proxy (weird office Cisco firewall issue slowing downloads from the Internet dramatically, but a local proxy outside the firewall works fine).
Try
echo "0" >/proc/sys/net/ipv4/tcp_sack
and see if that cleans up your Cisco issue. It can have a significant effect on ssh, scp and sftp transfers--perhaps yours as well (we use a Cisco Pix).
<snip> ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - I won't rise to the occasion, but I'll slide over to it. - ----------------------------------------------------------------------
On Tue, 8 Dec 2015 10:52:12 -0600 Chris Adams linux@cmadams.net wrote:
I have a brand-new Dell Precision workstation, on which I'm trying to install Fedora 23 (with my preferred desktop environment, MATE), which is turning into the most frustrating Linux install I've experienced in a long time (and I've been using Linux since before Red Hat existed). ...
Same experience here. My usual practice is i686 installation on PC with 1-4 GB of RAM, netinst from local NFS repos via kickstart with number of %include files, to SW md RAID (usually prepartitioned, but RAIDs are not created), MATE or XFce desktop. Doing it in this way is almost impossible for a large number of errors in F23 installer; such problems I have never had.
I think it would be best to release correction netinst images still for F23, to make the most of the errors were corrected in F24 already.
-
Chris Adams -
Franta Hanzlík -
Matthew Miller -
Paul Cartwright -
Porfirio Andrés Páiz Carrasco -
Rick Stevens