You are not logged in.

Pages: 1

#1 2019-03-28 10:28:53

pih
Member
Registered: 2019-03-28
Posts: 4

xdg-open: no method available for opening https://

Hi all,
I've just started using Arch and I'm trying to configure my system, but got stuck. I'm running i3wm, launched slack inside a docker container, but evey time I click on a link I get xdg-open: no method available for opening 'https://slack.com/ssb/signin'

I tried setting a default browser with

xdg-settings set default-web-browser firefox.desktop

but it didn't help. Can you point me in the right direction please?

Thanks

Offline

#2 2019-03-28 10:41:33

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,425

Re: xdg-open: no method available for opening https://

A docker container does not provide you with desktop session guarantees. Does it work outside of the docker container?

Last edited by V1del (2019-03-28 10:41:43)

Offline

#3 2019-03-28 10:59:48

pih
Member
Registered: 2019-03-28
Posts: 4

Re: xdg-open: no method available for opening https://

Potentially, I havent' seen this specific error outside of Slack container. But still feels like there's something missing.
Tried installing slack-desktop with yay, after starting the app and clicking sign in login page opens in a browser, however, after entering credentials nothing happens (i'm not taken back to the app).

I'm pretty sure that login should happen within the app (as was the case on all other distros in the past)

Offline

#4 2019-03-28 12:09:35

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,425

Re: xdg-open: no method available for opening https://

Well what now, do you actually have an issue with xdg-open or is this specifically limited to slack? As slack is a properietary application distribution specifics are likely to either be minimal or due to incorrect configuration.

FWIW This does sound like some broken session, how exactly do you start i3 ? What are your outputs for 

hostnamectl
loginctl session-status

Offline

#5 2019-03-28 12:33:39

pih
Member
Registered: 2019-03-28
Posts: 4

Re: xdg-open: no method available for opening https://

I have literally started setting up my machine today and as I use slack extensively for work that was one of the first things I set up (google was not very helpful in regards to my issue), yet the very same way I used to start that container in i3 on other work.

In regards to the information you asked for, i3 is started by lightdm-autologin during boot

 
❯ hostnamectl
   Static hostname: n/a
Transient hostname: archlinux
         Icon name: computer-desktop
           Chassis: desktop
        Machine ID: a40835f154d642239ba996e26ce0e064
           Boot ID: bb136bb4a02049548a1ab23702f14071
  Operating System: Arch Linux
            Kernel: Linux 5.0.4-arch1-1-ARCH
      Architecture: x86-64
❯ loginctl session-status
1 - piotr (1000)
           Since: Thu 2019-03-28 12:12:46 GMT; 19min ago
          Leader: 548 (lightdm)
            Seat: seat0; vc7
         Display: :0
         Service: lightdm-autologin; type x11; class user
         Desktop: i3
           State: active
            Unit: session-1.scope
                  ├─ 548 lightdm --session-child 14 17
                  ├─ 559 i3
                  ├─ 567 i3bar --bar_id=bar-0 --socket=/run/user/1000/i3/ipc-socket.559
                  ├─ 568 i3status
                  ├─ 723 /usr/bin/zsh
                  ├─ 728 nm-applet
                  ├─ 789 urxvt
                  ├─ 790 tmux
                  ├─ 877 tmux
                  ├─ 879 -zsh
                  ├─1034 /usr/bin/zsh
                  ├─1037 /usr/bin/python3 /usr/bin/qutebrowser
                  ├─1050 /usr/lib/qt/libexec/QtWebEngineProcess --type=zygote --webengine-schemes=qute:lL;qrc:sLV --lang=en-GB
                  ├─1071 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1080 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1086 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1096 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1124 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1136 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1148 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1156 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1172 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1178 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=desktop --enable-features=AllowContentInitiated>
                  ├─1569 loginctl session-status
                  └─1570 less

Mar 28 12:12:46 archlinux systemd[1]: Started Session 1 of user piotr.
Mar 28 12:13:14 archlinux sudo[982]:    piotr : TTY=pts/1 ; PWD=/home/piotr ; USER=root ; COMMAND=/usr/bin/systemctl start NetworkManager
Mar 28 12:13:14 archlinux sudo[982]: pam_unix(sudo:session): session opened for user root by piotr(uid=0)
Mar 28 12:13:14 archlinux sudo[982]: pam_unix(sudo:session): session closed for user root
Mar 28 12:17:57 archlinux sudo[1432]:    piotr : TTY=pts/1 ; PWD=/home/piotr ; USER=root ; COMMAND=/usr/bin/systemctl enable NetworkManager
Mar 28 12:17:57 archlinux sudo[1432]: pam_unix(sudo:session): session opened for user root by piotr(uid=0)
Mar 28 12:17:58 archlinux sudo[1432]: pam_unix(sudo:session): session closed for user root

Thanks

Offline

#6 2019-03-28 12:45:25

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,425

Re: xdg-open: no method available for opening https://

Good there we already have one important problem, that can lead to all sorts of weird issues, not unlike what you are experiencing.

You didn't set a host name, do so, reboot, retry.

Also FWIW, I'd focus on getting it to work in a normal environment first, if that works, you should check what happens differently in a docker container.

Last edited by V1del (2019-03-28 12:49:35)

Offline

#7 2019-03-28 13:11:37

pih
Member
Registered: 2019-03-28
Posts: 4

Re: xdg-open: no method available for opening https://

@V1del many thanks for all the help so far. I've set the hostname with hostnamectl, rebooted, tried yay installed Slack and it worked. Any idea how I can debug the containerized version?

Offline

Pages: 1

Board footer

Powered by FluxBB