[Linux-traipu] [Bug 711567] Re: Double window controls in Chromium after enabling Use System Title Bar and Borders

2012-05-04 Thread Daniel van Vugt
** Project changed: unity = compiz

** Package changed: unity (Ubuntu) = compiz (Ubuntu)

** Project changed: compiz = compiz-core

** Changed in: compiz-core
   Importance: Low = Medium

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/711567

Title:
  Double window controls in Chromium after enabling Use System Title
  Bar and Borders

Status in Chromium Browser:
  Unknown
Status in Compiz Core:
  Confirmed
Status in “chromium-browser” package in Ubuntu:
  Triaged
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: unity

  Steps to reproduce:
  1) Make sure Use System Title Bar and Borders is unticked (It is in the 
right click menu of the tab bar)
  2) Maximize Chromium
  3) Tick Use System Title Bar and Borders
  4) Untick Use System Title Bar and Borders
  5) Restore Chromium

  Result:
  At step 2 we see two sets of window controls, one drawn by Chromium and one 
in the top panel.
  After step 3 we see two sets of window controls, one in the top panel, one in 
Chromium's titlebar.
  When step 5 is executed we will find again that we have two sets of window 
controls, but this time one is drawn by Chromium and one by Unity.

  Expected result:
  At step 2: One set of window controls, the one drawn by Chromium.
  At step 3: One set of window controls; in the top panel (Unity).
  At step 5: One set of window controls, the one drawn by Chromium.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Tue Feb  1 18:52:53 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110127)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: unity

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

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


[Linux-traipu] [Bug 1058636] Re: system lags with fglrx, Chrome and Vsync

2012-09-30 Thread Daniel van Vugt
The behaviour of applications that do their own vsync is entirely
controlled by the graphics driver (and the application).

Compiz has nothing to do with it really.

** Project changed: compiz = chromium-browser

** Also affects: fglrx-installer (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1058636

Title:
  system lags with fglrx, Chrome and Vsync

Status in Chromium Browser:
  New
Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  Using the latest Ubuntu 12.10 build, the system stutters (to the point
  that the mouse doesn't move for a few milliseconds, very noticeable
  and annoying) when using the latest AMD Catalyst driver (fglrx 9.000
  from the quantal repository), Google Chrome and overwriting the driver
  software blacklist in about:flags (normally it should be accelerated
  by default anyway, it does with the driver from AMD.com and Ubuntu
  12.04).

  You you hover over some links, like the ones on engadget.com on the
  right (recent reviews), it stutters A LOT. When you go to about:flags
  and check disable GPU Vsync it runs smoothly and perfectly fine like
  it did with Compiz 0.9.7.x.

  Also while hovering/moving over links (with Vsync on/off), CPU usage
  goes up till 60% on my quadcore, but that's another story and has
  always been like that).

  I know there's one more Vsync related fix coming with the final compiz
  0.9.8.4 release, but I think I've read it only matters for nVidia.

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

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


[Linux-traipu] [Bug 1058636] Re: system lags with fglrx, Chrome and Vsync

2012-09-30 Thread Daniel van Vugt
If you found that ALL applications where affected, then the bug would
relate to compiz.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1058636

Title:
  system lags with fglrx, Chrome and Vsync

Status in Chromium Browser:
  New
Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  Using the latest Ubuntu 12.10 build, the system stutters (to the point
  that the mouse doesn't move for a few milliseconds, very noticeable
  and annoying) when using the latest AMD Catalyst driver (fglrx 9.000
  from the quantal repository), Google Chrome and overwriting the driver
  software blacklist in about:flags (normally it should be accelerated
  by default anyway, it does with the driver from AMD.com and Ubuntu
  12.04).

  You you hover over some links, like the ones on engadget.com on the
  right (recent reviews), it stutters A LOT. When you go to about:flags
  and check disable GPU Vsync it runs smoothly and perfectly fine like
  it did with Compiz 0.9.7.x.

  Also while hovering/moving over links (with Vsync on/off), CPU usage
  goes up till 60% on my quadcore, but that's another story and has
  always been like that).

  I know there's one more Vsync related fix coming with the final compiz
  0.9.8.4 release, but I think I've read it only matters for nVidia.

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

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


[Linux-traipu] [Bug 711567] Re: Double window controls in Chromium after enabling Use System Title Bar and Borders

2013-01-03 Thread Daniel van Vugt
** Changed in: compiz
Milestone: None = 0.9.9.0

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/711567

Title:
  Double window controls in Chromium after enabling Use System Title
  Bar and Borders

Status in Chromium Browser:
  Unknown
Status in Compiz:
  Confirmed
Status in Compiz Core:
  Confirmed
Status in “chromium-browser” package in Ubuntu:
  Triaged
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: unity

  Steps to reproduce:
  1) Make sure Use System Title Bar and Borders is unticked (It is in the 
right click menu of the tab bar)
  2) Maximize Chromium
  3) Tick Use System Title Bar and Borders
  4) Untick Use System Title Bar and Borders
  5) Restore Chromium

  Result:
  At step 2 we see two sets of window controls, one drawn by Chromium and one 
in the top panel.
  After step 3 we see two sets of window controls, one in the top panel, one in 
Chromium's titlebar.
  When step 5 is executed we will find again that we have two sets of window 
controls, but this time one is drawn by Chromium and one by Unity.

  Expected result:
  At step 2: One set of window controls, the one drawn by Chromium.
  At step 3: One set of window controls; in the top panel (Unity).
  At step 5: One set of window controls, the one drawn by Chromium.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Tue Feb  1 18:52:53 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110127)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: unity

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

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


[Linux-traipu] [Bug 711567] Re: Double window controls in Chromium after enabling Use System Title Bar and Borders

2013-01-22 Thread Daniel van Vugt
** Changed in: compiz
Milestone: 0.9.9.0 = 0.9.9.2

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/711567

Title:
  Double window controls in Chromium after enabling Use System Title
  Bar and Borders

Status in Chromium Browser:
  Unknown
Status in Compiz:
  Confirmed
Status in Compiz Core:
  Confirmed
Status in “chromium-browser” package in Ubuntu:
  Triaged
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: unity

  Steps to reproduce:
  1) Make sure Use System Title Bar and Borders is unticked (It is in the 
right click menu of the tab bar)
  2) Maximize Chromium
  3) Tick Use System Title Bar and Borders
  4) Untick Use System Title Bar and Borders
  5) Restore Chromium

  Result:
  At step 2 we see two sets of window controls, one drawn by Chromium and one 
in the top panel.
  After step 3 we see two sets of window controls, one in the top panel, one in 
Chromium's titlebar.
  When step 5 is executed we will find again that we have two sets of window 
controls, but this time one is drawn by Chromium and one by Unity.

  Expected result:
  At step 2: One set of window controls, the one drawn by Chromium.
  At step 3: One set of window controls; in the top panel (Unity).
  At step 5: One set of window controls, the one drawn by Chromium.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Tue Feb  1 18:52:53 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110127)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: unity

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

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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2018-10-04 Thread Daniel van Vugt
** Summary changed:

- Chromium does not use the GPU to decode videos
+ Web browsers lacking hardware-accelerated video decoding

** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

** Bug watch added: Mozilla Bugzilla #563206
   https://bugzilla.mozilla.org/show_bug.cgi?id=563206

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=563206
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

  https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

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

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


[Linux-traipu] [Bug 1811219] Re: High precision touchpad scrolling doesn't work in Wayland sessions (but does in Xorg)

2019-01-10 Thread Daniel van Vugt
** Bug watch added: code.google.com/p/chromium/issues #712737
   http://code.google.com/p/chromium/issues/detail?id=712737

** Also affects: chromium-browser via
   http://code.google.com/p/chromium/issues/detail?id=712737
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1811219

Title:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg).

  I guess it's probably Xwayland failing to support the more advanced
  XInput stuff?

  Note: This bug report is about high precision (and thus low latency)
  touchpad scrolling. It is not about "Smooth Scrolling" simply because
  "Smooth Scrolling" actually means something quite different in
  Chromium. :P

  Test case:

  1. In chrome://flags, set Smooth Scrolling to Disabled and restart the 
browser.
  2. Use your touchpad (usually two fingers) to scroll a web page.

  Observed:

  In an Ubuntu session (pure Xorg), the scrolling is noticeably high
  precision like a Macbook or Chromebook. In a Wayland session however,
  the scrolling stutters badly like it's still using old-style mouse
  wheel emulation.

  Note also: If you have "Smooth Scrolling" enabled then Chromium
  replaces the stutter with smoother scrolling but you can still tell
  it's broken in Wayland sessions because the latency is much higher.
  It's having to fake the smoothness by delaying and extrapolating from
  mouse wheel-style tick events.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 71.0.3578.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 
1280x1024 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Thu Jan 10 17:11:06 2019
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-12-04 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
     => libgnome-shell-browser-plugin.so
   (size: 22496 bytes, mtime: Wed Dec  5 20:53:32 2018)
  Load-Avg-1min: 2.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

-- 
Mailing list: https://launchpad.net/~linux-traipu
Post to : linux-traipu@lists.launchpad.net
Unsubscribe : 

[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2019-04-03 Thread Daniel van Vugt
Last I heard, Ubuntu "applying the patch" wasn't feasible because it
kept breaking due to upstream changes in Chromium. It's not a patch we
can carry without someone volunteering to maintain it. But oSoMoN is the
expert here and will have more current information...

P.S. You can watch YouTube videos with hardware acceleration (and no
need for patches) using these instructions:
https://wiki.ubuntu.com/IntelQuickSyncVideo#YouTube

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

  https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

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

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


[Linux-traipu] [Bug 1268210] Re: unity-scopes-runner: Typo in package description: "scoped"

2019-12-30 Thread Daniel van Vugt
** Tags added: focal

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Package Descriptions for Ubuntu.
https://bugs.launchpad.net/bugs/1268210

Title:
  unity-scopes-runner: Typo in package description: "scoped"

Status in Package Descriptions for Ubuntu:
  Triaged
Status in libunity:
  Confirmed
Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  Package: unity-scopes-runner
  Version: 7.1.3+14.04.20131106-0ubuntu1

  Hello,

  The package description contains a small typo, I think:
   The scope runner is a handy tool for wrapping on a desktop the various
   scoped installed on the system.
  Should be:
   The scope runner is a handy tool for wrapping on a desktop the various
   scopes installed on the system.

  in the string #16945
  
https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-ubuntu-main/fr/16945

  Regards,
  Pascal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ddtp-ubuntu/+bug/1268210/+subscriptions

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


[Linux-traipu] [Bug 1811219] Re: High precision touchpad scrolling doesn't work in Wayland sessions (but does in Xorg)

2020-05-06 Thread Daniel van Vugt
Fix committed upstream:

https://chromium.googlesource.com/chromium/src/+/48632c246b958ebde3f144fad428f3a38f3ea70f

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Fix Committed

** Tags removed: disco
** Tags added: fixed-upstream

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1811219

Title:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg).

  I guess it's probably Xwayland failing to support the more advanced
  XInput stuff?

  Note: This bug report is about high precision (and thus low latency)
  touchpad scrolling. It is not about "Smooth Scrolling" simply because
  "Smooth Scrolling" actually means something quite different in
  Chromium. :P

  Test case:

  1. In chrome://flags, set Smooth Scrolling to Disabled and restart the 
browser.
  2. Use your touchpad (usually two fingers) to scroll a web page.

  Observed:

  In an Ubuntu session (pure Xorg), the scrolling is noticeably high
  precision like a Macbook or Chromebook. In a Wayland session however,
  the scrolling stutters badly like it's still using old-style mouse
  wheel emulation.

  Note also: If you have "Smooth Scrolling" enabled then Chromium
  replaces the stutter with smoother scrolling but you can still tell
  it's broken in Wayland sessions because the latency is much higher.
  It's having to fake the smoothness by delaying and extrapolating from
  mouse wheel-style tick events.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 71.0.3578.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 
1280x1024 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Thu Jan 10 17:11:06 2019
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-12-04 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
     => libgnome-shell-browser-plugin.so
   (size: 22496 bytes, mtime: Wed Dec  5 20:53:32 2018)
  Load-Avg-1min: 2.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

-- 
Mailing list: https://launchpad.net/~linux-traipu
Post to : linux-traipu@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linux-traipu
More help   : 

[Linux-traipu] [Bug 1811219] Re: High precision touchpad scrolling doesn't work in Wayland sessions (but does in Xorg)

2020-07-07 Thread Daniel van Vugt
^^^
Fixed in Chromium 84, apparently.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1811219

Title:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg).

  I guess it's probably Xwayland failing to support the more advanced
  XInput stuff?

  Note: This bug report is about high precision (and thus low latency)
  touchpad scrolling. It is not about "Smooth Scrolling" simply because
  "Smooth Scrolling" actually means something quite different in
  Chromium. :P

  Test case:

  1. In chrome://flags, set Smooth Scrolling to Disabled and restart the 
browser.
  2. Use your touchpad (usually two fingers) to scroll a web page.

  Observed:

  In an Ubuntu session (pure Xorg), the scrolling is noticeably high
  precision like a Macbook or Chromebook. In a Wayland session however,
  the scrolling stutters badly like it's still using old-style mouse
  wheel emulation.

  Note also: If you have "Smooth Scrolling" enabled then Chromium
  replaces the stutter with smoother scrolling but you can still tell
  it's broken in Wayland sessions because the latency is much higher.
  It's having to fake the smoothness by delaying and extrapolating from
  mouse wheel-style tick events.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 71.0.3578.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 
1280x1024 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Thu Jan 10 17:11:06 2019
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-12-04 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
     => libgnome-shell-browser-plugin.so
   (size: 22496 bytes, mtime: Wed Dec  5 20:53:32 2018)
  Load-Avg-1min: 2.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Linux-traipu] [Bug 1811219] Re: High precision touchpad scrolling doesn't work in Wayland sessions (but does in Xorg)

2020-07-08 Thread Daniel van Vugt
Not today... I don't use a machine with a touchpad usually.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1811219

Title:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg).

  I guess it's probably Xwayland failing to support the more advanced
  XInput stuff?

  Note: This bug report is about high precision (and thus low latency)
  touchpad scrolling. It is not about "Smooth Scrolling" simply because
  "Smooth Scrolling" actually means something quite different in
  Chromium. :P

  Test case:

  1. In chrome://flags, set Smooth Scrolling to Disabled and restart the 
browser.
  2. Use your touchpad (usually two fingers) to scroll a web page.

  Observed:

  In an Ubuntu session (pure Xorg), the scrolling is noticeably high
  precision like a Macbook or Chromebook. In a Wayland session however,
  the scrolling stutters badly like it's still using old-style mouse
  wheel emulation.

  Note also: If you have "Smooth Scrolling" enabled then Chromium
  replaces the stutter with smoother scrolling but you can still tell
  it's broken in Wayland sessions because the latency is much higher.
  It's having to fake the smoothness by delaying and extrapolating from
  mouse wheel-style tick events.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 71.0.3578.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 
1280x1024 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Thu Jan 10 17:11:06 2019
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-12-04 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
     => libgnome-shell-browser-plugin.so
   (size: 22496 bytes, mtime: Wed Dec  5 20:53:32 2018)
  Load-Avg-1min: 2.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Linux-traipu] [Bug 1811219] Re: High precision touchpad scrolling doesn't work in Wayland sessions (but does in Xorg)

2020-07-08 Thread Daniel van Vugt
Verified fixed in chromium 84 (beta).

Although that means it's now as good as Xorg sessions, which isn't
really good enough IMHO. There's too much lag in both, which you can
remove with 'Smooth Scrolling = Disabled' in chrome://flags/

Weird ChromeOS doesn't have any of these problems...

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1811219

Title:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg).

  I guess it's probably Xwayland failing to support the more advanced
  XInput stuff?

  Note: This bug report is about high precision (and thus low latency)
  touchpad scrolling. It is not about "Smooth Scrolling" simply because
  "Smooth Scrolling" actually means something quite different in
  Chromium. :P

  Test case:

  1. In chrome://flags, set Smooth Scrolling to Disabled and restart the 
browser.
  2. Use your touchpad (usually two fingers) to scroll a web page.

  Observed:

  In an Ubuntu session (pure Xorg), the scrolling is noticeably high
  precision like a Macbook or Chromebook. In a Wayland session however,
  the scrolling stutters badly like it's still using old-style mouse
  wheel emulation.

  Note also: If you have "Smooth Scrolling" enabled then Chromium
  replaces the stutter with smoother scrolling but you can still tell
  it's broken in Wayland sessions because the latency is much higher.
  It's having to fake the smoothness by delaying and extrapolating from
  mouse wheel-style tick events.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 71.0.3578.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 
1280x1024 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Thu Jan 10 17:11:06 2019
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-12-04 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
     => libgnome-shell-browser-plugin.so
   (size: 22496 bytes, mtime: Wed Dec  5 20:53:32 2018)
  Load-Avg-1min: 2.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

-- 
Mailing list: https://launchpad.net/~linux-traipu
Post to : linux-traipu@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linux-traipu
More 

[Linux-traipu] [Bug 1811219] Re: High precision touchpad scrolling doesn't work in Wayland sessions (but does in Xorg)

2021-02-01 Thread Daniel van Vugt
** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1811219

Title:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg).

  I guess it's probably Xwayland failing to support the more advanced
  XInput stuff?

  Note: This bug report is about high precision (and thus low latency)
  touchpad scrolling. It is not about "Smooth Scrolling" simply because
  "Smooth Scrolling" actually means something quite different in
  Chromium. :P

  Test case:

  1. In chrome://flags, set Smooth Scrolling to Disabled and restart the 
browser.
  2. Use your touchpad (usually two fingers) to scroll a web page.

  Observed:

  In an Ubuntu session (pure Xorg), the scrolling is noticeably high
  precision like a Macbook or Chromebook. In a Wayland session however,
  the scrolling stutters badly like it's still using old-style mouse
  wheel emulation.

  Note also: If you have "Smooth Scrolling" enabled then Chromium
  replaces the stutter with smoother scrolling but you can still tell
  it's broken in Wayland sessions because the latency is much higher.
  It's having to fake the smoothness by delaying and extrapolating from
  mouse wheel-style tick events.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 71.0.3578.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 
1280x1024 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Thu Jan 10 17:11:06 2019
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-12-04 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
     => libgnome-shell-browser-plugin.so
   (size: 22496 bytes, mtime: Wed Dec  5 20:53:32 2018)
  Load-Avg-1min: 2.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2021-10-14 Thread Daniel van Vugt
Tracking in bug 1947115 for the Firefox snap, although once fixed that's
probably enough to close this one for Firefox too.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
  browsers.

  In 2015 I opened this bug , no easy solution was available and battery
  drained when playing video in browser was crazy.

  In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. Ubuntu now will integrate
  this patch on Snap chromium stable soon , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497


  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  We shall close this bug when both browsers will have Va-api decoding
  available in Stable.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2021-11-16 Thread Daniel van Vugt
It looks like the old Chrome bug has been dead for a while:

  https://bugs.chromium.org/p/chromium/issues/detail?id=463440

But some newer bugs offer hope:

  https://bugs.chromium.org/p/chromium/issues/detail?id=1121948
  https://bugs.chromium.org/p/chromium/issues/detail?id=1262051

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
  browsers.

  In 2015 I opened this bug , no easy solution was available and battery
  drained when playing video in browser was crazy.

  In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. Ubuntu now will integrate
  this patch on Snap chromium stable soon , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497


  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  We shall close this bug when both browsers will have Va-api decoding
  available in Stable.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2022-09-06 Thread Daniel van Vugt
** Tags added: kivu performance

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2022-08-17 Thread Daniel van Vugt
Partial duplicate: bug 1816497

** Changed in: chromium-browser (Ubuntu)
 Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio)

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2023-05-15 Thread Daniel van Vugt
Based on a recent report (https://discourse.ubuntu.com/t/problems-with-
intel-iris-xe-gpu-hardware-video-acceleration-in-22-04/34849/4), I think
Firefox is missing:

* Xwayland support: requires libva >= 2.17 in the gnome-42-2204 snap.
That's also missing from jammy-updates.

* Intel 13th gen support: The fix for bug 2004237 needs to go in the
gnome-42-2204 snap (patched iHD_drv_video.so).

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2023-05-15 Thread Daniel van Vugt
AV1 sounds like a third and orthogonal issue, separate from the two
issues mentioned in comment #146.

The fact the bug is solved for the Ubuntu archive but not for snaps is a
temporary problem. Longer term we will have graphics driver snaps being
updated independently of app/gnome snaps. So then all apps will get the
same level of hardware enablement at the same time.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2024-01-28 Thread Daniel van Vugt
This bug is still open for Firefox. Also the issue mentioned in comment
#146 isn't resolved yet. Unless comment #146 is wrong?

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2024-02-03 Thread Daniel van Vugt
Verified working in firefox (Wayland) on both Intel 12th and 13th gen
systems. intel_gpu_top shows hardware video decoding is in use straight
out of the box when viewing YouTube. The firefox snap versions tested
were 122.0-2 and 122.0-2.1, both Noble systems.

Caveat: intel_gpu_top also shows very high values for Render/3D, so it's
not power efficient. More work will need to be done toward zero-copy (or
just less copy) in future.


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Fix Released
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when most browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  January 2024:

  - Quickest answer : Install firefox Flatpak 
https://flathub.org/fr/apps/org.mozilla.firefox
   activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true

  - Snap : Test in Progress
  - deb from mozilla : not tested.

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
     -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2024-02-03 Thread Daniel van Vugt
I only tested a 13th gen U chip in the above comment. It looks like 13th
gen P chips should be supported so long as:

  intel-media-driver >= 22.3.1+dfsg1-1ubuntu2 (per bug 2004237)

which it looks like snaps are shipping with now.

Newer Intel 14th gen and Ultra chips might not be supported yet, but if
so then please log a new bug about that.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Fix Released
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when most browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  January 2024:

  - Quickest answer : Install firefox Flatpak 
https://flathub.org/fr/apps/org.mozilla.firefox
   activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true

  - Snap : Test in Progress
  - deb from mozilla : not tested.

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
     -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2024-01-31 Thread Daniel van Vugt
Yeah that's the same question I had in "EDIT" of comment #151. Someone
just needs to test it on old and new hardware.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when most browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  January 2024:

  - Quickest answer : Install firefox Flatpak 
https://flathub.org/fr/apps/org.mozilla.firefox
   activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true

  - Snap : still not ready
  - deb from mozilla : not tested.

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
     -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

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


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


[Linux-traipu] [Bug 2063336] Re: All Chromium based applications fail to render on Wayland

2024-04-24 Thread Daniel van Vugt
Sounds like bug 1967488 might've got fixed in the past few months (which
would be great news), worked for a while and then
https://issues.chromium.org/issues/329678163 hit which affects all GPUs
and OS releases.

Also the glitchy rendering after typing is bug 1970389 (if not bug
2059847 on Xorg), but after that I have no more bad news because those
are all the blockers for Wayland on Nvidia:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/2063336

Title:
  All Chromium based applications fail to render on Wayland

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Most of the time (3/4 desktop sessions attempted) all Chromium based
  applications I have tested (Chromium, VS Code, Mattermost) fail to
  render themselves, on actual display panel presenting random garbage,
  and when screenshotted, showing supposedly transparent pixels.

  I have also recorded an example video I can share in case this is of
  use (attached the screenshot with the video).

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 16:21:15 2024
  InstallationDate: Installed on 2021-11-08 (898 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Snap: chromium 124.0.6367.60 (latest/stable)
  SnapChanges: no changes found
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago)

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


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


[Linux-traipu] [Bug 2063336] Re: All Chromium based applications fail to render (dual NVIDIA GPU system)

2024-04-24 Thread Daniel van Vugt
Fixed upstream today?

https://issues.chromium.org/issues/329678163

** Also affects: chromium-browser via
   https://issues.chromium.org/issues/329678163
   Importance: Unknown
   Status: Unknown

** Summary changed:

- All Chromium based applications fail to render (dual NVIDIA GPU system)
+ All Chromium based applications fail to render on Wayland

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/2063336

Title:
  All Chromium based applications fail to render on Wayland

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I am noticing two

  - Most of the time (3/4 desktop sessions attempted) all Chromium based
  applications I have tested (Chromium, VS Code, Mattermost) fail to
  render themselves, on actual display panel presenting random garbage,
  and when screenshotted, showing supposedly showing transparent pixels.

  I have also recorded an example video I can share in case this is of
  use (attached the screenshot with the video).

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 16:21:15 2024
  InstallationDate: Installed on 2021-11-08 (898 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Snap: chromium 124.0.6367.60 (latest/stable)
  SnapChanges: no changes found
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago)

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


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


[Linux-traipu] [Bug 2063336] Re: All Chromium based applications fail to render on Wayland

2024-04-24 Thread Daniel van Vugt
*** This bug is a duplicate of bug 2063049 ***
https://bugs.launchpad.net/bugs/2063049

Since this isn't the first report of the problem, and is also confused
by separate Nvidia issues, let's use bug 2063049 instead.

** Changed in: chromium-browser (Ubuntu)
Milestone: ubuntu-24.04 => None

** This bug has been marked a duplicate of bug 2063049
   Google Chrome and Chromium 124 have a transparent window on Wayland

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/2063336

Title:
  All Chromium based applications fail to render on Wayland

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Most of the time (3/4 desktop sessions attempted) all Chromium based
  applications I have tested (Chromium, VS Code, Mattermost) fail to
  render themselves, on actual display panel presenting random garbage,
  and when screenshotted, showing supposedly transparent pixels.

  I have also recorded an example video I can share in case this is of
  use (attached the screenshot with the video).

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 16:21:15 2024
  InstallationDate: Installed on 2021-11-08 (898 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Snap: chromium 124.0.6367.60 (latest/stable)
  SnapChanges: no changes found
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago)

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


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


[Linux-traipu] [Bug 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland

2024-04-24 Thread Daniel van Vugt
Tracking upstream in:
https://issues.chromium.org/issues/329678163

** Summary changed:

- chromium snap doesnt launch properly on 24.04
+ Google Chrome and Chromium 124 have a transparent window on Wayland

** Bug watch added: issues.chromium.org/issues #329678163
   https://issues.chromium.org/issues/329678163

** Also affects: chromium-browser via
   https://issues.chromium.org/issues/329678163
   Importance: Unknown
   Status: Unknown

** Tags added: jammy

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Critical

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/2063049

Title:
  Google Chrome and Chromium 124 have a transparent window on Wayland

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  chromium snap only launches with titlebar and transparent window after
  recent snap update on wayland and intel grafics.

  Adding --ozone-platform=wayland fixes the issue for me. (workaround
  from bug #1968610)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: chromium-browser 2:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Sun Apr 21 20:25:30 2024
  DiskUsage:
   FilesystemType   Size  Used Avail Use% Mounted on
   rpool/ROOT/ubuntu_gk6kaa  zfs 50G  7,7G   42G  16% /
   tmpfs tmpfs   16G  128M   16G   1% /dev/shm
   rpool/USERDATA/k1l_0tberh zfs437G  396G   42G  91% /home/k1l
  InstallationDate: Installed on 2022-03-24 (760 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   635  Done2024-04-21T00:51:33+02:00  2024-04-21T00:52:11+02:00  Snap 
"chromium" aktualisieren
  Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60 
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
  Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)

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


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


[Linux-traipu] [Bug 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland

2024-05-01 Thread Daniel van Vugt
Looks like the fix is in Chrome 124.0.6367.118

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/2063049

Title:
  Google Chrome and Chromium 124 have a transparent window on Wayland

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  chromium snap only launches with titlebar and transparent window after
  recent snap update on wayland and intel grafics.

  Adding --ozone-platform=wayland fixes the issue for me. (workaround
  from bug #1968610)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: chromium-browser 2:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Sun Apr 21 20:25:30 2024
  DiskUsage:
   FilesystemType   Size  Used Avail Use% Mounted on
   rpool/ROOT/ubuntu_gk6kaa  zfs 50G  7,7G   42G  16% /
   tmpfs tmpfs   16G  128M   16G   1% /dev/shm
   rpool/USERDATA/k1l_0tberh zfs437G  396G   42G  91% /home/k1l
  InstallationDate: Installed on 2022-03-24 (760 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   635  Done2024-04-21T00:51:33+02:00  2024-04-21T00:52:11+02:00  Snap 
"chromium" aktualisieren
  Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60 
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
  Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)

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


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