[Desktop-packages] [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window

2023-06-26 Thread zwn 
*** This bug is a duplicate of bug 1732482 ***
https://bugs.launchpad.net/bugs/1732482

> The desktop file is necessary for Gnome Shell to categorize the PWA as
a different application — in its own tab group — instead of just another
Chromium window.

Since I am not familiar with the way how Gnome Shell decides which
windows belong together and you don't explain how it is done, it is
really hard for me to agree or disagree with anything.

In the comment #5 you mention window classes as a way to do this feat.
The desktop file seems like a possible way to launch Chromium with a
specific window class which makes it a separate application. Is this a
correct deduction?

Is the desktop file the only way to do this? I was under the impression
that using "chrome://apps" page as a launcher would be a different way
how to launch a new Chromium with the required window class. If this is
not the way then the launcher is broken - or at least creates a
misplaced expectations (but that would be a different bug). If the
launcher is not broken and sets everything correctly, then this bug is
not a duplicate of bug #1732482.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007652

Title:
  [snap] PWA don't launch as applications, just another chromium window

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I have recently converted from deb to snap package of chromium and
  progressive web applications (PWAs) launch just as another window of
  chromium and are not recognized as separate application by the window
  manager (for example when switching using Super+Tab) or dock (grouped
  under chromium windows).

  This is either a regression of the snap package vs deb or ubuntu 20.04
  vs ubuntu 18.04 (I am not able to differentiate between these two
  since both happened together).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window

2023-06-24 Thread zwn 
*** This bug is a duplicate of bug 1732482 ***
https://bugs.launchpad.net/bugs/1732482

I am aware of the problem with desktop files & snaps. Therefore I am
launching the installed app directly from Chromium page available at
chrome://apps to circumvent the problem (of not being able to pick up
the desktop file). That makes me believe that this is not a duplicate of
the linked bug since desktop files are not part of the reproducible test
case.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007652

Title:
  [snap] PWA don't launch as applications, just another chromium window

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I have recently converted from deb to snap package of chromium and
  progressive web applications (PWAs) launch just as another window of
  chromium and are not recognized as separate application by the window
  manager (for example when switching using Super+Tab) or dock (grouped
  under chromium windows).

  This is either a regression of the snap package vs deb or ubuntu 20.04
  vs ubuntu 18.04 (I am not able to differentiate between these two
  since both happened together).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window

2023-04-12 Thread zwn 
My use case is https://chat.google.com/. It offers to install itself
(button in the url bar). When I click it, it opens as top level window
without the url bar, but still grouped under the chromium windows - it
does not get its own button on the taskbar and Super+Tab does not
recognize the chat window as its own application. In both cases the deb
version created the feel that the chat is its own thing, separate from
chromium.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007652

Title:
  [snap] PWA don't launch as applications, just another chromium window

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I have recently converted from deb to snap package of chromium and
  progressive web applications (PWAs) launch just as another window of
  chromium and are not recognized as separate application by the window
  manager (for example when switching using Super+Tab) or dock (grouped
  under chromium windows).

  This is either a regression of the snap package vs deb or ubuntu 20.04
  vs ubuntu 18.04 (I am not able to differentiate between these two
  since both happened together).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2007652] [NEW] PWA don't launch as applications, just another chromium window

2023-02-16 Thread zwn 
Public bug reported:

I have recently converted from deb to snap package of chromium and PWAs
launch just as another window of chromium and are not recognized as
separate application by the window manager (for example when switching
using Super+Tab) or dock (grouped under chromium windows).

This is either a regression of the snap package vs deb or ubuntu 20.04
vs ubuntu 18.04 (I am not able to differentiate between these two since
both happened together).

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007652

Title:
  PWA don't launch as applications, just another chromium window

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I have recently converted from deb to snap package of chromium and
  PWAs launch just as another window of chromium and are not recognized
  as separate application by the window manager (for example when
  switching using Super+Tab) or dock (grouped under chromium windows).

  This is either a regression of the snap package vs deb or ubuntu 20.04
  vs ubuntu 18.04 (I am not able to differentiate between these two
  since both happened together).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2020-08-25 Thread zwn 
Same problem with Edifier TWS200:

Device 5C:C6:E9:C4:29:2F (public)
Name: EDIFIER TWS200 R
Alias: EDIFIER TWS200 R
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Vendor specific   (eb03-d102-11e1-9b23-00025b00a5a5)


Only Handsfree available, no Headset.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1576559

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1832473] [NEW] fails to create p2p-device when net.names=1

2019-06-12 Thread zwn 
Public bug reported:

In the default install setup I get this message in dmesg:

Jun 11 09:30:29 larsa wpa_supplicant[1053]: Failed to create interface 
p2p-dev-wlp0s20f3: -22 (Invalid argument)
Jun 11 09:30:29 larsa wpa_supplicant[1053]: nl80211: Failed to create a P2P 
Device interface p2p-dev-wlp0s20f3
Jun 11 09:30:29 larsa wpa_supplicant[1053]: P2P: Failed to enable P2P Device 
interface

and p2p wifi is not working. When I boot with net.names=0 (disable
consistent network device naming), everything is ok and `iw dev` lists
another interface

phy#0
Unnamed/non-netdev interface
wdev 0x5
addr 48:a4:72:fb:7d:14
type P2P-device
txpower 0.00 dBm
Interface wlan0
ifindex 3
wdev 0x1
addr 48:a4:72:fb:7d:13
ssid TP-LINK_CA74
type managed
channel 1 (2412 MHz), width: 40 MHz, center1: 2422 MHz
txpower 22.00 dBm

after which wpa_cli can be used to create p2p group.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: wpasupplicant 2:2.6-15ubuntu2.3
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 12 11:08:49 2019
InstallationDate: Installed on 2019-03-05 (98 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: wpa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1832473

Title:
  fails to create p2p-device when net.names=1

Status in wpa package in Ubuntu:
  New

Bug description:
  In the default install setup I get this message in dmesg:

  Jun 11 09:30:29 larsa wpa_supplicant[1053]: Failed to create interface 
p2p-dev-wlp0s20f3: -22 (Invalid argument)
  Jun 11 09:30:29 larsa wpa_supplicant[1053]: nl80211: Failed to create a P2P 
Device interface p2p-dev-wlp0s20f3
  Jun 11 09:30:29 larsa wpa_supplicant[1053]: P2P: Failed to enable P2P Device 
interface

  and p2p wifi is not working. When I boot with net.names=0 (disable
  consistent network device naming), everything is ok and `iw dev` lists
  another interface

  phy#0
Unnamed/non-netdev interface
wdev 0x5
addr 48:a4:72:fb:7d:14
type P2P-device
txpower 0.00 dBm
Interface wlan0
ifindex 3
wdev 0x1
addr 48:a4:72:fb:7d:13
ssid TP-LINK_CA74
type managed
channel 1 (2412 MHz), width: 40 MHz, center1: 2422 MHz
txpower 22.00 dBm

  after which wpa_cli can be used to create p2p group.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: wpasupplicant 2:2.6-15ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 12 11:08:49 2019
  InstallationDate: Installed on 2019-03-05 (98 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1832473/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 694468] Re: Unnecessary chrome when showing multiple tabs

2011-10-31 Thread zwn 
Is there a similar workaround for gtk-3?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/694468

Title:
  Unnecessary chrome when showing multiple tabs

Status in GTK+ GUI Toolkit:
  Confirmed
Status in “gnome-terminal” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-terminal

  When gnome-terminal shifts from showing a single tab to showing two or
  more tabs, it introduces unnecessary chrome on the left, bottom and
  right edges of the window. This is particularly visible when the
  terminal is maximised. Chrome on the right is masked to some extent by
  the scrollbar there, but should be eliminated as well.

  To reproduce:
   * launch gnome-terminal, showing only a single tab, maximised
   * note the lack of chrome around the edges of the screen
   * ctrl-shift-t to create a new tab

  What happens:
   * you see a gray border on the left and bottom of the screen

  What should happen:
   * there should be no gray border on the left and bottom of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/694468/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 694468] Re: Unnecessary chrome when showing multiple tabs

2011-10-31 Thread zwn 
Ok, there is :). In file /usr/share/themes/Ambiance/gtk-3.0/apps/gnome-
terminal.css add this:

TerminalWindow .notebook {
padding: 1px;
}

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/694468

Title:
  Unnecessary chrome when showing multiple tabs

Status in GTK+ GUI Toolkit:
  Confirmed
Status in “gnome-terminal” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-terminal

  When gnome-terminal shifts from showing a single tab to showing two or
  more tabs, it introduces unnecessary chrome on the left, bottom and
  right edges of the window. This is particularly visible when the
  terminal is maximised. Chrome on the right is masked to some extent by
  the scrollbar there, but should be eliminated as well.

  To reproduce:
   * launch gnome-terminal, showing only a single tab, maximised
   * note the lack of chrome around the edges of the screen
   * ctrl-shift-t to create a new tab

  What happens:
   * you see a gray border on the left and bottom of the screen

  What should happen:
   * there should be no gray border on the left and bottom of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/694468/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp