On https://lists.gnome.org/archives/commits-list/2019-May/msg04333.html
one may read:
main: Add systemd gnome-session monitoring code for leader
We are in the situation that gnome-session-binary is the session leader
process for the user. This process is managed via logind and is
To close down the Desktop, it seems that is it more intended to
terminate the running instance `gnome-session-ctl --monitor`. Therefore,
the line
ExecStop=-/bin/bash -exc '/usr/bin/killall gnome-session-ctl && logger
"PATCH: killall gnome-session-ctl"'
also work. And from the help page of `gnome-
The _Fast User Switch_ in the Menubar still don't work. But I found that I may
start a new desktop on next free VT by
```
XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0 dm-tool stwitch-to greeter
```
with the expected behavior. Also, session switching via `` works
as usual, then.
--
You r
I append a syslog containing logon and logoff cycle recorded with the
patched version of the gnome-session.service file.
** Attachment added: "syslog for user session cycle (patched
gnome-session.service)"
https://bugs.launchpad.net/ubuntu/noble/+source/gnome-session/+bug/2063383/+attachmen
Yes, because the controlling systemd service wait in vain for graceful
termination of the gnome-session-binary and send a SIGKILL after 90s.
For an unknown reason nobody seems to send a SIGTERM before. But I'm
neither used to write scripts for systemd nor know the details of
desktop session managem
I found a workaround by send a SIGTERM to the gnome-session-binary:
ubuntu@lenovy:~$ cat /lib/systemd/user/gnome-session.service
[Unit]
Description=GNOME Session Manager (Ubuntu downstream version for Unity support)
PartOf=graphical-session.target
[Service]
ExecStart=/bin/sh -exc '[ "$DESKTOP_SES
I append a syslog containing logon and logoff cycle while the both
gnome-session-binaries are parameterized to run in debug mode.
This offers to first off study the bug without setting up a test
environment.
** Attachment added: "syslog for user session cycle"
https://bugs.launchpad.net/ubunt
Seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/noble/+source/gnome-
session/+bug/2063383
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2093625
Title:
graphical session hang for 1m30s o
Public bug reported:
On logout or user switch, the graphical session hang until systemd hard
kills gnome-session-binary after a timeout of about 1m30s. This instance
seem to be driven by graphical-session-pre.target.
This issue appear even on a fresh vanilla installation I set up to trace
down th
*** This bug is a duplicate of bug 1841718 ***
https://bugs.launchpad.net/bugs/1841718
was fixed for me with common Ubuntu updates related to bug #1841718.
** This bug has been marked a duplicate of bug 1841718
[radeon] Rendering of combo boxes and tooltips is broken
--
You received this
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed-hwe (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860268
Title:
window titleb
Also, some other desktop elements like tooltips, drop down lists or even
the selection rubberband box of the screenshot feature are affected. It
seems, that the the similarity of this is a comparable small *height*.
The rubberband selection for instance is disturbed, if the enclosed
height is about
gjaekel@jelly:~$ lshw -C video
WARNING: you should run this program as super-user.
*-display
description: VGA compatible controller
product: Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
** Description changed:
- * After todays package update, the window titlebar area of all windows is
rendered in a disturbed way.
+ * After todays package update, the window titlebar area of all windows is
rendered in a disturbed way.
* Package update include a kernel change to 5.3 from 5.0. T
** Attachment added: "Example of a disturbed titlebar area"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+attachment/5321529/+files/Titlebar_disturbed.Ubuntu18_04.20200119.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "dmesg from boot with kernel 5.3"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+attachment/5321528/+files/dmesg.20200119
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Public bug reported:
* After todays package update, the window titlebar area of all windows is
rendered in a disturbed way.
* Package update include a kernel change to 5.3 from 5.0. The bug is not
related to the kernel; it also happen with the last one. Therefore, it's
related to the new graph
Dear Scott,
you're completely right:
configuring a new computer I run into the same issue:
* adding a remote printer (via ipp:), first tests works fine
* after declaring it as the default, the Printer Administration Page on
systemsettings fail. Running it from the console, it drops the same er
Public bug reported:
In general, hibernate (S3) and suspend action works fine. But there's a
little ugly artefact:
Probably different to others we're using this box at home as a "central
workstation" for the members of our family. From that, there continously
more than one user (X/gnome) session
I'm also don't observe this currently on my Unbutu workstations, but
with "su -" on some of my Gentoo Server's, too. And this type of problem
is also reported by users of other distributions!
After switching to another user via "su - foo" i eithter get kicked out
immediately (the shell writes "exi
As expected, 2.6.24-19 solves the issue and related artefacts for me,
too.
Thank you, John for discovering the core reason at #96. Two missing
statements, and we are lost in space ;)
Guido
--
Kernel 2.6.24-17 - broken resume from suspend to RAM
https://bugs.launchpad.net/bugs/226279
You receive
Dear john and Tim
john> Looking at the commit being reverted, its broken because the fix is not
complete compared to mainline.
john> [...]
john> Noting especially the changes made upstream to kernel/time/timekeeping.c
> @@ -178,6 +178,7 @@ static void change_clocksource(void)
> + new->cycl
Dear Tim,
i wonder about this TSC issue the patch was designed for happens on my
(and the other) machines, because it's have a single CPU without HT.
The patch says "return some last value until the normal used one is
higher than". From that: Will the TSC reset, if the CPU is suspended
(powered d
This is a "me too".
But i want to note, that i'm running it on an comparatively "old" and
plain vanilla surf/email station: P4/1.6Ghz (no HT), PATA-100, AGP-
GraphicCard (Matrox MGA550), uhci (USB 1.1), no WLAN, ...
may be this helps to exclude some things
good luck
Guido
--
Kernel 2.6.24-17
*** This bug is a duplicate of bug 226279 ***
https://bugs.launchpad.net/bugs/226279
... unfortunately confirmed on my box, a Fujitsu/Siemens FSC Scenic S2.
--
2.6.24-17 breaks suspend/resume
https://bugs.launchpad.net/bugs/226566
You received this bug notification because you are a member
25 matches
Mail list logo
