I can answer for 68.10.0 that the problem does not occur anymore (but
our setup changed since then, additionally using kerberos)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/507089
Title:
Thunderbi
I see. That was a long time ago, our setup has changed a lot since
then, and we obviously found workarounds. So I am not able to reproduce
the problem exactly. Maybe some confusion with pip(3)
Please close the bug, I will open a new one if problem occours again.
Thx!
Am Dienstag, den 01.12.2020,
Public bug reported:
cups-browsed wants to start avahi though that's decativated in
/lib/systemd/system/cups-browsed-service:
---
[Unit]
Description=Make remote CUPS printers available locally
Requires=cups.service
After=cups.service avahi-daemon.service
# Wants=avahi-daemon.service
[Service]
Ex
Still no luck here, not able to authenticate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817537
Title:
libsoup should support ntlmv2
To manage notifications about this bug go to:
https://bugs.l
Sorry to say that unfortunately it's not working here. Authentication
through ntlm still not working:
- installed package from proposed:
---
libsoup2.4 (2.62.1-1ubuntu0.2) bionic; urgency=medium
* debian/patches/git_ntlmv2_sup
Public bug reported:
When trying to start jupyter-notebook it complains about missing
libraries:
ImportError: No module named tornado.log
ImportError: No module named jinja2
ImportError: No module named zmq.eventloop
After apt-get install python-{zmq,jinja2,tornado}
Everything works, so these p
Can I edit the headline? It should be 'jupyter-notebook' not '
jupyter-notebooks'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831980
Title:
jupyter-notebooks needs additional packages:
python-{
Confirming fix, login working again on bionic. Thanks for your work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813873
Title:
Userspace break as a result of missing patch backport
To manage not
Am Montag, den 25.02.2019, 15:29 + schrieb Sebastien Bacher:
> The issue is fixed in the current Ubuntu version, closing for the
> current serie.
Hm, cannot confirm. At least evolution-ews fron cosmic cannot connect
to our server with ntlm selected.
--
You received this bug notification beca
Public bug reported:
Our Exchange admins recently made NTLMv2 obligatory. Since then
interaction with Exchange through Evolution isn't possible anymore.
In newer versions of libsoup that has been implemented, see
https://gitlab.gnome.org/GNOME/evolution-ews/issues/38
Could that be backported to
Confirming for 18.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792499
Title:
Incorrect quoting of titles
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
Confirming the login loop bug for 18.04.2 with 4.15.0-45-generic
And also confirming the fix in proposed with 4.15.0-46-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813873
Title:
Userspace
*** This bug is a duplicate of bug 1813873 ***
https://bugs.launchpad.net/bugs/1813873
Confirmed Bug for 18.04.2 with Kernel 4.15.0-45-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812095
file-roller should use $XDG_CACHE_HOME or have an option to select a
different directory for caching.
When users' home directories are on a remote machine and mounted via
NFS, then file-rollers' habit of creating ~/.fr-* directories,
extracting there and moving back the result creates huge i/o-loa
linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64
and
linux-image-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_amd64
both are working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
System works with
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/linux-
image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
Too funny. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
linux-image-4.4.0-116-generic_4.4.0-116.140~lp1745349Commitb0c3e8bd0405Reverted_amd64
seems to work here, 3 reboots in a row on one machine without hard locks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
No success, hard locks with b0c3e8bd040
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
To manage notifications about this bu
47a07600efe does not work here, hard lock on two pcs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
To manage notifications
Yay!
Three boots in a row worked with
linux-image-4.4.0-110-generic_4.4.0-110.133~lp1745349Commit7de295e2a47849_amd64
Was only able to test on one machine though, all my users are logged in.
More testing tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
No luck, unfortunately.
linux-image-4.4.0-110-generic_4.4.0-110.133~lp1745349Commitd3d0f0a209ee_amd64
shows the same hard lock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
Hard loc
Sorry, no improvement on ASUS H110M-C Board with
linux-image-4.4.0-116-generic_4.4.0-116.140~lp1745349Commitff2699cReverted_amd64
Still 4 out of 5 boots result in hard lock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Am 22.02.2018 um 09:05 schrieb ake sandgren:
> The 4.4.0-116-generic still hangs my laptop during boot the same way
> -112 did. And noibpb still solves the problem.
Confirming for Asus H110M-C boards, still the hardlocks.
--
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5046867/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5042847/+files/WifiSyslog.txt
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5046863/+files/WifiSyslog.txt
** At
Am 25.01.2018 um 21:45 schrieb Joseph Salisbury:
> Can you see if either of the following two kernels also exhibit the bug:
>
> 4.4.0-110: https://launchpad.net/~canonical-kernel-security-
> team/+archive/ubuntu/ppa/+build/14231477
>
> 4.4.0-111: https://launchpad.net/~canonical-kernel-security-
Public bug reported:
Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
instead they show
NMI watchdog: Watchdog detected hard lockup on cpu 0
NMI watchdog: Watchdog detected hard lockup on cpu 1
NMI watchdog: Watchdog detected hard lockup on cpu 3
NMI watchdog: Watchdog detecte
Public bug reported:
We cannot login via lightdm if we wait too long after boot:
Cursor in password input field stops blinking and if user inputs password
anyways, then pc freezes. No switcht go VT or login via ssh possible. Only
magic sysreq helps for rebooting.
When user switches to a virtual
Sorry, a typo... "switcht go VT" means "switch to"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680726
Title:
Xorg.freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Am 06.04.2016 um 06:48 schrieb Robert Ancell:
> Still occurring?
>
> ** Changed in: lightdm (Ubuntu)
>Status: New => Incomplete
>
Hm, we ar using Ubuntu 14.04 meanwhile, problem is not ocurring with it.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Confirming here, too: Cifs mounting with 3.13.0-38-generic/trusty-
proposed works again
Thanks for fixing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372482
Title:
mount.cifs does not work with
Am 08.10.2014 um 10:33 schrieb Tamas Pisch:
> When I tested the kernel from #12, the cifs mount worked. After that the
> problem reappeared. I think so that the new official kernel is buggy
> again. I installed again the test kernel, and the cifs mount works
> again...
As far as I can see there is
And could you check out the test kernel from #12?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372482
Title:
mount.cifs does not work with the 3.13.0.36-generic kernel
To manage notifications abo
Am 02.10.2014 um 01:37 schrieb UbuntuAddicted:
> i too am affected by this bug, I am running kernel 3.13.0-37-generic
> within Xubuntu and get the same error when trying to mount a cifs share
> that mounts just fine using kernel 3.13.0-35-generic. When can we expect
> to see a fix thru apt-get?
Ar
Am 25.09.2014 um 19:29 schrieb Joseph Salisbury:
> The test kernel posted in comment #12 appears to fix bug 1373473. Has
> anyone in this bug had a chance to test the kernel?
Tested on 4 machines with 3 different setups meanwhile, working on all
of them.
--
You received this bug notification be
>
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372482/comments/12
Yes, cifs mount works with that one (3.13.0-37-generic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Title:
mount
> This could be a duplicate of bug 1372482
>
> Can you post the errors you seen in /var/log/syslog?
Alright, there's a trace message:
[ cut here ]
Sep 25 09:00:01 pi-behrens kernel: [ 835.395138] WARNING: CPU: 0 PID: 4226 at
/build/buildd/linux-3.13.0/fs/cifs/transpor
Am 24.09.2014 um 17:30 schrieb Brad Figg:
> apport-collect 1373473
Ok, but that doesn't seem to reveal new info, judging from the files
newly uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/13
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214411/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214422/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Ti
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214416/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Title:
moun
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214418/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214412/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Titl
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214420/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Title:
mo
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214421/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214419/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214414/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214413/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Title:
mount.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214415/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
Title:
moun
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1373473/+attachment/4214417/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373473
apport information
** Tags added: apport-collected
** Description changed:
Mounting a share with mount.cifs fails with
'mount error(5): Input/output error'
Mounting through gigolo (smbclient) works
Mounting the same share works with the last kernel 3.13.0-35-generic
I have tried
Public bug reported:
Mounting a share with mount.cifs fails with
'mount error(5): Input/output error'
Mounting through gigolo (smbclient) works
Mounting the same share works with the last kernel 3.13.0-35-generic
I have tried adding sec=ntlm and sec=ntlmv2 to the options, but that does not
help
Confirming this bug for 31.1.1 Linux (Xubuntu 14.04): User accounts
through ldap authentication make Thunderbird crash when trying to print.
Installing nscd makes that go away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Confirming for Xubuntu 14.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291075
Title:
printer icon does not disappear
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Confirm this for 12.04 with hwe and trusty-kernel
(linux-3.13.0-32-generic #57~precise1-Ubuntu)
We have less than 100 ldap users and under 100 groups.
On some clients here we have to use hwe with a newer kernel to support the
hardware.
And on exactly those and only those clients from time to tim
Confirmed on 14.04 64bit, Chromium version 34.0.1847.116 Ubuntu 14.04
aura (260972)
This is bad because Chromium is a much used browser, my users are
crying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
Obviously Pulseaudio doesn't work when using NFS-mounted home directory.
Syslog shows:
$CLIENTNAME pulseaudio[9554]: [pulseaudio] core-util.c: Failed to create secure
directory ($USER_HOME/.config/pulse)
When working as a local-only user everything works.
ProblemType: Bug
Confirmed for Precise with
evolution 3.2.3-0ubuntu6
evolution-mapi 3.2.2-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/795563
Title:
evolution's incoming mail filter rules doesn't work with Exchan
Confirmed here with Precise, on several PCs.
Installed evolution packages:
evolution-3.2.3-0ubuntu6
evolution-common-3.2.3-0ubuntu6
evolution-data-server-3.2.3-0ubuntu7
evolution-data-server-common-3.2.3-0ubuntu7
evolution-mapi-3.2.2-1
evolution-plugins-3.2.3-0ubuntu6
evolution-webcal-2.32.0-2ubun
Bug confirmed here for Precise.
That bug is definitely a show stopper for Ubuntu in in large
heterogenous networks.
--
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/117736
Title:
pam_mount una
Public bug reported:
By default lightdm doesn't remember the last users here, I'm not sure if
it is because we are in an nfs4+ldap environment, for I have never
witnessed that on pcs with only local users.
Putting 'session optional pam_lastlog.so' into /etc/pam.d/lightdm helps
and all the last us
Am 15.04.2013 21:23, schrieb Gunnar Hjalmarsson:
> Thanks, Lars. The tags are right below the bug description, but I
> already did that. Now we just wait for someone to upload it to precise-
> updates. It usually takes at least a week.
Thanks!
> The latest change in accountsservice makes it possi
Bug seems fixed here with
accountsservice_0.6.15-2ubuntu9.6_amd64.deb
gir1.2-accountsservice-1.0_0.6.15-2ubuntu9.6_amd64.deb
libaccountsservice0_0.6.15-2ubuntu9.6_amd64.deb
on two machines with 3 accounts, so I assume it will work everywhere.
How do I add a tag here?
Thanks!
Just a sidenote aft
Ok, I found it and installed it again, but the lightdm package doesn't
seem to be the cause. And I found the problem doesn't occur on all of
the clients. Sigh...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
El 21.03.2013 15:30, Gunnar Hjalmarsson escribió:
> On 2013-03-21 12:14, Lars Behrens wrote:
>> It's lightdm 1.2.3-0ubuntu1+pam
>
> Aha, that one in my PPA. It's the same as 1.2.3-0ubuntu2. ;-)
Obviously there is a difference, because since today we have
1.2.3-0ubuntu2 (
Am 21.03.2013 10:51, schrieb Gunnar Hjalmarsson:
> On 2013-03-21 09:30, Lars Behrens wrote:
>> And btw.: lightdm is working now, too. Last session type and language
>> getting stored.
>
> Do you mean lightdm 1.2.3-0ubuntu2 in precise-proposed?
It's lightdm 1.2.3-
Am 20.03.2013 15:54, schrieb Gunnar Hjalmarsson:
> So I'd say it's safe to use it while awaiting the official update.
Ok, thx. Bug resolved from my point of view.
And btw.: lightdm is working now, too. Last session type and language
getting stored.
Have a good time,
Lars
--
You received this
Am 19.03.2013 19:21, schrieb Gunnar Hjalmarsson:
> Can it possibly be something as simple as settings of environment
> variables in e.g. ~/.profile or ~/.bashrc ? If so, and even if
> ~/.pam_environment is read as expected, such settings would override
> ~/.pam_environment, so to say.
>
> It shoul
Must be something in the home directories:
I completely deleted the ~ of the not working test account and had a new one
created, now the language settings work there.
So it is a matter of finding the bad settings file, can't delete all my users'
home dirs. ;-)
--
You received this bug notificat
Am 19.03.2013 12:10, schrieb Gunnar Hjalmarsson:
> Thanks for your help to improve Ubuntu by reporting this bug!
>
> The problem with incorrect failures in accountsservice when HOME is
> on NFS was also reported in bug 1083605, and a fix has been uploaded
> to Ubuntu 13.04. I attach a patch with a
Public bug reported:
There is no possibility to choose language in an interactive way in
Ubuntu 12.04, neither with XFCE4 nor with Gnome, neither with lightdm
nor with GDM3 when home dirs aren't on local drive.
Error message:
gdm-session-worker[2009]: AccountsService-WARNING: SetLanguage call fai
Public bug reported:
In an NFS4 with ldap-auth environment the last session type doesn't get
recorded per user. The default session (Xubuntu in our case) is pre-
selected, whatever session one last used. Not sure if that is a bug in
lightdm or accountsservice.
ProblemType: Bug
DistroRelease: Ubun
72 matches
Mail list logo