Re: N’hésites pas de commencer une conversation avec moi Caroline

Stop Le 04/07/2017, Caroline Ravisara a écrit : > > Je ne mords pas tu sais. Bon, sauf si t le demande… > http://bit.ly/2sIFNRR > > >

Re: Replace systemd

On 07/03/2017 01:41 PM, Jim Ohlstein wrote: Is there a pure Debian alternative? Have a look at https://devuan.org/. A couple of hours ago this was Debian Wheezy with the kde-plasma-desktop. Now it's Devuan Jessie and kde-plasma-desktop and the only systemd is "libsystemd0" and it seems

Re: Laser Printer recommendation...

On Tue, 4 Jul 2017 12:03:45 +0100 Brian wrote: > On Mon 03 Jul 2017 at 19:15:19 -0400, Celejar wrote: > > > On Mon, 3 Jul 2017 14:46:08 -0400 > > Dan Ritter wrote: > > > > ... > > > > > A Brother with all of: > > > > > > - ethernet networking > >

Re: Installing Debian on an android device

On Wed, Jul 5, 2017 at 8:58 AM, Fungi4All wrote: > Although I despise such devices, my only experience has been > helping a friend out locating certain settings and installing the proper > software for specific uses. > Lately, a problematic one, ended up in my hands as

Uitschrijven !!!!!!

Verzonden vanaf mijn Huawei mobiele telefoon

Re: Problems with apt in a clean stretch install.

I know I just wrote a long e-mail on this, but I think I just figured out in my own mind exactly what is going on and wanted to document it. As others have said the /etc/apt/trusted.gpg file is the issue. It seems that what is happening is this: 1. For some reason the first use

Re: Replace systemd

On Tue, 04 Jul 2017 15:35:10 -0700 David Griffith wrote: > On July 3, 2017 1:44:30 PM PDT, Martin Read > wrote: > >On 03/07/17 20:42, Rory Campbell-Lange wrote: > >> Is there a pure Debian alternative? > > > >There is an alternative init daemon, in the form of

Re: Replace systemd

On Tue, 4 Jul 2017 15:56:06 -0700 Jimmy Johnson wrote: > On 07/04/2017 03:11 PM, Patrick Bartek wrote: > > On Tue, 04 Jul 2017 19:51:39 +0200 deloptes > > wrote: > > > >> Christian Seiler wrote: > >> > >>> For both Jessie and Stretch, the following

Re: Problems with apt in a clean stretch install.

Firstly, thanks to all of those who have participated in this thread. I have some follow up comments and responses. This is a long reply, so the executive summary is that I managed to solve the issues on all my Stretch systems. There is a main issue and some kindred issues that manifest under

Re: N’hésites pas de commencer une conversation avec moi Ines

Stop!!! From: Ines Raelzki Sent: Tuesday, July 4, 2017 1:38:14 PM To: debian-user@lists.debian.org Subject: N’hésites pas de commencer une conversation avec moi Ines Je ne mords pas tu sais. Bon, sauf si t le demande…

Re: Replace systemd

Jimmy Johnson writes: > Funny, that sounds like something a Slack'er would say. Patrick, we > are not all keyboard wizards like you and that other Patrick who can > keyboard faster than I can read. That's a compliment on your abilities > by the way. Gnome or the Slacker way are not the only

Installing Debian on an android device

Although I despise such devices, my only experience has been helping a friend out locating certain settings and installing the proper software for specific uses. Lately, a problematic one, ended up in my hands as the owner gave up on it and purchased a better one. The problem seemed to be either

Re: Re: DOSEMU DPMI unhandled exception 0e (it's back!)

On July 4, 2017 3:55:32 PM PDT, bw wrote: >>>The trouble manifested when I tried using various components of an >old release of Turbo C. >>>Everything, 16 and 32 bit, tickles this bug. > >Hey David, don't give up, i got Turbo C+ 3.0 working fine in dosbox by >setting ver to

Re: Re: DOSEMU DPMI unhandled exception 0e (it's back!)

>>The trouble manifested when I tried using various components of an old >>release of Turbo C. >>Everything, 16 and 32 bit, tickles this bug. Hey David, don't give up, i got Turbo C+ 3.0 working fine in dosbox by setting ver to 6.00 in the dosbox.conf and using a real MS-DOS COMMAND.COM from

Re: Problems with apt in a clean stretch install.

> From: philwy...@kathenas.org > This issue seems to be created by "synaptic". > If you you "apt" in the terminal, you will be fine. As mindblowing as this topic seems to be I can not help but comment your response. It seems you must have not read 90% of the thread missing out on all the output

Re: Replace systemd

On 07/04/2017 03:11 PM, Patrick Bartek wrote: On Tue, 04 Jul 2017 19:51:39 +0200 deloptes wrote: Christian Seiler wrote: For both Jessie and Stretch, the following holds true: - GNOME requires systmed-logind's interfaces to work. (Or any alternative that implements the

Hibernar

Hola gente, desde que actualice al kernel 4.9.0.3 no me funciona la hibernación en mi portatil. Anteriormente con el 4.9.0.2 conseguí que funcionase siguiendo esta wiki: https://wiki.debian.org/SystemdSuspendSedation pero como digo desde que actualice a la 4.9.0.3 no hay manera. Lanzaba la

Re: Replace systemd

On July 3, 2017 1:44:30 PM PDT, Martin Read wrote: >On 03/07/17 20:42, Rory Campbell-Lange wrote: >> Is there a pure Debian alternative? > >There is an alternative init daemon, in the form of sysvinit (install >the package "sysvinit-core" to use this as your init daemon), and

Re: DOSEMU DPMI unhandled exception 0e (it's back!)

The trouble manifested when I tried using various components of an old release of Turbo C. Everything, 16 and 32 bit, tickles this bug. On July 4, 2017 7:52:36 AM PDT, bw wrote: >>When I start DOSEMU and use any DOS program, I get "DPMI: Unhandled >Exception 0e -

Re: Problems with apt in a clean stretch install.

On 07/04/2017 11:28 AM, Michael Lange wrote: Hi, On Tue, 4 Jul 2017 23:58:17 +0930 "Wayne Hartell" wrote: I did not read this last post or the whole thread very carefully, but now something hit my eyes: 4. sudo apt-get update [generated errors]

Re: Replace systemd

On Tue, 04 Jul 2017 19:51:39 +0200 deloptes wrote: > Christian Seiler wrote: > > > For both Jessie and Stretch, the following holds true: > > > > - GNOME requires systmed-logind's interfaces to work. (Or any > > alternative that implements the same DBus interface, but none

Re: Superblock last write time is in the future.

Le 04/07/2017 à 22:17, Felix Miata a écrit : Pascal Hambourg composed on 2017-07-04 21:28 (UTC+0200): Felix Miata composed: Pascal Hambourg composed on 2017-07-03 21:06 (UTC+0200): Setting the RTC with local time does not work with dual boot because when daylight saving time comes, both

HS Mailing list ou forum Django

Bonjour, Je découvre Django (sur Debian Stretch). Qui pourrait me conseiller une mailing list ou un forum ou équivalent ? Je ne parle ou écrit pas trop mal l'anglais mais la liste ou le forum était francophone en plus de tout le reste (bienveillance, activité, ...), je ne suis pas contre. Slts

Re: /etc/resolv.conf verdwenen na reboot

Op 04-07-17 om 16:30 schreef koen.w...@telenet.be > Een wilde gok: systemd en de bijhorende systemd-resolved.service? > > https://manpages.debian.org/testing/systemd/systemd-resolved.service.8.en.html Ik vind daar nog geen aanwijzingen die me doen vermoeden dat het /etc/resolv.conf zomaar

Re: Superblock last write time is in the future.

Pascal Hambourg composed on 2017-07-04 21:28 (UTC+0200): > Felix Miata composed: >> Pascal Hambourg composed on 2017-07-03 21:06 (UTC+0200): >>> Setting the RTC with local time does not work with dual boot because >>> when daylight saving time comes, both systems will do the shift, >>>

Re: Superblock last write time is in the future.

Le 03/07/2017 à 23:37, Felix Miata a écrit : Pascal Hambourg composed on 2017-07-03 21:06 (UTC+0200): Setting the RTC with local time does not work with dual boot because when daylight saving time comes, both systems will do the shift, resulting in a 2 hour shift unless some time

Re: Switching from Debian i386 to AMD64

On 2017-07-04 20:19 +0200, Dejan Jocic wrote: > On 04-07-17, Sven Joachim wrote: >> On 2017-07-04 17:33 +0200, Dejan Jocic wrote: >> > >> > Several. To see your cpu, type lscpu. Architecture is first in output. >> >> That's not correct, or at least not useful. The architecture is what >>

Re: Problems with apt in a clean stretch install.

Op 04-07-17 om 12:23 schreef Phil Wyett: This issue seems to be created by 'synaptic'. If you you 'apt' in the terminal, you will be fine. If you use 'software-properties-gtk' to adjust repositories, you will be fine. The issue is created if you run 'synaptic' and then adjust repositories via

Re: Switching from Debian i386 to AMD64

On 2017-07-04 18:39 +, Curt wrote: > On 2017-07-04, Sven Joachim wrote: >>> >>> Several. To see your cpu, type lscpu. Architecture is first in output. >> >> That's not correct, or at least not useful. The architecture is what >> uname(2) reports, and if the system is

RE : N’hésites pas de commencer une conversation avec moi Maeva

Bonsoir je te souhait une agréable soirée tendre bisous câlin Envoyé depuis mon appareil mobile Samsung.y Message d'origine De : Maeva Vouvi Date :04/07/2017 15:07 (GMT+00:00) À : debian-user@lists.debian.org Objet : N’hésites pas de commencer

Re: Switching from Debian i386 to AMD64

On 2017-07-04, Sven Joachim wrote: >> >> Several. To see your cpu, type lscpu. Architecture is first in output. > > That's not correct, or at least not useful. The architecture is what > uname(2) reports, and if the system is currently running a 32-bit > kernel, it will be

Re: Problems with apt in a clean stretch install.

Hi, On Tue, 4 Jul 2017 23:58:17 +0930 "Wayne Hartell" wrote: I did not read this last post or the whole thread very carefully, but now something hit my eyes: > 4. sudo apt-get update > [generated errors] > Err:16 http://ftp.iinet.net.au/debian/debian >

Re: Problems with apt in a clean stretch install.

On Tue, 04 Jul 2017 12:19:24 +0100 Phil Wyett wrote: > Additional info. Why via synaptic the 'trusted.gpg' file is being > created needs investigation. > > The file is a 32 byte file (way to small to be a valid key) is not > even viewable by normal key view methods i.e.

Re: Switching from Debian i386 to AMD64

Curt composed on 2017-07-04 17:53 (UTC): > Richard Owlett wrote: >> Thank you. I've i686 processors on both machines within reach ]as I >> suspected] >> I'll have to spend some time on man page for inxi to fully appreciate it. > But i686 is 32 bit isn't it? Some are 32, others are 64. 'cat

Re: Switching from Debian i386 to AMD64

On 04-07-17, Sven Joachim wrote: > On 2017-07-04 17:33 +0200, Dejan Jocic wrote: > > > On 04-07-17, Richard Owlett wrote: > >> I have been running Debian i386 since Squeeze. At that time it was required > >> as I was considering supporting some donated 32 bit machines at church. I > >> don't

Tu mort bien et tu suce apres

Envoyé à partir de mon Windows Phone

Re: Switching from Debian i386 to AMD64

On 2017-07-04 17:33 +0200, Dejan Jocic wrote: > On 04-07-17, Richard Owlett wrote: >> I have been running Debian i386 since Squeeze. At that time it was required >> as I was considering supporting some donated 32 bit machines at church. I >> don't recall what processor was in my personal machine

Re: Replace systemd

Christian Seiler wrote: > For both Jessie and Stretch, the following holds true: > > - GNOME requires systmed-logind's interfaces to work. (Or any > alternative that implements the same DBus interface, but none > exist in Debian at the moment) + one reason no to use Gnome

Re: How to deploy custom set of configuration files?

Joel Roth wrote: > I think the second scenario may be saying to change the > group of the altered config files, so the package manager > will know not to overwrite them during an upgrade. no it does not say that - it says the "group" of packages meaning not the user group. I think what they

Re: Switching from Debian i386 to AMD64

On 2017-07-04, Richard Owlett wrote: >> informations. >> > > Thank you. I've i686 processors on both machines within reach ]as I > suspected] > I'll have to spend some time on man page for inxi to fully appreciate it. But i686 is 32 bit isn't it? > I'm not aware of

Re: Switching from Debian i386 to AMD64

On 07/04/2017 10:33 AM, Dejan Jocic wrote: On 04-07-17, Richard Owlett wrote: I have been running Debian i386 since Squeeze. At that time it was required as I was considering supporting some donated 32 bit machines at church. I don't recall what processor was in my personal machine at that

Re: Laser Printer recommendation...

On Tue 04 Jul 2017 at 12:03:45 +0100, Brian wrote: > On Mon 03 Jul 2017 at 19:15:19 -0400, Celejar wrote: > > > On Mon, 3 Jul 2017 14:46:08 -0400 > > Dan Ritter wrote: > > > > ... > > > > > A Brother with all of: > > > > > > - ethernet networking > > > - duplex > > > -

Re: Switching from Debian i386 to AMD64

On 04-07-17, Richard Owlett wrote: > I have been running Debian i386 since Squeeze. At that time it was required > as I was considering supporting some donated 32 bit machines at church. I > don't recall what processor was in my personal machine at that time. I've > never had cause to investigate

Re: Debian 9 in VirtualBox

On Wed, 21 Jun 2017 19:48:52 +0200, Patrick Ruytings wrote: >Ik heb Debian 9 geïnstalleerd onder VirtualBox maar ik krijg geen >fullscreen beeld. Ik heb deze aanbevelingen gevolgd: >https://wiki.debian.org/VirtualBox >Maar toch lukt het mij niet. >Kan iemand mij

Switching from Debian i386 to AMD64

I have been running Debian i386 since Squeeze. At that time it was required as I was considering supporting some donated 32 bit machines at church. I don't recall what processor was in my personal machine at that time. I've never had cause to investigate the processors in my current laptops

Re: DOSEMU DPMI unhandled exception 0e (it's back!)

>When I start DOSEMU and use any DOS program, I get "DPMI: Unhandled Exception >0e - Terminating Client" That is really bad news, are you sure it's all programs, and not just programs that use DPMI ? If the problem is only DPMI enabled programs, you can probably solve it with some persistent

Re: update & dist-upgrade

El 04/07/17 a las 15:17, JAP escribió: Hoy ha sido el "gran día" para testing. Cambiamos de nombre. Si no estoy equivocado, el cambio fue el sábado pasado: Según el histórico de synaptic en mi equipo: Commit Log for Sat Jul 1 09:58:39 2017 Actualizó los siguientes paquetes: base-files

Re: Problems with apt in a clean stretch install.

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

Re: Laser Printer recommendation...

On Mon, Jul 03, 2017 at 07:15:19PM -0400, Celejar wrote: > On Mon, 3 Jul 2017 14:46:08 -0400 > Dan Ritter wrote: > > ... > > > A Brother with all of: > > > > - ethernet networking > > - duplex > > - BR/Script3 (Their PostScript clone, which I think is actually > >

Re: /etc/resolv.conf verdwenen na reboot

Een wilde gok: systemd en de bijhorende systemd-resolved.service? https://manpages.debian.org/testing/systemd/systemd-resolved.service.8.en.html Groeten, Koen Wybo - Oorspronkelijk bericht - Van: "Paul van der Vlis" Aan: debian-user-dutch@lists.debian.org

RE: Problems with apt in a clean stretch install.

> 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

/etc/resolv.conf verdwenen na reboot

Hallo, Op een server met Debian 9 heb ik een raar probleem. Na rebooten is het bestand /etc/resolv.conf verdwenen en werken nameserver lookups niet meer. Na het weer aanmaken werkt het weer. Ik gebruik ook dnsmasq, want de server is nameserver voor het lokale netwerk. Op de server staat een GUI

Re: Weigert te mounten op bepaalde locatie

Op 04-07-17 om 15:46 schreef Paul van der Vlis: > Hallo, > > Ik kan /dev/md2 goed mounten, maar op /disk gaat niet. Het lijkt goed te > gaan, maar het gaat niet goed: > > debian2:/# mount -v /dev/md2 /mnt > mount: /dev/md2 mounted on /mnt. > debian2:/# cd /mnt > debian2:/mnt# ls > data

R: Non esitare ad iniziare una conversazione con me Eleonora

Messaggio originale Da: "Eleonora Alenazi" Data: 4-lug-2017 12.16 A: Ogg: Non esitare ad iniziare una conversazione con me Eleonora --> Non mordo mica. Beh, posso farlo solo se me lo chiedi

Weigert te mounten op bepaalde locatie

Hallo, Ik kan /dev/md2 goed mounten, maar op /disk gaat niet. Het lijkt goed te gaan, maar het gaat niet goed: debian2:/# mount -v /dev/md2 /mnt mount: /dev/md2 mounted on /mnt. debian2:/# cd /mnt debian2:/mnt# ls data lost+found old debian2:/mnt# cd .. debian2:/# umount /mnt debian2:/# umount

update & dist-upgrade

Hoy ha sido el "gran día" para testing. Cambiamos de nombre. (O tal vez fue el fin de semana; desde el viernes no actualizaba) :~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 9.0 (stretch) Release:9.0 Codename: stretch :~#

Re: [trucs] affichage du mode vi du bash (readline inputrc)

On Tue, Jul 04, 2017 at 02:46:49PM +0200, pascatgm wrote: > On 03/07/2017 13:19, Alexandre Hoïde wrote: > > ¹ > > https://manpages.debian.org/stretch/readline-common/readline.3readline.en.html > > > Et pour ceux pour qui l'image parle plus que l'écrit... > > L'excellent site du non

Re: [trucs] affichage du mode vi du bash (readline inputrc)

On 03/07/2017 13:19, Alexandre Hoïde wrote: J'ai récemment découvert que GNU-readline -- le bidule pour la saisie et l'édition des lignes de commandes du bash -- permet d'afficher le mode (emacs / vi-insertion / vi-normal) en cours, à gauche de l'invite de commande. Pour ce faire, il faut

Re: Problems with apt in a clean stretch install.

On 07/04/2017 04:15 AM, Wayne Hartell wrote: The OP did not say, but I believe the problem is coming from a 9.1-live-dvd install, I had to same problem using it. The problem does not occur using the net-install. I have not tested any other installers but the rc3-live did not seem to have the

Re: N’hésites pas de commencer une conversation avec moi Adeline

Salut Sent from my Wiko RAINBOW UP 4GLe 4 juil. 2017 12:15, Adeline Horatiofoofoo a écrit : > > Je ne mords pas tu sais. Bon, sauf si t le demande… > http://bit.ly/2sHIzGR

[no subject]

Re: Problems with apt in a clean stretch install.

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

Re: Problems with apt in a clean stretch install.

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

RE: Problems with apt in a clean stretch install.

> 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

Re: Problems with apt in a clean stretch install.

On Tue, 2017-07-04 at 06:56 -0400, SDA wrote: > On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote: > > Er ... sorry that last email should read " Phil Wyett's > suggestion" in  > this thread.  > Hi, Additional info. Why via synaptic the 'trusted.gpg' file is being created needs

RE: Problems with apt in a clean stretch install.

> > > Read this: > > > > > > https://unix.stackexchange.com/questions/75807/no-public-key-availab > > > le-on-apt-get-update > > > > > > > Thanks. Yeah I have tried importing keys (even though they already exist as > > confirmed with 'apt-key list' and it makes no difference. All the keys > >

RE: Problems with apt in a clean stretch install.

> The OP did not say, but I believe the problem is coming from a 9.1-live-dvd > install, I had to same problem using it. The problem does not occur using the > net-install. I have not tested any other installers but the rc3-live did not > seem to have the problem, cause I > used it and

RE: Problems with apt in a clean stretch install.

> Out of the head, but you did check install media with MD5 or SHA sums? > Also, many people did do clean install of Jessie. Though, it is annoying bug for sure. But it is probably not so widespread. Perhaps you could give it a shot on a clean install with root enabled from start, you can always

Re: Laser Printer recommendation...

On Mon 03 Jul 2017 at 19:15:19 -0400, Celejar wrote: > On Mon, 3 Jul 2017 14:46:08 -0400 > Dan Ritter wrote: > > ... > > > A Brother with all of: > > > > - ethernet networking > > - duplex > > - BR/Script3 (Their PostScript clone, which I think is actually > >

Re: Problems with apt in a clean stretch install.

> > Read this: > > > > https://unix.stackexchange.com/questions/75807/no-public-key-available-on-apt-get-update > > > > Thanks. Yeah I have tried importing keys (even though they already exist as > confirmed with 'apt-key list' and it makes no difference. All the keys > complained about are

Re: Problems with apt in a clean stretch install.

On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote: Er ... sorry that last email should read " Phil Wyett's suggestion" in this thread.

Re: Problems with apt in a clean stretch install.

On 07/04/2017 03:23 AM, Phil Wyett wrote: On Tue, 2017-07-04 at 12:02 +0200, Dejan Jocic wrote: On 04-07-17, Wayne Hartell wrote: Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930): ...I managed to solve this error after checking that the permissions on /etc/apt/trusted.gpg were 0600 and

Re: Problems with apt in a clean stretch install.

On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote: > Thanks. Yeah I have tried importing keys (even though they already exist > as confirmed with 'apt-key list' and it makes no difference. All the keys > complained about are already present. > > I don't have enough experience nor

RE: Problems with apt in a clean stretch install.

> > W: GPG error: http://deb.debian.org/debian stretch Release: The following > > signatures couldn't be verified because the public key is not available: > > NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY > > CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500 > > W: The repository

Re: How to deploy custom set of configuration files?

Hi Viv, Varius Various wrote: > > Intuitive way to implement that would be to create a custom > package containing selected configuration files, and install it as a > last package. However according to [Debian GNU/Linux FAQ], [section > 11.7], it is not as simple. The wording of the

Re: Problems with apt in a clean stretch install.

Hi, On Tue, 4 Jul 2017 18:47:14 +0930 "Wayne Hartell" wrote: > > Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930): > > > > > ...I managed to solve this error after checking that the > > > permissions on /etc/apt/trusted.gpg were 0600 and edited them to be > > >

Re: Problems with apt in a clean stretch install.

On Tue, 2017-07-04 at 12:02 +0200, Dejan Jocic wrote: > On 04-07-17, Wayne Hartell wrote: > > > Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930): > > > > > > > ...I managed to solve this error after checking that the > > > > permissions on /etc/apt/trusted.gpg were 0600 and edited them > > >

Re: Problems with apt in a clean stretch install.

> W: GPG error: http://deb.debian.org/debian stretch Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY > CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500 > W: The repository

Re: Problems with apt in a clean stretch install.

On 04-07-17, Wayne Hartell wrote: > > Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930): > > > > > ...I managed to solve this error after checking that the > > > permissions on /etc/apt/trusted.gpg were 0600 and edited them to > > > be 0644. (Is this the correct default permission for the file

pam_systemd(su:session): Cannot create session: Already running in a session

Om mijn imaps server te monitoren gebruikte ik altijd het volgende commando (via xbindkeys): xfce4-terminal --maximize --execute su - imaps -c screen Om een of andere reden werkt dat niet meer. Als ik in de logging kijk zie ik: su[16105]: Successful su for imaps by cecil Dus ik voer niet

RE: Problems with apt in a clean stretch install.

> 1. Comment out DVD repository from /etc/apt/sources.list (add # before deb > cdrom:...). > 2. Try to # apt-get update > 3. Check if it work. If not, manualy download latest debian-archive-keyring > for stretch (from repository) and install it like > this: #dpkg -i

Re: Nvidia legacy driver install..

On 07/04/2017 01:09 AM, David Baron wrote: On יום שלישי, 4 ביולי 2017 16:27:21 IDT Mark Fletcher wrote: On Mon, Jul 03, 2017 at 09:17:00AM -0700, tony mollica wrote: On another note, just checking to see if anyone has used the nvidia driver (304 series) install and if there were any problems

Re: Problems with apt in a clean stretch install.

Dnia 2017-07-04, wto o godzinie 19:02 +0930, Wayne Hartell pisze: > > On 04-07-17, Wayne Hartell wrote: > > > > > > > >Did you try to change mirror you use in your sources.list? > > > > > > > > > > I did and it doesn't help (I get the same error with multiple > > > different sources). > > > > >

RE: Problems with apt in a clean stretch install.

> On 04-07-17, Wayne Hartell wrote: > > > > > >Did you try to change mirror you use in your sources.list? > > > > > > > I did and it doesn't help (I get the same error with multiple > > different sources). > > > > GPG error: http://deb.debian.org/debian stretch-updates InRelease: The > >

RE: Problems with apt in a clean stretch install.

>How about this solution, it worked in similar case: > > https://lists.debian.org/debian-user/2017/05/msg00467.html I saw that discussion earlier, but if you follow the thread through you'll note that the claim of "solution" was a false alarm. I will give it a try none the less, since I am

How to deploy custom set of configuration files?

Intuitive way to implement that would be to create a custom package containing selected configuration files, and install it as a last package. However according to [Debian GNU/Linux FAQ], [section 11.7], it is not as simple. The wording of the answer to this question is confusing,

RE: Problems with apt in a clean stretch install.

> Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930): > > > ...I managed to solve this error after checking that the > > permissions on /etc/apt/trusted.gpg were 0600 and edited them to be > > 0644. (Is this the correct default permission for the file trusted.gpg?)... > > I have to guess 644

Re: Problems with apt in a clean stretch install.

How about this solution, it worked in similar case: https://lists.debian.org/debian-user/2017/05/msg00467.html

Re: cant find distribution

On 04-07-17, Бурлаков Иван wrote: > Hi! > > Please help me! > > I cant find distr on debian 8.0 on website. > Please can you send me link for download (http link) iso debian 8.0& > > > ---  > С уважением, > Бурлаков Иван > +79260750111 > Archives:

Re: Problems with apt in a clean stretch install.

On 04-07-17, Wayne Hartell wrote: > > > >Did you try to change mirror you use in your sources.list? > > > > I did and it doesn't help (I get the same error with multiple different > sources). > > GPG error: http://deb.debian.org/debian stretch-updates InRelease: The > following signatures

Re: Problems with apt in a clean stretch install.

Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930): > ...I managed to solve this error after checking that the permissions on > /etc/apt/trusted.gpg were 0600 and edited them to be 0644. (Is this the > correct default permission for the file trusted.gpg?)... I have to guess 644 is correct, as

Re: Nvidia legacy driver install..

On יום שלישי, 4 ביולי 2017 16:27:21 IDT Mark Fletcher wrote: > On Mon, Jul 03, 2017 at 09:17:00AM -0700, tony mollica wrote: > > On another note, > > > > just checking to see if anyone has used the nvidia driver (304 series) > > install and if there were any problems that arose or needed to be

cant find distribution

Hi! Please help me! I cant find distr on debian 8.0 on website. Please can you send me link for download (http link) iso debian 8.0& ---  С уважением, Бурлаков Иван +79260750111

Re: LibreOffice5 Writer will not load

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jul 03, 2017 at 10:21:13PM -0700, dmacdoug wrote: > On Sun, Jul 02, 2017 at 12:12:40PM +0200, to...@tuxteam.de wrote: [...] > > Can you try to start it from a terminal [...] [...] > The first time I start it from a terminal there are no

Re: Nvidia legacy driver install..

On Mon, Jul 03, 2017 at 09:17:00AM -0700, tony mollica wrote: > On another note, > > just checking to see if anyone has used the nvidia driver (304 series) > install and if there were any problems that arose or needed to be resolved > either before or after the installation? > I had to do this

RE: Problems with apt in a clean stretch install.

> On 04-07-17, Wayne Hartell wrote: >> Hi all, >> >> >> >> I'm a Linux novice and have run into a problem with a clean Stretch >> install and apt. >> >> >> >> I started tinkering with Debian late in the game with Wheezy and have >> used Jessie pretty much without problem. After setting

Re: Problems with apt in a clean stretch install.

On 04-07-17, Wayne Hartell wrote: > Hi all, > > > > I'm a Linux novice and have run into a problem with a clean Stretch install > and apt. > > > > I started tinkering with Debian late in the game with Wheezy and have used > Jessie pretty much without problem. After setting up some new

Glib-2 2.64.2 unittest regex fails

Hi All, I am using Yocto poky Distro version 1.8.1 to build my image. And have used Glib-2 version 2.46.2 package. While testing glib-2 unittests, one of the test case "regex" failed with below logs: # ERROR:../../../glib-2.46.2/glib/tests/regex.c:129:test_new_fail: assertion failed (error ==

Problems with apt in a clean stretch install.

Hi all, I'm a Linux novice and have run into a problem with a clean Stretch install and apt. I started tinkering with Debian late in the game with Wheezy and have used Jessie pretty much without problem. After setting up some new Stretch systems (amd64) I am running into issues when using

Re: Kernel Panic in VMXNET3 Driver

Mini Trader wrote: > I am on stretch  Debian 4.9.30-2+deb9u2.  Is there a link to submit this > bug too? > > On Ubuntu's 4.4.0-83-generic this is not reproducible. usually reportbug is used to do this, however IMO you are hitting some other bug, but this is just a guess regards

  1   2   >