[Touch-packages] [Bug 264313] Re: ls --color hangs for directories linked from network
I do think the fact that a workaround exists is not enough. I really think the default behaviour in Ubuntu of a oft-used command should not create hangs of well over a minute in fairly standard circumstances. It also hangs on links that are not accessible because they have not been Kerberos authenticated or are on unmounted USB devices. So I do think the default should at least be changed here. It is unreasonable default behaviour, not least because it is really unobvious to most users why it happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/264313 Title: ls --color hangs for directories linked from network Status in coreutils package in Ubuntu: Confirmed Bug description: Binary package hint: coreutils ls --color hangs for directories linked from network resources if those resources are not available I guess it hangs in trying to validate the link ( have not tried to wait and see if it times out or not ) easily reproducible. annoying since --color is default Running Ubuntu 8.0.4 2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux ls (GNU coreutils) 6.10 ISSUE: since ls --color will try to determine if a symlink is broken or not (so that it will be correctly coloured), it *will* timeout on vanished resources. WORKAROUND: Inhibit 'ls' from following symlinks (at least in the context of --color): eval `dircolors -b | sed s/or=[^:]*://` Add the above to your profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/264313/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
One last thing if I may: what do you think is better, restart of the service or reboot of the vps? except for the additional logging, is there something I should be aware of when editing the above? Thanks -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
Before doing so, is there anything I should be aware of like the consequence of such editing and restarting? You wrote reboot or restart, reboot you mean VPS and restart you mean systemd-logind service? Ofcourse I prefer to restart the service only and not the whole vps, is there a recommended way to do it without breaking anything? I ask because during my searches for the problem, I read that it should be done with cautious. Thanks -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I attached the xls because of the indentation problem. Here is the logind output in text (which is ok with indentation). ** Attachment added: "journal-logind.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+attachment/5331729/+files/journal-logind.txt -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I attached an excel file of the ps -alx command. Regarding the other command, It is long because of the problem :) here is its content Feb 07 10:09:08 vps.server.local systemd[1]: Starting Login Service... Feb 07 10:09:08 vps.server.local systemd-logind[122]: New seat seat0. Feb 07 10:09:08 vps.server.local systemd[1]: Started Login Service. Feb 07 10:09:19 vps.server.local systemd[1]: Stopping Login Service... Feb 07 10:09:19 vps.server.local systemd[1]: Stopped Login Service. Feb 07 10:09:33 vps.server.local systemd[1]: Starting Login Service... Feb 07 10:09:33 vps.server.local systemd-logind[104]: New seat seat0. Feb 07 10:09:33 vps.server.local systemd[1]: Started Login Service. Feb 07 10:10:45 vps.server.local systemd[1]: Stopping Login Service... Feb 07 10:10:45 vps.server.local systemd[1]: Stopped Login Service. Feb 07 10:11:03 vps48064754.local systemd[1]: Starting Login Service... Feb 07 10:11:04 vps48064754.local systemd-logind[163]: New seat seat0. Feb 07 10:11:04 vps48064754.local systemd[1]: Started Login Service. Feb 07 10:13:53 vps48064754.local systemd-logind[163]: New session c1 of user root. Feb 07 10:15:34 vps48064754.local systemd[1]: /lib/systemd/system/systemd-logind.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service' Feb 07 10:17:54 vps48064754.local systemd-logind[163]: New session c2 of user debian-spamd. Feb 07 10:18:23 vps48064754.local systemd-logind[163]: New session c3 of user debian-spamd. Feb 07 10:21:08 vps48064754.local systemd-logind[163]: Removed session c1. Feb 07 10:21:08 vps48064754.local systemd[1]: Stopping Login Service... Feb 07 10:21:08 vps48064754.local systemd[1]: Stopped Login Service. Feb 07 10:21:36 vps48064754.local systemd[1]: Starting Login Service... Feb 07 10:21:36 vps48064754.local systemd-logind[151]: New seat seat0. Feb 07 10:21:36 vps48064754.local systemd[1]: Started Login Service. Then a lot of Feb 07 10:56:52 vps48064754.local systemd-logind[151]: New session cxxx of user domain. Then Feb 07 18:19:18 vps48064754.local systemd[1]: Stopping
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I did loginctl terminate-user domain before so now I have 47 such sessions. domain@domain:~$ ps -alx F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4 0 1 0 20 0 232712 10960 ep_pol Ss ?152:21 /lib/systemd/systemd --system --deserialize 12 1 0 2 1 20 0 0 0 kthrea S? 0:00 [kthreadd/79baa9] 1 0 3 2 20 0 0 0 kthrea S? 0:00 [khelper] 4 105 139 1 20 0 189016 988 poll_s Ssl ? 0:03 /usr/sbin/rsyslogd -n 4 0 149 1 20 0 88660 19704 ep_pol Ss ? 1:32 /lib/systemd/systemd-logind 4 0 152 1 20 0 28344 376 hrtime Ss ? 0:02 /usr/sbin/cron -f 4 100 153 1 20 0 48428 1944 ep_pol Ss ? 2:57 /usr/bin/dbus-daemon --system --address=systemd: --4 0 163 1 20 0 196840 18732 poll_s Ssl ? 0:00 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork -1 0 204 1 20 0 10096880 skb_wa Ss ? 0:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix1 0 205 204 20 0 10096892 lock_f S? 0:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix5 118 261 1 20 0 76184 15964 poll_s Ss ? 0:00 postgrey --pidfile=/var/run/postgrey/postgrey.pid -4 106 478 1 20 0 287428 12804 sigsus Ssl ? 0:00 /usr/sbin/named -f -u bind 4 0 489 1 20 0 184288 7800 poll_s Ssl ? 0:00 /usr/bin/python3 /usr/share/unattended-upgrades/una4 0 505 1 20 0 1036648 13412 poll_s Ssl ? 39:19 /usr/bin/python3 /usr/bin/fail2ban-server -xf start4 0 523 1 20 0 72288 916 poll_s Ss ? 0:00 /usr/sbin/sshd -D 0 999 526 1 20 0 4192092 693668 futex_ Sl ? 42:25 /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Djava.1 0 542 1 20 0 24176 256 poll_s Ss ? 0:00 /usr/sbin/xinetd -pidfile /run/xinetd.pid -stayaliv5 0 555 1 20 0 400524 16044 poll_s Ss ? 0:44 /usr/sbin/apache2 -k start 1 0 579 1 20 0 81052 18024 poll_s Ss ? 0:12 /usr/bin/perl /usr/share/usermin/miniserv.pl /etc/u1 0 581 1 20 0 87416 15492 poll_s Ss ? 0:34 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/we533 3714 555 20 0 400956 9468 ep_pol S? 0:00 /usr/sbin/apache2 -k start 533 3716 555 20 0 400892 9352 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 0 5194 1 20 0 76500 1740 ep_pol Ss ? 0:00 /lib/systemd/systemd --user 5 0 5195 5194 20 0 261960 7528 sigtim S? 0:00 (sd-pam) 4 0 5342 1 20 0 289044 2016 poll_s Ssl ? 0:07 /usr/lib/policykit-1/polkitd --no-debug 4 101 5968 1 20 0 71848 156 ep_pol Ss ? 0:00 /lib/systemd/systemd-networkd 4 0 5975 1 20 0 197976 49068 ep_pol Ss ? 0:12 /lib/systemd/systemd-journald 4 0 6087 1 20 0 42092 308 ep_pol Ss ? 0:00 /lib/systemd/systemd-udevd 5 114 6831 1 20 0 120580 2148 poll_s Ss ? 0:02 proftpd: (accepting connections) 4 0 9525 5194 20 0 90368 224 poll_s SLs ? 0:00 /usr/bin/gpg-agent --supervised 1 0 9928 1 20 0 90368 288 poll_s Ss ? 0:00 gpg-agent --homedir /root/.gnupg --use-standard-soc533 10880 555 20 0 400964 9324 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 113 11187 1 20 0 302396 6484 pause Ss ? 0:08 /usr/bin/freshclam -d --foreground=true 533 11901 555 20 0 400688 8748 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 0 13481 1 20 0 13008 844 poll_s Ss+ ? 0:00 /sbin/agetty -o -p -- \u --noclear tty2 linux 4 0 13482 1 20 0 13008 844 poll_s Ss+ ? 0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud cons4 0 17557 523 20 0 101548 4356 poll_s Ss ? 0:00 sshd: domain [priv] 5 1000 17572 17557 20 0 101548 1960 poll_s R? 0:00 sshd: domain@pts/0 0 1000 17573 17572 20 0 18628 2128 wait Ss pts/0 0:00 -bash 0 1000 17583 17573 20 0 25936 1276 - R+ pts/0 0:00 ps -alx 4 0 18418 1 20 0 317440 1580 ep_pol Ss ? 0:34 php-fpm: master process (/etc/php/7.2/fpm/php-fpm.c533 18419 18418 20 0 317440 1452 skb_wa S? 0:00 php-fpm: pool www 533 18420 18418 20 0 317440 1448 skb_wa S? 0:00 php-fpm: pool www 533 22504 555 20 0 182440 5768 poll_s S? 0:00 /usr/sbin/apache2 -k start 533 23288 555 20 0 400988 9672 SYSC_s S? 0:00 /usr/sbin/apache2 -k start The command journalctl -b -u systemd-logind starts with Feb-07 so there are A LOT of records there. Maybe a grep of something will show only the important stuff? -- You
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
Looks "quiet" but I have 1994 sessions in "loginctl list-sessions" domain@domain:~$ ps -elx F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 5 1000 25901 25885 20 0 101548 1960 ? S? 0:00 sshd: domain@pts/0 0 1000 25902 25901 20 0 18628 2132 wait Ss pts/0 0:00 -bash USER=domain LOGNAME=domain HOME=/home/sto 0 1000 26403 25902 20 0 25936 1276 - R+ pts/0 0:00 ps -elx LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=4 domain@domain:~$ -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I login to domain user using ssh from time to time... as a "bonus", Virtualmin open/close a session for that same user to do its stuff: https://www.cloudmin.com/node/54674 The above is causing the number of ghost sessions to grow even more rapidly Regarding "ps -elx", just to make sure: you want me to run it while I connect (ssh) using domain user? -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I don't mean to sound rude, just want to understand how this is working. I gave it a week and now loginctl list-sessions have 1955 sessions like that and it keeps growing... How the bug reports are handled? Thanks -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: New Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Something similar here too, with DBUS crashing out, and not generating a complete core dump (though plenty of disk and RAM) un 17 00:10:40 xps15 gjs[2607]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 17 00:10:40 xps15 gjs[2607]: message repeated 8 times: [ g_object_unref: assertion 'G_IS_OBJECT (object)' failed] Jun 17 00:10:40 xps15 systemd[1991]: gnome-terminal-server.service: Main process exited, code=killed, status=15/TERM Jun 17 00:10:40 xps15 systemd[1991]: gnome-terminal-server.service: Succeeded. Jun 17 00:10:45 xps15 gsd-print-notif[2333]: Source ID 3 was not found when attempting to remove it Jun 17 00:10:45 xps15 kernel: [ 8851.668166] rfkill: input handler enabled Jun 17 00:10:45 xps15 systemd[1]: unattended-upgrades.service: Succeeded. Jun 17 00:10:45 xps15 systemd[1991]: Stopping D-Bus User Message Bus... Jun 17 00:10:45 xps15 systemd[1991]: at-spi-dbus-bus.service: Succeeded. Jun 17 00:10:45 xps15 gnome-session[2037]: gnome-session-binary[2037]: WARNING: Lost name on bus: org.gnome.SessionManager Jun 17 00:10:45 xps15 gnome-session[2037]: gnome-session-binary[2037]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 17 00:10:45 xps15 gnome-session-binary[2037]: WARNING: Lost name on bus: org.gnome.SessionManager Jun 17 00:10:45 xps15 gnome-session-binary[2037]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 17 00:10:45 xps15 gvfsd[2182]: A connection to the bus can't be made Jun 17 00:10:45 xps15 gnome-shell[2175]: [AppIndicatorSupport-DEBUG] Lost nameorg.kde.StatusNotifierWatcher Jun 17 00:10:45 xps15 gnome-shell[2175]: JS WARNING: [resource:///org/gnome/gjs/modules/signals.js 128]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1 Jun 17 00:10:45 xps15 systemd[1991]: run-user-1000-gvfs.mount: Succeeded. Jun 17 00:10:45 xps15 systemd[1991]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM Jun 17 00:10:45 xps15 systemd[1991]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE Jun 17 00:10:45 xps15 tracker-miner-f[2474]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Jun 17 00:10:45 xps15 systemd[1991]: xdg-permission-store.service: Failed with result 'exit-code'. Jun 17 00:10:45 xps15 tracker-miner-f[2474]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Jun 17 00:10:45 xps15 systemd[1991]: gvfs-metadata.service: Succeeded. Jun 17 00:10:45 xps15 kernel: [ 8851.715910] dbus-daemon[2029]: segfault at 0 ip 7fcf20d73e53 sp 7ffefaadc258 error 6 in libdbus-1.so.3.19.9[7fcf20d51000+2d000] Jun 17 00:10:45 xps15 kernel: [ 8851.715930] Code: 89 12 48 89 52 08 48 89 17 c3 0f 1f 44 00 00 48 89 d6 e9 80 fe ff ff 48 8b 46 08 48 39 f0 74 47 48 8b 16 48 89 42 08 48 8b 16 <48> 89 10 48 39 37 74 15 48 c7 46 08 00 00 00 00 48 c7 06 00 00 00 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: Invalid Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=
[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade
I just encountered this bug today when upgrading from a fully updated 14.04 server to 16.04 using do-release-upgrade. My static IP configured in /etc/network/interfaces was configured to come up on eth0. Logging in on the console and replacing eth0 with ens32 in that interfaces file and rebooting fixed things. -- 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/1550539 Title: VMWare network interface name change with wily → xenial upgrade Status in systemd package in Ubuntu: Fix Released Bug description: Hi, I just (2016-02-26) upgraded from wily to xenial in my VMWare VM. The network interface name changed but the upgrade process didn't change /etc/network/interfaces. As such I was left without networking. This may be related to bug #1473542, but obviously isn't the same. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Feb 26 16:54:47 2016 InstallationDate: Installed on 2015-10-29 (120 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic root=UUID=9b4f66d9-95e1-45ff-b167-8ce887475c7e ro elevator=noop SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-02-26 (0 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1550539/+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 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports
This is fixed in the squid package now available in Xenial.
** Changed in: squid3 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1414754
Title:
/etc/logrotate.d/squid3 fails to execute sarg-reports
Status in logrotate package in Ubuntu:
Confirmed
Status in squid3 package in Ubuntu:
Fix Released
Bug description:
In Edubuntu 14.04 LTS, by default, the /etc/logrotate.d/squid3 file is
set to rotate the logs in a daily basis but it doesn't specifies that
to sarg-reports command.
/var/log/squid3/*.log {
daily
compress
delaycompress
rotate 2
missingok
nocreate
sharedscripts
prerotate
test ! -x /usr/sbin/sarg-reports || /usr/sbin/sarg-reports
endscript
postrotate
test ! -e /var/run/squid3.pid || test ! -x /usr/sbin/squid3
|| /usr/sbin/squid3 -k rotate
endscript
}
As consequence, sarg-reports fails to do its job and anacron reports
the following message:
/etc/cron.daily/logrotate:
SARG - Daily / Weekly / Monthly - Squid proxy usage reports creation tool
Written by Ugo Viti
Version: 20050202
Usage: /usr/sbin/sarg-reports [OPTIONS]
Allowed options:
manual, Create Manual report
today, Create Today report
daily, Create Daily report
weekly, Create Weekly report
monthly, Create Monthly report
A possible solution would be to add the rotation frequency required by
sarg-reports command as argument to it.
/var/log/squid3/*.log {
daily
compress
delaycompress
rotate 2
missingok
nocreate
sharedscripts
prerotate
test ! -x /usr/sbin/sarg-reports || /usr/sbin/sarg-reports
daily
endscript
postrotate
test ! -e /var/run/squid3.pid || test ! -x /usr/sbin/squid3
|| /usr/sbin/squid3 -k rotate
endscript
}
In a Squid3+Sarg configuration, it may be convenient to change the log
rotation frequency from daily to monthly, so sarg has more information
to work with in a single /var/log/squid3/access.log file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1414754/+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 1538221] Re: Monitors on DisplayPort do not wake from sleep
Chris - I would totally love to do that, however apport gets stuck and freezes during the collection process. Is there any way I can get you the information you need manually? (I suspect the freeze is related to the issue I reported -- several times, I've had freezes calling xrandr or other x- apps to try to get information about the state of the monitors.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1538221 Title: Monitors on DisplayPort do not wake from sleep Status in xorg package in Ubuntu: Incomplete Bug description: Potentially related: http://askubuntu.com/questions/546818/displayport-monitor-not-detected-if-switched-off-and-on-again https://bugs.freedesktop.org/show_bug.cgi?id=88063 http://superuser.com/questions/945362/displayport-link-failure-after-monitor-sleep I have three monitors plugged into an ATI HD 7950, one through DVI, the others through DisplayPort, via dual-link adapters. When KDE puts the monitors to sleep, only the DVI monitor wakes up, not the DisplayPort monitors. xrandr shows all three monitors on. xset dpms force on does not work. Using xrandr to change the resolution and change it back does not work. Logging out and logging back in does not work. Trying to switch to CLI with shift-alt-f1, I see a console, but it shows the bootlog (on the DVI monitor), without a login prompt. Trying to log out and log back in, lightdm behaves as though the other two monitors are on, but only displays on the DVI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538221/+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 1538221] Re: Monitors on DisplayPort do not wake from sleep
I'd really prefer to execute commands and provide the results, if that's at all possible. (And apport is still going, perhaps it'll unfreeze in a few hours.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1538221 Title: Monitors on DisplayPort do not wake from sleep Status in xorg package in Ubuntu: Incomplete Bug description: Potentially related: http://askubuntu.com/questions/546818/displayport-monitor-not-detected-if-switched-off-and-on-again https://bugs.freedesktop.org/show_bug.cgi?id=88063 http://superuser.com/questions/945362/displayport-link-failure-after-monitor-sleep I have three monitors plugged into an ATI HD 7950, one through DVI, the others through DisplayPort, via dual-link adapters. When KDE puts the monitors to sleep, only the DVI monitor wakes up, not the DisplayPort monitors. xrandr shows all three monitors on. xset dpms force on does not work. Using xrandr to change the resolution and change it back does not work. Logging out and logging back in does not work. Trying to switch to CLI with shift-alt-f1, I see a console, but it shows the bootlog (on the DVI monitor), without a login prompt. Trying to log out and log back in, lightdm behaves as though the other two monitors are on, but only displays on the DVI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538221/+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 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor
I see this too every so often... but I am usually able to recover the pointer with a suspend then resume. XPS13 9343 $ uname -a Linux flexi 3.19.0-33-generic #38-Ubuntu SMP Fri Nov 6 18:18:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*release* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu 15.04" NAME="Ubuntu" VERSION="15.04 (Vivid Vervet)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 15.04" VERSION_ID="15.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1467595 Title: cursor sometimes disappears on XPS 13 9343 and external monitor Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. Occasionally, the mouse cursor disappears (sometimes after screen lock, other times just normal usage). I saw something on stack exchange that said this might help: gsettings set org.gnome.settings-daemon.plugins.cursor active false I've done this and it sometimes helps and sometimes doesn't. I've also just seen the cursor come back on its own after a few minutes without doing anything. Trying to interact with the touch screen, then the mouse has no effect. Unplugging and replugging the mouse has no effect. Using the touchpad has no effect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:19:40 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1467595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
Yes, I'm experiencing the same thing. After a lock screen, my windows all move back onto one monitor. The main monitor has had the resolution dropped from 3840x2160 -- 2560x1440 Linux worky 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux unity 7.3.2 Graphics: Card: NVIDIA GK104GLM [Quadro K3000M] bus-ID: 01:00.0 Display Server: X.Org 1.17.1 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@59.9hz, 1920x1080@60.0hz, 2560x1440@60.0hz GLX Renderer: Quadro K3000M/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 346.59 Direct Rendering: Yes $ xrandr Screen 0: minimum 8 x 8, current 5560 x 1920, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) DP-0 connected primary 1080x1920+2560+0 left (normal left inverted right x axis y axis) 531mm x 298mm 1920x1080 59.9*+ 1680x1050 60.0 1600x1200 60.0 1440x900 59.9 1280x1024 60.0 1280x960 60.0 1280x800 59.8 1024x768 60.0 800x60060.3 56.2 640x48059.9 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected 1920x1080+3640+13 (normal left inverted right x axis y axis) 382mm x 215mm 1920x1080 60.0*+ DP-5 disconnected (normal left inverted right x axis y axis) DP-6 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 607mm x 345mm 3840x2160 60.0 + 2560x1440 60.0* 1920x1080 60.0 59.9 1680x1050 60.0 1600x900 60.0 1440x900 59.9 1280x1024 75.0 60.0 1280x800 59.8 1280x720 60.0 1152x864 75.0 1024x768 75.0 70.1 60.0 800x60075.0 72.2 60.3 56.2 640x48075.0 72.8 59.9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+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 1072206] Re: [nvidia] Window content is black or transparent
Celebration! Thanks Andrea and to all others involved. And thanks to those at Nvidia for nailing the reason, even given the problem was with compiz. Nvidia seem to be coming true on their recent promises. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: In Progress Status in Compiz 0.9.11 series: Triaged Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Ubuntu 12.10 64bit (updated from 12.04) / NVIDIA GeForce 8 proprietary driver. This bug happens to me from 12.04 from some update I think. It appears mostly when I open a new application and only ocassionally. As temporary solution creating some other event like opening Unity dash or opening some next window, etc. fix it. Then window content is refreshed and I can see all correctly. Same with stable and experimental nvidia drivers. Screenshot of this bug is attached. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] je adresářem: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.48 Sun Sep 9 20:22:27 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sat Oct 27 23:00:14 2012 DistUpgraded: 2012-10-23 19:34:29,842 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-experimental-304, 304.48, 3.5.0-17-generic, x86_64: installed virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:3468] InstallationDate: Installed on 2012-08-29 (59 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) JockeyStatus: kmod:nvidia_experimental_304 - nvidia_experimental_304 (Proprietary, Enabled, Not in use) kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_173_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=3ae94b68-4a0c-4633-aec7-b4ed25a23003 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-23 (4 days ago) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 05/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0208 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0208:bd05/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.8.4-0ubuntu3
[Touch-packages] [Bug 1403275] [NEW] i915 display driver causes crash back to login window
Public bug reported:
I've just installed Ubuntu 14.04 server on Dell Latitude E7440 and then
installed Cinnamon 2.4.5 on top of it. The laptop has an external
monitor connected through Display Port and a docking station.
On the first day the system worked perfectly.
On the second day, the system booted to the login screen (leaving the
external screen empty but otherwise seemed to be under X11's control),
it then let me type my username and password but then X exits, shows a
bit of VT1 with errors then gets back to the login page.
I found the following error in /var/log/kern.log:
[drm:intel_dp_complete_link_train] ERROR failed to train DP, aborting
I found a page which claims to solve this error for 12.04 in the second
comment in
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=73694#c2.
I found that the file linux-
source-3.13.0/drivers/gpu/drm/i915/intel_dp.c, which is included in the
tar file /usr/src/linux-source-3.13.0.tar.bz2 (also copied in /usr/src
/linux-source-3.13.0/linux-source-3.13.0.tar.bz2), from the kernel
source package linux-source-3.13.0, contains the pre-patch lines
mentioned in the fix above.
Would you please consider including this fix in the Ubuntu kernel?
Thanks,
--Amos
For completeness, the patch pointed to from the link above is:
Link: https://www.libreoffice.org/bugzilla/attachment.cgi?id=92231
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 8f17f8fbd0b1..5631cfb874db 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -847,8 +847,8 @@ intel_dp_compute_config(struct intel_encoder *encoder,
mode_rate = intel_dp_link_required(adjusted_mode-crtc_clock,
bpp);
- for (clock = 0; clock = max_clock; clock++) {
- for (lane_count = 1; lane_count = max_lane_count;
lane_count = 1) {
+ for (lane_count = 1; lane_count = max_lane_count; lane_count
= 1) {
+ for (clock = 0; clock = max_clock; clock++) {
link_clock =
drm_dp_bw_code_to_link_rate(bws[clock]);
link_avail = intel_dp_max_data_rate(link_clock,
lane_count);
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Dec 17 12:57:10 2014
InstallationDate: Installed on 2014-12-15 (1 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64
(20140722.3)
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug crash trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1403275
Title:
i915 display driver causes crash back to login window
Status in xorg package in Ubuntu:
New
Bug description:
I've just installed Ubuntu 14.04 server on Dell Latitude E7440 and
then installed Cinnamon 2.4.5 on top of it. The laptop has an external
monitor connected through Display Port and a docking station.
On the first day the system worked perfectly.
On the second day, the system booted to the login screen (leaving the
external screen empty but otherwise seemed to be under X11's control),
it then let me type my username and password but then X exits, shows a
bit of VT1 with errors then gets back to the login page.
I found the following error in /var/log/kern.log:
[drm:intel_dp_complete_link_train] ERROR failed to train DP, aborting
I found a page which claims to solve this error for 12.04 in the
second comment in
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=73694#c2.
I found that the file linux-
source-3.13.0/drivers/gpu/drm/i915/intel_dp.c, which is included in
the tar file /usr/src/linux-source-3.13.0.tar.bz2 (also copied in
/usr/src/linux-source-3.13.0/linux-source-3.13.0.tar.bz2), from the
kernel source package linux-source-3.13.0, contains the pre-patch
lines mentioned in the fix above.
Would you please consider including this fix in the Ubuntu kernel?
Thanks,
--Amos
For completeness, the patch pointed to from the link above is:
Link: https://www.libreoffice.org/bugzilla/attachment.cgi?id=92231
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 8f17f8fbd0b1..5631cfb874db 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -847,8 +847,8 @@ intel_dp_compute_config(struct intel_encoder *encoder,
mode_rate = intel_dp_link_required
