Re: Call for Testers - Wine 4.10 update

2019-06-15 Thread ToddAndMargo via users

On 6/15/19 9:43 PM, Michael Cronenworth wrote:

On 6/15/19 7:23 PM, ToddAndMargo via users wrote:
Wine Staging or regular Wine? 


Fedora packages wine-staging.


Good.  My experience is that Wine Staging is that
it is a better product and the developers are a zillion
times more responsive to bugs

Can 4.10 be run parallel to the old one?
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: Call for Testers - Wine 4.10 update

2019-06-15 Thread Michael Cronenworth

On 6/15/19 7:23 PM, ToddAndMargo via users wrote:
Wine Staging or regular Wine? 


Fedora packages wine-staging.
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: Call for Testers - Wine 4.10 update

2019-06-15 Thread ToddAndMargo via users

Wine Staging or regular Wine?
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


xRDP login, then a blank green screen

2019-06-15 Thread ToddAndMargo via users

Hi All,

I just upgraded two Fedora 28 servers to Fedora 30.  Both
have/had xRDP running on them.

After the upgrade, one works perfectly.

The other one, after you enter Xorg, username, password,
it switches to a big green screen, then eventually times out with:

connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to session manager, please wait...
login successful for display 10
started connecting
connection problem, giving up
some problem

For the life of me, I can't figure out what is different between the two 
servers.  I reused the good one's xrdp.ini and Xwrapper.config.  The

hardware is identical, except that the drive in tne working one
are mechanical and the problem one are SSD.  Same version of Xorg and
xrdp (both are the latest).

xorg-x11-server-Xorg-1.20.4-3.fc30.x86_64
xrdp-0.9.10-1.fc30.x86_64

Any words of wisdom?

Many thanks,
-T

xrdp.ini

[Globals]

ini_version=1
fork=true
port=3389
tcp_nodelay=true
tcp_keepalive=true
security_layer=negotiate
certificate=
key_file=

autorun=Xorg

allow_channels=true
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
max_bpp=32
new_cursors=true
use_fastpath=both
blue=009cb5
grey=dedede

ls_top_window_bg_color=009cb5
ls_width=350
ls_height=430
ls_bg_color=dedede
ls_logo_filename=
ls_logo_x_pos=55
ls_logo_y_pos=50
ls_label_x_pos=30
ls_label_width=60
ls_input_x_pos=110
ls_input_width=210
ls_input_y_pos=220
ls_btn_ok_x_pos=142
ls_btn_ok_y_pos=370
ls_btn_ok_width=85
ls_btn_ok_height=30
ls_btn_cancel_x_pos=237
ls_btn_cancel_y_pos=370
ls_btn_cancel_width=85
ls_btn_cancel_height=30

[Logging]
LogFile=xrdp.log
LogLevel=DEBUG
EnableSyslog=true
SyslogLevel=DEBUG

[Channels]
rdpdr=true
rdpsnd=true
drdynvc=true
cliprdr=true
rail=true
xrdpvr=true
tcutils=true

[Xorg]
name=Xorg
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
code=20
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


[389-users] Re: What Do I Need?

2019-06-15 Thread Eugene Poole
Since the most are laptops and tablets I'll power them down when not in 
use (all of my Linux machines remain powered up all the time) I'll leave 
them out of the equation for now until I read up on Samba.


TIA

Gene


On 6/13/2019 3:32 AM, William Brown wrote:



On 12 Jun 2019, at 19:43, Eugene Poole  wrote:

All of my Windows machines are workstations (2 WIN 7 laptops; 1 WIN 7 desktop; 
1 WIN 10 tablet).  I have 1 ArcaOS (OS/2) desktop. The remainder of my machines 
(40+) are CentOS Linux 7 and 6.

My 'main' machine is CentOS 7 and it runs Oracle 12c database; PostgreSQL 9.6 
database; master DNS; Apache Web Server; 6 KVM virtual machines.

I am much more 'comfortable' on Linux than I am on Windows.

The problem you will run into very quickly is that windows has no integration 
for sharing users/groups with LDAP. Windows will only interact with active 
directory, which is quite a different experience - but your linux clients can 
consume AD as generic LDAP clients.

There are some choices here like Samba AD for certain, but 389 may not do what 
you want in this case I'm sorry :(


Gene

On 6/12/2019 3:23 AM, William Brown wrote:

On 12 Jun 2019, at 04:25, Eugene Poole  wrote:

I need to control users and groups of users to provide them access to specific 
machines.  Once our machine number went above 15 controlling who has access to 
what machines has become difficult.

So you mention that you have some windows machines here too, is that correct? 
Are the machines workstations or servers? You have some linux machines too?


Gene

On 6/10/2019 4:11 AM, William Brown wrote:

On 7 Jun 2019, at 23:53, Eugene Poole  wrote:

I'm trying to upgrade my environment and I've reinstalled my CentOS machines to 
CentOS 7 except for one.  I've got my DNS for my LAN working just fine.  So now 
it's time for Directory Server.

What is a GOOD tutorial to follow? My environment includes 26 physical and KVM 
virtual machines; 4 Windows 7 machines and 1 ArcaOS (OS/2) machine. What is a 
DS configuration to go for?

I think the better thing to ask is what do you want to achieve here? What's your ideal 
setup for integrating each of these clients, and what information do you want to make 
available to them? I think that would help me to advise on "what next" for you 
:)




TIA

--
Eugene Poole
Woodstock, Georgia
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

--
Eugene Poole
Woodstock, Georgia
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

--
Eugene Poole
Woodstock, Georgia
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List 

Re: please... help me about grubby!

2019-06-15 Thread Samuel Sieb

On 6/15/19 2:23 PM, François Patte wrote:

Everything was ok untill grubby replaced grub2-mkconfig: when there is a
kernel update, grubby uses  the disabled sda3-sda4 partitions as the /
parttion in the /boot/grub2/grub.cfg file.


grubby has never replaced grub2-mkconfig.  They are independent. 
grub2-mkconfig is never run, except maybe on the initial install. 
Upgrades up to F30 have always used grubby.



I have now destroyed these partitions but grubby still uses them and
writes a faulty /boot/grub2/grub.cfg file.

Where does it find that these partitions still exist?


grubby only copies the information from the previous kernel in the 
grub.cfg file.



I can't upgrade my system now because I fear that the boot config file
will refer to a partition wich no longer exists on my system.


You don't mention which Fedora version you are using.  Starting with 
F30, grub uses BLS by default and grubby is no longer used.  A 
system-upgrade will convert the installed system to use BLS.  I don't 
know if it converts the existing grub.cfg or if it creates all new entries.

___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: rpmbuild

2019-06-15 Thread Samuel Sieb

On 6/15/19 1:10 PM, Patrick Dupre wrote:

Another question
How could I get
%{_bindir}/*
added in the %files section
without having to edit the generated .spec file (i.e. when I run cpanspec)?


You would have to modify cpanspec to substitute that.
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


please... help me about grubby!

2019-06-15 Thread François Patte
Bonjour,

I sent several messages about kernel updates and grubby.

Once upon a time I made 4 partitions on a ssd drive where the system is
installed. I use raid1+lvm

on sda1 and sdb1 I put the a /boot partition (raid1) for a debian install
on sda3 and sdb3 I also put /boot partition (raid1) for a fedora install

on sda2 and sdb2 I put a / partition (raid1+lvm) with label
"debian-racine" (at that time I had a debian install)
on sda4 and sdb4 I put a / partition (raid1+lvm) with label
"fedora-racine" for a fedora install.

So I had two linux installs: one was debian the other was fedora.

I abandonned debian and used the debian partition to install a fedora
version.  I wanted to keep two different partitions: on one partition
fedora-n on the other fedora-(n+1).

Then appears the "dnf system upgrade" and I disabled the my sda3-sda4
partitions and only used sda1-sda2 partitions (with label
"debian-racine") for my system.

Everything was ok untill grubby replaced grub2-mkconfig: when there is a
kernel update, grubby uses  the disabled sda3-sda4 partitions as the /
parttion in the /boot/grub2/grub.cfg file.

I have now destroyed these partitions but grubby still uses them and
writes a faulty /boot/grub2/grub.cfg file.

Where does it find that these partitions still exist?

I can't upgrade my system now because I fear that the boot config file
will refer to a partition wich no longer exists on my system.

Please help me!

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte



signature.asc
Description: OpenPGP digital signature
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: rpmbuild

2019-06-15 Thread Patrick Dupre
OK,
Thank Michael and Gordon.

The package perl-generators was not installed.
Now it makes more sense.

Another question
How could I get 
%{_bindir}/*
added in the %files section
without having to edit the generated .spec file (i.e. when I run cpanspec)?

Thank

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===


> Sent: Saturday, June 15, 2019 at 5:41 PM
> From: "Michael Schwendt" 
> To: users@lists.fedoraproject.org
> Subject: Re: rpmbuild
>
> On Fri, 14 Jun 2019 23:38:56 +0200, Patrick Dupre wrote:
> 
> > perl-Tk-JBrowseEntry-5.22-1.fc30.noarch
> 
> > The solutions that I found are:
> > 1) add Provides: perl(Tk::JBrowseEntry) = %{version}-%{release}
> > in perl-Tk-JBrowseEntry.spec
> > or
> > 2) remove 
> > BuildRequires:  perl(Tk::JBrowseEntry) >= 4.63
> > in
> > perl-Tk-JFileDialog.spec
> 
> These two steps contradict eachother.
> 
> The package created by step 1 meets the build requirements of the package
> you want to build. 5.22 >= 4.63, so it is not necessary to remove the
> BuildRequires tag in step 2.
> 
> In step 1, prefer "BuildRequires: perl-generators" instead of adding
> the "Provides" tag manually. A Perl Module package may include more
> than a single module.
> 
> > In my opinion, I should not have to edit the .spec files
> 
> If the output from cpanspec were perfect *and* would meet Fedora's
> Packaging Guidelines, too, you would not need to.
> ___
> 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/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: rpmbuild

2019-06-15 Thread Michael Schwendt
On Fri, 14 Jun 2019 23:38:56 +0200, Patrick Dupre wrote:

> perl-Tk-JBrowseEntry-5.22-1.fc30.noarch

> The solutions that I found are:
> 1) add Provides: perl(Tk::JBrowseEntry) = %{version}-%{release}
> in perl-Tk-JBrowseEntry.spec
> or
> 2) remove 
> BuildRequires:  perl(Tk::JBrowseEntry) >= 4.63
> in
> perl-Tk-JFileDialog.spec

These two steps contradict eachother.

The package created by step 1 meets the build requirements of the package
you want to build. 5.22 >= 4.63, so it is not necessary to remove the
BuildRequires tag in step 2.

In step 1, prefer "BuildRequires: perl-generators" instead of adding
the "Provides" tag manually. A Perl Module package may include more
than a single module.

> In my opinion, I should not have to edit the .spec files

If the output from cpanspec were perfect *and* would meet Fedora's
Packaging Guidelines, too, you would not need to.
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: kernel 5.1.6-200.fc29.x86_64 won't boot Xen DomU

2019-06-15 Thread Frédéric
same problem with KDE Plasma on Fedora 29 and nvidia drivers. I guess
it is more related with nvidia for my case.

Le jeu. 6 juin 2019 à 21:46, Markus Schönhaber
 a écrit :
>
> Hi,
>
> I'm running Fedora 29 in a Xen DomU on a Debian stretch Dom0. While
> kernel 5.0.19-200.fc29.x86_64 works just fine, 5.1.6-200.fc29.x86_64
> crashes on boot.
> Is anyone else seeing this? Is there a workaround?
>
> Regards
>   mks
>
> Tail of
> # xl create /etc/xen/f29.cfg -c
>
> > [2.164017] BUG: unable to handle kernel paging request at 
> > c9ceb818
> > [2.164120] #PF error: [normal kernel read fault]
> > [2.164190] PGD 7dbda067 P4D 7dbda067 PUD 7dbd9067 PMD 78104067 PTE 0
> > [2.164281] Oops:  [#1] SMP NOPTI
> > [2.164281] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
> > 5.1.6-200.fc29.x86_64 #1
> > [2.164281] RIP: e030:pmc_core_probe+0xd1/0x2b8
> > [2.164281] Code: c2 a0 15 ac 82 48 c7 c6 5a f4 17 82 48 c7 c7 e8 15 ac 
> > 82 e8 ce a6 95 fe 48 8b 05 97 70 2e 00 48 63 40 44 48 03 05 84 70 2e 00 
> > <8b> 00 48 8b 15 83 70 2e 00 31 f6 48 c7 c7 68 f4 17 82 8b 4a 48 ba
> > [2.164281] RSP: e02b:c971be10 EFLAGS: 00010286
> > [2.164281] RAX: c9ceb818 RBX:  RCX: 
> > 
> > [2.164281] RDX: 82ac15a0 RSI: 8217f45a RDI: 
> > 82ac15e8
> > [2.164281] RBP: 827da473 R08: 8073 R09: 
> > 88807d001600
> > [2.164281] R10: 7ff0 R11: 0001 R12: 
> > 829557a0
> > [2.164281] R13: 8276a73b R14:  R15: 
> > 
> > [2.164281] FS:  () GS:88807d40() 
> > knlGS:
> ___
> 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/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
___
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/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org