Re: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
On 06/14/2011 12:09 AM, Mick wrote: The last enews I read specifically warned *not* to turn on 3.1 and instead stay with the latest 2 version ... Do you have a specific reason that compels you to try to make KDE work with 3.1? If memory serves me right it was on this list that I picked up the idea that things are working just fine with 3.1, not to mention that most packages are smart enough to know which python they need with PYTHON_API variables sprinkled around ebuilds. So I was quite surprised to uncover this one.
Re: [gentoo-user] Gentoo + KDE + pulseaudio + ? == happiness
On 10/19/2010 09:48 AM, Paul Hartman wrote: 2010/10/18 Dmitry S. Makovey di...@makovey.net: I realize it may be a question more geared toward pulseaudio community but I'd rather find out whether there's something Gentoo-specific I'm missing first. Hi, do you know about this page? http://en.gentoo-wiki.com/wiki/PulseAudio I tried Pulseaudio in my Gentoo once by using that guide. thanks. I'm pretty sure I've followed that page before, but hey - it was a long time ago. I adjusted my setup according to what it says *now* - we'll see what comes out of it. I followed links a bit deeper and also checked my setup against http://forums.gentoo.org/viewtopic-t-789181-highlight-pulseaudio.html adjusting a thing or two (like using hal module vs udev, however something tells me I'll be switching back pretty soon...). I'll try it out for a while and post back the results.
Re: [gentoo-user] Gentoo + KDE + pulseaudio + ? == happiness
On 10/19/2010 09:48 AM, Paul Hartman wrote: Hi, do you know about this page? http://en.gentoo-wiki.com/wiki/PulseAudio I tried Pulseaudio in my Gentoo once by using that guide. thanks. I'm pretty sure I've followed that page before, but hey - it was a long time ago. I adjusted my setup according to what it says *now* - we'll see what comes out of it. I followed links a bit deeper and also checked my setup against http://forums.gentoo.org/viewtopic-t-789181-highlight-pulseaudio.html adjusting a thing or two (like using hal module vs udev, however something tells me I'll be switching back pretty soon...). I'll try it out for a while and post back the results. well my attempts are unsuccessful so far. Applying every trick in a book from the above links I've got nowhere. I can reliably reproduce the problem: start amarok, try to start playing movie with, say mplayer, skip through couple of frames - and voila! sound is gone. I've tried both Xine and GStreamer backends so far with the same outcome. So what I've done on top of my setup is: installed alsa-plugins, changed pulseaudio configs as per above forum post (checking along the way that my setup matches). Interesting touch on this entire ordeal I see Internal Audio Analog stereo after startup, but if I kill pulseaudio process with: /usr/bin/pulseaudio --kill my Multimedia settings will display PulseAudio server. Problems remain the same though. It could be the Mplayer's fault - I switched it over from ao=alsa to ao=pulse and same happens. Right now I've got to the point where one app may lock the device while other seems to be sending output to /dev/null and keeps sending it after app that locked device quits (looks like this is the result of using GStreamer over Xine backend).
Re: [gentoo-user] Logitech WebCam Pro 9000 and sound card [SOLVED?]
For completeness here's what I have ended up with: /etc/modprobe.d/alsa.conf : alias /dev/mixer snd-mixer-oss alias /dev/dsp snd-pcm-oss alias /dev/midi snd-seq-oss options snd cards_limit=4 slots=snd-hda-intel,snd-hda-intel,snd-usb-audio alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel options snd-card-0 enable=1 model=6stack-dig now as it turns out that sandwich of a sound system we're expected to run currently has more than one weak point. So I have learned that ALSA was only part of my problem, and I got it working just fine with the above config, now pulseaudio and phonon were two other areas where I didn't expect to struggle but I did! In the end, after spending some hours reading bulks of documents on ALSA, pulseaudio and phonon and noticing that in KDE-4.3.5 my control panel was showing not the stuff that documentation for abovementioned pieces suggests, I killed pulseaudio daemon, then restarted it back from command line and... lo-and-behold I've got PulseAudio Sound Server in the list of available output devices. Here's what I've done: in my home directory $ cat .kde4/Autostart/pulseaudio.sh #!/bin/sh /usr/bin/pulseaudio --kill /usr/bin/pulseaudio --start -D now things are singing again. Doesn't look like I'm getting both ALSA and PulseAudio, but that's OK - so far it seems like PulseAudio picks the right sinks/sources. I am not exactly sure why do I need to kill pulseaudio and restart it again - but it works. Anybody with a better insight please correct me.
Re: [gentoo-user] Logitech WebCam Pro 9000 and sound card
On 03/04/2010 08:37 AM, Paul Hartman wrote: 2010/3/4 Dmitry S. Makovey di...@makovey.net: Hi everybody, I have just bought Logitech WebCam Pro 9000 and much to my suprise things pretty much worked out of the box... almost. As I have discovered - even though video is working flawlessly, my audio has gone AWOL. I have the same webcam. My work-around is to unplug the webcam before you reboot. Real fix would be set up alsa so it knows the proper order of soundcards... I've never been able to get it to do that, though, so I just unplug webcam until I want to use it. If someone else has figured out how, I'd be happy to hear it too. well I've figured it out half-way (based on http://alsa.opensrc.org/index.php/MultipleCards ) alias char-major-116 snd alias char-major-14 soundcore options snd major=116 cards_limit=4 alias /dev/mixer snd-mixer-oss alias /dev/dsp snd-pcm-oss alias /dev/midi snd-seq-oss alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-osshree alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel options snd-hda-intel index=0 alias snd-card-1 snd-usb-audio alias sound-slot-1 snd-usb-audio options snd-usb-audio index=1 options snd slots=snd-hda-intel,snd-usb-audio Now my problem is that the only control ALSA shows for my built-in hda-intel is Master with no sub-channles available. Anybody knowledgeable enough to suggest where is the problem?
Re: [gentoo-user] KDE4+i945+kernel+external display = ?
William Kenworthy wrote: http://en.gentoo-wiki.com/wiki/Intel_GMA ah, the magic word: GMA :) Thanks for the reference I have started applying advises from there so we'll see what will I end up with. Welcome to our world of pain :( it is quite surprising considering that Intel has opensource drivers etc. So no weirdness should arise as developers have the specs etc. (at least that was my understanding so far). I made some headway using -hal for xorg-server in USE, and IgnoreEDID and setting DDC to false in xorg.conf but the latest updates ignore those and the UXA settings in the link above (check the xorg log for other dirty secrets) Xorg.0.log looks much cleaner now that I got drm issues out of the way... I am using 2.6.31-r3 (with kernel mode setting by default for the i915 - doesnt work well without it) and xorg-server 1.6.5. which intel driver do you use? Mine's 2.8.1 and I wonder if bumping to 2.9.1 that is in testing wouldn't yield better results. Its a laptop and there is no easy solution as the external screens (various) that I use with it often have only 1024x768 in common with its own LCD and stupid xorg wont let me overide it without consequences elsewhere :( xorg sucks badly at the moment and there is no viable alternative to switch to - and the saddest thing is the chipset has worked fine in the past (sadly becoming distant past for me) ... I too found degradation quite surprising since things were working pretty well up until now. I somewhat regret KDE4 switch because of all of this, however I definitely needed some of the features KDE4 apps had to offer. Traded off some of the features dear to my heart: multi-key combinations popping prompt menu, titlebar set correctly in Konsole without affecting tab name, and some others. Filed with bugs.kde.org... let's see what happens next. According to some KDE4 jsut highlighted problems in underlying Xorg, so hopefully now with all of that out in the open things will get fixed.
Re: [gentoo-user] Kgpg (KDE4) and missing menu items
Mick wrote: Over here the keys export, keys sign and keys reload are present in the drop down menu under Keys as icons, but the textual description is missing. Same with the main menu buttons. keys export, keys sign are shown but there are no tooltips when you hover over them. Otherwise they seem to work fine. yeah, that what I meant... shouldn't have written mails in the middle of the night. So I guess this is a known state of things? I never used Kgpg up until I've upgraded my work machine to KDE4 and now I find it quite surprising that something like that slipped by so many eyes...
[gentoo-user] KDE4+i945+kernel+external display = ?
Hi everybody, I've got an interesting issue today which I half-resolved, but am still wondering whether I missed something important or did something that'll bite me in the end. So here's short story: I've been running older kernel (2.6.22-gentoo-r9) and KDE3 on my laptop(x86,i945) for quite some time. Now with recent unmasking of KDE4 I went with the flow and upgraded my KDE3 to KDE4 (yep, I know it's still there, slotted etc., but that's not the point). So, after upgrade I've noticed how painfully slow my KDE4 was. Now, I've been running KDE4 on my home machine (amd64,nVidia) for quite some time now (ever since 4.2.0) and never noticed such things (mind you - it's running another rather dated kernel: 2.6.25-gentoo-r6), so I started digging. Xorg gave me no real reason for worries other than some complaints about DRI and the fact that compatible DRI would be part of kernel-2.6.28+, but I have not enabled any of the effects yet! Well, so I upgraded kernel, and... my X wouldn't start at all. Actually it did start but my externally plugged LCD monitor won't show anything. Lid on my Dell x420 laptop stays closed since I had trouble getting my 1920x1200 resolution on external LCD to cooperate with 1280x800 on internal one. SysRq saved me trouble of hitting reset too many times. A bit of digging on google brought me to this xorg.conf (probably suboptimal as I was adding options and never retracting them looking for the right combination): Section Device Identifier Intel Corporation Mobile Integrated Graphics Controller Driver intel BusID PCI:0:2:0 Option AccelMethod xaa Option monitor-LVDS LVDS EndSection Section Device Identifier Intel Corporation Mobile Integrated Graphics Controller 2 Driver intel BusID PCI:0:2:1 Option AccelMethod xaa Option monitor-LVDS LVDS EndSection Section Extensions Option Composite Enable EndSection Section Monitor Identifier LVDS Option Ignore True EndSection Section Module Load dri EndSection Section ServerFlags Option AIGLX EndSection Section DRI Group video Mode 0660 EndSection Section Screen Identifier Default Option XaaNoOffscreenPixmaps true DefaultDepth 24 Subsection Display Depth 16 Modes 1920x1200 EndSubsection Subsection Display Depth 24 Modes 1920x1200 EndSubsection Subsection Display Depth 32 Modes 1920x1200 EndSubsection EndSection Some of it are hints from KDE folk, some came from other resources. Not only that but I had recompiled my kernel quite a few times with pretty much every possible options related to intel graphics on i945 chipsets until I hit the right one. So it's kind of working. BUT - now every time I end KDE session instead of going back to KDM I'm being dropped to VT7, closer examination shows that KDM is running, but I can't get to it on any of the VTs. So I kill it and start again. And KDE4 itself leaves quite a few artifacts on screen (not entirely sure if it's related to a few effects I have enabled for usability's sake). KDE4 on my home machine haven't had any of those issues for quite some time now (it's got different issues though ;) ). Another annoyance is that with older kernel vesa framebuffer worked perfectly fine (... video=vesafb:ywrap,mttr,1280x800...@72 ...) and I was able to have full-screen framebuffered text console with 1280x800 resolution on external LCD. Now I get some viewport-like console where content is stuck in the upper-left corner (I assume it's resolution is 1280x800) but it didn't scale to full screen. So my real question is: are there any specific guides I should've followed instead of playing hit-n-miss? Did I miss something along the way that produces KDM issues? Do I really have to have an xorg.conf only to disable certain things? How do I deal with my framebuffer so that my console looks bit more sane and utilizes all given real estate of 26 monitor and not a mere 50% or so. Sorry for bundling all those into one mail, but it kind of popped up altogether so I felt bad about separating it :-D
[gentoo-user] KDE-4.2 and KDE-3.5
Hi, I was tracking KDE-4.x for a while now while sticking to stable KDE-3.5, which in gentoo's case is 3.5.9. Trying to get KDE-4.2 installed spits out a blocker: [blocks B ] =kde-base/kdebase-startkde-3.5.10 (=kde-base/kdebase-startkde-3.5.10 is blocking kde-base/kdelibs-4.2.0) which for me means switching to *2* testing platforms (3.5.10 and 4.2) when I want to test only 1 (4.2). Now my question is: how safe is it to do a workaround, and create local version of kde-base/kdelibs-4.2.0-r1 ebuild (say, -r2) which removes the block and just stick with 3.5.9 on 3.5 side ? I really don't feel like unmasking 3.5.10 builds and building them too. another confusing thing is: !=kde-base/kdebase-3.5.9-r4 !=kde-base/kdebase-startkde-3.5.10 which I read as you're fine using kde-3.5.9 as long as you don't use startkde. kind of weird. __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. ---
