Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/13/17 02:13, CLOSE Dave wrote:
> Ed Greshko wrote:
>
>> Oh, and since I think you said you're not using IPv6 for anything you
>> can disable it completely and try again.
>>
>> Adding ipv6.disable=1 to the boot parameters seems to work the best.
>> That way it is disabled from boot time.
> That did it! The greeting screen now appears as it should. Thanks!


Great.  Now the only unanswered question is Why do you have to disable IPv6 and 
I
don't?  Well, maybe that will remain unanswered.  :-) :-)

-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

Ed Greshko wrote:

> Oh, and since I think you said you're not using IPv6 for anything you
> can disable it completely and try again.
> 
> Adding ipv6.disable=1 to the boot parameters seems to work the best.
> That way it is disabled from boot time.

That did it! The greeting screen now appears as it should. Thanks!
-- 
 Dave Close

 "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/11/17 08:18, CLOSE Dave wrote:
> And when I try to connect,
>
> Jul 10 17:05:49 server kdm: fe80::3617:ebff:feeb:6b02:1[7472]: Cannot
> connect to fe80::3617:ebff:feeb:6b02:1, giving up
> Jul 10 17:05:49 server kdm[1676]: Display fe80::3617:ebff:feeb:6b02:1
> cannot be opened


Oh, and since I think you said you're not using IPv6 for anything you can 
disable it
completely and try again.

Adding ipv6.disable=1 to the boot parameters seems to work the best.  That way 
it is
disabled from boot time.

-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/11/17 08:46, CLOSE Dave wrote:
> Ed Greshko wrote:
>
>> I found that if I have ListenStream=192.168.1.198:5901 in my
>> xvnc.socket file I also get a failure on boot.  I thought it could
>> have been due to my using DHCP on that VM.  I changed it back to
>> ListenStream=5901.  Can you try just having that?
> The socket now reports that it is up correctly after boot. But I still
> get a blank screen on connecting.


OK.   So, since you're getting the blank screen and Xvnc is getting started 
and
you are getting connection error in the kdm log I think it is safe to say that 
there
is nothing wrong with the systemd stuff and the issue is with kdm and/or Xvnc.

Here is my /etc/kde/kdm/kdmrc file

[root@f25f kdm]# grep -v ^# kdmrc

[General]
ConfigVersion=2.4
StaticServers=:0
ReserveServers=:1,:2,:3
ServerVTs=-1
ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
PidFile=/var/run/kdm/kdm.pid
AuthDir=/var/run/kdm

[Xdmcp]
Enable=true
Xaccess=/etc/kde/kdm/Xaccess
Willing=/etc/kde/kdm/Xwilling

[Shutdown]
HaltCmd=/sbin/poweroff
BootManager=None


[X-*-Core]
Setup=/etc/kde/kdm/Xsetup
Session=/etc/kde/kdm/Xsession
ForceUserAuthDir=true
AutoReLogin=false
AllowRootLogin=true
AllowShutdown=Root
SessionsDirs=/usr/share/xsessions,/usr/share/kde4/apps/kdm/sessions
ClientLogFile=.xsession-errors-%d

[X-*-Greeter]
GUIStyle=Plastique
LogoArea=Logo
LogoPixmap=/usr/share/icons/hicolor/96x96/apps/fedora-logo-icon.png
GreetString=Fedora 22 (Twenty Two)
AntiAliasing=true
GreetFont=Sans,16,-1,5,75,0,0,0,0,0
StdFont=Sans,10,-1,5,50,0,0,0,0,0
FailFont=Sans,12,-1,5,75,0,0,0,0,0
UserList=false
ShowUsers=NotHidden
HiddenUsers=root
MinShowUID=-1
MaxShowUID=65530
SortUsers=true
FaceSource=PreferUser
FocusPasswd=true
EchoPasswd=true
UseBackground=true
BackgroundCfg=/var/lib/kdm/backgroundrc
GrabInput=Always
GrabServer=false
ForgingSeed=1108476160
AllowConsole=false
Preloader=/usr/bin/preloadkde
UseTheme=true
Theme=/usr/share/kde4/apps/kdm/themes/fedora

[X-:*-Core]
ServerAttempts=2
ServerTimeout=60
ServerCmd=/usr/bin/X -br -novtswitch -quiet
ServerArgsLocal=-background none -nolisten tcp
TerminateServer=true
AllowNullPasswd=true
AllowShutdown=All

[X-:*-Greeter]
PreselectUser=Previous
FocusPasswd=true
LoginMode=DefaultLocal
AllowClose=false

[X-:0-Core]
ClientLogFile=.xsession-errors

[X-:0-Greeter]


And because I can't think of anything else at the moment

[root@f25f kdm]# netstat -nap | grep kdm
udp6   0  0 :::177  :::*   
767/kdm
unix  2  [ ACC ] STREAM LISTENING 26390767/kdm 
/var/run/xdmctl/dmctl-:1/socket
unix  2  [ ACC ] STREAM LISTENING 21331767/kdm 
/var/run/xdmctl/dmctl-:0/socket
unix  2  [ ACC ] STREAM LISTENING 20931767/kdm 
/var/run/xdmctl/dmctl/socket
unix  3  [ ] STREAM CONNECTED 264041311/kdm_greet  
unix  3  [ ] STREAM CONNECTED 21674866/kdm_greet   
unix  3  [ ] STREAM CONNECTED 26393767/kdm 
unix  3  [ ] STREAM CONNECTED 26395767/kdm 
unix  3  [ ] STREAM CONNECTED 21334767/kdm 
unix  2  [ ] DGRAM20944767/kdm 
unix  3  [ ] STREAM CONNECTED 21356866/kdm_greet   
unix  3  [ ] STREAM CONNECTED 21336767/kdm 
unix  3  [ ] STREAM CONNECTED 264141311/kdm_greet


And when I connect there are no entries sent to the logs of kdm or messages.  
Only
when I close the vncviewer window do I get...

Jul 11 09:00:52 f25f kdm: localhost:1[1365]: Abnormal termination of greeter for
display localhost:1, code 1, signal 0
Jul 11 09:00:52 f25f kdm: localhost:1[1365]: Fatal X server IO error: No such 
file or
directory


-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Rick Stevens]

On 07/10/2017 05:42 PM, CLOSE Dave wrote:
> On 07/10/17 17:32, Ed Greshko wrote:
> 
>> Odd that you're getting an IPV6 error message.  I don't have a global
>> IPv6 address and only show
>>
>> [egreshko@f25f system]$ ip address show enp0s3
>> 2: enp0s3:  mtu 1500 qdisc fq_codel state 
>> UP group
>> default qlen 1000
>> link/ether 08:00:27:15:6d:e0 brd ff:ff:ff:ff:ff:ff
>> inet 192.168.1.198/24 brd 192.168.1.255 scope global dynamic enp0s3
>>valid_lft 84207sec preferred_lft 84207sec
>> inet6 fe80::a00:27ff:fe15:6de0/64 scope link
>>valid_lft forever preferred_lft forever
> 
> Yes, I also found that strange. But the address shown is the right one
> per the output of ifconfig. I'm not intentionally running v6...

The IPV6 you're seeing is the IPV6 link-local Unicast representation
of your MAC address. All systems have that. It's part of IPV6's neighbor
discovery and stateless address configuration systems.

Link-local Unicast addresses can't be routed--they're only visible on
the link the NIC is attached to. You can sort of think of them as the
IPV6 equivalent of IPV4's "224.0.0.0" addresses, although they do more.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Consciousness: that annoying time between naps.   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

Ed Greshko wrote:

> I found that if I have ListenStream=192.168.1.198:5901 in my
> xvnc.socket file I also get a failure on boot.  I thought it could
> have been due to my using DHCP on that VM.  I changed it back to
> ListenStream=5901.  Can you try just having that?

The socket now reports that it is up correctly after boot. But I still
get a blank screen on connecting.
-- 
 Dave Close

 "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/11/17 08:42, CLOSE Dave wrote:
> On 07/10/17 17:32, Ed Greshko wrote:
>
>> Odd that you're getting an IPV6 error message.  I don't have a global
>> IPv6 address and only show
>>
>> [egreshko@f25f system]$ ip address show enp0s3
>> 2: enp0s3:  mtu 1500 qdisc fq_codel state 
>> UP group
>> default qlen 1000
>> link/ether 08:00:27:15:6d:e0 brd ff:ff:ff:ff:ff:ff
>> inet 192.168.1.198/24 brd 192.168.1.255 scope global dynamic enp0s3
>>valid_lft 84207sec preferred_lft 84207sec
>> inet6 fe80::a00:27ff:fe15:6de0/64 scope link
>>valid_lft forever preferred_lft forever
> Yes, I also found that strange. But the address shown is the right one
> per the output of ifconfig. I'm not intentionally running v6...


And you still get the same error if you change to simply "ListenStream=5901"  ?

-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

On 07/10/17 17:32, Ed Greshko wrote:

> Odd that you're getting an IPV6 error message.  I don't have a global
> IPv6 address and only show
> 
> [egreshko@f25f system]$ ip address show enp0s3
> 2: enp0s3:  mtu 1500 qdisc fq_codel state UP 
> group
> default qlen 1000
> link/ether 08:00:27:15:6d:e0 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.198/24 brd 192.168.1.255 scope global dynamic enp0s3
>valid_lft 84207sec preferred_lft 84207sec
> inet6 fe80::a00:27ff:fe15:6de0/64 scope link
>valid_lft forever preferred_lft forever

Yes, I also found that strange. But the address shown is the right one
per the output of ifconfig. I'm not intentionally running v6...
-- 
 Dave Close

 "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

Ed Greshko wrote:

> You have a line in the Service segment of "Type".  I do not have that
> and it isn't in the original file in /lib/systemd/system.  Did you
> add that?

Rick Stevens wrote:

> I believe "Type=simple" is the default if you have "ExecStart="
> defined, but it wouldn't hurt to add it. After you edit any of these
> files, make sure you do a "systemctl daemon-reload" or your changes
> won't be seen by systemd until a reboot.

I had that line because it was in the example in bug 1393971. It isn't
in the later pages which seem to be derived from that. But, as you say,
having it or not doesn't make any difference.
-- 
Dave Close, Thales InFlyt Experience, Irvine California USA.
cell +1 949 394 2124, dave.cl...@us.thalesgroup.com

 "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/11/17 08:18, CLOSE Dave wrote:
> Ed Greshko wrote:
>
>>> HOWEVER, when I connect with "vncviewer server::5901", I get a blank
>>> screen with a momentary F8 prompt. I do not see the normal greeting
>>> screen. Something is still missing.
>> Then I noticed one thing which seems off or odd do me. 
>>
>> When you do "systemctl -l status xvnc.socket" you system is outputting
>> 2 lines.
>>
>> Jul 10 14:10:50 server systemd[1]: Listening on XVNC Server.
>> Jul 10 14:10:50 server systemd[1]: Starting XVNC Server.
>>
>> My system outputs only one.
>>
>> Jul 11 06:48:30 f25f.greshko.com systemd[1]: Listening on XVNC Server.
> That is evidently due to something wrong during boot. After a fresh
> boot, here's what I see.
>
> [root@server ~]# systemctl status xvnc.socket
>   xvnc.socket - XVNC Server
>Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
> preset: disabled)
>Active: failed (Result: resources)
>Listen: 10.76.185.91:5901 (Stream)
>  Accepted: 0; Connected: 0
>
> Jul 10 16:57:13 server systemd[1]: xvnc.socket: Failed to listen on
> sock...ss
> Jul 10 16:57:13 server systemd[1]: Failed to listen on XVNC Server.
> Jul 10 16:57:13 server systemd[1]: xvnc.socket: Unit entered failed state.
> Jul 10 16:57:13 server systemd[1]: Starting XVNC Server.
> Hint: Some lines were ellipsized, use -l to show in full.
> [root@server ~]# systemctl start xvnc.socket
> [root@server ~]# systemctl status xvnc.socket
>   xvnc.socket - XVNC Server
>Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
> preset: disabled)
>Active: active (listening) since Mon 2017-07-10 17:04:20 PDT; 1s ago
>Listen: 10.76.185.91:5901 (Stream)
>  Accepted: 0; Connected: 0
>
> Jul 10 17:04:20 server systemd[1]: Listening on XVNC Server.
> Jul 10 17:04:20 server systemd[1]: Starting XVNC Server.
>
>> Without any clients connected/connecting can you check to see if Xvnc is
>> running?  I only have a running /usr/bin/Xvnc when a client is connected.
> Without a connection, "ps -ef | grep vnc" shows only the grep. During an
> attempted connection, Xvnc is running with all the right options.
>
>> Also, check /var/log/kdm.log to see if there are errors.
> /var/log/kdm.log just tells me that useful messages are in syslog. In
> there, greping for kdm, I see:
>
> Jul 10 16:56:07 server audit: SERVICE_START pid=1 uid=0 auid=4294967295
> ses=4294967295 msg='unit=kdm comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Jul 10 16:56:07 server audit: SERVICE_STOP pid=1 uid=0 auid=4294967295
> ses=4294967295 msg='unit=kdm comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Jul 10 16:57:27 server audit: SERVICE_START pid=1 uid=0 auid=4294967295
> ses=4294967295 msg='unit=kdm comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Jul 10 16:57:27 server kdm[1676]: plymouth is running
> Jul 10 16:57:27 server kdm[1676]: plymouth is active on VT 1, reusing for :0
> Jul 10 16:57:27 server kdm[1676]: plymouth should quit after server startup
> Jul 10 16:57:30 server kdm[1676]: Quitting Plymouth with transition
> Jul 10 16:57:30 server kdm[1676]: Is Plymouth still running? no
>
> And when I try to connect,
>
> Jul 10 17:05:49 server kdm: fe80::3617:ebff:feeb:6b02:1[7472]: Cannot
> connect to fe80::3617:ebff:feeb:6b02:1, giving up
> Jul 10 17:05:49 server kdm[1676]: Display fe80::3617:ebff:feeb:6b02:1
> cannot be opened


I found that if I have ListenStream=192.168.1.198:5901 in my xvnc.socket file I 
also
get a failure on boot.  I thought it could have been due to my using DHCP on 
that
VM.  I changed it back to ListenStream=5901.  Can you try just having that?

Odd that you're getting an IPV6 error message.  I don't have a global IPv6 
address
and only show

[egreshko@f25f system]$ ip address show enp0s3
2: enp0s3:  mtu 1500 qdisc fq_codel state UP 
group
default qlen 1000
link/ether 08:00:27:15:6d:e0 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.198/24 brd 192.168.1.255 scope global dynamic enp0s3
   valid_lft 84207sec preferred_lft 84207sec
inet6 fe80::a00:27ff:fe15:6de0/64 scope link
   valid_lft forever preferred_lft forever

FWIW, after being summoned for breakfast I did add "Type=simple" and things 
still
worked for me. 


-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Rick Stevens]

On 07/10/2017 04:38 PM, Ed Greshko wrote:
> On 07/11/17 05:42, CLOSE Dave wrote:
>>
>> # cat /etc/systemd/system/xvnc@.service
>> [Unit]
>> Description=XVNC per Connection Daemon
>> After=syslog.target
>>
>> [Service]
>> Type=simple
>> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768
>> -depth 24 -once -SecurityTypes=None -fp /usr/share/X11/fonts/misc
>> StandardInput=socket
>> StandardError=syslog
>>
> 
> OhAnother thing
> 
> You have a line in the Service segment of "Type".  I do not have that and it 
> isn't in
> the original file in /lib/systemd/system.  Did you add that?

I believe "Type=simple" is the default if you have "ExecStart=" defined,
but it wouldn't hurt to add it. After you edit any of these files,
make sure you do a "systemctl daemon-reload" or your changes won't be
seen by systemd until a reboot.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  I won't rise to the occasion, but I'll slide over to it.  -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

Ed Greshko wrote:

>> HOWEVER, when I connect with "vncviewer server::5901", I get a blank
>> screen with a momentary F8 prompt. I do not see the normal greeting
>> screen. Something is still missing.

> Then I noticed one thing which seems off or odd do me. 
> 
> When you do "systemctl -l status xvnc.socket" you system is outputting
> 2 lines.
> 
> Jul 10 14:10:50 server systemd[1]: Listening on XVNC Server.
> Jul 10 14:10:50 server systemd[1]: Starting XVNC Server.
> 
> My system outputs only one.
> 
> Jul 11 06:48:30 f25f.greshko.com systemd[1]: Listening on XVNC Server.

That is evidently due to something wrong during boot. After a fresh
boot, here's what I see.

[root@server ~]# systemctl status xvnc.socket
  xvnc.socket - XVNC Server
   Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
preset: disabled)
   Active: failed (Result: resources)
   Listen: 10.76.185.91:5901 (Stream)
 Accepted: 0; Connected: 0

Jul 10 16:57:13 server systemd[1]: xvnc.socket: Failed to listen on
sock...ss
Jul 10 16:57:13 server systemd[1]: Failed to listen on XVNC Server.
Jul 10 16:57:13 server systemd[1]: xvnc.socket: Unit entered failed state.
Jul 10 16:57:13 server systemd[1]: Starting XVNC Server.
Hint: Some lines were ellipsized, use -l to show in full.
[root@server ~]# systemctl start xvnc.socket
[root@server ~]# systemctl status xvnc.socket
  xvnc.socket - XVNC Server
   Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
preset: disabled)
   Active: active (listening) since Mon 2017-07-10 17:04:20 PDT; 1s ago
   Listen: 10.76.185.91:5901 (Stream)
 Accepted: 0; Connected: 0

Jul 10 17:04:20 server systemd[1]: Listening on XVNC Server.
Jul 10 17:04:20 server systemd[1]: Starting XVNC Server.

> Without any clients connected/connecting can you check to see if Xvnc is
> running?  I only have a running /usr/bin/Xvnc when a client is connected.

Without a connection, "ps -ef | grep vnc" shows only the grep. During an
attempted connection, Xvnc is running with all the right options.

> Also, check /var/log/kdm.log to see if there are errors.

/var/log/kdm.log just tells me that useful messages are in syslog. In
there, greping for kdm, I see:

Jul 10 16:56:07 server audit: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=kdm comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 10 16:56:07 server audit: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=kdm comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 10 16:57:27 server audit: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=kdm comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 10 16:57:27 server kdm[1676]: plymouth is running
Jul 10 16:57:27 server kdm[1676]: plymouth is active on VT 1, reusing for :0
Jul 10 16:57:27 server kdm[1676]: plymouth should quit after server startup
Jul 10 16:57:30 server kdm[1676]: Quitting Plymouth with transition
Jul 10 16:57:30 server kdm[1676]: Is Plymouth still running? no

And when I try to connect,

Jul 10 17:05:49 server kdm: fe80::3617:ebff:feeb:6b02:1[7472]: Cannot
connect to fe80::3617:ebff:feeb:6b02:1, giving up
Jul 10 17:05:49 server kdm[1676]: Display fe80::3617:ebff:feeb:6b02:1
cannot be opened
-- 
 Dave Close

 "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/11/17 05:42, CLOSE Dave wrote:
>
> # cat /etc/systemd/system/xvnc@.service
> [Unit]
> Description=XVNC per Connection Daemon
> After=syslog.target
>
> [Service]
> Type=simple
> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768
> -depth 24 -once -SecurityTypes=None -fp /usr/share/X11/fonts/misc
> StandardInput=socket
> StandardError=syslog
>

OhAnother thing

You have a line in the Service segment of "Type".  I do not have that and it 
isn't in
the original file in /lib/systemd/system.  Did you add that?

-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/11/17 05:42, CLOSE Dave wrote:
>
> This was caused because the old service, vncserver@:1, was still
> running. After I stopped it (and deleted the files, just to be sure),
> status looks correct.
>
> ---
>
> # systemctl -l status xvnc.socket
>   xvnc.socket - XVNC Server
>Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
> preset: disabled)
>Active: active (listening) since Mon 2017-07-10 14:10:50 PDT; 27min ago
>Listen: 10.76.185.91:5901 (Stream)
>  Accepted: 2; Connected: 0
>
> Jul 10 14:10:50 pses37top systemd[1]: Listening on XVNC Server.
> Jul 10 14:10:50 pses37top systemd[1]: Starting XVNC Server.
>
> # cat /etc/systemd/system/xvnc.socket
> [Unit]
> Description=XVNC Server
>
> [Socket]
> ListenStream=10.76.185.91:5901
> Accept=yes
>
> [Install]
> WantedBy=sockets.target
>
> # cat /etc/systemd/system/xvnc@.service
> [Unit]
> Description=XVNC per Connection Daemon
> After=syslog.target
>
> [Service]
> Type=simple
> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768
> -depth 24 -once -SecurityTypes=None -fp /usr/share/X11/fonts/misc
> StandardInput=socket
> StandardError=syslog
>
> ---
>
> HOWEVER, when I connect with "vncviewer server::5901", I get a blank
> screen with a momentary F8 prompt. I do not see the normal greeting
> screen. Something is still missing.

First I though the problem may be due to using 5901, but I changed to that and 
it
still works for me.
Then I thought maybe it was your addition of  -fp /usr/share/X11/fonts/misc.  
So, I
added that and it still works for me.

Then I noticed one thing which seems off or odd do me. 

When you do "systemctl -l status xvnc.socket" you system is outputting 2 lines.

Jul 10 14:10:50 pses37top systemd[1]: Listening on XVNC Server.
Jul 10 14:10:50 pses37top systemd[1]: Starting XVNC Server.

My system outputs only one.

Jul 11 06:48:30 f25f.greshko.com systemd[1]: Listening on XVNC Server.

Without any clients connected/connecting can you check to see if Xvnc is 
running?  I
only have a running /usr/bin/Xvnc when a client is connected.

Also, check /var/log/kdm.log to see if there are errors.



-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

Ed Greshko wrote:

> You actually don't want xvnc@.service to be enabled or started.  The
> connection to the socket triggers starting of Xvnc

I realized that a while ago but forgot. It is presently not enabled.

> I find it odd that you get this "Listen: 10.76.185.91:5901"  when
> your file below for xvnc.socket has
> "ListenStream=10.76.185.91:5900".

I did my cut-and-paste to these messages from different tests. I'm
actually trying to use port 5901 to make the transition transparent for
users who are now using the single-user access technique.

I had written:

> # systemctl status -l xvnc@:.service
> ...
> Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Got more than one socket.

> # systemctl status -l xvnc.socket
> ...
>Active: failed (Result: resources)

This was caused because the old service, vncserver@:1, was still
running. After I stopped it (and deleted the files, just to be sure),
status looks correct.

---

# systemctl -l status xvnc.socket
  xvnc.socket - XVNC Server
   Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
preset: disabled)
   Active: active (listening) since Mon 2017-07-10 14:10:50 PDT; 27min ago
   Listen: 10.76.185.91:5901 (Stream)
 Accepted: 2; Connected: 0

Jul 10 14:10:50 pses37top systemd[1]: Listening on XVNC Server.
Jul 10 14:10:50 pses37top systemd[1]: Starting XVNC Server.

# cat /etc/systemd/system/xvnc.socket
[Unit]
Description=XVNC Server

[Socket]
ListenStream=10.76.185.91:5901
Accept=yes

[Install]
WantedBy=sockets.target

# cat /etc/systemd/system/xvnc@.service
[Unit]
Description=XVNC per Connection Daemon
After=syslog.target

[Service]
Type=simple
ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768
-depth 24 -once -SecurityTypes=None -fp /usr/share/X11/fonts/misc
StandardInput=socket
StandardError=syslog

---

HOWEVER, when I connect with "vncviewer server::5901", I get a blank
screen with a momentary F8 prompt. I do not see the normal greeting
screen. Something is still missing.
-- 
Dave Close, Thales InFlyt Experience, Irvine California USA.
cell +1 949 394 2124, dave.cl...@us.thalesgroup.com

 "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/08/17 09:40, CLOSE Dave wrote:
> Here's my files.

Just to clarify a bit more...
>
> # cd /etc/systemd/system
> # cat xvnc@.service
> [Unit]
> Description=XVNC per Connection Daemon
> After=syslog.target
>
> [Service]
> Type=simple
> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768
> -depth 24 -once -SecurityTypes=None -fp /usr/share/X11/fonts/misc
> StandardInput=socket
> StandardError=syslog

The next 2 lines must not appear in that file...
>
> [Install]
> WantedBy=multi-user.target


-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/08/17 10:22, Ed Greshko wrote:
> That is 5901 v.s. 5901

Of course I wanted to type 5901 v.s. 5900

-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/08/17 09:40, CLOSE Dave wrote:
> Almost. But the service isn't starting.
>
> # systemctl status -l xvnc@:.service
>   xvnc@:.service - XVNC per Connection Daemon
>Loaded: loaded (/etc/systemd/system/xvnc@.service; enabled; vendor
> preset: disabled)
>Active: failed (Result: resources)
>
> Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Got more than one socket.
> Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Failed to run 'start'
> task: Invalid argument
> Jul 07 18:27:08 server systemd[1]: Failed to start XVNC per Connection
> Daemon.
> Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Unit entered failed
> state.
> Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Failed with result
> 'resources'.
> Jul 07 18:27:08 server systemd[1]: Starting XVNC per Connection Daemon...

You actually don't want xvnc@.service to be enabled or started.  The connection 
to
the socket triggers starting of Xvnc

On my system with no VNC clients connected.

[root@f25f system]# ps -eaf | grep vnc
root  3523  1251  0 10:04 pts/000:00:00 grep --color=auto vnc

[root@f25f system]# systemctl status xvnc@.service
Failed to get properties: Unit name xvnc@.service is missing the instance name.

[root@f25f system]# systemctl status xvnc.socket
● xvnc.socket - XVNC Server
   Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor preset: 
disabl
   Active: active (listening) since Sat 2017-07-08 10:04:27 CST; 48s ago
   Listen: [::]:5900 (Stream)
 Accepted: 3; Connected: 0

Jul 08 10:04:27 f25f.greshko.com systemd[1]: Listening on XVNC Server.

Once a client connects

[root@f25f system]# ps -eaf | grep vnc
root  3529 1  1 10:06 ?00:00:00 /usr/bin/Xvnc -inetd -query 
localhost
-geometry 1024x768 -depth 24 -once -SecurityTypes=None
>
> # systemctl status -l xvnc.socket
> ● xvnc.socket - XVNC Server
>Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
> preset: disabled)
>Active: failed (Result: resources)
>Listen: 10.76.185.91:5901 (Stream)
>  Accepted: 0; Connected: 0
>
> Jul 07 18:27:06 server systemd[1]: xvnc.socket: Failed to listen on
> sockets: Cannot assign requested address
> Jul 07 18:27:06 server systemd[1]: Failed to listen on XVNC Server.
> Jul 07 18:27:06 server systemd[1]: xvnc.socket: Unit entered failed state.
> Jul 07 18:27:06 server systemd[1]: Starting XVNC Server.
I find it odd that you get this "Listen: 10.76.185.91:5901"  when your file 
below for
xvnc.socket has "ListenStream=10.76.185.91:5900".That is 5901 v.s. 5901. I 
think
you may have done something like what the vncserver@.service file tells you to 
do? 
That is enable xvnc@:1.service?

Here are my files...

[root@f25f system]# pwd
/etc/systemd/system

[root@f25f system]# cat xvnc@.service | grep -v ^#

[Unit]
Description=XVNC Per-Connection Daemon

[Service]
ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768 -depth 24 
-once
-SecurityTypes=None
StandardInput=socket
StandardError=syslog

[root@f25f system]# cat xvnc.socket | grep -v ^#

[Unit]
Description=XVNC Server

[Socket]
ListenStream=5900
Accept=yes

[Install]
WantedBy=sockets.target


And, with no client connected

root@f25f system]# netstat -nap | grep 5900
tcp6   0  0 :::5900 :::*LISTEN  
1/systemd

And connected

[root@f25f system]# netstat -nap | grep 5900
tcp6   0  0 :::5900 :::*LISTEN 
1/systemd  
tcp6   0  0 192.168.1.198:5900  192.168.1.18:56272  ESTABLISHED 
1/systemd



-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

Ed Greshko wrote:

> OK.   Sorry to have misunderstood precisely what you want to do. I
> now have it working as I suspect you need it.

Great. Thanks.

> 1.  Yes, you need KDM.  So, if you've not installed it do so.
> 
> 2.  Edit /etc/kde/kdm/kdmrc the [Xdmcp] section Enable=true.
> 
> 3.  Go to /lib/systemd/system and copy xvnc@.service and xvnc.socket
> to /etc/systemd/system

Done previously.

> 4.  Edit /etc/systemd/system/xvnc@.service and delete the User=nobody
> line.

Done now. Wasn't done before.

> 5.  Now this part is "temporary" until I determine the "proper" way
> to fix it.  Edit /etc/sysconfig/selinux and change it to be
> permissive.  If you don't do that then Xvnc won't be able to bind to
> port 5900.

Running selinux disabled.

> 6.  Enable port 5900 on your firewall.
> 
> 7.  If you've not already done it "systemctl --force enable kdm"

Done previously.

> 8.  Reboot.
> 
> Your console should now be showing KDM as your login screen.
> 
> And you now should be able to connect with something like remmina
> using VNC protocol and get presented with a KDM login screen.
> 
> If you run into trouble, let me know.

Almost. But the service isn't starting.

# systemctl status -l xvnc@:.service
  xvnc@:.service - XVNC per Connection Daemon
   Loaded: loaded (/etc/systemd/system/xvnc@.service; enabled; vendor
preset: disabled)
   Active: failed (Result: resources)

Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Got more than one socket.
Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Failed to run 'start'
task: Invalid argument
Jul 07 18:27:08 server systemd[1]: Failed to start XVNC per Connection
Daemon.
Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Unit entered failed
state.
Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Failed with result
'resources'.
Jul 07 18:27:08 server systemd[1]: Starting XVNC per Connection Daemon...

# systemctl status -l xvnc.socket
● xvnc.socket - XVNC Server
   Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor
preset: disabled)
   Active: failed (Result: resources)
   Listen: 10.76.185.91:5901 (Stream)
 Accepted: 0; Connected: 0

Jul 07 18:27:06 server systemd[1]: xvnc.socket: Failed to listen on
sockets: Cannot assign requested address
Jul 07 18:27:06 server systemd[1]: Failed to listen on XVNC Server.
Jul 07 18:27:06 server systemd[1]: xvnc.socket: Unit entered failed state.
Jul 07 18:27:06 server systemd[1]: Starting XVNC Server.

Here's my files.

# cd /etc/systemd/system
# cat xvnc@.service
[Unit]
Description=XVNC per Connection Daemon
After=syslog.target

[Service]
Type=simple
ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768
-depth 24 -once -SecurityTypes=None -fp /usr/share/X11/fonts/misc
StandardInput=socket
StandardError=syslog

[Install]
WantedBy=multi-user.target
# cat xvnc.*
[Unit]
Description=XVNC Server

[Socket]
ListenStream=10.76.185.91:5900
Accept=yes

[Install]
WantedBy=sockets.target
-- 
 Dave Close

 "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/08/17 08:32, Ed Greshko wrote:
> 7.  If you've not already done it "systemctl --force enable kdm"
>
> 8.  Reboot.
>
> Your console should now be showing KDM as your login screen.
>
> And you now should be able to connect with something like remmina using VNC 
> protocol
> and get presented with a KDM login screen.
>
> If you run into trouble, let me know.


Ooooppp  forgot one 

7a.   systemctl enable xvnc.socket

I missed that since I was paraphrasing the instructions in xvnc@.service to add 
the
step of deleting the User line and forgot you may not have read that part.


-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/08/17 01:50, CLOSE Dave wrote:
> Unfortunately, no, that doesn't help. I already have a one-user setup 
> working and I understand how to extend it to additional users -- so long 
> as the list of users is finite and known to me in advance. But the 
> extension technique involves using unique ports for each user. It is not 
> a properly scalable solution.
>
> With the single-user approach, vncviewer directly asks the user for his 
> password before initiating the connection. That's why it needs a unique 
> port for each user. Using XDMCP with a display manager that supports it 
> works differently. vncviewer doesn't ask for a password and initiates 
> the connection immediately. The user is presented with the same 
> graphical login screen a local user would see. Thus the number of users 
> is not limited by anything I do setting up the configuration.

OK.   Sorry to have misunderstood precisely what you want to do.
I now have it working as I suspect you need it.

1.  Yes, you need KDM.  So, if you've not installed it do so.

2.  Edit /etc/kde/kdm/kdmrc the [Xdmcp] section Enable=true.

3.  Go to /lib/systemd/system and copy xvnc@.service and xvnc.socket to
/etc/systemd/system

4.  Edit /etc/systemd/system/xvnc@.service and delete the User=nobody line.

5.  Now this part is "temporary" until I determine the "proper" way to fix it.  
Edit
/etc/sysconfig/selinux and change it to be permissive.  If you don't do that 
then
Xvnc won't be able to bind to port 5900.

6.  Enable port 5900 on your firewall.

7.  If you've not already done it "systemctl --force enable kdm"

8.  Reboot.

Your console should now be showing KDM as your login screen.

And you now should be able to connect with something like remmina using VNC 
protocol
and get presented with a KDM login screen.

If you run into trouble, let me know.


-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[CLOSE Dave]

I wrote:

> I'm trying to setup a multi-user VNC server on recent versions of
> Fedora without success thus far. I understand that doing so requires
> a display manager with XDMCP support. The current default DM is SDDM
> which does not include such support (at least so far as I've found).
> That means I need to change the DM.
> 
> Following a suggestion I found somewhere, I ran "dnf install kdm; 
> systemctl enable --force kdm.service". I chose KDM because the
> machines involved generally use KDE, not Gnome. That seems to be a
> painless substitution. However, I'm sure I'll have to install some
> protections against automatic updates that reverse the change.
> 
> Then I tried to follow the instructions in RH Bugzilla 1393971 
> () and those at
> RH Solutions 2516 (for XDMCP with xinetd) and 2681531 (which
> replaces xinetd with a systemd socket). I also modified
> /etc/kde/kdm/Xaccess to uncomment "*". After this I get a connection
> but no login screen, just a blank screen with a momentary note about
> using F8.
> 
> The log shows several errors at different times in my experiments. 
> Sometimes Plymouth is not running. Sometimes I'm told the VNC
> service got more than one socket. Usually KDM reports that it can't
> open the display, using an IPv6 notation for the display.
> 
> Can anyone point me to instructions which take into account systemd
> and the structure of recent Fedora releases? It seems to me likely
> that I've messed up something simple in trying to adapt the
> instructions (which are for xinetd and GDM). Or have I provided
> enough information to make a guess as to the problem?

On 07/06/17 19:51, Ed Greshko wrote:
> 
> This should help
> 
> https://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_Guide/ch-TigerVNC.html
>
>  Especially
> 
> 8.1.2.1. Configuring VNC Server for Two Users

> Oh, and FWIW, I am currently running only a single user setup on an
> F25/KDE-Only system.  No need to change sddm as your DM as that isn't
> what is being used by VNC.

Unfortunately, no, that doesn't help. I already have a one-user setup 
working and I understand how to extend it to additional users -- so long 
as the list of users is finite and known to me in advance. But the 
extension technique involves using unique ports for each user. It is not 
a properly scalable solution.

With the single-user approach, vncviewer directly asks the user for his 
password before initiating the connection. That's why it needs a unique 
port for each user. Using XDMCP with a display manager that supports it 
works differently. vncviewer doesn't ask for a password and initiates 
the connection immediately. The user is presented with the same 
graphical login screen a local user would see. Thus the number of users 
is not limited by anything I do setting up the configuration.

So, I'm still hoping someone here can help.
-- 
  Dave Close

  "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/07/17 09:26, CLOSE Dave wrote:
> I'm trying to setup a multi-user VNC server on recent versions of Fedora 
> without success thus far. I understand that doing so requires a display 
> manager with XDMCP support. The current default DM is SDDM which does 
> not include such support (at least so far as I've found). That means I 
> need to change the DM.


Oh, and FWIW, I am currently running only a single user setup on an F25/KDE-Only
system.  No need to change sddm as your DM as that isn't what is being used by 
VNC.

-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Multi-user VNC on F23 and later

[Ed Greshko]

On 07/07/17 09:26, CLOSE Dave wrote:
> I'm trying to setup a multi-user VNC server on recent versions of Fedora 
> without success thus far. I understand that doing so requires a display 
> manager with XDMCP support. The current default DM is SDDM which does 
> not include such support (at least so far as I've found). That means I 
> need to change the DM.
>
> Following a suggestion I found somewhere, I ran "dnf install kdm; 
> systemctl enable --force kdm.service". I chose KDM because the machines 
> involved generally use KDE, not Gnome. That seems to be a painless 
> substitution. However, I'm sure I'll have to install some protections 
> against automatic updates that reverse the change.
>
> Then I tried to follow the instructions in RH Bugzilla 1393971 
> () and those at RH 
> Solutions 2516 (for XDMCP with xinetd) and 2681531 (which replaces 
> xinetd with a systemd socket). I also modified /etc/kde/kdm/Xaccess to 
> uncomment "*". After this I get a connection but no login screen, just a 
> blank screen with a momentary note about using F8.
>
> The log shows several errors at different times in my experiments. 
> Sometimes Plymouth is not running. Sometimes I'm told the VNC service 
> got more than one socket. Usually KDM reports that it can't open the 
> display, using an IPv6 notation for the display.
>
> Can anyone point me to instructions which take into account systemd and 
> the structure of recent Fedora releases? It seems to me likely that I've 
> messed up something simple in trying to adapt the instructions (which 
> are for xinetd and GDM). Or have I provided enough information to make a 
> guess as to the problem?


This should help

https://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_Guide/ch-TigerVNC.html

Especially  

8.1.2.1. Configuring VNC Server for Two Users


-- 
Fedora Users List - The place to go to speculate endlessly



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Multi-user VNC on F23 and later

[CLOSE Dave]

I'm trying to setup a multi-user VNC server on recent versions of Fedora 
without success thus far. I understand that doing so requires a display 
manager with XDMCP support. The current default DM is SDDM which does 
not include such support (at least so far as I've found). That means I 
need to change the DM.

Following a suggestion I found somewhere, I ran "dnf install kdm; 
systemctl enable --force kdm.service". I chose KDM because the machines 
involved generally use KDE, not Gnome. That seems to be a painless 
substitution. However, I'm sure I'll have to install some protections 
against automatic updates that reverse the change.

Then I tried to follow the instructions in RH Bugzilla 1393971 
() and those at RH 
Solutions 2516 (for XDMCP with xinetd) and 2681531 (which replaces 
xinetd with a systemd socket). I also modified /etc/kde/kdm/Xaccess to 
uncomment "*". After this I get a connection but no login screen, just a 
blank screen with a momentary note about using F8.

The log shows several errors at different times in my experiments. 
Sometimes Plymouth is not running. Sometimes I'm told the VNC service 
got more than one socket. Usually KDM reports that it can't open the 
display, using an IPv6 notation for the display.

Can anyone point me to instructions which take into account systemd and 
the structure of recent Fedora releases? It seems to me likely that I've 
messed up something simple in trying to adapt the instructions (which 
are for xinetd and GDM). Or have I provided enough information to make a 
guess as to the problem?
-- 
  Dave Close

  "Age is a very high price to pay for maturity." -- Tom Stoppard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Adrian Sevcenco]

On 12/11/2016 08:55 PM, Michael Schwendt wrote:

On Sun, 11 Dec 2016 17:11:51 +0200, Adrian Sevcenco wrote:


No. That's not the same package I mentioned. Notice the extra ".2" behind
".fc23". That's a minor release update in the least-significant
right-most part of the package "Release" tag.


yes, you're right, i did not see it .. but is this ok to have a
versioning number after the os id??


Yes.

https://fedoraproject.org/wiki/Packaging:Versioning#Minor_release_bumps_for_old_branches

What you call "os id" is known as "dist tag" and is part of the package
Release, so for example

  1.fc23.1   would be higher (= "newer") than   1.fc23

but

  1.fc24 would still be higher than   1.fc23.1

because fc24 is higher than fc23.

i see, thank you for information!




smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Michael Schwendt]

On Sun, 11 Dec 2016 17:11:51 +0200, Adrian Sevcenco wrote:

> > No. That's not the same package I mentioned. Notice the extra ".2" behind
> > ".fc23". That's a minor release update in the least-significant
> > right-most part of the package "Release" tag.  
>
> yes, you're right, i did not see it .. but is this ok to have a 
> versioning number after the os id??

Yes.

https://fedoraproject.org/wiki/Packaging:Versioning#Minor_release_bumps_for_old_branches

What you call "os id" is known as "dist tag" and is part of the package
Release, so for example

  1.fc23.1   would be higher (= "newer") than   1.fc23

but

  1.fc24 would still be higher than   1.fc23.1

because fc24 is higher than fc23.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

f23 :: openvpn 2.3.14-1 :: Failed running command (--up/--down)

[Adrian Sevcenco]

Hi! Did anyone succeeded to run openvpn server in fedora >= 23 ?
(this is 2.3.14 version - f25 srpm rebuilt on f23)

Even if i have all the needed configuration and permissions of the 
script i have a message like :
WARNING: Failed running command (--up/--down): could not execute 
external program


and somehow it would seem that NetworkManager is involved
full log here : http://pastebin.com/WcRR2cTd

all files in /etc/openvpn have root:openvpn ownership
and the the script have 755 permissions

the configuration is simple :
script-security 2
dev tun10
dev-type tun
topology p2p
port 1194

tls-server
local MY_PUB_IP
ifconfig 10.1.1.1 10.1.1.2
up /etc/openvpn/sev-vpn.up

dh keys/dh.pem
ca keys/ca.crt
cert keys/sev.spacescience.ro.crt
key keys/sev.spacescience.ro.key
tls-auth keys/ta.key 0 # This file is secret
cipher AES-256-CBC
comp-lzo yes
push "comp-lzo yes"
txqueuelen 4096
route 192.168.1.0 255.255.255.0
push "route 10.10.8.0 255.255.252.0"
push "route 172.20.0.0 255.255.255.0"
user openvpn
group openvpn
fast-io
keepalive 10 120
persist-tun
persist-key
verb 9

Did anyone have a success story of openvpn server on fedora?
Thank you!
Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Adrian Sevcenco]

On 12/11/2016 02:42 PM, Michael Schwendt wrote:

On Sat, 10 Dec 2016 17:34:26 +0200, Adrian Sevcenco wrote:


Just based on what you've quoted, I would guess the explicit dependency
found in kf5-frameworkintegration on an older Qt 5 version blocks the
update. There should be are rebuild in the updates repo, however:
kf5-frameworkintegration-5.27.0-1.fc23.2.x86_64.rpm
It depends on the Qt 5.6.2 package. Do you see it in the repo?
Maybe you are affected by more so-called "broken dependencies"?

the thing is that i have it installed :
rpm -qa kf5-frameworkintegration
kf5-frameworkintegration-5.27.0-1.fc23.x86_64


No. That's not the same package I mentioned. Notice the extra ".2" behind
".fc23". That's a minor release update in the least-significant
right-most part of the package "Release" tag.
yes, you're right, i did not see it .. but is this ok to have a 
versioning number after the os id??


anyway, the problem was solved (fixed packages in updates) ..

Thank you!
Adrian



Details like that can be _very_ important when examining dependency
problems and checking which packages are available in the repo.




smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Michael Schwendt]

On Sat, 10 Dec 2016 17:34:26 +0200, Adrian Sevcenco wrote:

> > Just based on what you've quoted, I would guess the explicit dependency
> > found in kf5-frameworkintegration on an older Qt 5 version blocks the
> > update. There should be are rebuild in the updates repo, however:
> > kf5-frameworkintegration-5.27.0-1.fc23.2.x86_64.rpm
> > It depends on the Qt 5.6.2 package. Do you see it in the repo?
> > Maybe you are affected by more so-called "broken dependencies"?  
> the thing is that i have it installed :
> rpm -qa kf5-frameworkintegration
> kf5-frameworkintegration-5.27.0-1.fc23.x86_64

No. That's not the same package I mentioned. Notice the extra ".2" behind
".fc23". That's a minor release update in the least-significant
right-most part of the package "Release" tag.

Details like that can be _very_ important when examining dependency
problems and checking which packages are available in the repo.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Adrian Sevcenco]

On 12/10/2016 07:18 PM, Rex Dieter wrote:

Adrian Sevcenco wrote:


Hi! It would seem that the configs for the qt and kde updates were broken
.. trying to update i have this :


Should be fixed by:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-22b09070a2

Thanks a lot! it worked :)

Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Rex Dieter]

Adrian Sevcenco wrote:

> Hi! It would seem that the configs for the qt and kde updates were broken
> .. trying to update i have this :

Should be fixed by:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-22b09070a2

-- Rex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Adrian Sevcenco]

On 12/10/2016 04:19 PM, Michael Schwendt wrote:

On Sat, 10 Dec 2016 12:52:27 +0200, Adrian Sevcenco wrote:


Hi! It would seem that the configs for the qt and kde updates were broken ..
trying to update i have this :

Error: package kf5-frameworkintegration-5.27.0-1.fc23.x86_64 requires
qt5-qtbase(x86-64) = 5.6.1, but none of the providers can be installed.
... and so on

but if i try only qt5 update :
dnf -v update qt5-* --best --allowerasing
i get
removing 7 packages :
kde-print-manager
kde-print-manager-libs
plasma-desktop
plasma-integration
plasma-workspace
plasma-workspace-drkonqi
sddm-breeze

and downgrading:
kdeplasma-addons
kf5-frameworkintegration
kf5-frameworkintegration-libs
kf5-kdeclarative
kf5-kwayland
kf5-plasma

and the actual qt5 packages proposed for update are 5.6.2-1

so .. what is going on?


You need to show the fully versioned list of which packages are installed
at the time _before_ you try to update and the fully versioned list of
which packages are available in all enabled repos.

Only then you can draw conclusions, usually after examining the package
dependencies.

Ok, so everything depends on qt5-qbase :
rpm -qa qt5-qtbase
qt5-qtbase-5.6.1-3.fc23.x86_64

proposed update : 5.6.2-1.fc23


Just based on what you've quoted, I would guess the explicit dependency
found in kf5-frameworkintegration on an older Qt 5 version blocks the
update. There should be are rebuild in the updates repo, however:
kf5-frameworkintegration-5.27.0-1.fc23.2.x86_64.rpm
It depends on the Qt 5.6.2 package. Do you see it in the repo?
Maybe you are affected by more so-called "broken dependencies"?

the thing is that i have it installed :
rpm -qa kf5-frameworkintegration
kf5-frameworkintegration-5.27.0-1.fc23.x86_64

as i said, the main problem is with update only qt5-*
i get proposal to erase :
kde-print-manager
kde-print-manager-libs
plasma-desktop
plasma-integration
plasma-workspace
plasma-workspace-drkonqi
sddm-breeze

and downgrade :
kdeplasma-addons
kf5-frameworkintegration
kf5-frameworkintegration-libs
kf5-kdeclarative
kf5-kwayland
kf5-plasma

that would mean that these packages have hard dependency on the old 5.6.1

Should i open 1 signle ticket in bugzila for all these packages or just
a ticket per package?

Thank you!
Adrian




Fedora still doesn't do anything to prevent such broken deps in stable
releases, unfortunately. Some stay around for a long time, because nobody
stumbles into them or nobody reports them.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org




--
--
Adrian Sevcenco, Ph.D.   |
Institute of Space Science - ISS, Romania|
adrian.sevcenco at {cern.ch,spacescience.ro} |
--



smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: f23 :: kde and qt updates broken

[Michael Schwendt]

On Sat, 10 Dec 2016 12:52:27 +0200, Adrian Sevcenco wrote:

> Hi! It would seem that the configs for the qt and kde updates were broken ..
> trying to update i have this :
> 
> Error: package kf5-frameworkintegration-5.27.0-1.fc23.x86_64 requires 
> qt5-qtbase(x86-64) = 5.6.1, but none of the providers can be installed.
> ... and so on
> 
> but if i try only qt5 update :
> dnf -v update qt5-* --best --allowerasing
> i get
> removing 7 packages :
> kde-print-manager
> kde-print-manager-libs
> plasma-desktop
> plasma-integration
> plasma-workspace
> plasma-workspace-drkonqi
> sddm-breeze
> 
> and downgrading:
> kdeplasma-addons
> kf5-frameworkintegration
> kf5-frameworkintegration-libs
> kf5-kdeclarative
> kf5-kwayland
> kf5-plasma
> 
> and the actual qt5 packages proposed for update are 5.6.2-1
> 
> so .. what is going on?

You need to show the fully versioned list of which packages are installed
at the time _before_ you try to update and the fully versioned list of
which packages are available in all enabled repos.

Only then you can draw conclusions, usually after examining the package
dependencies.

Just based on what you've quoted, I would guess the explicit dependency
found in kf5-frameworkintegration on an older Qt 5 version blocks the
update. There should be are rebuild in the updates repo, however:
kf5-frameworkintegration-5.27.0-1.fc23.2.x86_64.rpm
It depends on the Qt 5.6.2 package. Do you see it in the repo?
Maybe you are affected by more so-called "broken dependencies"?

Fedora still doesn't do anything to prevent such broken deps in stable
releases, unfortunately. Some stay around for a long time, because nobody
stumbles into them or nobody reports them.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

f23 :: kde and qt updates broken

[Adrian Sevcenco]

Hi! It would seem that the configs for the qt and kde updates were broken ..
trying to update i have this :

Error: package kf5-frameworkintegration-5.27.0-1.fc23.x86_64 requires 
qt5-qtbase(x86-64) = 5.6.1, but none of the providers can be installed.

... and so on

but if i try only qt5 update :
dnf -v update qt5-* --best --allowerasing
i get
removing 7 packages :
kde-print-manager
kde-print-manager-libs
plasma-desktop
plasma-integration
plasma-workspace
plasma-workspace-drkonqi
sddm-breeze

and downgrading:
kdeplasma-addons
kf5-frameworkintegration
kf5-frameworkintegration-libs
kf5-kdeclarative
kf5-kwayland
kf5-plasma

and the actual qt5 packages proposed for update are 5.6.2-1

so .. what is going on?

Thank you!
Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Today's F23 Qt5 update

[Kevin Cummings]

On 12/07/16 19:13, Ed Greshko wrote:
> 
> 
> On 12/08/16 06:08, Kevin Cummings wrote:
>> What is wrong with the dependencies?  What can I do to fix it?
> 
> Not really running F23 since it will go EOL soon.  But I had a VM and tested 
> and verified
> the issue you're seeing.
> 
> You can do "dnf --best update" to determine what the broken dependency is.  
> In this I it
> seems related to qt5-qtbase.  So, I would probably ping the kde mailing list 
> to see what
> gives.

I'm not running KDE, but I do run a couple of KDE apps, and they bring
in an awful lot of KDE dependencies.  A whole bunch of kf5 rpms got
updated in the previous update yesterday, including, kf5-kdeclarative,
which was apparently built with a hard dependency of needing
qt5-qtbase-5.6.1, but the current update wants to update qt5-qtbase to
5.6.2 version.  Bad dependency, bad dependency!  Thanks for the pointer Ed!
I guess I'll just have to wait until Fedora gets around to fixing their
stuff.

-- 
Kevin J. Cummings
kjch...@verizon.net
cummi...@kjchome.homeip.net
cummi...@kjc386.framingham.ma.us
Registered Linux User #1232 (http://www.linuxcounter.net/)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Today's F23 Qt5 update

[Ed Greshko]

On 12/08/16 06:08, Kevin Cummings wrote:
> What is wrong with the dependencies?  What can I do to fix it?

Not really running F23 since it will go EOL soon.  But I had a VM and tested 
and verified
the issue you're seeing.

You can do "dnf --best update" to determine what the broken dependency is.  In 
this I it
seems related to qt5-qtbase.  So, I would probably ping the kde mailing list to 
see what
gives.

-- 
You're Welcome Zachary Quinto
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Today's F23 Qt5 update

[Kevin Cummings]

Am I the only person seeing the following:

> v = 18.487/19.290/20.489/0.863 ms
> [root@kjclap4 ~]# dnf update
> Last metadata expiration check: 1:27:15 ago on Wed Dec  7 15:39:19 2016.
> Dependencies resolved.
> =
>  Package  Arch
> Version RepositorySize
> =
> Skipping packages with broken dependencies:
>  python3-qt5  x86_64  
> 5.5.1-2.fc23.6  updates  3.8 M
>  qt-creator   x86_64  
> 4.0.3-2.fc23updates   16 M
>  qt-creator-data  noarch  
> 4.0.3-2.fc23updates  1.1 M
>  qt5-qdoc x86_64  
> 5.6.2-2.fc23updates  477 k
>  qt5-qtbase   x86_64  
> 5.6.2-1.fc23updates  3.0 M
>  qt5-qtbase-commonnoarch  
> 5.6.2-1.fc23updates   29 k
>  qt5-qtbase-devel x86_64  
> 5.6.2-1.fc23updates  4.0 M
>  qt5-qtbase-gui   x86_64  
> 5.6.2-1.fc23updates  5.2 M
>  qt5-qtbase-mysql x86_64  
> 5.6.2-1.fc23updates   57 k
>  qt5-qtconnectivity   x86_64  
> 5.6.2-1.fc23updates  400 k
>  qt5-qtdeclarativex86_64  
> 5.6.2-1.fc23updates  4.2 M
>  qt5-qtlocation   x86_64  
> 5.6.2-1.fc23updates  737 k
>  qt5-qtmultimedia x86_64  
> 5.6.2-1.fc23updates  784 k
>  qt5-qtquickcontrols  x86_64  
> 5.6.2-1.fc23updates  928 k
>  qt5-qtscript x86_64  
> 5.6.2-1.fc23updates  1.0 M
>  qt5-qtsensorsx86_64  
> 5.6.2-1.fc23updates  195 k
>  qt5-qtserialport x86_64  
> 5.6.2-1.fc23updates   65 k
>  qt5-qtsvgx86_64  
> 5.6.2-1.fc23updates  157 k
>  qt5-qttools  x86_64  
> 5.6.2-2.fc23updates   44 k
>  qt5-qttools-common   noarch  
> 5.6.2-2.fc23updates   24 k
>  qt5-qttools-libs-clucene x86_64  
> 5.6.2-2.fc23updates   49 k
>  qt5-qttools-libs-designerx86_64  
> 5.6.2-2.fc23updates  2.7 M
>  qt5-qttools-libs-designercomponents  x86_64  
> 5.6.2-2.fc23updates  789 k
>  qt5-qttools-libs-helpx86_64  
> 5.6.2-2.fc23updates  218 k
>  qt5-qtwebchannel x86_64  
> 5.6.2-1.fc23updates   84 k
>  qt5-qtwebkit x86_64  
> 5.6.2-1.fc23updates   10 M
>  qt5-qtwebsockets 

Re: Botched fedup F23 -> F24 with nvidia

[Greg Woods]

On Mon, Nov 7, 2016 at 7:33 AM, joev.8450  wrote:

> doesn't the nVidia installer uninstall everything nvidia before it
> installs the version in the invoked installer run file?


I wouldn't know as I always install everything from packages, and that's
what Mark is doing as well. For me, I use rpmfusion as the repo and they
maintain Nvidia driver packages. I don't know exactly why this happens, but
I have seen cases where updating a kernel and installing the new driver
with a normal "dnf update" puts the Nvidia stuff in a screwed-up state
where GNOME won't work. The way I have fixed it is just "dnf remove
*nvidia*" and then reinstall the nvidia packages I need from scratch.

--Greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[Mark]

On Mon, 2016-11-07 at 09:33 -0500, joev.8450 wrote:
> doesn't the nVidia installer uninstall everything nvidia before it
> installs the version in the invoked installer run file?  I mean is
> there
> something else I should invoke or do to make sure I've uninstalled
> everything nvidia?  I'm having somewhat of a similar problem but
> re-running the installer which tells me it is uninstalling the
> installed
> version isn't helping.

What I did was to use 'rpm -e' to remove all nvidia related packages
and then 'yum install' to get those same packages back.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[joev.8450]

doesn't the nVidia installer uninstall everything nvidia before it
installs the version in the invoked installer run file?  I mean is there
something else I should invoke or do to make sure I've uninstalled
everything nvidia?  I'm having somewhat of a similar problem but
re-running the installer which tells me it is uninstalling the installed
version isn't helping.

regards,

Joe Verreau
Durand, MI

On 11/04/2016 09:23 AM, Mark wrote:
> On Thu, 2016-11-03 at 12:28 -0600, Greg Woods wrote:
>> On Thu, Nov 3, 2016 at 11:30 AM, Mark 
>> wrote:
>>
>>> All I got was a grey page with the text "Oh no! Something has
>>> gone wrong.
>>>
>> When using the Nvidia proprietary driver, when I have this happen,
>> the only
>> way I have successfully recovered is to uninstall everything *nvidia*
>> and
>> reinstall clean. I just finished doing that yesterday.
> Thanks Greg. That did the trick
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: After fedup F23 -> F24 no more left-handed mouse

[stan]

On Fri, 04 Nov 2016 17:17:09 +0100
Mark  wrote:

> Hi
> 
> I just upgraded my desktop from F23 to F24 via fedup and after that
> the setting to have the right mouse button as the primary one has no
> effect. That is I go to All Settings -> Mouse & Touchpad and select
> Right as the primary button. But it has no effect at all. Even when I
> go to Test Your Settings it still reports that the right button is the
> secondary one.
> 
> Is there some config file that I could tweak to set this?

Without knowing your desktop, it will be hard for people to respond.
What shows in /etc/X11/xorg.conf.d/?  Is there any hard coded config
for the mouse there?  You could add one to set your desired mouse
configuration, if there isn't.  A search should give you examples that
you can tweak.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

After fedup F23 -> F24 no more left-handed mouse

[Mark]

Hi

I just upgraded my desktop from F23 to F24 via fedup and after that the
setting to have the right mouse button as the primary one has no
effect. That is I go to All Settings -> Mouse & Touchpad and select
Right as the primary button. But it has no effect at all. Even when I
go to Test Your Settings it still reports that the right button is the
secondary one.

Is there some config file that I could tweak to set this?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[Mark]

On Thu, 2016-11-03 at 12:28 -0600, Greg Woods wrote:
> On Thu, Nov 3, 2016 at 11:30 AM, Mark 
> wrote:
> 
> > 
> > All I got was a grey page with the text "Oh no! Something has
> > gone wrong.
> > 
> 
> When using the Nvidia proprietary driver, when I have this happen,
> the only
> way I have successfully recovered is to uninstall everything *nvidia*
> and
> reinstall clean. I just finished doing that yesterday.

Thanks Greg. That did the trick
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[Greg Woods]

On Thu, Nov 3, 2016 at 11:30 AM, Mark  wrote:

> All I got was a grey page with the text "Oh no! Something has
> gone wrong.
>

When using the Nvidia proprietary driver, when I have this happen, the only
way I have successfully recovered is to uninstall everything *nvidia* and
reinstall clean. I just finished doing that yesterday.

--Greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Botched fedup F23 -> F24 with nvidia

[Mark]

Hi

I've got a Fedora 23 desktop that I thought was time to upgrade to
Fedora 24. I followed these instructions 
https://fedoramagazine.org/upgrading-fedora-23-workstation-to-fedora-24

And because I have nvidia kernel modules from rpmfusion I also did 
dnf install http://download1.rpmfusion.org/free/fedora/rpmfusion-free-r
elease-24.noarch.rpm
dnf install http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-non
free-release-24.noarch.rpm
before fedup. 

The upgrade process went without any problems until the first boot up
with F24. All I got was a grey page with the text "Oh no! Something has
gone wrong. A problem has occurred and the system can't recover. Please
log out and try again."

With Ctrl-Alt-F2 I could get a terminal, and verified that I had a
matching nvidia module for the new kernel. I tried to run the command
nvidia-xconfig and reboot. I also tried to boot one of the F23 kernels.
I tried to disconnect the second monitor if that would make any
difference. All got was that grey page telling me that something was
wrong. dmesg didn't provide any message that I though would be directly
suspicious.

The graphics card is a Nvidia Quadro 600 (GF108GL)

How to recover?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: How to access the "Packages" directory on the f23 and f24 Workstation iso image?

[Ed Greshko]

On 11/03/16 09:33, Rick Stevens wrote:
> On 11/02/2016 06:30 PM, fred roller wrote:
>> Mount -o loop file.iso ./somedirectory/you/made
>>
>> I believe will mount your image
>>
>> Most archive managers will open an iso file as well. Booting a live
>> usb/dvd would allow for exploring. 
> To be certain:
>
>   mount -o loop -t iso9660 /path/to/file.iso /desired/mountpoint
>
> The "-t iso9660" ensures a CDROM-style FS is used. It should autodetect
> it, but "belt and suspenders" is never a bad idea.

And, after you did all that and mounted all the other file systems contained on 
the LiveCD
you'd find that there is no "Packages" directory.  :-)

It isn't needed since the "install to disk" process simply copies whole 
directories from
the rootfs.img to where it is needed and doesn't do package installs like the 
DVD installs
of older releases. 

-- 
You're Welcome Zachary Quinto
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: How to access the "Packages" directory on the f23 and f24 Workstation iso image?

[Rick Stevens]

On 11/02/2016 06:30 PM, fred roller wrote:
> Mount -o loop file.iso ./somedirectory/you/made
> 
> I believe will mount your image
> 
> Most archive managers will open an iso file as well. Booting a live
> usb/dvd would allow for exploring. 

To be certain:

mount -o loop -t iso9660 /path/to/file.iso /desired/mountpoint

The "-t iso9660" ensures a CDROM-style FS is used. It should autodetect
it, but "belt and suspenders" is never a bad idea.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   You possess a mind not merely twisted, but actually sprained.-
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: How to access the "Packages" directory on the f23 and f24 Workstation iso image?

[fred roller]

Mount -o loop file.iso ./somedirectory/you/made

I believe will mount your image

Most archive managers will open an iso file as well. Booting a live usb/dvd
would allow for exploring.

Fred Roller

On Nov 2, 2016 7:13 PM, "jd1008"  wrote:

>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

How to access the "Packages" directory on the f23 and f24 Workstation iso image?

[jd1008]

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Can't suspend F23 due to mate-settings-daemon and mate-multiload-applet

[Kevin Cummings]

Have anyone else noticed this?

If I boot any of the recent 4.7 kernels, I can immediately suspend my
laptop without incident.  If I leave the system up for some reasonable
amount of time, then everytime I try to suspend, it fails.  journalctl
shows that 2 Mate daemons refuse to Freeze:

Here is just one exert from my journal:

> Oct 26 12:43:04 kjclap4 kernel: PM: Preparing system for sleep (freeze)
> Oct 26 12:43:04 kjclap4 kernel: Freezing user space processes ... 
> Oct 26 12:43:04 kjclap4 kernel: Freezing of tasks failed after 20.004 seconds 
> (2 tasks refusing to freeze, wq_busy=0):
> Oct 26 12:43:04 kjclap4 kernel: mate-settings-d D 8800aed2fc20 0  
> 1419   1192 0x0004
> Oct 26 12:43:04 kjclap4 kernel:  8800aed2fc20 8800aed68000 
> 880119ddba80 8800aed2fc00
> Oct 26 12:43:04 kjclap4 kernel:  8800aed3 8800aed2fc50 
> 8800befae260 880095e7c000
> Oct 26 12:43:04 kjclap4 kernel:  fe00 8800aed2fc38 
> ad7e0c65 8800befae190
> Oct 26 12:43:04 kjclap4 kernel: Call Trace:
> Oct 26 12:43:04 kjclap4 kernel:  [] schedule+0x35/0x80
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> request_wait_answer+0x15b/0x250 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] ? 
> wake_atomic_t_function+0x70/0x70
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> __fuse_request_send+0x71/0x80 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> fuse_request_send+0x27/0x30 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> fuse_simple_request+0xcc/0x1a0 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] fuse_statfs+0xe1/0x150 
> [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> statfs_by_dentry+0x6c/0x90
> Oct 26 12:43:04 kjclap4 kernel:  [] vfs_statfs+0x1b/0xa0
> Oct 26 12:43:04 kjclap4 kernel:  [] user_statfs+0x58/0xa0
> Oct 26 12:43:04 kjclap4 kernel:  [] SYSC_statfs+0x27/0x60
> Oct 26 12:43:04 kjclap4 kernel:  [] SyS_statfs+0xe/0x10
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> entry_SYSCALL_64_fastpath+0x1a/0xa4
> Oct 26 12:43:04 kjclap4 kernel: mate-multiload- D 8800a8c4bc20 0  
> 1698  1 0x0004
> Oct 26 12:43:04 kjclap4 kernel:  8800a8c4bc20 8800a72b3a80 
> 8800abfb1d40 8800a8c4bc00
> Oct 26 12:43:04 kjclap4 kernel:  8800a8c4c000 8800a8c4bc50 
> 8800befae0d0 880095e7c000
> Oct 26 12:43:04 kjclap4 kernel:  fe00 8800a8c4bc38 
> ad7e0c65 8800befae000
> Oct 26 12:43:04 kjclap4 kernel: Call Trace:
> Oct 26 12:43:04 kjclap4 kernel:  [] schedule+0x35/0x80
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> request_wait_answer+0x15b/0x250 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] ? 
> wake_atomic_t_function+0x70/0x70
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> __fuse_request_send+0x71/0x80 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> fuse_request_send+0x27/0x30 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> fuse_simple_request+0xcc/0x1a0 [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] fuse_statfs+0xe1/0x150 
> [fuse]
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> statfs_by_dentry+0x6c/0x90
> Oct 26 12:43:04 kjclap4 kernel:  [] vfs_statfs+0x1b/0xa0
> Oct 26 12:43:04 kjclap4 kernel:  [] user_statfs+0x58/0xa0
> Oct 26 12:43:04 kjclap4 kernel:  [] SYSC_statfs+0x27/0x60
> Oct 26 12:43:04 kjclap4 kernel:  [] SyS_statfs+0xe/0x10
> Oct 26 12:43:04 kjclap4 kernel:  [] 
> entry_SYSCALL_64_fastpath+0x1a/0xa4
> Oct 26 12:43:04 kjclap4 kernel: 
> Oct 26 12:43:04 kjclap4 rtkit-daemon[657]: The canary thread is apparently 
> starving. Taking action.
> Oct 26 12:43:04 kjclap4 rtkit-daemon[657]: Demoting known real-time threads.
> Oct 26 12:43:04 kjclap4 rtkit-daemon[657]: Successfully demoted thread 1545 
> of process 1460 (/usr/bin/pulseaudio).
> Oct 26 12:43:04 kjclap4 kernel: Restarting tasks ... done.
> Oct 26 12:43:04 kjclap4 rtkit-daemon[657]: Successfully demoted thread 1533 
> of process 1460 (/usr/bin/pulseaudio).
> Oct 26 12:43:04 kjclap4 rtkit-daemon[657]: Successfully demoted thread 1460 
> of process 1460 (/usr/bin/pulseaudio).
> Oct 26 12:43:04 kjclap4 rtkit-daemon[657]: Demoted 3 threads.
> Oct 26 12:43:04 kjclap4 kernel: video LNXVIDEO:01: Restoring backlight state

Can anyone shed some light on this?  It continues through kernel 4.7.9.
(I have not yet booted 4.7.10.)

If I try and suspend, it fails, and restores the kernel to a fully
running state, usually on battery, and usually with the laptop fan
continuing to run, expelling heat into my laptop case if I don't notice it!

-- 
Kevin J. Cummings
kjch...@verizon.net
cummi...@kjchome.homeip.net
cummi...@kjc386.framingham.ma.us
Registered Linux User #1232 (http://www.linuxcounter.net/)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23 rsnapshot log timestamps funny

[James Hogarth]

On 20 October 2016 at 11:31, Patrick O'Callaghan  wrote:
> On Thu, 2016-10-20 at 10:13 +0100, Christopher Ross wrote:
>> Since yesterday's update of rsnapshot to
>> rsnapshot-1.4.2-1.fc23.noarch
>>
>> The format of the date/time field in the rsnapshot.log has gone funny,
>> as per the following examples...
>>
>> [19/Oct/2016:11:53:42] /usr/bin/rsnapshot daily: completed successfully
>> [19/Oct/2016:12:04:15] /usr/bin/rsnapshot hourly: completed successfully
>> [2016-10-19T18:08:11] /usr/bin/rsnapshot hourly: completed successfully
>> [2016-10-20T00:07:09] /usr/bin/rsnapshot hourly: completed successfully
>> [2016-10-20T06:06:31] /usr/bin/rsnapshot hourly: completed successfully
>>
>>
>> Is anyone else seeing this? Is there an easy fix?
>
> You might want to ask on the rsnapshot list at 
> https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
>


Hi, one of the maintainers here ...

This was a change way back in 2012:
https://github.com/rsnapshot/rsnapshot/commit/332872aa5

It certainly sounds like potentially a valid RFE to customise the
date/log format ...

Are you able to open an issue on github to track it? I expect either
someone there will be interested to comment at the least, and
hopefully maybe get the log format customisable or something.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23 rsnapshot log timestamps funny

[Patrick O'Callaghan]

On Thu, 2016-10-20 at 10:13 +0100, Christopher Ross wrote:
> Since yesterday's update of rsnapshot to
> rsnapshot-1.4.2-1.fc23.noarch
> 
> The format of the date/time field in the rsnapshot.log has gone funny, 
> as per the following examples...
> 
> [19/Oct/2016:11:53:42] /usr/bin/rsnapshot daily: completed successfully
> [19/Oct/2016:12:04:15] /usr/bin/rsnapshot hourly: completed successfully
> [2016-10-19T18:08:11] /usr/bin/rsnapshot hourly: completed successfully
> [2016-10-20T00:07:09] /usr/bin/rsnapshot hourly: completed successfully
> [2016-10-20T06:06:31] /usr/bin/rsnapshot hourly: completed successfully
> 
> 
> Is anyone else seeing this? Is there an easy fix?

You might want to ask on the rsnapshot list at 
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

F23 rsnapshot log timestamps funny

[Christopher Ross]

Since yesterday's update of rsnapshot to
rsnapshot-1.4.2-1.fc23.noarch

The format of the date/time field in the rsnapshot.log has gone funny, 
as per the following examples...


[19/Oct/2016:11:53:42] /usr/bin/rsnapshot daily: completed successfully
[19/Oct/2016:12:04:15] /usr/bin/rsnapshot hourly: completed successfully
[2016-10-19T18:08:11] /usr/bin/rsnapshot hourly: completed successfully
[2016-10-20T00:07:09] /usr/bin/rsnapshot hourly: completed successfully
[2016-10-20T06:06:31] /usr/bin/rsnapshot hourly: completed successfully


Is anyone else seeing this? Is there an easy fix?

Many thanks,
Chris R.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

what creates /dev/watchdog and /dev/watchdog0 on my f23 system?

[Robert P. J. Day]

  poking around in watchdog support for the first time, and i see
these special device files:

  crw---. 1 root root  10, 130 Oct 15 04:55 /dev/watchdog
  crw---. 1 root root 250,   0 Oct 15 04:55 /dev/watchdog0

can someone tell me what part of the boot process creates those
special files?

  i've yet to install the "watchdog" package, so there's no
user space watchdog daemon running yet. i do see the kernel threads:

root13 2  0 04:55 ?00:00:00 [watchdog/0]
root16 2  0 04:55 ?00:00:00 [watchdog/1]
root24 2  0 04:55 ?00:00:00 [watchdog/2]
root32 2  0 04:55 ?00:00:00 [watchdog/3]
root40 2  0 04:55 ?00:00:00 [watchdog/4]
root48 2  0 04:55 ?00:00:00 [watchdog/5]
root56 2  0 04:55 ?00:00:00 [watchdog/6]
root64 2  0 04:55 ?00:00:00 [watchdog/7]
root85 2  0 04:55 ?00:00:00 [watchdogd]

so i was assuming maybe a udev entry was creating them, but i don't
see it. still reading the docs so i'm sure i'll run across it
eventually, but would be nice if i knew who was responsible for
creating them. thanks.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Patrick O'Callaghan]

On Thu, 2016-10-13 at 10:36 +0100, Gary Stainburn wrote:
> On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote:
> > Unfortunately, I cannot convert this into a usable solution in the KDE menu
> > Editor
> 
> I've been totally unable to get this working properly within KDE Menu Editor.

This might be better discussed on the Fedora KDE List.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote:
> Unfortunately, I cannot convert this into a usable solution in the KDE menu
> Editor

I've been totally unable to get this working properly within KDE Menu Editor.

Instead I've had to modify my root BASH script to cope.  Not pretty, but here 
it is in case anyone else wants it.

#!/bin/bash

user=root
kons=''
ssh=`which ssh`
while [[ "$1" =~ ^-.* ]]; do
  if [ "$1" == "-u" ]; then
user=$2
shift
shift
  fi
  if [ "$1" == '-k' ]; then
kons='y'
shift
  fi
# echo remainder $*
done

if [ "$1" == "" ]; then
  host=127.0.0.1
else
  host=`shift`
fi

if [ -z "$kons" ]; then
  $ssh -Y -C -l $user $host $*
else
  konsole -e "$ssh -Y -C -l $user $host $*"
fi
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

On Thursday 13 October 2016 09:48:31 Gary Stainburn wrote:
> On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote:
> > That looks similar to this upstream bug:
> > https://bugs.kde.org/show_bug.cgi?id=366793
>
> Interestingly, I now have two problems.
>
> This is indeed the problem on the PC I initially experienced the problem
> on.
>
> As suggested in the bug report, changing
>
> konsole -c root ollie
>
> to
>
> konsole -e bash root ollie
>
> fixed the problem.
>
Unfortunately, I cannot convert this into a usable solution in the KDE menu 
Editor
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote:
> That looks similar to this upstream bug:
> https://bugs.kde.org/show_bug.cgi?id=366793

Interestingly, I now have two problems.

This is indeed the problem on the PC I initially experienced the problem on.

As suggested in the bug report, changing 

konsole -c root ollie

to

konsole -e bash root ollie

fixed the problem.

However, I now have a similar but different problem on the laptop I used on 
Tuesday. Hay Ho
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote:
> On 7 October 2016 at 16:05, Gary Stainburn
>
>  wrote:
> > I don't know when it stopped working working, but it was recently.
> > Unfortunately, with almost daily updates I don't know what's caused it.
> >
> > I have menu entried within my KDE which start a ssh command inside a
> > konsole. This has worked fine for as long as I can remember (F9 or
> > before)
> >
> > However, now when I try, I get the launch feedback, the konsole window
> > never opens.
> >
> > If I open a konsole session, e.g. by right clicking the desktop, and then
> > run the ssh command then all works fine.
> >
> > Can annyone suggest how I can debug/fix the problem?
>
> That looks similar to this upstream bug:
> https://bugs.kde.org/show_bug.cgi?id=366793

I have tried replicating this bug on my system, but don't have a problem.

The bug reports that the '-c' argument is not recognised. However, when I try 
it, the command works, with a new konsole window opening and the ssh command 
working.  I do get an error when I close the new child window, but that is 
all.

However, while testing this I found an odd behaviour.  If I run the command

konsole -e bash -c "root ollie"

it works and I have a konsole session which is logged into Ollie.  However, if 
I do

konsole -e sh -c "ssh -Y C -l root ollie"

it briefly opens the window but then immediately closes it, presumably because 
the SSH has failed.  The odd thing is that the two commands are effectively 
the same thing

[gary@gary ~]$ cat bin/root
#!/bin/bash

if [ "$1" == "" ]; then
  host=127.0.0.1
else
  host=`shift`
fi

ssh  -Y -C -l root $host $*
[gary@gary ~]$ 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F23: KDE menu launch SSH inside konsole fails after update

[Ahmad Samir]

On 7 October 2016 at 16:05, Gary Stainburn
 wrote:
> I don't know when it stopped working working, but it was recently.
> Unfortunately, with almost daily updates I don't know what's caused it.
>
> I have menu entried within my KDE which start a ssh command inside a konsole.
> This has worked fine for as long as I can remember (F9 or before)
>
> However, now when I try, I get the launch feedback, the konsole window never
> opens.
>
> If I open a konsole session, e.g. by right clicking the desktop, and then run
> the ssh command then all works fine.
>
> Can annyone suggest how I can debug/fix the problem?

That looks similar to this upstream bug:
https://bugs.kde.org/show_bug.cgi?id=366793

-- 
Ahmad Samir
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

F23: KDE menu launch SSH inside konsole fails after update

[Gary Stainburn]

I don't know when it stopped working working, but it was recently. 
Unfortunately, with almost daily updates I don't know what's caused it.

I have menu entried within my KDE which start a ssh command inside a konsole. 
This has worked fine for as long as I can remember (F9 or before)

However, now when I try, I get the launch feedback, the konsole window never 
opens.

If I open a konsole session, e.g. by right clicking the desktop, and then run 
the ssh command then all works fine.

Can annyone suggest how I can debug/fix the problem?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Upgrade to F23 breaks Adobe Reader

[Stephen Davies]

On 17/09/16 03:07, Samuel Sieb wrote:

dnf repoquery --whatprovides libgdk_pixbuf_xlib-2.0.so.0


Thanks for that.

I'm still coming to grips with dnf syntax

Your suggestion gives:

dnf repoquery --whatprovides libgdk_pixbuf_xlib-2.0.so.0
Last metadata expiration check: 1:56:03 ago on Sat Sep 17 09:01:33 2016.
gdk-pixbuf2-xlib-0:2.32.1-1.fc23.i686
gdk-pixbuf2-xlib-0:2.32.3-1.fc23.i686

Also,

dnf provides libgdk_pixbuf_xlib-2.0.so.0

gives

Last metadata expiration check: 1:58:14 ago on Sat Sep 17 09:01:33 2016.
gdk-pixbuf2-xlib-2.32.3-1.fc23.i686 : Additional library for using gdk-pixbuf 
with bare xlib

Repo: @System

gdk-pixbuf2-xlib-2.32.3-1.fc23.i686 : Additional library for using gdk-pixbuf 
with bare xlib

Repo: updates

gdk-pixbuf2-xlib-2.32.1-1.fc23.i686 : Additional library for using gdk-pixbuf 
with bare xlib

Repo: fedora

I had omitted the trailing -2.0.so.0 so fund nothing.

acroread now works again;-))

Cheers,
Stephen
--
=
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia.Mobile:040 304 0583
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Upgrade to F23 breaks Adobe Reader

[Eddie G. O'Connor Jr.]

I was about to recommend an uninstall and re-install. When I realized? This 
ain't Windows!! On Sep 16, 2016 1:34 PM, Samuel Sieb  wrote:
>
> On 09/16/2016 01:04 AM, Stephen Davies wrote:
> > Following last night's upgrade to F23, Adobe Reader now gives:
> >
> > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading
> > shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object
> > file: No such file or directory
> >
> > Needless to say, acroread worked perfectly before the upgrade but there
> > is now no sign of a 32-bit libgdk_pixbuf_xlib-2.0.so (but there is a
> > 64-bit version).
> >
> dnf install gdk-pixbuf2-xlib.i686
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Upgrade to F23 breaks Adobe Reader

[Samuel Sieb]

On 09/16/2016 10:34 AM, Samuel Sieb wrote:

On 09/16/2016 01:04 AM, Stephen Davies wrote:

Following last night's upgrade to F23, Adobe Reader now gives:

/opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading
shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object
file: No such file or directory

Needless to say, acroread worked perfectly before the upgrade but there
is now no sign of a 32-bit libgdk_pixbuf_xlib-2.0.so (but there is a
64-bit version).


dnf install gdk-pixbuf2-xlib.i686


Btw, you can find that by using
dnf repoquery --whatprovides libgdk_pixbuf_xlib-2.0.so.0

That might tell you the 32-bit or 64-bit version, but you can install 
the one you need.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Upgrade to F23 breaks Adobe Reader

[Samuel Sieb]

On 09/16/2016 01:04 AM, Stephen Davies wrote:

Following last night's upgrade to F23, Adobe Reader now gives:

/opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading
shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object
file: No such file or directory

Needless to say, acroread worked perfectly before the upgrade but there
is now no sign of a 32-bit libgdk_pixbuf_xlib-2.0.so (but there is a
64-bit version).


dnf install gdk-pixbuf2-xlib.i686
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Upgrade to F23 breaks Adobe Reader

[Fernando Cassia]

welll, Adobe Reader for Linux hasn't been supported for at least two
years...
https://forums.adobe.com/thread/1597058

FC

On Fri, Sep 16, 2016 at 8:04 AM, Stephen Davies  wrote:

> Following last night's upgrade to F23, Adobe Reader now gives:
>
> /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading
> shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object
> file: No such file or directory
>
> Needless to say, acroread worked perfectly before the upgrade but there is
> now no sign of a 32-bit libgdk_pixbuf_xlib-2.0.so (but there is a 64-bit
> version).
>
> Cheers,
> Stephen
> --
> 
> =
> Stephen Davies Consulting P/L Phone: 08-8177
> 1595
> Adelaide, South Australia.Mobile:040 304
> 0583
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>



-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Upgrade to F23 breaks Adobe Reader

[Stephen Davies]

Following last night's upgrade to F23, Adobe Reader now gives:

/opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading shared 
libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object file: No 
such file or directory


Needless to say, acroread worked perfectly before the upgrade but there is now 
no sign of a 32-bit libgdk_pixbuf_xlib-2.0.so (but there is a 64-bit version).


Cheers,
Stephen
--
=
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia.Mobile:040 304 0583
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Upgrade to F23 breaks PERL

[Samuel Sieb]

On 09/16/2016 12:10 AM, Stephen Davies wrote:

I take it from your comment that CPAN puts things into /usr/local.


Yes.


Can I just blow away all things PERL in /usr/local and then install any
modules that go missing using dnf?


Assuming the module is packaged, you can do, for example:
dnf install 'perl(Unix::Syslog)'
If the module is not packaged, you can use 'cpanspec' to generate rpms 
that you can install.  I used that extensively for a library system I 
installed.  Some of the spec files I had to edit a bit before they would 
work and you have to package the dependencies first, but I managed to 
package all the requirements successfully.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Upgrade to F23 breaks PERL

[Stephen Davies]

On 16/09/16 15:32, Samuel Sieb wrote:

On 09/15/2016 06:04 PM, Stephen Davies wrote:

-- /usr/bin/perl: symbol lookup error:
/usr/local/lib64/perl5/auto/Unix/Syslog/Syslog.so: undefined symbol:
Perl_xs_version_bootcheck

I understand from other posts that this is probably caused by my having
two PERL installations but:

a. I have no idea why there are two PERLs
b. I can find no instructions on how to remove one version and
(hopefully) fix this issue.


Did you or some program you installed use cpan to install some modules? That's
what it looks like.  Either remove /usr/local/lib64/perl5 or rename it and see
if that fixes your problem.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

When a similar thing happened after the F22, I did load/reload some modules 
via CPAN and that fixed that.


I have since discovered that modules can be installed using dnf (though this 
is pretty well disguised) and tried that just now.


A combination of that and renaming .so files in the /usr/local/ tree seems to 
haver fixed the immediate issue but leaves the potential for it to happen 
again next time.


I take it from your comment that CPAN puts things into /usr/local.
Can I just blow away all things PERL in /usr/local and then install any 
modules that go missing using dnf?


Cheers and thanks,
Stephen

--
=
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia.Mobile:040 304 0583
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Upgrade to F23 breaks PERL

[Samuel Sieb]

On 09/15/2016 06:04 PM, Stephen Davies wrote:

-- /usr/bin/perl: symbol lookup error:
/usr/local/lib64/perl5/auto/Unix/Syslog/Syslog.so: undefined symbol:
Perl_xs_version_bootcheck

I understand from other posts that this is probably caused by my having
two PERL installations but:

a. I have no idea why there are two PERLs
b. I can find no instructions on how to remove one version and
(hopefully) fix this issue.

Did you or some program you installed use cpan to install some modules? 
That's what it looks like.  Either remove /usr/local/lib64/perl5 or 
rename it and see if that fixes your problem.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Upgrade to F23 breaks PERL

[Stephen Davies]

I have seen many posts relating to this type of issue but no canonical way to 
fix it properly.


Since updating to F23 (from F22) using dnf last night, many/all PERL programs 
are broken and give errors such as:


fetch_modules: error loading required module Compress/Zlib.pm:
  Can't load '/usr/local/lib64/perl5/auto/Compress/Raw/Zlib/Zlib.so' for 
module Compress::Raw::Zlib: libperl.so.5.20: cannot open shared object file: 
No such file or directory at /usr/lib64/perl5/DynaLoader.pm line 193.

   at /usr/local/share/perl5/Compress/Zlib.pm line 11.
  Compilation failed in require at /usr/local/share/perl5/Compress/Zlib.pm 
line 11.
  BEGIN failed--compilation aborted at 
/usr/local/share/perl5/Compress/Zlib.pm line 11.

  Compilation failed in require at /usr/sbin/amavisd line 210.
/usr/bin/perl: symbol lookup error: 
/usr/local/lib64/perl5/auto/MIME/Base64/Base64.so: undefined symbol: 
Perl_xs_version_bootcheck


or

-- /usr/bin/perl: symbol lookup error: 
/usr/local/lib64/perl5/auto/Unix/Syslog/Syslog.so: undefined symbol: 
Perl_xs_version_bootcheck


I understand from other posts that this is probably caused by my having two 
PERL installations but:


a. I have no idea why there are two PERLs
b. I can find no instructions on how to remove one version and (hopefully) fix 
this issue.


(In the meantime, I cannot run amavisd so am inundated with spam.)

TIA,
Stephen
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23: Seems sshd service not accepting connections

[Rick Stevens]

On 09/08/2016 11:43 AM, Ron Leach wrote:
> Running F23/XFCE, with firewalld, and having commanded:
> # systemctl start sshd.service
> 
> /var/log/secure
> 
> shows that sshd is opening port 22, and listening on 0.0.0.0 .
> There is no entry suggesting a login attempt is received.
> 
> In the XFCE GUI for firewalld, everything is running in zone labelled
> 'public'.
> - The network interface is bound to the zone 'public'
> - SSH service is enabled in zone 'public'
> - I've added port 22/tcp to the list of active ports in zone 'public'
> - 'Lockdown', and 'panic mode' are disabled
> 
> These settings are the same in mode 'permanent' and in mode 'runtime'
> 
> sshd config is set to listen on 0.0.0.0 (and ::).
> 
> Our LAN uses ipv4, in the range 192.168.0/24 .
> 
> This machine is connected to the network, but I cannot log in to sshd
> from any machine on the LAN.  The client times-out after a few seconds. 
> Clients do not report a 'rejection'.
> 
> If any list readers have any ideas about what else might need to be set
> up, or might be going wrong, I'd be very grateful to hear,

Have you tried to "ssh -vvv remote-ip" to see what's going on? You could
also run a tcpdump (or Wireshark) on port 22 of the machine you're
trying to connect to in order to get a trace.

The most common things I've found is that you aren't permitting the
authentication method you're trying to use in your /etc/ssh/sshd_config
file. By default, you should be allowed to log in via a username and
password. In the sshd_config file, the line is

PasswordAuthentication yes

Note that if it's not in the sshd_config file, it's enabled. However,
I've seen a lot of systems where the "PasswordAuthentication no" is set
which would require one of the other authentication methods available to
be used.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-We look for things.  Things that make us go!-
--- The "Paclyds", Star Trek TNG -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23: Seems sshd service not accepting connections

[Mark Haney]

The things I would do first thing:

Can you SSH to localhost on port 22? If not, then check to see if the port
is listening using netstat -an | grep 22
Run nmap from another system on that subnet to that machine to see if port
22 is available on the network if the above is fine.


My guess is that ssh isn't bound to the NIC and not listening on port 22.
Last resort would be to shut down the firewall and test it that way.  (If
it's a true 'public' server, I wouldn't just leave the FW down if that
fixes it.  But it will give you a place to start.)



On Thu, Sep 8, 2016 at 2:43 PM, Ron Leach  wrote:

> Running F23/XFCE, with firewalld, and having commanded:
> # systemctl start sshd.service
>
> /var/log/secure
>
> shows that sshd is opening port 22, and listening on 0.0.0.0 .
> There is no entry suggesting a login attempt is received.
>
> In the XFCE GUI for firewalld, everything is running in zone labelled
> 'public'.
> - The network interface is bound to the zone 'public'
> - SSH service is enabled in zone 'public'
> - I've added port 22/tcp to the list of active ports in zone 'public'
> - 'Lockdown', and 'panic mode' are disabled
>
> These settings are the same in mode 'permanent' and in mode 'runtime'
>
> sshd config is set to listen on 0.0.0.0 (and ::).
>
> Our LAN uses ipv4, in the range 192.168.0/24 .
>
> This machine is connected to the network, but I cannot log in to sshd from
> any machine on the LAN.  The client times-out after a few seconds.  Clients
> do not report a 'rejection'.
>
> If any list readers have any ideas about what else might need to be set
> up, or might be going wrong, I'd be very grateful to hear,
>
> Ron
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>



-- 

Mark Haney ::: Senior Systems Engineer
*VIF* *International Education*
P.O. Box 3566 ::: Chapel Hill, N.C. 27515 ::: USA
919-265-5006 office

Global learning for all.
www.viflearn.com
Find VIF on Facebook <http://facebook.com/VIFInternationalEducation> |
Twitter <https://twitter.com/vifglobaled> | LinkedIn
<http://www.linkedin.com/company/vif-international-education>

Recognized as a ‘Best for the World’
<http://bestfortheworld.bcorporation.net/> B Corp!
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F23: Seems sshd service not accepting connections

[Ron Leach]

Running F23/XFCE, with firewalld, and having commanded:
# systemctl start sshd.service

/var/log/secure

shows that sshd is opening port 22, and listening on 0.0.0.0 .
There is no entry suggesting a login attempt is received.

In the XFCE GUI for firewalld, everything is running in zone labelled 
'public'.

- The network interface is bound to the zone 'public'
- SSH service is enabled in zone 'public'
- I've added port 22/tcp to the list of active ports in zone 'public'
- 'Lockdown', and 'panic mode' are disabled

These settings are the same in mode 'permanent' and in mode 'runtime'

sshd config is set to listen on 0.0.0.0 (and ::).

Our LAN uses ipv4, in the range 192.168.0/24 .

This machine is connected to the network, but I cannot log in to sshd 
from any machine on the LAN.  The client times-out after a few 
seconds.  Clients do not report a 'rejection'.


If any list readers have any ideas about what else might need to be 
set up, or might be going wrong, I'd be very grateful to hear,


Ron
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Tim]

On Fri, 2016-08-12 at 18:03 -0400, Jon LaBadie wrote:
> Love it!!  First three responses are:
>  
>  1. Yes, designed to work that way
>  2. Not recommended
>  3. Better do a fresh install

What's wrong with that?  It contains all the answers that different
people want to hear.  ;-)

-- 

All mail to my mailbox is automatically deleted, there is no point trying
to privately email me, I will only read messages posted to the public lists.

George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Chris Murphy]

On Fri, Aug 12, 2016 at 4:03 PM, Jon LaBadie  wrote:
> On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote:
>> Planning on taking my F22 desktop to F24 soon.
>>
>> Just want to confirm that trying to skip a
>> release ist verboten. :(
>>
> Love it!!  First three responses are:
>
>  1. Yes, designed to work that way
>  2. Not recommended
>  3. Better do a fresh install
>
> :)

Well you could read mine as "upgrade should work, but might have a
rough edge here and there". The upgrade process is tested as part of
release criteria, and if it doesn't work it is release blocking. But
there's always a need for more testing of such things to find the edge
cases. And the difficulty there is most of that testing is done on
cleanly installed n-1 version. Not as much testing happens on aged n-1
systems before running the n version upgrade.

A conservative approach would be to tar up /boot and then snapshot the
'fedora-root' LV before doing the upgrade (or for Btrfs users tar
/boot and then snapshot the 'root' subvolume). I guess the drawback is
conventional LVM snapshots is that they are tedious to use: you have
to have free space in the VG already, which is not a Fedora
installation default, so that the CoW changes to the original volume
during the upgrade have somewhere to go, it's slow, and you have to
commit or reject changes at some point which is also confusing (to me
anyway). LVM thinp snapshots and Btrfs snapshots are way easier to
work with, with LVM thinp LV's totally obviating any future need to
shrink a file system as well - just fstrim it and any unused logical
extents are returned to the VG for reallocation to any other LV.

Or the conservative conventional approach is to back it all up and be
prepared to restore it if it goes badly.

So I'd say I'm closer to opinion 1 than opinion 2.


-- 
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Temlakos]

On 08/12/2016 07:51 PM, Samuel Sieb wrote:

On 08/12/2016 03:40 PM, Rick Stevens wrote:

On 08/12/2016 03:03 PM, Jon LaBadie wrote:

On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote:

Planning on taking my F22 desktop to F24 soon.

Just want to confirm that trying to skip a
release ist verboten. :(


Love it!!  First three responses are:

 1. Yes, designed to work that way
 2. Not recommended
 3. Better do a fresh install

:)


I think the real concensus is "F22->F24 is probably doable, but not
recommended". The safest way is to back up and do a fresh install.
The next best bet is to:

F22->F23
"dnf --refresh upgrade"
F23->F24

I haven't used the dnf upgrade mechanism to skip a release, but the
old fedup often times had issues doing that. Hence my reticence to
recommend it.


fedup (dnf system-upgrade) is supposed to handle that now.
--


How odd. I did a straight F22->F24 upgrade using dnf's direct commands. 
In fact, I /tried/ to go F22->F23 at first. And the network wouldn't let me.


The only problems I had:

1. The graphical interface not loading by default. One of you told me 
how to fix that.


2. A command called "systraycmd" not found when I tried to load a very 
old executable--goes back to F10--in fact it's the old pwmanager program.


If anyone can help repair /that/, I'd appreciate it.

Temlakos
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Samuel Sieb]

On 08/12/2016 03:40 PM, Rick Stevens wrote:

On 08/12/2016 03:03 PM, Jon LaBadie wrote:

On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote:

Planning on taking my F22 desktop to F24 soon.

Just want to confirm that trying to skip a
release ist verboten. :(


Love it!!  First three responses are:

 1. Yes, designed to work that way
 2. Not recommended
 3. Better do a fresh install

:)


I think the real concensus is "F22->F24 is probably doable, but not
recommended". The safest way is to back up and do a fresh install.
The next best bet is to:

    F22->F23
"dnf --refresh upgrade"
F23->F24

I haven't used the dnf upgrade mechanism to skip a release, but the
old fedup often times had issues doing that. Hence my reticence to
recommend it.


fedup (dnf system-upgrade) is supposed to handle that now.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Rick Stevens]

On 08/12/2016 03:03 PM, Jon LaBadie wrote:
> On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote:
>> Planning on taking my F22 desktop to F24 soon.
>>
>> Just want to confirm that trying to skip a
>> release ist verboten. :(
>>
> Love it!!  First three responses are:
> 
>  1. Yes, designed to work that way
>  2. Not recommended
>  3. Better do a fresh install
> 
> :)

I think the real concensus is "F22->F24 is probably doable, but not
recommended". The safest way is to back up and do a fresh install.
The next best bet is to:

F22->F23
"dnf --refresh upgrade"
F23->F24

I haven't used the dnf upgrade mechanism to skip a release, but the
old fedup often times had issues doing that. Hence my reticence to
recommend it.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Time: Nature's way of keeping everything from happening at once.  -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Jon LaBadie]

On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote:
> Planning on taking my F22 desktop to F24 soon.
> 
> Just want to confirm that trying to skip a
> release ist verboten. :(
> 
Love it!!  First three responses are:

 1. Yes, designed to work that way
 2. Not recommended
 3. Better do a fresh install

:)
-- 
Jon H. LaBadie  jo...@jgcomp.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Chris Murphy]

Upgrades are ultimately non-deterministic, for all sorts of reasons,
so at some point it makes more sense to just clean install and suffer
redoing customizations.


Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Rick Stevens]

On 08/12/2016 11:59 AM, Jon LaBadie wrote:
> Planning on taking my F22 desktop to F24 soon.
> 
> Just want to confirm that trying to skip a
> release ist verboten. :(

I don't think it's verboten, but it's not a great idea. Ideally you'd
upgrade to F23, do a full-boat update, then move on to F24.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Animal testing is futile.  They always get nervous and give the   -
- wrong answers  -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F22 -> F23 -> F24 ?

[Samuel Sieb]

On 08/12/2016 11:59 AM, Jon LaBadie wrote:

Planning on taking my F22 desktop to F24 soon.

Just want to confirm that trying to skip a
release ist verboten. :(

I believe that with F24 it was intended that going from F22 to F24 
should work.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F22 -> F23 -> F24 ?

[Jon LaBadie]

Planning on taking my F22 desktop to F24 soon.

Just want to confirm that trying to skip a
release ist verboten. :(

Jon
-- 
Jon H. LaBadie  jo...@jgcomp.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23 : DBus.Error.NoReply: can't enable bluetooth.

[sean darcy]

On 08/06/2016 03:42 PM, Jon LaBadie wrote:

On Sat, Aug 06, 2016 at 03:07:49PM -0400, sean darcy wrote:

On a dual boot lenovo laptop, bluetooth works on windows, but not fedora.

The kernel finds bluetooth:

dmesg | grep Bluet
[   16.369045] Bluetooth: Core ver 2.21
[   16.372683] Bluetooth: HCI device and connection manager initialized
[   16.373928] Bluetooth: HCI socket layer initialized
[   16.375159] Bluetooth: L2CAP socket layer initialized
[   16.376488] Bluetooth: SCO socket layer initialized
[   17.323669] Bluetooth: hci0: read Intel version: 370710010002030d56
[   17.325355] Bluetooth: hci0: Intel device is already patched. patch num:
56
[   38.998012] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   39.000420] Bluetooth: BNEP filters: protocol multicast
[   39.002702] Bluetooth: BNEP socket layer initialized
[ 4974.462452] Bluetooth: RFCOMM TTY layer initialized
[ 4974.462459] Bluetooth: RFCOMM socket layer initialized
[ 4974.462525] Bluetooth: RFCOMM ver 1.11

But on boot I get a dialog box:

org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.

and bluetoothctl doesn't scan;

show
Controller D0:7E:35:D7:9D:66
Name: lenovo.riverside
Alias: ChromeLinux_7E85
Class: 0x1c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0527
Discovering: yes
scan on
Failed to start discovery: org.bluez.Error.InProgress

Any help appreciated.


I think I got a similar message when I turned off the
bluetooth transmitter via a switch on my laptop.  It
was the "Error In Progress" that I recall.

Jon

Yes, but this is dual boot machine. BT works under windows, so it's not 
a hardware issue. Also, BT and wireless share the same hw switch. 
Wireless works fine under F23, only BT fails.


sean

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23 : DBus.Error.NoReply: can't enable bluetooth.

[Jon LaBadie]

On Sat, Aug 06, 2016 at 03:07:49PM -0400, sean darcy wrote:
> On a dual boot lenovo laptop, bluetooth works on windows, but not fedora.
> 
> The kernel finds bluetooth:
> 
> dmesg | grep Bluet
> [   16.369045] Bluetooth: Core ver 2.21
> [   16.372683] Bluetooth: HCI device and connection manager initialized
> [   16.373928] Bluetooth: HCI socket layer initialized
> [   16.375159] Bluetooth: L2CAP socket layer initialized
> [   16.376488] Bluetooth: SCO socket layer initialized
> [   17.323669] Bluetooth: hci0: read Intel version: 370710010002030d56
> [   17.325355] Bluetooth: hci0: Intel device is already patched. patch num:
> 56
> [   38.998012] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [   39.000420] Bluetooth: BNEP filters: protocol multicast
> [   39.002702] Bluetooth: BNEP socket layer initialized
> [ 4974.462452] Bluetooth: RFCOMM TTY layer initialized
> [ 4974.462459] Bluetooth: RFCOMM socket layer initialized
> [ 4974.462525] Bluetooth: RFCOMM ver 1.11
> 
> But on boot I get a dialog box:
> 
> org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
> include: the remote application did not send a reply, the message bus
> security policy blocked the reply, the reply timeout expired, or the network
> connection was broken.
> 
> and bluetoothctl doesn't scan;
> 
> show
> Controller D0:7E:35:D7:9D:66
>   Name: lenovo.riverside
>   Alias: ChromeLinux_7E85
>   Class: 0x1c010c
>   Powered: yes
>   Discoverable: no
>   Pairable: yes
>   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
>   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
>   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
>   UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
>   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
>   UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
>   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
>   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
>   UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
>   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
>   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
>   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
>   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
>   UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
>   Modalias: usb:v1D6Bp0246d0527
>   Discovering: yes
> scan on
> Failed to start discovery: org.bluez.Error.InProgress
> 
> Any help appreciated.
> 
I think I got a similar message when I turned off the
bluetooth transmitter via a switch on my laptop.  It
was the "Error In Progress" that I recall.

Jon
-- 
Jon H. LaBadie  jo...@jgcomp.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F23 : DBus.Error.NoReply: can't enable bluetooth.

[sean darcy]

On a dual boot lenovo laptop, bluetooth works on windows, but not fedora.

The kernel finds bluetooth:

dmesg | grep Bluet
[   16.369045] Bluetooth: Core ver 2.21
[   16.372683] Bluetooth: HCI device and connection manager initialized
[   16.373928] Bluetooth: HCI socket layer initialized
[   16.375159] Bluetooth: L2CAP socket layer initialized
[   16.376488] Bluetooth: SCO socket layer initialized
[   17.323669] Bluetooth: hci0: read Intel version: 370710010002030d56
[   17.325355] Bluetooth: hci0: Intel device is already patched. patch 
num: 56

[   38.998012] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   39.000420] Bluetooth: BNEP filters: protocol multicast
[   39.002702] Bluetooth: BNEP socket layer initialized
[ 4974.462452] Bluetooth: RFCOMM TTY layer initialized
[ 4974.462459] Bluetooth: RFCOMM socket layer initialized
[ 4974.462525] Bluetooth: RFCOMM ver 1.11

But on boot I get a dialog box:

org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message 
bus security policy blocked the reply, the reply timeout expired, or the 
network connection was broken.


and bluetoothctl doesn't scan;

show
Controller D0:7E:35:D7:9D:66
Name: lenovo.riverside
Alias: ChromeLinux_7E85
Class: 0x1c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0527
Discovering: yes
scan on
Failed to start discovery: org.bluez.Error.InProgress

Any help appreciated.

sean
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23, Nouveau, and GeForce 750 Ti

[Tim]

Allegedly, on or about 02 August 2016, Justin Moore sent:
> Rebooting into single user and re-doing the install process for the
> video drivers would work, but it was a real pain to do that every time
> (the power in our neighborhood is ... finicky, so reboots are sadly a
> frequent-ish occurrence).

Unless your harddrive is suffering repeated data corruption, I can't
imagine that reinstalling the same drivers over and over is *actually*
doing anything about the problem.

And I can't imagine why a power failure would be the cause of that.  The
files read for supporting the hardware were read at boot time, and
thereafter held in memory.  A crash, later on, should not have any
effect on the hard drive, other than to any files being written at the
time, or to files that have not yet been written.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

This email has been brought to you by beetwix. Mmm, spewy! Get some into
you today.


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23, Nouveau, and GeForce 750 Ti

[Robin Laing]

On 02/08/16 07:06, Justin Moore wrote:

Can anyone help me understand whether VDPAU is even supported on
my hardware/kernel/driver combination, and if so, what I need to do
to get it to work?


I don't know about that, but I do know that on F24 the nouveau driver
would freeze up solid as a rock once every few days with my 750 Ti
card, so I gave up and installed the nvidia binary drivers from
rpmfusion, which have not frozen up once.


I used the NVidia drivers for a few months, but upon every reboot
I'd get the "oh no! something has gone wrong" message:

https://ask.fedoraproject.org/en/question/69051/why-do-i-get-the-oh-no-something-has-gone-wrong-screen-when-using-the-fedora-22-live-dvd/


https://photos.google.com/share/AF1QipO54mV5FUh95O906IObqPZax_RhlM-sRV2NH6EZGTuVYsG6d9sr9P-L4YBndzSuKg?key=cmt4UFRFUkR1R1RJeUZic1ZoVkJwZHVMaWZ3MGd3

 Rebooting into single user and re-doing the install process for the
video drivers would work, but it was a real pain to do that every
time (the power in our neighborhood is ... finicky, so reboots are
sadly a frequent-ish occurrence).

I finally got tired of doing that on every reboot and decided to
switch over to Nouveau, but if Nouveau can't do things like hardware
acceleration on a two year-old card then I might have to switch back
to the NVidia drivers.

-jdm



The only issue I have had with the latest F23/24 is in F24 and the
latest kernel without signed drivers.  akmods-nvidia wouldn't allow the
module to be loaded if I had full secure boot.  If I select other OS in 
the BIOS, I have no issue loading the driver.


As I needed full acceleration with my video cards, I went with the 
rpmfusion akmods.



robin


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23, Nouveau, and GeForce 750 Ti

[Justin Moore]

>
> > Can anyone help me understand whether VDPAU is even supported on my
> > hardware/kernel/driver combination, and if so, what I need to do to get
> it
> > to work?
>
> I don't know about that, but I do know that on F24 the nouveau
> driver would freeze up solid as a rock once every few days
> with my 750 Ti card, so I gave up and installed the nvidia
> binary drivers from rpmfusion, which have not frozen up once.
>

I used the NVidia drivers for a few months, but upon every reboot I'd get
the "oh no! something has gone wrong" message:

https://ask.fedoraproject.org/en/question/69051/why-do-i-get-the-oh-no-something-has-gone-wrong-screen-when-using-the-fedora-22-live-dvd/

https://photos.google.com/share/AF1QipO54mV5FUh95O906IObqPZax_RhlM-sRV2NH6EZGTuVYsG6d9sr9P-L4YBndzSuKg?key=cmt4UFRFUkR1R1RJeUZic1ZoVkJwZHVMaWZ3MGd3

Rebooting into single user and re-doing the install process for the video
drivers would work, but it was a real pain to do that every time (the power
in our neighborhood is ... finicky, so reboots are sadly a frequent-ish
occurrence).

I finally got tired of doing that on every reboot and decided to switch
over to Nouveau, but if Nouveau can't do things like hardware acceleration
on a two year-old card then I might have to switch back to the NVidia
drivers.

-jdm


> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F23, Nouveau, and GeForce 750 Ti

[Tom Horsley]

On Tue, 2 Aug 2016 08:35:40 -0400
Justin Moore wrote:

> Can anyone help me understand whether VDPAU is even supported on my
> hardware/kernel/driver combination, and if so, what I need to do to get it
> to work?

I don't know about that, but I do know that on F24 the nouveau
driver would freeze up solid as a rock once every few days
with my 750 Ti card, so I gave up and installed the nvidia
binary drivers from rpmfusion, which have not frozen up once.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F23, Nouveau, and GeForce 750 Ti

[Justin Moore]

I have a GeForce 750 Ti card and I'm having issues with stability and
features with the nouveau driver on Fedora 23. Per lspci, I have

NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)

and kernel 4.6.4-201.fc23.x86_64. It appears that I'm running into the same
(or a similar) issue as here:

https://bugs.freedesktop.org/show_bug.cgi?id=95251

I can get it to work on each output port (DisplayPort, HDMI, and DVI) and
I'm driving all three monitors simultaneously. However vdpauinfo shows that
none of the hardware acceleration is working:

Decoder capabilities:

namelevel macbs width height

MPEG1  --- not supported ---
MPEG2_SIMPLE   --- not supported ---
MPEG2_MAIN --- not supported ---
[ etc etc ]

When I start X I do see this message:

[26.829] (II) modeset(0): [DRI2]   VDPAU driver: nouveau

but I also see this repeated a few times:

[26.355] (EE) Unknown chipset: NV117

I'm getting conflicting messages from Freedesktop.org about whether this
should work at all, so I can't tell if this is an upstream issue or a
Fedora issue. I have a 750 Ti, which per

https://nouveau.freedesktop.org/wiki/CodeNames/#NV110

is the Maxwell chipset NV117 with the GM107 chipset.

The video acceleration matrix

https://nouveau.freedesktop.org/wiki/VideoAcceleration/

seems to indicate that this is VP6, and everything is TODO. However the
main Nouveau wiki page at https://nouveau.freedesktop.org/wiki/ has this
entry:

* Apr, 2015: GM107 acceleration support merged into 4.1

and

https://www.phoronix.com/scan.php?page=news_item&px=GTX-750-Nouveau-Linux-4.1-Try

indicates that as of 4.1 acceleration should start to work. I'm on kernel
4.6.4.

Can anyone help me understand whether VDPAU is even supported on my
hardware/kernel/driver combination, and if so, what I need to do to get it
to work?

Thanks,
-jdm
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: captive portal SSL certificate issue on F23

[Frederic Muller]

On 07/09/2016 03:55 PM, Fernando Cassia wrote:
> 
> On Fri, Jul 8, 2016 at 5:20 AM, Frederic Muller  <mailto:f...@cm17.com>> wrote:
> 
> I am on F23 at the moment
> 
> 
> You dont say which browser you use, and Fedora flavor.
> For instance, on Fedora XFCE, the default browser is Midori.
> On more vanila Fedora versions, its usually Firefox
> 
> FC
> 
> 
> -- 
> During times of Universal Deceit, telling the truth becomes a
> revolutionary act
> Durante épocas de Engaño Universal, decir la verdad se convierte en un
> Acto Revolucionario
> - George Orwell
> 

The thing is it is not coming from the browser. Network manager has a
component which handle that "captive portal page". So my browser is not
launched at all. Basically when the computer connects to the wifi
network Network Manager launched a "browser like" application and
display the captive portal page. I have found some bugs affecting that
part which are 6+ months old but do not help me with my problem.

Bug I am talking about is:
https://bugzilla.redhat.com/show_bug.cgi?id=1252839

Thank you.

And I am using GNOME as a DE.

Fred
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: captive portal SSL certificate issue on F23

[Fernando Cassia]

On Fri, Jul 8, 2016 at 5:20 AM, Frederic Muller  wrote:

> I am on F23 at the moment


You dont say which browser you use, and Fedora flavor.
For instance, on Fedora XFCE, the default browser is Midori.
On more vanila Fedora versions, its usually Firefox

FC


-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: captive portal SSL certificate issue on F23

[Frederic Muller]

On 07/08/2016 03:20 PM, Frederic Muller wrote:
> Hi!
> 
> So everything was working well until maybe 4-5 days ago. Now I am
> systematically getting a SSL certificate error regardless of the captive
> portal I go to, and thus blocking me from identifying and using the
> internet on that connection. Any idea what this could be and how to
> "clean it up" to go back to the working mode ;-)
> 
> I am on F23 at the moment.
> 
> Thank you.
> 
> Fred
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
> 

Hi again!

I can see my problem is not affecting a lot of people. I wanted to
correct the post and mention the exact error message as
"Unacceptable TLS certificate"

Does this help?

Thanks.

Fred
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

captive portal SSL certificate issue on F23

[Frederic Muller]

Hi!

So everything was working well until maybe 4-5 days ago. Now I am
systematically getting a SSL certificate error regardless of the captive
portal I go to, and thus blocking me from identifying and using the
internet on that connection. Any idea what this could be and how to
"clean it up" to go back to the working mode ;-)

I am on F23 at the moment.

Thank you.

Fred
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Strange messages from sudo dnf repoquery --unsatisfied after upgrade from F23 to F24.

[Stephen Morris]

On 08/07/16 08:11, Rick Stevens wrote:

On 07/07/2016 02:51 PM, Stephen Morris wrote:

On 07/07/16 09:49, Ed Greshko wrote:

On 07/07/16 06:10, Stephen Morris wrote:

Thanks Ed. I issued the command and got back Packager: None.
I then tried the same command on a package that I know only exists in
the Negativo17
repositories and that gave the same response of Packager : None.

Another option...

dnf info kmod-nvidia

Thanks Ed, I tried that command and it did tell me that it was indeed
installed and which repository it came from. I then tried a dnf info
kmod-nvidia* which showed me all the associated packages from the
Negativo17 and Rpmfusion repositories. It also told me that the
kmod-nvidia-$(uname -r) packages were installed and came from repository
@commandline, which I assume means they were compiled, which surprised
me because I thought the purpose of the kmod-nvidia metadata package was
to pull in and install the pre-compiled nvidia binary packages matching
the kernel, is that not correct?

"@@commandline" means that the RPM was installed from an RPM residing on
the local disk and not from the web. Any time you install an RPM from
a local disk file (regardless of where you downloaded it from), it will
appear to come from the "@@comandline" repo since dnf didn't go out and
fetch the RPM itself.
Thanks Rick, I had installed those packages manually at one point 
because the upgrade broke Xorg both for the nvidia packages an nouveau, 
but I thought I had uninstalled the manually installed versions before I 
eventually got to the install method that enabled the nvidia packages to 
work.



I also thought the akmod-nvidia package was in both the Negativo17 and
Rpmfusion repositories, but when I issue 'dnf info akmod-nvidia' it only
shows me information relative the installed version that came from the
Negativo17 repository. Shouldn't it have told me that there was an
installed version that came from the Negativo17 repository and an
uninstalled version in the Rpmfusion repository?

I would think under "Installed Packages" it would list the installed
one from "@@commandline" and under "Available Packages" the ones
available from Negativo17 and rpmfusion.

I'm not running akmod-nvidia on my F23 box, but searching for any
"akmod*" stuff:

[root@prophead ~]# dnf list akmod*
Last metadata expiration check: 0:06:56 ago on Thu Jul  7 14:51:02 2016.
Installed Packages
akmod-VirtualBox.x86_64 5.0.16-2.fc23  @@commandline
akmods.noarch   0.5.4-2.fc23   @@commandline
Available Packages
akmod-ndiswrapper.x86_641.60-1.fc23rpmfusion-free
akmod-nvidia.x86_64 1:358.16-1.fc23rpmfusion-nonfree
akmod-nvidia-304xx.x86_64   304.131-2.fc23 rpmfusion-nonfree
akmod-nvidia-340xx.x86_64   1:340.96-1.fc23rpmfusion-nonfree
akmod-wl.x86_64 6.30.223.271-4.fc23rpmfusion-nonfree
akmod-xtables-addons.x86_64 2.10-1.fc23rpmfusion-free

Yes, the akmod-VirtualBox and akmods.noarch were installed from RPMs I
had downloaded previously.
From the command you have listed and what the same command shows on my 
system, is that the akmod-nvidia packages in the two repositories are 
named differently, I thought they were the same name.


regards,
Steve




Just relative to the 2nd message in my original thread, isn't that
message for the standard F24 kernel, saying that it has an unsatisfiable
dependency on the associated kernel-core package? My issue with that is
if that is the case, how and why did a 'sudo dnf upgrade' issued the day
after the upgrade install that kernel, because I believe the missing
dependency should have stopped it from being installed, or am I missing
something?

regards,
Steve

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Strange messages from sudo dnf repoquery --unsatisfied after upgrade from F23 to F24.

[Rick Stevens]

On 07/07/2016 02:51 PM, Stephen Morris wrote:
> On 07/07/16 09:49, Ed Greshko wrote:
>>
>> On 07/07/16 06:10, Stephen Morris wrote:
>>> Thanks Ed. I issued the command and got back Packager: None.
>>> I then tried the same command on a package that I know only exists in
>>> the Negativo17
>>> repositories and that gave the same response of Packager : None.
>> Another option...
>>
>> dnf info kmod-nvidia
> Thanks Ed, I tried that command and it did tell me that it was indeed
> installed and which repository it came from. I then tried a dnf info
> kmod-nvidia* which showed me all the associated packages from the
> Negativo17 and Rpmfusion repositories. It also told me that the
> kmod-nvidia-$(uname -r) packages were installed and came from repository
> @commandline, which I assume means they were compiled, which surprised
> me because I thought the purpose of the kmod-nvidia metadata package was
> to pull in and install the pre-compiled nvidia binary packages matching
> the kernel, is that not correct?

"@@commandline" means that the RPM was installed from an RPM residing on
the local disk and not from the web. Any time you install an RPM from
a local disk file (regardless of where you downloaded it from), it will
appear to come from the "@@comandline" repo since dnf didn't go out and
fetch the RPM itself.

> I also thought the akmod-nvidia package was in both the Negativo17 and
> Rpmfusion repositories, but when I issue 'dnf info akmod-nvidia' it only
> shows me information relative the installed version that came from the
> Negativo17 repository. Shouldn't it have told me that there was an
> installed version that came from the Negativo17 repository and an
> uninstalled version in the Rpmfusion repository?

I would think under "Installed Packages" it would list the installed
one from "@@commandline" and under "Available Packages" the ones
available from Negativo17 and rpmfusion.

I'm not running akmod-nvidia on my F23 box, but searching for any
"akmod*" stuff:

[root@prophead ~]# dnf list akmod*
Last metadata expiration check: 0:06:56 ago on Thu Jul  7 14:51:02 2016.
Installed Packages
akmod-VirtualBox.x86_64 5.0.16-2.fc23  @@commandline
akmods.noarch   0.5.4-2.fc23   @@commandline
Available Packages
akmod-ndiswrapper.x86_641.60-1.fc23rpmfusion-free
akmod-nvidia.x86_64 1:358.16-1.fc23rpmfusion-nonfree
akmod-nvidia-304xx.x86_64   304.131-2.fc23 rpmfusion-nonfree
akmod-nvidia-340xx.x86_64   1:340.96-1.fc23rpmfusion-nonfree
akmod-wl.x86_64 6.30.223.271-4.fc23rpmfusion-nonfree
akmod-xtables-addons.x86_64 2.10-1.fc23rpmfusion-free

Yes, the akmod-VirtualBox and akmods.noarch were installed from RPMs I
had downloaded previously.

> Just relative to the 2nd message in my original thread, isn't that
> message for the standard F24 kernel, saying that it has an unsatisfiable
> dependency on the associated kernel-core package? My issue with that is
> if that is the case, how and why did a 'sudo dnf upgrade' issued the day
> after the upgrade install that kernel, because I believe the missing
> dependency should have stopped it from being installed, or am I missing
> something?
> 
> regards,
> Steve
> 
> -- 
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org


-- 
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   "As for me, I aspire to be the Walmart Greeter in Hell." -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Strange messages from sudo dnf repoquery --unsatisfied after upgrade from F23 to F24.

[Stephen Morris]

On 07/07/16 09:49, Ed Greshko wrote:


On 07/07/16 06:10, Stephen Morris wrote:

Thanks Ed. I issued the command and got back Packager: None.
I then tried the same command on a package that I know only exists in the 
Negativo17
repositories and that gave the same response of Packager : None.

Another option...

dnf info kmod-nvidia
Thanks Ed, I tried that command and it did tell me that it was indeed 
installed and which repository it came from. I then tried a dnf info 
kmod-nvidia* which showed me all the associated packages from the 
Negativo17 and Rpmfusion repositories. It also told me that the 
kmod-nvidia-$(uname -r) packages were installed and came from repository 
@commandline, which I assume means they were compiled, which surprised 
me because I thought the purpose of the kmod-nvidia metadata package was 
to pull in and install the pre-compiled nvidia binary packages matching 
the kernel, is that not correct?


I also thought the akmod-nvidia package was in both the Negativo17 and 
Rpmfusion repositories, but when I issue 'dnf info akmod-nvidia' it only 
shows me information relative the installed version that came from the 
Negativo17 repository. Shouldn't it have told me that there was an 
installed version that came from the Negativo17 repository and an 
uninstalled version in the Rpmfusion repository?


Just relative to the 2nd message in my original thread, isn't that 
message for the standard F24 kernel, saying that it has an unsatisfiable 
dependency on the associated kernel-core package? My issue with that is 
if that is the case, how and why did a 'sudo dnf upgrade' issued the day 
after the upgrade install that kernel, because I believe the missing 
dependency should have stopped it from being installed, or am I missing 
something?


regards,
Steve

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org