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
*
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
Hi,
The Debian Bug Squashing Party earlier this month in Venlo, Netherlands was
productive and fun. Thanks a lot to Transceptor Technology, part of the
insign.it Group, for hosting[1] us, sponsoring food and being very hospitable
(you might know this company as the people behind the SiriDB[2
On Fri, 25 Jan 2019 12:59:16 +
Paul Sutton wrote:
> Hi
>
> I have set up report-bug however upon running I am informs me that
> gir1.2-vte-2.91
> is missing, this is required to run the program with the GUI.
>
> I have no problem installing this (and have don
Hi
I have set up report-bug however upon running I am informs me that
gir1.2-vte-2.91
is missing, this is required to run the program with the GUI.
I have no problem installing this (and have done) but just thought I
would mention it.
report bug defaults to the CLI version anyway.
Paul
s behavior.
As this is a rather odd bug, I am unsure how to gather more information, nor am
I sure what is causing it, as I have a feeling that it is a compilation of
issues.
Any help would be appreciated. Thank you!
Respectfully,
Chris Talbot
On 2019-01-23, Richard Hector wrote:
>
> Ok, it seems if I go through the list on the dsa page above, I can then
> download the packages from their respective pages on
> packages.debian.org, where they're listed along with checksums. Tedious,
> but should work :-)
>
> Richard
>
>
Not certain why
Hello, I recently upgraded to Debian Buster and now experience severe
graphical lag(10-15FPS on a blank desktop, less with a window open
according to KDE's built in FPS monitor) after resuming from suspend.
Reportbug said to contact this address because I don't know which
package is causing
On 23/01/19 5:05 PM, Richard Hector wrote:
> Hi all,
>
> I just read about the current apt security update on The Register:
>
> https://www.theregister.co.uk/2019/01/22/debian_package_manager_flaws/
>
> It suggests running apt update with redirects disallowed ... but
> security.debian.org
Hi all,
I just read about the current apt security update on The Register:
https://www.theregister.co.uk/2019/01/22/debian_package_manager_flaws/
It suggests running apt update with redirects disallowed ... but
security.debian.org appears to do a redirect.
There's a tip at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Debian Bug Squashing Party (BSP) in Gothenburg, Sweden - 7 April 2019
=
I am very happy to invite you to a Debian Bug Squashing Party in
Gothenburg, Sweden, on Sunday April 7th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Debian Bug Squashing Party (BSP) in Gothenburg, Sweden - 7 April 2019
=
I am very happy to invite you to a Debian Bug Squashing Party in
Gothenburg, Sweden, on Sunday April 7th
El 12/1/19 a les 12:40, a...@probeta.net ha escrit:
> Bon dia a tothom,
>
> Fa molt de temps que em barallo amb un bug, que intento acorralar, però
> no hi ha manera.
>
> Afecta a Debian Testing en el sistema gràfic, i aquí em veig molt
> perdut, entre controladors, s
Àlex writes:
> Sí així vaig fer. Vaig descarregar el nucli 4.9 de la Debian estable i
> el vaig instal.lar, i quan vull veure vídeo arrenco amb aquest nucli.
> Des de la versió 4.14 a la 4.19 la cosa ha anat malament i no sé si amb
> el temps es corregirà, però sempre puc canviar de hardware
El 14/1/19 a les 13:09, Àlex ha escrit:
El teu hardware gràfic és Radeon?
- Sí, és el AMD/ATI Richland (Radeon HD 8670D). Està integrat amb la
CPU: Quad Core AMD A10-6800K, és el que anomenen APU. Deu ser del 2013 o
14, tecnologia de 32 nm. Res de darrera generació. Evidenment, és un
model
El 12/1/19 a les 18:33, Eduard Selma ha escrit:
> El 12/1/19 a les 12:40, a...@probeta.net ha escrit:
>> Bon dia a tothom,
>>
>> Fa molt de temps que em barallo amb un bug, que intento acorralar,
>> però no hi ha manera.
>>
>> Afecta a Debian Testing en
> Pel que dius, semblaria un problema del compositor, que no actualitza
> l'estat de la pantalla correctament. Ara bé, si et passa amb Gnome i
> també amb Xfce, que utilitzen compositors diferents, aleshores m'inclino
> a pensar que és una altra cosa.
Sí, i amb Gnome amb Xorg es congelava tot
L+ALT+F7
>
> No sé ni per on començar. Algun consell?
Els problemes que tenen a veure amb el sistema gràfic són difícils de
solucionar pel teu compte, a no ser que siguis un expert en el tema. Si
el bug és reproduïble (és a dir es produeix sempre que fas alguna cosa
concreta), pots anar pr
El 12/1/19 a les 12:40, a...@probeta.net ha escrit:
Bon dia a tothom,
Fa molt de temps que em barallo amb un bug, que intento acorralar, però
no hi ha manera.
Afecta a Debian Testing en el sistema gràfic, i aquí em veig molt
perdut, entre controladors, servidors de finestres, gestors de
Fins al nucli 4.13 tot anava bé, però en actualitzar al nucli 4.14
l’escriptori Gnome es «congelava» cada pocs minuts. A tots els
següents nuclis fins el 4.19 el problema persisteix. A aquest enllaç
hi ha els canvis que aporta el nucli 4.14 a Radeon, però no els sé
interpretar:
Bon dia a tothom,
Fa molt de temps que em barallo amb un bug, que intento acorralar, però
no hi ha manera.
Afecta a Debian Testing en el sistema gràfic, i aquí em veig molt
perdut, entre controladors, servidors de finestres, gestors de
finestres, compositors, mesas, cairos, egl, etc.
Si
afterwards); it is important to
note that it does not happen after every boot)
- I do not know whether it can be linked to GNOME or any other package down to
pulseaudio
- I do not know which details could be useful ; I would be happy to submit a
much more detailed bug report as soon as I know how I
Il 06/01/19 12:41, Étienne Mollier ha scritto:
Since you can reproduce the bug in Debian, I guess it is worth a
report, with a mention to the upstream bug page and, if possible
the patch fixing it. Put information necessary to the context,
but no need to copy the entire thread on KDE bug
On 1/6/19 12:26 PM, Andrea Borgia wrote:
> Hi.
>
> Case in point: https://bugs.kde.org/show_bug.cgi?id=395875
>
> There is no corresponding bugreport for the Debian package; had I not found
> the upstream bug, I would have filed a report with nearly the same
> information,
Hi.
Case in point: https://bugs.kde.org/show_bug.cgi?id=395875
There is no corresponding bugreport for the Debian package; had I not
found the upstream bug, I would have filed a report with nearly the same
information, since my tests match the issue perfectly.
Question is, for tracking
Hello,
I have the issue in the subject when a right click on a USB drive and click
on "safely remove drive". I am on Debian 9.6 with gnome.
It happen with different drives and different usb ports.
Looking on the www it was an old 2.6 kernel bug.
Below hostnamectl output concerning ar
Howard writes:
> The URL for the Debian Bug project apparently isn't working or has
> changed. I've found two links that are not working. The first one is
> here in ReportBug, where the blue link for "Homepage of reportbug
> project" is broken. (The yellow tool tip s
On 12/6/2018 8:22 AM, Howard Johnson wrote:
> Aloha,
>
> The URL for the Debian Bug project apparently isn't working or has
> changed. I've found two links that are not working. The first one is
> here in ReportBug, where the blue link for "Homepage of reportbug
El 5/12/18 a les 16:37, Alex Muntada ha escrit:
...
>
> * [0] https://bugs.debian.org/810216
> * [1] https://bugs.debian.org/902620
Àlex:
ja estàs completament dins de Matrix, comptes ja basat en zero[1]
:
* [1]:
https://en.wikipedia.org/wiki/Zero-based_numbering#In_computer_programming
Aloha,
The URL for the Debian Bug project apparently isn't working or has
changed. I've found two links that are not working. The first one is
here in ReportBug, where the blue link for "Homepage of reportbug
project" is broken. (The yellow tool tip shows the bad URL being trie
i explicant-ho,
que també tanca un bug al respecte demanant més detalls:
https://salsa.debian.org/letsencrypt-team/certbot/certbot/blob/master/debian/certbot.cron.d
https://bugs.debian.org/908841
Salut,
Alex
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Alex Muntada
⢿⡄⠘⠷⠚⠋ Debian Developer - log.alexm.org
Hola Narcís,
inline:
On Wed, Dec 5, 2018 at 3:54 PM Narcis Garcia wrote:
>
> Amb "systemctl status certbot" veuràs que se t'ha disparat el mateix
> dia. Això vol dir que és un servei que fa una tasca (one-shot) i s'atura
> fins el següent torn, que no sé si són una o dues vegades al dia.
OK,
Crec que continua sent un bug perquè està duplicat en cron i en
systemd, perquè no avisa, és a dir: mal muntat en general, lo qual les
modificacions per una banda i no l'altre no es propaguen bé. Però el
meu problema sembla que ja està resolt!
Gràcies!
Pedro
[1]
# cat /lib/systemd/system
Hola,
Crec que letsencrypt té un bug per com està empaquetat a debian
Acostumo a treure els permisos de root a letsencrypt (i fer-ho amb un
usuari dedicat), això implica que al meu /etc/cron.d/certbot [1]
l'executa l'usuari letsencrypt enlloc de root
que intel·ligentment m'avisa si el vull
On Mon, 3 Dec 2018 09:41:21 -0600
craig macdonald wrote:
> Hello all,
>
> I've discovered a small bug in linux (wifi?) networking, but I haven't
> been able to report it because I don't seem to know the correct package
> to report the bug against.
>
> I bought an older
Hi.
Here, at debian-user, we reply to the list so the whole community would
benefit from the answers. Writing to a list participant directly can be
OK as long as something private is discussed. Which is clearly not the
case here.
On Mon, Dec 03, 2018 at 01:26:10PM -0600, craig macdonald
Hi.
On Mon, Dec 03, 2018 at 09:41:21AM -0600, craig macdonald wrote:
> Hello all,
>
> I've discovered a small bug in linux (wifi?) networking, but I haven't
> been able to report it because I don't seem to know the correct
> package to report the bug against.
Actually yo
Hello all,
I've discovered a small bug in linux (wifi?) networking, but I haven't been
able to report it because I don't seem to know the correct package to report
the bug against.
I bought an older, "obsolete" usb wifi adapter (D-Link DWA-130, Rev. F) after
reading of the difficul
fig/KVIrc and try to load this
> one configuration directory instead?
>
I actually noticed it too and tried the trick with renaming directories before
I filed the bug, it did not work for me. Now trying different things I found
the winning combination I think that solves the issue:
1. Rename &q
local10, on 2018-11-29:
> Nov 27, 2018, 7:24 PM by loca...@tutanota.com:
> > Am I the only one who's having this issue? It's kind of
> > annoying and there's no response from the maintenance team:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908420
&g
Nov 27, 2018, 7:24 PM by loca...@tutanota.com:
> Am I the only one who's having this issue? It's kind of annoying and there's
> no response from the maintenance team:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908420
> <https://bugs.debian.org/cgi-bin/bugrep
Hi,
Am I the only one who's having this issue? It's kind of annoying and there's no
response from the maintenance team:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908420
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908420>
Regards,
On Fri, Nov 23, 2018 at 11:39:48AM -0200, Luciano Andress Martini wrote:
> 2- Try to change the ip in /etc/network/interfaces
> 3- Run ifdown enp0s3
> 4- Run ifup enp0s3
Perhaps you want to do it this way instead:
2- ifdown enp0s3
3- edit /etc/network/interfaces
4- ifup enp0s3
I am not sure if my answers are reaching the users because i did not
received it back so sorry to creating a new thread, but i think this
is very important, please follow this steps to emulate it:
1- Install Debian 9.6 without graphical interface.
2- Try to change the ip in
On 2018-11-05, Greg Wooledge wrote:
>
> In this case, he probably "told it to run in a terminal", and whether
> the terminal uses a login shell or not is irrelevant. The fact that
> now it's running the program inside a terminal (or possibly a terminal
> plus a shell), instead of directly
On Mon, Nov 05, 2018 at 12:31:11PM +, Andy Smith wrote:
> - You have a launcher file that references an executable. In normal
> cases calling the launcher from your desktop environment (I don't
> know if this is by menu or button or something else) causes the
> binary to run. I'm
you so it would be a lot of
work to try this out. I'm only trying to help you file the right bug
against the right software, but if that is not welcome just say so
and I am happy to leave you to it.
If I understand correctly:
- You have a launcher file that references an executable. In normal
On 11/04/2018 07:34 AM, Andy Smith wrote:
On Sun, Nov 04, 2018 at 07:24:04AM -0600, Richard Owlett wrote:
Turns out there was a *YUCKY* choice for a default setting.
In the default profile for mate-terminal there is a choice titled
"Run command as a login shell".
The option is *not*
have spewed some error into some log
file, but did not pop up a dialog saying "That isn't a valid binary"
or whatever. I don't think that you would get different results no
matter what setting you had for running terminals as login or not.
So if it bothers you that trying to execute g
.
A custom MATE launcher pointed the corrupted file.
When the launcher icon was clicked there was no response whatsoever.
Including *NO ERROR MESSAGE*
Is this a bug or a feature?
If a feature, why?
Turns out there was a *YUCKY* choice for a default setting.
In the default profile for mate-terminal
On 2018-10-31, rhkra...@gmail.com wrote:
>> >>
>> >> Due a non-reproducible sequence of events, a binary executable was over
>> >> written by the contents of a man page in pure text format.
>> >
>> > Just to (maybe?) help with the proper focus, was this a human error or
>> > something that
ailed PEBKAC ;< "
Ok, then, it doesn't seem to indicate a disk problem (as some seemed to
suspect).
Reco's comment that it could be a "(mis)feature" and Greg's response led
me to investigate further. I'm personally convinced there is a bug
having some aspects of being a "c
On Wednesday, October 31, 2018 11:45:15 AM Richard Owlett wrote:
> On 10/31/2018 10:31 AM, rhkra...@gmail.com wrote:
> > On Wednesday, October 31, 2018 10:14:40 AM Richard Owlett wrote:
> >> Debian 9.1 with MATE installed from DVD set.
> >>
> >> Due a non-reproducible sequence of events, a binary
ncher pointed the corrupted file.
When the launcher icon was clicked there was no response whatsoever.
Including *NO ERROR MESSAGE*
Is this a bug or a feature?
If a feature, why?
nse whatsoever.
> Including *NO ERROR MESSAGE*
> Is this a bug or a feature?
> If a feature, why?
ver.
Including *NO ERROR MESSAGE*
Is this a bug or a feature?
If a feature, why?
A (mis)feature. Any executable text file without defined shebang is a
shell script. In this case - a syntactically invalid shell script.
So it can be executed, but the child shell will exit immediately.
I thin
On Wednesday 31 October 2018 10:39:17 Gene Heskett wrote:
> On Wednesday 31 October 2018 10:31:40 Reco wrote:
> > Hi.
> >
> > On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> > > On 10/31/2018 09:18 AM, Curt wrote:
> > > > On 2018-10-31, Richard Owlett wrote:
> > > > >
d file.
>>> When the launcher icon was clicked there was no response whatsoever.
>>> Including *NO ERROR MESSAGE*
>>> Is this a bug or a feature?
>>> If a feature, why?
>>>
>>>
>>>
>>
>>
>
>
>
--
When you have fever you are heavy and light, you are small and swollen, you
climb endlessly a ladder which turns like a wheel.
--Jean Rhys, Voyage in the Dark
On Wed, Oct 31, 2018 at 05:27:58PM +0300, Reco wrote:
> A (mis)feature. Any executable text file without defined shebang is a
> shell script.
Not quite. An attempt to execute a file that doesn't have a valid magic
number in the first few bytes triggers an ENOEXEC from the execve(2) call.
If this
On Wednesday 31 October 2018 10:31:40 Reco wrote:
> Hi.
>
> On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> > On 10/31/2018 09:18 AM, Curt wrote:
> > > On 2018-10-31, Richard Owlett wrote:
> > > > Debian 9.1 with MATE installed from DVD set.
> > > >
> > > > Due a
On Wednesday 31 October 2018 10:31:40 Reco wrote:
> Hi.
>
> On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> > On 10/31/2018 09:18 AM, Curt wrote:
> > > On 2018-10-31, Richard Owlett wrote:
> > > > Debian 9.1 with MATE installed from DVD set.
> > > >
> > > > Due a
Hi.
On Wed, Oct 31, 2018 at 09:29:52AM -0500, Richard Owlett wrote:
> On 10/31/2018 09:18 AM, Curt wrote:
> > On 2018-10-31, Richard Owlett wrote:
> > > Debian 9.1 with MATE installed from DVD set.
> > >
> > > Due a non-reproducible sequence of events, a binary executable was over
> > >
launcher pointed the corrupted file.
When the launcher icon was clicked there was no response whatsoever.
Including *NO ERROR MESSAGE*
Is this a bug or a feature?
If a feature, why?
wn
> reason, the
> resulting file was tagged as executable.
Replace your HDD today, don't give it another chance to corrupt your
data.
> A custom MATE launcher pointed the corrupted file.
> When the launcher icon was clicked there was no response whatsoever.
> Including *NO ERROR MESSAGE*
&
utable.
I want to predict immediately that this can of worms will produce the
longest thread in the history of debian user.
> A custom MATE launcher pointed the corrupted file.
> When the launcher icon was clicked there was no response whatsoever.
> Including *NO ERROR MESSAGE*
>
.
When the launcher icon was clicked there was no response whatsoever.
Including *NO ERROR MESSAGE*
Is this a bug or a feature?
If a feature, why?
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é
Hola,
Si intento entrar amb el login gràfic lightdm, surt immediatament i em
torna a la pantalla de login. Al fitxer .xsession-errors hi ha les
següents línies
dbus-update-activation-environment: setting
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
ruption. next->prev should be prev
> (0533875c), but was c2b0df70. (next=c2b0df70).
> [ 6787.703475] [ cut here ]
> [ 6787.703477] kernel BUG at
> /build/linux-43CEzF/linux-4.16.12/lib/list_debug.c:25!
> [ 6787.703578] invalid opcode:
I have a syslog capture of a BUG that I seem to routinely hit under
specific circumstances.
I have other details that might be of interest to whomever is interested
in this BUG. For example, this is a fully updated Debian "buster" system
with a ext4 (OS) and ZFS (storage array) f
Hi.
On Fri, Oct 05, 2018 at 12:41:44PM +0200, Pétùr wrote:
> Hi,
>
> I cannot connect to WPA2 Entreprise network (PEAP + MSCHAPv2) with
> openssl 1.1.1-1 (in sid today). I can connect 1.1.0f-3+deb9u2 version
> (stable).
>
> Is it a bug in openssl 1.1.1-1 or some ki
Hi,
I cannot connect to WPA2 Entreprise network (PEAP + MSCHAPv2) with
openssl 1.1.1-1 (in sid today). I can connect 1.1.0f-3+deb9u2 version
(stable).
Is it a bug in openssl 1.1.1-1 or some kind of incompatibility between
openssl 1.1.1-1 and my radius server?
The error log with the 1.1.1-1
iled.
> >
> > Would you please help me take a look?
> >
> > --Error Details--
> >
> > Reported error:
> >
> >
> >
> > /550 5.0.350 Remote server returned an error -> 550 Unknown or archived bug/
> >
On Fri 14 Sep 2018 at 21:29:41 +0200, Thomas Schmitt wrote:
[snip]
> So if you do not feel entitled (or are not allowed) to send the
> "unarchive" command, then consider to contact Ben Hutchings and to ask
> about the forth-and-back in that bug.
Nobody is disallowed from
Remote server returned an error -> 550 Unknown or archived bug/
DSN generated by:
BYAPR05MB4613.namprd05.prod.outlook.com
Remote server:
buxtehude.debian.org
If the email receiver is not correct, please help me forward it to the
right receiver.
Thanks!
--
Best Regards
Hi,
Yanhui He wrote:
> I need to update a 3rd PR to Debian by sending mail
> to 896...@bugs.debian.org, but it always failed.
> 550 5.0.350 Remote server returned an error -> 550 Unknown or archived bug
The bug tracker page
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=89691
Hi,
I need to update a 3rd PR to Debian by sending mail to
896...@bugs.debian.org<mailto:896...@bugs.debian.org>, but it always failed.
Would you please help me take a look?
--Error Details--
Reported error:
550 5.0.350 Remote server returned an error -> 550 Unknown or arc
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
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.
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,
Reco wrote:
> Wait. You're *the* Thomas Schmitt who wrote xorriso?
Yep. I am the current developer of libburn, libisofs, libisoburn, cdrskin,
xorriso.
There were others involved, though.
libburn was forked from a half-dead project in 2006. Not more than 25
percent of the code is still from
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
1001 - 1100 of 8562 matches
Mail list logo
