[Bug 994388]

2013-01-11 Thread Mark Jenkins
Created attachment 72818
set correct paper tray in UI

This was fixed in 38f8241859cdef4dd7c3098e365947dd5b64f78c by David Tardon, but 
unfortunately this bug wasn't referenced in the commit message (unlike his 
previous attempt which he had to reverse), so it never had the chance to appear 
in this bug report and to get into later 3.5.x releases, its only resolved in 
3.6 releases.
http://cgit.freedesktop.org/libreoffice/core/commit/?id=38f8241859cdef4dd7c3098e365947dd5b64f78c

I've applied that commit as a patch without change against Ubuntu 12.04
LTS's version 3.5 build which they call 3.5.4-0ubuntu1.1 and was able to
build, run, and see this bug is resolved. (launchpad bug #994388).
Didn't notice any regressions with some brief testing, and the patch
appears to be a limited in it's scope.

I'm now going to deploy that particular build to real users in a 10 desk
office running Ubuntu 12.04 where this bug has been of concern and see
if they notice any regressions due to this fix being applied.

I believe this bug was still present in 3.5.7. I will confirm, and try
this patch against against an unadulterated LibreOffice 3.5.7 when I get
the chance, particularly if interest is expressed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994388

Title:
  [Upstream] Libreoffice can't select printer tray

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/994388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 89906] Re: kdesktop_lock refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
** Description changed:

  Binary package hint: kdesktop
  
- A user account can have a blank password. To set it to blank
- # passwd -d username
- 
- GDM uses PAM for authentication, and PAM will allow users with blank
- passwords to authenticate in certain situations if nullok_secure in
- /etc/pam.d/common-auth is changed to nullok.
- 
- After doing this it is posible to login to kde with a blank password. If
- the sesison is locked, it will refuse to unlock.
+ If I login to kde with a blank password and the sesison is locked, it
+ will refuse to unlock.
  
  /usr/bin/kdesktop_lock is in kdesktop. Using 4:3.5.2-0ubuntu27 (dapper-
  security)

-- 
kdesktop_lock refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 89906] Re: kdesktop_lock refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
** Description changed:

  Binary package hint: kdesktop
+ 
+ Using Gnome Display Manger (GDM) and PAM for authentication.
+ 
+ nullok_secure in /etc/pam.d/common-auth has been changed to nullok to
+ allow passwordless login.
  
  If I login to kde with a blank password and the sesison is locked, it
  will refuse to unlock.
  
  /usr/bin/kdesktop_lock is in kdesktop. Using 4:3.5.2-0ubuntu27 (dapper-
  security)

-- 
kdesktop_lock refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 89906] Re: kdesktop_lock refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
kdesktop_lock will not unlock if nothing is typed in and the unlock
button is clicked, but if an arbitrary string is put into the password
box it will unlock.

-- 
kdesktop_lock refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 89906] Re: kdesktop_lock refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
kcheckpass (which kdesktop_lock executes to check the password) is
behaving correctly, it immediatly exits with code 0 (success) on
accounts with a blank password.

-- 
kdesktop_lock refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 89906] Re: kdesktop_lock refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
I'm having the same problem with gnome-screensaver and xscreensaver,
which means this isn't a kde specific problem. Going to determine if
this is due to a bug somewhere else or if this is just a configuration
problem.

-- 
kdesktop_lock refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 89906] Re: kdesktop_lock refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
I stopped using nullok in /etc/pam.d/common-auth and added a 
auth sufficient pam_listfile.so item=user
to /etc/pam.d/gdm, /etc/pam.d/kscreensaver, /etc/pam.d/xscreensaver, and 
/etc/pam.d/gnome-screensaver
(Actually I put an
@include auth-null-password-user
into these files and put the line in auth-null-password-user)

kscreensaver and gnome-screensaver unlock without problem now.
xscreensaver still requires an attempt at typing a password to unlock.

-- 
kdesktop_lock refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 89906] kblankscrn.kss refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
Public bug reported:

Binary package hint: kdebase-bin

A user account can have a blank password. To set it to blank
# passwd -d username

GDM uses PAM for authentication, and PAM will allow users with blank
passwords to authenticate in certain situations if nullok_secure in
/etc/pam.d/common-auth is changed to nullok.

After doing this it is posible to login to kde with a blank password. If
the sesison is locked, it will refuse to unlock.

/usr/bin/kblankscrn.kss is in kdebase-bin. Using 4:3.5.2-0ubuntu27
(dapper-security)

** Affects: kdebase (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
kblankscrn.kss refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 89906] Re: kdesktop_lock refuses to unlock accounts with blank password

2007-03-05 Thread Mark Jenkins
** Summary changed:

- kblankscrn.kss refuses to unlock accounts with blank password
+ kdesktop_lock refuses to unlock accounts with blank password

** Description changed:

- Binary package hint: kdebase-bin
+ Binary package hint: kdesktop
  
  A user account can have a blank password. To set it to blank
  # passwd -d username
  
  GDM uses PAM for authentication, and PAM will allow users with blank
  passwords to authenticate in certain situations if nullok_secure in
  /etc/pam.d/common-auth is changed to nullok.
  
  After doing this it is posible to login to kde with a blank password. If
  the sesison is locked, it will refuse to unlock.
  
- /usr/bin/kblankscrn.kss is in kdebase-bin. Using 4:3.5.2-0ubuntu27
- (dapper-security)
+ /usr/bin/kdesktop_lock is in kdesktop. Using 4:3.5.2-0ubuntu27 (dapper-
+ security)

-- 
kdesktop_lock refuses to unlock accounts with blank password
https://launchpad.net/bugs/89906

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 52857] Re: ERROR: cpu exception in dosemu code outside of VM86()!

2006-11-19 Thread Mark Jenkins
There's a LKML thread on this.
http://lkml.org/lkml/2005/5/11/12

-- 
ERROR: cpu exception in dosemu code outside of VM86()!
https://launchpad.net/bugs/52857

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 53439] Re: Thunderbird full cpu

2006-11-08 Thread Mark Jenkins
After poking arround with gdb I was able to observe that I'm experiencing this 
bug
https://bugzilla.mozilla.org/show_bug.cgi?id=230580

-- 
Thunderbird full cpu
https://launchpad.net/bugs/53439

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 53439] Re: Thunderbird full cpu

2006-11-03 Thread Mark Jenkins
A profile generated during the cpu slam using jprof.

** Attachment added: jprof profile of cpu hoging madness
   http://librarian.launchpad.net/4963688/profile.html

-- 
Thunderbird full cpu
https://launchpad.net/bugs/53439

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 53439] Re: Thunderbird full cpu

2006-11-02 Thread Mark Jenkins
Experiencing this too. For me it seems to happen specifically when the
address book is being explicitly opened, or implicity accesed by type-
ahead when entering addresses. Planning on running this through a
profiler asap.

Running 1.5.0.7-0ubuntu0.6.06

-- 
Thunderbird full cpu
https://launchpad.net/bugs/53439

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 49627] Re: macro gh_init from /usr/include/guile/gh.h has a syntax error

2006-06-13 Thread Mark Jenkins
** Attachment added: A patch that fixes the problem
   
http://librarian.launchpad.net/3026065/gh_dot_h_gh_init_macro_syntax_error.diff

-- 
macro gh_init from /usr/include/guile/gh.h has a syntax error
https://launchpad.net/bugs/49627

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs