[Bug 799605] Re: pam-auth-update creates a 'common-account' that fails with cached logins

2018-02-05 Thread Reinhard Mayr 
This helped me on 16.04: http://kennywest.blogspot.co.at/2007/04
/pamccreds-howto.html

>> QUOTE
Update /etc/pam.d/common-auth:

auth sufficient pam_unix.so
auth [authinfo_unavail=ignore success=1 default=die] pam_ldap.so use_first_pass
auth [default=done] pam_ccreds.so action=validate use_first_pass
auth [default=done] pam_ccreds.so action=store use_first_pass
auth [default=done] pam_ccreds.so action=update use_first_pass

Update /etc/pam.d/common-account:

account sufficient pam_unix.so nullok_secure
account sufficient pam_ldap.so
account required pam_permit.so
<< QUOTE

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

Title:
  pam-auth-update creates a 'common-account' that fails with cached
  logins

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpam-ccreds/+bug/799605/+subscriptions

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

[Bug 1015913] [NEW] Printer settings are forgotten after printing

2012-06-21 Thread Reinhard Mayr 
Public bug reported:

Ubuntu 12.04, shotwell 0.12.3, all packages up-to-date.

Select a photo and print it: File / Print ...
 * Paper type is Automatic (would need Photo paper)
 * paper source is Auto (would need Photo tray)
 * paper size is A4 (would need 4x6 borderless photo)
 * image quality is normal (would need hires photo)

These settings are reset after each printing run. For the next job I
have to reapply these settings manually.

Is there a way to make the settings persistent?

Thanks!

** Affects: shotwell (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Printer settings are forgotten after printing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1015913/+subscriptions

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

Re: [Bug 532374] Re: Lenovo Thinkpads with Core i5 and i7 suspend/resume (with kernel oops) once then fail horribly on next suspend

2010-06-20 Thread Reinhard Mayr 
Regarding the update, I just burnt the bootable CD available from the lenovo
site... Boot it, the rest is all pretty straight forward. Reading the readme
file could also be useful. -- Have no fear ;)

Cheers, Reinhard.

2010/6/20 Matt Price matt.pr...@utoronto.ca

 i have a t410 and of course suffer from this bug like everyone else.  i
 appear to have BIOS version 1.09:
 $ sudo dmidecode -s bios-version
 6IET49WW (1.09 )

 i would like to update to the newest bios but i'm a little terrified to
 do so -- can anyone out there give or point me to a reliable and
 complete set of instructions as to what I ought to do to make this work?
 Thank you so much,

 also: will i have to update to 2.6.34, as suggested in some postings, or
 will that workaround no longer be necessary after the bios update?  Thanks,
 matt

 --
 Lenovo Thinkpads with Core i5 and i7 suspend/resume (with kernel oops) once
 then fail horribly on next suspend
 https://bugs.launchpad.net/bugs/532374
 You received this bug notification because you are a direct subscriber
 of the bug.

 Status in The Linux Kernel: Unknown
 Status in OEM Priority Project: Fix Released
 Status in “linux” package in Ubuntu: Invalid
 Status in “linux” source package in Lucid: Invalid

 Bug description:
 THIS HAPPENS ONLY TO THINKPADS WITH i5 or i7 PROCESSORS: Thinkpad T410,
 T510 and X201 models are affected (intel integrated graphics, nvidia
 discrete graphics).  The first suspend/resume completes successfully.  The
 second suspend appears to work, but when waking, a few LEDs flicker, but the
 laptop stays suspended (moon LED on the lid stays lit, LED around power
 button continues to pulse).  Pressing the power button again causes a reboot
 (no other buttons seem to do anything in this state).

 Per https://wiki.ubuntu.com/DebuggingKernelSuspend:

 $ grep -A4 Magic .tmp/dmesg.txt
 [1.148585]   Magic number: 0:523:347
 [1.148587]   hash matches
 /build/buildd/linux-2.6.32/drivers/base/power/main.c:471
 [1.148615]  pci:00: hash matches

 That's the DRAM Controller.

 Same results from the xterm session, and also without X, so no
 gnome-power-manager interactions.

 This issue effects:
 Thinkpads X201, T410, T510, W510
  possibly T410s



 To unsubscribe from this bug, go to:
 https://bugs.launchpad.net/linux/+bug/532374/+subscribe


-- 
Lenovo Thinkpads with Core i5 and i7 suspend/resume (with kernel oops) once 
then fail horribly on next suspend
https://bugs.launchpad.net/bugs/532374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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