[Bug 1003813] Re: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5)
This bug occurred to me apparently today for the first time, as from the /var/log/syslog.* that I checked. I'm attaching the relevant part of the syslog, as well as the dpkg.log from the last week. ** Attachment added: syslog+dpkg.log.txt https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1003813/+attachment/3452823/+files/syslog%2Bdpkg.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003813 Title: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1003813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003813] Re: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5)
Forgot to add (to #7): The bug occurred during boot. Recently, I'm used not to turn off my laptop too often, but rather I put it in stand by, so I don't boot too often either. FYI, I have a couple of remote samba shares mounted by default in my /etc/fstab, but now I was booting at home, whilst those shares are only available when I'm plugged onto the corporate network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003813 Title: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1003813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750786] Re: nmbd job fails to start on boot
Hi, a part of this problem is still there in 11.04, with samba, just upgraded from proposed-updates (2:3.5.8~dsfg-1ubuntu2.2), despite the log reports * debian/samba.smbd.upstart: Do not attempt to start smbd until network device is up, previously smbd was starting too early and often failing. (LP: #771305) I'm experimenting it in this flavour: samba seems to be working, as I'm seeing a shared folder, but _printers only_ are not shared. As usual, a manual restart (sudo service smbd restart) fixes the issue (and the printer magically shows up in the WinVista client), but on reboot it's always the same: I can see the folder shares, not the printer. Configuration of smbd.conf and nmbd.conf is all default, I also tried the modification of cipher2 (remove the and net-device-up !loopback from nmbd.conf) without success. Also, I tried to add a and started nmbd to smbd.conf, as I spotted from the thread that the problem might be due to smbd and nmbd booting up concurrently, again without success. Something very strange I have in /var/log/boot.log: Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service S20smbd start Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the start(8) utility, e.g. start S20smbd start: Unknown job: S20smbd As you can see, it seems smbd's name is being actually mistaken as S20smbd, i.e., the rc.d link. However, I double-checked the rc.d links, and I can't see anything irregular: $ ls -l /etc/rc*/*smb* lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc2.d/S20smbd - ../init.d/smbd lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc3.d/S20smbd - ../init.d/smbd lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc4.d/S20smbd - ../init.d/smbd lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc5.d/S20smbd - ../init.d/smbd and the smbd.conf is there in /etc/init/smbd.conf. Now I'm going to try this samba4. -- 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/750786 Title: nmbd job fails to start on boot -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 750786] Re: nmbd job fails to start on boot
Hi, a part of this problem is still there in 11.04, with samba, just upgraded from proposed-updates (2:3.5.8~dsfg-1ubuntu2.2), despite the log reports * debian/samba.smbd.upstart: Do not attempt to start smbd until network device is up, previously smbd was starting too early and often failing. (LP: #771305) I'm experimenting it in this flavour: samba seems to be working, as I'm seeing a shared folder, but _printers only_ are not shared. As usual, a manual restart (sudo service smbd restart) fixes the issue (and the printer magically shows up in the WinVista client), but on reboot it's always the same: I can see the folder shares, not the printer. Configuration of smbd.conf and nmbd.conf is all default, I also tried the modification of cipher2 (remove the and net-device-up !loopback from nmbd.conf) without success. Also, I tried to add a and started nmbd to smbd.conf, as I spotted from the thread that the problem might be due to smbd and nmbd booting up concurrently, again without success. Something very strange I have in /var/log/boot.log: Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service S20smbd start Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the start(8) utility, e.g. start S20smbd start: Unknown job: S20smbd As you can see, it seems smbd's name is being actually mistaken as S20smbd, i.e., the rc.d link. However, I double-checked the rc.d links, and I can't see anything irregular: $ ls -l /etc/rc*/*smb* lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc2.d/S20smbd - ../init.d/smbd lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc3.d/S20smbd - ../init.d/smbd lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc4.d/S20smbd - ../init.d/smbd lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc5.d/S20smbd - ../init.d/smbd and the smbd.conf is there in /etc/init/smbd.conf. Now I'm going to try this samba4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750786 Title: nmbd job fails to start on boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124406] Re: Keyboard keys get stuck and repeat (Feisty, Gutsy)
I don't know if this can help, but on my system (Dell Latitude D830 with Ubuntu 8.04 x86_64, details below) this happens apparently only when I launch Emacs (22.1.1) from X (using Gnome), and I try to Alt-Tab to some other applications. I can Alt-Tab from any other applications without problems, but when I do that from Emacs (and I can edit and type whatever within Emacs without problems), keyboard hangs and does not respond anymore, but actually the entire windowing system hangs and does not even respond to mouse. Switching to console mode, then to graphics mode again takes everything back to life again. Tried both with accelerated NVIDIA driver and with default nv one, behavior is the same. Also, this behavior is *deterministic*: just one simple Alt+Tab from Emacs, and I'm lost. I verified that it does not happen when trying to switch from a terminal running emacs22-nox. This would seem to be a problem of the windowing system, but probably triggered by something that only Emacs does. This was not happening before (I use a lot Emacs from X/Gnome), so it must have been caused by some recent upgrade. For what it may concern, this happens both from the laptop keyboard and from an external one connected to the docking station (actually, it's a PS/2 keyboard routed through a PS/2-USB video/mouse/keyboard switch). Finally, don't know if it may be relevant/useful, but it's already a few months that my Ubuntu/Gnome refuses to configure correctly the keyboard layout, no matter how many times I tell it I want an IT one by default, I always get a US one (it's only X/Gnome, because the text console gets correctly the configured default). No matter if I delete the US configuration, leaving only the IT one, it will always be US after boot. -- Kernel (default Ubuntu): Linux laptop 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux Attached a log of hopefully relevant installed applications along with their versions. ** Attachment added: installed-apps.txt http://launchpadlibrarian.net/18345972/installed-apps.txt -- Keyboard keys get stuck and repeat (Feisty, Gutsy) https://bugs.launchpad.net/bugs/124406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124406] Re: Keyboard keys get stuck and repeat (Feisty, Gutsy)
Just verified that the same bad behavior exists with kernel 2.6.26.5 Vanilla (attached detail of configuration). ** Attachment added: config-2.6.26.5 http://launchpadlibrarian.net/18346923/config-2.6.26.5 -- Keyboard keys get stuck and repeat (Feisty, Gutsy) https://bugs.launchpad.net/bugs/124406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124406] Re: Keyboard keys get stuck and repeat (Feisty, Gutsy)
** Also affects: emacs Importance: Undecided Status: New -- Keyboard keys get stuck and repeat (Feisty, Gutsy) https://bugs.launchpad.net/bugs/124406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124406] Re: Keyboard keys get stuck and repeat (Feisty, Gutsy)
It seems that, removing *accessibility packages*, fixes the situation (or at least it cannot occur so easily now). I just removed these two packages: ii gnome-accessibility-themes 2.22.0-0ubuntu1 accessibility themes for the GNOME 2 desktop ii gnome-accessibility-themes-extras 2.22.0-0ubuntu1 accessibility themes for the GNOME 2 desktop -- Keyboard keys get stuck and repeat (Feisty, Gutsy) https://bugs.launchpad.net/bugs/124406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
