FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/eric6 | 19.04 | 20.3 +-+ devel/es-eric6 | 19.04 | 20.3 +-+ finance/R-cran-fGarch | 3042.83.1 | 3042.83.2 +-+ german/eric6| 19.04 | 20.3 +-+ russian/eric6 | 19.04 | 20.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
> On 8. Mar 2020, at 00:04, Greg 'groggy' Lehey wrote: > > On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote: > > [More irrelevant text deleted, also dropping current@] > > Is it really so difficult to trim your replies? > >> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: > ???On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: >> This was only an issue on the "latest" branch. If you don't alter >> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" >> branch, which fortunately wasn't affected. > No, this isn't necessarily correct. I have never modified this file, > but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest > with this revision string: > # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z > bdrewery $ > Despite the age, this appears to identical to the current version, > according to svn blame. Arguably this should be the default anyway. >> Installing 12.1 from install media gives you quarterly. > > Yes, quite possibly. But as I said, it's not always the case. In the part you trimmed he wrote: >> I installed 12.1 on a new laptop yesterday, I have not experienced >> issues with pkg. my comment > > This was only an issue on the "latest" branch. If you don't alter > "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" > branch, which fortunately wasn't affected. > was a direct response to that (fresh install of a 12.1 system). This obviously doesn’t necessarily apply to systems that have been updated from previous releases. -m ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote: [More irrelevant text deleted, also dropping current@] Is it really so difficult to trim your replies? >> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: >> >> ???On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: >>> This was only an issue on the "latest" branch. If you don't alter >>> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" >>> branch, which fortunately wasn't affected. >> >> No, this isn't necessarily correct. I have never modified this file, >> but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest >> with this revision string: >> >> # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z >> bdrewery $ >> >> Despite the age, this appears to identical to the current version, >> according to svn blame. Arguably this should be the default anyway. > > Installing 12.1 from install media gives you quarterly. Yes, quite possibly. But as I said, it's not always the case. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Re: Pkg repository is broken...
> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: > > On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: > > [much irrelevant text deleted] > > People, please trim your replies. Only relevant text should remain > >>> On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble >>> wrote: >>> >>> I installed 12.1 on a new laptop yesterday, I have not experienced >>> issues with pkg. >> >> This was only an issue on the "latest" branch. If you don't alter >> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" >> branch, which fortunately wasn't affected. > > No, this isn't necessarily correct. I have never modified this file, > but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest > with this revision string: > > # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z > bdrewery $ > > Despite the age, this appears to identical to the current version, > according to svn blame. Arguably this should be the default anyway. > Installing 12.1 from install media gives you quarterly. -m > Greg > -- > Sent from my desktop computer. > Finger g...@freebsd.org for PGP public key. > See complete headers for address and phone numbers. > This message is digitally signed. If your Microsoft mail program > reports problems, please read http://lemis.com/broken-MUA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: [much irrelevant text deleted] People, please trim your replies. Only relevant text should remain > On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote: >> >> I installed 12.1 on a new laptop yesterday, I have not experienced >> issues with pkg. > > This was only an issue on the "latest" branch. If you don't alter > "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" > branch, which fortunately wasn't affected. No, this isn't necessarily correct. I have never modified this file, but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest with this revision string: # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z bdrewery $ Despite the age, this appears to identical to the current version, according to svn blame. Arguably this should be the default anyway. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Re: Should 'Reported by' reflect who/which system reported the port to be out-of-date?
Hi, On 3/7/20 9:49 PM, Yuri wrote: I got a feedback that such use of 'Reported by' might be incorrect. I've never received any negative feedback about it. In fact, I believe it is a nice way of giving credits to some really useful services. Mateusz ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Should 'Reported by' reflect who/which system reported the port to be out-of-date?
El sáb., 7 mar. 2020 21:50, Yuri escribió: > I got a feedback that such use of 'Reported by' might be incorrect. > > > Opinions? > I don't know if it is incorrect, but I often use "Reported by: portscout". Never had negative feedback. Cheers > > Yuri > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Should 'Reported by' reflect who/which system reported the port to be out-of-date?
I got a feedback that such use of 'Reported by' might be incorrect. Opinions? Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
> On 7 Mar 2020, at 12:23, Adam Jimerson wrote: > > > On 3/7/20 6:56 AM, Michael Gmelin wrote: >> >> I worked around the situation locally by setting ALTABI >> on `pkg update': >> >> # ALTABI=FreeBSD:12.0:amd64 pkg update -f >> >> This allowed me to run >> >> # pkg upgrade >> >> without any issues, so I assume none of the about 30 packages I updated >> contained a wrong ABI/architecture. >> >> I verified this by checking: >> >> # pkg query "%q" | sort | uniq -c >> 112 FreeBSD:12:* >> 219 FreeBSD:12:amd64 >> >> Note that you could also export ALTABI to the environment or set it >> in /usr/local/etc/pkg.conf, but I figured that I might forget it in >> there. >> >> Also, it seems like none of my packages were affected and not setting >> it on `pkg upgrade' meant that pkg checks for that (at least that's >> what I assume it does) and therefore I won't have to deal with >> different ABIs in my installed packages later. >> >> All of this should be really temporary anyway and hopefully be resolved >> soon. >> >> Cheers, >> Michael >> > > I'm not screaming either, figured it wouldn't really help speed up > fixing things and that the right people were already working on fixing > it. I am also still getting this on 12.1-RELEASE, but the ALTABI work > around worked for me. > I also figured it will get fixed eventually, and it was my decision to switch from the default quarterly repo to the latest repo, so have to expect some problems from time to time. It would be nice to have some sort of indicator as to the progress the process though, it was a little confusing to see the package build server for 121amd64 had finished a day or two before the repo actually got updated, I guess it either has to wait for all builds to be finished and sync with mirrors? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote: > On 2020-03-07 05:10, Ronald Klop wrote: > > On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey > > wrote: > > > >> On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > >>> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey > >>> wrote: > > Any workarounds in the meantime? This must affect a lot of > people, including those who use 12-: > > pkg: wrong architecture: FreeBSD:12.0:amd64 instead of > FreeBSD:12:amd64 > pkg: repository FreeBSD contains packages with wrong ABI: > FreeBSD:12.0:amd64 > >>> > >>> Still broken for me on 12.1. > >> > >> Strange. Mine cleared up automatically the following day. > >> > >> It's also strange how few replies I have received. Two private > >> messages (why?), yours, and that was it. You'd think that people > >> would be screaming. > >> > >> Greg > > > > > > I'm not screaming because I'm settling with the situation and > > starting to make workarounds. > > And wondering where the official communication of the community is. > > Nothing about this situation on www.freebsd.org. All information > > about the situation seems scattered through the mailinglists. > > > > Things are working for me on 13-CURRENT again, but still broken on > > 12.1-RELEASE. See attachment. > > > > Ronald. > > ___ > > freebsd-curr...@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscr...@freebsd.org" > > > Did you try: > pkg update -f > > > I installed 12.1 on a new laptop yesterday, I have not experienced > issues with pkg. > This was only an issue on the "latest" branch. If you don't alter "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" branch, which fortunately wasn't affected. Anyway, this has been fixed as of today 13:30 UTC, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244549#c43 -m -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg 1.20 no mouse buttons
On Sat, 07 Mar 2020 10:48:05 +0100 "Ronald Klop" wrote: > On Thu, 05 Mar 2020 23:24:46 +0100, Michael Gmelin > wrote: > > > > > > >> On 5. Mar 2020, at 14:46, Ronald Klop wrote: > >> > >> Hi, > >> > >> I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse > >> to "hardware mouse". That fixed mouse integration with VirtualBox. > >> > >> Still have weird behaviour. Two finger swipe down & up (which > >> normally only scrolls) makes the browser go back. With xev I see > >> that next to logical button 4 & 5 for scrolling this also triggers > >> logical buttons 8 & 9. Swipe down presses 8 & 9 and up releases > >> the buttons. Why? > > > > Hi, > > > > Please check/post the outputs of: > > libinput list-devices > > xinput list > > xinput list-props > > See atttachments. "unnamed" is the vboxmouse driver which comes with > the virtualbox-ose-additions pkg. > I reproduced the problem here in virtualbox (on a MacBook + 12.1-RELEASE, but close enough). Note that I didn't need the vmmouse driver to reproduce it. It also doesn't seem to come with the virtualbox-ose-additions package [anymore]?! That said: I could see the issue you're talking about when two finger scrolling sideways - this means, if I'm not scrolling 100% straight. When running xev and being really focused to move two fingers vertically, I don't get buttons 8 and 9. This is not practical though and I can see why you're annoyed by that. Fortunately, buttons 8 and 9 can be disabled quite easily: # xinput set-button-map 9 1 2 3 4 5 6 7 0 0 This is for device id 9 (intellimouse), which did the trick in my setup. In case device id 10 is relevant in your setup, you can also try: # xinput set-button-map 10 1 2 3 4 5 6 7 0 0 And in case of 11 (this is the one from the vmmouse driver): # xinput set-button-map 11 1 2 3 4 5 6 7 0 0 You can verify that the setting caught on by calling: # xinput get-button-map If this does the trick for you, you can simply put it into your ~/.xinitrc to set it automatically on startx. Cheers, Michael -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11/xpra - anyone porting the Python3 version?
On Tue, Feb 25, 2020 at 10:38:19AM +0400, Gleb Popov wrote: > On Tue, Feb 25, 2020 at 12:00 AM Torfinn Ingolfsen wrote: > > > Hello, > > Is anyone working on a Python3 supported port of xpra? > > The homepage mentions that Python3 support was completed late > > September last year > > > > You are welcome to test it: https://reviews.freebsd.org/D23743 > Ow sorry, rmport does not check for Phabricator reviews (perhaps it should) and I only noticed this mail after removing the old x11/xpra port. René ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On 3/7/20 6:56 AM, Michael Gmelin wrote: > > I worked around the situation locally by setting ALTABI > on `pkg update': > > # ALTABI=FreeBSD:12.0:amd64 pkg update -f > > This allowed me to run > > # pkg upgrade > > without any issues, so I assume none of the about 30 packages I updated > contained a wrong ABI/architecture. > > I verified this by checking: > > # pkg query "%q" | sort | uniq -c >112 FreeBSD:12:* >219 FreeBSD:12:amd64 > > Note that you could also export ALTABI to the environment or set it > in /usr/local/etc/pkg.conf, but I figured that I might forget it in > there. > > Also, it seems like none of my packages were affected and not setting > it on `pkg upgrade' meant that pkg checks for that (at least that's > what I assume it does) and therefore I won't have to deal with > different ABIs in my installed packages later. > > All of this should be really temporary anyway and hopefully be resolved > soon. > > Cheers, > Michael > I'm not screaming either, figured it wouldn't really help speed up fixing things and that the right people were already working on fixing it. I am also still getting this on 12.1-RELEASE, but the ALTABI work around worked for me. signature.asc Description: OpenPGP digital signature
Re: Downloading source archive from GitHub release instead of repo tar
On 3/7/20 12:53 PM, Stefan Bethke wrote:
I'm working on updating the Gitea port to 1.11, and I need to download the
source archive off the release page, instead of an archive of the Github repo.
The source archive on the release page contains additional files that are
needed for the build (Go and node modules that would need to be downloaded
during the build otherwise).
PORTNAME= gitea
DISTVERSIONPREFIX= v
DISTVERSION=1.11.2
USE_GITHUB= yes
How do I tell make that I do want to download the release tar.gz instead of the
repo archive? Specifically, I need to download
https://github.com/go-gitea/gitea/releases/download/v1.11.2/gitea-src-1.11.2.tar.gz
instead of
https://codeload.github.com/go-gitea/gitea/tar.gz/v1.11.2?dummy=/go-gitea-gitea-v1.11.2_GH0.tar.gz
In such case I'd just just use
MASTER_SITES=
https://github.com/go-gitea/gitea/releases/download/${DISTVERSIONFULL}/
and then set DISTNAME appropriately.
Cheers,
Mateusz Piotrowski
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Sat, 07 Mar 2020 10:10:43 +0100 "Ronald Klop" wrote: > On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey > wrote: > > > On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > >> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey > >> wrote: > >>> > >>> Any workarounds in the meantime? This must affect a lot of > >>> people, including those who use 12-: > >>> > >>> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of > >>> FreeBSD:12:amd64 > >>> pkg: repository FreeBSD contains packages with wrong ABI: > >>> FreeBSD:12.0:amd64 > >> > >> Still broken for me on 12.1. > > > > Strange. Mine cleared up automatically the following day. > > > > It's also strange how few replies I have received. Two private > > messages (why?), yours, and that was it. You'd think that people > > would be screaming. > > > > Greg > > > I'm not screaming because I'm settling with the situation and > starting to make workarounds. > And wondering where the official communication of the community is. > Nothing about this situation on www.freebsd.org. All information > about the situation seems scattered through the mailinglists. > > Things are working for me on 13-CURRENT again, but still broken on > 12.1-RELEASE. See attachment. > I worked around the situation locally by setting ALTABI on `pkg update': # ALTABI=FreeBSD:12.0:amd64 pkg update -f This allowed me to run # pkg upgrade without any issues, so I assume none of the about 30 packages I updated contained a wrong ABI/architecture. I verified this by checking: # pkg query "%q" | sort | uniq -c 112 FreeBSD:12:* 219 FreeBSD:12:amd64 Note that you could also export ALTABI to the environment or set it in /usr/local/etc/pkg.conf, but I figured that I might forget it in there. Also, it seems like none of my packages were affected and not setting it on `pkg upgrade' meant that pkg checks for that (at least that's what I assume it does) and therefore I won't have to deal with different ABIs in my installed packages later. All of this should be really temporary anyway and hopefully be resolved soon. Cheers, Michael -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Downloading source archive from GitHub release instead of repo tar
I'm working on updating the Gitea port to 1.11, and I need to download the source archive off the release page, instead of an archive of the Github repo. The source archive on the release page contains additional files that are needed for the build (Go and node modules that would need to be downloaded during the build otherwise). PORTNAME= gitea DISTVERSIONPREFIX= v DISTVERSION=1.11.2 USE_GITHUB= yes How do I tell make that I do want to download the release tar.gz instead of the repo archive? Specifically, I need to download https://github.com/go-gitea/gitea/releases/download/v1.11.2/gitea-src-1.11.2.tar.gz instead of https://codeload.github.com/go-gitea/gitea/tar.gz/v1.11.2?dummy=/go-gitea-gitea-v1.11.2_GH0.tar.gz Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: Pkg repository is broken...
Am 07.03.2020 um 08:50 schrieb sth...@nethelp.no: > > I think a lot of people are waiting for some kind of guidance on how > to fix these problems, if the repos are supposed to be okay now. It would be really great if someone in the know would send something to -announce or similar, with an ETR. Maybe even with suggestions for workarounds. A forum thread mentions a workaround for those that cannot easily start compiling their own ports: https://forums.freebsd.org/threads/pkg-wrong-architecture-freebsd-12-0-amd64-instead-of-freebsd-12-amd64.74310/page-3 > ALTABI thing must be added in /usr/local/etc/pkg.conf: ALTABI = > "FreeBSD:12.0:amd64" Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: Pkg repository is broken...
Le sam. 7 mars 20 à 1:38:55 +0100, Greg 'groggy' Lehey écrivait : > > Still broken for me on 12.1. Still broken for me on 12.1-STABLE, but with a different error: "size mismatch, fetching from remote" and then "size mismatch, cannot continue" for the first package being fetched. Same after a `pkg clean'. > Strange. Mine cleared up automatically the following day. > > It's also strange how few replies I have received. Two private > messages (why?), yours, and that was it. You'd think that people > would be screaming. I read somewhere that the packages building farm switched from 12.0 to 12.1, and I was just waiting for the dust to settle... -- Th. Thomas. signature.asc Description: PGP signature
Re: Xorg 1.20 no mouse buttons
> On 7. Mar 2020, at 10:48, Ronald Klop wrote: > > On Thu, 05 Mar 2020 23:24:46 +0100, Michael Gmelin wrote: > >> >> On 5. Mar 2020, at 14:46, Ronald Klop wrote: >>> >>> Hi, >>> >>> I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse to >>> "hardware mouse". That fixed mouse integration with VirtualBox. >>> >>> Still have weird behaviour. Two finger swipe down & up (which normally only >>> scrolls) makes the browser go back. With xev I see that next to logical >>> button 4 & 5 for scrolling this also triggers logical buttons 8 & 9. Swipe >>> down presses 8 & 9 and up releases the buttons. Why? >> >> Hi, >> >> Please check/post the outputs of: >> libinput list-devices >> xinput list >> xinput list-props > > See atttachments. "unnamed" is the vboxmouse driver which comes with the > virtualbox-ose-additions pkg. What do you see when running xev libinput debug-events while two-finger scrolling? Do you see XF86Back and XF86Forward events? -m > Ronald. > > > > >> >> -m >> >> >>> Regards, >>> Ronald. >>> >>> > On Thu, 27 Feb 2020 19:42:34 +0100, Daniel Morante via freebsd-ports > wrote: Roland, Your issue might be related to this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244110 > On 2/26/2020 5:29 PM, Ronald Klop wrote: > It works again. > Changed back from virtualboxvideo from drm-devel-kmod to the driver from > virtualbox-ose-additions. But did some other changes at the same time > also. Not sure yet what happened, but it was integration of the mouse > with virtualbox which failed somehow. > Regards, > Ronald. >> On Wed, 26 Feb 2020 20:40:14 +0100, Ronald Klop >> wrote: >> Hello, >> Since my upgrade to Xorg 1.20 things seem to work except that no mouse >> buttons work. Pointer movement works good still. >> I'm running a fairly recent FreeBSD 13-CURRENT in VirtualBox (On Windows >> 10). The mouse is a touchpad on my Lenovo IdeaPad laptop. >> Previously it worked using fine. >> What can I do or debug to fix this? >> Regards, >> Ronald. >> [23.241] >> X.Org X Server 1.20.7 >> X Protocol Version 11, Revision 0 >> [23.241] Build Operating System: FreeBSD 13.0-CURRENT amd64 >> [23.241] Current Operating System: FreeBSD sjakie 13.0-CURRENT >> FreeBSD >> 13.0-CURRENT #4 r357762M: Sun Feb 16 12:16:08 CET 2020 >> builder@sjakie:/data/src/obj-freebsd-current/data/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG >> amd64 >> [23.241] Build Date: 22 February 2020 07:06:47AM >> [23.241] >> [23.241] Current version of pixman: 0.38.4 >> [23.241] Before reporting problems, check http://wiki.x.org >> to make sure that you have the latest version. >> [23.241] Markers: (--) probed, (**) from config file, (==) default >> setting, >> (++) from command line, (!!) notice, (II) informational, >> (WW) warning, (EE) error, (NI) not implemented, (??) unknown. >> [23.241] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 24 >> 19:18:14 2020 >> [23.244] (==) Using system config directory >> "/usr/local/share/X11/xorg.conf.d" >> [23.246] (==) No Layout section. Using the first Screen section. >> [23.246] (==) No screen section available. Using defaults. >> [23.246] (**) |-->Screen "Default Screen Section" (0) >> [23.246] (**) | |-->Monitor "" >> [23.247] (==) No monitor specified for screen "Default Screen >> Section". >> Using a default monitor configuration. >> [23.247] (==) Automatically adding devices >> [23.247] (==) Automatically enabling devices >> [23.247] (==) Not automatically adding GPU devices >> [23.247] (==) Max clients allowed: 256, resource mask: 0x1f >> [23.262] (==) FontPath set to: >> /usr/local/share/fonts/misc/, >> /usr/local/share/fonts/TTF/, >> /usr/local/share/fonts/OTF/, >> /usr/local/share/fonts/Type1/, >> /usr/local/share/fonts/100dpi/, >> /usr/local/share/fonts/75dpi/, >> catalogue:/usr/local/etc/X11/fontpath.d >> [23.263] (==) ModulePath set to "/usr/local/lib/xorg/modules" >> [23.263] (II) The server relies on udev to provide the list of input >> devices. >> If no devices become available, reconfigure udev or disable >> AutoAddDevices. >> [23.263] (II) Loader magic: 0x435010 >> [23.263] (II) Module ABI versions: >> [23.263] X.Org ANSI C Emulation: 0.4 >> [23.263] X.Org Video Driver: 24.1 >> [23.263] X.Org XInput driver : 24.1 >> [23.263] X.Org Server Extension : 10.0 >> [23.263] (--) PCI:*(0@0:2:0) 80ee:beef:: rev 0, Mem @ >> 0xe000/134217728, BIOS @ 0x/65536 >> [23.263] (II) LoadModule: "glx" >> [23.265] (II) Loading >>
Re: Xorg 1.20 no mouse buttons
On Thu, 05 Mar 2020 23:24:46 +0100, Michael Gmelin wrote: On 5. Mar 2020, at 14:46, Ronald Klop wrote: Hi, I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse to "hardware mouse". That fixed mouse integration with VirtualBox. Still have weird behaviour. Two finger swipe down & up (which normally only scrolls) makes the browser go back. With xev I see that next to logical button 4 & 5 for scrolling this also triggers logical buttons 8 & 9. Swipe down presses 8 & 9 and up releases the buttons. Why? Hi, Please check/post the outputs of: libinput list-devices xinput list xinput list-props See atttachments. "unnamed" is the vboxmouse driver which comes with the virtualbox-ose-additions pkg. Ronald. -m Regards, Ronald. On Thu, 27 Feb 2020 19:42:34 +0100, Daniel Morante via freebsd-ports wrote: Roland, Your issue might be related to this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244110 On 2/26/2020 5:29 PM, Ronald Klop wrote: It works again. Changed back from virtualboxvideo from drm-devel-kmod to the driver from virtualbox-ose-additions. But did some other changes at the same time also. Not sure yet what happened, but it was integration of the mouse with virtualbox which failed somehow. Regards, Ronald. On Wed, 26 Feb 2020 20:40:14 +0100, Ronald Klop wrote: Hello, Since my upgrade to Xorg 1.20 things seem to work except that no mouse buttons work. Pointer movement works good still. I'm running a fairly recent FreeBSD 13-CURRENT in VirtualBox (On Windows 10). The mouse is a touchpad on my Lenovo IdeaPad laptop. Previously it worked using fine. What can I do or debug to fix this? Regards, Ronald. [23.241] X.Org X Server 1.20.7 X Protocol Version 11, Revision 0 [23.241] Build Operating System: FreeBSD 13.0-CURRENT amd64 [23.241] Current Operating System: FreeBSD sjakie 13.0-CURRENT FreeBSD 13.0-CURRENT #4 r357762M: Sun Feb 16 12:16:08 CET 2020 builder@sjakie:/data/src/obj-freebsd-current/data/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG amd64 [23.241] Build Date: 22 February 2020 07:06:47AM [23.241] [23.241] Current version of pixman: 0.38.4 [23.241] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [23.241] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [23.241] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 24 19:18:14 2020 [23.244] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" [23.246] (==) No Layout section. Using the first Screen section. [23.246] (==) No screen section available. Using defaults. [23.246] (**) |-->Screen "Default Screen Section" (0) [23.246] (**) | |-->Monitor "" [23.247] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [23.247] (==) Automatically adding devices [23.247] (==) Automatically enabling devices [23.247] (==) Not automatically adding GPU devices [23.247] (==) Max clients allowed: 256, resource mask: 0x1f [23.262] (==) FontPath set to: /usr/local/share/fonts/misc/, /usr/local/share/fonts/TTF/, /usr/local/share/fonts/OTF/, /usr/local/share/fonts/Type1/, /usr/local/share/fonts/100dpi/, /usr/local/share/fonts/75dpi/, catalogue:/usr/local/etc/X11/fontpath.d [23.263] (==) ModulePath set to "/usr/local/lib/xorg/modules" [23.263] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [23.263] (II) Loader magic: 0x435010 [23.263] (II) Module ABI versions: [23.263] X.Org ANSI C Emulation: 0.4 [23.263] X.Org Video Driver: 24.1 [23.263] X.Org XInput driver : 24.1 [23.263] X.Org Server Extension : 10.0 [23.263] (--) PCI:*(0@0:2:0) 80ee:beef:: rev 0, Mem @ 0xe000/134217728, BIOS @ 0x/65536 [23.263] (II) LoadModule: "glx" [23.265] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [23.292] (II) Module glx: vendor="X.Org Foundation" [23.292] compiled for 1.20.7, module version = 1.0.0 [23.292] ABI class: X.Org Server Extension, version 10.0 [23.292] (==) Matched vboxvideo as autoconfigured driver 0 [23.292] (==) Matched modesetting as autoconfigured driver 1 [23.292] (==) Matched scfb as autoconfigured driver 2 [23.292] (==) Matched vesa as autoconfigured driver 3 [23.292] (==) Assigned the driver to the xf86ConfigLayout [23.292] (II) LoadModule: "vboxvideo" [23.292] (II) Loading /usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so [23.294] (II) Module vboxvideo: vendor="Oracle Corporation" [23.294] compiled for 1.20.7, module version = 1.0.1 [23.294] Module
Re: Pkg repository is broken...
On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey wrote: On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: Any workarounds in the meantime? This must affect a lot of people, including those who use 12-: pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64 Still broken for me on 12.1. Strange. Mine cleared up automatically the following day. It's also strange how few replies I have received. Two private messages (why?), yours, and that was it. You'd think that people would be screaming. Greg I'm not screaming because I'm settling with the situation and starting to make workarounds. And wondering where the official communication of the community is. Nothing about this situation on www.freebsd.org. All information about the situation seems scattered through the mailinglists. Things are working for me on 13-CURRENT again, but still broken on 12.1-RELEASE. See attachment. Ronald.Sat Mar 7 09:06:04 UTC 2020 Updating FreeBSD repository catalogue... [freebsd12.klop.ws] Fetching meta.conf: . done [freebsd12.klop.ws] Fetching packagesite.txz: .. done Processing entries: .. pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64 Processing entries... done Unable to update repository FreeBSD Error updating repositories! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
