Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Chromium cannot determine default browser on KDE Plasma
@ 2019-09-14 18:42 voidlinux-github
  2021-06-12 19:24 ` Johnnynator
  2021-06-12 19:26 ` [ISSUE] [CLOSED] " Johnnynator
  0 siblings, 2 replies; 3+ messages in thread
From: voidlinux-github @ 2019-09-14 18:42 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

New issue by daunknownfox2010 on void-packages repository

https://github.com/void-linux/void-packages/issues/14457

Description:
Under a fresh install of KDE Plasma in combination with Chromium, it seems Chromium cannot determine the default browser under the KDE Plasma environment (I have also tested it with LXQt installed alongside KDE Plasma, it seems to work there oddly enough).

### System

* xuname:  
  *Void 5.2.14_1 x86_64 AuthenticAMD*
* package:  
  *chromium-76.0.3809.132_1*

### Expected behavior

Chromium should be able to determine the default browser that is set.

### Actual behavior

Chromium cannot determine the default browser ("Chromium cannot determine or set the default browser") on the Settings page.

### Steps to reproduce the behavior

Use the KDE Plasma desktop and open Chromium. Navigate to the Settings page and look under "Default browser", you should see it cannot determine the default browser.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Chromium cannot determine default browser on KDE Plasma
  2019-09-14 18:42 [ISSUE] Chromium cannot determine default browser on KDE Plasma voidlinux-github
@ 2021-06-12 19:24 ` Johnnynator
  2021-06-12 19:26 ` [ISSUE] [CLOSED] " Johnnynator
  1 sibling, 0 replies; 3+ messages in thread
From: Johnnynator @ 2021-06-12 19:24 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 289 bytes --]

New comment by Johnnynator on void-packages repository

https://github.com/void-linux/void-packages/issues/14457#issuecomment-860097885

Comment:
Turns out, the problem is simply that `xdg-settings` is not compatible with dash, that issue wasn't caused by neither chromium nor KDE Plasma.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ISSUE] [CLOSED] Chromium cannot determine default browser on KDE Plasma
  2019-09-14 18:42 [ISSUE] Chromium cannot determine default browser on KDE Plasma voidlinux-github
  2021-06-12 19:24 ` Johnnynator
@ 2021-06-12 19:26 ` Johnnynator
  1 sibling, 0 replies; 3+ messages in thread
From: Johnnynator @ 2021-06-12 19:26 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

Closed issue by daunknownfox2010 on void-packages repository

https://github.com/void-linux/void-packages/issues/14457

Description:
Under a fresh install of KDE Plasma in combination with Chromium, it seems Chromium cannot determine the default browser under the KDE Plasma environment (I have also tested it with LXQt installed alongside KDE Plasma, it seems to work there oddly enough).

### System

* xuname:  
  *Void 5.2.14_1 x86_64 AuthenticAMD*
* package:  
  *chromium-76.0.3809.132_1*

### Expected behavior

Chromium should be able to determine the default browser that is set.

### Actual behavior

Chromium cannot determine the default browser ("Chromium cannot determine or set the default browser") on the Settings page.

### Steps to reproduce the behavior

Use the KDE Plasma desktop and open Chromium. Navigate to the Settings page and look under "Default browser", you should see it cannot determine the default browser.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-06-12 19:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-14 18:42 [ISSUE] Chromium cannot determine default browser on KDE Plasma voidlinux-github
2021-06-12 19:24 ` Johnnynator
2021-06-12 19:26 ` [ISSUE] [CLOSED] " Johnnynator

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).