I use OpenSuse 13.1. There is a bug in pavucontrol with skype, that causes a terrible noise when starting skype.
It is solved by killing skype and starting it with
>> PULSE_LATENCY_MSEC=60 skype
This is great.
Now I don't want to kill/restart skype manually on each boot.
I read that I could add this line to skype.desktop:
Exec=env PULSE_LATENCY_MSEC=60 skype %U
I did this, but still same problem.
Also, I seem to have two skype.desktop files (one in /home/dorien/bin/skype-4.2.0.11/ and one in the 4.2.0.13). I have changed the line in both, but no effect.
Does Opensuse (13.1) not read this when starting? Or is there another way to control the startup option?
The new skype version 3.x supports pulseaudio, so updating to this version makes this hack unnecessary.
Related
I accidentally set the default systemctl target to basic target while trying to switch from multi-user to graphical target on my raspberry Pi 3B which runs the Raspbian OS. Since then when I boot my RPi it does not start and only displays a welcoming screen. I tried to edit the config and cmdline files while in recovery mode to try to access the command line but I could not. Can someone explain to me what the basic target even is because I have been searching online for hours and cannot find a proper explanation? Do I need to format my RPi now or can I access my command line by some way to switch to multi-user target?
Thanks in advance.
The documentation for all systemd so-called special units is available under systemd.special(7) man page (or in the respective online version).
basic.target is an early-boot synchronization point, ordered even before initrd, so the service for login prompts is simply not started, thus there's no command line to work with. This is nicely described and visualized in the bootup(7) man page.
You can temporarily override the default target from the kernel command line using the systemd.unit= argument (systemd(1), section Kernel Command Line).
In your case, adding systemd.unit=multi-user.target to your kernel command line should be enough to allow you to boot back into your rPi and then make the target change permanent by calling systemctl set-default multi-user.target (or graphical.target, as that seems to be the original way you were trying to follow).
Not a VERY big deal, but it's still annoying. Qt Creator shows Not Responding for a few minutes upon startup, then it's OK. What could be the reason? How to fix it? I have cleared my temp files, also have given Qt Creator admin rights. It still does not help. Below is the screenshot:
Tried disabling the welcome screen as per the suggestion. Now the welcome screen does not show up, but I still have the same problem:
The culprit is likely the "welcome" screen.
Go to help - about plugins and disable welcome.
Another source of delays might be due to an internet connection being unable to go through and waiting to time out.
It is normal if the first time Creator is started to take a little longer while scanning for external tools, but after the initial run it should not be a problem.
As the comment noted, it might be the case of a recently introduced issue, in the case you are running the affectd version - 4.6.1.
For those observing instances of the problem with versions 4.8 and upwards running on Windows 10, I can confirm Windows Defender having a role in it.
Disabling the Welcome Plugin does not always solve the problem, as this is also triggered by first-open of the File menù (which populates Recent Files/Projects submenus) or often by simply hitting Ctrl+K.
My solution consisted in adding Qt Creator to the Windows Defender exclusion list.
This is done by navigating Windows Security -> Virus & threat protection -> Virus & threat protection settings -> Exclusions.
Then add a Process exclusion entry using the path to the Qt Creator binary directory, such as C:\Qt\qtcreator-4.9.0\bin\*.
Note the presence of the final \* bit, to whitelist all binaries in that directory.
I have installed Domino Designer in a Windows VM on VirtualBox on OS X.
When I start entering code in the JavaScript editor, Domino starts to work for every letter I type. The hourglass icon appears and the network symbol on the status bar flashes. This operation takes up to several seconds for every letter I type.
If I try to type anything before the hourglass disappears, the keyboard may hang up and the result is a long list of the same letters that I have to delete again (causing the hourglass to appear for each letter I delete again).
I have tried to disable functionality like "Content Assist", "Quick Diff" and other helpful stuff without luck.
I would really appreciate hints or tips to make this nightmare vanish...
I've not used domino designer, but first thought would be that your VM isn't handling the processing required by the designer.
What are the specs on you windows VM? Did you allocate enough RAM, for example? Make sure they match the requirements to run the designer:
http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1351628933716&osPlatform=Windows
Thanks to Joel for leading me into the right path.
I did several things, and together it now seems that I have a much better environment. I still see the hour glass from time to time, but it does not mess up my code anymore, and most of the time it does not bother me.
What I did was the following:
Changed the memory settings for Domino in this file:
[notes dir]\framework\rcp\deploy\jvm.properties
New values:
vmarg.Xmx=-Xmx1024m
vmarg.Xms=-Xms512m
vmarg.Xmca=-Xmca512k
Then I changed the virtual memory of my guest Windows install to a fixed swap file of 4096 MB.
At least I connected my Mac to a faster network using Thunderbolt to Ethernet cable adapter. I don't think the last thing did any difference, but at least I now have a faster and more reliable network connection.
I'm using qtwebsocket from https://github.com/antlafarge/QtWebsocket on QT Creator 5.0, Linux 64bit. I'm trying connect to echo test:
wsSocket->connectToHost( "echo.websocket.org", 80 );
But I immediately get disconnected status. I tried also with ws:// and http:// prefix but same error. Any idea? I even don't know how to report a bug on this gitorious.
It is important to me to don't use webkit, I need pure TCP socket connection.
Regards
There is also a Qt websockets add-on module located at https://qt.gitorious.org/qt/qtwebsockets.
It has been tested on several platforms, and successfully succeeds with the AutoBahn Testsuite.
Just quickly looking at the example located:
https://github.com/antlafarge/QtWebsocket/tree/master/Example
I don't know the state of the project too well, but it looks like there is still a to-do list on what it can do; one item I noticed, it says WSS is not yet supported.
Try running both sides of the Client and Server in the included example, and see if you can get a connection in that context before trying the echo.websocket.org server.
Hope that helps.
I want to place a skype call automatically and I tried different ways:
first I used a api with python which worked for me with an older skype version, after the update it's not working anymore.
then I tried to install a plugin in firefox, set the firefox settings and placed a file in /usr/bin that should call skype number when clicking a skype link. I tried this with calling that skype link with a small script. Not working :(
do you know any other options? I'm using ubuntu 8.10 intrepid
Did you look at the official APIs? There are APIs for COM (not an option on Linux, I guess?) and Java (which you might try).
And there is also an official Skype API for Python. If that's what you used, and it fails with the new Skype version, I suggest you bug the Skype developers about that.