[Unstable Update] 2021-03-27 - Gnome 40, Kernels, Browsers, Haskell, Pipewire, AMDVLK, Wine

anon88624618 · 28 March 2021 12:58

The aur package I’m using has already been updated…

servimo · 28 March 2021 19:35

My pamac gui is with this:

2021-03-28_15-03

I have gtk3-classic and gtk3-nocsd installed.
Normal gtk3 does the same.

philm · 28 March 2021 20:55

You may want to reenable CSD as this is the way forward. XFCE will add more CSD in future anyway. Maybe took also a look at libxfce4ui-nocsd.

robin0800 · 28 March 2021 21:07

This is mine

philm · 28 March 2021 21:07

Also we are in the process to port Pamac to GTK4 so we match upcoming Gnome changes better.

servimo · 28 March 2021 21:09

I removed gtk3-nocsd but kept gtk3-classic, I don`t like the dialogs of normal gtk3 because it is too long.

robin0800 · 28 March 2021 21:12

You can still have “gt3-nocsd” with “gtk3_classic” no conflicts.
This for me fixes pamac.

servimo · 28 March 2021 21:28

Did you use another window manager? Openbox?

robin0800 · 28 March 2021 21:28

no just standard.
Top bar is “cinnXP-Embedded” (AUR)

servimo · 28 March 2021 21:37

You are using cinnamon
I am on XFCE

robin0800 · 28 March 2021 21:39

yes I am I love it.

D.Dave · 28 March 2021 22:12

You can try to execute this command in a Terminal:
xfconf-query -c xsettings -p /Gtk/DialogsUseHeader -s false

Then reboot.

stargazer · 29 March 2021 06:49

I’m so glad that you mentioned this @philm. I’ve been dying to ask you this ever since I saw your post, “After looking at it again, it was one of the best decision by XFCE team to do it. I would even liked they did the full switch IMHO.” I felt it was too late to ask then and decided I’d watch and learn.

I want to get on the happy-csd-train too What was the technical lightbulb moment for you, when you got onboard with CSD and the direction GTK is going?

Thank you.

nyepi · 29 March 2021 11:11

Possible typo in ISO build workflow

github.com/manjaro/release-review

Possible typo in ISO build workflow

opened 05:21AM - 17 Mar 21 UTC

closed 05:24PM - 08 Apr 21 UTC

bryanjhv

I was trying to build an ISO, using as guide the workflow for ISO build you have… here. Then, I noticed the following, which might be a typo: https://github.com/manjaro/release-review/blob/603b9d908f899998d1a096f6a857a7135d2198d8/.github/workflows/iso_build.yaml#L88-L90 Shouldn't the last line read `manjaro-revoked` instead of `trusted` twice? Similar to the steps for Arch keys: https://github.com/manjaro/release-review/blob/603b9d908f899998d1a096f6a857a7135d2198d8/.github/workflows/iso_build.yaml#L95-L97 Thanks in advance for checking this out!

github.com

manjaro-gnome/download/blob/master/.github/workflows/iso_build.yaml#L100


      
          name: iso_build
          on:
            workflow_dispatch:
            schedule:
              - cron:  '30 2 * * *'
          
          jobs:
            prepare-release:
              runs-on: ubuntu-20.04
              steps:
                - 
                  uses: styfle/cancel-workflow-action@0.9.0
                  with:
                    access_token: ${{ github.token }}
                - 
                  id: time
                  uses: nanzm/get-time-action@v1.1
                  with:
                    format: 'YYYYMMDDHHmm'
              outputs:
                release_tag: ${{ steps.time.outputs.time }}
            build-release:
              runs-on: ubuntu-20.04
              needs: [prepare-release]
              strategy:
                matrix:
                  EDITION: [gnome-next]
                  BRANCH: [unstable]
                  SCOPE: [full, minimal]
              steps:
                - 
                  uses: styfle/cancel-workflow-action@0.9.0
                  with:
                    access_token: ${{ github.token }}
                - 
                  id: time
                  uses: nanzm/get-time-action@v1.1
                  with:
                    format: 'YY.MM'   
                -
                  name: image-build-upload
                  uses: manjaro/manjaro-iso-action@main
                  with:
                    edition: ${{ matrix.edition }}
                    branch: ${{ matrix.branch }}
                    scope: ${{ matrix.scope }}
                    version: ${{ steps.time.outputs.time }}-development
                    kernel: linux68
                    code-name: "Nightly-Build"
                    release-tag: ${{ needs.prepare-release.outputs.release_tag }}
                -
                  name: rollback
                  if: ${{ failure() || cancelled() }}
                  run: |
                    echo ${{ github.token }} | gh auth login --with-token
                    gh release delete ${{ needs.prepare-release.outputs.release_tag }} -y --repo ${{ github.repository }}

jrichard326 · 29 March 2021 12:04

Wine 6.5-1 and 6.5-2 do not work for me. I downgraded to 6.4-1 and it works again (xfce). Can anybody confirm?

Thanks

servimo · 29 March 2021 14:23

I am using wine-staging 6.5-2 and is working.

adreampuppet · 29 March 2021 15:28

The two Windows apps that I run through Wine (version 6.5-2) both open and perform as expected.

freggel.doe · 29 March 2021 16:39

Latest fontconfig-update changed the location of the 11-lcdfilter*.conf files from /etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail/.
If anybody has symlinked one of those in /etc/fonts/conf.d/ - the symlinks will need to be adjusted accordingly.

edit: Just “found” the noto-fonts-compat package on one of my systems, which probably wants to adopt those path changes as well @philm?

jrichard326 · 29 March 2021 17:05

I installed wine-staging 6.5-2 to see if it would make a difference. It does not launch, however, via command line I do get the program (QuickPar) to launch. Here is the output from terminal:

./QuickPar.exe                                                                                                               
002c:fixme:winediag:LdrInitializeThunk wine-staging 6.5 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION

If this is related to the Mesa-Intel warning, I am uncertain how to fix it. Any ideas?

edit:
It might be related to 1924933 – mesa 21 breaks some wine programs
WineHQ Bugzilla – Bug 50869 – Killing Wine process in Wine 6.5 doesn't terminate the application because of the new use of start.exe

edit#2: I get the same error when running via CLI in 6.4-1, but the program launches.

I found the fix:
cp -a ~/.wine/drive_c/windows/command/start.exe ~/.wine/drive_c/windows/

tuxmanjarino · 29 March 2021 20:18

That blue in pamac-gtk is a little too strong and a bit “off” in my opinion, the eye “falls” on that instead of the program’s icon. I would prefer something from Manjaro’s turquoise palette.