Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
I tried reading webpages using orca in the latest chrome but a 1 year old bug tells orca to use lines rather than sentences as per orca default settings
*** End of the template - remove these template lines ***

Note that you're using google's proprietary chrome package. I'm
assuming that the same thing happens with debian's chromium package? If
so, please update this package when it gets fixed upstream.


On Thu, 08 Jun 2023 19:56:17 +0100 jordan <jordanlivesey9@gmail.com>  wrote:
 > Package: google-chrome-stable
 > Version: 114.0.5735.106-1
 > Severity: important
 > X-Debbugs-Cc: jordanlivesey9@gmail.com
 >
 > Dear Maintainer,
 >
 > *** Reporter, please consider answering these questions, where
appropriate ***
 >
 >    * What led up to the situation?
 >    * What exactly did you do (or not do) that was effective (or
 >      ineffective)?
 >    * What was the outcome of this action?
 >    * What outcome did you expect instead?
 > I tried reading webpages using orca in the latest chrome but a 1
year old bug tells orca to use lines rather than sentences as per orca
default settings
 > *** End of the template - remove these template lines ***
 >
 >
 > -- System Information:
 > Debian Release: 12.0
 >   APT prefers testing-security
 >   APT policy: (500, 'testing-security'), (500, 'testing')
 > Architecture: amd64 (x86_64)
 >
 > Kernel: Linux 6.1.0-9-amd64 (SMP w/6 CPU threads; PREEMPT)
 > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE not set
 > Shell: /bin/sh linked to /usr/bin/dash
 > Init: systemd (via /run/systemd/system)
 > LSM: AppArmor: enabled
 >
 > Versions of packages google-chrome-stable depends on:
 > ii  ca-certificates     20230311
 > ii  dpkg                1.21.22
 > ii  fonts-liberation    1:1.07.4-11
 > ii  libasound2          1.2.8-1+b1
 > ii  libatk-bridge2.0-0  2.46.0-5
 > ii  libatk1.0-0         2.46.0-5
 > ii  libatspi2.0-0       2.46.0-5
 > ii  libc6               2.36-9
 > ii  libcairo2           1.16.0-7
 > ii  libcups2            2.4.2-3
 > ii  libcurl3-gnutls     7.88.1-10
 > ii  libcurl4            7.88.1-10
 > ii  libdbus-1-3         1.14.6-1
 > ii  libdrm2             2.4.114-1+b1
 > ii  libexpat1           2.5.0-1
 > ii  libgbm1             22.3.6-1+deb12u1
 > ii  libglib2.0-0        2.74.6-2
 > ii  libgtk-3-0          3.24.37-2
 > ii  libgtk-4-1          4.8.3+ds-2
 > ii  libnspr4            2:4.35-1
 > ii  libnss3             2:3.87.1-1
 > ii  libpango-1.0-0      1.50.12+ds-1
 > ii  libu2f-udev         1.1.10-3
 > ii  libvulkan1          1.3.239.0-1
 > ii  libx11-6            2:1.8.4-2
 > ii  libxcb1             1.15-1
 > ii  libxcomposite1      1:0.4.5-1
 > ii  libxdamage1         1:1.1.6-1
 > ii  libxext6            2:1.3.4-1+b1

Note that you're using google's proprietary chrome package. I'm
assuming that the same thing happens with debian's chromium package? If
so, please update this package when it gets fixed upstream.


On Thu, 08 Jun 2023 19:56:17 +0100 jordan <jordanlivesey9@gmail.com>  wrote:
 > Package: google-chrome-stable
 > Version: 114.0.5735.106-1
 > Severity: important
 > X-Debbugs-Cc: jordanlivesey9@gmail.com
 >
 > Dear Maintainer,
 >
 > *** Reporter, please consider answering these questions, where
appropriate ***
 >
 >    * What led up to the situation?
 >    * What exactly did you do (or not do) that was effective (or
 >      ineffective)?
 >    * What was the outcome of this action?
 >    * What outcome did you expect instead?
 > I tried reading webpages using orca in the latest chrome but a 1
year old bug tells orca to use lines rather than sentences as per orca
default settings
 > *** End of the template - remove these template lines ***
 >
 >
 > -- System Information:
 > Debian Release: 12.0
 >   APT prefers testing-security
 >   APT policy: (500, 'testing-security'), (500, 'testing')
 > Architecture: amd64 (x86_64)
 >
 > Kernel: Linux 6.1.0-9-amd64 (SMP w/6 CPU threads; PREEMPT)
 > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE not set
 > Shell: /bin/sh linked to /usr/bin/dash
 > Init: systemd (via /run/systemd/system)
 > LSM: AppArmor: enabled
 >
 > Versions of packages google-chrome-stable depends on:
 > ii  ca-certificates     20230311
 > ii  dpkg                1.21.22
 > ii  fonts-liberation    1:1.07.4-11
 > ii  libasound2          1.2.8-1+b1
 > ii  libatk-bridge2.0-0  2.46.0-5
 > ii  libatk1.0-0         2.46.0-5
 > ii  libatspi2.0-0       2.46.0-5
 > ii  libc6               2.36-9
 > ii  libcairo2           1.16.0-7
 > ii  libcups2            2.4.2-3
 > ii  libcurl3-gnutls     7.88.1-10
 > ii  libcurl4            7.88.1-10
 > ii  libdbus-1-3         1.14.6-1
 > ii  libdrm2             2.4.114-1+b1
 > ii  libexpat1           2.5.0-1
 > ii  libgbm1             22.3.6-1+deb12u1
 > ii  libglib2.0-0        2.74.6-2
 > ii  libgtk-3-0          3.24.37-2
 > ii  libgtk-4-1          4.8.3+ds-2
 > ii  libnspr4            2:4.35-1
 > ii  libnss3             2:3.87.1-1
 > ii  libpango-1.0-0      1.50.12+ds-1
 > ii  libu2f-udev         1.1.10-3
 > ii  libvulkan1          1.3.239.0-1
 > ii  libx11-6            2:1.8.4-2
 > ii  libxcb1             1.15-1
 > ii  libxcomposite1      1:0.4.5-1
 > ii  libxdamage1         1:1.1.6-1
 > ii  libxext6            2:1.3.4-1+b1

Oops, I meant please update this *bug report* when it gets fixed
upstream.

yes, it happens to all chromium browsers, even upstream chromium, the bug
has been present since march 2022

yes, it happens to all chromium browsers, even upstream chromium, the bug
has been present since march 2022