Ubuntu :: How To Make KDE Programs Not Look Horrible
Nov 15, 2010
Right now, KDE programs look like really bad. This is not a reduced color depth image, this is what I'm getting, with strange black lines around the buttons. I have only installed that particular KDE application, I have not installed KDE itself.
So I've just recently started using awesome, but I was wondering why things look like this and how I can fix it
Just wondering why it's so 'un-decorated' I guess, I assume I'm just not running something I should be at startup, it happens on all programs and windows. http://i51.tinypic.com/afac5c.png
It's looks like windows 98
Here's another screenshot of it http://i54.tinypic.com/349ary9.png
Just all the borders, menus and stuff look horrible.
having some massive sound quality issues... my sound sounds so incredibly horrible.. it sounds like my speakers are blown out, all crackly and ******. at a loss because i do have sound, it just sounds horrible.
Recently switched from windows XP on Debian. Very happy) After reading smth my eyes are really tired, fonts are smoothed or smth like that But! Do not like the font settings, there is no definition that is in the windows. Very tired eyes, advise how to configure?KDE stands Smoothing, that is just not done
Would like to make an installation with a number of programs. I would like to take a snapshot ( backup ) of my installation and being able to restore that later.
How can I take a snapshot, is it possible to 'save' everything to an ISO and burn to a CD ?
Like under Windows, there is a shortcut for minimizing all windows: Win+D. However under Gnome this does not work similar as under Windows. Under Windows I can just press Win+D and everything will get minimized. However under Gnome this does not work for fullscreen programs.
I have to close a fullscreen application and start it again if I just want to switch to another program like for example from a game to my browser. I don't want to close it but only minimize it.
This is my 2nd attempt at installing Debian since 5.0 several months back but I am determined to get it running this time.Install of 64bit Squeeze went well, installed the ati proprietary drivers directly from ati which resulted in horrrible performance.Uninstalled that and followed to the T. At the "aticonfig --initial" part I got the message "No supported devices detected" soI went ahead and entered the config manually. Now on normal boot I get a black screen and I can't seem to boot into Recovery mode as it hangs at Tray or ANSI.
you can see below my taskbar Imageshack - snapshot1dj.png I would like to make the different programs running and shown at taskabar firefox,Fslint, Thunderbird to have some borders around them,
I am curious of how to make a GUI interface that uses multiple programs and commands. I have found wxwidgets as the most likely candidate for making my own interface.Is this the best programming language for a beginner?
Normally when a program is open an entry is placed on the taskbar in order to easily find it, which is useful when a lot of programs are open. In Ubuntu 10.04, when I moved a program to the other monitor (I'm using 2 monitors) the taskbar entry also moves to the taskbar on that monitor.
Now I switched over to Ultimate Edition, which is Ubuntu 10.04 with a lot of stuff added to it. When I drag a program to the other monitor, the entry in the taskbar disappears, but it does not reappear in the taskbar of the other monitor. So now the only way for me to find a program on this monitor if its hidden behind other windows is to use alt-tab.
Actually I had a folder called Lib, in which I had a few libraries installed and configured.(MPI, PETSc, SLEPc) I accidently deleted (by rm) the contents of that folder.
Then I reinstalled MPI,PETSC,SLEPC using the same tarballs as earlier(thus, the version etc. is the same).
I already had a fortran program with many modules and subroutine files, and the corresponding makefile which used to compile and run fine. But now when I type "make" in the same directory as before, I get this: (shortened, many similar errors)
Code:
Firstly, why is mpif90 compiling my program when I didnt tell it to? In my makefile, I have specified gfortran as my compiler....nowhere have I even mentioned mpif90. Such a thing never used to occur before.
Also, if I rename file_variable.f to file_variable.f90, these errors dissappear (I understand why, but that is not the problem), but a new error comes:
Why is the new MPI installation interfering with make ? I want to go back to how things were before I stupidly broke all installations. The errors themselves are not the problem, the problem is why the new mpi installation is interfering with make.
It seems as if mpif90 has taken over make and gfortran. I suppose I didnt install it correctly, or probably I didnt uninstall the earlier one correctly.
Everything that worked earlier doesnt work suddenly. I use ubuntu 11.04 MPICH2-1.3.2
I notice that when you try to Make link to any file or folder form context menu, It just copy the same file size? even when i tried to copy the link to external storage disk..
I am following the instructions on Section 8.1.* Device Driver ConceptsHere I was able to proceed till section 8.1.4.After making the hello.c file,the make file and patching the Kconfig as mentioned,I tried to run the $ make ARCH=ARM CROSS_COMPILE=xscale_be- gconfig This gave error as:make: *** No rule to make target `gconfig'. Stop.I am not sure if my kernel is correctly compliled,but I was able to complie and build the kernel for arm before by cloning the kernel and building from the following link without any error. https://omapzoom.org/gf/project/omap...ux+OMAP+Kernel
I just installed Gnome Shell in Ubuntu 11.04 through UGR Linux and everything works fine! The only problem is that I cannot run make and make install. I get the following errors:
Code: alexandros@Autobot:~/gnome-shell/source/gnome-shell-extensions$ make && make install Making all in extensions make[1]: Entering directory `/home/alexandros/gnome-shell/source/gnome-shell-extensions/extensions'[code]........
he clicks on everything on his GNOME desktop, and manages to delete everything, including menus, icons, etc. The people he lives with aren't skilled enough to fix it, and I live a good eight hours away. I have remote capabilities with NX, but that requires them to initiate a connection to my workstation here, which is more painful than I thought it would be. I need a way of locking down the desktop, so it's read-only, so he can't make the changes he seems to keep making. I figure I could make the .gnome directory read-only, but I don't know if that would affect the normal operation.
I need to modify fs/open.c and fs/read_write.c to make my modifications. I cannot find any options in 'make menuconfig' to make these files modules rather than compiled elements. I'm thinking these cannot be modules because the file system won't work without open.c and read_write.c. Is this correct - I cannot compile fs/open.c and fs/read_write.c as modules, only as compiled elements? Or, is there some way for a module to overwrite these routines when the module is installed and re-enable the routines when the module is removed?
I want to gave much details as possible. working directory (~/a1/shell) in the shell directory i have Makefile. also in the shell directory i have subdirectory's (obj, src, include)
My current Makefile
Quote:
#What needs to be built to make all files and dependencies
clean:
# End of Makefile
I wanted it so: all .o files are created in the obj subdirectory, and my application, sshell, is created in the shell directory.
I am getting this error when i run the make run: No rule to make target 'shell.h', needed by 'shutil.o'. stop
These kernel sources are usually the sources from debian, with a couple of more patches that I add. It appears that for nvidia-driver package versions higher than 352.79-1, the kernel headers/sources need to be prepared with 'make prepare' and 'make prepare scripts'. It's that simple. I concluded this after the nvidia dkms build failed on my custom kernel, but then succeeded after I pointed it to the full sources, but only after running 'make prepare' and 'make prepare scripts' on them. The problem is that this make-kpkg scheme doesn't appear to do this, or if it does, it doesn't properly include in the headers everything that it should.