#9909 Fedora Media Writer 4.1.8 released
Closed: Invalid 3 years ago by jgrulich. Opened 3 years ago by jgrulich.

Describe the issue
A new Media Writer has been released today with some changes in Mac OS bundle, which should now work on Mac OS Big Sur. I would like to ask you to make official/signed builds.
Link to the release: https://github.com/FedoraQt/MediaWriter/releases/tag/4.1.8

When do you need this? (YYYY/MM/DD)
The sooner the better.

If we cannot complete your request, what is the impact?
MediaWriter not working on Mac OS Big Sur.


@kevin When you get a chance :smile:

Metadata Update from @mohanboddu:
- Issue assigned to kevin
- Issue tagged with: medium-gain, medium-trouble, ops

3 years ago

Hi, here is the windows signed binary

Sorry for the lengthy delay here.

osx signed: https://scrye.com/~kevin/fedora/FedoraMediaWriter-osx-4.1.7.dmg

@kparal @adamw

Can we get a quick round of testing on these? Should we add a process where we get qa signoff? Or should we just put them about the uss-shipit and call it good?

@lbrabec Is Mac OS Big Sur available for the Mac Mini we have? (I don't think so, but checking just to be sure). If not, I'm not aware of any device where we could check this.

No, afaik High Sierra only.

We could kindly ask @jsedlak or @mkrizek

I will test it myself.

I can test whether FMW works on Big Sur, but I am not able to test whether created flash drive is bootable.

Sorry for the lengthy delay here.

osx signed: https://scrye.com/~kevin/fedora/FedoraMediaWriter-osx-4.1.7.dmg

@kparal @adamw

Can we get a quick round of testing on these? Should we add a process where we get qa signoff? Or should we just put them about the uss-shipit and call it good?

Either I'm doing something wrong, because I don't know how to use Mac OS properly, but it tells me it comes from unverified developer and I still have to go through the same process as with non-verified app, that means going to settings → security and allow it from there.

I can test whether FMW works on Big Sur, but I am not able to test whether created flash drive is bootable.

For the record, that is not necessary, you can simply do cmp ISO device and if it matches, FMW did its job properly.

Starting FMW 4.1.7 on macOS Big Sur gives me SIGABRT every time I try to run it. Note that it's being reported as FMW 4.1.6 in log.

Process:               Fedora Media Writer [29875]
Path:                  /Applications/Fedora Media Writer.app/Contents/MacOS/Fedora Media Writer
Identifier:            org.fedoraproject.MediaWriter
Version:               4.1.6 (4.1.6)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Fedora Media Writer [29875]
User ID:               501

Date/Time:             2021-01-12 09:51:05.166 +0100
OS Version:            macOS 11.1 (20C69)
Report Version:        12
Bridge OS Version:     5.1 (18P3030)
Anonymous UUID:        66534F39-2211-AF03-B119-70294F568600

Sleep/Wake UUID:       3D835FEA-369B-478C-B400-EE661E487A15

Time Awake Since Boot: 100000 seconds
Time Since Wake:       290 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  dyld: Using shared cache: 467A83CB-BA86-3F07-B652-B9256C74080A
Library not loaded: @rpath/QtQuick.framework/Versions/5/QtQuick
  Referenced from: /Applications/Fedora Media Writer.app/Contents/MacOS/Fedora Media Writer
  Reason: image not found

Binary Images:
       0x109f22000 -        0x10a228fff +org.fedoraproject.MediaWriter (4.1.6 - 4.1.6) <6F670A5E-90DC-3EAB-842A-906572685768> /Applications/Fedora Media Writer.app/Contents/MacOS/Fedora Media Writer
       0x119c61000 -        0x119cfcfff  dyld (832.7.1) <DEA51514-B4E8-3368-979B-89D0F8397ABC> /usr/lib/dyld
    0x7fff2115d000 -     0x7fff214c0fff  com.apple.Foundation (6.9 - 1770.300) <44A7115B-7FF0-3300-B61B-0FA71B63C715> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff26518000 -     0x7fff2651efff  com.apple.DiskArbitration (2.7 - 2.7) <83DED679-BE65-3475-8AFF-D664BBAFA60A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration

Model: MacBookAir9,1, BootROM 1554.60.15.0.0 (iBridge: 18.16.13030.0.0,0), 4 processors, Quad-Core Intel Core i5, 1,1 GHz, 16 GB, SMC 
Graphics: kHW_IntelIrisPlusGraphicsItem, Intel Iris Plus Graphics, spdisplays_builtin
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, LPDDR4X, 3733 MHz, SK Hynix, H9HCNNNFBMALPR-NEE
Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, LPDDR4X, 3733 MHz, SK Hynix, H9HCNNNFBMALPR-NEE
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Sep 11 2020 17:38:16 version 16.20.293.5.3.6.95 FWID 01-e5bd2163
Bluetooth: Version 8.0.2f9, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: BillBoard Device
USB Device: USB 3.1 Bus
USB Device: Apple T2 Bus
USB Device: Touch Bar Backlight
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Air, Apple Inc., 85.0

Starting FMW 4.1.7 on macOS Big Sur gives me SIGABRT every time I try to run it. Note that it's being reported as FMW 4.1.6 in log.

```
Process: Fedora Media Writer [29875]
Path: /Applications/Fedora Media Writer.app/Contents/MacOS/Fedora Media Writer
Identifier: org.fedoraproject.MediaWriter
Version: 4.1.6 (4.1.6)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Fedora Media Writer [29875]
User ID: 501

Date/Time: 2021-01-12 09:51:05.166 +0100
OS Version: macOS 11.1 (20C69)
Report Version: 12
Bridge OS Version: 5.1 (18P3030)
Anonymous UUID: 66534F39-2211-AF03-B119-70294F568600

Sleep/Wake UUID: 3D835FEA-369B-478C-B400-EE661E487A15

Time Awake Since Boot: 100000 seconds
Time Since Wake: 290 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
dyld: Using shared cache: 467A83CB-BA86-3F07-B652-B9256C74080A
Library not loaded: @rpath/QtQuick.framework/Versions/5/QtQuick
Referenced from: /Applications/Fedora Media Writer.app/Contents/MacOS/Fedora Media Writer
Reason: image not found

Binary Images:
0x109f22000 - 0x10a228fff +org.fedoraproject.MediaWriter (4.1.6 - 4.1.6) <6F670A5E-90DC-3EAB-842A-906572685768> /Applications/Fedora Media Writer.app/Contents/MacOS/Fedora Media Writer
0x119c61000 - 0x119cfcfff dyld (832.7.1) <DEA51514-B4E8-3368-979B-89D0F8397ABC> /usr/lib/dyld
0x7fff2115d000 - 0x7fff214c0fff com.apple.Foundation (6.9 - 1770.300) <44A7115B-7FF0-3300-B61B-0FA71B63C715> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff26518000 - 0x7fff2651efff com.apple.DiskArbitration (2.7 - 2.7) <83DED679-BE65-3475-8AFF-D664BBAFA60A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration

Model: MacBookAir9,1, BootROM 1554.60.15.0.0 (iBridge: 18.16.13030.0.0,0), 4 processors, Quad-Core Intel Core i5, 1,1 GHz, 16 GB, SMC
Graphics: kHW_IntelIrisPlusGraphicsItem, Intel Iris Plus Graphics, spdisplays_builtin
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, LPDDR4X, 3733 MHz, SK Hynix, H9HCNNNFBMALPR-NEE
Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, LPDDR4X, 3733 MHz, SK Hynix, H9HCNNNFBMALPR-NEE
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Sep 11 2020 17:38:16 version 16.20.293.5.3.6.95 FWID 01-e5bd2163
Bluetooth: Version 8.0.2f9, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: BillBoard Device
USB Device: USB 3.1 Bus
USB Device: Apple T2 Bus
USB Device: Touch Bar Backlight
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Air, Apple Inc., 85.0
```

@kevin how did you build the binary? Comparing your build and the non-signed I produced, I can see the path to libraries are different.

Was using our SOP: https://docs.pagure.org/releng/sop_fedora_media_writer.html

But I see now something is wacky with xcode. ;( There are updates pending, so let me try and update and reboot and see if I can get it to run better.

ok, after fighting with xcode all day I think I have it working. ;)

can you try the new build at:

https://scrye.com/~kevin/fedora/FedoraMediaWriter-osx-4.1.7.dmg

Hi, I just released a new stable version. There were two issues in the previous one. Can you please update to 4.1.8?

Same problem, doesn't work. Looking into the document how you do it, I don't think you should install old Qt 5.7 in the first place. Can you do one of the following options?

1) Run the MacOS build script shipped with MediaWriter
2) Just sign the build I produced

See https://github.com/FedoraQt/MediaWriter/blob/4.1/dist/mac/build.sh#L46. There are additional steps needed to produce a working bundle.

I don't think we want to just sign your build... so I will look at the script. Thanks!

Sorry that last comment reads a bit rude, which was not intended. We just don't want to sign binaries that were not built by releng or in a controlled env like koji.

I got things to build using your build.sh. Thanks! But I'm now hitting a missing ../app/Entitlements.plist file?

I gather I can generate one via Xcode? Or should I use an existing one? Thoughts?

And sorry this is turning out to be a hassle. :(

I got things to build using your build.sh. Thanks! But I'm now hitting a missing ../app/Entitlements.plist file?

I gather I can generate one via Xcode? Or should I use an existing one? Thoughts?

I think you need to generate one, but I have never used this part of the script. Also, the script was not originally written by me.

Did you also install newer Qt? Here is a list of things we install and do in github to produce a Mac OS bundle with the script:

brew install qt
echo 'export PATH="/usr/local/opt/qt/bin:$PATH"' >> ~/.bash_profile
brew install xz
brew install git
brew install cmake
npm install -g create-dmg

I wonder whether we can use some Fedora CI to make this all automated? Make it watch for new releases of FMW and do signed builds automatically and publishing them on the website.

Yeah, I have installed all those. I managed to find/create a Entitlements.plist

This let me build a unnotorized one:
https://scrye.com/~kevin/fedora/FedoraMediaWriter-osx-4.1.8.unnotarized.dmg
Give that a try?

I'd love to have a better/official way to build this. In the past we were stuck by not having hardware easily available.
However, I see aws now offers osx instsances, so perhaps we could setup something in CI/buildsystem to do this.

Looks good. I checked that library paths are correct and the app works for me.

So, @humaton can you do a windows 4.1.8? Then I guess we should get a bit more testing and push them out?

We really need to find a way how to automate this. There is already a new version of Fedora Media Writer, this time it's quite a big update and there are new dependencies, but I would like to get this one out first.

I agree.

So, I put the 4.1.8 one in place (although not yet with the latest link).

@humaton can you build the windows one, upload it and update the latest links on them?

I don't know if we need to do anything else to make them live on the website or not.

@jgrulich so there is no 4.1.8 version in koji without those RPMS I am unable to sign 4.1.8 version. Do you want me to sign 4.2.0 ?

I am sorry for the delays but notifications from pagure just don't work for me :/

When I try to build the 4.2.0 version it fails with

=== Composing installer
+ unix2dos
./build.sh: line 200: /home/thrcka/projects/MediaWriter/LICENSE: No such file or directory

@humaton: I think we can try to build 4.2.0 already. I will open a new issue and CC you there. I will also try to build it locally for Windows and push fixed version so you can build it.

Metadata Update from @jgrulich:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Done