> Perhaps something like 1A86/7523 plugged on 1A40/0101. That being said
it seems like both are generic ids
Ah, but this 1A86/7523 line is properly emitted by upstream in the `usb-
generic.rules` file, so it shouldn't be enabled by default, to avoid
matching such combination of generic devices.
T
> Are you saying we re-enable lines:
> ENV{PRODUCT}=="10c4/ea60
I didn't talk about these lines, but the 403/6001 ones, that do match a
proper Braille manufacturer string:
ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Hedo Reha Technik GmbH",
ENV{BRLTTY_BRAILLE_DRIVER}="hd", GOTO="brltty_u
> aren't the identifiers in ENV{PRODUCT} already idVendor/idProduct?
I don't know the details. From what I gather from the upstream source
code, this device has a special rule to appear like this in the udev
file:
Drivers/Braille/Baum/braille.c:
{ /* NLS eReader Zoomax (20 cells) */
.v
> it's a bit unclear to me which entries there should be considered
'generic USB IDs'?
They are marked "Generic Identifier", that's
0403:6001
10C4:EA60
10C4:EA80
> I also don't understand why those rules are debian specific
See the diff between ./debian/brltty-udeb.udev.rules and
./Autostart/Ud
orca only suggests brltty, it's the *-desktop packages which seem to be
recommending brltty.
If Ubuntu really wants to install brltty by default, it should disable
the udev entries for the generic USB IDs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Yes, unfortunately there is no way to fix it in that case. The udev
rules properly avoid starting brltty when the iManufacturer field is
changed from FTDI to the actual manufacturer of the device, but not when
it is left to FTDI.
--
You received this bug notification because you are a member of U
> In this case, brltty appeared (or at least the device claim) after a
dist-upgrade
Ah, do you happen to have a log of that dist-upgrade, so we can
determine what brought it in?
> It still feels very bad form for a vendor device to use the default
VID/PID of the underlying converter chip
Yes. Un
Debian is installing the brltty package only when brltty was used during
installation.
Brltty gets started during installation either through the udev rules,
or started manually from the kernel command line. The finish-install
script just checks out /var/run/brltty.pid to determine whether a brltt
*** This bug is a duplicate of bug 526398 ***
https://bugs.launchpad.net/bugs/526398
** This bug has been marked a duplicate of bug 526398
accerciser crashed with LookupError in _inner()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 526398 ***
https://bugs.launchpad.net/bugs/526398
** This bug has been marked a duplicate of bug 526398
accerciser crashed with LookupError in _inner()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes, but it is meant to be so: the Seika Braille device is announced as
such, so we have to recognize such devices in brltty, otherwise the
Seika Braille devices would not work at all.
The question is rather: why is brltty installed on your system? It is
supposed to be installed only if you instal
Ah, the patch is already in brltty 6.4 actually, so no change on the
Debian side actually :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950488
Title:
brltty ftbfs in jammy
To manage notificatio
Ok, thanks!
The corresponding commit upstream is
e6ed2372887ac0106db8854f70e9b2fdcadec74f, attached here, could somebody
check that this fixes the build issue on Ubuntu? I'll then integrate the
patch in Debian as well.
** Attachment added: "patch"
https://bugs.launchpad.net/ubuntu/+source/brl
> it is probably newer python versions being stricter with the use of
non existing options?
The --without-viavoice is not passed to the python bindings, so that
cannot be the problem.
That said I have now dropped the option from debian/rules, thanks :)
--
You received this bug notification beca
Please provide the whole build log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950488
Title:
brltty ftbfs in jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
> Enabling CONFIG_ACCESSIBILITY could affect console output
No it won't: no source code uses CONFIG_ACCESSIBILITY.
CONFIG_ACCESSIBILITY only enables the accessibility configuration menu
which allows enabling speakup.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It seems I have to insist again: patch
https://launchpadlibrarian.net/405256420/patch should definitely really
really be applied. As explained in
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146/comments/73 that script should really *not* pass
--force to setupcon. There is no rea
This works with espeak-ng, so not a bug in mbrola-br2 but in espeak
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893511
Title:
espeak cannot find voice file for mbrola-br2
To manage notifications
I guess this is due to the following change in at-spi2-atk:
* Meson: don't hard-code shared_library (!19).
which made meson emit a lot of new libraries in Requires.private of atk-
bridge-2.0.pc, and thus the -dev package now has to add them in Depends.
--
You received this bug notification beca
This was fixed in Debian in 1.11.10-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731719
Title:
Add multiarch metadata to libhwloc-plugins
To manage notifications about this bug go to:
https://b
I confirm that there is still no volume control in lightdm-gtk-greeter
2.0.6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507344
Title:
Add volume control support to lightdm-gtk-greeter
To manag
But scripts changing between scancode and ascii/unicode (such as for
some terminal emulation, dosbox, etc.) would break. I'm not saying they
are widespread, but I have seen this kind of use, and requiring such
flag will suddenly break them.
--
You received this bug notification because you are a
How will kbd_mode know whether it's safe or not?
Adding a -f option to kbd_mode will at best break some *other* existing
scripts, while this very script should really definitely *NOT* pass -f
to setupcon. That is the nonsense which needs to be fixed.
--
You received this bug notification because
That is when updating the console-setup package, yes. As mentioned on
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146/comments/73 that's because its config script passes
--force to setupcon, it really shouldn't, as mentioned there
--
You received this bug notification because
Xorg can't do anything about intercepting Alt-key, it's the kernel which
takes the shortcut away.
Again, as mentioned on https://bugs.launchpad.net/ubuntu/+source
/console-setup/+bug/520546/comments/66
«
proposed fix:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attac
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546
Is there really any reason why keyboard-configuration.postinst passes
--force to setupcon?
In Debian we do this in the Debian installer because it is running
within a bterm and thus can't detect it's running
As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch.
** Attachment added: "proposed fix"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch
--
You received th
Charlie: do you have the espeak package installed? It is needed to have
espeak-generic working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571956
Title:
sd_generic breaks speech-dispatchter
To ma
>From the upstream policykit bug entry, it is actually a misuse of the
policykit API from brltty. I have uploaded a fix in Debian's brltty
5.6-5.
Ubuntu should definitely include the policykit-fix patch contained in
that 5.6-5 version as an update to ubuntu 18.04, otherwise all blind
users will ha
Yes, disabling that patch fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782320
Title:
Braille display inoperable in GUI since polkit-update
To manage notifications about this bug
I can confirm the same issue on Debian: upgrading from version 0.105-20
to version 0.105-21 brings the same issue.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1116
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is most probably due to the introduction of Fix-CVE-2018-1116
-Trusting-client-supplied-UID.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782320
Title:
Braille display inoperable in GUI
This seems to be an issue within policykit itself. Printing the actual
error shows:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: process with PID
12570 has been replaced
>From reading the source code, it seems that policykit is checking the
start time of the program and finds a mismatch.
Note: to reproduce the issue, one just needs to install an Ubuntu 18.04
system, start brltty by hand as root with:
sudo brltty -b no
then try to connect to it as normal logged-in user through brlapi:
python3
>>> import brlapi
>>> b = brlapi.Connection()
which shouldn't raise an exceptio
They are now available in cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354715
Title:
[needs-packaging] Support also nl1 and nl3
To manage notifications about this bug go to:
https://bugs.l
Well, this is not a real solution, we need to fix polkit, otherwise all
users will have the same issue, and we don't want to make them all
revert back to file-based authentication.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Hello,
The files for these plugins are indeed missing in POTFILES.in. I have
pushed then i18n-plugins-a11y branch that adds just them, and i18n-
plugins which just adds the missing .xml.in files for all plugins (not
sure why they were not added for all plugins already)
Samuel
--
You received th
lasakro, stu: which USB ID does your device have?
(otherwise we can't know what to fix in brltty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874181
Title:
brltty daemon prevents creation of ttyUS
I don't know how ubuntu manages that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741070
Title:
Please merge brltty (main) 5.5-4 from Debian unstable (main)
To manage notifications about this bu
I have pushed the AT_SPI_BUS removal patch to branch
https://code.launchpad.net/~samuel-thibault/lightdm-gtk-greeter/at-spi-
bus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670933
Title:
[PATCH
Hello,
Still now news on this and #1366534 ? This is really hurting users...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670933
Title:
[PATCH] Accessibility partly broken due to X root window be
Indeed, for instance, "Enhanced Zoom Desktop" (the name of the ezoom
plugin) appears in fr.po, but it is not translated on the ccsm panel,
while others are, for instance "Opacity, Brightness and Saturation" (the
name of the obs plugin)
--
You received this bug notification because you are a membe
Hello,
Just to confirm that the approch proposed by Luke is sound. Removing the
AT_SPI_BUS property would really be the safest for the user session:
even if systemd doesn't manage to properly clean the at-spi dbus, at
least the session isn't exposed to its existence.
--
You received this bug not
Hello,
This was reported in debian http://bugs.debian.org/851623 , and that led
to upstream fix
https://github.com/brltty/brltty/commit/0a5341121ba8f4de24407ce2a4d5369dadf5d099
** Bug watch added: Debian Bug tracker #851623
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851623
--
You recei
I have suggested a patch to Dave, upstream maintainer of brltty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579531
Title:
openConnection: connect: No such file or directory
To manage notificatio
I've commited it, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567658
Title:
ubuntuBSD support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brlt
Please see the end of https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=797595 : awt is currently not calling
XInitThreads(), and libxcb is thus not thread-safe. Jabref happens to be
using threads, so all kinds of funky things is to be expected. The patch
proposed there will probably fix the issue
Hello,
While I could reproduce the issue with java-atk-wrapper 0.30, I can not
reproduce it with java-atk-wrapper 0.33. I had reported the issue on
https://bugzilla.gnome.org/show_bug.cgi?id=698095 , and it was reported
as fixed.
Perhaps it is the time to consider re-enabling accessibility in
/et
Well, yes, brltty needs mountkernfs, like a lot of software actually.
Having it disabled seems the culprit here, not brltty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365054
Title:
package brlt
Again, there is no point in shipping nl1 and nl3 as long as we don't
have any tool to produce .pho files for them. We only have that for the
nl2 language (thanks to espeak), that's why I uploaded that one.
Uploading nl1 and nl3 would be like promise the user that he can use
them, but the truth is t
I too believe that Andreas' proposal is the right one. It permits people
who really want the extra 5th level to be able to easily get it, while
not breaking the 99% usual usage.
Just for the record, I had not seen the linuxfr discussion. I guess
mostly only people who would want the extra 5th leve
I too believe that Andreas' proposal is the right one. It permits people
who really want the extra 5th level to be able to easily get it, while
not breaking the 99% usual usage.
Just for the record, I had not seen the linuxfr discussion. I guess
mostly only people who would want the extra 5th leve
Hello,
Until a solution is to be found, could 518c769d be reverted for now?
Breaking the very standard behavior of right control in all applications
(e.g. xterminals!!) is really not acceptable, compared to the few issues
that the behavior has without it.
Samuel
--
You received this bug notific
Hello,
Until a solution is to be found, could 518c769d be reverted for now?
Breaking the very standard behavior of right control in all applications
(e.g. xterminals!!) is really not acceptable, compared to the few issues
that the behavior has without it.
Samuel
--
You received this bug notific
This should get fixed by the next brltty version, 4.5, to be released
very soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082679
Title:
brlapi.OperationError.__str__ return bytes
To manage no
Attila Hammer, le Mon 14 Jan 2013 07:22:17 -, a écrit :
> In Ubuntu Quantal and Ubuntu Raring if I enabling Orca with braille support,
> the Orca's debug.out file I see following traceback error message:
> BrlTTY seems to have disappeared:
>
> Traceback (most recent call last):
> File "/usr
Why should it have to care about screen size? 100% zoom is supposed to
be "app DPI matches screen DPI", it has nothing to do with the whole
screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/521877
Let me disagree: I keep using my laptop either on a 17" monitor, or on a
21" monitor, or on the internal LVDS.
In both 17" and 21" monitor cases, I do want 100% zoom to really mean
100% zoom, so I need correct DPI.
Your reasoning leads to having to modify xorg.conf each time I switch,
which means
This is fixed in debian's latest upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029864
Title:
read error appears from btltty during precise server iso testing
To manage notifications about
I still don't think it will fly:
- either the user is not knowledged about mbrola voices, and he will
just install mbrola-nl* and wonder for a long time why they do not
show up in high-level speech interfaces.
- or he is knowledged about mbrola voices, he will have to be anyway,
to use these voic
Yes, mbrola alone will permit to read some existing phoneme files, but
as I said, we still lack a tool to *produce* nl1/2/3 phoneme files. Put
another way: how to start from a Dutch text and get mbrola to speak it?
I don't know any free tool to produce nl1/2/3 phoneme files that mbrola
would then b
Dave Mielke, le Mon 14 Nov 2011 09:38:57 -0500, a écrit :
> I'm going to try to figure out if we can get to the virtual serial device
> from
> knowledge of which USB device is being used. If we can, that should solve the
> problem. If anyone already knows how to do it, please let me know.
Mmm,
Dave Mielke, le Wed 09 Nov 2011 10:44:57 -0500, a écrit :
> I wonder if there's a way to figure out which serial device is associated with
> a given USB device.
I believe so: I've just plugged a converter:
[161835.668469] usb 2-1.1.1: new full speed USB device number 9 using ehci_hcd
[161835.7656
Dave Mielke, le Wed 09 Nov 2011 10:06:24 -0500, a écrit :
> [quoted lines by Samuel Thibault on 2011/11/09 at 15:14 +0100]
>
> >Err, precedence, really? Won't that let brltty still start?
>
> Sure. It'd only be a problem for that one particular model of braille d
ironfisher, le Wed 09 Nov 2011 13:11:06 -, a écrit :
> Dave Mielke wrote:
> >Strictly speaking, yes, brltty is causing the problem. An easy solution,
> >though, would be for Ubuntu to give brltty's udev file an earlier position in
> >the udev rules file processing order so that the generic rul
Harry Bloomberg, le Wed 09 Nov 2011 03:56:09 -, a écrit :
> I too wasted a week of my finite life chasing after this. I know of no
> other operating system in widespread usage that comes configured by
> default like this.
Yes, and that's a shame. There is no reason why a braille device
should
Hazuki Amamiya, le Wed 09 Nov 2011 01:20:22 -, a écrit :
> I wasted over a week's time to find out why my LCD display not working
> properly before I get to here. I's say the brltty is too aggressive and
> since brltty has no intention to fix this problem (this issue repeat and
> repeat and rep
ironfisher, le Tue 08 Nov 2011 18:12:59 -, a écrit :
> Let's deactivate BRLTTY default
Please don't do that. It'd make way harder for blind people to use
Ubuntu.
> or contact with BRLTTY developers to not claim the USB interface by
> default.
That is already what I proposed: comment the ent
Harry Bloomberg, le Mon 24 Oct 2011 01:21:32 -, a écrit :
> Bus 003 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
> Composite Device
Ok, it's indeed the same.
Samuel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Harry Bloomberg, le Sat 22 Oct 2011 18:00:13 -, a écrit :
> I think it's usb 2.
I mean the output of lsusb, e.g.
Bus 002 Device 008: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
my mouse has USB ID 046d:c050.
Samuel
--
You received this bug notification because you are a member of Ubu
Harry Bloomberg, le Sat 22 Oct 2011 01:09:47 -, a écrit :
> I'm seeing the exact same thing with an Icom IC-7200 amateur radio
> tranceiver.
What is the USB ID of that device?
Samuel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Christian Weiske, le Sun 16 Oct 2011 09:09:15 -, a écrit :
> Same problem here with an ELV USB-WDE1 weather data receiver.
What is its USB ID?
Samuel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Berend Dekens, le Fri 14 Oct 2011 12:45:29 -, a écrit :
> After upgrading from Ubuntu 11.04 to 11.10, I no longer found a
> '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a
> Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc.
> CP210x Composite Device".
** Changed in: brltty (Ubuntu)
Status: Expired => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/502947
Title:
Please replace some hungarian specific table files with Brltty
--
Ok, packaged, successfully tested, and uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165245
Title:
[needs-packaging] festival-mbrola
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I'll ITP the festvox-us1, festvox-us2, festvox-us3, festvox-en1 series
of package, each containing just the file. Yes, I'll reference the LP
number.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165245
Mmm, I don't see how you could use nl1 and nl3. Could you explain how
you proceed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/543651
Title:
[needs-packaging] mbrola-voices
--
ubuntu-bugs mailin
Err, why having to complete 543651 first? To get a much better fine-
grain dependency, festival-mbrola should rather build a series of
packages, one for each language, each of which depending on the
corresponding mbrola voice package. If you depend on all the mbrola
voices at once, you'll get sever
I'm not sure to understand what you mean by a "mbrola-voices package",
and in particular, "mbrola package has already a suggestion for this
package on Karmic, even though this package still needs to be created.":
mbrola suggests mbrola-voice (provided by all mbrola voice packages),
not mbrola-voice
Mmm, what do you mean by "in the meanwhile"?
About nl1, nl3, it is not really useful, since we do not currently have
tools to produce the phoneme files for them (espeak supports only nl2)
About us3, it's already packaged in Debian, Ubuntu just needs to inherit
it.
--
You received this bug notif
Could people have a look at standards instead of trolling?
SUSv4 adds the following exception:
« if an operand resolves to the root directory, rm shall write a
diagnostic message to standard error and do nothing more with such
operands. »
--
rm does not preserve root by default
https://bugs.lau
This seems to be fixed in version 2.10.11 of gthumb.
** Changed in: gthumb (Ubuntu)
Status: Invalid => Fix Released
--
doesn't refresh automatically on duplicating a file
https://bugs.launchpad.net/bugs/312418
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Err, I'm not developper of the software... Could you please directly
report to Eitan Isaacson instead? Same for the
crash bug.
--
About dialog missing
https://bugs.launchpad.net/bugs/541723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
It has been commited upstream, ready for future 4.2
--
Please replace some hungarian specific table files with Brltty
https://bugs.launchpad.net/bugs/502947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Ah, the list is poster-only. It'd be better if you subscribed to it
so you can perhaps discuss yourself with other hungarian people on the
list about the table.
Once it is in the upstream package on mielke.cc, it will automatically
propagate to Ubuntu & other distributions when they upgrade.
--
Could you consider to discuss on brl...@mielke.cc for proper upstream
inclusion? I guess my old table could just be discarded and replaced
by yours...
--
Please replace some hungarian specific table files with Brltty
https://bugs.launchpad.net/bugs/502947
You received this bug notification becau
Fixed in Debian's 4.1-2
--
udevd errors in /lib/udev/rules.d/85-brltty.rules
https://bugs.launchpad.net/bugs/491775
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Steve Langasek, le Tue 13 Oct 2009 23:14:50 -, a écrit :
> On Tue, Oct 13, 2009 at 11:00:14PM -0000, Samuel thibault wrote:
> > Steve Langasek, le Tue 13 Oct 2009 22:40:44 -, a écrit :
> > > Making the gdm and kdm jobs depend on cryptsetup is not a solution
> >
Steve Langasek, le Tue 13 Oct 2009 22:40:44 -, a écrit :
> Making the gdm and kdm jobs depend on cryptsetup is not a solution
> because cryptsetup is optional and depending on an optional job doesn't
> DTRT.
insserv's Should-Start is exactly that and works exactly as would be
expected here.
-
arky, le Tue 13 Oct 2009 08:46:45 -, a écrit :
> $ grep Default-Start /etc/init.d/brltty
> # Default-Start: S
>
> Default-Start should be a number
Errr, for S script, no.
--
update-rc.d warnings: runlevel arguments
https://bugs.launchpad.net/bugs/450176
You received this bug notificat
arky, le Tue 13 Oct 2009 08:44:25 -, a écrit :
> update-rc.d: warning: brltty stop runlevel arguments (none) do not match LSB
> Default-Stop values (0 6)
this is fixed in debian's 4.0-9 and later (Bug#548550).
Samuel
--
update-rc.d warnings: runlevel arguments
https://bugs.launchpad.net/b
Scott James Remnant, le Mon 12 Oct 2009 12:38:20 -, a écrit :
> On Sun, 2009-10-11 at 14:49 +, Tom Jaeger wrote:
>
> > Does upstart ensure that only one 'console owner' job can run at the
> > same time? I assume it would also be a problem if one 'console owner'
> > job took away the conso
Steve Langasek, le Sun 11 Oct 2009 08:46:37 -, a écrit :
> On Sun, Oct 11, 2009 at 07:37:09AM -0000, Samuel thibault wrote:
> > I don't know cryptsetup and slash, but can't Xorg just wait for the
> > termination of that?
>
> The problem is that cryptsetup isn&#x
Tom Jaeger, le Sun 11 Oct 2009 03:39:24 -, a écrit :
> Scott James Remnant wrote:
> > That precisely fits the problem definition.
> >
> > "console owner" while X is running while forcibly take the ownership of
> > tty7 away from X. It doesn't like that so much (cf. this bug)
>
> So this is e
Bryce Harrington, le Thu 08 Oct 2009 00:39:09 -, a écrit :
> On Wed, Oct 07, 2009 at 11:46:20PM -0000, Samuel thibault wrote:
> > Bryce Harrington, le Wed 07 Oct 2009 23:31:46 -, a ??crit :
> > > On Wed, Oct 07, 2009 at 10:44:02PM -0000, Samuel thibault wrote:
> >
Bryce Harrington, le Wed 07 Oct 2009 23:31:46 -, a écrit :
> On Wed, Oct 07, 2009 at 10:44:02PM -0000, Samuel thibault wrote:
> > Bryce Harrington, le Wed 07 Oct 2009 22:30:13 -, a ??crit :
> > > On Wed, Oct 07, 2009 at 10:13:20PM -0000, Samuel thibault wrote:
> >
Bryce Harrington, le Wed 07 Oct 2009 22:30:13 -, a écrit :
> On Wed, Oct 07, 2009 at 10:13:20PM -0000, Samuel thibault wrote:
> > Bryce: please also add a dependency on the console configuration
> > scripts, as while waiting for acpi probably helps to wait for the
> >
Bryce: please also add a dependency on the console configuration
scripts, as while waiting for acpi probably helps to wait for the
console configuration, it'd be better to really make sure gdm doesn't
start before it.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.la
Tom Jaeger, le Wed 07 Oct 2009 00:29:13 -, a écrit :
> Samuel thibault wrote:
> > Could people getting the error check /proc/`pidof X`/status? Here I
> > have
> >
> > SigIgn: 10301000
> >
> > The important part is the 3. If the 3 is not ther
Mmm, ok, this can only happen when the ioctl handler is
hung_up_tty_ioctl, i.e. the tty got hung up after Xorg opened it, most
probably because with the parallel start in upstart the console may
get tinkered with after Xorg gets started. After an Xorg restart (or
equivalently, login/logout), no pr
1 - 100 of 145 matches
Mail list logo
