** Changed in: compiz (Ubuntu Bionic)
Status: Fix Released => Invalid
** Changed in: compiz (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
** Changed in: compiz (Ubuntu Bionic)
Status: Invalid => Fix Released
** Changed in: compiz (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
It is not invalid; it is a regression vs all previous screen lock
implementations that compiz does pam handling in process instead of in a
helper process, making it vulnerable to this kind of library skew.
** Changed in: compiz (Ubuntu)
Status: Invalid => Triaged
--
You received this bug
Marking compiz as invalid because this is a ubuntu-release-upgrader
problem.
** Changed in: compiz (Ubuntu)
Status: New => Invalid
** Changed in: compiz (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of compiz
packagers,
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.21
---
ubuntu-release-upgrader (1:18.04.21) bionic; urgency=medium
* DistUpgradeQuirks.py: when a snap fails to install try the next one
instead of trying to check the return code of the called process which
I tested a release upgrade from Ubuntu 16.04 to Ubuntu 18.04 today using
the version of release-upgrader in -proposed and the lock screen did not
appear.
bdmurray@clean-xenial-amd64:/tmp/u-r-u$ grep "release-upgrader version"
/var/log/dist-upgrade/main.log
2018-07-16 14:00:39,174 INFO
** Description changed:
[Impact]
During a release upgrade, the screen should not be locked because the upgrade
of underlying libraries may leave the system in an inconsistent state where the
process locking the screen may not be able to unlock it again. (Its possible
for the screen to lock
Hello Steve, or anyone else affected,
Accepted ubuntu-release-upgrader into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:18.04.20 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Description changed:
- During a release upgrade, the screen should not be locked because the
- upgrade of underlying libraries may leave the system in an inconsistent
- state where the process locking the screen may not be able to unlock it
- again.
+ [Impact]
+ During a release upgrade, the
** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1778817
Title:
release
This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.4
---
ubuntu-release-upgrader (1:18.10.4) cosmic; urgency=medium
* DistUpgradeQuirks.py, DistUpgradeController.py: move inhibiting of
gnome-session idle so that it is called immediately after the upgrade
** Branch linked: lp:ubuntu-release-upgrader
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1778817
Title:
release upgrade from xenial to bionic desktop: screen locks itself,
** Branch linked: lp:~brian-murray/ubuntu-release-upgrader/improve-
inhibit-idle
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1778817
Title:
release upgrade from xenial to bionic
I reported bug 1780342 regarding the lock screen after the upgrade has
completed and one has not rebooted.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1778817
Title:
release
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of compiz
packagers, which is
syslog search for 'inhibit':
$ zgrep -i inhibit /var/log/syslog.*
/var/log/syslog.5.gz:Jun 26 11:56:40 epona org.freedesktop.Notifications[1961]:
** (notify-osd:2212): WARNING **: dnd_is_idle_inhibited(): got error "No such
method 'IsInhibited'"
$
so, not interesting.
I can reproduce first part of the problem during an upgrade from 17.10
to 18.04 and the screen locks during the upgrade. It locks before u-r-u
issues the inhibit command and proceeds with the upgrade with the screen
locked.
--
You received this bug notification because you are a member of compiz
Steve - your /var/log/dist-upgrade/main.log file may be helpful in
sorting out where the inhibit went wrong. Could you add it to the bug?
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
On Wed, Jul 04, 2018 at 07:47:15AM -, Sebastien Bacher wrote:
> > Ok, but we still need to know how to inhibit the screen locking in compiz,
> > since the previous standard method is ineffective.
>
> The command that Julian pointed out as the one used by u-r-u is correct
> and works from our
> Ok, but we still need to know how to inhibit the screen locking in compiz,
> since the previous standard method is ineffective.
The command that Julian pointed out as the one used by u-r-u is correct
and works from our testing
> unless you are running a GNOME session.
>
I reproduced the second part of the problem (screen locks and fails to
unlock) after upgrading from 16.04 to 18.04 and before restarting the
machine (finish the upgrade, close the upgrader and wait until the
screen saver goes off)
The following lines are displayed in the journal:
juil. 04
No. This upgrade had the screen locked over a conffile prompt. The
upgrade was definitely still in progress.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1778817
Title:
release
I believe the issue is that the gnome-session-inhibit call is terminated
after the upgrade unless you are running a GNOME session.
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-
upgrader/trunk/view/head:/DistUpgrade/DistUpgradeQuirks.py#L444
After the upgrade completed and
On Tue, Jul 03, 2018 at 02:26:14PM -, Sebastien Bacher wrote:
> @Steve, you are probably right about the compiz use of pam but that
> doesn't seem likely to get changed at this point, at least not before
> the LTS upgrades to bionic are turned on
Ok, but we still need to know how to inhibit
@Steve, you are probably right about the compiz use of pam but that
doesn't seem likely to get changed at this point, at least not before
the LTS upgrades to bionic are turned on
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in
Doing "/usr/bin/gnome-session-inhibit --inhibit idle --inhibit-only" on
Xenial seems to work fine so the issue seems to be on the ubuntu-
release-upgrader side. Is the process using the correct user environment
(uid, dbus session bus, etc) to talk to the active session?
--
You received this bug
That's the first report of the issue and screen locking inhibition has
been working fine on xenial so far, is there anything useful (warning,
errors, info about screen locking, inhibiting, screensaver, session) in
the system logs/journal? Can you reproduce the bug or was it a one time
thing?
--
So, u-r-u runs /usr/bin/gnome-session-inhibit --inhibit idle --inhibit-
only - running that manually works fine to block stuff on cosmic, but
not sure about xenial.
systemd-inhibit --what=idle does not prevent locking.
--
You received this bug notification because you are a member of compiz
** Tags added: id-5b32dfc70f54891287c5942a
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1778817
Title:
release upgrade from xenial to bionic desktop: screen locks itself,
password
The failure is because pam_unix depends on libcrypt, and libcrypt is
part of glibc, and compiz doesn't otherwise have libcrypt loaded into
memory, and libcrypt has a tight versioned dependency on the
corresponding version of libc itself (requires symbol GLIBC_2.25). So
when dlopen() tries to load
30 matches
Mail list logo
