evolution 3.36 bug

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

evolution 3.36 bug

Orrin McGill

Hi,

I have three systems:

A Linux Mint 19.3 64 bit with evolution 3.28.5

A Linux Mint 19.3 64 bit with evolution 3.28.5

A Linux Mint 19.3 64 bit with evolution 3.36

 

The EVO 3.28 systems recognize my Network printer, the 3.36 unit do not. (BUG)

 

Orrin

 

 


_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Andre Klapper
On Sat, 2020-05-30 at 08:24 -0500, [hidden email] wrote:
> I have three systems:
> A Linux Mint 19.3 64 bit with evolution 3.28.5
> A Linux Mint 19.3 64 bit with evolution 3.28.5
> A Linux Mint 19.3 64 bit with evolution 3.36
>
> The EVO 3.28 systems recognize my Network printer, the 3.36 unit do
> not. (BUG)

Feel free to report a bug with sufficient info in the issue tracker of
Linux Mint. Evolution itself has no "printer recognition" code.

andre
--
Andre Klapper  |  [hidden email]
https://blogs.gnome.org/aklapper/


_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Pete Biggs
In reply to this post by Orrin McGill
On Sat, 2020-05-30 at 08:24 -0500, [hidden email] wrote:
> Hi,
> I have three systems:
> A Linux Mint 19.3 64 bit with evolution 3.28.5
> A Linux Mint 19.3 64 bit with evolution 3.28.5
> A Linux Mint 19.3 64 bit with evolution 3.36
>  
> The EVO 3.28 systems recognize my Network printer, the 3.36 unit do not. (BUG)
>  

Evolution does not have any printer code in it (other than for
formatting) it uses the printers that the system tells it are
available.

From your other post it looks like the 3.36 version you are using is a
Flatpack one.  Flatpack programs run in a sandbox which is a very
different environment to a native version.  Are you sure the printers
are available in the flatpack sandbox?

Evolution 3.36 deals with printers quite happily (NOT A BUG)

P.


_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Orrin McGill
Finally some substance, now how do I get a flatpack sandbox to
recognise the printers available on the system.

Note to self: do not use flatpack versions.


On Sat, 2020-05-30 at 15:45 +0100, Pete Biggs wrote:

> On Sat, 2020-05-30 at 08:24 -0500, [hidden email] wrote:
> > Hi,
> > I have three systems:
> > A Linux Mint 19.3 64 bit with evolution 3.28.5
> > A Linux Mint 19.3 64 bit with evolution 3.28.5
> > A Linux Mint 19.3 64 bit with evolution 3.36
> >  
> > The EVO 3.28 systems recognize my Network printer, the 3.36 unit do
> > not. (BUG)
> >  
>
> Evolution does not have any printer code in it (other than for
> formatting) it uses the printers that the system tells it are
> available.
>
> From your other post it looks like the 3.36 version you are using is
> a
> Flatpack one.  Flatpack programs run in a sandbox which is a very
> different environment to a native version.  Are you sure the printers
> are available in the flatpack sandbox?
>
> Evolution 3.36 deals with printers quite happily (NOT A BUG)
>
> P.
>
>
> _______________________________________________
> evolution-list mailing list
> [hidden email]
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Pete Biggs
On Sat, 2020-05-30 at 10:07 -0500, Orrin McGill wrote:

Please don't top post on this mailing list.

> Finally some substance,

I can only apologize on behalf of everyone here for not immediately
providing you with a comprehensive answer.

>  now how do I get a flatpack sandbox to
> recognise the printers available on the system.

I don't know (and indeed don't like) flatpack, but it probably depends
on the default permissions of flatpack, your desktop and numerous other
things.

You need to take it up with your distro.

>
> Note to self: do not use flatpack versions.
>
They can be useful - especially when a distro doesn't provide the most
recent version or for testing things. But if you are going to use a
flatpack version of something then you need to be aware of the
constraints associated with it. Evolution is a very complex
application, not everything fits within the constraints of a sandbox
packaging system.

P.


_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Gnome Evolution - General mailing list
In reply to this post by Orrin McGill
On Sat, 2020-05-30 at 10:07 -0500, Orrin McGill wrote:
> Finally some substance, now how do I get a flatpack sandbox to
> recognise the printers available on the system.
>
> Note to self: do not use flatpack versions.

Snaps and Flatpacks could run in a development mode, fore example:

"D-Bus access

Access to the entire bus with --socket=system-bus or --socket=session-
bus should be avoided, unless the application is a development tool." -
https://docs.flatpak.org/en/latest/sandbox-permissions.html

And as always for all those Linux unique crap, the obligatory blame
other for our unfinished moronism:

"you should file individual bugs for each application on their Flathub
pages, as the way they enumerate and access printers is likely different
for each one of them, and the problem wouldn't be a generic Flatpak or
portal problem." -
https://github.com/flatpak/xdg-desktop-portal/issues/341

You unlikely will find such unfinshed container approaches on other
UNIXoid platforms, such as FreeBSD.

While I'm in favour of Linux, I anyway cast an eye on UNIXoid platforms
that still stay to a standard. You will not find pulseaudio, a flatpack
or a snap thingy etc. on any of my Linux installs. While I'm willing to
use something that is far away from UNIX alike philosophy, such as
systemd, I'm not willing to use crap such as pulseaudio, since upstream
does blame ALSA drivers that work when using ALSA, if they don't work
when using pulseaudio.

There's no advantage when using containers such as sanps or flatpacks,
when it is rocket since to get an app working without issues or to
switch to a development mode to get them working.

Note! Linux has got no standard.
De facto https://en.wikipedia.org/wiki/Linux_Standard_Base isn't a
standard.

Avoid to divate more from common sense, than absolutely needed. We are
more or less forced to use systemd, but we don't need to use something
like a flatpack. If you run in unresolvable soname issues when trying to
build latest software from upstream, migrate to a rolling release
distro. I'm using Arch Linux. It does follow upstream and at worst I
sometimes need to maintain a few outdated libraries on my own, to
install them parallel to the latest and greatest libraries provided by
the rolling release's repositories.





_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Gnome Evolution - General mailing list
PS:

All those container approaches with the need to set a "disable sandbox
security completely" flag to get things working, remind me of the virus
scanner paradox http://blog.fefe.de/?ts=b6cea88d .

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Andre Klapper
On Sat, 2020-05-30 at 19:48 +0200, Ralf Mardorf wrote:
> PS:
>
> All those container approaches with the need to set a "disable sandbox
> security completely" flag to get things working, remind me of the virus
> scanner paradox http://blog.fefe.de/?ts=b6cea88d .

Such "PS" are quite unhelpful when linking to an article which is in
German language only. Please refrain from doing that. Thanks.

andre
--
Andre Klapper  |  [hidden email]
https://blogs.gnome.org/aklapper/


_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution 3.36 bug

Ángel González
In reply to this post by Orrin McGill
On 2020-05-30 at 10:07 -0500, Orrin McGill wrote:
> Finally some substance, now how do I get a flatpack sandbox to
> recognise the printers available on the system.
>
> Note to self: do not use flatpack versions.

Supposedly there is an interface that would allow printing from the
sandbox:
https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.Print


Alternatively, you could probably allow network access to cupsd, and
have the system inside the flatpack sandbox access that "network
printer".


I have no experience with flatpack, so I'm afraid I cannot give you more
detailed advice.

Cheers

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list