clang-3.4 isn't fully released yet, is it? I think it's still work in
progress, and it isn't in the package manager (not even in sid).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242300
Title:
Cl
Public bug reported:
This command fails saying that limits.h cannot be found:
echo '#include ' | clang -v -xc -o /dev/null -
This is the full verbose output from it:
Debian clang version 3.2-7ubuntu1 (tags/RELEASE_32/final) (based on LLVM 3.2)
Target: x86_64-pc-linux-gnu
Thread model: posix
"/us
> The strange thing is that after this crash it kept "reading"
> (maybe it is restarted automatically?) but then crashed the
> programs it was reading from.
>
> --
If orca detects a problem it will attempt to restart. This is probably why
you were seeing this behavior.
Mike
--
[apport] esp
I think we have a much larger sound problem here. I just installed
Cepstral swift and test-speech shows me the voice and all its parameters
but I hear nothing from the sound card.
--
[apport] espeak-synthesis-driver crashed with SIGSEGV in strcpy()
https://launchpad.net/bugs/92060
--
ubuntu-bu
I just downloaded Jonathan's latest espeak zip file. Orca still only
talks for about 30 seconds and then crashes because speech has crashed.
I'm about to install Cepstral Swift to see if that works.
--
[apport] espeak-synthesis-driver crashed with SIGSEGV in strcpy()
https://launchpad.net/bugs/9
Sorry I wasn't clear in my last comment. I was responding to the following
comment.
[apport] espeak-synthesis-driver crashed with SIGSEGV in strcpy() from Jan
Claeys
at 2007-03-13 22:46:14 UTC
--
[apport] espeak-synthesis-driver crashed with SIGSEGV in strcpy()
https://launchpad.net/bugs/
I can confirm this behavior with latest updates. This bug has rendered
my system pretty useless. It doesn't matter how I start orca: from a
terminal, from a launch menu shortcut or at startup. Just to confirm it
wasn't a problem with gnome-speech or orca I rebuilt both with the same
result.
--
I am also noticing the problems reported above. I am using a Dell
latitude d400 with a broadcom bcm4306 wireless chip set. I am not able
to view any wireless networks. Do the developers have enough
information here from other users or should I include more details?
--
bcm43xx completely broken
Well, re-adding the exit line certainly changes the behavior. Now when
I boot the laptop with the USB display attached brltty continually tries
to initialize the display never with any success. This is the exact
behavior I reported in the original bug. It almost seems like something
that starts
An interesting new development here. Within the past half hour a new version
of brltty was uploaded and added to udev to support the auto detection of
braille displays on boot up. Braille now starts successfully for me. A couple
small problems remain though:
1. brltty attempted to start twic
> My mistake, use "sudo modprobe -r ehci_hcd"
>
Sadly nothing has changed.
Mike
--
USB braille display no longer starts with brltty
https://launchpad.net/bugs/80892
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The "sudo modprobe ehci_hcd" made no difference. When I tried to restart
brltty I got the same result. I also just tried the latest brltty sources from
head with the same result.
If it would help, perhaps I could allow you to ssh into a machine that exhibits
the problem. I'm normally not int
If you can give me more detailed information on what you are asking I
can give this a try. Note that the same braille display and the same
version of brltty work just fine on an edgy system.
--
USB braille display no longer starts with brltty
https://launchpad.net/bugs/80892
--
ubuntu-bugs mai
Hi Henrik, removing the network manager and rebooting made no difference
with this problem.
--
USB braille display no longer starts with brltty
https://launchpad.net/bugs/80892
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi Henrik,
> Thanks Mike. Hm, interesting looks like it's interfering with
> Network Manager somehow. -- A new feature in Feisty.
>
> I'll add a bug task for NM so the maintainers of that will
> have a look.
> In the meantime, Mike: could you try uninstalling
> network-manager and see if that h
** Attachment added: "log of attempt to start brltty"
http://librarian.launchpad.net/6083796/E%3A%5Csyslog
--
USB braille display no longer starts with brltty
https://launchpad.net/bugs/80892
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
Here is the requested syslog. Note that I killed the brltty process
after it attempted to initialize several times.
--
USB braille display no longer starts with brltty
https://launchpad.net/bugs/80892
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Public bug reported:
I have connected a Baum Super Vario braille display to the USB port of
my laptop. When I boot feisty I hear the tone telling me the the
display is attempting to initialize just as the GDM login is appearing.
After about 2 seconds I then hear the tone telling me that the
conne
18 matches
Mail list logo
