when will this be in the main repositories?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741934
Title:
Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for
PTI fix)
To manage
running an Apache2 server with NTLM authentication against an AD,
stopped working with 500 Internal Server error since the Samba upgrade.
Apache config:
AuthType NTLM
AuthName "..."
NTLMAuth on
NTLMAuthHelper "/usr/bin/ntlm_auth --helper-protocol=squid-.5-ntlmssp"
NTLMBasicAuthoritative on
running on a fresh Mint 15 install here, albeit with a /home directory
from a former LMDE install.
After replacing the file from post #38, categories get highlighted, but
no applications show. Search field does not work: I can type, but
nothing is found, categories only fade out.
After I renamed
Post №6 solved the problem for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/485949
Title:
TeX/LaTeX/pdfLaTeX binaries not working over CIFS/SAMBA shares
To manage notifications about
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/886048
Title:
“check password script” option does not reliably pass
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886048
Title:
“check password script” option does not reliably pass parameters
To manage
does not work for me in either lucid or onoeric. No GPT here and only
8GB (virtual, test) harddrives. Please reopen!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681535
Title:
Auto-detection of a
sure, here it is! Thank you for your attention.
** Attachment added: checkpw.sh
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/886048/+attachment/2655076/+files/checkpw.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
sure, here it is! Thank you for your attention.
** Attachment added: checkpw.sh
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/886048/+attachment/2655076/+files/checkpw.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
the purpose of my “check password script” is, amongst others, to check
if a new password contains relevant portions of the username. Therefore,
it is called like this from smb.conf:
check password script = /usr/local/sbin/checkpw.sh %U
I did expect it to pass the username
Public bug reported:
the purpose of my “check password script” is, amongst others, to check
if a new password contains relevant portions of the username. Therefore,
it is called like this from smb.conf:
check password script = /usr/local/sbin/checkpw.sh %U
I did expect it to pass the username
It is still not working as expected with Lucid.
And it's breaking a script of mine, sending every instance to an
endless, CPU eating loop…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/354793
Public bug reported:
from the smb.conf man page:
check password script (G)
The name of a program that can be used to check password complexity.
The password is
sent to the program's standard input.
The program must return 0 on a good password, or any other
Sorry! The option has to be set on the server where the password
actually will be changed!
I was testing this on a server with a slave LDAP directory.
** Changed in: samba (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
from the smb.conf man page:
check password script (G)
The name of a program that can be used to check password complexity.
The password is
sent to the program's standard input.
The program must return 0 on a good password, or any other
Sorry! The option has to be set on the server where the password
actually will be changed!
I was testing this on a server with a slave LDAP directory.
** Changed in: samba (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hm! Seems I was using an old, pre-release version of server iso. It
seems to work fine with a newly-downloaded version.
** Changed in: debian-installer (Ubuntu)
Status: New = Invalid
--
Lucid Preseed: GRUB location disregarded
https://bugs.launchpad.net/bugs/605454
You received this bug
Public bug reported:
Binary package hint: debian-installer
I created a CD for automatic installation of Lucid servers using the
preseed template file from https://help.ubuntu.com/10.04/installation-
guide/example-preseed.txt.
Now I need to have a high-capacity installation source. “No big
** Description changed:
I downloaded the DVD iso file from
http://cdimage.ubuntu.com/dvd/current/ and tried to install it. The
installation failed like this:
Debbootstrap warning.
Warning:
file:///cdrom/pool/main/z/zlib/zlib1g_1.2.3.3.dfsg-15ubuntu1_amd64.deb was
corrupt
and
Public bug reported:
I downloaded the DVD iso file from
http://cdimage.ubuntu.com/dvd/current/ and tried to install it. The
installation failed like this:
Debbootstrap warning.
Warning: file:///cdrom/pool/main/z/zlib/zlib1g_1.2.3.3.dfsg-15ubuntu1_amd64.deb
was corrupt
and then some consecutive
** Attachment added: package from the official DVD iso
http://launchpadlibrarian.net/48818022/zlib1g_1.2.3.3.dfsg-15ubuntu1_amd64-corrupt.deb
--
Ubuntu 10.04 DVD: install fails due to corrupt zlib1g package
https://bugs.launchpad.net/bugs/583362
You received this bug notification because
Public bug reported:
Binary package hint: update-manager
I am unsure what this may be. Seems a common error during upgrade, bug
reports about this are often marked as “invalid” by the maintainers.
I'll file this report either way because the software asks me for it.
** Affects: update-manager
** Attachment added: apt.log
http://launchpadlibrarian.net/48265108/apt.log
--
update-manager reports “some updates could not be installed… your system is in
an unusuable state… please report this bug”.
https://bugs.launchpad.net/bugs/578724
You received this bug notification because you
** Attachment added: apt.log
http://launchpadlibrarian.net/48265125/apt.log
** Attachment removed: apt.log
http://launchpadlibrarian.net/48265108/apt.log
--
update-manager reports “some updates could not be installed… your system is in
an unusuable state… please report this bug”.
** Attachment added: apt-term.log
http://launchpadlibrarian.net/48265148/apt-term.log
--
update-manager reports “some updates could not be installed… your system is in
an unusuable state… please report this bug”.
https://bugs.launchpad.net/bugs/578724
You received this bug notification
** Attachment added: lspci.txt
http://launchpadlibrarian.net/48265152/lspci.txt
--
update-manager reports “some updates could not be installed… your system is in
an unusuable state… please report this bug”.
https://bugs.launchpad.net/bugs/578724
You received this bug notification because
** Attachment added: system_state.tar.gz
http://launchpadlibrarian.net/48265178/system_state.tar.gz
--
update-manager reports “some updates could not be installed… your system is in
an unusuable state… please report this bug”.
https://bugs.launchpad.net/bugs/578724
You received this bug
** Attachment added: main.log
http://launchpadlibrarian.net/48265171/main.log
--
update-manager reports “some updates could not be installed… your system is in
an unusuable state… please report this bug”.
https://bugs.launchpad.net/bugs/578724
You received this bug notification because you
** Attachment added: term.log
http://launchpadlibrarian.net/48265200/term.log
--
update-manager reports “some updates could not be installed… your system is in
an unusuable state… please report this bug”.
https://bugs.launchpad.net/bugs/578724
You received this bug notification because you
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Does setting preserve case=no solve your issues ?
No, as “touch test.test ; touch TEST.test” still creates two separate
files.
Anyhow, “touch file.test ; ls FILE.test” (correctly) returns FILE.test?
--
case sensitivity option (case sensitive=no) is not honored
–– more importantly, with “preserve case = no” it is seems to be
impossible to create mixed-case file names; but only from Windows, LINUX
does allow this…?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification
My conclusion for now:
Does setting preserve case=no solve your issues ?
YES, BUT it creates a new critical issue. With this option, it is no
longer possible to create files with the case that the file passes (see
smb.conf). They are forced to be the default case (lower).
--
case sensitivity
hm… might “short preserve case = no” be the key?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
** Changed in: samba (Ubuntu)
Status: New = Invalid
** Description changed:
Binary package hint: samba
In my setup using samba's “case sensitive = no” option it is not
possible for Windows machines to create files with the same filename but
different cases. Example: “file.test”
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Does setting preserve case=no solve your issues ?
No, as “touch test.test ; touch TEST.test” still creates two separate
files.
Anyhow, “touch file.test ; ls FILE.test” (correctly) returns FILE.test?
--
case sensitivity option (case sensitive=no) is not honored
–– more importantly, with “preserve case = no” it is seems to be
impossible to create mixed-case file names; but only from Windows, LINUX
does allow this…?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification
My conclusion for now:
Does setting preserve case=no solve your issues ?
YES, BUT it creates a new critical issue. With this option, it is no
longer possible to create files with the case that the file passes (see
smb.conf). They are forced to be the default case (lower).
--
case sensitivity
hm… might “short preserve case = no” be the key?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: samba (Ubuntu)
Status: New = Invalid
** Description changed:
Binary package hint: samba
In my setup using samba's “case sensitive = no” option it is not
possible for Windows machines to create files with the same filename but
different cases. Example: “file.test”
Public bug reported:
Binary package hint: samba
In my setup using samba's “case sensitive = no” option it is not
possible for Windows machines to create files with the same filename but
different cases. Example: “file.test” can not reside next to
“FILE.test”.
However, when a LINUX client
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43896901/Dependencies.txt
** Attachment added: SambaInstalledVersions.txt
http://launchpadlibrarian.net/43896902/SambaInstalledVersions.txt
--
case sensitivity option (case sensitive=no) is not honored
I disagree.
The problem is that when, for example, two files “test.test” and
“test.TEST” are being addressed they should be treated as the exact same
file, as case sensitivity should be off and SAMBA should not care about
letter cases. They do when being addressed by a Windows (7) machine, in
my
Public bug reported:
Binary package hint: samba
In my setup using samba's “case sensitive = no” option it is not
possible for Windows machines to create files with the same filename but
different cases. Example: “file.test” can not reside next to
“FILE.test”.
However, when a LINUX client
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43896901/Dependencies.txt
** Attachment added: SambaInstalledVersions.txt
http://launchpadlibrarian.net/43896902/SambaInstalledVersions.txt
--
case sensitivity option (case sensitive=no) is not honored
I disagree.
The problem is that when, for example, two files “test.test” and
“test.TEST” are being addressed they should be treated as the exact same
file, as case sensitivity should be off and SAMBA should not care about
letter cases. They do when being addressed by a Windows (7) machine, in
my
Another occurence here.
--
TeX/LaTeX/pdfLaTeX binaries not working over CIFS/SAMBA shares
https://bugs.launchpad.net/bugs/485949
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This is affecting me too, also in an installation on a physical machine.
The error does *not* occur when installing without proper network
connection (I suspect the error comes from a package updated during
installation). But it *does* when dist-upgrading afterwards.
--
lucid server alpha2 grub
49 matches
Mail list logo
