[06:25] Hi, I'm trying to get docky to work w/Lubuntu 10.10 using xcompmgr, anyone else get this work? [06:26] and you could tell us more [06:26] what's the exact problem in getting docky to work [06:29] when i try to install xcompmgr i get the following error: [06:29] E: firmware-b43-installer: subprocess installed post-installation script returned error exit status 1 [06:29] and that's a broadcom driver [06:29] do you have a broadcom wlan or something [06:30] yes i do [06:30] yep [06:30] deal first with that [06:30] hum, why would broadcom have anything to do with xcompmgr? [06:31] read the error [06:31] it says firmware-b43-installer [06:31] it doesnt say anything about xcompmanager [06:31] right [06:31] is see [06:31] so how about: sudo apt-get install -f [06:32] to fix broken dependencies? [06:32] i will try that [06:34] Building dependency tree [06:34] Reading state information... Done [06:34] The following packages were automatically installed and are no longer required: [06:34] ndiswrapper-common libdmraid1.0.0.rc16 python-pyicu cryptsetup libecryptfs0 [06:34] reiserfsprogs rdate python-webkit localechooser-data ecryptfs-utils [06:34] libdebconfclient0 dmraid keyutils [06:34] Use 'apt-get autoremove' to remove them. [06:34] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [06:34] 1 not fully installed or removed. [06:34] After this operation, 0B of additional disk space will be used. [06:35] Setting up firmware-b43-installer (4.150.10.5-4) ... [06:35] Not supported low-power chip with PCI id 14e4:4315! [06:35] Aborting. [06:35] dpkg: error processing firmware-b43-installer (--configure): [06:35] subprocess installed post-installation script returned error exit status 1 [06:35] No apport report written because MaxReports is reached already [06:35] Errors were encountered while processing: [06:35] firmware-b43-installer [06:35] E: Sub-process /usr/bin/dpkg returned an error code (1) [06:35] not supported low power chip [06:35] sudo apt-get purge firmware-b43-installer [06:35] !paste | JimZilla [06:35] JimZilla: For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imagebin.org/?page=add | !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [06:37] bingo [09:51] How do I force Xorg to go into a different resolution. The native Lubuntu screen resolution only had 1024x768, 800x600, and 640x480, I know the monitor and card can go higher... but how? [09:53] Hi I am trying to fix the volume slider on the lxde panel. It doesn't work now, but I can't find any information how to configure it [09:53] Any ideas? [10:19] nobody here that has some hints on getting an volume slider to work? [10:21] Ascavasaion, stop lxdm, run Xorg -configure from tty1, sudo mv /root/Xorg.conf /etc/X11/ and add few mode lines with wanted resolution [10:21] joris, and how it's not working [10:22] bioterror, Thanks man. And it will still open the desktop managers? [10:23] you can easily dig from google those few lines [10:24] some old X11 xorg.conf has vanished from pastebin which I've made [10:25] Ascavasaion, you can make your xorg.conf, pastebin it and I can modify it for you :D [10:25] or someone else [10:25] !paste | Ascavasaion [10:25] Ascavasaion: For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imagebin.org/?page=add | !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [10:26] it should be under SubSection "Display" [10:26] Modes "1200x800" or what ever you want it to use [11:00] bioterror wel the volume control just doesn't do anything.. I can't even move the slider. I can't find any documentation on how to configure it. I just solved it with installing volumeicon http://www.softwarebakery.com/maato/volumeicon.html [11:03] joris__, sounds weird [11:04] ALSA maybe bioterror ? [11:05] cant be alsa, if alsa was the problem, he would report for not having sounds [11:05] ;) [11:06] but I havent met before that kind of problem [11:06] bioterror volumeicon works very well so it is not really an issue any more, but it might be related that alsamixer uses pcm to control the volume, changing the master slider doesn't change the volume in alsamixer [11:13] a root/normal user problem? [11:17] something with the volume application itself, I think [11:17] what do you mean Ascavasaion? [11:17] I didn't run alsamixer as root.. [11:18] joris__, I do not know.. I am just making suggestions. [11:18] joris__, Then I do not know. [11:18] Well thanks for trying anyway [11:19] But it is solved and I just returned the laptop I was working on to the owner. I was just very happy to get a working volume applet on that thing [11:19] Would removing it and re-adding it to the panel not help? [11:19] No I did try that [11:19] My uneducated guess is that it was not connected to the volume slider alsamixer uses [11:20] That's why I was wondering if there was some config file somewhere I could edit [11:20] No sorry buddy... my knowledge of Linux is dodgy. [11:21] But volumeicon http://www.softwarebakery.com/maato/volumeicon.html did solve the problem very well [11:22] My knowledge of linux is not too good as well, but I know my way around ubuntu. I was going to install ubuntu, but it was unusable slow [11:22] So I installed lubuntu, worked very well, but there are too much glitches to be real satisfied [11:23] joris, with alsamixer you can adjust volume without a problem, right? [11:23] I am using lubuntu on one of my home computers [11:23] bioterror yes [11:23] but only with the pcm slider [11:24] Master was not doing anything [11:24] okay [11:24] that might be the problem then [11:25] if you cant move all bars in alsamixer [11:28] Probably yes [11:28] but I cannot select pcm in the volume applet [11:28] There is no preferences or something. Maybe there is a config file, but where would I find that? [11:30] As mentioned I got it solved though with volumeicon ,maybe lubuntu should adopt this as the default volume control. It is pretty nice [11:33] maybe for next cycle [11:33] you can suggest that on the mailing list :--) [11:35] hmm wel let's first see if it doesn't give any trouble, before start making suggestions [11:37] What would be the most polished LXDE distro at the moment? [11:38] I chose ubuntu because I know that, but there was some stuff not really working very well [11:39] joris__: Good going [11:42] joris, Lubuntu that is ;) [11:42] LXDE and Lubuntu works so closely together [11:45] well I love lubuntu for it's speed and easy interface, but it is really missing a little bit of polish of it just works that ubuntu has [11:45] what is it missing === MrChrisDruif1 is now known as MrChrisDruif [11:46] Well I had trouble with volume control, xine in chromium and couldn't get an encrypted home folder to work [11:47] small problems! ;D [11:47] ;) [11:47] encrypted home is under progress, it has something to do with LXDM [11:47] for 11.04 it should work [11:47] cool good to know! [11:48] that volume control thingie sounds like a case for bugraport [11:48] check your chipset with lspci and report :-) [11:48] yeah it was not my computer, so I can not do any testing [11:50] But maybe I will make a suggestion for volumeicon if it keeps on working nice. But I saw that the developer of volumeicon is not really interested in getting volumeicon in debian, so it will probably not be picked up very fast [11:51] problem seems to be alsa/oss [11:54] really? but lubuntu is using alsa, is the volume control using oss? [11:54] nope, but if someone decides to use OSS, it will make problems, I think [11:54] I'm all the way ALSA [11:55] Hmm yeah but I was using alsa, so can't be the issue [11:56] hi szczur [11:57] hi bioterror [11:57] * szczur just woke up :P [11:57] huh :o [11:57] my workday is almost done and you're just getting up :o [11:59] today is my day-off [12:03] The wonderful joys of international teams with completely different timezones :P [12:03] szczur is only one hour behind me ;) [19:04] hi [19:04] hi === Timo__ is now known as Timo_