Hola, Eloi
> Acabo de recordar que fa un temps (oldstable o fins i tot
> oldoldstable) hi va haver un canvi important a la comanda su,
> bàsicament hi havia dues implementacions i es va canviar d'una
> a l'altra per defecte, que tenia algunes subtileses. Crec que
> es va documentar a les release
Escric ràpid i de memòria perquè tinc poc temps ara mateix, intentaré
documentar la resposta millor quan pugui...
El 24/9/21 a les 17:58, Alex Muntada ha escrit:
[...]
- millorar l'script de postinst de postgres perquè utilitzi algun
altre mecanisme per canviar a l'usuari postgres
Acabo
Hola, Julio
> la directiva del fitxer
> /etc/pam.d/su
> és
> # auth sufficient pam_rootok.so
> Si la descomentem el postgresql funciona.bé, ja que lògicament
> ja no demana el pass
Confirmo que comentant la directiva em passa el mateix que a
vosaltres. Instal·lant dialog em surten els
Hola Àlex,
la directiva del fitxer
/etc/pam.d/su
és
# auth sufficient pam_rootok.so
Si la descomentem el postgresql funciona.bé, ja que lògicament ja no demana el
pass, però llavors tenim un "forat" pel ticket de kerberos :)
...
Has de descomentar la 2a línia.
S'entèn?
Le 23 septembre
Hola, Julio
> ... com que a la configuració del nostre pam teníem una
> directiva que obligava a root a demanar password quan feia su
> l'script d'instal·lació es parava demanant un password, però
> tant era el que escriguessis, o que en una altra terminal
> posessis el password a l'usuari
Hola Julio,
El que em sorprén en aquella instrucció no es tant el que demani un password
>
Doncs és precisament això, el que em sorprèn... que demani un password. En
principi, des de qualsevol shell de root hauríem de poder connectar-nos a
qualsevol usuari amb shell, sense necessitat de
Le 21 septembre 2021 08:01:43 GMT+02:00, jordi Perera
a écrit :
>On 20/9/21 23:56, Julio Amorós wrote:
>> Hola,
>> ../.. a la configuració del nostre pam teníem una
>> directiva que obligava a root a demanar password quan feia su > ../..
>>
>> I la instrucció:
>>
>> * su -s /bin/sh
On 20/9/21 23:56, Julio Amorós wrote:
Hola,
../.. a la configuració del nostre pam teníem una
directiva que obligava a root a demanar password quan feia su > ../..
I la instrucció:
* su -s /bin/sh postgres -c "test -O /var/lib/postgresql &&
test -G /var/lib/postgresql" || \
- Mail original -
> De: "patrick jollant"
> À: debian-user-french@lists.debian.org
> Envoyé: Lundi 13 Septembre 2021 11:56:02
> Objet: Bug : Evince - Impression PDF freezes
> Bonjour,
> ne sachant où exposer le problème, j'ai ouvert un sujet sur ce forum
>
Bonjour,
- supprimer le paquet ipp-usb me paraît une mauvaise idée car c'est une
dépendance:
didier@hp-notebook14:~$ apt rdepends ipp-usb
ipp-usb
Reverse Depends:
Recommande: cups-daemon
Recommande: libsane1
Recommande: sane-airscan
Ton unique imprimante-scanner peut être détectée
Perhaps it should be said that personal use of gpg and the use that a
system administrator makes of it and key-ing are different use-cases. So we
might expect fewer assumptions to hold and greater mystery :-)
On Sat, Jun 26, 2021, 1:53 PM wrote:
> On Sat, Jun 26, 2021 at 08:42:26AM -0400, Cindy
On Sat, Jun 26, 2021 at 08:42:26AM -0400, Cindy Sue Causey wrote:
> On 6/26/21, Andrei POPESCU wrote:
[...]
> > Well, it makes perfect sense if you remember that "everything is a
> > file", even if there are exceptions (e.g. network devices).
>
>
> Hopefully I'm reading this right. While on
On 6/26/21, Andrei POPESCU wrote:
>> Andrei, thanks for having picked up my problem and having cared for the
>> release notes to comment on it, and also for supposedly having motivated
>> Julian Andres Klose to publish a very helpful blog post on the related
>> subject. Brad Rogers here in the
On 26.06.21 11:54, Andrei POPESCU wrote:
(...)
Very good points, all appreciated.
Feel free to suggest patches for it through bugs against the harden-doc
package, or merge requests in Salsa if the Maintainer is accepting them.
I'll do so. I decided, motivated also by observing how you are
On Jo, 24 iun 21, 16:42:34, Marco Möller wrote:
> On 21.06.21 07:58, Andrei POPESCU wrote:
> > On Du, 20 iun 21, 10:20:42, Andrei POPESCU wrote:
> > > Package: release-notes
> > > X-Debbugs-Cc: debian-user@lists.debian.org, a...@packages.debian.org
> > >
> > > On Sb, 19 iun 21, 22:07:35, Marco
On 21.06.21 07:58, Andrei POPESCU wrote:
On Du, 20 iun 21, 10:20:42, Andrei POPESCU wrote:
Package: release-notes
X-Debbugs-Cc: debian-user@lists.debian.org, a...@packages.debian.org
On Sb, 19 iun 21, 22:07:35, Marco Möller wrote:
Command apt-key and its man page say that apt-key is
On Du, 20 iun 21, 10:20:42, Andrei POPESCU wrote:
> Package: release-notes
> X-Debbugs-Cc: debian-user@lists.debian.org, a...@packages.debian.org
>
> On Sb, 19 iun 21, 22:07:35, Marco Möller wrote:
> >
> > Command apt-key and its man page say that apt-key is deprecated, but do not
> > suggest an
On Fri, May 21, 2021 at 06:47:17PM -0400, Mohamud Ali wrote:
> dictionory
> Sorry, command-not-found has crashed! Please file a bug report at:
> http://www.debian.org/Bugs/Reporting
> Please include the following information with the report:
>
> command-not-found version: 0.3
> Python version:
command spelling??
L
-Original Message-
From: Mohamud Ali [mailto:khtos...@icloud.com]
Sent: Friday, May 21, 2021 3:47 PM
To: debian-user@lists.debian.org
Subject: Bug reportin
dictionory
Sorry, command-not-found has crashed! Please file a bug report at:
On Fri, May 21, 2021 at 06:47:17PM -0400, Mohamud Ali wrote:
> Python version: 3.9.1 final 0
> Distributor ID: Kali
> Description: Kali GNU/Linux Rolling
Please report this to your operating system's support team, not to
Debian's user mailing list, or any other place.
David Wright wrote:
> AIUI you really want to avoid using accented characters or any sort
> of composition in your username and password. The reason is that if
> your computer gets set in any unexpected language setting (or unset),
> you might not be able to login at all, and unable to correct
On Sat 10 Apr 2021 at 19:11:15 (-0400), mcgarrett wrote:
> > On April 10, 2021 at 5:53 PM laurent aerens
> > wrote:
> >
> > Package: unknown
> >
> > Version: debian 9 - 10
> >
> > Severity: minor
> >
> > When I type accent marks (¨^´`) in the terminal followed by a letter
>
On Sat 10 Apr 2021 at 23:53:27 (+0200), laurent aerens wrote:
> Package: unknown
>
> Version: debian 9 - 10
>
> Severity: minor
>
> When I type accent marks (¨^´`) in the terminal followed by a letter
> (that does not match with the accent) (for example ^ and the letter n)
> nothing happens and
On Sat, Apr 10, 2021 at 11:53:27PM +0200, laurent aerens wrote:
> Package: unknown
>
> Version: debian 9 - 10
>
> Severity: minor
This looks like you're attempting to generate headers for a bug report,
except that you're writing to debian-user rather than to the bug tracking
system, and you've
> On April 10, 2021 at 5:53 PM laurent aerens wrote:
>
>
> Package: unknown
>
> Version: debian 9 - 10
>
> Severity: minor
>
> When I type accent marks (¨^´`) in the terminal followed by a letter
> (that does not match with the accent) (for example ^ and the letter n)
>
On 21.03.2021 12:40, Andrei POPESCU wrote:
[Bcc: debian-boot]
Dear Debian-User subscribers,
The Release Notes editor is asking whether this is still an issue for
bullseye (i.e. if the patch to Debian Installer mentioned below was
applied in the meantime).
It will be a while until I get to
[Bcc: debian-boot]
Dear Debian-User subscribers,
The Release Notes editor is asking whether this is still an issue for
bullseye (i.e. if the patch to Debian Installer mentioned below was
applied in the meantime).
It will be a while until I get to check that. If someone can confirm
either way
On Sun, 14 Mar 2021 21:20:39 -0400
Jude DaShiell wrote:
> Why is frobtads missing from debian repositories? The frobtads package
> makes it possible for those living outside of g.u.i. land to play tads
> games on the console.
frobtads is in Debian non-free, in Sid and Jessie:
On Sun, Mar 14, 2021 at 21:20:39 -0400, Jude DaShiell wrote:
> Why is frobtads missing from debian repositories?
Looking at the tracker, the package is held back by "failure to build from
source" bugs, which are considered RC critical:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836934
Ohh, this packages hasn't been update for so long.
If no objection, I will upload the current git snapshot.
Tiezhu Yang 于2021年2月24日周三 上午11:15写道：
>
> (1) Background
> Source: luajit
> Version: luajit_2.1.0~beta3+dfsg-5.3_mips64el.deb
> Severity: important
> Link:
Thanks Andrei.
On Mon, Dec 14, 2020, 5:15 AM Andrei POPESCU
wrote:
> Package: release-notes
> X-Debbugs-CC: debian-user@lists.debian.org
>
> Dear Release Notes Maintainers,
>
> Some text based on below would make sense for the Release Notes for
> buster. If agreed I'll try to come up with a
On Ma, 27 oct 20, 20:15:13, Jonathan wrote:
> Good Evening,
>
> I was attempting to get my microphone working on my T14 AMD as it is the
> only non-functioning piece I was aware of. Browsing possible solutions I was
> shown the following could fix the issue if added to the kernel config:
>
>
On Sb, 03 oct 20, 16:35:00, thinkingtw...@tutanota.com wrote:
> Hello,
>
> Having gone through Debian's ReportBug system, I am unsure which
> packages the issue is coming from hence the email contact.
>
> The problem is quite straightforward. After the last update from Linux
> Kernel
On Tue, Sep 22, 2020 at 09:10:15AM +1000, Michael Slade wrote:
> I don't know what package to assign this to so I guess I can't use the usual
> bug reporting mechanism.
>
> I have a debian bullseye mate desktop with a custom keyboard shortcut set up
> to run xterm. I noticed that an ssh agent is
On Vi, 11 sep 20, 07:26:21, Volker Bäurer wrote:
> Hello,
>
> I use the Clamav/Buster. When restarting the service I get:
>
> "... mkdir[17696]: /bin/mkdir: cannot create directory '/run/clamav': File
> exists"
>
> This message is useless because the directory exists and I have seen it since
On Thu, 27 Aug 2020 03:04:21 + (UTC)
Long Wind wrote:
> it crash, reboot can also fail
> at first i thought it's hard disk faultlater i realize that it's more
> likely caused by wireless bug i don't have time to file bug report
It looks like this issue has come up before in Buster.
Hi,
On Sun, 19 Jul 2020 18:47:37 -0400
The Wanderer wrote:
> Looking at it, I don't see anything which strikes me as qualifying as
> buggy. Can you clarify what about it you see as being a misbehavior
> problem?
>
(...)
> It appears that the software previously provided in libgcc1 is now being
On 2020-07-19 at 18:14, Default User wrote:
> On 2020-07-19 at 16:27, Stefan Monnier wrote:
>
>>> This has been going on since the beginning of June, 2020, with
>>> no end in sight.
>>> Bug #961990 - IIUC, no activity since 2020-06-02.
>>>
>> You show a session where you reject all the proposed
On 2020-07-19 at 16:27, Stefan Monnier wrote:
>> This has been going on since the beginning of June, 2020, with no end in
>> sight.
>> Bug #961990 - IIUC, no activity since 2020-06-02.
>>
> You show a session where you reject all the proposed solutions, but
> I don't see any justification why
On 2020-07-19 at 16:27, Stefan Monnier wrote:
>> This has been going on since the beginning of June, 2020, with no end in
>> sight.
>> Bug #961990 - IIUC, no activity since 2020-06-02.
>
> You show a session where you reject all the proposed solutions, but
> I don't see any justification why
> This has been going on since the beginning of June, 2020, with no end in
> sight.
> Bug #961990 - IIUC, no activity since 2020-06-02.
You show a session where you reject all the proposed solutions, but
I don't see any justification why you reject those choices, so I don't
know what you
[it's likely you are not subscribed, sorry for the Cc: in case you are]
On Sb, 20 iun 20, 07:58:33, gilleswicki wrote:
> Hello, I found a bug on my system and tried to report it using the
> reportbug software. But as I don't know which packet is the cause of
> the bug, following the procedure
On Thu, 30 Apr 2020 15:13:29 +0300
deuxb...@gmail.com wrote:
> hello,
> i would like to report a bug on Debian.
> fresh install on my system (Chuwi minibook) - trying to shutdown causes
> reboot (windows works without a problem).
Thank you! Please use the reportbug' tool:
Kamil Jońca composed on 2019-11-27 22:31 (UTC+0100):
>...X.org 1.20.4 driver: modesetting...
To switch to nouveau from modesetting could be as simple as installing
xserver-xorg-video-nouveau. If it's already installed, you may need to specify
it
in /etc/X11/xorg.conf.d/50-device.conf to
Felix Miata writes:
> Kamil Jońca composed on 2019-11-27 21:35 (UTC+0100):
>
>> Felix Miata writes:
>
>>> Kamil Jońca composed on 2019-11-27 19:23 (UTC+0100):
>>
There is debian box
>
>>> Which Debian version?
>
>> sid.
>
> I don't have Sid on my box with G84.
> ...
>>> # inxi -V |
Kamil Jońca composed on 2019-11-27 21:35 (UTC+0100):
> Felix Miata writes:
>> Kamil Jońca composed on 2019-11-27 19:23 (UTC+0100):
>
>>> There is debian box
>> Which Debian version?
> sid.
I don't have Sid on my box with G84.
...
>> # inxi -V | head -n1
>> inxi 3.0.37-00 (2019-11-19)
>> #
Felix Miata writes:
> Kamil Jońca composed on 2019-11-27 19:23 (UTC+0100):
>
>> There is debian box
>
> Which Debian version?
sid.
>
>> with:
>> --8<---cut here---start->8---
>> 08:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT]
Kamil Jońca composed on 2019-11-27 19:23 (UTC+0100):
> There is debian box
Which Debian version?
> with:
> --8<---cut here---start->8---
> 08:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT]
> (rev a1)
> --8<---cut
Yes, I was originally using another desktop, lxde, and switched to
gnome. Now I can't switch back
On 09/18/2019 08:01 AM, songbird wrote:
Thomas H. George wrote:
...
Two problems after a distribution upgrade to Buster
1. At login window after boot up the desktop selection is locked a
Gnome.
Thomas H. George wrote:
...
> Two problems after a distribution upgrade to Buster
>
> 1. At login window after boot up the desktop selection is locked a
> Gnome. That is, if the symbol to change the desktop selection is
> selected a list of available desktops is displayed with a dot indicating
On Mi, 01 mai 19, 11:33:23, Hans wrote:
> Hi folks,
>
> I am running into the little issue, that I can not set the clock in plasma5
> (KDE). Neither as a normal user nor as root.
>
> I want to set the clock using systemd to set the time automatically, but when
> ever I want set the hook and
On 2019-04-25, morgan wrote:
> Hi,
>
> I installed Eclipse on my debian stretch but it crashes when launching.
> I attached the logs, I don't understand if I could do anything, nor in
> which package(s) are the issues. Sorry for not using reportbug for this
> report.
>
> Feel free to contact me
In-Reply-To: <3685896c-ded1-395b-6312-cef63a9d2...@pouzenc.fr>
>Ludovic Pouzenc
>I have doubts about the right package to submit against (gnome-shell,
>pulseaudio, wayland, udev, kernel)
>Poor work-around :
>
>- enable accessibility feature "visual-bell". The problem vanishes,
Since the
Lucas,
Já tentou dar um apt-get -f install ?
De: Fred Maranhão
Enviado: quinta-feira, 4 de abril de 2019 08:58
Para: Lista Debian
Assunto: Re: Bug Instação PHP
você pode atualizar o seu sistema antes? rodando
apt update; apt upgrade
pode mostrar o conteúdo do
você pode atualizar o seu sistema antes? rodando
apt update; apt upgrade
pode mostrar o conteúdo do sources.list?
assim:
# more /etc/apt/sources.list /etc/apt/sources.list.d/*
::
/etc/apt/sources.list
::
deb http://security.debian.org/debian-security stretch/updates main
Hi Sandro,
great! This did the trick. I deleted the line beginning with "Headerstate" and
everything is working fine again.
However, I knew, that the entry must have been in kmail2rc, but I could not
really understand the values in this line. I can only confirm what you said:
not really
Hello Andy,
Thank you very much for your lengthy and very informative answer.
After some investigation, I discovered that it was /dev/sdc that had
some problems. So I took it out of the Rais 1 array. But this didn't
really help since I got other freeze.
grep "120 seconds" kern.log
Feb 18
Hi Steve,
On Fri, Feb 15, 2019 at 09:35:27AM +0100, steve wrote:
> >for i in /dev/sd{b..f}; do echo "DISK: ${i}"; smartctl -l scterc "${i}";
> >sleep 3; done
>
> I get this for sdb and sdc
>
> SCT Error Recovery Control:
> Read: Disabled
> Write: Disabled
>
> and this for
Hi all,
Thank you for your answers. Was busy so couldn't answer before.
My system disk (with /, /usr, /boot and /boot/efi) is on a separate
(non-RAID) disk sda.
Maybe this works for you, too?
You can try:
cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6]
Hello Steve,
As some of the other responders already said, check your drives' SMART
values.
But a disk may fail without any indication in the SMART table. I've seen
this a couple of years ago and documented it here:
On 2/12/19 12:48 PM, David Christensen wrote:
I had a Linux md RAID0 (mirror) ...
Correction -- RAID1 is mirror.
David
On 12.02.2019 16:08, steve wrote:
> Hi There,
>
> Here is what I get on my up to date stretch box:
>
> Feb 10 12:19:12 box kernel: [ 7734.562060] INFO: task md0_raid1:461
> blocked for more than 120 seconds.
> Feb 10 12:19:12 box kernel: [ 7734.562068] Tainted: P
> OE
On 2/12/19 11:37 AM, Tom Bachreier wrote:
Feb 12, 2019, 12:08 PM by dl...@bluewin.ch:
The system blocks for about 3 minutes and then I get back a hand on it.
I have a similar - maybe the same - problem in buster - see the thread
"Software RAID blocks" on this list about a month ago.
Feb 12, 2019, 12:08 PM by dl...@bluewin.ch:
> Hi There,
>
> Here is what I get on my up to date stretch box:
>
> Feb 10 12:19:12 box kernel: [ 7734.562060] INFO: task md0_raid1:461 blocked
> for more than 120 seconds.
> [...]
> Feb 10 12:19:12 box kernel: [ 7734.562192] INFO: task
On 2/12/19 3:08 AM, steve wrote:
Hi There,
Here is what I get on my up to date stretch box:
Feb 10 12:19:12 box kernel: [ 7734.562060] INFO: task md0_raid1:461
blocked for more than 120 seconds.
and so one.
The system blocks for about 3 minutes and then I get back a hand on it.
I'm no
I don't understand the point of this email -- are you advocating for some
change, or to avoid some change?
(I looked at the bug report and skimmed some of the messages -- it seems like
by posting this to the debian-user list you are looking for comments or
support here, but the issue is not
Thorsten Glaser:
> Just accept that this idea, originating from the systemd people at
Fedora/Freedesktop, is NOT welcome to classical Unix people.
Ahem! We classical Unix people experienced this idea in the late 1980s,
from where it *really* originated, Sun and AT
*
Alex Muntada writes:
> Anava a suggerir-te que per aquestes coses provis el shellcheck
> però veig que la recomanació que dóna és diferent:
>
> In gpg-tty.sh line 2:
> export GPG_TTY=$(tty)
>^-- SC2155: Declare and assign separately to avoid masking return
> values.
>
> No tinc clar si
Hola Ernest,
> Sí, era aquesta línia:
>
> export GPG_TTY=$(tty)
>
> ...
>
> La solució és posar-ho entre cometes
>
> export GPG_TTY="$(tty)"
Anava a suggerir-te que per aquestes coses provis el shellcheck
però veig que la recomanació que dóna és diferent:
In gpg-tty.sh line 2:
export
Antoni Villalonga writes:
> Em sembla que alguna comanda dona un error i aquest s'acaba parsejant
> malament, resultant un error extrany.
Sí, era aquesta línia:
export GPG_TTY=$(tty)
L'ordre tty tornava el text "no és un tty", de manera que després de
la substitució quedava
export GPG_TTY=no
Hola,
Em sembla que alguna comanda dona un error i aquest s'acaba parsejant
malament, resultant un error extrany.
També podries provar un altre wm.
Això pot servir com a wm dummy. Si aguanta 30 segons sense tornar al gestor
de sessions
#!/usr/bin/env bash
sleep 30
Més facil és instalar un
Hola,
tictacbum writes:
> que hi tens a la línia 43 del /etc/X11/Xsession? al meu hi tinc un
> comentari, per això m'estranya que et salti a aquesta línia
Sí, hi ha un comentari. És l'Xsession de Debian, no l'he tocat. Diria
que el número de línia no és fiable, perquè l'Xsession afegeix
Hola Ernest,
que hi tens a la línia 43 del /etc/X11/Xsession? al meu hi tinc un
comentari, per això m'estranya que et salti a aquesta línia
has provat de comentar tot el de .environment excepte l'export
LANG="ca_ES.UTF-8" i provar d'entrar a veure si peta?
salut!
Lluís
Missatge de Ernest Adrogué
On Tue, 11 Sep 2018 21:24:42 -0400
Ric Moore wrote:
Hello Ric,
>Works a charm for me, and has for years, BUT every once in awhile
As it does for many, I'm sure.
>the volume levels back up to 100%. Pulse rides on top of alsa, so alsa
And that's a problem. Now, if sound goes wrong there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 11, 2018 at 08:28:02PM -0500, james wrote:
> E: The value 'stable-updates' is invalid for APT::Default-Release as
> such a release is not available in the sources
> E: _cache->open() failed, please report.
Please post here the contents of
On 09/10/2018 08:27 AM, Brad Rogers wrote:
On Mon, 10 Sep 2018 11:53:01 + (UTC)
Curt wrote:
Hello Curt,
So uninstall it then in that unfortunate case--with extreme prejudice
Time.
Oh, and I can't be arsed to try PA in the first place. :-)
Or are we dealing with the supernatural
On Monday, September 10, 2018 09:37:28 AM Thomas Schmitt wrote:
> I could offer my program cdrskin as real example.
> It is a cdrecord/wodim compatibility wrapper but exceeds both when it
> comes to DVD and BD media.
Thanks, for:
* the useful example, and
* changing the Subject: line
Hi.
On Mon, Sep 10, 2018 at 03:37:28PM +0200, Thomas Schmitt wrote:
> Hi,
>
> Reco wrote:
> > > It's the usual. A compatibility wrapper can never exceed the original.
>
> rhkra...@gmail.com wrote:
> > Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how
> > to
Hi,
Reco wrote:
> > It's the usual. A compatibility wrapper can never exceed the original.
rhkra...@gmail.com wrote:
> Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how
> to say what I want to say, let me try a made-up example.
I could offer my program cdrskin as real
On Mon, 10 Sep 2018 11:53:01 + (UTC)
Curt wrote:
Hello Curt,
>So uninstall it then in that unfortunate case--with extreme prejudice
Time.
Oh, and I can't be arsed to try PA in the first place. :-)
>Or are we dealing with the supernatural here (software from Hell)?
I'm wary because of
On 2018-09-10, Brad Rogers wrote:
>
> The machine it does affect is the one that I routinely use, which has
> been in use for longer than PA has been around. I /could/ install PA,
> but am reluctant to do so, since sound works here ATM and I'm concerned
> that installing PA may cause issues for
On Monday, September 10, 2018 05:49:01 AM Reco wrote:
> It's the usual. A compatibility wrapper can never exceed the original.
Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how
to say what I want to say, let me try a made-up example.
Suppose some piece of software is
On Mon, 10 Sep 2018 12:49:01 +0300
Reco wrote:
Hello Reco,
>On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote:
>> I've not been running apulse long, but so far, no crashes in Ff 62.
>So upstream lies then. To quote apulse's README.md:
Maybe, maybe not. It's only been a couple of
Hi.
On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote:
> On Sun, 9 Sep 2018 11:43:39 +0300
> Reco wrote:
>
> Hello Reco,
>
> >Moreover, apulse causes Firefox to crash since Firefox version 58, as
>
> I've not been running apulse long, but so far, no crashes in Ff 62.
So
On Sun, 9 Sep 2018 11:43:39 +0300
Reco wrote:
Hello Reco,
>Moreover, apulse causes Firefox to crash since Firefox version 58, as
I've not been running apulse long, but so far, no crashes in Ff 62.
>apulse is a kludge, not a solution.
That's as may be (I don't have an opinion either way).
Rob van der Putten wrote:
> Does anyone know why ALSA is no longer supported?
You mean supported by Firefox? I guess they decided PA is more easy to
implement as default interface ... whatever underlaying audio system you
use.
I still could not understand why, but this seems irreversible.
to...@tuxteam.de (2018-09-09):
> Personally, I couldn't care less: I consider my browser's inability
> to make sounds a welcome *feature*, so not having Pulse (which is my
> default) just naturally takes care of that.
Same for me. And apulse seems to work for me anyway.
> Given the amount of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Sep 09, 2018 at 10:24:30AM +0200, Rob van der Putten wrote:
> Hi there
>
>
> Note: A reply in bugs failed.
>
> On 09/09/18 10:08, Marco Lucidi wrote:
>
> > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault
> > wrote:
> > > Unfortunately
Hi.
On Sun, Sep 09, 2018 at 10:24:30AM +0200, Rob van der Putten wrote:
> Hi there
>
>
> Note: A reply in bugs failed.
>
> On 09/09/18 10:08, Marco Lucidi wrote:
>
> > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault
> > wrote:
> > > Unfortunately AIUI upstream has stopped
On Sun, 22 Jul 2018 17:19:42 +0100,
Phil Wyett wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On Sun, 2018-07-22 at 18:55 +0300, Askar Safin wrote:
- 8< -
>>
>> I am unable listen music using https://vk.com/audio anymore.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 2018-07-22 at 18:55 +0300, Askar Safin wrote:
> Recently Debian Stretch introduced the most annoying bug ever: https://bugs.de
> bian.org/900533 ("chromium 67.0.3396.62-1: youtube video, gif's, html5, and
> movies no longer work"). It affects
Hi Mike,
Thank you a lot. Problem is solved. :-)
Best greetings, thanks again
Benjamin
On 03/07/18 13:53, Michael Stone wrote:
> On Tue, Jul 03, 2018 at 01:18:57PM +0200, Benjamin Herwig wrote:
>> I encountered some strange USB behaviour (also others on the internet,
>> for example
>>
On Tue, Jul 03, 2018 at 01:18:57PM +0200, Benjamin Herwig wrote:
I encountered some strange USB behaviour (also others on the internet,
for example
https://www.linuxquestions.org/questions/linux-hardware-18/what-does-cdc_acm-unknown-symbol-refcount_inc_not_zero-err-0-in-dmesg-mean-4175633136/)
On Mon, 30 Apr 2018 10:09:44 -0400 Roberto C. Sánchez sent:
> On Mon, Apr 30, 2018 at 04:18:01PM +0300, Abdullah Ramazanoglu wrote:
> >
> > AFAIK it is still there untouched in git sources, as originally
> > mentioned in the bug report
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896806
On Mon 30 Apr 2018 at 16:18:01 +0300, Abdullah Ramazanoglu wrote:
> On Mon, 30 Apr 2018 14:24:19 +0200 to...@tuxteam.de said:
> > On Mon, Apr 30, 2018 at 03:00:07PM +0300, Abdullah Ramazanoglu wrote:
> > > On Mon, 30 Apr 2018 06:43:03 +0200 to...@tuxteam.de said:
> >
> > [...]
> >
> > > > It
On Monday 30 April 2018 10:09:44 Roberto C. Sánchez wrote:
> On Mon, Apr 30, 2018 at 04:18:01PM +0300, Abdullah Ramazanoglu wrote:
> > AFAIK it is still there untouched in git sources, as originally
> > mentioned in the bug report
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896806
> >
>
On Mon, Apr 30, 2018 at 04:18:01PM +0300, Abdullah Ramazanoglu wrote:
>
> AFAIK it is still there untouched in git sources, as originally mentioned in
> the bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896806
>
> That aside, the question of whether it will ever get fixed in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Apr 30, 2018 at 03:00:07PM +0300, Abdullah Ramazanoglu wrote:
> On Mon, 30 Apr 2018 06:43:03 +0200 to...@tuxteam.de said:
[...]
> > It seems this issue is fixed upstream. Would you like to check that?
> >
> > Tone down. Apply Hanlon's razor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Apr 29, 2018 at 11:20:00PM +0300, Abdullah Ramazanoglu wrote:
> On Sun, 29 Apr 2018 12:52:54 -0700 Don Armstrong said:
>
> > If there is a concern here, it's a privacy concern. Google's public
> > statements regarding maintaining privacy and
101 - 200 of 2012 matches
Mail list logo
