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 of software-properties-gtk creates this file, but (the bug I presume) is that it's not created correctly. It's empty and potentially has the wrong permissions on it. a. I suspect it being empty is the consequence of the permissions, but I am just guessing. 2. Running 'apt-get update' will now produce errors about user "_apt" and not being able to read the /etc/apt/trusted.gpg file. 3. Making /etc/apt/trusted.gpg readable (i.e., 0600 --> 0644) only obfuscates the problem; now the empty file is accessible (so no errors about reading it), but the keys are not available and /etc/apt/trusted.gpg.d is now ignored and results in key errors. [Wild goose chase may now commence]. 4. The real fix is to delete /etc/apt/trusted.gpg and after that point it seems not to be created again (even if running software-properties-gtk). Everything works again since the /etc/apt/trusted.gpg.d folder can once again be interrogated. Hopefully this post isn't just adding noise, but I thought a short description of the issue in one post could be useful for posterity.
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 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, but no big deal I guess. Now for the full details. I have managed to solve, I think, the problem on 2 physical laptops and 2 virtual machines. I think I was getting side tracked by multiple different apt-get errors and different output on different machines. On one (Dell) laptop I had to: 1. Delete /etc/apt/trusted.gpg 2. Purge /var/lib/apt/lists [I was seeing symlinking errors with that path in the apt-get output] 3. Change sources.list to the default described here: https://wiki.debian.org/SourcesList (On that laptop I am using contrib and non-free for Ethernet and Wifi). On the VM where I ran into this issue initially, and where I was going well out of my comfort zone trying to "fix" stuff, I had to: 1. Delete /etc/apt/trusted.gpg 2. Restore /etc/apr/trusted.gpd.d [which I had blown away somehow during previous attempts at solving the issue] [apt-key list was returning an empty list which I realized was due to my heavy handedness there] 3. Change sources.list to the default described here: https://wiki.debian.org/SourcesList (On that VM I am NOT using contrib and non-free). [EDIT: Now I realize that the problems with my local mirror might only be present when contrib and non-free are included]. On a different (Compaq) laptop (where I have LVM/encryption) I had never ran Synaptic and so didn't need to do anything other than remove the install DVD from /etc/apt/sources.list, and it seems that I also edited sources.list to that described here: https://wiki.debian.org/SourcesList (On that laptop I am using contrib and non-free for Wifi only). On the second VM, where I had also never run Synaptic, 'sudo apt-get update' results in the following issues off the bat. W: The repository 'cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 DVD Binary-1 20170617-13:08] stretch Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 DVD Binary-1 20170617-13:08]/dists/stretch/main/binary-amd64/Packages Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs E: Some index files failed to download. They have been ignored, or old ones used instead. If I edit /etc/apt/sources.list to comment the second line for the DVD (one duplicate commented line exists already) then 'sudo apt-get update' runs without error, even when using the original local mirror repositories. [EDIT: I think the local mirror works because I am not using contrib and non-free on the VMs]. debianuser@masterdebian964:~$ sudo apt-get update Ign:1 http://ftp.iinet.net.au/debian/debian stretch InRelease Hit:2 http://ftp.iinet.net.au/debian/debian stretch-updates InRelease Hit:3 http://ftp.iinet.net.au/debian/debian stretch Release Hit:5 http://security.debian.org/debian-security stretch/updates InRelease Reading package lists... Done I'm not sure what the issue with the DVD is. I don't recall such an issue in Jessie, but it's not a deal breaker. Now if on this second VM I run Synaptic (or software-properties-gtk) and edit the repository sources, running 'sudo apt-get update' results in: Hit:1 http://security.debian.org/debian-security stretch/updates InRelease Ign:2 http://ftp.iinet.net.au/debian/debian stretch InRelease Hit:3 http://ftp.iinet.net.au/debian/debian stretch-updates InRelease Hit:4 http://ftp.iinet.net.au/debian/debian stretch Release Reading package lists... Done W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://ftp.iinet.net.au/debian/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://ftp.iinet.net.au/debian/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key. If I delete /etc/apt/trusted.gpg the issue is resolved and furthermore, if I re-edit my sources list using software-properties-gtk *again* the /etc/apt/trusted.gpg file is no longer re-created. It
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 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
on this particular laptop.]
4. sudo apt-get update
[generated errors]
Err:16 http://ftp.iinet.net.au/debian/debian stretch/updates/non-free
Sources
404 Not Found
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
5. sudo apt-get upgrade
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
6. So then I tried changed sources.list to that found here:
https:
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 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.
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 > > complained about are already present. > > > > I don't have enough experience nor understanding of Linux to know whether > > it's a bug or dumb user and though I suspect the latter, I feel like > > there'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 more - did You try to install > debian-keyring (before was debian-archive-keyring)? I had no problems under Jessie and have used it on multiple systems. This seems to be a new issue with Stretch. There doesn't seem to be a debian-keyring package under stretch (only debian-archive-keyring). I'm following some other leads and will report back how I go. I do very much appreciate your assistance.
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 installed software with no > problem. > > Cheers, > -- > Jimmy Johnson > Debian Stretch - KDE Plasma 5.8.6 at sda13 Registered Linux User #380263 Hi Jimmy, I saw one of your previous posts regarding the live cd/dvd. I used the following to install, but not sure if this is the live dvd you refer to (I thought there was a difference between a regular install dvd and a live dvd?). f0a87f42ba0090314a4d3e45afe43d7fe7c115305bed266fe51a650c58cf3cab debian-9.0.0-amd64-DVD-1.iso My keys (using apt-key list) seem to be present, but then I am not experienced enough to know 100% for sure what I am looking at. Certainly the keys complained about are listed. Regards, Wayne.
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 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 clean install with root enabled, though if the DVD is the culprit (as per Jimmy Johnson) I may be best off installing 8.8 and doing a net upgrade.
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 'http://deb.debian.org/debian stretch Release' is not > > signed. > > N: Data from such a repository can't be authenticated and is therefore > > potentially dangerous to use. > > N: See apt-secure(8) manpage for repository creation and user configuration > > details. > > E: Failed to fetch > > http://deb.debian.org/debian/dists/stretch/updates/main/source/Sources 404 > > Not Found [IP: 52.85.41.44 80] > > E: Some index files failed to download. They have been ignored, or old ones > > used instead. > > > > > > 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 already present. I don't have enough experience nor understanding of Linux to know whether it's a bug or dumb user and though I suspect the latter, I feel like there's a chance it could be the former.
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 /path/to/debian-archive-keyring.deb and try again to make > update. I did this. Here is the full output in case I am missing something pertinent in my previous descriptions of the errors. debianuser@masterdebian964:~/Documents$ sudo dpkg -i debian-archive-keyring_2017.5_all.deb (Reading database ... 126483 files and directories currently installed.) Preparing to unpack debian-archive-keyring_2017.5_all.deb ... Unpacking debian-archive-keyring (2017.5) over (2017.5) ... Setting up debian-archive-keyring (2017.5) ... debianuser@masterdebian964:~/Documents$ sudo apt-get update Ign:1 http://deb.debian.org/debian stretch InRelease Ign:2 http://deb.debian.org/debian stretch/updates InRelease Get:3 http://deb.debian.org/debian stretch-updates InRelease [88.5 kB] Hit:4 http://deb.debian.org/debian stretch Release Ign:3 http://deb.debian.org/debian stretch-updates InRelease Ign:5 http://deb.debian.org/debian stretch/updates Release Get:6 http://deb.debian.org/debian stretch Release.gpg [3,108 B] Ign:6 http://deb.debian.org/debian stretch Release.gpg Ign:7 http://deb.debian.org/debian stretch/updates/main Sources Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons Ign:7 http://deb.debian.org/debian stretch/updates/main Sources Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons Ign:7 http://deb.debian.org/debian stretch/updates/main Sources Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons Ign:7 http://deb.debian.org/debian stretch/updates/main Sources Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons Ign:7 http://deb.debian.org/debian stretch/updates/main Sources Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons Err:7 http://deb.debian.org/debian stretch/updates/main Sources 404 Not Found [IP: 52.85.41.44 80] Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons Fetched 91.6 kB in 33s (2,733 B/s) Reading package lists... Done W: GPG error: http://deb.debian.org/debian stretch-updates
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 couldn't be verified because the public key is > > not > > available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The > > repository 'http://deb.debian.org/debian stretch-updates InRelease' is > > not signed.Updating from such a repository can't be done securely, and > > is therefore disabled by default.See apt-secure(8) manpage for > > repository creation and user configuration details. > > > > Notably, the keys (e.g., 8B48AD6246925553 and 7638D0442B90D010) ARE > > present when I run 'apt-key list'. > > > > When I search this forum for these keys (e.g., "8B48AD6246925553") I > > find two threads with similar kinds of errors, but no solution on > > either. I'm wondering whether I have fallen into some kind of crack perhaps. > > > > Not sure that it will be helpful, but just a thought. How about reinstalling debian-archive-keyring package? That doesn't seem possible, I get: "Reinstallation of debian-archive-keyring is not possible, it cannot be downloaded." I tried adding my installation DVD back into the sources, but apt rejects it with the following: "The repository 'cdrom://Debian GNU/Linux 9.0.0 _Stretch_ = Official amd64 DVD Binary-1 20170617-13:08] stretch Release' does not have a Release file."
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 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 choosing. I may have to go back to Jessie where I never had these kinds of problems.
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 that is what is set on the Stretch I have > booted currently (as are all regular files in /etc/apt/), and I've never > touched it myself. > > Do you get the same errors running 'apt update' instead of 'apt-get update'? Yes, it seems that I get the same errors that way too. I tried a new clean install test and seem to end up with permissions under /etc/apt/ always as 0600, so I am not sure what is going on. Looks like an issue with a clean install, but I am wondering why it's not coming up more often (unless most people are upgrading from Jessie).
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 >> Stretch systems (amd64) I am running into issues when using apt. >> >> >> >> The first set of errors I get from apt when trying to run "update" are: >> >> >> >> W: http://ftp.iinet.net.au/debian/debian/dists/stretch-updates/InRelease: >> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file >> is not readable by user '_apt' executing apt-key. >> >> W: http://ftp.iinet.net.au/debian/dists/stretch/Release.gpg: The >> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is >> not readable by user '_apt' executing apt-key. >> >> W: >> http://security.debian.org/debian-security/dists/stretch/updates/InRelease: >> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file >> is not readable by user '_apt' executing apt-key. >> >> >> >> 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?) >> >> >> >> After that, when I run apt-get update again, I get a list of errors >> about errors occurring due to signature verification. >> >> e.g., "The repository is not updated and the previous index files will >> be used. GPG error: http://ftp.iinet.net.au/debian/debian >> stretch-updates >> InRelease: The following signatures couldn't be verified because the >> public 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-archive-keyring" 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. > >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 couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The repository 'http://deb.debian.org/debian stretch-updates InRelease' is not signed.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details. Notably, the keys (e.g., 8B48AD6246925553 and 7638D0442B90D010) ARE present when I run 'apt-key list'. When I search this forum for these keys (e.g., "8B48AD6246925553") I find two threads with similar kinds of errors, but no solution on either. I'm wondering whether I have fallen into some kind of crack perhaps. I'm not sure why this is happening with all my fresh installs. I am wondering whether the fact I used a local mirror (ftp.iinet.net.au) during the install process has anything to do with it. I guess there is one way to find out. Another thing I'll mention that may or may not be relevant is that during the installation I did not (and have not in the past) set up root, instead preferring to use sudo. I should also note that I read in another thread that Jimmy Johnson says: "Also, if you used the live dvd it's screwing up apt gpg-keys and you will not see updates until the keys are fixed. ", but I didn't install from the live DVD, I installed from the regular non live DVD, so I don't think this is relevant. In the meantime I guess I can experiment with different install settings/approaches, but I'd rather, of course, find a way to fix an already installed system. Cheers.
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 apt. The first set of errors I get from apt when trying to run "update" are: W: http://ftp.iinet.net.au/debian/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://ftp.iinet.net.au/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key. 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?) After that, when I run apt-get update again, I get a list of errors about errors occurring due to signature verification. e.g., "The repository is not updated and the previous index files will be used. GPG error: http://ftp.iinet.net.au/debian/debian stretch-updates InRelease: The following signatures couldn't be verified because the public 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-archive-keyring" 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: Debian Gnome Or XFCE ?
I am currently a Debian Jessie XFCE user. I want to have your views on Gnome VS XFCE. I want to try Gnome but I want to know if Gnome is stable and works constantly without freezing and crashing. Please share me your experience with Debian Gnome. With Kind Regards, Dwijesh I haven't had trouble with Gnome3 on both a real laptop (low power Compaq with Intel graphics), and also on VMware virtual machines (although there were some hoops to jump through to avoid fallback mode for Debian 7). Debian 8 works seamlessly on VMware. I also got Gnome3 running in the Jessie beta on a 9 year old desktop, without issue and it seemed to perform reasonably well. I can't compare to XCFE since I haven't used that, but I do like Gnome 3.
RE: Debian 7.1 root password issue.
Cindy-Sue Causey butterflyby...@gmail.com wrote: On 2/2/15, Wayne Hartell w.hart...@ozemail.com.au wrote: Michael Collins wrote: Log in with the user account. Left-click the user account name (upper right corner), select system settings, select user, left-click Unlock. Enter the root password. Change the user account to an administrator. As a new Linux/Debian user I have been doing the not recommended thing (at least I think it says it's not recommended; it has been a while since my last install) thing of not setting a password for root. That way there's no hoops to jump through to the installer puts my intended user account into the sudoers list. Now the steps to do this manually are re-described above I realize that under Gnome it's not actually that hard to do (when making my install selections I had memories of the manual way trying to edit the sudoers file, which for a new user is a little daunting. I recall it taking me a few attempts to get it to work. The installer gave me an easy way out). That brings me to my point; due to my installer choices, I cannot log in under root on the three systems that I have installed so far. Right now I have no reason to believe that this is or ever will be an issue since I can use sudo and that feels safer to me. Does anyone have any different opinions on this? (These are home systems and predominantly for learning Linux/Debian at this point, as opposed to being core systems that are depended upon for daily use, although one day in the not too distant future I hope to change this). My apologies if this has already been suggested or if you've already mentioned you tried it, but have you tried: passwd root via command line as one of your users that has rights to do so? You enter a password, enter it again to confirm, and done deal. It seems a little too easy to do, actually. Every time I do it, my mind wanders off thinking how easy it is to change if someone gains control of one of our sudo enabled user accounts... I just gave that a whirl and yes it works like a charm! Regards, Wayne. Just thinking out loud :) Cindy :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/006b01d0402b$6d149060$473db120$@ozemail.com.au
RE: Debian 7.1 root password issue.
Michael Collins wrote: SANG KIM sangkim8986 at msn.com writes: I recently installed debian 7.1 and I reinstalled it at least five times. I've tried installing it with a root password created and without and Debian still won't let me log in as root. It says authentication failed after I type in the root password. I've tried reinstalling it without creating a root password and it still won't let me log in. I get the same message as before. I can log in as another user, but not as root. I've checked the passwords entered and every time the password is correct, but Debian says that it's not. How can I fix these issues. I've tried to use the password command to remove whatever password I created/didn't create and I get an error message that the password command cannot be found in BASH. Is there something wrong with the Debian 7.1? I can't even install updates to the OS. Thank you. Log in with the user account. Left-click the user account name (upper right corner), select system settings, select user, left-click Unlock. Enter the root password. Change the user account to an administrator. What a pita! Regards, MC As a new Linux/Debian user I have been doing the not recommended thing (at least I think it says it's not recommended; it has been a while since my last install) thing of not setting a password for root. That way there's no hoops to jump through to the installer puts my intended user account into the sudoers list. Now the steps to do this manually are re-described above I realize that under Gnome it's not actually that hard to do (when making my install selections I had memories of the manual way trying to edit the sudoers file, which for a new user is a little daunting. I recall it taking me a few attempts to get it to work. The installer gave me an easy way out). That brings me to my point; due to my installer choices, I cannot log in under root on the three systems that I have installed so far. Right now I have no reason to believe that this is or ever will be an issue since I can use sudo and that feels safer to me. Does anyone have any different opinions on this? (These are home systems and predominantly for learning Linux/Debian at this point, as opposed to being core systems that are depended upon for daily use, although one day in the not too distant future I hope to change this). Cheers. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/000f01d03f67$e938cea0$bbaa6be0$@ozemail.com.au
RE: gedit bug with long lines. (was RE: gedit slow with a 1.5Mb text file)
Curt wrote: The *gedit faq* is edifying on the long lines issue (seems like you missed reading it in your research): https://wiki.gnome.org/Apps/Gedit/FAQ I was searching for bug reports; I hadn't expected an FAQ to exist on the very topic I was interested in. Quite honestly that's a first. FAQs as I tend to encounter them never have anything useful. I'm actually quite impressed. Thanks for the link. gedit is very slow and/or crashes when opening files with very long lines. Can you fix it? When designing GtkTextView (the text display widget of gtk+ which gedit uses) the developers had to make a design decision: trading off bad performance and memory use on corner cases like very long lines Long lines are a corner case? in exchange for better performance in search operations and full support for UTF-8 text. This is a known limitation of GtkTextView and cannot be fixed. On top of that Pango seems to use a lot of CPU drawing such long lines. This may be fixable, but it isn't easy... Feel free to give it a try. This is what I had gleaned from the various bug reports; the issues is known but for some reason it's really hard to fix. Crashes with long lines are usually due to out-of-memory conditions, but if that's not the case then we would like to know about it. So I guess this isn't getting fixed anytime soon. Cheers. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/001801d03ec9$e77c0e40$b6742ac0$@ozemail.com.au
RE: gedit slow with a 1.5Mb text file
Renaud (Ron) OLGIATI said: Possibly non-formatted, with one line per paragraph ? That's what it looks like with line numbers on (very big paragraphs too), but my question is why would this slow gedit down and is there any way around it? It seems to present the content as I would expect. Cheers. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/016e01d03e20$3831fca0$a895f5e0$@ozemail.com.au
gedit slow with a 1.5Mb text file
I grabbed a 1.5MB text file from Windows (converted using dos2unix, not that it appears to make a difference) and tried to open this in gedit and it takes about 45 seconds to open the file. That is a whole lot slower than I was expecting. To make things worse the performance within gedit is very sluggish and searching the text file is not possible; it simply locks up the gedit process (maxes out the CPU). I did some research and attempted to use gvim (no performance issue per se, but it just gives me weird output when trying to navigate the file). I got similar weird output with vi. Search functionality seems to work at least. Navigating the file seems to work as expected in gedit, but the performance stinks. So it's performance and weird output (vi/gvim), or completely slow to the point it's unusable, and expected output (gedit). Neither option works for me. I didn't think that I would ever have fond thoughts of Notepad, but right now... well I digress. I have noted discussions on-line where people are complaining that gedit can't handle text files of the order of 100's of MB, but the file I am dealing with here is 1.5MB. I tested this on two Debian systems (one virtual, one real) and got the same result. I know dealing with text files under Linux is a topic of great discussion (whereas under Windows you never need to think about it), but surely it cannot be this painful to deal with a plain text file? One thing I have noticed under vim is that if I turn on line numbers the document is showing as several large chunks of text on a handful of lines, as opposed to a large number of short lines. Would this be tripping up gedit performance wise perhaps? (And vi/gvim, presentation wise?) Any advice or tips on this, especially from Windows to Linux converts, would be gratefully received. Right now it looks like I have to use two text editors to get what I want (gedit, as painfully slow as it is, to read through the file) and vi/gvim to search it. Cheers. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/016d01d03e1c$793cf9b0$6bb6ed10$@ozemail.com.au
RE: gedit slow with a 1.5Mb text file
Lisi Reisz wrote: Why did a _text_ file need converting? Or do you not mean .txt? Yeah just a regular ASCII text file, but as another reply pointed out new lines are handled slightly differently under Windows vs Unix/Linux. I don't think that is the problem though. Cheers, Wayne. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/017001d03e39$41b78ab0$c526a010$@ozemail.com.au
RE: gedit slow with a 1.5Mb text file
Linux-Fan wrote: In my experience, VIM is slow with long lines (which are automatically wrapped and often look strange if the result is too large to fit on a single page) and syntax highlighting. Using many short lines, VIM has always been good enough for me (even with several MiB file size). I think that's what's happening for me. The line length runs well off the screen. I just didn't expect it. Whenever I need to edit large text files, I chose JEdit (Package `jedit`) which has never been slow even with files above 50 MiB for me. Thanks, I'll take a look at it. Wayne. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/017901d03e3b$ba13d980$2e3b8c80$@ozemail.com.au
RE: gedit slow with a 1.5Mb text file
Wayne Hartell wrote: I grabbed a 1.5MB text file from Windows (converted using dos2unix, not that it appears to make a difference) and tried to open this in gedit and it takes about 45 seconds to open the file. That is a whole lot slower than I was expecting. To make things worse the performance within gedit is very sluggish and searching the text file is not possible; it simply locks up the gedit process (maxes out the CPU). I did some research and attempted to use gvim (no performance issue per se, but it just gives me weird output when trying to navigate the file). I got similar weird output with vi. Search functionality seems to work at least. Navigating the file seems to work as expected in gedit, but the performance stinks. So it's performance and weird output (vi/gvim), or completely slow to the point it's unusable, and expected output (gedit). Neither option works for me. I didn't think that I would ever have fond thoughts of Notepad, but right now... well I digress. I have noted discussions on-line where people are complaining that gedit can't handle text files of the order of 100's of MB, but the file I am dealing with here is 1.5MB. I tested this on two Debian systems (one virtual, one real) and got the same result. I know dealing with text files under Linux is a topic of great discussion (whereas under Windows you never need to think about it), but surely it cannot be this painful to deal with a plain text file? One thing I have noticed under vim is that if I turn on line numbers the document is showing as several large chunks of text on a handful of lines, as opposed to a large number of short lines. Would this be tripping up gedit performance wise perhaps? (And vi/gvim, presentation wise?) Any advice or tips on this, especially from Windows to Linux converts, would be gratefully received. Right now it looks like I have to use two text editors to get what I want (gedit, as painfully slow as it is, to read through the file) and vi/gvim to search it. I found the following link and used the fold command to wrap the long lines in the text file to 80 columns and viola, gedit now runs fast and the searches work. http://www.cyberciti.biz/tips/linux-unix-word-wrap-command.html So I guess gedit really was choking on the very long lines in the source file. Thanks to everyone that responded. Cheers, Wayne. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/019001d03e3f$e430ce90$ac926bb0$@ozemail.com.au
RE: gedit slow with a 1.5Mb text file
Patrick Wiseman wrote: Unix text files end lines with LF, Windows with CRLF. That was the purpose of pre-processing the file with dos2unix. It didn't seem to help. I think the file I have simply does not have many line feeds. Is that abnormal for Linux perhaps? Wayne. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/016f01d03e38$bc62d9f0$35288dd0$@ozemail.com.au
gedit bug with long lines. (was RE: gedit slow with a 1.5Mb text file)
Wayne Hartell wrote: I grabbed a 1.5MB text file from Windows (converted using dos2unix, not that it appears to make a difference) and tried to open this in gedit and it takes about 45 seconds to open the file. That is a whole lot slower than I was expecting. To make things worse the performance within gedit is very sluggish and searching the text file is not possible; it simply locks up the gedit process (maxes out the CPU). In case anyone is interested, I did some further research into this knowing the issue is long lines and it seems that the bug has existed (and been known about) for many years, but still not fixed. The earliest bug record I can find dates back to 2003, so I'm guessing the work around is my best bet for the foreseeable future. :) Either that or address the problem on the source side. Cheers. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/001401d03e9c$6a713a10$3f53ae30$@ozemail.com.au
RE: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
Bob, Trying my best with the trimming; I'll keep observing how other people do it and try to learn from that. It does work in other Linux distros that I have tried. If it works anywhere then it should be possible to learn why and/or why not and to transfer that knowledge. The other distro may have done something unique and special there to make it work. The task is then to figure this out and make it available in Debian. That's what I would have thought. Rhythm Box appears to work just fine. How would Rhythm Box know what your smb username and password would be? Good question. My guess is perhaps since it's part of Gnome it's more integrated and since Gnome must know my credentials when I access the Windows shares initially, it probably has a standard place to store that information. But this is just a guess from a day 3 day old Debian user. I suggest that you post a new message to the mailing list. [snip] Give it a go. Good luck! I was thinking that myself but wasn't sure on the best procedure there either so thanks for filling me in. When I get a chance I'll do just that. Cheers, Wayne. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/008801d02c8f$97d839a0$c788ace0$@ozemail.com.au
RE: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
Sorry, Wayne. I have done it yet again. Clicked reply in the Debian list. I should have pressed l and replied to the list, not you personally. :-( Lisi Hi, Wayne, Welcome to Debian! Good choice! And also welcome to the list. Thank you. So far I am liking what I see. On Friday 09 January 2015 06:07:52 Wayne Hartell wrote: Thanks. I'm sure to violate some conventions here in reply format or what have you. Just let me know if I do and I'll try to remedy in future. You have a basic underlying problem: Your email client does not quote correctly. I had a look. You are running Outlook. All I can say is: bad luck! But your quoting is a bit of a mess and I tried to sort it out for my reply, but it is too early in the morning (I am on GMT and had a late night.). So we all just have to be patient. Most of us have been there, done that and got the T-shirt. There are lots of super Linux email clients out there. Yes, you're right I am using Outlook since I've signed up to this list on a virtual machine that is configured for taking on the road for my work. I haven't yet taken a look at Evolution and others e-mail clients, but I fear that I'll be stuck on Outlook for a little while longer, until I convince myself to make a permanent switch. Hopefully this is a little better in terms of what is expected on the list. I edited a couple of settings to try to improve things. Once you are on a civilised email client, bottom posting, or even better, interleaving, is preferred. With suitable trimming, of course. (Which I am not very good at myself.) I'm sure I'll take a while to look anything but amateur. Now, the problem [snip] is that when I attempt to play an mp3 file using vlc, where that mp3 file is located on a password protected Windows share, vlc fails to play the file. VLC is unable to open the MRL (I have more detailed debug output if needed). Now, I have tried a newer version of VLC from the backports (2.1.2 I think), and it did not help. The work around is to edit the smb://host/path/file.mp3 to be smb://user:password@host/path/file.mp3 When I do this, it will work, but I have to do it for every file I add to the play list. Rhythm Box appears to work just fine. [snip] Anyway, I appreciate you taking the time to respond to my post. This may seem a little trivial, If you use vlc frequently and it does this every time, that is not trivial!! I can't really be any help at all, since I don't use vlc and have no Windows in the house so don't use Samba, but you only had one reply and it didn't feel very welcoming. Agreed; it's not trivial if that's what you are trying to do. Right now listening to music is not high on my agenda; it just jumped out at me as something that should probably work off the bat, especially when there seems to be no other samba related issues. I may end up just logging the issue when I am confident I understand the process and am not just wasting other people's time. Cheers, Wayne. but it's my first serious foray into Linux, just a couple of days old, and rather than run from issues I want to learn not only how to tackle the issues, but the processes that go along with Debian in general. :-)) Lisi Wayne Hartell wrote: I'm a new Debian/Linux user and brand new to this mailing list. Welcome. To that end I have been tinkering with various Linux distros and I have found a reproducible issue in Wheezy ... Please report it as a bug. https://www.debian.org/Bugs/ that I wish to discuss on the Debian user Forums, but I appear to be unable to register. Every IP I try I appears to be black-listed. I even attempted using TOR and those IPs were also black-listed. The problem is I can't post to the forums to tell them I can't register. I can't find anything on Google about this problem. I for one don't like web forums. Fortunately most of the real activity takes place on the mailing lists. You have subscribed to this mailing list and so don't need any of the web forums. Simply discuss the problem here. If there is a better way to report this issue please let me know. Please discuss your problem here. What problem are you having? What reproducible issue have you found in Wheezy? Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501091410.39304.lisi.re...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/005701d02c1f$d4318d90$7c94a8b0$@ozemail.com.au
Unable to join the Debian User Forum; appears that all IPs are being black-listed.
Hi, I'm a new Debian/Linux user and brand new to this mailing list. I'm here primarily because I'm not impressed with the way Windows (particularly the latest technical preview) is heading and am looking for alternatives. To that end I have been tinkering with various Linux distros and I have found a reproducible issue in Wheezy that I wish to discuss on the Debian user Forums, but I appear to be unable to register. Every IP I try I appears to be black-listed. I even attempted using TOR and those IPs were also black-listed. The problem is I can't post to the forums to tell them I can't register. I can't find anything on Google about this problem. It appears as if the black-list check conducted by the forums is now returning positive for all IPs being requested, which means no one can sign up, if I interpret this correctly. http://www.ahbl.org/content/last-notice-wildcarding-services-jan-1st Last Notice: Wildcarding of Services Jan 1st As promised in April, on Jan 1st, 2015, i'll be wildcarding all zones no longer in operation - this includes rhsbl.ahbl.org, dnsbl.ahbl.org, and ircbl.ahbl.org. This means that these services will return positive responses for any queries. If you are still using these services, this may cause you to incorrectly tag e-mail as spam, or create other unintended consequences. Fix and maintain your servers, now. Do not contact us about 'removing' your domain or IP address from our lists, as there is nothing we can do for you. So it would seem that whoever administers these forums needs to know about it, but I cannot find an appropriate place to report this issue (other than the forums themselves which I cannot access). If there is a better way to report this issue please let me know. Regards, Wayne.
RE: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
Hi Bob, Thanks. I'm sure to violate some conventions here in reply format or what have you. Just let me know if I do and I'll try to remedy in future. With respect to reporting the issue as a bug I started down that path using Reportbug, but noticed that a similar issue (not quite the same, or maybe I just didn't understand it fully), so I wanted to discuss it first. Thanks for providing that opportunity. First the issue is quite minor and I am able to work around it, but it's one of those things for a user like myself, coming from Windows, that pops up and feels like it should work, but doesn't. It does work in other Linux distros that I have tried. The issue is specifically with VLC Media Player (vlc package) and attempting to play an mp3 file via network (I believe smb) share. I'm running stable, so the version of vlc is: 2.0.3 (or, under synaptic, 2.0.3-5+deb7u1). Now, the problem, and this is reproducible from a physical laptop that I installed and also a virtual machine (both running 64-bit Wheezy), is that when I attempt to play an mp3 file using vlc, where that mp3 file is located on a password protected Windows share, vlc fails to play the file. VLC is unable to open the MRL (I have more detailed debug output if needed). Now, I have tried a newer version of VLC from the backports (2.1.2 I think), and it did not help. The work around is to edit the smb://host/path/file.mp3 to be smb://user:password@host/path/file.mp3 When I do this, it will work, but I have to do it for every file I add to the play list. Rhythm Box appears to work just fine. I'm not overly concerned about the issue which is why I wanted to discuss it before I submitted any official bug (that would obviously be low priority). I noticed Debian bug #602985 appears quite similar (it's about getting VLC to prompt for smb credentials), but I'm not sure if it's exactly the same. Anyway, I appreciate you taking the time to respond to my post. This may seem a little trivial, but it's my first serious foray into Linux, just a couple of days old, and rather than run from issues I want to learn not only how to tackle the issues, but the processes that go along with Debian in general. Thanks, Wayne. Wayne Hartell wrote: I'm a new Debian/Linux user and brand new to this mailing list. Welcome. To that end I have been tinkering with various Linux distros and I have found a reproducible issue in Wheezy ... Please report it as a bug. https://www.debian.org/Bugs/ that I wish to discuss on the Debian user Forums, but I appear to be unable to register. Every IP I try I appears to be black-listed. I even attempted using TOR and those IPs were also black-listed. The problem is I can't post to the forums to tell them I can't register. I can't find anything on Google about this problem. I for one don't like web forums. Fortunately most of the real activity takes place on the mailing lists. You have subscribed to this mailing list and so don't need any of the web forums. Simply discuss the problem here. If there is a better way to report this issue please let me know. Please discuss your problem here. What problem are you having? What reproducible issue have you found in Wheezy? Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/004901d02bd2$9acd59a0$d0680ce0$@ozemail.com.au
