Nice catch. Thank you.
This indeed does seem to be a workaround. Forcing version 1.0 avoids the
issue. Its not a proper fix however. Seems to be bug in higher versions.
>From the man doc:
The default since v4.13.5 is for the client and server to negotiate the
highest possible version greater tha
I forced version 2.1 and i did NOT reproduce issue. I also forced 3.0
again, and issue occurred again.
So, it seems forcing 2.1 may also be workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
opened bug upstream https://bugzilla.samba.org/show_bug.cgi?id=13647
** Bug watch added: Samba Bugzilla #13647
https://bugzilla.samba.org/show_bug.cgi?id=13647
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Actually, it just reoccurred on 2.1, then i dropped back to 2.0 and it
reoccurred. Now back on 1.0 again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777364
Title:
coping files to cifs mounted di
client libraries of samba are 2:4.7.6+dfsg~ubuntu-0ubuntu2
** Description changed:
How to reproduce:
Copy some large files from local filesystem to CIFS mounted filesystem.
After some gigabytes, it syslog will show "general protection fault" and
- mounted file system will become unresons
Public bug reported:
How to reproduce:
Copy some large files from local filesystem to CIFS mounted filesystem.
After some gigabytes, it syslog will show "general protection fault" and
mounted file system will become unresponsive.
How often does it occur:
Every time, after a few minutes or so.
GPF syslog attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777364
Title:
coping files to cifs mounted directory causes general protection fault
To manage notifications about this bug go to
I grabbed the latest 4.18.0-041800rc1 and recreated it quickly
I attach the output from syslog. Let me know what else i can provide to
be of assistance.
** Attachment added: "gpf with latest kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777364/+attachment/5154405/+files/gpf.4.
Public bug reported:
Running pwsafe has problems.
It has two failure modes.
1) It starts, waits 15 to 20 seconds then Window opens
2) Does not start at all. The process is still running:
For 1) an strace reveals:
18966 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
** Attachment added: "blocks forever on futex"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1160923/+attachment/3600826/+files/blocksOnFutex.strace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
dpkg -l | grep udev
ii gir1.2-gudev-1.0175-0ubuntu13
amd64libgudev-1.0 introspection data
ii libgudev-1.0-0:amd641:175-0ubuntu13
amd64GObject-based wrapper library for lib
warning on cmd line after timeout passes:
Error creating proxy: Error calling StartServiceByName for
org.gtk.vfs.Daemon: Timeout was reached (g-io-error-quark, 24)
(pwsafe:31636): GVFS-CRITICAL **: fill_mountable_info: assertion `proxy
!= NULL' failed
--
You received this bug notification becau
perhaps is problem with pwsafe. Resolving for now.
** Changed in: udev (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160923
Title:
udev gvfs timeout
To mana
I have a smilar issue from logs in
https://answers.launchpad.net/ubuntu/+source/cups/+question/212469
We can see in both issues
[Job X] Printing page 1, Y%
then
[Client Z] Accepted from localhost (Domain)
and then the printing stops.
--
You received this bug notification because you are a m
lsb_release -a; uname -a; apt-cache policy cups
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.10
Release:12.10
Codename: quantal
Linux flowers 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:32:08 UTC 2012 i686
i686 i686 GNU/Linux
cups:
Installed: 1.6.
Bought an HP. moved on.
** Changed in: cups (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074759
Title:
epson stylus photo r800 fails print after 12.10 Quant
Public bug reported:
I have two laptops with 12.04 which both printed perfectly to epson
stylus photo r800. After upgrade, both fail in the same way. The
printers are recognised and loaded. But when a print command is sent, or
ink level status query via mtink is made, the request never completes.
lsb_release -rd
Description:Ubuntu 12.10
Release:12.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074759
Title:
epson stylus photo r800 fails print after 12.10 Quantal Quetzal
upgr
SO, i noticed that usblp is removed when i print:
Nov 17 23:14:52 salzburg kernel: [ 138.202412] usb 3-2: USB disconnect, device
number 2
Nov 17 23:14:52 salzburg kernel: [ 138.202676] usblp0: removed
Nov 17 23:14:52 salzburg udev-configure-printer: remove
/devices/pci:00/:00:14.0/usb3
other errors in cups error log
D [17/Nov/2012:23:26:24 +0100] Calling FindDeviceById(cups-Stylus-Photo-R800)
D [17/Nov/2012:23:26:24 +0100] Calling DeleteDevice(cups-Stylus-Photo-R800)
D [17/Nov/2012:23:26:24 +0100] DeleteDevice failed:
org.freedesktop.DBus.Error.InvalidArgs:Type of message, `(s)
OK, i uploaded cups error log for the print that failed.
This is the one that usblp was removed in syslog
Apparently, blacklisting of usblp is not required in 1.6.X
** Attachment added: "cups error log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1074759/+attachment/3436916/+files/pr
I believe i have same issue from 4.18.0-13 to 4.18.0-14 on lenovo T410.
on boot last thing i see is
"Loading initial ramdisk ..."
On subsequent boot on different kernel from syslog i can see an OOPS and
stack trace. Attaching. Let me know if i can assist or if its separate
issue.
** Attachment a
22 matches
Mail list logo
