Thanks for the bug report, Kevin.
I followed your instructions on how to reproduce it, but failed. The
auto-login feature is working in my pristine Groovy VM even after I
fully upgrade the system and install sssd.
What Lucas pointed above is indeed strange: you could be facing some
unrelated
Thanks for the bug report.
This happens because of how systemd handles /var/run/. If you look at
the directory, you will see that it is actually a symlink to /run/.
This directory is populated on every boot. There are a few ways that
packages can choose in order to create directories under this
Verification for Groovy:
First, verifying that the bug manifests itself:
# apt policy node-uid-number
node-uid-number:
Installed: 0.0.6-1
Candidate: 0.0.6-1
Version table:
*** 0.0.6-1 500
500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
100
Verification for Focal:
First, verifying that the bug manifests itself:
# apt policy node-uid-number
node-uid-number:
Installed: 0.0.6-1
Candidate: 0.0.6-1
Version table:
*** 0.0.6-1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100
This is strange, indeed. The MP for the merge is:
https://code.launchpad.net/~sergiodj/ubuntu/+source/python-rtslib-
fb/+git/python-rtslib-fb/+merge/397174
As you can read there, I did check if the package installed/uninstalled
correctly. Bryce also double-checked it. I don't know if the
Thanks for taking the time to write a report. As you noticed, this was
caused by a local configuration issue. As such, I am marking this bug
as Invalid. Feel free to reopen it and provide more information if you
think it is a real bug.
** Changed in: mysql-5.7 (Ubuntu)
Status: New =>
Thanks for the report. I can indeed confirm the bug. I could also
verify that the behaviour still happens as of Hirsute.
I've subscribed the Ubuntu Server team to the bug; we will look into it
as time permits. This does not seem to be an urgent issue, though, so
it may take a while until it is
** Changed in: sssd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916562
Title:
libnss-sss removes config when not being purged
To manage notifications
Thanks for providing more information.
Unfortunately, I still cannot reproduce the problem. This time I tried
using a Hirsute VM instead of a container, but everything worked as
expected. I was able to send an email from inside the VM, the email
went through without problems, and I received it
** Description changed:
[ Impact ]
The node-uid-number package is pretty much unusable on Focal because it
doesn't ship the "get-uid-gid.js" file. Since this package is a
dependency of npm, this means that there can be situations when npm will
fail to perform a certain task (see
number (Ubuntu Focal)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Also affects: node-uid-number (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: node-uid-number (Ubuntu Groovy)
Status: New => Confirmed
** Changed in: node-uid-number (Ub
** Also affects: node-uid-number (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: node-uid-number (Ubuntu Focal)
Status: New => Confirmed
** Changed in: node-uid-number (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification
Thank you for taking the time to file a bug report.
>From the logs, it is not possible to obtain the information necessary to
investigate. I am thinking that this may be a local configuration
issue, but I'm not sure. Did you do any local modifications to the PHP
configuration files, or are you
Thank you for taking the time to file a bug report.
Based on your logs, you are likely having several issues like:
2021-02-19 15:37:23 0 [ERROR] InnoDB: Invalid flags 0x4800 in ./ibdata1
This seems to be a local configuration issue. Also, I did not
understand your description: what do you mean
Thank you for your report.
The logs you posted are a bit strange. This part here:
fev 21 15:24:28 euhe.in systemd[184109]:
[0;1;31m[0;1;39m[0;1;31mmysql.service: Failed at step USER spawning
/usr/share/mysql/mysql-systemd-start: No such process[0m
It says that
Thanks for the report.
I can confirm this behaviour. Here are the reproduction steps, assuming
you're in a Focal VM:
# apt install samba apache2 curl cifs-utils
# cat << EOF >> /etc/samba/smb.conf
[testshare]
path = /testshare
browseable = yes
read only = yes
guest ok = yes
EOF
# mkdir
** Changed in: apache2 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916391
Title:
Range requests broken on CIFS mounted document root
To manage
Thank you for taking the time to file a bug report.
Based on the error messages posted in the description of the bug, it
seems to me like there was some race condition on dpkg and it was unable
to acquire the necessary lock to perform the operation. Initially this
seems strange to me, since dpkg
Thank you for your bug report. I've subscribe Christian to it, who is
our qemu expert. He will take a look as time permits.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916313
Title:
memory
Thank you all for the further investigation on this bug.
@Nathan, were you able to identify an upstream patch that fixes this
issue? I would appreciate if you could point me to a commit so that I
could test it locally as well.
Thanks.
--
You received this bug notification because you are a
eb 19 23:08:11 telegraf-hirsute telegraf[2133]: 2021-02-19T23:08:11Z E!
[agent] Error writing to outputs.influxdb: could not write any address
** Affects: telegraf (Ubuntu)
Importance: Medium
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
--
You received this b
Public bug reported:
The current golang-go on hirsute can't work with vendorized dependencies
when "go list -m all" is used.
# go list -m all
go list -m: can't compute 'all' using the vendor directory
(Use -mod=mod or -mod=readonly to bypass.)
This has been reported and apparently
OK, new package (with the same version) uploaded now, which addresses
the comments made by Robie. Let me know what you think. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905790
Title:
On Thursday, February 18 2021, Robie Basak wrote:
>> + certs = CERT_CreateSubjectCertList (NULL, handle,
> >derSubject,
>
> Doesn't this need a return value test? AFAICT,
> CERT_CreateSubjectCertList might return NULL, and CERTLIST_HEAD (certs)
> will unconditionally look up a member? There's a
*** This bug is a duplicate of bug 1915826 ***
https://bugs.launchpad.net/bugs/1915826
** This bug has been marked a duplicate of bug 1915826
package apache2 2.4.41-4ubuntu3.1 failed to install/upgrade: installed
apache2 package post-installation script subprocess returned error exit
Bryce was able to provide a possible reproducer:
# apt install apache2
# rm -rf /usr/share/apache2/default-site/
# apt purge apache2
# apt install apache2
I'm marking this bug as Triaged.
@Katarina, could you confirm whether you've removed /usr/share/apache2
/default-site/ before purging the
Thanks for bug report.
I attempted to reproduce it here, but could not. Here's what I did
(inside a LXD Groovy container):
# id games
uid=5(games) gid=60(games) groups=60(games)
# apt install -y libglib2.0-bin gvfs gvfs-backends dbus-x11 samba
# eval $(dbus-launch --sh-syntax)
# cat
Thank you for taking the time to file a bug report.
We will need more information in order to proceed with the investigation
of the bug. Based on the logs posted, I could not determine the cause
for the error message.
When I repeat the steps described in the DpkgHistoryLog.log in a Focal
Thanks for the report. I've subscribed Christian, who will look into
this issue when possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915811
Title:
Empty NUMA topology in machines with
I am marking this bug as Won't Fix for Bionic because as far as I could
see there is nobody who is affected by this but there. Of course, I am
willing to reconsider this decision in case someone shows up and
complains about this problem on Bionic.
** Changed in: sssd (Ubuntu Bionic)
Upstream is aware of the bug and is working on a solution.
** Bug watch added: Samba Bugzilla #14621
https://bugzilla.samba.org/show_bug.cgi?id=14621
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=14621
Importance: Unknown
Status: Unknown
--
You received
Thanks for the report, Brandon.
I can confirm this behaviour, and here are simple reproducible steps to
verify it:
# apt install clamav
# echo hi > test
# stat test
...
Access: 2021-02-10 19:53:04.982514441 +
...
# clamscan test
# stat test
Access: 2021-02-10 19:53:32.482243351 +
I'm
Thanks for driving this effort, much appreciated. I can work on
properly applying the patches and testing the packages next week (feel
free to ping me on IRC if I don't update this bug). I don't know about
backporting this to Bionic; it seems that it's not a very urgent issue
to justify the
Ah, good to know! No problem at all, Brian! Cheers :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To manage
Ah, I see that is has indeed been backport by Debian, and is already in
hirsute: debian/patches/2bf3b79d05bf85e41cbdcb020bd1cc424f59dd9a.diff is
the patch. @Brian, would you like me to backport the patch to another
release?
--
You received this bug notification because you are a member of
@Brian, Ops, sorry. I forgot about this bug, and then I kind of assumed
that it had already been backported on Debian. This is just for
hirsute, right? I can backport it now, give me just a second.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for the quick reply.
Hm, I was expecting to see an entry dated as Feb 01, at around 15:20,
which is the time present in the MySQL error log.
These errors are quite hard to diagnose, because they cannot be easily
reproducible. However, the "workaround" we suggest is to just run "apt-
Thank you for taking the time to file a bug report.
Unfortunately, I am unable to reproduce it locally using a Focal
container with the latest MySQL package installed. I could not find
anything particularly wrong in your configuration files either, and,
although your
Thank you for taking the time to file a bug report.
Unfortunately, I am unable to reproduce it locally using a Focal
container with the latest MySQL package installed. I could not find
anything particularly wrong in your configuration files either, and,
although your
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913810
Title:
restart doesn't test for syntax errors
To manage notifications about
Thanks for the patch, Lucas.
I'm not a Ruby expert, but the code LGTM, and the rationale too. It
seems you forgot to run update-maintainer. Once you do, feel free to
upload the package. Are you considering sending this change to Debian
as well?
Cheers.
--
You received this bug notification
Thanks for the bug report.
Initially I wasn't able to reproduce it with a pristine installation of
Ubuntu Bionic + sssd, then aa-enforcing sssd, and then enabling
overlayroot=tmpfs. sssd was able to start successfully.
Then, we had a chat on IRC where Andreas let me know that sssd's
autopkgtest
** Changed in: samba (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912750
Title:
samba-tool domain provision crash with "password hash userPassword
Thank you for your reply.
OK, that confirms my suspicion that the upstream bug referenced in the
original description does not (entirely) relate to this issue.
I was able to confirm a few things:
- This bug is reproducible in hirsute as well, which means that the
latest version of samba in our
Thanks for the bug report and for following up on it. I tried creating
a Focal VM and installing unbound in it, and it succeeded. Since it is
not clear how to reproduce the issue, and no logs were provided, I am
marking this bug as Incomplete. If you happen to find more details
about the
Thanks for the bug report. I'm marking this bug as Triaged and
subscribing ubuntu-server to it. When the feature is accepted upstream
we can decide whether it makes sense to backport it or to wait for a new
upstream release of the package.
** Changed in: sosreport (Ubuntu)
Status: New =>
Thanks for the reply, Peter.
Yes, if you start rabbitmqctl directly via the command line then the
systemd unit will not be invoked, and process will use the default
limits specified by the system. If that is the way you invoked
rabbitmqctl, then what you can do is modify the limits before
Offhand, after analysing the bug and the patches mentioned in the
original description, I'm a bit skeptical that we're dealing with the
same issue here.
The upstream bug expliciltly mentions a limitation with crypt_r on RHEL
systems, and the person says that the underlying problem is that "...
@EOLE team, could you run a test with the PPA provided above and see if
it fixes the bug for you, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912750
Title:
samba-tool domain provision
OK, I can reproduce the bug here.
I backported the 3 upstream patches that fix this bug, and built a new
Samba version in a PPA:
https://launchpad.net/~sergiodj/+archive/ubuntu/samba-bug1912750
However, even after installing it, I'm still seeing the error when
running "samba-tool".
I'm still
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912750
Title:
samba-tool domain provision cr
@Kees Baker, thanks for providing your krb5.conf. Would it be possible
to also provide the contents of any file under /etc/krb5.conf.d/ and
/var/lib/sss/pubconf/krb5.include.d/. I'm wondering if there's anything
in those directories that is influencing the bug. Thanks.
--
You received this
Like Andreas, I cannot reproduce the coredump either.
# smbclient //focal-01.example.com/myshare -k
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER
Even after using the same options as the ones
Performing the verification on Groovy:
First, confirming that the current sssd manifests the bug:
# apt policy sssd
sssd:
Installed: 2.3.1-3ubuntu2
Candidate: 2.3.1-3ubuntu2
Version table:
*** 2.3.1-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu groovy-updates/main amd64
Performing the verification on Focal:
First, confirming that the current sssd manifests the bug:
# apt policy sssd
sssd:
Installed: 2.2.3-3ubuntu0.2
Candidate: 2.2.3-3ubuntu0.2
Version table:
*** 2.2.3-3ubuntu0.2 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64
Hi Paride,
Thanks for further investigating. I assumed that the crash was indeed
reproducible by hacking the package, but I think it's important to get a
reproducer that doesn't involve rebuilding anything if we're thinking
about an SRU (for Groovy, for example).
In any case, I think it's
Thanks for the patch, Lucas.
I reviewed it and it seems reasonable. I'd probably use a "Origin:
backport" header and mention the commit URL there as well. I haven't
run the dep8 tests myself but I trust the results you posted :-).
LGTM.
--
You received this bug notification because you are a
Thanks, Paride.
I had also found the same bug yesterday, but I decided not to mark the
bug as Triaged because I still cannot reproduce it.
As noted previously, I would like to be able to reproduce the issue
before moving forward. This will prove useful if we have to SRU the
patch.
I still
Thanks for the report. I've reassigned the bug to net-snmp, since this
is not a nagios-plugins issue.
I'm also having a bit of trouble reproducing this one. I think I
generated the certificates correctly by doing:
# net-snmp-cert genca -I -n hostname.example.com
# net-snmp-cert gencsr -I -t
Thanks for the report.
Just by installing the package I cannot trigger this problem; it
complains that it "cannot find inband device". I wonder what it would
take to have a reproducer for this.
In any case, this looks like a valid bug. Since there is a known and
easy workaround, I'm marking it
** Package changed: nagios-plugins (Ubuntu) => net-snmp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912390
Title:
[Patch] TLS/DTLS: inconsistent allowed_uses behaviour when in debug
Thanks for the bug report.
This should have been opened against net-snmp, and not nagios-plugins,
right? I'm reassigning it to the proper package.
It seems to me that it's a valid bug, but it would be great to have a
more detailed reproducer. I tried editing /etc/ssl/openssl.cnf and
extend the
Thank you for the bug report.
I am assuming that this bug refers to Hirsute. The PR you linked is
still being reviewed upstream. Eventually it will be accepted and
released upstream. I am marking this bug as a Wishlist for now, since
it seems to me that the feature is not yet ready to be
** Description changed:
+ [ Impact ]
+
+ sssd users on Focal, Groovy and Hirsute can experience problems when
+ setting sssd's apparmor profile to "Enforce" mode. In this scenario,
+ apparmor will prevent sssd from being able to execute programs under the
+ /usr/libexec/sssd/* path, which will
** Also affects: sssd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Hirsute)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: New
Verification for Groovy.
root@groovy-desktop:~# apt policy sssd
sssd:
Installed: 2.3.1-3
Candidate: 2.3.1-3
Version table:
*** 2.3.1-3 500
500 http://ca.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
Booting the VM and verifying that the bug
Verification for Focal:
root@focal-desktop:~# apt policy sssd
sssd:
Installed: 2.2.3-3ubuntu0.1
Candidate: 2.2.3-3ubuntu0.1
Version table:
*** 2.2.3-3ubuntu0.1 500
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100 /var/lib/dpkg/status
** Changed in: sssd (Ubuntu Focal)
Assignee: Sergio Durigan Junior (sergiodj) => Marco Trevisan (Treviño)
(3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905790
Title:
Make S
OK, packages uploaded for Groovy and Focal (waiting on the SRU team
now), and Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900642
Title:
sssd won't start
To manage notifications about
t; Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900642
Title:
sssd won't start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910611
Title:
sssd startup fails when appar
Sorry, scratch that, I got confused and assumed that you were mounting a
Samba share. I moved the bug back to cifs-utils.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882980
Title:
unix
AFAIU, the work on SMBv3 UNIX extensions on Samba is ongoing:
https://wiki.samba.org/index.php/SMB3-Linux
So, while cifs-utils tries to use "unix" when mounting the share, Samba
still doesn't support it, and therefore mount.cifs falls back to nounix.
This is not necessarily a bug; it's just
Confirmed that the bug still exists with cifs-utils 6.11-1ubuntu1.
** Changed in: cifs-utils (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090760
Title:
Closing after confirming that it's been fixed.
** Changed in: cifs-utils (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/260396
Title:
cifs.mount:
Confirmed that the bug still exists with cifs-utils 6.11-1ubuntu1.
** Changed in: cifs-utils (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090764
Title:
Brian, thanks so much for accepting the SRU so quick! As it turns out,
I was able to come up with a better, more complete fix, and upstream has
accepted it a few days ago. For that reason, and after consulting with
Robie, I am dropping the verification-* tags from this bug, and will
prepare a
Aside from reinstalling the package, you can try to overwrite your
current apparmor profile with the one that is shipped by default in the
package. Something like the following:
# wget
Thank you for taking the time to file a bug report.
Based on what I can find in the attached logs, I cannot really
understand the sequence of commands that may have led to this error. I
tried reproducing it in a container here, making sure to enable i386
first, but everything (curl, nodejs and
*** This bug is a duplicate of bug 1906627 ***
https://bugs.launchpad.net/bugs/1906627
Thanks for your report. It indeed seems like a duplicate of bug
1906627, so I am marking it as such.
** This bug has been marked a duplicate of bug 1906627
GSS-SPNEGO implementation in cyrus-sasl2 is
Thank you for taking the time to file a bug report.
Could you please provide some reproduction steps here? I'm not a ceph
expert, and it seems like there needs to be some initial configuration
to make ceph work. I did spend some time trying to configure it here,
but it'd be easier if you could
Thank you for the bug report.
Unfortunately, we still don't have enough details to proceed with the
investigation of this problem, so I am not going to change anything
here. If you can provide more information (as per Christian's request),
feel free to mark this bug as New again.
Thanks.
--
Thanks for taking the time to report a bug.
I am unable to reproduce the issue here. I've tried it on a Focal lxd
container, a Focal VM, and a Focal system (native). I'm always able to
execute the following commands:
# sudo nmap -n 192.168.1.1/24
# sudo nmap -4 -vvv -ddd -sn -PR 8.8.8.8
They
Thank you for taking the time to file a bug report.
>From the information you provided, it is hard to determine what the root
cause of the problem is. I see some interesting things, though:
1) According to DpkgHistoryLog.txt, your unnatended-upgrades command has
been failing a lot lately. This
Package uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908149
Title:
dfwinreg: FTBFS on hirsute due to missing Build-Dep
To manage notifications about this bug go to:
Package uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908134
Title:
cura: FTBFS on hirsute
To manage notifications about this bug go to:
** Patch added: "dfwinreg.patch"
https://bugs.launchpad.net/debian/+source/dfwinreg/+bug/1908149/+attachment/5443581/+files/dfwinreg.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908149
rtance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Affects: dfwinreg (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #976653
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976653
** Also affects: df
** Patch added: "cura.diff"
https://bugs.launchpad.net/debian/+source/cura/+bug/1908134/+attachment/5443556/+files/cura.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908134
Title:
cura:
ltimaker/Cura/commit/00bc1bfcdc960d4bad62adc4b1615ca4cc6b3cee
** Affects: cura
Importance: Unknown
Status: Unknown
** Affects: cura (Ubuntu)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Affects: cura (Debian)
Importance: Unk
Finally! Thanks for the detailed steps, Lee. I was finally able to
reproduce it locally.
For the record, these are the commands you can issue to reproduce.
Suppose that you have a samba share named "sambashare" serving a
directory at $HOME/testshare.
$ gio mount smb://127.0.0.1/sambashare
$
@Timo thanks for looking into that. FWIW, I've just opened a MR on
salsa in order to propose this change to the Debian sssd as well:
https://salsa.debian.org/sssd-team/sssd/-/merge_requests/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
+ [ Impact ]
+
+ Starting from Groovy, sssd became a dependency of ubuntu-desktop. This
+ means that Ubuntu users who install the Desktop version will
+ automatically get sssd installed in their systems.
+
+ By default, sssd does not try to make any assumptions about
@Lee Tae Hoon, thank you for the feedback. I downloaded the zip file
you provided, but I still can't see anything useful in the logs. I
wonder what's really happening. I will have to bug you one more time
and ask you to provide a network trace of the moment of the failure,
please. You can read
I finally had some time to do some investigation on this bug. I
appreciate the analysis done by others, and the patch provided by
Dimitri.
I verified that using ConditionPathExists on sssd.service does prevent
sssd from starting (as expected), which means that the error messages in
the log are
ned) => Sergio Durigan Junior (sergiodj)
** Changed in: sssd (Ubuntu Hirsute)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: sssd (Ubuntu Groovy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
I forgot to mention, but I:
1) Replaced my smb.conf with Lee Tae Hoon's smb.conf, and tried to
reproduce the error. Everything still works for me.
2) Tried moving files (via terminal and using Nautilus) to the share. I
can access them fine.
3) Tried attaching another disk to my Focal VM,
Thanks for the replies, Rapper_skull an Lee Tae Hoon.
Lee, I have a few questions for you.
1) What is the name of the file you tried to open? Based on the
screenshot you posted earlier, I thought the file was named
IMG_1809.JPG. However, in your logs I don't see any attempt to open a
Hi, thanks for reporting the bug.
Before anything else, I would like to ask if there is any particular
reason why you marked the bug as Invalid. Have you perhaps found the
problem or a workaround? If that is the case, then could you update
this bug and post what you've found? Maybe other users
** Changed in: telegraf (Ubuntu Focal)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897631
Title:
[SRU] Add telegraf to focal's universe repository
To manage
801 - 900 of 1060 matches
Mail list logo
