hp printer installation
Any attempt to install my hp4630 all-in one printer on a clean install F36 produces dialog saying "python3 not responding" and ultimately fails. Same printer has installed and worked as expected on F35 and many previous fedora installations. Installation attempt is for wireless connection. ___ 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: F36 pvcs problem
On 6/6/22 15:14, Florian Weimer wrote: * Roger Wells: we use pvcs here for CM and have for many years (~30). Currently we are using it on RHEL 7 & Fedora. On F35 (and earlier) no issues at all. On F36 (installed end of last week) some programs are not recognized and issue error message "not a dynamic executable" when examined with "ldd": any ideas? Have you installed glibc.i686? Genius, very good. That seems to be the cause. Plus a couple of others, eg libstdc++.i686. Thank you very much Thanks, Florian . ___ 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: F36 pvcs problem
On 6/6/22 15:13, Sérgio Basto wrote: Hi, what is pvcs ? an ancient commercial source code configuration management tool, first released 37 years ago On Mon, 2022-06-06 at 14:05 -0400, Roger Wells wrote: we use pvcs here for CM and have for many years (~30). Currently we are using it on RHEL 7 & Fedora. On F35 (and earlier) no issues at all. On F36 (installed end of last week) some programs are not recognized and issue error message "not a dynamic executable" when examined with "ldd": any ideas? which mlcproxy ~/pvcs/vm/linux/bin/mlcproxy [roger@rwells-x280 linux]$ mlcproxy bash: /home/roger/pvcs/vm/linux/bin/mlcproxy: No such file or directory [roger@rwells-x280 linux]$ ldd /home/roger/pvcs/vm/linux/bin/mlcproxy not a dynamic executable ___ 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 ___ 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: F36 pvcs problem
On 6/6/22 14:28, Stephen Smoogen wrote: On Mon, 6 Jun 2022 at 14:07, Roger Wells wrote: we use pvcs here for CM and have for many years (~30). Currently we are using it on RHEL 7 & Fedora. On F35 (and earlier) no issues at all. On F36 (installed end of last week) some programs are not recognized and issue error message "not a dynamic executable" when examined with "ldd": any ideas? I would check to see if there is an security issue as it saying `bash: /home/roger/pvcs/vm/linux/bin/mlcproxy: No such file or directory` either means its not there, or something going on. thanks for responding, It's there, and when copied to a CentOS7 machine runs fine. 1. stat /home/roger/pvcs/vm/linux/bin/mlcproxy 2. ls -lZ /home/roger/pvcs/vm/linux/bin/mlcproxy 3. file /home/roger/pvcs/vm/linux/bin/mlcproxy Also not sure if you are meaning the code is 30 years old, but if it is, I would wonder if it was an a.out binary which I think was dropped from the kernel recently. https://www.phoronix.com/scan.php?page=news_item=Linux-Remove-a.out <https://www.phoronix.com/scan.php?page=news_item=Linux-Remove-a.out> pvcs was actually first released 37 years ago. This release, 8.6.3 is just a year or so old. It works fine on F35 which mlcproxy ~/pvcs/vm/linux/bin/mlcproxy [roger@rwells-x280 linux]$ mlcproxy bash: /home/roger/pvcs/vm/linux/bin/mlcproxy: No such file or directory [roger@rwells-x280 linux]$ ldd /home/roger/pvcs/vm/linux/bin/mlcproxy not a dynamic executable ___ 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 -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-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___ 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
F36 pvcs problem
we use pvcs here for CM and have for many years (~30). Currently we are using it on RHEL 7 & Fedora. On F35 (and earlier) no issues at all. On F36 (installed end of last week) some programs are not recognized and issue error message "not a dynamic executable" when examined with "ldd": any ideas? which mlcproxy ~/pvcs/vm/linux/bin/mlcproxy [roger@rwells-x280 linux]$ mlcproxy bash: /home/roger/pvcs/vm/linux/bin/mlcproxy: No such file or directory [roger@rwells-x280 linux]$ ldd /home/roger/pvcs/vm/linux/bin/mlcproxy not a dynamic executable ___ 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: where is /1 coming from?
On 10/12/2016 10:58 AM, Chuck Anderson wrote: > Am I the only one who can't see the email body below? no > > On Wed, Oct 12, 2016 at 10:44:00AM -0400, pete0verse wrote: >> >> MIME-Version: 1.0 >> Content-Type: multipart/alternative; >> boundary="--_com.samsung.android.email_1427992738156800" >> >> _com.samsung.android.email_1427992738156800 >> Content-Type: text/plain; charset=utf-8 >> Content-Transfer-Encoding: base64 >> >> SSBoYWQgdGhpcyBpc3N1ZSBvZiAxIGluIC8gaW4gRjI0IEkgaGFkIHVwZ3JhZGVkIGZyb20gMjIu >> wqAKCgpTZW50IHZpYSB0aGUgU2Ftc3VuZyBHYWxheHkgUzcsIGFuIEFUJlQgNEcgTFRFIHNtYXJ0 >> cGhvbmUKLS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLUZyb206IEpvYWNoaW0gQmFj >> a2VzIDxqb2FjaGltLmJhY2tlc0ByaHJrLnVuaS1rbC5kZT4gRGF0ZTogMTAvMTIvMTYgIDEwOjM2 >> IEFNICAoR01ULTA1OjAwKSBUbzogRGV2ZWxvcG1lbnQgZGlzY3Vzc2lvbnMgcmVsYXRlZCB0byBG >> ZWRvcmEgPGRldmVsQGxpc3RzLmZlZG9yYXByb2plY3Qub3JnPiBTdWJqZWN0OiBSZTogd2hlcmUg >> aXMgLzEgY29taW5nIGZyb20/IApPbiAxMC8xMi8xNiAxNTowMywgTWF0dGhldyBNaWxsZXIgd3Jv >> dGU6Cj4gU29tZW9uZSBvbiBSZWRkaXQgbm90ZWQgdGhhdCB0aGVyZSdzIGEgemVyby1sZW5ndGgg >> ZmlsZSBuYW1lZCBgMWAgaW4gLwo+IG9uIHRoZWlyIEYyNSBzeXN0ZW0uIEkganVzdCBsb29rZWQg >> b24gbWluZSwgYW5kIEkgaGF2ZSBvbmUgdG9vLiBJdCdzCj4gbm90IG93bmVkIGJ5IGFueSBSUE0u >> IEFuZCBJIGNoZWNrZWQgb24gYW4gRjI0IGJveCwgYW5kIGl0J3MgZ290IHRoYXQKPiB0b28uIEFu >> eW9uZSBrbm93IHdoZXJlIHRoaXMgaXMgY29taW5nIGZyb20/Cj4KQWRkaXRpb25hbGx5IEkgc2Vl >> IGEgZmlsZSBjYWxsZWQgL251bGwgd2l0aCB6ZXJvIGxlbmd0aCEKCktpbmQgcmVnYXJkcwoKSm9h >> Y2hpbSBCYWNrZXMKCi0tIAoKRmVkb3JhIHJlbGVhc2UgMjUgKFR3ZW50eSBGaXZlKQpLZXJuZWwt >> NC44LjEtMS5mYzI1Lng4Nl82NAoKCkpvYWNoaW0gQmFja2VzIDxqb2FjaGltLmJhY2tlc0ByaHJr >> LnVuaS1rbC5kZT4KaHR0cDovL3d3dy11c2VyLnJocmsudW5pLWtsLmRlL35iYWNrZXMvCl9fX19f >> X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCmRldmVsIG1haWxpbmcg >> bGlzdCAtLSBkZXZlbEBsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1bnN1YnNjcmliZSBzZW5k >> IGFuIGVtYWlsIHRvIGRldmVsLWxlYXZlQGxpc3RzLmZlZG9yYXByb2plY3Qub3JnCg== >> >> _com.samsung.android.email_1427992738156800 >> Content-Type: text/html; charset=utf-8 >> Content-Transfer-Encoding: base64 >> >> PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 >> L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2PkkgaGFkIHRoaXMgaXNzdWUg >> b2YgMSBpbiAvIGluIEYyNCBJIGhhZCB1cGdyYWRlZCBmcm9tIDIyLiZuYnNwOzwvZGl2PjxkaXY+ >> PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgaWQ9ImNvbXBvc2Vy >> X3NpZ25hdHVyZSI+PGRpdiBzdHlsZT0iZm9udC1zaXplOjg1JTtjb2xvcjojNTc1NzU3IiBkaXI9 >> ImF1dG8iPlNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBTNywgYW4gQVQmYW1wO1QgNEcgTFRF >> IHNtYXJ0cGhvbmU8L2Rpdj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2IHN0eWxlPSJmb250LXNp >> emU6MTAwJTtjb2xvcjojMDAwMDAwIj48IS0tIG9yaWdpbmFsTWVzc2FnZSAtLT48ZGl2Pi0tLS0t >> LS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS08L2Rpdj48ZGl2PkZyb206IEpvYWNoaW0gQmFj >> a2VzICZsdDtqb2FjaGltLmJhY2tlc0ByaHJrLnVuaS1rbC5kZSZndDsgPC9kaXY+PGRpdj5EYXRl >> OiAxMC8xMi8xNiAgMTA6MzYgQU0gIChHTVQtMDU6MDApIDwvZGl2PjxkaXY+VG86IERldmVsb3Bt >> ZW50IGRpc2N1c3Npb25zIHJlbGF0ZWQgdG8gRmVkb3JhICZsdDtkZXZlbEBsaXN0cy5mZWRvcmFw >> cm9qZWN0Lm9yZyZndDsgPC9kaXY+PGRpdj5TdWJqZWN0OiBSZTogd2hlcmUgaXMgLzEgY29taW5n >> IGZyb20/IDwvZGl2PjxkaXY+PGJyPjwvZGl2PjwvZGl2Pk9uIDEwLzEyLzE2IDE1OjAzLCBNYXR0 >> aGV3IE1pbGxlciB3cm90ZTo8YnI+Jmd0OyBTb21lb25lIG9uIFJlZGRpdCBub3RlZCB0aGF0IHRo >> ZXJlJ3MgYSB6ZXJvLWxlbmd0aCBmaWxlIG5hbWVkIGAxYCBpbiAvPGJyPiZndDsgb24gdGhlaXIg >> RjI1IHN5c3RlbS4gSSBqdXN0IGxvb2tlZCBvbiBtaW5lLCBhbmQgSSBoYXZlIG9uZSB0b28uIEl0 >> J3M8YnI+Jmd0OyBub3Qgb3duZWQgYnkgYW55IFJQTS4gQW5kIEkgY2hlY2tlZCBvbiBhbiBGMjQg >> Ym94LCBhbmQgaXQncyBnb3QgdGhhdDxicj4mZ3Q7IHRvby4gQW55b25lIGtub3cgd2hlcmUgdGhp >> cyBpcyBjb21pbmcgZnJvbT88YnI+Jmd0Ozxicj5BZGRpdGlvbmFsbHkgSSBzZWUgYSBmaWxlIGNh >> bGxlZCAvbnVsbCB3aXRoIHplcm8gbGVuZ3RoITxicj48YnI+S2luZCByZWdhcmRzPGJyPjxicj5K >> b2FjaGltIEJhY2tlczxicj48YnI+LS0gPGJyPjxicj5GZWRvcmEgcmVsZWFzZSAyNSAoVHdlbnR5 >> IEZpdmUpPGJyPktlcm5lbC00LjguMS0xLmZjMjUueDg2XzY0PGJyPjxicj48YnI+Sm9hY2hpbSBC >> YWNrZXMgJmx0O2pvYWNoaW0uYmFja2VzQHJocmsudW5pLWtsLmRlJmd0Ozxicj5odHRwOi8vd3d3 >> LXVzZXIucmhyay51bmkta2wuZGUvfmJhY2tlcy88YnI+X19fX19fX19fX19fX19fX19fX19fX19f >> X19fX19fX19fX19fX19fX19fX19fX188YnI+ZGV2ZWwgbWFpbGluZyBsaXN0IC0tIGRldmVsQGxp >> c3RzLmZlZG9yYXByb2plY3Qub3JnPGJyPlRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwgdG8g >> ZGV2ZWwtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmc8YnI+PC9ib2R5PjwvaHRtbD4= >> >> _com.samsung.android.email_1427992738156800-- >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >
Re: F24, small backward steps
On 09/13/2016 04:03 PM, Michael Catanzaro wrote: > On Tue, 2016-09-13 at 14:33 -0400, Roger Wells wrote: >> It was the first problem, the one with deja-dup > > Where did you report the bug? The upstream bug tracker is [1]. If you > reported it somewhere else, of course you'd be told it's the wrong > place > > Unfortunately, I think deja-dup is unmaintained, so reporting bugs is > not likely to result in fixes. It's not even user-visible, for many > years, now due to some problem with the appdata file. But there's no > chance of a fix if the issue isn't reported, so still a good idea > if it is unmaintained why does its GUI operation change between Fedora versions? > Michael > > [1] https://bugs.launchpad.net/deja-dup > -- > devel mailing list > devel@lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org > -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: F24, small backward steps
On 09/13/2016 12:31 PM, Bastien Nocera wrote: > For which one of the problems you listed? It would certainly have been > interesting to list those in your original mail. It was the first problem, the one with deja-dup > > - Original Message - >> On 09/13/2016 11:09 AM, Daniel P. Berrange wrote: >>> On Tue, Sep 13, 2016 at 10:00:32AM -0500, Michael Catanzaro wrote: >>>> Hi, >>>> >>>> To be clear, the problem is that a small handful of package maintainers >>>> (including Bastien) are collectively "responsible" for all of the GNOME >>>> and freedesktop components in Fedora (including fprintd), and it's >>>> simply not reasonable to expect them to read all the bugs that are >>>> assigned to them, let alone take the time to forward them upstream. If >>>> you use Red Hat Bugzilla, the right developers may never notice your >>>> bug report at all. >>>> >>>> You have a much better chance filing bugs upstream. You should only use >>>> Red Hat Bugzilla for these components if you happen to know there is a >>>> specific maintainer who actually looks at the Red Hat bugs for that >>>> specific component, or if you're planning to propose it as a release >>>> blocker, or if you just don't care whether anybody sees your bug. If >>>> you have a packaging bug then it's the right place, but please ping >>>> someone to be sure it gets noticed. >>>> >>>> Of course this is not how Bugzilla is intended to work, but it is how >>>> it actually works for GNOME stuff. It's unfortunate, but without some >>>> Launchpad-style automatic bug forwarding, this is going to remain the >>>> case indefinitely. >>> >>> This is a truly awful experiance from POV of a Fedora user filing bugs :-( >>> We've set a silent trap for them with no warning of the fact that their >>> bug reports are going to be ignored until Fedora EOL procedure closes >>> them :-( >>> >>> Even if we can't enhance Red hat Bugzilla, we can at least do more to >>> alert users to this so they stand a chance of doing the right thing. >>> >>> eg, update the component description to tell user to file in GNOME >>> bugzilla instead, and have a bot that adds a comment to any new bugs >>> that are still filed, closing them WONTFIX and asking the user to >>> re-open against upstream GNOME bugzilla, instead of leaving the bug >>> open and ignored until Fedora EOL. >>> >>> Regards, >>> Daniel >>> >> Thanks for recognizing this. I am the OP. I pretty quickly got a >> response suggesting that I file a bug report "upstream". I did that, or >> so I thought, and immediately got a response from someone that it was >> the wrong place or list followed by another declaring the matter closed. >> I went back to my day job. >> >> >> -- >> Roger Wells, P.E. >> leidos >> 221 Third St >> Newport, RI 02840 >> 401-847-4210 (voice) >> 401-849-1585 (fax) >> roger.k.we...@leidos.com >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org >> > -- > devel mailing list > devel@lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org > -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: F24, small backward steps
On 09/13/2016 11:09 AM, Daniel P. Berrange wrote: > On Tue, Sep 13, 2016 at 10:00:32AM -0500, Michael Catanzaro wrote: >> Hi, >> >> To be clear, the problem is that a small handful of package maintainers >> (including Bastien) are collectively "responsible" for all of the GNOME >> and freedesktop components in Fedora (including fprintd), and it's >> simply not reasonable to expect them to read all the bugs that are >> assigned to them, let alone take the time to forward them upstream. If >> you use Red Hat Bugzilla, the right developers may never notice your >> bug report at all. >> >> You have a much better chance filing bugs upstream. You should only use >> Red Hat Bugzilla for these components if you happen to know there is a >> specific maintainer who actually looks at the Red Hat bugs for that >> specific component, or if you're planning to propose it as a release >> blocker, or if you just don't care whether anybody sees your bug. If >> you have a packaging bug then it's the right place, but please ping >> someone to be sure it gets noticed. >> >> Of course this is not how Bugzilla is intended to work, but it is how >> it actually works for GNOME stuff. It's unfortunate, but without some >> Launchpad-style automatic bug forwarding, this is going to remain the >> case indefinitely. > > This is a truly awful experiance from POV of a Fedora user filing bugs :-( > We've set a silent trap for them with no warning of the fact that their > bug reports are going to be ignored until Fedora EOL procedure closes > them :-( > > Even if we can't enhance Red hat Bugzilla, we can at least do more to > alert users to this so they stand a chance of doing the right thing. > > eg, update the component description to tell user to file in GNOME > bugzilla instead, and have a bot that adds a comment to any new bugs > that are still filed, closing them WONTFIX and asking the user to > re-open against upstream GNOME bugzilla, instead of leaving the bug > open and ignored until Fedora EOL. > > Regards, > Daniel > Thanks for recognizing this. I am the OP. I pretty quickly got a response suggesting that I file a bug report "upstream". I did that, or so I thought, and immediately got a response from someone that it was the wrong place or list followed by another declaring the matter closed. I went back to my day job. -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: F24, small backward steps
On 09/09/2016 04:44 PM, Adam Williamson wrote: > On Fri, 2016-09-09 at 15:53 -0400, Roger Wells wrote: >> Just a couple of smallish things after upgrading (via dnf) from F23 to >> F24 a couple of months ago: >> >> 1. deja-dup gui: >> >> one has to deselect then reselect the Overview option in order >> to be offered the "Backup Now" option. >> >> The details option in the progress dialog will only display two >> or three lines, is not resizeable, and does not follow resizing the >> entire dialog >> >> The progress dialog does not wait to be dismissed at the end, >> causing any messages about problems (like failure to backup a particular >> file) to not be seen > > This really isn't anything particular to Fedora. deja-dup is just an > app we ship. The appropriate place to report issues with it is to its > upstream bug tracker. Just did that. > >> 2. fingerprint identification: >> >> The laptop has a fingerprint reader and it works fine. However >> I prefer not to use it. The user set up specifies that fingerprint login >> is disabled. >> >> However whenever I am asked for a password the fingerprint >> reader blinks until I swipe a finger over it (even after using a >> password). >> >> No fingerprint is registered. >> >> This is different than F23 where it never blinked. > > This you should probably file a bug on (against, I guess, gnome-shell? > But it depends a lot on the answer to my second question below...), but > with a bit more detail. What exactly do you mean by "The user set up > specifies that fingerprint login is disabled" - what "user set up" are > you referring to exactly? When exactly does this happen - more detail > on "whenever I am asked for a password". Thanks! 1. Press the button on the upper right corner of the Gnome desktop. 2. Press the settings button on the lower left of the menu 3. Select Users On the resulting "Users" dialog one can select Fingerprint Login: Disabled/Enabled In my case it is Disabled As far as when this occurs, at least: 1. at boot up login 2. after suspense login and not 1. not when a browser asks for a password when visiting a site 2. when issuing a command using sudo, like mounting an external share Once again, this did not occur on F23 and started as soon as I upgraded to F24 Its no big deal. We could do like windows 10 which just stops the fingerprint reader when a password is entered. Let me know if you think I should submit this upstream somewhere. It feels like it may be similar to the scrolling problems mentioned that seem be fixed after installing libinit and adjusting some configuration files in /etc. After doing that the Gnome "Mouse & Touchpad" settings dialog (same place as the "Users" mentioned above) took on a whole new meaningful life. HTH, thanks for your response > -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
F24, small backward steps
Just a couple of smallish things after upgrading (via dnf) from F23 to F24 a couple of months ago: 1. deja-dup gui: one has to deselect then reselect the Overview option in order to be offered the "Backup Now" option. The details option in the progress dialog will only display two or three lines, is not resizeable, and does not follow resizing the entire dialog The progress dialog does not wait to be dismissed at the end, causing any messages about problems (like failure to backup a particular file) to not be seen 2. fingerprint identification: The laptop has a fingerprint reader and it works fine. However I prefer not to use it. The user set up specifies that fingerprint login is disabled. However whenever I am asked for a password the fingerprint reader blinks until I swipe a finger over it (even after using a password). No fingerprint is registered. This is different than F23 where it never blinked. 3. Scrolling issues: This, edge and natural scrolling via the touchpad, was covered nicely in a previous thread. Solutions offered there work well but should be better integrated as I am sure they will be. Desktop is: gnome-desktop3-3.20.2-1.fc24.x86_64 laptop is Thinkpad X240 (Intel graphics) Not to be a pita, just trying to help I really like Fedora & the Gnome desktop -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
F24 mouse/touchpad natural scrolling
Hello, In the Mouse & Touchpad settings dialog where one can select/deselect Natural Scrolling there is no difference between settings. The view/window is moved around the contents, i.e. not "Natural Scrolling" The machine is a Thinkpad x240, OS is F24, just upgraded from F23 a day or so ago. This setting worked as expected on F23 Actually, I just checked and none of the settings, "Mouse Speed", "Primary Button" included has any effect. I did set the speed to high on F23 and thought it worked. Never messed with the "Primary Button" though. uname -a: Linux rwells-x240 4.6.4-301.fc24.x86_64 #1 SMP Tue Jul 12 11:50:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux TIA -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: 3D printing SIG
On 03/17/2016 11:08 AM, Miro Hrončok wrote: > Hi Fedorains, > > I was thinking about creating a 3D printing SIG in Fedora. Would anyone > be interested in that? > > Miro > -- > devel mailing list > devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org +1 -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Hi Guys !
On 10/07/2015 06:06 PM, Jules Bashizi wrote: > I got admission into some British university and I am to buy a laptop . > wish to know a machine which is good with Linux . any advice on which > and where to get it please ! > > > Hi, I have been using Linux on X series Lenovo Thinkpads for many years, X200, X220, X240 and before that IBM A31 & X31 Linux versions include Fedora, Centos, RHEL but I have briefly tried Ubuntu (successfully). I develop navigation and mapping software for autonomous marine vehicles for a living using these computers. Good Luck in school HTH -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
