** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ ps -Af | grep -v grep | egrep -w "PPID|$(pgrep -u $USER systemd)"
UID PIDPPID C STIME
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ ps -Af | grep -v grep | egrep -w "PPID|$(pgrep -u $USER systemd)"
UID PIDPPID C STIME
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
- $ loginctl list-sessions
- SESSION UID USER SEAT TTY
- 99 1001 sebastien seat0
- 79
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ loginctl list-sessions
SESSION UID USER SEAT TTY
52 1001 sebastien seat0
79
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ loginctl list-sessions
- SESSION UID USER SEAT TTY
- 52 1001 sebastien seat0
-
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
+ $ loginctl list-sessions
+ SESSION UID USER SEAT TTY
+ 52 1001 sebastien seat0
+
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
+ $ loginctl session-status $(loginctl list-sessions | grep -v tty | grep $USER
| awk '{print $1}')
$
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
- $ ps -Af | grep -v grep | egrep -w "PID|$(pgrep -u $USER systemd)"
+ $ ps -Af | grep -v grep | egrep -w
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
- $ ps -fu $USER | grep -v grep | grep $(pgrep -u $USER systemd)
+ $ ps -Af | grep -v grep | egrep -w
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
- $ ps -fu $USER | grep -v grep | grep $(pgrep -u $USER -o systemd)
+ $ ps -fu $USER | grep -v grep |
Public bug reported:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ ps -fu $USER | grep -v grep | grep $(pgrep -u $USER systemd)
sebasti+ 64862 1 0 13:13 ?00:00:00
@juliank It's not fixed :
$ aptitude search -F '%p' "?origin(jonathonf-vim) ( ?architecture(amd64) |
?architecture(all) ) ?installed"
E: Could not open file
/var/lib/apt/lists/fr.archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-i386_Packages
- open (24: Too many open files)
E: Could not
So I've just restarted the lightdm.service :
$ sudo service lightdm restart
$ service lightdm status
● lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset:
enabled)
Active: active (running) since Wed 2020-01-29 02:09:37 CET;
Hi, I have the same pb. on my ubuntu xenial,
here's what I get in the "lightdm.service" journal :
$ journalctl -au lightdm -S "2020-01-29 1:59"
-- Logs begin at lun. 2020-01-27 11:14:43 CET, end at mer. 2020-01-29 02:01:47
CET. --
janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Failed to write
I have also this pb. It seems gpg cannot handle more than
/etc/apt/trusted.gpg (one keyring) + 39 keyrings in
/etc/apt/trusted.gpg.d/ : https://lists.gnupg.org/pipermail/gnupg-
users/2013-December/048571.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
On ubuntu artful (17.10), both `iwconfig` and `iw dev` report 6Mb/s :
$ iwconfig wlp6s0
wlp6s0IEEE 802.11 ESSID:"eduroam"
Mode:Managed Frequency:5.24 GHz Access Point: CC:46:D6:CB:1E:6E
Bit Rate=6 Mb/s Tx-Power=18 dBm
Retry short limit:7 RTS thr:off
Hi, I also have the same pb.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1707393
Title:
vlc no longer displays certain streams since update vdpau
Status in mesa package
Yes, clearing my KDE cache and rebooting solved the problem for me :
$ rm -rfv /var/tmp/kdecache-$USER
Thanks again to @randyyang :) !
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
Public bug reported:
Hi,
After my ISP home router is being rebooted, my KUbuntu Trusty 14.04.5
LTS does neighter reconnect to my hidden wifi network automatically nor
manually with the Plasma NM applet.
The ONLY workaround I have found so far is by typing the following
command :
$ nmcli con up
Hi, yes removing the /var/lib/apt/lists/partial/* files solved the pb.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1479045
Title:
E: Method gave invalid 103
Public bug reported:
Hi,
I'm using KUbuntu 14.04.4 with kernel 4.2.0-27-generic.
After installing bcmwl-kernel-source_6.30.223.248+bdcom-
0ubuntu8_amd64.deb (which I have downloaded from
http://packages.ubuntu.com/xenial/bcmwl-kernel-source) the following way
:
$ sudo gdebi -n
BTW : I'm Using Ubuntu 14.10.
LXDE does not have this pb. since the PrintScreen triggers the scrot
program that generates the screenshot in my home directory.
Sebastien.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity
Hi,
This bug affects me in both XFCE and KDE environments.
I have not tried in LXDE yet but I am about to try.
This issues is been opened in 2006, can you please change the severity
to "Medium" or "High" so that someone help us ?
Sebastien.
--
You received this bug notification because you
23 matches
Mail list logo
