[gentoo-user] Re: bluetooth audio
Thoughts? -james On Thu, Oct 21, 2010 at 9:11 PM, James j...@nc.rr.com wrote: All, Anyone have experience with a2dp + bluetooth? I've been Googling this for quite a while and have not really gotten lucky with setting this up. First off, I'm running xfce4 and find that most of the tools don't work very well with this window manager. For example, the Gentoo documentation is fairly specific to Gnome and KDE. Is Blueman the only non-Gnome and non-KDE tool that works well with xfce4? Also, the a2dp thing has me pulling my hair out. Is the *only* way to use a2dp with pulseaudio? Is there no way to simply redirect all audio to the bluetooth headset? Anyone who can toss some experience in my direction would be greatly appreciated. Thanks! -james
[gentoo-user] Re: usb stick autodiscovery
James wireless at tampabay.rr.com writes: emerge -D $(qlist -IC kde-base/) Dolphin is back, it show up in the 'lost and found' submenu in kde4.4.5 and it's icon is now a question mark, so something is messed up. The kde4 usbviewer app is missing... How/what do I emerge to get this back? Any suggestions are welcome, as googling has been fruitless, up to this point. James
Re: [gentoo-user] baselayout -- openrc ?
On 10/23/2010 5:03 AM, Neil Bothwick wrote: On Sat, 23 Oct 2010 02:50:26 +0200, Alan McKinnon wrote: You're mixing two different definitions of stable. Portage 2.2 is certainly reliable, but it is anything but stable with a new version coming out every day at the moment,. I'm waiting for tomorrow when my regularly scheduled portage update hits _rc100. Well, it hasn't happened yet. A day without a portage update, a rare thing these days. Maybe someone decided that Gentoo is not Debian and 99 release candidates should be enough for a bunch of python scripts. Looks like someone agrees with you: [ebuild U ] sys-apps/portage-2.2.0_alpha1 [2.2_rc91] Although, perhaps I'm missing something but doesn't alpha come *before* release candidate? :)
Re: [gentoo-user] cruft after perl-cleaner --all
On Sat, 23 Oct 2010 18:30:38 -0500, Dale wrote: Is there a way to find cruft? Some script or something? My install is pretty old and I would guess there are a few left over files here and there. Emerge portage-utils and run qfile with the --orphans option. The man page gives examples of how to use it. -- Neil Bothwick Bus: (n.) a connector you plug money into, something like a slot machine. signature.asc Description: PGP signature
Re: [gentoo-user] baselayout -- openrc ?
On Sun, 24 Oct 2010 10:30:55 -0400, Mike Edenfield wrote: Maybe someone decided that Gentoo is not Debian and 99 release candidates should be enough for a bunch of python scripts. Looks like someone agrees with you: [ebuild U ] sys-apps/portage-2.2.0_alpha1 [2.2_rc91] Although, perhaps I'm missing something but doesn't alpha come *before* release candidate? :) That was my thought too, and they had to switch from 2.2 to 2.2.0 to stop portage itself feeling the same. Perhaps it will be stabilised before Debian 10.0 is released... -- Neil Bothwick I heard someone tried the monkeys-on-typewriters bit trying for the plays of W. Shakespeare but all they got was the collected works of Francis Bacon signature.asc Description: PGP signature
Re: [gentoo-user] baselayout -- openrc ?
On Sun, 2010-10-24 at 10:30 -0400, Mike Edenfield wrote: Looks like someone agrees with you: [ebuild U ] sys-apps/portage-2.2.0_alpha1 [2.2_rc91] Although, perhaps I'm missing something but doesn't alpha come *before* release candidate? :) One could argue that if you've had as many as 99 release candidates you were pretty much alpha all along ;) -a
Re: [gentoo-user] cruft after perl-cleaner --all
Neil Bothwick wrote: On Sat, 23 Oct 2010 18:30:38 -0500, Dale wrote: Is there a way to find cruft? Some script or something? My install is pretty old and I would guess there are a few left over files here and there. Emerge portage-utils and run qfile with the --orphans option. The man page gives examples of how to use it. I tried like the man page says but it only found one file that was orphaned. Either portage does a exceptional job or I'm not doing something right. lol Dale :-) :-)
Re: [gentoo-user] Re: usb stick autodiscovery
Apparently, though unproven, at 03:49 on Sunday 24 October 2010, James did opine thusly: Dale rdalek1967 at gmail.com writes: Hello Dale, On mine, I had to add the device notifier widget to the panel. That is what does the little pop up here. Looks like one of your systems didn't add that by default, mine didn't either tho. Well device notifier is on the systems that work. somehow it got deleted off this system I missing the 'dolphin file manager' and the 'usb viewer' from the kde-4.4.2 H, somehow this looks strange What the best way to rebuild all of the kde packages on a (kde-meta) system? emerge kde-meta only rebuild the meta package itself emerge -avuND world If that doesn't pull in the missing bits, you have USE flags and/or package.mask getting in the way. equery depends might help, but it's only accurate for stuff you already have. For more complex things, I usually read the ebuild and see what *DEPEND says You'll have to find what -meta package[1] pulls in dolphin and usb viewer (grep ... *-meta/*ebuild) comes in handy here and then read those ebuilds to find themerge conditions. kde-meta is merely a meta package for other meta packages... -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] baselayout -- openrc ?
Apparently, though unproven, at 16:30 on Sunday 24 October 2010, Mike Edenfield did opine thusly: On 10/23/2010 5:03 AM, Neil Bothwick wrote: On Sat, 23 Oct 2010 02:50:26 +0200, Alan McKinnon wrote: You're mixing two different definitions of stable. Portage 2.2 is certainly reliable, but it is anything but stable with a new version coming out every day at the moment,. I'm waiting for tomorrow when my regularly scheduled portage update hits _rc100. Well, it hasn't happened yet. A day without a portage update, a rare thing these days. Maybe someone decided that Gentoo is not Debian and 99 release candidates should be enough for a bunch of python scripts. Looks like someone agrees with you: [ebuild U ] sys-apps/portage-2.2.0_alpha1 [2.2_rc91] Although, perhaps I'm missing something but doesn't alpha come *before* release candidate? :) Yes, but: 2.2.0_alpha1 comes *after* 2.2_rc99 -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Preventing a package from being updated
Apparently, though unproven, at 13:50 on Saturday 23 October 2010, daid kahl did opine thusly: Don't worry about it. I'm not sure if portage-2.1.9.20 will deal with this automagically (I *think* it does these days and 2.2 definitely does) but if not just emerge -C shadow ; emerge -1 shadow then emerge -avuND world. No good technical reason for doing shadow first apart from getting it over and done with while you watch and confirm it works fine. Then do world and wander over to the kettle letting portage go on with doing it's thing unattended For my own comfort, on a case like this, if I didn't have the portage FEATURE buildpkg or buildsyspkg turned on, I'd make sure that was on and that I had a functional backup of shadow to install from binary, in case something went very wrong. But I tend to be extremely cautious in terms of how I maintain my system, and a lot of that caution is just paranoia. Just because you're paranoid doesn't mean they're NOT out to get you :-) Or in this case, it doesn't mean it's not justified. I now have buildpkg enabled for @system - everything else I can re-run emerge to fix. After watching portage break python *twice* exactly a year apart, watching the exciting developments in python-3, after some horrendous shadow breakage 3 years ago and the convoluted upgrade path for bash 2 years ago, and someone's b0rked commit of glibc-2.12 to the tree quite recently, I feel entirely justified in keeping binary copies of @system around. It long ago stopped being paranoia and started being good old common sense (right up there with backups). -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Preventing a package from being updated
Alan McKinnon alan.mckin...@gmail.com writes: Just because you're paranoid doesn't mean they're NOT out to get you :-) Or in this case, it doesn't mean it's not justified. I now have buildpkg enabled for @system - everything else I can re-run emerge to fix. Does this mean for portage -2.1.9.22 you advocate FEATURES=buildsyspkg in make.conf? If so is that the correct line or do we need FEATURES=buildsyspkg sandbox I find the man page wording a little unclear and its warning about an error serious. thanks allan
Re: [gentoo-user] baselayout -- openrc ?
On Mon, 25 Oct 2010 00:29:30 +0200, Alan McKinnon wrote: Although, perhaps I'm missing something but doesn't alpha come *before* release candidate? :) Yes, but: 2.2.0_alpha1 comes *after* 2.2_rc99 It should also come after 2.2, but I appear to have missed that release. 99 release candidates and then no release is something of an anti-climax :( -- Neil Bothwick Eye of newt, toe of frog, regular Coke and fries to go, please. signature.asc Description: PGP signature
Re: [gentoo-user] Preventing a package from being updated
Allan Gottlieb wrote: Alan McKinnonalan.mckin...@gmail.com writes: Just because you're paranoid doesn't mean they're NOT out to get you :-) Or in this case, it doesn't mean it's not justified. I now have buildpkg enabled for @system - everything else I can re-run emerge to fix. Does this mean for portage -2.1.9.22 you advocate FEATURES=buildsyspkg in make.conf? If so is that the correct line or do we need FEATURES=buildsyspkg sandbox I find the man page wording a little unclear and its warning about an error serious. thanks allan This is mine. FEATURES= buildpkg sandbox fixpackages parallel-fetch --keep-going It has been that way here for a pretty long while and no problems that I know of. According to the man page, you should have sandbox in there as well. I think Alan was showing what could be added but not all the options that are available and should be there. Then again, Alan knows Gentoo pretty well and may know that he doesn't need sandbox. Just thought I would share a example that is in use and appears to work. Dale :-) :-)
[gentoo-user] vmware - help
Hi all, looking for some serious vmware debugging help! I've had vmware-workstation working for ages, but sometime this year (ok I use it sporadically!) it's stopped. I don't know if its the old GTK issue or what. No google searches has found anything similar, although I've tried a lot of suggestions I found anyway. Most recently I've recompiled the kernel, modules and workstation. I currently using workstation 6.5.4.246459 with tuxonice sources 2.6.35 and modules 1.0.0.25-r1 This is what happens if I run with the shipped_gtk option: $ VMWARE_USE_SHIPPED_GTK=force vmware Logging to /tmp/vmware-iain/setup-14963.log /usr/share/themes/Unity/gtk-2.0/gtkrc:67: error: unexpected identifier `colorize_scrollbar', expected character `}' /opt/vmware/workstation/bin/vmware: line 31: 14963 Segmentation fault $BINDIR/vmware-modconfig --appname=VMware Workstation --icon=vmware-workstation I think the gtkrc error is a red herring, but I'm willing to try any theme engine and theme you suggest :) and the force option: $ vmware Logging to /tmp/vmware-iain/setup-15540.log filename: /lib/modules/2.6.35-tuxonice/misc/vmmon.ko supported: external license:GPL v2 description:VMware Virtual Machine Monitor. author: VMware, Inc. depends: vermagic: 2.6.35-tuxonice SMP preempt mod_unload CORE2 4KSTACKS filename: /lib/modules/2.6.35-tuxonice/misc/vmnet.ko supported: external license:GPL v2 description:VMware Virtual Networking Driver. author: VMware, Inc. depends: vermagic: 2.6.35-tuxonice SMP preempt mod_unload CORE2 4KSTACKS filename: /lib/modules/2.6.35-tuxonice/misc/vmblock.ko supported: external version:1.1.2.0 license:GPL v2 description:VMware Blocking File System author: VMware, Inc. srcversion: AD9C87216C830F9C343F8E3 depends: vermagic: 2.6.35-tuxonice SMP preempt mod_unload CORE2 4KSTACKS parm: root:The directory the file system redirects to. (charp) filename: /lib/modules/2.6.35-tuxonice/misc/vmci.ko supported: external supported: external license:GPL v2 description:VMware Virtual Machine Communication Interface (VMCI). author: VMware, Inc. depends: vermagic: 2.6.35-tuxonice SMP preempt mod_unload CORE2 4KSTACKS filename: /lib/modules/2.6.35-tuxonice/misc/vsock.ko supported: external license:GPL v2 version:1.0.0.0 description:VMware Virtual Socket Family author: VMware, Inc. srcversion: 5930B98648580F723B86142 depends:vmci vermagic: 2.6.35-tuxonice SMP preempt mod_unload CORE2 4KSTACKS filename: /lib/modules/2.6.35-tuxonice/misc/vmmon.ko supported: external license:GPL v2 description:VMware Virtual Machine Monitor. author: VMware, Inc. depends: vermagic: 2.6.35-tuxonice SMP preempt mod_unload CORE2 4KSTACKS *** glibc detected *** /opt/vmware/workstation/lib/vmware/bin/vmware: malloc(): memory corruption: 0x0959b1a0 *** === Backtrace: = /lib/libc.so.6(+0x6ba71)[0xb4d1aa71] /lib/libc.so.6(+0x6e88b)[0xb4d1d88b] /lib/libc.so.6(__libc_calloc+0xab)[0xb4d1ec1b] //usr/lib/opengl/nvidia/lib/libGL.so.1(+0x82fa8)[0xb4b67fa8] /usr/lib/libglib-2.0.so.0(g_hash_table_new_full+0x87)[0xb72b9d87] /opt/vmware/workstation/lib/vmware/lib/libvmwareui.so.0/libvmwareui.so.0(+0x44bd45)[0xb55efd45] /opt/vmware/workstation/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0(Poll_InitWithImpl+0x1d)[0xb5e6600d] /opt/vmware/workstation/lib/vmware/lib/libvmwareui.so.0/libvmwareui.so.0(Poll_InitGtk+0x20)[0xb55ef7d0] /opt/vmware/workstation/lib/vmware/bin/vmware(_ZN3lui13ManageableDlgD0Ev +0x33b)[0x80aa967] /lib/libc.so.6(__libc_start_main+0xe6)[0xb4cc5cc6] /opt/vmware/workstation/lib/vmware/bin/vmware(_ZN3Gtk9TreeModelD1Ev +0x75)[0x80aa7d1] === Memory map: 08048000-083d2000 r-xp 08:07 5509263/opt/vmware/workstation/lib/vmware/bin/vmware 083d2000-083d6000 rw-p 0038a000 08:07 5509263/opt/vmware/workstation/lib/vmware/bin/vmware 083d6000-083da000 rw-p 00:00 0 09573000-095b5000 rw-p 00:00 0 [heap] b300-b3021000 rw-p 00:00 0 b3021000-b310 ---p 00:00 0 b31d9000-b31dd000 rw-p 00:00 0 b31dd000-b3302000 r-xp 08:07 4080101 /opt/vmware/workstation/lib/vmware/lib/libcrypto.so.0.9.8/libcrypto.so.0.9.8 b3302000-b3317000 rw-p 00125000 08:07 4080101 /opt/vmware/workstation/lib/vmware/lib/libcrypto.so.0.9.8/libcrypto.so.0.9.8 b3317000-b331b000 rw-p 00:00 0 b331b000-b335b000 r-xp 08:07 4342037 /opt/vmware/workstation/lib/vmware/lib/libssl.so.0.9.8/libssl.so.0.9.8 b335b000-b335f000 rw-p 0003f000 08:07 4342037 /opt/vmware/workstation/lib/vmware/lib/libssl.so.0.9.8/libssl.so.0.9.8 b335f000-b336f000 r-xp 08:07 5228442/lib/libbz2.so.1.0.6 b336f000-b337 r--p f000 08:07 5228442
