Re: Crashes with noveau driver and non-Debian software: How can I report the problems?

On 2017-08-16 05:14 -0400, Felix Miata wrote: > Erik Brangs composed on 2017-08-16 10:31 (UTC+0200): > >> ...The binaries sometimes crash on my machine and the console shows error >> messages from the nouveau driver. I asked upstream about this and they said >> it was "likely a buggy GL

Re: Crashes with noveau driver and non-Debian software: How can I report the problems?

Erik Brangs composed on 2017-08-16 10:31 (UTC+0200): > ...The binaries sometimes crash on my machine and the console shows error > messages from the nouveau driver. I asked upstream about this and they said > it was "likely a buggy GL implementation" in the graphics driver. The > binaries work

Crashes with noveau driver and non-Debian software: How can I report the problems?

Hi, I'm using Anki as a flashcard software. It was available in Jessie but has been removed for Stretch because upstream didn't release a version for current QT in time for Stretch. It's unlikely that Anki can get backported to Stretch because that would require a backport of QT [1]. So I need

Re: Problems with apt in a clean stretch install.

On Wed 05 Jul 2017 at 11:10:44 (+0200), Michael Lange wrote: > Hi, > > I'm glad you could finally fix the issue. > > On Wed, 5 Jul 2017 12:15:33 +0930 > "Wayne Hartell" wrote: > > > I know I just wrote a long e-mail on this, but I think I just figured > > out in my

Re: SAMBA problems on Debian 8.8

On Sat, 15 Jul 2017 17:10:03 +0200, Jason Wittlin-Cohen 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

Re: SAMBA problems on Debian 8.8

'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' I, too, have been having problems that seem to point to samba. Note that I am still running Jessie. If I run 'sudo

[SOLVED (mostly)] Re: SAMBA problems on Debian 8.8

Thanks a lot to all who have helped and/or contemplated my problem. After: --- apt-get install --reinstall samba apt-get install samba-dbg samba-doc ---

Re: SAMBA problems on Debian 8.8

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 amd64

Re: SAMBA problems on Debian 8.8

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

Re: SAMBA problems on Debian 8.8

Am 15.07.2017 um 14:58 schrieb Ulf Volmer: On 15.07.2017 13:56, Hans Kraus wrote: yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply stopped working. I did not do anything on the system. There were samba updates for jessie yesterday. First one was broken on some systems so

Re: SAMBA problems on Debian 8.8

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 > wrote: Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen: Did you run an apt-get

Re: SAMBA problems on Debian 8.8

On 15.07.2017 13:56, Hans Kraus wrote: > yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply > stopped working. I did not do anything on the system. There were samba updates for jessie yesterday. First one was broken on some systems so maybe it will help to do an upgrade again.

Re: SAMBA problems on Debian 8.8

On 15-07-17, Hans Kraus 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

SAMBA problems on Debian 8.8

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

Re: Problems with apt in a clean stretch install.

Hi, I'm glad you could finally fix the issue. On Wed, 5 Jul 2017 12:15:33 +0930 "Wayne Hartell" wrote: > 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

Re: Problems with apt in a clean stretch install.

On 05-07-17, Wayne Hartell wrote: > > Fungi4All wrote: > > And this for the OP: > > 1  But if there is such a basic problem with installation what is > > so different that the rest of the new stretch installers did not > > face? > > > > That's a good question. I'm not 100% sure what the problem

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: Problems with apt in a clean stretch install.

different circumstances. The main issue is that the /etc/apt/trusted.gpg file seems to be problematic and once *removed* (rather than just made readable) the problems are resolved. One quasi-significant secondary issue is that the installation DVD doesn't seem to be accepted as a valid source

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: 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: 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: 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: 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: 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

Re: Problems with apt in a clean stretch install.

now 100% for sure what I am looking at. Certainly the keys complained about are listed. Regards, Wayne. Hi Wayne, I have not tested that install dvd. But I did have problems with the live-dvd, I've used rc3 and it was great, maybe try it or use the zip file I attached to my other post for a qu

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.

ere's a chance it could be the former. > > > > Hmmm I use Jessie for last years, with no any experience with Strech yet. But > I feel you have some problem(s) with sources.list or with apt > file(s) privileges somehow/somewhere. > > In this link before, there is something

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.

always allow sudo for your user after that? Yes I did verify using SHA-256. f0a87f42ba0090314a4d3e45afe43d7fe7c115305bed266fe51a650c58cf3cab debian-9.0.0-amd64-DVD-1.iso My clean installs of Jessie never had any problems; just clean stretch installs. If I can't find any other solution I will try a

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: 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

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: 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.

he less, since I am clutching at straws now. FYI - I just tested a brand new clean install, this time NOT using a local mirror during installation and it's the same problems again. I have to conclude that there's something wrong with the installation, at least for the combination of options I am c

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: 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: Problems with apt in a clean stretch install.

r is an abbreviated hand typed reproduction; not the >> actual output. I can provide the full list of errors if it helps. >> >> >> >> In another thread I read something about ensuring that the >> "debian-archive-keyring" is installed, and it is,

Re: Problems with apt in a clean stretch install.

key is not available: NO_PUBKEY > > > > The above error is an abbreviated hand typed reproduction; not the actual > output. I can provide the full list of errors if it helps. > > > > In another thread I read something about ensuring that the > "debian-arch

Problems with apt in a clean stretch install.

eyring" is installed, and it is, version 2017.5. I just checked on second clean stretch install and it's the same situation; same exact problems. I am wondering what I might be doing wrong? Regards, Wayne.

Re: Problems with missing information in MATE's "help system"

n't understand. I can't believe a DE doesn't have a menu system. > >>Does it not have an Edit Preferences or some such. Then look for > >>Startup Programs in whatever Edit Preferences throws up, menu or > >>dialog box. > >> > >>Cheers, > >>David. > &g

Re: Problems with missing information in MATE's "help system"

ike GNOME 2 it will under System -> Preferences -> Startup Applications from the top panel. In Mate 1.16.2 (Stretch): System->Preferences->Personal->Startup Applications In Mate 1.8.1 (Jessie): System->Preferences->Startup Applications I think there were two pro

Re: Problems with missing information in MATE's "help system"

On 2017-06-29, David Wright wrote: > On Tue 27 Jun 2017 at 08:26:47 (-0500), Richard Owlett wrote: >> I am using the MATE desktop on Debian Stretch. >> I wish to run a user specific script each time a specific user logs in. >> The script is known to work because I

Re: Problems with missing information in MATE's "help system"

On Tue 27 Jun 2017 at 08:26:47 (-0500), Richard Owlett wrote: > I am using the MATE desktop on Debian Stretch. > I wish to run a user specific script each time a specific user logs in. > The script is known to work because I manually run it each and every > time I login. > > The MATE help system

Problems with missing information in MATE's "help system"

I am using the MATE desktop on Debian Stretch. I wish to run a user specific script each time a specific user logs in. The script is known to work because I manually run it each and every time I login. The MATE help system lacks a usable index making finding a specific option difficult. One

Email problems

please ignore & excuse the noise 0x17F9F9B7.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature

Re: Workaround {Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]}

On Sat 24 Jun 2017 at 06:42:34 (-0500), Richard Owlett wrote: > On 06/23/2017 02:42 PM, Felix Miata wrote: > >Richard Owlett composed on 2017-06-23 06:25 (UTC-0500): > >. > >>>I've identified one problem source. > >>>At least sometimes after a power off shut down it comes up with the > >>>laptop

Re: Workaround {Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]}

On 06/23/2017 02:42 PM, Felix Miata wrote: Richard Owlett composed on 2017-06-23 06:25 (UTC-0500): . I've identified one problem source. At least sometimes after a power off shut down it comes up with the laptop display selected as primary. How can I force it to always come up with the VGA

Re: Workaround {Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]}

Richard Owlett composed on 2017-06-23 06:25 (UTC-0500): . >> I've identified one problem source. >> At least sometimes after a power off shut down it comes up with the >> laptop display selected as primary. >> How can I force it to always come up with the VGA monitor as primary? . Maybe

Re: Where to Report Non-Bug Problems

On 06/23/2017 10:06 AM, Greg L wrote: I wanted to report missing backgrounds (wallpaper) in Debian Stretch stable. Which individual or email address shall I report this to? I appreciate your help. Thank you. Most likely report it against whichever desktop environment you are using. If you

Re: Where to Report Non-Bug Problems

Great, thank you. On Jun 23, 2017 8:38 AM, "Henrique de Moraes Holschuh" wrote: > On Fri, 23 Jun 2017, Greg L wrote: > > I wanted to report missing backgrounds (wallpaper) in Debian Stretch > > stable. Which individual or email address shall I report this to? I > > appreciate

Re: Where to Report Non-Bug Problems

On Fri, 23 Jun 2017, Greg L wrote: > I wanted to report missing backgrounds (wallpaper) in Debian Stretch > stable. Which individual or email address shall I report this to? I > appreciate your help. Thank you. Since this is unrelated to software defects, and you already contacted the list

Where to Report Non-Bug Problems

I wanted to report missing backgrounds (wallpaper) in Debian Stretch stable. Which individual or email address shall I report this to? I appreciate your help. Thank you.

Workaround {Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]}

On 06/20/2017 07:14 AM, Richard Owlett wrote: On 06/18/2017 05:45 AM, Richard Owlett wrote: On 06/17/2017 03:02 PM, Curt wrote: On 2017-06-17, Richard Owlett wrote: I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too small and is in the "short and

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 07:20 PM, Jimmy Johnson wrote: On 06/20/2017 05:14 AM, Richard Owlett wrote: On 06/18/2017 05:45 AM, Richard Owlett wrote: On 06/17/2017 03:02 PM, Curt wrote: On 2017-06-17, Richard Owlett wrote: I'm using Debian Testing on a Lenovo T510 Thinkpad whose

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 05:14 AM, Richard Owlett wrote: On 06/18/2017 05:45 AM, Richard Owlett wrote: On 06/17/2017 03:02 PM, Curt wrote: On 2017-06-17, Richard Owlett wrote: I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too small and is in the "short and

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

Richard Owlett composed on 2017-06-20 07:14 (UTC-0500): > How can I force it to always come up with the VGA monitor as primary? . If you are interested, might like to try to create an xorg.conf that will do what you want. In order to make such attempt I will need: 1-to see an unadulterated[1]

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 20/06/17 21:21, Richard Owlett wrote: On 06/20/2017 02:06 PM, JPlews wrote: On 20/06/17 13:14, Richard Owlett wrote: I had understood ARandR would use it automatically. It evidently doesn't. This is my experience too, including some of the randomness, after reboots the DE is setting

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 02:41 PM, deloptes wrote: I've identified one problem source. At least sometimes after a power off shut down it comes up with the laptop display selected as primary. How can I force it to always come up with the VGA monitor as primary? I created

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 02:06 PM, JPlews wrote: On 20/06/17 13:14, Richard Owlett wrote: I had understood ARandR would use it automatically. It evidently doesn't. This is my experience too, including some of the randomness, after reboots the DE is setting things, I find Gnome really weak in this area.

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

> > I've identified one problem source. > At least sometimes after a power off shut down it comes up with the > laptop display selected as primary. > How can I force it to always come up with the VGA monitor as primary? > > I created /home/richard/.screenlayout/VGA-as-master.sh with preferred >

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 20/06/17 13:14, Richard Owlett wrote: I had understood ARandR would use it automatically. It evidently doesn't. This is my experience too, including some of the randomness, after reboots the DE is setting things, I find Gnome really weak in this area. The window oddness you describe

Re: Debian Stretch: Problems with installation - computer froze

Hi, had similar problem with debian9. After basic installation I installed serveral services und system haltet while running apt-get install. We're running debian as virtual machines on ESX 6.5. So, I've figured out, when you install a brand new Server together with ESX6.5 mode and vmxnet3

One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/18/2017 05:45 AM, Richard Owlett wrote: On 06/17/2017 03:02 PM, Curt wrote: On 2017-06-17, Richard Owlett wrote: I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too small and is in the "short and wide" category. I prefer my 17" diagonal external

Re: problems with _apt user privileges in upgrading from Jessie to Stretch [solved?]

On 2017-06-19 11:03 -0700, Jim McCloskey wrote: > Sven Joachim (svenj...@gmx.de) wrote: > > |> On my system, only /var/lib/apt/lists/partial is owned by > |> the _apt user, and it's not world-readable: > >|> All the regular files in /var/lib/apt/lists are owned by >

Re: Re: problems with _apt user privileges in upgrading from Jessie to Stretch [solved?]

Sven Joachim (svenj...@gmx.de) wrote: |> On my system, only /var/lib/apt/lists/partial is owned by |> the _apt user, and it's not world-readable: |> All the regular files in /var/lib/apt/lists are owned by |> root:root and have standard 0644 permissions Thank

Re: problems with _apt user privileges in upgrading from Jessie to Stretch [solved?]

On 2017-06-18 13:30 -0700, Jim McCloskey wrote: > Posting here in case this might help others who may be encountering the > same problem. > > I really appreciate the enhanced security provided for apt in the new > release. But one of the changes caused me a small headache in upgrading. >

problems with _apt user privileges in upgrading from Jessie to Stretch [solved?]

Posting here in case this might help others who may be encountering the same problem. I really appreciate the enhanced security provided for apt in the new release. But one of the changes caused me a small headache in upgrading. Following the upgrade, running `apt get update'resulted in

Re: ARandR problems: Bug or opderator?

On 06/17/2017 03:02 PM, Curt wrote: On 2017-06-17, Richard Owlett wrote: I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too small and is in the "short and wide" category. I prefer my 17" diagonal external with a nominal 4:3 aspect ratio. I am using

Re: ARandR problems: Bug or opderator?

On 2017-06-17, Richard Owlett wrote: > I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too > small and is in the "short and wide" category. > I prefer my 17" diagonal external with a nominal 4:3 aspect ratio. > > I am using ARandR Screen Layout Editor

dist-upgrade jessie->stretch, texlive problems

Hi all, I performed a dist-upgrade from jessie to stretch on my desktop. It did not went well. I manage to solve many problems except the texlive issue. I finally remove anything tex related and try to slowly install it back. I started with tex-common. That went well. Then with texlive-base

ARandR problems: Bug or opderator?

768 and normal orientation vga monitor as 1280 x 1024 and normal orientation With those settings it _can_ and *FREQUENTLY* does display what I want. Generally it chooses not to :/ I have two problems which I presume to be closely intertwined. After a cold boot, if I open a text file with pluma it fill

Re: Encoding problems with latin accented characters in vfat partition

this >> list).  The only problem now is about latin accented characters such as >> bontà, perché, ragù, ecc...  In my home directory I have many files such >> named, but when I want to copy them into the above vfat driver there are >> encoding problems: those characte

Re: Encoding problems with latin accented characters in vfat partition

ist). The only problem now is about latin accented characters such as >> bontà, perché, ragù, ecc... In my home directory I have many files such >> named, but when I want to copy them into the above vfat driver there are >> encoding problems: those characters are messing and `

Re: Encoding problems with latin accented characters in vfat partition

racters such as bontà, > perché, > ragù, ecc...  In my home directory I have many files such named, but > when I > want to copy them into the above vfat driver there are encoding > problems: those > characters are messing and `Bad file decriptor' error messages > sometimes >

Re: Encoding problems with latin accented characters in vfat partition

> perché, ragù, ecc... In my home directory I have many files such named, but > when I want to copy them into the above vfat driver there are encoding > problems: those characters are messing and `Bad file decriptor' error > messages sometimes appear. I've never had this problem before, i

Encoding problems with latin accented characters in vfat partition

such named, but when I want to copy them into the above vfat driver there are encoding problems: those characters are messing and `Bad file decriptor' error messages sometimes appear. I've never had this problem before, in my Linux home directory. Please suggest whoever can how to face and solve

Re: puppy Linux reports problems with USB/network drive

com>: > Original Message > > Subject: Re: puppy Linux reports problems with USB/network drive > UTC Time: May 21, 2017 11:33 AM > From: pas...@plouf.fr.eu.org > > Le 21/05/2017 à 04:56, Albert Hodge a écrit : > > > > When I plugged it into

Re: puppy Linux reports problems with USB/network drive

Original Message Subject: Re: puppy Linux reports problems with USB/network drive UTC Time: May 21, 2017 11:33 AM From: pas...@plouf.fr.eu.org Le 21/05/2017 à 04:56, Albert Hodge a écrit : > > When I plugged it into the USB port it gave a warning message, that the >

Re: puppy Linux reports problems with USB/network drive

Le 21/05/2017 à 04:56, Albert Hodge a écrit : When I plugged it into the USB port it gave a warning message, that the NTFS -3g driver was able to mount the NTFS partition but says, Dirty volume mount was forced by the "force" mount option. It is mounted read/write, but advice is only write to

web site problems on localhost

Greetings; I found the problem, something had replaced the index.html, which was a link to the front-page.html of my web site with the default apache index.html. Restored that by rm'ing the renamed copy of it, then cp'd the ~ version back to the real one, voila! Web page functions normally.

Re: Sound problems (mpd, mpv mainly)

On Mon, 17 Apr 2017, kamaraju kusumanchi wrote: > On Sat, Apr 8, 2017 at 7:09 AM, Pierre Frenkiel > wrote: > > Nevertheless, I don't see why this package is not > > upgraded in Jessie: it just gives a list, and have then no dependency > > problem. > > Packages in

Re: Sound problems (mpd, mpv mainly)

On Sat, Apr 8, 2017 at 7:09 AM, Pierre Frenkiel wrote: > Nevertheless, I don't see why this package is not > upgraded in Jessie: it just gives a list, and have then no dependency > problem. Packages in Debian Stable are upgraded only when it fixes a security

Re: Sound problems (mpd, mpv mainly)

Thanks Kamaraju, that looks awesome. So extrapolating from the pattern of the dates, i would guess that 'stretch' should be actually released on the creation date of 'buster', 2018-07-01. (And i should note, just for the record, that indeed the wikipedia article on debian versions had more

Re: Sound problems (mpd, mpv mainly)

On Sat, 8 Apr 2017, Frank wrote: What makes you think it shouldn't matter? Jessie has version 0.26 of the distro-info-data package. That line must have been added in a later version. Stretch has 0.33 and jessie-backports 0.32~bpo8+1. you are right: installing version .33 actually gives the

Re: Sound problems (mpd, mpv mainly)

Op 08-04-17 om 09:23 schreef Pierre Frenkiel: On Sat, 8 Apr 2017, kamaraju kusumanchi wrote: . . . % cat /usr/share/distro-info/debian.csv . . . 11,Bullseye,bullseye,2020-11-05 hi, can you explain why I don't have this line? I am on Jessie, but that should not matter. What makes you

Re: Sound problems (mpd, mpv mainly)

On Sat, 8 Apr 2017, kamaraju kusumanchi wrote: . . . % cat /usr/share/distro-info/debian.csv . . . 11,Bullseye,bullseye,2020-11-05 hi, can you explain why I don't have this line? I am on Jessie, but that should not matter. best regards, -- Pierre Frenkiel

<    5   6   7   8   9   10   11   12   13   14   >