Re: Debian GNU/Linux 9 (stretch) 64-bit

[Jason Wittlin-Cohen]

Every BIOS has its own key combination to enter the BIOS and/or choose a
boot device for a single boot.  For my system, it is DEL and F11,
respectively.  In most cases, the first screen you see after you turn on
the computer should tell you what button to press.  If it says nothing, try
repeatedly hitting DEL, F11, and F12.  One of those should work. :)

On Fri, Aug 4, 2017 at 8:50 AM, Stephen Brandt  wrote:

> I have a problem I'm trying to report but the report bug has directed me
> to you.  I don't know what package I'm reporting on.  Everything I've
> tried entering has been rejected.  I used the internet version to
> install Debian on my computer. I wanted to install Debian as a 2nd OS on
> my computer along with Ubuntu.  Unfortunately for me, I was half asleep
> while doing the install and guessing at the choices being offered. The
> problem I encountered was some of the instructions/choices were off the
> left hand side of the monitor and not visible.  I had to guess at what I
> was doing.  One of the consequences is the install overwrote my Ubuntu
> OS and I lost everything.  The other consequence is now I'm unable to
> boot from my dvd drive.  It seems that no matter what I try regarding
> changes to the BIOS before booting to try and boot from the dvd drive,
> the Debian OS overwrites my changes and forces booting from the Hard
> Drive.  I need help.
>
> Thanks,
>
> Stephen
>
>
>

Re: Thunderbird 52.2.1 and Enigmail

[Jason Wittlin-Cohen]

Sorry for the oversight.  I am actually running on Stretch, so I'm using
Enigmail 1.9.7.  Perhaps someone can backport the version from Stretch to
Jessie to resolve this issue.

On Tue, Jul 25, 2017 at 7:26 PM, Daniel Bareiro <daniel-lis...@gmx.net>
wrote:

> Hi, Jason.
>
> Thanks for your reply. But please respond to the list so that we can all
> take advantage of the contribution.
>
> On 25/07/17 18:54, Jason Wittlin-Cohen wrote:
>
> > I'm not seeing the behavior you described with Thunderbird + Enigmail.
>
> Thats weird. Are you using Debian Jessie packages for both?
>
>
> Thanks again for your reply.
>
> Kind regards,
> Daniel
>
>

Re: Can debian-live-9.0.1-i386-lxde be made to install from USB?

[Jason Wittlin-Cohen]

That's not exactly what I'm seeing.  I began seeding the Debian 9.0
installer image on 6/17 and the Live image on 6/20, when the 9.0.1 released.

debian-9.0.0-amd64-DVD-1.iso  171.36 GB
debian-live-9.0.1-amd64-gnome.iso 157.90 GB
debian-live-9.0.1-amd64-cinnamon.iso  107.85 GB
debian-9.0.0-amd64-netinst.iso  3.50 GB

The net install doesn't really count since the Debian site has a direct
link to download it, and people are unlikely to bother with such a small
download over Bittorrent.

Note:  Dejan, sorry for the direct email. Meant to email the list.

On Tue, Jul 18, 2017 at 12:04 PM, Jason Wittlin-Cohen <
jwittlinco...@gmail.com> wrote:

> That's not exactly what I'm seeing.  I began seeding the Debian 9.0
> installer image on 6/17 and the Live image on 6/20, when the 9.0.1 released.
>
> debian-9.0.0-amd64-DVD-1.iso  171.36 GB
> debian-9.0.0-amd64-DVD-1.iso  157.90 GB
> debian-live-9.0.1-amd64-cinnamon.iso  107.85 GB
> debian-9.0.0-amd64-netinst.iso  3.50 GB
>
> The net install doesn't really count since the Debian site has a direct
> link to download it, and people are unlikely to bother with such a small
> download over Bittorrent.
>
> On Tue, Jul 18, 2017 at 11:39 AM, Dejan Jocic <jode...@gmail.com> wrote:
>
>> On 18-07-17, Jason Wittlin-Cohen wrote:
>> > Many people have had issues installing with the Live installer on this
>> > mailing list.  The question is why Debian even offers the option if
>> there
>> > is no interest in testing it to make it work.  The initial live
>> installer
>> > images (9.0, before 9.0.1) were completely broken and could not even
>> begin
>> > the install[1].  Clearly, this resulted from a complete lack of testing
>> as
>> > it would have been easily caught given that it is a deterministic error
>> > that to applied to ALL the live ISOs.  I think it's unfair to blame
>> users
>> > for using the Live media as an installer.  Either test the live images
>> to
>> > make sure it can be used for installation on a wide variety of
>> hardware, or
>> > don't provide the option at all.  It appears that the debian-devel
>> mailing
>> > list HAS called for more testing due to this situation with the explicit
>> > threat that live images will cease to be produced if nobody wants to
>> test
>> > them [2].  With that said, users should always use the regular d-i
>> > installer images to do an actual install.  The live images are useful
>> for
>> > testing to see if your hardware is supported and also for recovery.
>> >
>> > Takeaway:  If you want to install Debian, either use the network
>> installer
>> > (small installation image) or use one of the DVD images (large
>> installation
>> > images), NOT the live disks.  You can download either here:
>> > https://www.debian.org/distrib/.  Only use the Live ISOs to test out
>> Debian
>> > and to ensure hardware support.  If you have a need for non-free
>> firmware
>> > to complete the install (e.g. non-free network firmware for wifi
>> devices),
>> > use the images here
>> > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-
>> including-firmware/9.0.0+nonfree/amd64/bt-dvd/
>> > .
>> >
>> > [1]https://cdimage.debian.org/debian-cd/9.0.1-live/amd64/iso-hybrid/
>> > [2] https://lists.debian.org/debian-devel/2017/06/msg00335.html
>> >
>>
>> Trouble is that live images are, judging by my torrents, most popular
>> media of choice. Just debian-live-9.0.1-amd64-gnome.iso was uploaded for
>> 23 GB, while debian-9.0.0-amd64-DVD-1.iso is on 14.68 GB and
>> debian-9.0.0-amd64-netinst.iso is on 463 MB. So, something in big red
>> letters should be there on Debian site as a warning for people not to
>> download live for install. At least till we get 9.0.2 live iso.
>>
>>
>>
>>
>>
>

Re: Can debian-live-9.0.1-i386-lxde be made to install from USB?

[Jason Wittlin-Cohen]

Many people have had issues installing with the Live installer on this
mailing list.  The question is why Debian even offers the option if there
is no interest in testing it to make it work.  The initial live installer
images (9.0, before 9.0.1) were completely broken and could not even begin
the install[1].  Clearly, this resulted from a complete lack of testing as
it would have been easily caught given that it is a deterministic error
that to applied to ALL the live ISOs.  I think it's unfair to blame users
for using the Live media as an installer.  Either test the live images to
make sure it can be used for installation on a wide variety of hardware, or
don't provide the option at all.  It appears that the debian-devel mailing
list HAS called for more testing due to this situation with the explicit
threat that live images will cease to be produced if nobody wants to test
them [2].  With that said, users should always use the regular d-i
installer images to do an actual install.  The live images are useful for
testing to see if your hardware is supported and also for recovery.

Takeaway:  If you want to install Debian, either use the network installer
(small installation image) or use one of the DVD images (large installation
images), NOT the live disks.  You can download either here:
https://www.debian.org/distrib/.  Only use the Live ISOs to test out Debian
and to ensure hardware support.  If you have a need for non-free firmware
to complete the install (e.g. non-free network firmware for wifi devices),
use the images here
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.0.0+nonfree/amd64/bt-dvd/
.

[1]https://cdimage.debian.org/debian-cd/9.0.1-live/amd64/iso-hybrid/
[2] https://lists.debian.org/debian-devel/2017/06/msg00335.html


On Tue, Jul 18, 2017 at 10:47 AM, Darac Marjal 
wrote:

> On Wed, Jul 19, 2017 at 12:14:52AM +1000, Erik Christiansen wrote:
>
>> On 18.07.17 08:20, Greg Wooledge wrote:
>>
>>> On Tue, Jul 18, 2017 at 10:55:26AM +0200, Dejan Jocic wrote:
>>> > This release of Debian came with buggy live images. It was fixed with
>>> > 9.0.1 live images, or at least it seemed so.
>>>
>>> No, the 9.0.1 Debian live images are still broken when used for
>>> installations.  They fail to set a root password or to set up the primary
>>> user account with sudo access, at least in some cases.  Users in Freenode
>>> #debian are constantly having to be told how to boot from rescue media
>>> to set the root password.
>>>
>>> WHY DO PEOPLE ATTEMPT TO INSTALL DEBIAN USING A LIVE CD IMAGE
>>>
>>
>> www.debian.org -> "CD/USB ISO images", then choose the only possibly
>> viable alternative to CD/DVD, since there's no CD/DVD on the new host.
>>
>
> Did you read the two yellow boxes at the top of that page?
>
> 1. If you simply want to install Debian and have an Internet connection
> on the target computer please consider the Network Install media which
> is a smaller download.
>
> 2. On i386 and amd64 architectures, all CD/DVD images can be used on a
> USB stick too.
>
> I can see your logic, but the webpage IS telling you that "Even if
> you're trying to install from USB, these are the images you REALLY
> want."
>
>
> --
> For more information, please reread.
>

Re: SAMBA problems on Debian 8.8

[Jason Wittlin-Cohen]

BTW, here is what I see when I run dpkg -l | grep samba:

jason@storage-server:~$ dpkg -l | grep samba
ii  python-samba  2:4.2.14+dfsg-0+deb8u7+b1
  amd64Python bindings for Samba
ii  samba 2:4.2.14+dfsg-0+deb8u7+b1
  amd64SMB/CIFS file, print, and login server for Unix
ii  samba-common  2:4.2.14+dfsg-0+deb8u7
   all  common files used by both the Samba server and client
ii  samba-common-bin  2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba common files used by both the server and the client
ii  samba-dbg 2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba debugging symbols
ii  samba-doc 2:4.2.14+dfsg-0+deb8u7
   all  Samba documentation
ii  samba-dsdb-modules2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba Directory Services Database
ii  samba-libs:amd64  2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba core libraries
ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba Virtual FileSystem plugins


On Sat, Jul 15, 2017 at 11:09 AM, Jason Wittlin-Cohen <
jwittlinco...@gmail.com> wrote:

> You are running an out-of-date version of samba (2:4.2.14+dfsg-0+deb8u6
>  vs. 4.2.14+dfsg-0+deb8u7+b1).  In addition, you seem to be missing
> samba-common-bin,  samba-dsdb-modules, and python-samba, all of which are
> dependencies of samba.
>
> Try 'sudo apt-get install --reinstall samba'
>
> If that doesn't include install the removed packages, run, 'sudo apt-get
> install samba-common-bin samba-dsdb-modules python-samba'
>
> On Sat, Jul 15, 2017 at 11:01 AM, Hans Kraus <h...@hanswkraus.com> wrote:
>
>> Am 15.07.2017 um 16:05 schrieb Jason Wittlin-Cohen:
>>
>>> What does 'dpkg -l | grep samba'  show?
>>>
>>> On Sat, Jul 15, 2017 at 10:01 AM, Hans Kraus <h...@hanswkraus.com
>>> <mailto:h...@hanswkraus.com>> wrote:
>>>
>>> Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen:
>>>
>>> Did you run an apt-get dist-upgrade yesterday?  Debian released
>>> updated Samba packages as part of a security update.  However,
>>> the updated packages had dependency issues and were quickly
>>> replaced by new packages.  If you attempted to run a
>>> dist-upgrade with the broken packages, it would have installed
>>> samba and samba-core.  Check to see whether your samba packages
>>> are still installed.
>>>
>>> On Sat, Jul 15, 2017 at 7:56 AM, Hans Kraus <h...@hanswkraus.com
>>> <mailto:h...@hanswkraus.com> <mailto:h...@hanswkraus.com
>>>
>>> <mailto:h...@hanswkraus.com>>> wrote:
>>>
>>>  Hi,
>>>
>>>  yesterday, 14. July, about 9:30 pm my SAMBA shares on
>>> Debian simply
>>>  stopped working. I did not do anything on the system.
>>>
>>>  When I now try to connect to them from Windows 8.1 I do not
>>> see them
>>>  in the "Connect Network Drive" window.
>>>
>>>  When I enter the address manually I get the error "The
>>> connection isn't
>>>  accepted from the remote device ...".
>>>
>>>  All texts are my translations from German, so the will be
>>> only
>>>  approximately correct.
>>>
>>>  Any advice for me and what debug info shall I supply?
>>>
>>>  Kind regards,
>>>  Hans
>>>
>>>
>>> No, definitely not. I do updates/upgrades rather infrequently and I
>>> issued (packed in a small script):
>>>
>>> /usr/sbin/update-smart-drivedb
>>> apt-get update
>>> apt-get -y upgrade
>>> apt-get -y autoremove
>>>
>>> only after the error occurred.
>>>
>>> Kind regards,
>>> Hans
>>>
>>
>> root@robbe:/var/log/samba# dpkg -l | grep samba
>> rc  samba 2:4.2.14+dfsg-0+deb8u6   amd64SMB/CIFS
>> file, print, and login server for Unix
>> ii  samba-common 2:4.2.14+dfsg-0+deb8u7   all  common
>> files used by both the Samba server and client
>> ii  samba-dsdb-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
>> Samba Directory Services Database
>> ii  samba-libs:amd64 2:4.2.14+dfsg-0+deb8u7+b1amd64
>> Samba core libraries
>> ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
>> Samba Virtual FileSystem plugins
>> ii  vlc-plugin-samba 2.2.6-1~deb8u1   amd64
>> Samba plugin for VLC
>> root@robbe:/var/log/samba#
>>
>> Kind regards,
>> Hans
>>
>>
>

Re: SAMBA problems on Debian 8.8

[Jason Wittlin-Cohen]

You are running an out-of-date version of samba (2:4.2.14+dfsg-0+deb8u6
 vs. 4.2.14+dfsg-0+deb8u7+b1).  In addition, you seem to be missing
samba-common-bin,  samba-dsdb-modules, and python-samba, all of which are
dependencies of samba.

Try 'sudo apt-get install --reinstall samba'

If that doesn't include install the removed packages, run, 'sudo apt-get
install samba-common-bin samba-dsdb-modules python-samba'

On Sat, Jul 15, 2017 at 11:01 AM, Hans Kraus <h...@hanswkraus.com> wrote:

> Am 15.07.2017 um 16:05 schrieb Jason Wittlin-Cohen:
>
>> What does 'dpkg -l | grep samba'  show?
>>
>> On Sat, Jul 15, 2017 at 10:01 AM, Hans Kraus <h...@hanswkraus.com
>> <mailto:h...@hanswkraus.com>> wrote:
>>
>> Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen:
>>
>> Did you run an apt-get dist-upgrade yesterday?  Debian released
>> updated Samba packages as part of a security update.  However,
>> the updated packages had dependency issues and were quickly
>> replaced by new packages.  If you attempted to run a
>> dist-upgrade with the broken packages, it would have installed
>> samba and samba-core.  Check to see whether your samba packages
>> are still installed.
>>
>> On Sat, Jul 15, 2017 at 7:56 AM, Hans Kraus <h...@hanswkraus.com
>> <mailto:h...@hanswkraus.com> <mailto:h...@hanswkraus.com
>>
>> <mailto:h...@hanswkraus.com>>> wrote:
>>
>>  Hi,
>>
>>  yesterday, 14. July, about 9:30 pm my SAMBA shares on
>> Debian simply
>>  stopped working. I did not do anything on the system.
>>
>>  When I now try to connect to them from Windows 8.1 I do not
>> see them
>>  in the "Connect Network Drive" window.
>>
>>  When I enter the address manually I get the error "The
>> connection isn't
>>  accepted from the remote device ...".
>>
>>  All texts are my translations from German, so the will be
>> only
>>  approximately correct.
>>
>>  Any advice for me and what debug info shall I supply?
>>
>>  Kind regards,
>>  Hans
>>
>>
>> No, definitely not. I do updates/upgrades rather infrequently and I
>> issued (packed in a small script):
>>
>> /usr/sbin/update-smart-drivedb
>> apt-get update
>> apt-get -y upgrade
>> apt-get -y autoremove
>>
>> only after the error occurred.
>>
>> Kind regards,
>> Hans
>>
>
> root@robbe:/var/log/samba# dpkg -l | grep samba
> rc  samba 2:4.2.14+dfsg-0+deb8u6   amd64SMB/CIFS file,
> print, and login server for Unix
> ii  samba-common 2:4.2.14+dfsg-0+deb8u7   all  common
> files used by both the Samba server and client
> ii  samba-dsdb-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
> Samba Directory Services Database
> ii  samba-libs:amd64 2:4.2.14+dfsg-0+deb8u7+b1amd64
> Samba core libraries
> ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
> Samba Virtual FileSystem plugins
> ii  vlc-plugin-samba 2.2.6-1~deb8u1   amd64
> Samba plugin for VLC
> root@robbe:/var/log/samba#
>
> Kind regards,
> Hans
>
>

Re: Samba security updates held back on Jessie server

[Jason Wittlin-Cohen]

Fixed packages have been uploaded for Jessie and Stretch.

On Jul 14, 2017 12:16 PM, "Jason Cohen"  wrote:

> You might want to forward this to 868...@bugs.debian.org.  I reported the
> issue I found and received a reply indicating that they are building new
> packages but I'm not sure if these issues were also caught.
>
> On 07/14/2017 12:13 PM, Guy Marcenac wrote:
>
> Le 14/07/2017 à 16:40, Jason Cohen a écrit :
>
> Yup, the issue appears to be that python-samba requires python-talloc
> 2.1.6 and only 2.1.2 is available in Jessie.  This was probably a typo.
> The prior python-samba package only required 2.0.6.  I've reported this to
> the bug tracker.
>
> hi,
> It looks like it is not the only dependency error
> samba-common-bin depends on libncurses5 (>=6), and the jessie version is
> 5.9+20140913-1+b1
> smbclient depends on libreadline7 (>=6) which I cannot find in jessie
>
> --
> guy
>
>
>

Re: PLEASE STOP YOUR MAILS

[Jason Wittlin-Cohen]

If you want to unsubscribe, go here: https://lists.debian.org/debian-user/

On Sat, Jul 8, 2017 at 2:55 AM, fisma2b  wrote:

>
>
> I do not want to be in your mailing list anymore. Please remove my email
> from your list debian-user@lists.debian.org Stop your mails please Thanks
> again
>

Fwd: firmware-realtek: Add support for the rtl8812au/rtl8814au 802.11ac devices (already packaged in Ubuntu, Kali Linux)

[Jason Wittlin-Cohen]

I made a wishlist bug to add support for the rtl8812au/rtl8814au hardware.
Given that it's already made its way into Ubuntu, perhaps there's a chance
this will get included in Debian at some point.

-- Forwarded message --
From: Jason Cohen 
Date: Thu, Jul 6, 2017 at 8:35 PM
Subject: firmware-realtek: Add support for the rtl8812au/rtl8814au 802.11ac
devices (already packaged in Ubuntu, Kali Linux)
To: Debian Bug Tracking System 


Package: firmware-realtek
Version: 20161130-3
Severity: wishlist

Dear Maintainer,

Please provide support for the rtl8812au (802.11ac 2x2) and rtl8814au
(802.11ac
3x3 MIMO) devices. Drivers for this hardware is provided by:
https://github.com/astsam/rtl8812au. These drivers are already packaged in
Ubuntu since 16.04 LTS (and derivatives) as well as Kali Linux 2017.1
[3],[4].
There are relatively few 802.11ac USB adapters on the market and many of the
available devices appear to use this chipset. You can provide some examples
of
hardware using this chipset here [5].  In my case, I am using an Edimax
Edimax
EW-7822UAC (Bus 003 Device 023: ID 7392:a822 Edimax Technology Co., Ltd).
The
COMFAST CF-917AC is an example of the faster rtl18814au hardware[6].


[1]
http://www.realtek.com.tw/products/productsView.aspx?
Langid=1=57=5=4=397
[2]
http://www.realtek.com.tw/products/productsView.aspx?
Langid=1=21=57=5=4=392
[3] https://packages.ubuntu.com/search?keywords=rtl8812au-dkms
[4] https://www.kali.org/news/kali-linux-20171-release/ and
https://bugs.kali.org/view.php?id=3260
[5] https://wiki.gentoo.org/wiki/AC1200_Wireless_Adapters
[6] https://www.amazon.com/dp/B01B75MHR0



-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.130

-- no debconf information

Re: glusterfs and qemu/kvm

[Jason Wittlin-Cohen]

The last post on the bug report indicates that this issue has been fixed.
The changelog for the fixed version states:

   * enable glusterfs support (glusterfs-common), in qemu-block-extra

Stretch and newer contain qemu-block-extra, and it depends on glusterfs-common.


On Jul 6, 2017 8:10 AM, "Dave Sherohman"  wrote:

I'm currently running a number of virtual hosts under qemu/kvm backed by
iscsi storage and would like to move the storage onto glusterfs.
Unfortunately, Debian's qemu does not come with gluster support.  When
searching for information on this, I came across this bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775431

It was tagged wontfix in Oct 2015 and closed Dec 2016.  The basic reason
for the wontfix is that gluster is packaged in a way which makes it
infeasible to provide gluster support in the core qemu package, or even
to create a qemu-glusterfs package, and this in turn is because upstream
does things in a way which would make it difficult to maintain a stable
glusterfs-dev package.

Has this situation changed at all since then?  Assuming it hasn't, is
there a recommended procedure for replacing the standard Debian qemu
with a version which adds gluster support?

--
Dave Sherohman

Re: Driver/firmware for Realtek RTL8814U WiFi USB Adapter?

[Jason Wittlin-Cohen]

I have the Edimax EW-7822UAC (2x2 802.11ac) which uses the rtl8812AU
chipset.  I can confirm that the firmware-realtek package does not contain
support for the rtl8812AU chipset, and presumably also does not
support the RTL8814U
chipset.  Neither are listed on https://wiki.debian.org/rtl819x.  In
contrast, Ubuntu and its derivatives, such as Mint, do package this
driver.  For example, see
https://packages.ubuntu.com/xenial/kernel/rtl8812au-dkms.

Fortunately, I was able to compile and install the rtl8812AU driver from
https://github.com/diederikdehaas/rtl8812AU without difficulty.  I have
been using this wireless card on a desktop system with Stretch.  It has
been reliable and I had no problem configuring it with networks running
WPA2-PSK and WPA2-Enterprise (EAP-TLS).  I'm getting speeds around 300
Mbit/sec @ 65-70 dbm when connected to a Ubiquiti AC-LR.  In contrast, Mint
installed the driver for me without issue but had constant issues with
EAP-TLS due to bugs in network-manager.

On Wed, Jul 5, 2017 at 2:41 PM, Larry Dighera  wrote:

> Which Debian Stretch package provides firmware for the Realtek
> RTL8814U chip?  In particular, the Comfast CF-917AC 1750Mbps USB3
> adapter: https://www.amazon.com/dp/B01B75MHR0 .
>
> Kali Linux supports the RTL8814 natively:
> https://www.kali.org/news/kali-linux-20171-release/ .  Further, there
> are some clues here: https://bugs.kali.org/view.php?id=3260
> https://github.com/diederikdehaas/rtl8812AU
> https://github.com/astsam/rtl8812au
> https://github.com/lwfinger/rtlwifi_new
>
> But, I'm looking for an "official" Debian firmware package.
>
> I wasn't able to find the rt8814 mentioned here:
> https://www.debian.org/distrib/packages nor here:
> http://linux-wless.passys.nl/query_chipset.php?chipset=Realtek
> nor here: https://wireless.wiki.kernel.org/en/users/drivers
>
>

Re: Problems with apt in a clean stretch install.

[Jason Wittlin-Cohen]

Hi Wayne,

I ran into the same issue with trusted.gpg.  I opened the file in nano and
it was completely empty.  My guess is that apt is looking to this file for
the public keys of the various servers, and it complains when it can't find
them.  In fact, the keys are stored in the /etc/apt/trusted.gpg.d/.  The
relevant files are debian-archive-stretch-automatic.gpg
and debian-archive-stretch-security-automatic.gpg.  When you have an empty
trusted.gpg file in /etc/apt, it appears to ignore the
/etc/apt/trusted.gpg.d directory.   Deleting the empty trusted.gpg file
resolved the issue for me.   Importing the public keys manually isn't
helping because apt is looking to the wrong location for the public keys.

Jason

On Tue, Jul 4, 2017 at 10:28 AM, Wayne Hartell 
wrote:

> > On Tue, 2017-07-04 at 20:50 +0930, Wayne Hartell wrote:
> > > > Er ... sorry that last email should read " Phil Wyett's
> > > > suggestion" in
> > >
> > > this thread.
> > >
> > > Yes, trying Phil's suggestion and will report back once I have had the
> > > time to explore it properly (several systems now exhibiting this
> > > problem). As a teaser, it seems that even software-properties-gtk
> > > creates the trusted.gpg file, but even with that file deleted (as per
> > > Phil) and sticking to the terminal and apt-get, I get the same key
> > > related errors. In fact if I use software-properties-gtk it seems to
> > > jam up on "Refeshing software cache"...
> > > has been going on one machine now over 30 minutes.
> > >
> >
> >
> > Hi,
> >
> > I do not use the main server. I switched 'software-properties-gtk' to
> use it and I also get a hang at the what seems the end of the 'reload'
> > process. In the terminal I see:
> >
> > Traceback (most recent call last):
> >  File "/usr/lib/python3/dist-
> > packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in
> on_pktask_finish
> >results = self._pktask.generic_finish(result)
> > GLib.Error: pk-client-error-quark: E: The repository 'http://deb.debia
> n.org/debian stretch/updates Release' does not have a Release file.
> > W: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
> > W: See apt-secure(8) manpage for repository creation and user
> configuration details.
> > (319)
> >
> > During handling of the above exception, another exception occurred:
> >
> > Traceback (most recent call last):
> >  File "/usr/lib/python3/dist-
> > packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in
> on_pktask_finish
> >Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
> >  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
> 326, in new_init
> >return super_init_func(self, **new_kwargs)
> >  File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 537,
> in __init__
> >self._init(*args, **new_kwargs)
> >  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
> 326, in new_init
> >return super_init_func(self, **new_kwargs)
> >  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
> 326, in new_init
> >return super_init_func(self, **new_kwargs)
> > TypeError: could not convert value for property `transient_for' from
> DialogCacheOutdated to GtkWindow
> >
> > Using a mirror such as bytemark.co.uk, results in no issues here.
> >
> >
> >
> > Regards
> >
> > Phil
>
> I double checked here whether trusted.gpg is created or not when I use
> 'software-properties-gtk' and it definitely is. When that file is present,
> however, I get the errors related to being unable to read it, plus all the
> other errors remain, even when using the same server as you are using.
>
> FYI - I see the same exceptions as you in the terminal when running
> 'software-properties-gtk'.
>
> On a laptop that I have set up for my wife (time to get her into Debian!)
> I was able to solve the issue just now by doing the following:
>
> 1. sudo -rm -f /etc/apt/trusted.gpg
> [Thanks for this step!]
> 2. sudo apt-get update
> [generated errors]
> Err:15 http://ftp.iinet.net.au/debian/debian
> stretch/updates/non-free Sources
> 404 Not Found
> [Perhaps this expected with non-free sources]
> A bunch of stuff (only seen on this laptop) about 'Symlinking
> final file /var/lib/apt/lists <...> failed - pkgAcqIndex::StageDownloadDone
> (17: File exists)
> The repository 'http://ftp.iinet.net.au/debian/debian
> stretch/updates Release' does not have a Release file.
> Failed to fetch http://ftp.iinet.net.au/
> debian/dists/stretch/updates/non-free/source/Sources 404 Not Found
> But this time NO public key errors, which is weird because they
> were definitely happening earlier on this machine.
> 3. /var/lib/apt/lists$ sudo rm -r -f *
> [This was mentioned by Dejan Jocic earlier, but the thread didn't
> lead to a solution. I tried it this time due to the Symlinking errors I was
> seeing 

Re: Replace systemd

[Jason Wittlin-Cohen]

I assume this will work fine for a server system, but will it work on a
desktop system using GNOME?  From what I've read, GNOME has several systemd
dependencies, but it's not clear to me whether this requires systemd to be
used as init, or merely that systemd's packages must be installed.

Also, the future of sysvinit in Debian is not clear.  I've done some
research and one particular Debian developer claims that there is no plan
to support sysvinit as of Stretch, declaring that systemd is the only
option as of Stretch [1].  However, a different source [2] indicates that
there are several developers maintaining sysvinit currently.

[1]
https://www.reddit.com/r/debian/comments/3x8ef1/what_is_the_status_of_init_independency_in_stretch/cy2olz2/
[2] http://without-systemd.org/wiki/index.php/Debian_Stretch

On Mon, Jul 3, 2017 at 4:39 PM, Greg Wooledge  wrote:

> On Mon, Jul 03, 2017 at 08:42:11PM +0100, Rory Campbell-Lange wrote:
> > Simply put; systemd doesn't suit me. Its a bit like being asked to use
> > an graphical editor instead of vi. Or being forced to use Windows. My
> > laptop doesn't feel like my machine anymore.
> >
> > Is there a pure Debian alternative?
>
> You may switch to one of the other init systems.  Assuming stretch
> (Debian 9):
>
> To use sysvinit, simply "apt-get install sysvinit-core" and reboot.
>
> To use runit, "apt-get install runit-systemd", reboot, "apt-get install
> runit-init", and reboot again.
>
>