2013-12-09 - Fedora QA Meeting - recap

2013-12-09 Thread Adam Williamson
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20131209

Next meeting is scheduled for 2013-12-16 at 1600 UTC in #fedora-meeting.
If you have topics you think we should bring up at the meeting, please
add them to the Wiki page at
https://fedoraproject.org/wiki/QA/Meetings/20131216. Thanks!

TOPIC: Previous meeting follow-up
===
* adamw to draft a new test case and matrix row for validating
  cloud image checksums - adamw still failed to get around to
  this, will try once more for next week 

TOPIC: Fedora 20 Final status
===
* Test coverage was looking decent, just a couple of tests
  remain that hadn't been run since Beta
* Two accepted blockers were outstanding, and several proposed
* Next compose date depends to some extent on anaconda work
* Go/No-Go again on Thursday 

TOPIC: Open floor
===
* tflink and roshi both looking for feedback on ideas: tflink's
  proposal for a taskotron task description format[1] and
  roshi's proposal for validation test case 'roadmaps' for
  running multiple tests together[2]

Action items
===
* adamw to draft a new test case and matrix row for validating
  cloud image checksums

1. https://lists.fedoraproject.org/pipermail/qa-devel/2013-December/000556.html
2. http://roshi.fedorapeople.org/testing-efficiently.html
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

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

Fedora 19 updates-testing report

2013-12-09 Thread updates
The following Fedora 19 Security updates need testing:
 Age  URL
  73  
https://admin.fedoraproject.org/updates/FEDORA-2013-17836/davfs2-1.4.7-3.fc19
  52  
https://admin.fedoraproject.org/updates/FEDORA-2013-19262/quassel-0.9.1-1.fc19
  45  
https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19
  13  
https://admin.fedoraproject.org/updates/FEDORA-2013-22208/subversion-1.7.14-1.fc19
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-22507/drupal6-6.29-1.fc19
   6  https://admin.fedoraproject.org/updates/FEDORA-2013-22610/nbd-3.5-1.fc19
   6  
https://admin.fedoraproject.org/updates/FEDORA-2013-22608/maradns-2.0.07d-1.fc19
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-22680/tuxcut-5.0-15.fc19
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-22697/xdialog-2.3.1-13.fc19
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-22693/openstack-nova-2013.1.4-3.fc19
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-22677/monitorix-3.4.0-1.fc19
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-22761/hdapsd-20090401.20131204git401ca60-1.fc19
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-22776/gimp-2.8.10-4.fc19
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-22764/zabbix-2.0.9-2.fc19
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-22787/mod_nss-1.0.8-27.fc19
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22914/mingw-openjpeg-1.5.1-5.fc19
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22919/net-snmp-5.7.2-13.fc19
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22888/xen-4.2.3-11.fc19
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22900/dcraw-9.19-4.fc19
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22924/ufraw-0.19.2-10.fc19
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-22996/munin-2.0.18-2.fc19
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-23016/munin-2.0.19-1.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23062/rubygem-i18n-0.6.1-4.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23085/samba-4.0.13-1.fc19


The following Fedora 19 Critical Path updates have yet to be approved:
 Age URL
  19  
https://admin.fedoraproject.org/updates/FEDORA-2013-21772/unzip-6.0-11.fc19
  10  
https://admin.fedoraproject.org/updates/FEDORA-2013-22326/fedora-bookmarks-15-4.fc19
   8  https://admin.fedoraproject.org/updates/FEDORA-2013-22509/llvm-3.3-3.fc19
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-22421/gvfs-1.16.4-2.fc19
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-22463/gvfs-1.16.4-1.fc19
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-22512/highlight-3.16.1-1.fc19
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-22670/libfm-1.1.3-1.fc19
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-22774/langtable-0.0.22-1.fc19
   1  https://admin.fedoraproject.org/updates/FEDORA-2013-9/qt-4.8.5-11.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23080/nautilus-3.8.2-2.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23074/openssl-1.0.1e-31.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23085/samba-4.0.13-1.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23072/systemd-204-18.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-22324/mutter-3.8.4-2.fc19,clutter-1.14.4-6.fc19


The following builds have been pushed to Fedora 19 updates-testing

asymptote-2.24-2.fc19
clutter-1.14.4-6.fc19
docker-registry-0.6.0-4.fc19
gccxml-0.9.0-0.19.20131209.git9a114c0c.fc19
glite-lb-client-6.0.8-2.fc19
libupnp-1.6.19-1.fc19
mate-themes-1.6.3-0.2.git52ee204.fc19
matreshka-0.4.0-2.fc19
mesa-libGLU-9.0.0-4.fc19
mutter-3.8.4-2.fc19
nautilus-3.8.2-2.fc19
openlmi-tools-0.9-12.fc19
openlmi-tools-0.9-14.fc19
openssl-1.0.1e-31.fc19
perl-Net-DNS-0.73-1.fc19
perl-Net-DNS-SEC-0.17-1.fc19
php-drush-drush-6.2.0-1.fc19
python-rhsm-1.10.8-1.fc19
python-waitress-0.8.5-3.fc19
rubygem-i18n-0.6.1-4.fc19
samba-4.0.13-1.fc19
smem-1.4-1.fc19
subscription-manager-1.10.8-1.fc19
systemd-204-18.fc19
varnish-agent-2.1-5.fc19
wicd-1.7.2.4-7.fc19
wireshark-1.10.3-7.fc19

Details about builds:



 asymptote-2.24-2.fc19 (FEDORA-2013-23078)
 Descriptive vector graphics language

Update Information:

Fix issues identified by abrt.

ChangeLog:

* Wed Aug 14 2013 Tom Callaway  - 2.24-2
- use unversioned docdir macros
* Wed Aug 14 2013 Tom Callaway  - 2.24-1
- update to 2.24
* Sat Aug  3 2013 Fedora Release Engineering  
- 2.23-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_2

Fedora 18 updates-testing report

2013-12-09 Thread updates
The following Fedora 18 Security updates need testing:
 Age  URL
 234  
https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18
  80  
https://admin.fedoraproject.org/updates/FEDORA-2013-17195/spice-gtk-0.18-3.fc18
  77  
https://admin.fedoraproject.org/updates/FEDORA-2013-17431/thunderbird-17.0.9-1.fc18
  75  
https://admin.fedoraproject.org/updates/FEDORA-2013-17635/wireshark-1.10.2-4.fc18
  73  
https://admin.fedoraproject.org/updates/FEDORA-2013-17853/davfs2-1.4.7-3.fc18
  16  
https://admin.fedoraproject.org/updates/FEDORA-2013-21875/389-ds-base-1.3.0.9-1.fc18
  10  
https://admin.fedoraproject.org/updates/FEDORA-2013-22315/ruby-1.9.3.484-32.fc18
  10  
https://admin.fedoraproject.org/updates/FEDORA-2013-22313/subversion-1.7.14-1.fc18
   6  https://admin.fedoraproject.org/updates/FEDORA-2013-22607/nbd-3.5-1.fc18
   6  
https://admin.fedoraproject.org/updates/FEDORA-2013-22606/maradns-2.0.07d-1.fc18
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-22686/tuxcut-5.0-15.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-22771/gimp-2.8.10-4.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-22786/mod_nss-1.0.8-27.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22949/net-snmp-5.7.2-7.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22866/xen-4.2.3-11.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22929/dcraw-9.19-4.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22899/ufraw-0.19.2-10.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-22986/munin-2.0.18-2.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-22993/munin-2.0.19-1.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23068/rubygem-i18n-0.6.0-2.fc18


The following Fedora 18 Critical Path updates have yet to be approved:
 Age URL
 303  
https://admin.fedoraproject.org/updates/FEDORA-2013-2192/nautilus-3.6.3-5.fc18
  13  
https://admin.fedoraproject.org/updates/FEDORA-2013-22215/taglib-1.9.1-2.fc18
  13  
https://admin.fedoraproject.org/updates/FEDORA-2013-22253/kde-settings-4.9-22.fc18
  10  
https://admin.fedoraproject.org/updates/FEDORA-2013-22299/fedora-bookmarks-15-4.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-22457/libbluray-0.4.0-2.fc18
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-22690/libfm-1.1.3-1.fc18
   2  https://admin.fedoraproject.org/updates/FEDORA-2013-22918/opus-1.1-1.fc18
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-22917/colord-1.0.5-1.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-23060/openssl-1.0.1e-31.fc18


The following builds have been pushed to Fedora 18 updates-testing

asymptote-2.24-2.fc18
gccxml-0.9.0-0.19.20131209.git9a114c0c.fc18
glite-lb-client-6.0.8-2.fc18
mate-themes-1.6.3-0.2.git52ee204.fc18
openssl-1.0.1e-31.fc18
perl-Net-DNS-0.73-1.fc18
perl-Net-DNS-SEC-0.17-1.fc18
php-drush-drush-6.2.0-1.fc18
python-rhsm-1.10.8-1.fc18
python-waitress-0.8.5-3.fc18
rubygem-i18n-0.6.0-2.fc18
subscription-manager-1.10.8-1.fc18

Details about builds:



 asymptote-2.24-2.fc18 (FEDORA-2013-23070)
 Descriptive vector graphics language

Update Information:

Fix issues identified by abrt.

ChangeLog:

* Wed Aug 14 2013 Tom Callaway  - 2.24-2
- use unversioned docdir macros
* Wed Aug 14 2013 Tom Callaway  - 2.24-1
- update to 2.24
* Sat Aug  3 2013 Fedora Release Engineering  
- 2.23-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
* Thu May 23 2013 Tom Callaway  - 2.23-1
- update to 2.23
* Fri May 17 2013 Tom Callaway  - 2.22-1
- update to 2.22
* Sun Feb 10 2013 Rahul Sundaram  - 2.21-5
- remove vendor tag from desktop file. https://fedorahosted.org/fpc/ticket/247
- clean up spec to follow current guidelines
* Thu Jan 31 2013 Tom Callaway  - 2.21-4
- use pillow compatible import (from PIL import foo)

References:

  [ 1 ] Bug #912925 - [abrt] asymptote-2.21-3.fc18: exit: Process /usr/bin/asy 
was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=912925




 gccxml-0.9.0-0.19.20131209.git9a114c0c.fc18 (FEDORA-2013-23064)
 XML output extension to GCC

Update Information:

Fix for ppc(64)

Minor fix in gcc 4.8 support files.
Minor fix in gcc 4.8 support files.

ChangeLog:

* Mon Dec  9 201

Re: Not able to install F20 over IPv6

2013-12-09 Thread Adam Williamson
On Mon, 2013-12-09 at 19:10 +0100, A.J. Werkman wrote:
> On 12/09/2013 05:36 PM, Kevin Fenzi wrote:
> > On Mon, 09 Dec 2013 09:08:51 +0100
> > "A.J. Werkman"  wrote:
> >
> >> Adam,
> >>
> >> You asked people to test F20 with IPv6. I do agree that works fine.
> >> But the problems I see is getting F20 installed IPv6 only.
> >>
> >> In my experience as soon as you involve IPv4 somehow, things work.
> >>
> >> My testcase is a IPv6 only network, without IPv4-DHCP. Wether you
> >> supply IPv6 address on the boot command line or you supply addresses
> >> in the opening network screen after boot, F20 crashes.
> >> Even kickstarting with installation from local media makes F20 crash.
> > I agree that it would be good to support this case... but I'm not sure
> > we have any specific 'ipv6 only' test cases/criteria, so it's not been
> > something on the radar much...
> >
> > Perhaps something to propose for next release?
> >
> > kevin
> +1 for me. I proposed this some time ago. At that point there was not 
> much enthousiasme for it. But if Fedora wants to be, as it always 
> claims, on the cutting edge, you should have IPv6-only in QA.
> 
> One thing you would immediatly run into is the fact that 
> bugzilla.redhat.com does not resolve to an IPv6 address. So sending 
> crash reports from anaconda isn't possible at the moment from IPv6.

Instead of proposing that somebody writes a test case, perhaps write a
test case and propose that? It's generally going to get you to your goal
faster.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

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

Re: gnome-session-properties.desktop with NoDisplay=true

2013-12-09 Thread Matthias Clasen
On Mon, 2013-12-09 at 22:00 -0200, Bruno Medeiros wrote:
> Hi, all.
> 
> 
> I'm using F20 and had some trouble to find where to setup my startup
> applications. 

gnome-tweak-tool can set up startup applications in f20.


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

Re: gnome-session-properties.desktop with NoDisplay=true

2013-12-09 Thread piruthiviraj natarajan
I believe its an upstream decision.
On Dec 10, 2013 5:31 AM, "Bruno Medeiros"  wrote:

> Hi, all.
>
> I'm using F20 and had some trouble to find where to setup my startup
> applications. After a Google search, I figured out that we need to run
> gnome-session-properties from a terminal or alt+f2 window. This screen is
> not available when searching on Gnome Shell prompt. I personally think that
> it's a bad decision, this is a simple window and should appear on the
> search.
>
> My questions are:
>
> Is it Fedora-specific or the default upstream behavior?
>
> Any changes of having NoDisplay=false accepted either in Fedora or
> upstream?
>
> Thanks in advance,
>
> --
> BrunoJCM
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

gnome-session-properties.desktop with NoDisplay=true

2013-12-09 Thread Bruno Medeiros
Hi, all.

I'm using F20 and had some trouble to find where to setup my startup
applications. After a Google search, I figured out that we need to run
gnome-session-properties from a terminal or alt+f2 window. This screen is
not available when searching on Gnome Shell prompt. I personally think that
it's a bad decision, this is a simple window and should appear on the
search.

My questions are:

Is it Fedora-specific or the default upstream behavior?

Any changes of having NoDisplay=false accepted either in Fedora or upstream?

Thanks in advance,

-- 
BrunoJCM
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Not able to install F20 over IPv6

2013-12-09 Thread Dennis Gilmore
Everything but bugzilla reporting should work today over ipv6 only. If it 
doesn't it is a bug, which needs to be filed.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: systemd-208-9.fc20 package in f20 unsigned

2013-12-09 Thread Bruno Medeiros
On Sat, Dec 7, 2013 at 6:44 PM, Adam Williamson  wrote:

> On 2013-12-07 01:54, Bruno Medeiros wrote:
>
>> On Fri, Dec 6, 2013 at 3:20 PM, Kevin Fenzi  wrote:
>>
>>  Greetings.
>>>
>>> systemd-208-9.fc20 was pushed into the base fedora 20 repos last
>>> night
>>> (as it fixed a blocker bug for the upcoming release).
>>>
>>> However, it was not signed properly, so Fedora 20 prerelease users
>>> will see an error about the package not being signed.
>>>
>>> This has already been corrected and the signed package will be in
>>> tomorrow's branched compose. Please wait for that compose to
>>> update, or
>>> if you need to test that the blocker is fixed, you can use
>>> --nogpgcheck to upgrade to the new package.
>>>
>>
>>

BTW, any special reason for not having --nogpgcheck documented on "man
fedup" ?


 I'm the reporter of bug
>> https://bugzilla.redhat.com/show_bug.cgi?id=1038863 [1] and I'm trying
>>
>> fedup 0.8.0 as suggested on this issue. I got the same error, but for
>> the package systemd-libs:
>>
>> Package systemd-libs-208-9.fc20.x86_64.rpm is not signed
>>
>> Is this package also corrected?
>>
>
> They all come from the same source package, so yes, it will be.
>

Thanks for the info.

-- 
BrunoJCM
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F20: System doesn't resume correctly from suspend any more

2013-12-09 Thread Ankur Sinha
On Tue, 2013-12-10 at 09:07 +1100, Ankur Sinha wrote:
> I'm going to try downgrading the package to see if that fixes it.

Downgrade -> works

Re-Upgrade to reproduce -> couldn't reproduce, started working.

Oh well.
-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG



signature.asc
Description: This is a digitally signed message part
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

nspr update to 4.10.2 in need of Karma form proven testers

2013-12-09 Thread Elio Maldonado Batiz

Hi,

The updates are to address CVE-2013-5607 and the update to Firefox 26.

https://admin.fedoraproject.org/updates/nspr-4.10.2-1.fc19
https://admin.fedoraproject.org/updates/nspr-4.10.2-1.fc18

Thank you,

Elio
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F20: System doesn't resume correctly from suspend any more

2013-12-09 Thread Ankur Sinha
Hi,

Of late, I only get the Fedora bubble when my system resumes from
suspend. The gnome-shell lock screen doesn't come up. Even heading to a
virtual terminal and restarting gnome-shell doesn't work. Is anyone else
seeing this? Any ideas on how I should go about debugging this? I didn't
find much in journalctl at a glance.

There was a systemd upgrade recently:
Upgraded systemd-208-8.fc20.x86_64 @updates-testing
Upgrade  208-9.fc20.x86_64 @fedora
Upgraded systemd-libs-208-8.fc20.i686  @updates-testing
Upgraded systemd-libs-208-8.fc20.x86_64@updates-testing

I'm going to try downgrading the package to see if that fixes it.

F20, Gnome3, up dated with -testing enabled.
-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG



signature.asc
Description: This is a digitally signed message part
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

★ Test, Richard Vickery left a message for you

2013-12-09 Thread Richard Vickery
Richard Vickery left a message for you

Its sender and content will be shown only to you and you can delete it at any 
time. You can instantly reply to it, using the message exchange system. To find 
out what was written to you, just follow this link:
http://us1.badoo.com/01234664006/in/hdDZct1in5w/?lang_id=3&g=57-0-4&m=21&mid=52a6286e000302b6956e0115e305013f


If clicking the links in this message does not work,
copy and paste them into the address bar of your browser.


This email is a part of delivering a message sent by Richard Vickery on the 
system. If you received this email by mistake, please just ignore it. After a 
short time the message will be removed from the system.


Have fun!
The Badoo Team

You have received this email from Badoo Trading Limited (postal address below).
If you do not wish to receive further email communications from Badoo click 
here to opt out: 
https://us1.badoo.com/impersonation.phtml?lang_id=3&email=test%40lists.fedoraproject.org&block_code=8d089b&m=21&mid=52a6286e000302b6956e0115e305013f&g=0-0-4.

Badoo Trading Limited is a limited company registered in England and Wales
under CRN 7540255 with its registered office at Media Village, 131 - 151 Great 
Titchfield Street, London, W1W 5BB.-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F20/Gnome3: How to add own plain colors for usage as desktop background?

2013-12-09 Thread Matthias Clasen
On Mon, 2013-12-09 at 10:35 +0100, Joachim Backes wrote:
> Hi all,
> 
> I want to define in gnome3/F20 additional plain colours for usage as
> desktop background, but I did not find a menu to do that (only 15
> coulours available).
> 
> Any advice?

Those 15 colors are currently hardcoded. You can of course set your own
by exploring the settings in org.gnome.desktop.background. If you want a
way to do this in the UI, you could lobby for
https://bugzilla.gnome.org/show_bug.cgi?id=689351

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

Re: bugzilla problem

2013-12-09 Thread Kevin Fenzi
On Mon, 09 Dec 2013 14:50:22 -0500
Cole Robinson  wrote:

> On 12/09/2013 11:44 AM, Gene Czarcinski wrote:
> > It is kind of difficult to file new bug reports if, when I select
> > the product Fedora, I get a "502 proxy error".  If instead of
> > selecting the product Fedora I select the product Fedora
> > Documentation, things work as normal.
> > 
> > Gene
> 
> Same issue, was affecting me on Friday as well. I filed a report with
> the RH bugzilla admins, received a response that it was 'fixed' over
> the weekend, but it still fails 100% of the time for me. Specifically
> the link:
> 
> https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora
> 
> I reopened the internal report, I'll respond here if there's any news.

My understanding is that they have figured out the problem, there's a
fix and they are just looking at rolling it out as a hotfix now. 

See: 

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

kevin


signature.asc
Description: PGP signature
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: bugzilla problem

2013-12-09 Thread Cole Robinson
On 12/09/2013 11:44 AM, Gene Czarcinski wrote:
> It is kind of difficult to file new bug reports if, when I select the product
> Fedora, I get a "502 proxy error".  If instead of selecting the product Fedora
> I select the product Fedora Documentation, things work as normal.
> 
> Gene

Same issue, was affecting me on Friday as well. I filed a report with the RH
bugzilla admins, received a response that it was 'fixed' over the weekend, but
it still fails 100% of the time for me. Specifically the link:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora

I reopened the internal report, I'll respond here if there's any news.

- Cole
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Not able to install F20 over IPv6

2013-12-09 Thread A.J. Werkman


On 12/09/2013 05:36 PM, Kevin Fenzi wrote:

On Mon, 09 Dec 2013 09:08:51 +0100
"A.J. Werkman"  wrote:


Adam,

You asked people to test F20 with IPv6. I do agree that works fine.
But the problems I see is getting F20 installed IPv6 only.

In my experience as soon as you involve IPv4 somehow, things work.

My testcase is a IPv6 only network, without IPv4-DHCP. Wether you
supply IPv6 address on the boot command line or you supply addresses
in the opening network screen after boot, F20 crashes.
Even kickstarting with installation from local media makes F20 crash.

I agree that it would be good to support this case... but I'm not sure
we have any specific 'ipv6 only' test cases/criteria, so it's not been
something on the radar much...

Perhaps something to propose for next release?

kevin
+1 for me. I proposed this some time ago. At that point there was not 
much enthousiasme for it. But if Fedora wants to be, as it always 
claims, on the cutting edge, you should have IPv6-only in QA.


One thing you would immediatly run into is the fact that 
bugzilla.redhat.com does not resolve to an IPv6 address. So sending 
crash reports from anaconda isn't possible at the moment from IPv6.



Koos.

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

bugzilla problem

2013-12-09 Thread Gene Czarcinski
It is kind of difficult to file new bug reports if, when I select the 
product Fedora, I get a "502 proxy error".  If instead of selecting the 
product Fedora I select the product Fedora Documentation, things work as 
normal.


Gene
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Not able to install F20 over IPv6

2013-12-09 Thread Kevin Fenzi
On Mon, 09 Dec 2013 09:08:51 +0100
"A.J. Werkman"  wrote:

> Adam,
> 
> You asked people to test F20 with IPv6. I do agree that works fine.
> But the problems I see is getting F20 installed IPv6 only.
> 
> In my experience as soon as you involve IPv4 somehow, things work.
> 
> My testcase is a IPv6 only network, without IPv4-DHCP. Wether you
> supply IPv6 address on the boot command line or you supply addresses
> in the opening network screen after boot, F20 crashes.
> Even kickstarting with installation from local media makes F20 crash.

I agree that it would be good to support this case... but I'm not sure
we have any specific 'ipv6 only' test cases/criteria, so it's not been
something on the radar much... 

Perhaps something to propose for next release?

kevin


signature.asc
Description: PGP signature
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] 2013-12-09 @ 17:00 UTC (or directly after QA meeting) - F20 Final Blocker Bug Review #4.5

2013-12-09 Thread Jaroslav Reznik
- Original Message -
> # F20 Final Blocker Review meeting #4.5
> # Date: 2013-12-09
> # Time: 17:00 UTC (12:00 EST, 09:00 PST), or directly after QA meeting
> # Location: #fedora-blocker-review on irc.freenode.net
> 
> Yes folks, it's time for more Monday blocker review - just like last
> week. Thursday is Go/No-Go again, and there are several new proposed
> blockers, so we should really take a look at them tomorrow to make the
> workload clear.

Hi guys,
I'm not sure I'll make the beginning/middle part of the meeting :(.

> We've got 8 proposed blockers and 5 proposed freeze exception issues to
> get through, as I write this. The full list is located here:
> http://qa.fedoraproject.org/blockerbugs/current . It might be worth the
> time to read up on them before the meeting - that way
> we can get through them all as fast as possible.

Voted for clear cases (actually one so far).

Jaroslav
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Switch back to KDM?

2013-12-09 Thread poma
On 09.12.2013 14:35, Martin Briza wrote:
> Hi,
> 
> This discussion was already there, I'm not going for it again, sorry,  
> nothing constructive will result of it.
> 
> For me, it's especially the fact it's C++11/Qt.
> 
> If you want to see the reasons for yourself, read the links in the  
> documentation section of the change proposal.
> Also, Aaron Seigo linked it some time ago on his G+ profile and there was  
> a nice flame of SDDM vs. LightDM.

No way am goin to read it! ;)
Thanks but no thanks.


poma


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

Re: Switch back to KDM?

2013-12-09 Thread poma
On 09.12.2013 13:38, Jaroslav Reznik wrote:
> - Original Message -
>> On 09.12.2013 12:41, Adam Pribyl wrote:
>>> On Mon, 9 Dec 2013, Jaroslav Reznik wrote:
>>>
 - Original Message -
> On 12/08/13 12:05, Christopher Meng wrote:
>> Target to f21:
>>
>> http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM
>
> Thanks  I thought the target was F20 since it was in all the previous
> test releases.  I guess this is a good explanation 
>
> SDDM is now lacking some functionality compared to KDM, namely XDMCP, VNC
> and
> multi-seat support. They are planned to be added.

 Martin Briza, the KDE SIG guys is working a lot on XDMCP and multi seat
 support
 - not sure what support is already there. But the initial idea behind
 switching
 to SDDM was - it works pretty well for standard use cases, everyone who
 needs
 more features can switch back to KDE. In the end - even these standard
 usecases
 were not covered very well, so it was postponed to F21. KDM really has to
 die,
 it's dead for several years now...
>>>
>>> Hm, so GDM is useless for XDMCP, multiseat, multihead and long user lists,
>>> KDM is dead, but still usable, switching to SDDM is fine for standard use
>>> case on desktop but lacking XDMCP and multiseat... this does not sound
>>> very good to me.
>>
>> Very detailed,
>> http://fedoraproject.org/wiki/Features/LightDM
>> It is not clear why they do not want to use it!?
> 
> http://aseigo.blogspot.cz/2013/03/logging-into-plasma-workspaces-2.html
> 
> It's a bit Mir vs Wayland, Canonical CLA and that SDDM feels "native" to Qt
> guys. But as far as I know, there was no final call.

OK I see.
I assume therefore that the Qt port and continue from there is not a
valuable option.
Thanks for the link.


poma




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

Re: Switch back to KDM?

2013-12-09 Thread Martin Briza

Hi,

This discussion was already there, I'm not going for it again, sorry,  
nothing constructive will result of it.


For me, it's especially the fact it's C++11/Qt.

If you want to see the reasons for yourself, read the links in the  
documentation section of the change proposal.
Also, Aaron Seigo linked it some time ago on his G+ profile and there was  
a nice flame of SDDM vs. LightDM.


Cheers,
Martin

On Mon, 09 Dec 2013 12:56:55 +0100, poma   
wrote:



On 09.12.2013 12:41, Adam Pribyl wrote:


Hm, so GDM is useless for XDMCP, multiseat, multihead and long user  
lists,
KDM is dead, but still usable, switching to SDDM is fine for standard  
use

case on desktop but lacking XDMCP and multiseat... this does not sound
very good to me.


Very detailed,
http://fedoraproject.org/wiki/Features/LightDM
It is not clear why they do not want to use it!?


poma


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

Re: Switch back to KDM?

2013-12-09 Thread Martin Briza
Actually there are problems with cooperating with our PAM stack, namely  
audit is preventing from starting more than one session (even  
consecutively) from the DM.
I was working on fixing the authentication for quite a while but couldn't  
fix it right in time so we postponed the change for Fedora 21 to not  
provide a half-functional DM in our spin.


On Mon, 09 Dec 2013 10:08:26 +0100, Jaroslav Reznik   
wrote:



- Original Message -

On 12/08/13 12:05, Christopher Meng wrote:
> Target to f21:
>
> http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM

Thanks  I thought the target was F20 since it was in all the  
previous

test releases.  I guess this is a good explanation 

SDDM is now lacking some functionality compared to KDM, namely XDMCP,  
VNC and

multi-seat support. They are planned to be added.


Martin Briza, the KDE SIG guys is working a lot on XDMCP and multi seat  
support
- not sure what support is already there. But the initial idea behind  
switching
to SDDM was - it works pretty well for standard use cases, everyone who  
needs
more features can switch back to KDE. In the end - even these standard  
usecases
were not covered very well, so it was postponed to F21. KDM really has  
to die,

it's dead for several years now...

Jaroslav

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

Re: Multi-head intel and nvidia configuration fails 100%

2013-12-09 Thread flashl

On 2013-12-09 06:45, poma wrote:

On 09.12.2013 09:48, fla...@dailybrood.com wrote:

On 2013-12-09 01:36, poma wrote:

On 08.12.2013 23:52, fla...@dailybrood.com wrote:


Thanks Felix. I'm happy to report changing bios settings on MB: AMI
Z77A-G43 (MS-7758)) to PEG+IGD Multi-Monitor appears to treat nv gpu
as
master which solves my problem.


BIOS Setup - Advanced
▶ Integrated Graphics Configuration
  ▶ IGD Multi-Monitor
  Enables both integrated and discrete graphics at the same time. 
When

  disabled, it will default to Initiated Graphics Adapter selection.


poma


Thanks, Poma.  Just to verify ...

Advanced setting Options:
Selection#1 = Intel HD4000 is master
->Integrated Graphics Configuration
-->IGD
-->IGD Multi-Monitor enabled

Selection#2 = PCIe is master
->Integrated Graphics Configuration
-->PEG
-->IGD Multi-Monitor enabled

Is this correct?

Thanks for response,
Flash


Mr Gordon, why don't you just try both options.


poma


I have.  #1 worked for F19 and #2 works for F20.  Just trying to 
lockdown what I believed happen between versions.


Flash
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

rawhide report: 20131209 changes

2013-12-09 Thread Fedora Rawhide Report
Compose started at Mon Dec  9 05:15:07 UTC 2013

Broken deps for i386
--
[LuxRender]
LuxRender-1.0-16.fc21.i686 requires libImath-2_0.so.10
LuxRender-1.0-16.fc21.i686 requires libIlmThread-2_0.so.10
LuxRender-1.0-16.fc21.i686 requires libIlmImf-Imf_2_0.so.20
LuxRender-1.0-16.fc21.i686 requires libIex-2_0.so.10
LuxRender-1.0-16.fc21.i686 requires libHalf.so.10
LuxRender-core-1.0-16.fc21.i686 requires libImath-2_0.so.10
LuxRender-core-1.0-16.fc21.i686 requires libIlmThread-2_0.so.10
LuxRender-core-1.0-16.fc21.i686 requires libIlmImf-Imf_2_0.so.20
LuxRender-core-1.0-16.fc21.i686 requires libIex-2_0.so.10
LuxRender-core-1.0-16.fc21.i686 requires libHalf.so.10
LuxRender-lib-1.0-16.fc21.i686 requires libImath-2_0.so.10
LuxRender-lib-1.0-16.fc21.i686 requires libIlmThread-2_0.so.10
LuxRender-lib-1.0-16.fc21.i686 requires libIlmImf-Imf_2_0.so.20
LuxRender-lib-1.0-16.fc21.i686 requires libIex-2_0.so.10
LuxRender-lib-1.0-16.fc21.i686 requires libHalf.so.10
[OpenEXR_CTL]
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libImath.so.6
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIlmThread.so.6
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIlmImf.so.7
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIexMath.so.6
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIex.so.6
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libHalf.so.6
OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIlmThread.so.6
OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIlmImf.so.7
OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIex.so.6
[OpenEXR_Viewers]
OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libImath-2_0.so.10
OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIlmThread-2_0.so.10
OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIlmImf-Imf_2_0.so.20
OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIexMath-2_0.so.10
OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIex-2_0.so.10
OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libHalf.so.10
[R-RScaLAPACK]
R-RScaLAPACK-0.6.1-13.fc20.i686 requires libatlas.so.3
[blueman]
blueman-1.23-7.fc20.i686 requires obex-data-server >= 0:0.4.3
blueman-1.23-7.fc20.i686 requires gvfs-obexftp
[converseen]
converseen-0.6.2-2.fc20.i686 requires libMagick++-6.Q16.so.1
[derelict]
derelict-tcod-3-20.20130626gite70c293.fc20.i686 requires tcod
derelict-tcod-devel-3-20.20130626gite70c293.fc20.i686 requires tcod
[dmapd]
dmapd-0.0.55-5.fc21.i686 requires libImath-2_0.so.10
dmapd-0.0.55-5.fc21.i686 requires libIlmThread-2_0.so.10
dmapd-0.0.55-5.fc21.i686 requires libIlmImf-Imf_2_0.so.20
dmapd-0.0.55-5.fc21.i686 requires libIexMath-2_0.so.10
dmapd-0.0.55-5.fc21.i686 requires libIex-2_0.so.10
dmapd-0.0.55-5.fc21.i686 requires libHalf.so.10
[dragonegg]
dragonegg-3.3-11.fc21.i686 requires gcc = 0:4.8.2-1.fc21
[drawtiming]
drawtiming-0.7.1-11.fc20.i686 requires libMagick++-6.Q16.so.1
[evolution-rss]
1:evolution-rss-0.3.94-2.fc21.i686 requires libcamel-1.2.so.46
[gpsdrive]
gpsdrive-2.11-20.fc20.i686 requires libgps.so.20
[gtkd]
gtkd-2.0.0-29.20120815git9ae9181.fc18.i686 requires libphobos-ldc.so.60
[httpdtap]
httpdtap-0.2-2.fc21.noarch requires kernel-debuginfo
httpdtap-0.2-2.fc21.noarch requires httpd-debuginfo
httpdtap-0.2-2.fc21.noarch requires apr-util-debuginfo
httpdtap-0.2-2.fc21.noarch requires apr-debuginfo
[kawa]
1:kawa-1.11-5.fc19.i686 requires servlet25
[koji]
koji-vm-1.8.0-2.fc20.noarch requires python-virtinst
[libghemical]
libghemical-2.99.1-24.fc20.i686 requires libf77blas.so.3
libghemical-2.99.1-24.fc20.i686 requires libatlas.so.3
[libopensync-plugin-irmc]
1:libopensync-plugin-irmc-0.22-7.fc20.i686 requires libopenobex.so.1
[licq]
licq-1.8.1-1.fc21.i686 requires libgloox.so.8
[mpqc]
mpqc-2.3.1-23.fc20.i686 requires libf77blas.so.3
mpqc-2.3.1-23.fc20.i686 requires libatlas.so.3
[netdisco]
netdisco-1.1-6.fc20.noarch requires perl(SNMP::Info::Layer2::Bay)
[nifti2dicom]
nifti2dicom-0.4.6-3.fc20.i686 requires libvtksys.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkWidgets.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkVolumeRendering.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkViews.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkTextAnalysis.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkRendering.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkParallel.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkInfovis.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkImaging.so.5.10
nifti2dicom-0.4.6-3.fc20.i686 requires libvtkIO.so.5

Re: Switch back to KDM?

2013-12-09 Thread Jaroslav Reznik
- Original Message -
> On 09.12.2013 12:41, Adam Pribyl wrote:
> > On Mon, 9 Dec 2013, Jaroslav Reznik wrote:
> > 
> >> - Original Message -
> >>> On 12/08/13 12:05, Christopher Meng wrote:
>  Target to f21:
> 
>  http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM
> >>>
> >>> Thanks  I thought the target was F20 since it was in all the previous
> >>> test releases.  I guess this is a good explanation 
> >>>
> >>> SDDM is now lacking some functionality compared to KDM, namely XDMCP, VNC
> >>> and
> >>> multi-seat support. They are planned to be added.
> >>
> >> Martin Briza, the KDE SIG guys is working a lot on XDMCP and multi seat
> >> support
> >> - not sure what support is already there. But the initial idea behind
> >> switching
> >> to SDDM was - it works pretty well for standard use cases, everyone who
> >> needs
> >> more features can switch back to KDE. In the end - even these standard
> >> usecases
> >> were not covered very well, so it was postponed to F21. KDM really has to
> >> die,
> >> it's dead for several years now...
> > 
> > Hm, so GDM is useless for XDMCP, multiseat, multihead and long user lists,
> > KDM is dead, but still usable, switching to SDDM is fine for standard use
> > case on desktop but lacking XDMCP and multiseat... this does not sound
> > very good to me.
> 
> Very detailed,
> http://fedoraproject.org/wiki/Features/LightDM
> It is not clear why they do not want to use it!?

http://aseigo.blogspot.cz/2013/03/logging-into-plasma-workspaces-2.html

It's a bit Mir vs Wayland, Canonical CLA and that SDDM feels "native" to Qt
guys. But as far as I know, there was no final call.

Jaroslav

> 
> poma
> 
> 
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Switch back to KDM?

2013-12-09 Thread poma
On 09.12.2013 12:41, Adam Pribyl wrote:
> On Mon, 9 Dec 2013, Jaroslav Reznik wrote:
> 
>> - Original Message -
>>> On 12/08/13 12:05, Christopher Meng wrote:
 Target to f21:

 http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM
>>>
>>> Thanks  I thought the target was F20 since it was in all the previous
>>> test releases.  I guess this is a good explanation 
>>>
>>> SDDM is now lacking some functionality compared to KDM, namely XDMCP, VNC 
>>> and
>>> multi-seat support. They are planned to be added.
>>
>> Martin Briza, the KDE SIG guys is working a lot on XDMCP and multi seat 
>> support
>> - not sure what support is already there. But the initial idea behind 
>> switching
>> to SDDM was - it works pretty well for standard use cases, everyone who needs
>> more features can switch back to KDE. In the end - even these standard 
>> usecases
>> were not covered very well, so it was postponed to F21. KDM really has to 
>> die,
>> it's dead for several years now...
> 
> Hm, so GDM is useless for XDMCP, multiseat, multihead and long user lists, 
> KDM is dead, but still usable, switching to SDDM is fine for standard use 
> case on desktop but lacking XDMCP and multiseat... this does not sound 
> very good to me.

Very detailed,
http://fedoraproject.org/wiki/Features/LightDM
It is not clear why they do not want to use it!?


poma


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

F-20 Branched report: 20131209 changes

2013-12-09 Thread Fedora Branched Report
Compose started at Mon Dec  9 07:15:02 UTC 2013

Broken deps for armhfp
--
[avro]
avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce
avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client
[blueman]
blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3
blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp
[cloud-init]
cloud-init-0.7.2-7.fc20.noarch requires dmidecode
[cobbler]
cobbler-2.4.0-2.fc20.noarch requires syslinux
[fts]
fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14
[ghc-hjsmin]
ghc-hjsmin-devel-0.1.4.3-2.fc20.armv7hl requires 
ghc-devel(language-javascript-0.5.8-28fa88554adf134b03284de53334e91d)
[gofer]
ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) >= 0:0.16.0
[gtkd]
gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 
0:2.0.0-29.20120815git9ae9181.fc18
[kawa]
1:kawa-1.11-5.fc19.armv7hl requires servlet25
[koji]
koji-vm-1.8.0-2.fc20.noarch requires python-virtinst
[kyua-cli]
kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0
kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0
[msp430-libc]
msp430-libc-20120224-2.fc19.noarch requires msp430-gcc >= 0:4.6.3
[nifti2dicom]
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10
nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10
[nocpulse-common]
nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI)
[openbox]
gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel
gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel
[openpts]
openpts-0.2.6-7.fc20.armv7hl requires tboot
[owncloud]
owncloud-5.0.13-1.fc20.noarch requires 
php-pear(pear.symfony.com/Routing)
[perl-Language-Expr]
perl-Language-Expr-0.19-4.fc19.noarch requires 
perl(:MODULE_COMPAT_5.16.2)
[php-Assetic]
php-Assetic-1.1.2-1.fc20.noarch requires 
php-pear(pear.symfony.com/Process) < 0:3.0
php-Assetic-1.1.2-1.fc20.noarch requires 
php-pear(pear.symfony.com/Process) >= 0:2.1
[php-Metadata]
php-Metadata-1.5.0-1.fc20.noarch requires 
php-pear(pear.symfony.com/DependencyInjection)
[php-SymfonyCmfRouting]
php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires 
php-pear(pear.symfony.com/Routing) < 0:3.0
php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires 
php-pear(pear.symfony.com/Routing) >= 0:2.2
php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires 
php-pear(pear.symfony.com/HttpKernel) < 0:3.0
php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires 
php-pear(pear.symfony.com/HttpKernel) >= 0:2.2
php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires 
php-pear(pear.symfony.com/EventDispatcher) < 0:3.0
php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires 
php-pear(pear.symfony.com/EventDispatcher) >= 0:2.2
[php-doctrine-DoctrineDBAL]
php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires 
php-pear(pear.symfony.com/Console) < 0:3.0
php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires 
php-pear(pear.symfony.com/Console) >= 0:2.0
[php-doctrine-DoctrineORM]
php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires 
php-pear(pear.symfony.com/Yaml) < 0:3.0
php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires 
php-pear(pear.symfony.com/Yaml) >= 0:2.0
php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires 
php-pear(pear.symfony.com/Console) < 0:3.0
php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires 
php-pear(pear.symfony.com/Console) >= 0:2.0
[php-guzzle-Guzzle]
php-guzzle-Guzzle-3.7.4-2.fc20.noarch requires 
php-pear(pear.symfony.com/EventDispatcher) >= 0:2.1.0
[php-phpunit-DbUnit]
php-phpunit-DbUnit-1.3.0-1.fc20.noarch require

Re: Multi-head intel and nvidia configuration fails 100%

2013-12-09 Thread poma
On 09.12.2013 09:48, fla...@dailybrood.com wrote:
> On 2013-12-09 01:36, poma wrote:
>> On 08.12.2013 23:52, fla...@dailybrood.com wrote:
>>
>>> Thanks Felix. I'm happy to report changing bios settings on MB: AMI
>>> Z77A-G43 (MS-7758)) to PEG+IGD Multi-Monitor appears to treat nv gpu 
>>> as
>>> master which solves my problem.
>>
>> BIOS Setup - Advanced
>> ▶ Integrated Graphics Configuration
>>   ▶ IGD Multi-Monitor
>>   Enables both integrated and discrete graphics at the same time. When
>>   disabled, it will default to Initiated Graphics Adapter selection.
>>
>>
>> poma
> 
> Thanks, Poma.  Just to verify ...
> 
> Advanced setting Options:
> Selection#1 = Intel HD4000 is master
> ->Integrated Graphics Configuration
> -->IGD
> -->IGD Multi-Monitor enabled
> 
> Selection#2 = PCIe is master
> ->Integrated Graphics Configuration
> -->PEG
> -->IGD Multi-Monitor enabled
> 
> Is this correct?
> 
> Thanks for response,
> Flash

Mr Gordon, why don't you just try both options.


poma


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

Re: Switch back to KDM?

2013-12-09 Thread Adam Pribyl

On Mon, 9 Dec 2013, Jaroslav Reznik wrote:


- Original Message -

On 12/08/13 12:05, Christopher Meng wrote:
> Target to f21:
>
> http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM

Thanks  I thought the target was F20 since it was in all the previous
test releases.  I guess this is a good explanation 

SDDM is now lacking some functionality compared to KDM, namely XDMCP, VNC and
multi-seat support. They are planned to be added.


Martin Briza, the KDE SIG guys is working a lot on XDMCP and multi seat support
- not sure what support is already there. But the initial idea behind switching
to SDDM was - it works pretty well for standard use cases, everyone who needs
more features can switch back to KDE. In the end - even these standard usecases
were not covered very well, so it was postponed to F21. KDM really has to die,
it's dead for several years now...


Hm, so GDM is useless for XDMCP, multiseat, multihead and long user lists, 
KDM is dead, but still usable, switching to SDDM is fine for standard use 
case on desktop but lacking XDMCP and multiseat... this does not sound 
very good to me.



Jaroslav



Adam Pribyl
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F20/Gnome3: How to add own plain colors for usage as desktop background?

2013-12-09 Thread Joachim Backes
Hi all,

I want to define in gnome3/F20 additional plain colours for usage as
desktop background, but I did not find a menu to do that (only 15
coulours available).

Any advice?

Kind regards

Joachim Backes

-- 

Fedora release 20 (Heisenbug)
Kernel-3.11.10-301.fc20.x86_64

Joachim Backes 
https://www-user.rhrk.uni-kl.de/~backes
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Switch back to KDM?

2013-12-09 Thread Jaroslav Reznik
- Original Message -
> On 12/08/13 12:05, Christopher Meng wrote:
> > Target to f21:
> >
> > http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM
> 
> Thanks  I thought the target was F20 since it was in all the previous
> test releases.  I guess this is a good explanation 
> 
> SDDM is now lacking some functionality compared to KDM, namely XDMCP, VNC and
> multi-seat support. They are planned to be added.

Martin Briza, the KDE SIG guys is working a lot on XDMCP and multi seat support
- not sure what support is already there. But the initial idea behind switching
to SDDM was - it works pretty well for standard use cases, everyone who needs
more features can switch back to KDE. In the end - even these standard usecases
were not covered very well, so it was postponed to F21. KDM really has to die,
it's dead for several years now...

Jaroslav  

> --
> Getting tired of non-Fedora discussions and self-serving posts
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Multi-head intel and nvidia configuration fails 100%

2013-12-09 Thread flashl

On 2013-12-09 01:36, poma wrote:

On 08.12.2013 23:52, fla...@dailybrood.com wrote:


Thanks Felix. I'm happy to report changing bios settings on MB: AMI
Z77A-G43 (MS-7758)) to PEG+IGD Multi-Monitor appears to treat nv gpu 
as

master which solves my problem.


BIOS Setup - Advanced
▶ Integrated Graphics Configuration
  ▶ IGD Multi-Monitor
  Enables both integrated and discrete graphics at the same time. When
  disabled, it will default to Initiated Graphics Adapter selection.


poma


Thanks, Poma.  Just to verify ...

Advanced setting Options:
Selection#1 = Intel HD4000 is master
->Integrated Graphics Configuration
-->IGD
-->IGD Multi-Monitor enabled

Selection#2 = PCIe is master
->Integrated Graphics Configuration
-->PEG
-->IGD Multi-Monitor enabled

Is this correct?

Thanks for response,
Flash
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Not able to install F20 over IPv6

2013-12-09 Thread A.J. Werkman

Adam,

You asked people to test F20 with IPv6. I do agree that works fine.
But the problems I see is getting F20 installed IPv6 only.

In my experience as soon as you involve IPv4 somehow, things work.

My testcase is a IPv6 only network, without IPv4-DHCP. Wether you supply 
IPv6 address on the boot command line or you supply addresses in the 
opening network screen after boot, F20 crashes.

Even kickstarting with installation from local media makes F20 crash.

On 12/09/2013 12:32 AM, Adam Williamson wrote:

On Sun, 2013-12-08 at 10:50 +0100, A.J. Werkman wrote:

I haven't been able to install F20 over an IPv6 network. I constantly
run into: error: [Errno 101] Network is unreachable.

In a shell of the installer I can see and prove that there is network
connectivity.

I filled bug: https://bugzilla.redhat.com/show_bug.cgi?id=1026079 but
see no activity in this field of error.

Wouldn't this be a candidate for a blocker?

Possibly (though it would've been better to nominate it when you filed
it rather than now...), but I did ask a few other people to test F20

Sorry, I assumed the bug would have been picked up and taken care of.

with IPv6 and so far they all say it worked fine...


Koos.

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