Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Brave will not install on OpenSuse #6946

Closed
stan-qaz opened this issue Jan 31, 2017 · 37 comments
Closed

Brave will not install on OpenSuse #6946

stan-qaz opened this issue Jan 31, 2017 · 37 comments

Comments

@stan-qaz
Copy link

stan-qaz commented Jan 31, 2017

Test plan

  1. Set up openSUSE vm
  2. Download the browser binary
  3. Select in Dolphin file manager and pick Install from the right click menu
  4. Provide root password to Yast
  5. Make sure that Yast does not show the error message.

  • Did you search for similar issues before submitting this one?

#5614
#5580

  • Describe the issue you encountered:

Yast complained that there was no GConf2 provider available.

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    OpenSuse 42.2

  • Brave Version (revision SHA):
    0.13.0 (edit and 0.13.1)

  • Steps to reproduce:

    1. Download brave-0.13.0.x86_64.rpm
    2. Select in Dolphin file manager and pick Install from the right click menu
    3. Provide root password to Yast
    4. Yast shows error message.

brave install fail

I have the packages in related reports loaded and 0.12.15 is running with no issues.

gconf2

keyring


Trying the alternate install option via the command line I get these errors:

p3620:/home/data/download # rpm -i brave-0.13.0.x86_64.rpm error: Failed dependencies: GConf2 is needed by brave-0.13.0-1.x86_64 libXScrnSaver is needed by brave-0.13.0-1.x86_64

@stan-qaz
Copy link
Author

stan-qaz commented Feb 2, 2017

Issue remains in 13.1

p3620:/home/data/download # rpm -i --test brave-0.13.1.x86_64.rpm
error: Failed dependencies:
GConf2 is needed by brave-0.13.1-1.x86_64
libXScrnSaver is needed by brave-0.13.1-1.x86_64

@grinderx
Copy link

# zypper install brave
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides GConf2 needed by brave-0.13.2-1.x86_64
 Solution 1: do not install brave-0.13.2-1.x86_64
 Solution 2: break brave-0.13.2-1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 2
Resolving dependencies...
Resolving package dependencies...

The following NEW package is going to be installed:
  brave

1 new package to install.
Overall download size: 68.8 MiB. Already cached: 0 B. After the operation, additional 68.8 MiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package brave-0.13.2-1.x86_64                                                                (1/1),  68.8 MiB ( 68.8 MiB unpacked)
Retrieving: brave-0.13.2.x86_64.rpm .....................................................................................[done (374.2 KiB/s)]
brave-0.13.2.x86_64.rpm:
    Header V4 RSA/SHA256 Signature, key ID 448eee6c: NOKEY
    V4 RSA/SHA256 Signature, key ID 448eee6c: NOKEY

brave-0.13.2-1.x86_64 (brave-rpm-release): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a): r
Retrieving package brave-0.13.2-1.x86_64                                                                (0/1),  68.8 MiB ( 68.8 MiB unpacked)
Retrieving: brave-0.13.2.x86_64.rpm .....................................................................................[done (406.5 KiB/s)]
brave-0.13.2.x86_64.rpm:
    Header V4 RSA/SHA256 Signature, key ID 448eee6c: NOKEY
    V4 RSA/SHA256 Signature, key ID 448eee6c: NOKEY

brave-0.13.2-1.x86_64 (brave-rpm-release): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a): i
Checking for file conflicts: ..........................................................................................................[done]
(1/1) Installing: brave-0.13.2-1.x86_64 .................<23%>============================================================================[/](1/1) Installing: brave-0.13.2-1.x86_64 ..............................................................................................[error]
Installation of brave-0.13.2-1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: warning: /var/cache/zypp/packages/brave-rpm-release/brave-0.13.2.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 448eee6c: NOKEY


Abort, retry, ignore? [a/r/i] (a): a
Problem occured during or after installation or removal of packages:
Installation aborted by user

Please see the above error message for a hint.

@grinderx
Copy link

Same while trying to install directly from the rpm package, bypassing the repo:

# zypper in brave-0.13.2.x86_64.rpm
root's password:
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides GConf2 needed by brave-0.13.2-1.x86_64
 Solution 1: do not install brave-0.13.2-1.x86_64
 Solution 2: break brave-0.13.2-1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): c

# rpm -Uvh brave-0.13.2.x86_64.rpm 
error: Failed dependencies:
        GConf2 is needed by brave-0.13.2-1.x86_64
        libXScrnSaver is needed by brave-0.13.2-1.x86_64

@jiri-bati-novak
Copy link

Still unable to install with 0.13.5...

@cndouglas cndouglas changed the title 0.13.0 Will not install on OpenSuse Brave will not install on OpenSuse Mar 24, 2017
@cndouglas cndouglas added the bug label Mar 24, 2017
@mati865
Copy link
Contributor

mati865 commented Apr 5, 2017

gconf2 on openSUSE:

Repository     : openSUSE-Tumbleweed-Oss            
Name           : gconf2                             
Version        : 3.2.6-10.5                         
Arch           : x86_64                             
Vendor         : openSUSE                           
Installed Size : 2.0 MiB                            
Installed      : Yes                                
Status         : up-to-date                         
Source package : gconf2-3.2.6-10.5.src              
Summary        : GNOME Configuration Database System
Description    :                                    
    GConf is a configuration database system for storing application
    preferences. It supports default or mandatory settings set by the
    administrator, and changes to the database are instantly applied to all
    running applications. It is written for the GNOME desktop but doesn't
    require it.
Provides       : [9]                                
    libgconf-2.so.4()(64bit)
    libgconfbackend-oldxml.so()(64bit)
    libgconfbackend-xml.so()(64bit)
    libgsettingsgconfbackend.so()(64bit)
    typelib(GConf) = 2.0
    config(gconf2) = 3.2.6-10.5
    gconf2 = 3.2.6-10.5
    gconf2(x86-64) = 3.2.6-10.5
    /usr/bin/gconftool-2

Therefore "GConf2" here, which is fine for Fedora have to be "gconf2" for openSUSE.

@cndouglas
Copy link

cndouglas commented Apr 10, 2017

Related: #8156

@Achimh3011
Copy link

Same problem on openSUSE Tumbleweed, version currently 20170524

Brave 0.15.314, works fine when dependencies are ignored.

@markathomas
Copy link

same on openSUSE 42.2. works if you ignore dependencies on install

@Garbee
Copy link

Garbee commented Jul 14, 2017

It looks like we need to have a second linuxPackaging.json file managed for OpenSUSE. That way the requirements can be modified to fit the suse naming. Also, this would allow us to resolve #5614 in the process. Then in tools/buildInstaller.js we add a 3rd RPM build using the OpenSUSE config with its own name. Like append suse- to it in the build output directory.

The only major hiccup is distributing this new installer. We could upload it as-named to the current RPM directory and just install with suse-brave-{whatever}.rpm from here on out. But having suse- in front of the package name looks fugly. So a better solution is to have its own repo location and rename the suse- build filename on upload.

That's at least my thoughts after a quick diagnostic on the situation. Any input from more experienced maintainers for SUSE is very welcome.

@apinter
Copy link

apinter commented Jul 21, 2017

@markathomas is right, just ignore the GConf2 dependency and it fine, but still the repo is not available using zypper.

Permission to access 'https://s3-us-west-2.amazonaws.com/brave-rpm-release/x86_64/media.1/media' denied.

Abort, retry, ignore? [a/r/i/...? shows all options] (a): 

@mati865
Copy link
Contributor

mati865 commented Jul 21, 2017

@apinter it's another issue reported here #8156

mati865 added a commit to mati865/browser-laptop that referenced this issue Jul 24, 2017
RPM 4.13 added support for boolean dependencies, we can use it to
resolve issue with openSUSE.

Fix brave#6946
@posix4e
Copy link
Contributor

posix4e commented Jul 29, 2017

This should fix it when we have it working properly electron-userland/electron-installer-redhat#74

@Garbee
Copy link

Garbee commented Jul 29, 2017

@posix4e That doesn't solve it fully. OpenSUSE Leap will still have the problem. As discussed in the PR trying to address this. That ONLY works for Tumbleweed users.

A second binary is required to fully resolve the issue until Leap gets a newer RPM build native. Otherwise, we're stuck in the same issue.

@posix4e
Copy link
Contributor

posix4e commented Jul 31, 2017

Got it. . I'm ok with a new binary

@luixxiul
Copy link
Contributor

I created a new issue for installation on openSUSE Leap: #10210.

@Garbee
Copy link

Garbee commented Jul 31, 2017

@luixxiul This issue is already about Leap. Why open a new one?

@posix4e
Copy link
Contributor

posix4e commented Jul 31, 2017

Could you try https://storage.googleapis.com/posis-brave-mirror/brave-0.20.0.x86_64.rpm and see if that fixes it?

@Garbee
Copy link

Garbee commented Aug 1, 2017

That RPM seems to have one dependency issue. libXScrnSaver. If that is ignored, it appears to successfully install.

Output
jonathan@linux-1yey ~/Downloads> sudo zypper in brave-0.20.0.x86_64.rpm 
[sudo] password for root: 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides libXScrnSaver needed by brave-0.20.0-1.x86_64
 Solution 1: do not install brave-0.20.0-1.x86_64
 Solution 2: break brave-0.20.0-1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 

@posix4e
Copy link
Contributor

posix4e commented Aug 1, 2017

@Garbee shall I remove it? Here's my branch https://github.com/posix4e/browser-laptop/tree/suse

@Garbee
Copy link

Garbee commented Aug 1, 2017

I get a 404 checking your branch. Seems to be private.

I'll take a look at that requirement in a little bit and get back to you. It may just be another thing that needs a new name.

@Garbee
Copy link

Garbee commented Aug 2, 2017

Hmm. Removing libXScrnSaver shouldn't be necessary as it does exist for OpenSUSE as named. I'm going to try and dig into the RPM build and see if I can find something out as to why this is triggering for this build but not the others.

@Garbee
Copy link

Garbee commented Aug 3, 2017

@posix4e Yup, your branch commit LGTM for the required changes on the builds. Not sure on the infrastructure work needed since now the other binaries are in subfolders. Could have an adverse affect on existing repository configs for users.

@posix4e
Copy link
Contributor

posix4e commented Aug 3, 2017

@Garbee I am planning on doing a release soon anyway. I've got some fancy stuff to make our builds more reliable and secure next!

posix4e added a commit to posix4e/browser-laptop that referenced this issue Aug 3, 2017
@luixxiul luixxiul modified the milestones: 0.21.x (Nightly Channel), 0.22.x Aug 3, 2017
@cezaraugusto cezaraugusto modified the milestones: 0.21.x (Developer Channel), 0.22.x (Nightly Channel) Oct 14, 2017
@darkdh darkdh modified the milestones: 0.22.x (Nightly Channel), 0.20.x (Beta Channel) Nov 3, 2017
syuan100 pushed a commit to syuan100/browser-laptop that referenced this issue Nov 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.