Error-message on fresh install of 1.18.0 on Ubuntu 19.10 using deb-package #859

p4fg · 2019-12-03T10:04:21Z

Fresh install using the ubuntu-deb-package.
Starting up.
Getting error:

Unhandled Promise Rejection
Error: ENOENT: no such file or directory, open '/opt/Buttercup/resources/app-update.yml'

The text was updated successfully, but these errors were encountered:

p4fg · 2019-12-03T10:10:05Z

Creating the file (empty) gives the same results strangely enough

perry-mitchell · 2019-12-11T17:23:28Z

Hi @p4fg - Apologies for the delay. What's the permissions on that dir? If you start bcup as a more priviledged user does it help? Wondering if it's a permissions issue.

ghostd · 2019-12-15T22:06:23Z

Hi @perry-mitchell

I have the same issue after an upgrade to 1.18.0

My 'resources' directory only contains a 'app.asar' file.

If i 'touch' the asked file, i get an other error (it seems the application attempts to read my empty file and does not find some required properties)

d-air1 · 2019-12-22T03:25:33Z

I'm also experiencing this problem on a fresh install of ubuntu 19.10 using buttercup-desktop version 1.18.1.

Here is the output of terminal when running as regular user and root:
buttercup-desktop

21:19:45.074 › Buttercup starting up...
21:19:45.146 › Restoring state... {
  settingsByArchiveId: {},
  archives: [],
  settings: {
    columnSizes: { tree: 230, entries: 230 },
    condencedSidebar: true,
    menubarAutoHide: false,
    archivesLoading: false,
    isTrayIconEnabled: true,
    isBrowserAccessEnabled: false,
    locale: 'en'
  }
}
(electron) 'setAutoHideMenuBar function' is deprecated and will be removed. Please use 'autoHideMenuBar property' instead.
21:19:50.619 › Checking for update
21:19:50.645 › Error: Error: ENOENT: no such file or directory, open '/opt/Buttercup/resources/app-update.yml'
[Error: ENOENT: no such file or directory, open '/opt/Buttercup/resources/app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/Buttercup/resources/app-update.yml'
}
^C21:21:30.670 › Running before-quit operation.
d-air1@reki:~$ sudo buttercup-desktop
[29747:1221/212142.894449:FATAL:atom_main_delegate.cc(207)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap
d-air1@reki:~$ sudo buttercup-desktop --no-sandbox
21:22:01.441 › Buttercup starting up...
21:22:02.436 › Restoring state... {}
(electron) 'setAutoHideMenuBar function' is deprecated and will be removed. Please use 'autoHideMenuBar property' instead.
21:22:07.920 › Checking for update
21:22:07.930 › Error: Error: ENOENT: no such file or directory, open '/opt/Buttercup/resources/app-update.yml'
[Error: ENOENT: no such file or directory, open '/opt/Buttercup/resources/app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/Buttercup/resources/app-update.yml'
}
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)

(buttercup-desktop:29767): dconf-WARNING **: 21:22:15.851: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:15.889: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:15.900: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:15.918: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:15.951: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:15.968: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:15.984: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:16.001: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:16.019: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:16.036: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:16.052: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:16.068: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:16.082: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:19.977: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:19.987: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.005: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.022: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.047: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.080: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.095: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.123: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.140: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.156: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.173: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:20.189: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:22.899: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:22.933: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:22.950: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:22.971: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:22.985: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:22.996: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:23.013: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:23.030: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:23.046: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:23.063: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:23.080: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:23.101: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:23.125: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:24.080: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:24.107: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:24.125: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:24.490: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(buttercup-desktop:29767): dconf-WARNING **: 21:22:24.491: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

d-air1 · 2019-12-22T03:27:42Z

So it seems to be looking for a file that doesn't exist on startup and it seems it is having problems changing to dconf. This seems to result in nothing happening when trying to create a new archive.

d-air1 · 2019-12-22T03:41:50Z

Unless I'm doing something wrong I can't create a new archive at all. I have tried this with version 1.18.1 using the deb package and the appimage. The appimage does not have the update check error however.

d-air1 · 2019-12-23T05:39:48Z

For now the 1.17.3 works.

chasbro-1 · 2019-12-31T00:10:05Z

I still have this issue with 1.18.2. Happens about 5 seconds after I open butter-desktop app. I am using LinuxMint 19.3.

niniks · 2020-01-06T08:57:53Z

I still have this issue with 1.18.2. Happens about 5 seconds after I open butter-desktop app. I am using LinuxMint 19.3.

Same problem here, fresh install on newest version ubuntu

LuckyLukert · 2020-01-15T17:08:33Z

Hi,

I have the same issue on Ubuntu 18-LTS. Is there anything we can do?
E.g. creating a file with some special content that is needed?

Also, is there a possibility to just disable automatic updates?
I would prefer my password manager to not open network connections.

Best, Philip

perry-mitchell · 2020-01-18T16:04:37Z

I would prefer my password manager to not open network connections.

Security updates for something as vital as a password manager are super important. We wouldn't want to immediately provide the option for people to forgo updates and potentially forget to allow patching security vulnerabilities. Adding an option like this to Buttercup goes against our instincts here.

Perhaps a setting to allow specifying an update-check schedule? Not sure what would make this more appealing to you.

ghostd · 2020-01-18T22:03:28Z

Maybe this is related to electron-userland/electron-builder#4233
This issue mentions a potential workaround: electron-userland/electron-builder#2736 (comment)... if someone knows how to check this

heyvoon · 2020-03-03T08:59:26Z

Samhe here on Linux Mint 18.3 Cinnamon
Buttercup 1.19.0

After installation, first time fire up;

EDavidF · 2020-03-04T17:08:41Z

Continuing to get after update to 1.19.0. Between this and the android app to require Google services, I think my Buttercup experiment may be ending, which is too bad- these apps have a lot going for them.

sallar · 2020-03-05T09:13:10Z

Hi @EDavidF, we are working on this Linux issue. But would you mind elaborating on the Android issue? We had a problem with Google Services but it's now fixed.

EDavidF · 2020-03-05T16:46:51Z

@sallar see @perry-mitchell 's comment here: buttercup/buttercup-mobile#75 (comment)
I will add comment there.
Thanks.

ziltsh · 2020-03-26T09:47:46Z

Error pop-up from 1.18.2:

Eror message after upgrading to 1.19.0:

Also the system->about menu does not produce any window or information.

I am running:
$ date; lsb_release -d ; uname -srvmo
Thu 26 Mar 2020 10:47:25 AM CET
Description: Debian GNU/Linux bullseye/sid
Linux 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux

ndurbindhcs · 2020-04-07T16:37:57Z

I have same issue on v1.18.2 & v1.19.0

Tue 07 Apr 2020 09:35:27 AM PDT
Description: Fedora release 31 (Thirty One)
Linux 5.5.13-200.fc31.x86_64 #1 SMP Wed Mar 25 21:55:30 UTC 2020 x86_64 GNU/Linux

I wish I never upgraded from earlier v0.17.x This is such a PITA and has me regretting migrating to buttercup. Why can't someone fix this after so many people asking for this to be patched for months?

sidahmed-malaoui · 2020-04-14T11:07:47Z

Apparently, in version 1.19.0, disabling automatic updates at startup (System -> Preferences -> Disable update on start) will make this error disappear, and I could create or open archives.

PS : When you create an archive, you have to specify the extension (which is .bcup).

I hope this will help someone until the app is fixed.

joubertredrat · 2020-04-15T23:26:51Z

Same issue here. Installed in Linux Mint 19.3 using deb package

perry-mitchell · 2020-04-19T12:55:08Z

The issue is that only AppImage build types support auto-updates on linux, thanks to how electron-builder works. Because we currently can't detect how buttercup was installed, there's currently no way to know if we should even attempt to check for updates (why this error is appearing). The solution would be to detect install type (probably at build time), and then disable auto-updates if on a platform that doesn't support them.

If some one would be kind enough to make a PR for this we could fast-track it..

franko108 · 2020-04-24T09:17:47Z

Same issue on my Ubuntu 19.10, installed instance from the link: https://github.com/buttercup/buttercup-desktop/releases/download/v1.19.0/buttercup-desktop_1.19.0_amd64.deb

I can't create an empty archive. No errors on GUI, but archive isn't been created.

dreamstorpi · 2020-05-19T10:07:27Z

I had the same issue.
I got rid of the error message by disabling auto update on start up in the preferences.
But, of course, that doesn't solve the issue; just makes the annoyance go away.
V1.19.0 on Fedora 32

jabbajac · 2020-06-05T17:22:44Z

Still having the same issue on v1.19.0

I'm on ubuntu 18.04 LTS

Doctor-Who · 2020-06-09T08:56:47Z

Same issue with RPM and openSUSE Leap 15.1

SerhiiK · 2020-06-14T19:22:42Z

Have the same issue on ubuntu 16.04 with v1.19.0

LeonardPeris · 2020-07-05T13:56:23Z

This has already been referenced in Issue #917 .
As noted, this is Electron's Update Mechanism trying to update the app, which is not permitted on Linux system. This will be fixed in future releases.

ldexterldesign · 2020-07-09T22:48:10Z

FYI not just Linux

Wow, after months of tolerating this I'm glad it's not just me!

Be lovely to get this fixed 🙏

Sincerely

software - operating system: Apple, macOS, 10.15.5 (19F101)
software - application: Buttercup, 1.19.0 (1.19.0)

sallar · 2020-07-13T09:19:01Z

Hey everyone, can you please check to see if this is still an issue?

steve-goldberg · 2020-07-16T19:44:46Z

I'm still having this issue. I'm pop os 20.04 on a dell xps 15.

ldexterldesign · 2020-08-24T20:54:49Z

Hi @sallar,

Apologies for delay

Not an issue for me any longer, haven't seen that error in a while

Hope this helps

Sincerely

perry-mitchell · 2021-04-05T18:23:35Z

Stale and no longer relevant as for now we're no longer supporting deb packages.

ghostd mentioned this issue Dec 20, 2019

Error on checking for update #873

Closed

sallar added this to the v1.18.2 milestone Dec 28, 2019

sallar modified the milestones: v1.18.2, next-release Jan 11, 2020

perry-mitchell added Platform: Linux Priority: High Status: Available Type: Bug labels Jan 25, 2020

ghostd mentioned this issue Mar 18, 2020

Unhandled Promise Rejection : missing app-update.yml #896

Closed

ghostd mentioned this issue Apr 24, 2020

Desktop on Ubuntu 19.10 #906

Closed

perry-mitchell closed this as completed Apr 5, 2021

perry-mitchell added Status: Abandoned and removed Status: Available labels Apr 5, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error-message on fresh install of 1.18.0 on Ubuntu 19.10 using deb-package #859

Error-message on fresh install of 1.18.0 on Ubuntu 19.10 using deb-package #859

p4fg commented Dec 3, 2019

p4fg commented Dec 3, 2019

perry-mitchell commented Dec 11, 2019

ghostd commented Dec 15, 2019

d-air1 commented Dec 22, 2019 •

edited by perry-mitchell

Loading

d-air1 commented Dec 22, 2019 •

edited

Loading

d-air1 commented Dec 22, 2019

d-air1 commented Dec 23, 2019

chasbro-1 commented Dec 31, 2019 •

edited

Loading

niniks commented Jan 6, 2020

LuckyLukert commented Jan 15, 2020

perry-mitchell commented Jan 18, 2020

ghostd commented Jan 18, 2020

heyvoon commented Mar 3, 2020

EDavidF commented Mar 4, 2020

sallar commented Mar 5, 2020

EDavidF commented Mar 5, 2020

ziltsh commented Mar 26, 2020 •

edited

Loading

ndurbindhcs commented Apr 7, 2020

sidahmed-malaoui commented Apr 14, 2020

joubertredrat commented Apr 15, 2020

perry-mitchell commented Apr 19, 2020 •

edited

Loading

franko108 commented Apr 24, 2020

dreamstorpi commented May 19, 2020

jabbajac commented Jun 5, 2020

Doctor-Who commented Jun 9, 2020

SerhiiK commented Jun 14, 2020

LeonardPeris commented Jul 5, 2020

ldexterldesign commented Jul 9, 2020

sallar commented Jul 13, 2020

steve-goldberg commented Jul 16, 2020

ldexterldesign commented Aug 24, 2020

perry-mitchell commented Apr 5, 2021

Error-message on fresh install of 1.18.0 on Ubuntu 19.10 using deb-package #859

Error-message on fresh install of 1.18.0 on Ubuntu 19.10 using deb-package #859

Comments

p4fg commented Dec 3, 2019

p4fg commented Dec 3, 2019

perry-mitchell commented Dec 11, 2019

ghostd commented Dec 15, 2019

d-air1 commented Dec 22, 2019 • edited by perry-mitchell Loading

d-air1 commented Dec 22, 2019 • edited Loading

d-air1 commented Dec 22, 2019

d-air1 commented Dec 23, 2019

chasbro-1 commented Dec 31, 2019 • edited Loading

niniks commented Jan 6, 2020

LuckyLukert commented Jan 15, 2020

perry-mitchell commented Jan 18, 2020

ghostd commented Jan 18, 2020

heyvoon commented Mar 3, 2020

EDavidF commented Mar 4, 2020

sallar commented Mar 5, 2020

EDavidF commented Mar 5, 2020

ziltsh commented Mar 26, 2020 • edited Loading

ndurbindhcs commented Apr 7, 2020

sidahmed-malaoui commented Apr 14, 2020

joubertredrat commented Apr 15, 2020

perry-mitchell commented Apr 19, 2020 • edited Loading

franko108 commented Apr 24, 2020

dreamstorpi commented May 19, 2020

jabbajac commented Jun 5, 2020

Doctor-Who commented Jun 9, 2020

SerhiiK commented Jun 14, 2020

LeonardPeris commented Jul 5, 2020

ldexterldesign commented Jul 9, 2020

sallar commented Jul 13, 2020

steve-goldberg commented Jul 16, 2020

ldexterldesign commented Aug 24, 2020

perry-mitchell commented Apr 5, 2021

d-air1 commented Dec 22, 2019 •

edited by perry-mitchell

Loading

d-air1 commented Dec 22, 2019 •

edited

Loading

chasbro-1 commented Dec 31, 2019 •

edited

Loading

ziltsh commented Mar 26, 2020 •

edited

Loading

perry-mitchell commented Apr 19, 2020 •

edited

Loading