Hi all, Tim.
I wanted to update topic v3.5.13-sru in Etherpad, but I encountered an
unexpected problem. Since line 1873 I see only line numbers, but I do not see
content. Anything below so I can not edit - or read others :) Any ideas? Move
list of changes to the wiki?
Thanks
Slavek
--
All,
I need help to find out why I cannot get the new graphical login to display.
Instead of the o2_enterprise theme, I get the old xdg login. Here is the R14 shot:
http://www.3111skyline.com/dl/dt/trinity/ss/tdm_r14-xdg-screen.jpg
The same think in 3.5.13-sru
http://www.3111skyline.com/dl/dt/trinity/ss/kdm-3513-sru-xdg-old.jpg
The kdmrc & tdmrc are default with 'k' 't' appropriate for each. Here is the
kdmrc:
[X-*-Core]
Setup=/opt/trinity/share/config/kdm/Xsetup
Startup=/opt/trinity/share/config/kdm/Xstartup
Reset=/opt/trinity/share/config/kdm/Xreset
Session=/opt/trinity/share/config/kdm/Xsession
AllowRootLogin=false
AllowNullPasswd=false
AllowShutdown=Root
ClientLogFile=.xsession-errors-%s
[X-*-Greeter]
LogoArea=Logo
LogoPixmap=/opt/trinity/share/apps/kdm/pics/kdelogo.png
AntiAliasing=true
MinShowUID=500
MaxShowUID=65000
UseTheme=true
Theme=/opt/trinity/share/apps/kdm/themes/o2_enterprise
[X-:*-Core]
ServerCmd=/usr/bin/X -br
ServerArgsLocal=-nolisten tcp
AllowNullPasswd=true
AllowShutdown=All
[X-:*-Greeter]
PreselectUser=Previous
FocusPasswd=true
LoginMode=DefaultLocal
AllowClose=true
[X-:0-Core]
ClientLogFile=.xsession-errors
[X-:0-Greeter]
On tdm/kdm start, you can see a momentary message flash in the center of the
black screen before the old xdg login dialog appears, but I can't find where
that message is logged and it just appears for a fraction of a second.
At any rate, I need help figuring out why the o2_enterprise chooser is falling
back to the old dialog. One clue is that both the login dialog and logout dialog
are 'regular windows' (with window decorations, etc.) instead of pixmaps. I
don't know why, but I suspect solving the greeter issue will solve the other...
Is anyone else experiencing this problem with their latest builds? It could
always be an arch upstream change issue, but I can't figure out how to tell
exactly what is failing to tell. Thoughts? Wisdom?
--
David C. Rankin, J.D.,P.E.
Tim,
Looking at the graphical tdm greeter issue, I have the same SAK error on R14
that I see in 3513-sru. In .xsession-errors, I get:
[kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check
tdmtsak for proper functionality.
I looked at the code in tdebase/kdesktop/lockeng.cc and the correct tdmtsak
and kdmtsak executables are being called in R14/3513, so I can't explain this
error with tdmrc UseSAK=true??
--
David C. Rankin, J.D.,P.E.
Building TDE against CUPS 1.4.5 (Slackware 13.1). As of today I now receive the following build failures:
/dev/shm/tdelibs/tdeprint/cups/kmcupsjobmanager.cpp:300: error: 'class IppRequest' has no member named 'last'
/dev/shm/tdelibs/tdeprint/cups/kmcupsmanager.cpp:571: error: 'class IppRequest' has no member named 'last'
/dev/shm/tdelibs/tdeprint/cups/kmcupsmanager.cpp:902: error: 'class IppRequest' has no member named 'last'
Reversing commit 9bc0d2cd resolves the failure, but I presume the patch should be tweaked to support CUPS < 1.6.
Darrell
Slavek,
I don't know what name change did this, but kdesktop tries to load 'tdmtsak'.
It should be loading 'kdmtsak'. Here is the error generated in .xsession-errors:
[kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check
tdmtsak for proper functionality.
I checked and the kdmtsak binary is there:
18:52 tdesru:~> l /opt/trinity/bin/*sak*
-rws--x--x 1 root root 28209 Aug 12 01:21 /opt/trinity/bin/kdmtsak
-rwxr-xr-x 1 root root 24113 Aug 12 01:46 /opt/trinity/bin/tsak
--
David C. Rankin, J.D.,P.E.
Tim, All,
Since grub is dead upstream and movement is toward grub2, how will this be
supported in tdm? Currently Grub and Lilo are the only boot managers supported.
Has anybody looked to see what is needed to add Grub2 support?
This will affect the shutdown dialog options to restart "Select bootloader".
It looks like the main differences will be to parse /boot/grub/grub.cfg instead
of /boot/grub/menu.lst. In grub, the menu.lst file was formatted like:
# comment
title
root
kernel
initrd
savedefault
# comment for chainload
title
rootnorverify
makeactive
chainloader
savedefault
Under grub2 grub.cfg, you have something like:
### comment ###
menuentry 'New Title' --class arch --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-core repo
kernel-true-a625b429-6143-459c-a57c-6c5bba56d715' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5
a625b429-6143-459c-a57c-6c5bba56d715
else
search --no-floppy --fs-uuid --set=root
a625b429-6143-459c-a57c-6c5bba56d715
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux
root=UUID=a625b429-6143-459c-a57c-6c5bba56d715 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
}
So for grub2 it looks like you will parse for 'menuentry' 'set root' in order
to pass that information to grub2 for restart. Anybody looked into this yet? Do
we want to open a feature request on it?
(for those not using grub2 yet -- just wait :)
--
David C. Rankin, J.D.,P.E.
Many sound files are named with a KDE_* prefix. Everything works as is and there is no requirement to rename the files. Yet in the spirit of renaming for branding purposes, should we rename those files to TDE_*?
There are two packages that contain the files: tdebase and tdeartwork. Renaming and updating the respective make files is straightforward, as is updating 11 default eventsrc config files in other packages in the source tree.
A remaining challenge is updating existing user profile eventsrc config files to use the renamed files because existing eventsrc config files will be referencing sound files with the KDE_* prefix, which no longer would exist.
Currently we have no mechanism to update profile eventsrc files. We can write a new shell script to perform the updates. The new script would be called by the migratekde3 and called once from within starttde, like the r14-xdg-update script. Or embed the updates in the migratekde3 and r14-xdg-update scripts.
The renaming would be R14 only and not expected to be backwards compatible with 3.5.13 sru.
Comments?
Darrell
Tim, Slavek,
After receiving a error message that knotify crashed (see:
http://www.3111skyline.com/dl/dt/trinity/ss/3513-knotifyCrash-disable-aRts.…),
I begin checking the .xsession-errors file. The are a number of errors 'Could
not load library! Trying exec....' This may be normal, but I want to confirm
whether there is a problem here or not. I have included the part for my
.xsession-errors file that contains the error messages:
[startkde] kdeinit started successfully.
kdeinit: Got KWRAPPER 'ksmserver' from socket.
kdeinit: PID 821 terminated.
kdeinit: Got SETENV
'SESSION_MANAGER=local/tdesru:@/tmp/.ICE-unix/822,unix/tdesru:/tmp/.ICE-unix/822,inet6/tdesru:44438,inet/tdesru:51121'
from klauncher.
kdeinit: Got EXEC_NEW 'kwin' from launcher.
kdeinit: Got EXT_EXEC 'knotify' from launcher.
kdeinit: Got EXEC_NEW '/opt/trinity/bin/kdesktop' from launcher.
Could not load library! Trying exec....
kdeinit: PID 825 terminated.
kdeinit: PID 828 terminated.
kdeinit: Got EXEC_NEW 'kicker' from launcher.
[kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check
tdmtsak for proper functionality.
kdeinit: Got EXEC_NEW 'kio_file' from launcher.
kdeinit: Got EXEC_NEW 'kio_file' from launcher.
kdeinit: PID 832 terminated.
kdeinit: Got SETENV 'XCURSOR_THEME=default' from klauncher.
kdeinit: Got SETENV
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/david/.gtkrc:/home/david/.trinity/share/config/gtkrc'
from klauncher.
kdeinit: Got SETENV
'GTK2_RC_FILES=/home/david/.gtkrc-2.0-kde-kde4:/home/david/.trinity/share/config/gtkrc-2.0'
from klauncher.
kdeinit: Got EXEC_NEW 'nspluginscan' from launcher.
Could not load library! Trying exec....
kdeinit: Got EXEC_NEW 'artswrapper' from launcher.
Could not load library! Trying exec....
kdeinit: Got EXEC_NEW 'kaccess' from launcher.
kdeinit: Got EXEC_NEW 'kmixctrl' from launcher.
kdeinit: Got EXEC_NEW 'krandrtray' from launcher.
Could not load library! Trying exec....
kdeinit: PID 840 terminated.
kdeinit: Got EXEC_NEW 'basket' from launcher.
Could not load library! Trying exec....
kdeinit: PID 838 terminated.
kdeinit: Got EXT_EXEC 'kbuildsycoca' from launcher.
kbuildsycoca running...
Reusing existing ksycoca
kdeinit: PID 841 terminated.
kdeinit: Got EXEC_NEW 'kmix' from launcher.
kdeinit: Got EXEC_NEW 'ktip' from launcher.
Could not load library! Trying exec....
kdeinit: PID 843 terminated.
kdeinit: Got EXEC_NEW '/usr/bin/VBoxClient-all' from launcher.
Could not load library! Trying exec....
kdeinit: Got EXEC_NEW 'klipper' from launcher.
kdeinit: Got EXEC_NEW 'kpowersave' from launcher.
kdeinit: Got EXEC_NEW 'korgac' from launcher.
Could not load library! Trying exec....
kdeinit: Got EXEC_NEW 'krandrtray' from launcher.
Could not load library! Trying exec....
kdeinit: PID 867 terminated.
kdeinit: PID 846 terminated.
kdeinit: PID 853 terminated.
kdeinit: PID 850 terminated.
kdeinit: PID 854 terminated.
kdeinit: PID 848 terminated.
kdeinit: PID 864 terminated.
kdeinit: PID 859 terminated.
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0xc00006
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0xc00006
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0xc00006
kdeinit: PID 845 terminated.
kdeinit: Got EXT_EXEC 'ksnapshot' from launcher.
Could not load library! Trying exec....
<snip>
In response to the knotify crash dialog, choosing "Try again" restores knotify
operation and I can play sound events fine. However, I need to figure out which
library can't be loaded. How do I do this? I can annotate startkde, but what do
I do for kdeinit? Is this logged somewhere? If so, where. There may be a couple
of lingering 't' 'k' issues that need fixing somewhere. Any help appreciated.
Also, if there is some way to turn up logging in tde, let me know. I recall
that there is a way to turn up what goes in xsession-errors, but I'm drawing
blanks this morning :)
--
David C. Rankin, J.D.,P.E.
All,
Looking into why the tdm display manager themes are not displaying, I needed
to open many files as root. It would be really helpful to have a context menu
item for files that is something like "Open As: " or "Edit as: " where you can
choose the user to open the file under. This just saves having to type tdesu
filename on the cli. Is there already something like that that can be included
in tde?
--
David C. Rankin, J.D.,P.E.
Tim, Slavek, Francios,
One conflict with kde4 and 3.5.13-sru is the install of .menu files in
/etc/xdg/menus (I think by tdebase). I have two ideas. Either are OK if they
will work:
(1) cherry-pick the commit that changes the names of the menu files from
kde-xxx.menu to tde-xxx.menu for sru. E.g.:
etc/xdg/menus/tde-information.menu
etc/xdg/menus/tde-screensavers.menu
etc/xdg/menus/tde-settings.menu
etc/xdg/menus/applications-merged/tde-essential.menu
The problem here is I don't know how much else in the code has to be changed
along with this. OR
(2) Install all kde-xxx.menu files to $TDEDIR/etc/xdg. I don't know if this will
work, but my installs already put the following files in /opt/trinity/etc
opt/trinity/etc/xdg/menus/applications.menu
opt/trinity/etc/xdg/menus/applications.menu-no-kde
If putting kde-information.menu,kde-screensavers.menu,kde-settings.menu, and
tde-essential.menu in /opt/trinity/etc/xdg will work, I think we can just make a
change in tdebase TDESetupPaths.cmake. It looks to me like tdelibs/kded installs
the applications menu in /opt/trinity/etc while tdebase installs the rest of the
menus in /etc.
If we can do either (1) or (2), that will eliminate an install confict with
kde 4.9. What say the experts? Can we do something like this?
--
David C. Rankin, J.D.,P.E.