- Arch-general - lists.archlinux.org

[arch-general] pppoe-start resets eth0 MTU
by b4283 30 Jul '09

30 Jul '09

Hi, I usually set my eth0 adapter's MTU value to 7200 to get reach of Jumbo Frame function of my hub. But after I run pppoe-start (comes from rp-pppoe), it seems that the program will automatically reset the MTU value of eth0 to 1500, which is a big bugger. Does anyone know how to prevant this from happening that I wouldn't have to run "sudo ifconfig eth0 mtu 7200" again? -- b4283.

1 0

[arch-general] Latest updates messed up kdemod3 libjpeg.so.62?
by David C. Rankin 29 Jul '09

29 Jul '09

Listmates, Up until this past week kdemod3 and kde4-unstable had lived side-by-side quite harmoniously. However, now kcontol in kdemod3 will not run until the following link is created: ln -s /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.62 After the link is made, kcontol will start, but any attempt to access the panel or taskbar settings (among others) results in a complete kcontrol crash. The backtraces are generally the same: [KCrash handler] #5 0x0000000000000000 in ?? () #6 0x00007f3a2e4f29b5 in jpeg_CreateDecompress () from /usr/lib/libjpeg.so.62 #7 0x00007f3a2d92de78 in ?? () from /opt/qt/plugins/imageformats/libqjpeg.so #8 0x00007f3a337d32f9 in QImageIO::read () from /opt/qt/lib/libqt-mt.so.3 #9 0x00007f3a337d3696 in QImage::load () from /opt/qt/lib/libqt-mt.so.3 #10 0x00007f3a2a9e1b3d in KBackgroundRenderer::doWallpaper () from /opt/kde/lib/kde3/kcm_kicker.so #11 0x00007f3a2a9e270a in KBackgroundRenderer::render () from /opt/kde/lib/kde3/kcm_kicker.so #12 0x00007f3a2a9e2a28 in KBackgroundRenderer::qt_invoke () from /opt/kde/lib/kde3/kcm_kicker.so #13 0x00007f3a337fd3cf in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3 #14 0x00007f3a337ff726 in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3 #15 0x00007f3a3381d8a5 in QTimer::event () from /opt/qt/lib/libqt-mt.so.3 #16 0x00007f3a3379fc75 in QApplication::internalNotify () from /opt/qt/lib/libqt-mt.so.3 #17 0x00007f3a337a0dca in QApplication::notify () from /opt/qt/lib/libqt-mt.so.3 #18 0x00007f3a34f91ee2 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4 #19 0x00007f3a33796353 in QEventLoop::activateTimers () from /opt/qt/lib/libqt-mt.so.3 #20 0x00007f3a337517b8 in QEventLoop::processEvents () from /opt/qt/lib/libqt-mt.so.3 #21 0x00007f3a337b6609 in QEventLoop::enterLoop () from /opt/qt/lib/libqt-mt.so.3 #22 0x00007f3a337b64c2 in QEventLoop::exec () from /opt/qt/lib/libqt-mt.so.3 #23 0x00007f3a2f0555fa in kdemain () from /opt/kde/lib/libkdeinit_kcontrol.so #24 0x00000000004076e8 in ?? () #25 0x0000000000407e85 in ?? () #26 0x0000000000408562 in ?? () #27 0x0000000000408ea4 in ?? () #28 0x00007f3a313d69ed in __libc_start_main () from /lib/libc.so.6 #29 0x0000000000404549 in ?? () #30 0x00007fff9c658818 in ?? () #31 0x000000000000001c in ?? () #32 0x0000000000000005 in ?? () #33 0x00007fff9c659ad5 in ?? () #34 0x0000000000000000 in ?? () Do I need to create another link or a different link to solve this problem. Also, where should this bug report go? Chakra or Arch? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

8 11

[arch-general] VirtualBox keeps crashing
by Tim Gelter 29 Jul '09

29 Jul '09

Hello listmates, I'm having semi-frequent virtualbox crashes with existing and newly created virtual machines. Here is a snippet from /var/log/kernel.log : Jul 29 08:24:17 guapArch kernel: VirtualBox[5142] trap int3 ip:7f7dde81dd9a sp:7f7dd003bf00 error:0 Jul 29 11:38:43 guapArch kernel: VirtualBox[6559] trap int3 ip:7f4bcedacd9a sp:7f4bc0b74f00 error:0 Jul 29 11:56:47 guapArch kernel: VirtualBox[6589] trap int3 ip:7f1fd205ad9a sp:7f1fc4622f00 error:0 Jul 29 13:47:46 guapArch kernel: hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Jul 29 14:08:30 guapArch kernel: VirtualBox[7034] trap int3 ip:7f8f29938d9a sp:7f8f154e3f00 error:0 I've googled around a bit and don't see anything anywhere. Do any of you happen to have any ideas as to what is going on here? root ~ # pacman -Q virtualbox_bin virtualbox_bin 3.0.2-2 root ~ # uname -r 2.6.30-ARCH root ~ # pacman -Q kernel26 kernel26 2.6.30.2-1 root ~ # pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date kdemod-core is up to date kdemod-extragear is up to date kdemod-playground is up to date :: Starting full system upgrade... local database is up to date Thanks! Tim

2 2

[arch-general] lddd from devtools rewritten
by clemens fischer 28 Jul '09

28 Jul '09

I rewrote lddd from extra/devtools. The intent was to make it faster and remove false positives, as well as support for ignoring certain files completely, filtering the list of missing libs to handle optional dependencies, take /etc/ld.so.conf into account and in general make it more usable. NB: uses bash-4 features. URL: http://ino-waiting.gmxhome.de/files/lddd-c.sh Here's the help screen: $ lddd-c.sh -h Use lddd-c.sh [options] [paths] Default-paths: $PATH, /lib:/usr/lib:/opt/qt/lib:/opt/kde/lib:/usr/lib/libfakeroot:/opt/NX/lib:/usr/local/lib:/usr/local/libexec options: -d <item>: do not check glob <item>, can be given multiple times. -l <item>: ignore missing library glob <item>, multiple times. -L: do not use LD_LIBRARY_PATH running ldd(1)[1]. -v: be more and more chatty. -D <glob>: trigger tracing on meeting <glob>, debugging aid. Environment variables: $LDDD_LIB_IGNORE: globs of missing lib-names to ignore[2]. $LDDD_DONT_CHECK: globs of file names to completely ignore[2]. [1] risks false positives, but finds all broken ELF dependencies. [2] space separated list of globs, needs to be quoted to the shell. NB: A broken ELF file will be reported unless it is ignored ('-d' option or $LDDD_DONT_CHECK) or _ALL_ of its missing libs are ignored ('-l' or $LDDD_LIB_IGNORE)! _version: 20090727-2016_ The "new and improved" algorithm goes like this: 1. All files executable by the user or matching the customary *.so patterns are collected after verifying their ELFness. 2. The file paths are checked to see if their base directories contain any libraries and these directories are collected into LD_LIBRARY_PATH. 3. In a third loop, the files from step one are checked by ldd(1) prefixed with this LD_LIBRARY_PATH to see if any prerequisites are missing. This step is repeated without the path to check the odd customer. 4. Suspects aquired this way are sent to a co-process to determine the packages they belong to. 5. Results are collected into files in /tmp/lddd-c.sh-$UID and a summary listed to stdout. This makes it easy to use in cron-jobs. Detail is controlled by the number of '-v' options. Step four was intended to speed up the process, but as it turns out it doesn't help all that much. The pacman call is indeed expensive and can be done in parallel, but it obviously competes for disk access. Therefore the co-process caches the file list of any broken package expecting to find more broken files in it, but this only helps big packages with several broken executables. All in all lddd-c.sh is an improvement over the simpler lddd and the terribly hacked findbrokenpkgs[1]. As there should be no false positives, it should report b0rked packages after botched or incomplete updates in a reliable way. Valuable testing was done by Allan McRae and AttilaH. Some nasty bugs would still stink the code without their patience. [1] http://bbs.archlinux.org/viewtopic.php?id=13882 clemens

1 1

[arch-general] What? - NO 'p' in dmraid-1.0.0.rc15-8 anymore?
by David C. Rankin 28 Jul '09

28 Jul '09

Listmates, After going through the testing process with dmraid-1.0.0.rc15 where the biggest change for users was the addition of the 'p' in the /dev/mapper/raidname_device_partx naming convention, the last update warns that you must now *remove* the 'p' from fstab, etc.. What's up? Will we have to add the 'p' again next week? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

1 1

Re: [arch-general] [arch-dev-public] [signoff] ed 1.4-1
by Gerardo Exequiel Pozzi 28 Jul '09

28 Jul '09

Roman Kyrylych wrote: > On Tue, Jul 28, 2009 at 21:52, Eric Bélanger<snowmaniscool(a)gmail.com> wrote: > >> On Tue, Jul 28, 2009 at 10:27 AM, Ronald van Haren<pressh(a)gmail.com> wrote: >> >>> On Sun, Jul 26, 2009 at 8:59 PM, Andreas Radke <a.radke(a)arcor.de> wrote: >>> >>>> minor upstream update. please signoff. >>>> >>>> -Andy >>>> >>>> Changes in version 1.4: >>>> >>>> >>>> * The undo command has been fixed to restore the modified status of the >>>> buffer being edited. >>>> >>>> * A race condition with user interrupt has been fixed in >>>> search_and_replace. >>>> >>>> * The functions resize_line_buffer and resize_undo_buffer have been >>>> added to definitively fix the aliasing warnings. >>>> >>>> * Some minor corrections have been made to the manual. >>>> >>> It still fires up and displays a simple txt document, haven't tested >>> anything fancy though. >>> signoff i686 >>> Ronald >>> >> signoff x86_64 >> > > signoff['x86_64']++ > > > Sign-Off i686 Manual pages are OK Info pages are not compressed. (pending for next pacman) but... $ ed a i can't still import my office2007 documents here!!! I am desesperate! . w tested 72 q $ -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D

1 0

[arch-general] AUR networkmanager-plasmoid-svn
by Manne Merak 28 Jul '09

28 Jul '09

Anyone know what is going on with this plasmoid? I see it has been marked as out of date. It hasnt build successfully for me in a month now. Manne

2 1

[arch-general] /etc/resolv.conf continuously wiped since yesterday
by Caleb Cushing 28 Jul '09

28 Jul '09

since a reboot/updates yesterday my /etc/resolv.conf has been getting wiped (when it happens I lose all dns). I don't know why. does anyone have any ideas what might be going on? # A sample configuration for dhcpcd. # See dhcpcd.conf(5) for details. # Inform the DHCP server of our hostname for DDNS. hostname # A list of options to request from the DHCP server. # Most distributions have NTP support. option ntp_servers # Behave nicely on networks and respect their MTU. # However, a lot of buggy DHCP servers set invalid MTUs so this is not # enabled by default. #option interface_mtu # A ServerID is required by RFC2131. # Some broken DHCP servers do not send one and dhcpcd can work without it. # Some broken DHCP servers NAK incorrectly and do not include a ServerID either so # the default is to require a ServerID. require dhcp_server_identifier # A hook script is provided to lookup the hostname if not set by the DHCP # server, but it should not be run by default. nohook lookup-hostname noipv4ll -- Caleb Cushing http://xenoterracide.blogspot.com

4 6

[arch-general] Cisco VPN config
by Rafa Griman 27 Jul '09

27 Jul '09

Hi :) Got a Cisco VPN connection with my office, but can't manage to get it running. I've seen that there's a: - vpnc package: installed it, but it doesn't import the .pcf file, says it can't find the file. - cisco-vpnclient: but it's out-dated I've been searching through the Wiki but haven't found any help on how to setup a Cisco VPN connection to my office. Anyone have a link or some tips they could share? TIA Rafa BTW Got the KMS + UXA running, seems I messed something up the other time I tried 0:) Thanks also for the kdmrc tip. -- "We cannot treat computers as Humans. Computers need love." rgriman(a)skype.com rgriman(a)jabberes.org

6 10

[arch-general] Where can I find the "boot" log to find out what failed on boot?
by David C. Rankin 27 Jul '09

27 Jul '09

Listmates, Seems like a simple question, but I've searched /var/log and can't find a file that contains the boot history showing all the "fail" messages during boot. For some reason after the latest update, my i686 box showed a half dozen or so "fail" messages. I need to find the log of what died. The upside to this? This was my i686 box that would no longer start kde after the next-previous set of updates. Now kde4 starts fine again. Whatever failed can't be that critical because the box is functioning fine, but I still want to find out what failed. If the file is in /var/log, then I just flat missed it. I thought it would be daemons.log, but I found no fail messages. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

10 11