Re: ask to test latest systemd build for systemd-resolved problems
> On Sat, Mar 27, 2021 at 01:19:01AM +0000, Gerard Ryan wrote: > > That's probably unrelated. This shouldn't happen, so maybe file > a bug. Maybe it's something about systemd-networkd or NetworkManager > not starting (whatever you use)? I've created the following but for that one: https://github.com/systemd/systemd/issues/19140 Thanks, Ger. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ask to test latest systemd build for systemd-resolved problems
(resending through lists.fp.o, since I'm not actually subscribed atm, so it was rejected) I was one of the people who experienced the problem with 246.12-1.fc33 on F33. With that version, I was able to resolve google.com and fedoraproject.org just fine, but it seemed I wasn't able to resolve most other domains that I tried (including duckduckgo.com and redhat.com). Just highlighting that as it sounds like other folks had issues with google.com but not other domains. With 248~rc4.git20210326.b240c08-1.fc33 from your copr build on F33, my wired ethernet (eno1) doesn't work, so it seems I've got other issues with that one. With 248~rc4.git20210326.b240c08-1.fc34 from your copr build on F34 on that same machine (different ostree), I don't appear to have any networking issues -- I'm able to connect to the network and resolve all of the domains that I tried. Let me know if you'd like me to try anything in particular in either of those scenarios: I've got each one available as a pinned ostree deployment in silverblue, so it's easy to get back to them. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Orphaning packages
Hi all, I no longer use the following packages nor have the time to maintain them, so I'm going to orphan them: - aether-connector-okhttp - dtdparser - eclipse-jbosstools - eclipse-m2e-core - eclipse-webtools - javaewah - jboss-classpool-scoped - jboss-reflect - jbossxb - jdf-stacks-client - jhighlight - maven-indexer - minimal-json - nodejs-acorn - nodejs-carrier - nodejs-doctrine - nodejs-isarray - nodejs-tern - nodejs-tern-cordovajs - nodejs-tern-liferay - nodejs-typescript - okhttp - openshift-java-client - port-allocator-maven-plugin - smooks - takari-filemanager - takari-local-repository - truecommons - truecommons-parent - truezip - uddi4j - wise - wsil4j Thanks, Gerard. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Orphaning JBoss Tools package
On 11/02/2015 11:49 PM, Marcus Karlsson wrote: > On Sun, Nov 01, 2015 at 03:56:15PM +0000, Gerard Ryan wrote: >> Hi devel list (and cc'ed eclipse-sig list), >> >> I'm going to orphan the eclipse-jbosstools package in rawhide, as I'm no >> longer able to give it the time that it needs. My understanding is that >> if nobody takes it, it will be auto-retired after 6 weeks (please >> correct me if I'm wrong here). >> >> If you're interested in taking it & have any questions, I'm happy to >> provide any input I can. I think ideally it would want more than one >> active maintainer to get it into the shape that it needs to be (not all >> features are currently packaged, and significant effort would be >> required there). >> >> Thanks, >> Gerard. > > Hi Gerard. > > I'm interested in stepping up and maintaining this package as I > occasionally use it and would love to see it fully supported on Fedora. > :-) > > Marcus > Hi Marcus, That's great to hear that you're interested in it. Like you said, it would be great to see all of it in Fedora, since it's great for the kind of development that it targets. Currently it doesn't build in Rawhide because of missing dependencies. Also there's a new release that I spend a couple of weekends trying to get to work, but eventually failed. Have you had a chance to look at it yet and try it out? Gerard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Orphaning JBoss Tools package
Hi devel list (and cc'ed eclipse-sig list), I'm going to orphan the eclipse-jbosstools package in rawhide, as I'm no longer able to give it the time that it needs. My understanding is that if nobody takes it, it will be auto-retired after 6 weeks (please correct me if I'm wrong here). If you're interested in taking it & have any questions, I'm happy to provide any input I can. I think ideally it would want more than one active maintainer to get it into the shape that it needs to be (not all features are currently packaged, and significant effort would be required there). Thanks, Gerard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announcing the release of Fedora 23 Beta!
On 10/18/2015 06:49 PM, Andreas Tunek wrote: > 2015-10-02 21:20 GMT+02:00 Gerard Ryan <gali...@fedoraproject.org>: >> On 10/02/2015 07:11 PM, Andreas Tunek wrote: >>> 2015-09-26 0:10 GMT+02:00 Thomas Daede <bztdli...@gmail.com>: >>>> On 09/25/2015 02:18 PM, Andreas Tunek wrote: >>>> >>>>> Removed librtmp (what could go wrong?), now I get the following error: >>>>> >>>>> Sep 25 23:14:39 iMacLinux dnf[621]: Error: package >>>>> kernel-core-4.1.7-200.fc22.x86_64 requires systemd >= 200, but none of >>>>> the providers can be installed >>>>> Sep 25 23:14:39 iMacLinux dnf[621]: (try to add '--allowerasing' to >>>>> command line to replace conflicting packages) >>>>> Sep 25 23:14:39 iMacLinux systemd[1]: dnf-system-upgrade.service: main >>>>> process exited, code=exited, status=1/FAILURE >>>>> Sep 25 23:14:39 iMacLinux systemd[1]: Unit dnf-system-upgrade.service >>>>> entered failed state. >>>>> Sep 25 23:14:39 iMacLinux systemd[1]: dnf-system-upgrade.service failed. >>>>> Sep 25 23:14:39 iMacLinux systemd[1]: Rebooting as result of failure. >>>>> >>>> >>>> This looks like it might be related to >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1244175 >>>> >>>> I had a similar problem. --allowerasing will try to erase the currently >>>> running kernel, which will fail. >>> >>> Seems like the above is a blocker now. I will test again when updated. >>> >> >> FWIW I think you're hitting the same issue as I am, reported here: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1266589 >> >> -- > > I still can't upgrade, I get: > > dnf system-upgrade download --releasever=23 --distro-sync > dnf system-upgrade reboot > > ... > Oct 18 19:45:47 iMacLinux dnf[668]: Error: package > kernel-core-4.2.3-200.fc22.x86_64 requires systemd >= 200, but none of > the providers can be installed > Oct 18 19:45:47 iMacLinux dnf[668]: (try to add '--allowerasing' to > command line to replace conflicting packages) > Oct 18 19:45:47 iMacLinux systemd[1]: dnf-system-upgrade.service: main > process exited, code=exited, status=1/FAILURE > Oct 18 19:45:47 iMacLinux systemd[1]: Unit dnf-system-upgrade.service > entered failed state. > Oct 18 19:45:47 iMacLinux systemd[1]: dnf-system-upgrade.service failed. > Oct 18 19:45:47 iMacLinux systemd[1]: Rebooting as result of failure. > Oct 18 19:45:47 iMacLinux audit[1]: pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=dnf-system-upgrade comm="systemd" exe= > ... Hi Andreas, Yes, I'm in the same situation. Would you mind adding the info of what you get to the bug in bugzilla so that the maintainers can see it all in one place (it's difficult for everyone to keep up with this mailing list all the time) and know that there are more people experiencing it. Thanks a lot, Gerard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announcing the release of Fedora 23 Beta!
On 10/19/2015 07:47 PM, Reindl Harald wrote: > > > Am 19.10.2015 um 20:35 schrieb Gerard Ryan: >> On 10/18/2015 06:49 PM, Andreas Tunek wrote: >>> I still can't upgrade, I get: >>> >>> dnf system-upgrade download --releasever=23 --distro-sync >>> dnf system-upgrade reboot >> >> Yes, I'm in the same situation. Would you mind adding the info of what >> you get to the bug in bugzilla so that the maintainers can see it all in >> one place (it's difficult for everyone to keep up with this mailing list >> all the time) and know that there are more people experiencing it > > any bet "dnf --releasever=23 --distro-sync" followed by a reboot just > works as online dist-upgrades are working *for years* on dozens fo > machines while all the offline-updatem, pre-upgrade and whatever stuff > was *never* reliebale Thankfully I only ever have one or two systems to update. :) Even if that online way that you mention works, I'm going to hold off until the "recommended" (is it?) way works, since otherwise I won't have any way to verify the fix when it comes. Let's hope that once these issues are ironed out that it will be as reliable as any other way. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announcing the release of Fedora 23 Beta!
On 10/02/2015 07:11 PM, Andreas Tunek wrote: > 2015-09-26 0:10 GMT+02:00 Thomas Daede: >> On 09/25/2015 02:18 PM, Andreas Tunek wrote: >> >>> Removed librtmp (what could go wrong?), now I get the following error: >>> >>> Sep 25 23:14:39 iMacLinux dnf[621]: Error: package >>> kernel-core-4.1.7-200.fc22.x86_64 requires systemd >= 200, but none of >>> the providers can be installed >>> Sep 25 23:14:39 iMacLinux dnf[621]: (try to add '--allowerasing' to >>> command line to replace conflicting packages) >>> Sep 25 23:14:39 iMacLinux systemd[1]: dnf-system-upgrade.service: main >>> process exited, code=exited, status=1/FAILURE >>> Sep 25 23:14:39 iMacLinux systemd[1]: Unit dnf-system-upgrade.service >>> entered failed state. >>> Sep 25 23:14:39 iMacLinux systemd[1]: dnf-system-upgrade.service failed. >>> Sep 25 23:14:39 iMacLinux systemd[1]: Rebooting as result of failure. >>> >> >> This looks like it might be related to >> https://bugzilla.redhat.com/show_bug.cgi?id=1244175 >> >> I had a similar problem. --allowerasing will try to erase the currently >> running kernel, which will fail. > > Seems like the above is a blocker now. I will test again when updated. > FWIW I think you're hitting the same issue as I am, reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1266589 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
minimal-json license change
Howdy, The recent update of minimal-json in Rawhide to version 0.9.4 has changed the license from EPL to MIT. An update for f23 will follow. Thanks, Gerard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Not-very-reassuring info on FedUp wiki page for F21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi devel, On the Important Changes in the Upgrade process to Fedora 21 on the FedUp wiki page[1], I see the following: Apparently there will be a new option --product=PRODUCT and before update you will be required to choose one of the possibilities. To obtain the old behaviour apparently --product=nonproduct should be used. I think this could be improved to give more sure directions. I know it's a wiki, and just edit/fix it, but I don't know enough about what it should be to confidently change it. Could someone who is more sure than I (and the original author, apparently) of what it should be weigh in? Is it just a case of removing the apparently(s)? [1] https://fedoraproject.org/wiki/FedUp Thanks a lot, Gerard. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUhK6lAAoJEG7cfkpivEoVIX8QAIC+FDz+dtD8GKFpq+xWOyxj 3JO0GRPw9T4UTbK/GqL30n3SFP0syHDcqIjFHhieQOOtGPslDorpVbEugmhByilj H+1PXaWu7Di4nLFWsr0oAiO6xld1ZijsHo5das1ELOD/j2M+C7UR9N7VFZqR2PPk pqhCNGiZiihm75ucoZvIsdkGqBQqqbKGCMeDB/3h2dq6Ph9D/0X1nVDzRQLzOID+ 2hCLPeMG0KjBrcDb7jHbSTAJsuhW4pZb3BSjgw/skQnTYhNcV/MiivEVXiiULdOq 4GOlvMiP7OW/d0etIQiOdc1T3VPglyK8O2fNsuvOlYyHTchKghbKc8hyGbF/CUso NjJn60lXynNHiFsfoE3gGUHXMjpTUcm1XDkKwYANBMj2aJ/vnzCHadQHBsk/4Bxr GZ3j5hB/NI9nbwmjtZFmsSZzE3Y6N1qcKCJkBaI60uOZ8OWHtz61FM6IIZpHAOPD dllGCtV9Ua3rd8ngkELZ11HGBFzIqQuCdXAXovEkpz5UlUrdy0FUNFd/hX0937yi xi0ffwMqyqY3eaVq1pJB8qMMljHr98kN4nrcFtis2Scpg+CGTOm9DtT1ko+LP/7a cvKJXvVPU/6yqQN2qdU7iuuyxww/F93Hm3YJkl/FMVIoN0xVMbjLUzgFWio7EciH 1VdxNySxevr9tss4d/uX =plgB -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Not-very-reassuring info on FedUp wiki page for F21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/12/14 22:00, Matthew Miller wrote: On Sun, Dec 07, 2014 at 01:49:47PM -0800, Samuel Sieb wrote: [1] https://fedoraproject.org/wiki/FedUp I was about to go edit it, but I see that mattdm has already fixed it. :-) Very quickly. If you have further refinements, go for it! Very quickly indeed! Thanks a lot! :) Gerard. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUhNe+AAoJEG7cfkpivEoVdesQAJgC0yMkqnU9nedn5AgelqdP jkrxmAGJyu4awaaO/YLfa/1Rky+6H3QnNeXuM5y26TwxugDqV5XlbN+kwfOo4dfK +ntt/QaOSphqYR4TJcGaK0ETSMvyKsnZ+VkvE84vILZ3M9Fpf9vZxY1QgBNigqNA pWvAoJRBL7rl9TZeyFBcxjQGRVD5iJCgs2AjI1xQsesN3fpdV8W5ZlJGJQDDe/tY zAZsuTI751NgMEmw63OBFtkzKb0wCtSxLpCQ+cX3+VVaLI9bigj4qs22OHohggvA vKPMopEynvuvYdFkgICvF/DjlEPhQqhMd2G5/iAPSGqHcBx0AgI4R4Pmbe1jNdr7 j3F5mpHKpFSHnKbQkn6tJW9EyzG5Ae69/+ba4hptTkB+KFMFE1hYO0XJ5JGGZubV ED+BdLmgg7FI3d79g6jq5dLo27GgE3do5qmrWoPZBZQUi9O9vr5U5khP4w6ieDo4 BFHb+ku5GGvSSBvXPj4enfhvSmarRDy1ZYH0eGdJtLNhW9TEv7EINs4ff233lmBs dVclj/O9nr/EFI/3dr0QnW3q6WzFO3MuVVKyNzau67HeQb7NXFcUpXpSHKFEU3xV WqE/mw1FW3OTs4TQ1LDeR9otugU5+bsXnqbv28iwWiIw5KFWXzu9ecNUkJYwx9ox /bn9Ay8eu85KP5pkxa0E =qbpA -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Trouble retiring package on F21 branch
Hi, We're trying to retire package eclipse-wtp-common on F21 and Rawhide. My understanding is that this should be done F21 first, then Rawhide. F21 has proven problematic so far. Bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=1117475 History: 1. Package eclipse-wtp-common is obsoleted/provided by eclipse-webtools subpackage 2. A package administrator (note: not owner), tries to use fedpkg to retire, but it fails: Performs dead.package commit, then can't change point of contact to orphan in the second part of that process. 3. Proven packager comes to help; tries to retire, gets message You are not allowed to retire this package. 4. Package owner comes along, tries to retire. Get's a little further in that the package is now orphan for that branch, but then gets message: You are not allowed to retire the package: eclipse-wtp-common on branch f21 Is there something additional that we need to do, or is there something in the above sequence of events that has screwed things up? Or is F21 in some state that is preventing package retirement? Or is it something else? Thanks in advance for any help that any of you can provide! Gerard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Considering GNOME 3.12 as an F20 update
On Thu, Apr 3, 2014 at 7:50 PM, Matthias Clasen mcla...@redhat.com wrote: Did you experience crashes or other serious problems with applications ? Hi Matthias, I had a problem with the new totem/Videos having a non-responsive UI. I'm away on a work assignment until the 13th so unfortunately I can't verify that it's still a problem or if it was some bad configuration that I had. From what I remember, videos directly in my home directory were displayed as thumbnails on the main window and they would play fine. If I tried to add/open a local video from another location (even subdirectory of my home) by clicking on the + at the corner, nothing happened. I wasn't given an open file dialog or anything like that. As I said, it may not actually still be a problem. Maybe someone else can verify? Thanks, Gerard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: /usr/lib/java
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, Jun 16, 2013 at 08:48:38PM +0200, gil wrote: hi, I would like to report this: in my F18 there is something of wrong... /usr/lib/java/ java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/ in each java folder file:///usr/lib/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/jansi-native-linux.jar file:///usr/lib/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/jffi.jar file:///usr/lib/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/jss4.jar file:///usr/lib/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/java/swt.jar regards gil Problem looks to be that %{_libdir}/java/java is a misplaced symlink to its parent %{_libdir}/java/ Gerard. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) iQIcBAEBCAAGBQJRvrESAAoJEG7cfkpivEoVjlIP/12r+7ulsY6fYEuee4rIiXlY UOX4pvqEQ12w3WYINZlAfolhY08PqJTMIoV6aNWTqYtOuUI2pFdqE5/sgSXJmrYS FLIifV+3ueGpPVhPzCpr+BmtTgCgdi50htFItv9beZuSeJ1y2Y5LsnklPI4+bOZM nnWyQ6CixNS7drFl9lmkd4VLiW0leb+ZgSgtz34eZUqdb3suBESRDRQxgOz7cbsR rBjs+e8fz39C0cKp/fTU/2e1XxfArSH5qz2x1hiLJXD0VRy0n3U+Buw+IiOx0zzf eR6rMpBE8jXTokaEAlTiLJG9xGVqTGkENL70xVPo9OO8Ftu4rTEoo+T/It0J28xD Iz194SA94i86WrsFYY5dJm4LDUOe4Bvim+2Wy2XvvKCbv8j1NewqOTcUoU1axqCA D0tg7XbfeEBs+JFnGxiLhnPdI3NZ4H7euL9okQf/oN05VUzKG9fLmg2S7aL0OvwA /UIHUgEF5YWtFpsmxHxYuTuu8JJf3/HufwHQRFPfbyFAPnm/RcZduNDEaeC3Dprm wy4APMBuJzY1a2lJQCtTKP9RnXXQKxlf0KquLf8zpNZZVruT0PZ9wjD7wVhQsz6r 5bE4Gn6yuMPT9OHolgpImTphUK4ireFrB8S3YoWXVNjy7i40JD48VVn+8J5zAenW rIg2KT2LDshrQkfG8VsC =odD1 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Customizing Firefox Search.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Feb 14, 2013 at 07:03:41AM -0500, Daniel J Walsh wrote: Any know of a way to build a customized search into firefox. Basically I want to setup a search pull down which is hard coded to a particular site. For example, add a menu item called MyBlog And what ever I put into the search window ends up going to google as $SEARCHTEXT site:danwalsh.livejournal.com You could use a custom bookmark with a keyword for this. I don't know all of the different parameters in a google search url, so here's an example using DuckDuckGo: 1. Create a new bookmark with the following as the url: https://duckduckgo.com/?q=site%3Adanwalsh.livejournal.com+%s 2. Set the keyword to something such as: dw 3. In the url bar, you should now be able to search for $SEARCHTEXT on your site by typing simply: dw $SEARCHTEXT How to add a keyword to a bookmark isn't obvious in my opinion, so here that is too: 1. Hit Ctrl+Shift+o to open the main bookmarks window 2. On the left pane, click on unsorted bookmarks (or wherever you want the bookmark to be located, I don't think it matters much). 3. From the 'Organize' menu at the top of that window, choose 'New Bookmark'. 4. A 'New Bookmark' dialog appears. In the 'Location' field, enter the custom url from above (or if you want, an equivalent of your own crafting, with %s as the $SEARCHTEXT). In the 'Keyword' field, enter what you would like the keyword to be (dw in the example above). I hope this helps! Gerard. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) iQIcBAEBAgAGBQJRHQSaAAoJEG7cfkpivEoVp5gQAIVSMomvONfmm2XDj5HnWL0V UgqsQHEIUr4knb0GlkJPQCdNV9ZYFZz9lIR7OZEUuGn0O9ySqJji+lNnZpnV80cL mn4kly5F+FJ7mO1chKOeTd6A/gGJnLD2vHMqUcNFAbQDca8MYdiEeDTjrdYawZvB PO7eNcgd/VbZdNSV0BFtlnbn8U9trxMvEIlKGv0rlbf/i1WeA5ujREbLGXsSj5D8 0kr0/CyEWWzbBCDlniHfQOlLUdTCeju6HkR2jqV2XOiEspsDEvdDyULFbdHx4JIH ofDjs6QAztscpJUAPgIy0uJoId4XxW5kwrVS1rqazM2w2cgUqKov5F0VfWGvv06t ZVQQfZcfWd3ceI24mZpwvD1LbKZUv+xXnd/xcnwSHLeEYzw62vRT7W5eXTC416uF CiW3Cxp6hZ/T2gEhoqTNUDtXAcvpCBg82meKQ1EgzZ06h7jkPgEqqg12n2GGRKBK Ypi8zb5d3WCP73K/kBYUOCwgpRwnIsG6Ab6HikIhnX82KQ8CMG/nSNOT3W5O7nYr m0vfKvxHg+RxEpo/+rbpeaS+2rL2Mx1I6TZ0uYAOKdiwxEuQTwvyCWXc9yZlkeRK irJ2NVRww96Y95U5JBLYS5Scytj1XZCV971cmdSDNN+rTrmx2VYNJx2uojYYmOkJ pMh55wj3j4QJ7kwi47YH =1baN -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: To the Mate package maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jan 18, 2013 at 06:10:06PM -0500, Sam Varshavchik wrote: I see that Gnome's lock screen now shows a pretty clock, after the display wakes up, that must be swiped away in order to unlock the desktop. Somehow (and this would be the snarky part) I knew even before I started looking, that there seems to be no bloody way to turn it off, in case you don't feel fond of having to go through an extra step of unlocking a locked desktop. If you've got a keyboard, pressing enter at that clock cover screen will get it away so you don't need to swipe it. I know you probably know this already, but just in case you don't, it's definitely quicker than swiping with the mouse for me. - -- Gerard Ryan. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) iQIcBAEBAgAGBQJQ+d6IAAoJEG7cfkpivEoVJfkQAKHpxugL5Cq82X5fUzy0Basp 0J9NtwYq1G35hOcCUuMjOWyb233eEmsgkxOvztcvHuI6ShCyj+K8LQIPXXYllrik ZjN42axPKyR+1qaNHf8e2nevvB/rlzgaxe+Si8VzsZbC065PTOPhi+WHLrdnFuGd FwXfCDlJhLDYFDhsaseZI3m2FvCA/p6xzylTMy6BeNDJMw7MgT7K37llgjYs0MI/ IfCSF+MGq4wigdOqlLm3tuJbIoOBeq/C8oL3BjQTRxHsMuCirVjbM0qScv+cteu0 7b6Ye6xDl9agnzhhQAfh0szD44s7qK1AdWS9dv2aoeqk+oQ1dFtDf+LcTmMYBw2d ivYnCqvTfBCwWkocxkpiDml9e1YB1rbcZgkGgkGPOKIB3J7ZyExjOCsdj/ZlIqWw jxeEN2IoK7j2el6Orgjhh6hhGigprMQurnLNBM5/dd9j8LGvb9p21rYSacWgKCEd WeynoPcRGJYbrIidy/h1IQpX+EKFShfTeuNJwWghNvUaHNHsufcPP+COxzRQEBsB 0GRXgien66jV4ws1KBmYIid6icfvuebgixdgDI+SSFkPI16/kf/UphaYsU9QlY8t w9rn6hDd2vEuNMaNA1Qw/0JjLrCbvHOZA6Mv0Ax0NHyKAgCk693stMqZo4XDOLWP 4gmLgaEww4CKAkQN11pw =QrYn -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel