Can someone confirm if this bug is still the case in Lucid? If not, I'll
have a prep machine in a few days.
Also, if anyone has any direction on where this is heading, please let
me know also. Specifically, does this need patching? Or should the wiki
be updated to reflect the new behaviour of
I have given this a second try after some updates, and the original
functionality quirk seems to have resolved itself. However, data keys
are still missing from /apps/panel/global if opened in gconf-editor, or
if I were to dump them via gconftool.
Regards
Iain
--
gnome-panel global keys missing
Yes, see the attached image.
Rest assured, I have done nothing but switch to guest session and opened
those two programs.
I'll give gnome-panel a re-installation, to see if that clears it up.
Regards
Iain
** Attachment added: Screenshot.png
Hmm, reinstalling the package via dpkg seems to have resolved the issue,
which strikes heavy bearing to another bug I'm currently trying to
investigate (have no official report on the issue yet).
This incident actually may shed some light onto what the core problem
is...
Feel free to close this
Public bug reported:
Binary package hint: gnome-panel
If I open gconf-editor, and browse to '/apps/panel/global', all keys
listed there are missing.
If I were to run in a terminal: `gconftool --set
/apps/panel/global/lock_down --type bool true`, gnome-panel does not
adhere to this setting.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41438334/Dependencies.txt
--
gnome-panel global keys missing in gconf
https://bugs.launchpad.net/bugs/542883
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
And with regards to bug #459199, updated to match system uid
configuration.
Also, renamed it to disallow_invalid_login to better describe what it
does.
Regards
Iain
** Attachment added: 29_disallow_invalid_login.patch
http://launchpadlibrarian.net/37358835/29_disallow_invalid_login.patch
--
And imported all the relevant translations from gdm-2.20 into gdm-2.28
(using a perl script to grab+insert into files, so there may be error,
although I'm confident there isn't).
If anyone has any comments - greatly appreciated. As I'm learning here
as much as I am contributing.
Regards
Iain
@Kees, I agree.
This patch attached should do just that.
It's a slight modification of another part of the gdm code that
disallows the showing of system users in the selection screen. Copied it
into the do_accredit stage of the user authorisation, tested and it
works as expected.
Just putting
** Attachment added: 26_disallow_rootlogin.patch
http://launchpadlibrarian.net/37226490/26_disallow_rootlogin.patch
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
Public bug reported:
Binary package hint: gdm
Steps to reproduce:
1) Create a password for root
2) Logout
3) Login as root
Now, previous versions of Ubuntu prevented a graphical root login in
GDM, and I see no reason why this should differ in the new versions.
There has always been a strict
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35788719/Dependencies.txt
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
Thankfully, the fix is trivial too:
Add the following to /etc/pam.d/gdm
authrequiredpam_succeed_if.so user != root quiet
Patch for the debian build attached.
Regards
Iain
** Attachment added: disallow_root_login.patch
Just running sudo passwd is enough to set the password.
Actually, after having a sleep on it, would it be useful just to deny
uid's 1000 and the 'nobody' user?
ie:
auth required pam_succeed_if.so uid = 1000 quiet
auth required pam_succeed_if.so user != nobody quiet
This, I think will restore
I looked into this a bit when Bender2k14 mentioned it on the forums.
Pausing the timer if the file is reported to be a broken link seems like the
most obvious thing to do.
Patch against the nautilus source directory is attached.
Regards
Iain
** Attachment added: timed_wait.patch
Public bug reported:
Binary package hint: nautilus
Hi, I've noticed that when I double click Up in Nautilus that I go up
two directories in the GUI. But according to the text-based location
I've only gone up one.
Also, I cannot re-enter the directory that I am supposedly in (because I
am
** Attachment added: Ogg Video of the Bug in action.
http://launchpadlibrarian.net/13832791/out.ogg
--
Double-Click Up Bug
https://bugs.launchpad.net/bugs/220864
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
17 matches
Mail list logo
