Debian Configuration :: Configure Skype On System (testing, X86) But Unsuccessfully?
Oct 3, 2010
but I have been literally banging my head against the wall.I am trying to configure skype on my system (testing, x86) but unsuccessfully.Let me say that I am now using skype (static) as downloaded from skype website.
$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 04)
I'm trying to set up my Intel Wireless 3945ABG (which is supported in the kernel) and I don't understand where to start if I want to use systemd to do this.
I've installed my Debian (Stretch Alpha4) base system using the wireless to download the necessary components but when I boot into the system I need to set up the wireless card separately.
I would prefer to be able to install wireless without the requirement of connecting via ethernet so no package installs other than what is downloaded by the installer.
I can't even find documentation on this specific issue because everyone seems to reference /etc/network/interfaces which AFAIK is not supported in systemd. How do I configure a wireless card using only systemd?
I've installed the latest testing version, which has 2.6.32 kernel perfect for me. I was very amazed when check system monitor and saw it runs with 90MB RAM, meanwhile my ubuntu desktop takes only 400, and the pocket version of ubuntu on vmware has 180MB RAM.
The questions is: Debian runs on vmware 7. Could the amount of RAM change when switching to a normal environment? Or I have to test and see what is happening..What problems could occur when using a testing version?
(==) Log file: "/var/log/Xorg.0.log", Time: xx (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) open /dev/fb0: No such file or directory
[Code].....
My usual aptitude safe-upgrade routine has not throw any errors. I do remember a libxcb-* package updating (or installing?) on the last run. This is the only relevant package I can recall.
I have an older system that has been running testing for about 4 years. Originally I was running testing for several packages that were not yet available in stable. However, now that this system has a more crucial role in the network I have considered moving it to stable in hopes that it I can gain some insurance on it's uptime. It is important to note that I have never had a problem with the testing distribution and would be quite content to continue running it; I do want to know my options though.
I have not yet updated the system since the stable release of squeeze, I am considering to change my sources from testing to stable and just let apt take care of the rest. Anyone have any experience with such a thing? After searching Google I have found some solutions to force a downgrade, but that is really not what needs to be done here. I suppose I should have switched my sources to squeeze some time ago and this probably would have worked itself out.
A similar question is what happens a couple of years from now when another release happens. Have you had good luck updating from old stable to stable? I've run testing on several machines now for several years and have went through freezes and dist-upgrades several times with no major problems at all. Will I see the same stability if I move to the stable distribution?
After the latest update of network-manager-gnome to version 1.1.90-3 , I see that I have to start the nm-applet in Testing from a terminal, otherwise I can't bring up my wired connection.
The usual nmcli networking on command is failing to connect, also restarting the network-manager.service with systemctl doesn't do anything, the only way to connect at this time is indeed to manually start the nm-applet from a terminal.
I've also spotted this message in the logs:
Code: Select alltraps: nm-applet[1105] general protection ip error:0 in libgobject-2.0.so.0.4600.2
Could it be something wrong with my configuration (although , it worked before this update) or is it some bug in network-manager-gnome 1.1.90 ?
I've been working on the setup of a FTP server on my Debian system for the whole afternoon. But I can't get it straight! Normally I get it working in just a second, but it's been a while I guess.
I installed only proftpd-basic and it's default dependencies. Should be enough right?
My configuration files are as follows:
I created the user zeitgeist, gave it a password, group and a homedir. Group of the user is nogroup and the homedir is correct with the 755 permission. My port 21 for FTP is open I tested it with nmap -p 21 [ip-address].
My Filezilla client tells me that at first he is connecting, then the connection is established, And then the connection is closed by server.
For anyone using Blueman with Testing (Squeeze), todays Python upgrade to version 2.6 stops it from working due to a Blueman bug. This has been fixed in blueman version 1.21-4, which you can install from SID if you don't want to wait the 10 days for the normal migration.
I am running testing (with fluxbox) and my keyboard periodically freezes, meaning whatever I type in it doesn't respond. This lasts a few seconds (can be 2-3 or sometimes even more like 10) and one's it comes back I get all the keystrokes I was typing during the freeze. The frequency of the freezes can be like 4-5 times every hour and are very annoying. I can't seem to relate them to anything, they can occur during heavy usage but also when the box is doing absolutely nothing but waiting lazily for me to type some google search terms.
Can anybody help me track this problem down? At the moment I am using a wireless keyboard but this must be unrelated since I tested a couple of other keyboards (both wireless and wired) and the problem persists.
can't use catalyst driver, virtualbox refuse to run, selinux problems,I want to know if its possible to install only this new kernel 2.6.38 without "contaminating" the rest of my installation with unstable packages?
After doing a aptitude full-upgrade I no longer have the Debian menu showing in the Openbox menu. According to Obmenu, Debian is listed; it's just not showing when I right click. The upgrade brought a new version of Openbox so I assume that has something to do with it.
I'm trying to install Debian-testing to an ASUS 1018P netbook on which I have successfully installed Arch in the past. I'm installing from an external DVD drive and when I get to the point of network configuration it fails. I'm connected via Ethernet via eth0 which is recognized. Here is the last part of the ouput:
kernel: [ 1807.932848] atl1c 0000:01:00.0: irq 29 for MSI/MSI-X kernel: [ 1807.933453] ADDRCONF(NETDEV_UP): eth0: link is not ready dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval is 8 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval is 15 code....
I have been trying to install fglrx drivers for my ATI card with Debian testing (x86) but without any luck. I have tried what it says here http://wiki.debian.org/ATIProprietary but I only come up with a blank screen (and also invoke-rc.d gdm stop does not work either?) I have also followed the directions at [URL]....html and that doesn't work either (make error 127). I must be doing something totally wrong.
AMD 64 Upgrade to testing last night killed my internet connection. The lan works, I can ping the dns server from my IP, however no mail, browser possible. Is something in testing broken again?
I just updated my Debian testing as usual (apt-get update && apt-get dist-upgrade), and it totally screwed up Nvidia drivers. I had to revert to integrated graphic card to start Xorg. After that, I noticed that libgl1-nvidia-glx is missing, and when I tried to install it back, it produces the following:
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: libgl1-nvidia-glx : Depends: libgl1-nvidia-alternatives but it is not going to be installed E: Broken packages
I will be relocating to a permanent residence sometime in the next year or two. I've recently begun thinking about the best way to implement a home-based network. It occurred to me that the most elegant solution might be the use of VM technology to eliminate as much hardware and wiring as possible.My thinking is this: Install a multi-core system and configure it to run several VMs, one each for a firewall, a caching proxy server, a mail server, a web server. Additionally, I would like to run 2-4 VMs as remote (RDP)workstations, using diskless workstations to boot the VMs over powerline ethernet.The latest powerline technology (available later this year) will allow multiple devices on a residential circuit operating at near gigabit speed, just like legacy wired networks.
In theory, the above would allow me to consolidate everything but the disklessworkstations on a single server and eliminate all wired (and wireless) connections except the broadband connection to the Internet and the cabling to the nearest power outlets. It appears technically possible, but I'm not sure about the various virtual connections among VMs. In theory, each VM should be able to communicate with the other as if it was on the same network via the server data bus, but what about setting up firewall zones? Any internal I/O bandwidth bottlenecks? Any other potential "gotchas", caveats, issues? (Other than the obvious requirement of having enough CPU and RAM).Any thoughts or observations welcome, especially if they are from real world experience in a VM environment. BTW--in case you're wondering why I'm posting here, it's because I run Debian on all my workstations/servers (running VirtualBox as a VM for Windows XP on one workstation).
EDIT: This thread has taken a different turn, please go down to viewtopic.php?f=30&t=64242#p370832 Below is I originally wrote, now totally irrelevant.:D I am delighted/bored with my one Debian Squeeze install, so I've decided to free up a partition to play with another configuration of the universal OS.At the moment I am liking the looks of the supposedly not so unstable Sid; what's the ideal download/install path to get Sid up and running? Is it:1) I already have a live Squeeze GNOME DVD lying around; should I install that again and upgrade to Sid?
I would like to buy a video camera to use for skype video calls. It should be reasonably priced and above all work both under Debian and Ubuntu with minimal effort (ideally a plug and play) and...it would be nice if I could buy it from Amazon .
I have troubles with microphone on skype. It used to work ok and now I don know what i have changed. I can hear myself in earphones is I blow into mic. but if I try to record myself arecord -d 10 test.wav Here is may amixer output:
I can't use the webcam with skype. I followed the instructions on the SDB Skype page of opensuse.org. I can make calls and recieve calls, but there is no video option. Sound isn't going either way during the calls. In Skype's options menu, there is a place to test the video. When I click on the "Test" button, Skype freezes and eventually the terminate application window comes up. The webcam is a Logitech that works fine in Cheese, and I've used it with previous versions of Opensuse and Skype. The only skype available that I've found is the 2.1 beta version, so that's what I'm using. I'm using Opensuse 11.4 with KDE4.
I just installed Squeeze on an older PC. Installation seemed to go fine. But when it booted up on the installed system for the first time, I could not login - username/password failure. I tried every possible typing error and CAP LOCK error I could have made - still nothing.
I brought up a console window and tried logging in as root - same problem.
I booted into single user mode and entered passwd command to set new root password - I got a SYSTEM ERROR message from the passwd command.
I booted to a Live CD, went to /etc/shadow and deleted the encrypted password. Rebooted on the hard drive, went to console window and logged in as root, with no password required. So far so good. I entered passwd command to set new password and got the same SYSTEM ERROR message.
The machine seems fine when running on the Live CD, and the install seemed to go fine.
i have recently installed freeradius in my debian jessie. i want to configure it to act as radius to my home router to authenticate wifi users. i want to use EAP-PWD auth medthod but there is no such section found in eap.conf.does any body know's how to configure EAP-PWD??
I am a ubuntu user but I want to go to the next level to use debian because what I heard of it, but I get confused to what to install on my computer do I install debian testing or debain stable with testing repositories.
- I want to use this system to the home use only. - I want to use the newest packages because the stable packages is too old to use. - What about using more than one repository i.e stable with testing with unstable at the same time (the same sourcelist) - Is the testing and unstable sid packages good enough for the home use?
I've got a task: make time server, that gets time from gps, shows it on display and send to different systems through different ports like com, ltp, etc.
Solution is qt program, included in hybrid iso image.
I've created my binary-hybrid.iso debian, added my program and installed it on pc sudo dd if=/media/cdrom/binary-hybrid.iso of=/dev/sda then i restarted and everything is ok, but...
I also need: 1) to make my pc works as ntp-server, to do this i must change file ntp.conf in ntp****.deb before i build my iso how can i do this?
as i realized according to live.debian.net/manual it's possible to do by putting smth to /live-build/config/packages.chroot and by adding some parameters to lb config but i can't find how and what
2) to save my program parameters after reboot. for example, i have such parameter as gmt. it defined as +3. i can change it while program is running to -5 for example and i want to have gmt -5 when i next time turn on my computer
When in programming it is simple - program creates ini file in it's directory and read/write parameters from this ini-file, but how to make possible to do the same thing when it works from iso?
I am using Debian testing. If I install the gnome-desktop-environment then the sound driver defaults to HDA but since I just installed gnome-core (for a more stripped-down version of gnome) the default is the OSS driver. How do I get ALSA to default to the sound driver HDA?
I saw rsyslog is now installed in Debian Lenny instead of syslog. I want to send local iptables log to remote server. I modified the file config /etc/rsyslog.conf like this :
I have a Debian server that had only one onboard NIC (1000 Gbps) but now I've added two PCI Intel Pro 1000 NIC's into the system to bump up the total # of NIC's to three. My question now is can I specifically assign or force Debian which interface to configure as ethx? I would always like my onboard NIC to be 'eth0' and the two additional NIC's to be 'eth1' and 'eth2'. For some reason Debian loads the modules at random and sometimes what was my
I would like to know which is the default audio system for Squeeze. I'll explain the reason for this question: I had a lenny desktop working like a charm until the hard disk damaged completely. After buying a new desktop computer, I installed Ubuntu 9.10 and I didn't know that the default audio system for Ubuntu was pulseaudio; so I always had problems with skype and my microphone. I remember that with my lenny desktop I never ever had any problem with my sound system and skype.
I've googled for months without finding a consistent fix for this problem in Ubuntu, I've also heard lots and lots of people with the same problem as mine and never solved it; so I decided to get rid of it and install debian Squeeze in my box, but I would like to be sure which is the default audio system for Squeeze, or at least know if anyone have had problems with skype and Squeeze.
Using the howto at http://wiki.debian.org/skype I installed Skype 2.1 beta 2. It launches OK using either skype or linux32 skype and brings up the login screen. It already has my username but when I enter my password skype crashes before logging me in. I get the error: