[Touch-packages] [Bug 1872282] Re: Failed to get user record: Invalid argument

2020-04-14 Thread Josef Hopfgartner
Hey Balint,

thanks for the fix!
Works like a charm right now.

I've also noticed an improvement with version 245:
after reboot gdm login screen displays the last logins from AD/winbind accounts 
the same like from UNIX accounts.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1872282

Title:
  Failed to get user record: Invalid argument

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  system is ubuntu focal with pam_winbind and nss_winbind enabled.

  unix users are not affected.
  this bug won't happen with systemd version 2.44.3

  beginning with version 245 (including 245.4-2) no user session will be 
created after login.
  login itself works e.g. on tty2.
  but loginctl does not show a corresponding user session.
  gdm login needs a user session, so it fails.

  this bug already seems to be handled here:
  https://github.com/systemd/systemd/issues/15149

  this bug only affects user sessions directly on a samba domain controller.
  users can log in with pam_systemd version 245 on winbind client workstations 
in the same domain.

  journalctl reports:
  Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: 
pam_systemd(login:session): Failed to get user record: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-systemd:amd64 244.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 12 11:44:41 2020
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1872282] [NEW] Failed to get user record: Invalid argument

2020-04-12 Thread Josef Hopfgartner
Public bug reported:

system is ubuntu focal with pam_winbind and nss_winbind enabled.

unix users are not affected.
this bug won't happen with systemd version 2.44.3

beginning with version 245 (including 245.4-2) no user session will be created 
after login.
login itself works e.g. on tty2.
but loginctl does not show a corresponding user session.
gdm login needs a user session, so it fails.

this bug already seems to be handled here:
https://github.com/systemd/systemd/issues/15149

this bug only affects user sessions directly on a samba domain controller.
users can log in with pam_systemd version 245 on winbind client workstations in 
the same domain.

journalctl reports:
Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: 
pam_systemd(login:session): Failed to get user record: Invalid argument

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libpam-systemd:amd64 244.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Apr 12 11:44:41 2020
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1872282

Title:
  Failed to get user record: Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  system is ubuntu focal with pam_winbind and nss_winbind enabled.

  unix users are not affected.
  this bug won't happen with systemd version 2.44.3

  beginning with version 245 (including 245.4-2) no user session will be 
created after login.
  login itself works e.g. on tty2.
  but loginctl does not show a corresponding user session.
  gdm login needs a user session, so it fails.

  this bug already seems to be handled here:
  https://github.com/systemd/systemd/issues/15149

  this bug only affects user sessions directly on a samba domain controller.
  users can log in with pam_systemd version 245 on winbind client workstations 
in the same domain.

  journalctl reports:
  Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: 
pam_systemd(login:session): Failed to get user record: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-systemd:amd64 244.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 12 11:44:41 2020
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1423859] [NEW] package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 zurück

2015-02-20 Thread Josef Hopfgartner
Public bug reported:

during apt update probably related to systemd sysv scripts not running
(dbus and policykit)

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: colord 1.2.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Fri Feb 20 08:50:09 2015
Dmesg:
 
DuplicateSignature: package:colord:1.2.8-0ubuntu1:Unterprozess neues 
pre-removal-Skript gab den Fehlerwert 143 zurück
ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 
zurück
SourcePackage: colord
Title: package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 143 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1423859

Title:
  package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess
  neues pre-removal-Skript gab den Fehlerwert 143 zurück

Status in colord package in Ubuntu:
  New

Bug description:
  during apt update probably related to systemd sysv scripts not running
  (dbus and policykit)

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: colord 1.2.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 20 08:50:09 2015
  Dmesg:
   
  DuplicateSignature: package:colord:1.2.8-0ubuntu1:Unterprozess neues 
pre-removal-Skript gab den Fehlerwert 143 zurück
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 
zurück
  SourcePackage: colord
  Title: package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 143 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1412125] [NEW] package powerd 0.16+15.04.20150116.1-0ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 6 zurück

2015-01-18 Thread Josef Hopfgartner
Public bug reported:

during apt-get update powerd doesn't start again

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: powerd 0.16+15.04.20150116.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
Date: Sat Jan 17 16:35:50 2015
DuplicateSignature: package:powerd:0.16+15.04.20150116.1-0ubuntu1:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 6 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 6 zurück
SourcePackage: powerd
Title: package powerd 0.16+15.04.20150116.1-0ubuntu1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 6 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1412125

Title:
  package powerd 0.16+15.04.20150116.1-0ubuntu1 failed to
  install/upgrade: Unterprozess installiertes post-installation-Skript
  gab den Fehlerwert 6 zurück

Status in powerd package in Ubuntu:
  New

Bug description:
  during apt-get update powerd doesn't start again

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: powerd 0.16+15.04.20150116.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jan 17 16:35:50 2015
  DuplicateSignature: 
package:powerd:0.16+15.04.20150116.1-0ubuntu1:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 6 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 6 zurück
  SourcePackage: powerd
  Title: package powerd 0.16+15.04.20150116.1-0ubuntu1 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 6 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1396797] [NEW] package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

2014-11-26 Thread Josef Hopfgartner
Public bug reported:

reinstall - then ok

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: gnome-icon-theme 3.12.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
Date: Wed Nov 26 21:48:40 2014
DuplicateSignature: package:gnome-icon-theme:3.12.0-1ubuntu1:Trigger bilden 
eine Schleife, aufgegeben
ErrorMessage: Trigger bilden eine Schleife, aufgegeben
PackageArchitecture: all
SourcePackage: gnome-icon-theme
Title: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1396797

Title:
  package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade:
  Trigger bilden eine Schleife, aufgegeben

Status in “gnome-icon-theme” package in Ubuntu:
  New

Bug description:
  reinstall - then ok

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: gnome-icon-theme 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  Date: Wed Nov 26 21:48:40 2014
  DuplicateSignature: package:gnome-icon-theme:3.12.0-1ubuntu1:Trigger bilden 
eine Schleife, aufgegeben
  ErrorMessage: Trigger bilden eine Schleife, aufgegeben
  PackageArchitecture: all
  SourcePackage: gnome-icon-theme
  Title: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1396797/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 147551] Re: cups-pdf fails to generate file when user does not print to default ~/PDF (apparmor vs.cups-pdf inconsistency)

2014-10-05 Thread Josef Hopfgartner
This is what syslog says:
apparmor="DENIED" operation="connect" profile="/usr/lib/cups/backend/cups-pdf" 
name="/run/samba/winbindd/pipe" pid=15076 comm="cups-pdf" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

So, in /etc/apparmor.d/usr.sbin.cupsd a new entry has to be entered:
/run/samba/winbindd/pipe rw,

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/147551

Title:
  cups-pdf fails to generate file when user does not print to default
  ~/PDF (apparmor vs.cups-pdf inconsistency)

Status in “apparmor” package in Ubuntu:
  Invalid
Status in “cups-pdf” package in Ubuntu:
  Invalid
Status in “cupsys” package in Ubuntu:
  Won't Fix

Bug description:
  I had a working cups-pdf setup in Feisty, but after the upgrade to
  Gutsy it doesn't work anymore.

  The log file says:

  Mon Oct  1 10:05:49 2007  [STATUS] PDF creation successfully finished (nobody)
  Mon Oct  1 10:14:51 2007  [ERROR] failed to set file mode for PDF file (non 
fatal) (/home/hunzikea/Desktop/Report_a_bug.pdf)
  Mon Oct  1 10:14:51 2007  [STATUS] PDF creation successfully finished 
(hunzikea)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp