Re: When to submit regression in a PR
On Fri, Jun 21, 2013, at 2:42, Aymeric Mansoux wrote: > > My question therefore is: while I will mention these problems upstream, > should I also make the PR? Contact the port maintainer directly? > I understand it is not FreeBSD specific (same issue on Debian Sid) > however it really make the current port unusable for those working on > laptops and those needing to input characters only reachable with the > compose key. > It's probably a good idea to open a PR and let the port maintainer know, but we really need to have upstream to fix it. FreeBSD discourages doing custom "development" in the ports tree, so even if you could whip up a patch to fix it we would prefer that it get committed upstream and the port updated to pull the new version rather than have the port committer include a custom patch with the port. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Acer Laptop Bightness and Volume Hotkeys not working!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have an Acer (S3-391) laptop, its a recent model with an SSD and HHD for a very nice price. I'm running FreeBSD 10-current, because of the wireless driver. I notice I can't use the brightness hotkeys (Fn + Left/Right Arrows) even with acpi_video... Als has the subject states I can't use audio hotkeys too (Fn + UP/DOWN arrows), but I'm not sure if I would need to load any extra module to do this! Can anybody advice on this? Many Thanks, Mike -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJRxj6TAAoJEGKyFhaKt9g3LuIP/1NGHMeE5EwmRUOjWoYZs2aP 1P2FobRlELoX2GI09/fsE8en7Yis5T3P1IK/l2qCM0XkI52uQs51iRNiMvYkjyjH JvGsKDNrj5R0ca+3XtHOaLRfVgTD4lSL2DJFF1ztKwoA4Y/fhcxhcOUGP+Wv10dx f8p7LynS3aQcQQFbCSvRzTf/+qcaKnRhBVmsSIJ9ZPPkaHwr+vFB8qUYNMhldFM9 MINSdryrox3dYcv8yr7XSk10mcXBmuKZD/r3OSkAxak74bXZveXVXHS2MyE8Wh3P rYHo+lcXO443It/fRJGFHZA/Yqd4ZQOEjzguo/s58ewd4+0oE/vLPW2EO8TjVc3j 5nquNmVsrF5lU5RheCGpLKyLuXk8MhdsSEXcHYKu4Ei8hknwsUHbasSzOxIvuRtu 3xAPV19ZYtJyK/GHMcPCPYfgB7/3FIcmCpfJrohTdT8ys8nMK+fbx+0I8HMeiJId 3ym0Dydb2d1xhBwAcnVn2OxAufWPpsWlJidQx6n3r5oB5txeIcqCHk4Or88lo0oZ sGh0CF611DuxAD+X+aglyxHBRaSOthngqIDDSt3C0AnLt29c1cQMYc5mRhEnDmFj J5apaa+3yfgRXRUT2a5M/okuW/tBkxTli4ravToXA3cOSo89vs91WQ0VN5bAQjwb ztHte9UXAZKz7ciHJILt =N8Xt -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Acer Laptop Bightness and Volume Hotkeys not working!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/23/13 00:17, Miguel Clara wrote: > > I have an Acer (S3-391) laptop, its a recent model with an SSD and > HHD for a very nice price. > > I'm running FreeBSD 10-current, because of the wireless driver. > > I notice I can't use the brightness hotkeys (Fn + Left/Right > Arrows) even with acpi_video... > > Als has the subject states I can't use audio hotkeys too (Fn + > UP/DOWN arrows), but I'm not sure if I would need to load any extra > module to do this! > > Can anybody advice on this? > > > Many Thanks, > > > Mike > The sound hotkey "problem" is fixed, I forgot to set my keyboard Layout properly in KDE setting it to "Acer Laptop" fixed this! But I still have the brightness issue, and xbacklight gives me this: xbacklight -get No outputs have backlight property -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJRxkK2AAoJEGKyFhaKt9g3sBIP/0aj4VmZYZhTsNqqFP8jr3Xa t/im5s/WGCgxT2tLOpCCA41OMPxUad+578dBrWu7P6FuLuVsMnErjvaBpliVtQZz 6ImMfKVakiNrLTVTBiAOwVpvEgZZQqtpI0IjeSYifuh/yy1gE5bzlZLumVzmoHCS QwsPxRxmvVLQ3/62IgXs+NPpEr9p2m9zOdysXD13G8o/MXz5p6etZlovXT61HV2D lMf9yMcZpTmLMjVd5/QGQz5deyNOWfxmJhG2a5LW8JtITG7xIT2gflkbm4J6Rj9B 7c4X1MzbX852IJHFY9b8hFj/9I7+dDnFZj3qpihCL78qsNd/wXg3h+Y0me1vHxEZ Vjo5Z4AQoL4E1U5cFkTieBPt8avYIuCztUSk6YQh1VIvS6s9/jSl36F3xeX7kkx6 AOzdzUJGpRU1Xe2vpbFfFwemDUAl73PKIf7I5KWXXCD85RHshw1di6HYohAubGkr j4cssQ0inQ8667vi4IGeTjzpgGTvvICiN+hjbw8DQhKkN/GbYf0D2uQ5TWhKe/pH CjT9LDQH1bKzVdzTG2i5a1W8Z+WT1tsvl0u+Tb5Lwma7bynILKgdyz7WiQRgc6M4 g2gZAl/A3mlJ0pXDfDnCU6IftywqcW+fVAcBkl2hPMb5xIiRaE4gZELJi3mOLwBm +PkaE5rWW5l9wjX7MsKd =1wfh -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
freebsd-update percentage indicators - what are they, why are they so random?
I'm using freebsd-update to upgrade my system to the latest minor release. At a couple points in the process, I get weird status indicators (percentages) showing me that something is happening: Fetching 1 metadata files... 70.5% done. 70.5% 70.5% 74.2% 74.2% 81.7% 81.7% 70.5% Inspecting system... done. Sometimes these numbers are negative, and although not entirely random, they don't seem to follow any particular pattern... they don't creep up from 0 to 100, at least: Preparing to download files... done. -4.7% -8.4% -9.6% 35.4% 30.6% 30.5% 45.2% 43.4% 43.0% 68.1% 68.2% 68.2% 44.4% 43.0% 43.0% 72.0% 71.9% 71.9% 69.1% 69.0% 69.0% 72.0% 71.9% 71.9% 69.1% 69.0% 69.0% 52.2% 50.2% 49.9% 53.4% 56.8% 57.5% 59.0% 55.1% 56.0% 91.4% 94.5% 94.3% 90.4% 94.5% 94.3% 54.8% 54.6% 55.3% 28.8% 24.9% 24.2% 57.0% 53.3% 55.1% Attempting to automatically merge changes in files... done. What is the point of these numbers? Does everyone see them, or is it just me? Are they supposed to be on separate lines like this, or are they supposed to overwrite each other one line? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Should I be able to use mergemaster with freebsd-update?
I'm using freebsd-update to upgrade my system to the latest minor version (from 8.3-RELEASE to 8.4-RELEASE). I'm surprised that the merge handling system isn't more robust. When upgrading the old way, from source, I was used to using mergemaster to handle any merges that couldn't be done automatically. But when using freebsd-update, it seems that any failed merges require that you get dumped into an empty text editor for each file. It doesn't even tell you where the new file is so you can load it and compare it to the old one. After that, you're asked to approve every diff, but if you reject one, you don't get a chance to re-edit; the entire upgrade aborts and you have to start all over again. Since it wasn't obvious what to do, last time I upgraded, I just loaded all my old files and kept them as-is, without merging them. This time, I'm trying to actually take care of them when prompted. When I get dumped into the empty text editor, I suppose it's not too hard to figure out that the new file is in /var/db/freebsd-update/merge/8.4-RELEASE, but that's certainly not documented anywhere. It could at least be mentioned prior to being sent to the editor. The old file is mentioned, so why not the new? Regardless, when doing a manual merge by loading both files and consolidating them, or by copy-paste voodoo between terminal windows, it is far easier to screw up than mergemaster's method, at least in my experience. So I was thinking that when I get to this stage of the freebsd-update process, it would be nice to use mergemaster in a separate terminal window. I mean, I know where the new files are, and I know where I need the merged files to go, so it should be just a matter of invoking mergemaster with the right flags, right? Then when I'm dumped into a text editor, it won't be empty; I'll see the mergemaster-produced file, and can just give it a once-over. The handbook even mentions mergemaster as if it is an option: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html#freebsdupdate-config-file ...or at least, it suggests I read about it, for some reason. But I can't figure out how to get mergemaster to use freebsd-update's file locations. Here is what I tried: mergemaster -ciFv -m /var/db/freebsd-update/merge/8.4-RELEASE -D /var/db/freebsd-update/merge/new Here's what that results in, even if I add trailing slashes: make: don't know how to make distrib-dirs. Stop make: don't know how to make distrib-dirs. Stop *** FATAL ERROR: Cannot 'cd' to /var/db/freebsd-update/merge/8.4-RELEASE and install files to the temproot environment Any suggestions appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
