users March 2017

users@lists.fedoraproject.org

110 participants
89 discussions

Kernel errors
by ProPAAS DBA 31 Mar '17

31 Mar '17

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: 0000000088282803 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...

3 2

Not able to launch mediawriter
by Lawrence E Graves 31 Mar '17

31 Mar '17

[root@Jehovah ~]# mediawriter Warning: QQmlApplicationEngine failed to load component ((null):0, (null)) Warning: qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed qrc:/main.qml:21 module "QtQuick.Controls" is not installed qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed qrc:/main.qml:21 module "QtQuick.Controls" is not installed qrc:/main.qml:22 module "QtQuick.Controls.Styles" is not installed qrc:/main.qml:24 module "QtQuick.Dialogs" is not installed qrc:/main.qml:21 module "QtQuick.Controls" is not installed ((null):0, (null)) I am running Fedora 25. What to do? -- All things are workable but don't all things work. Prov. 3:5 & 6

7 26

F24 system shutdown during dnf cleanup
by Robert Moskowitz 31 Mar '17

31 Mar '17

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 updates 80 k kernel-core x86_64 4.9.17-100.fc24 updates 20 M kernel-debug-core x86_64 4.9.17-100.fc24 updates 21 M kernel-debug-modules x86_64 4.9.17-100.fc24 updates 23 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 updates 22 M kernel-headers x86_64 4.9.17-100.fc24 updates 1.1 M kernel x86_64 4.9.9-100.fc24 @updates 0 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-modules x86_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.

2 1

dnf aborting
by Kevin Cummings 31 Mar '17

31 Mar '17

I last updated: Mar 27 01:01:34 INFO Upgraded: icoutils-0.31.3-1.fc24.x86_64 Mar 27 01:01:35 INFO Cleanup: icoutils-0.31.2-1.fc24.x86_64 Since then, dnf update aborts with: > *** Error in `/usr/bin/python3': realloc(): invalid next size: 0x00005597a7b29670 *** > ======= Backtrace: ========= > /lib64/libc.so.6(+0x7570b)[0x7f66a367e70b] > /lib64/libc.so.6(+0x8080c)[0x7f66a368980c] > /lib64/libc.so.6(realloc+0x184)[0x7f66a368a714] > /lib64/libsolv.so.0(solv_realloc+0x1e)[0x7f6693c2e21e] > /lib64/libsolv.so.0(+0x40cfb)[0x7f6693c2dcfb] > /lib64/libsolv.so.0(+0x33bea)[0x7f6693c20bea] > /lib64/libsolv.so.0(dataiterator_step+0x1161)[0x7f6693c292e1] > /lib64/libhawkey.so.2(+0xf5c4)[0x7f6693e835c4] > /lib64/libhawkey.so.2(hy_query_apply+0x10a3)[0x7f6693e84bf3] > /lib64/libhawkey.so.2(hy_query_run_set+0x9)[0x7f6693e85ef9] > /lib64/libhawkey.so.2(running_kernel+0xac)[0x7f6693e8131c] > /lib64/libhawkey.so.2(sack_running_kernel+0x17)[0x7f6693e870e7] > /lib64/libhawkey.so.2(hy_goal_run_all_flags+0x4bc)[0x7f6693e7f81c] > /usr/lib64/python3.5/site-packages/hawkey/_hawkey.so(+0xa84e)[0x7f669409c84e] > /lib64/libpython3.5m.so.1.0(PyCFunction_Call+0xe9)[0x7f66a43a4f29] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x75b9)[0x7f66a441c759] > /lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x5f59)[0x7f66a441b0f9] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4] > /lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x5f59)[0x7f66a441b0f9] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4] > /lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3] > /lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x5f59)[0x7f66a441b0f9] > /lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3] > /lib64/libpython3.5m.so.1.0(PyEval_EvalCodeEx+0x23)[0x7f66a441eab3] > /lib64/libpython3.5m.so.1.0(PyEval_EvalCode+0x1b)[0x7f66a441eadb] > /lib64/libpython3.5m.so.1.0(+0x146d64)[0x7f66a443dd64] > /lib64/libpython3.5m.so.1.0(PyRun_FileExFlags+0x95)[0x7f66a44402b5] > /lib64/libpython3.5m.so.1.0(PyRun_SimpleFileExFlags+0xf4)[0x7f66a4440424] > /lib64/libpython3.5m.so.1.0(Py_Main+0xedc)[0x7f66a445708c] > /usr/bin/python3(main+0x170)[0x5597a3886b70] > /lib64/libc.so.6(__libc_start_main+0xf1)[0x7f66a3629731] > /usr/bin/python3(_start+0x29)[0x5597a3886c19] Anyone else seeing this? -- Kevin J. Cummings kjchome(a)verizon.net cummings(a)kjchome.homeip.net cummings(a)kjc386.framingham.ma.us Registered Linux User #1232 (http://www.linuxcounter.net/)

4 6

BackupPC 4.1.0 testing needed - Any BackupPC users on the group?
by Richard Shaw 30 Mar '17

30 Mar '17

I have taken over maintenance of the BackupPC package and have made the update to 4.1.0 available through COPR[1] for now for a couple of reasons: 1. It's a huge change, hardlinks are no longer used for deduplication, but v4 can read v3 backups. 2. Some of the settings in /etc/BackupPC/config.pl were tweaked and need manual attention after the upgrade. See https://backuppc.github.io/backuppc/BackupPC.html#BackupPC-4.0 for details. The plan is to update f26 and rawhide to v4 and leave f25 and EPEL alone. Those that want to update to v4 can use the COPR. Thanks, Richard [1] https://copr.fedorainfracloud.org/coprs/hobbes1069/BackupPC/

2 2

Restoring a QEMU snapshot
by Patrick O'Callaghan 29 Mar '17

29 Mar '17

I have a QEMU image snapshot: $ sudo qemu-img info /var/lib/libvirt/images/Windows10.qcow2 image: /var/lib/libvirt/images/Windows10.qcow2 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 196K cluster_size: 65536 backing file: /home/poc/Win10/win10.qcow2 backing file format: qcow2 Format specific information: compat: 1.1 lazy refcounts: true refcount bits: 16 corrupt: false However when I try to restore the virtual disk I get: $ sudo qemu-img snapshot -a /var/lib/libvirt/images/Windows10.qcow2 /home/poc/Win10/win10.qcow2 qemu-img: Could not apply snapshot '/var/lib/libvirt/images/Windows10.qcow2': -2 (No such file or directory) I must be doing something obviously wrong, but can't see what it is. Hints would be appreciated. poc

4 20

Firefox and flash plugin
by Terry Polzin 29 Mar '17

29 Mar '17

Firefox is complaining about flash not being up to date. I believe i have the latest of both. dnf list installed | grep -e firefox -e flash-plugin firefox.x86_64 52.0-6.fc25 @updates flash-plugin.x86_64 25.0.0.127-release @adobe-linux-x86_64

7 7

vmware-tray received an X Window System error
by Dominik Kucher 29 Mar '17

29 Mar '17

Is that a bug? i have installed today the update to 12.5.5 The program 'vmware-tray' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 2374408 error_code 141 request_code 138 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- Dominik Kucher

1 0

monitor restarting (from sleep) issue on F25, HP Envy
by Matt Morgan 29 Mar '17

29 Mar '17

I just bought an HP Envy and installed F25 over the weekend. I have a few problems I did not have on the Dell XPS 13 it replaced. First, upon resuming from sleep, my external monitor doesn't wake up. The monitor says it's getting no input from the PC, and the Displays settings app doesn't show a second monitor. The only differences from before are a) the XPS 13 had a mini-displayport, and this one is HDMI b) this is a fresh install of F25, where the old computer was upgraded probably from F22. What can I do, any suggestions? Right now only rebooting seems to work. Thanks, Matt

2 1

F25: Desktop PC not booting without a screen
by Eigeldinger Simon 28 Mar '17

28 Mar '17

Hi all, I am Simon and I am blind. I tried to boot a Fedora Workstation 25 live USB without a screen attached to a desktop machine. It seems the machine doesn't boot completely at least hanging while the desktop should come up. On the arch wiki i read something about x server and its autoconfig mode where it detects the screen and if no screen is present it stops starting the desktop which makes the PC hang. According to the wayland mailing list this also happens with wayland though wayland supports screenless booting. which needs to be specified in the wayland adapter for gnome. Anyone maybe knows more about that? I thought of using Fedora on a project i have in my mind. Having a small PC without a screen in the kitchen would be pretty interesting. navigation is done using a keyboard and knowing where we are is done using the orca screen reader and speakers. Attaching a screen would be the last thing i want to do. Greetings, Simon Mit freundlichen Grüßen Simon Eigeldinger Informatik Nebengebäude 1, OG1 Stadt Hohenems Kaiser-Franz-Josef-Straße 4 6845 Hohenems Österreich Tel.: +43 5576 7101-1143 Fax: +43 5576 7101-1149 E-Mail: simon.eigeldinger(a)hohenems.at<mailto:simon.eigeldinger@hohenems.at> Web: www.hohenems.at<http://www.hohenems.at> Diese Nachricht und allfällige angehängte Dokumente sind vertraulich und nur für den/die Adressaten bestimmt.

4 9

← Newer
1
2
3
4
5
6
7
8
9
Older →