On Mon, May 25, 2020 at 10:04:45PM +0200, Marco Möller wrote:
Even worth, apt is one out of a very few priority reasons to use Debian, or?
When I first used Debian, 20 years ago, apt(-get) was indeed one of the
primary reasons to use Debian. But back then it did not have Recommends:
nor auto-re
On Lu, 25 mai 20, 22:04:45, Marco Möller wrote:
> If installing (default parameters in use: with recommends) a package, and
> right afterwards removing it, then the by recommendation drawn in packages
> do not become removed automatically.
This behaviour is intended and controlled by the
AutoRem
x27; option applies
> > only to the current install command. The result of a subsequent remove
> > command will depend on the state of the dependency graph as a whole at
> > the time.
> >
>
> So, no "undo" is in apt available, its database does not store suf
Marco M??ller wrote:
> So, no "undo" is in apt available, its database does not store sufficient
> information for it. :-( This is what I see as a severe bug.
There is no undo for apt. There is uninstall, and purge.
Suppose you install Feeblix, which recommends libfoo, and
te of the dependency graph as a whole at
the time.
So, no "undo" is in apt available, its database does not store
sufficient information for it. :-( This is what I see as a severe bug.
Not your fault, thanks for your input! I have had hope for a moment that
there would exist some &quo
mply missing the simple step how to return to the former
> > > > system state after having tested a package. Otherwise this is a bug.
> > > > To me it appears to be a severe bug, as apt is not managing the
> > > > packages in my system as expected.
> >
> >
kages do not become removed automatically. The system is swelling
with no more wanted packages!
I hope I am simply missing the simple step how to return to the former
system state after having tested a package. Otherwise this is a bug.
To me it appears to be a severe bug, as apt is not managin
do not become removed automatically. The system is swelling
> > with no more wanted packages!
> > I hope I am simply missing the simple step how to return to the former
> > system state after having tested a package. Otherwise this is a bug.
> > To me it appears to be a severe bug,
ackages!
> I hope I am simply missing the simple step how to return to the former
> system state after having tested a package. Otherwise this is a bug.
> To me it appears to be a severe bug, as apt is not managing the
> packages in my system as expected.
>
>
> Commandline
On 2020-05-25 at 16:04, Marco Möller wrote:
> If installing (default parameters in use: with recommends) a package,
> and right afterwards removing it, then the by recommendation drawn
> in packages do not become removed automatically. The system is
> swelling with no more wanted packages!
If I'
to the former
system state after having tested a package. Otherwise this is a bug. To
me it appears to be a severe bug, as apt is not managing the packages in
my system as expected.
Commandline: apt install deborphan
Install: deborphan:amd64 (1.7.33), dialog:amd64 (1.3-20190808-1, automatic
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:
https
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
fwupd is worth noting: https://en.wikipedia.org/wiki/Fwupd
and not only does it manage PC firmwares (UEFI) but peripheral cards
firmwares too
but it is far from widely adopted :-(
instead of "Buster", which has
> been the stable distribustion since July 6th 2019.
If it's just the name of the stable distribution it doesn't matter, the
general principle is still the same.
Anyway, if you find anything outdated/wrong/missing you could report a
bug against t
Hi there,
On Sat, 28 Mar 2020, rba777 wrote:
...
[ 0.457794] ACPI BIOS Error (bug): Failure creating named object
[\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
[ 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20190816/psobject-220)
...
Using apt and apt
Jude DaShiell wrote:
>
> Does any Linux app exist to let systems know when bios updates become
> available for the bios running on those systems?
No. It would require a mechanism supported by each manufacturer,
and they tend not to even be consistent on their own websites.
Server manufacturers
On Sat, 28 Mar 2020, Darac Marjal wrote:
> Date: Sat, 28 Mar 2020 06:55:55
> From: Darac Marjal
> To: debian-user@lists.debian.org
> Subject: Re: Question regarding an ACPI BIOS Error (bug)
>
>
> On 28/03/2020 09:35, rba...@protonmail.ch wrote:
> > Hi all, I've be
10073] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
These aren't errors; these ones are just informative.
> [ 0.457794] ACPI BIOS Error (bug): Failure creating named object
> [\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
> [ 0.457802] ACPI Error: AE_ALREADY_EXIST
BIOS Error (bug): Failure creating named object
[\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
[ 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20190816/psobject-220)
[ 0.457805] ACPI: Skipping parse of AML opcode: OpcodeName unavailable
(0x0014)
[ 0.4
Hi,
I'm having a problem after an update some weeks ago, every few minutes the
pc is freezing for a while and after it recover, it seem to be the same as
writte on this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
I'm getting also the same errors:
[50928.830285] GpuWatc
Thanks for passing that along, Didar. It shows my cert is OK as well.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BB
Hi,
This post is informational:
Lets Encrypt discovered a bug in their CA software (boulder) related to CAA
checking code. They have decided to revoke a subset of certificates issued on
March 4, 2020.
More information:
https://arstechnica.com/information-technology/2020/03/lets-encrypt-revoking
On Mon, Mar 02, 2020 at 01:14:59PM +1030, heman wrote:
> hi Tomas, thanks for the response, pretty sure the docker image was the
> official debian:buster from dockerhub. I'll double check.
>
> I hadn't thought of looking for an issue reporting link on dockerhub, as I
> figured it would be part o
On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:
I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from mul
On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:
> Hi,
>
> I've read https://www.debian.org/Bugs/Reporting
> but it is still completely unclear to me how I can report what I
> consider to be a bug or flaw with the debian docker image [...]
That depends on where you go
Hi,
I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from multiple packages.
(from reading the page at the above U
Please take a look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949471 . I have
reported it as a bug in open-infrastructure-system-build , but I don't
think the problem is in this component; I think the problem is in one of
the components that it installs ( maybe ca-certifi
topology in‐ formation. This aligns to a
> multiple of the physical block size in a way that
> guarantees optimal performance
>
>
> 1. Probably parted detected physical sector size as 512
> instead of 4096? Why?
>
> 2. Even if p
that physical sector is 512 instead of
> 4096, why start from 65535 and not from 65536? What is the logic
> behind? How using odd multiplier can improve performance?
>
> Is it a bug in parted or I am missing something?
Bug #923561 has a long discussion about alignment and optimal transfe
Le 04/12/2019 à 13:15, Sergey Spiridonov a écrit :
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 82DD924B-BF0E-40FF-9037-1FD4E7307D26
Device Start End Sectors Size Type
/dev/sd
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 contain
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 | hea
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)
>> #
ller: NVIDIA Corporation G84 [GeForce 8600 GT]
>> (rev a1)
>> --8<---cut here---end--->8---
>> in it.
>
>> I have feeling that graphic drivers have bug, but I am not sure:
>> My simple test:
>> ebook-viewer anthing.e
<---cut here---end--->8---
> in it.
> I have feeling that graphic drivers have bug, but I am not sure:
> My simple test:
> ebook-viewer anthing.epub
What provides ebook viewer? aptitude search ebook shows me nothing by that name.
...
> Th
There is debian box with:
--8<---cut here---start->8---
08:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT]
(rev a1)
--8<---cut here---end--->8---
in it.
I have feeling that graphic driv
Am Montag, 25. November 2019, 20:07:56 CET schrieb Goran Delcev:
Hi Goran,
this bug is known since almost 2 years. I reported it in the list, sent a
bugreport tzo
powerdevil (and askeds the list, which package might be responsible for it),
but got
no solution. People told me, the kernel
Hi Julian,
Quoting sj...@uranus.uni-freiburg.de (2019-11-21 11:39:14)
> if it (from around June 28th) still matters for somebody: I
> re-installed my whole system and I couldn't re-recognise the behaviour
> described. I also can't remember having changed anything in the
> "deeper settings of th
Hi,
if it (from around June 28th) still matters for somebody: I re-installed my
whole system and I couldn't re-recognise the behaviour described. I also can't
remember having changed anything in the "deeper settings of the system"…
However, best regards,
Julian Schreck
--
> Hi,
>
> Julian Schr
Eero Volotinen wrote:
> Any clue why systemctl start snort is not running start section of init
> script? (if start is already run once?)
Don't use the snort package from the Debian repository, it is ancient
(last upload was in 2015) and might as well be orphaned or better yet
removed from Debia
mmand systemctl restart snort
> Sounds like a bug?
>Eero
That could be a bug. On the other hand, "killed" implies that it may
not have had the opportunity to perform a clean shutdown, perhaps
leaving behind a PID file or some other cruft that must be cleaned up
prior to the nex
Hi,
Any clue why systemctl start snort is not running start section of init
script? (if start is already run once?)
For example, if snort daemon is killed then only way to start it is run
command systemctl restart snort
Sounds like a bug?
Eero
Peter Ehlert writes:
> SOLVED
Thank You Very Much, Peter^^^
(because that is very important part in installing i think)
Sincerely,
--
^고맙습니다 _地平天成_ 감사합니다_^))//
SOLVED
add this to /etc/NetworkManager/NetworkManager.conf
per bug #835553
[device]
wifi.scan-rand-mac-address=no
That worked for me with a Ralink Technology, Corp. RT5370 Wireless
Adapter on Debian Stretch. Thank you very much.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842422#40
On Sat, 9 Nov 2019, Peter Ehlert wrote:
> Date: Sat, 9 Nov 2019 13:28:02
> From: Peter Ehlert
> To: debian-user@lists.debian.org
> Subject: Re: Debian Installer Bug -Wifi driver not installed
> Resent-Date: Sat, 9 Nov 2019 18:45:09 + (UTC)
> Resent-From: debian-use
On 11/9/19 9:25 AM, Patrick Bartek wrote:
On Sat, 9 Nov 2019 06:16:17 -0800
Peter Ehlert wrote:
I have a desktop computer running Debian Buster Mate that I want to move
to a different location and use Wifi.
Using a cheap USB dongle NetworkManager Applet detects the device, lets
me select fro
On Sat, 9 Nov 2019 06:16:17 -0800
Peter Ehlert wrote:
> I have a desktop computer running Debian Buster Mate that I want to move
> to a different location and use Wifi.
> Using a cheap USB dongle NetworkManager Applet detects the device, lets
> me select from available networks, accepts passwor
I have a desktop computer running Debian Buster Mate that I want to move
to a different location and use Wifi.
Using a cheap USB dongle NetworkManager Applet detects the device, lets
me select from available networks, accepts password, but will not
connect..and after a few moments it closes..
I have a desktop computer running Debian Buster Mate that I want to move
to a different location and use Wifi.
Using a cheap USB dongle NetworkManager Applet detects the device, lets
me select from available networks, accepts password, but will not
connect..and after a few moments it closes..
Le 28/10/2019 à 09:14, Andy Smith a écrit :
I will take a guess that the switching of the iptables commands to
use the nftables framework has somehow caused this iptable_filter
module to not be loaded even though the firewall still works.
Correct.
Is it a bug that loading rules into the
On Sb, 14 sep 19, 04:20:42, Yoann LE BARS wrote:
>
> Well, I think this patch should probably be added to the package. Can
> anyone tell me what I should do to propose this patch? Should I open a
> bug issue on Debian bug tracker, then send the patch? Should I do
> someth
On Sb, 14 sep 19, 04:00:08, Yoann LE BARS wrote:
>
> But as it is the first time I propose some workaround to a bug, I want
> to make sure I have done what is needed. So, can anyone confirm my
> message is sufficient of if I should do something more?
Depends on what you mean by
gement software works again. I
have for the moment made this change permanent by adding those
modules to a file in /etc/modules-load.d/.
I will take a guess that the switching of the iptables commands to
use the nftables framework has somehow caused this iptable_filter
module to not be loaded even thou
Hi,
it seems systemd-networkd of the Buster distribution does not work
reliable on some of my systems.
Can you help me to further analyze the problem in front of bug creation?
Short summary:
If an interface uses static addresses and the cable is unplugged and
plugged in again, the interface does
Hi, I installed Debian 10 on my old laptop (BIOS mode) using the
unsupported firmware iso.
I noticed that using the Graphical installer it fails connecting to the
wifi.
Using the classic ncurses installer, it connects successfully.
I checked also with the latest firmware-10.1.0-amd64-netinst.iso an
sure you have yet another desktop installed and
available to select? you don't mention if you've actually
installed another desktop that should show up in the menu
or not.
so it may not actually be a bug because there is nothing
else to select.
2. There is no sound. The alsamixe
#x27;ve actually
installed another desktop that should show up in the menu
or not.
so it may not actually be a bug because there is nothing
else to select.
> 2. There is no sound. The alsamixer and the Gnome sound tool show only
> an HDMI option but my monitor has no speakers. If I reboot
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
Gnome is the current selections. Ther
bug I have not seen in Debian bug tracker system:
when I tried to launch FFADO-mixer, it failed to load (see log at the
end of this message).
I have asked for help on FFADO mailing list:
https://sourceforge.net/p/ffado/mailman/ffado-user/?viewmonth=201909&viewday=11
Jona
Hello everybody out there!
I am using Debian 10 :
$ cat /etc/debian_version
10.1
I am using Ardour 5 from standard distribution repositories:
$ aptitude versions ardour
i 1:5.12.0-3stable
900
I have experimented bug #874598
Package: apt
Severity: wishlist
On Ma, 06 aug 19, 16:22:34, Keith Bainbridge wrote:
>
> I found a simple guide at
>
>
> https://www.linuxbabe.com/debian/install-latest-virtualbox-6-0-10-debian-10-buster
>
>
> In summary:
> Create new sources file:
> sudo nano /etc/apt/sources.list.d/oracle-vi
Reco wrote:
> lsinitramfs /boot/initrd.img* | grep ttf$
Hmm here it does not find anything, but plymouth is in the initram
When looking for ttf
grep
ttf -r /etc/initramfs-tools /usr/share/initramfs-tools/
/usr/share/lintian/overrides
/usr/share/initramfs-tools/hooks/plymouth: if
[
On Sun, Jul 28, 2019 at 01:54:01PM +0200, deloptes wrote:
> Reco wrote:
>
> > plymouth, maybe? You know, that fancy bootloader program?
>
> yes I know and use it - much better than 80s dos style boot up screen,
> but ... perhaps needs a check out of curiosity.
>
> Do you know how/where to check
Reco wrote:
> plymouth, maybe? You know, that fancy bootloader program?
>
yes I know and use it - much better than 80s dos style boot up screen,
but ... perhaps needs a check out of curiosity.
Do you know how/where to check this?
thanks in advance
regards
Hi.
On Sun, Jul 28, 2019 at 12:07:33PM +0200, deloptes wrote:
> J.W. Foster wrote:
>
> > OK I got it sorted out. Seems it was a font issue. i had to install ttf
> > dejavu and it all installed ok
>
> Jut curious what a dejavu ttf font might have to do with building initramfs
plymouth,
J.W. Foster wrote:
> OK I got it sorted out. Seems it was a font issue. i had to install ttf
> dejavu and it all installed ok
Jut curious what a dejavu ttf font might have to do with building initramfs
regards
Hi,
On Thu, Jul 25, 2019 at 02:55:13AM +, J.W. Foster wrote:
E: initramfs-tools: installed initramfs-tools package post-installation script
subprocess returned error exit status 1
There can be many reasons why this package's post-installation
script may have failed. I don't think you have sh
Hi.
On Tue, Jul 09, 2019 at 11:17:08AM +0100, Frediano Ziglio wrote:
> But what about a bug in a package packaged in Debian and which you
> manage the sources knowing Debian packaged one has surely a bug and
> you want to report?
reportbug --src
> What if this is a securit
Hi,
I would like to report a bug for a package which is in Debian. The page
at https://www.debian.org/Bugs/Reporting says mainly install reportbug and
use it or other weird mail way involving some manual field to add. But what
about a bug in a package packaged in Debian and which you manage the
Hi,
I tried to shut down the pc with ctrl + alt + 1 -> [login] -> sudo poweroff ->
no reaction.
I had some music file playing. A snippet (< 1 s) was repeated roughly between 5
and 10 times before I didn't hear anything further on.
Ctrl + SysRq + k normally reboot immediately. In my case, no react
Hi,
Julian Schreck wrote:
> I could narrow it down to lxterminal (autostarted),
You could start another terminal program from the lxterminal and then
end the lxterminal. (I use "xterm", the old and sparse one.)
You could also check whether the lxterm menus give you an opportunity
to disable any f
Hi,
I could narrow it down to lxterminal (autostarted), openbox or an automatically
started process. Any other advice than changing the window manager (in case
that was suggested/your intention)?
- A rough description of the kind of computer: ”# lshw“ gives
debian
descr
ink so. (I should've
tested this before writing to you…)
The thing is that I don't know which package could cause this bug, therefore
I'm writing to this list. As far as I can see, this behaviour may only be
caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution, openbox.
O
Hi,
sj...@uranus.uni-freiburg.de wrote:
> As far as I can see, this behaviour may only be
> caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution,
> openbox.
Consider to use alternatives for a few days until it is clear whether
avoiding one or more of the suspects makes the freeze
e thing is that I don't know which package could cause this bug, therefore
I'm writing to this list. As far as I can see, this behaviour may only be
caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution, openbox.
Or a package acting behind my knowledge may also be causing
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 con
I'm using Debian Stretch 9.9(stable) in HP Notebook. From around 4-5
weeks oftentimes, I'm getting "[Firmware Bug]: battery: (dis)charge rate
invalid." warning message in kernel ring buffer probably this was
started after upgradation of Linux-header package[*]. Till yesterday,
Andrei POPESCU wrote:
> Debian is typically using LTS kernels for stable releases, so buster
> will most likely release with 4.19.
This is a good choice - running custom 4.19 I can say that I will not intend
to upgrade it in near feature.
On Sb, 08 iun 19, 16:08:27, Andrea Borgia wrote:
> Il 08/06/19 12:18, Andrei POPESCU ha scritto:
>
> > On Mi, 27 mar 19, 21:22:18, Andrea Borgia wrote:
> > > 2) maybe I am not using the proper keywords but I can't seem to find
> > > information on Debian kernel policy, specifically: when does a ne
Il 08/06/19 12:18, Andrei POPESCU ha scritto:
On Mi, 27 mar 19, 21:22:18, Andrea Borgia wrote:
2) maybe I am not using the proper keywords but I can't seem to find
information on Debian kernel policy, specifically: when does a new kernel
from upstream enter "unstable"?
Usually quite soon afte
,
> should I do anything else, like closing it or adding some special tags? As
> far as current "testing" branch is concerned, this bug is still present,
> unless you install a kernel from "experimental"[4] or upstream.
If there is a fixed version in Debian you can mar
On Wednesday 22 May 2019 03:47:00 am Curt wrote:
> On 2019-05-21, Gene Heskett wrote:
> >> That I don't know. I don't have it here on my Stretch. It would be
> >> interesting to discover what dragged brltty into yours.
> >
> > Good question. The install image is supposed to be the latest
> > stra
On 2019-05-21, Gene Heskett wrote:
>>
>> That I don't know. I don't have it here on my Stretch. It would be
>> interesting to discover what dragged brltty into yours.
>>
> Good question. The install image is supposed to be the latest straight
> amd64 debian stretch, with a rt-preempt kernel and t
On Tuesday 21 May 2019 07:44:51 pm David Wright wrote:
> On Tue 21 May 2019 at 17:21:33 (-0400), Gene Heskett wrote:
> > On Tuesday 21 May 2019 02:31:26 pm Curt wrote:
> > > On 2019-05-21, Gene Heskett wrote:
> > > >> We are positively discriminating in favor of the blind.
> > > >
> > > > Then pe
On Tue 21 May 2019 at 17:21:33 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 02:31:26 pm Curt wrote:
> > On 2019-05-21, Gene Heskett wrote:
> > >> We are positively discriminating in favor of the blind.
> > >>
> > > Then perhaps the better question is why was it running on a new
> > > stre
On Tuesday 21 May 2019 02:37:57 pm bw wrote:
> In-Reply-To: <201905211405.01261.ghesk...@shentel.net>
>
> >> We are positively discriminating in favor of the blind.
> >
> >Then perhaps the better question is why was it running on a new
> > stretch install? I think it probably could be fixed to k
On Tuesday 21 May 2019 02:31:26 pm Curt wrote:
> On 2019-05-21, Gene Heskett wrote:
> >> We are positively discriminating in favor of the blind.
> >>
> >> > Cheers, Gene Heskett
> >
> > Then perhaps the better question is why was it running on a new
> > stretch install? I think it probably coul
On 2019-05-21, Gene Heskett wrote:
>>
>> We are positively discriminating in favor of the blind.
>>
>> > Cheers, Gene Heskett
>
> Then perhaps the better question is why was it running on a new stretch
> install? I think it probably could be fixed to keep both camps happy.
That I don't know. I
On Tue 21 May 2019 at 14:05:01 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 11:41:00 am Curt wrote:
> > On 2019-05-21, Gene Heskett wrote:
> > > This to me is a bug that needs fixed. No sense in denying someone
> > > using
> >
> > There are
On Tuesday 21 May 2019 11:41:00 am Curt wrote:
> On 2019-05-21, Gene Heskett wrote:
> > This to me is a bug that needs fixed. No sense in denying someone
> > using
>
> There are already oldenbugs flurrying around the question, Gene.
>
> Here's one from 2012:
>
On 2019-05-21, Gene Heskett wrote:
>
> This to me is a bug that needs fixed. No sense in denying someone using
There are already oldenbugs flurrying around the question, Gene.
Here's one from 2012:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616
tags 667616 + wontf
(daemon) providing access to the
> Linux/Unix console (when in text mode) for a blind person using a
> refreshable braille display."
daytime again, and time to file a bug report, something I've not tried to
negotiate since my last mind numbing encounter with the dumbest software
ou
On Fri 17 May 2019 at 20:20:03 +, Riccardo Paolo Bestetti wrote:
> > You could also consider just applying the patches which work for you
> > and getting on with life. Bugs have been reported and not responded
> > to. You have done your part; now it is up to someone else who is in
> > a positi
-Original Message-
From: Brian
Sent: venerdì 17 maggio 2019 19:21
To: debian-user@lists.debian.org
Subject: Re: FW: knockd package long-standing bug
> You could also consider just applying the patches which work for you and
> getting on with life. Bugs have been reported a
On Wed 15 May 2019 at 08:02:01 +, Riccardo Paolo Bestetti wrote:
> -Original Message-
> From: to...@tuxteam.de
> Sent: mercoledì 15 maggio 2019 07:47
> To: debian-user@lists.debian.org
> Subject: Re: FW: knockd package long-standing bug
>
> Hi Tomás,
>
&
-Original Message-
From: to...@tuxteam.de
Sent: mercoledì 15 maggio 2019 07:47
To: debian-user@lists.debian.org
Subject: Re: FW: knockd package long-standing bug
Hi Tomás,
> I don't understand to whom you sent a mail: to the maintainer's (Leonardo's)
> Debian
On Tue, May 14, 2019 at 10:56:18PM +, Riccardo Paolo Bestetti wrote:
> >>Hello,
> >>
> >>Bug #868015 has been open since Jul 2017 [...]
> >Hi Riccardo, I'll take a chance at answering your question [...]
[good points]
> Your input is much appreciate
>>Hello,
>>
>>Bug #868015 has been open since Jul 2017 and the fix consists in 3
>>lines added to the system unit file. I.e. knockd.service lacks the
>>[Install] section and thus the service can't be made to auto-start after a
>>reboot.
>>Since t
801 - 900 of 5927 matches
Mail list logo
