[solved] KDE Desktop themes - not applying fully

Changing the Desktop Theme in KDE has always just applied to Plasma panels for me. But looking around elsewhere it looks like it should be changing icons, window decorations, colours, basically everything. Any idea why it would not be working? There are no errors printed to stdout while it's changing.
Last edited by 12eason (2012-11-07 00:29:30)

Hmm, no they don't. Whole theming system such as it is gives you a lot of choices too, and lots of room for easy personalization. I'm not much of a fan of standard plasma theme, but I like icons and window decoration. So, if everything was so 'integrated', if I understood your point correctly, replacing just one part that I don't like would also require replacing all the others. And that would be unnecessary mess. Choices are good, that's why we like to have them.

Similar Messages

[Solved] KDE Desktop Effects no longer working

Hello,
I just did an update, (I didn't think it was a major one, I don't recall seeing graphics update, though I'm not sure how to confirm - is there a way to see recently updated packages in yaourt?) and after a brief issue with powertop that was solved by a restart (https://bbs.archlinux.org/viewtopic.php?id=179789 - it may be unrelated though) I found that when I restarted, KWin Crashed, and since then, my desktop effects are not working.
I have gone to the KDE Desktop Effects Settings Menu, and under the advanced menu, set the compositing type back to OpenGL 3.1, clicked apply, and confirmed that I wanted to try it even though it had evidently crashed Kwin. I then received a message stating "21 desktop effects could not be loaded". When I clicked details, a popup window said:
"For technical reasons it is not possible to determine all possible error causes.
Desktop effect system is not running."
For the record, I am on a Thinkpad X201 with intel graphics.
Any ideas?
Last edited by TheGuyWithTheFace (2014-04-19 07:35:43)

Some Extra information:
I just tried a restart, that didn't work.
I then went back into effect settings, and saw that "enable effects at startup" was not checked. I also saw that under the advanced settings, Qt Graphics system was set to raster. Since I'm not sure which it was supposed to be on originally, but the current configuration wasn't working, I also set that to Native, and then clicked apply. KWin then crashed, here is the output:
Application: KWin (kwin), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
To enable execution of this file add
add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.19-gdb.py
line to your configuration file "/home/perry/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/perry/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
[Current thread is 1 (Thread 0x7fafaa788800 (LWP 796))]
Thread 4 (Thread 0x7faf8beb3700 (LWP 797)):
#0 0x00007fafa3f7e3f8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007fafa420a034 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2 0x00007fafa41fd745 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fafa4209b7f in ?? () from /usr/lib/libQtCore.so.4
#4 0x00007fafa3f7a0a2 in start_thread () from /usr/lib/libpthread.so.0
#5 0x00007fafa9fa9d1d in clone () from /usr/lib/libc.so.6
Thread 3 (Thread 0x7faf8b27a700 (LWP 798)):
#0 0x00007fafa3f7e3f8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007fafa420a034 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2 0x00007fafa41fd745 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fafa4209b7f in ?? () from /usr/lib/libQtCore.so.4
#4 0x00007fafa3f7a0a2 in start_thread () from /usr/lib/libpthread.so.0
#5 0x00007fafa9fa9d1d in clone () from /usr/lib/libc.so.6
Thread 2 (Thread 0x7faf8a878700 (LWP 799)):
#0 0x00007fafa9fa2fd3 in select () from /usr/lib/libc.so.6
#1 0x00007fafa42e6c13 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007fafa4209b7f in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fafa3f7a0a2 in start_thread () from /usr/lib/libpthread.so.0
#4 0x00007fafa9fa9d1d in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7fafaa788800 (LWP 796)):
[KCrash Handler]
#5 0x00007fafa9ef9389 in raise () from /usr/lib/libc.so.6
#6 0x00007fafa9efa788 in abort () from /usr/lib/libc.so.6
#7 0x00007fafa9ef24a6 in __assert_fail_base () from /usr/lib/libc.so.6
#8 0x00007fafa9ef2552 in __assert_fail () from /usr/lib/libc.so.6
#9 0x00007fafa7d6f8d9 in ?? () from /usr/lib/libX11.so.6
#10 0x00007fafa7d6f96e in ?? () from /usr/lib/libX11.so.6
#11 0x00007fafa7d6fc4d in _XEventsQueued () from /usr/lib/libX11.so.6
#12 0x00007fafa7d72905 in _XGetRequest () from /usr/lib/libX11.so.6
#13 0x00007fafa4dfe587 in ?? () from /usr/lib/libGL.so.1
#14 0x00007fafa4dfbf6b in ?? () from /usr/lib/libGL.so.1
#15 0x00007faf89bef6db in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#16 0x00007faf89befa33 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#17 0x00007faf89befb8b in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#18 0x00007faf89b89ef6 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#19 0x00007fafa4dfd898 in ?? () from /usr/lib/libGL.so.1
#20 0x00007fafa4dd804c in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1
#21 0x00007fafaa34e479 in ?? () from /usr/lib/libkdeinit4_kwin.so
#22 0x00007fafaa350029 in ?? () from /usr/lib/libkdeinit4_kwin.so
#23 0x00007fafaa34aefc in ?? () from /usr/lib/libkdeinit4_kwin.so
#24 0x00007fafaa32f4b5 in ?? () from /usr/lib/libkdeinit4_kwin.so
#25 0x00007fafaa2b6c75 in ?? () from /usr/lib/libkdeinit4_kwin.so
#26 0x00007fafa431d6ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#27 0x00007fafa41fa958 in QFutureWatcherBase::event(QEvent*) () from /usr/lib/libQtCore.so.4
#28 0x00007fafa3491f0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#29 0x00007fafa34984d0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#30 0x00007fafa8bfa88a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#31 0x00007fafa4309a6d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#32 0x00007fafa430caad in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#33 0x00007fafa352f71c in ?? () from /usr/lib/libQtGui.so.4
#34 0x00007fafa43086cf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0x00007fafa43089c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0x00007fafa430dae9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#37 0x00007fafaa2e7896 in kdemain () from /usr/lib/libkdeinit4_kwin.so
#38 0x00007fafa9ee5b05 in __libc_start_main () from /usr/lib/libc.so.6
#39 0x00000000004006fe in _start ()

KDE desktop does not come up after log out

I have updated KDE to the lastest version using the Arch packages. It worked wonderfully the first time, all of my widgits were intact and my desktop was just as I had left it, custom background and everything. Then, however, I logged out to make sure Fluxbox worked. Now, even after rebooting, the KDE desktop doesn't come up. It will bring up Pidgin which was running before but the taskbar and all of the widgets are gone and it has this grey background that is the same as the one in the KDM.
No errors are produced, although it does now ask for the password for a Wallet that "Plasma Desktop" wants to access. I recognise the name of the wallet (kdewallet) and input the password correctly after this, two notifications pop up with informational thing. One is about some indexing service being "rebuilt" for new features and the other is saying that it's falling back on a different sound output. None of this seems to have an impact on the limited usability I have.
Has anyone else expereinced this? Are there any log files where errors would be outputted to?
Any help would be appreciated.
Thanks in advance.

I have found the relevent messages. They are at a pastebin. http://pastebin.ca/1522805
I'm not entirely sure what is going on here.
After the top line of that post, there are a LOT of errors related to "No block with decorrelation terms" in fact the vast majority of that file are those things. All other "errors" are warnings related to my Fluxbox session which is working fine.
Lines 1, 11 and 12 seem to be the most severe errors:
[0xa2412b0] main input error: ES_OUT_RESET_PCR called
"/usr/bin/dolphin(4560)" Error in thread 3049428752 : "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files"
"/usr/bin/dolphin(4560)" Error in thread 3049428752 : "QLocalSocket::connectToServer: Invalid name"
I have no idea where to even begin fixing them. However it is Nepomuk that comes up with the rebuilding message i mentioned in my previous post.
Last edited by guitarMan666 (2009-08-09 10:10:05)

Custom theme not applied

I've created a new Flex library project called Foo, which contains a css file default.css.
I want to apply the .swc as a theme to project Bar.
So I went to Properties -> Flex Theme -> Import Theme.. and imported Foo.swc.
A new theme called Foo showed up. I selected it and clicked OK to recompile Bar.
The css file was not applied ;(
What am I missing?

I've created a new Flex library project called Foo, which contains a css file default.css.
I want to apply the .swc as a theme to project Bar.
So I went to Properties -> Flex Theme -> Import Theme.. and imported Foo.swc.
A new theme called Foo showed up. I selected it and clicked OK to recompile Bar.
The css file was not applied ;(
What am I missing?

Awesome cursor theme not applied at root-window and bar.

I've just started using awesomeWM and it's quite neat. My problem is that my cursor theme doesn't get applied completely. It's all fine in apps, but appears without theme when mouse is over the bar and root window.
My setup info here:
1. I set my xcursor theme with this:
ln -s /usr/share/icons/Flatbed-Green-Regular/ ~/.icons/default
2. I have this in my ~/.xinitrc
xsetroot -cursor_name left_ptr &
and the cursor actually is set to be left pointer instead of an "X".
3. Version
awesome --version
awesome v3.4-rc2-5-g9a9c3d1 (Piku)
• Build: Oct 8 2009 17:56:27 for i686 by gcc version 4.4.1
• D-Bus support: ✔
Also /usr/share/doc/awesome/luadoc/modules/root.html#cursor must be just for this purpose, but I don't know the working syntax... I tried adding this to rc.lua (but with no avail):
cursor = "Flatbed-Green-Regular"
root.cursor(cursor)
Edit: Well, anrxc told me "xcb does not support Xcursor yet", meaning this issue can't really be solve by now.
Last edited by lolilolicon (2009-10-09 14:32:20)

Got it now. xsetroot needs the display if you've got a multihead setup or I guess it just doesn't bother. (Alternately I might just have a weird multihead setup. Nvidia with one rotated screen in TwinView which isn't even supposed to work.)
xsetroot -d :0 -cursor_name left_ptr
xsetroot -d :0.1 -cursor_name left_ptr
That fixed it for me.

[SOLVED] KDE I/O not working

Hello, all.
I have a wonderful little laptop running Arch with openbox. Earlier today, I decided to install Kate. In usage, I tried to save my file, at which point Kate crashed. I then re-opened Kate, and tried to open a file, and Kate crashed.
So, I figured it might be a problem with Openbox, so, I installed KDE, and tried to run it in KDE. Well, it turns out, the plasma desktop won't load. It simply loads a white background, starts my programs in the autostart directory, but no desktop.
Here is a screenshot. I opened Firefox from the terminal (Guake is one of my autostart programs) to demonstrate what happens when I open a window.
When I initially installed Arch (about a month ago), I first installed KDE, because it was the easiest to install. Everything worked fine.
A week or so ago, I had customized openbox to my satisfaction, so I uninstalled KDE. Before I did that, KWrite worked just fine. I tried Kwrite today, and I had the same I/O problems.
The KDE Settings manager also refuses to load properly.
Here is a screenshot of my vain attempt to run the KDE settings manager in Openbox (It has worked before).
I found a post on an openSUSE forum with a similar issue. The solution in question did not solve my problem.
I found nothing searching the ArchWiki or the Arch Forums.
Basically, I am having trouble even isolating the problem, let alone solving it. Any help would be appreciated greatly.
Cheers, Metgz.
If it helps, here is the error traceback from the KDE crash handler:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0db9702780 (LWP 1153))]
Thread 2 (Thread 0x7f0d9eac9700 (LWP 1154)):
#0 0x00007f0db68bc954 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007f0d9f1d77a7 in ?? () from /usr/lib/libQtScript.so.4
#2 0x00007f0d9f1d77d9 in ?? () from /usr/lib/libQtScript.so.4
#3 0x00007f0db68b8e0f in start_thread () from /usr/lib/libpthread.so.0
#4 0x00007f0db905d31d in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7f0db9702780 (LWP 1153)):
[KCrash Handler]
#5 0x00007f0db38ac220 in KFileDialog::KFileDialog(KUrl const&, QString const&, QWidget*, QWidget*) () from /usr/lib/libkio.so.5
#6 0x00007f0db38a8a9b in KEncodingFileDialog::KEncodingFileDialog(QString const&, QString const&, QString const&, QString const&, KFileDialog::OperationMode, QWidget*) () from /usr/lib/libkio.so.5
#7 0x00007f0db38a988a in KEncodingFileDialog::getSaveUrlAndEncoding(QString const&, QString const&, QString const&, QWidget*, QString const&) () from /usr/lib/libkio.so.5
#8 0x00007f0d9f828335 in KateDocument::documentSaveAs() () from /usr/lib/libkatepartinterfaces.so.4
#9 0x00007f0d9f82ad72 in ?? () from /usr/lib/libkatepartinterfaces.so.4
#10 0x00007f0db6f5db8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x00007f0db8497f82 in QAction::triggered(bool) () from /usr/lib/libQtGui.so.4
#12 0x00007f0db8498170 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQtGui.so.4
#13 0x00007f0db88d2463 in ?? () from /usr/lib/libQtGui.so.4
#14 0x00007f0db88d8849 in ?? () from /usr/lib/libQtGui.so.4
#15 0x00007f0db78203a0 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libkdeui.so.5
#16 0x00007f0db84eda49 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x00007f0db88d9afb in QMenu::event(QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x00007f0db849e18c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x00007f0db84a2e6b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#20 0x00007f0db7766df6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#21 0x00007f0db6f486ae in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#22 0x00007f0db849efcb in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/libQtGui.so.4
#23 0x00007f0db851999c in ?? () from /usr/lib/libQtGui.so.4
#24 0x00007f0db8518861 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#25 0x00007f0db853ea22 in ?? () from /usr/lib/libQtGui.so.4
#26 0x00007f0db6602845 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007f0db6602b78 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00007f0db6602c34 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007f0db6f76b66 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00007f0db853e69e in ?? () from /usr/lib/libQtGui.so.4
#31 0x00007f0db6f473ff in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#32 0x00007f0db6f47688 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0x00007f0db6f4c328 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#34 0x00007f0db93244cd in kdemain () from /usr/lib/libkdeinit4_kate.so
#35 0x00007f0db8f98725 in __libc_start_main () from /usr/lib/libc.so.6
#36 0x0000000000400721 in _start ()
Last edited by metgz (2012-12-27 22:37:52)

Lone wolf: I just re-installed all of KDE, but to no avail.
If I am not mistaken, the 's' will prevent needed packages from being removed, and, because it proceeds 'c', will override it.
REMOVE OPTIONS
-c, --cascade
Remove all target packages, as well as all packages that depend on one or more target packages. This operation is recursive, and must be used with care since it
can remove many potentially needed packages.
-n, --nosave
Instructs pacman to ignore file backup designations. Normally, when a file is removed from the system the database is checked to see if the file should be
renamed with a .pacsave extension.
-s, --recursive
Remove each target specified including all of their dependencies, provided that (A) they are not required by other packages; and (B) they were not explicitly
installed by the user. This operation is recursive and analogous to a backwards --sync operation, and helps keep a clean system without orphans. If you want to
omit condition (B), pass this option twice.
-u, --unneeded
Removes targets that are not required by any other packages. This is mostly useful when removing a group without using the -c option, to avoid breaking any
dependencies.
hout orphans. If you want to
omit condition (B), pass this option twice.
Perhaps I should be using -Runs instead.
As for more potentially helpful info: I decided to try out various KDE applications to see if they would work. The links go to screenshots.
Dolphin - No (See a screenshot of Nemo for comparison).
Konsole - Yes
Konqueror No
Kate - No
KWrite - No
Plasma desktop - No
KDE system settings - No

Import - user preset not applied 'fully'

This is update of problem reported in previous entry 'duplicate imports'. Have now tracked the cause of this observation.
The problem dates back to at least Lightroom 3.
I use different import presets for my set of cameras so that the file name reflects the camera.
I also have pairs of presets where the only difference is that a duplicate backup is created or not.
On my PC the default path for backup files has the drive letter of my card reader.
What I notice is that if I select the 'backup' preset then change my mind and select the 'non-backup' preset the flag enabling the creation of a backup copy remains selected. On then proceeding with the import a backup copy is made on the card using the default path.
This is not normally a problem as I then re-format the card in the camera, but it could be a problem if the card is nearly full as the backup copy process will fail due to lack of space on the card.
This became apparent because I initially imported files into my LR3 catalogue and thus unknowingly created duplicates on the card.
Then on importing into my LR4_beta catalogue two copies of each file appeared, the original in the location set by the camera and the duplicate/backup created by LR3. The import dialog does not show paths on cards so it is not apparent that the duplicate files are in different folders.
This looks like a bug in the handling of presets, that some settings, in this case the flag to enable backup file creation, are not updated on selecting the preset.
The pairs of preset names are similar eg c41_backup and c41_nobackup.
For the softies benefit I also note that if I select the 'non backup' preset for a different camera the flag does get cleared, suggesting the bug is something to do with recognising a change of pre-set.
I have not checked but this may be the cause of other mysterious import issues.
Message was edited by: gp7024

Do you have "Apply Auto Tone adjustments" checked in the Preferences>Presets tab? If yes, uncheck it. If not:
Take one image into the Develop module, press and hold the Shift key and the "Reset" button bottom-right will change to "Reset (Adobe)", then click on that button. Does the image reset to the way you expected it? If so, you've (inadvertently) changed the default develop settings, to reset them go to Develop menu>Set Default Settings>click on "Restore Adobe Default Settings".

[SOLVED] [Openbox] Icon-theme not working(?)

Hi!
I hope you guys could help me with the following problem.
Currently I'm running Openbox, compton, tint2, gtk2/3 on my Arch-system.
The problem I'm having right now is that tint2 tray icons are not showing Faenza-Dark but showing gnome(?) dark icons. I would like to have white/grey icons instead of dark ones!
My tint2 config:
# Tint2 config file
# Generated by tintwizard (http://code.google.com/p/tintwizard/)
# For information on manually configuring tint2 see http://code.google.com/p/tint2/wiki/Configure
# Background definitions
# ID 1
rounded = 0
border_width = 0
background_color = #FFFFFF 20
border_color = #FFFFFF 0
# Backgrounds
panel_background_id = 1
taskbar_background_id = 0
task_background_id = 0
task_active_background_id = 1
systray_background_id = 0
clock_background_id = 0
# Panel
panel_monitor = 1
panel_position = bottom center horizontal
panel_size = 0 38
panel_items = LTSC
panel_margin = 0 0
panel_padding = 0 0 5
font_shadow = 0
panel_background_id = 1
wm_menu = 1
panel_dock = 0
panel_layer = top
# Launcher
launcher_icon_theme = Numix
launcher_padding = 10 10 10
launcher_icon_size = 22
launcher_tooltip = 0
launcher_apps_dir = /home/archie/.config/tint2/launchers
# Taskbar
taskbar_mode = single_desktop
taskbar_padding = 0 0 10
# Tasks
urgent_nb_of_blink = 20
task_icon = 1
task_text = 0
task_centered = 1
task_maximum_size = 58 0
task_padding = 10 4
# Systray
systray_padding = 0 10 6
systray_sort = left2right
systray_icon_size = 22
systray_icon_asb = 100 0 0
systray_icon_theme = Faenza-Dark
# Clock
time1_format = %I:%M %p
time1_font = Open Sans 9
time2_format = %D
time2_font = Open Sans 9
clock_font_color = #ffffff 80
clock_padding = 10 0
# Tooltip
tooltip = 0
# Mouse
mouse_middle = close
mouse_right = none
# Autohide
autohide = 0
/home/archie/.config/gtk-3.0/settings.ini:
[Settings]
gtk-theme-name=Greybird
gtk-icon-theme-name=Faenza-Dark
gtk-font-name=Open Sans 9
gtk-cursor-theme-name=Vanilla-DMZ
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=0
gtk-menu-images=0
gtk-enable-event-sounds=1
gtk-enable-input-feedback-sounds=1
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle=hintfull
gtk-xft-rgba=rgb
I'm running tint2-svn and already tried the normal one.
Could some tell me a hint?
Last edited by beta990 (2014-01-13 21:58:18)

Thanks for posts!
I have done all the steps, but real key was to reboot the system! Even pkill X didn't work. It's now solved.
To give users with the same issue a solution:
- Set icon-theme with lxappearance
- Be sure that gtk3.0/settings.ini has fallback and icon-theme the same value (not know if it really needed)
- Reboot! pkill X didn't work for me.
Thanks again.

Windows Theme not applied after changing OS language

Hi,
I have a theme(.theme file) which I have created and applied on my system. However after I change the language from "Control Panel > Region and Language" setting, my theme which was applied goes away. I tried retaining the theme
by Enabling below settings in Group Policy but was of no help.
- Prevent Changing Theme
-Prevent Changing Window Color and Appearance
Does anyone know the solution to this? Any help would be appreciated.
Thanks,
Rommel;

Hi,
For the deny error message, it would be better to use Process Monitor to capture the trace and it would record the deny message when you encounter the error.
Process Monitor:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
If there is any difficult to use Process Monitor,please feel free let me know.
In addition, I'm not suggest you use 3rd theame in Windows 7, it's probably infect system stability with a lot of unknown problem.
Roger Lu
TechNet Community Support

[SOLVED] plasma-desktop could not start

hi!
i have almost two weeks after installing archlinux yesterday i powered off the laptop and when i powered it on but there was no plasma-desktop then i tried plasma-desktop in the consoe and i get this output
[issam@fuhrer ~]$ plasma-desktop
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
any suggestions?
Last edited by fuhrer (2013-07-22 17:07:03)

sorry i forgot to give the solution
i removed/moved the "~/.kde4" directory and every thing returned as usual and if you have some themes/dolphin plugins/ksplash themes ... you can make backup and copy theme to the new "~/.kde4" directory

[Solved] KDE desktop crashed when i close the flash music player

My desktop is kde 4.7.3-1, and the kernel is linux-3.1.4-1.
Just as the Title, those days everytime when I close the flash music player"http://player.mbox.sogou.com/player" in firefox, my desktop crashed, and my desktop panel disapeared for a while. Several seconds later the desktop recovered. I have no idea what caused the problem. Does anyone have the same problem? Or who have idea what have to do with it?
Any idea is helpful! Thank you in advance!
Last edited by speeds (2011-12-10 12:52:53)

Just out of interest, why the old KDE?
You may get more info if you start firefox from the command line and reproduce the crash.

[SOLVED] KDE 4.3 (not kdemod) dont run after login in KDM

Hi! I've not been using kde for a while, but now I decided to install new release (4.3). But I can't start it. I start KDM, press login, it starts loading kde (one icon of hard drive appears) and it falls back to console with this message in /var/log/kdm.log:
X.Org X Server 1.6.3
Release Date: 2009-7-31
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH i686
Current Operating System: Linux axell 2.6.30-ARCH #1 SMP PREEMPT Fri Jul 31 18:10:38 UTC 2009 i686
Build Date: 03 August 2009 08:45:00PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 6 16:34:45 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) intel(0): Non-contiguous GTT entries: (6295552,0x163ffbe000) vs (6291456,0x3fe00000)
(EE) intel(0): Non-contiguous GTT entries: (6299648,0x163fe02000) vs (6295552,0x3ffbe000)
(EE) intel(0): Non-contiguous GTT entries: (6295552,0x163ffbe000) vs (6291456,0x3fe00000)
(EE) intel(0): Non-contiguous GTT entries: (6299648,0x163fe02000) vs (6295552,0x3ffbe000)
(EE) intel(0): Non-contiguous GTT entries: (6295552,0x163ffbe000) vs (6291456,0x3fe00000)
(EE) intel(0): Non-contiguous GTT entries: (6299648,0x163fe02000) vs (6295552,0x3ffbe000)
Setting master
Dropping master
(EE) intel(0): Failed to initialize kernel memory manager
(EE) intel(0): Non-contiguous GTT entries: (6295552,0x163ffbe000) vs (6291456,0x3fe00000)
(EE) intel(0): Non-contiguous GTT entries: (6299648,0x163fe02000) vs (6295552,0x3ffbe000)
(EE) intel(0): Non-contiguous GTT entries: (6295552,0x163ffbe000) vs (6291456,0x3fe00000)
(EE) intel(0): Non-contiguous GTT entries: (6299648,0x163fe02000) vs (6295552,0x3ffbe000)
(EE) intel(0): Non-contiguous GTT entries: (6295552,0x163ffbe000) vs (6291456,0x3fe00000)
(EE) intel(0): Non-contiguous GTT entries: (6299648,0x163fe02000) vs (6295552,0x3ffbe000)
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x813171b]
1: /usr/bin/X(xf86SigHandler+0x9e) [0x80caf0e]
2: [0xb7eed400]
3: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_memory+0x203) [0xb791b9f3]
4: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_framebuffer+0x2b9) [0xb791c109]
5: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_2d_memory+0xeb) [0xb791c42b]
6: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7911565]
7: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7915e8f]
8: /usr/bin/X(AddScreen+0x198) [0x8071788]
9: /usr/bin/X(InitOutput+0x72e) [0x80af88e]
10: /usr/bin/X(main+0x1cb) [0x8071e9b]
11: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7aafa36]
12: /usr/bin/X [0x8071511]
Fatal server error:
Caught signal 11. Server aborting
Kernel, xorg-server, drivers, hal and other related packages are up to date.
Xorg.0.log has the same error messages.
BTW, xfce4 still works and xfce4's composition works fine.
I need some solution I want to try kde 4.3
P.S. I'm running Arch x86 on Benq laptop with integrated intel 945GM video.
Last edited by Axell (2009-08-08 03:20:17)

And my xorg.conf is here (X doesn't start without xorg.conf).
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
# InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "extmod"
Load "dri"
Load "dri2"
Load "dbe"
Load "record"
Load "glx"
Load "synaptics"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
#Section "InputDevice"
# Identifier "Mouse0"
# Driver "synaptics"
# Option "Protocol" "synaptics"
# Option "Device" "/dev/psaux"
# Option "ZAxisMapping" "4 5 6 7"
#EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
Option "DRI" "TRUE" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Option "AccelMethod" "XAA"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Last edited by Axell (2009-08-06 13:48:45)

.Xdefaults Xcursor.theme not applying since last update

I'm using Openbox. Since last system update about 10 days ago this is not working. To be more exact it is loaded, but inmediatelly unloaded and reverts to default cursor theme.
At work, I have Archlinux too, but I haven't updated yet, and this is working perfectly. I could post software versions, but I don't know what programs could be important for this situation.
Thanks in advance.
NeOnsKuLL

Hm, I use xcursor-neutral from the repos and I activate it only via .Xdefaults with this line
Xcursor*theme: Neutral
I name it "Neutral" because the folder is /usr/share/icons/Neutral, so just look, in which folder your theme is in and change it for yours.
That's all, my system is absolutely up to date incl [testing]
Last edited by Army (2009-06-17 16:17:15)

Portal theme not applied to reports

Hi.
I've been creating a Portal theme for users with visual disabilities by customising various aspects of the standard high contrast theme available. The problem I am experiencing is that when I access a backend system report the display of that report in the main screen area does not use the customised theme which I have assigned to myself through the 'Personalize' link. The rest of the Portal display uses my customised theme, but the report uses a standard SAP theme.
I know it must be possible to change the theme which is used to display reports because when I change, for example, from the SAP Tradeshow theme to SAP Chrome I can see that the colour scheme for the report changes. However, I cannot make the report display use any of my custom themes.
Does anybody know how I can force the report display to use my custom theme?

In the transaction iview properties you can set the portal theme. Please verify it is correct.
Do you see the standard portal theme instead? Or is it the reference to the old server?

[SOLVED] Some Xfce themes not displaying correctly

When I try to use certain themes (e.g., anything that requires Murrine), it does not display correctly, instead looking more like the default GTK theme:
http://ompldr.org/vNW04cQ
How do I fix this?
Last edited by woddfellow2 (2010-09-23 01:42:55)

The themes you're having problems with probably use options that the current stable version of the Murrine engine can't handle. Try installing gtk-engine-murrine-git from AUR...I suspect that will fix the problem.

[solved] KDE Desktop themes - not applying fully

Similar Messages

Maybe you are looking for