Re: LibreOffice failing on both fc27 and fc26

2017-03-18 Thread Viorel Tabara 
On Thu Mar 16 2017 18:21:26 GMT-0600 (MDT) GERHARD GOETZHABER 
 wrote:
> since KDE has become nothing more than a tragedy

That's an unfair statement to KDE maintainers who do put a lot of effort 
and have provided the open source community with awesome software. The 
least you can do is switch to an environment that suits you. The most 
you can do is lend a hand. But statement like that one aren't helping.

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

Re: LibreOffice failing on both fc27 and fc26

2017-03-18 Thread Viorel Tabara 
On Sat Mar 18 2017 16:05:39 GMT-0600 (MDT) GERHARD GOETZHABER 
 wrote:
> Though I'd like to know what was wrong before ...

Apparently no one else has run into similar issue so that'd be hard to 
troubleshoot. It's also pointless, given that the new install is working 
fine. A wild guess would be "user error".

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

Re: LibreOffice failing on both fc27 and fc26

2017-03-17 Thread Viorel Tabara 
On Thu Mar 16 2017 19:21:04 GMT-0600 (MDT) GERHARD GOETZHABER 
 wrote:
> However, even disabling SElinux followed by reboot didn't help ...

Sorry I missed this in my previous reply...as a general rule you don't 
want to disable SELinux, rather turn on permissive mode, or if something 
is really obstructing your work add a custom module as instructed.

Note that since you've been running with SELinux disabled it's a good 
practice to force a relabel on your next system reboot.

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

Re: LibreOffice failing on both fc27 and fc26

2017-03-17 Thread Viorel Tabara 
On Thu Mar 16 2017 19:21:04 GMT-0600 (MDT) GERHARD GOETZHABER 
 wrote:
> I got the following SElinux alert:
> 
> SELinux is preventing (ostnamed) from mounton access on the file 
> /proc/mtrr.

https://bugzilla.redhat.com/show_bug.cgi?id=1411360

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

Re: DNS not working in 0225 compose

2017-02-26 Thread Viorel Tabara 
On Sat Feb 25 2017 21:20:27 GMT-0700 (MST) Bowen Wang 
 wrote: 
> Also when I try to open the network manager, I found I can't open it.  
> I can see it in the application menu, but when I tried to open it, it 
> is just cannot be opened.

Do 'nmcli device show' and 'ip a' show any interfaces? Do 'systemctl 
status NetworkManager.service' and 'journalctl -b' show any errors?

> Maybe the network driver is down? 

That's the first thing I would check but you've got no running 
NetworkManager and my knowledge isn't good enough to explain how it ties 
into the kernel.

'lspci -vvv' is one way to view the kernel module for your network 
interface(s) or use  'ethtool -i' with the network devices listed by the 
commands above. Try it with both working and non-working kernels.

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

Re: DNS not working in 0225 compose

2017-02-25 Thread Viorel Tabara 
On Sat Feb 25 2017 10:22:17 GMT-0700 (MST) Bowen Wang 
 wrote: 
> ping www.google.com the terminal says that the service is unknown.

The message indicates that your network is "down". Since the other 
kernel works I would suspect the network driver for your wireless or 
wired interface. Does testing with the "other" interface -- wired or 
wireless -- produce the same result?

NetworkManager applet should give visual clues about connection status, 
or from a terminal use 'nmcli' or 'ip'. Also check the system logs for 
any errors related to network stack.

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

Re: Moan about dnf on Rawhide

2017-02-20 Thread Viorel Tabara 
On Mon Feb 20 2017 10:16:42 GMT-0700 (MST) Adam Williamson 
 wrote: 
> On Mon, 2017-02-20 at 17:46 +0100, Ralf Corsepius wrote: 
>> The person, who added this  prerequisite, should leave Fedora, 
>> IMNSHO. 
>  
> This kind of tone is unacceptable and a clear violation of the Code of 
> Conduct: 
>  
> https://getfedora.org/code-of-conduct 
>  
> "Be respectful. Not all of us will agree all the time, but 
> disagreement is no excuse for poor behavior and poor manners. We might 
> all experience some frustration now and then, but we cannot allow that 
> frustration to turn into a personal attack." 
>  
> I'm placing you on moderation for this list. 
>  
 
+1 and thanks.

On a related note, Rawhide documentation is clear about the risks of 
running an non-stable version [1].

-- 
Viorel

[1]:https://fedoraproject.org/wiki/Releases/Rawhide 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Moan about dnf on Rawhide

2017-02-19 Thread Viorel Tabara 
On Sun Feb 19 2017 11:23:24 GMT-0700 (MST) stan 
 wrote: 
> I ran a dnf --best update and there are 317 errors, and dnf skips 
> everything.  :-)   
[...] 
> I suppose I'll be forced to --allowerasing if I want to do a dnf 
> update.  Or force install the dnf dependencies of the new 3.6 ABI so I 
> can then run dnf update and have it update everything else. 
>  
> What a mess.  Maybe a new install of rawhide would be easier. 
 
Or use the rpmdb from a backup as a reference to bring the system to  
that state. 
 
On a related note, I recall a discussion somewhere on the Fedora mailing  
lists, about doing an LVM snapshot of rootfs prior to upgrading as an  
easy way to roll back. 
 
--  
Viorel 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Moan about dnf on Rawhide

2017-02-19 Thread Viorel Tabara 
On Sun Feb 19 2017 09:50:24 GMT-0700 (MST) stan 
 wrote: 
> Not here.  I tried all kinds of variations of the above, and I keep 
> getting errors.

I prefer to keep the Koji URL as a visual clue in dnf history:

   [root@omiday ~]# dnf history dnf
   Last metadata expiration check: 2:11:01 ago on Sun Feb 19 11:40:53 2017 MST.
   ID | Command line | Date and time| Action(s)  | 
Altered
   
---
  323 | install https://kojipkgs | 2017-02-17 22:55 | Update |7 
 <
  322 | upgrade dnf  | 2017-02-17 22:50 | Update |9 
> 
  275 | -y upgrade   | 2017-01-01 20:31 | I, O, U|  708 
EE
  265 | upgrade  | 2016-12-19 13:38 | E, I, O, U |  615 
EE
  227 | --releasever=rawhide sys | 2016-11-24 17:55 | D, E, I, O, U  | 1358 
EE
  200 | -y upgrade   | 2016-10-20 10:59 | E, I, U|  146 
  
  145 | upgrade  | 2016-09-15 20:22 | E, I, O, U |  209 
EE
  117 | --nogpgcheck upgrade | 2016-08-20 16:33 | E, I, U|   91 
  
  100 | --releasever=25 system-u | 2016-08-11 13:56 | D, E, I, O, U  | 1492 
EE
  1 |  | 2016-06-14 10:31 | Install| 1364 EE

It does take me a bit longer to build the dependency list but it's not 
something that bothers me that much, I rarely rely on Koji RPMs:

   [root@omiday ~]# dnf history info 323
   Last metadata expiration check: 2:11:12 ago on Sun Feb 19 11:40:53 2017 MST.
   Transaction ID : 323
   Begin time : Fri Feb 17 22:55:16 2017
   Begin rpmdb: 2651:a559e374360c3500f0c5d574f47f2d81aab6a6ab
   End time   :22:55:23 2017 (7 seconds)
   End rpmdb  : 2652:70ab883f3c3b46c029d1650e7d60b5571e6df359
   User   :  
   Return-Code: Success
   Command Line   : install 
https://kojipkgs.fedoraproject.org//packages/dnf/2.1.0/1.fc26/noarch/dnf-2.1.0-1.fc26.noarch.rpm
 
https://kojipkgs.fedoraproject.org//packages/dnf/2.1.0/1.fc26/noarch/python2-dnf-2.1.0-1.fc26.noarch.rpm
 
https://kojipkgs.fedoraproject.org//packages/dnf/2.1.0/1.fc26/noarch/dnf-conf-2.1.0-1.fc26.noarch.rpm
 
https://kojipkgs.fedoraproject.org//packages/dnf/2.1.0/1.fc26/noarch/python3-dnf-2.1.0-1.fc26.noarch.rpm
 
https://kojipkgs.fedoraproject.org//packages/yum/3.4.3/512.fc26/noarch/yum-3.4.3-512.fc26.noarch.rpm
 
https://kojipkgs.fedoraproject.org//packages/dnf/2.1.0/1.fc26/noarch/dnf-automatic-2.1.0-1.fc26.noarch.rpm
 
https://kojipkgs.fedoraproject.org//packages/dnf/2.1.0/1.fc26/noarch/dnf-yum-2.1.0-1.fc26.noarch.rpm
   Transaction performed with:
  Upgraded  dnf-2.0.1-2.fc26.noarch   @rawhide
  Installed rpm-4.13.0-11.fc26.x86_64 @rawhide
   Packages Altered:
  Upgraded dnf-2.0.1-2.fc26.noarch   @rawhide
  Upgrade  2.1.0-1.fc26.noarch   @@commandline
  Upgraded dnf-automatic-2.0.1-2.fc26.noarch @rawhide
  Upgrade2.1.0-1.fc26.noarch @@commandline
  Upgraded dnf-conf-2.0.1-2.fc26.noarch  @rawhide
  Upgrade   2.1.0-1.fc26.noarch  @@commandline
  Upgraded dnf-yum-2.0.1-2.fc26.noarch   @rawhide
  Upgrade  2.1.0-1.fc26.noarch   @@commandline
  Upgraded python2-dnf-2.0.1-2.fc26.noarch   @rawhide
  Upgrade  2.1.0-1.fc26.noarch   @@commandline
  Upgraded python3-dnf-2.0.1-2.fc26.noarch   @rawhide
  Upgrade  2.1.0-1.fc26.noarch   @@commandline
  Upgraded yum-3.4.3-511.fc26.noarch @@commandline/rawhide
  Upgrade  3.4.3-512.fc26.noarch @@commandline

> # dnf install ./dnf-2.1.0-1.fc26.noarch.rpm 
> ./python3-dnf-2.1.0-1.fc26.noarch.rpm --allowerasing

I try to stay away from  "allowerasing" -- once I had to go through a 
massive rpm-fu work. It was fun but time consuming.

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

Re: Moan about dnf on Rawhide

2017-02-17 Thread Viorel Tabara 
On Fri Feb 17 2017 22:43:55 GMT-0700 (MST) Russel Winder 
 wrote: 
> [root@anglides ~]# dnf list kernel ArgumentError: argument 
> --obsoletes: conflicting option string: -- obsoletes [root@anglides 
> ~]#  
>  
> This has been happening for a while now. Given that dnf is so critical 
> to updating Rawhide I would not have expected this to be the case. 

Upgrading to latest from Koji fixed it for me:

   [root@omiday ~]# dnf list kernel
   Last metadata expiration check: 1:34:19 ago on Fri Feb 17 21:21:08 2017 MST.
   Installed Packages
   kernel.x86_64  4.10.0-0.rc4.git2.1.fc26  @rawhide
   kernel.x86_64  4.10.0-0.rc6.git0.1.fc26  @rawhide
   kernel.x86_64  4.10.0-0.rc7.git1.1.fc26  @rawhide
   Available  Packages
   kernel.x86_64  4.10.0-0.rc8.git0.1.fc26  rawhide

   [root@omiday ~]# rpm -q dnf
   dnf-2.1.0-1.fc26.noarch

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

Re: a couple of issues with Lmod and 'man' bash completion

2017-01-19 Thread Viorel Tabara 
On Wed Jan 18 2017 05:45:17 GMT-0700 (MST) Patrick O'Callaghan 
 wrote:
> Since you're running F25, the appropriate forum is the Users list, not the
> Test list.

I'm not looking for user support, rather I want to confirm a bug [1].

> The Test list is for unreleased versions.

Actually there have been plenty of discussions on this list about current 
Fedora releases. Now back to the point in question -- I run one Rawide 
installation, where I first noticed the issue. To reliably test/troubleshoot I 
needed two machines running an identical OS version.

-- 
Viorel

[1]:https://lists.fedoraproject.org/archives/
- us...@lists.fedoraproject.org -- Community support for Fedora users
- test@lists.fedoraproject.org  -- For testing and quality assurance of Fedora 
  releases 
:wq
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

a couple of issues with Lmod and 'man' bash completion

2017-01-17 Thread Viorel Tabara 
Hello,

The first issue has to do with 'man' tab completion not working when 'Lmod' 
package is installed. To debug I enabled expansion in the interactive shell on 
two systems -- a working one shown below as 'mha' and the broken one ('pc96'), 
both running F25 up to date:

set -x

followed by:

man dnf
Ctrl-C

and then diff-ing the output:

   omiday ~ $ diff _man-mha _man-pc96 
   1c1
   < mha ~ $ man dnf+ local cmd=man
   ---
   > pc96 ~ $ man dnf+ local cmd=man
   248,252c248,250
   < + local manpath=
   < + [[ -z '' ]]
   < ++ manpath
   < + manpath=/usr/local/share/man:/usr/share/man
   < + [[ -z /usr/local/share/man:/usr/share/man ]]
   ---
   > + local manpath=/usr/share/lmod/lmod/share/man::
   > + [[ -z /usr/share/lmod/lmod/share/man:: ]]
   > + [[ -z /usr/share/lmod/lmod/share/man:: ]]
   256c254
   < + manpath=/usr/local/share/man:/usr/share/man:
   ---
   > + manpath=/usr/share/lmod/lmod/share/man:::
   258c256
   < + manpath='/usr/local/share/man/*man*/dnf* /usr/share/man/*man*/dnf*  
/usr/local/share/man/*cat*/dnf* /usr/share/man/*cat*/dnf* '
   ---
   > + manpath='/usr/share/lmod/lmod/share/man/*man*/dnf* /*man*/dnf* 
/*man*/dnf*  /usr/share/lmod/lmod/share/man/*cat*/dnf* /*cat*/dnf* /*cat*/dnf* '
   260c258
   < ++ eval command ls '/usr/local/share/man/*man*/dnf* 
/usr/share/man/*man*/dnf*  /usr/local/share/man/*cat*/dnf* 
/usr/share/man/*cat*/dnf* '
   ---
   > ++ eval command ls '/usr/share/lmod/lmod/share/man/*man*/dnf* /*man*/dnf* 
/*man*/dnf*  /usr/share/lmod/lmod/share/man/*cat*/dnf* /*cat*/dnf* /*cat*/dnf* '
   266c264
   < + local i start=11
   ---
   > + local i start=0
   289,290c287,288
   < + (( i=11 ))
   < + (( i < 11 ))
   ---
   > + (( i=0 ))
   > + (( i < 0 ))
 
I'm still unclear whether the non-empty 'manpath' interfering with 'man' tab 
completion is a bug in Lmod or in Bash completion but unset-ing MANPATH (which 
is where 'manpath' is initialized from) *before* 'man dnf' (completion 
loading here is lazy) effectively fixes the tab completion. I can investigate 
further if needed but I'm hoping someone more knowledgeable will chime in.

Second issue: Lmod is required by python3-sphinx on Rawhide but not on F25 --  
here's the output from those two systems:

   omiday ~ $ rpm -qR python3-sphinx
   /bin/sh
   /usr/bin/python3
   /usr/sbin/alternatives
   Lmod
   config(python3-sphinx) = 1.5.1-1.fc26
   python(abi) = 3.6
   python-sphinx-locale = 1.5.1-1.fc26
   python3-babel
   python3-docutils
   python3-imagesize
   python3-jinja2
   python3-mock
   python3-pygments
   python3-requests
   python3-six
   python3-snowballstemmer
   python3-sphinx-theme-alabaster
   python3-sphinx_rtd_theme
   rpmlib(CompressedFileNames) <= 3.0.4-1
   rpmlib(FileDigests) <= 4.6.0-1
   rpmlib(PayloadFilesHavePrefix) <= 4.0-1
   rpmlib(PayloadIsXz) <= 5.2-1

   pc96 ~ $ rpm -qR python3-sphinx
   /bin/sh
   /bin/sh
   /usr/bin/python3
   /usr/sbin/update-alternatives
   /usr/sbin/update-alternatives
   python(abi) = 3.5
   python-sphinx-locale = 1.4.8-2.fc25
   python3-babel
   python3-docutils
   python3-imagesize
   python3-jinja2
   python3-mock
   python3-pygments
   python3-six
   python3-snowballstemmer
   python3-sphinx-theme-alabaster
   python3-sphinx_rtd_theme
   rpmlib(CompressedFileNames) <= 3.0.4-1
   rpmlib(FileDigests) <= 4.6.0-1
   rpmlib(PayloadFilesHavePrefix) <= 4.0-1
   rpmlib(PayloadIsXz) <= 5.2-1


If any of those are bugs please let me know under which component they should 
be filed under and I can do that myself. And assuming that the bash completion 
isn't a bug any pointers on how to fix it are more than welcome.

Thanks much.

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

rawhide - SELinux is preventing sshd from name_connect access on the tcp_socket port 5901

2016-12-03 Thread Viorel Tabara 
I hit this when connecting to a VNC session via SSH port forwarding:

Dec 03 18:25:54 omiday.can.local audit[2665]: AVC avc:  denied  { name_connect 
} for  pid=2665 comm="sshd" dest=5901 
scontext=system_u:system_r:sshd_t:s0-s0:c0.c1023 
tcontext=system_u:object_r:vnc_port_t:s0 tclass=tcp_socket permissive=1
Dec 03 18:25:57 omiday.can.local dbus-daemon[5699]: [system] Activating service 
name='org.fedoraproject.Setroubleshootd' requested by ':1.147' (uid=0 pid=5650 
comm="/usr/sbin/sedispatch " label="system_u:system_r:audisp_t:s0") (using 
servicehelper)
Dec 03 18:25:58 omiday.can.local dbus-daemon[5699]: [system] Successfully 
activated service 'org.fedoraproject.Setroubleshootd'
Dec 03 18:25:58 omiday.can.local setroubleshoot[22291]: SELinux is preventing 
sshd from name_connect access on the tcp_socket port 5901. For complete SELinux 
messages. run sealert -l 208a9002-1dee-43dc-b50a-d37538df836a
Dec 03 18:25:58 omiday.can.local python3[22291]: SELinux is preventing sshd 
from name_connect access on the tcp_socket port 5901.

 *  Plugin catchall (100. 
confidence) suggests   **

 If you believe that sshd 
should be allowed name_connect access on the port 5901 tcp_socket by default.
 Then you should report this as 
a bug.
 You can generate a local 
policy module to allow this access.
 Do
 allow this access for now by 
executing:
 # ausearch -c 'sshd' --raw | 
audit2allow -M my-sshd
 # semodule -X 300 -i my-sshd.pp

If it's a bug I can file it in Bugzilla.

Thanks.

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

adding gpg import step to dnf upgrade wiki?

2016-11-22 Thread Viorel Tabara 
This occurred to me while I was upgrading using the CLI instructions [1] and 
got prompted with:

   [SKIPPED] sudo-1.8.18p1-1.fc25.i686.rpm: Already downloaded
   [SKIPPED] the_silver_searcher-0.33.0-1.fc25.i686.rpm: Already downloaded
   [SKIPPED] tzdata-2016i-1.fc25.noarch.rpm: Already downloaded
   [SKIPPED] tzdata-java-2016i-1.fc25.noarch.rpm: Already downloaded
   warning: /var/lib/dnf/system-upgrade/dmidecode-3.0-5.fc25.i686.rpm: Header 
V3 RSA/SHA256 Signature, key ID fdb19c98: NOKEY
   Importing GPG key 0xFDB19C98:
   Userid : "Fedora 25 Primary (25) "
   Fingerprint: C437 DCCD 558A 66A3 7D6F 4372 4089 D8F2 FDB1 9C98
   From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-i386
   Is this ok [y/N]: y
   Key imported successfully
   Running transaction check
   Transaction check succeeded.
   Running transaction test

Since the installation instructions urge users to validate the download [2] 
would it make sense to add something similar [3] to the DNF wiki as the very 
first step?

-- 
Viorel

[1]:https://fedoraproject.org/wiki/DNF_system_upgrade
[2]:https://getfedora.org/en/workstation/download/ws-download-splash
[3]:https://getfedora.org/en/verify 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Hail Mary by 20161008.n.0 updates - kernel 4.9 git4 fully o.k.!

2016-10-09 Thread Viorel Tabara 
On Sun Oct 09 2016 03:53:51 GMT-0600 (MDT) GERHARD GOETZHABER 
 wrote:
> Hi, fellas!
> 
> I can't do but immediately report this success:
> The boot process now not only goes without any failure note but even faster 
> than ever before, and so far I can see up to the first minutes after update 
> and rebooting everything is working excellently!
> 
> Basic hardware: Sabertooth FX990 1st gen., FX6300 slightly tuned up, 
> SuperTrak EX8760T (SAS RAID PCIe 2.0 x8 controller based on a PMC Sierra 
> chip) running 3+1spare 6Gb/s SAS drives à 1 TB assembled as a RAID 5 array, 
> R7 260X featuring two monitors (main on DP, second on DVI), 1 6 Gb/s SATA 2 
> TB drive and 1 6 Gb/s SSD 256 GB on motherboard's AMD controller
> Periphery: Eaton Ellipse ECO 1200 UPS, Canon I-sensys LBP7100Cn, Epson 
> Perfection V370 Photo
> Fedora, as always done by me, is set up from a USB 3 stick containing an 
> Everything ISO, KDE environment with MM support and admin tools as well as 
> LibreOffice primarily chosen.
> Other software: Firefox Developer Edition, Mozilla Earlybird, mc, gparted, 
> Yakuake, Ffmpeg compiled in by myself, all Gstreamer plugins, extra K3b 
> codecs and so on, Audacious with Freeworld plugins, Audacity Freeworld, 
> Handbrake, Openshot, Gimp, Inkscape, Bluefish
> 
> Great work!
> 
> Be the Ancients with ye,
> 
> Geri Goetzhaber

Great news Geri and I for one, can certainly sense the excitement ;) Enjoy the 
new shiny kernel.

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

Re: Testing request: mediawriter for F23 and F24

2016-10-02 Thread Viorel Tabara 
On Fri Sep 30 2016 23:55:37 GMT-0600 (MDT) Adam Williamson 
 wrote:
> Hmm, sorry? Results step 1 is:
> 
> "The USB stick should be wiped before being written with the image"
> 
> are you saying that didn't happen when you tried with a non-live image?
> What did happen?

If the USB stick contains a live image the tool will display at startup a 
message to that effect (step 6) and assuming that "How to test" and "Expected 
Results" are a one to one match I was looking for a notification similar to the 
one that pops up *before* you are burning a RW disc.

I would actually go as far as merging "How to test" steps 1 and 2, and remove 
"Expected Results" step 1. IMO step 6 is the wipe test (although a wipe happens 
during the write in step 3 but that detail is transparent to user).

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

Re: Testing request: mediawriter for F23 and F24

2016-09-30 Thread Viorel Tabara 
On Fri Sep 30 2016 13:58:51 GMT-0600 (MDT) Adam Williamson 
 wrote:
> Test case: https://fedoraproject.org/wiki/QA:Testcase_USB_fmw

Done with two bonus bananas [1]:

1. A cosmetic glitch [2]. To replicate, reinsert the USB key while FMW is open.

2. Expected Results #1 only happens if the media contains a *live* image.

-- 
Viorel

[1]:You need to tell us where the Monkey comes from.
[2]:https://fedoraproject.org/wiki/QA:Testcase_USB_fmw
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Fedora on usb connected media

2016-09-30 Thread Viorel Tabara 
On Fri Sep 30 2016 10:39:07 GMT-0600 (MDT) Chris Murphy 
> OK but what is the bug ID?

https://bugzilla.redhat.com/show_bug.cgi?id=1371661 

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

Re: Fedora crash reports: up in f24 over f23 when normalized to number of installed systems

2016-09-23 Thread Viorel Tabara 
On Thu Sep 22 2016 14:50:43 GMT-0600 (MDT) Matthew Miller 
 wrote:
> We probably _can_ -- the data is there. Just need to find a way to
> show it that brings out that answer. Maybe instead of counting number
> of reports, count number of packages with reports each day and compare;
> that'd show if it's general or specific crashyness.

If we are weighing in the bugginess perhaps we should be looking at Bugzilla 
instead? There are 4472 bugs for F23 vs 3869 for F24 over a 3 month period 
starting with the release date [1]. That is, if all abrt reports do end up as 
bug reports.

-- 
Viorel

[1]:https://viorel.fedorapeople.org/Screenshot_2016-09-22_20-19-11.png 

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

Re: F25 Alpha blocker / FE fixes: karma needed!

2016-08-20 Thread Viorel Tabara 
On Mon Aug 15 2016 18:31:21 GMT-0600 (MDT) Adam Williamson 
 wrote:
> 1. https://admin.fedoraproject.org/updates/FEDORA-2016-97debec731
>sssd-1.14.0-5.fc25 | https://bugzilla.redhat.com/show_bug.cgi?id=1366403
> 
> This one has just landed. It should fix an issue the openQA FreeIPA
> tests ran into with sssd_be crashing on a system enrolled into a
> FreeIPA domain during installation via kickstart. Re-creating the whole
> test is somewhat tedious, but you can leave +1 karma if you have a
> system configured as a FreeIPA or Active Directory client using sssd
> and it still works fine after updating sssd to 1.14.0-5.fc25 and
> rebooting. If your system isn't enrolled in a FreeIPA or Active
> Directory domain, you can't test this.

I see that the update has got enough karma, however I'm getting:

   [root@omiday ~]# ipa-client-install 
   Using existing certificate '/etc/ipa/ca.crt'.
   Discovery was successful!
   Client hostname: omiday.can.local
   Realm: CAN.LOCAL
   DNS Domain: can.local
   IPA Server: stuff.can.local
   BaseDN: dc=can,dc=local

   Continue to configure the system with these values? [no]: yes
   Removed old keys for realm CAN.LOCAL from /etc/krb5.keytab
   Synchronizing time with KDC...
   Attempting to sync time using ntpd.  Will timeout after 15 seconds
   Attempting to sync time using ntpd.  Will timeout after 15 seconds
   Unable to sync time with NTP server, assuming the time is in sync. Please 
check that 123 UDP port is opened.
   User authorized to enroll computers: admin
   Password for admin@CAN.LOCAL: 
   Joining realm failed: Host is already joined.
   Inconsistency detected by ld.so: dl-close.c: 811: _dl_close: Assertion 
`map->l_init_called' failed!

   Installation failed. Rolling back changes.
   IPA client is not configured on this system.

The same error if I do:

   omiday ~ $ ssh -S none pc96.can.local 
   Last login: Sat Aug 20 12:01:10 2016 from 192.168.0.11
   pc96 ~ $ logout
   Connection to 192.168.0.5 closed.
   Inconsistency detected by ld.so: dl-close.c: 811: _dl_close: Assertion 
`map->l_init_called' failed!
 
The comment in bug 1189856 [1] suggests a glibc issue and that may very well be 
the case as I can successfully run ipa-client-install on a Fedora 24 box.

I'll boot a fresh F25 later on today and post back the results.

-- 
Viorel


[1]:https://bugzilla.redhat.com/show_bug.cgi?id=1189856#c8 
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Group join process tweak proposal

2016-08-08 Thread Viorel Tabara 
On Mon Aug 08 2016 18:45:48 GMT-0600 (MDT) Adam Williamson 
 wrote:
> * Create a [https://bugzilla.redhat.com/createaccount.cgi Bugzilla Account] 
> (ideally using the same address as the one associated with your FAS account)

Hi Adam, I'd remove "ideally" as it contradicts the request under "What are you 
looking to do" further down the page:

Please make sure that the email addresses for your Fedora account and the 
Bugzilla account are the same.

> If the applicant is already an active Fedora contributor in other teams, and 
> you as a sponsor can verify that, this also is sufficient verification.

Does the process involve more than what Zodbot's ".fas" or ".fasinfo" provide?  

That would be all from me. Nice write up ;)

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: QA group joining process: new members cannot subscribe to list until approved

2016-08-05 Thread Viorel Tabara 
On Fri Aug 05 2016 16:08:49 GMT-0600 (MDT) Adam Williamson 
 wrote:
> Still, we could probably clarify the join process in any case.

What's the purpose of phone number in FAS? It's a piece of personal information 
spammers will never reveal.

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Just checking…

2016-06-12 Thread Viorel Tabara 
On Sun Jun 12 2016 00:57:08 GMT-0600 (MDT) Russel Winder  
wrote:
> Setting
> 
> SELINUX=permissive
> 
> in /etc/selinux/config allows GDM to start on my Lenovo X1.
> 
> This allows for UI-based use but clearly at the expense of SELinux. 

What happens if you enable it after logging in:

setenforce 1

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Fedora 24 Final blocker bug status mail

2016-05-21 Thread Viorel Tabara 
On Fri May 20 2016 21:32:33 GMT-0600 (MDT) Samuel Sieb  wrote:
> You don't need to enter all that.  Just check the radio buttons at the bottom 
> right and put a short comment about whether or not it works for you.  If it 
> doesn't, also put a short explanation of why not.

Thanks Samuel, I did just that.

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Fedora 24 Final blocker bug status mail

2016-05-20 Thread Viorel Tabara 
On Thu May 19 2016 15:48:44 GMT-0600 (MDT) Adam Williamson 
 wrote:
> 6. https://bugzilla.redhat.com/show_bug.cgi?id=1330766 - realmd - MODIFIED
>[abrt] realmd: g_cancellable_is_cancelled(): realmd killed by SIGSEGV
> 
> This is an issue in FreeIPA client enrolment which I hit in manual
> testing, a potential fix just appeared so we need to test that.

I tested and updated Bugzilla but can't get my comment into Bodhi so here it is 
the screenlog:

[root@qaclient ~]# realm -v join --user=admin1 freeipa.qa-test
* Resolving: _ldap._tcp.freeipa.qa-test
* Resolving: freeipa.qa-test
* Performing LDAP DSE lookup on: 192.168.0.242
* Successfully discovered: qa-test
Password for admin1:
* Required files: /usr/sbin/ipa-client-install, /usr/sbin/oddjobd, 
/usr/libexec/oddjob/mkhomedir, /usr/sbin/sssd
* LANG=C /usr/sbin/ipa-client-install --domain qa-test --realm QA-TEST 
--mkhomedir --enable-dns-updates --unattended --force-join --server 
freeipa.qa-test --fixed-primary --principal admin1 -W --force-ntpd
WARNING: yacc table file version is out of date
Using existing certificate '/etc/ipa/ca.crt'.
Client hostname: qaclient.can.local
Realm: QA-TEST
DNS Domain: qa-test
IPA Server: freeipa.qa-test
BaseDN: dc=qa-test
Synchronizing time with KDC...
Attempting to sync time using ntpd.  Will timeout after 15 seconds
Enrolled in IPA realm QA-TEST
Created /etc/ipa/default.conf
New SSSD config will be created
Configured sudoers in /etc/nsswitch.conf
Configured /etc/sssd/sssd.conf
Configured /etc/krb5.conf for IPA realm QA-TEST
trying https://freeipa.qa-test/ipa/json
Forwarding 'ping' to json server 'https://freeipa.qa-test/ipa/json'
Forwarding 'ca_is_enabled' to json server 'https://freeipa.qa-test/ipa/json'
Systemwide CA database updated.
Hostname (qaclient.can.local) does not have A/ record.
Failed to update DNS records.
Missing A/ record(s) for host qaclient.can.local: 192.168.122.118.
Missing reverse record(s) for address(es): 192.168.122.118.
Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Forwarding 'host_mod' to json server 'https://freeipa.qa-test/ipa/json'
Could not update DNS SSHFP records.
SSSD enabled
Configured /etc/openldap/ldap.conf
No SRV records of NTP servers found. IPA server address will be used
NTP enabled
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Configuring qa-test as NIS domain.
Client configuration complete.

* /usr/bin/systemctl enable sssd.service
* /usr/bin/systemctl restart sssd.service
* /usr/bin/sh -c /usr/sbin/authconfig --update --enablesssd 
--enablesssdauth --enablemkhomedir --nostart && /usr/bin/systemctl enable 
oddjobd.service && /usr/bin/systemctl start oddjobd.service
* Successfully enrolled machine in realm
[root@qaclient ~]#
[root@qaclient ~]#
[root@qaclient ~]# #3
[root@qaclient ~]# ## # Expected Results:
[root@qaclient ~]# #
[root@qaclient ~]#
[root@qaclient ~]# # Check that the domain is now configured: realm list
[root@qaclient ~]# realm list
qa-test
type: kerberos
realm-name: QA-TEST
domain-name: qa-test
configured: kerberos-member
server-software: ipa
client-software: sssd
required-package: freeipa-client
required-package: oddjob
required-package: oddjob-mkhomedir
required-package: sssd
login-formats: %U@qa-test
login-policy: allow-realm-logins
[root@qaclient ~]#
[root@qaclient ~]#
[root@qaclient ~]#
[root@qaclient ~]# #  Check that you can resolve domain accounts on the 
local computer
[root@qaclient ~]# getent passwd admin@qa-test
admin@qa-test:*:131000:131000:Administrator:/home/admin:/bin/bash
[root@qaclient ~]#
[root@qaclient ~]#
[root@qaclient ~]#
[root@qaclient ~]# #  Check that you have an appropriate entry in your 
host's keytab: su -c 'klist -k'
[root@qaclient ~]# klist -k
Keytab name: FILE:/etc/krb5.keytab
KVNO Principal
 
--
1 host/qaclient.can.local@QA-TEST
1 host/qaclient.can.local@QA-TEST
1 host/qaclient.can.local@QA-TEST
1 host/qaclient.can.local@QA-TEST
[root@qaclient ~]#
[root@qaclient ~]#
[root@qaclient ~]#
[root@qaclient ~]# #  Check that you can use your keytab with kerberos: su 
-c 'kinit -k (principal)'
[root@qaclient ~]#
[root@qaclient ~]# kinit -k host/qaclient.can.local@QA-TEST
[root@qaclient ~]# echo $?
0
[root@qaclient ~]#
 

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:

Re: F24 beta virt-install with kickstart fails

2016-05-20 Thread Viorel Tabara 
On Fri May 20 2016 15:02:17 GMT-0600 (MDT) Adam Williamson 
 wrote:
> I don't use virt-install, but we've done many kickstart installs of F24
> both manually and in openQA and they work fine.

"No space left on device" may hint to wrong partitioning or disk allocation.  
Jos can you try with a very basic ks file first and post it here?

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Self-Introduction

2016-05-02 Thread Viorel Tabara 
On Mon May 02 2016 15:07:41 GMT-0600 (MDT) Adam Williamson 
 wrote:
> Which page?

Hi Adam, this is the page I was referring to:

   https://fedoraproject.org/wiki/QA#Communicate
   QA project meetings are held Mondays at 16.00 UTC in the fedora meeting 
   channel on IRC.

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Self-Introduction

2016-05-02 Thread Viorel Tabara 
On Sat Apr 23 2016 22:48:19 GMT-0600 (MDT) John Dulaney 
 wrote:
> We also have weekly IRC meetings at 11 AM Eastern (both DST and not DST) in 
> #fedora-meeting.

The QA wiki page reads 16:00 UTC. If it needs an update I can do that.


-- 
Viorel

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Self-introduction (Viorel Tabara)

2016-05-01 Thread Viorel Tabara 
Hello all,

I'm fairly new to Fedora as a community, having joined CommOps about three 
months ago where I mostly helped with wiki gardening and scratched a bit the 
Fedocal surface. Recently I decided to try my hand at a ticket that involves 
Python development which is the area I'd like to strengthen while contributing 
back to the community that shaped my work and personal life. I've been enjoying 
earning a living as a sysadmin and started my Linux journey in the days of 
RedHat 7.2 but only extensively (and exclusively) using it at work  since 2005. 
 
My home computers have been all happily running Fedora since Lovelock version.

Repetitive tasks are boring...without a computer and I have always tried 
bringing in the automation fun regardless of whether it was about writing docs  
or setting up a server environment. In the past month I've been reading the 
'test' mailing list and QA wiki and meetbot logs trying to build a base for 
helping out efficiently. I did upgrade my work laptop to F24 Alpha (XFCE) and 
have been just using it normally ever since, but that's about all I can say 
about my testing participation. The responses to the recent applications 
convinced me to apply even if there is much more left to learn about composes, 
wiki pages generation, Bodhi, OpenQA, Taskotron and all other interesting bits.

If QA needs an extra pair of hands I'd be happy to start learning and help out  
although the meetings schedule conflicts with my day job hours so most of the 
time I won't be able to attend -- hopefully that isn't a requirement for being 
part of the group.

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Latest state of Rawhide

2016-05-01 Thread Viorel Tabara 
On Fri Apr 29 2016 11:05:47 GMT-0600 (MDT) Adam Williamson 
 wrote:
> On Fri, 2016-04-29 at 09:49 -0700, Rick Stevens wrote:
>> As I understand it, permissive should allow all operations but give
>> warnings while disabled means, well, disabled. However, I've seen
>> permissive mode _block_ some operations and not issue any warnings
>> about those blocked operations.

Does anything get logged when 'dontaudit' is disabled?

> This is known, there are *some* special forms of SELinux filtering that
> can't be made 'permissive'. It works for most stuff, though. I think
> Dan has a blog post on it somewhere.

Improving/refreshing SELinux knowledge is never a bad thing ;) so I did some 
reading and have come across:

http://danwalsh.livejournal.com/67855.html 

Is that it?

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: F24 Alpha seamonkey segmentation fault on upgraded profile

2016-04-06 Thread Viorel Tabara 
On Tue Apr 05 2016 00:44:40 GMT-0600 (MDT) Adam Williamson 
 wrote:
> To be precise - since navigating Bugzilla can be tricky the first time!
>  - select Fedora as the 'classification' and the 'product', then
> seamonkey as the component (if you just type 'seamonkey' into the box
> it should find it for you after a second or two) and set the 'version'
> to 24. Then provide a summary and a description, and attach the
> backtrace if you can. The other fields aren't so important.

Tonight while testing whether the crash happens with a new profile added to the 
F23 config and then transferred over to the F24 box, abrt kicked in so I went 
through the process of submitting a bug report which did a much better job of 
collecting information than I did.

Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1324341 

> Thanks a lot for testing!

Thanks for testing all the Fedora editions I've been enjoying for many years ;)

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

F24 Alpha seamonkey segmentation fault on upgraded profile

2016-04-05 Thread Viorel Tabara 
Hello,

I'm a new contributor to Fedora and this is my first time helping out with 
testing so I'm not sure where to report, in what format and everything else 
that is explained in the QA documentation pages that I haven't read yet.

I upgraded from F23 and as per subject line Seamonkey segfaults on the existing 
profile.

Here's a rundown of my tests:

- Desktop: XFCE
- Version: seamonkey-2.40-1.fc24.x86_64 
- Configuration:
   - one profile
   - password protected (i.e. master password set which triggers the password 
 prompt upon startup)
   - no addons

How I tested:

1. Start Seamonkey.
2. Enter the master password.
Result: Segmentation fault.

1. Start Seamonkey.
2. At the master password prompt press ESC.
Result: Segmentation fault.

Next, I created a new profile 'test', set it as default and re-tested:

- No master password:
   1. Start Seamonkey.
   - Result: Pass.
- With master password:
   1. Start Seamonkey.
   2. Enter master password.
   - Result: Pass.

I can provide a gdb backtrace.

Looking forward to more testing fun.

-- 
Viorel
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org