Someone have some suggest for this my issue?
It's only a my problem or this happened to all (is sufficient click on
jnlp link)?
NOTE: if I use a old version of Fedora (22) the problem not happened
and the java app is opened immediately
ThanksDario
Il giorno ven, 26/04/2019 alle 21.55 +0200, Dario L
On 4/25/19 1:31 AM, Ed Greshko wrote:
Everything you've said indicates the annoying issues are related to the
"Approach"
application.
Of course. I can't do anything about Approach, but I can do
somnething about CUPS-PDF.
___
users mailing list --
On 4/25/19 7:10 AM, Tim via users wrote:
I haven't touched Lotus since Win98 went out of fashion, so I can't
recall what menu options you have (nor find any on-line examples). But
have you gone through the menus and looked for a portrait/landscape
page setting that is*not* part of the printing
On 4/30/19 4:57 PM, ToddAndMargo via users wrote:
> On 4/25/19 1:31 AM, Ed Greshko wrote:
>> Everything you've said indicates the annoying issues are related to the
>> "Approach"
>> application.
>
> Of course. I can't do anything about Approach, but I can do
> somnething about CUPS-PDF.
>
Try o
On 4/30/19 2:22 AM, Ed Greshko wrote:
On 4/30/19 4:57 PM, ToddAndMargo via users wrote:
On 4/25/19 1:31 AM, Ed Greshko wrote:
Everything you've said indicates the annoying issues are related to the
"Approach"
application.
Of course. I can't do anything about Approach, but I can do
somnethi
On 4/30/19 6:48 PM, ToddAndMargo via users wrote:
> On 4/30/19 2:22 AM, Ed Greshko wrote:
>> On 4/30/19 4:57 PM, ToddAndMargo via users wrote:
>>> On 4/25/19 1:31 AM, Ed Greshko wrote:
Everything you've said indicates the annoying issues are related to the
"Approach"
application.
>>
On 4/30/19 4:56 AM, Ed Greshko wrote:
On 4/30/19 6:48 PM, ToddAndMargo via users wrote:
On 4/30/19 2:22 AM, Ed Greshko wrote:
On 4/30/19 4:57 PM, ToddAndMargo via users wrote:
On 4/25/19 1:31 AM, Ed Greshko wrote:
Everything you've said indicates the annoying issues are related to the
"Appro
On Tue, 2019-04-30 at 10:07 +0200, Dario Lesca wrote:
> Someone have some suggest for this my issue?
> It's only a my problem or this happened to all (is sufficient click
> on jnlp link)?
> NOTE: if I use a old version of Fedora (22) the problem not happened
> and the java app is opened immediately
On 29.04.19 17:51, Patrick O'Callaghan wrote:
> On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
>> I just attempted update f29->f30 using
>> sudo dnf system-upgrade download --refresh --releasever=30
>
> F30 has not been released yet. This should be reported on the Fedora
> Test list, not h
Now that the release announcement has been done, I can say that
upgrading for me (on a VM) also failed. After the final reboot, I just
got a grub prompt.
On 30/04/2019 17.34, Ulf Volmer wrote:
> On 29.04.19 17:51, Patrick O'Callaghan wrote:
>> On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
On 29.04.19 15:43, Neal Becker wrote:
> I just attempted update f29->f30 using
> sudo dnf system-upgrade download --refresh --releasever=30
>
> After reboot
> sudo dnf system-upgrade reboot
>
> The system got to
> running transaction
>
> But then seemed to hang. I waited about 15 minutes. T
On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
> On 29.04.19 17:51, Patrick O'Callaghan wrote:
> > On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
> > > I just attempted update f29->f30 using
> > > sudo dnf system-upgrade download --refresh --releasever=30
> >
> > F30 has not been rel
On 30.04.19 17:53, Sjoerd Mullender wrote:
> Now that the release announcement has been done, I can say that
> upgrading for me (on a VM) also failed. After the final reboot, I just
> got a grub prompt.
No issues here. Two physical systems running f30 now, both using UEFI.
Which hypervisor are y
On 30.04.19 18:40, Patrick O'Callaghan wrote:
> On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
>> https://fedoramagazine.org/announcing-fedora-30/
>
> That announcement is dated today. My reply was yesterday.
My apologies.
Best regards
Ulf
___
u
On 4/30/19 6:40 PM, Patrick O'Callaghan wrote:
On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
On 29.04.19 17:51, Patrick O'Callaghan wrote:
On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
I just attempted update f29->f30 using
sudo dnf system-upgrade download --refresh --releasever
On 4/30/19 5:53 PM, Sjoerd Mullender wrote:
Now that the release announcement has been done, I can say that
upgrading for me (on a VM) also failed. After the final reboot, I just
got a grub prompt.
So far, the upgrade went fine on 2 out of 3 systems. On the 3rd system,
I am also stuck with a
Per the subject line, I see that there is this announcement
(https://fedoramagazine.org/announcing-fedora-30/), but after
starting the upgrade and downloading the packages, the upgrade made no
progress.
Usually, the announcement of a new release is made with an email blast,
which as yet, I
On 30/04/2019 18:39, Max Pyziur wrote:
>
> Per the subject line, I see that there is this announcement
> (https://fedoramagazine.org/announcing-fedora-30/), but after starting
> the upgrade and downloading the packages, the upgrade made no progress.
>
> Usually, the announcement of a new release is
On Tue, 2019-04-30 at 18:50 +0200, Ralf Corsepius wrote:
> On 4/30/19 6:40 PM, Patrick O'Callaghan wrote:
> > On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
> > > On 29.04.19 17:51, Patrick O'Callaghan wrote:
> > > > On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
> > > > > I just attem
https://fedoramagazine.org/announcing-fedora-30/
'...to assist Linux admins in the configuration of common GNU/Linux
subsystems.'
Is this the first the first time Red Hat has officially refered to the
opperating system it's running in this way? If so, it must have been 15 years
coming! That s
On 30/04/2019 18.48, Ulf Volmer wrote:
> On 30.04.19 17:53, Sjoerd Mullender wrote:
>> Now that the release announcement has been done, I can say that
>> upgrading for me (on a VM) also failed. After the final reboot, I just
>> got a grub prompt.
>
> No issues here. Two physical systems running f
anyone ?!
;-)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/M
On 30.04.19 21:14, Sjoerd Mullender wrote:
> On 30/04/2019 18.48, Ulf Volmer wrote:
>> Which hypervisor are you using? Is your disk visible in the grub shell?
> Earlier I had accidentally replied directly instead of to the list.
>
> To answer the question publicly, I'm using KVM. The guest is an
Hi all,
Despite what I said in another thread I decided to go ahead with the
upgrade to Fedora 30 (from 29) on three VMs running under VMWare. Two
went without problems, but the one running my webserver (with sites
secured by LetsEncrypt) gives the following errors -
Error:
Problem 1: package
On 30.04.19 22:09, Danny Horne via users wrote:
> Problem 1: package python2-acme-0.31.0-1.fc29.noarch requires
> python2-josepy, but none of the providers can be installed
> - python2-josepy-1.1.0-6.fc29.noarch does not belong to a distupgrade
> repository
> - problem with installed package
On 30/04/2019 21:49, Ulf Volmer wrote:
> Certbot on fedora 29 and also on 30 is based on python3 instead of
> python2. So I'm surpriced about your issues. I think you can safely
> remove the packages. Or add --allowerasing to the 'dnf system-upgrade
> download' command.
>
> Best regards
> Ulf
> ___
Just a heads up that this can be an issue, but I'm not sure how common
it is. It applies to BIOS (not UEFI) firmware, and for systems that
originally had Fedora 20 or older installed and also never had
'grub2-install' issued since then. Therefore it can be prevented just
by running 'grub2-install'
On Tue, Apr 30, 2019 at 9:53 AM Sjoerd Mullender wrote:
>
> Now that the release announcement has been done, I can say that
> upgrading for me (on a VM) also failed. After the final reboot, I just
> got a grub prompt.
It could be this:
https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_men
On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> Just a heads up that this can be an issue, but I'm not sure how common
> it is. It applies to BIOS (not UEFI) firmware, and for systems that
> originally had Fedora 20 or older installed and also never had
> 'grub2-install' issued since then.
Hi Everyone,
I recently upgraded to Freeradius 3.0.19-1 and I noticed after I
restarted the service I was getting the following errors:
Apr 29 22:01:29 freeradius systemd[1]: Starting FreeRADIUS high performance
RADIUS server
Apr 29 22:01:30 freeradius sh[1970]: make: *** No rule to make
Is there a workaround for the issue where the Fedora 30 upgrade decides
that all of Eclipse is not compatible with Fedora 30 and removes the
complete collection of Eclipse packages?
If it's best to wait until the issue is resolved before upgrading,
will GNOME Software automatically update my dow
On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
wrote:
>
> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> > Just a heads up that this can be an issue, but I'm not sure how common
> > it is. It applies to BIOS (not UEFI) firmware, and for systems that
> > originally had Fedora 20 or o
Chris Murphy wrote:
> On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> wrote:
>>
>> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
>>> Just a heads up that this can be an issue, but I'm not sure how common
>>> it is. It applies to BIOS (not UEFI) firmware, and for systems that
>>> ori
Chris Murphy writes:
On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
wrote:
>
> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> > Just a heads up that this can be an issue, but I'm not sure how common
> > it is. It applies to BIOS (not UEFI) firmware, and for systems that
> > origi
Make sure you turn off any Gnome extensions that you have downloaded
from gnome.org. There is an issue where some gnome extensions that are
loaded from the user account will cause gnome-shell to crash. What you
will see is you try to log in and after a few seconds it returns back
to the login scree
Chris Murphy writes:
On Tue, Apr 30, 2019 at 9:53 AM Sjoerd Mullender wrote:
>
> Now that the release announcement has been done, I can say that
> upgrading for me (on a VM) also failed. After the final reboot, I just
> got a grub prompt.
It could be this:
https://fedoraproject.org/wiki/Commo
On Tue, 30 Apr 2019, Danny Horne via users wrote:
On 30/04/2019 18:39, Max Pyziur wrote:
Per the subject line, I see that there is this announcement
(https://fedoramagazine.org/announcing-fedora-30/), but after starting
the upgrade and downloading the packages, the upgrade made no progress.
Hi All,
If you are upgrade from 29 to 30, make sure you
update dnf and libdnf first do to a bug that has
been fixed (my procedure below takes care of this).
So far I have one virtual machine running FC30. Haven't
got a chance to torture it yet though.
This is my update procedure:
FC 29 -->>
On 4/30/19 8:25 PM, Patrick O'Callaghan wrote:
On Tue, 2019-04-30 at 18:50 +0200, Ralf Corsepius wrote:
On 4/30/19 6:40 PM, Patrick O'Callaghan wrote:
On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
On 29.04.19 17:51, Patrick O'Callaghan wrote:
On Mon, 2019-04-29 at 09:43 -0400, Neal Bec
On Tue, Apr 30, 2019 at 8:12 PM Sam Varshavchik wrote:
>
> Chris Murphy writes:
>
> > On Tue, Apr 30, 2019 at 9:53 AM Sjoerd Mullender wrote:
> > >
> > > Now that the release announcement has been done, I can say that
> > > upgrading for me (on a VM) also failed. After the final reboot, I just
>
On Tue, Apr 30, 2019 at 7:21 PM Todd Zullinger wrote:
>
> Chris Murphy wrote:
> > On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> > wrote:
> >>
> >> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> >>> Just a heads up that this can be an issue, but I'm not sure how common
> >>> it i
Hi,
I recently recovered my home partition from some corruption. Most of everything
is working OK but my spamprobe database appears not to be
I use spam probe in a procmail recipe, from their examples in the man page:
:0
SCORE=| /bin/spamprobe train
:0 wf
| formail -I "X-SpamProbe:
42 matches
Mail list logo