Re: Exim4 in Debian?
On Sun, 2024-04-28 at 16:58 -0400, Cindy Sue Causey wrote: > DISCLAIMER: This is my first listserv reply using Evolution after Gmail dumped > their old, simple web based format. My apologies in advance if there are any > major formatting glitches in this response. This little side adventure sure > has > had its own learning curve. :) Evolution sometimes misformats replies. You can prevent this by enabling the Outbox option in the Mail Preferences, previewing each mail before you send it, double-click the message to edit it if needed, previewing again and then sending the mail once it looks correct. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: pipewire config
On Thu, 2023-03-02 at 09:44 -0500, Frank Carmickle wrote:
> Does anyone have pipewire running as a system service
Pipewire in Debian only has a per-user service:
$ dpkg -L pipewire{,-pulse} | grep 'systemd.*\.'
/usr/lib/systemd/user/pipewire.service
/usr/lib/systemd/user/pipewire.socket
/usr/lib/systemd/user/pipewire-pulse.service
/usr/lib/systemd/user/pipewire-pulse.socket
That service has the root user disabled:
$ dpkg -L pipewire{,-pulse} | grep 'systemd.*\.' | xargs -d '\n' grep -ih
root
ConditionUser=!root
ConditionUser=!root
ConditionUser=!root
ConditionUser=!root
To override that, run this when logged in as root:
systemctl --user edit pipewire{,-pulse}.{service,socket}
Then save this to each of the override files:
[Unit]
ConditionUser=
Then reload the systemd config and start the root user services:
systemctl --user daemon-reload
systemctl --user start pipewire{,-pulse}.{service,socket}
Then check that the services are running:
systemctl --user is-active pipewire{,-pulse}.{service,socket}
Then if they aren't you can check for more details:
systemctl --user status pipewire{,-pulse}.{service,socket}
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Re: Are Their Any Live Kernel Patches in Debian?
On Wed, 2023-02-15 at 10:07 -0800, Chime Hart wrote: > Hi All: A friend of mine who seems to love-and-follow Ubuntu asks me if > Debian > has any live kernel patches, where you wouldn't need to boot the system? I am > in Debian SID-and-would `absolutely love an option such as that. Thanks so > much > in advance As I understand it, the Linux kernel live patches aren't possible to just produce automatically, it requires a team with enough Linux kernel knowledge to make it work. Debian doesn't have a team doing that yet. I don't think that Linux kernel live patches are very suitable for Debian unstable/sid because the major version of Linux in sid changes fairly often, although there are stable updates in sid, but those are fairly frequent. So the service would mostly be for stable/oldstable. Probably the best people in Debian to do that are the LTS team, who provide support for old Debian releases, including for Linux, the LTS team are paid by external sponsors, so they might have the financial resources needed to make this a reality for Debian. Please contact them about this service idea. https://lists.debian.org/debian-lts/ Also, I think that the base Linux kpatch tools are open source, but the infrastructure that RedHat/SUSE/Canonical use to provide them are not. However, I think the Gentoo folks do have some open infra code. https://github.com/dynup/kpatch https://wiki.gentoo.org/wiki/Elivepatch https://wiki.gentoo.org/wiki/Live_patching https://github.com/gentoo/elivepatch-server https://github.com/gentoo/elivepatch-client -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Orca Isn't Autostarting
On Fri, 2022-12-09 at 18:30 -0600, K0LNY_Glenn wrote: > Hope someone has some ideas. I note that orca is supposed to autostart by default: $ apt-file search autostart | grep ^orca: orca: /etc/xdg/autostart/orca-autostart.desktop Seems it only happens when the screen-reader option is enabled in the GNOME settings. I am not sure if MATE sets that setting though. $ grep -iE 'exec|condition' /etc/xdg/autostart/orca-autostart.desktop Exec=orca AutostartCondition=GSettings org.gnome.desktop.a11y.applications screen-reader-enabled You could try enabling the GNOME screen reader setting manually: $ gsettings set org.gnome.desktop.a11y.applications screen-reader-enabled true -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: add accessibility section to "List of sections" pages?
On Mon, 2020-02-24 at 07:51 -0800, Rich Morin wrote: > In response, I received the following suggestions from Paul Wise: > > > One against each of the relevant packages asking to update the section. FTR, I'm not entirely sure this is necessary, ISTR that section mismatches between the archive and packages are reported on tracker.debian.org, so maybe leave filing these bugs for a while. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Calamares in Debian 10
Michaël Caron Couturier wrote: > If the rumor is true, Calamares would be used in Debian 10. Calamares is available on the Debian 10 live images, which are available here if you would like to test them: https://cdimage.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/ > Previously known as innaccessible, it was a disaster when created, we > must stand against it unless the accessibility issues are fixed. The normal debian-installer is still available in the installer images and the boot menu of the live images so there are still accessible ways to install Debian 10. The debian-installer frontend that ran in Debian live images in earlier releases was very buggy so it was removed. Some time after the removal, some Debian folks discovered the Calamares cross-distro install system and added it to Debian and the live images. It looks like the cause of the accessibility issues is that Calamares runs as root instead of the user of the session. Calamares uses the KDE partition manager and version 4 of that allows it to be run as the user but unfortunately that was not released early enough for it to reach buster. So the good news is that the accessibility issues are being solved but the bad news is that they likely won't be for buster. https://github.com/calamares/calamares/issues/523 https://stikonas.eu/wordpress/2019/05/02/kde-partition-manager-4-0/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Hi, I am blind
On Mon, 2018-04-16 at 10:15 +0200, Samuel Thibault wrote: > Well, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855446 accessible-via seems different to what I propose. accessible-via references software that makes each package accessible. The proposed accessible-to would reference classes of abilities that are required to use the package. For example accessible-to::sighted. I've no idea if this sort of thing would be useful though. > but it seems https://debtags.debian.org/ hasn't gotten updated yet. I'd suggest filing another bug about that. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#859580: fenrir: typo in Description: e* spellchecker
Package: fenrir Version: 1.05-1 Severity: minor There is an extra e in the description before the first bullet point: reader. It has a lot of functionality: . --> e* spellchecker * advanced review functionality * copy/paste ... -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#706661: pocketsphinx: README file is not useful, please remove it
Package: pocketsphinx Version: 0.8-2 Severity: minor Usertags: readme The upstream README file contains only the package description and build instructions. As such it isn't useful to users of the binary package since they already have seen the package description and have a prebuilt binary. Please remove the upstream README file from the binary package. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pocketsphinx depends on: ii libc6 2.13-38 ii libjs-jquery 1.7.2+dfsg-1 ii libpocketsphinx1 0.8-2 ii libsphinxbase10.8-1 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#706663: python-pocketsphinx: missing dependency on python-sphinxbase
Package: python-pocketsphinx Version: 0.8-2 Severity: grave Justification: renders package unusable python-pocketsphinx is missing a dependency on python-sphinxbase: pabs@chianamo ~/tmp/speech-test $ cat test.py from pocketsphinx import Decoder HMM = /usr/share/pocketsphinx/model/hmm/en_US/hub4wsj_sc_8k LM = /usr/share/pocketsphinx/model/lm/en_US/hub4.5000.DMP DICT = /usr/share/pocketsphinx/model/lm/en_US/cmu07a.dic WAV = test.wav decoder = Decoder(hmm=HMM, lm=LM, dict=DICT) fh = open(WAV) fh.seek(44) # skip the WAV header decoder.decode_raw(fh) print decoder.get_hyp() # short for hypothesis pabs@chianamo ~/tmp/speech-test $ python test.py Traceback (most recent call last): File test.py, line 1, in module from pocketsphinx import Decoder File sphinxbase.pxd, line 150, in init pocketsphinx (pocketsphinx.c:7934) ImportError: No module named sphinxbase -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-pocketsphinx depends on: ii libc6 2.13-38 ii libpocketsphinx1 0.8-2 ii libsphinxbase10.8-1 ii python2.7.3-4 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#706664: python-pocketsphinx: exception importing Decoder: ValueError: PyCapsule_GetPointer called with invalid PyCapsule object
Package: python-pocketsphinx Version: 0.8-2 Severity: normal Importing just the decoder module fails, the module itself should handle any initialisation that is needed to make this work. Importing the whole pocketsphinx module and then calling the decoder from that works though. pabs@chianamo ~/tmp/speech-test $ cat test.py from pocketsphinx import Decoder HMM = /usr/share/pocketsphinx/model/hmm/en_US/hub4wsj_sc_8k LM = /usr/share/pocketsphinx/model/lm/en_US/hub4.5000.DMP DICT = /usr/share/pocketsphinx/model/lm/en_US/cmu07a.dic WAV = test.wav decoder = Decoder(hmm=HMM, lm=LM, dict=DICT) fh = open(WAV) fh.seek(44) # skip the WAV header decoder.decode_raw(fh) print decoder.get_hyp() # short for hypothesis pabs@chianamo ~/tmp/speech-test $ python test.py Traceback (most recent call last): File test.py, line 1, in module from pocketsphinx import Decoder File sphinxbase.pxd, line 150, in init pocketsphinx (pocketsphinx.c:7935) ValueError: PyCapsule_GetPointer called with invalid PyCapsule object -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-pocketsphinx depends on: ii libc6 2.13-38 ii libpocketsphinx1 0.8-2 ii libsphinxbase10.8-1 ii python2.7.3-4 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#706664: python-pocketsphinx: exception importing Decoder: ValueError: PyCapsule_GetPointer called with invalid PyCapsule object
Control: severity -1 important On Fri, 2013-05-03 at 12:26 +0800, Paul Wise wrote: Importing just the decoder module fails, the module itself should handle any initialisation that is needed to make this work. Importing the whole pocketsphinx module and then calling the decoder from that works though. Actually it looks like the issue is that it needs to be imported twice: pabs@chianamo ~/tmp/speech-test $ python Python 2.7.3 (default, Jan 2 2013, 13:56:14) [GCC 4.7.2] on linux2 Type help, copyright, credits or license for more information. from pocketsphinx import Decoder Traceback (most recent call last): File stdin, line 1, in module File sphinxbase.pxd, line 150, in init pocketsphinx (pocketsphinx.c:7935) ValueError: PyCapsule_GetPointer called with invalid PyCapsule object from pocketsphinx import Decoder from pocketsphinx import Decoder pabs@chianamo ~ $ python Python 2.7.3 (default, Jan 2 2013, 13:56:14) [GCC 4.7.2] on linux2 Type help, copyright, credits or license for more information. import pocketsphinx Traceback (most recent call last): File stdin, line 1, in module File sphinxbase.pxd, line 150, in init pocketsphinx (pocketsphinx.c:7935) ValueError: PyCapsule_GetPointer called with invalid PyCapsule object import pocketsphinx import pocketsphinx import pocketsphinx -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: [Pkg-fonts-devel] ITP: fonts-opendyslexic
On Wed, Jan 16, 2013 at 6:41 PM, Tanguy Ortolo wrote: Any advice? I don't know much about fonts, but AFAIK OpenType is an enhanced version of TrueType so it probably doesn't make sense to ship anything but OpenType. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6epcyterorjxyqf554zaoxy_qtcgq6xfph_jtuhrnh...@mail.gmail.com
Re: RFS: sonic
On Sun, Apr 17, 2011 at 4:54 AM, Bill Cox waywardg...@gmail.com wrote: I have to admit I haven't figured out how to distribute ChangeLog properly. My google-fu is failing me. I'd like to get rid of the override. Also, like some other projects, like speech-dispatcher, I'm keeping the log in git, and ChangeLog is just a dummy file to make autotools happy. It doesn't really add any value to distribute it, but it makes 'lintian --pedantic' happy. What's the right thing to do in this case? Shipping an empty changelog file is useless. Either ship a useful changelog in the upstream tarball or don't ship a less than useful changelog in the Debian binary package. lintian is only informational (especially at pedantic level), ignore its warnings if they are not useful. For upstream projects I personally use git2cl or similar at `make distcheck` time to generate a useful ChangeLog for inclusion in the upstream tarball. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikMk�QpkTdyof3ss-Bxu_X8=p...@mail.gmail.com
