Bug#974543: Acknowledgement (segmentation fault on launch)

[Mika Hanhijärvi]

I am able to work around this problem on Debian Buster by adding the line:


imports.gi.versions.GtkSource = "3.0";


to the beginning of the file:


/usr/share/sushi/js/viewers/text.js

Bug#974543: Acknowledgement (segmentation fault on launch)

[Mika Hanhijärvi]

I am able to work around this problem on Debian Buster by adding the line:


imports.gi.versions.GtkSource = "3.0";


to the beginning of the file:


/usr/share/sushi/js/viewers/text.js

Bug#974543: Acknowledgement (segmentation fault on launch)

[Mika Hanhijärvi]

I am able to work around this problem on Debian Buster by adding the line:

|imports.gi.versions.GtkSource = "3.0";|


to the beginning of the file:

|
|

|/usr/share/sushi/js/viewers/text.js|

|
|

Bug#974543: Acknowledgement (segmentation fault on launch)

[Mika Hanhijärvi]

I am able to work around this problem on Debian Buster by adding the line:

|imports.gi.versions.GtkSource = "3.0";|


to the beginning of the file:

|
|

|/usr/share/sushi/js/viewers/text.js|

|
|

Bug#974543: segmentation fault on launch

[Mika Hanhijärvi]

Package: gnome-sushi
Version: 3.30.0-2
Severity: grave

Hello

Sushi does not seem to work on Debian Buster. If I select e.g. some mp3 file in
Nautilus filemanager and press the space bar then nothing happens. The same
happens if I select file of some other type. I also get this error in the
/var/log/syslog

Nov 12 06:16:13 miksuh-laptop kernel: [10482.886638] sushi-start[11917]:
segfault at 0 ip 7ff7a1aaf64f sp 7ffe20adb3c0 error 6 in
libgjs.so.0.0.0[7ff7a1a75000+67000]
Nov 12 06:16:13 miksuh-laptop kernel: [10482.886648] Code: 00 e8 a5 7c fc ff 4c
8b 04 24 48 8d 0d 5d 41 03 00 48 8b 7c 24 18 89 c6 31 d2 31 c0 e8 4a 9e fc ff
48 8b 7b 18 e8 11 8e fc ff <41> c7 07 01 00 00 00 e9 82 00 00 00 0f 1f 44 00 00
48 8b bb 78 01

When I try to launch sushi from the command line it segfaults with the followin
error:

Gjs-Message: 06:06:08.541: JS WARNING: [/usr/share/sushi/js/viewers/text.js
26]: Requiring Gdk but it has 2 versions available; use imports.gi.versions to
pick one
Gjs-Message: 06:06:08.563: JS WARNING: [/usr/share/sushi/js/viewers/text.js
30]: Requiring GtkSource but it has 2 versions available; use
imports.gi.versions to pick one

(sushi-start:11595): Gjs-WARNING **: 06:06:08.564: JS ERROR: Error: Requiring
Sushi, version none: Requiring namespace 'GtkSource' version '3.0', but '4' is
already loaded
@/usr/share/sushi/js/viewers/text.js:33:7

Segmentation fault


This seems to be the same bug as reported upstream here:

https://gitlab.gnome.org/GNOME/sushi/-/issues/12






-- System Information:
Debian Release: 10.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-sushi depends on:
ii  gir1.2-clutter-1.0  1.26.2+dfsg-10
ii  gir1.2-clutter-gst-3.0  3.0.26-2
ii  gir1.2-evince-3.0   3.30.2-3+deb10u1
ii  gir1.2-gdkpixbuf-2.02.38.1+dfsg-1
ii  gir1.2-glib-2.0 1.58.3-2
ii  gir1.2-gst-plugins-base-1.0 1.14.4-2
ii  gir1.2-gstreamer-1.01.14.4-1
ii  gir1.2-gtk-3.0  3.24.5-1
ii  gir1.2-gtkclutter-1.0   1.8.4-4
ii  gir1.2-gtksource-3.03.24.9-2
ii  gir1.2-pango-1.01.42.4-8~deb10u1
ii  gir1.2-webkit2-4.0  2.28.4-1~deb10u1
ii  gstreamer1.0-plugins-good   1.14.4-1
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4
ii  libclutter-1.0-01.26.2+dfsg-10
ii  libclutter-gst-3.0-03.0.26-2
ii  libclutter-gtk-1.0-01.8.4-4
ii  libevdocument3-43.30.2-3+deb10u1
ii  libevview3-33.30.2-3+deb10u1
ii  libfreetype62.9.1-3+deb10u2
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libgirepository-1.0-1   1.58.3-2
ii  libgjs0g1.54.3-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libgtk-3-0  3.24.5-1
ii  libgtksourceview-3.0-1  3.24.9-2
ii  libharfbuzz0b   2.3.1-1
ii  libmusicbrainz5-2   5.1.0+git20150707-9
ii  libpango-1.0-0  1.42.4-8~deb10u1
ii  libpangocairo-1.0-0 1.42.4-8~deb10u1
ii  libx11-62:1.6.7-1+deb10u1
ii  nautilus3.30.5-2

gnome-sushi recommends no packages.

Versions of packages gnome-sushi suggests:
ii  gstreamer1.0-libav  1.15.0.1+git20180723+db823502-2

-- no debconf information

Bug#974543: segmentation fault on launch

[Mika Hanhijärvi]

Package: gnome-sushi
Version: 3.30.0-2
Severity: grave

Hello

Sushi does not seem to work on Debian Buster. If I select e.g. some mp3 file in
Nautilus filemanager and press the space bar then nothing happens. The same
happens if I select file of some other type. I also get this error in the
/var/log/syslog

Nov 12 06:16:13 miksuh-laptop kernel: [10482.886638] sushi-start[11917]:
segfault at 0 ip 7ff7a1aaf64f sp 7ffe20adb3c0 error 6 in
libgjs.so.0.0.0[7ff7a1a75000+67000]
Nov 12 06:16:13 miksuh-laptop kernel: [10482.886648] Code: 00 e8 a5 7c fc ff 4c
8b 04 24 48 8d 0d 5d 41 03 00 48 8b 7c 24 18 89 c6 31 d2 31 c0 e8 4a 9e fc ff
48 8b 7b 18 e8 11 8e fc ff <41> c7 07 01 00 00 00 e9 82 00 00 00 0f 1f 44 00 00
48 8b bb 78 01

When I try to launch sushi from the command line it segfaults with the followin
error:

Gjs-Message: 06:06:08.541: JS WARNING: [/usr/share/sushi/js/viewers/text.js
26]: Requiring Gdk but it has 2 versions available; use imports.gi.versions to
pick one
Gjs-Message: 06:06:08.563: JS WARNING: [/usr/share/sushi/js/viewers/text.js
30]: Requiring GtkSource but it has 2 versions available; use
imports.gi.versions to pick one

(sushi-start:11595): Gjs-WARNING **: 06:06:08.564: JS ERROR: Error: Requiring
Sushi, version none: Requiring namespace 'GtkSource' version '3.0', but '4' is
already loaded
@/usr/share/sushi/js/viewers/text.js:33:7

Segmentation fault


This seems to be the same bug as reported upstream here:

https://gitlab.gnome.org/GNOME/sushi/-/issues/12






-- System Information:
Debian Release: 10.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-sushi depends on:
ii  gir1.2-clutter-1.0  1.26.2+dfsg-10
ii  gir1.2-clutter-gst-3.0  3.0.26-2
ii  gir1.2-evince-3.0   3.30.2-3+deb10u1
ii  gir1.2-gdkpixbuf-2.02.38.1+dfsg-1
ii  gir1.2-glib-2.0 1.58.3-2
ii  gir1.2-gst-plugins-base-1.0 1.14.4-2
ii  gir1.2-gstreamer-1.01.14.4-1
ii  gir1.2-gtk-3.0  3.24.5-1
ii  gir1.2-gtkclutter-1.0   1.8.4-4
ii  gir1.2-gtksource-3.03.24.9-2
ii  gir1.2-pango-1.01.42.4-8~deb10u1
ii  gir1.2-webkit2-4.0  2.28.4-1~deb10u1
ii  gstreamer1.0-plugins-good   1.14.4-1
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4
ii  libclutter-1.0-01.26.2+dfsg-10
ii  libclutter-gst-3.0-03.0.26-2
ii  libclutter-gtk-1.0-01.8.4-4
ii  libevdocument3-43.30.2-3+deb10u1
ii  libevview3-33.30.2-3+deb10u1
ii  libfreetype62.9.1-3+deb10u2
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libgirepository-1.0-1   1.58.3-2
ii  libgjs0g1.54.3-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libgtk-3-0  3.24.5-1
ii  libgtksourceview-3.0-1  3.24.9-2
ii  libharfbuzz0b   2.3.1-1
ii  libmusicbrainz5-2   5.1.0+git20150707-9
ii  libpango-1.0-0  1.42.4-8~deb10u1
ii  libpangocairo-1.0-0 1.42.4-8~deb10u1
ii  libx11-62:1.6.7-1+deb10u1
ii  nautilus3.30.5-2

gnome-sushi recommends no packages.

Versions of packages gnome-sushi suggests:
ii  gstreamer1.0-libav  1.15.0.1+git20180723+db823502-2

-- no debconf information

Re: [BRLTTY] brlapi programming examples

[Mika Hanhijärvi]

Hi


Still have not managed to make that work. I changed


#!/usr/bin/python3


to:


#!/usr/bin/env python



So python 2.7 is now used instead of python 3. Now I get this error:


Traceback (most recent call last):
  File "./test6.py", line 7, in 
    b.enterTtyMode()
  File "brlapi.pyx", line 395, in brlapi.Connection.enterTtyMode
brlapi.OperationError: Can't determine tty number



I am running the code from the GNOME Terminal window. I have not tried 
to run it from console yet. Should it work when run from terminal window 
or am I missing something?










Samuel Thibault kirjoitti 25.8.2020 klo 21.15:

Hello,

Mika Hanhijärvi, le mar. 25 août 2020 20:54:31 +0300, a ecrit:

#!/usr/bin/python3
import brlapi

try:
   b = brlapi.Connection()
   b.enterTtyMode()
If I understand it correctly that should work

Yes, that's alright.


but when I run that I get this error:

Traceback (most recent call last):
   File "./test5.py", line 6, in 
     b.enterTtyMode()
   File "brlapi.pyx", line 446, in brlapi.Connection.enterTtyMode
brlapi.OperationError: 

That's odd, I tried it in a VM, without problem.

Unfortunately it seems the exception printing got broken.

You can however check the brltty logs, you can raise its verbosity to
debug and add the server category in /etc/brltty.conf's log-level line.

Samuel
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] brlapi programming examples

[Mika Hanhijärvi]

Hello


I have not checked out yet what is in the brltty logs, but I just tried 
to run that same python code on my other laptop which is also running 
Debian Buster. On that laptop brltty version is 5.6. I got the same 
result so the same problem exists on both laptops and with both brltty 
5.6 and 6.0.




I am using Gnome desktop and I run that python code from terminal 
window. I have tried to disable braille feature in Orca settings but 
that did not make any difference. I will check out brltty logs tomorrow.





Samuel Thibault kirjoitti 25.8.2020 klo 21.15:

Hello,

Mika Hanhijärvi, le mar. 25 août 2020 20:54:31 +0300, a ecrit:

#!/usr/bin/python3
import brlapi

try:
   b = brlapi.Connection()
   b.enterTtyMode()
If I understand it correctly that should work

Yes, that's alright.


but when I run that I get this error:

Traceback (most recent call last):
   File "./test5.py", line 6, in 
     b.enterTtyMode()
   File "brlapi.pyx", line 446, in brlapi.Connection.enterTtyMode
brlapi.OperationError: 

That's odd, I tried it in a VM, without problem.

Unfortunately it seems the exception printing got broken.

You can however check the brltty logs, you can raise its verbosity to
debug and add the server category in /etc/brltty.conf's log-level line.

Samuel
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] brlapi programming examples

[Mika Hanhijärvi]

Hello


Thanks. I did read the "pydoc3 brlapi" documentation and I tried this 
simple test:



#!/usr/bin/python3
import brlapi

try:
  b = brlapi.Connection()
  b.enterTtyMode()
except brlapi.ConnectionError as e:
  if e.brlerrno == brlapi.ERROR_CONNREFUSED:
    print("Connection to %s refused. BRLTTY is too busy..." % e.host)
  elif e.brlerrno == brlapi.ERROR_AUTHENTICATION:
    print("Authentication with %s failed. Please check the permissions 
of %s" % (e.host,e.auth))
  elif e.brlerrno == brlapi.ERROR_LIBCERR and (e.libcerrno == 
errno.ECONNREFUSED or e.libcerrno == errno.ENOENT):

    print("Connection to %s failed. Is BRLTTY really running?" % (e.host))
  else:
    print("Connection to BRLTTY at %s failed: " % (e.host))
  print(e)
  print(e.brlerrno)
  print(e.libcerrno)



If I understand it correctly that should work but when I run that I get 
this error:




Traceback (most recent call last):
  File "./test5.py", line 6, in 
    b.enterTtyMode()
  File "brlapi.pyx", line 446, in brlapi.Connection.enterTtyMode
brlapi.OperationError: 




Am I missing something? Any idea what is wrong? I use Debi an 10 
"Buster" and I have installed brltty 6.0 packages from the Debian 
Buster's backports repository.








Samuel Thibault kirjoitti 24.8.2020 klo 17.33:

Hello,

Mika Hanhijärvi, le lun. 24 août 2020 17:25:58 +0300, a ecrit:

Could someone please tell me from where I can find some examples of how to
use brlapi in my own application or game?

You have the documentation online
https://brltty.app/doc/Manual-BrlAPI/English/BrlAPI.html
and the doxygen documentation
https://brltty.app/doc/BrlAPIref/index.html

and you can find in the brltty source Programs/apitest.c or
Programs/xbrlapi.c for C examples, and the head of "pydoc3 brlapi" which
shows a python example.

Samuel
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] brlapi programming examples

[Mika Hanhijärvi]

Hi


Could someone please tell me from where I can find some examples of how 
to use brlapi in my own application or game? I just would like to create 
my own braille tetris :-) I would try to do that juset for fun :-) I 
would like to know how to use the control keys in braille display and 
how tocontrol display's content dot by dot . Both Python and C or C 
examples are welcome.




___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Is there a bluetooth guide for the Freedom Scientific displays?

[Mika Hanhijärvi]

Hi


Atleast my Focus 40 Blue has worked wery well over Bluetooth. I 
avctually have used USB cable only when braille display's battery is 
empty or if I want to charge the battery at the same time when I am 
using the braille display. Atleast the battery in my braille display has 
lasted well.




Georgina Joyce kirjoitti 21.6.2020 klo 18.07:

Hello All,

I have found my Pi 3B and it appears I have speakup up and working. I 
had to install brltty and I have uncommented the driver line of the 
configuration file. It is currently tethered by USB cable. My next 
step is to configure preferences and see how much bluetooth takes a 
hit on the battery. But how do I establish the bluetooth code for the 
Focus Blue?


Many thanks,

Gena

Gena

Call: M0EBP
DMR ID: 2346259
Loc: IO83PS
73


___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Bug#913978: (no subject)

[Mika Hanhijärvi]

Hi


Has there been any progress in fixing this bug?Atleast I have not heard
about any progress at all. Looks like Gnome developers do not care about
accessibility at all...

Bug#913978: (no subject)

[Mika Hanhijärvi]

Hi


Has there been any progress in fixing this bug?Atleast I have not heard
about any progress at all. Looks like Gnome developers do not care about
accessibility at all...

Bug#931585: gnome: Executed applications dock lost

[Mika Hanhijärvi]

Hi


Are you talking about the legacy status icon panel? It sounds like you
are talking about it. If so then please note that status icon panel was
removed from Gnome, it is not part of the Gnome anymore. So this it not
a bug. Gnome developers decided to remove the legacy status icon panel
from Gnome.  

Bug#931585: gnome: Executed applications dock lost

[Mika Hanhijärvi]

Hi


Are you talking about the legacy status icon panel? It sounds like you
are talking about it. If so then please note that status icon panel was
removed from Gnome, it is not part of the Gnome anymore. So this it not
a bug. Gnome developers decided to remove the legacy status icon panel
from Gnome.  

Bug#931490: should not be removed from Buster (important for visually impaired users))

[Mika Hanhijärvi]

Package: revelation
Version: 0.4.14-3
Severity: grave
Tags: ipv6

Hello

I am sorry that I report this so close to Buster release but I just noticeed
that in the Debian Buster release notes it is said that Revelation is removed
from the Buster. Release notes suggests that passwords can be exported from
Revelation and then imported to keepass2 password manager. Unfortunately that
is not an option if you are blind or other visually impaired user like I am.
Keepass2 password manager is not accessible with the Orca screen reader. So it
is not accessible if you are visually impaired. I am still using Debian
Stretch, but this problem most likeyly applies to Buster too. I have tried
every graphical password manager I can find in Debian Stretch and Revelation
isthe only graphical password managerwhich is accessible with the Orca screen
reader. None of the other graphical password managers are accessible with the
Orca screen reader. So Revelation is really the only accessible graphical
password manager for the visually impaired users.

So now if Revelation password manager is is not in Buster then suddenly
visually impaired users have no way to store their passwords and no way to
access passwords already stored in Revelation.

This is not ok, it is not ok to remove Revelation from Debian when there is no
other accessible password manger and no way to use keepass2 because it is not
accessible with Orca screen reader.

Please include Revelation in Buster.



-- System Information:
Debian Release: 9.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages revelation depends on:
ii  gconf2 3.2.6-4+b1
ii  gnome-extra-icons  1.1-3
ii  gnome-icon-theme   3.12.0-2
ii  python 2.7.13-2
ii  python-cracklib2.9.2-5
ii  python-crypto  2.6.1-7
ii  python-dbus1.2.4-1+b1
ii  python-gnome2  2.28.1+dfsg-1.2
ii  python-gobject 3.22.0-2
ii  python-gtk22.24.0-5.1
ii  shared-mime-info   1.8-1+deb9u1

revelation recommends no packages.

revelation suggests no packages.

-- no debconf information

Bug#931490: should not be removed from Buster (important for visually impaired users))

[Mika Hanhijärvi]

Package: revelation
Version: 0.4.14-3
Severity: grave
Tags: ipv6

Hello

I am sorry that I report this so close to Buster release but I just noticeed
that in the Debian Buster release notes it is said that Revelation is removed
from the Buster. Release notes suggests that passwords can be exported from
Revelation and then imported to keepass2 password manager. Unfortunately that
is not an option if you are blind or other visually impaired user like I am.
Keepass2 password manager is not accessible with the Orca screen reader. So it
is not accessible if you are visually impaired. I am still using Debian
Stretch, but this problem most likeyly applies to Buster too. I have tried
every graphical password manager I can find in Debian Stretch and Revelation
isthe only graphical password managerwhich is accessible with the Orca screen
reader. None of the other graphical password managers are accessible with the
Orca screen reader. So Revelation is really the only accessible graphical
password manager for the visually impaired users.

So now if Revelation password manager is is not in Buster then suddenly
visually impaired users have no way to store their passwords and no way to
access passwords already stored in Revelation.

This is not ok, it is not ok to remove Revelation from Debian when there is no
other accessible password manger and no way to use keepass2 because it is not
accessible with Orca screen reader.

Please include Revelation in Buster.



-- System Information:
Debian Release: 9.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages revelation depends on:
ii  gconf2 3.2.6-4+b1
ii  gnome-extra-icons  1.1-3
ii  gnome-icon-theme   3.12.0-2
ii  python 2.7.13-2
ii  python-cracklib2.9.2-5
ii  python-crypto  2.6.1-7
ii  python-dbus1.2.4-1+b1
ii  python-gnome2  2.28.1+dfsg-1.2
ii  python-gobject 3.22.0-2
ii  python-gtk22.24.0-5.1
ii  shared-mime-info   1.8-1+deb9u1

revelation recommends no packages.

revelation suggests no packages.

-- no debconf information

Bug#913978: (no subject)

[Mika Hanhijärvi]

Hi


This bug should still be fixed in Buster. If that is not possible then
it would be good if the old style gnome-control-center in Debian
Stretch's Gnome 3.22 could be ported to Buster. It really should be
available as an alternative as a e.g package
gnome-control-center-legacy. The old style gnome-control-center works
just fine with Orca in Stretch.


I really do not understand what are the Gnome developers thinking. They
really should not make changes like this without testing that the new
users interface is accessible with the Orca screen reader. Theyreally
should not release anything before testing it first.


The least that should be done is to provide the old style
gnome-control-center as an alternative.


If nothing else really can be done then those keystorkes should atleast
be documented. That is a really bad work around but ofcourse better than
nothing.


When fixed gnome-control-center will be available it really should be
backported to Buster.


I know this is not Debian's fault so do not understand me wrong.


I hope that you all will have a fun and warm summer :-)

Bug#913978: (no subject)

[Mika Hanhijärvi]

Hi


This bug should still be fixed in Buster. If that is not possible then
it would be good if the old style gnome-control-center in Debian
Stretch's Gnome 3.22 could be ported to Buster. It really should be
available as an alternative as a e.g package
gnome-control-center-legacy. The old style gnome-control-center works
just fine with Orca in Stretch.


I really do not understand what are the Gnome developers thinking. They
really should not make changes like this without testing that the new
users interface is accessible with the Orca screen reader. Theyreally
should not release anything before testing it first.


The least that should be done is to provide the old style
gnome-control-center as an alternative.


If nothing else really can be done then those keystorkes should atleast
be documented. That is a really bad work around but ofcourse better than
nothing.


When fixed gnome-control-center will be available it really should be
backported to Buster.


I know this is not Debian's fault so do not understand me wrong.


I hope that you all will have a fun and warm summer :-)

Bug#923203: (no subject)

[Mika Hanhijärvi]

Please note that there are many visually impaired users who must use the
Orca screen reader which speaks the content on screen. If pulseaudio
would not start automatically then for the blind user like me it would
be impossible to use the computer.

Bug#923203: (no subject)

[Mika Hanhijärvi]

Please note that there are many visually impaired users who must use the
Orca screen reader which speaks the content on screen. If pulseaudio
would not start automatically then for the blind user like me it would
be impossible to use the computer.

Re: [BRLTTY] skipping broken cells

[Mika Hanhijärvi]

On 5/14/19 11:51 AM, Mario Lang wrote:
> Devin Prater  writes:
>
>> Hi all. I have a Vario Ultra 20 with dots that don't work, in cells 6, 7,
>> and somewhere around 18 and 19. Is there a way in BRLTTY to have those
>> cells skipped, so that braille simply continues on the next uneffected
>> cell? Of course, this would have to be set up by the user, but I think this
>> could allow displays to hang on a little longer.
> As far as I remember, this topic has been brought up before, but the
> functionality hasn't been implemented yet.


Hi


I really hope that feature will be added to brltt.  It would be really
goog if brltty could skip broken cells.


___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Bug#721763: brltty grabs tty from CP2102/CP2109 device disconnecting default

[Mika Hanhijärvi]

Hello


This bug seems to still exist in Debian 9.8 "Stretch". I actually do not 
own any hardware using the cp210X kernel module, I am just forwarding 
this information here.



Output from lsusb command:


Bus 006 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
UART Bridge / myAVR mySmartUSB light
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Output from logs:

 Mar 31 07:23:57 debian kernel: [ 6221.612063] usb 6-2: new full-speed
USB device number 2 using uhci_hcd
Mar 31 07:23:57 debian kernel: [ 6221.791082] usb 6-2: New USB device
found, idVendor=10c4, idProduct=ea60
Mar 31 07:23:57 debian kernel: [ 6221.791086] usb 6-2: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Mar 31 07:23:57 debian kernel: [ 6221.791088] usb 6-2: Product: CP2102
USB to UART Bridge Controller
Mar 31 07:23:57 debian kernel: [ 6221.791090] usb 6-2: Manufacturer:
Silicon Labs
Mar 31 07:23:57 debian kernel: [ 6221.791092] usb 6-2: SerialNumber: 0001
Mar 31 07:23:57 debian mtp-probe: checking bus 6, device 2:
"/sys/devices/pci:00/:00:1d.0/usb6/6-2"
Mar 31 07:23:57 debian mtp-probe: bus: 6, device: 2 was not an MTP device
Mar 31 07:23:57 debian kernel: [ 6221.869563] usbcore: registered new
interface driver usbserial
Mar 31 07:23:57 debian kernel: [ 6221.869586] usbcore: registered new
interface driver usbserial_generic
Mar 31 07:23:57 debian kernel: [ 6221.869607] usbserial: USB Serial
support registered for generic
Mar 31 07:23:57 debian kernel: [ 6221.892149] usbcore: registered new
interface driver cp210x
Mar 31 07:23:57 debian kernel: [ 6221.892173] usbserial: USB Serial
support registered for cp210x
Mar 31 07:23:57 debian kernel: [ 6221.892225] cp210x 6-2:1.0: cp210x
converter detected
Mar 31 07:23:57 debian kernel: [ 6221.898200] usb 6-2: cp210x converter
now attached to ttyUSB0
Mar 31 07:24:01 debian brltty[430]: USB configuration set error 16:
Laite tai resurssi varattu.
Mar 31 07:24:01 debian brltty[430]: brltty: USB configuration set error
16: Laite tai resurssi varattu.
Mar 31 07:24:01 debian kernel: [ 6225.530058] usb 6-2: usbfs: interface
0 claimed by cp210x while 'brltty' sets config #1
Mar 31 07:24:01 debian brltty[430]: brltty: USB interface in use: 0 (cp210x)
Mar 31 07:24:01 debian brltty[430]: USB interface in use: 0 (cp210x)
Mar 31 07:24:01 debian kernel: [ 6225.532412] cp210x ttyUSB0: cp210x
converter now disconnected from ttyUSB0
Mar 31 07:24:01 debian kernel: [ 6225.532431] cp210x 6-2:1.0: device
disconnected
Mar 31 07:24:01 debian brltty[430]: Ignored Byte: 00
Mar 31 07:24:01 debian brltty[430]: brltty: Ignored Byte: 00
AFAIK the version of brltty in use is 5.4-7 which is the current brltty in 
Debian Stretch. Any idea if brltty 5.6 or later fixes this problem?

Thanks in advance.

Regards
Mika

Bug#913978: is not accessible with Orca screenreader

[Mika Hanhijärvi]

Hi


Thanks a lot. When this bug is fixed I hope it will be fixed also in 
Gnome 3.30, not just in Gnome 3.32 so that Debian Buster will also have 
the fix. It looks like Debian 10 "Buster" will be released with Gnome 
3.30, I ofcourse may be wrong. I am usin Debian stable releases on 
desktop and laptop so I will upgrade all my computers to Debian Buster 
when it is released sometime in the next summer. And after that the next 
time I will upgrade is when Debian 11 will be released sometime in 2021...



On 1/1/19 1:05 AM, Jeremy Bicha wrote:

Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/327

On Sat, Nov 17, 2018 at 4:03 PM Mika Hanhijärvi  wrote:

This is wery severe unacceptable problem. This bug makes Gnome 3.30 unusable
for the visually impaired users because you can not access or change the
desktop settings.

Thank you for taking the time to report this bug.

I agree that the GNOME Settings app has many accessible problems for
navigating with only a keyboard and screen reader.

I opened a bug now for the most critical issue. When that's fixed, you
should be able to navigate most of the Settings app, although there
are some elements that are not read and the context may be unclear.

Thanks,
Jeremy Bicha

Bug#913978: is not accessible with Orca screenreader

[Mika Hanhijärvi]

Hi


Thanks a lot. When this bug is fixed I hope it will be fixed also in 
Gnome 3.30, not just in Gnome 3.32 so that Debian Buster will also have 
the fix. It looks like Debian 10 "Buster" will be released with Gnome 
3.30, I ofcourse may be wrong. I am usin Debian stable releases on 
desktop and laptop so I will upgrade all my computers to Debian Buster 
when it is released sometime in the next summer. And after that the next 
time I will upgrade is when Debian 11 will be released sometime in 2021...



On 1/1/19 1:05 AM, Jeremy Bicha wrote:

Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/327

On Sat, Nov 17, 2018 at 4:03 PM Mika Hanhijärvi  wrote:

This is wery severe unacceptable problem. This bug makes Gnome 3.30 unusable
for the visually impaired users because you can not access or change the
desktop settings.

Thank you for taking the time to report this bug.

I agree that the GNOME Settings app has many accessible problems for
navigating with only a keyboard and screen reader.

I opened a bug now for the most critical issue. When that's fixed, you
should be able to navigate most of the Settings app, although there
are some elements that are not read and the context may be unclear.

Thanks,
Jeremy Bicha

Bug#913978: is not accessible with Orca screenreader

[Mika Hanhijärvi]

Package: gnome-control-center
Version: 1:3.30.2-1
Severity: grave
Tags: a11y


Hello

I installed Debian Buster on virtual machine awhile ago. I wanted to try Buster
on virtual machine before upgrading my computers which are currently running
Debian Stretch. I am blind so I have to use screen reader which speaks the
content on screen. As a blind user I also can not use mouse so I use computer
from keyboard only without using mouse.

Gnome 3.30 desktop's new style settings window in Debian Buster is currently
completely unusable with the Orca screen reader. It is completely impossible to
access Gnome desktop settings using Orca screen reader. I can open the settings
window but the content of the window is completely inaccessible.

This is wery severe unacceptable problem. This bug makes Gnome 3.30 unusable
for the visually impaired users because you can not access or change the
desktop settings.

Here is how to reproduce this problem:

1) Make sure Orca screen reader is installed and running
2) Open Gnome desktop settings window
3) Try to navigate settings from keyboard using the arrow, tab etc keys.

Expected result should be that Orca should speak the content on screen and you
should be able to navigate and change settings from keyboard without any need
to use mouse. But it does not work as expected and settings window is not
accessiblwhich makes the settings window
completely unusable.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.45-1
ii  apg2.2.3.dfsg.1-5
ii  colord 1.4.3-3+b1
ii  desktop-file-utils 0.23-4
ii  gnome-control-center-data  1:3.30.2-1
ii  gnome-desktop3-data3.30.2-1
ii  gnome-settings-daemon  3.30.1.2-1
ii  gsettings-desktop-schemas  3.28.1-1
ii  libaccountsservice00.6.45-1
ii  libatk1.0-02.30.0-1
ii  libc6  2.27-8
ii  libcairo-gobject2  1.16.0-1
ii  libcairo2  1.16.0-1
ii  libcanberra-gtk3-0 0.30-6
ii  libcanberra0   0.30-6
ii  libcheese-gtk253.30.0-1
ii  libcheese8 3.30.0-1
ii  libclutter-1.0-0   1.26.2+dfsg-7
ii  libclutter-gtk-1.0-0   1.8.4-3
ii  libcolord-gtk1 0.1.26-2
ii  libcolord2 1.4.3-3+b1
ii  libcups2   2.2.8-5
ii  libfontconfig1 2.13.1-2
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii  libglib2.0-0   2.58.1-2
ii  libgnome-bluetooth13   3.28.2-2
ii  libgnome-desktop-3-17  3.30.2-1
ii  libgoa-1.0-0b  3.30.0-1
ii  libgoa-backend-1.0-1   3.30.0-1
ii  libgrilo-0.3-0 0.3.6-1
ii  libgtk-3-0 3.24.1-2
ii  libgtop-2.0-11 2.38.0-2
ii  libgudev-1.0-0 232-2
ii  libibus-1.0-5  1.5.19-1
ii  libkrb5-3  1.16.1-1
ii  libmm-glib01.8.2-1
ii  libnm0 1.14.4-3
ii  libnma01.8.18-2
ii  libpango-1.0-0 1.42.4-3
ii  libpangocairo-1.0-01.42.4-3
ii  libpolkit-gobject-1-0  0.105-21
ii  libpulse-mainloop-glib012.2-2
ii  libpulse0  12.2-2
ii  libpwquality1  1.4.0-2
ii  libsecret-1-0  0.18.6-3
ii  libsmbclient   2:4.9.1+dfsg-2
ii  libsoup2.4-1   2.64.1-3
ii  libupower-glib30.99.9-1
ii  libwacom2  0.31-1
ii  libwayland-server0 1.16.0-1
ii  libx11-6   2:1.6.7-1
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-7+b2

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-5.2+b1
ii  cups-pk-helper0.2.6-1+b1
ii  gkbd-capplet  3.26.0-3
ii  gnome-online-accounts 3.30.0-1
ii  gnome-user-docs   3.30.1-1
ii  gnome-user-share  3.28.0-1
ii  iso-codes 4.1-1
ii  libcanberra-pulse 0.30-6
ii  libnss-myhostname 239-11
ii  mousetweaks   3.12.0-4
ii  network-manager-gnome 1.8.18-2
ii  policykit-1   0.105-21
ii  pulseaudio-module-bluetooth   12.2-2
ii  realmd0.16.3-2
ii  rygel 0.36.2-1
ii  rygel-tracker 0.36.2-1
ii  system-config-printer-common  1.5.11-3

Versions of packages gnome-control-center suggests:
ii  gnome-software   3.30.1-1
ii  gstreamer1.0-pulseaudio  1.14.4-1
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module 

Bug#913978: is not accessible with Orca screenreader

[Mika Hanhijärvi]

Package: gnome-control-center
Version: 1:3.30.2-1
Severity: grave
Tags: a11y


Hello

I installed Debian Buster on virtual machine awhile ago. I wanted to try Buster
on virtual machine before upgrading my computers which are currently running
Debian Stretch. I am blind so I have to use screen reader which speaks the
content on screen. As a blind user I also can not use mouse so I use computer
from keyboard only without using mouse.

Gnome 3.30 desktop's new style settings window in Debian Buster is currently
completely unusable with the Orca screen reader. It is completely impossible to
access Gnome desktop settings using Orca screen reader. I can open the settings
window but the content of the window is completely inaccessible.

This is wery severe unacceptable problem. This bug makes Gnome 3.30 unusable
for the visually impaired users because you can not access or change the
desktop settings.

Here is how to reproduce this problem:

1) Make sure Orca screen reader is installed and running
2) Open Gnome desktop settings window
3) Try to navigate settings from keyboard using the arrow, tab etc keys.

Expected result should be that Orca should speak the content on screen and you
should be able to navigate and change settings from keyboard without any need
to use mouse. But it does not work as expected and settings window is not
accessiblwhich makes the settings window
completely unusable.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.45-1
ii  apg2.2.3.dfsg.1-5
ii  colord 1.4.3-3+b1
ii  desktop-file-utils 0.23-4
ii  gnome-control-center-data  1:3.30.2-1
ii  gnome-desktop3-data3.30.2-1
ii  gnome-settings-daemon  3.30.1.2-1
ii  gsettings-desktop-schemas  3.28.1-1
ii  libaccountsservice00.6.45-1
ii  libatk1.0-02.30.0-1
ii  libc6  2.27-8
ii  libcairo-gobject2  1.16.0-1
ii  libcairo2  1.16.0-1
ii  libcanberra-gtk3-0 0.30-6
ii  libcanberra0   0.30-6
ii  libcheese-gtk253.30.0-1
ii  libcheese8 3.30.0-1
ii  libclutter-1.0-0   1.26.2+dfsg-7
ii  libclutter-gtk-1.0-0   1.8.4-3
ii  libcolord-gtk1 0.1.26-2
ii  libcolord2 1.4.3-3+b1
ii  libcups2   2.2.8-5
ii  libfontconfig1 2.13.1-2
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii  libglib2.0-0   2.58.1-2
ii  libgnome-bluetooth13   3.28.2-2
ii  libgnome-desktop-3-17  3.30.2-1
ii  libgoa-1.0-0b  3.30.0-1
ii  libgoa-backend-1.0-1   3.30.0-1
ii  libgrilo-0.3-0 0.3.6-1
ii  libgtk-3-0 3.24.1-2
ii  libgtop-2.0-11 2.38.0-2
ii  libgudev-1.0-0 232-2
ii  libibus-1.0-5  1.5.19-1
ii  libkrb5-3  1.16.1-1
ii  libmm-glib01.8.2-1
ii  libnm0 1.14.4-3
ii  libnma01.8.18-2
ii  libpango-1.0-0 1.42.4-3
ii  libpangocairo-1.0-01.42.4-3
ii  libpolkit-gobject-1-0  0.105-21
ii  libpulse-mainloop-glib012.2-2
ii  libpulse0  12.2-2
ii  libpwquality1  1.4.0-2
ii  libsecret-1-0  0.18.6-3
ii  libsmbclient   2:4.9.1+dfsg-2
ii  libsoup2.4-1   2.64.1-3
ii  libupower-glib30.99.9-1
ii  libwacom2  0.31-1
ii  libwayland-server0 1.16.0-1
ii  libx11-6   2:1.6.7-1
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-7+b2

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-5.2+b1
ii  cups-pk-helper0.2.6-1+b1
ii  gkbd-capplet  3.26.0-3
ii  gnome-online-accounts 3.30.0-1
ii  gnome-user-docs   3.30.1-1
ii  gnome-user-share  3.28.0-1
ii  iso-codes 4.1-1
ii  libcanberra-pulse 0.30-6
ii  libnss-myhostname 239-11
ii  mousetweaks   3.12.0-4
ii  network-manager-gnome 1.8.18-2
ii  policykit-1   0.105-21
ii  pulseaudio-module-bluetooth   12.2-2
ii  realmd0.16.3-2
ii  rygel 0.36.2-1
ii  rygel-tracker 0.36.2-1
ii  system-config-printer-common  1.5.11-3

Versions of packages gnome-control-center suggests:
ii  gnome-software   3.30.1-1
ii  gstreamer1.0-pulseaudio  1.14.4-1
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module 

Orca 3.30

[Mika Hanhijärvi]

Hi


I am a blind user and I am using Debian Stretch. I just upgraded the 
Orca screen reader to version 3.30 available in the Stretch backports. I 
noticed that after upgrading the Orca screen reader the Gnome desktop 
Applications menu does not work with Orca anymore. Orca speaks nothing 
when I try to access the Applications menu at the Gnome desktop top 
panel. This problem exists on all of my computers running Debian Stretch.


The problem disappears if I downgrade the Orca to the version 3.22 
available in the Stretch main repository. The problem also did not exist 
when I was using Orca 3.28 installed from the Stretch backports. If I 
re-upgrade to Orca 3.30 then the problem does exist again. So it seems 
to me there is something wrong in the Orca 3.30.



Here is how to reproduce this problem:

1) Make sure that Orca screen reader version 3.30 is installed and running


2) Make sure Orca speaks if you e.g press some key from the keyboard or 
do something else like that.



3) Make sure you have enabled the Applications -menu in the Gnome Tweaktool

- Start Gnome Tweak tool

- Select "Extensions" from the settings page list

- activate the "Applications Menu" extension.


4) Go to Applications -menu which is now located in the Gnome desktop 
top panel.



5) Use keyboard arrow keys to navigate the Applications menu.



I am using Stretch on all of my computers and I have not upgraded to 
testing yet. So I can not confirm this, but  awhile ago there was some 
possibly related discussion at the Finnish mailing list for the visually 
impaired people. Someone said that Orca 3.30 does not speak when you are 
trying to access Gnome desktop settings under Debian unstable. I really 
can not confirm that and I do not know if that problem is has something 
to do with the problem I am reporting now.




It is possible that Orca 3.30 iscausing other problems, not just 
problems with the Applications menu, I have not had enough time to check 
that out.



It would be really important for the visually impaired users if this 
problem could be checked and solved, even more so if that is is really 
causing problems in Debian unstable or testing as mentioned abowe etc.



Thanks in advance.


Regards

Mika

Re: [BRLTTY] Brltty and Super key etc

[Mika Hanhijärvi]

Ok thanks . That explains why I have not found any way to use Super key.


- Mika







On 20/10/17 18:48, Samuel Thibault wrote:
> Hello,
>
> Mika Hanhijärvi, on ven. 20 oct. 2017 18:41:23 +0300, wrote:
>> 6) Fn key
> I can speak for this one: it's not possible, because it is a key which
> is handled by the BIOS of the PC itself, software does not see it. So it
> can't be synthesized.
>
> Others should be possible to synthesize.
>
> Samuel

___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty

[BRLTTY] Brltty and Super key etc

[Mika Hanhijärvi]

Hi

Could someone please tell me if it is possible to use Super key (also
known as Windows key) from integrated braille keyboard in braille
display? If itt is possible then could you please tell me how can I us
it. I am using Linux (Debian 9.0 "Stretch") and my braille display is
Freedom Scientific Focus 40 Blue.

I know how to use keyboard shortcuts like ctrl + a and alt + f, but is
it possible to use keyboard shortcuts like Super + a ?

I am asking this because on Gnome desktop Super key is used in many
keyboard shortcuts. Super key is really needed if you want to control
Gnome desktop using braille display.

If there is no way to use the Supe key on linux and brltty then I really
hope that brltty developers will add that feature.


Also is it possible to emulate these key presses:


1( f6 and f10

2) shift + f10

3) ctrl + f10

4) Super + f10

5) Menu key

6) Fn key


- Mika

___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty

Bug#864670: closed by Samuel Thibault <sthiba...@debian.org> (Bug#864670: fixed in brltty 5.5-2)

[Mika Hanhijärvi]

Thank you wery much :-) It would be great if tis new version would be
available for the Stretch too in the backports repository.

Bug#864670: closed by Samuel Thibault <sthiba...@debian.org> (Bug#864670: fixed in brltty 5.5-2)

[Mika Hanhijärvi]

Thank you wery much :-) It would be great if tis new version would be
available for the Stretch too in the backports repository.

Bug#864987: firefox-esr: does not work with ALSA but blind many users use ALSA

[Mika Hanhijärvi]

Package: firefox-esr
Version: 52.2.0esr-1~deb9u1
Severity: important

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?

*** End of the template - remove these template lines ***
It seems that the Firefox 452 does not work with ALSA anymore. The problem i
with that is that lots of blind and other visually impaired users use ALSA
instead of Pulseaudio. Currently if you want to use both Orca screen reader on
desktop and espeakup on console then it is best to use ALSA instead of
Pulseaudio because Pulseaudio causes problems if you want to use both Orca and
espeakup. Firefox is currrently the only modern web browser on Linux which
works with Orca. Now that Mozilla has dropped support for the ALSA there is not
a single browser which is really usable if you are blind and especially if you
use ALSA instead of Pulseaudio.

I know this is not Debians fault, this is fully Mozillas fault.

I hope that Debian would make the Firefox-estr 45 available easily atleast for
now. Firefox esr 45.9  Worked just fine. I am blind myself and I was thinking
of switching from pulseaudio to alsa because I would like to use both Orca and
espeakup. But now when there is firefox esr 52 in Debian Stretch I am not sure
what should I do. I will probably downgrade Firefox esr to 45.9 using the
Debian snapshots repository. I know how to use snapshots but there is lots of
blind users who do not even know snapshots repository exists.

I know that using old browser may causesevere security risks, but obviously
there is not much option...

Firefo esr also 52.20 currently in Debian Stretch also does not really work as
well with Orca screen reader as Firefox ESR 45.9 did. That is another reason
why I am going to downgrade the browser. I will make another bug report about
that.

This bug report really should be forwarded to Mox
zilla too so that they know what they are doing to blind users...



-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: /usr/share/xul-ext/adblock-plus
Package: xul-ext-adblock-plus
Status: enabled

Name: Application Update Service Helper
Location: ${PROFILE_EXTENSIONS}/aushel...@mozilla.org.xpi
Status: enabled

Name: Default theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: Web Compat
Location: ${PROFILE_EXTENSIONS}/webcom...@mozilla.org.xpi
Status: enabled

-- Plugins information
Name: GNOME Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled

Name: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3.1))
Location: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-8-plugin:amd64
Status: enabled

Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: enabled


-- Addons package information
ii  firefox-esr52.2.0esr-1~ amd64Mozilla Firefox web browser - Ext
ii  gnome-shell3.22.3-3 amd64graphical shell for the GNOME des
ii  icedtea-8-plug 1.6.2-3.1amd64web browser plugin based on OpenJ
ii  rhythmbox-plug 3.4.1-2+b1   amd64plugins for rhythmbox music playe
ii  xul-ext-adbloc 2.7.3+dfsg-1 all  advertisement blocking extension 

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libasound21.1.3-5
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.18-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libgtk2.0-0   2.24.31-2
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-0 

Bug#864837: screenreader stops speaking

[Mika Hanhijärvi]

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Hi

I am sorry that I repport this so close to release of Stretch.

I am not really sure to which package I should report this bug. I am not sure
if this bug is in Orca, Pulseaudio, speech-dispatcher or someething else. I
think it might be problem with Pulseaudio, or maybe not. Really do not know.

Note that I tryed to send this bug report earlier but my laptop did run out of
battery when reportbug was sending the bug report so bug report probably was
not sent. I first tryed to send itthe bug report to pulseaudio, but I am now
thinking that maybe I should reportit o Orca so that Debian accessibility guys
get notified about this. I am really sorry if thiscauses mess and a duplicate
bug report to two packages.

I am blind so I have to use computer using the screen reader. So it is
important for me that screen reader works relealibly.

I have espeakup and Orca installed. I would like to use espeakup on console and
Orca on desktop. I also would like to be able to switch between text mode
console and graphical nome desktop without logging out from the desktop.
Currently that does not work. I have two laptops and both have this problem.
Note that I have not made clean Stretch installation, Ihave upgraded my systems
to Stretch.


For some reason if espeakup sppeaks something when the computer is booting then
screen reader does not speak anytging on GDM login screen. If that happens then
screen reader also does not speak at all on desktop. This makes it impossible
for me to login to desktop or use the deshtop. I have noticed that if I go to
text console then eseakup speaks just fin.

If espeakup does not speak anytging then screen reader speaks on GDM login
screen. If I go to text console then espeakup does not speak at all. If I login
to desktop then Orca screen reader speaks just fine. If I login to desktop then
this also happens: If I switch from desktop to GDM login screen thusing the
ctrl + alt + f1 then screen reader does not speak on GDM login screen at all.
If I then return to desktop then Orca screen reader on desktop speaks again
just fine. If I switch form desktop to text console using e.g ctrl + alt + f3
then espeakup does not speak at all on console. If I then switch back to
desktothen Orca speaks again on desktop just fine.


If I logout from desktop to gdm login screen then screen reader speaks on gdm
login screen.

So it seems that the sc reader works just on one of the following views:
console, gdm or desktop. It is not possible to switch between those. That is
not good.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python33.5.3-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#864837: screenreader stops speaking

[Mika Hanhijärvi]

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Hi

I am sorry that I repport this so close to release of Stretch.

I am not really sure to which package I should report this bug. I am not sure
if this bug is in Orca, Pulseaudio, speech-dispatcher or someething else. I
think it might be problem with Pulseaudio, or maybe not. Really do not know.

Note that I tryed to send this bug report earlier but my laptop did run out of
battery when reportbug was sending the bug report so bug report probably was
not sent. I first tryed to send itthe bug report to pulseaudio, but I am now
thinking that maybe I should reportit o Orca so that Debian accessibility guys
get notified about this. I am really sorry if thiscauses mess and a duplicate
bug report to two packages.

I am blind so I have to use computer using the screen reader. So it is
important for me that screen reader works relealibly.

I have espeakup and Orca installed. I would like to use espeakup on console and
Orca on desktop. I also would like to be able to switch between text mode
console and graphical nome desktop without logging out from the desktop.
Currently that does not work. I have two laptops and both have this problem.
Note that I have not made clean Stretch installation, Ihave upgraded my systems
to Stretch.


For some reason if espeakup sppeaks something when the computer is booting then
screen reader does not speak anytging on GDM login screen. If that happens then
screen reader also does not speak at all on desktop. This makes it impossible
for me to login to desktop or use the deshtop. I have noticed that if I go to
text console then eseakup speaks just fin.

If espeakup does not speak anytging then screen reader speaks on GDM login
screen. If I go to text console then espeakup does not speak at all. If I login
to desktop then Orca screen reader speaks just fine. If I login to desktop then
this also happens: If I switch from desktop to GDM login screen thusing the
ctrl + alt + f1 then screen reader does not speak on GDM login screen at all.
If I then return to desktop then Orca screen reader on desktop speaks again
just fine. If I switch form desktop to text console using e.g ctrl + alt + f3
then espeakup does not speak at all on console. If I then switch back to
desktothen Orca speaks again on desktop just fine.


If I logout from desktop to gdm login screen then screen reader speaks on gdm
login screen.

So it seems that the sc reader works just on one of the following views:
console, gdm or desktop. It is not possible to switch between those. That is
not good.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python33.5.3-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#864837: screenreader stops speaking

[Mika Hanhijärvi]

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Hi

I am sorry that I repport this so close to release of Stretch.

I am not really sure to which package I should report this bug. I am not sure
if this bug is in Orca, Pulseaudio, speech-dispatcher or someething else. I
think it might be problem with Pulseaudio, or maybe not. Really do not know.

Note that I tryed to send this bug report earlier but my laptop did run out of
battery when reportbug was sending the bug report so bug report probably was
not sent. I first tryed to send itthe bug report to pulseaudio, but I am now
thinking that maybe I should reportit o Orca so that Debian accessibility guys
get notified about this. I am really sorry if thiscauses mess and a duplicate
bug report to two packages.

I am blind so I have to use computer using the screen reader. So it is
important for me that screen reader works relealibly.

I have espeakup and Orca installed. I would like to use espeakup on console and
Orca on desktop. I also would like to be able to switch between text mode
console and graphical nome desktop without logging out from the desktop.
Currently that does not work. I have two laptops and both have this problem.
Note that I have not made clean Stretch installation, Ihave upgraded my systems
to Stretch.


For some reason if espeakup sppeaks something when the computer is booting then
screen reader does not speak anytging on GDM login screen. If that happens then
screen reader also does not speak at all on desktop. This makes it impossible
for me to login to desktop or use the deshtop. I have noticed that if I go to
text console then eseakup speaks just fin.

If espeakup does not speak anytging then screen reader speaks on GDM login
screen. If I go to text console then espeakup does not speak at all. If I login
to desktop then Orca screen reader speaks just fine. If I login to desktop then
this also happens: If I switch from desktop to GDM login screen thusing the
ctrl + alt + f1 then screen reader does not speak on GDM login screen at all.
If I then return to desktop then Orca screen reader on desktop speaks again
just fine. If I switch form desktop to text console using e.g ctrl + alt + f3
then espeakup does not speak at all on console. If I then switch back to
desktothen Orca speaks again on desktop just fine.


If I logout from desktop to gdm login screen then screen reader speaks on gdm
login screen.

So it seems that the sc reader works just on one of the following views:
console, gdm or desktop. It is not possible to switch between those. That is
not good.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python33.5.3-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#864829: screen reader stops speaking

[Mika Hanhijärvi]

Package: pulseaudio
Version: 10.0-1
Severity: grave

Hi

I am sorry that I repport this so close to release of Stretch.

I am not really sure to which package I should report this bug. I am not 100%
sure if this g is in Pulseaudio, speech-eispatcher or someething else. I think
it might be a problem with Pulseaudio.

I am blind so I have to use computer using the screen reader. So it is
important for me that screen reader works relealibly.

I am using the Gnome desktop.
I have espeakup and Orca installed. I would like to use espeakup on console and
Orca on desktop. I also would like to be able to switch between text mode
console and graphical nome desktop without logging out from the desktop.
Currently that does not work. I have two laptops and both have this problem.
Note that I have not made clean Stretch installation, Ihave upgraded my systems
to Stretch.


For some reason if espeakup sppeaks something when the computer is booting then
screen reader does not speak anytging on GDM login screen. If that happens then
screen reader also does not speak at all on desktop. This makes it impossible
for me to login to desktop or use the deshtop. I have noticed that if I go to
text console then eseakup speaks just fin.

If espeakup does not speak anytging then screen reader speaks on GDM login
screen. If I go to text console then espeakup does not speak at all. If I login
to desktop then Orca screen reader speaks just fine. If I login to desktop then
this also happens: If I switch from desktop to GDM login screen thusing the
ctrl + alt + f1 then screen reader does not speak on GDM login screen at all.
If I then return to desktop then Orca screen reader on desktop speaks again
just fine. If I switch form desktop to text console using e.g ctrl + alt + f3
then espeakup does not speak at all on console. If I then switch back to
desktothen Orca speaks again on desktop just fine.


If I logout from desktop to gdm login screen then screen reader speaks on gdm
login screen.

So it seems that the sc reader works just on one of the following views:
console, gdm or desktop. It is not possible to switch between those. That is
not good.

I dreally hope this will be fixed vecause this bug makes it impossible to
switch between desktop, gdm and console if you can not see and have to rely on
screen reader.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.18-1
ii  libgcc1  1:6.3.0-18
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18
ii  libsystemd0  232-25
ii  libtdb1  1.3.11-2
ii  libudev1 232-25
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+b1

Versions of packages pulseaudio suggests:
ii  paman0.9.4-1+b3
ii  paprefs  0.9.10-2+b1
ii  pavucontrol  3.0-3.1
ii  pavumeter0.9.3-4+b3
ii  udev 232-25

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use 

Bug#864829: screen reader stops speaking

[Mika Hanhijärvi]

Package: pulseaudio
Version: 10.0-1
Severity: grave

Hi

I am sorry that I repport this so close to release of Stretch.

I am not really sure to which package I should report this bug. I am not 100%
sure if this g is in Pulseaudio, speech-eispatcher or someething else. I think
it might be a problem with Pulseaudio.

I am blind so I have to use computer using the screen reader. So it is
important for me that screen reader works relealibly.

I am using the Gnome desktop.
I have espeakup and Orca installed. I would like to use espeakup on console and
Orca on desktop. I also would like to be able to switch between text mode
console and graphical nome desktop without logging out from the desktop.
Currently that does not work. I have two laptops and both have this problem.
Note that I have not made clean Stretch installation, Ihave upgraded my systems
to Stretch.


For some reason if espeakup sppeaks something when the computer is booting then
screen reader does not speak anytging on GDM login screen. If that happens then
screen reader also does not speak at all on desktop. This makes it impossible
for me to login to desktop or use the deshtop. I have noticed that if I go to
text console then eseakup speaks just fin.

If espeakup does not speak anytging then screen reader speaks on GDM login
screen. If I go to text console then espeakup does not speak at all. If I login
to desktop then Orca screen reader speaks just fine. If I login to desktop then
this also happens: If I switch from desktop to GDM login screen thusing the
ctrl + alt + f1 then screen reader does not speak on GDM login screen at all.
If I then return to desktop then Orca screen reader on desktop speaks again
just fine. If I switch form desktop to text console using e.g ctrl + alt + f3
then espeakup does not speak at all on console. If I then switch back to
desktothen Orca speaks again on desktop just fine.


If I logout from desktop to gdm login screen then screen reader speaks on gdm
login screen.

So it seems that the sc reader works just on one of the following views:
console, gdm or desktop. It is not possible to switch between those. That is
not good.

I dreally hope this will be fixed vecause this bug makes it impossible to
switch between desktop, gdm and console if you can not see and have to rely on
screen reader.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.18-1
ii  libgcc1  1:6.3.0-18
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18
ii  libsystemd0  232-25
ii  libtdb1  1.3.11-2
ii  libudev1 232-25
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+b1

Versions of packages pulseaudio suggests:
ii  paman0.9.4-1+b3
ii  paprefs  0.9.10-2+b1
ii  pavucontrol  3.0-3.1
ii  pavumeter0.9.3-4+b3
ii  udev 232-25

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use 

Bug#864670: has broken Finnish braille table

[Mika Hanhijärvi]

Package: brltty
Version: 5.4-7
Severity: grave

I did get a new braille display awhile ago. I have been testing it and I have
noticed that braille table for the Finnish  language is broken. Reading text
works but It is impossible to write text in Finnish using the integrated
braille keyboard in the braille display. Writing text in Finnish language is
not possible because writing scandinavian letters (which are wery commonly used
in Finnish language) does not work. The following scandinavian letters are used
in Finnish language. Small letters: ä, ö, å. Capital letters: Ä, Ö, Å.

It seems that the braille table for the Finnish language has many lines which
define some weird control characters. Those lines conflict with lines defining
scandinavian letters . If I remove those conflicting control character lines
then both reading and writing text in Finnish works correctly.

I am a blind user from Finland so it is wery important for me that writing text
in Finnish works. My native language is Finnish so I am really using braille in
Finnish.

The braille table for the Finnish language is in the file:
/etc/brltty/Text/fi.ttb

First of all these lines define scandinavian letters used in the Finnish
language. These lines are correct and SHOULD NOT be changed:

char \xC4   (  345 7 )  # C4 ⡜ Ä [LATIN CAPITAL LETTER A WITH DIAERESIS]
char \xC5   (167 )  # C5 ⡡ Å [LATIN CAPITAL LETTER A WITH RING ABOVE]
char \xD6   ( 2 4 67 )  # D6 ⡪ Ö [LATIN CAPITAL LETTER O WITH DIAERESIS]
char \xE4   (  345   )  # E4 ⠜ ä [LATIN SMALL LETTER A WITH DIAERESIS]
char \xE5   (16  )  # E5 ⠡ å [LATIN SMALL LETTER A WITH RING ABOVE]
char \xF6   ( 2 4 6  )  # F6 ⠪ ö [LATIN SMALL LETTER O WITH DIAERESIS]


The problem described in this bug report is caused by the following lines.

This line is defined incorrectly and conflicts with the small letter "ä" ("ä"
in Finnish braille is dots: 3, 4, 5) :

char \x84   (  345   )  # 84 ⠜   []


- This line conflicts with the small letter "Å" ("å" in Finnish braille is
dots: 1, 6) :

char \x86   (16  )  # 86 ⠡   [START OF SELECTED AREA]


- This line conflicts with the capital letter "Ä" ("Ä" in Finnish braille is
dots: 3, 4, 5, 7) :

char \x8E   (  345 7 )  # 8E ⡜   [SINGLE SHIFT TWO]


- This line conflicts with the capital letter "Å" ("Å" in Finnish braille is
dots: 1,6,7) :

char \x8F   (167 )  # 8F ⡡   [SINGLE SHIFT THREE]


- This line conflicts with the small letter "ö" ("ö" in Finnish braille is
dots: 2, 4, 6) :

char \x94   ( 2 4 6  )  # 94 ⠪   [CANCEL CHARACTER]


- This line conflicts with the capital letter "Ö" ("Ö" in Finnish braille is
dots: 2, 4, 6, 7) :

char \x99   ( 2 4 67 )  # 99 ⡪   []


I really do not know for what and how those control characters are used, all I
know is that if those control character lines are not commented out then
writing text in the Finnish language is not possible. Those control character
lines should be commented out, removed or changed so that those do not conflict
with any other line.

I have compared the Finnish braille table with Swedish braille table because
Swedish is the second official language in finland. It seems that the Swedish
braille table does not define those control characters.

The braille table for the Swedish language is in the file:
/etc/brltty/Text/sv-1996.ttb

How to reproduce this bug:

1) select the Finnish language in the file:
/etc/brltty.conf

Uncomment this line:

text-table  fi  # Finnish

2) Restart brltty
3) connect Braille display which has integrated Braille keyboard
4) start e.g text editor
5) Try to write these scandinavian letters using the integrated Braille
keyboard in the Braille display:

- small letter ä )braille dots: 3, 4, 5)
- small letter ö (braille dots: 2, 4, 6)
- small letter å (braille dots: 1, 6)
- capital letter Ä (braille dots: 3, 4, 5, 7)
- capital letter Ö (braille dots: 2, 4, 6, 7)
- capital letter Å (braille dots: 1, 6, 7)



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages brltty depends on:
ii  init-system-helpers1.48
ii  libasound2 1.1.3-5
ii  libbluetooth3  5.43-2
ii  libbrlapi0.6   5.4-7
ii  libc6  2.24-11
ii  libglib2.0-0   2.50.3-2
ii  libgpm21.20.4-6.2+b1
ii  libicu57   57.1-6
ii  libncursesw5   6.0+20161126-1
ii  libpolkit-gobject-1-0  0.105-18
ii  libsystemd0232-25
ii  libtinfo5  6.0+20161126-1
ii  lsb-base   9.20161125
ii  policykit-10.105-18

Versions of packages brltty recommends:
ii  python  2.7.13-2

Versions of packages brltty 

Bug#864670: has broken Finnish braille table

[Mika Hanhijärvi]

Package: brltty
Version: 5.4-7
Severity: grave

I did get a new braille display awhile ago. I have been testing it and I have
noticed that braille table for the Finnish  language is broken. Reading text
works but It is impossible to write text in Finnish using the integrated
braille keyboard in the braille display. Writing text in Finnish language is
not possible because writing scandinavian letters (which are wery commonly used
in Finnish language) does not work. The following scandinavian letters are used
in Finnish language. Small letters: ä, ö, å. Capital letters: Ä, Ö, Å.

It seems that the braille table for the Finnish language has many lines which
define some weird control characters. Those lines conflict with lines defining
scandinavian letters . If I remove those conflicting control character lines
then both reading and writing text in Finnish works correctly.

I am a blind user from Finland so it is wery important for me that writing text
in Finnish works. My native language is Finnish so I am really using braille in
Finnish.

The braille table for the Finnish language is in the file:
/etc/brltty/Text/fi.ttb

First of all these lines define scandinavian letters used in the Finnish
language. These lines are correct and SHOULD NOT be changed:

char \xC4   (  345 7 )  # C4 ⡜ Ä [LATIN CAPITAL LETTER A WITH DIAERESIS]
char \xC5   (167 )  # C5 ⡡ Å [LATIN CAPITAL LETTER A WITH RING ABOVE]
char \xD6   ( 2 4 67 )  # D6 ⡪ Ö [LATIN CAPITAL LETTER O WITH DIAERESIS]
char \xE4   (  345   )  # E4 ⠜ ä [LATIN SMALL LETTER A WITH DIAERESIS]
char \xE5   (16  )  # E5 ⠡ å [LATIN SMALL LETTER A WITH RING ABOVE]
char \xF6   ( 2 4 6  )  # F6 ⠪ ö [LATIN SMALL LETTER O WITH DIAERESIS]


The problem described in this bug report is caused by the following lines.

This line is defined incorrectly and conflicts with the small letter "ä" ("ä"
in Finnish braille is dots: 3, 4, 5) :

char \x84   (  345   )  # 84 ⠜   []


- This line conflicts with the small letter "Å" ("å" in Finnish braille is
dots: 1, 6) :

char \x86   (16  )  # 86 ⠡   [START OF SELECTED AREA]


- This line conflicts with the capital letter "Ä" ("Ä" in Finnish braille is
dots: 3, 4, 5, 7) :

char \x8E   (  345 7 )  # 8E ⡜   [SINGLE SHIFT TWO]


- This line conflicts with the capital letter "Å" ("Å" in Finnish braille is
dots: 1,6,7) :

char \x8F   (167 )  # 8F ⡡   [SINGLE SHIFT THREE]


- This line conflicts with the small letter "ö" ("ö" in Finnish braille is
dots: 2, 4, 6) :

char \x94   ( 2 4 6  )  # 94 ⠪   [CANCEL CHARACTER]


- This line conflicts with the capital letter "Ö" ("Ö" in Finnish braille is
dots: 2, 4, 6, 7) :

char \x99   ( 2 4 67 )  # 99 ⡪   []


I really do not know for what and how those control characters are used, all I
know is that if those control character lines are not commented out then
writing text in the Finnish language is not possible. Those control character
lines should be commented out, removed or changed so that those do not conflict
with any other line.

I have compared the Finnish braille table with Swedish braille table because
Swedish is the second official language in finland. It seems that the Swedish
braille table does not define those control characters.

The braille table for the Swedish language is in the file:
/etc/brltty/Text/sv-1996.ttb

How to reproduce this bug:

1) select the Finnish language in the file:
/etc/brltty.conf

Uncomment this line:

text-table  fi  # Finnish

2) Restart brltty
3) connect Braille display which has integrated Braille keyboard
4) start e.g text editor
5) Try to write these scandinavian letters using the integrated Braille
keyboard in the Braille display:

- small letter ä )braille dots: 3, 4, 5)
- small letter ö (braille dots: 2, 4, 6)
- small letter å (braille dots: 1, 6)
- capital letter Ä (braille dots: 3, 4, 5, 7)
- capital letter Ö (braille dots: 2, 4, 6, 7)
- capital letter Å (braille dots: 1, 6, 7)



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages brltty depends on:
ii  init-system-helpers1.48
ii  libasound2 1.1.3-5
ii  libbluetooth3  5.43-2
ii  libbrlapi0.6   5.4-7
ii  libc6  2.24-11
ii  libglib2.0-0   2.50.3-2
ii  libgpm21.20.4-6.2+b1
ii  libicu57   57.1-6
ii  libncursesw5   6.0+20161126-1
ii  libpolkit-gobject-1-0  0.105-18
ii  libsystemd0232-25
ii  libtinfo5  6.0+20161126-1
ii  lsb-base   9.20161125
ii  policykit-10.105-18

Versions of packages brltty recommends:
ii  python  2.7.13-2

Versions of packages brltty 

Bug#864670: has broken Finnish braille table

[Mika Hanhijärvi]

Package: brltty
Version: 5.4-7
Severity: grave

I did get a new braille display awhile ago. I have been testing it and I have
noticed that braille table for the Finnish  language is broken. Reading text
works but It is impossible to write text in Finnish using the integrated
braille keyboard in the braille display. Writing text in Finnish language is
not possible because writing scandinavian letters (which are wery commonly used
in Finnish language) does not work. The following scandinavian letters are used
in Finnish language. Small letters: ä, ö, å. Capital letters: Ä, Ö, Å.

It seems that the braille table for the Finnish language has many lines which
define some weird control characters. Those lines conflict with lines defining
scandinavian letters . If I remove those conflicting control character lines
then both reading and writing text in Finnish works correctly.

I am a blind user from Finland so it is wery important for me that writing text
in Finnish works. My native language is Finnish so I am really using braille in
Finnish.

The braille table for the Finnish language is in the file:
/etc/brltty/Text/fi.ttb

First of all these lines define scandinavian letters used in the Finnish
language. These lines are correct and SHOULD NOT be changed:

char \xC4   (  345 7 )  # C4 ⡜ Ä [LATIN CAPITAL LETTER A WITH DIAERESIS]
char \xC5   (167 )  # C5 ⡡ Å [LATIN CAPITAL LETTER A WITH RING ABOVE]
char \xD6   ( 2 4 67 )  # D6 ⡪ Ö [LATIN CAPITAL LETTER O WITH DIAERESIS]
char \xE4   (  345   )  # E4 ⠜ ä [LATIN SMALL LETTER A WITH DIAERESIS]
char \xE5   (16  )  # E5 ⠡ å [LATIN SMALL LETTER A WITH RING ABOVE]
char \xF6   ( 2 4 6  )  # F6 ⠪ ö [LATIN SMALL LETTER O WITH DIAERESIS]


The problem described in this bug report is caused by the following lines.

This line is defined incorrectly and conflicts with the small letter "ä" ("ä"
in Finnish braille is dots: 3, 4, 5) :

char \x84   (  345   )  # 84 ⠜   []


- This line conflicts with the small letter "Å" ("å" in Finnish braille is
dots: 1, 6) :

char \x86   (16  )  # 86 ⠡   [START OF SELECTED AREA]


- This line conflicts with the capital letter "Ä" ("Ä" in Finnish braille is
dots: 3, 4, 5, 7) :

char \x8E   (  345 7 )  # 8E ⡜   [SINGLE SHIFT TWO]


- This line conflicts with the capital letter "Å" ("Å" in Finnish braille is
dots: 1,6,7) :

char \x8F   (167 )  # 8F ⡡   [SINGLE SHIFT THREE]


- This line conflicts with the small letter "ö" ("ö" in Finnish braille is
dots: 2, 4, 6) :

char \x94   ( 2 4 6  )  # 94 ⠪   [CANCEL CHARACTER]


- This line conflicts with the capital letter "Ö" ("Ö" in Finnish braille is
dots: 2, 4, 6, 7) :

char \x99   ( 2 4 67 )  # 99 ⡪   []


I really do not know for what and how those control characters are used, all I
know is that if those control character lines are not commented out then
writing text in the Finnish language is not possible. Those control character
lines should be commented out, removed or changed so that those do not conflict
with any other line.

I have compared the Finnish braille table with Swedish braille table because
Swedish is the second official language in finland. It seems that the Swedish
braille table does not define those control characters.

The braille table for the Swedish language is in the file:
/etc/brltty/Text/sv-1996.ttb

How to reproduce this bug:

1) select the Finnish language in the file:
/etc/brltty.conf

Uncomment this line:

text-table  fi  # Finnish

2) Restart brltty
3) connect Braille display which has integrated Braille keyboard
4) start e.g text editor
5) Try to write these scandinavian letters using the integrated Braille
keyboard in the Braille display:

- small letter ä )braille dots: 3, 4, 5)
- small letter ö (braille dots: 2, 4, 6)
- small letter å (braille dots: 1, 6)
- capital letter Ä (braille dots: 3, 4, 5, 7)
- capital letter Ö (braille dots: 2, 4, 6, 7)
- capital letter Å (braille dots: 1, 6, 7)



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages brltty depends on:
ii  init-system-helpers1.48
ii  libasound2 1.1.3-5
ii  libbluetooth3  5.43-2
ii  libbrlapi0.6   5.4-7
ii  libc6  2.24-11
ii  libglib2.0-0   2.50.3-2
ii  libgpm21.20.4-6.2+b1
ii  libicu57   57.1-6
ii  libncursesw5   6.0+20161126-1
ii  libpolkit-gobject-1-0  0.105-18
ii  libsystemd0232-25
ii  libtinfo5  6.0+20161126-1
ii  lsb-base   9.20161125
ii  policykit-10.105-18

Versions of packages brltty recommends:
ii  python  2.7.13-2

Versions of packages brltty 

Bug#859262: closed by Paul Gevers <elb...@debian.org> (Bug#859262: fixed in gnome-orca 3.22.2-3)

[Mika Hanhijärvi]

Unfortunately this did not fix the problem. The problem still exists. I 
still have noticed this only when using Synaptic.



One interesting thing is that if it happens when I do this:



/) Go to eg virtual desktop 2 on Gnome/

2) start Synaptic on that virtual desktop

3) click Reload button

4) Go to e.g virtual desktop 1 and do something else like browse the web 
using firefox or something else



5) Let Synaptic to finish reloading the repository information,

6) Go back to virtual desktop 2 where Synaptic is running and where it's 
window is open



Orca stops speaking when you do the step 6. That happened again some 
minutes ago and that has happened many times. Synaptic was running and 
reloading on one virtual desktop and I was browsing facebook on another 
virtual desktop. Everything worked just fine until I did goback to that 
virtual desktop where Synaptic was running. When I did that Orca 
immediately stopped to speak. When I closed the Synaptic using alt + f4 
then Orca started to speak again.



And by the way I do not remember if this problem existed in Debian 
Jessie. Both of my laptops are quite new. I first installed Debian 
Jessien on those laptops, but I upgraded to Stretch soon after that. My 
desktop computer is still running Debian 7.0 "Wheezy". I did not really 
use Debian 8.0 "Jessie" much on those laptops so you can say that I 
jumped from Wheezy to Stretch. This problem does not exist in Wheezy and 
I really can not say if it existed in Jessie, but it does still exist in 
Stretch. I do not know if this problem exists in new Stretch 
installations. I am going to make a clean Stretch install when I buy the 
new SSD disk, but I can not do that right now.











On 05/03/2017 09:51 PM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the gnome-orca package:

#859262: gnome-orca: Gets stuck if target app is busy

It has been closed by Paul Gevers .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Paul Gevers 
 by
replying to this email.

Bug#859262: closed by Paul Gevers <elb...@debian.org> (Bug#859262: fixed in gnome-orca 3.22.2-3)

[Mika Hanhijärvi]

Unfortunately this did not fix the problem. The problem still exists. I 
still have noticed this only when using Synaptic.



One interesting thing is that if it happens when I do this:



/) Go to eg virtual desktop 2 on Gnome/

2) start Synaptic on that virtual desktop

3) click Reload button

4) Go to e.g virtual desktop 1 and do something else like browse the web 
using firefox or something else



5) Let Synaptic to finish reloading the repository information,

6) Go back to virtual desktop 2 where Synaptic is running and where it's 
window is open



Orca stops speaking when you do the step 6. That happened again some 
minutes ago and that has happened many times. Synaptic was running and 
reloading on one virtual desktop and I was browsing facebook on another 
virtual desktop. Everything worked just fine until I did goback to that 
virtual desktop where Synaptic was running. When I did that Orca 
immediately stopped to speak. When I closed the Synaptic using alt + f4 
then Orca started to speak again.



And by the way I do not remember if this problem existed in Debian 
Jessie. Both of my laptops are quite new. I first installed Debian 
Jessien on those laptops, but I upgraded to Stretch soon after that. My 
desktop computer is still running Debian 7.0 "Wheezy". I did not really 
use Debian 8.0 "Jessie" much on those laptops so you can say that I 
jumped from Wheezy to Stretch. This problem does not exist in Wheezy and 
I really can not say if it existed in Jessie, but it does still exist in 
Stretch. I do not know if this problem exists in new Stretch 
installations. I am going to make a clean Stretch install when I buy the 
new SSD disk, but I can not do that right now.











On 05/03/2017 09:51 PM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the gnome-orca package:

#859262: gnome-orca: Gets stuck if target app is busy

It has been closed by Paul Gevers .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Paul Gevers 
 by
replying to this email.

Bug#859262: closed by Paul Gevers <elb...@debian.org> (Bug#859262: fixed in gnome-orca 3.22.2-3)

[Mika Hanhijärvi]

Unfortunately this did not fix the problem. The problem still exists. I 
still have noticed this only when using Synaptic.



One interesting thing is that if it happens when I do this:



/) Go to eg virtual desktop 2 on Gnome/

2) start Synaptic on that virtual desktop

3) click Reload button

4) Go to e.g virtual desktop 1 and do something else like browse the web 
using firefox or something else



5) Let Synaptic to finish reloading the repository information,

6) Go back to virtual desktop 2 where Synaptic is running and where it's 
window is open



Orca stops speaking when you do the step 6. That happened again some 
minutes ago and that has happened many times. Synaptic was running and 
reloading on one virtual desktop and I was browsing facebook on another 
virtual desktop. Everything worked just fine until I did goback to that 
virtual desktop where Synaptic was running. When I did that Orca 
immediately stopped to speak. When I closed the Synaptic using alt + f4 
then Orca started to speak again.



And by the way I do not remember if this problem existed in Debian 
Jessie. Both of my laptops are quite new. I first installed Debian 
Jessien on those laptops, but I upgraded to Stretch soon after that. My 
desktop computer is still running Debian 7.0 "Wheezy". I did not really 
use Debian 8.0 "Jessie" much on those laptops so you can say that I 
jumped from Wheezy to Stretch. This problem does not exist in Wheezy and 
I really can not say if it existed in Jessie, but it does still exist in 
Stretch. I do not know if this problem exists in new Stretch 
installations. I am going to make a clean Stretch install when I buy the 
new SSD disk, but I can not do that right now.











On 05/03/2017 09:51 PM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the gnome-orca package:

#859262: gnome-orca: Gets stuck if target app is busy

It has been closed by Paul Gevers .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Paul Gevers 
 by
replying to this email.

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

Ok, thanks for the info :-)


_ Mika




On 05/07/2017 05:49 PM, Joanmarie Diggs wrote:

I am looking at the line of code which caused the crash and it is the
same line of code as in the bug I reported. So you might have been doing
something different, but it appears to be the same bug which needs to be
fixed in AT-SPI2.

--joanie

On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote:


If it is the same bug then I have to say I did not close any application
when Orca crashed. I also did not do anythything particularly fast. I am
not 100% sure what I Was doing but If I remember correctly I just
switched between virtual Gnome desktops which did have some application
windows open.




On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug:
https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is
not good
because blind users like me have to rely on screen reader working
reliably.
This, or similar, problem also existed before the latest update to
Orca in
Debian Stretch, so I do not know if this has anything to do with the
latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal
Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack
(most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184
in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in
_dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
   (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

Ok, thanks for the info :-)


_ Mika




On 05/07/2017 05:49 PM, Joanmarie Diggs wrote:

I am looking at the line of code which caused the crash and it is the
same line of code as in the bug I reported. So you might have been doing
something different, but it appears to be the same bug which needs to be
fixed in AT-SPI2.

--joanie

On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote:


If it is the same bug then I have to say I did not close any application
when Orca crashed. I also did not do anythything particularly fast. I am
not 100% sure what I Was doing but If I remember correctly I just
switched between virtual Gnome desktops which did have some application
windows open.




On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug:
https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is
not good
because blind users like me have to rely on screen reader working
reliably.
This, or similar, problem also existed before the latest update to
Orca in
Debian Stretch, so I do not know if this has anything to do with the
latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal
Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack
(most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184
in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in
_dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
   (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

Ok, thanks for the info :-)


_ Mika




On 05/07/2017 05:49 PM, Joanmarie Diggs wrote:

I am looking at the line of code which caused the crash and it is the
same line of code as in the bug I reported. So you might have been doing
something different, but it appears to be the same bug which needs to be
fixed in AT-SPI2.

--joanie

On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote:


If it is the same bug then I have to say I did not close any application
when Orca crashed. I also did not do anythything particularly fast. I am
not 100% sure what I Was doing but If I remember correctly I just
switched between virtual Gnome desktops which did have some application
windows open.




On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug:
https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is
not good
because blind users like me have to rely on screen reader working
reliably.
This, or similar, problem also existed before the latest update to
Orca in
Debian Stretch, so I do not know if this has anything to do with the
latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal
Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack
(most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184
in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in
_dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
   (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

When I read the discussion in Gnome bug page I see that some people have 
regular Orca crashes which happen often e.g when they close some 
application. Luckily I have not noticed problem like that. Orca crashes 
do not happen often or regularly on my computer, just sometimes. I also 
have not had Orca crashes when I have closed applications. I think those 
crashes have happened mostly when I have switched between apps running 
on different Gnome virtual desktops. I run just one application on each 
virtual desktop.






On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: amd64
  (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

When I read the discussion in Gnome bug page I see that some people have 
regular Orca crashes which happen often e.g when they close some 
application. Luckily I have not noticed problem like that. Orca crashes 
do not happen often or regularly on my computer, just sometimes. I also 
have not had Orca crashes when I have closed applications. I think those 
crashes have happened mostly when I have switched between apps running 
on different Gnome virtual desktops. I run just one application on each 
virtual desktop.






On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: amd64
  (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

When I read the discussion in Gnome bug page I see that some people have 
regular Orca crashes which happen often e.g when they close some 
application. Luckily I have not noticed problem like that. Orca crashes 
do not happen often or regularly on my computer, just sometimes. I also 
have not had Orca crashes when I have closed applications. I think those 
crashes have happened mostly when I have switched between apps running 
on different Gnome virtual desktops. I run just one application on each 
virtual desktop.






On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: amd64
  (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

If it is the same bug then I have to say I did not close any application 
when Orca crashed. I also did not do anythything particularly fast. I am 
not 100% sure what I Was doing but If I remember correctly I just 
switched between virtual Gnome desktops which did have some application 
windows open.





On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: amd64
  (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

If it is the same bug then I have to say I did not close any application 
when Orca crashed. I also did not do anythything particularly fast. I am 
not 100% sure what I Was doing but If I remember correctly I just 
switched between virtual Gnome desktops which did have some application 
windows open.





On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: amd64
  (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#859262: Re: freezes Orca screen reader

[Mika Hanhijärvi]

Hello




On 04/29/2017 09:42 PM, Paul Gevers wrote:

Hi Mika, Tim,

On 29-04-17 17:51, Joanmarie Diggs wrote:

And to prepare for fixes of the package in Debian (which is 3.22.2 and
will be extremely hard convince the release managers to update in this
stage due to the freeze), which fixes would we need to backport to fix
the issues identified so far?

commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7
commit 382c5408afc7dd25f9b477a5e30c50ba917155c0
commit d51f87a7f000d099da98247dc7ca337b2b5483be
commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6

I prepared and build¹ a Debian gnome-orca package with the above
mentioned upstream commits that should prevent Orca from freezing (or
appearing to do so). It would be great if you could install the deb²
(checksum below³) and report if it resolves your issues with Synaptic
(as my Orca installation isn't set-upped properly, I don't hear anything).

Paul

¹
http://debomatic-amd64.debian.net/distribution#testing/gnome-orca/3.22.2-3~debo1
²
http://debomatic-amd64.debian.net/debomatic/testing/pool/gnome-orca_3.22.2-3~debo1/gnome-orca_3.22.2-3~debo1_all.deb
³
paul@testavoira ~ $ sha256sum gnome-orca_3.22.2-3~debo1_all.deb
6d9c8bca6b211ac1570792dd66fde8a46cdf59a038b87a0d9bf16a43822e1887
gnome-orca_3.22.2-3~debo1_all.deb





Ok. I will try it now, thanks.

Bug#859262: Re: freezes Orca screen reader

[Mika Hanhijärvi]

Hello




On 04/29/2017 09:42 PM, Paul Gevers wrote:

Hi Mika, Tim,

On 29-04-17 17:51, Joanmarie Diggs wrote:

And to prepare for fixes of the package in Debian (which is 3.22.2 and
will be extremely hard convince the release managers to update in this
stage due to the freeze), which fixes would we need to backport to fix
the issues identified so far?

commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7
commit 382c5408afc7dd25f9b477a5e30c50ba917155c0
commit d51f87a7f000d099da98247dc7ca337b2b5483be
commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6

I prepared and build¹ a Debian gnome-orca package with the above
mentioned upstream commits that should prevent Orca from freezing (or
appearing to do so). It would be great if you could install the deb²
(checksum below³) and report if it resolves your issues with Synaptic
(as my Orca installation isn't set-upped properly, I don't hear anything).

Paul

¹
http://debomatic-amd64.debian.net/distribution#testing/gnome-orca/3.22.2-3~debo1
²
http://debomatic-amd64.debian.net/debomatic/testing/pool/gnome-orca_3.22.2-3~debo1/gnome-orca_3.22.2-3~debo1_all.deb
³
paul@testavoira ~ $ sha256sum gnome-orca_3.22.2-3~debo1_all.deb
6d9c8bca6b211ac1570792dd66fde8a46cdf59a038b87a0d9bf16a43822e1887
gnome-orca_3.22.2-3~debo1_all.deb





Ok. I will try it now, thanks.

Bug#859262: Re: freezes Orca screen reader

[Mika Hanhijärvi]

Hello




On 04/29/2017 09:42 PM, Paul Gevers wrote:

Hi Mika, Tim,

On 29-04-17 17:51, Joanmarie Diggs wrote:

And to prepare for fixes of the package in Debian (which is 3.22.2 and
will be extremely hard convince the release managers to update in this
stage due to the freeze), which fixes would we need to backport to fix
the issues identified so far?

commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7
commit 382c5408afc7dd25f9b477a5e30c50ba917155c0
commit d51f87a7f000d099da98247dc7ca337b2b5483be
commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6

I prepared and build¹ a Debian gnome-orca package with the above
mentioned upstream commits that should prevent Orca from freezing (or
appearing to do so). It would be great if you could install the deb²
(checksum below³) and report if it resolves your issues with Synaptic
(as my Orca installation isn't set-upped properly, I don't hear anything).

Paul

¹
http://debomatic-amd64.debian.net/distribution#testing/gnome-orca/3.22.2-3~debo1
²
http://debomatic-amd64.debian.net/debomatic/testing/pool/gnome-orca_3.22.2-3~debo1/gnome-orca_3.22.2-3~debo1_all.deb
³
paul@testavoira ~ $ sha256sum gnome-orca_3.22.2-3~debo1_all.deb
6d9c8bca6b211ac1570792dd66fde8a46cdf59a038b87a0d9bf16a43822e1887
gnome-orca_3.22.2-3~debo1_all.deb





Ok. I will try it now, thanks.

Bug#861387: fails to open applet menu

[Mika Hanhijärvi]

Hello
On 04/29/2017 06:35 PM, Scott Leggett wrote:

tags 861387 + moreinfo unreproducible
severity 861387 important
--

Hello Mika,

On 2017-04-28.13:17, Mika Hanhijärvi wrote:

Package: pasystray
Version: 0.6.0-1
Severity: grave

Hello

pasystray applet is visible in the Gnome's legacy icon tray but when I click
the  icon then applet menu does not open. This makes pasystray unusable,
atleast on Gnome, I do not know if the problem happens on other desktops too.


Thanks for the bug report.

I have tried to reproduce your issue by downloading the latest live-cd
of Strech with Gnome, and installing pasystray. As you can see in the
attached screenshot, the menu does work for me (both right-click and
left-click).

Could you provide any more information about your Gnome configuration
that is different from the default?

You could also try running `pasystray -d` in a terminal to print debug
information that may help figure out what's going on.

In the meantime, I have downgraded the severity of the bug as I cannot
reproduce it on a default Gnome desktop.





I can not see the screenshot because I am blind. If the pasystray menu 
opens then atleast it does not work with Orca screen reader. Note that I 
use the computer using keyboard whithout using mouse. Blind users like 
me can not use mouse. So  when I say that  i click the pasystray icon, I 
mean that I select the icon using left and right arrow keys from 
keyboard and then I click the icon using enter or space from keyboard.


When I click the pasystray icon Orca screen reader says something like 
"shshshsh" or something like that, but  the pasystray menu can not be 
accessed from keyboard. The menu may be accessible using mouse, but as I 
said I am blind and I can not use mouse.


I am using the Gnome desktop installed by Debian. This problem happens 
on both of my laptops running Debian Stretch. Both laptops have been 
upgraded from Jessie to Stretch  The only package that I have installed 
from outside of debian is Skype.


I have still the padevchooser installed, because pasystray does not 
work. I do not know if that could  cause problems. I would like to 
uninstall padevchooser because it is not in Debian anymore, but if If I 
uninstall it and pasystray does anot work then I have no Pulseaudio 
applet at all...


Here is how to reproduce this bug:

1) install Orca screen reader
2) activate Orca
3) go to Gnome desktop legacy icon tray by pressing  ctrl-alt-tab from 
keyboard
4) select the pasystray applet by using left and right arrow keys from 
keyboard

5( click the  pasystray by pressing enter or space from keyboard

Bug#861387: fails to open applet menu

[Mika Hanhijärvi]

Package: pasystray
Version: 0.6.0-1
Severity: grave

Hello

pasystray applet is visible in the Gnome's legacy icon tray but when I click
the  icon then applet menu does not open. This makes pasystray unusable,
atleast on Gnome, I do not know if the problem happens on other desktops too.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pasystray depends on:
ii  gnome-icon-theme 3.12.0-2
ii  libatk1.0-0  2.22.0-1
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavahi-glib1   0.6.32-2
ii  libc62.24-10
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libnotify4   0.7.7-2
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpulse-mainloop-glib0  10.0-1
ii  libpulse010.0-1
ii  libx11-6 2:1.6.4-3

pasystray recommends no packages.

Versions of packages pasystray suggests:
ii  paman   0.9.4-1+b3
ii  paprefs 0.9.10-2+b1
ii  pavucontrol 3.0-3+b3
ii  pavumeter   0.9.3-4+b3
ii  pulseaudio-module-zeroconf  10.0-1

-- no debconf information

Bug#861387: fails to open applet menu

[Mika Hanhijärvi]

Package: pasystray
Version: 0.6.0-1
Severity: grave

Hello

pasystray applet is visible in the Gnome's legacy icon tray but when I click
the  icon then applet menu does not open. This makes pasystray unusable,
atleast on Gnome, I do not know if the problem happens on other desktops too.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pasystray depends on:
ii  gnome-icon-theme 3.12.0-2
ii  libatk1.0-0  2.22.0-1
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavahi-glib1   0.6.32-2
ii  libc62.24-10
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libnotify4   0.7.7-2
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpulse-mainloop-glib0  10.0-1
ii  libpulse010.0-1
ii  libx11-6 2:1.6.4-3

pasystray recommends no packages.

Versions of packages pasystray suggests:
ii  paman   0.9.4-1+b3
ii  paprefs 0.9.10-2+b1
ii  pavucontrol 3.0-3+b3
ii  pavumeter   0.9.3-4+b3
ii  pulseaudio-module-zeroconf  10.0-1

-- no debconf information

Bug#859926: speechd-up: fails to install

[Mika Hanhijärvi]

Hello


On 04/09/2017 10:10 PM, Samuel Thibault wrote:

Control: retitle -1 speechd-up: fails to install

Hello,

Mika Hanhijärvi, on dim. 09 avril 2017 13:42:36 +0300, wrote:

When I try to install speechd-up package I get this error:

E: speechd-up: subprocess installed post-installation script returned error
exit status 1

Do you happen to have the espeakup package installed too?  They can't
work at the same time.

Otherwise, could somebody from debian-accessibility check whether
speechd-up works with the current speech-dispatcher?

Samuel




No. I do not have espeakup installed.

I removed espeakup because I wanted to try if speechd-up would solve 
atleast part of the one problem I have (maybe offtopic here). For some 
reason if espeakup speaks something when computer is booting then screen 
reader does not speak on Gdm login screen and on desktop. But espeak 
speaks on console.  So I have to reboot sometimes severaltimes. If  
espeakup does not say anything when computer boots, then screen reader 
speaks on gdm, but not on console. If I then login to desktop then  Orca 
speaks on desktop, but  if I go back to gdm screen whitout logging out 
from desktop first then screen reader does not speak on gdm screen. 
espeakup also does not speak on console. If I logout from desktop then 
screen reader starts to speak on gdm screen again, but espeak still does 
not speak on console. So I can not switch between desktop, gdm login 
screen and console, I am blind so I need to use screen reader.


I have no idea to which package I would need to file the bug, because I 
do not know if the problem is in espeakup, pulseaudio, 
speech-dispatcher, Orca or espeak / espeak-ng   ...


So I wanted to try if speechd-up would solve atleast part of the problem.

- Mika

Bug#859926: speechd-up: fails to install

[Mika Hanhijärvi]

Hello


On 04/09/2017 10:10 PM, Samuel Thibault wrote:

Control: retitle -1 speechd-up: fails to install

Hello,

Mika Hanhijärvi, on dim. 09 avril 2017 13:42:36 +0300, wrote:

When I try to install speechd-up package I get this error:

E: speechd-up: subprocess installed post-installation script returned error
exit status 1

Do you happen to have the espeakup package installed too?  They can't
work at the same time.

Otherwise, could somebody from debian-accessibility check whether
speechd-up works with the current speech-dispatcher?

Samuel




No. I do not have espeakup installed.

I removed espeakup because I wanted to try if speechd-up would solve 
atleast part of the one problem I have (maybe offtopic here). For some 
reason if espeakup speaks something when computer is booting then screen 
reader does not speak on Gdm login screen and on desktop. But espeak 
speaks on console.  So I have to reboot sometimes severaltimes. If  
espeakup does not say anything when computer boots, then screen reader 
speaks on gdm, but not on console. If I then login to desktop then  Orca 
speaks on desktop, but  if I go back to gdm screen whitout logging out 
from desktop first then screen reader does not speak on gdm screen. 
espeakup also does not speak on console. If I logout from desktop then 
screen reader starts to speak on gdm screen again, but espeak still does 
not speak on console. So I can not switch between desktop, gdm login 
screen and console, I am blind so I need to use screen reader.


I have no idea to which package I would need to file the bug, because I 
do not know if the problem is in espeakup, pulseaudio, 
speech-dispatcher, Orca or espeak / espeak-ng   ...


So I wanted to try if speechd-up would solve atleast part of the problem.

- Mika

Bug#859926: speechd-up: fails to install

[Mika Hanhijärvi]

Hello


On 04/09/2017 10:10 PM, Samuel Thibault wrote:

Control: retitle -1 speechd-up: fails to install

Hello,

Mika Hanhijärvi, on dim. 09 avril 2017 13:42:36 +0300, wrote:

When I try to install speechd-up package I get this error:

E: speechd-up: subprocess installed post-installation script returned error
exit status 1

Do you happen to have the espeakup package installed too?  They can't
work at the same time.

Otherwise, could somebody from debian-accessibility check whether
speechd-up works with the current speech-dispatcher?

Samuel




No. I do not have espeakup installed.

I removed espeakup because I wanted to try if speechd-up would solve 
atleast part of the one problem I have (maybe offtopic here). For some 
reason if espeakup speaks something when computer is booting then screen 
reader does not speak on Gdm login screen and on desktop. But espeak 
speaks on console.  So I have to reboot sometimes severaltimes. If  
espeakup does not say anything when computer boots, then screen reader 
speaks on gdm, but not on console. If I then login to desktop then  Orca 
speaks on desktop, but  if I go back to gdm screen whitout logging out 
from desktop first then screen reader does not speak on gdm screen. 
espeakup also does not speak on console. If I logout from desktop then 
screen reader starts to speak on gdm screen again, but espeak still does 
not speak on console. So I can not switch between desktop, gdm login 
screen and console, I am blind so I need to use screen reader.


I have no idea to which package I would need to file the bug, because I 
do not know if the problem is in espeakup, pulseaudio, 
speech-dispatcher, Orca or espeak / espeak-ng   ...


So I wanted to try if speechd-up would solve atleast part of the problem.

- Mika

Bug#859949: has a dependency problem

[Mika Hanhijärvi]

Package: python3-espeak
Version: 0.5-1+b4
Severity: grave

Packages python-espeak and python3-espeak can not be installed because of the
dependency problem if espeak speech synthesizer is replaced with espeak-ng by
installing the package libespeak-ng-libespeak1 which replaces the package
libespeak1

This bug makes it impossible to install e.g package ibus-braille when espeak is
replaced with espeak-ng.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-espeak depends on:
ii  libc6 2.24-9
ii  libespeak-ng-libespeak1 [libespeak1]  1.49.0+dfsg-8
ii  libgcc1   1:6.3.0-11
ii  libstdc++66.3.0-11
ii  python3   3.5.3-1

python3-espeak recommends no packages.

python3-espeak suggests no packages.

Bug#859949: has a dependency problem

[Mika Hanhijärvi]

Package: python3-espeak
Version: 0.5-1+b4
Severity: grave

Packages python-espeak and python3-espeak can not be installed because of the
dependency problem if espeak speech synthesizer is replaced with espeak-ng by
installing the package libespeak-ng-libespeak1 which replaces the package
libespeak1

This bug makes it impossible to install e.g package ibus-braille when espeak is
replaced with espeak-ng.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-espeak depends on:
ii  libc6 2.24-9
ii  libespeak-ng-libespeak1 [libespeak1]  1.49.0+dfsg-8
ii  libgcc1   1:6.3.0-11
ii  libstdc++66.3.0-11
ii  python3   3.5.3-1

python3-espeak recommends no packages.

python3-espeak suggests no packages.

Bug#859926: fails to install

[Mika Hanhijärvi]

Package: speechd-up
Version: 0.5~20110719-6+b1
Severity: grave

When I try to install speechd-up package I get this error:

E: speechd-up: subprocess installed post-installation script returned error
exit status 1

Synaptic marks the package as installed. If I try to reinstall the package I
get this error:

E: Internal Error, No file name for speechd-up:amd64





-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages speechd-up depends on:
ii  libc6  2.24-9
ii  libdotconf01.3-0.2
ii  libspeechd20.8.6-4
ii  speech-dispatcher  0.8.6-4

speechd-up recommends no packages.

speechd-up suggests no packages.

-- no debconf information

Bug#859926: fails to install

[Mika Hanhijärvi]

Package: speechd-up
Version: 0.5~20110719-6+b1
Severity: grave

When I try to install speechd-up package I get this error:

E: speechd-up: subprocess installed post-installation script returned error
exit status 1

Synaptic marks the package as installed. If I try to reinstall the package I
get this error:

E: Internal Error, No file name for speechd-up:amd64





-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages speechd-up depends on:
ii  libc6  2.24-9
ii  libdotconf01.3-0.2
ii  libspeechd20.8.6-4
ii  speech-dispatcher  0.8.6-4

speechd-up recommends no packages.

speechd-up suggests no packages.

-- no debconf information

Bug#859926: fails to install

[Mika Hanhijärvi]

Package: speechd-up
Version: 0.5~20110719-6+b1
Severity: grave

When I try to install speechd-up package I get this error:

E: speechd-up: subprocess installed post-installation script returned error
exit status 1

Synaptic marks the package as installed. If I try to reinstall the package I
get this error:

E: Internal Error, No file name for speechd-up:amd64





-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages speechd-up depends on:
ii  libc6  2.24-9
ii  libdotconf01.3-0.2
ii  libspeechd20.8.6-4
ii  speech-dispatcher  0.8.6-4

speechd-up recommends no packages.

speechd-up suggests no packages.

-- no debconf information

Bug#859262: freezes Orca screen reader

[Mika Hanhijärvi]

Package: synaptic
Version: 0.84.2
Severity: grave

Synaptic often freezes the Orca screen reader so that Orca speaks nothing until
Synaptic is closed. The same happens on both of my laptops running Debian
Stretch.

I am blind so I have to use computer using Orca screen reader. It happens wery
often that when I e.g click the Reload button in Synaptic, or select Reload
from the Synaptic menu, then Orca screen reader stops speaking. Synapticdoes
not freeze the whole desktop, just Orca.  This problem seems to happen
randomly, sometimes it happens sometimes it does not. When Synaptic has
finished reloading the package database information Orca may start speaking
again, but often it does not. If it does not then I have to close the Synaptic
by pressing alt + F4 after which Orca starts to speak again.

It also happens sometimes that if I have reloaded repository package database
information and click Mark all updades after that then Orca stops speaking. On
my second laptop it currently happens almost every time that Orca stops
speaking when I click the Mark all updates or select it from the menu. Tkhat
also seems to happen randomly, sometimes it happens sometimes not.

I have not noticed any problems like that when I have used other applications,
this happns only when I am using Synaptic.

As I said I have two laptops running Debian Stretch and both have the same
problems. Both laptops have been upgraded from Jessie to Stretch. The first
laptop was almost clean Jessie installation before it was upgraded to Stretch,
it still has wery little apps installed.

I am using Gnome desktop. I am blind so it is difficult for me to try to figure
out what is wrong. I I have used both espeak and espeak-ng speech synthetisers
with Orca screen reader, the same problem exists notmatter which of those is in
use.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.4~rc2
ii  libapt-pkg5.01.4~rc2
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:6.3.0-11
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-3
ii  libgtk-3-0   3.22.9-4
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   6.3.0-11
ii  libvte-2.91-00.46.1-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.3-1
ii  policykit-1  0.105-17
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.2499-1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.49
pn  deborphan
pn  dwww 
ii  menu 2.1.47+b1
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information

Bug#859262: freezes Orca screen reader

[Mika Hanhijärvi]

Package: synaptic
Version: 0.84.2
Severity: grave

Synaptic often freezes the Orca screen reader so that Orca speaks nothing until
Synaptic is closed. The same happens on both of my laptops running Debian
Stretch.

I am blind so I have to use computer using Orca screen reader. It happens wery
often that when I e.g click the Reload button in Synaptic, or select Reload
from the Synaptic menu, then Orca screen reader stops speaking. Synapticdoes
not freeze the whole desktop, just Orca.  This problem seems to happen
randomly, sometimes it happens sometimes it does not. When Synaptic has
finished reloading the package database information Orca may start speaking
again, but often it does not. If it does not then I have to close the Synaptic
by pressing alt + F4 after which Orca starts to speak again.

It also happens sometimes that if I have reloaded repository package database
information and click Mark all updades after that then Orca stops speaking. On
my second laptop it currently happens almost every time that Orca stops
speaking when I click the Mark all updates or select it from the menu. Tkhat
also seems to happen randomly, sometimes it happens sometimes not.

I have not noticed any problems like that when I have used other applications,
this happns only when I am using Synaptic.

As I said I have two laptops running Debian Stretch and both have the same
problems. Both laptops have been upgraded from Jessie to Stretch. The first
laptop was almost clean Jessie installation before it was upgraded to Stretch,
it still has wery little apps installed.

I am using Gnome desktop. I am blind so it is difficult for me to try to figure
out what is wrong. I I have used both espeak and espeak-ng speech synthetisers
with Orca screen reader, the same problem exists notmatter which of those is in
use.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.4~rc2
ii  libapt-pkg5.01.4~rc2
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:6.3.0-11
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-3
ii  libgtk-3-0   3.22.9-4
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   6.3.0-11
ii  libvte-2.91-00.46.1-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.3-1
ii  policykit-1  0.105-17
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.2499-1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.49
pn  deborphan
pn  dwww 
ii  menu 2.1.47+b1
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information

Bug#858645: opening and saving remote documents fails

[Mika Hanhijärvi]

Package: libreoffice-writer
Version: 1:5.2.5-2
Severity: normal

If I try to save document to remote  Google Drive using Libreoffice then I get
the  General input / output error. The same happens if I try to open remote
document.

 when I added my Google Drive account it didn't gave any error. I entered my
email ID in username and my password in password in Google Drive. I don't have
2 factor authentication.

I am blind so it is difficult for me to try to figure out what is wrong.

I am using the current LibreOffice in Debian Stretch



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libreoffice-writer depends on:
ii  dpkg   1.18.23
ii  libabw-0.1-1   0.1.1-4
ii  libc6  2.24-9
ii  libe-book-0.1-10.1.2-4
ii  libetonyek-0.1-1   0.1.6-5
ii  libgcc11:6.3.0-10
ii  libicu57   57.1-5
ii  libmwaw-0.3-3  0.3.9-1
ii  libodfgen-0.1-10.1.6-2
ii  libreoffice-base-core  1:5.2.5-2
ii  libreoffice-core   1:5.2.5-2
ii  librevenge-0.0-0   0.0.4-6
ii  libstdc++6 6.3.0-10
ii  libwpd-0.10-10 0.10.1-5
ii  libwpg-0.3-3   0.3.1-3
ii  libwps-0.4-4   0.4.5-1
ii  libxml22.9.4+dfsg1-2.2
ii  uno-libs3  5.2.5-2
ii  ure5.2.5-2
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages libreoffice-writer recommends:
ii  libreoffice-math  1:5.2.5-2

Versions of packages libreoffice-writer suggests:
ii  default-jre [java5-runtime]2:1.8-58
ii  fonts-crosextra-caladea20130214-1
ii  fonts-crosextra-carlito20130920-1
ii  libreoffice-base   1:5.2.5-2
pn  libreoffice-gcj
ii  libreoffice-java-common1:5.2.5-2
ii  openjdk-8-jre [java5-runtime]  8u121-b13-4

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.7+b1
ii  fonts-opensymbol  2:102.7+LibO5.2.5-2
ii  libboost-date-time1.62.0  1.62.0+dfsg-4
ii  libc6 2.24-9
ii  libcairo2 1.14.8-1
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.1-8
ii  libcurl3-gnutls   7.52.1-3
ii  libdbus-1-3   1.10.16-1
ii  libdbus-glib-1-2  0.108-2
ii  libdconf1 0.26.0-2+b1
ii  libeot0   0.01-4+b1
ii  libexpat1 2.2.0-2
ii  libexttextcat-2.0-0   3.4.4-2+b1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3+b2
ii  libgcc1   1:6.3.0-10
ii  libgl1-mesa-glx [libgl1]  13.0.5-1
ii  libglew2.02.0.0-3+b1
ii  libglib2.0-0  2.50.3-1
ii  libgltf-0.0-0v5   0.0.2-5
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgraphite2-31.3.9-4
ii  libharfbuzz-icu0  1.4.2-1
ii  libharfbuzz0b 1.4.2-1
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libhyphen02.8.8-5
ii  libice6   2:1.0.9-2
ii  libicu57  57.1-5
ii  libjpeg62-turbo   1:1.5.1-2
ii  liblangtag1   0.6.2-1
ii  liblcms2-22.8-4
ii  libldap-2.4-2 2.4.44+dfsg-3
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-2
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libodfgen-0.1-1   0.1.6-2
ii  libpcre3  2:8.39-2.1
ii  libpng16-16   1.6.28-1
ii  librdf0   1.0.17-1.1
ii  libreoffice-common1:5.2.5-2
ii  librevenge-0.0-0  0.0.4-6
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-10
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxml2   2.9.4+dfsg1-2.2
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  libxslt1.11.1.29-2
ii  uno-libs3 5.2.5-2
ii  ure   5.2.5-2
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu5

-- no debconf information

Bug#858645: opening and saving remote documents fails

[Mika Hanhijärvi]

Package: libreoffice-writer
Version: 1:5.2.5-2
Severity: normal

If I try to save document to remote  Google Drive using Libreoffice then I get
the  General input / output error. The same happens if I try to open remote
document.

 when I added my Google Drive account it didn't gave any error. I entered my
email ID in username and my password in password in Google Drive. I don't have
2 factor authentication.

I am blind so it is difficult for me to try to figure out what is wrong.

I am using the current LibreOffice in Debian Stretch



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libreoffice-writer depends on:
ii  dpkg   1.18.23
ii  libabw-0.1-1   0.1.1-4
ii  libc6  2.24-9
ii  libe-book-0.1-10.1.2-4
ii  libetonyek-0.1-1   0.1.6-5
ii  libgcc11:6.3.0-10
ii  libicu57   57.1-5
ii  libmwaw-0.3-3  0.3.9-1
ii  libodfgen-0.1-10.1.6-2
ii  libreoffice-base-core  1:5.2.5-2
ii  libreoffice-core   1:5.2.5-2
ii  librevenge-0.0-0   0.0.4-6
ii  libstdc++6 6.3.0-10
ii  libwpd-0.10-10 0.10.1-5
ii  libwpg-0.3-3   0.3.1-3
ii  libwps-0.4-4   0.4.5-1
ii  libxml22.9.4+dfsg1-2.2
ii  uno-libs3  5.2.5-2
ii  ure5.2.5-2
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages libreoffice-writer recommends:
ii  libreoffice-math  1:5.2.5-2

Versions of packages libreoffice-writer suggests:
ii  default-jre [java5-runtime]2:1.8-58
ii  fonts-crosextra-caladea20130214-1
ii  fonts-crosextra-carlito20130920-1
ii  libreoffice-base   1:5.2.5-2
pn  libreoffice-gcj
ii  libreoffice-java-common1:5.2.5-2
ii  openjdk-8-jre [java5-runtime]  8u121-b13-4

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.7+b1
ii  fonts-opensymbol  2:102.7+LibO5.2.5-2
ii  libboost-date-time1.62.0  1.62.0+dfsg-4
ii  libc6 2.24-9
ii  libcairo2 1.14.8-1
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.1-8
ii  libcurl3-gnutls   7.52.1-3
ii  libdbus-1-3   1.10.16-1
ii  libdbus-glib-1-2  0.108-2
ii  libdconf1 0.26.0-2+b1
ii  libeot0   0.01-4+b1
ii  libexpat1 2.2.0-2
ii  libexttextcat-2.0-0   3.4.4-2+b1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3+b2
ii  libgcc1   1:6.3.0-10
ii  libgl1-mesa-glx [libgl1]  13.0.5-1
ii  libglew2.02.0.0-3+b1
ii  libglib2.0-0  2.50.3-1
ii  libgltf-0.0-0v5   0.0.2-5
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgraphite2-31.3.9-4
ii  libharfbuzz-icu0  1.4.2-1
ii  libharfbuzz0b 1.4.2-1
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libhyphen02.8.8-5
ii  libice6   2:1.0.9-2
ii  libicu57  57.1-5
ii  libjpeg62-turbo   1:1.5.1-2
ii  liblangtag1   0.6.2-1
ii  liblcms2-22.8-4
ii  libldap-2.4-2 2.4.44+dfsg-3
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-2
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libodfgen-0.1-1   0.1.6-2
ii  libpcre3  2:8.39-2.1
ii  libpng16-16   1.6.28-1
ii  librdf0   1.0.17-1.1
ii  libreoffice-common1:5.2.5-2
ii  librevenge-0.0-0  0.0.4-6
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-10
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxml2   2.9.4+dfsg1-2.2
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  libxslt1.11.1.29-2
ii  uno-libs3 5.2.5-2
ii  ure   5.2.5-2
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu5

-- no debconf information

Bug#858634: listviews are not accessible with Orca screen reader

[Mika Hanhijärvi]

Package: banshee
Version: 2.6.2-6.1
Severity: important

Hi

Banshe's artist, album, genre and song listviews are not accessible with Orca
screen reader.

I am blind so I have to use computer using screen reader which speaks the
content on screen. If I go e.g to the artist list and try to select one of the
artists using keyboard up and down arrow keys then Orca screen reader speaks
nothing. Same hapeens if I try to select album, genre or song.

This bug makes Banshee unusable for the users who are visually impaired and
have to use computer using screen reader..



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages banshee depends on:
ii  gnome-icon-theme  3.12.0-2
ii  gstreamer1.0-alsa [gstreamer1.0-audiosink]1.10.4-1
ii  gstreamer1.0-plugins-bad [gstreamer1.0-audiosink  1.10.4-1
ii  gstreamer1.0-plugins-base 1.10.4-1
ii  gstreamer1.0-plugins-good [gstreamer1.0-audiosin  1.10.4-1
ii  gstreamer1.0-pulseaudio [gstreamer1.0-audiosink]  1.10.4-1
ii  libc6 2.24-9
ii  libcairo2 1.14.8-1
ii  libdbus-glib-1-2  0.108-2
ii  libdbus-glib2.0-cil   0.6.0-1
ii  libdbus2.0-cil0.8.1-2
ii  libgconf2.0-cil   2.24.2-4
ii  libgdata2.1-cil   2.2.0.0-2
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libgkeyfile1.0-cil0.1-5
ii  libglib2.0-0  2.50.3-1
ii  libglib2.0-cil2.12.40-1
ii  libgpod4  0.8.3-8
ii  libgstreamer-plugins-base1.0-01.10.4-1
ii  libgstreamer1.0-0 1.10.4-1
ii  libgtk-sharp-beans-cil2.14.1-4
ii  libgtk2.0-0   2.24.31-2
ii  libgtk2.0-cil 2.12.40-1
ii  libgudev1.0-cil   0.1-4
ii  libkarma0 0.1.2-2.5
ii  libmono-addins0.2-cil 1.0+git20130406.adcd75b-4
ii  libmono-cairo4.0-cil  4.6.2.7+dfsg-1
ii  libmono-corlib4.5-cil 4.6.2.7+dfsg-1
ii  libmono-posix4.0-cil  4.6.2.7+dfsg-1
ii  libmono-sharpzip4.84-cil  4.6.2.7+dfsg-1
ii  libmono-system-core4.0-cil4.6.2.7+dfsg-1
ii  libmono-system-xml4.0-cil 4.6.2.7+dfsg-1
ii  libmono-system4.0-cil 4.6.2.7+dfsg-1
ii  libmono-zeroconf1.0-cil   0.9.0-6
ii  libmtp9   1.1.12-1+b1
ii  libnotify0.4-cil  0.4.0~r3032-7
ii  libpango-1.0-01.40.4-1
ii  libpangocairo-1.0-0   1.40.4-1
ii  libsoup-gnome2.4-12.56.0-2
ii  libsoup2.4-1  2.56.0-2
ii  libsqlite3-0  3.16.2-3
ii  libtaglib2.1-cil  2.1.0.0-3
ii  libwebkitgtk-1.0-02.4.11-3
ii  libwnck22 2.30.7-5.1
ii  libx11-6  2:1.6.4-3
ii  libxrandr22:1.5.1-1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  mono-runtime  4.6.2.7+dfsg-1

Versions of packages banshee recommends:
ii  avahi-daemon 0.6.32-2
ii  brasero  3.12.1-4
ii  gstreamer1.0-pulseaudio  1.10.4-1
ii  media-player-info22-3

Versions of packages banshee suggests:
pn  banshee-dbg
pn  gstreamer1.0-ffmpeg
ii  gstreamer1.0-plugins-bad   1.10.4-1
ii  gstreamer1.0-plugins-ugly  1.10.4-1

-- no debconf information

Bug#857501: does not work with Orca screen reader and espeak

[Mika Hanhijärvi]

Package: mbrola
Version: 3.01h+2-2
Severity: grave

Hi

If I go to Orca screen reader settings and select the "Espeak Mbrola generic"
as a speech synthetiser then Orca speaks nothing. That speech synthetiser did
still work couple of days ago when I used it the last time. Orca did speak
using those more natural sounding mbrola voices. I installed the latest update
to mbrola package yesterday and if I now select that "Espeak Mbrola generic"
then Orca speakks nothing.

I am blind so it is difficult for me to try to solve what is causing this. I
have not changed the Orca and speech-dispatcher settings so that is not causing
the problem.

I have also noticed that if I now start the Gespeaker application and select
one of the mbrola voices then  Gespeaker speaks in wery robotic voice which
does not sound at all like that same mbrolaa voice did sound earlier.

The same happens if I use espeak with mbrola voice from command line. Espeak
speaks in wery robotic voice which does not sound like mbrola voice used to
sound. I also get this error message:

$ espeak -v mb-en1 "hello world"

mbrowrap error: Unable to get .wav header from mbrola
mbrola voice not found

I get the same error if I use some other mbrola voice than mb-en1.

So, any idea what is causing the problem?




-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mbrola depends on:
ii  dpkg-dev 1.18.23
pn  libc6:i386 | libc6-i386  

mbrola recommends no packages.

Versions of packages mbrola suggests:
pn  cicero 
ii  espeak 1.48.04+dfsg-5+b1
ii  mbrola-ee1 [mbrola-voice]  0.0.20020407-1
ii  mbrola-en1 [mbrola-voice]  19980910-2
ii  mbrola-es1 [mbrola-voice]  0.0.19980610-2
ii  mbrola-fr4 [mbrola-voice]  0.0.19990521-2
ii  mbrola-us1 [mbrola-voice]  0.3-2
ii  mbrola-us2 [mbrola-voice]  0.1-2
ii  mbrola-us3 [mbrola-voice]  0.1-1

-- no debconf information

Bug#857501: does not work with Orca screen reader and espeak

[Mika Hanhijärvi]

Package: mbrola
Version: 3.01h+2-2
Severity: grave

Hi

If I go to Orca screen reader settings and select the "Espeak Mbrola generic"
as a speech synthetiser then Orca speaks nothing. That speech synthetiser did
still work couple of days ago when I used it the last time. Orca did speak
using those more natural sounding mbrola voices. I installed the latest update
to mbrola package yesterday and if I now select that "Espeak Mbrola generic"
then Orca speakks nothing.

I am blind so it is difficult for me to try to solve what is causing this. I
have not changed the Orca and speech-dispatcher settings so that is not causing
the problem.

I have also noticed that if I now start the Gespeaker application and select
one of the mbrola voices then  Gespeaker speaks in wery robotic voice which
does not sound at all like that same mbrolaa voice did sound earlier.

The same happens if I use espeak with mbrola voice from command line. Espeak
speaks in wery robotic voice which does not sound like mbrola voice used to
sound. I also get this error message:

$ espeak -v mb-en1 "hello world"

mbrowrap error: Unable to get .wav header from mbrola
mbrola voice not found

I get the same error if I use some other mbrola voice than mb-en1.

So, any idea what is causing the problem?




-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mbrola depends on:
ii  dpkg-dev 1.18.23
pn  libc6:i386 | libc6-i386  

mbrola recommends no packages.

Versions of packages mbrola suggests:
pn  cicero 
ii  espeak 1.48.04+dfsg-5+b1
ii  mbrola-ee1 [mbrola-voice]  0.0.20020407-1
ii  mbrola-en1 [mbrola-voice]  19980910-2
ii  mbrola-es1 [mbrola-voice]  0.0.19980610-2
ii  mbrola-fr4 [mbrola-voice]  0.0.19990521-2
ii  mbrola-us1 [mbrola-voice]  0.3-2
ii  mbrola-us2 [mbrola-voice]  0.1-2
ii  mbrola-us3 [mbrola-voice]  0.1-1

-- no debconf information

No network and update notifications on Gnome desktop

[Mika Hanhijärvi]

Hi

I am using Debian Stretch on both of my laptops. I use Gnome desktop. I 
have installedd all updates available.


For some reason I do not get any network notifications. If I e.g connect 
to wifi network, disconnect from it or if the connection just gets  
disconnected for some reason then I do not get any notification. That is 
not good.


 Notifications are activated in the Gnome settings. Network application 
notifications are also activated. I have activated both sound alerts and 
notification banners.  I get no sound alerts and no notification 
banners. The same happens on both of my laptops.


I am blind so it is difficult for me to try to solve this. I have no 
idea in which package the problem is.


I have noticed one thing. When I go to Network's notification settings 
(Gnome desktop's settings: Settings->Notifications->Network)and switch 
the notification banner on or o ff then Orca says "Not pressed Not 
pressed" or "Pressed Pressed". So it says two times "Not pressed" or 
"Pressed". The does not happen if I switch notifacation banners on or 
off for some other application, it happens only if I change Network's 
notification settings. Maybe this is a sign of bug somewhere.


I do get e.g e-mail notifications from Mailnag etc.

Similarly I also do not get anysoftware update notifications. When there 
is updates available I do not get any notification. I have noticed that 
even  if there really is updates available I get no notification about 
that. It does not seem to matter if my computer is connected to wifi or 
mobile broadband. The same happens on both of my laptops. This is not 
good at all.


There really should be both network and update notifications, those are 
important part of desktop.


I do not know if it somehow causes problems that I have both Gnome and 
Mate desktop installed. I really do not know how could that cause the 
problem, and as I said I do get e.g e-mail notifications from Mailnag I 
will most likely uninstall Mate at some point because I like Gnome more. 
I do not really use Mate .


Any idea what is wrong? Thanks in advance.

Bug#608056: kaffeine: crashes on startup

[Mika Hanhijärvi]

Package: kaffeine
Version: 1.0-2
Severity: grave
Tags: squeeze
Justification: renders package unusable

I have just upgraded from Lenny to Squeeze. In Lenny Kaffeine worked
just fine, but in Squeeze when I try to run kaffeine it's window opens
but then Kaffeine crashes.

When Kaffeine is run from the commandline it outputa this:

mik...@miksuhdesktop:~$ kaffeine(15813) DvbManager::readDeviceConfigs:
can't
open /home/miksuh/.kde/share/apps/kaffeine/config.dvb
mik...@miksuhdesktop:~$ KCrash: Application 'kaffeine-xbu' crashing...
sock_file=/home/miksuh/.kde/socket-miksuhDesktop/kdeinit4__0

Here is information from the the crash information dialog:

Application: Kaffeine (kaffeine-xbu), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5a39710 (LWP 15815))]

Thread 4 (Thread 0xb19abb70 (LWP 15817)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb5eac482 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0xb6071e64 in __pthread_cond_timedwait (cond=0x9c32ee8,
mutex=0x9c32ed0,
abstime=0xb19ab320) at forward.c:152
#3  0xb762cbdf in metronom_sync_loop (this=0x9c32e88) at metronom.c:870
#4  0xb5ea7955 in start_thread (arg=0xb19abb70) at pthread_create.c:300
#5  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb1037b70 (LWP 15818)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb6057696 in *__GI___poll (fds=0xb60daff4, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb116b6b2 in ?? () from /usr/lib/libpulse.so.0
#3  0xb11583d9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0xb1159c43 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0xb1159d14 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0xb116b463 in ?? () from /usr/lib/libpulse.so.0
#7  0xb112c322 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8  0xb5ea7955 in start_thread (arg=0xb1037b70) at pthread_create.c:300
#9  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xac835b70 (LWP 15819)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb5eabf7f in __pthread_cond_wait (cond=0x9c40118, mutex=0x9c40100)
at
pthread_cond_wait.c:153
#2  0xb6071e0d in __pthread_cond_wait (cond=0x9c40118, mutex=0x9c40100)
at
forward.c:139
#3  0xb763d87e in fifo_peek_int (this_gen=0x9c3ea08) at audio_out.c:348
#4  fifo_peek (this_gen=0x9c3ea08) at audio_out.c:388
#5  ao_loop (this_gen=0x9c3ea08) at audio_out.c:1015
#6  0xb5ea7955 in start_thread (arg=0xac835b70) at pthread_create.c:300
#7  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb5a39710 (LWP 15815)):
[KCrash Handler]
#6  0xabeeb29c in XF86DRIQueryExtension () from /usr/lib/libGL.so.1
#7  0x000f in ?? ()



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kaffeine depends on:
ii  kdebase-runtime   4:4.4.5-1  runtime components from the
offici
ii  libc6 2.11.2-7   Embedded GNU C Library:
Shared lib
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libkdecore5   4:4.4.5-2  the KDE Platform Core
Library
ii  libkdeui5 4:4.4.5-2  the KDE Platform User
Interface Li
ii  libkfile4 4:4.4.5-2  the File Selection Dialog
Library 
ii  libkio5   4:4.4.5-2  the Network-enabled File
Managemen
ii  libqt4-dbus   4:4.6.3-4  Qt 4 D-Bus module
ii  libqt4-network4:4.6.3-4  Qt 4 network module
ii  libqt4-sql4:4.6.3-4  Qt 4 SQL module
ii  libqt4-sql-sqlite 4:4.6.3-4  Qt 4 SQLite 3 database
driver
ii  libqt4-svg4:4.6.3-4  Qt 4 SVG module
ii  libqt4-xml4:4.6.3-4  Qt 4 XML module
ii  libqtcore44:4.6.3-4  Qt 4 core module
ii  libqtgui4 4:4.6.3-4  Qt 4 GUI module
ii  libsolid4 4:4.4.5-2  Solid Library for KDE
Platform
ii  libstdc++64.4.5-8The GNU Standard C++
Library v3
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libxine1  1.1.19-2   the xine video/media player
librar
ii  libxine1-ffmpeg   1.1.19-2   MPEG-related plugins for
libxine1
ii  libxine1-x1.1.19-2   X desktop video output
plugins for
ii  libxss1   1:1.2.0-2  X11 Screen Saver extension
library

kaffeine recommends no packages.

Versions of packages kaffeine suggests:
ii  libdvdcss21.2.10-0.3 Simple foundation for
reading DVDs

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact 

[Pkg-kde-extras] Bug#608056: kaffeine: crashes on startup

[Mika Hanhijärvi]

Package: kaffeine
Version: 1.0-2
Severity: grave
Tags: squeeze
Justification: renders package unusable

I have just upgraded from Lenny to Squeeze. In Lenny Kaffeine worked
just fine, but in Squeeze when I try to run kaffeine it's window opens
but then Kaffeine crashes.

When Kaffeine is run from the commandline it outputa this:

mik...@miksuhdesktop:~$ kaffeine(15813) DvbManager::readDeviceConfigs:
can't
open /home/miksuh/.kde/share/apps/kaffeine/config.dvb
mik...@miksuhdesktop:~$ KCrash: Application 'kaffeine-xbu' crashing...
sock_file=/home/miksuh/.kde/socket-miksuhDesktop/kdeinit4__0

Here is information from the the crash information dialog:

Application: Kaffeine (kaffeine-xbu), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5a39710 (LWP 15815))]

Thread 4 (Thread 0xb19abb70 (LWP 15817)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb5eac482 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0xb6071e64 in __pthread_cond_timedwait (cond=0x9c32ee8,
mutex=0x9c32ed0,
abstime=0xb19ab320) at forward.c:152
#3  0xb762cbdf in metronom_sync_loop (this=0x9c32e88) at metronom.c:870
#4  0xb5ea7955 in start_thread (arg=0xb19abb70) at pthread_create.c:300
#5  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb1037b70 (LWP 15818)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb6057696 in *__GI___poll (fds=0xb60daff4, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb116b6b2 in ?? () from /usr/lib/libpulse.so.0
#3  0xb11583d9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0xb1159c43 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0xb1159d14 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0xb116b463 in ?? () from /usr/lib/libpulse.so.0
#7  0xb112c322 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8  0xb5ea7955 in start_thread (arg=0xb1037b70) at pthread_create.c:300
#9  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xac835b70 (LWP 15819)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb5eabf7f in __pthread_cond_wait (cond=0x9c40118, mutex=0x9c40100)
at
pthread_cond_wait.c:153
#2  0xb6071e0d in __pthread_cond_wait (cond=0x9c40118, mutex=0x9c40100)
at
forward.c:139
#3  0xb763d87e in fifo_peek_int (this_gen=0x9c3ea08) at audio_out.c:348
#4  fifo_peek (this_gen=0x9c3ea08) at audio_out.c:388
#5  ao_loop (this_gen=0x9c3ea08) at audio_out.c:1015
#6  0xb5ea7955 in start_thread (arg=0xac835b70) at pthread_create.c:300
#7  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb5a39710 (LWP 15815)):
[KCrash Handler]
#6  0xabeeb29c in XF86DRIQueryExtension () from /usr/lib/libGL.so.1
#7  0x000f in ?? ()



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kaffeine depends on:
ii  kdebase-runtime   4:4.4.5-1  runtime components from the
offici
ii  libc6 2.11.2-7   Embedded GNU C Library:
Shared lib
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libkdecore5   4:4.4.5-2  the KDE Platform Core
Library
ii  libkdeui5 4:4.4.5-2  the KDE Platform User
Interface Li
ii  libkfile4 4:4.4.5-2  the File Selection Dialog
Library 
ii  libkio5   4:4.4.5-2  the Network-enabled File
Managemen
ii  libqt4-dbus   4:4.6.3-4  Qt 4 D-Bus module
ii  libqt4-network4:4.6.3-4  Qt 4 network module
ii  libqt4-sql4:4.6.3-4  Qt 4 SQL module
ii  libqt4-sql-sqlite 4:4.6.3-4  Qt 4 SQLite 3 database
driver
ii  libqt4-svg4:4.6.3-4  Qt 4 SVG module
ii  libqt4-xml4:4.6.3-4  Qt 4 XML module
ii  libqtcore44:4.6.3-4  Qt 4 core module
ii  libqtgui4 4:4.6.3-4  Qt 4 GUI module
ii  libsolid4 4:4.4.5-2  Solid Library for KDE
Platform
ii  libstdc++64.4.5-8The GNU Standard C++
Library v3
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libxine1  1.1.19-2   the xine video/media player
librar
ii  libxine1-ffmpeg   1.1.19-2   MPEG-related plugins for
libxine1
ii  libxine1-x1.1.19-2   X desktop video output
plugins for
ii  libxss1   1:1.2.0-2  X11 Screen Saver extension
library

kaffeine recommends no packages.

Versions of packages kaffeine suggests:
ii  libdvdcss21.2.10-0.3 Simple foundation for
reading DVDs

-- no debconf information




___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org

Bug#608056: kaffeine: crashes on startup

[Mika Hanhijärvi]

Package: kaffeine
Version: 1.0-2
Severity: grave
Tags: squeeze
Justification: renders package unusable

I have just upgraded from Lenny to Squeeze. In Lenny Kaffeine worked
just fine, but in Squeeze when I try to run kaffeine it's window opens
but then Kaffeine crashes.

When Kaffeine is run from the commandline it outputa this:

mik...@miksuhdesktop:~$ kaffeine(15813) DvbManager::readDeviceConfigs:
can't
open /home/miksuh/.kde/share/apps/kaffeine/config.dvb
mik...@miksuhdesktop:~$ KCrash: Application 'kaffeine-xbu' crashing...
sock_file=/home/miksuh/.kde/socket-miksuhDesktop/kdeinit4__0

Here is information from the the crash information dialog:

Application: Kaffeine (kaffeine-xbu), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5a39710 (LWP 15815))]

Thread 4 (Thread 0xb19abb70 (LWP 15817)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb5eac482 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0xb6071e64 in __pthread_cond_timedwait (cond=0x9c32ee8,
mutex=0x9c32ed0,
abstime=0xb19ab320) at forward.c:152
#3  0xb762cbdf in metronom_sync_loop (this=0x9c32e88) at metronom.c:870
#4  0xb5ea7955 in start_thread (arg=0xb19abb70) at pthread_create.c:300
#5  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb1037b70 (LWP 15818)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb6057696 in *__GI___poll (fds=0xb60daff4, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb116b6b2 in ?? () from /usr/lib/libpulse.so.0
#3  0xb11583d9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0xb1159c43 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0xb1159d14 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0xb116b463 in ?? () from /usr/lib/libpulse.so.0
#7  0xb112c322 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8  0xb5ea7955 in start_thread (arg=0xb1037b70) at pthread_create.c:300
#9  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xac835b70 (LWP 15819)):
#0  0xb77bc424 in __kernel_vsyscall ()
#1  0xb5eabf7f in __pthread_cond_wait (cond=0x9c40118, mutex=0x9c40100)
at
pthread_cond_wait.c:153
#2  0xb6071e0d in __pthread_cond_wait (cond=0x9c40118, mutex=0x9c40100)
at
forward.c:139
#3  0xb763d87e in fifo_peek_int (this_gen=0x9c3ea08) at audio_out.c:348
#4  fifo_peek (this_gen=0x9c3ea08) at audio_out.c:388
#5  ao_loop (this_gen=0x9c3ea08) at audio_out.c:1015
#6  0xb5ea7955 in start_thread (arg=0xac835b70) at pthread_create.c:300
#7  0xb6064e7e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb5a39710 (LWP 15815)):
[KCrash Handler]
#6  0xabeeb29c in XF86DRIQueryExtension () from /usr/lib/libGL.so.1
#7  0x000f in ?? ()



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kaffeine depends on:
ii  kdebase-runtime   4:4.4.5-1  runtime components from the
offici
ii  libc6 2.11.2-7   Embedded GNU C Library:
Shared lib
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libkdecore5   4:4.4.5-2  the KDE Platform Core
Library
ii  libkdeui5 4:4.4.5-2  the KDE Platform User
Interface Li
ii  libkfile4 4:4.4.5-2  the File Selection Dialog
Library 
ii  libkio5   4:4.4.5-2  the Network-enabled File
Managemen
ii  libqt4-dbus   4:4.6.3-4  Qt 4 D-Bus module
ii  libqt4-network4:4.6.3-4  Qt 4 network module
ii  libqt4-sql4:4.6.3-4  Qt 4 SQL module
ii  libqt4-sql-sqlite 4:4.6.3-4  Qt 4 SQLite 3 database
driver
ii  libqt4-svg4:4.6.3-4  Qt 4 SVG module
ii  libqt4-xml4:4.6.3-4  Qt 4 XML module
ii  libqtcore44:4.6.3-4  Qt 4 core module
ii  libqtgui4 4:4.6.3-4  Qt 4 GUI module
ii  libsolid4 4:4.4.5-2  Solid Library for KDE
Platform
ii  libstdc++64.4.5-8The GNU Standard C++
Library v3
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libxine1  1.1.19-2   the xine video/media player
librar
ii  libxine1-ffmpeg   1.1.19-2   MPEG-related plugins for
libxine1
ii  libxine1-x1.1.19-2   X desktop video output
plugins for
ii  libxss1   1:1.2.0-2  X11 Screen Saver extension
library

kaffeine recommends no packages.

Versions of packages kaffeine suggests:
ii  libdvdcss21.2.10-0.3 Simple foundation for
reading DVDs

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact 

Bug#605348: upgrade-reports: Lenny-Squeeze upgrade FAILED - dependency cycle in openoffice.org-common

[Mika Hanhijärvi]

Package: upgrade-reports
Severity: important


I just tried to upgrade my desktop PC from Lenny to Squeeze. Upgrade 
failed with error:

'E:Couldn't configure pre-depend openoffice.org-common for 
openoffice.org-voikko, probably a dependency cycle.'




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#605349: Lenny-Squeeze upgrade FAILED - dependency cycle in openoffice.org-common

[Mika Hanhijärvi]

Package: openoffice.org-common
Severity: important


I just tried to upgrade my desktop PC from Lenny to Squeeze. Upgrade 
failed with error:

'E:Couldn't configure pre-depend openoffice.org-common for 
openoffice.org-voikko, probably a dependency cycle.'




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#605349: Lenny-Squeeze upgrade FAILED - dependency cycle in openoffice.org-common

[Mika Hanhijärvi]

Package: openoffice.org-common
Severity: important


I just tried to upgrade my desktop PC from Lenny to Squeeze. Upgrade 
failed with error:

'E:Couldn't configure pre-depend openoffice.org-common for 
openoffice.org-voikko, probably a dependency cycle.'




-- 
To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/129100.18906.7.ca...@a91-152-161-10.elisa-laajakaista.fi

Bug#493352: Still not fixed

[Mika Hanhijärvi]

I don't understand why this bug was not fixed in Lenny. Lenny has now
broken gdebi-gtk. There sure was enough time to fix this bug. The bug
was originally reported in august. I remimded about this last time in
november. Simple patch which fixes the problem has been available long
time too. 

I have to say that if you are not interested to fix the bugs then you
should let someone else maintain the package.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Sun, 2009-02-08 at 14:14 +1100, Jonny Noog wrote:
 Perhaps you could try setting up your Device section in your xorg.conf 
 like mine (my xorg.conf is attached to a previous message) and then 
 comment out the Textured2D option?

Well I think I'll try that today and report if it helped. I doubt it as
i said earlier, but after testing we know it for sure.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Sun, 2009-02-08 at 14:14 +1100, Jonny Noog wrote:
 Perhaps you could try setting up your Device section in your xorg.conf 
 like mine (my xorg.conf is attached to a previous message) and then 
 comment out the Textured2D option?

Well I think I'll try that today and report if it helped. I doubt it as
i said earlier, but after testing we know it for sure.




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Sun, 2009-02-08 at 14:14 +1100, Jonny Noog wrote:
 Perhaps you could try setting up your Device section in your xorg.conf 
 like mine (my xorg.conf is attached to a previous message) and then 
 comment out the Textured2D option?

Well because clean xorg.conf created by aticonfig --initial does not
work I find it hard to believe that any extra tweaking like in your
xorg.conf would help because fglrx 8-7-3 did not need it. And I don't
even have the same gfx chip you have..




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Sun, 2009-02-08 at 14:14 +1100, Jonny Noog wrote:
 Perhaps you could try setting up your Device section in your xorg.conf 
 like mine (my xorg.conf is attached to a previous message) and then 
 comment out the Textured2D option?

Well because clean xorg.conf created by aticonfig --initial does not
work I find it hard to believe that any extra tweaking like in your
xorg.conf would help because fglrx 8-7-3 did not need it. And I don't
even have the same gfx chip you have..




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Sun, 2009-02-08 at 09:35 +1100, Jonny Noog wrote:
 Hi Patrick,
 
 I commented out the line:
 
 Option Textured2D True
 
 in the Device section of my xorg.conf, rebooted and it works!!! Xorg 
 does not crash! So it looks like my Mobility X1400 is much happier with 
 those settings and the 1:9-1-1 driver. 

Lucky you. I don't have Textured2D -option in my xorg.conf, never had.
And X does not work...





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Sun, 2009-02-08 at 09:35 +1100, Jonny Noog wrote:
 Hi Patrick,
 
 I commented out the line:
 
 Option Textured2D True
 
 in the Device section of my xorg.conf, rebooted and it works!!! Xorg 
 does not crash! So it looks like my Mobility X1400 is much happier with 
 those settings and the 1:9-1-1 driver. 

Lucky you. I don't have Textured2D -option in my xorg.conf, never had.
And X does not work...





-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Thu, 2009-02-05 at 08:30 +0100, Patrick Matthäi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Mika Hanhijärvi schrieb:
  On Tue, 2009-02-03 at 20:02 +0100, Patrick Matthäi wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Patrick Matthäi schrieb:
  I talked about this issue with one release manager.
  As AMD states this issue is fixed with the 9.1 release, I should package
  this release today and upload it to experimental (but it will not have
  xserver-xorg 1.6 support).
 
  The problem is, that I do not have those hardware where it segfaults, so
  I need your responses.
 
  I will mail you again this evening.
 
  Okay it is still at uploading but should be finished in 20 minutes.
 
  1:9-1-1 will be in experimental and for the backporters to lenny/sid you
  can then also get it here:
 
  http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
  It may also fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513208
  Would be nice if someone could test it.
 
  Bye and thanks.
 
  
  I would like to try that new fglrx driver, but in the experimental there
  is only amd64 packages. I run 32bit Debian (i386) on 64 bit computer, so
  i can't test that driver...
  
 
 Try something like:
 
 # apt-get install pbuilder devscripts
 
 # dget http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
 # mkdir result
 
 # pbuilder --create --basetgz lenny.tgz --distribution lenny
 
 # pbuilder --build --basetgz lenny.tgz --buildresult result/
 fglrx-driver_9-1-1.dsc
 
 
 Then fglrx should build and you will find the debs in result/.

Hi !!

Ok, I'll try that today. But unfortunately I'm quite sure it wont
work :( 

I installed latest fglrx driver yesterday. I used ATI installer which
generated Debian packages. When I installed those packages I got again
the same result: corrupted screen and crash...

I attached my xorg.conf, maybe you can see some problems in it. In that
case I just don't understand why fglrx 8-7-3 and earlier works just
fine, but 8-12-4 and later versions don't..

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type man /etc/X11/xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section Files
FontPath/usr/share/fonts/X11/misc
FontPath/usr/X11R6/lib/X11/fonts/misc
FontPath/usr/share/fonts/X11/cyrillic
FontPath/usr/X11R6/lib/X11/fonts/cyrillic
FontPath/usr/share/fonts/X11/100dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/share/fonts/X11/75dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/share/fonts/X11/Type1
FontPath/usr/X11R6/lib/X11/fonts/Type1
FontPath/usr/share/fonts/X11/100dpi
FontPath/usr/X11R6/lib/X11/fonts/100dpi
FontPath/usr/share/fonts/X11/75dpi
FontPath/usr/X11R6/lib/X11/fonts/75dpi
# path to defoma fonts
FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
EndSection

Section Module
Loadi2c
Loadbitmap
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Loadint10
Loadvbe
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  CoreKeyboard
Option  XkbRules  xorg
Option  XkbModel  pc105
Option  XkbLayout fi
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/input/mice
Option  Protocol  ImPS/2
Option  Emulate3Buttons   true
EndSection

Section Device
Identifier  ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
Driver  fglrx
BusID   PCI:1:5:0
EndSection

Section Monitor
Identifier  DELL P1110
Option  DPMS
DisplaySize 400 300 
EndSection

Section Screen
Identifier  Default Screen
Device  ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
Monitor DELL P1110
DefaultDepth24
SubSection Display
Depth   1
Modes   1600x1200 1280x1024 1152x864

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

Just a bit more information:

computer: HP dx5150sff
gfx: ATI Radeon Xpress 200 (integrated)

lspci says (I already sent that full lpci -vv output earlier):
01:05.0 VGA compatible controller: ATI Technologies Inc RS480 [Radeon
Xpress 200G Series]
01:05.1 Display controller: ATI Technologies Inc Radeon Xpress Series
(RS480)





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Thu, 2009-02-05 at 08:30 +0100, Patrick Matthäi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Mika Hanhijärvi schrieb:
  On Tue, 2009-02-03 at 20:02 +0100, Patrick Matthäi wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Patrick Matthäi schrieb:
  I talked about this issue with one release manager.
  As AMD states this issue is fixed with the 9.1 release, I should package
  this release today and upload it to experimental (but it will not have
  xserver-xorg 1.6 support).
 
  The problem is, that I do not have those hardware where it segfaults, so
  I need your responses.
 
  I will mail you again this evening.
 
  Okay it is still at uploading but should be finished in 20 minutes.
 
  1:9-1-1 will be in experimental and for the backporters to lenny/sid you
  can then also get it here:
 
  http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
  It may also fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513208
  Would be nice if someone could test it.
 
  Bye and thanks.
 
  
  I would like to try that new fglrx driver, but in the experimental there
  is only amd64 packages. I run 32bit Debian (i386) on 64 bit computer, so
  i can't test that driver...
  
 
 Try something like:
 
 # apt-get install pbuilder devscripts
 
 # dget http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
 # mkdir result
 
 # pbuilder --create --basetgz lenny.tgz --distribution lenny
 
 # pbuilder --build --basetgz lenny.tgz --buildresult result/
 fglrx-driver_9-1-1.dsc
 
 
 Then fglrx should build and you will find the debs in result/.

Ok,, I did try that. I did build the fglrx 9.1 driver using pbuilder. I
installed all the packages it created. And no, it did not help. X still
does not work. X still hangs, I still get corrupted screen and I still
can't go to console.. 

There is one difference though. When I'm using 9.1 driver I don't see
this error in the Xorg.0.log anymore:


...
Fatal server error:
Caught signal 11.  Server aborting


Now end of the Xorg.0.log looks like this:


(II) LoadModule: fglrxdrm
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(==) fglrx(0): Capabilities: 0x
(==) fglrx(0): CapabilitiesEx: 0x
(==) fglrx(0): cpuFlags: 0x401f
(==) fglrx(0): OpenGL ClientDriverName: fglrx_dri.so


I have attached the full Xorg.0.log.

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux Miksuh-desktop 2.6.26-1-686 #1 SMP Sat Jan 10 
18:29:31 UTC 2009 i686
Build Date: 09 January 2009  02:57:16AM
 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Fri Feb  6 18:02:29 2009
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor DELL P1110
(**) |   |--Device ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
(**) |--Input Device Generic Keyboard
(**) |--Input Device Configured Mouse
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist.
Entry deleted from font path.
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist.
Entry deleted from font path.
(==) Including the default font path 
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/cyrillic,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Fri, 2009-02-06 at 14:08 +0100, Patrick Matthäi wrote:

 Hmm may you test please following:
 
 # mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
 # touch /etc/X11/xorg.conf
 # aticonfig --initial

I did try it, and it did not help. I still get the same result no matter
if I use my original xorg.conf or xorg.xonf created by aticonfig
--initial. Xorg.0.log looks a bit different, but not much. I have again
attached it and also xorg.conf



X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux Miksuh-desktop 2.6.26-1-686 #1 SMP Sat Jan 10 
18:29:31 UTC 2009 i686
Build Date: 09 January 2009  02:57:16AM
 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Fri Feb  6 17:35:46 2009
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout aticonfig Layout
(**) |--Screen aticonfig-Screen[0]-0 (0)
(**) |   |--Monitor aticonfig-Monitor[0]-0
(**) |   |--Device aticonfig-Device[0]-0
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to /etc/X11/rgb
(==) ModulePath set to /usr/lib/xorg/modules
(==) |--Input Device default pointer
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81e38c0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 2.0
X.Org XInput driver : 2.0
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: pcidata
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor=X.Org Foundation
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1002,5950 card 103c,3009 rev 10 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1002,5a3f card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:05:0: chip 1002,5a37 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:12:0: chip 1002,4379 card 103c,3009 rev 00 class 01,01,8f hdr 00
(II) PCI: 00:13:0: chip 1002,4374 card 103c,3009 rev 00 class 0c,03,10 hdr 80
(II) PCI: 00:13:1: chip 1002,4375 card 103c,3009 rev 00 class 0c,03,10 hdr 00
(II) PCI: 00:13:2: chip 1002,4373 card 103c,3009 rev 00 class 0c,03,20 hdr 00
(II) PCI: 00:14:0: chip 1002,4372 card 103c,3009 rev 11 class 0c,05,00 hdr 80
(II) PCI: 00:14:1: chip 1002,4376 card 103c,3009 rev 00 class 01,01,82 hdr 00
(II) PCI: 00:14:3: chip 1002,4377 card 103c,3009 rev 00 class 06,01,00 hdr 80
(II) PCI: 00:14:4: chip 1002,4371 card , rev 00 class 06,04,01 hdr 81
(II) PCI: 00:14:5: chip 1002,4370 card 103c,3009 rev 02 class 04,01,00 hdr 80
(II) PCI: 00:18:0: chip 1022,1100 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 01:05:0: chip 1002,5954 card 103c,3009 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:05:1: chip 1002,5854 card 103c,3008 rev 00 class 03,80,00 hdr 00
(II) PCI: 02:00:0: chip 14e4,1677 card 103c,3009 rev 20 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,3), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1  0   0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1  0   0xc000 - 0xcfff (0x1000) IX[B]
(II) Bus 1 non-prefetchable memory range:
[0] -1  0   0xfda0 - 0xfdaf (0x10) 

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Thu, 2009-02-05 at 08:30 +0100, Patrick Matthäi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Mika Hanhijärvi schrieb:
  On Tue, 2009-02-03 at 20:02 +0100, Patrick Matthäi wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Patrick Matthäi schrieb:
  I talked about this issue with one release manager.
  As AMD states this issue is fixed with the 9.1 release, I should package
  this release today and upload it to experimental (but it will not have
  xserver-xorg 1.6 support).
 
  The problem is, that I do not have those hardware where it segfaults, so
  I need your responses.
 
  I will mail you again this evening.
 
  Okay it is still at uploading but should be finished in 20 minutes.
 
  1:9-1-1 will be in experimental and for the backporters to lenny/sid you
  can then also get it here:
 
  http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
  It may also fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513208
  Would be nice if someone could test it.
 
  Bye and thanks.
 
  
  I would like to try that new fglrx driver, but in the experimental there
  is only amd64 packages. I run 32bit Debian (i386) on 64 bit computer, so
  i can't test that driver...
  
 
 Try something like:
 
 # apt-get install pbuilder devscripts
 
 # dget http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
 # mkdir result
 
 # pbuilder --create --basetgz lenny.tgz --distribution lenny
 
 # pbuilder --build --basetgz lenny.tgz --buildresult result/
 fglrx-driver_9-1-1.dsc
 
 
 Then fglrx should build and you will find the debs in result/.

Hi !!

Ok, I'll try that today. But unfortunately I'm quite sure it wont
work :( 

I installed latest fglrx driver yesterday. I used ATI installer which
generated Debian packages. When I installed those packages I got again
the same result: corrupted screen and crash...

I attached my xorg.conf, maybe you can see some problems in it. In that
case I just don't understand why fglrx 8-7-3 and earlier works just
fine, but 8-12-4 and later versions don't..

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type man /etc/X11/xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section Files
FontPath/usr/share/fonts/X11/misc
FontPath/usr/X11R6/lib/X11/fonts/misc
FontPath/usr/share/fonts/X11/cyrillic
FontPath/usr/X11R6/lib/X11/fonts/cyrillic
FontPath/usr/share/fonts/X11/100dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/share/fonts/X11/75dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/share/fonts/X11/Type1
FontPath/usr/X11R6/lib/X11/fonts/Type1
FontPath/usr/share/fonts/X11/100dpi
FontPath/usr/X11R6/lib/X11/fonts/100dpi
FontPath/usr/share/fonts/X11/75dpi
FontPath/usr/X11R6/lib/X11/fonts/75dpi
# path to defoma fonts
FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
EndSection

Section Module
Loadi2c
Loadbitmap
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Loadint10
Loadvbe
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  CoreKeyboard
Option  XkbRules  xorg
Option  XkbModel  pc105
Option  XkbLayout fi
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/input/mice
Option  Protocol  ImPS/2
Option  Emulate3Buttons   true
EndSection

Section Device
Identifier  ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
Driver  fglrx
BusID   PCI:1:5:0
EndSection

Section Monitor
Identifier  DELL P1110
Option  DPMS
DisplaySize 400 300 
EndSection

Section Screen
Identifier  Default Screen
Device  ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
Monitor DELL P1110
DefaultDepth24
SubSection Display
Depth   1
Modes   1600x1200 1280x1024 1152x864

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

Just a bit more information:

computer: HP dx5150sff
gfx: ATI Radeon Xpress 200 (integrated)

lspci says (I already sent that full lpci -vv output earlier):
01:05.0 VGA compatible controller: ATI Technologies Inc RS480 [Radeon
Xpress 200G Series]
01:05.1 Display controller: ATI Technologies Inc Radeon Xpress Series
(RS480)





-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Thu, 2009-02-05 at 08:30 +0100, Patrick Matthäi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Mika Hanhijärvi schrieb:
  On Tue, 2009-02-03 at 20:02 +0100, Patrick Matthäi wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Patrick Matthäi schrieb:
  I talked about this issue with one release manager.
  As AMD states this issue is fixed with the 9.1 release, I should package
  this release today and upload it to experimental (but it will not have
  xserver-xorg 1.6 support).
 
  The problem is, that I do not have those hardware where it segfaults, so
  I need your responses.
 
  I will mail you again this evening.
 
  Okay it is still at uploading but should be finished in 20 minutes.
 
  1:9-1-1 will be in experimental and for the backporters to lenny/sid you
  can then also get it here:
 
  http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
  It may also fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513208
  Would be nice if someone could test it.
 
  Bye and thanks.
 
  
  I would like to try that new fglrx driver, but in the experimental there
  is only amd64 packages. I run 32bit Debian (i386) on 64 bit computer, so
  i can't test that driver...
  
 
 Try something like:
 
 # apt-get install pbuilder devscripts
 
 # dget http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
 # mkdir result
 
 # pbuilder --create --basetgz lenny.tgz --distribution lenny
 
 # pbuilder --build --basetgz lenny.tgz --buildresult result/
 fglrx-driver_9-1-1.dsc
 
 
 Then fglrx should build and you will find the debs in result/.

Ok,, I did try that. I did build the fglrx 9.1 driver using pbuilder. I
installed all the packages it created. And no, it did not help. X still
does not work. X still hangs, I still get corrupted screen and I still
can't go to console.. 

There is one difference though. When I'm using 9.1 driver I don't see
this error in the Xorg.0.log anymore:


...
Fatal server error:
Caught signal 11.  Server aborting


Now end of the Xorg.0.log looks like this:


(II) LoadModule: fglrxdrm
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(==) fglrx(0): Capabilities: 0x
(==) fglrx(0): CapabilitiesEx: 0x
(==) fglrx(0): cpuFlags: 0x401f
(==) fglrx(0): OpenGL ClientDriverName: fglrx_dri.so


I have attached the full Xorg.0.log.

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux Miksuh-desktop 2.6.26-1-686 #1 SMP Sat Jan 10 
18:29:31 UTC 2009 i686
Build Date: 09 January 2009  02:57:16AM
 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Fri Feb  6 18:02:29 2009
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor DELL P1110
(**) |   |--Device ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
(**) |--Input Device Generic Keyboard
(**) |--Input Device Configured Mouse
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist.
Entry deleted from font path.
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist.
Entry deleted from font path.
(WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist.
Entry deleted from font path.
(==) Including the default font path 
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/cyrillic,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Fri, 2009-02-06 at 14:08 +0100, Patrick Matthäi wrote:

 Hmm may you test please following:
 
 # mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
 # touch /etc/X11/xorg.conf
 # aticonfig --initial

I did try it, and it did not help. I still get the same result no matter
if I use my original xorg.conf or xorg.xonf created by aticonfig
--initial. Xorg.0.log looks a bit different, but not much. I have again
attached it and also xorg.conf



X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux Miksuh-desktop 2.6.26-1-686 #1 SMP Sat Jan 10 
18:29:31 UTC 2009 i686
Build Date: 09 January 2009  02:57:16AM
 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Fri Feb  6 17:35:46 2009
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout aticonfig Layout
(**) |--Screen aticonfig-Screen[0]-0 (0)
(**) |   |--Monitor aticonfig-Monitor[0]-0
(**) |   |--Device aticonfig-Device[0]-0
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to /etc/X11/rgb
(==) ModulePath set to /usr/lib/xorg/modules
(==) |--Input Device default pointer
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81e38c0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 2.0
X.Org XInput driver : 2.0
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: pcidata
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor=X.Org Foundation
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1002,5950 card 103c,3009 rev 10 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1002,5a3f card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:05:0: chip 1002,5a37 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:12:0: chip 1002,4379 card 103c,3009 rev 00 class 01,01,8f hdr 00
(II) PCI: 00:13:0: chip 1002,4374 card 103c,3009 rev 00 class 0c,03,10 hdr 80
(II) PCI: 00:13:1: chip 1002,4375 card 103c,3009 rev 00 class 0c,03,10 hdr 00
(II) PCI: 00:13:2: chip 1002,4373 card 103c,3009 rev 00 class 0c,03,20 hdr 00
(II) PCI: 00:14:0: chip 1002,4372 card 103c,3009 rev 11 class 0c,05,00 hdr 80
(II) PCI: 00:14:1: chip 1002,4376 card 103c,3009 rev 00 class 01,01,82 hdr 00
(II) PCI: 00:14:3: chip 1002,4377 card 103c,3009 rev 00 class 06,01,00 hdr 80
(II) PCI: 00:14:4: chip 1002,4371 card , rev 00 class 06,04,01 hdr 81
(II) PCI: 00:14:5: chip 1002,4370 card 103c,3009 rev 02 class 04,01,00 hdr 80
(II) PCI: 00:18:0: chip 1022,1100 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 01:05:0: chip 1002,5954 card 103c,3009 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:05:1: chip 1002,5854 card 103c,3008 rev 00 class 03,80,00 hdr 00
(II) PCI: 02:00:0: chip 14e4,1677 card 103c,3009 rev 20 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,3), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1  0   0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1  0   0xc000 - 0xcfff (0x1000) IX[B]
(II) Bus 1 non-prefetchable memory range:
[0] -1  0   0xfda0 - 0xfdaf (0x10) 

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Tue, 2009-01-27 at 18:26 +0100, Patrick Matthäi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Mika Hanhijärvi schrieb:
  On Tue, 2009-01-27 at 14:43 +0100, Bertrand Marc wrote:
  Hi,
 
  And what version of the fglrx-module are you using ? Did you compile 
  your own module with module-assistant ?
  
  Yes I did use module-assistant. I did run: # m-a a-i fglrx 
  which did create and install package:
  
  fglrx-kernel-2.6.26-1-686 , version 1:8-12-4+2.6.26-13
  
  When I used that module package fglrx did crash Xorg. 
  
  I know there is prebuild fglrx kernel module packages in the Lenny's
  repository, but AFAIK those are buolt for the fglrx 8-7-3. I did anyway
  try those prebuild packages too after using module-assistant did not
  work. I installed current stock package: fglrx-modules-2.6.26-1-686 ,
  version 2.6.26+8-7-1. but using those packages did not work any better
  than using module-assistant, fglrx did crash Xorg.
  
  By the way, why those prebuilt fglrx kernel module packages were not
  updated at the same time fglrx-driver etc packages were updated? 
 
 They are maintained by the non-free extra kernel team and they are
 uploaded, but not yet in Lenny.
 
 
 Hmm at all this is in an interesting issue.. Could you send us your
 dmesg *after* it crashed, and also lspci -vv

Hi !!

I'm sorry I did not respond to you earlier, I have been a bit busy with
my studies etc.

I have attached output of lspci -vv. I booted to single user mode and
then executed that command.

 .
 Your xorg.conf would be also interesting and did you tried it out yet
 without 3D acceleration?

I did try all of these:

1) I disabled loading dri module from xorg.conf: It did not help
2) I disabled loading dri and glx modules from xorg.conf: it did not
help
3) I uninstalled the fglrx kernel module package: it did not help

So none of those three tests changed anything, xorg still did not work.


00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
Subsystem: Hewlett-Packard Company Device 3009
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR- INTx-
Latency: 64
Region 3: Memory at ignored (64-bit, non-prefetchable)
Kernel modules: ati-agp

00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 99
Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
I/O behind bridge: c000-cfff
Memory behind bridge: fda0-fdaf
Prefetchable memory behind bridge: c800-d7ff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [b0] Subsystem: ATI Technologies Inc RS480 PCI Bridge
Kernel modules: shpchp

00:05.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: d000-dfff
Memory behind bridge: fde0-fdef
Prefetchable memory behind bridge: fdb0-fdbf
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v1) Root Port (Slot-), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 64ns, 
L1 1us
ExtTag+ RBE- FLReset-
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency 
L0 64ns, L1 1us

Bug#513222: [Pkg-fglrx-devel] Bug#513222: fglrx-driver: crashes Xorg

[Mika Hanhijärvi]

On Tue, 2009-02-03 at 20:02 +0100, Patrick Matthäi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Patrick Matthäi schrieb:
  I talked about this issue with one release manager.
  As AMD states this issue is fixed with the 9.1 release, I should package
  this release today and upload it to experimental (but it will not have
  xserver-xorg 1.6 support).
  
  The problem is, that I do not have those hardware where it segfaults, so
  I need your responses.
  
  I will mail you again this evening.
  
 
 Okay it is still at uploading but should be finished in 20 minutes.
 
 1:9-1-1 will be in experimental and for the backporters to lenny/sid you
 can then also get it here:
 
 http://packages.linux-dev.org/fglrx-driver_9-1-1.dsc
 
 It may also fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513208
 Would be nice if someone could test it.
 
 Bye and thanks.
 

I would like to try that new fglrx driver, but in the experimental there
is only amd64 packages. I run 32bit Debian (i386) on 64 bit computer, so
i can't test that driver...




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org