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?
On 08/12/2012 05:50 PM, David C. Rankin wrote: <snip>
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?
I think I have found the flashed message that appears before the default greeter appears. It looks like it is related to the new Xorg. Here is my kdm.log for today. The Corrupt data! messages look promising. What is putting those messages there?:
Aug 12 11:31:08 kdm_config[688] info: Cannot open master configuration file /opt/trinity/share/config/kdm/kdmdistrc
X.Org X Server 1.12.3 Release Date: 2012-07-09 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.4.4-3-ARCH i686 Current Operating System: Linux tdesru 3.4.7-1-ARCH #1 SMP PREEMPT Sun Jul 29 20:05:01 UTC 2012 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=a625b429-6143-459c-a57c-6c5bba56d715 ro quiet Build Date: 09 July 2012 04:03:16PM
Current version of pixman: 0.26.2 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: Sun Aug 12 11:31:09 2012 (==) Using config directory: "/etc/X11/xorg.conf.d" /usr/bin/iceauth: creating new authority file /tmp/1229229438/.ICEauthority QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QDialog) Negative sizes (-1,-1) are not possible 11 XSELINUXs still allocated at reset SCREEN: 0 objects of 144 bytes = 0 total bytes 0 private allocs COLORMAP: 0 objects of 4 bytes = 0 total bytes 0 private allocs DEVICE: 0 objects of 64 bytes = 0 total bytes 0 private allocs CLIENT: 0 objects of 152 bytes = 0 total bytes 0 private allocs WINDOW: 0 objects of 28 bytes = 0 total bytes 0 private allocs PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs TOTAL: 1 objects, 8 bytes, 0 allocs 10 SELECTIONs still allocated at reset WINDOW: 0 objects of 28 bytes = 0 total bytes 0 private allocs PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs TOTAL: 1 objects, 8 bytes, 0 allocs 1 PIXMAPs still allocated at reset PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs TOTAL: 1 objects, 8 bytes, 0 allocs /usr/bin/iceauth: creating new authority file /tmp/0252723348/.ICEauthority QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QDialog) Negative sizes (-1,-1) are not possible Corrupt data!
Corrupt data!
QGArray::at: Absolute index -1 out of range Aug 12 17:42:54 kdm_config[2843] info: Cannot open master configuration file /opt/trinity/share/config/kdm/kdmdistrc 1 XSELINUXs still allocated at reset SCREEN: 0 objects of 140 bytes = 0 total bytes 0 private allocs DEVICE: 0 objects of 64 bytes = 0 total bytes 0 private allocs CLIENT: 0 objects of 152 bytes = 0 total bytes 0 private allocs WINDOW: 0 objects of 28 bytes = 0 total bytes 0 private allocs PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs TOTAL: 1 objects, 8 bytes, 0 allocs 1 PIXMAPs still allocated at reset PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs TOTAL: 1 objects, 8 bytes, 0 allocs /usr/bin/iceauth: creating new authority file /tmp/1704988676/.ICEauthority QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QDialog) Negative sizes (-1,-1) are not possible krootimage: Fatal IO error: client killed kwin: Fatal IO error: client killed reading '/root/.kompmgr.pid' as kompmgr pidfile
Server terminated successfully (0). Closing log file.
X.Org X Server 1.12.3 Release Date: 2012-07-09 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.4.4-3-ARCH i686 Current Operating System: Linux tdesru 3.4.7-1-ARCH #1 SMP PREEMPT Sun Jul 29 20:05:01 UTC 2012 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=a625b429-6143-459c-a57c-6c5bba56d715 ro quiet Build Date: 09 July 2012 04:03:16PM
Current version of pixman: 0.26.2 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: Sun Aug 12 17:43:13 2012 (==) Using config directory: "/etc/X11/xorg.conf.d" /usr/bin/iceauth: creating new authority file /tmp/0998279359/.ICEauthority QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QDialog) Negative sizes (-1,-1) are not possible Server terminated successfully (0). Closing log file.
Can anybody tell what the issue is there? Does the new Xorg not work with QWidget leading to:
QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QDialog) Negative sizes (-1,-1) are not possible
??
On 08/12/2012 06:05 PM, David C. Rankin wrote:
I think I have found the flashed message that appears before the default greeter appears. It looks like it is related to the new Xorg. Here is my kdm.log for today. The Corrupt data! messages look promising. What is putting those messages there?:
Here is the message. It says:
"Press Ctrl+Alt+Del to begin"
What in the heck is this and how do I disable it? Is this tsak?
http://www.3111skyline.com/dl/dt/trinity/ss/kdm-passwd-error.jpg
Could this be killing the graphical chooser?
On 08/12/2012 06:05 PM, David C. Rankin wrote:
I think I have found the flashed message that appears before the default greeter appears. It looks like it is related to the new Xorg. Here is my kdm.log for today. The Corrupt data! messages look promising. What is putting those messages there?:
Here is the message. It says:
"Press Ctrl+Alt+Del to begin"
What in the heck is this and how do I disable it? Is this tsak?
http://www.3111skyline.com/dl/dt/trinity/ss/kdm-passwd-error.jpg
Could this be killing the graphical chooser?
-- David C. Rankin, J.D.,P.E.
Turn off SAK support in tdmrc to reenable the (less secure) graphical greeter...
Tim
On 08/12/2012 07:06 PM, Timothy Pearson wrote:
On 08/12/2012 06:05 PM, David C. Rankin wrote:
I think I have found the flashed message that appears before the default greeter appears. It looks like it is related to the new Xorg. Here is my kdm.log for today. The Corrupt data! messages look promising. What is putting those messages there?:
Here is the message. It says:
"Press Ctrl+Alt+Del to begin"
What in the heck is this and how do I disable it? Is this tsak?
http://www.3111skyline.com/dl/dt/trinity/ss/kdm-passwd-error.jpg
Could this be killing the graphical chooser?
-- David C. Rankin, J.D.,P.E.
Turn off SAK support in tdmrc to reenable the (less secure) graphical greeter...
Tim
DAMN!,
http://www.3111skyline.com/dl/dt/trinity/ss/kdm-chooser-OK.jpg
That has been it this whole time!! When did tsak begin killing the graphical login? Moreover, why did that "Press Ctrl+Alt+Del to begin" (pop-under) the main xdg chooser window so many time before it finally gave me the dialog? I must have started tdm/kdm 15 times and it never gave me the "Press Ctrl+Alt+Del to begin" before. That's weird...
Oh, well, at least we know what the culprit.
Slavek,
Here are the changes/"cherry picks" I would propose for 3513-sru kdmrc generation (kdm/config.def). The kdm/tdm changes are necessary to avoid conflicts with kde4 (e.g. stale .pid file, etc..):
-PidFile=/var/run/kdm.pid +PidFile=/var/run/tdm.pid
-#DataDir= +DataDir=/var/lib/tdm
-#SystemShell=/bin/bash (optional change - all distros I know use bash) +SystemShell=/bin/bash
-#UseSAK=false (disables graphical login if enabled) +UseSAK=false
-Preloader=/opt/trinity/bin/preloadkde (preloadkde does NOT exist) +#Preloader=/opt/trinity/bin/preloadkde
I have attached a patch for consideration or to help identify commits that do this...
http://www.3111skyline.com/dl/dt/trinity/ss/kdm-chooser-OK.jpg
That has been it this whole time!! When did tsak begin killing the graphical login? Moreover, why did that "Press Ctrl+Alt+Del to begin" (pop-under) the main xdg chooser window so many time before it finally gave me the dialog? I must have started tdm/kdm 15 times and it never gave me the "Press Ctrl+Alt+Del to begin" before. That's weird...
Oh, well, at least we know what the culprit.
Serious work went into updating tsak after 3.5.13. I don't know all of the patches but there were many. I don't know whether those patches can be backported. Check bug reports 898 and 906 for most of the fixes.
Darrell
On Monday 13 of August 2012 04:31:55 Darrell Anderson wrote:
http://www.3111skyline.com/dl/dt/trinity/ss/kdm-chooser-OK.jpg
That has been it this whole time!! When did tsak begin killing the graphical login? Moreover, why did that "Press Ctrl+Alt+Del to begin" (pop-under) the main xdg chooser window so many time before it finally gave me the dialog? I must have started tdm/kdm 15 times and it never gave me the "Press Ctrl+Alt+Del to begin" before. That's weird...
Oh, well, at least we know what the culprit.
Serious work went into updating tsak after 3.5.13. I don't know all of the patches but there were many. I don't know whether those patches can be backported. Check bug reports 898 and 906 for most of the fixes.
Darrell
Darrell, all patches on the SAK I carefully backport to v3.5.13-sru. I believe that I have not overlooked any SAK patch.
Slavek --
On 08/12/2012 09:45 PM, Slávek Banko wrote:
Serious work went into updating tsak after 3.5.13. I don't know all of the
patches but there were many. I don't know whether those patches can be backported. Check bug reports 898 and 906 for most of the fixes.
Darrell
Yes, I recall all the CPU at 100% due to tsak fun...
Darrell, all patches on the SAK I carefully backport to v3.5.13-sru. I believe that I have not overlooked any SAK patch.
I have no clue why UseSAK=true causes the graphical kdm-greeter to fail. It has not been that long ago I was using tsak with the graphical greeter. What is strange is that it began to fail for both R14 and 3513-sru at about the same time 3 weeks or so ago. (it could just be coincidence in timing)
If SAK was working and backported, I wouldn't mind using it, but at the same time, it's not one of those things I've ever been too concerned about in a home or small-office setting. If a bad guy has physical access to a box, all you have to do is pop in a boot CD and pull the power-cord. All the great login security in the world won't help in that situation......
I don't know kdm/tdm greeter code well enough to know what would make it fail to load a graphical greeter that easily. But, reading through the full kdmrc, it looks like GrabServer=true may be to blame. That reads:
# Hold the X-server grabbed the whole time the greeter is visible. This # may be more secure, but it will disable any background and other # X-clients started from the Setup script. # Default is false #GrabServer=true
If the SAK code in 3513-sru has the effect of setting GrabServer=true, then that could explain the graphical chooser failure...
On 08/12/2012 09:45 PM, Slávek Banko wrote:
Serious work went into updating tsak after 3.5.13. I don't know all of the
patches but there were many. I don't know whether those patches can
be
backported. Check bug reports 898 and 906 for most of the fixes.
Darrell
Yes, I recall all the CPU at 100% due to tsak fun...
Darrell, all patches on the SAK I carefully backport to v3.5.13-sru. I believe that I have not overlooked any SAK patch.
I have no clue why UseSAK=true causes the graphical kdm-greeter to fail.
By design--the graphical greeter has no mechanism by which to request a SAK keypress sequence from the user.
Tim
On 08/13/2012 12:20 AM, Timothy Pearson wrote:
By design--the graphical greeter has no mechanism by which to request a SAK keypress sequence from the user.
Tim
OK,
Buy why couldn't the keypress simply pass-through the graphical greeter? I guess I just don't know enough about it to understand -- and I almost like it that way :)
On 08/13/2012 12:20 AM, Timothy Pearson wrote:
By design--the graphical greeter has no mechanism by which to request a SAK keypress sequence from the user.
Tim
OK,
Buy why couldn't the keypress simply pass-through the graphical greeter? I guess I just don't know enough about it to understand -- and I almost like it that way :)
-- David C. Rankin, J.D.,P.E.
It's not a technical limitation, it's more an issue of someone sitting down and adding a SAK request screen to the themed greeter by writing the needed code and making attractive, matching graphics for each TDE theme. As I use the "ugly" windowed login screen I probably won't be the one to do this particular task. ;-)
Tim
-
Darrell Anderson -
David C. Rankin -
Slávek Banko -
Timothy Pearson