The following reply was made to PR kern/182139; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: kern/182139: lock order reversal
Date: Mon, 16 Sep 2013 06:50:08 +0200
--f46d0438eb6d4a888e04e678f0c5
Content-Type: text/plain; charset
Related problem:
misc/174859: Installation: /etc/hosts file
jb
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
The following reply was made to PR bin/173725; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: bin/173725: portsnap(8) - fix entry validation
Date: Wed, 21 Nov 2012 16:47:15 +0100
It is not desirable to have a partially successful
The following reply was made to PR kern/173414; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: kern/173414: ACPI battery time incorrect
Date: Tue, 6 Nov 2012 10:07:47 +0100
$ sysctl -d hw.acpi.battery.time
hw.acpi.battery.time
The following reply was made to PR bin/173005; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation
fault: 11 (core dumped)
Date: Mon, 29 Oct 2012 07:15:10 +0100
Simplifyin
The following reply was made to PR bin/173005; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation
fault: 11 (core dumped)
Date: Sun, 28 Oct 2012 20:41:50 +0100
This is t
The following reply was made to PR bin/173005; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation
fault: 11 (core dumped)
Date: Sun, 28 Oct 2012 10:03:36 +0100
Well done,
The following reply was made to PR kern/172931; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: kern/172931: Suspen/resume blocks USB mouse
Date: Sat, 27 Oct 2012 13:20:47 +0200
After boot and first (good) suspend:
crw-rw-rw- 1
The following reply was made to PR kern/172931; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: kern/172931: Suspen/resume blocks USB mouse
Date: Sat, 27 Oct 2012 10:06:58 +0200
Supplemental info.
I repeated these tests twice
The following reply was made to PR misc/172965; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, j...@bovine.net
Cc:
Subject: Re: misc/172965: pw useradd does not allow -g ""
Date: Fri, 26 Oct 2012 20:58:46 +0200
I am presenting a summary that would suggest bette
The following reply was made to PR misc/172965; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, j...@bovine.net
Cc:
Subject: Re: misc/172965: pw useradd does not allow -g ""
Date: Wed, 24 Oct 2012 00:26:58 +0200
What about 'pw usermod' ?
Wow !
The following reply was made to PR misc/172965; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, j...@bovine.net
Cc:
Subject: Re: misc/172965: pw useradd does not allow -g ""
Date: Tue, 23 Oct 2012 23:38:19 +0200
> # pw useradd moo6 -g ""
Make sur
The following reply was made to PR misc/172965; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, j...@bovine.net
Cc:
Subject: Re: misc/172965: pw useradd does not allow -g ""
Date: Tue, 23 Oct 2012 00:17:12 +0200
And what that one-time override would be ?
"
The following reply was made to PR misc/172965; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, j...@bovine.net
Cc:
Subject: Re: misc/172965: pw useradd does not allow -g ""
Date: Mon, 22 Oct 2012 23:35:49 +0200
You took it out of context.
$ man pw
...
The following reply was made to PR misc/171078; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc: Olivier Duchateau , x...@freebsd.org
Subject: Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout
Date: Wed, 3 Oct 2012 22:13:52 +0200
I
The following reply was made to PR misc/171078; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout
Date: Wed, 3 Oct 2012 08:45:32 +0200
I also nuked
~/.config/xfce
The following reply was made to PR misc/171078; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout
Date: Wed, 3 Oct 2012 08:23:45 +0200
This has been corrected - ck-launch
The following reply was made to PR misc/171078; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com
Cc:
Subject: Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout
Date: Thu, 27 Sep 2012 16:17:51 +0200
On XFCE logout, this time the error
OK. Last time. Let's keep it close - fixing it in xorg.conf is
the way to handle it if we want to keep HAL enabled for other
packages (apps).
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe,
The following reply was made to PR misc/171251; it has been noted by GNATS.
From: J B
To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org
Cc:
Subject: misc/171251: xfce4-battery-plugin erroneously charging from AC
Date: Sun, 2 Sep 2012 15:20:23 +0200
# sysctl -a |grep -i battery
# sysctl -a |grep -i battery
hw.acpi.battery.life: 99
hw.acpi.battery.time: -1
hw.acpi.battery.state: 0
hw.acpi.battery.units: 1
hw.acpi.battery.info_expire: 5
dev.battery.0.%desc: ACPI Control Method Battery
dev.battery.0.%driver: battery
dev.battery.0.%location: handle=\_SB_.PCI0.LPC_.EC__.BAT0
d
Hi,
apparently this is not fixed yet - I tested it in:
$ uname -a
FreeBSD localhost.localdomain 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14
03:56:40 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
$ cat .startx.log
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Versio
This problem is solved.
$ # which createfp
/usr/local/bin/createfp
There is no libexttextcat in ports any more, only libtextcat.
But there is still reference to libexttextcat there:
/usr/local/share/doc/libexttextcat/README.libtextcat
___
freebsd-bugs@fr
This seems to be fixed.
Please close it.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Please refer to old PR (basically the same problem -
why do you create new PRs for the same problem ?).
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168717
Yesterday I built libreoffice successfully on
FreeBSD 9.0-RELEASE-p3 #0.
There is a build log that documents that your "fix" by removing
> The trick is to remove boost. Libreoffice uses its own bundled version.
>
> Chris
But it seems that libreoffice and the other ports/packages require the same
boost-* packages versions. So, libreoffice should not require to
remove them, only to install the same from its bundle you say (?), which
-- Forwarded message --
From: J B
Date: Sun, Jul 1, 2012 at 10:59 PM
Subject: Re: ports/168717: editors/libreoffice: does not compile
To: Chris Rees
> The trick is to remove boost. Libreoffice uses its own bundled version.
>
> Chris
OK.
But it seems that libreoffic
$ uname -a
FreeBSD localhost.localdomain 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun
12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/
GENERIC i386
# cat /var/log/portmaster.log
...
Sun Jun 10 23:43:01 CEST 2012
Upgrade of boost-jam-1.45.0 to boost-jam
One more debug output attempt.
[root@localhost /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tai
l_build]# export VALGRIND=memcheck
[root@localhost /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tai
l_build]# gmake -r
...
[ build CUT ] lotuswordpro_test_lotuswordpro
R=
Next, debugging result.
[root@localhost /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tai
l_build]# export DEBUGCPPUNIT=TRUE
[root@localhost /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tai
l_build]# gmake -r
...
[ build CUT ] lotuswordpro_test_lotuswordpro
R=/usr/po
Next I continued in top-level dir.
This time it died inside 'tail_build':
...
gmake[2]: *** No rule to make target `/usr/ports/editors/libreoffice/work/libreo
ffice-core-3.5.2.2/workdir/unxfbsdi.pro/CxxObject/filter/source/config/cache/bas
econtainer.o', needed by `/usr/ports/editors/libreoffice/wo
Next similar error inside 'sfx2':
[ build DEP ] SRS:sfx/res
[ build SRS ] sfx/res
[ build RES ] sfxen-US
gmake[2]: *** No rule to make target `/usr/ports/editors/libreoffice/work/libreo
ffice-core-3.5.2.2/workdir/unxfbsdi.pro/CxxObject/sfx2/source/doc/guisaveas.o',
needed by `/usr/ports/editors/lib
I continued the previous "vlc error" step with 'make' in higher level dir:
[root@localhost /usr/ports/editors/libreoffice]# make
...
cppcanvas deliver
Module 'cppcanvas' delivered successfully. 0 files copied, 0 files unchanged
--
/usr/local/bin/bash
cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2
source ./Env.Host.sh
cd vcl
gmake clean # optional
gmake -r
when the problem is isolated and fixed exit and re-run 'make' from the top-level
gmake[1]: *** [build] Error 1
gmake[1]: Leaving directory
`/usr/ports/edi
[root@localhost /usr/ports/editors/libreoffice]# make
...
Making:guesslang.lib
Making:libguesslanglo.so
lingucomponent deliver
Module 'lingucomponent' delivered successfully. 12 files copied, 2 files unchang
ed
---
The following reply was made to PR misc/169061; it has been noted by GNATS.
From: J B
To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org
Cc:
Subject: Re: misc/169061: portmaster can not update p5-XML-SAX - a dependency
loop
Date: Thu, 14 Jun 2012 12:45:01 +0200
I missed the /usr
I missed the /usr/ports/PDATING instructions.
Now it is OK. Sorry about bothering you.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
The following reply was made to PR misc/168938; it has been noted by GNATS.
From: J B
To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org
Cc:
Subject: Re: misc/168938: moused enabled causes xorg startx to fail
Date: Mon, 11 Jun 2012 22:57:10 +0200
On Mon, Jun 11, 2012 at 9:16 AM
On Mon, Jun 11, 2012 at 9:16 AM, J B wrote:
> This is a bit strange.
> To fix the problem I disabled moused in /etc/rc.conf .
> I could 'startx' X session.
> But 'ps' still showed moused processes:
> $ ps auxww |grep -i mouse
> root 1286 0.0 0.1
The following reply was made to PR misc/168938; it has been noted by GNATS.
From: J B
To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org
Cc:
Subject: Re: misc/168938: moused enabled causes xorg startx to fail
Date: Mon, 11 Jun 2012 09:16:38 +0200
This is a bit strange.
To fix
This is a bit strange.
To fix the problem I disabled moused in /etc/rc.conf .
I could 'startx' X session.
But 'ps' still showed moused processes:
$ ps auxww |grep -i mouse
root1286 0.0 0.1 9716 1148 ?? Ss8:55AM 0:01.02
/usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.u
The following reply was made to PR kern/165533; it has been noted by GNATS.
From: J B
To: bug-follo...@freebsd.org, me...@bristol.ac.uk
Cc:
Subject: Re: kern/165533: [lpr] [patch] wrong 661 permission for
/var/spool/output/lpd/.seq (should be 660)
Date: Tue, 28 Feb 2012 21:40:08 +0100
42 matches
Mail list logo
