Bug#1002924: yabasic: input and line input throw syntax errors

[Jude DaShiell]

Package: yabasic
Severity: important
X-Debbugs-Cc: dashiellj...@gmail.com

Dear Maintainer,



   * What led up to the situation?
   Wrote a line of code for interpretation.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 ran yabasic ty.bas. line of code was
 input "enter birth year: ",y
   * What was the outcome of this action?
   syntax error  followed by abend.
   * What outcome did you expect instead?
   enter birth year: 




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

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1001016: telegram-desktop backports request

[Jude DaShiell]

telegram-cli was also outdated and may remain so if no longer supported.


On Sat, 4 Dec 2021, Ralf Neubauer wrote:

> Hi Nicholas,
>
> I can second that, everything is fine now! Thank you for the quick reaction!
>
> Just to have it documented somewhere, in one of the out-of-date versions
> I had to click the [Ok] button in the message box multiple times to
> activate the window after having been away for some time. I assume the
> message boxes were stacking, about five or ten exactly one over the
> other. Since the upgrade to 3.1.1 I can't reproduce this any more for
> lack of urgent messages, but the code may still behave the same way if
> it is triggered the next time and it is very confusing for users.
>
> Thank you again,
> Ralf
>
> On Sat, Dec 04, 2021 at 11:13:14AM +, piorunz wrote:
> > Hi Nicholas,
> >
> > That's fantastic, everything works ok now! Thank you!
> >
> > I set up new Firefox profile with Telegram tab just in case, put that in
> > place of old Telegram window, that worked for me for a day, but now I am
> > back to using telegram desktop app. Great work:)
> >
> > On 04/12/2021 10:45, Nicholas Guriev wrote:
> > > Hello!
> > >
> > > On ??, 2021-12-03 at 19:44 +, piorunz wrote:
> > > > Testing has got 3.1.1. I hope bullseye-backports can update it? CC to
> > > > maintainer, Nicholas Guriev! Thanks in advance.
> > >
> > > I have uploaded this version to Backports. It is already available on
> > > mirrors and should work okay.
> > > https://ftp.debian.org/debian/pool/main/t/telegram-desktop/
> > >
> >
> >
> > --
> > With kindest regards, Piotr.
> >
> > ???
> > ??? Debian - The universal operating system
> > ??? https://www.debian.org/
> > ???
>
>

Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

[Jude DaShiell]

What happens to someone who only has a bluetooth keyboard and has a 
bluetooth dongle connected to their computer to use bluetooth 
temporarily since their usb keyboard broke?


On Mon, 3 Jul 2017, Felipe Sateler wrote:


Date: Mon, 3 Jul 2017 10:27:36
From: Felipe Sateler 
To: Antoine Beaupr? ,
debian-accessibil...@lists.debian.org
Cc: Michael Biebl , 805...@bugs.debian.org,
Aurelien Jacobs 
Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP
sink on session start
Resent-Date: Mon,  3 Jul 2017 14:28:34 + (UTC)
Resent-From: debian-accessibil...@lists.debian.org

Adding the a11y list to CC.

Dear a11y team, a short summary for you: Currently, pulseaudio does not
negotiate bluetooth devices the same way it does with alsa devices, with a
result that is undesirable: if the gdm login screen grabs the BT device, it
becomes unavailable in the logged in session. The change being discussed
here is to disable bluetooth in the gdm login screen.

On Mon, Jul 3, 2017 at 10:20 AM, Antoine Beaupr?  wrote:


On 2017-07-03 15:46:20, Michael Biebl wrote:

Am 03.07.2017 um 00:05 schrieb Antoine Beaupr?:

On 2017-07-02 23:43:55, Michael Biebl wrote:

Am 02.07.2017 um 23:36 schrieb Antoine Beaupr?:

On 2017-07-02 23:16:19, Michael Biebl wrote:



Have you tested the workaround from the arch wiki and can you

confirm it

works?


I cannot, unfortunately, test this anymore, as I have disabled the
pulseaudio socket as directed earlier, with:

rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/

pulseaudio.socket


I don't know what that was pointing to, so I can't quite restore that
behavior directly.


That's from the postinst:

UNIT=/usr/lib/systemd/user/pulseaudio.socket
USERUNITDIR=/var/lib/gdm3/.config/systemd/user
if ! [ -L $USERUNITDIR/sockets.target.wants/pulseaudio.socket ]; then
  mkdir -p $USERUNITDIR/sockets.target.wants
  ln -sf $UNIT $USERUNITDIR/sockets.target.wants
fi

You can run that manually or simply re-install the gdm3 package so that
code is run again.


Thanks! I believe I have rolled back the workarounds and implemented the
fix default.pa documented in the Arch wiki. Everything seems to work
normally now, ie. I can correctly connect through A2DP to my bluetooth
speaker.


Since concerns were raised that this might break existing a11y setups, I
don't plan to make an upload with this change.


I don't understand the impact this could have regarding
accessibility. There are, as far as I know, currently no usable way to
have bluetooth audio working at all in the gdm3 login prompt, because
there's no way to associate a device, so there's no loss of
functionality here. But there *is* a loss of functionality for
everyone (*including* screen reader users) *after* the user is logged
in: they cannot correctly configure bluetooth devices!



Bluetooth pairings are global. Once you configured them in your user
session, they will become available to gdm too.




Can we get a better idea of the use case you are worried about here?



Here is where the input of the a11y team would be very appreciated. Is
disabling bluetooth in the login screen likely to cause problem?




To be really clear here, the change I am proposing is the one documented
in the Arch wiki and now also in the Debian wiki:

https://wiki.debian.org/BluetoothUser/a2dp#Workaround_
2:_disable_pulseaudio.27s_bluetooth_in_gdm

which currently consists of adding the following
/var/lib/gdm3/.config/pulse/default.pa file:

#!/usr/bin/pulseaudio -nF
#

# load system wide configuration
.include /etc/pulse/default.pa

### unload driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
  unload-module module-bluetooth-policy
.endif

.ifexists module-bluetooth-discover.so
  unload-module module-bluetooth-discover
.endif

How would this break accessibility?



My own thought is that if your only speakers are BT, how are you going to
have the screen read if there is no BT?




--

Bug#744849: espeakup: usb speakers inaccessible on use and during installation

[Jude DaShiell]

 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  62
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.10
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength 101
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize064
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0001 1.1 root hub
  bcdDevice3.14
  iManufacturer   3 
  iProduct2 
  iSerial 1 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   25
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0002  1x 2 bytes
bInterval 255
[jude@athame ~]$ 
[jude@athame ~]$ speaker-test

speaker-test 1.0.27.2

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Playback open error: -16,Device or resource busy
[jude@athame ~]$ exit
exit

Script done on Sat Apr 19 07:40:22 2014
On Tue, 15 Apr 
2014, Jude DaShiell wrote:

 Package: espeakup
 Version: 1:0.71-14
 Severity: important
 Tags: d-i upstream
 
 Dear Maintainer,
 
 *** Reporter, please consider answering these questions, where appropriate ***
 
* What led up to the situation?  failed modifying configuration to have 
 espeakup use usb speakers on an already installed system and failed to get 
 debian installer espeakup to find usb speakers and use them.
* What exactly did you do (or not do) that was effective (or
  ineffective)?  Tried several modifications of /etc/default/espeakup all 
 failed.  Tried installation using s command at boot prompt too.
* What outcome did you expect instead?  I expected to be able to switch 
 from conventional stereo speakers by modifying configuration file and 
 expected espeakup would find those usb speakers when I tried an install, 
 archlinux has no trouble with this at all  for whatever reason.  Also 
 documentation in /etc/default/espeakup for this case was missing.
 Script started on Thu 10 Apr 2014 06:04:24 AM EDT
 jude@d-216-36-20-9:~$ aplay -L
 null
 Discard all samples (playback) or generate zero samples (capture)
 pulse
 PulseAudio Sound Server
 default:CARD=CK804
 NVidia CK804, NVidia CK804
 Default Audio Device
 sysdefault:CARD=CK804
 NVidia CK804, NVidia CK804
 Default Audio Device
 front:CARD=CK804,DEV=0
 NVidia

Bug#744849: espeakup: usb speakers inaccessible on use and during installation

[Jude DaShiell]

I should have included the asound.conf file alsa created when I chose my 
sound card; it may be useful:
Script started on Sat Apr 19 09:00:46 2014
[jude@athame ~]$ cat /etc/asound.o  .conf
pcm.!default {
type plug
slave.pcm {
type hw
card 1
}
}

ctl.!default {
type hw
card 1
}
[jude@athame ~]$ exit
exit

Script done on Sat Apr 19 09:01:04 2014

jude jdash...@shellworld.net


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

Bug#744849: espeakup: usb speakers inaccessible on use and during installation

[Jude DaShiell]

I will check arch and be back with information later today or tomorrow.  
One thing I forgot to mention is that when this system boots up, the 
first speakers to click on are the large usb speakers and this is no 
different in talkingarch either April 2014 version.  This may turn out 
to be a udev problem in that incorrect rules are being written in those 
files automatically by udev.  I haven't yet mastered udev rules writing 
yet so don't yet do anything to those files until I understand that 
process.

On Thu, 17 Apr 2014, Samuel Thibault wrote:

 Hello,
 
 Jude DaShiell, le Tue 15 Apr 2014 07:31:06 -0400, a ?crit :
  The fact that the debian installer also fails to find and use my usb 
  speakers points at a larger problem though.
 
 Well, not really: the debian installer is a special case of a Debian
 system, things may not work there at all while they would on an
 installed system.
 
  archlinux has no trouble with this at all  for whatever reason.
 
 Perhaps archlinux outputs to all cards at the same time?  Or perhaps by
 luck archlinux gets the USB soundcard as first one?  How does aplay -L
 show up there?
 
 * I expected to be able to switch from conventional stereo speakers
  by modifying configuration file and expected espeakup would find
  those usb speakers when I tried an install, Also documentation in
  /etc/default/espeakup for this case was missing.
 
 I have completed the paragraph:
 
  # To choose audio output on another sound card, uncomment this and set as
 +# appropriate (either a card number or a card name as seen in CARD= alsa
 +# output).
  #
  # export ALSA_CARD=0
 
 Now, that will only be feasible for an installed system.  About
 debian-installer time, I guess we would ideally want to emit the synth
 to all sound cards?  I'm afraid espeakup might just not support this,
 and we'd have to chose a card.  I'm wondering whether we really want to
 provide the user with a way to select it at debian-installer time, just
 like we don't make him select which graphic card should be used.
 
 Samuel
 
 

jude jdash...@shellworld.net


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

Bug#744849: espeakup unusable with usb speakers before and after install

[Jude DaShiell]

I did a little experimenting with speaker-test and aplay -L before 
checking out talkingarch linux.
Commands like:
speaker-test -Dsurround50:CARD=Audio,DEV=0 enter
apparently found a device but errored out complaining about broken 
configuration.  I didn't break any configuration so am wondering if nvidia 
tools somewhere may have broken the configuration now.
Talkingarch when it thinks it found a machine with multiple sound cards 
plays a message and sends a beep through each of what it thinks are sound 
cards and lets the user hit enter to choose that sound card for operation 
and installation later on.  That happens before anything else happens 
after the system loads if archlinux is new on that hardware.



jude jdash...@shellworld.net


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

Bug#744849: espeakup: usb speakers inaccessible on use and during installation

[Jude DaShiell]

Package: espeakup
Version: 1:0.71-14
Severity: important
Tags: d-i upstream

Dear Maintainer,

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

   * What led up to the situation?  failed modifying configuration to have 
espeakup use usb speakers on an already installed system and failed to get 
debian installer espeakup to find usb speakers and use them.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?  Tried several modifications of /etc/default/espeakup all 
failed.  Tried installation using s command at boot prompt too.
   * What outcome did you expect instead?  I expected to be able to switch from 
conventional stereo speakers by modifying configuration file and expected 
espeakup would find those usb speakers when I tried an install, archlinux has 
no trouble with this at all  for whatever reason.  Also documentation in 
/etc/default/espeakup for this case was missing.
Script started on Thu 10 Apr 2014 06:04:24 AM EDT
jude@d-216-36-20-9:~$ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
default:CARD=CK804
NVidia CK804, NVidia CK804
Default Audio Device
sysdefault:CARD=CK804
NVidia CK804, NVidia CK804
Default Audio Device
front:CARD=CK804,DEV=0
NVidia CK804, NVidia CK804
Front speakers
surround40:CARD=CK804,DEV=0
NVidia CK804, NVidia CK804
4.0 Surround output to Front and Rear speakers
surround41:CARD=CK804,DEV=0
NVidia CK804, NVidia CK804
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=CK804,DEV=0
NVidia CK804, NVidia CK804
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=CK804,DEV=0
NVidia CK804, NVidia CK804
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=CK804,DEV=0
NVidia CK804, NVidia CK804
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=CK804,DEV=0
NVidia CK804, NVidia CK804 - IEC958
IEC958 (S/PDIF) Digital Audio Output
default:CARD=Audio
USB Audio, USB Audio
Default Audio Device
sysdefault:CARD=Audio
USB Audio, USB Audio
Default Audio Device
front:CARD=Audio,DEV=0
USB Audio, USB Audio
Front speakers
surround40:CARD=Audio,DEV=0
USB Audio, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=Audio,DEV=0
USB Audio, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Audio,DEV=0
USB Audio, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Audio,DEV=0
USB Audio, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Audio,DEV=0
USB Audio, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Audio,DEV=0
USB Audio, USB Audio
IEC958 (S/PDIF) Digital Audio Output
jude@d-216-36-20-9:~$ exit
Script done on Thu 10 Apr 2014 06:05:21 AM EDT
The script file shows what sound equipment is on this machine and I don't know 
what to extract from here to put in that last export statement in 
/etc/default/espeakup.  The fact that the debian installer also fails to find 
and use my usb speakers points at a larger problem though.

*** End of the template - remove these template lines ***


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

Kernel: Linux 3.13-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages espeakup depends on:
ii  espeak  1.47.11-1
ii  libc6   2.18-4
ii  libespeak1  1.47.11-1

espeakup recommends no packages.

espeakup suggests no packages.

-- Configuration Files:
/etc/default/espeakup changed:
VOICE=en


-- no debconf information

jude jdash...@shellworld.net


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

Bug#735202: bug 735202 status

[Jude DaShiell]

Script started on Sun 16 Mar 2014 06:21:45 AM EDT
jude@d-216-36-20-9:~$ uname -ar
Linux d-216-36-20-9 3.13-1-amd64 #1 SMP Debian 3.13.5-1 (2014-03-04) x86_64 
GNU/Linux
jude@d-216-36-20-9:~$ exit
Script done on Sun 16 Mar 2014 06:21:55 AM EDT
With the kernel version and other recent updates shown above, on this 
hardware so far as I can tell the speakup cut and paste bug has been 
squashed.  I tried a cut and paste operation with this kernel a little 
earlier and the cut and paste worked the way it had worked in earlier 
kernel versions without the crashed systems.

 jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

If that missing dependency is undocumented and also not an mandatory 
automatic install with another package that needs a fix or two.  If 
anyone can test this on a machine with an ensonicq (I think 1370) sound 
card if this bug can't be reproduced, pulseaudio is at least 
participating and may be doing more than that.  Intel sound cards and 
pulseaudio don't get along well and until I learned that, I couldn't 
figure out how pulseaudio routinely failed yet speakup came up working.  
The amd64k machine I have unfortunately has one of the intel junk cards.

On Sun, 2 Feb 2014, Paul Gevers wrote:

 On 02-02-14 11:29, Geoff Shang wrote:
  IMHO, tryign to work around the bug isn't the right approach.  A bug
  that will crash the entire system hard needs to be treated as a bug that
  needs to be fixed.
 
 I agree with you. But a missing dependency can also very well be a bug,
 so I wasn't trying to work around the bug. But indeed, bringing a
 system completely to a halt does hardly look like a missing dependency
 issue.
 
 Paul
 
 
 

jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

Not entirely sure, what's my best bet for installing a readline package 
that is likely to work?

On Sun, 2 Feb 2014, Paul Gevers wrote:

 On 26-01-14 19:28, Geoff Shang wrote:
  It seems to happen when working in more primitive environments with
  no readline.
 
 Triggered by the mail of Jude, do you confirm that installing readline
 prevents this bug from happening? Than indeed adding that as a
 dependency would solve your issue.
 
 Paul
 
 
 

jude jdash...@shellworld.net


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

Bug#735702: speakup crashes debian

[Jude DaShiell]

This bug does not exist in arch linux with their current kernel release.  
So it's possible this bug is unique to debian.



jude jdash...@shellworld.net


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

Bug#735702: speakup crashes debian

[Jude DaShiell]

On another intel celleron machine I have slackware current running.  This 
version has no problem doing mark/cut/paste operations with speakup.  The 
kernel version differs from debian and I'm including the typescript file 
with output of uname -ar on the slackware current machine in this message.  
This should help narrow down the search a little.

Script started on Wed 05 Feb 2014 10:17:24 PM EST
jude@ribs:~$ uname -ar
Linux ribs 3.10.17-smp #2 SMP Wed Oct 23 17:13:14 CDT 2013 i686 Intel(R) 
Celeron(R) CPU 1.80GHz GenuineIntel GNU/Linux
jude@ribs:~$ exit
exit

Script done on Wed 05 Feb 2014 10:17:36 PM EST

jude jdash...@shellworld.net


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

Bug#735702: speakup crashes debian

[Jude DaShiell]

The slackware box with kernel 3.10 on it described earlier has speech 
output happening over a litetalk synthesizer rather than the sound card.  
No slackware install can be done with a sound card as it can be done with 
debian yet so this may implicate pulseaudio and the intel sound card on 
the amd64 athelon k8 machine since all intel sound cards so far as I know 
are single channel architecture and pulseaudio behaves badly with single 
channel architecture sound cards when those get used for screen reader 
speech production.



jude jdash...@shellworld.net


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

Bug#735202: Fwd: speakup freezes when trying to past

[Jude DaShiell]

A little more information that may go a ways to sorting this bug out.  
Although I used a debian speakup talking install to install jessie/sid, 
the installation did not put an ~/.inputrc file in my home directory.  If 
one of those should be in the home directory, what should be in that file 
for speakup to work correctly?  Without ~/.inputrc, unless --edit is 
initialized in some other way the readline library will not be used by 
bash according to the bash man page.



jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

This disagrees with your hypothesis I'll look for a msgid I may not have 
archived that issue of the digest.  Squeeze and wheezy were mentioned in 
that message and I've been running Jessie/sid for quite a while.  The 
motherboard I have in this amd athelon k8 is a southbridge model not a 
more recent northbridge model, I only know this since the builder of 
this computer comes over and cleans it out with compressed air every so 
often and he checked out the hardware in it for me.

On Sun, 2 Feb 2014, Paul Gevers wrote:

 On 01-02-14 22:12, Jude DaShiell wrote:
  I understand this bug existed not much prior to the present kernel version 
  from what I read on the spea...@linux-speakup.org mailing list so this bug 
  was carried into this kernel version from at least one earlier version.  
 
 Do you have an URL or message-id to the discussion that you mean? Does
 this now agree or disagree with my hypothesis?
 
 Paul
 
 
 
 

jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

I haven't got a msgid for that message.

On Sun, 2 Feb 2014, Paul Gevers wrote:

 On 01-02-14 22:12, Jude DaShiell wrote:
  I understand this bug existed not much prior to the present kernel version 
  from what I read on the spea...@linux-speakup.org mailing list so this bug 
  was carried into this kernel version from at least one earlier version.  
 
 Do you have an URL or message-id to the discussion that you mean? Does
 this now agree or disagree with my hypothesis?
 
 Paul
 
 
 
 

jude jdash...@shellworld.net


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

Bug#735202: Info received (Bug#735202: speakup crashes debian)

[Jude DaShiell]

I tried rlfe package and ledit package to get readline functionality 
into the bash shell and neither package had any positive effect on this 
bug situation.  I don't know if a missing readline in a bash shell is 
causing this to happen or not but if so, neither of these packages will 
do the job by themselves.

On Sun, 2 Feb 2014, Debian Bug Tracking System wrote:

 Thank you for the additional information you have supplied regarding
 this Bug report.
 
 This is an automatically generated reply to let you know your message
 has been received.
 
 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.
 
 Your message has been sent to the package maintainer(s):
  Debian Accessibility Team debian-accessibil...@lists.debian.org
 
 If you wish to submit further information on this problem, please
 send it to 735...@bugs.debian.org.
 
 Please do not send mail to ow...@bugs.debian.org unless you wish
 to report a problem with the Bug-tracking system.
 
 

jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

I understand this bug existed not much prior to the present kernel version 
from what I read on the spea...@linux-speakup.org mailing list so this bug 
was carried into this kernel version from at least one earlier version.  
On Sat, 25 Jan 2014, Paul Gevers wrote:

 On 24-01-14 22:24, Jude DaShiell wrote:
  jude@d-216-36-20-9:~$ uname -a
  Linux d-216-36-20-9 3.12-1-amd64 #1 SMP Debian 3.12.6-2 (2013-12-29) x86_64 
  GNU/Linux
 
 I am fully guessing here, but my hypothesis is that the bug is caused by
 the new kernel version scheme, which dropped the patch version, ie.
 3.12 i.s.o 3.12.0.  I don't know where this would come into play though.
 
 Paul
 
 
 

jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

If I run cpanp on this amd64 Athelon k8 machine, I hear readline is 
enabled.  If some other readline package or packages need installing so 
bash uses readline automatically and those packages aren't on this machine 
and working I think those packages need to be made speakup dependencies 
for future versions of speakup. On Sun, 26 Jan 2014, Geoff Shang wrote:

 Hi,
 
 this may not be the same bug, but there has been a long-standing Speakup bug
 that locks up the machine.  I've seen it as early as Squeeze but it may have
 been there earlier (I don't remember).
 
 Whether or not it crashes seems to depend on your environment at the time.
 Pasting to a regular bash prompt and into most applications works just fine.
 It seems to happen when working in more primitive environments with no
 readline.
 
 Here's a sure-fire way to reproduce it:
 
 1.  cut anything to the clipboard.
 
 2.  Run the command:
 
 cat
 
 This should open stdin for input.
 
 3.  Paste.
 
 4. Crash!
 
 AFAIK, this locks the kernel and only a power cycle will fix it.
 
 As noted previously, this only affects local sessions - even running an ssh to
 localhost and doing the above will not reproduce it.
 
 I've observed on several machines running both Squeeze and Wheezy.
 
 Geoff.
 
 
 

jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

Script started on Fri 24 Jan 2014 04:35:50 PM EST
jude@d-216-36-20-9:~$ uname -a
Linux d-216-36-20-9 3.12-1-amd64 #1 SMP Debian 3.12.6-2 (2013-12-29) x86_64 
GNU/Linux
jude@d-216-36-20-9:~$ exit
Script done on Fri 24 Jan 2014 04:36:11 PM EST
On Fri, 24 Jan 2014, Paul Gevers wrote:

 Hi Jude
 
 I think your issue is recorded in bug 735202 [1]. Could you verify the
 kernel number for me by running
 uname -a
 
 Paul
 
 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735202
 
 For the record, this mail was sent to debian-accessibil...@lists.debian.org
 https://lists.debian.org/debian-accessibility/2014/01/msg00107.html
 
 On 24-01-14 11:05, Jude DaShiell wrote:
  I am running debian_version: jessie/sid on an amd64 athelon k8 machine and 
  using speakup and speakup_soft for speech.  I would have used reportbug to 
  report this problem however after running dpkg-reconfig --priority=low 
  exim4-config and answering all of the questions to get exim4 set up some 
  problem exists that prevents this machine from sending email.
  
  If I don't have text in the speakup clipboard as a result of any operation 
  and hit the speakup paste key combination, sometimes that crashes debian 
  and someimes speakup says paste.  Whenever I have text in the speakup 
  clipboard as a result of a speakup mark operation followed by a speakup 
  cut operation and then I hit the speakup paste operation combination of 
  keys debian crashes.  A debian crash consists of loosing speakup and this 
  also renders all keyboard command combinations useless.  The only way I 
  get control restored is to power off the computer with an emergency power 
  down with the power button on the computer then reboot the machine.  I 
  have this debian installation up to date and one of those updates was a 
  speakup update in a kernel that got distributed that caused this problem.  
  Between the time this installation had been done originally and now, 
  speakup must have been updated at least once since it didn't do this with 
  a paste operation just after original installation.  Those on the 
  linux-speakup list think I'm running wheezy which has this problem when it 
  has it because its version of speakup in the kernel is not up to date, but 
  this is not the case.  I don't know if jessie/sid shares that same status 
  as does wheezy.
  
  
  
  jude jdash...@shellworld.net
  
  
 
 
 

jude jdash...@shellworld.net


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

Bug#735202: speakup crashes debian

[Jude DaShiell]

Hi, I sent you a typescript file with the command and its output as you 
requested earlier today.

On Fri, 24 Jan 2014, Paul Gevers wrote:

 Hi Jude
 
 I think your issue is recorded in bug 735202 [1]. Could you verify the
 kernel number for me by running
 uname -a
 
 Paul
 
 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735202
 
 For the record, this mail was sent to debian-accessibil...@lists.debian.org
 https://lists.debian.org/debian-accessibility/2014/01/msg00107.html
 
 On 24-01-14 11:05, Jude DaShiell wrote:
  I am running debian_version: jessie/sid on an amd64 athelon k8 machine and 
  using speakup and speakup_soft for speech.  I would have used reportbug to 
  report this problem however after running dpkg-reconfig --priority=low 
  exim4-config and answering all of the questions to get exim4 set up some 
  problem exists that prevents this machine from sending email.
  
  If I don't have text in the speakup clipboard as a result of any operation 
  and hit the speakup paste key combination, sometimes that crashes debian 
  and someimes speakup says paste.  Whenever I have text in the speakup 
  clipboard as a result of a speakup mark operation followed by a speakup 
  cut operation and then I hit the speakup paste operation combination of 
  keys debian crashes.  A debian crash consists of loosing speakup and this 
  also renders all keyboard command combinations useless.  The only way I 
  get control restored is to power off the computer with an emergency power 
  down with the power button on the computer then reboot the machine.  I 
  have this debian installation up to date and one of those updates was a 
  speakup update in a kernel that got distributed that caused this problem.  
  Between the time this installation had been done originally and now, 
  speakup must have been updated at least once since it didn't do this with 
  a paste operation just after original installation.  Those on the 
  linux-speakup list think I'm running wheezy which has this problem when it 
  has it because its version of speakup in the kernel is not up to date, but 
  this is not the case.  I don't know if jessie/sid shares that same status 
  as does wheezy.
  
  
  
  jude jdash...@shellworld.net
  
  
 
 
 

jude jdash...@shellworld.net


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

Bug#735202: Info received (speakup crashes debian)

[Jude DaShiell]

I haven't verified this yet but was told doing an ssh localhost before a 
paste from speakup clipboard is supposed to prevent this problem.  I 
suppose that will be useful for work on a local computer, but if you're 
online and cut information from an online source this work around 
probably won't help.

On Fri, 24 Jan 2014, Debian Bug Tracking System wrote:

 Thank you for the additional information you have supplied regarding
 this Bug report.
 
 This is an automatically generated reply to let you know your message
 has been received.
 
 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.
 
 Your message has been sent to the package maintainer(s):
  Debian Accessibility Team debian-accessibil...@lists.debian.org
 
 If you wish to submit further information on this problem, please
 send it to 735...@bugs.debian.org.
 
 Please do not send mail to ow...@bugs.debian.org unless you wish
 to report a problem with the Bug-tracking system.
 
 

jude jdash...@shellworld.net


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

Bug#707196: Activate software speech synthesiser in KDE too (for desktop=kde installs)?

[Jude DaShiell]

From what I understand, kde offers ktts and jovie.  I don't know that 
the combination constitutes a full screen reader solution though and it 
may not be feasible to  extend espeakup into kde.

On Wed, 8 May 2013, Petter Reinholdtsen wrote:

 
 Package:  espeakup-udeb
 Version:  1:0.71-13
 Severity: wishlist
 User: debian-...@lists.debian.org
 Usertags: debian-edu
 
 The Wheezy installer have a very nice option to get the installer to
 speak, and if this is enabled the configuration is passed on to Gnome to
 continue the load speaking experience also after boot.
 
 But when installing using desktop=kde, the resulting desktop is not
 configured to speak up.
 
 Could espeakup-udeb be extended to install and set up the required
 packages for a KDE desktop too?  I am not sure what should be installed
 or set up, but have read somewhere that KDE uses festival for its load
 speaking abilities.
 
 Even if KDE isn't using espeakup, I suspect it do not make sense to
 provide several speakup mechanism within d-i, and that the espeakup-udeb
 package should handle KDE speakup too.
 
 

---
jude jdash...@shellworld.net
About to block another web browser version?  Ask yourself what Tim
Berners-lee would do.


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

Bug#633620: Info received (Bug#633620: installation-report: espeakup amdk8 wheezy to sid)

[Jude DaShiell]

I expect the ata errors are happening because of the disk on which 
debian was installed.  It's in a drive sled and recently I asked a 
sighted friend to check the drive sled out and was told nothing is wrong 
with the drive sled.  Another drive sled that goes in the same slot on 
the same computer that has another Linux distribution on it has none of 
the ata errors when it comes up.

On Tue, 12 Jul 2011, Samuel Thibault wrote:

 Jude DaShiell, le Tue 12 Jul 2011 06:32:56 -0400, a ?crit :
  http://www.shellworld.net/~jdashiel/dmesg.log has the current dmesg 
  output.  A little over 50k so I put it on my web page.
 
 50k is not a problem, so attaching it, so it's not lost.
 
 Samuel
 





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

Bug#633620: installation-report: espeakup amdk8 wheezy to sid

[Jude DaShiell]

Package: installation-reports
Version: 2.45
Severity: normal



-- Package-specific info:

Boot method: network apt-get dist-upgrade
Image version: 
Date: Date and time of the install

Machine: amd k8 athelon
Partitions: df -Tl will do; the raw partition table is preferred


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20110517-23:41
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux md 2.6.32-5-486 #1 Tue Mar 8 21:03:02 UTC 2011 i686 GNU/Linux
lspci -knn: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory 
Controller [10de:005e] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge 
[10de:0050] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] 
(rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005a] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005b] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:04.0 Multimedia audio controller [0401]: nVidia Corporation 
CK804 AC'97 Audio Controller [10de:0059] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: Intel ICH
lspci -knn: 00:06.0 IDE interface [0101]: nVidia Corporation CK804 IDE 
[10de:0053] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: pata_amd
lspci -knn: 00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0054] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0055] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge 
[10de:005c] (rev a2)
lspci -knn: 00:0a.0 Bridge [0680]: nVidia Corporation CK804 Ethernet Controller 
[10de:0057] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: 00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
lspci -knn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Address Map [1022:1101]
lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] DRAM Controller [1022:1102]
lspci -knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control [1022:1103]
lspci -knn: 05:00.0 VGA compatible controller [0300]: ATI Technologies 

Bug#633626: nethack-common: fails to purge associated files

[Jude DaShiell]

Package: nethack-common
Version: 3.4.3
Severity: important


/var/games/nethack and /etc/nethack directories with all content
remain on machine after aptitude remove --purge nethack-common is run
and all dependencies are selected for removal.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nethack-common depends on:
ii  debconf [debconf-2.0] 1.5.40 Debian configuration management sy
ii  debianutils   4.0.2  Miscellaneous utilities specific t
ii  libc6 2.13-10Embedded GNU C Library: Shared lib

Versions of packages nethack-common recommends:
pn  nethack-console | nethack-x11 none (no description available)

nethack-common suggests no packages.



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

Bug#633626: Acknowledgement (nethack-common: fails to purge associated files)

[Jude DaShiell]

Further system examination found none of the startup scripts for 
nethack-common and nethack-console were removed by aptitude remove 
--purge nethack-common.  Maybe it's not debian policy to purge 
dependencies as well, but if so that to me would seem strange.

On Tue, 12 Jul 2011, Debian Bug Tracking System wrote:

 Thank you for filing a new Bug report with Debian.
 
 This is an automatically generated reply to let you know your message
 has been received.
 
 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.
 
 As you requested using X-Debbugs-CC, your message was also forwarded to
   jdash...@shellworld.net
 (after having been given a Bug report number, if it did not have one).
 
 Your message has been sent to the package maintainer(s):
  Joshua Kwan jo...@triplehelix.org
 
 If you wish to submit further information on this problem, please
 send it to 633...@bugs.debian.org.
 
 Please do not send mail to ow...@bugs.debian.org unless you wish
 to report a problem with the Bug-tracking system.
 
 





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

Bug#633620: installation-report: espeakup amdk8 wheezy to sid

[Jude DaShiell]

Mostly successful, alsa can't seem to figure out what sound card I have 
but the system still talks.  Soud card identification capability was lost 
in wheezy and not recovered in sid.On Tue, 12 Jul 2011, Samuel Thibault 
wrote:

 So, was it successful?
 
 If so, great, and we'll happily close the bug report and thank you for
 reporting it (we also need successful report, not only issue reports)
 
 Else, please provide details :)
 
 Samuel
 
 





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

Bug#633620: Info received (Bug#633620: installation-report: espeakup amdk8 wheezy to sid)

[Jude DaShiell]

http://www.shellworld.net/~jdashiel/dmesg.log has the current dmesg 
output.  A little over 50k so I put it on my web page. On Tue, 12 Jul 
2011, Debian Bug Tracking System wrote:

 Thank you for the additional information you have supplied regarding
 this Bug report.
 
 This is an automatically generated reply to let you know your message
 has been received.
 
 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.
 
 Your message has been sent to the package maintainer(s):
  Debian Install Team debian-b...@lists.debian.org
 
 If you wish to submit further information on this problem, please
 send it to 633...@bugs.debian.org.
 
 Please do not send mail to ow...@bugs.debian.org unless you wish
 to report a problem with the Bug-tracking system.
 
 





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

Bug#633596: installation-report:

[Jude DaShiell]

Package: installation-reports
Version: 2.45
Severity: normal



-- Package-specific info:

Boot method: cd
Image version: http://people.debian.org/~sthibault/espeakup/espeakup-i386.iso 
6/10/2011
Date: Date and time of the install

Machine: amd athelon k8
Partitions: df -Tl will do; the raw partition table is preferred


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20110517-23:41
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux md 2.6.32-5-486 #1 Tue Mar 8 21:03:02 UTC 2011 i686 GNU/Linux
lspci -knn: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory 
Controller [10de:005e] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge 
[10de:0050] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] 
(rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005a] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005b] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:04.0 Multimedia audio controller [0401]: nVidia Corporation 
CK804 AC'97 Audio Controller [10de:0059] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: Intel ICH
lspci -knn: 00:06.0 IDE interface [0101]: nVidia Corporation CK804 IDE 
[10de:0053] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: pata_amd
lspci -knn: 00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0054] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0055] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge 
[10de:005c] (rev a2)
lspci -knn: 00:0a.0 Bridge [0680]: nVidia Corporation CK804 Ethernet Controller 
[10de:0057] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: 00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
lspci -knn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Address Map [1022:1101]
lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] DRAM Controller [1022:1102]
lspci -knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control [1022:1103]
lspci -knn: 05:00.0 VGA 

Bug#575588: bsdmainutils: col -bx no longer cleans typescript files

[Jude DaShiell]

Package: bsdmainutils
Version: 8.0.8
Severity: normal

Since I don't run other releases of Debian I can't say that the col bug only
applies to sid/squeeze.  col -bx  typescript typescript.tmp in previous
versions had all of the escape codes cleaned out of it.  That's not the case
anymore, command runs but fails to change typescript in any noticeable way. 
This technique for cleaning typescript files generated by the script utility
was documented in debian-reference package.

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

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages bsdmainutils depends on:
ii  bsdutils  1:2.16.2-0 Basic utilities from 4.4BSD-Lite
ii  debianutils   3.2.2  Miscellaneous utilities specific t
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libncurses5   5.7+20100313-1 shared libraries for terminal hand

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp   4:4.4.3-1  The GNU C preprocessor (cpp)
ii  miscfiles [wordlist]  1.4.2.dfsg.1-9 Dictionaries and other interesting
pn  vacation  none (no description available)
ii  wamerican [wordlist]  6-3American English dictionary words 
ii  wbritish [wordlist]   6-3British English dictionary words f
ii  whois 5.0.1  an intelligent whois client

-- no debconf information



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

Bug#470716: kudos on gnome-orca update

[Jude DaShiell]

Package: gnome-orca
Version: 2.22.0-1
Severity: wishlist

Congratulations on a fast update for gnome-orca which got disabled by 
updates on March 11, 2008.  By March 12, 2008 an update was available 
and cleared the problem or problems introduced by the updates to the 
point that gnome-orca now speaks again as it did before.


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

Kernel: Linux 2.6.18-4-speakup-686 (SMP w/1 CPU core)
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 gnome-orca depends on:
ii  libgail-gnome-module  1.20.0-1   GNOME Accessibility Implementation
ii  libgnome-speech7  1:0.4.18-1 GNOME text-to-speech library
ii  python2.4.4-6An interactive high-level object-o
ii  python-brlapi 3.9-5  Python bindings for BrlAPI
ii  python-glade2 2.12.1-1   GTK+ bindings: Glade support
ii  python-gnome2 2.20.1-2   Python bindings for the GNOME desk
ii  python-gtk2   2.12.1-1   Python bindings for the GTK+ widge
ii  python-pyatspi1.22.0-1   Assistive Technology Service Provi
ii  python-support0.7.7  automated rebuilding support for P

Versions of packages gnome-orca recommends:
ii  gnome-mag1:0.14.10-4 a screen magnifier for the GNOME d
ii  wget 1.10.2-3retrieves files from the web

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]