Re: kern/182139: lock order reversal

[J B]

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=ISO-8859-1
 
 I got similar errors, I assume after umount.
 # mount -t ext2fs /dev/ada0s6 /mnt/
 # umount /mnt
 # cat /var/log/messages
 ...
 Sep 16 06:35:41 localhost kernel: lock order reversal:
 Sep 16 06:35:41 localhost kernel: 1st 0xc8077d84 ufs (ufs) @
 /usr/src/sys/kern/vfs_mount.c:1237
 Sep 16 06:35:41 localhost kernel: 2nd 0xc8077a30 syncer (syncer) @
 /usr/src/sys/kern/vfs_subr.c:2210
 Sep 16 06:35:41 localhost kernel: KDB: stack backtrace:
 Sep 16 06:35:41 localhost kernel:
 db_trace_self_wrapper(c117e5e0,7f00,0,ac,0,...) at
 db_trace_self_wrapper+0x2d/frame 0xf0
 b518a0
 Sep 16 06:35:41 localhost kernel:
 kdb_backtrace(c118211d,c8077a30,c118bdc2,c69979b8,c118b751,...) at
 kdb_backtrace+0x30/frame
 0xf0b51908
 Sep 16 06:35:41 localhost kernel:
 witness_checkorder(c8077a30,9,c118b751,8a2,c8077a50,...) at
 witness_checkorder+0xc8a/frame 0
 xf0b51958
 Sep 16 06:35:41 localhost kernel:
 __lockmgr_args(c8077a30,80100,c8077a50,0,0,0,c118b751,8a2) at
 __lockmgr_args+0x83f/frame 0xf
 0b51a2c
 Sep 16 06:35:41 localhost kernel:
 vop_stdlock(f0b51aa0,246,c143bf54,c143bf6c,c143bf58,...) at
 vop_stdlock+0x4d/frame 0xf0b51a5c
 Sep 16 06:35:41 localhost kernel:
 VOP_LOCK1_APV(c128a948,f0b51aa0,c0aac8c9,c8077a50,c12baff8,...) at
 VOP_LOCK1_APV+0x104/frame 0xf0b51a88
 Sep 16 06:35:41 localhost kernel:
 _vn_lock(c80779fc,80100,c118b751,8a2,c8077a60,...) at _vn_lock+0xa1/frame
 0xf0b51ac8
 Sep 16 06:35:41 localhost kernel:
 vputx(c80b42a0,0,c118ad5b,518,c1280cc8,...) at vputx+0x219/frame 0xf0b51b10
 Sep 16 06:35:41 localhost kernel:
 dounmount(c80b42a0,800,c7fc3930,494,c0f50777,...) at
 dounmount+0x3d1/frame 0xf0b51b70
 Sep 16 06:35:41 localhost kernel:
 sys_unmount(c7fc3930,f0b51cc8,14,c117c645,7b3,...) at
 sys_unmount+0x3a1/frame 0xf0b51c40
 Sep 16 06:35:41 localhost kernel: syscall(f0b51d08) at syscall+0x2de/frame
 0xf0b51cfc
 Sep 16 06:35:41 localhost kernel: Xint0x80_syscall() at
 Xint0x80_syscall+0x21/frame 0xf0b51cfc
 Sep 16 06:35:41 localhost kernel: --- syscall (22, FreeBSD ELF32,
 sys_unmount), eip = 0x280c826b, esp = 0xbfbfd284, ebp = 0xbfbfd350 ---
 Sep 16 06:35:41 localhost kernel: lock order reversal:
 Sep 16 06:35:41 localhost kernel: 1st 0xc8077d84 ufs (ufs) @
 /usr/src/sys/kern/vfs_mount.c:1237
 Sep 16 06:35:41 localhost kernel: 2nd 0xc757f4a4 devfs (devfs) @
 /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_vfsops.c:872
 Sep 16 06:35:41 localhost kernel: KDB: stack backtrace:
 Sep 16 06:35:41 localhost kernel:
 db_trace_self_wrapper(c117e5e0,7478652f,2f736632,32747865,7366765f,...) at
 db_trace_self_wrapper+0x2d/frame 0xf0b51888
 Sep 16 06:35:41 localhost kernel:
 kdb_backtrace(c118211d,c757f4a4,c11751ac,c69977b0,c80aadb3,...) at
 kdb_backtrace+0x30/frame 0xf0b518f0
 Sep 16 06:35:41 localhost kernel:
 witness_checkorder(c757f4a4,9,c80aadb3,368,0,...) at
 witness_checkorder+0xc8a/frame 0xf0b51940
 Sep 16 06:35:41 localhost kernel:
 __lockmgr_args(c757f4a4,80400,c757f4c4,0,0,0,c80aadb3,368) at
 __lockmgr_args+0x83f/frame 0xf0b51a14
 Sep 16 06:35:41 localhost kernel:
 vop_stdlock(f0b51a88,c118b751,0,f0b51ae4,c80b42b0,...) at
 vop_stdlock+0x4d/frame 0xf0b51a44
 Sep 16 06:35:41 localhost kernel:
 VOP_LOCK1_APV(c1270d7c,f0b51a88,c80b42a0,f0b51ae4,c12baff8,...) at
 VOP_LOCK1_APV+0x104/frame 0xf0b51a70
 Sep 16 06:35:41 localhost kernel:
 _vn_lock(c757f470,80400,c80aadb3,368,f0b51b10,...) at _vn_lock+0xa1/frame
 0xf0b51ab0
 Sep 16 06:35:41 localhost kernel:
 ext2_sync(c80b42a0,1,c118ad5b,518,c1280cc8,...) at ext2_sync+0x233/frame
 0xf0b51b10
 Sep 16 06:35:41 localhost kernel:
 dounmount(c80b42a0,800,c7fc3930,494,c0f50777,...) at
 dounmount+0x49c/frame 0xf0b51b70
 Sep 16 06:35:41 localhost kernel:
 sys_unmount(c7fc3930,f0b51cc8,14,c117c645,7b3,...) at
 sys_unmount+0x3a1/frame 0xf0b51c40
 Sep 16 06:35:41 localhost kernel: syscall(f0b51d08) at syscall+0x2de/frame
 0xf0b51cfc
 Sep 16 06:35:41 localhost kernel: Xint0x80_syscall() at
 Xint0x80_syscall+0x21/frame 0xf0b51cfc
 Sep 16 06:35:41 localhost kernel: --- syscall (22, FreeBSD ELF32,
 sys_unmount), eip = 0x280c826b, esp = 0xbfbfd284, ebp = 0xbfbfd350 ---
 
 --f46d0438eb6d4a888e04e678f0c5
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 I got similar errors, I assume after umount.# mou=
 nt -t ext2fs /dev/ada0s6 /mnt/# umount /mnt# cat /var/log/mes=
 sages...Sep 16 06:35:41 localhost kernel: lock order reversal:
 Sep 16 06:35:41 localhost kernel: 1st 0xc8077d84 ufs (ufs) @ /usr/src/sys/k=
 ern/vfs_mount.c:1237Sep 16 06:35:41 localhost kernel: 2nd 0xc8077a30 sy=
 ncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2210Sep 16 06:35:41 localh=
 ost kernel: KDB: stack backtrace:
 Sep 16 06:35:41 localhost kernel

Re: kern/165533: [lpr] [patch] wrong 661 permission for /var/spool/output/lpd/.seq (should be 660)

[J B]

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

 Regarding fix to .seq file permission:
 
 http://ftp.utcluj.ro/pub/docs/ldp/bible-src/howtos/printing.html
 ...
 The Important Files
 Apart from the programs discussed above, each spool directory should
 contain four files - .seq, errs. lock and status. These files should
 have the permissions "-rw-rw-r--". The .seq file contains the job
 number counter for lpr to assign ...
 
 So, we can relax the permission to 0664.
 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"

Re: misc/168938: moused enabled causes xorg startx to fail

[J B]

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.ums0.pid
root1888   0.0  0.1   9716   1144  ??  Is8:55AM  0:00.00
/usr/sbin/moused -p /dev/psm0 -t auto
root2045   0.0  0.1  12340   2516  ??  I 8:55AM  0:00.01
hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
root2065   0.0  0.1  12340   2520  ??  I 8:55AM  0:00.01
hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
jb  2262   0.0  0.1   9748   1284   2  S+9:03AM  0:00.01
grep -i mouse

I have 2 mouses: Lenovo thinkpad stick and external usb mouse.

There was a fix offered on questions-list:
Disable hal in xorg.conf, ServerLayout section:
Option "AutoAddDevices" "Off"

I assume this is a temp solution only.

So I enabled moused in /etc/rc.conf, with the above xorg.conf fix. and rebooted.
'startx' log shows:

(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)

but mouses seem to work again.
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"

Re: misc/168938: moused enabled causes xorg startx to fail

[J B]

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 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.ums0.pid
 root1888   0.0  0.1   9716   1144  ??  Is8:55AM  0:00.00
 /usr/sbin/moused -p /dev/psm0 -t auto
 root2045   0.0  0.1  12340   2516  ??  I 8:55AM  0:00.01
 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
 root2065   0.0  0.1  12340   2520  ??  I 8:55AM  0:00.01
 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
 jb  2262   0.0  0.1   9748   1284   2  S+9:03AM  0:00.01
 grep -i mouse
 
 I have 2 mouses: Lenovo thinkpad stick and external usb mouse.
 
 There was a fix offered on questions-list:
 Disable hal in xorg.conf, ServerLayout section:
 Option "AutoAddDevices" "Off"
 
 I assume this is a temp solution only.
 
 So I enabled moused in /etc/rc.conf, with the above xorg.conf fix. and 
rebooted.
 'startx' log shows:
 
 (EE) config/hal: NewInputDeviceRequest failed (8)
 (EE) config/hal: NewInputDeviceRequest failed (8)
 
 but mouses seem to work again.
 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"

Re: misc/168938: moused enabled causes xorg startx to fail

[J B]

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   9716   1148  ??  Ss    8:55AM  0:01.02
> /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid
> root        1888   0.0  0.1   9716   1144  ??  Is    8:55AM  0:00.00
> /usr/sbin/moused -p /dev/psm0 -t auto
> root        2045   0.0  0.1  12340   2516  ??  I     8:55AM  0:00.01
> hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
> root        2065   0.0  0.1  12340   2520  ??  I     8:55AM  0:00.01
> hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
> jb          2262   0.0  0.1   9748   1284   2  S+    9:03AM  0:00.01
> grep -i mouse
>
> I have 2 mouses: Lenovo thinkpad stick and external usb mouse.

Oops, I must have goofed.
Disabling moused in rc.conf did just that for the default (built-in) mouse.
$ ps auxww|grep -i mouse
root1938   1.0  0.1  12340   2628  ??  S10:31PM 0:00.92
hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
root1287   0.0  0.1   9716   1148  ??  Ss   10:31PM 0:00.12
/usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid
root1958   0.0  0.1  12340   2516  ??  I10:31PM 0:00.01
hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
jb  2110   0.0  0.0   1928708   1  R+   10:34PM 0:00.02
grep -i mouse

No problem with moused here.
___
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"

Re: misc/168938: moused enabled causes xorg startx to fail

[J B]

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, 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 =A0 =A0 =A0 =A01286 =A0 0.0 =A00.1 =A0 9716 =A0 1148 =A0?? =A0Ss =A0=
  =A08:55AM =A00:01.02
 > /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid
 > root =A0 =A0 =A0 =A01888 =A0 0.0 =A00.1 =A0 9716 =A0 1144 =A0?? =A0Is =A0=
  =A08:55AM =A00:00.00
 > /usr/sbin/moused -p /dev/psm0 -t auto
 > root =A0 =A0 =A0 =A02045 =A0 0.0 =A00.1 =A012340 =A0 2516 =A0?? =A0I =A0 =
 =A0 8:55AM =A00:00.01
 > hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
 > root =A0 =A0 =A0 =A02065 =A0 0.0 =A00.1 =A012340 =A0 2520 =A0?? =A0I =A0 =
 =A0 8:55AM =A00:00.01
 > hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
 > jb =A0 =A0 =A0 =A0 =A02262 =A0 0.0 =A00.1 =A0 9748 =A0 1284 =A0 2 =A0S+ =
 =A0 =A09:03AM =A00:00.01
 > grep -i mouse
 >
 > I have 2 mouses: Lenovo thinkpad stick and external usb mouse.
 
 Oops, I must have goofed.
 Disabling moused in rc.conf did just that for the default (built-in) mouse.
 $ ps auxww|grep -i mouse
 root1938   1.0  0.1  12340   2628  ??  S10:31PM 0:00.92
 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
 root1287   0.0  0.1   9716   1148  ??  Ss   10:31PM 0:00.12
 /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid
 root1958   0.0  0.1  12340   2516  ??  I10:31PM 0:00.01
 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
 jb  2110   0.0  0.0   1928708   1  R+   10:34PM 0:00.02
 grep -i mouse
 
 No problem with moused here.
___
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"

Re: misc/169061: portmaster can not update p5-XML-SAX - a dependency loop

[J B]

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"

Re: misc/169061: portmaster can not update p5-XML-SAX - a dependency loop

[J B]

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/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"

ports/168717: editors/libreoffice: does not compile

[J B]

[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

---
Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/lib
reoffice-core-3.5.2.2/vcl/prj

 it seems that the error is inside 'vcl', please re-run build
 inside this module to isolate the error and/or test your fix:
---

/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/editors/libreoffice/work/libreoffice-cor
e-3.5.2.2'
gmake: *** [source-env-and-recurse] Error 2
*** Error code 1

Stop in /usr/ports/editors/libreoffice.
*** Error code 1

Stop in /usr/ports/editors/libreoffice.
[root@localhost /usr/ports/editors/libreoffice]#
___
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"

ports/168717: editors/libreoffice: does not compile

[J B]

/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/editors/libreoffice/work/libreoffice-core-3.5.2.2'
gmake: *** [source-env-and-recurse] Error 2
*** Error code 1

Stop in /usr/ports/editors/libreoffice.
*** Error code 1

OK.
I did as instructed above (up to 'gmake -r', and I got a clean compile.
...
[ build MOD ] vcl
R=/usr/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2
&& O=$S/solver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p
$W/Module/ && touch $W/Module/vcl
[ build ALL ] top level modules: bootstrap src.downloaded vcl
[ build ALL ] loaded modules: vcl

[ build CHK ] vcl
R=/usr/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2
&& O=$S/solver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p
$W/Module/check/ && touch $W/Module/check/vcl
[ build CHK ] loaded modules: vcl

[root@localhost
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl]#

It seems to be a clean compile. So, what is the problem ?
If I do it all  ('make') from the top level (as I have done it many
times), it fails as documented here.
What next ?
___
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"

ports/168717: editors/libreoffice: does not compile

[J B]

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

---
Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/lib
reoffice-core-3.5.2.2/framework/prj

 it seems that the error is inside 'framework', please re-run build
 inside this module to isolate the error and/or test your fix:
---

/usr/local/bin/bash
cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2
source ./Env.Host.sh
cd framework
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/editors/libreoffice/work/libreoffice-cor
e-3.5.2.2'
gmake: *** [source-env-and-recurse] Error 2
*** Error code 1

Stop in /usr/ports/editors/libreoffice.
*** Error code 1

Stop in /usr/ports/editors/libreoffice.
[root@localhost /usr/ports/editors/libreoffice]#

So, it continued compilations, and this time it died inside 'framework'.
I followed up according to instructions and it seems I got a clean compile
(as previously inside 'vcl'):
...
[ build ALL ] top level modules: bootstrap src.downloaded framework
[ build ALL ] loaded modules: framework

[ build CHK ] framework
R=/usr/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2
&& O=$S/solver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p
$W/Module/check/ && touch $W/Module/check/framework
[ build CHK ] loaded modules: framework

[root@localhost
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/framework]#

So I continu with 'make' in top-level dir.
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"

ports/168717: editors/libreoffice: does not compile

[J B]

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/libreoffice/work/libreoffice-core-3.5.2.2/workdir/
unxfbsdi.pro/LinkTarget/Library/libsfxlo.so'.  Stop.
dmake:  Error code 2, while making 'all'

---
Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/lib
reoffice-core-3.5.2.2/sfx2/prj

 it seems that the error is inside 'sfx2', please re-run build
...

I followed instructions and compilation inside 'sfx2' seems to be clean:
...
[ build CHK ] sfx2
R=/usr/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2
&& O=$S/solver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p
$W/Module/check/ && touch $W/Module/check/sfx2
[ build CHK ] loaded modules: sfx2

[root@localhost
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/sfx2]#

So I continued with 'make' from top-level dir.
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"

ports/168717: editors/libreoffice: does not compile

[J B]

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/work/libreoffice-core-3
.5.2.2/workdir/unxfbsdi.pro/LinkTarget/Library/libfilterconfiglo.so'.  Stop.
gmake[2]: *** Waiting for unfinished jobs
clang++: warning: argument unused during compilation: '-rpath=/usr/lib:/usr/loca
l/lib'
dmake:  Error code 2, while making 'all'

---
Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/lib
reoffice-core-3.5.2.2/tail_build/prj

 it seems that the error is inside 'tail_build', please re-run build
 inside this module to isolate the error and/or test your fix:
---

/usr/local/bin/bash
cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2
source ./Env.Host.sh
cd tail_build
gmake clean # optional
gmake -r

So, I followed with compilation inside 'tail_build'.
Unfortunately, unlike previous inside module builds, it died:
...
[root@localhost /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tai
l_build]# gmake -r
...
[ build LNK ] CppunitTest/libtest_lotuswordpro_test_lotuswordpro.so
R=/usr/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2 && O=$S/s
olver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p $W/LinkTarget/Cppun
itTest/ && clang++ -shared -Wl,-z,noexecstack   -Wl,-rpath-link,/lib:/usr/lib -W
l,-z,combreloc   -L$S/solenv/unxfbsdi/lib -L$O/lib -L$S/solenv/unxfbsdi/lib -L/u
sr/local/lib  -Wl,--hash-style=sysv  -Wl,--dynamic-list-cpp-new -Wl,--dynamic-li
st-cpp-typeinfo -Wl,-Bsymbolic-functions  -Wl,--strip-all   $W/CxxObject/lotuswo
rdpro/qa/cppunit/test_lotuswordpro.o -Wl,--start-group  -Wl,--end-group  -L/
usr/local/lib -lcppunit-lcomphelpgcc3 -luno_cppu -luno_cppuhelpergcc3 -luno_
sal -ltest -lunotest -lvcllo -o $W/LinkTarget/CppunitTest/libtest_lotuswordpro_t
est_lotuswordpro.so
TEMPFILE=/tmp/gbuild.XX.PzdEQBnY &&  mv ${TEMPFILE} /usr/ports/editors/libre
office/work/libreoffice-core-3.5.2.2/workdir/unxfbsdi.pro/LinkTarget/CppunitTest
/libtest_lotuswordpro_test_lotuswordpro.so.objectlist
[ build CUT ] lotuswordpro_test_lotuswordpro
R=/usr/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2 && O=$S/s
olver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p $W/CppunitTest/ &&
(LD_LIBRARY_PATH="$O/lib":$O/lib/sqlite   DBGSV_ERROR_OUT=shell STAR_RESOURCEPAT
H=$O/bin/   $O/bin/cppunit/cppunittester $W/LinkTarget/CppunitTest/libtest_lotus
wordpro_test_lotuswordpro.so --headless --protector unoexceptionprotector.so uno
exceptionprotector "-env:CONFIGURATION_LAYERS=xcsxcu:file://$O/xml/registry"   "
-env:UNO_TYPES= file://$O/bin/udkapi.rdb  file://$O/bin/types.rdb"  "-env:UNO_SE
RVICES=file://$O/xml/ure/services.rdb  file://$O/xml/component/lotuswordpro/util
/lwpfilter.component  file://$O/xml/configmgr.component  file://$O/xml/ucb1.comp
onent  file://$O/xml/ucpfile1.component"   -env:URE_INTERNAL_LIB_DIR=file://$O/l
ib  -env:LO_LIB_DIR=file://$O/lib > $W/CppunitTest/lotuswordpro_test_lotuswordpr
o.test.log 2>&1 || (cat $W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log &
& echo; echo "Error: a unit test failed, please do one of:"; echo; echo "export
DEBUGCPPUNIT=TRUE# for exception catching"; echo "export GDBCPPUNITT
RACE=\"gdb --args\" # for interactive debugging"; echo "export VALGRIND=memcheck
# for memory checking" ; echo "and retry." && false))
Segmentation fault (core dumped)
File tested,Test Result,Execution Time (ms)
file:///usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/lotuswordpro
/qa/cppunit/data/pass/A14.lwp,Signal 11 during cups initialization called, ignor
ing cups

Error: a unit test failed, please do one of:

export DEBUGCPPUNIT=TRUE# for exception catching
export GDBCPPUNITTRACE="gdb --args" # for interactive debugging
export VALGRIND=memcheck# for memory checking
and retry.
gmake: *** [/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir
/unxfbsdi.pro/CppunitTest/lotuswordpro_test_lotuswordpro.test] Error 1
[root@localhost /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tai
l_build]#

It died with Signal 11 segmentation fault.
That's it.
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"

ports/168717: editors/libreoffice: does not compile

[J B]

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/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2
&& O=$S/solver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p
$W/CppunitTest/ && (LD_LIBRARY_PATH="$O/lib":$O/lib/sqlite
DBGSV_ERROR_OUT=shell STAR_RESOURCEPATH=$O/bin/ gdb -nx
--command=$S/solenv/bin/gdbtrycatchtrace-stdout -return-child-result
--args  $O/bin/cppunit/cppunittester
$W/LinkTarget/CppunitTest/libtest_lotuswordpro_test_lotuswordpro.so
--headless --protector unoexceptionprotector.so unoexceptionprotector
"-env:CONFIGURATION_LAYERS=xcsxcu:file://$O/xml/registry"
"-env:UNO_TYPES= file://$O/bin/udkapi.rdb  file://$O/bin/types.rdb"
"-env:UNO_SERVICES=file://$O/xml/ure/services.rdb
file://$O/xml/component/lotuswordpro/util/lwpfilter.component
file://$O/xml/configmgr.component  file://$O/xml/ucb1.component
file://$O/xml/ucpfile1.component"
-env:URE_INTERNAL_LIB_DIR=file://$O/lib  -env:LO_LIB_DIR=file://$O/lib
> $W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log 2>&1 || (cat
$W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log && echo; echo
"Error: a unit test failed, please do one of:"; echo; echo "export
DEBUGCPPUNIT=TRUE# for exception catching"; echo "export
GDBCPPUNITTRACE=\"gdb --args\" # for interactive debugging"; echo
"export VALGRIND=memcheck# for memory checking" ; echo
"and retry." && false))
GNU gdb (GDB) 7.4.1 [GDB v7.4.1 for FreeBSD]
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-portbld-freebsd9.0".
For bug reporting instructions, please see:
...
Reading symbols from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/bin/cppunit/cppunittester...(no
debugging symbols found)...done.
Catchpoint 1 (throw)
Catchpoint 2 (catch)
[New LWP 101699]
[New Thread 28404300 (LWP 101699)]
[New Thread 28405200 (LWP 100757)]
File tested,Test Result,Execution Time (ms)
file:///usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/lotuswordpro/qa/cppunit/data/pass/A14.lwp,[New
Thread 2c544e00 (LWP 101580)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 28404300 (LWP 101699)]
0x28114d57 in rtl_uString_acquire () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/libuno_sal.so.3
#0  0x28114d57 in rtl_uString_acquire () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/libuno_sal.so.3
#1  0x0160 in ?? ()
#2  0xbfbf9768 in ?? ()
#3  0x2c012510 in SvpSalInstance::GetDefaultPrinter() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/libvclplug_svplo.so
#4  0x28f6618e in Printer::GetDefaultPrinterName() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/libvcllo.so
#5  0x28f66b6d in Printer::Printer() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/libvcllo.so
#6  0x2c8ba0ec in LwpPageLayout::GetWidthAndHeight(double&, double&)
() from 
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#7  0x2c8ba804 in LwpPageLayout::RegisterStyle() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#8  0x2c8a382d in LwpHeadLayout::RegisterStyle() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#9  0x2c87e638 in LwpFoundry::RegisterAllLayouts() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#10 0x2c86b855 in LwpDocument::RegisterLayoutStyles() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#11 0x2c86b507 in LwpDocument::RegisterStyle() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#12 0x2c86d60e in LwpDocSock::RegisterStyle() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#13 0x2c86b54f in LwpDocument::RegisterStyle() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#14 0x2c85a388 in Lwp9Reader::ParseDocument() () from
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsdi.pro/lib/liblwpftlo.so
#15 0x2c85a11c in Lwp9Reader::Read() () from
/usr/ports/editors/libreoffi

ports/168717: editors/libreoffice: does not compile

[J B]

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=/usr/ports/editors/libreoffice/work && S=$R/libreoffice-core-3.5.2.2 && O=$S/s
olver/unxfbsdi.pro && W=$S/workdir/unxfbsdi.pro &&  mkdir -p $W/CppunitTest/ &&
(LD_LIBRARY_PATH="$O/lib":$O/lib/sqlite G_SLICE=always-malloc GLIBCXX_FORCE_NEW=
1 DBGSV_ERROR_OUT=shell STAR_RESOURCEPATH=$O/bin/  valgrind --tool=memcheck --nu
m-callers=50 $O/bin/cppunit/cppunittester $W/LinkTarget/CppunitTest/libtest_lotu
swordpro_test_lotuswordpro.so --headless --protector unoexceptionprotector.so un
oexceptionprotector "-env:CONFIGURATION_LAYERS=xcsxcu:file://$O/xml/registry"
"-env:UNO_TYPES= file://$O/bin/udkapi.rdb  file://$O/bin/types.rdb"  "-env:UNO_S
ERVICES=file://$O/xml/ure/services.rdb  file://$O/xml/component/lotuswordpro/uti
l/lwpfilter.component  file://$O/xml/configmgr.component  file://$O/xml/ucb1.com
ponent  file://$O/xml/ucpfile1.component"   -env:URE_INTERNAL_LIB_DIR=file://$O/
lib  -env:LO_LIB_DIR=file://$O/lib > $W/CppunitTest/lotuswordpro_test_lotuswordp
ro.test.log 2>&1 || (cat $W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log
&& echo; echo "Error: a unit test failed, please do one of:"; echo; echo "export
 DEBUGCPPUNIT=TRUE# for exception catching"; echo "export GDBCPPUNIT
TRACE=\"gdb --args\" # for interactive debugging"; echo "export VALGRIND=memchec
k# for memory checking" ; echo "and retry." && false))
Killed
==76298== Memcheck, a memory error detector
==76298== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
... < many blank lines >
unxfbsdi.pro/lib
==76298==
==76298== Invalid read of size 4
... < many blank lines >
==76298==  overflow in your program's main thread (unlikely but
==76298==  possible), you can try to increase the size of the
==76298==  main thread stack using the --main-stacksize= flag.
==76298==
==76298== HEAP SUMMARY:
==76298== in use at exit: 4,543,775 bytes in 119,988 blocks
==76298==   total heap usage: 169,357 allocs, 49,369 frees, 19,954,753 bytes all
ocated
==76298==
==76298== LEAK SUMMARY:
==76298==definitely lost: 12,272 bytes in 2 blocks
==76298==indirectly lost: 520 bytes in 2 blocks
==76298==  possibly lost: 76,540 bytes in 1,049 blocks
==76298==still reachable: 4,454,443 bytes in 118,935 blocks
==76298== suppressed: 0 bytes in 0 blocks
==76298== Rerun with --leak-check=full to see details of leaked memory
==76298==
==76298== For counts of detected and suppressed errors, rerun with: -v
==76298== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)

Error: a unit test failed, please do one of:

export DEBUGCPPUNIT=TRUE# for exception catching
export GDBCPPUNITTRACE="gdb --args" # for interactive debugging
export VALGRIND=memcheck# for memory checking
and retry.
gmake: *** [/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir
/unxfbsdi.pro/CppunitTest/lotuswordpro_test_lotuswordpro.test] Error 1
[root@localhost /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tai
l_build]#

I guess that's all I could do.
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"

ports/168717: editors/libreoffice: does not compile

[J B]

$ 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-1.48.0
...
Mon Jun 11 00:07:43 CEST 2012
Upgrade of boost-libs-1.45.0_1 to boost-libs-1.48.0
...

$ ls -d /var/db/pkg/boost-*
/var/db/pkg/boost-jam-1.48.0/var/db/pkg/boost-libs-1.48.0

# pkg_delete /var/db/pkg/boost-*

# cd /usr/ports/editors/libreoffice
[root@localhost /usr/ports/editors/libreoffice]# make clean
===>  Cleaning for libreoffice-3.5.4
[root@localhost /usr/ports/editors/libreoffice]# make
...
=> Attempting to fetch http://ftp.rediris.es/mirror/TDF/libreoffice/src/3.5.4/li
breoffice-core-3.5.4.2.tar.xz
...
===>   libreoffice-3.5.4 depends on file: /usr/local/lib/libboost_regex.a - not
found
===>Verifying install for /usr/local/lib/libboost_regex.a in /usr/ports/deve
l/boost-libs
...
=> Attempting to fetch http://heanet.dl.sourceforge.net/project/boost/boost/1.48
.0/boost_1_48_0.tar.bz2
boost_1_48_0.tar.bz2  100% of   46 MB  240 kBps 00m00s
===>  Extracting for boost-libs-1.48.0
...
===>   boost-libs-1.48.0 depends on executable: bjam - not found
===>Verifying install for bjam in /usr/ports/devel/boost-jam
===>  Extracting for boost-jam-1.48.0
...
LibreOffice build succesfully finished.
...
[root@localhost /usr/ports/editors/libreoffice]# make install
...
===>   Registering installation for libreoffice-3.5.4
[root@localhost /usr/ports/editors/libreoffice]#

NOTE:
As seen above, the boost-lib and boost-jam are required for libreoffice
compilation.
I see missing '+REQUIRED_ BY' file in their package dirs:
 /var/db/pkg/boost-libs-1.48.0/
+COMMENT+CONTENTS   +DESC   +DISPLAY+MTREE_DIRS
# ls /var/db/pkg/boost-jam-1.48.0/
+COMMENT+CONTENTS   +DESC   +MTREE_DIRS

So, what was the trick with boost removal ?
If none, then what was the fix (this should be stated before closing the PR).
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"

Fwd: ports/168717: editors/libreoffice: does not compile

[J B]

-- 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 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 actually is a
download from
a distinct site as shown in my build log:
> => Attempting to fetch 
> http://heanet.dl.sourceforge.net/project/boost/boost/1.48
> .0/boost_1_48_0.tar.bz2
> boost_1_48_0.tar.bz2  100% of   46 MB  240 kBps 00m00s
> ===>  Extracting for boost-libs-1.48.0
> ...

The missing "REQUIRED_BY' file should be there too and include libreoffice and
the other ports/packages for the integrity of packages database, and thus any
package management utility like portmaster.
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"

ports/168717: editors/libreoffice: does not compile

[J B]

> 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
actually is a download from a distinct site as shown in my build log:
> => Attempting to fetch 
> http://heanet.dl.sourceforge.net/project/boost/boost/1.48
> .0/boost_1_48_0.tar.bz2
> boost_1_48_0.tar.bz2  100% of   46 MB  240 kBps 00m00s
> ===>  Extracting for boost-libs-1.48.0
> ...

The missing "REQUIRED_BY' file should be there too and include libreoffice and
the other ports/packages for the integrity of packages database, and thus any
package management utility like portmaster.

I just installed povray-3.7.0.r3_2 and here you go,
the boost-libs package database was updated:
# cat /var/db/pkg/boost-libs-1.48.0/+REQUIRED_BY
povray-3.7.0.r3_2

So should libreoffice.
Please reopen this PR until libreoffice build and packaging gets fixed.
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"

ports/169581: editors/libreoffice:

[J B]

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
boost-* libs is not needed, at least on this FB release.
Read the logs and comments - it is all there.
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"

misc/168938: moused enabled causes xorg startx to fail

[J B]

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"

misc/170128: libexttextcat-3.3.1 update problem

[J B]

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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: ports/168938: x11/xorg: moused(8) enabled causes xorg startx to fail

[J B]

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 Version 11, Revision 0
Build Operating System: FreeBSD 9.0-RELEASE i386
Current Operating System: 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
Build Date: 11 June 2012  07:18:51AM

Current version of pixman: 0.24.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 27 20:20:10 2012
(==) Using config file: "/usr/local/etc/X11/xorg.conf"
(EE) xf86OpenSerial: Cannot open device /dev/psm0
Device busy.
(EE) PS/2 Mouse: cannot open input device
(EE) PreInit returned NULL for "PS/2 Mouse"
(EE) config/hal: NewInputDeviceRequest failed (8)
...
$

Sorry about that. Please reopen it.


On Fri, Aug 24, 2012 at 6:51 PM,   wrote:
> Synopsis: x11/xorg: moused(8) enabled causes xorg startx to fail
>
> State-Changed-From-To: open->closed
> State-Changed-By: eadler
> State-Changed-When: Fri Aug 24 16:51:28 UTC 2012
> State-Changed-Why:
> Per submitter request
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=168938
___
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"

misc/171251: xfce4-battery-plugin erroneously charging from AC

[J B]

# 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
dev.battery.0.%pnpinfo: _HID=PNP0C0A _UID=0
dev.battery.0.%parent: acpi0
# sysctl -d hw.acpi.battery.life
hw.acpi.battery.life: percent capacity remaining
#
___
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"

misc/171251: xfce4-battery-plugin erroneously charging from AC

[J B]

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
 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
 dev.battery.0.%pnpinfo: _HID=PNP0C0A _UID=0
 dev.battery.0.%parent: acpi0
 # sysctl -d hw.acpi.battery.life
 hw.acpi.battery.life: percent capacity remaining
 #
___
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"

misc/16893​8: moused enabled causes xorg startx to fail

[J B]

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, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout

[J B]

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 is just different:
 $ cat .startx.log
 ...
 xinit: connection to X server lost
 
 waiting for X server to shut down xfsettingsd: Fatal IO error 35
 (Resource temporarily unavailable) on X server :0.0.
 $
___
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"

Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout

[J B]

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-session is already handled by XFCE's
 startxfce4 and initrc.
 $ cat .xinitrc
 exec startxfce4
 
 Please note that the error messages
 "xfsettingsd: Fatal IO error 0 (No error: 0) on X server :0.0.
 waiting for X server to shut down"
 and
 "waiting for X server to shut down xfsettingsd: Fatal IO error 35
 (Resource temporarily unavailable) on X server :0.0."
 show up randomly - there is instability in some program execution.
 System is up-to-date.
___
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"

Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout

[J B]

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*
 ~/.cache/sessions/
 and reconfigured XFCE, but it did not make any difference.
___
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"

Re: misc/171078: X and XFCE (xfsettingsd) errors on shutdown/logout

[J B]

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 have done some additional testing.
 1. I recompiled all installed XFCE ports.
 2. I nuked
 ~/.config/xfce*
 ~/.cache/sessions/
 3. Then I tested as below:
 
 a) $ startx
 I did not do anything, just Log Out from XFCE (orginal
 /unconfigured desktop).
 $ cat .startx.log
 xauth:  file /home/jb/.serverauth.1817 does not exist
 
 X.Org X Server 1.7.7
 Release Date: 2010-05-04
 X Protocol Version 11, Revision 0
 Build Operating System: FreeBSD 9.1-RC1 i386
 Current Operating System: 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
 Build Date: 02 September 2012  11:52:43AM
 
 Current version of pixman: 0.24.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
 Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct  3 21:15:49 2012
 (==) Using config file: "/usr/local/etc/X11/xorg.conf"
 (EE) config/hal: NewInputDeviceRequest failed (8)
 (EE) config/hal: NewInputDeviceRequest failed (8)
 /usr/local/bin/startxfce4: X server already running on display :0
 xrdb:  "Xft.hinting" on line 31 overrides entry on line 6
 xrdb:  "Xft.hintstyle" on line 32 overrides entry on line 7
 
 (xfsettingsd:1875): GLib-CRITICAL **: g_str_has_prefix: assertion
 `prefix != NULL' failed
 
 (xfwm4:1863): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix !=
 NULL' failed
 
 (xfwm4:1863): xfwm4-WARNING **: The property
 '/general/double_click_distance' of type int is not supported
 
 (xfdesktop:1871): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1871): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1871): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1871): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1871): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 xinit: connection to X server lost
 
 waiting for X server to shut down
 $
 
 b) $ startx
 This time I configured the desktop (Menu - Settings):
 - just changed some font sizes
 - removed bottom panel, moved upper panel to bottom
 - I did NOT touch Session and Startup (this is where xfsettingsd resides)
 Then I just did Log Out from XFCE (configured desktop).
 $ cat .startx.log
 xauth:  file /home/jb/.serverauth.1907 does not exist
 
 X.Org X Server 1.7.7
 Release Date: 2010-05-04
 X Protocol Version 11, Revision 0
 Build Operating System: FreeBSD 9.1-RC1 i386
 Current Operating System: 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
 Build Date: 02 September 2012  11:52:43AM
 
 Current version of pixman: 0.24.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
 Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct  3 21:19:46 2012
 (==) Using config file: "/usr/local/etc/X11/xorg.conf"
 (EE) config/hal: NewInputDeviceRequest failed (8)
 (EE) config/hal: NewInputDeviceRequest failed (8)
 /usr/local/bin/startxfce4: X server already running on display :0
 xrdb:  "Xft.hinting" on line 31 overrides entry on line 6
 xrdb:  "Xft.hintstyle" on line 32 overrides entry on line 7
 
 (xfdesktop:1960): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1960): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1960): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1960): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 
 (xfdesktop:1960): GLib-GIO-CRITICAL **: g_file_get_path: assertion
 `G_IS_FILE (file)' failed
 xinit: connection to X server lost
 
 waiting for X server to shut down
 $
 NOTE: no xfsettingsd error messages yet !
 
 c). $ startx
 I did not do anything, just Log Out from XFCE.
 $ cat .startx.log
 
 X.Org X Server 1.7.7
 Release Date

Re: misc/172965: pw useradd does not allow -g ""

[J B]

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 useradd command also has the ability to set new user and group
  defaults by using the -D option.  Instead of adding a new user, pw writes
  a new set of defaults to its configuration file, /etc/pw.conf.  When
  using the -D option, you must not use either -n name or -u uid or an
  error will result.  Use of -D changes the meaning of several command line
  switches in the useradd command.  These are:
 
  -DSet default values in /etc/pw.conf configuration file, or a
different named configuration file if the -C config option
is used.
 ...
 
 # pw useradd -D -g ""
 # cat /etc/pw.conf
 ...
 # Default group (leave blank for new group per user)
 defaultgroup = ""
 ...
 # pw useradd moo3
 # grep -i moo3 /etc/passwd
 moo3:*:1005:1005:User &:/home/moo3:/bin/sh
 
 # pw useradd -D -g "nobody"
 # cat /etc/pw.conf
 ...
 # Default group (leave blank for new group per user)
 defaultgroup = "nobody"
 ...
 # pw useradd moo4
 # grep -i moo4 /etc/passwd
 moo4:*:1006:65534:User &:/home/moo4:/bin/sh
 
 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"

Re: misc/172965: pw useradd does not allow -g ""

[J B]

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 ?
 "" ? Impossible, it has to be a valid group (it goes to /etc/passwd).
 # pw useradd moo4
 # pw useradd moo5 -g nobody
 # pw useradd moo6 -g moo6
 pw: group `moo6' does not exist
 # pw useradd moo7 -g ""
 pw: group `' is not defined
 # grep -i moo /etc/passwd
 moo4:*:1003:1003:User &:/home/moo4:/bin/sh
 moo5:*:1004:65534:User &:/home/moo5:/bin/sh
___
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"

Re: misc/172965: pw useradd does not allow -g ""

[J B]

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 sure that the new group is added to /etc/group"
 # grep -i moo /etc/group
 moo6:*:8007:
 
 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"

Re: misc/172965: pw useradd does not allow -g ""

[J B]

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 !
 I just tested (btw, without your patch):
 # pw usermod moo4 -g "nobody"
 # pw usermod moo4 -g ""
 Segmentation fault: 11 (core dumped)
 #
 
 I opened PR#:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=173005
 
 With regard to your changes:
 make sure you test 'pw useradd' and 'pw usermod' entries, both old and new
 (override with -g "") syntax, with "-N" option.
 
 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"

Re: misc/172965: pw useradd does not allow -g ""

[J B]

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 better solution.
 
 pw(8):
 ...
 USER OPTIONS
  The following options apply to the useradd and usermod commands:
 ...
  -g group  Set the account's primary group to the given group.  group
may be defined by either its name or group number.
 ...
  The useradd command also has the ability to set new user and group
  defaults by using the -D option.  Instead of adding a new user, pw writes
  a new set of defaults to its configuration file, /etc/pw.conf.  When
  using the -D option, you must not use either -n name or -u uid or an
  error will result.  Use of -D changes the meaning of several command line
  switches in the useradd command.  These are:
 
  -DSet default values in /etc/pw.conf configuration file, or a
different named configuration file if the -C config option
is used.
 ...
  -g group  Set the default group for new users.  If a blank group is
specified using -g "", then new users will be allocated
their own private primary group with the same name as their
login name.  If a group is supplied, either its name or uid
may be given as an argument.
 ...
 
 Now, let's review it once again.
 # pw useradd moo -g moo
 pw: group `moo' does not exist
 # pw useradd moo -g boo
 pw: group `boo' does not exist
 # pw useradd moo -g ""
 pw: group `' is not defined
 
 You want to make a one-time override of any default group as established in
 /etc/pw.conf by "-D -g" options:
 # pw useradd moo -g ""
 moo:*:8007:8007:User &:/home/moo:/bin/sh
 
 But, the below does the same but by checking if user name/id is equal to
 primary group name/id as entered:
 # pw useradd moo -g moo
 moo:*:8007:8007:User &:/home/moo:/bin/sh
 which clearly reflects user's intentions as entered.
 By contrast, your solution is less clear about the user's intentions; also,
 it introduces blank group specification -g "" to entry whose context is
 an immediate and particular account setup, but which is specific to -D -g ""
 type of entry whose context is setting up system defaults for any accounts
 setup.
___
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"

Re: kern/172931: Suspen/resume blocks USB mouse

[J B]

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.
 
 Reboot.
 'startx' for XFCE.
 
 Before suspend:
 $ ps auxwww|grep mouse
 root   1296   0.0  0.1  9608 1456 ??  Is9:26AM 0:00.10
 /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid
 root   1671   0.0  0.1  9608 1500 ??  Ss9:26AM 0:00.01
 /usr/sbin/moused -p /dev/psm0 -t auto
 root   1796   0.0  0.2 12244 3176 ??  I 9:26AM 0:00.02
 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
 root   1824   0.0  0.2 12244 3184 ??  I 9:26AM 0:00.01
 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
 
 Trial 1
 ---
 Suspend (XFCE panel: menu: user JB - Suspend)
 
 Resume (power switch ON).
 
 After resume:
 $ ps auxwww|grep mouse
 root   1671   0.0  0.1   9608   1500 ??  Ss9:27AM  0:00.79
 /usr/sbin/moused -p /dev/psm0 -t auto
 root   1796   0.0  0.2  12244   3176 ??  I 9:27AM  0:00.02
 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
 root   2007   0.0  0.1   9608   1556 ??  Is9:32AM  0:00.07
 /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid
 root   2063   0.0  0.2  12244   3452 ??  I 9:33AM  0:00.01
 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
 
 Note:
 - first suspend/resume seems to work OK (both mouses work).
 - the moused PIDs are different for USB mouse (1296 -> 2007)
 
 Trial 2
 ---
 Suspend (XFCE panel: menu: user JB - Suspend)
 
 Resume (power switch ON).
 
 After resume:
 $ ps auxwww|grep mouse
 root   1671   0.0  0.1   9608   1500 ??  Ss9:27AM  0:00.93
 /usr/sbin/moused -p /dev/psm0 -t auto
 root   1796   0.0  0.2  12244   3176 ??  I 9:28AM  0:00.02
 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
 
 Note:
 - second suspend/resume blocks USB mouse
 - neither HAL nor moused processes present
 
 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"

Re: kern/172931: Suspen/resume blocks USB mouse

[J B]

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 root  wheel0,  41 Oct 27 12:35 /dev/psm0
 crw-r--r--  1 root  operator0, 130 Oct 27 14:35 /dev/ums0
 
 After second (bad) suspend:
 $ ls -al /dev/ums0
 ls: /dev/ums0: No such file or directory
___
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"

Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation fault: 11 (core dumped)

[J B]

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, except for error message.
 
 It should be:
 # pw usermod mark -g ""
 pw: group `' is not defined
 
 which would be consistent with:
 # pw useradd mark -g ""
 pw: group `' is not defined
 
 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"

Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation fault: 11 (core dumped)

[J B]

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 the current (unpatched) state:
 
 # pw useradd moo -g moo
 pw: group `moo' does not exist
 # pw useradd moo -g boo
 pw: group `boo' does not exist
 # pw useradd moo -g ""
 pw: group `' is not defined
 
 As you can see there is a distinction between error msgs
 based on user input of primary group (or lack of it).
 That's why I asked you to be consistent with past and
 current user experience.
 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"

Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation fault: 11 (core dumped)

[J B]

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

 Simplifying for user is good.
 So, go ahead - that segmentation fault looks bad :-)
 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"

Re: kern/173414: ACPI battery time incorrect

[J B]

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: remaining time in minutes
 
 Why is it impossible or improper to compute and show battery's remaining
 time ? Because the machine is on on-line power supply ?
 
 The battery's state, that is, its remaining time, is still valid and of
 interest to user at any machine state (load, etc), regardless of power supply
 being on-line or off-line.
 
 I want to know WHAT IF, at any time (without or with consideration of current
 machine state (load, etc) in the computation of battery remaining time),
 I disconnected the on-line power supply, could I expect to happen to my
 machine with regard to expected length-of-time availability of battery power
 supply.
 
 If you think that the battery's "percent capacity remaining" is enough, then
 you are mistaken.
 hw.acpi.battery.life: percent capacity remaining
 
 The battery's "percent capacity remaining" is misleading because its max level
 is degrading over time (the 100% of a new battery is not the same 100% after
 a year or so of random discharging and charging). They just do not tell me
 how much estimated run time I would have as I explained above.
 
 This is what Linux shows about my battery state:
 
 $ cat /proc/acpi/battery/BAT0/info
 present: yes
 design capacity: 56160 mWh
 last full capacity:  38720 mWh
 battery technology:  rechargeable
 design voltage:  10800 mV
 design capacity warning: 1936 mWh
 design capacity low: 200 mWh
 capacity granularity 1:  1 mWh
 capacity granularity 2:  1 mWh
 model number:COMPATIBLE
 serial number:2413
 battery type:LION
 OEM info:BATSZ
 
 $ cat /proc/acpi/battery/BAT0/state
 present: yes
 capacity state:  ok
 charging state:  charged
 present rate:0 mW
 remaining capacity:  38720 mWh
 present voltage: 12405 mV
 
 These are the original and degraded capacity values of 100% I am talking
 about:
 ...
 design capacity: 56160 mWh
 last full capacity:  38720 mWh
 ...
 remaining capacity:  38720 mWh
 ...
 
 So, please compute this
 hw.acpi.battery.time: remaining time in minutes
 and make it available at any time, and at any state of the machine.
 There is a good use for this data.
___
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"

Re: bin/173725: portsnap(8) - fix entry validation

[J B]

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 execution of an entry.
 If I were interested in partial outcomes, I would have requested:
 # portsnap fetch; portsnap update
 
 Check up front and reject entire entry:
 if update
   if no dir portsdir (e.g. /usr/ports), then reject entry
 PORTSDIR not configured or does not exist.
 You must run 'portsnap extract' before running 'portsnap update'.
 
 This advises the user to review and remedy the problem first, which is
 the right thing to do.
___
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"

Re: bin/172846: bsdinstall - setting hostname

[J B]

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"