Description of problem: I simply executed Fedora Media Writer and tried to make a USB bootable image. The whole system then froze. Version-Release number of selected component: mediawriter-4.0.7-0.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mediawriter crash_function: nouveau_pushbuf_data executable: /usr/bin/mediawriter global_pid: 2858 kernel: 4.8.8-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 nouveau_pushbuf_data at pushbuf.c:727 #6 nouveau_pushbuf_space at pushbuf.c:689 #7 PUSH_SPACE at ./nouveau_winsys.h:31 #8 BEGIN_NVC0 at nvc0/nvc0_winsys.h:116 #9 nvc0_validate_stipple at nvc0/nvc0_state_validate.c:262 #10 nvc0_state_validate at nvc0/nvc0_state_validate.c:785 #11 nvc0_state_validate_3d at nvc0/nvc0_state_validate.c:803 #12 nvc0_draw_vbo at nvc0/nvc0_vbo.c:977 #13 st_draw_vbo at state_tracker/st_draw.c:251 #14 vbo_validated_drawrangeelements at vbo/vbo_exec_array.c:850
Created attachment 1224820 [details] File: backtrace
Created attachment 1224821 [details] File: cgroup
Created attachment 1224822 [details] File: core_backtrace
Created attachment 1224823 [details] File: dso_list
Created attachment 1224824 [details] File: environ
Created attachment 1224825 [details] File: limits
Created attachment 1224826 [details] File: maps
Created attachment 1224827 [details] File: mountinfo
Created attachment 1224828 [details] File: namespaces
Created attachment 1224829 [details] File: open_fds
Created attachment 1224830 [details] File: proc_pid_status
Created attachment 1224831 [details] File: var_log_messages
Hello, I'm sorry you're experiencing such issues. Please, can you try updating your "mesa-" packages using the repository at [1] and report back with information if that helped or not? [1] https://copr.fedorainfracloud.org/coprs/kkofler/qtwebengine/
*** Bug 1398650 has been marked as a duplicate of this bug. ***
*** Bug 1399041 has been marked as a duplicate of this bug. ***
The crash is coming from the driver, reassigning to it.
*** Bug 1403157 has been marked as a duplicate of this bug. ***
Mostly mediawriter has been consistently hanging my system when attempting to restore a usb stick, with the occasional abort. In F25, when video acceleration was turned off, mediawriter performed correctly, and "restored" a usb stick which had a bootable iso on it. /etc/X11/xorg.conf.d/20-nouveau.conf Section "Device" Identifier "GeForce 6150 LE" Driver "nouveau" Option "AccelMethod" "none" EndSection
What is the status of this?
Similar problem has been detected: Selecting KDE, the software crash reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mediawriter crash_function: nouveau_pushbuf_data executable: /usr/bin/mediawriter global_pid: 3103 kernel: 4.10.10-200.fc25.x86_64 package: mediawriter-4.0.95-1.fc26 pkg_vendor: Fedora Project reason: mediawriter killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: When I select the image to burn (fedora workstation for instance, or also selecting kde spin), the download seems to start, but after a little bit of time, mediawriter crashes. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mediawriter crash_function: nouveau_pushbuf_data executable: /usr/bin/mediawriter global_pid: 5590 kernel: 4.10.10-200.fc25.x86_64 package: mediawriter-4.0.95-1.fc26 pkg_vendor: Fedora Project reason: mediawriter killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Anyone concerned to fix this? In an upstream issue (https://github.com/MartinBriza/MediaWriter/issues/90) the author said, this is a driver issue of the nouveau driver. It's especially bad as it happened to me exactly at the most important point where the program is used. And in my case it froze the *whole system*! That's the worst UX you can get. I would have expected it to be better for such an important, official Fedora tool! You cannot share Fedora with anyone if you cannot create an installation image!
Similar problem has been detected: d/l'ed fedora 26; using fedora 25; installed liveusb-creator (installs as mediawriter); ran mediawriter (not sudo); selected desktop; that's it reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mediawriter crash_function: nouveau_pushbuf_data executable: /usr/bin/mediawriter global_pid: 2629 kernel: 4.11.8-200.fc25.x86_64 package: mediawriter-4.1.0-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: mediawriter killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.