25 Aug
2021
25 Aug
'21
11:14 a.m.
I'm using Debian 11 Bullseye, I followed the instructions at
(https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Inst…) and
added the repos to my sources.list file then I imported the GPG key, but running sudo
apt-get update gives me error 404 as seen below.
Ign:5 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x bullseye InRelease
Ign:6 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x bullseye
InRelease
Err:7 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x bullseye Release
404 Not Found [IP: 37.205.10.16 80]
Err:8 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x bullseye
Release
404 Not Found [IP: 37.205.10.16 80]
Reading package lists... Done
I suspect this is from your server's side, could you please fix that?
25 Aug
25 Aug
11:24 a.m.
Anno domini 13:14:23 Wed, 25 Aug 2021 +0200 (CEST)
jakolineplayer--- via tde-users scripsit:
I'm using Debian 11 Bullseye, I followed the
instructions at
(https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Inst…) and
added the repos to my sources.list file then I imported the GPG key, but running sudo
apt-get update gives me error 404 as seen below.
Ign:5 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x bullseye
InRelease
Ign:6 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x bullseye
InRelease
Err:7 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x bullseye Release
404 Not Found [IP: 37.205.10.16 80]
Err:8 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x bullseye
Release
404 Not Found [IP: 37.205.10.16 80]
Reading package lists... Done
I suspect this is from your server's side, could you please fix that?
37.205.10.16 works from here. I'd suggest, you try again .. or a bit later.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
11:43 a.m.
Replacing bullseye with buster in the repo line makes it work fine, I've been stuck in
this since morning
404 Not Found [IP: 37.205.10.16 80]
12:38 p.m.
On 2021/08/25 8:43:00 PM, jakolineplayer--- via tde-users wrote:
Replacing bullseye with buster in the repo line makes
it work fine, I've been stuck in this since morning
404 Not Found [IP: 37.205.10.16 80]
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
37.205.10.16 working fine from here too....
Cheers
Michele
8:54 p.m.
On Wed August 25 2021 04:14:23 jakolineplayer--- via tde-users wrote:
I'm using Debian 11 Bullseye, I followed the
instructions at
(https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Ins
tructions) and added the repos to my sources.list file then I imported the
GPG key, but running sudo apt-get update gives me error 404 as seen below.
<snip>
Hi Jakolineplayer,
Sorry. TDE Stable has not yet been released for Bullseye. It is due
with the next TDE release about the end of October.
Preliminary Stable Build is available for Bullseye and I have briefly
tested it. However PSB updates frequently so personally I prefer not
to install it on Debian Stable but a lot of people do.
If you want to try PSB IIRC you would have to use this in your
/etc/apt/sources.list:
deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb bullseye
deps-r14 main-r14
deb-src http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb bullseye
deps-r14 main-r14
TTBOMK these are the Debian and derivative releases currently supported
by TDE Stable:
artful buster focal lucid raspbian-stretch trusty zesty
ascii cosmic groovy precise raspbian-wheezy wheezy
beowulf disco hirsute raspbian-buster squeeze xenial
bionic eoan jessie raspbian-jessie stretch yakkety
And by TDE PSB:
ascii bullseye focal jessie sid wheezy
beowulf buster groovy raspbian-bullseye stretch xenial
bionic ceres hirsute raspbian-buster trusty
bookworm chimaera impish raspbian-stretch unstable
--Mike
26 Aug
26 Aug
7:35 a.m.
Mike, adding the PSB repo you suggested in your msg resulted a failure in reloading the
list
$ sudo apt-get update
E: Malformed entry 16 in list file /etc/apt/sources.list (Component)
E: The list of sources could not be read.
Any help? Is going back to Debian 10 really the only way for me to use Trinity (for now)?
Also one more thing, what does PSB stand for exactly? Is it like a developmental branch?
7:46 a.m.
On Thu August 26 2021 00:35:24 jakolineplayer--- via tde-users wrote:
Mike, adding the PSB repo you suggested in your msg
resulted a failure in
reloading the list
$ sudo apt-get update
E: Malformed entry 16 in list file /etc/apt/sources.list (Component)
E: The list of sources could not be read.
Any help? Is going back to Debian 10 really the only way for me to use
Trinity (for now)? Also one more thing, what does PSB stand for exactly? Is
it like a developmental branch?
My email wrapped the lines - the deps14 and main14 should be on the same
lines as the preceding stuff.
If that doesn't work please post your complete sources.list as an attachment
and I'll check it.
PSB is Preliminary Stable Build. It's more stable than the testing branch but
still receives updates just about daily. I have used the PSB branch but not
the testing branch. I think that's mostly for devels.
--Mike
8:02 a.m.
On 2021/08/26 4:46:07 PM, Mike Bird wrote:
PSB is Preliminary Stable Build. It's more stable
than the testing branch but
still receives updates just about daily. I have used the PSB branch but not
the testing branch. I think that's mostly for devels.
PSB is the running version of R14.0.x, basically the on going version between one stable
release and the next one.
PTB is the running version of R14.1.x, basically the on going version of what will be the
next minor release, sooner or
later.
They are both equally stable, I would say.
The installation instructions are at these pages, just need to follow them accordingly and
there shouldn't be any issue.
https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Inst…
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
https://wiki.trinitydesktop.org/Preliminary_Testing_Builds
Cheers
Michele
8:55 a.m.
Thanks for your help everyone, Trinity is now installed and it's working fine.
My issue right now is that I'm unable to mount my NTFS partition through Konqueror
file manager, or Caja file manager, or really any file manager. I get the following
error:
Unable to mount this device.
Potential reasons include:
Improper device and/or user privilege level
Corrupt data on storage device
Technical details:
org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
Any help?
4:13 p.m.
On Thu, 26 Aug 2021 10:55:58 +0200 (CEST)
jakolineplayer--- via tde-users <users(a)trinitydesktop.org> wrote:
Thanks for your help everyone, Trinity is now
installed and it's working fine.
My issue right now is that I'm unable to mount my NTFS partition through Konqueror
file manager, or Caja file manager, or really any file manager. I get the following
error:
Unable to mount this device.
Potential reasons include:
Improper device and/or user privilege level
Corrupt data on storage device
Technical details:
org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform
operation
Any help?
Can you mount it directly from the commandline as root? "mount /dev/[whatever]
[mountpoint]"?
The reason I ask is that NTFS is not well-supported by the Linux kernel and you may have
to install additional packages to get non-kernel support working.
If you can mount it from the command line, your problem is with security mechanisms in
udisks and/or dbus, as the error message suggests.
E. Liddell
6:41 p.m.
Thanks, I was able to automount my ntfs partition using ntfs-3g and the /etc/fstab method
27 Aug
27 Aug
12:08 p.m.
On Thursday 26 of August 2021 10:55:58 jakolineplayer--- via tde-users
wrote:
Thanks for your help everyone, Trinity is now
installed and it's working
fine.
My issue right now is that I'm unable to mount my NTFS partition through
Konqueror file manager, or Caja file manager, or really any file
manager. I get the following error:
Unable to mount this device.
Potential reasons include:
Improper device and/or user privilege level
Corrupt data on storage device
Technical details:
org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to
perform operation
Any help?
I also encountered this problem on my test machine. Udisks2 seems to
require policykit agent, which is not yet available in TDE. This is one of
the things we want to solve before releasing TDE R14.0.11.
Cheers
--
Slávek
1213
days inactive
1215
days old
11 comments
6 participants
participants (6)
-
Dr. Nikolaus Klepp -
E. Liddell -
jakolineplayer＠tutanota.com -
Michele Calgaro -
Mike Bird -
Slávek Banko