Tag: fix
Weird Bug Fix for Crashing Owncloud Client on Ubuntu 14.04:Segmentation Fault (core dumped)
Not that most of you are going to ever see this or care, but as for me, I just spent about 6 hours over the last few weeks trying to resolve it so I hope as a public service this will help someone both fix their client and save some time!
Background:
My Ubuntu owncloud client was working just fine on my netbook. Then I made a change to the server where the URL changed where owncloud was hosted. On one machine, I simply booted up owncloud, changed the setting and everything worked. On the other machine, it would not forget the former URL and something went wacky inside. I hope you like my terminology. Anyways, I took the time and courage to just start trying to delete everything from my netbook related to owncloud and reinstall but that didn’t work either. Finally, this is what worked (assuming you have opened a terminal window):
1. sudo apt-get purge owncloud-client
2. sudo apt-get autoremove owncloud-client
3. go to your home folder and totally delete the owncloud folder (make sure you save anything that might be in it and not synced to your server!)
4. KEY STEP
a) cd /tmp
b) ls
You should now see at least one directory that starts with sni-qt_owncloud_3658-HTGzH (or something along those lines). In my case, I had many of them which I thought to be a problem. So, I deleted them all and this was the step that fixed everything. How to delete?
c) rm -rvf sni-qt ….
d) repeat steps ‘b’ and ‘c’ above until all traces of these sni-qt directories are *totally gone*
5. Reinstall owncloud-client
sudo apt-get install owncloud-client
NOTE: It’s probably better, although I didn’t try, to instead open your software centre and install it from here. I found my icon didn’t show up using the command line here in the terminal…. sup to you….
6. start owncloud by just typing ‘owncloud’ or by searching for it the normal way you open programs.
7. go into your ‘settings’ and make sure your server settings are correct.
Everything should now be working
Hope that helped and if you have time and energy please file this blog with the owncloud open source team. I ran out of time….
Sound problem with Qtel (open source Echolink) in Ubuntu 14.04
If you are looking to get set up Echolink on your shiny new Ubuntu 14.04 machine, be sure to read the how to article I wrote before.
However, even after having such a formidable victory and feeling waves of joy when the repeater list finally populated Qtel on my Trusty Tahr, I had a less-than-raring experience of not being able to hear the ECHOTEST server, or any other repeater, sound.
I remember VA7OBI told me that he had success when he opened 5200 TCP but when I tried everything it didn’t work for me. In fact, remind me to publish the way that this frustration led me to fighting my ISP and how I got two months free internet out of the deal…but I digress… After I did a DMZ on my computer it instantly started working so it was definitely a port problem.
Here is what solved my problem *instantly*.
1. Open router or modem/router configuration page
2. Go to your firewall settings.
3. Open (or often called ‘port forwarding’) the following port range:
5198-5199 UDP
4. Make sure this new rule in your router/modem is pointing to the machine (or multiple machines) where Qtel is installed. In my case it was 192.168.1.75 to show an example IP address.
If you don’t know how to find your IP address, it’s very easy in Ubuntu. Just open your terminal (control + alt + t) and type this:
ifconfig
you will see this kind of spew:
eth0 Link encap:Ethernet HWaddr 00:16:76:b4:24:17
inet addr:192.168.1.75 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:76ff:feb4:2417/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11386 errors:0 dropped:0 overruns:0 frame:0
TX packets:10070 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9551513 (9.5 MB) TX bytes:1181280 (1.1 MB)
eth0 is your hardwired connection which mine, obviously is. If your machine is connected by wifi, it will look roughly the same but you will see ‘wlan0’ or something like that which will have your ipaddress beside it like mine above.
Now just make sure those 5198-5199 UDP ports are open and pointing to that machine where qtel is.
Final note: your modem/router may, from time to time, send out new IP addresses to your computer(s). If Qtel stops working one day again, it’s probably just a matter of running this tutorial again and updating your IP address in the port forwarding rule in your router/modem.
If you feel really saucy and snazzy, you could set a static IP address for your machine and never run this tutorial again. I’m too lazy for now so I’ll risk having to do this again, ha.
Take it easy and keep on being Ubuntu
Making Skype and your Mic Submit under the power of Ubuntu 13.10
It’s sad that we’re even using Skype on Ubuntu considering it’s owned by a company with zero interest in open source… but alas, some habits die hard and we don’t want this little program to prevent you from realizing that Ubuntu is, by far, the best thing that will happen to your computer life (and other parts as well – some of my best friends came from the Ubuntu community). Just for the records, though, we should be supporting the build of open source versions of VOIP software, or the inclusion of VOIP features in apps such as Twinkle, Jabber, and the like. At any point MS could pull back their API and you are SOL, PAL.
Everything in my Ubuntu life works very well – except for this non-Ubuntu annoying little foreign habit that I haven’t given up. In particular I’ve been fighting my sound on just one laptop. I’ve tried a myriad of tutorials and this and that, but what I’ve found to be a reliable work around is a simple change in the way I launch everything. Here is what I do and I hope this solution is a nice easy way to fix your sound issues found within Skype in some beta releases of Ubuntu:
- Make sure your headset (or webcam, or whatever external device you are using for your sound) is unplugged.
- Start your computer and make sure everything else is up and running.
- Start Skype.
- Log in. You should hear the usual startup sound. If not, you may have to open your sound settings and mess with the ‘alert volume’. I didn’t find that little trick in any tutorial and it worked for me.
- Plug in your headset or audio device
- Follow this tutorial (the one with the screen shot with the red arrows). For me the solution was to unplug mic from sound card and plug it back in. Might as well. Only takes a second.
- Do a Skype test call. Hopefully everything is working well.
Although I don’t have time to research it, I think the source of my problems (besides the fact that Skype is the culprit in general) is that I have other audio-related software running and they fight for priority over the sound card. Je ne sais pas. All I know is this flow works for me and got me back in action while I try to find a way out of depending on Skype or Google..
Recent Comments