[Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-05-01 Thread eladner
If you reboot (or unmount/remount) with the "ls every minute" cron job
active, it should prevent the timeout on the share and not reach the
keep-alive echo that starts the flood.  I think it is about the
15-minute mark (of inactivity) where the client starts the echo flood.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686099

Title:
  connection flood to port 445 on mounting cifs volume under kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1686099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-04-25 Thread eladner
Maybe.  This is a production system so I'll have to schedule something.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686099

Title:
  connection flood to port 445 on mounting cifs volume under kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1686099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-04-25 Thread eladner
The system is behind a firewall so I can't run apport-collect directly.
Is there a way to run it to a file and upload separately?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686099

Title:
  connection flood to port 445 on mounting cifs volume under kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-04-25 Thread eladner
** Attachment added: "output from ubuntu-bug linux"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686099/+attachment/4867760/+files/bug.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686099

Title:
  connection flood to port 445 on mounting cifs volume under kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-04-25 Thread eladner
and the "apport-bug linux" attachment isn't sufficient?

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686099

Title:
  connection flood to port 445 on mounting cifs volume under kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1686099] [NEW] connection flood to port 445 on mounting cifs volume under kernel

2017-04-25 Thread eladner
Public bug reported:

This is identical to the bug reported on the Debian kernel list, only
I'm running 4.4.0, not 4.[89].0

After about 15 mintues, the cifsd daemon starts flooding echo requests
on port 445 to the windows server causing a constant 1MB/s load (around
10,000 packets per second) that eventually leads to system instability
that forces a reboot to correct.  This is repeatable and as far as I
know started about a week ago (possibly with the installation of
4.4.0-75).

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686099

Title:
  connection flood to port 445 on mounting cifs volume under kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540659] [NEW] LIRC produces multiple events from one keypress

2016-02-01 Thread eladner
Public bug reported:

lsb_release:
Description:Ubuntu 14.04.3 LTS
Release:14.04

# apt-cache policy lirc
lirc:
  Installed: 0.9.0-0ubuntu1
  Candidate: 0.9.0-0ubuntu5
  Version table:
 0.9.0-0ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
 *** 0.9.0-0ubuntu1 0
100 /var/lib/dpkg/status

What happened:

After upgrading from 12.04 to 14.04.3, lirc 0.9.0-0ubuntu5 was
generating multiple non-unique key press events.  "irw" showed that the
multiple key presses didn't have event numbers (second column of irw
output).  No hardware changed.  Only an upgrade to 14.04.3.

No combination of min_repeat or suppress_repeats in lirc.conf would
suppress the multiple events.   No combination of repeat or delay
options in the .lircrc file worked either.

This same configuration was working fine under 0.9.0-0ubuntu1 on a 12.04
box.

Sample IRW output:

# Note the zero event number in the second column.
1781 00 1 Hauppauge_350
1781 00 1 Hauppauge_350
1782 00 2 Hauppauge_350
1782 00 2 Hauppauge_350
1783 00 3 Hauppauge_350
1783 00 3 Hauppauge_350

I reverted the package back to  0.9.0-0ubuntu1 and the problem did not
completely go away (there were occasional multiple events, but they were
unique with an event number in the second field).  Adding
suppress_repeats to the lirc.conf fixed this issue easily.

One caveat is that I'm using an IguanaIR USB receiver wit the supplied
igdaemon and the lirc iguanaIR driver blacklisted so the igdaemon can
use libUSB to grab and talk to the receiver (iguana's recommended
solution).

Apparently there is some regression between 0.9.0-0ubuntu1 and
0.9.0-0ubuntu5 that's not identifying unique events correctly.

What I expected:

LIRC would work with the config files from the previous machine (no
other hardware changes other than an upgrade to 14.04.3).

** Affects: lirc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540659

Title:
  LIRC produces multiple events from one keypress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1540659/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1250191] Re: Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup

2014-07-17 Thread eladner
*** This bug is a duplicate of bug 1217959 ***
https://bugs.launchpad.net/bugs/1217959

I have the same problem.. I've tried the instructions to reset deja dup
completely, have reinstalled it, excluded $HOME/.cache from the backup
and it still occurs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250191

Title:
  Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not
  found in backup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1250191/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 908686] Re: wine windows can't change resolution

2013-01-25 Thread eladner
I can confirm this exists on Ubuntu 12.04, gnome-shell 3.4.1.  Looking
for an easy way to upgrade to gnome shell 3.6 for testing (without
breaking my whole desktop)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908686

Title:
  wine windows can't change resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/908686/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 413356] Re: Marvell 88e8001 onboard nic refuses to work on new 9.04 install

2009-08-14 Thread eladner
And how's that going to work if the machine is not connected to the
network?  Is there a way to network over USB cables or something?

-- 
Marvell 88e8001 onboard nic refuses to work on new 9.04 install
https://bugs.launchpad.net/bugs/413356
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 413356] [NEW] Marvell 88e8001 onboard nic refuses to work on new 9.04 install

2009-08-13 Thread eladner
Public bug reported:

Install is 9.04 fresh off the CD
uname -a
Linux mythbox 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 
i686 GNU/Linux
/proc/version_signature
Ubuntu 2.6.28-11.42-generic

others attached.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Marvell 88e8001 onboard nic refuses to work on new 9.04 install
https://bugs.launchpad.net/bugs/413356
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 413356] Re: Marvell 88e8001 onboard nic refuses to work on new 9.04 install

2009-08-13 Thread eladner
fresh install.  twice.  Marvell 88e8001 shows in the lspci, but is not
recognized.  Tried manually modprobing the modules and doesn't change
anything.

Previously, 8.10 was installed on this system and had no problems with
the interface.

Logs of fresh boot included in the archive.

** Attachment added: log files
   http://launchpadlibrarian.net/30293051/ubuntu_logs.tar.gz

-- 
Marvell 88e8001 onboard nic refuses to work on new 9.04 install
https://bugs.launchpad.net/bugs/413356
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


Re: [Bug 60501] Re: Exchange fails to allow authentication

2007-07-26 Thread eladner
I'm not seeing the issue any more, but I'm not sure if it was because of a
change in Evolution, or a change in public folders managed by the company.
I no longer have 10's of thousands of folders like I did before, but I can't
tell if somebody cleaned up the folders or Evo just ignores them.

On 7/25/07, Bill Gjestvang [EMAIL PROTECTED] wrote:

 Is anyone still seeing this in current releases (feisty or gutsy)?
 Answers either way would be helpful. Feisty was much improved for this
 sort of evolution stuff, in my experience.

 ** Changed in: evolution-exchange (Ubuntu)
  Assignee: (unassigned) = Bill Gjestvang
Status: New = Incomplete

 --
 Exchange fails to allow authentication
 https://bugs.launchpad.net/bugs/60501
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Eric Ladner

-- 
Exchange fails to allow authentication
https://bugs.launchpad.net/bugs/60501
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 60501] Re: Exchange fails to allow authentication

2006-12-09 Thread eladner
I have the same issue with Evolution.  Tens of thousands of public
folders.  Sounds like what is needed is an option in the exchange
connector to turn off public folders altogether

-- 
Exchange fails to allow authentication
https://launchpad.net/bugs/60501

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs