Re: strange abort with kcheckpass
On Tuesday 12 January 2010 17:49:25 Damian Weber wrote: Hi, all, I've got a strange SIGABRT issue with kcheckpass. Of course, kcheckpass is not contained in the base system, yet I write to this list since the base system could be able to help with tracking this down. (kcheckpass is called from a screen locker which fails to operate properly as a consequence of the SIGABRT.) Normal behaviour: (for example with wrong password) $ kcheckpass Password: Authentication failure Strange behaviour here (called mybox below): $ kcheckpass Abort trap: 6 I've recompiled the kcheckpass part of the kdebase3 port with option -g. Starting with debugger even doesn't let me reach a breakpoint at main(), because the SIGABRT happens earlier. # pwd /usr/ports/x11/kdebase3/work/kdebase-3.5.10/kcheckpass # ldd ./kcheckpass ./kcheckpass: libkdefakes.so.6 = /usr/local/lib/libkdefakes.so.6 (0x68193000) libpam.so.4 = /usr/lib/libpam.so.4 (0x68195000) libjpeg.so.10 = /usr/local/lib/libjpeg.so.10 (0x6819c000) libthr.so.3 = /lib/libthr.so.3 (0x681d) libc.so.7 = /lib/libc.so.7 (0x6808) # gdb ./kcheckpass GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... (gdb) b main Breakpoint 1 at 0x1470: file kcheckpass.c, line 297. (gdb) r Starting program: /usr/ports/x11/kdebase3/work/kdebase-3.5.10/kcheckpass/kcheckpass Program terminated with signal SIGABRT, Aborted. The program no longer exists. You can't do that without a process to debug. (gdb) q $ uname -a FreeBSD mybox 7.2-STABLE FreeBSD 7.2-STABLE #18: Mon Dec 14 00:39:13 CET 2009 mybox i386 $ ls -ld /var/db/pkg/kdebase* drwxr-xr-x 2 root wheel 512 Jan 11 18:35 /var/db/pkg/kdebase-3.5.10_4/ drwxr-xr-x 2 root wheel 512 Jan 11 18:35 /var/db/pkg/kdebase-kompmgr-3.5.10_1/ Any ideas what's the cause or what I should try next to see where this abort comes from? Thanks, Damian try debugging kcheckpass --nofork, as it will prevent the process forking off into the background. A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: atapicam cd error
On Thursday 24 May 2007 21:48:04 JoaoBR wrote: On Thursday 24 May 2007 15:15:51 you wrote: On Wed, 23 May 2007 17:40:25 -0300 [EMAIL PROTECTED] ~ uname -a FreeBSD asus64.konav201.local 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Apr 17 17:38:20 HST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~ dmesg | grep acd acd0: DMA limited to UDMA33, device found non-ATA66 cable acd0: DVDR SONY DVD RW DW-Q120A/PYS1 at ata1-master UDMA33 acd1: DVDROM TOSHIBA ODD-DVD SD-M1802/1030 at ata1-slave UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x0 K3B works fine after build kernel/world on above date. Hi so you are suggesting a rollback? I compiled on may 21st and 23rd and as Joe Altman confirmed too it's not working anymore on amd64 ... on i386 it's ok, may be this is a good moment then to change my backup strategy and use usb mem chips and kick atapicam out of the kernel ping# uname -a FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23 15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 (compiled from sources updated immediately before the build started, no later than 10.00 UTC on 23.5.2007) k3b is working absolutely fine on this box, I just managed to burn a CD followed by a DVD. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Friday 25 May 2007 00:46:09 JoaoBR wrote: On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote: ping# uname -a FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23 15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 (compiled from sources updated immediately before the build started, no later than 10.00 UTC on 23.5.2007) k3b is working absolutely fine on this box, I just managed to burn a CD followed by a DVD. so that is funny now so i tried and indeed I can write an iso with cdrecord which is your k3b version? I have k3b 1.0_2 Same here. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new compiler error, kdepim-3.5.6_3
On Sunday 06 May 2007 15:51:45 [EMAIL PROTECTED] wrote: I'm running KDE-3.5.6 on FreeBSD 6.2-STABLE #2: Fri May 4 19:12:15 EDT 2007, and CVSup'd ports this morning (05/06/2007) When running portupgrade -a, the following error (see below) occurs after the build of kdepim3 runs for just over an an hour (kdepim-3.5.6_3) (machine info: Athlon XP2000, 512MB RAM - for the curious:) How to fix? We really don't want to force this, do we?:o) Byron Stop in /usr/ports/deskutils/kdepim3. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.91306.7 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=kdepim-3.5.6_2 UPGRADE_PORT_VER=3.5.6_2 make ** Fix the problem and try again. --- Skipping 'x11/kde3' (kde-3.5.6) because a requisite package 'kdepim-3.5.6_2' (deskutils/kdepim3) failed (specify -k to force) [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 194 packages found (-0 +1) . done] ** Listing the failed packages (*:skipped / !:failed) ! deskutils/kdepim3 (kdepim-3.5.6_2)(new compiler error) * x11/kde3 (kde-3.5.6) Unfortunately, you've not pasted the important part, which is the part that actually shows the error in kdepim3. This would have come just before the Stop in /usr/ports/deskutils/kdepim3. message above. The part you pasted just shows it failed, but not the failure itself. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent libxine update seems to cause ICE on 6-STABLE/amd64
On Sunday 18 February 2007 11:04, Jack L. wrote: It fails to compile with the gcc version that comes with FreeBSD 6 and 7, but it compiles fine on gcc 4.1 when I tried. It's probably a compiler bug that's been fixed on the 4.x series. Yes, I agree it builds fine on 6.2/amd64 when gcc 4.1 is used. I guess a simple fix for the port would be to update the USE_GCC version to a value known to work (4.1 and 4.2 from ports are ok, no idea about 4.0). Hopefully someone more familiar with the compiler suites would be able to fix the system compilers. Andy On 2/17/07, Andy Fawcett [EMAIL PROTECTED] wrote: On Thursday, libxine was updated in the ports collection to version 1.1.4 Unfortunately, this seems to cause some kind of compiler-suite error on 6.2-STABLE/amd64. dsputil.c:3826: error: unrecognizable insn: (insn 62 10 12 0 (set (reg:SI 0 ax [61]) (subreg:SI (plus:DI (subreg:DI (reg:SI 7 sp) 0) (const_int -4 [0xfffc])) 0)) -1 (nil) (nil)) dsputil.c:3826: internal compiler error: in extract_insn, at recog.c:2083 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. gmake[5]: *** [dsputil.lo] Error 1 gmake[5]: Leaving directory `/usr/ports/multimedia/libxine/work/xine-lib-1.1.4/src/libffmpeg/libavcod ec' Please see PR ports/109213 (raised by another person) for slightly more context to the error. It's bitten two of us so far, apparently in identical way. I'm not sure this should be a ports PR, maybe it should go to the compiler suite? Andy -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent libxine update seems to cause ICE on 6-STABLE/amd64
On Sunday 18 February 2007 16:32, Ariff Abdullah wrote: On Sun, 18 Feb 2007 14:28:54 +0200 Andy Fawcett [EMAIL PROTECTED] wrote: On Sunday 18 February 2007 11:04, Jack L. wrote: It fails to compile with the gcc version that comes with FreeBSD 6 and 7, but it compiles fine on gcc 4.1 when I tried. It's probably a compiler bug that's been fixed on the 4.x series. Yes, I agree it builds fine on 6.2/amd64 when gcc 4.1 is used. I guess a simple fix for the port would be to update the USE_GCC version to a value known to work (4.1 and 4.2 from ports are ok, no idea about 4.0). Hopefully someone more familiar with the compiler suites would be able to fix the system compilers. How about using default compiler + this patch: http://people.freebsd.org/~ariff/ports/multimedia_libxine/patch-xzz This patch allows libxine to build on my system. Thanks, Andy -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Recent libxine update seems to cause ICE on 6-STABLE/amd64
On Thursday, libxine was updated in the ports collection to version 1.1.4 Unfortunately, this seems to cause some kind of compiler-suite error on 6.2-STABLE/amd64. dsputil.c:3826: error: unrecognizable insn: (insn 62 10 12 0 (set (reg:SI 0 ax [61]) (subreg:SI (plus:DI (subreg:DI (reg:SI 7 sp) 0) (const_int -4 [0xfffc])) 0)) -1 (nil) (nil)) dsputil.c:3826: internal compiler error: in extract_insn, at recog.c:2083 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. gmake[5]: *** [dsputil.lo] Error 1 gmake[5]: Leaving directory `/usr/ports/multimedia/libxine/work/xine-lib-1.1.4/src/libffmpeg/libavcodec' Please see PR ports/109213 (raised by another person) for slightly more context to the error. It's bitten two of us so far, apparently in identical way. I'm not sure this should be a ports PR, maybe it should go to the compiler suite? Andy -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
On Tuesday 06 December 2005 23:46, Kris Kennaway wrote: On Tue, Dec 06, 2005 at 02:36:05PM -0700, secmgr wrote: Update to 5.4 before trying to update to 6.0. Kris So is there any supported direct 5.3-6.0 upgrade path, or is a stop in 5.4 ville manditory now.? I tried to say that you have to update to 5.4 before you can update to 6.0, i.e. updates from older versions are not supported. It may be easier to do a binary upgrade (i.e. download release media and use the upgrade option). At least with a vanilla install of 5.3, I had no problem going directly to 6.0. This was an extremely basic install, and I only did it because I lost my 6.0-R cd :) A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg-clients conflicts with xterm (patch)
On Wednesday 16 November 2005 23:26, Dejan Lesjak wrote: On Wednesday 16 of November 2005 04:26, James Long wrote: After hours of head-banging over the past couple of days, I have finally succeeded in installing EITHER xorg-clients-6.8.2_1 OR xterm-206_1. Previously, installing either port told me that it conflicted with the other, in spite of having cvsupped my ports tree twice to ensure I was getting the most recent version of the ports, hopefully including a fix to the chicken-and-egg problem noted in /usr/ports/UPDATING x11/xorg-clients port does not conflict with any version of xterm. Where do you see that? For an interesting variation, I have a totally up to date ports tree, with the latest versions of xterm and xorg-clients already installed: xterm-206_1 Terminal emulator for the X Window System xorg-clients-6.8.2_1 X client programs and related files from X.Org then, portupgrade -fp xterm xorg-clients ... === Installing for xterm-206_1 === xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Again, please note that xterm conflicts with the version of the clients it is supposed to work with. This is repeatable on 2 systems I have tried so far, 5.4-RELEASE/i386 and 6.0-STABLE/amd64. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg-clients conflicts with xterm (patch)
Argh! Correction below. On Thursday 17 November 2005 00:02, Andy Fawcett wrote: On Wednesday 16 November 2005 23:26, Dejan Lesjak wrote: On Wednesday 16 of November 2005 04:26, James Long wrote: After hours of head-banging over the past couple of days, I have finally succeeded in installing EITHER xorg-clients-6.8.2_1 OR xterm-206_1. Previously, installing either port told me that it conflicted with the other, in spite of having cvsupped my ports tree twice to ensure I was getting the most recent version of the ports, hopefully including a fix to the chicken-and-egg problem noted in /usr/ports/UPDATING x11/xorg-clients port does not conflict with any version of xterm. Where do you see that? For an interesting variation, I have a totally up to date ports tree, with the latest versions of xterm and xorg-clients already installed: xterm-206_1 Terminal emulator for the X Window System xorg-clients-6.8.2_1 X client programs and related files from X.Org then, portupgrade -fp xterm xorg-clients ... === Installing for xterm-206_1 === xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Again, please note that xterm conflicts with the version of the clients it is supposed to work with. this should read shows a conflict with a version of the port that is not installed. This is repeatable on 2 systems I have tried so far, 5.4-RELEASE/i386 and 6.0-STABLE/amd64. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lifetime of FreeBSD branches
On Friday 27 May 2005 23:22, Matthias Buelow wrote: Scott Long wrote: Yeah, and what I'm trying to do is smooth the bumps for the long term. The 4.x-5.x transition was simply a gigantic mess for users, and it was largely a function of it being 4+ years in the making. rantIt still _is_ a gigantic mess. My hosted 5.3-stable server just crapped itself for the second time this year, for no apparent reason. I suggest reestablishing 4.x as the production tree and continuing to maintain it for a while, including making releases, and regressing 5.x to what it is and probably will be for quite a while: experimental./rant And to counter your rant, I've been using 5.x since 5.0-DP1 on a range of hardware (mostly i386 in quite different setups, and more recently amd64 too) with virtually no problems. On the other hand, 4.x (I think it was 4.9, but I really cannot remember for sure) crapped all over one box so hard I refuse to ever use it again. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qt applications hang
On Sunday 20 March 2005 09:26, Francois Tigeot wrote: On Sat, Mar 19, 2005 at 05:47:01PM -0800, David Wolfskill wrote: There's a recent entry in /usr/ports/UPDATING that may be relevant. Thanks, but I fail to see what is relevant in this case. I suspected at one time the system compiler to be busted, but I recompiled everything with -O -pipe and the problem remains. Cc to -amd64 to see if there may be something architecture specific. [For the record, every QT application hang immediately when some menu options are selected. The system is 5.4-PRERELEASE/amd64] I have 5.4-PRE on my work amd64 box (kernel/world built a few days ago) and I'm running KDE from ports in it without apparent problems. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qt33 Build Problem
On Monday 17 January 2005 22:23, Tom Huppi wrote: I worked at re-building Qt33 for quite some time, but 'libqt-mt.so' still retains a reference to 'libc_r'. If there are any common reasons why this may be, I'de be interested to know of them. Make sure you rebuild devel/qmake before building qt This is because it is the config defined by qmake (actually /usr/local/share/qt/mkspecs/freebsd-g++/qmake.conf) that defines what thread library to use in building qt. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
