- Arch-general - lists.archlinux.org

[arch-general] Help with backtrace from kcmshell crash - changing icons.
by David C. Rankin 14 Aug '10

14 Aug '10

Guys, I have a problem with kdemod3. It is really still in quite fantastic shape. When I try to switch icons to the 'iceglass' icons theme (or Azenis theme, etc..) kcmshell crashes starting with ? "strlen() from /lib/libc.so.6" ?? Hopefully it isn't something like the std c libraries now being incompatible with kcmshell?? I'm guessing that there is something in the icon file like an extra space or a long filename that is causing Appearance -> Icons (change theme). The crash occurs the moment I click on the theme to get a preview, so it might be something related to the preview and not the icon set itself. I have used this save icon theme with kde3 many times on SuSE, so I guess some file has been patched to get around whatever is causing this to choke. My immediate problem is I suck at reading backtraces. Can you help a brother out and give it a once-over and see if a specific file or problem stands out? If I can figure out what package started the crash, I can go look for an update or patch in AUR or with google generally. But I can't tell what package to start looking for. Thanks. The backtrace is: 18:38 alchemy:~/dt/icons/coolicons> cat ~/arch/bugs/icons-iceglass.kcrash [Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007f62ee19c642 in strlen () from /lib/libc.so.6 #6 0x00007f62ef030cb0 in gz_open () from /usr/lib/libz.so.1 #7 0x00007f62f1d74e37 in KSVGIconEngine::load(int, int, QString const&) () from /opt/kde/lib/libkdecore.so.4 #8 0x00007f62eb1e6616 in IconThemesConfig::themeSelected(QListViewItem*) () from /opt/kde/lib/kde3/kcm_icons.so #9 0x00007f62eb1ead00 in IconThemesConfig::qt_invoke(int, QUObject*) () from /opt/kde/lib/kde3/kcm_icons.so #10 0x00007f62f05753cf in QObject::activate_signal(QConnectionList*, QUObject*) () from /opt/qt/lib/libqt-mt.so.3 #11 0x00007f62f088ec00 in QListView::selectionChanged(QListViewItem*) () from /opt/qt/lib/libqt-mt.so.3 #12 0x00007f62f064d1d2 in QListView::setCurrentItem(QListViewItem*) () from /opt/qt/lib/libqt-mt.so.3 #13 0x00007f62f06537ac in QListView::contentsMousePressEventEx(QMouseEvent*) () from /opt/qt/lib/libqt-mt.so.3 #14 0x00007f62f25e707f in KListView::contentsMousePressEvent(QMouseEvent*) () from /opt/kde/lib/libkdeui.so.4 #15 0x00007f62f067d61f in QScrollView::viewportMousePressEvent(QMouseEvent*) () from /opt/qt/lib/libqt-mt.so.3 #16 0x00007f62f067c4d0 in QScrollView::eventFilter(QObject*, QEvent*) () from /opt/qt/lib/libqt-mt.so.3 #17 0x00007f62f064c91e in QListView::eventFilter(QObject*, QEvent*) () from /opt/qt/lib/libqt-mt.so.3 #18 0x00007f62f057545c in QObject::activate_filters(QEvent*) () from /opt/qt/lib/libqt-mt.so.3 #19 0x00007f62f05754b7 in QObject::event(QEvent*) () from /opt/qt/lib/libqt-mt.so.3 #20 0x00007f62f05a9be3 in QWidget::event(QEvent*) () from /opt/qt/lib/libqt-mt.so.3 #21 0x00007f62f0517c75 in QApplication::internalNotify(QObject*, QEvent*) () from /opt/qt/lib/libqt-mt.so.3 #22 0x00007f62f0518feb in QApplication::notify(QObject*, QEvent*) () from /opt/qt/lib/libqt-mt.so.3 #23 0x00007f62f1d0aee2 in KApplication::notify(QObject*, QEvent*) () from /opt/kde/lib/libkdecore.so.4 #24 0x00007f62f04b7858 in QETWidget::translateMouseEvent(_XEvent const*) () from /opt/qt/lib/libqt-mt.so.3 #25 0x00007f62f04b6356 in QApplication::x11ProcessEvent(_XEvent*) () from /opt/qt/lib/libqt-mt.so.3 #26 0x00007f62f04c9022 in QEventLoop::processEvents(unsigned int) () from /opt/qt/lib/libqt-mt.so.3 #27 0x00007f62f052e609 in QEventLoop::enterLoop() () from /opt/qt/lib/libqt-mt.so.3 #28 0x00007f62f06e5480 in QDialog::exec() () from /opt/qt/lib/libqt-mt.so.3 #29 0x00007f62ebbe284a in kdemain () from /opt/kde/lib/libkdeinit_kcmshell.so #30 0x00000000004076e8 in ?? () #31 0x0000000000407e85 in ?? () #32 0x0000000000408562 in ?? () #33 0x0000000000408ea4 in ?? () #34 0x00007f62ee13fc4d in __libc_start_main () from /lib/libc.so.6 #35 0x0000000000404549 in ?? () #36 0x00007fff18e7cb18 in ?? () #37 0x000000000000001c in ?? () #38 0x0000000000000005 in ?? () #39 0x00007fff18e7da23 in ?? () #40 0x0000000000000000 in ?? () -- 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

2 1

[arch-general] Request to orphan package
by ptchinster 14 Aug '10

14 Aug '10

Hello, I am the maintainer of eclipse-android (http://aur.archlinux.org/packages.php?ID=14544) One of the dependancies is eclipse-classic (http://aur.archlinux.org/packages.php?ID=32314) (v3.5 as opposed to 3.6 in the main repos) which is NOT maintained by me. There are several issues with this PKGBUILD including being out of date, not having a working build(), and not offering a correct provides array. The first of which was brought to the current maintainers attention back on May 13th, and he hasn't touched it since. I am willing to adopt this package as soon as orphaned. Thanks, ptchinster -- "Somewhere, something incredible is waiting to be known." --Carl Sagan "Keep on rockin' in the free world." -- Neil Young

3 2

[arch-general] Help me recover KDE-Plasma context menu
by Nilesh Govindarajan 14 Aug '10

14 Aug '10

I changed the plasma desktop behavior to show application launcher menu on right click. Now I'm unable to set wallpaper etc. How to revert to default setting if not by rm -r ~/.kde4/share/config/plasma* -- Regards, Nilesh Govindarajan Facebook: http://www.facebook.com/nilesh.gr Twitter: http://twitter.com/nileshgr Website: http://www.itech7.com VPS Hosting: http://www.itech7.com/a/vps

2 3

[arch-general] Fwd: [arch-dev-public] /dev/shm permissions and building in chroot
by Thomas Dziedzic 14 Aug '10

14 Aug '10

On Fri, Aug 13, 2010 at 10:51 PM, Allan McRae <allan(a)archlinux.org> wrote: > Hi, > > I have been tracking down a python3 bug and it turns out to be caused by > our chroot building. Essentially the permissions of /dev/shm are different > in the chroot than on the system: > > allan@mugen /home/arch/chroot/stable-i686/copy/dev > > ls -ld shm > drwxr-xr-x 2 root root 40 Jul 12 15:16 shm > > allan@mugen /dev > > ls -ld shm > drwxrwxrwt 2 root root 40 Aug 14 10:23 shm > > So when configure scripts try to test for POSIX semaphores by writing in > that directory, they fail. > > Looking at the relevant line in mkarchroot: > mount -o bind /dev "${working_dir}/dev" > > Doing that manually show the same issue. Should we add > > chmod 1777 "${working_dir}/dev/shm" > > after the mount? It fixes my issue but feels hackish. Any other > suggestions? > > Allan > > > > oops I don't have time to try it now, but we could try mounting it without a bind as described here: http://www.linuxfromscratch.org/lfs/view/stable/chapter06/kernfs.html Cheers! Sorry for sending it to arch-general, but I don't have "write" access to arch-dev-public :P

1 0

[arch-general] Mailman update
by Dan Vratil 13 Aug '10

13 Aug '10

Hi, please, could someone update the mailman package? It's outdated quite a long (at least since February 2009) and there is a new version 2.1.13 from December 2009. Thank you! Dan -- --------------------------------- Dan Vrátil vratil(a)progdansoft.com ICQ 249163429 Jabber progdan(a)jabber.cz Tel. +420 732 326 870 Tento email neobsahuje žádné viry, protože odesílatel nepoužívá Windows. / This email does not contain any viruses because the sender does not use Windows.

6 10

[arch-general] bash - pathname expansion controls 'set -f' or 'set -o noglob' on broken?
by David C. Rankin 13 Aug '10

13 Aug '10

Guys, I'm either misunderstanding how to control expansion of wildcards on the command line when passing the parameter containing the wildcard as a cli option to a script or the bash controls to allow that are broken. I want to set up a little script alias to search /var/abs for packages and I want the ability to pass either 'name' or 'name*' or '*name*' as input, but if there is anything matching in the current directory, expansion happens before the cli is passed to the script. Reading, I should be able to turn globbing off with either 'set -f' or 'set -o noglob' and then I should be able to pass the parameter contained a wildcard to the script without any pathname expansion. That appears broken -- or my logic is broken. From man bash 'set -f' or 'set -o noglob on' should prevent expansion: set [+abefhkmnptuvxBCEHPT] [+o option] [arg ...] <snip> -f Disable pathname expansion. <snip> -o option-name The option-name can be one of the following: <snip> noglob Same as -f. EXAMPLE: touch pacman-foo then use the following as your test script (tst.sh): #!/bin/bash myvar="$1" printf "Search: %s\n" $myvar exit 0 Now since i have a file called pacman-foo in my directory trying to pass 'pacman*' should result in expansion before the cli is read resulting in: 00:42 nirvana:~/scr/arch/tmp> ./tst.sh pacman* Search: pacman-foo single-quoting doesn't even protect the cli?? : 00:42 nirvana:~/scr/arch/tmp> ./tst.sh 'pacman*' Search: pacman-foo Now try 'set -f' to disable pathname expanstion: 01:00 nirvana:~/scr/arch/tmp> set -f 01:02 nirvana:~/scr/arch/tmp> ./tst.sh pacman* Search: pacman-foo 01:02 nirvana:~/scr/arch/tmp> ./tst.sh 'pacman*' Search: pacman-foo Huh? Now try 'set -o noglob' 01:02 nirvana:~/scr/arch/tmp> set -o noglob 01:03 nirvana:~/scr/arch/tmp> ./tst.sh pacman* Search: pacman-foo 01:04 nirvana:~/scr/arch/tmp> ./tst.sh 'pacman*' Search: pacman-foo Huh? Again.. What gives is it bash or is it something I'm reading wrong? -- 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

3 6

[arch-general] [signoff] kernel26 2.6.35.1-1
by Thomas Bächler 13 Aug '10

13 Aug '10

Upstream update, please test and sign off. We should probably be able to move this to core by the end of the week unless major problems occur. Please also sign off on 2.6.34.3 (see http://mailman.archlinux.org/pipermail/arch-dev-public/2010-August/017557.h…) I'd like to move that to core today already, as it fixes a number of problems with .34.2.

2 1

Re: [arch-general] [arch-dev-public] [signoff] sudo-1.7.4.p2-1
by Florian Pritz 13 Aug '10

13 Aug '10

On 11.08.2010 04:58, Allan McRae wrote: > Upstrema update. Upstream moved the location of the timestamp files, so > everyone will receive the sudo lecture on first usage. > > Signoff both, > Allan User signoff both Some defaults changed too. (1 timestamp per tty or behavior of -s, maybe more I didn't look) -- Florian Pritz -- {flo,bluewind}(a)server-speed.net

1 0

[arch-general] mirror.cs.vt.edu outdated
by Harry Strongburg 12 Aug '10

12 Aug '10

Hello, this mirror has an old lasysync of 1279951267. Googling this number returns a few results for other mirrors at this time. What does it mean? Lastly, what mirror is the "most trusted"? I trust vt.edu, their uptime has been wonderful until it stopped updating packages. I don't want to use the archlinux.org server, as it's limited (and you guys probably don't like the extra load). Thanks.

4 3

[arch-general] Fw: [arch-dev-public] [staging] repository: Let's give it a try!
by Mario Figueiredo 12 Aug '10

12 Aug '10

Forward Rationale: To give end users (and potential devs) an opportunity to discuss this too. On 11-08-2010 16:29, Pierre Schmitz wrote: > Hi devs, > > my last attempt for this didn't get much feedback so I try to keep it > short this time...for more details see the old thread at: > http://mailman.archlinux.org/pipermail/arch-dev-public/2010-May/016770.html > > This time I am just asking to give it a try. It's implementation is > trivial and if we feel it wont work out we could easily remove it later. > If there are no real objections I'd like to implement this soon; let's > say next week. Even if you don't see the benefit right now I would be > pleased to at least give it a try. > > The idea can be summed up like this: > > testing: > * don't break packages intentionally > * don't push incomplete rebuilds > This would definitely get me interested in Testing. Right now my Linux knowledge is limited and thus Testing is a no-go zone. If however I could have a guarantee that Testing offers the same package sanity insurance of the other mirrors, I could start participating. > staging: > * a global staging repository for collaboration > its more similar to your ~/staging dir than a regular repository > * mostly meant for incomplete rebuilds > * will be excluded from mirroring (for now) > > I am open for any questions or suggestions. Thanks for reading, > > Pierre > It needs to be said that this is also reflection of what one should expect to encounter in the development process in the wild. Apart from the potential for collaboration, the idea that the Arch repos could mimic this development cycle is very appealing to me. __________________________ | | V V Development <-> Staging <-> Testing -> Release Packaging maintenance is taken away from the end user, giving them "safe" (it's still a beta, hence the quotes) access to Testing. Meanwhile developers would separate packaging from Testing, considerably giving them a lot more control over what users can access from Testing.

3 3