[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Re #42; pardon; machine-confusion. The problem with 4.15.0-72 indeed but on a Xeon E5606, AMD HD 5770 graphics -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Re #41, "Can anyone else confirm?" For me and for a few other reports out there, the problem *started* with 4.15.0-72. Core 2 Duo with old G45 onboard graphics. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
So glad I took the time to report this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Upstream seems silent; bug remains in NEW state and no follow-up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Actually, no, that doesn't work for me. Was expecting it would given the comments on the samba bug, but, well, no. It *does* work to send HUP once booted: rene@t5500:~$ ping WD-NETCENTER ping: WD-NETCENTER: Name or service not known rene@t5500:~$ sudo kill -HUP $(systemctl show winbind -p MainPID --value) rene@t5500:~$ ping WD-NETCENTER PING WD-NETCENTER (192.168.1.33) 56(84) bytes of data. 64 bytes from fs7-netcenter (192.168.1.33): icmp_seq=1 ttl=64 time=1.86 ms It seems the networkd-dispatcher script is still too early. Must by the way also admit I'd maybe not consider it a better workaround even it if did work than just waiting for network-online.target; nmbd as mentioned already does as well, so only people with minimal Windows- networking needs or wants would get any potential benefit from NOT simply waiting for network-online.target. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
As to the reply you got on https://bugzilla.samba.org/show_bug.cgi?id=13607, I can deny a "net cache flush" doing anything to get WINS name resolving going for me when booted with the original service file: rene@t5500:~$ ping WD-NETCENTER ping: WD-NETCENTER: Name or service not known rene@t5500:~$ net cache flush rene@t5500:~$ ping WD-NETCENTER ping: WD-NETCENTER: Name or service not known -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "winbind.service-working" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185183/+files/winbind.service-working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Thanks much for checking. I see; I was expecting this to be an
"immediately obvious" sort of thing to someone with unlike me an actual
clue about samba/winbind, but I have with the above guidance nos
supplied more information.
Specifically, it would appear that your explicitly mentioned "wins
server" configuration will be the difference. I never expected my
/etc/samba/smb.conf to be relevant since mine is fully vanilla, as
provided by the "samba-common" package. It is also attached, but:
rene@t5500:~$ debsums samba-common | grep /usr/share/samba/smb.conf
/usr/share/samba/smb.conf OK
rene@t5500:~$ cmp /usr/share/samba/smb.conf /etc/samba/smb.conf
rene@t5500:~$
This is to say that I do not in fact have a WINS server specified; that
judging by the logs my winbind is relying on broadcasts, and bombing out
in that case if started before network-online.target.
There's two logs attached with "debug level = 5", one log.winbindd-
nonworking and one log.winbindd-working, in which "nonworking" is
without /etc/systemd/system/winbind.service (i.e., default) and working
with.
In the nonworking situation the log shows:
[2018/09/05 22:44:21.132692, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'winbindd' finished starting up and ready to serve connections
[2018/09/05 22:44:42.487584, 3]
../source3/winbindd/winbindd_misc.c:395(winbindd_interface_version)
[ 1917]: request interface version (version = 29)
[2018/09/05 22:44:42.487775, 3]
../source3/winbindd/winbindd_misc.c:428(winbindd_priv_pipe_dir)
[ 1917]: request location of privileged pipe
[2018/09/05 22:44:42.487995, 3]
../source3/winbindd/winbindd_wins_byname.c:56(winbindd_wins_byname_send)
[ 1917]: wins_byname WD-NETCENTER
[2018/09/05 22:44:42.488050, 3]
../source3/libsmb/namequery.c:2142(resolve_wins_send)
resolve_wins: WINS server resolution selected and no WINS servers listed.
[2018/09/05 22:44:42.488086, 3]
../source3/libsmb/namequery.c:1880(name_resolve_bcast_send)
name_resolve_bcast: Attempting broadcast lookup for name WD-NETCENTER<0x20>
and silence after that, whereas in the working situation:
[2018/09/05 22:39:51.454142, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'winbindd' finished starting up and ready to serve connections
[2018/09/05 22:40:41.498139, 3]
../source3/winbindd/winbindd_misc.c:395(winbindd_interface_version)
[ 1992]: request interface version (version = 29)
[2018/09/05 22:40:41.498346, 3]
../source3/winbindd/winbindd_misc.c:428(winbindd_priv_pipe_dir)
[ 1992]: request location of privileged pipe
[2018/09/05 22:40:41.498570, 3]
../source3/winbindd/winbindd_wins_byname.c:56(winbindd_wins_byname_send)
[ 1992]: wins_byname WD-NETCENTER
[2018/09/05 22:40:41.498627, 3]
../source3/libsmb/namequery.c:2142(resolve_wins_send)
resolve_wins: WINS server resolution selected and no WINS servers listed.
[2018/09/05 22:40:41.498676, 3]
../source3/libsmb/namequery.c:1880(name_resolve_bcast_send)
name_resolve_bcast: Attempting broadcast lookup for name WD-NETCENTER<0x20>
[2018/09/05 22:40:41.499722, 4]
../source3/libsmb/nmblib.c:108(debug_nmb_packet)
nmb packet from 192.168.1.33(35072) header: id=7546 opcode=Query(0)
response=Yes
header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
answers: nmb_name=WD-NETCENTER<20> rr_type=32 rr_class=1 ttl=259200
answers 0 char .! hex C0A80121
[2018/09/05 22:40:41.499808, 2]
../source3/libsmb/namequery.c:1430(name_query_validator)
Got a positive name query response from 192.168.1.33 ( 192.168.1.33 )
The accompanying -nonworking and -working service files are also
attached but their only difference is as already described:
rene@t5500:~$ diff -u /{lib,etc}/systemd/system/winbind.service
--- /lib/systemd/system/winbind.service 2018-08-06 13:30:25.0 +0200
+++ /etc/systemd/system/winbind.service 2018-09-05 22:12:10.650061750 +0200
@@ -1,7 +1,8 @@
[Unit]
Description=Samba Winbind Daemon
Documentation=man:winbindd(8) man:samba(7) man:smb.conf(5)
-After=network.target nmbd.service
+After=network-online.target nmbd.service
+Wants=network-online.target
[Service]
Type=notify
So, I guess it's broadcasts that need network-online.target. Seeing as
how relying on those is the vanilla situation I take it this still means
the "winbind" package wants the service file adjustment?
** Attachment added: "log.winbindd-nonworking"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185180/+files/log.winbindd-nonworking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubuntu 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "log.winbindd-working" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185181/+files/log.winbindd-working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "winbind.service-nonworking" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185184/+files/winbind.service-nonworking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "log.winbindd-nonworking" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185182/+files/log.winbindd-nonworking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Oh, and the mentioned vanilla smb.conf... ** Attachment added: "smb.conf" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185185/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Just to add: the issue's the same and fully constant on an Intel Xeon E5606 @2,13GHz with 8GiB running Mint 19 Cinnamon 64-bit, and an Intel Core 2 Duo E8400 @ 3GHz withj 4GiB running Mint 19 Xfce 64-bit. That is... it's not a subtle race and I assume anyone will see this if installing only "winbind" and not the rest of "samba". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Yes, the network itself comes up fine. "Does not work" simply means that NetBIOS name resolution is unavailable even after it does; that e.g. "ping NAS" for "NAS" the NetBIOS name of my, well, NAS, tells me the name cannot be resolved. There would not appear to be relevant logs nor configuration files. The issue is simply that with "After=network.target" rather then "After =network-online.target" the winbindd daemon is started too early; does start, but does not work. Needs to be restarted for it to start to work. I am as mentioned on Linux Mint 19 but would be surprised if this were not the case on Ubuntu 18.04 itself as well. This is a standard, wired desktop without even wireless available. It is easy to reproduce: have the "winbind" and "libnss-winbind" packages installed but not "samba" itself, enable WINS name resolution in /etc/nsswitch.con as detailed and as normal, and reboot. As also mentioned, installing "samba" itself hides the issue by winbind having a dependency on nmbd and nmbd in turn on network-online.target; without "samba", we appear to have a simple systemd bootup race, solved by having it depend on network-online.target itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] [NEW] winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Public bug reported:
[copied from the Linux Mint forum]
Just installed Mint 19 and noticed a WINS name resolution buglet. I
assume this applies to Ubuntu 18.04 as well.
Windows, i.e., NetBIOS, name resolution is on Linux provided for by the
"winbindd" daemon, part of the Samba suite. One does not need either of
the other two Samba daemons "smbd" and "nmbd" when NetBIOS name
resolution is all you need: sudo apt-get install libnss-winbind (which
additionally pulls in "winbind" itself) and adding "wins" before "dns"
to the "hosts" line of /etc/nsswitch.conf is enough.
While this works fine directly after installation it does no more after
reboot due to a systemd unit file dependency issue. The standard
/lib/systemd/system/winbind.service orders itself after "network.target"
and "nmbd.service" which if you do not in fact have "samba" hence
"nmbd.service" installed amounts to "network.target" only. It however
needs "network-online.target" -- itself a dependency of "smbd.service"
if you do have that installed as well.
You can solve things by copying the unit file to its corresponding
directory under /etc and editing it,
sudo cp /{lib,etc}/systemd/system/winbind.service
xed admin:/etc/systemd/system/winbind.service
to change the line
After=network.target nmbd.service
to the two lines
After=network-online.target nmbd.service
Wants=network-online.target
After save and reboot you will have NetBIOS name resolution functional
without all of the rest of Samba running.
Note that although this fix is not needed when you do have "samba"
itself installed the above is still fine also the
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubuntu 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310489] Re: xorg.conf overwritten by booting system
Also affected, although nothing to do with a multi-gpu system. Mint 17.3 (64-bit, Cinnamon) and a local /etc/X11/xorg.conf to slow down my crazy- fast Logitech mouse. Installing fglrx renamed xorg.conf to xorg.conf- DATE (and put nothing in its place). Not a huge problem in this case, but certainly rather uncourteous of it. If this is an involved problem, perhaps at least this specific situation could be worked around by not moving xorg.conf out of the way if it isn't being replaced by anything. That is, I imagine it could be generally troublesome to merge a local configuration, but merging with a new /empty/ configuration is not. If a new xorg.conf is in fact generated, maybe a user warning if an old one was also found... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1310489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071530]
Ouch, that's painful. I just found out that Wayland also uses mesa... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071530 Title: X Error of failed request: BadAlloc (insufficient resources for operation) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1071530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071530]
This specific issue has been fixed (for me, Intel 865G on arch linux) in mesa-9.1-2 which is at the time of writing in the testing repository. 9.1 does regress with respect to 8.0 (ie, "Speed Dreams" just crashed on me, which it didn't use to) but that sort of thing is just business as usual for older intel. In two releases time, nothing will work anymore again, so let's count our blessings for now. Or rather, I guess from the reply one above, let's count the number of opensuse users -- and prey to god it stays above 1000 so that the pack of drug-crazed baboons that have been fucking up 3D on older intel on basically each and every release for multiple years now keeps getting told so by en entity with a cool corporate presence. Or something. Go Wayland go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071530 Title: X Error of failed request: BadAlloc (insufficient resources for operation) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1071530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
