Version with fix, ledgersmb 1.3.46-1, is in Ubuntu ('Wily')
** Changed in: ledgersmb (Ubuntu)
Status: Confirmed = 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/1078817
Title:
** Changed in: ledgersmb (Debian)
Status: Confirmed = 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/1078817
Title:
After installation it doesn't work
To manage notifications
** Changed in: ledgersmb (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078817
Title:
After installation it doesn't work
To manage notifications about
See also http://bugs.debian.org/698298.
** Bug watch added: Debian Bug tracker #698298
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698298
** Also affects: ledgersmb (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698298
Importance: Unknown
Status: Unknown
--
If you are using the correct initial password for that user when you're
attempting to use update the user account, it's possible that it has
expired. If so, you may be able to resolve that by using something
like the following SQL:
ALTER USER enzo VALID UNTIL '2012-11-30';
--
You received
That allowed me to make a few more steps.
I still get the HTTP authentication request and I have no idea about the answer
I need to give.
** Attachment added: Screenshot of the request
https://bugs.launchpad.net/ubuntu/+source/ledgersmb/+bug/1078817/+attachment/3441211/+files/shot-0089.png
** Changed in: ledgersmb (Ubuntu)
Assignee: (unassigned) = Ubuntu LedgerSMB (ledgersmb)
** Changed in: ledgersmb (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There are issues with the automatic configuration during the LedgerSMB
package install, which is why that is not enabled by default. The
issue in this case has to do with the 'ledgersmb' database admin user
not being set up with the correct permissions. That can be corrected by
executing the
