Re: System alive but can't access from the monitor
I have 2 F25 systems, the problem I'm seeing with the monitor not coming back from sleep only happens on one of them. I did a grep for nouveau on the 2 systems in /var/log/messages. There are no messages including nouveau on the system that does not exhibit the problem. This system has an Intel graphics controller. On this system lspci shows 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) On the one that exhibits the problem I see the following: Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: NVIDIA G86 (086100a2) Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: bios: version 60.86.37.00.51 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: bios: M0203T not found Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: bios: M0203E not matched! Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: fb: 512 MiB DDR2 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: VRAM: 512 MiB Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: GART: 1048576 MiB Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: TMDS table version 2.0 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB version 4.0 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB outp 00: 02000300 0028 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB outp 01: 01000302 0030 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB outp 02: 04011310 0028 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB outp 03: 010223f1 00c0c080 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB conn 00: 1030 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB conn 01: 0100 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB conn 02: 0210 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB conn 03: 0211 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: DCB conn 04: 0213 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: failed to create encoder 0/1/0: -19 Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: TV-1 has no encoders, removing Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: MM: using CRYPT for buffer copies Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x7, bo 9b51add56800 Mar 31 15:29:31 jackstraw kernel: fbcon: nouveaufb (fb0) is primary device Mar 31 15:29:31 jackstraw kernel: nouveau :01:00.0: fb0: nouveaufb frame buffer device Mar 31 15:29:31 jackstraw kernel: [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 On this system lspci shows: 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1) This problem occurs on both 4.10.5 AN 4.10.6 Paolo On 03/31/2017 04:08 PM, Robin Laing wrote: On 30/03/17 01:35, Ed Greshko wrote: On 03/30/17 14:24, Paolo Galtieri wrote: Folks, I have 2 F25 systems that have been updated today. These 2 systems share a monitor. One system is attached via a kvm switch to the monitor, the other system is attached via hdmi. This morning and twice this evening a problem has started to manifest itself. This configuration has been working fine for several years. I will call the systems A and B, system A is attached to the monitor via hdmi, system B via VGA. If I switch to system A for a while and then try to switch back to system B the monitor instead of staying on VGA cycles from VGA to DVI to HDMI and returns to system A. I can ssh into system B and everything looks fine, i.e. things that were running under my user id are still running, e.g. chrome and firefox. I looked at /var/log/messages and I see this: Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0... Mar 29 23:00:02 jackstraw systemd: Stopped target Default. Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System. Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets. Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket. Mar 29 23:00:02 jackstraw systemd: Stopped target Timers. Mar 29 23:00:02 jackstraw systemd: Stopped target Paths. Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown. Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session... Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588 (kill). This was at the time I switched from system A to system B. Each of the other times I saw this problem I see the same set of messages in the log file. Can someone explain what they mean and could they be the cause of the problem? I see the same messages on the other system, but there they were part of other messages related to rebooting the system. The only way I can recover is reboot the system. Here's my video card info: 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1) Any assistance is appreciated. Since everything is still runnin
Re: System alive but can't access from the monitor
On 30/03/17 01:35, Ed Greshko wrote: On 03/30/17 14:24, Paolo Galtieri wrote: Folks, I have 2 F25 systems that have been updated today. These 2 systems share a monitor. One system is attached via a kvm switch to the monitor, the other system is attached via hdmi. This morning and twice this evening a problem has started to manifest itself. This configuration has been working fine for several years. I will call the systems A and B, system A is attached to the monitor via hdmi, system B via VGA. If I switch to system A for a while and then try to switch back to system B the monitor instead of staying on VGA cycles from VGA to DVI to HDMI and returns to system A. I can ssh into system B and everything looks fine, i.e. things that were running under my user id are still running, e.g. chrome and firefox. I looked at /var/log/messages and I see this: Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0... Mar 29 23:00:02 jackstraw systemd: Stopped target Default. Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System. Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets. Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket. Mar 29 23:00:02 jackstraw systemd: Stopped target Timers. Mar 29 23:00:02 jackstraw systemd: Stopped target Paths. Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown. Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session... Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588 (kill). This was at the time I switched from system A to system B. Each of the other times I saw this problem I see the same set of messages in the log file. Can someone explain what they mean and could they be the cause of the problem? I see the same messages on the other system, but there they were part of other messages related to rebooting the system. The only way I can recover is reboot the system. Here's my video card info: 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1) Any assistance is appreciated. Since everything is still running as it was it sounds similar to problems with monitors not coming back from sleep. Couple of questions. 1. Are you using the nouveau driver or the nVidia driver for your card? 2. Are you running GNOME under Wayland or X11? If you are using X11, and since you can ssh into the system, what is the output if you do... ssh systemB export DISPLAY=:0 xrandr Using my system as an example, does doing something like this bring the monitor back? [egreshko@meimei ~]$ acer Last login: Thu Mar 30 15:24:26 2017 from 192.168.1.18 [egreshko@acer ~]$ export DISPLAY=:0 [egreshko@acer ~]$ xrandr Screen 0: minimum 8 x 8, current 1280 x 800, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) LVDS-0 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1280x800 59.91*+ HDMI-0 disconnected (normal left inverted right x axis y axis) [egreshko@acer ~]$ xrandr --output LVDS-0 --off [egreshko@acer ~]$ xrandr --output LVDS-0 --auto With the last two kernels, using the nouveau driver, I am having graphic issues. I can open a session but once the screen locks, then I cannot get back to the desktop session. Using KDE from sddm and Xorg. These are in the dmesg output. [8.664136] nouveau :01:00.0: NVIDIA G84 (084000a2) [8.787588] nouveau :01:00.0: bios: version 60.84.55.00.08 [8.808963] nouveau :01:00.0: fb: 512 MiB GDDR3 [8.859472] nouveau :01:00.0: DRM: VRAM: 512 MiB [8.859476] nouveau :01:00.0: DRM: GART: 1048576 MiB [8.859484] nouveau :01:00.0: DRM: TMDS table version 2.0 [8.859488] nouveau :01:00.0: DRM: DCB version 4.0 [8.859494] nouveau :01:00.0: DRM: DCB outp 00: 02000300 0028 [8.859499] nouveau :01:00.0: DRM: DCB outp 01: 01000302 0030 [8.859503] nouveau :01:00.0: DRM: DCB outp 02: 04011310 0028 [8.859507] nouveau :01:00.0: DRM: DCB outp 03: 02011312 0030 [8.859511] nouveau :01:00.0: DRM: DCB outp 04: 010223f1 00c0c080 [8.859515] nouveau :01:00.0: DRM: DCB conn 00: 1030 [8.859518] nouveau :01:00.0: DRM: DCB conn 01: 2130 [8.859522] nouveau :01:00.0: DRM: DCB conn 02: 0210 [8.859525] nouveau :01:00.0: DRM: DCB conn 03: 0211 [8.859529] nouveau :01:00.0: DRM: DCB conn 04: 0213 [8.865523] nouveau :01:00.0: DRM: failed to create encoder 0/1/0: -19 [8.865528] nouveau :01:00.0: DRM: TV-1 has no encoders, removing [8.865830] nouveau :01:00.0: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). [8.877852] nouveau :01:00.0: DRM: MM: using CRYPT for buffer copies [8.938575] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x7, bo 936ca13d1c00 [8.940133] fbcon: nouveaufb (fb0) is
Re: Kernel errors
On Fri, Mar 31, 2017 at 8:48 AM, ProPAAS DBA wrote: > Hi All; > > I'm running Fedora 25, KDE spin on a Lenovo Thinkpad X1 Carbon 4th gen. > > I'm seeing errors like this on a pretty regular basis: > > 08:40:46 ... kernel:mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank > 128: 88282803 Message from syslogd@F25Host at Mar 31 08:40:46 ... > > Any thoughts on what this might be? Do I need to start shopping for a new > machine? > > Thanks in advance... > > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > > Further info: http://www.advancedclustering.com/act_kb/what-are-machine-check-exceptions-or-mce/ Try: root@localhost:/root> /usr/sbin/mcelog > mcelog.out Cat out mcelog.out and see if it affords any more detailed info. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Kernel errors
On Fri, 31 Mar 2017 08:48:21 -0600 ProPAAS DBA wrote: > I'm running Fedora 25, KDE spin on a Lenovo Thinkpad X1 Carbon 4th > gen. > > I'm seeing errors like this on a pretty regular basis: > > 08:40:46 ... kernel:mce: [Hardware Error]: CPU 2: Machine Check: 0 > Bank 128: 88282803 Message from syslogd@F25Host at Mar 31 > 08:40:46 ... > > Any thoughts on what this might be? Do I need to start shopping for a > new machine? The wikipedia explanation page. https://en.wikipedia.org/wiki/Machine-check_exception Some quotes from that page. "A Machine Check Exception (MCE) is a type of computer hardware error that occurs when a computer's central processing unit detects a hardware problem." "Normal causes for MCE errors include overheating and/or incorrect hardware installation. Specific manually-induced causes include: overclocking (which normally increases heat-output) poorly-fitted heatsink/computer fans (the same problem can happen with excessive dust in the CPU fan) an overloaded internal or external power-supply (fixable by upgrading) " ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On 03/31/2017 10:41 AM, Michael Schwendt wrote: rpm -Va 2>&1 | tee verify.txt Thank you very much for your teachings. I have learn a lot from you. I only found one file missing. pulse. Have no idea what it is for. -- All things are workable but don't all things work. Prov. 3:5 & 6 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On Fri, 31 Mar 2017 10:31:20 -0600, Lawrence E Graves wrote: > > dnf reinstall qt5-qtquickcontrols qt5-qtbase > > That was simple and it worked. Although I don't understand what took > place and why it did not load those files correctly the first time. You had "missing" files, i.e. packages reported as installed, but their contents gone missing for unknown reasons. Reinstalling the packages corrected that. Try running the follow command as root: rpm -Va 2>&1 | tee verify.txt When it's done, display the file "verify.txt" and especially watch out for "missing" files. The "man rpm" section on "VERIFY OPTIONS" tells what the output means. If you see too many missing or damaged files, you may want to reinstall their packages, too, and find out why you lose files. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On 03/31/2017 10:26 AM, Michael Schwendt wrote: dnf reinstall qt5-qtquickcontrols qt5-qtbase That was simple and it worked. Although I don't understand what took place and why it did not load those files correctly the first time. -- All things are workable but don't all things work. Prov. 3:5 & 6 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On Fri, 31 Mar 2017 10:22:05 -0600, Lawrence E Graves wrote: > [root@Jehovah ~]# rpm -Va qt5-qtquickcontrols qt5-qtbase > qt5-qtdeclarative mediawriter > missing /usr/lib64/qt5/qml/QtQuick/Controls > missing /usr/lib64/qt5/qml/QtQuick/Controls/ApplicationWindow.qml > missing /usr/lib64/qt5/qml/QtQuick/Controls/BusyIndicator.qml > missing /usr/lib64/qt5/qml/QtQuick/Controls/Button.qml -snip- dnf reinstall qt5-qtquickcontrols qt5-qtbase at least. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On Fri, 31 Mar 2017 13:57:22 +0200, Martin Bříza wrote: > On Fri, 31 Mar 2017 12:21:19 +0200, Lawrence E Graves > wrote: > > On 03/31/2017 01:54 AM, Martin Bříza wrote: > >> rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter > > [root@Jehovah ~]# rpm -q qt5-qtquickcontrols qt5-qtbase > > qt5-qtdeclarative mediawriter > > qt5-qtquickcontrols-5.7.1-2.fc25.x86_64 > > qt5-qtbase-5.7.1-14.fc25.x86_64 > > qt5-qtdeclarative-5.7.1-5.fc25.x86_64 > > mediawriter-4.0.8-0.fc25.x86_64 > > [ > > > > Honestly, I'm pretty lost. You seem to have the missing packages and you > seem to have the right versions... Trouble-shooting is _hard_, if the person experiencing the problem is so sparse with words. Just for the record, I've run "dnf -y install mediawriter", it installed these two packages, mediawriter x86_64 4.0.8-0.fc25 @updates 4.8 M qt5-qtquickcontrols x86_64 5.7.1-2.fc25 @updates 3.7 M and afterwards, it started without problems. Verifying the installed packages, especially qt5-qtquickcontrols, rpm -V mediawriter qt5-qtquickcontrols and then trying to reproduce with a fresh user account is what I would suggest, too. "rpm -Va" as superuser root is worth a try, because often it finds damaged or lost files a user hasn't noticed yet. Next would be a curious look at: ldd /usr/lib64/qt5/qml/QtQuick/Dialogs/libdialogplugin.so ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On 03/31/2017 10:12 AM, Ahmad Samir wrote: On 31 March 2017 at 12:21, Lawrence E Graves wrote: On 03/31/2017 01:54 AM, Martin Bříza wrote: rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter [root@Jehovah ~]# rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter qt5-qtquickcontrols-5.7.1-2.fc25.x86_64 qt5-qtbase-5.7.1-14.fc25.x86_64 qt5-qtdeclarative-5.7.1-5.fc25.x86_64 mediawriter-4.0.8-0.fc25.x86_64 [ A shot in the dark, also check that the packages are installed correctly: rpm -Va qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter [root@Jehovah ~]# rpm -Va qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter missing /usr/lib64/qt5/qml/QtQuick/Controls missing /usr/lib64/qt5/qml/QtQuick/Controls/ApplicationWindow.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/BusyIndicator.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Button.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Calendar.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/CheckBox.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/ComboBox.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/GroupBox.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Label.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Menu.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/MenuBar.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/AbstractCheckable.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/BasicButton.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/BasicTableView.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/CalendarHeaderModel.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/CalendarUtils.js missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/ColumnMenuContent.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/ContentItem.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/Control.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/EditMenu.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/EditMenu_base.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/FastGlow.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/FocusFrame.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/HoverButton.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/MenuContentItem.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/MenuContentScroller.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/MenuItemSubControls.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/ModalPopupBehavior.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollViewHelper.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/SourceProxy.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/StackView.js missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/StackViewSlideDelegate.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/Style.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/SystemPaletteSingleton.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/TabBar.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/TableViewItemDelegateLoader.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/TableViewSelection.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/TextHandle.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/TextInputWithHandles.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/TextSingleton.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/ToolMenuButton.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/TreeViewItemDelegateLoader.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/qmldir missing /usr/lib64/qt5/qml/QtQuick/Controls/Private/style.js missing /usr/lib64/qt5/qml/QtQuick/Controls/ProgressBar.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/RadioButton.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Slider.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/SpinBox.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/SplitView.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/StackView.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/StackViewDelegate.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/StackViewTransition.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/StatusBar.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Styles missing /usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base missing /usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/ApplicationWindowStyle.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/BasicTableViewStyle.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/BusyIndicatorStyle.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/ButtonStyle.qml missing /usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/CalendarStyle.qml missing /usr/lib64/qt5/qml/Qt
Re: Not able to launch mediawriter
On 31 March 2017 at 12:21, Lawrence E Graves wrote: > > > On 03/31/2017 01:54 AM, Martin Bříza wrote: >> >> rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter > > [root@Jehovah ~]# rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative > mediawriter > qt5-qtquickcontrols-5.7.1-2.fc25.x86_64 > qt5-qtbase-5.7.1-14.fc25.x86_64 > qt5-qtdeclarative-5.7.1-5.fc25.x86_64 > mediawriter-4.0.8-0.fc25.x86_64 > [ A shot in the dark, also check that the packages are installed correctly: rpm -Va qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter -- Ahmad Samir ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Kernel errors
Hi All; I'm running Fedora 25, KDE spin on a Lenovo Thinkpad X1 Carbon 4th gen. I'm seeing errors like this on a pretty regular basis: 08:40:46 ... kernel:mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 128: 88282803 Message from syslogd@F25Host at Mar 31 08:40:46 ... Any thoughts on what this might be? Do I need to start shopping for a new machine? Thanks in advance... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: F24 system shutdown during dnf cleanup
I would recommend to get inspired by article http://dnf.baseurl.org/2016/12/15/repair-of-broken-system-with-dnf-2-0/ where you can find how to repair broken system. With dnf-2.0 you can use "dnf check" command, that could reveal problems on your system. Hope that it will help Jaroslav On Fri, Mar 31, 2017 at 12:11 AM, Robert Moskowitz wrote: > Today I was doing a dnf update and had a few things being updated and new > kernel installed. > > Right when it was past cleanup messages and you are waiting for the > complete message, I lost power and for some reason the system did a > shutdown. Got that little active image Fedora shows during a shutdown. > > The system restarted ok. How do I find out what the state is? What might > still need to be done? When I grep for 'kernel' in /var/log/dnf.log I get: > > Mar 30 12:38:22 SUBDEBUG drpm: spawned 19063: /usr/bin/applydeltarpm -a > x86_64 /var/cache/dnf/updates-c4f1c95f64c2b794/packages/kernel- > headers-4.9.13-101.fc24_4.9.17-100.fc24.x86_64.drpm > /var/cache/dnf/updates-c4f1c95f64c2b794/packages/kernel- > headers-4.9.17-100.fc24.x86_64.rpm > > > And the last install for kernel was: > > Mar 30 12:38:03 DEBUG ---> Package kernel-modules.x86_64 4.9.9-100.fc24 > will be erased > kernel x86_64 4.9.17-100.fc24 updates80 k > kernel-core x86_64 4.9.17-100.fc24 updates20 M > kernel-debug-core x86_64 4.9.17-100.fc24 updates21 M > kernel-debug-modulesx86_64 4.9.17-100.fc24 updates23 M > kernel-debug-modules-extra x86_64 4.9.17-100.fc24 updates 2.3 M > kernel-modules x86_64 4.9.17-100.fc24 updates22 M > kernel-headers x86_64 4.9.17-100.fc24 updates 1.1 M > kernel x86_64 4.9.9-100.fc24 @updates0 > kernel-core x86_64 4.9.9-100.fc24 @updates 53 M > kernel-debug-core x86_64 4.9.9-100.fc24 @updates 55 M > kernel-debug-modulesx86_64 4.9.9-100.fc24 @updates 22 M > kernel-debug-modules-extra x86_64 4.9.9-100.fc24 @updates 2.1 M > kernel-modules x86_64 4.9.9-100.fc24 @updates 22 M > > > How do I check this out? > > thanks. > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On 03/31/17 18:21, Lawrence E Graves wrote: > > > On 03/31/2017 01:54 AM, Martin Bříza wrote: >> rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter > [root@Jehovah ~]# rpm -q qt5-qtquickcontrols qt5-qtbase > qt5-qtdeclarative mediawriter > qt5-qtquickcontrols-5.7.1-2.fc25.x86_64 > qt5-qtbase-5.7.1-14.fc25.x86_64 > qt5-qtdeclarative-5.7.1-5.fc25.x86_64 > mediawriter-4.0.8-0.fc25.x86_64 > [ > If you do an "ldd -v /usr/bin/mediawriter" is there anything not right with the output? Could you create a new user and try starting it under the new user? And not as root. -- Fedora Users List - The place to go to get others to do the work for you ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On 03/31/2017 05:57 AM, Martin Bříza wrote: On Fri, 31 Mar 2017 12:21:19 +0200, Lawrence E Graves wrote: On 03/31/2017 01:54 AM, Martin Bříza wrote: rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter [root@Jehovah ~]# rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter qt5-qtquickcontrols-5.7.1-2.fc25.x86_64 qt5-qtbase-5.7.1-14.fc25.x86_64 qt5-qtdeclarative-5.7.1-5.fc25.x86_64 mediawriter-4.0.8-0.fc25.x86_64 [ Honestly, I'm pretty lost. You seem to have the missing packages and you seem to have the right versions... Exactly what I am experiencing. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org -- All things are workable but don't all things work. Prov. 3:5 & 6 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On Fri, 31 Mar 2017 12:21:19 +0200, Lawrence E Graves wrote: On 03/31/2017 01:54 AM, Martin Bříza wrote: rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter [root@Jehovah ~]# rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter qt5-qtquickcontrols-5.7.1-2.fc25.x86_64 qt5-qtbase-5.7.1-14.fc25.x86_64 qt5-qtdeclarative-5.7.1-5.fc25.x86_64 mediawriter-4.0.8-0.fc25.x86_64 [ Honestly, I'm pretty lost. You seem to have the missing packages and you seem to have the right versions... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On 03/31/2017 01:54 AM, Martin Bříza wrote: rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter [root@Jehovah ~]# rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter qt5-qtquickcontrols-5.7.1-2.fc25.x86_64 qt5-qtbase-5.7.1-14.fc25.x86_64 qt5-qtdeclarative-5.7.1-5.fc25.x86_64 mediawriter-4.0.8-0.fc25.x86_64 [ -- All things are workable but don't all things work. Prov. 3:5 & 6 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On Fri, 31 Mar 2017 09:50:44 +0200, Joe Zeff wrote: On 03/31/2017 12:36 AM, Martin Bříza wrote: On Thu, 30 Mar 2017 19:11:56 +0200, Joe Zeff wrote: On 03/30/2017 06:34 AM, Martin Bříza wrote: first, please don't run mediawriter as root. Second, this is because it cannot find the Qt Quick Controls. These should be included in the qt5-qtquickcontrols package, which is a dependency of mediawriter. Did you modify your installation of one of these packages? The Fedora documentation says it needs to be run using sudo, which is the same as running it as root. Uh, can you please point me to where does it say that? It definitely shouldn't say that. With pleasure: https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/sect-preparing-boot-media.html As a matter of fact, the instructions are wrong because they tell you to run liveusb-creator, not mediawriter, as you can see by this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1434185 Thank you! You're right, there's a few errors which is strange because half of the document points to the right application. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On Thu, 30 Mar 2017 18:22:20 +0200, Lawrence E Graves wrote: On 03/30/2017 08:18 AM, Martin Bříza wrote: rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative Mine came back the same as yours did but still unable to launch mediawriter. Hmm, that's pretty odd. I'm not sure what else to recommend than fully updating your system. From what you say, it should be okay nevertheless though. :/ Just out of curiosity though please, can you post the output of the following command in your next reply? # rpm -q qt5-qtquickcontrols qt5-qtbase qt5-qtdeclarative mediawriter ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On 03/31/2017 12:36 AM, Martin Bříza wrote: On Thu, 30 Mar 2017 19:11:56 +0200, Joe Zeff wrote: On 03/30/2017 06:34 AM, Martin Bříza wrote: first, please don't run mediawriter as root. Second, this is because it cannot find the Qt Quick Controls. These should be included in the qt5-qtquickcontrols package, which is a dependency of mediawriter. Did you modify your installation of one of these packages? The Fedora documentation says it needs to be run using sudo, which is the same as running it as root. Uh, can you please point me to where does it say that? It definitely shouldn't say that. With pleasure: https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/sect-preparing-boot-media.html As a matter of fact, the instructions are wrong because they tell you to run liveusb-creator, not mediawriter, as you can see by this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1434185 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not able to launch mediawriter
On Thu, 30 Mar 2017 19:11:56 +0200, Joe Zeff wrote: On 03/30/2017 06:34 AM, Martin Bříza wrote: first, please don't run mediawriter as root. Second, this is because it cannot find the Qt Quick Controls. These should be included in the qt5-qtquickcontrols package, which is a dependency of mediawriter. Did you modify your installation of one of these packages? The Fedora documentation says it needs to be run using sudo, which is the same as running it as root. Uh, can you please point me to where does it say that? It definitely shouldn't say that. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
