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
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.ne
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
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
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
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:~$
** 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.n
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
serv
** 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/bug
** 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.launc
** 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.n
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://bug
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 "winbi
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 f
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 no
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 certainl
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
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 o
18 matches
Mail list logo
