Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, Sep 27, 2012 at 09:09:51PM +0200, Martin Sourada wrote: > On Thu, 27 Sep 2012 17:39:27 +0200 > Till Maas wrote: > > This has already manifested for me with the slow keys feature that GDM > > enables and makes one believe that the keyboard died. > > > Yes, this happened to me once as well... I was really bewildered as to > what to do. But I think with tapping it's the other way around than > you suggest -- when Fedora switched the default to disabled (I don't > recall which version it was), I really thought something was broken -- > just like with the keyboard. No matter how much I tapped, nothing > happened. :-o disabled upstream in version 0.15.0 (June 2008), Fedora re-enabled it in response to #439386 (which somehow got merged upstream again for 0.15.2), but that was then finally disabled upstream with version 1.0 (Feb 2009). It has been disabled since, except for the Apple touchpads which don't have physical buttons. Cheers, Peter > Now I know it's because tapping is disabled but at that time I thought > it was hardware feature, not something you disable in software > configuration. So until I learned what actually happened I really > thought something was broken and I didn't know what. > > However, as I said earlier, I do not want to change the default > (again), both camps are probably equally numbered, and changes to > default that are not strongly supported (either by unbreakable > arguments or overwhelming numbers) are more disturbing than helpful. I > would just like to better understand the other camp. And Adam is doing > a pretty helpful job on that front ;-) > > Cheers, > Martin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Planned Outage: Buildsystem server reboots - 2012-10-02 21:00 UTC
Planned Outage: Buildsystem server reboots - 2012-10-02 21:00 UTC There will be an outage starting at 2012-10-02 21:00 UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2012-10-02 21:00 UTC' Reason for outage: We will be rebooting servers to bring them up to the latest updates/errata. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control Unaffected Services: Ask Fedora - http://ask.fedoraproject.org/ BFO - http://boot.fedoraproject.org/ DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - http://fedorapeople.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ QA Services Secondary Architectures Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/3489 Contact Information: Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. signature.asc Description: PGP signature ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, 27 Sep 2012 17:39:27 +0200 Till Maas wrote: > This has already manifested for me with the slow keys feature that GDM > enables and makes one believe that the keyboard died. > Yes, this happened to me once as well... I was really bewildered as to what to do. But I think with tapping it's the other way around than you suggest -- when Fedora switched the default to disabled (I don't recall which version it was), I really thought something was broken -- just like with the keyboard. No matter how much I tapped, nothing happened. :-o Now I know it's because tapping is disabled but at that time I thought it was hardware feature, not something you disable in software configuration. So until I learned what actually happened I really thought something was broken and I didn't know what. However, as I said earlier, I do not want to change the default (again), both camps are probably equally numbered, and changes to default that are not strongly supported (either by unbreakable arguments or overwhelming numbers) are more disturbing than helpful. I would just like to better understand the other camp. And Adam is doing a pretty helpful job on that front ;-) Cheers, Martin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, 2012-09-27 at 13:59 +0200, Martin Sourada wrote: > Hi Adam, > > On Wed, 26 Sep 2012 08:54:07 -0700 > Adam Williamson wrote: > > When lots of people who clearly aren't complete idiots tell you > > something happens to them, it's probably best just to accept that it > > does, because arguing that you can't possibly see how it could > > possibly happen to them is only going to make you look churlish. > > > there's no need to jump the gun ;-) While, after rereading my post I > kind of see where you've got the impression (looks like one or two words > I meant to write are missing there), I did not mean that as an argument, > just a point of view -- what I meant is that my brain does not > process *why* it happens (tap while move), but that *does not* mean I > don't accept that it happens for real people. There's a huge difference > between knowing and understanding ;-) > > Hence why I also included the question about smart phones, because I > believe that while interaction via touch-pad is indirect and relative > (you don't actually see the screen under your finger; you move > objects relative to where you start), the interaction is physically > pretty much same -- when you move right it moves right (whatever it is > you're moving -- on notebook usually cursor, on touch-screen usually > some object), when you tap, it clicks exactly where you are... To answer the question, I don't have the problem on smartphones, no. But I don't think it's a very useful comparison. You tap a lot more and drag a lot less on smartphones; tapping on something is the normal interaction, and you usually drag only for some kind of gesture. There's no cursor to move around. On a laptop, moving the cursor is probably what you do the most of. Add to that that the technologies used in the two aren't precisely the same and they're probably calibrated differently, and...it's just not a very germane comparison, really. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, Sep 27, 2012 at 05:42:47PM +0200, drago01 wrote: > Not buying that. If you tap and nothing happens you may also think > that something is broken "why does my touchpad not work" ... this is > even more likely then your scenario. > So this argument is flawed as well. The default isn't being changed, so this entire discussion is flawed. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, Sep 27, 2012 at 05:42:47PM +0200, drago01 wrote: > Not buying that. If you tap and nothing happens you may also think > that something is broken "why does my touchpad not work" ... this is > even more likely then your scenario. > So this argument is flawed as well. You know more that "it is broken". You know then the tap-to-click feature is missing and have a clear and reproducible error report "I tap on the touchpad and the click is not noticed". It is a lot easier to notice that something is missing and to describe it than to notice that something is there that is sometimes causing trouble. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Test-Mojibake] Created tag perl-Test-Mojibake-0.5-1.fc18
The lightweight tag 'perl-Test-Mojibake-0.5-1.fc18' was created pointing to: 934af71... Update to 0.5 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Test-Mojibake] Created tag perl-Test-Mojibake-0.5-1.fc19
The lightweight tag 'perl-Test-Mojibake-0.5-1.fc19' was created pointing to: 934af71... Update to 0.5 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, Sep 27, 2012 at 10:42 AM, drago01 wrote: > > Not buying that. If you tap and nothing happens you may also think > that something is broken "why does my touchpad not work" ... this is > even more likely then your scenario. > So this argument is flawed as well. > > But was tap to click ever enabled by default in Fedora then suddenly switched to disabled? If the default has always been disabled, why would a user have the expectation that tapping is broken when it was never a default in the first place? Moreover, a simple google of "fedora tap to click" tells you exactly how to enable it. This discussion is creating a problem where there isn't one. Tap to click is also disabled in OS X by default and I think Mac users are able to figure it out just fine. If they can find the setting, Fedora users can as well :) -- Steve Morrissey Information Technology Systems & Services University of Minnesota Duluth o: 218.726.8866 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, Sep 27, 2012 at 5:39 PM, Till Maas wrote: > On Thu, Sep 27, 2012 at 02:47:47PM +0200, drago01 wrote: >> On Thu, Sep 27, 2012 at 2:34 PM, Tomas Radej wrote: > >> > I don't expect much of a consensus to arise around this point, so I suggest >> > we check if in the main environments, the tap-to-click setting is easily >> > accessible and user-friendly. This state won't bother people who have >> > problems with tap-to-click, and won't pose problems for people who want to >> > have it on. I think that it's safe to assume that if the user installed >> > Fedora successfully, they realize that to enable clicking with their >> > touchpad, they need to go to Mouse/Touchpad settings and set it there in a >> > checkbox. >> >> The problem with your argument is that it can go with both directions. >> We can have it enabled by default and in case the user is annoyed by >> it he/she can turn it off. > > It is easier to enable something that is missing than to disable some > annoying behaviour whose cause is unknown. For example if you miss > tap-to-click, you know what you need to search for to enable it. If the > touchpad behaves strange because of accidental clicks, it is not that > clear whether this is a bad setting or a hardware or software defect. Not buying that. If you tap and nothing happens you may also think that something is broken "why does my touchpad not work" ... this is even more likely then your scenario. So this argument is flawed as well. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, Sep 27, 2012 at 02:47:47PM +0200, drago01 wrote: > On Thu, Sep 27, 2012 at 2:34 PM, Tomas Radej wrote: > > I don't expect much of a consensus to arise around this point, so I suggest > > we check if in the main environments, the tap-to-click setting is easily > > accessible and user-friendly. This state won't bother people who have > > problems with tap-to-click, and won't pose problems for people who want to > > have it on. I think that it's safe to assume that if the user installed > > Fedora successfully, they realize that to enable clicking with their > > touchpad, they need to go to Mouse/Touchpad settings and set it there in a > > checkbox. > > The problem with your argument is that it can go with both directions. > We can have it enabled by default and in case the user is annoyed by > it he/she can turn it off. It is easier to enable something that is missing than to disable some annoying behaviour whose cause is unknown. For example if you miss tap-to-click, you know what you need to search for to enable it. If the touchpad behaves strange because of accidental clicks, it is not that clear whether this is a bad setting or a hardware or software defect. This has already manifested for me with the slow keys feature that GDM enables and makes one believe that the keyboard died. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Heads up: My FC18 i686 vhost was bricked by lastest updates.
Caution (it might just be me, but just in case...) I can no longer boot my Fedora 18, i686, virtual host this morning after "yum update" https://bugzilla.redhat.com/show_bug.cgi?id=861130 I suspect, but can't verify quickly, either systemd or glibc. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On 09/27/2012 03:07 PM, Steve Morrissey wrote: The problem with your argument is that it can go with both directions. We can have it enabled by default and in case the user is annoyed by it he/she can turn it off. This is exactly right, there really is no right/wrong answer to this. For many it simply depends on what system you're using. If I'm using my Lenovo then I definitely don't want tap-to-click enabled because it has button both above and below the trackpad that work perfectly fine. I know, right, I should have specified that I suggest that because it's the status quo. TR -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
> > The problem with your argument is that it can go with both directions. > We can have it enabled by default and in case the user is annoyed by > it he/she can turn it off. This is exactly right, there really is no right/wrong answer to this. For many it simply depends on what system you're using. If I'm using my Lenovo then I definitely don't want tap-to-click enabled because it has button both above and below the trackpad that work perfectly fine. If I'm using a newer-model MacBook I want tap-to-click turned on because the whole trackpad clicks which can be cumbersome/hard to press vs. simple tapping. If I'm using an old MacBook that actually has a physical trackpad button I want tap-to-click off because it's an old laptop and the trackpad is getting worn and picky when it comes to detecting input properly. As others have pointed out this is actually one of the easiest to find settings and changing it is beyond trivial for even the most basic users. There is simply no good case to change defaults as there are too many variables at play. On Thu, Sep 27, 2012 at 7:47 AM, drago01 wrote: > On Thu, Sep 27, 2012 at 2:34 PM, Tomas Radej wrote: > > Hi, > > > > > > On 09/26/2012 08:51 PM, les wrote: > >> > >> Please, you can enable this feature if you want it, and if your touchpad > >> handles it well, then good for you. Tapping is a "feature", not a > >> characteristic of touch pad use, and as such should be accessible to > those > >> who want it, but not enabled by default. Just my personal point of view. > >> Regards, Les H > > > > > > I agree with this. Unless your touchpad's buttons are broken (like mine, > but > > that's beside the point), you can move around the system, no problem, and > > enable tap-to-click at will. > > > > The question that comes with this is if the switch is easily accessible. > In > > Gnome it is (albeit it has a funny label - 'Enable mouse clicks with > > touchpad' - what's wrong with 'Tap to click'?), but it appeared only > > recently in XFCE. I don't know about other environments which we ship, > > please submit your experience. > > > > I don't expect much of a consensus to arise around this point, so I > suggest > > we check if in the main environments, the tap-to-click setting is easily > > accessible and user-friendly. This state won't bother people who have > > problems with tap-to-click, and won't pose problems for people who want > to > > have it on. I think that it's safe to assume that if the user installed > > Fedora successfully, they realize that to enable clicking with their > > touchpad, they need to go to Mouse/Touchpad settings and set it there in > a > > checkbox. > > The problem with your argument is that it can go with both directions. > We can have it enabled by default and in case the user is annoyed by > it he/she can turn it off. > > I don't think that continuing this discussion makes much sense. There > are people who want/like it and there are some who do not ... unless > we can detect that (i.e read the users mind) we cannot find a solution > that works for everybody. > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > -- Steve Morrissey Information Technology Systems & Services University of Minnesota Duluth o: 218.726.8866 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20120927 changes
Compose started at Thu Sep 27 08:15:06 UTC 2012 Broken deps for x86_64 -- [almanah] almanah-0.8.0-7.fc18.x86_64 requires libedataserverui-3.0.so.3()(64bit) almanah-0.8.0-7.fc18.x86_64 requires libedataserver-1.2.so.16()(64bit) almanah-0.8.0-7.fc18.x86_64 requires libecal-1.2.so.12()(64bit) almanah-0.8.0-7.fc18.x86_64 requires libebook-1.2.so.13()(64bit) [avgtime] avgtime-0-0.2.git20120724.fc18.x86_64 requires libphobos-ldc.so.59()(64bit) [clutter-gtk010] clutter-gtk010-0.11.4-6.fc17.i686 requires libcogl.so.9 clutter-gtk010-0.11.4-6.fc17.x86_64 requires libcogl.so.9()(64bit) [dogtag-pki] dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-util-javadoc >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-tools >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-tks >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-symkey >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-silent >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-setup >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-server >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-selinux >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-ocsp >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-kra >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-java-tools-javadoc >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-console >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-common-javadoc >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-ca >= 0:10.0.0 dogtag-pki-10.0.0-0.8.a1.fc19.noarch requires pki-base >= 0:10.0.0 [dustmite] dustmite-1-5.20120304gitcde46e0.fc17.x86_64 requires libphobos-ldc.so.59()(64bit) [ease] ease-0.4-18.fc17.i686 requires libcogl.so.9 ease-0.4-18.fc17.x86_64 requires libcogl.so.9()(64bit) [evolution-exchange] evolution-exchange-3.5.2-1.fc18.x86_64 requires libedataserverui-3.0.so.3()(64bit) evolution-exchange-3.5.2-1.fc18.x86_64 requires libedataserver-1.2.so.16()(64bit) evolution-exchange-3.5.2-1.fc18.x86_64 requires libedata-cal-1.2.so.17()(64bit) evolution-exchange-3.5.2-1.fc18.x86_64 requires libedata-book-1.2.so.14()(64bit) evolution-exchange-3.5.2-1.fc18.x86_64 requires libecal-1.2.so.12()(64bit) evolution-exchange-3.5.2-1.fc18.x86_64 requires libebook-1.2.so.13()(64bit) evolution-exchange-3.5.2-1.fc18.x86_64 requires libebackend-1.2.so.3()(64bit) evolution-exchange-3.5.2-1.fc18.x86_64 requires libcamel-1.2.so.36()(64bit) [fedora-ksplice] fedora-ksplice-0.5-10.fc18.x86_64 requires ksplice [flush] flush-0.9.10-7.fc18.x86_64 requires libboost_thread-mt.so.1.48.0()(64bit) flush-0.9.10-7.fc18.x86_64 requires libboost_system-mt.so.1.48.0()(64bit) flush-0.9.10-7.fc18.x86_64 requires libboost_signals-mt.so.1.48.0()(64bit) flush-0.9.10-7.fc18.x86_64 requires libboost_filesystem-mt.so.1.48.0()(64bit) [fontik] fontik-0.6.1-3.20120305git5dbbc513.fc19.x86_64 requires libgee-0.8.so.1()(64bit) [freeipa] freeipa-server-3.0.0-0.8.fc19.x86_64 requires selinux-policy >= 0:3.11.1-21 freeipa-server-3.0.0-0.8.fc19.x86_64 requires pki-symkey >= 0:10.0.0-0.33.a1 freeipa-server-3.0.0-0.8.fc19.x86_64 requires pki-silent >= 0:10.0.0-0.33.a1 freeipa-server-3.0.0-0.8.fc19.x86_64 requires pki-setup >= 0:10.0.0-0.33.a1 freeipa-server-3.0.0-0.8.fc19.x86_64 requires pki-ca >= 0:10.0.0-0.33.a1 [gcc-python-plugin] gcc-python2-debug-plugin-0.9-4.fc19.x86_64 requires gcc = 0:4.7.1-7.fc19 gcc-python2-plugin-0.9-4.fc19.x86_64 requires gcc = 0:4.7.1-7.fc19 gcc-python3-debug-plugin-0.9-4.fc19.x86_64 requires gcc = 0:4.7.1-7.fc19 gcc-python3-plugin-0.9-4.fc19.x86_64 requires gcc = 0:4.7.1-7.fc19 [gcstar] gcstar-1.7.0-2.fc19.noarch requires perl(Gtk2::Table) gcstar-1.7.0-2.fc19.noarch requires perl(Gtk2::HBox) gcstar-1.7.0-2.fc19.noarch requires perl(Gtk2::Frame) gcstar-1.7.0-2.fc19.noarch requires perl(Gtk2::EventBox) [gdb-heap] gdb-heap-0.5-9.fc18.x86_64 requires glibc(x86-64) = 0:2.15 [glom] glom-1.18.6-1.fc17.x86_64 requires libboost_python.so.1.48.0()(64bit) glom-libs-1.18.6-1.fc17.i686 requires libboost_python.so.1.48.0 glom-libs-1.18.6-1.fc17.x86_64 requires libboost_python.so.1.48.0()(64bit) [gnome-applets] 1:gnome-applets-3.5.1-1.fc18.x86_64 requires libgweather-3.so.0()(64bit) [gnome-pilot] gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libedataserverui-3.0.so.1()(64bit) gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libedataserver-1.2.so.16()(64bit) gnome-pil
Fedora ARM weekly status meeting minutes 2012-09-26
Good day all, Thanks to those who were able to join us for the weekly status meeting yesterday. For those that were unable, the minutes are posted below: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2012-09-26/fedora-meeting-1.2012-09-26-20.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2012-09-26/fedora-meeting-1.2012-09-26-20.00.txt Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2012-09-26/fedora-meeting-1.2012-09-26-20.00.log.html Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dependency bug wodim/genisoimage
On 27 September 2012 13:13, wrote: >> From: Adam Williamson >> Bugzilla goes by .src.rpm name not binary rpm >> name. rpm -qi can tell you the .src.rpm from which any binary package >> was built. > > I used to get tripped up on this too and I've been doing Linux since the RHL > 4.0 days. In some cases it's entirely unobvious (e.g,. > python-imgcreate-*.rpm originates from livecd-tools-*.src.rpm). Once you > realize what's going on, you can usually see the connection, but I suspect > some/many a would-be-bug-reporters give up when they simply cannot find the > binary rpm listed in BZ. > > Perhaps the mouse-over and click-through help text of BZ's Component field > could better explain this. It might also be good to note how easy it is to > grock the src.rpm name from a "suspect" file using rpm -qif > /some/suspect/filename. > This might be worthwhile. I had no idea it worked this way, though in hindsight it's obvious why. A hint somewhere in the UI might work (maybe a "Can't find your component?" link). It is noted in the guided bug report form, but I doubt many people use that after their first couple of reports. -- imalone http://ibmalone.blogspot.co.uk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Thu, Sep 27, 2012 at 2:34 PM, Tomas Radej wrote: > Hi, > > > On 09/26/2012 08:51 PM, les wrote: >> >> Please, you can enable this feature if you want it, and if your touchpad >> handles it well, then good for you. Tapping is a "feature", not a >> characteristic of touch pad use, and as such should be accessible to those >> who want it, but not enabled by default. Just my personal point of view. >> Regards, Les H > > > I agree with this. Unless your touchpad's buttons are broken (like mine, but > that's beside the point), you can move around the system, no problem, and > enable tap-to-click at will. > > The question that comes with this is if the switch is easily accessible. In > Gnome it is (albeit it has a funny label - 'Enable mouse clicks with > touchpad' - what's wrong with 'Tap to click'?), but it appeared only > recently in XFCE. I don't know about other environments which we ship, > please submit your experience. > > I don't expect much of a consensus to arise around this point, so I suggest > we check if in the main environments, the tap-to-click setting is easily > accessible and user-friendly. This state won't bother people who have > problems with tap-to-click, and won't pose problems for people who want to > have it on. I think that it's safe to assume that if the user installed > Fedora successfully, they realize that to enable clicking with their > touchpad, they need to go to Mouse/Touchpad settings and set it there in a > checkbox. The problem with your argument is that it can go with both directions. We can have it enabled by default and in case the user is annoyed by it he/she can turn it off. I don't think that continuing this discussion makes much sense. There are people who want/like it and there are some who do not ... unless we can detect that (i.e read the users mind) we cannot find a solution that works for everybody. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
Hi, On 09/26/2012 08:51 PM, les wrote: Please, you can enable this feature if you want it, and if your touchpad handles it well, then good for you. Tapping is a "feature", not a characteristic of touch pad use, and as such should be accessible to those who want it, but not enabled by default. Just my personal point of view. Regards, Les H I agree with this. Unless your touchpad's buttons are broken (like mine, but that's beside the point), you can move around the system, no problem, and enable tap-to-click at will. The question that comes with this is if the switch is easily accessible. In Gnome it is (albeit it has a funny label - 'Enable mouse clicks with touchpad' - what's wrong with 'Tap to click'?), but it appeared only recently in XFCE. I don't know about other environments which we ship, please submit your experience. I don't expect much of a consensus to arise around this point, so I suggest we check if in the main environments, the tap-to-click setting is easily accessible and user-friendly. This state won't bother people who have problems with tap-to-click, and won't pose problems for people who want to have it on. I think that it's safe to assume that if the user installed Fedora successfully, they realize that to enable clicking with their touchpad, they need to go to Mouse/Touchpad settings and set it there in a checkbox. Tomas Radej -- FAS, IRC nick tradej -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dependency bug wodim/genisoimage
> From: Adam Williamson > Bugzilla goes by .src.rpm name not binary rpm > name. rpm -qi can tell you the .src.rpm from which any binary package > was built. I used to get tripped up on this too and I've been doing Linux since the RHL 4.0 days. In some cases it's entirely unobvious (e.g,. python-imgcreate-*.rpm originates from livecd-tools-*.src.rpm). Once you realize what's going on, you can usually see the connection, but I suspect some/many a would-be-bug-reporters give up when they simply cannot find the binary rpm listed in BZ. Perhaps the mouse-over and click-through help text of BZ's Component field could better explain this. It might also be good to note how easy it is to grock the src.rpm name from a "suspect" file using rpm -qif /some/suspect/filename. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
Hi Adam, On Wed, 26 Sep 2012 08:54:07 -0700 Adam Williamson wrote: > When lots of people who clearly aren't complete idiots tell you > something happens to them, it's probably best just to accept that it > does, because arguing that you can't possibly see how it could > possibly happen to them is only going to make you look churlish. > there's no need to jump the gun ;-) While, after rereading my post I kind of see where you've got the impression (looks like one or two words I meant to write are missing there), I did not mean that as an argument, just a point of view -- what I meant is that my brain does not process *why* it happens (tap while move), but that *does not* mean I don't accept that it happens for real people. There's a huge difference between knowing and understanding ;-) Hence why I also included the question about smart phones, because I believe that while interaction via touch-pad is indirect and relative (you don't actually see the screen under your finger; you move objects relative to where you start), the interaction is physically pretty much same -- when you move right it moves right (whatever it is you're moving -- on notebook usually cursor, on touch-screen usually some object), when you tap, it clicks exactly where you are... Also some people seemed to misunderstand -- I do understand why you can accidentally tap while typing (i.e. accidentally use touch-pad, while using keyboard) and that's already handled by an existing configuration option. The only thing I personally don't understand (but accept that it happens) is that you can actually use touch-pad for moving and meanwhile accidentally tap. Martin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora ARM weekly status meeting 2012-09-26
Morning all, Sorry for missing last nights meeting. In the short term I don't think I'll be able to make one until at least November as I'll be in Helsinki until at least Nov 2nd and that would make the meeting 11pm for me. I'll move to the format of updating by replying to this mail each week :-) > Current items on the agenda: > > 1) F18/19 Build status - problem packages None to report at the moment. I still have two outstanding items from Jon Masters namely: * llvm triplet * openmpi atomicss patch > 2) 3.6 kernel mmc driver - status update See the reply to dmalin. Basically I look to have a fix I'm happy with and dgilmore has tested a booting kernel. I'll post a scratch build for testing today. http://fpaste.org/BJLj/ > 3) VFAD summary > > 4) Raspberry Pi status update > > 5) your topic here > > If you have any other items you would like to discuss that are not mentioned, > please feel free to send an email to the list or bring it up at the end of > the meeting. > > Paul > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
