Venkatesh's questions

I am using Ubuntu GNOME 14.04. I integrated my Google account with it. But every time I login GNOME asks for my google account password. But when I give it, it simply wont accept it! I am 100% sure I am typing the right password for my google account(It doesn't have 2 step verification at present. I was using it before but not now.) Since it didn't work I tried my login password but that too didn't work. Then I removed integration for that account from "Online Accounts" then removed all my cache and tried integrating again. It integrates, but again, if I type in my password when asked for, the same issue persists. Here is a screen shot:

(asking for password:)

(after right password is given:)

I tried following this answer partly(I deleted goa-1.0 but not evolution since it would delete my evolution configuration which I want!) But deleting goa-1.0 didn't let me integrate my google account at all and so it doesn't work!(I recreated goa-1.0 and now I can reintegrate my account but the password issue persists).

So now my question is: How do I integrate my google account with my Ubuntu GNOME without any such issues as explained above?

PS:- Should I be doing something with seahorse here? I dunno how it works and all and so if I have to use it, tell me what to do elaborately.

I just started using Ubuntu GNOME 14.04 LTS. From the 'Help' application I see that there ought to be certain icons if I am using a wired connection on my GNOME top bar as shown below:

But there isn't any! I see only a couple of icons on my top bar as shown below:

So how to get those icons on my top bar? I can't right click on the top bar too! I am not able to know if I am connected to the internet without this. I ought to enter my browser and search for google or something to know if I am connected. So need help here!

PS:- BTW I see that there aren't many icons on my top bar. Is this normal? Am I missing any other default icons? If yes can you tell how to get those? BTW I have libappindicator 1 and libappindicator 3-1 installed. So, that shouldn't be a problem. Also I tried this but it didn't work. Let me also add that I changed to a different icon theme too but that also didn't help(presently using numix-circle theme). The default tweak tool also doesn't seem to have any options to solve this issue of mine.

I am using Ubuntu 14.04(with Unity). Just today(as of the date of this post) I did a sudo apt-get update && sudo apt-get upgrade and at the end of the 'Upgrade' process I got the following error :-

Setting up crossplatformui (1.0.38) ...
 * Stopping ACPI services...                                             [ OK ] 
 * Starting ACPI services...                                             [ OK ] 
package libqtgui4 exist
QT_VERSION = 4
make -C /lib/modules/3.13.0-27-generic/build M=/usr/local/bin/ztemtApp/zteusbserial/below2.6.27 modules
make[1]: Entering directory `/usr/src/linux-headers-3.13.0-27-generic'
  CC [M]  /usr/local/bin/ztemtApp/zteusbserial/below2.6.27/usb-serial.o
/usr/local/bin/ztemtApp/zteusbserial/below2.6.27/usb-serial.c:34:28: fatal error: linux/smp_lock.h: No such file or directory
 #include <linux/smp_lock.h>
                            ^
compilation terminated.
make[2]: *** [/usr/local/bin/ztemtApp/zteusbserial/below2.6.27/usb-serial.o] Error 1
make[1]: *** [_module_/usr/local/bin/ztemtApp/zteusbserial/below2.6.27] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-27-generic'
make: *** [modules] Error 2
dpkg: error processing package crossplatformui (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 crossplatformui
E: Sub-process /usr/bin/dpkg returned an error code (1)

From then on whatever apt-get command I use(so far as I know, except apt-get update) I keep getting the above error at the end of the process. But whichever apt-get command I use does what it has to without fail.(For example I tried installing blender with sudo apt-get install blender and it installed fine though it showed the above error.) After this I even got a kernel update(from 3.13.0-27 to 3.13.0-29 via the Software Updater), but even now the issue persists. How do I solve this issue?

In Ubuntu tweak 0.8.7 which is installed in my Ubuntu 14.04 LTS running unity I could not delete a particular file called 'fail' in the thumbnail cache. I am actually trying to remove that file with the 'Janitor' feature that is available with Ubuntu tweak. Every time I try deleting that file Ubuntu tweak crashes(i.e. closes). Why does this happen and how to delete it? By the way I could delete every other thumbnail cache file and also other kind of cache except this 'fail' file. Below is a screen shot:-

I am using Ubuntu 14.04 LTS with Unity. Since Ubuntu One is no more I am using Copy . But I can't see the copy icon in the notification area of the Panel. I am sure that copy is running in the background because the System Monitor app says so. I have libappindicator1 and libappindicator3-1. installed. Yet I don't see the icon.

Lets say I have three image files to edit. Consider all the files are in ~/Pictures. Let name of the first file be 1.svg, name of the second file be 2.svg and name of the third file be 3.svg .I have Inkscape editor. Now, I want a bash script to be executed so that the following must happen:

1. First 1.svg must open for me to edit.
2. After editing, when I close that file, automatically 2.svg must open for me to edit.
3. Now when I complete editing 2.svg, I want 3.svg to open for editing.
4. Now after editing 3.svg the script must end by closing GIMP.

PS:- If you are wondering if this is home work, it is not! See here . You will notice that I have to edit images there. To make that answer better I need help here. So please help. Also I AM A COMPLETE BEGINNER. I don't know anything about bash. So explain your answer as elaborately as possible. Also you might consider giving an answer with GIMP editor to edit .jpg files . It might be useful for others. By the way, I am using 14.04 LTS . Thanks in advance.

UPDATE :- The above linked answer was edited according to the accepted answer below.

I just downloaded Numix circle icon theme. I applied that theme from Unity tweak tool. Now my launcher and Nautilus has the theme I applied but Cairo dock doesn't. Why is it so and how to change my dock to get that theme?

PS :- I am using Ubuntu 14.04 with Unity. I have also made some edits in my launcher as suggested in the answers here.

First let me show my launcher :-

I feel my launcher is made to look ugly by the 'square-tile-thing'(for the lack of a better word) thats behind the icon. I want the icons alone to be viewed(without the tile behind). So are there any ways to remove the 'square-tile-thing' ?

PS:- I am using Ubuntu 14.04 LTS with unity. By 'square-tile-thing' I mean the square that is around each icon. (See the picture above or see your own launcher!)

First let me show a screenshot of my Panel notification area.

I just want to remove the En icon from there. How do I do it? I am using Ubuntu 14.04 with Unity.

First of all, my desktop environment is unity. I am using it with 14.04 OS(with all recent updates). I recently installed infinity conky. I installed and followed all the instructions correctly in the readme file provided with the conky. But my conky appears distorted, like this(the background image is my own wallpaper):

As you would have seen there are boxes after the fonts. The fonts seem to overlap from the last status rather than replacing it(for example you can see the time). Also if you look above the analog clock you will see a half visible icon. This means I also have a transparency issue. Also when i run the conky in the terminal I see output as "Unknown varaiable". That output keeps on printing as you can see below:

I attempted configuring the conky with help from the chat room yesterday. This is what I tried:

• Changed the font to "Ubuntu"
• Disabled anti-aliasing

Both did not work. Here is .conkyrc file (it is without any edits).

PS: I tried downloading conky manager from here But it is not available for 14.04. Note that I have conky, conkyall, curl installed. Also is this just a problem with unity itself? Don't unity and conky don't go well with each other? Or is it because I am using a developer version OS that I am being confronted with this problem?

Update :- I noticed something recently. The conky doesn't appear distorted when I start it from terminal. But the moment I minimize or close the terminal, or move to another workspace the conky gets distorted as mentioned above. I thought it was running from the terminal that caused the problem and so added the script to startup applications and rebooted. Now the conky appeared without distortion but only until I opened a new window or moved to another workspace. Thus the problem seems to me to be due to unity. But is it really? If it is so, it is because of which particular aspect of unity and which file should I add when I submit a bug report about this?

I wanted to change my desktop screen resolution to 1366x768. But my VESA drivers(AMD REDWOOD) did not detect that resolution. So I created a shell script as follows:-

xrandr --newmode "1368x768_60.00"   85.25  1368 1440 1576 1784  768 771 781 798 -hsync +vsync  
xrandr --addmode DVI-0 1368x768_60.00  
xrandr --output DisplayPort-0 --off --output DVI-0 --mode 1368x768_60.00 --pos 0x0 --rotate normal --output HDMI-0 --off

I saved it as lightdmxrandr.sh in /usr/bin and made it executable. Then I added the following lines to /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf(which is the equivalent of the well known /etc/lightdm/lightdm.conf . I am using the above file as I am on 14.04 where there is no /etc/lightdm/lightdm.conf .) :-

greeter-session=unity-greeter  
display-setup-script=/usr/bin/lightdmxrandr.sh  
session-setup-script=/usr/bin/lightdmxrandr.sh

and saved it. In theory this should have changed both the login screen resolution and desktop screen resolution to 1366x768 . But surprisingly this changed only the login screen resolution. The desktop resolution was not changed. Later I added the script to Startup applications and that changed my desktop resolution.

So I want to know why the edits I made to lightdm.conf file(or rather the 50-ubuntu.conf file) did not affect my desktop resolution. Is this some kind of bug that has to be reported at launchpad or is it wrong to say that edits in lightdm will affect desktop screen?

PS:- In my opinion this is not just specific to Ubuntu 14.04.

I want my system to run with 1366x768 resolution. Note that this resolution is not detected by the open source driver. So I created a bash script as follows :-

xrandr --newmode "1368x768_60.00" 85.25 1368 1440 1576 1784 768 771 781 798 -hsync +vsync xrandr --addmode DVI-0 1368x768_60.00
xrandr --output DisplayPort-0 --off --output DVI-0 --mode 1368x768_60.00 --pos 0x0 --rotate normal --output HDMI-0 --off

and saved it as lightdmxrandr.sh in /usr/bin and also made it executable. In /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf , I added these lines:-

greeter-session=unity-greeter
display-setup-script=/usr/bin/lightdmxrandr.sh
session-setup-script=/usr/bin/lightdmxrandr.sh

Now I saved the file and rebooted my PC. My login screen had 1366x768 resolution. So I happily typed in my password and pressed return. But when my desktop starts I dont have 1366x768 resloution! I tried running the script above at runlevel. That didnt work. Infact even the login screen's resolution did'nt change! So I need to know what must be done to make that script run just before the desktop session begins. Thanks in advance.

PS:- I have an ATI radeon 5570 HD graphic card. I am using the AMD REDWOOD open source drivers. I know that I can get the 1368x768 resolution with a AMD proprietary driver from the AMD website. But I prefer to use the Open source drivers. If you have patience, read this question too. The above question was born out of problems arose by that question. Also note that I am using Ubuntu 14.04 but this question is not too '14.04 specific'.

I am using Ubuntu 14.04. I have an AMD Radeon 5570 HD graphic card. Actually, the default open source REDWOOD drivers aren't allowing me to choose my monitor's maximum screen resolution(which is 1366 x 768). I just have two resolutions displayed which are 1024x768 and 800x600 . If I give the command :

xrandr -s 1366x768

then the output is:

Size 1366x768 not found in available modes

So just for the sake of getting 1366x768 resolution I am forced to install the proprietary graphic driver that AMD gives me from its site. But if I install it(which itself is quite a problem-prone process), I undergo a lot of 'inconvenience'. Sometimes after an OS update, the driver crashes unity. Then I will have to uninstall that driver from a tty and google around for a solution. Also I encounter screen tearing problems occasionally. In addition I also cant see my login screen(See this question which states this particular problem). The main problem is AMD does not update its driver as quick as Ubuntu updates its OS. This is quite irritating.

So, I want the maximum resolution(and performance) that my graphics card and monitor can give me without installing the 'problematic' proprietary graphic card driver that AMD gives. Is this possible? Suggestions please. Thanks in advance.

PS :- More system specs details:-

• Intel i3 2100 processor
• AMD P8H61-M PLUS2 motherboard
• AMD Radeon 5570 HD graphic card
• DELL monitor

(BTW, Thank you for reading through my elaborate description!)

I installed the latest AMD BETA driver from this site . The installation was perfect. But now I am not able to see my login screen(where you type your password, as you know). My monitor displays "OUT OF RANGE" when I am on my login screen . But I can type in my password and enter into my Desktop without any problem. Probably the login screen resolution is beyond the resolution of my monitor. If that is the case, then how can I change the resolution of the login screen alone? (BTW, my graphic card is ATI Radeon 5570 HD. I have DELL monitor with maximum resolution of 1366x768. Also I can view my desktop without problems.)

PS:- This question is very much similar to this question. But none of the solutions solve the problem in 14.04 which I am using. Note that the problem stated above was also present in Ubuntu 13.10.