Re: fedup f20-f21 kde broken deps
On Fri, 2014-12-12 at 06:06 +0100, Ralf Corsepius wrote: On 12/08/2014 08:26 AM, Adam Williamson wrote: On Mon, 2014-12-08 at 07:36 +0100, Ralf Corsepius wrote: Just for the purpose of testing upgrade.img, you can simply enable updates-testing if it turns out you have a situation like this and you need a package from u-t to make the upgrade package set viable. This is not true. They are completely different scenarios. The purpose of using release+updates+updates-testing is entirely different from using release+updates, esp. in stages like these. The purpose of using release+updates is to test upgrading to Fedora(N+1) (and testing fedup/yum/dnf-support ) and not to test update-candidate packages from update-testing. I don't really see the distinction as important, I consider this to be critically important ... because it is a perennially moving target in any case. After Tuesday, f21 will get a new stable updates push every day. ... it is likely the #1 cause of users facing broken updates - Esp. during time-frames shortly after releases like these. I haven't checked details this time, but there a quite a few reports indicating this has happened again with this release. I haven't seen a single person report a dep issue of this nature, and I spent most of release day in #fedora, and have been following G+, forum, and various news site feedback since. -- 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: fedup f20-f21 kde broken deps
On Fri, 12 Dec 2014 00:12:37 -0800, Adam Williamson wrote: I haven't seen a single person report a dep issue of this nature, and I spent most of release day in #fedora, and have been following G+, forum, and various news site feedback since. Violated upgrade path issues still hit users. One example: R in F21 older than in F19 https://lists.fedoraproject.org/pipermail/users/2014-December/456108.html Other users don't ask the Fedora Project but just give up and hope it will work some months later (which isn't guaranteed either). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
test Digest, Vol 116, Issue 59
Send test mailing list submissions to test@lists.fedoraproject.org To subscribe or unsubscribe via the World Wide Web, visit https://admin.fedoraproject.org/mailman/listinfo/test or, via email, send a message with subject or body 'help' to test-requ...@lists.fedoraproject.org You can reach the person managing the list at test-ow...@lists.fedoraproject.org When replying, please edit your Subject line so it is more specific than Re: Contents of test digest... ---BeginMessage--- On 10/14/2013 03:27 PM, T.C. Hollingsworth wrote: On Mon, Oct 14, 2013 at 9:04 AM, Eric Blake ebl...@redhat.com wrote: I've got a similar problem - I've got my laptop set up to automount an NFS share over wifi, and frequently hit a hang during system shutdown because systemd allows Networkmanager (and the wifi) to be taken down before NFS is fully unmounted, where the system then stalls for several minutes waiting for the NFS unmount that is impossible at that point. I have no idea where to look at adding a dependency that says that yes, my wifi network connection really must have a longer lifetime on BOTH sides of the NFS mount point. Are you using systemd's automounting logic or plain ol' autofs? Dunno. Whatever I got by installing F17 with anaconda then incrementally upgrading through F18, F19, and now F20, and where I set up my /etc/fstab by copying the same configuration that worked for me since F12 pre-systemd days. So it might not be ideal, but it's one of those it works well enough for me that I'm not going to waste time tweaking it unless it breaks first situations. Except that it's noticeably broken enough at shutdown that I bothered to ask on the list :) The corresponding /etc/fstab entry: nas:/backup /mnt/backup nfs bg,user,_netdev 0 0 # systemctl list-dependencies mnt-backup.mount mnt-backup.mount ├─-.mount ├─system.slice └─network-online.target └─NetworkManager-wait-online.service -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- On Mon, Oct 14, 2013 at 2:41 PM, Eric Blake ebl...@redhat.com wrote: Dunno. Whatever I got by installing F17 with anaconda then incrementally upgrading through F18, F19, and now F20, and where I set up my /etc/fstab by copying the same configuration that worked for me since F12 pre-systemd days. So it might not be ideal, but it's one of those it works well enough for me that I'm not going to waste time tweaking it unless it breaks first situations. Except that it's noticeably broken enough at shutdown that I bothered to ask on the list :) The corresponding /etc/fstab entry: nas:/backup /mnt/backup nfs bg,user,_netdev 0 0 Okay, so the bg option is a little different from what most people refer to as automounting, in that it just repeatedly attempts to mount the share until it succeeds, whereas true automounting waits until you attempt to access the mount to even try to mount it. Of course, this distinction matters very little to _you_, but it might indicate what systemd is getting wrong here. I'm curious as to whether systemd even tracks the mount properly in this case. Does `systemctl status mnt-backup.mount` indicate success or failure? If it indicates success, systemd definitely should be tearing down the mount on shutdown. (systemd by design is supposed to reverse Before/After deps for stop operations.) Definitely file a bug in this instance. If it indicates failure, systemd isn't getting informed that this mount actually succeeds. You could file a bug against systemd regarding this, but their answer might just be use real automounting if you want this to work properly. To do that, switch your bg mount option for x-systemd.automount and see if it gets unmounted properly on shutdown afterwards. Their answer could just as easily be yeah, we need to fix this, so please do file the bug anyway, if only for the benefit of others who might run into this. -T.C. ---End Message--- ---BeginMessage--- Are multiple avahi/mDNS instances supposed to reliably work on one NIC with virtual machines? I'm experiencing hostname resolution failure with avahi about 1 minute after avahi-daemon.service starts. Nothing is recorded in the journal in between working and not working. I've disabled firewalld in the VM and on the host and get the same results. The baremetal host I can ssh to/from without there ever being a problem: ssh chris@f20s.local The qemu/kvm guest, I can ssh to/from intermittently: ssh chris@f20sv.local If I constantly log out and login, it always works, for 3-4 minutes. If I stop doing that for even 20 or seconds, the next attempt I get: ssh: Could not resolve hostname f20sv.local: nodename nor servname provided, or not known When that happens, I can still login the old fashioned way, ssh ch...@192.168.1.xxx and this
rawhide report: 20141212 changes
Compose started at Fri Dec 12 05:15:03 UTC 2014 Broken deps for i386 -- [3Depict] 3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0 [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [bibletime] bibletime-2.10.1-4.fc22.i686 requires libsword-1.7.3.so [cab] cab-0.1.9-12.fc22.i686 requires cabal-dev [dnssec-check] dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14 [glances] glances-2.1.2-2.fc22.noarch requires python-psutil = 0:2.0.0 [kdeplasma-addons] plasma-wallpaper-marble-4.14.3-1.fc22.i686 requires libmarblewidget.so.19 [nwchem] nwchem-openmpi-6.3.2-11.fc21.i686 requires libmpi_usempi.so.1 [openstack-neutron-gbp] openstack-neutron-gbp-2014.2-0.2.acb85f0git.fc22.noarch requires openstack-neutron = 0:2014.2 [pam_mapi] pam_mapi-0.2.0-3.fc22.i686 requires libmapi.so.0 [python-docs] python-docs-2.7.8-1.fc22.noarch requires python = 0:2.7.8 [python-selenium] python3-selenium-2.43.0-1.fc22.noarch requires python3-rdflib [rubygem-wirb] rubygem-wirb-1.0.3-2.fc21.noarch requires rubygem(paint) 0:0.9 [shogun] shogun-doc-3.2.0.1-0.27.git20140804.96f3cf3.fc22.noarch requires shogun-data = 0:0.8.1-0.18.git20140804.48a1abb.fc22 [subsurface] subsurface-4.2-3.fc22.i686 requires libmarblewidget.so.19 [uwsgi] uwsgi-plugin-gridfs-2.0.7-2.fc22.i686 requires libmongoclient.so uwsgi-stats-pusher-mongodb-2.0.7-2.fc22.i686 requires libmongoclient.so [vfrnav] vfrnav-20140510-2.fc22.i686 requires libpolyclipping.so.16 vfrnav-utils-20140510-2.fc22.i686 requires libpolyclipping.so.16 Broken deps for x86_64 -- [3Depict] 3Depict-0.0.16-3.fc22.x86_64 requires libmgl.so.7.2.0()(64bit) [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [bibletime] bibletime-2.10.1-4.fc22.x86_64 requires libsword-1.7.3.so()(64bit) [cab] cab-0.1.9-12.fc22.x86_64 requires cabal-dev [dnssec-check] dnssec-check-1.14.0.1-4.fc20.x86_64 requires libval-threads.so.14()(64bit) dnssec-check-1.14.0.1-4.fc20.x86_64 requires libsres.so.14()(64bit) [glances] glances-2.1.2-2.fc22.noarch requires python-psutil = 0:2.0.0 [kdeplasma-addons] plasma-wallpaper-marble-4.14.3-1.fc22.x86_64 requires libmarblewidget.so.19()(64bit) [nwchem] nwchem-openmpi-6.3.2-11.fc21.x86_64 requires libmpi_usempi.so.1()(64bit) [openstack-neutron-gbp] openstack-neutron-gbp-2014.2-0.2.acb85f0git.fc22.noarch requires openstack-neutron = 0:2014.2 [pam_mapi] pam_mapi-0.2.0-3.fc22.i686 requires libmapi.so.0 pam_mapi-0.2.0-3.fc22.x86_64 requires libmapi.so.0()(64bit) [python-docs] python-docs-2.7.8-1.fc22.noarch requires python = 0:2.7.8 [python-selenium] python3-selenium-2.43.0-1.fc22.noarch requires python3-rdflib [rubygem-wirb] rubygem-wirb-1.0.3-2.fc21.noarch requires rubygem(paint) 0:0.9 [shogun] shogun-doc-3.2.0.1-0.27.git20140804.96f3cf3.fc22.noarch requires shogun-data = 0:0.8.1-0.18.git20140804.48a1abb.fc22 [subsurface] subsurface-4.2-3.fc22.x86_64 requires libmarblewidget.so.19()(64bit) [uwsgi] uwsgi-plugin-gridfs-2.0.7-2.fc22.x86_64 requires libmongoclient.so()(64bit) uwsgi-stats-pusher-mongodb-2.0.7-2.fc22.x86_64 requires libmongoclient.so()(64bit) [vfrnav] vfrnav-20140510-2.fc22.i686 requires libpolyclipping.so.16 vfrnav-20140510-2.fc22.x86_64 requires libpolyclipping.so.16()(64bit) vfrnav-utils-20140510-2.fc22.x86_64 requires libpolyclipping.so.16()(64bit) Broken deps for armhfp -- [3Depict] 3Depict-0.0.16-3.fc22.armv7hl requires libmgl.so.7.2.0 [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [avro] avro-mapred-1.7.5-9.fc22.noarch requires hadoop-mapreduce avro-mapred-1.7.5-9.fc22.noarch requires hadoop-client [bibletime] bibletime-2.10.1-4.fc22.armv7hl requires libsword-1.7.3.so [cab] cab-0.1.9-12.fc22.armv7hl requires cabal-dev [dnssec-check] dnssec-check-1.14.0.1-4.fc20.armv7hl requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.armv7hl requires libsres.so.14 [glances] glances-2.1.2-2.fc22.noarch requires python-psutil = 0:2.0.0 [kdeplasma-addons] plasma-wallpaper-marble-4.14.3-1.fc22.armv7hl requires libmarblewidget.so.19 [openstack-neutron-gbp] openstack-neutron-gbp-2014.2-0.2.acb85f0git.fc22.noarch requires openstack-neutron = 0:2014.2 [ostree] ostree-grub2-2014.12-1.fc22.armv7hl requires grub2 [pam_mapi] pam_mapi-0.2.0-3.fc22.armv7hl requires libmapi.so.0 [python-docs] python-docs-2.7.8-1.fc22.noarch requires python
Fedora/Gnome3 : Display Problem on my hardware.
Hey guys, My old PC MoBo recently died and so, I built a new PC with the following hardware specification : * Processor : AMD A4-6300K 3.7 GHz Dual Core APU with integrated Radeon HD 8370D GPU * MoBo : MSI A58M-E33 * RAM : 4 GB Corsair Value RAM 1600 MHz. * HDD : 500 GB WD Caviar @ 7200 rpm * Monitor : 19 inch Samsung SyncMaster at 1400 X 900 pixels @ 60-75 Hz refresh rate So, I went ahead and popped in the Fedora 21 Workstation Disc. Anaconda worked well and installed Fedora 21. But as soon as I restarted my PC and logged in I found the desktop flickering! I moved the mouse pointer and it flickered even more vigorously and when I pulled through the activities hot corner, I could barely see the icons, which appeared like distorted squares. Somehow, I managed to open the terminal. All the text in the terminal were clearly visible, I installed Xfce desktop and to my surprise it worked fine, text and icon everything was clear and perfectly usable. Next, I installed KDE and it worked as well. I really had trouble understanding the wobbly widgety interface, though! So, I assumed the problem is with Gnome 3. I reinstalled the complete Gnome desktop and alas, the problem persisted! I have used Fedora 20 for quite some time on my laptop, so, I booted a live image of Fedora 20, that I had had flashed onto a pen drive and still there was the same problem. Frustrated, I gave up and installed Ubuntu, Unity worked well but when I installed Gnome3, I was back where I was, running a completely graphically distorted UI! I've since changed many distros (without Gnome as DE) and all of them worked fine. Windows 8.1 worked fluidly as well! I am currently using Ubuntu 14.10 (with Unity as DE). I found it quite close to Gnome3. However, I would still like to use Fedora and since, I'm using this as a multimedia PC, so Gnome3 is still my preference. From my observations, it seems to be a Gnome 3 hardware incompatibility issue. I've tried changing refreshing rate, resolution and colour depth and nothing could solve the issue! Even switching to the proprietary AMD drivers didn't work out. Should I file a bug report on BugZilla? If anyone's got some idea, please help! Thanks, Madhurjya Roy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup f20-f21 kde broken deps
On Fri, 2014-12-12 at 11:00 +0100, Michael Schwendt wrote: On Fri, 12 Dec 2014 00:12:37 -0800, Adam Williamson wrote: I haven't seen a single person report a dep issue of this nature, and I spent most of release day in #fedora, and have been following G+, forum, and various news site feedback since. Violated upgrade path issues still hit users. One example: R in F21 older than in F19 https://lists.fedoraproject.org/pipermail/users/2014-December/456108.html Other users don't ask the Fedora Project but just give up and hope it will work some months later (which isn't guaranteed either). That's not a dependency problem. Nothing breaks. The upgrade works, R probably still works, and the docs do suggest running a distro-sync after the upgrade if you want to resolve situations like that. Of course it's not perfect, it's just that I'm not sure anyone's suggested an alternative that's *better* yet. The best combination of ideas I can see is this: Use updates/ as a staging area during Branched freezes, and disallow pushes if the upgradepath would be violated versus stable and the packages currently *pending* for stable. The thing with that is, I'm not sure it's even viable to write a test for that, the 'currently pending' part. Without it, you can't do a simultaneous push of an update to stable for all supported releases, because the upgradepath is violated for the older releases at the time you submit the update. If you want to push the same update to all three releases you have to submit it for the newest, wait a day for it to go stable, submit it for N-1, wait a day, submit it for N-2, wait a day - it's kind of impractical. We struggle enough already with getting updates actually shipped (see the updates-testing status mails with the list of un-pushed security updates). (The other thing we could do is have fedup do distro-sync, but we've already got a whole bug report arguing about that.) -- 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: Fedora/Gnome3 : Display Problem on my hardware.
On Fri, Dec 12, 2014 at 09:19:22PM +0530, Madhurjya Roy wrote: Hey guys, I understand that Gnome-3 simply doesn't work well without 3D video acceleration. i've not personally experienced that, so I don't know if your symptoms are what actually occurs without 3D accel. Now, I know your AMD processor includes a Radeon video unit, so you SHOULD be getting 3d accel. however, if you didn't install AMD/ATI's proprietary driver for it, you're probably depending on the open source driver instead, and I suppose it simply may not work very well with that particular chip. As I said, I have no direct experience, so I may be all wet here. Good luck! Fred My old PC MoBo recently died and so, I built a new PC with the following hardware specification : * Processor : AMD A4-6300K 3.7 GHz Dual Core APU with integrated Radeon HD 8370D GPU * MoBo : MSI A58M-E33 * RAM : 4 GB Corsair Value RAM 1600 MHz. * HDD : 500 GB WD Caviar @ 7200 rpm * Monitor : 19 inch Samsung SyncMaster at 1400 X 900 pixels @ 60-75 Hz refresh rate So, I went ahead and popped in the Fedora 21 Workstation Disc. Anaconda worked well and installed Fedora 21. But as soon as I restarted my PC and logged in I found the desktop flickering! I moved the mouse pointer and it flickered even more vigorously and when I pulled through the activities hot corner, I could barely see the icons, which appeared like distorted squares. Somehow, I managed to open the terminal. All the text in the terminal were clearly visible, I installed Xfce desktop and to my surprise it worked fine, text and icon everything was clear and perfectly usable. Next, I installed KDE and it worked as well. I really had trouble understanding the wobbly widgety interface, though! So, I assumed the problem is with Gnome 3. I reinstalled the complete Gnome desktop and alas, the problem persisted! I have used Fedora 20 for quite some time on my laptop, so, I booted a live image of Fedora 20, that I had had flashed onto a pen drive and still there was the same problem. Frustrated, I gave up and installed Ubuntu, Unity worked well but when I installed Gnome3, I was back where I was, running a completely graphically distorted UI! I've since changed many distros (without Gnome as DE) and all of them worked fine. Windows 8.1 worked fluidly as well! I am currently using Ubuntu 14.10 (with Unity as DE). I found it quite close to Gnome3. However, I would still like to use Fedora and since, I'm using this as a multimedia PC, so Gnome3 is still my preference. From my observations, it seems to be a Gnome 3 hardware incompatibility issue. I've tried changing refreshing rate, resolution and colour depth and nothing could solve the issue! Even switching to the proprietary AMD drivers didn't work out. Should I file a bug report on BugZilla? If anyone's got some idea, please help! Thanks, Madhurjya Roy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- Fred Smith -- fre...@fcshome.stoneham.ma.us - God made him who had no sin to be sin for us, so that in him we might become the righteousness of God. --- Corinthians 5:21 - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora/Gnome3 : Display Problem on my hardware.
On Fri, 2014-12-12 at 12:10 -0500, Fred Smith wrote: On Fri, Dec 12, 2014 at 09:19:22PM +0530, Madhurjya Roy wrote: Hey guys, I understand that Gnome-3 simply doesn't work well without 3D video acceleration. i've not personally experienced that, so I don't know if your symptoms are what actually occurs without 3D accel. Now, I know your AMD processor includes a Radeon video unit, so you SHOULD be getting 3d accel. however, if you didn't install AMD/ATI's proprietary driver for it, you're probably depending on the open source driver instead, and I suppose it simply may not work very well with that particular chip. As I said, I have no direct experience, so I may be all wet here. Shell will run fine without 3D acceleration, it'll just be a bit slow and use some CPU time. It wouldn't do *this*, though. It's probably more a case of a bug in the radeon driver for the hardware in question which GNOME's rendering happens to hit, while the other desktops don't. I'd file the bug either against xorg-x11-drv-ati in RH Bugzilla or Product xorg, Component Driver/Radeon in bugs.freedesktop.org , including the stuff described in https://fedoraproject.org/wiki/How_to_debug_Xorg_problems . -- 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: Fedora/Gnome3 : Display Problem on my hardware.
Thank you for the response! As a high school student, I'm no expert in the department but shouldn't it be actually a GNOME3 shell bug, considering the fact that the same driver worked when used with other DEs? And if indeed, it's a driver problem, then the problem should lie within AMD's main codebase. That'd explain the fact that even the proprietary drivers couldn't resolve the issue. I'm also wondering if the problem is in anyway associated with some AMD CPUs in general! One of my friends, also noticed some occasional minor distortions on his Debian (GNOME) system running an AMD Athlon x64 4600+ processor with an old nVidia nForce integrated GPU. Cheers, Madhurjya Roy On 12/12/2014, Adam Williamson adamw...@fedoraproject.org wrote: On Fri, 2014-12-12 at 12:10 -0500, Fred Smith wrote: On Fri, Dec 12, 2014 at 09:19:22PM +0530, Madhurjya Roy wrote: Hey guys, I understand that Gnome-3 simply doesn't work well without 3D video acceleration. i've not personally experienced that, so I don't know if your symptoms are what actually occurs without 3D accel. Now, I know your AMD processor includes a Radeon video unit, so you SHOULD be getting 3d accel. however, if you didn't install AMD/ATI's proprietary driver for it, you're probably depending on the open source driver instead, and I suppose it simply may not work very well with that particular chip. As I said, I have no direct experience, so I may be all wet here. Shell will run fine without 3D acceleration, it'll just be a bit slow and use some CPU time. It wouldn't do *this*, though. It's probably more a case of a bug in the radeon driver for the hardware in question which GNOME's rendering happens to hit, while the other desktops don't. I'd file the bug either against xorg-x11-drv-ati in RH Bugzilla or Product xorg, Component Driver/Radeon in bugs.freedesktop.org , including the stuff described in https://fedoraproject.org/wiki/How_to_debug_Xorg_problems . -- 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 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup f20-f21 kde broken deps
On Fri, 12 Dec 2014 08:58:02 -0800, Adam Williamson wrote: On Fri, 2014-12-12 at 11:00 +0100, Michael Schwendt wrote: On Fri, 12 Dec 2014 00:12:37 -0800, Adam Williamson wrote: I haven't seen a single person report a dep issue of this nature, and I spent most of release day in #fedora, and have been following G+, forum, and various news site feedback since. Violated upgrade path issues still hit users. One example: R in F21 older than in F19 https://lists.fedoraproject.org/pipermail/users/2014-December/456108.html Other users don't ask the Fedora Project but just give up and hope it will work some months later (which isn't guaranteed either). That's not a dependency problem. Nothing breaks. Really? Just comparing the RPM based dependencies in the builds for F20 and F21 reveals several changed SONAMEs. That is a broken dependency by definition, because F21 does not provide the stuff that's required by the F20 package. @ -4,7 +4,7 @@ /bin/sh /bin/sh /bin/sh -config(R-core) = 3.1.2-1.fc20 +config(R-core) = 3.1.2-1.fc21 cups gawk ld-linux-x86-64.so.2()(64bit) @@ -30,15 +30,15 @@ libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.3.1)(64bit) libgfortran.so.3()(64bit) -libgfortran.so.3(GFORTRAN_1.0)(64bit) libglib-2.0.so.0()(64bit) libgobject-2.0.so.0()(64bit) libgomp.so.1()(64bit) libgomp.so.1(GOMP_1.0)(64bit) +libgomp.so.1(GOMP_4.0)(64bit) libgomp.so.1(OMP_1.0)(64bit) libICE.so.6()(64bit) -libicui18n.so.50()(64bit) -libicuuc.so.50()(64bit) +libicui18n.so.52()(64bit) +libicuuc.so.52()(64bit) libjpeg.so.62()(64bit) libjpeg.so.62(LIBJPEG_6.2)(64bit) liblapack.so.3()(64bit) @@ -59,10 +59,11 @@ librt.so.1()(64bit) librt.so.1(GLIBC_2.2.5)(64bit) libSM.so.6()(64bit) -libtcl8.5.so()(64bit) +libtcl8.6.so()(64bit) libtiff.so.5()(64bit) libtiff.so.5(LIBTIFF_4.0)(64bit) -libtk8.5.so()(64bit) +libtk8.6.so()(64bit) +libtre.so.5()(64bit) libX11.so.6()(64bit) libXext.so.6()(64bit) libXmu.so.6()(64bit) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup f20-f21 kde broken deps
On Fri, 2014-12-12 at 19:37 +0100, Michael Schwendt wrote: On Fri, 12 Dec 2014 08:58:02 -0800, Adam Williamson wrote: On Fri, 2014-12-12 at 11:00 +0100, Michael Schwendt wrote: On Fri, 12 Dec 2014 00:12:37 -0800, Adam Williamson wrote: I haven't seen a single person report a dep issue of this nature, and I spent most of release day in #fedora, and have been following G+, forum, and various news site feedback since. Violated upgrade path issues still hit users. One example: R in F21 older than in F19 https://lists.fedoraproject.org/pipermail/users/2014-December/456108.html Other users don't ask the Fedora Project but just give up and hope it will work some months later (which isn't guaranteed either). That's not a dependency problem. Nothing breaks. Really? Awesome, so now you have me running a test install of F20 with R just to see what happens in this situation. There's certainly no other way I could be using my damn morning. We seem to keep going in circles here. Here's what I'm contending: * Any particular fedup test is only of value, regarding package upgrade path issues, for that particular day's compose of *both* the 'from' distro *and* the 'to' distro. We started debating this last week, and there was at least one updates push for *both* F20 *and* F21 between last week and the GA date. So 'failures' for fedup upgradepath last week were not necessarily failing on release day. Is it useful to catch upgradepath issues and then go to Bodhi, look into the state of the from and to distros, and try to help make sure they're consistent for release day? Of course it is. But with the way updates currently work, I think it's taking things too far to say that it's worthless to test upgrades against updates-testing, which was one place where we started this endless debate. * The obvious way you can really 'solve' this 'problem' is to tighten down the updates policy, but that's not a free action. It *does* come with negative consequences and there *will* be pushback against it from packagers. Personally I am totally happy if anyone wants to come up with a comprehensive proposal for adjusting the updates policy and *take it to FESCo*, who own the updates policy. If someone comes up with such a proposal, we can even put it up for discussion on this list or in a QA meeting and decide if QA as a whole wants to back it in the FESCo discussion. But I'm just tired of going around in endless discussion, especially when no-one seems to acknowledge the issue just isn't as straightforward as 'oh well it's OBVIOUSLY wrong and we should OBVIOUSLY just have strict upgradepath enforcement'. The other path you can take is to try and convince wwoods to have fedup do distro-sync. The bug reports for that are https://bugzilla.redhat.com/show_bug.cgi?id=892061 and h ttps://github.com/wgwoods/fedup/issues/21 . Given that wwoods filed https://github.com/wgwoods/fedup/issues/21 himself, I'm guessing he'd welcome a patch. -- 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: Fedora/Gnome3 : Display Problem on my hardware.
On Fri, 2014-12-12 at 23:52 +0530, Madhurjya Roy wrote: Thank you for the response! As a high school student, I'm no expert in the department but shouldn't it be actually a GNOME3 shell bug, considering the fact that the same driver worked when used with other DEs? Likely not. As I wrote, it's most likely just that GNOME is exercising rendering paths the other desktops aren't. It uses OpenGL rather more in desktop rendering than most desktops do. You can certainly choose to file a bug against a GNOME component if you like (I'd guess either gnome-shell, mutter, or clutter), I just suspect it'd get pinged around a couple of components and then they'd wind up telling you file a graphics driver bug... -- 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
Successful install of F21-Xfce on Lenovo x120e
Install went smoothly. Took about an hour for a netinst from my local repo. Was able to add local updates repo per Adam's instructions. Yes, system got hot during install; both CPUs at max and who knows what else. Still need to tear into the unit to see if the heatsink is on right. No problems with nvram. I suppose once this was fixed with a Fedora entry, nothing furture needed. System boots up. So now it will be moving everything over, installing all the stuff I had on my old system. And submit bug reports on Xfce as I go (like turning off screen on lock). Have a good weekend all. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Successful install of F21-Xfce on Lenovo x120e
On Fri, 2014-12-12 at 15:21 -0500, Robert Moskowitz wrote: Install went smoothly. Took about an hour for a netinst from my local repo. Was able to add local updates repo per Adam's instructions. Yes, system got hot during install; both CPUs at max and who knows what else. Still need to tear into the unit to see if the heatsink is on right. No problems with nvram. I suppose once this was fixed with a Fedora entry, nothing furture needed. FWIW, any UEFI Fedora install will remove and recreate the 'Fedora' entry, so it sounds like that worked. -- 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: Fedora/Gnome3 : Display Problem on my hardware.
On Fri, Dec 12, 2014 at 11:52:10PM +0530, Madhurjya Roy wrote: Thank you for the response! As a high school student, I'm no expert in the department but shouldn't it be actually a GNOME3 shell bug, considering the fact that the same driver worked when used with other DEs? And if indeed, it's a driver problem, then the problem should lie within AMD's main codebase. That'd explain the fact that even the proprietary drivers couldn't resolve the issue. I'm also wondering if the problem is in anyway associated with some AMD CPUs in general! One of my friends, also noticed some occasional minor distortions on his Debian (GNOME) system running an AMD Athlon x64 4600+ processor with an old nVidia nForce integrated GPU. In that case it's not an AMD/ATI graphics processor, it's NVIDIA. I've been running AMD CPUs with NVidia graphics cards for years and haven't encountered such problems (though I have to admit that I can't stand Gnome-3.x and use it only long enough to install Mate.) I have, otoh, run Gnome-2.x on those systems for all those years and can't say I've ever seen any such problem on them. Fred -- Fred Smith -- fre...@fcshome.stoneham.ma.us Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. - Isaiah 40:28 (niv) - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup and distro-sync
On 12/12/2014 01:16 PM, Adam Williamson wrote: The other path you can take is to try and convince wwoods to have fedup do distro-sync. The bug reports for that are https://bugzilla.redhat.com/show_bug.cgi?id=892061 and h ttps://github.com/wgwoods/fedup/issues/21 . Given that wwoods filed https://github.com/wgwoods/fedup/issues/21 himself, I'm guessing he'd welcome a patch. Apparently redhat-upgrade-tool (which appears to be a fork of fedup) doesn't use distro-sync either, despite the fact that there is NO attempt to make sure package versions in RHEL7 are greater than RHEL6, which leads to total carnage: https://bugzilla.redhat.com/show_bug.cgi?id=1173713 -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
2014-11-24 @ 16:00 UTC - Fedora QA Meeting - Minutes
== #fedora-meeting: Fedora QA meeting == Meeting started by adamw at 16:00:34 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-11-24/fedora-qa.2014-11-24-16.00.log.html . Meeting summary --- * Roll call (adamw, 16:00:53) * Fedora 21 Final status (adamw, 16:05:40) * AGREED: TC4 to go today with cockpit and freeipa fixes (and something from mclasen for #1160499) (adamw, 16:14:54) * AGREED: we'll run a blocker review meeting after this meeting (yay meetings) (adamw, 16:21:31) * LINK: https://lists.fedoraproject.org/pipermail/test/2014-November/123936.html (roshi, 16:29:08) * ACTION: adamw to mail desktop@ about release blocking status of high-contrast icons (adamw, 16:36:42) * Test Days (adamw, 16:40:58) * last test day, Atomic, went off OK, that should be the end of the F21 Test Days - thanks all who helped out (adamw, 16:43:31) * Open floor (adamw, 16:45:54) Meeting ended at 16:53:05 UTC. Action Items * adamw to mail desktop@ about release blocking status of high-contrast icons Action Items, by person --- * adamw * adamw to mail desktop@ about release blocking status of high-contrast icons * **UNASSIGNED** * (none) People Present (lines said) --- * adamw (71) * roshi (36) * nirik (13) * jreznik_2nd (10) * sgallagh (10) * zodbot (9) * kparal (7) * mclasen (5) * pwhalen (2) * kinokoio (2) * jreznik (2) * smccann (1) * tflink (1) * pschindl (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- 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
2014-12-08 @ 16:00 UTC - Fedora QA Meeting - Minutes
== #fedora-meeting: Fedora QA meeting == Meeting started by adamw at 16:00:38 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-12-08/fedora-qa.2014-12-08-16.00.log.html . Meeting summary --- * Roll call (adamw, 16:00:52) * Fedora 21 - thanks! (adamw, 16:04:08) * thanks to everyone for Fedora 21 testing work, great job (adamw, 16:05:18) * Fedora 21 final check-in (adamw, 16:05:52) * temporary bug in fedup #1171473 is a releng issue, should be sorted soon (adamw, 16:08:00) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1171787 also dup? (satellit, 16:08:16) * adamw has done the initial final release version of https://fedoraproject.org/wiki/Common_F21_bugs , please nominate any further bugs for the page by adding CommonBugs keyword (adamw, 16:09:53) * multiple people have seen the corrupted console output while fedup is running until you hit a key, we will make sure it's filed and Common Bugs'ed (adamw, 16:13:49) * Fedora 22 planning (adamw, 16:19:31) * LINK: http://kojipkgs.fedoraproject.org/mash/ (adamw, 16:22:52) * AGREED: we will try to implement the plan of organized early (pre-Alpha TC1) installer validation testing for Fedora 22 (adamw, 16:45:06) * ACTION: roshi to look at implementing a compose event listener in taskotron (adamw, 16:45:17) * ACTION: adamw to work on wiki magic and relval (adamw, 16:45:29) * we will continue to discuss blocker review process improvements and discuss more specific proposals as they are made (adamw, 16:46:06) * so far we see no specific QA concerns in the tick/tock discussion, we will continue to monitor (adamw, 16:51:32) * roshi will work on co-ordinating test days again this cycle, he's happy to have any help if anyone else wants to join in on that (adamw, 16:55:09) * pschindl will help roshi with test day co-ordination (adamw, 16:56:06) * Open floor (adamw, 17:01:26) Meeting ended at 17:12:01 UTC. Action Items * roshi to look at implementing a compose event listener in taskotron * adamw to work on wiki magic and relval Action Items, by person --- * adamw * adamw to work on wiki magic and relval * roshi * roshi to look at implementing a compose event listener in taskotron * **UNASSIGNED** * (none) People Present (lines said) --- * adamw (172) * kparal (43) * sgallagh (42) * roshi (33) * tflink (16) * bcl (13) * danofsatx-work (12) * jreznik (11) * satellit (10) * brunowolff (7) * zodbot (4) * pwhalen (3) * amita (2) * pschindl (2) * Guest26560 (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- 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: Fedora/Gnome3 : Display Problem on my hardware.
Hi! Does it look like something like this: http://snag.gy/AGPaq.jpg I've started having the problem on F20 after a xorg update about 3 weeks ago and it has stayed. I upgraded (new install though) to F21 to get the same result unfortunately. It's also a Radeon (HD 6770 though) card. Thanks. Fred On 12/12/2014 10:49 PM, Madhurjya Roy wrote: Hey guys, My old PC MoBo recently died and so, I built a new PC with the following hardware specification : * Processor : AMD A4-6300K 3.7 GHz Dual Core APU with integrated Radeon HD 8370D GPU * MoBo : MSI A58M-E33 * RAM : 4 GB Corsair Value RAM 1600 MHz. * HDD : 500 GB WD Caviar @ 7200 rpm * Monitor : 19 inch Samsung SyncMaster at 1400 X 900 pixels @ 60-75 Hz refresh rate So, I went ahead and popped in the Fedora 21 Workstation Disc. Anaconda worked well and installed Fedora 21. But as soon as I restarted my PC and logged in I found the desktop flickering! I moved the mouse pointer and it flickered even more vigorously and when I pulled through the activities hot corner, I could barely see the icons, which appeared like distorted squares. Somehow, I managed to open the terminal. All the text in the terminal were clearly visible, I installed Xfce desktop and to my surprise it worked fine, text and icon everything was clear and perfectly usable. Next, I installed KDE and it worked as well. I really had trouble understanding the wobbly widgety interface, though! So, I assumed the problem is with Gnome 3. I reinstalled the complete Gnome desktop and alas, the problem persisted! I have used Fedora 20 for quite some time on my laptop, so, I booted a live image of Fedora 20, that I had had flashed onto a pen drive and still there was the same problem. Frustrated, I gave up and installed Ubuntu, Unity worked well but when I installed Gnome3, I was back where I was, running a completely graphically distorted UI! I've since changed many distros (without Gnome as DE) and all of them worked fine. Windows 8.1 worked fluidly as well! I am currently using Ubuntu 14.10 (with Unity as DE). I found it quite close to Gnome3. However, I would still like to use Fedora and since, I'm using this as a multimedia PC, so Gnome3 is still my preference. From my observations, it seems to be a Gnome 3 hardware incompatibility issue. I've tried changing refreshing rate, resolution and colour depth and nothing could solve the issue! Even switching to the proprietary AMD drivers didn't work out. Should I file a bug report on BugZilla? If anyone's got some idea, please help! Thanks, Madhurjya Roy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] 2014-12-15 @16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2014-12-15 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's meeting time again on Monday! Let's follow up on the action items from last week, and also pick up the agenda items we didn't get to, and maybe talk over the upgradepath debate a bit. As always, please reply to this mail if you'd like to propose any additional topics! == Proposed Agenda Topics == 1. Previous meeting follow-up * roshi to look at implementing a compose event listener in taskotron * adamw to work on wiki magic and relval 2. Tooling check-in: taskotron, blockerbugs, relval, etc 3. Release criteria changes (esp. multiboot) 4. Upgrade path discussion 5. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora/Gnome3 : Display Problem on my hardware.
It's quite similar to that, just more severe! In my case, when I open the 'activities' menu, there are square and triangular lines spread all over and almost none of the icons render correctly. Another thing worth pointing out is that applications are not affected by it. Most of the applications I ran (Nautilus, GIMP, Gnome Terminal, Application Settings) rendered correctly. The problem mainly affects the panel on the top, the calendar view that opens up from there (like the one in your picture) and the 'activities' menu. I'm downloading the Fedora live image, once it is done, I'll boot up and share some screenshots. I guess that'll provide a better idea of it. Madhurjya Roy On 13/12/2014, Frederic Muller f...@cm17.com wrote: Hi! Does it look like something like this: http://snag.gy/AGPaq.jpg I've started having the problem on F20 after a xorg update about 3 weeks ago and it has stayed. I upgraded (new install though) to F21 to get the same result unfortunately. It's also a Radeon (HD 6770 though) card. Thanks. Fred On 12/12/2014 10:49 PM, Madhurjya Roy wrote: Hey guys, My old PC MoBo recently died and so, I built a new PC with the following hardware specification : * Processor : AMD A4-6300K 3.7 GHz Dual Core APU with integrated Radeon HD 8370D GPU * MoBo : MSI A58M-E33 * RAM : 4 GB Corsair Value RAM 1600 MHz. * HDD : 500 GB WD Caviar @ 7200 rpm * Monitor : 19 inch Samsung SyncMaster at 1400 X 900 pixels @ 60-75 Hz refresh rate So, I went ahead and popped in the Fedora 21 Workstation Disc. Anaconda worked well and installed Fedora 21. But as soon as I restarted my PC and logged in I found the desktop flickering! I moved the mouse pointer and it flickered even more vigorously and when I pulled through the activities hot corner, I could barely see the icons, which appeared like distorted squares. Somehow, I managed to open the terminal. All the text in the terminal were clearly visible, I installed Xfce desktop and to my surprise it worked fine, text and icon everything was clear and perfectly usable. Next, I installed KDE and it worked as well. I really had trouble understanding the wobbly widgety interface, though! So, I assumed the problem is with Gnome 3. I reinstalled the complete Gnome desktop and alas, the problem persisted! I have used Fedora 20 for quite some time on my laptop, so, I booted a live image of Fedora 20, that I had had flashed onto a pen drive and still there was the same problem. Frustrated, I gave up and installed Ubuntu, Unity worked well but when I installed Gnome3, I was back where I was, running a completely graphically distorted UI! I've since changed many distros (without Gnome as DE) and all of them worked fine. Windows 8.1 worked fluidly as well! I am currently using Ubuntu 14.10 (with Unity as DE). I found it quite close to Gnome3. However, I would still like to use Fedora and since, I'm using this as a multimedia PC, so Gnome3 is still my preference. From my observations, it seems to be a Gnome 3 hardware incompatibility issue. I've tried changing refreshing rate, resolution and colour depth and nothing could solve the issue! Even switching to the proprietary AMD drivers didn't work out. Should I file a bug report on BugZilla? If anyone's got some idea, please help! Thanks, Madhurjya Roy -- 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
[Test-Announce] 2014-12-15 @16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2014-12-15 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's meeting time again on Monday! Let's follow up on the action items from last week, and also pick up the agenda items we didn't get to, and maybe talk over the upgradepath debate a bit. As always, please reply to this mail if you'd like to propose any additional topics! == Proposed Agenda Topics == 1. Previous meeting follow-up * roshi to look at implementing a compose event listener in taskotron * adamw to work on wiki magic and relval 2. Tooling check-in: taskotron, blockerbugs, relval, etc 3. Release criteria changes (esp. multiboot) 4. Upgrade path discussion 5. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce
