from:"Daniel Gnoutcheff"

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1335738/+attachment/4142349/+files/ProcEnviron.txt

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

Title:
  autostarts under gnome3, conflicts with gnome-shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1335738/+subscriptions

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

[Bug 1335738] [NEW] autostarts under gnome3, conflicts with gnome-shell

Public bug reported:

To reproduce:
1) Install Gnome 3 (e.g. as part of Ubuntu GNOME, package 
   'ubuntu-gnome-desktop')
2) Install some other desktop environment where light-locker is useful (e.g.
   xfce or lxde).
3) Install light-locker

Expected:
light-locker should only be autolaunched when the selected DE needs a
generic screen locker (e.g. xfce or lxde).  Gnome 3 has its own screen
locker that's integrated with gnome-shell, so light-locker generally should
not be run under Gnome 3.

Actual:
1) light-locker is autolaunched when Gnome 3 is started.
2) I have my system configured to lock the screen when going to sleep.
   However, when I resume from sleep, sometimes find that light-locker has
   grabbed the keyboard and mouse.  This prevents me from using
   gnome-shell's unlock screen.
--- 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 14.04
Package: light-locker 1.4.0-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Tags:  trusty
Uname: Linux 3.13.0-30-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-04-15 (75 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse kvm lpadmin plugdev 
sambashare sudo tape vboxusers video wireshark
_MarkForUpload: True

** Affects: light-locker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected trusty

** Tags added: apport-collected trusty

** Description changed:

  To reproduce:
  1) Install Gnome 3 (e.g. as part of Ubuntu GNOME, package 
 'ubuntu-gnome-desktop')
  2) Install some other desktop environment where light-locker is useful (e.g.
 xfce or lxde).
  3) Install light-locker
  
  Expected:
  light-locker should only be autolaunched when the selected DE needs a
  generic screen locker (e.g. xfce or lxde).  Gnome 3 has its own screen
  locker that's integrated with gnome-shell, so light-locker generally should
  not be run under Gnome 3.
  
  Actual:
  1) light-locker is autolaunched when Gnome 3 is started.
  2) I have my system configured to lock the screen when going to sleep.
 However, when I resume from sleep, sometimes find that light-locker has
 grabbed the keyboard and mouse.  This prevents me from using
 gnome-shell's unlock screen.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 14.04
+ Package: light-locker 1.4.0-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
+ Tags:  trusty
+ Uname: Linux 3.13.0-30-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2014-04-15 (75 days ago)
+ UserGroups: adm admin cdrom dialout dip fax floppy fuse kvm lpadmin plugdev 
sambashare sudo tape vboxusers video wireshark
+ _MarkForUpload: True

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

Title:
  autostarts under gnome3, conflicts with gnome-shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1335738/+subscriptions

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

[Bug 1335738] Dependencies.txt

apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1335738/+attachment/4142348/+files/Dependencies.txt

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

Title:
  autostarts under gnome3, conflicts with gnome-shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1335738/+subscriptions

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

Re: [Bug 1335738] Re: autostarts under gnome3, conflicts with gnome-shell

On 06/30/2014 04:26 AM, Simon Steinbeiß wrote:
 Hey,
 I have to admit that this was not an anticipated use-case. Either way, 
 light-locker installs a desktop-file into /etc/xdg/autostart to ensure it's 
 getting started up when a session starts. It cannot know which DE people want 
 to use it with, so we will certainly not add some built-in DE detection.

I don't think light-locker would have to do DE detection.  The autostart
specification allows applications to be enabled/disabled by DE via the
OnlyShownIn and NotShownIn keys.  The DEs themselves enforce these keys,
and many autostart files use them.  See:

http://standards.freedesktop.org/autostart-spec/autostart-
spec-0.5.html#idm140084019414432

 The useful thing that you can do to fix your problem is to make sure it
 gets started in your other sessions by adding it to the session
 autostart and removing the entry from /etc/xdg/autostart (or: see if
 gnome-shell can actually inhibit starting certain apps, as I'm not a
 gnome user I wouldn't know).

AFAIK Gnome respects the OnlyShownIn and NotShownIn keys in autostart
files.  (Practically speaking, though, I'll probably just replace
light-locker with xscreensaver, as the former breaks when using GDM.)

 In the end I'd say this is not a bug in light-locker, it's entirely
 expected that it autostarts *by default* after you install it.

While I agree that convenient defaults are nice, it's more important
that the defaults be safe.  Blindly injecting light-locker into every
installed DE is not a safe default.

In my case, I installed light-locker to satisfy a recommends
dependency in xfce4-session, so I expected that it would only run under
xfce.  I did not expect that it would run under other DEs, and I
certainly didn't expect that it would *break* things.  It took me
several days to figure out why my Gnome sessions were occasionally
locking up.

I think any one of the following would address this issue:

  - Have at least one of light-locker and gnome-shell declare a
'breaks' dependency on the other (so apt-get will refuse to install
them both).

  - Add 'NotShowIn=GNOME;' to /etc/xdg/autostart/light-locker.desktop,
i.e. blacklist those DEs known to conflict with light-locker.

  - Add 'OnlyShowIn=XFCE;LXDE;' to
/etc/xdg/autostart/light-locker.desktop, i.e. whitelist those DEs
known to benefit from light-locker.

  - Remove /etc/xdg/autostart/light-locker.desktop and have the DEs
start light-locker themselves if and when they want it.  (I think
xfce and razor-qt use xscreensaver this way.)

HTH! (Disclaimer: I haven't actually tested these ideas.)

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

Title:
  autostarts under gnome3, conflicts with gnome-shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1335738/+subscriptions

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

[Bug 1336065] [NEW] Does not fail gracefully when lighdm isn't running

Public bug reported:

To reproduce:
1) install gdm and use it as the display manager
2) install light-locker and xfce (another DE that uses light-locker would
   probably work as well).  Observe that the light-locker package does not
   declare lightdm as a dependency, nor does it conflict with gdm.
3) login with xfce
4) lock the screen (e.g. with a suspend/resume cycle or with the command 
   'sudo loginctl lock-session $XDG_SESSION_ID')

Expected: one of the following should happen:
  - APT should prohibit me from installing light-locker (i.e. light-locker
and gdm should be declared as conflicting packages)
-or-
  - light-locker should refuse to run when gdm is the display manager
-or-
  - light-locker should support gdm (i.e. it should get gdm to spawn a login
screen and display it)

Result:
- light-locker is installable and runnable even when gdm is the display
  manager.
- The screen goes black and displays the message This session is locked:
  You'll be redirected to the unlock dialog automatically in a few seconds.
  However, the promised redirection never happens, leaving the user with no
  discoverable way to unlock their session.
- If there happens to be a gdm login screen running on another VT, then I
  can unlock the session by manually switching to gdm's VT and trying to
  login as the user to whom the locked session belongs.
- However, it's often the case that no such login screen is running.  The
  only way I know how to unlock the session without the login screen is to
  get to a command line somewhere and run 
  'sudo loginctl unlock-session [locked session ID]'.
- While the system does start the gdm login screen after the last user
  logs out or when someone uses the switch user function in (at least)
  Gnome or Xfce, it does not appear that light-locker ever manages to start
  it when locking a session.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: light-locker 1.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun 30 13:00:29 2014
SourcePackage: light-locker
UpgradeStatus: Upgraded to trusty on 2014-04-15 (76 days ago)

** Affects: light-locker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  Does not fail gracefully when lighdm isn't running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1336065/+subscriptions

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

[Bug 1335452] [NEW] single file drag-and-drop incorrectly handled

2014-06-28 Thread Daniel Gnoutcheff

Public bug reported:

To reproduce:
  1) Start meld.
  2) Click File comparison.
  3) Pick a single text file in nautilus, and then drag and drop the
 file onto one of the file selection buttons [i.e. one of the
 buttons with the text (None)].

Expected: Meld should either:
  - Accept the dropped file as one of the files to compare, i.e. the
file selection button should now show the name of the file I just
dropped.
*or*
  - Reject the drop -- it should not respond to the drag, and dropping
should cause the dragged file to snap back to the nautilus window
from which it was dragged.

Actual:
  - While dragging, Meld visually promises to accept the dragged file: a
+ shows up next to the mouse cursor, and it even highlights the
file selection button with a black border when the dragged file is
hovering over it.
  - But when I actually drop the file, Meld fails to keep this promise:
it apparently does nothing with the file, as the file selection
button still shows (None) as the filename.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: meld 1.8.4-1
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jun 28 11:22:20 2014
PackageArchitecture: all
SourcePackage: meld
UpgradeStatus: Upgraded to trusty on 2014-04-15 (74 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  single file drag-and-drop incorrectly handled

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

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

[Bug 1335457] [NEW] files on network mountpoints unsupported but file picker displays them

2014-06-28 Thread Daniel Gnoutcheff

Public bug reported:

To reproduce:
  1) Use nautilus to mount a remote SSH share.
  2) Start Meld
  3) Click File comparison
  4) Click one of the file selection buttons [with the text (None)].
  5) A file picker dialog opens.  Observe that this dialog permits you
 to select files on network shares.
  6) Pick some file on the SSH share mounted earlier, and click Open.

Expected: Meld should either:
  - Support reading files from network shares (like my SSH mountpoint).
*or*
  - Restrict the file picker such that the user can only select files on
the local filesystem (so that step 6 above isn't allowed).

Actual:  Meld's file picker allows me to select a file from my SSH
mountpoint and thus implicit promises to handle such files.  But when I
click Open, Meld silently rejects the file and continues to
show (None) in the file selection button.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: meld 1.8.4-1
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jun 28 12:12:25 2014
PackageArchitecture: all
SourcePackage: meld
UpgradeStatus: Upgraded to trusty on 2014-04-15 (74 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  files on network mountpoints unsupported but file picker displays them

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

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

[Bug 1329130] [NEW] Can't link to files with spaces in their filenames

2014-06-11 Thread Daniel Gnoutcheff

Public bug reported:

To reproduce:
1. Identify (or create) a file with a space in its filename, e.g. 
'/home/gnoutchd/Lots of Junk.txt'
2. Select that file in nautilus and choose 'Copy' from the right-click context 
menu.
3. Open a note in Gnote and paste.

Expected:  Gnote inserts a (working) link the file '/home/gnoutchd/Lots
of Junk.txt'.

Actual: Gnote inserts the text '/home/gnoutchd/Lots of Junk.txt', but
only the prefix '/home/gnoutchd/Lots' gets highlighted as a link.  When
that link is clicked, Gnote attempts to open the URL
'file:///home/gnoutchd/Lots', which is not what I wanted to link to.  If
a file with this truncated name happens to exist, Gnote opens it;
otherwise, I get an info dialog with the text:

 Cannot open location

 file:///home/gnoutchd/Lots: Error when getting information for file 
 '/home/gnoutchd/Lots': No such file or directory

As a workaround, I can still generate a link to the desired file by
typing in a percent-quoted URL, e.g.
'file:///home/gnoutchd/Lots%20of%20Junk.txt'.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnote 3.10.3-1
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jun 11 20:35:58 2014
SourcePackage: gnote
UpgradeStatus: Upgraded to trusty on 2014-04-15 (57 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Can't link to files with spaces in their filenames

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

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

[Bug 1324728] [NEW] ibus-daemon high memory usage

2014-05-29 Thread Daniel Gnoutcheff

Public bug reported:

After surfing the web in firefox for a while, I observed that ibus-
daemon was occupying a surprisingly large amount of memory (smem reports
its unique set size [USS] as 107 MiB). This is much higher than the
usage observed shortly after login (about 1.3 MiB USS).

Not sure yet if there's anything in particular needed to trigger this.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ibus 1.5.5-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu May 29 20:02:38 2014
ExecutablePath: /usr/bin/ibus-daemon
SourcePackage: ibus
UpgradeStatus: Upgraded to trusty on 2014-04-15 (44 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  ibus-daemon high memory usage

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

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

[Bug 1316399] [NEW] Podcast episodes deleted if played while waiting for download

2014-05-05 Thread Daniel Gnoutcheff

Public bug reported:

To reproduce:

1) Find a podcast that (a) has at least three episodes in it and (b) has
   episodes that are sufficiently long that you can perform step (5)
   below while waiting for one to download.  (I encountered this bug on
   http://www.npr.org/rss/podcast.php?id=35, which is the podcast for
   the U.S.A. radio show Wait Wait Don't Tell Me by NPR).
2) Subscribe to the podcast (i.e. select Podcasts under Library,
   click Add, enter the URL in the search box, click Search, click
   Subscribe, and click Close.).
3) Rhythmbox will download only the most recent episode.  Wait for that
   download to complete.
4) Select at two of the older (not yet downloaded) episodes with
   ctrl-click.  Then right-click on the selected episodes and choose
   download episode from the context menu.  Rhythmbox will start
   downloading one episode and mark the other as waiting.
5) Before that download completes, double-click on the waiting episode.

Results:
1) The double-clicked episode immediately starts playing, but it still
   displays its status as waiting.  The existing download is not
   interrupted.
2) When the existing download completes, the double-clicked episode
   continues to play but also starts downloading, apparently from the
   beginning.
3) When the double-clicked episode finishes downloading, it abruptly
   stops playing and then disappears from the episode list.  After this,
   the episode is no longer visible anywhere in Rhythmbox.  This
   persists even after a restart.

Expected result: Not sure what I would expect, but episodes most
certainly should not be getting deleted. ;)

The attached 'rbx.log' contains the output of 'rhythmbox -d' when
performing the performing the procedure described above.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon May  5 23:57:48 2014
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to trusty on 2014-04-15 (20 days ago)

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


** Tags: amd64 apport-bug trusty

** Attachment added: rbx.log
   https://bugs.launchpad.net/bugs/1316399/+attachment/4106018/+files/rbx.log

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

Title:
  Podcast episodes deleted if played while waiting for download

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

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

[Bug 1315510] [NEW] EDS (Evolution) contacts integration is missing

2014-05-02 Thread Daniel Gnoutcheff

Public bug reported:

Ubuntu's Thunderbird used to support reading and writing contacts from
the Evolution address book, presumably though the Thunderbird EDS
Contacts extension https://launchpad.net/thunderbird-eds-extension. In
trusty, this extension appears to be missing, and the contacts in my
Evolution address book (which is my primary address book) are no longer
accessible in Thunderbird.

I really liked this extension, as I enjoy having a centralized address
book on my desktop. I also used the Evolution address book with
syncevolution (for my N900), gnome-shell (via gnome-contacts), and
empathy.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: thunderbird 1:24.5.0+build1-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gnoutchd  16889 F pulseaudio
 /dev/snd/pcmC0D0p:   gnoutchd  16889 F...m pulseaudio
BuildID: 20140428202043
Channel: Unavailable
CurrentDesktop: GNOME
Date: Fri May  2 15:34:44 2014
ForcedLayersAccel: False
IpRoute:
 default via 10.179.201.1 dev eth0  proto static  metric 1024 
 10.179.201.0/24 dev eth0  proto kernel  scope link  src 10.179.201.80 
 10.179.201.0/24 dev wlan0  proto kernel  scope link  src 10.179.201.102
Profile1PrefSources:
 prefs.js
 
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
 
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
 
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
 
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
Profile1Prefs:
 extensions.lastAppVersion: 24.3.0 (prefs.js)
 network.cookie.prefsMigrated: true (prefs.js)
Profile2PrefSources:
 prefs.js
 
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
 
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
 
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
 
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
Profile2Prefs:
 extensions.lastAppVersion: 24.3.0 (prefs.js)
 network.cookie.prefsMigrated: true (prefs.js)
 plugin.importedState: true (prefs.js)
Profiles:
 Profile0 (Default) - LastVersion=24.5.0/20140428202043 (In use)
 Profile1 - LastVersion=24.3.0/20140210221147 (Out of date)
 Profile2 - LastVersion=24.3.0/20140210221147 (Out of date)
RelatedPackageVersions:
 rhythmbox-mozilla 3.0.2-0ubuntu1
 totem-mozilla 3.10.1-1ubuntu4
 gnome-shell   3.10.4-0ubuntu5
RfKill:
 1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: Upgraded to trusty on 2014-04-15 (17 days ago)
WpaSupplicantLog:
 
dmi.bios.date: 02/27/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETD0WW (2.30 )
dmi.board.name: 7733A82
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETD0WW(2.30):bd02/27/2012:svnLENOVO:pn7733A82:pvrThinkPadR61/R61i:rvnLENOVO:rn7733A82:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7733A82
dmi.product.version: ThinkPad R61/R61i
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug trusty

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

Title:
  EDS (Evolution) contacts integration is missing

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

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

[Bug 1290113] Re: media player (Nokia N900) not detected

2014-04-15 Thread Daniel Gnoutcheff

I've just upgraded to trusty, and I still can reproduce this bug.

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

Title:
  media player (Nokia N900) not detected

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

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

[Bug 1290113] [NEW] media player (Nokia N900) not detected

2014-03-09 Thread Daniel Gnoutcheff

Public bug reported:

To reproduce:
- Launch Rhythmbox
- Plug in a Nokia N900 and select mass storage mode.

Expected:
- Rhythmbox detects the N900 as a media player (USB mass storage), lists it 
under Devices, and allows the user to manage the music on it.

Actual:
- Rhythmbox does not respond at all to the presense of the N900.

This bug is a regression: it used to work in previous Ubuntu versions,
and it also works in the rhythmbox shipped in Debian 7 (wheezy).

Some interesting-looking output from 'rhythmbox --debug':
 device /dev/sdb has no ID_MEDIA_PLAYER tag in udev
 /media/gnoutchd/Nokia N900 is already a mount point
 override file /media/gnoutchd/Nokia N900/.is_audio_player not found on mount 
 /media/gnoutchd/Nokia N900

The attached 'n900-udev.txt' contains an extract of the output of
'udevadm info --export-db'. Note that ID_MEDIA_PLAYER is set on
'/devices/pci:00/:00:1a.7/usb1/1-3', but it is not set on the
entry that corresponds to the actual /dev/sdb device
('/devices/pci:00/:00:1a.7/usb1/1-3/1-3:1.0/host19/target19:0:0/19:0:0:0/block/sdb').
This is a change from Debian wheezy, where ID_MEDIA_PLAYER is set on
both.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sun Mar  9 16:07:26 2014
MarkForUpload: True
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to saucy on 2013-10-18 (141 days ago)

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


** Tags: amd64 apport-bug saucy

** Attachment added: n900-udev.txt
   
https://bugs.launchpad.net/bugs/1290113/+attachment/4015423/+files/n900-udev.txt

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

Title:
  media player (Nokia N900) not detected

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

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

[Bug 1290197] [NEW] Yahoo! finance changes have broken quote retreival

2014-03-09 Thread Daniel Gnoutcheff

Public bug reported:

Finance::Quote is no longer able to retrive quotes from Yahoo (at least when it 
is used though Gnumeric).  It works again if I edit 
/usr/share/perl5/Finance/Quote/Yahoo/USA.pm to replace 
 $YAHOO_URL = (http://finance.yahoo.com/d;);
with
 $YAHOO_URL = (http://download.finance.yahoo.com/d/quotes.csv;);

This has already been addressed upstream and in Debian:
  
https://github.com/finance-quote/finance-quote/commit/a4cfca753c45c41fd8d44be0070b7a7aabe8ca79
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739142

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: libfinance-quote-perl 1.17+git20120506-1 [modified: 
usr/share/perl5/Finance/Quote/Yahoo/USA.pm]
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sun Mar  9 23:45:30 2014
MarkForUpload: True
PackageArchitecture: all
SourcePackage: libfinance-quote-perl
UpgradeStatus: Upgraded to saucy on 2013-10-18 (142 days ago)

** Affects: libfinance-quote-perl (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: libfinance-quote-perl (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug saucy

** Bug watch added: Debian Bug tracker #739142
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739142

** Also affects: libfinance-quote-perl (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739142
   Importance: Unknown
   Status: Unknown

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

Title:
  Yahoo! finance changes have broken quote retreival

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfinance-quote-perl/+bug/1290197/+subscriptions

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

[Bug 1290197] Re: Yahoo! finance changes have broken quote retrieval

2014-03-09 Thread Daniel Gnoutcheff

** Summary changed:

- Yahoo! finance changes have broken quote retreival
+ Yahoo! finance changes have broken quote retrieval

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

Title:
  Yahoo! finance changes have broken quote retrieval

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfinance-quote-perl/+bug/1290197/+subscriptions

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

[Bug 1289571] [NEW] middle-clicking message tray icon causes keyboard and mouse input blockage

2014-03-07 Thread Daniel Gnoutcheff

Public bug reported:

If I middle-click on an icon in the gnome-shell message tray, I am no
longer able to interact with any open applications until I restart the
shell.  If I run xdotool key XF86LogGrabInfo in SSH, X reports in
/var/log/Xorg.0.log that gnome-shell is holding input grabs:

[127752.125] (II) Printing all currently active device grabs:
[127752.125] Active grab 0x100 (xi2) on device 'Virtual core pointer' (2):
[127752.125]   client pid 2743 /usr/bin/gnome-shell
[127752.125]   at 118408724 (from active grab) (device thawed, state 1)
[127752.125]   xi2 event mask for device 2: 0xf0100
[127752.125]   owner-events false, kb 1 ptr 1, confine 0, cursor 0x0
[127752.125] Active grab 0x100 (xi2) on device 'Virtual core keyboard' (3):
[127752.125]   client pid 2743 /usr/bin/gnome-shell
[127752.125]   at 118408724 (from active grab) (device thawed, state 1)
[127752.125]   xi2 event mask for device 3: 0xc000
[127752.125]   owner-events false, kb 1 ptr 1, confine 0, cursor 0x0

It appears as though this may have already been reported and fixed
upstream, but it does not appear to have been backported to 3.8.x:
https://bugzilla.gnome.org/show_bug.cgi?id=700854

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.8.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Fri Mar  7 12:49:51 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.desktop.interface' b'clock-format' b'12h'
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
 b'org.gnome.desktop.interface' b'gtk-im-module' b'gtk-im-context-simple'
MarkForUpload: True
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to saucy on 2013-10-18 (139 days ago)

** Affects: gnome-shell
 Importance: Unknown
 Status: Unknown

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

** Bug watch added: GNOME Bug Tracker #700854
   https://bugzilla.gnome.org/show_bug.cgi?id=700854

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=700854
   Importance: Unknown
   Status: Unknown

** Description changed:

  If I middle-click on an icon in the gnome-shell message tray, I am no
  longer able to interact with any open applications until I restart the
  shell.  If I run xdotool key XF86LogGrabInfo in SSH, X reports in
  /var/log/Xorg.0.log that gnome-shell is holding input grabs:
  
  [127752.125] (II) Printing all currently active device grabs:
  [127752.125] Active grab 0x100 (xi2) on device 'Virtual core pointer' (2):
- [127752.125]   client pid 2743 /usr/bin/gnome-shell 
+ [127752.125]   client pid 2743 /usr/bin/gnome-shell
  [127752.125]   at 118408724 (from active grab) (device thawed, state 1)
  [127752.125]   xi2 event mask for device 2: 0xf0100
  [127752.125]   owner-events false, kb 1 ptr 1, confine 0, cursor 0x0
  [127752.125] Active grab 0x100 (xi2) on device 'Virtual core keyboard' 
(3):
- [127752.125]   client pid 2743 /usr/bin/gnome-shell 
+ [127752.125]   client pid 2743 /usr/bin/gnome-shell
  [127752.125]   at 118408724 (from active grab) (device thawed, state 1)
  [127752.125]   xi2 event mask for device 3: 0xc000
  [127752.125]   owner-events false, kb 1 ptr 1, confine 0, cursor 0x0
  
- It appears as thought this may have already been reported and fixed
+ It appears as though this may have already been reported and fixed
  upstream, but it does not appear to have been backported to 3.8.x:
  https://bugzilla.gnome.org/show_bug.cgi?id=700854
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-shell 3.8.4-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Mar  7 12:49:51 2014
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  b'org.gnome.desktop.interface' b'clock-format' b'12h'
-  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
-  b'org.gnome.desktop.interface' b'gtk-im-module' b'gtk-im-context-simple'
+  b'org.gnome.desktop.interface' b'clock-format' b'12h'
+  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
+  b'org.gnome.desktop.interface' b'gtk-im-module' b'gtk-im-context-simple'
  MarkForUpload: True
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (139 days ago)

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

Title:
  middle-clicking message tray icon causes keyboard and mouse input
  blockage

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

-- 
ubuntu-bugs mailing list

[Bug 850939] Re: [i965gm] GPU lockup EIR:0x00000010, followed by PLL state assertion failure

2013-11-08 Thread Daniel Gnoutcheff

I have not encountered this bug in a long time, and I believe that it is
fixed in the kernel as of upstream commit 3eef8918, which is included in
v3.5 and later.  The fix was backported to v3.2.y kernels with commit
71583724, which is included in v3.2.21 and later.

So, quantal and later have the fix because they use kernel v3.5 and
later, precise has this fix because it tracks the upstream v3.2.y stable
kernel, and if my memory is correct, lucid was never affected by this
bug.  So, this bug no longer affects any supported version of Ubuntu.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Fix Released

** Changed in: linux (Ubuntu Precise)
   Status: New = 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/850939

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 1124789] Patch forwarded to hostapd list

2013-05-15 Thread Daniel Gnoutcheff

On 04/15/2013 11:45 AM, Mathieu Trudel-Lapierre wrote:
 The patch does make some sense to me; so I'd be in favor of including it
 once it got a review from upstream. In order to speed up this process,
 would you be up to sending the patch on the hostapd mailing list?

Sure, patch (lightly edited and) sent.
(Message-Id 1368678090-7021-1-git-send-email-dan...@gnoutcheff.name)

Sorry about my super-slow response time. :)

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

Title:
  Unclean termination on dbus-daemon shutdown

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

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

[Bug 1024482] Better workaround

2013-02-28 Thread Daniel Gnoutcheff

While mucking around in gtk/gdk, I discovered a better workaround for
this bug.  While logged in as some user with sudo access, run the commands:

echo GDK_CORE_DEVICE_EVENTS=true | sudo tee ~lightdm/.pam_environment
sudo chown lightdm:lightdm ~lightdm/.pam_environment

This ensures that the next time any one of the lightdm greeters are run,
it will have an environment variable named GDK_CORE_DEVICE_EVENTS set.
This in turn causes gdk to disable its use of XInput2, thus avoiding
this bug.  Once those commands are run, xsetroot and friends should work
upon the next login.

HTH!

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

Title:
  Mouse cursor theme does not change from default after login

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

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

Re: [Bug 1024482] Re: Mouse cursor theme does not change from default after login

2013-02-24 Thread Daniel Gnoutcheff

On 02/24/2013 03:25 AM, swiftgeek wrote:
 So i guess that the reason of why webkit/gtk-builder are working is a
 crazy race condition :]

I think the reason that lightdm-webkit-greeter is not affected is that
it links against GTK2, not GTK3.  Both GTK2 and GTK3 define a
gdk_window_set_cursor() function: the GTK3 version uses XInput's
problematic XIDefineCursor function, while the GTK2 version does not.

As for the patch to lightdm-gtk-greeter: I think that works because with
the patch, gdk_window_set_cursor() is no longer called on the root
window, it's only called on windows created by the greeter itself.
These windows disappear once the greeter exits, so any device cursor
definitions would disappear with them.

It's not a problem when a program sets device cursors on it's own
windows: that only affects those windows and the program (presumably)
knows how to deal with them.   It's when something sets a device cursor
on the *root* window that we have problems, because lots of programs
need to work with the root window and many of them don't use XInput2.

 Would it be possible to patch gdk_window_set_cursor() and include fixed one 
 in greeters (eg. as __gdk_window_set_cursor() )
 and post fixed one on gnome's bugzilla?

Yeah, I'll take a shot at a patch.  If we end up modifying the greeters,
though, I think it would be simpler to replace the call to
gdk_window_set_cursor() with a call to XDefineCursor().  The
implementation of gdk_window_set_cursor() is gnarlier than you might
think, since it deals with alternative windowing systems (Win32,
Wayland, HTML5, etc.) and stuff.

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

Title:
  Mouse cursor theme does not change from default after login

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

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

[Bug 1024482] Re: Mouse cursor theme does not change from default after login

2013-02-23 Thread Daniel Gnoutcheff

OK, I think I've tracked down the cause of this bug.

Thanks to MPX (multi-pointer X), it turns out that each X window
(including the root window) may have *multiple* cursor icon settings.
Traditionally, under the core X11 protocol, a window could only define a
standard cursor, which can be set by the XDefineCursor(3) function.
However, XInput2 introduces the possibility of having multiple mouse
pointers on the screen, and it allows windows to define a device
cursor for each pointer individually.  This can be done though XInput's
XIDefineCursor(3) function.  Crucially, if a given window has both a
standard cursor and a device cursor defined, then the device cursor will
override the standard cursor, at least for the particular master
pointer device that the device cursor was defined for.

Here is the relevant extract from the XInput2 protocol specification, which is 
shipped as /usr/share/doc/x11proto-input-dev/XI2proto.html in the 
x11proto-input-dev package:
 Whenever device enters a window W, the cursor shape is selected in the
 following order:
 - if the current window has a device cursor C(d) defined for device,
   display this cursor C(d).
 - otherwise, if the current window has a cursor C(w) defined in the core
   protocol’s window attributes, display cursor C(w).
 - repeat on parent window until a cursor has been found.

On a typical system with a single master pointer device, this means that
once a device pointer is set, the standard cursor setting loses its
effect.  So, if something sets a device pointer on the root window, then
any program that that tries to change the cursor icon by setting the
root window's standard cursor (which includes xsetroot, XFCE, and GNOME)
is sabotaged.

And the final piece: if XInput support is available, GTK3's
implementation of gdk_window_set_cursor will use XIDefineCursor.  Since
both unity-greeter and lightdm-gtk-greeter use gdk_window_set_cursor,
that means both greeters set a device cursor on the root window.  From
that point on, xsetroot and friends are SOL.

The behavior of the xserver is set in the protocol specification, so we
can't fix this problem there. I think the best solution is to get
unity-greeter and lightdm-gtk-greeter to use XDefineCursor instead of
XIDefineCursor.  This might be done by modifying gdk_window_set_cursor()
or by modifying the  greeters to use XDefineCursor directly instead of
deferring to gdk.  swiftgeek's approach might work too, but I think we
can do something simpler than that.

In the meantime, working around this bug is somewhat of a pain because
(1) XIUndefineCursor doesn't seem to work correctly on the root window
(probably an xserver bug, I'll follow up on that later) and (2) the
xserver currently prohibits removal of the initial Virtual core
pointer master pointer device, which is the pointer device that our
greeters are setting a device cursor for.  So, once the device cursor is
set on the root window, I don't think there's any way to get the
standard cursor setting to work again.

A workaround is to (re)set the device cursor instead.  My attached
xiset.c will set the device cursor on the root window to whatever the
default XCursor theme is.  (I originally wrote it while trying to
understand the behavior of gdk_window_set_cursor().)  I set my desired
Xcursor theme in ~/.Xdefaults and have my DE run this program at login.
It does the job for now. I've also heard of an xicursorset tool
floating around, which might do the job as well.

** Attachment added: xiset.c
   
https://bugs.launchpad.net/lightdm/+bug/1024482/+attachment/3544110/+files/xiset.c

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

Title:
  Mouse cursor theme does not change from default after login

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

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

[Bug 1094173]

2013-02-15 Thread Daniel Gnoutcheff

Alright, I am officially convinced that the aforementioned commit does
indeed fix this bug.  During the past month and a half, I made sure that
I was always running a kernel that included that patch, and I have not
seen this bug in that time.

For the record, the patch was released in longterm kernel v3.7.3 as commit
  41c8765e911cf54ad0c71bf3a1642b918af937e8
and in Ubuntu's extended longterm kernel v3.5.7.3 as commit
  13938a31f36fa72027928eddb159327ab5568a46

Thanks!

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

Title:
  compiz terminates with intel_do_flush_locked failed: Device or
  resource busy

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

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

[Bug 1094173]

2013-02-15 Thread Daniel Gnoutcheff

 If the patch works on 3.7 you only need to send the commit sha1 (in
 the 3.8-rc upstream) of it with a link to this bugzilla and a
 tested-by to sta...@vger.kernel.org It will the automatically trickle
 down to stable kernels and distro kernel builds.

Thanks for the advice.  I have had an experience, though, with a stable 
kernel maintainer who wanted the submitted patches to apply with no 
manual effort, not even trivial context changes.  The patch in question 
wouldn't apply to 3.5.7.y without context changes, so I wanted to be safe.

BTW, is this patch relevant for kernels 3.4 and older?  The linked 
bugzillas gave me the impression that the bugs addressed by this commit 
have only been witnessed in kernels 3.5 and later, and of those, it 
appears that only 3.7 is maintained on kernel.org.  (3.5.7.y comes from 
Ubuntu's extended longterm kernel effort).

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

Title:
  compiz terminates with intel_do_flush_locked failed: Device or
  resource busy

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

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

[Bug 1124789] [NEW] Unclean termination on dbus-daemon shutdown

2013-02-13 Thread Daniel Gnoutcheff

Public bug reported:

When wpa_supplicant is terminated normally (i.e. with SIGTERM or SIGINT
or 'wpa_cli terminate'), it brings down any wireless interfaces it is
managing.  However, if wpa_supplicant is started by dbus activation and
if the dbus messagebus is then shut down, it terminates abruptly and
improperly without deconfiguring any network interfaces.

Note that wpa_supplicant has its PID file installed in
/run/sendsigs.omit.d, so /etc/init.d/sendsigs makes no attempt to shut
it down. Since wpa_supplicant is not supervised by upstart, it is
typical for dbus-daemon to be shut down before wpa_supplicant is.

This has been reported upstream (along with steps to reproduce and a patch) at:
  http://w1.fi/bugz/show_bug.cgi?id=474

This bug, along with a bug in network-manager (which I will report separately), 
means that when I connect my laptop to a wifi network, no attempt is made to 
disconnect from that network when shutting the system down. This in turn 
triggers a bug in my BIOS which causes this system to hardlock in the middle of 
BIOS post when I reboot while still connected to a wifi network:
  http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: wpasupplicant 1.0-2ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
Uname: Linux 3.5.0-24-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Wed Feb 13 22:12:08 2013
MarkForUpload: True
SourcePackage: wpa
UpgradeStatus: Upgraded to quantal on 2012-10-20 (116 days ago)

** Affects: hostap
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug quantal running-unity

** Bug watch added: w1.fi/bugz/ #474
   http://w1.fi/bugz/show_bug.cgi?id=474

** Also affects: hostap via
   http://w1.fi/bugz/show_bug.cgi?id=474
   Importance: Unknown
   Status: Unknown

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

Title:
  Unclean termination on dbus-daemon shutdown

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

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

[Bug 1124803] [NEW] NetworkManager doesn't respond to SIGTERM in daemon mode

2013-02-13 Thread Daniel Gnoutcheff

Public bug reported:

NetworkManager does not respond to SIGTERM when started in daemon mode,
as upstart does by default.  This also happens when running
NetworkManager manually from the command line as long as the --no-daemon
option is not used.

This was reported upstream and was fixed by commit
  64342a313ef497fca8a4fb7567900d4a1460065f

It appears that this bug forces upstart to SIGKILL NetworkManager during 
shutdown, which, amoung other things, means that n-m doesn't deconfigure 
network interfaces as intended.  This bug, along with bug 1124789 (in 
wpasupplicant), means that no attempt is made to disconnect from a wifi network 
during shutdown. This in turn triggers a bug in my BIOS which causes this 
system to hardlock in the middle of BIOS post when I reboot while still 
connected to a wifi network:
  http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: network-manager 0.9.6.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
Uname: Linux 3.5.0-24-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Wed Feb 13 22:32:52 2013
IpRoute:
 default via 10.179.201.1 dev eth0  proto static
 10.179.201.0/24 dev eth0  proto kernel  scope link  src 10.179.201.80  metric 1
 10.179.201.0/24 dev wlan0  proto kernel  scope link  src 10.179.201.105  
metric 9
 169.254.0.0/16 dev eth0  scope link  metric 1000
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to quantal on 2012-10-20 (116 days ago)
WpaSupplicantLog:

mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-03-21T22:57:56
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
 eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN
 running 0.9.6.0connected   enabled   enabled 
enabledenabled enabled

** Affects: network-manager
 Importance: Unknown
 Status: Unknown

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug quantal running-unity

** Bug watch added: GNOME Bug Tracker #683932
   https://bugzilla.gnome.org/show_bug.cgi?id=683932

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=683932
   Importance: Unknown
   Status: Unknown

** Description changed:

  NetworkManager does not respond to SIGTERM when started in daemon mode,
  as upstart does by default.  This also happens when running
- NetworkManager manually from the command line.
+ NetworkManager manually from the command line as long as the --no-daemon
+ option is not used.
  
  This was reported upstream and was fixed by commit
-   64342a313ef497fca8a4fb7567900d4a1460065f
+   64342a313ef497fca8a4fb7567900d4a1460065f
  
  It appears that this bug forces upstart to SIGKILL NetworkManager during 
shutdown, which, amoung other things, means that n-m doesn't deconfigure 
network interfaces as intended.  This bug, along with bug 1124789 (in 
wpasupplicant), means that no attempt is made to disconnect from a wifi network 
during shutdown. This in turn triggers a bug in my BIOS which causes this 
system to hardlock in the middle of BIOS post when I reboot while still 
connected to a wifi network:
-   http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862
+   http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Wed Feb 13 22:32:52 2013
  IpRoute:
-  default via 10.179.201.1 dev eth0  proto static 
-  10.179.201.0/24 dev eth0  proto kernel  scope link  src 10.179.201.80  
metric 1 
-  10.179.201.0/24 dev wlan0  proto kernel  scope link  src 10.179.201.105  
metric 9 
-  169.254.0.0/16 dev eth0  scope link  metric 1000
+  default via 10.179.201.1 dev eth0  proto static
+  10.179.201.0/24 dev eth0  proto kernel  scope link  src 10.179.201.80  
metric 1
+  10.179.201.0/24 dev wlan0  proto kernel  scope link  src 10.179.201.105  
metric 9
+  169.254.0.0/16 dev eth0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no

[Bug 1124789] Re: Unclean termination on dbus-daemon shutdown

2013-02-13 Thread Daniel Gnoutcheff

** Description changed:

  When wpa_supplicant is terminated normally (i.e. with SIGTERM or SIGINT
  or 'wpa_cli terminate'), it brings down any wireless interfaces it is
  managing.  However, if wpa_supplicant is started by dbus activation and
  if the dbus messagebus is then shut down, it terminates abruptly and
  improperly without deconfiguring any network interfaces.
  
  Note that wpa_supplicant has its PID file installed in
  /run/sendsigs.omit.d, so /etc/init.d/sendsigs makes no attempt to shut
  it down. Since wpa_supplicant is not supervised by upstart, it is
  typical for dbus-daemon to be shut down before wpa_supplicant is.
  
  This has been reported upstream (along with steps to reproduce and a patch) 
at:
-   http://w1.fi/bugz/show_bug.cgi?id=474
+   http://w1.fi/bugz/show_bug.cgi?id=474
  
- This bug, along with a bug in network-manager (which I will report 
separately), means that when I connect my laptop to a wifi network, no attempt 
is made to disconnect from that network when shutting the system down. This in 
turn triggers a bug in my BIOS which causes this system to hardlock in the 
middle of BIOS post when I reboot while still connected to a wifi network:
-   http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862
+ This bug, along with bug 1124803 (in network-manager), means that when I 
connect my laptop to a wifi network, no attempt is made to disconnect from that 
network when shutting the system down. This in turn triggers a bug in my BIOS 
which causes this system to hardlock in the middle of BIOS post when I reboot 
while still connected to a wifi network:
+   http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: wpasupplicant 1.0-2ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Wed Feb 13 22:12:08 2013
  MarkForUpload: True
  SourcePackage: wpa
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (116 days ago)

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

Title:
  Unclean termination on dbus-daemon shutdown

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

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

Re: [Bug 1094173] Re: compiz terminates with intel_do_flush_locked failed: Device or resource busy

2013-02-11 Thread Daniel Gnoutcheff

On 02/08/2013 05:31 AM, Luis Henriques wrote:
 This bug is awaiting verification that the kernel for Quantal in
 -proposed solves the problem (3.5.0-24.37). Please test the kernel and
 update this bug with the results. If the problem is solved, change the
 tag 'verification-needed-quantal' to 'verification-done-quantal'.

OK, I have installed that kernel and I am running it now.  Recall,
however, that this bug is not reliably reproducible and can take several
weeks to manifest,

That said, here's what we have now:

- Upstream believes that commit b4a98e57 fixes this bug.
- A backport of that commit was released in v3.7.3.
- After a mouth and a half, I can vouch for the fact that this bug is
  fixed as of v3.7.3.  (I didn't check if it was present in v3.7.2,
  though.)
- A backport of the same commit was also released in v3.5.7.3, and I'm
  of the understanding this should have trickled down into this
  -proposed kernel.

Based on that, I'm around 95% confident that this kernel does indeed fix
this bug.  If this isn't good enough, then I would need to run this
kernel for at least a month to empirically verify this.

 If verification is not done by one week from today, this fix will be
 dropped from the source code, and this bug will be closed.

I'm not sure what the standards are here -- I'm tempted to just declare
this verified, but I don't know if that's justified.  If it isn't,
then a week will not be enough time.  Please advise.

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

Title:
  compiz terminates with intel_do_flush_locked failed: Device or
  resource busy

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

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

[Bug 1094173] [NEW] compiz terminates with intel_do_flush_locked failed: Device or resource busy

2012-12-27 Thread Daniel Gnoutcheff

Public bug reported:

I'm running unity on Intel GM965 graphics. Occasionally, unity/compiz
will terminate with

  intel_do_flush_locked failed: Device or resource busy

If I then attempt to restart compiz, it initially starts up
successfully, but if I use it a little (e.g. if I open a new window or
move an existing window around), then within a second or so it
terminates again with the same error.  Every attempt to restart compiz
fails in this way, and it continues to fail even if I restart the
xserver.  However, once I reboot the system, compiz runs normally again.

I have reported this upstream at
https://bugs.freedesktop.org/show_bug.cgi?id=58732, and I've attached
various debug logs there.

Chris Wilson believes that commit
b4a98e57fc27854b5938fc8b08b68e5e68b91e1f should fix this. I am in the
process of verifying that, and since that commit is believed to fix
several other bugs in kernels 3.5 and later, it has been submitted for
inclusion in 3.7.y stable kernels.  I will submit a backport (context
update, really) for 3.5.7.y shortly.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-21-generic 3.5.0-21.32
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gnoutchd   2653 F pulseaudio
Date: Thu Dec 27 20:34:55 2012
HibernationDevice: RESUME=UUID=15733ed1-09e8-4ba7-aa20-c7f0136412a5
MachineType: LENOVO 7733A82
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic 
root=UUID=d03dbee7-efb8-45ae-bdbc-e06fb7d61b04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-21-generic N/A
 linux-backports-modules-3.5.0-21-generic  N/A
 linux-firmware1.95
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-10-20 (68 days ago)
WpaSupplicantLog:
 
dmi.bios.date: 04/08/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC7WW (2.27 )
dmi.board.name: 7733A82
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn7733A82:pvrThinkPadR61/R61i:rvnLENOVO:rn7733A82:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7733A82
dmi.product.version: ThinkPad R61/R61i
dmi.sys.vendor: LENOVO

** Affects: linux
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug quantal running-unity

** Bug watch added: freedesktop.org Bugzilla #58732
   https://bugs.freedesktop.org/show_bug.cgi?id=58732

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=58732
   Importance: Unknown
   Status: Unknown

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

Title:
  compiz terminates with intel_do_flush_locked failed: Device or
  resource busy

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

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

[Bug 1082100] [NEW] [REGRESSION] Unable to modify CalDAV items (this.mItemInfoCache[aNewItem.id] is undefined)

2012-11-22 Thread Daniel Gnoutcheff

Public bug reported:

This bug showed up with the 1.9+build1-0ubuntu0.12.10.1 update that I
pulled in yesterday.

Steps to reproduce:
1. Create an event inside a calendar hosted by a CalDAV sever (in my case, a
Darwin Calendar Server instance running on the local machine).
2. Restart Thunderbird.
3. Try to modify that event's start time.

Expected:
The new start time should be shown on the calendar display, and it should be
saved to the CalDAV sever as well

Actual:
The event remains unchanged, both on the local display and on the server. The
Thunderbird error console contains:
Timestamp: 11/22/2012 11:08:42 AM
Error: this.mItemInfoCache[aNewItem.id] is undefined
Source File:
file:///usr/lib/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calDavCalendar.js
Line: 660

It should be noted that other calendar programs can modify the same
event on the CalDAV server, and those modifications show up in Lightning
after a synchronize. Furthermore, this bug does not affect events that
were initially created on the CalDAV server by other calendar programs,
and it also doesn't effect events that were created on that server by
previous versions of Lightning. It only seems to occur when one creates
an event using the latest version of Lightning and then tries to modify
the event (under the same profile) in Lightning. (I'm betting that other
instances of Lighting using different profiles would also be able to
edit it, just like other calendar programs can -- I'll verify this
shortly.)

** Affects: lightning-extension (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/1082100

Title:
[REGRESSION] Unable to modify CalDAV items
(this.mItemInfoCache[aNewItem.id] is undefined)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightning-extension/+bug/1082100/+subscriptions

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

[Bug 1082100] Re: [REGRESSION] Unable to modify CalDAV items (this.mItemInfoCache[aNewItem.id] is undefined)

2012-11-22 Thread Daniel Gnoutcheff

I've just managed to reproduce this issue in a fresh Thunderbird
profile, but it seems I'll need to revise my steps to reproduce. The
offline support feature and the synchronize button seem to be relevant.
Here are my steps to reproduce now:

1) Select a CalDAV calendar with offline support enabled
2) Create an event
3) Click synchronize
4) Restart Thunderbird
5) Try to change the start time of the event created earlier

Also, it turns out that it's not necessary to create the event in Lightning in 
order to trigger this bug: it's also possible to trigger it with events created 
elsewhere, like so:
1) Add a CalDAV calendar to Lightning with Offline Support enabled
2) Close Thunderbird
3) Use another calendar application (I used Evolution) to create an event on 
the same CalDAV calendar
4) Start Thunderbird, the new event should show up on the Lightning calendar 
display as well
5) Click synchronize
6) Restart Thunderbird
7) Try to change the start time of the event created earlier

HTH!

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

Title:
  [REGRESSION] Unable to modify CalDAV items
  (this.mItemInfoCache[aNewItem.id] is undefined)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightning-extension/+bug/1082100/+subscriptions

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

[Bug 1082100] Re: [REGRESSION] Unable to modify CalDAV items (this.mItemInfoCache[aNewItem.id] is undefined)

2012-11-22 Thread Daniel Gnoutcheff

Ugh, sorry about the noise, but I had better clarify:

I said in my initial bug report that this bug does not effect events
created outside of Lightning: just to be clear, it appears that was
wrong about this, and my second comment includes the counterexample I
found. I suspect that I got fooled earlier because I wasn't paying
attention to my use of the synchronize button.

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

Title:
  [REGRESSION] Unable to modify CalDAV items
  (this.mItemInfoCache[aNewItem.id] is undefined)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightning-extension/+bug/1082100/+subscriptions

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

[Bug 850939]

2012-06-04 Thread Daniel Gnoutcheff

OK, I am reasonably confident that the patch from comment 25 fixes this
bug.

 From April 14th to May 22ed, I made sure to use a kernel that contained 
that patch, and I never had any post-resume hangs during that period. 
As an experiment, I then reverted the patch, and it didn't take long to 
get another post-resume hang.  So the application of that patch strongly 
correlates with the absence of these hangs.

Looks good to me. :D

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 850939]

2012-06-04 Thread Daniel Gnoutcheff

--- Comment #28 from Marcos Dionemdi...@grulic.org.ar  2012-06-02 
08:30:32 PDT ---
 how to reproduce: launch ufo, select single player game, skirmish, start game.
 the 3d terrain shows up, but after a few seconds (I woulds say 2-5) it hangs,
 creen goes black and one or two seconds after music stops. the machine is 
 still
 reachable by ssh.

Thanks for the report, Marcos.  Does it hang happen every time you run 
the game?  I was not able to reproduce the hang that way, even without 
the patch from comment 25.  Of course, I have different userspace 
(Ubuntu 12.04 amd64 with playdeb's ufoai) and different hardware (Lenovo 
ThinkPad R61 7733A82).

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 864233] Re: New Window doesn't take focus once launched

2012-04-20 Thread Daniel Gnoutcheff

*** This bug is a duplicate of bug 781931 ***
https://bugs.launchpad.net/bugs/781931

** This bug has been marked a duplicate of bug 781931
   New windows are moved to front but don't take focus

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

Title:
  New Window doesn't take focus once launched

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz-core/+bug/864233/+subscriptions

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

[Bug 850939]

NAK, it appears that the referenced commit does *not* fix this bug.  I
just had another one of these crashes with v3.4-rc1 despite the fact
that it contains this commit.

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 850939]

Created attachment 59973
gnoutchd-v3.4-rc1+-i915_error_state

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 850939]

Created attachment 59974
gnoutchd-v3.4-rc1+-KernelLog.txt

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 850939]

Created attachment 59975
gnoutchd-v3.4-rc1+-intel_reg_dumper.txt

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 850939]

error-state and logs attached as requested.  The running kernel was
compiled from commit v3.4-rc1-271-g5d32c88

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 850939]

--- Comment #24 from Chris Wilsonch...@chris-wilson.co.uk  2012-04-14 
08:46:59 PDT ---
 Wait a sec... Does this hang almost immediately upon boot?

As I described in comment 6, this is a hang that occasionally happens 
immediately after resume from suspend.

I've applied the patch in comment 25 on top of v3.4-rc2-333-g668ce0a and 
I am trying it now.  It doesn't seem to have broken anything, but since 
this hang is rare, unpredictable, and (at present) not reliably 
reproducible, I can't say with confidence that the bug is fixed until 
I've run it for at least a month.

All of my remarks in comment 6 still hold true.  I'm still hoping to 
find a way to quickly reproduce this, but at present, I know nothing at 
all about computer graphics, so I'm stuck behind a huge learning curve.

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 850939]

2012-03-17 Thread Daniel Gnoutcheff

This bug is still present on Ubuntu precise (12.04) beta.  The relevant
package versions are:

kernel: 3.2.0-18.29
libdrm2: 2.4.30-1ubuntu1
libgl1-mesa-glx: 8.0.1-0ubuntu2
xserver-xorg: 1:7.6+10ubuntu1
xserver-xorg-video-intel: 2:2.17.0-1ubuntu4

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 953004] [NEW] Dragging toolbar doesn't move window

2012-03-12 Thread Daniel Gnoutcheff

Public bug reported:

To reproduce:
1) Ensure that the nautilus main toolbar is enabled (View - Main Toolbar)
2) Drag an empty space on the main toolbar

Expected:
The window moves (much like when dragging the titlebar)

Actual:
The drag is ignored

In most other apps, dragging the toolbar does move the window as
expected.  This also worked in nautilus in oneiric, but it no longer
works in precise.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.91-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 12 09:15:41 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '1011x594+118+112'
 org.gnome.nautilus.window-state sidebar-width 151
SourcePackage: nautilus
UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)

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


** Tags: amd64 apport-bug apport-lpi precise

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

Title:
  Dragging toolbar doesn't move window

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

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

[Bug 953004] Re: Dragging toolbar doesn't move window

2012-03-12 Thread Daniel Gnoutcheff

** Description changed:

  To reproduce:
  1) Ensure that the nautilus main toolbar is enabled (View - Main Toolbar)
  2) Drag an empty space on the main toolbar
  
  Expected:
  The window moves (much like when dragging the titlebar)
  
  Actual:
  The drag is ignored
  
  In most other apps, dragging the toolbar does move the window as
- expected.  This also worked in nautilus in oneric, but it no longer
+ expected.  This also worked in nautilus in oneiric, but it no longer
  works in precise.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.3.91-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Mon Mar 12 09:15:41 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
-  org.gnome.nautilus.window-state geometry '1011x594+118+112'
-  org.gnome.nautilus.window-state sidebar-width 151
+  org.gnome.nautilus.window-state geometry '1011x594+118+112'
+  org.gnome.nautilus.window-state sidebar-width 151
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)

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

Title:
  Dragging toolbar doesn't move window

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

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

[Bug 850939]

2012-03-12 Thread Daniel Gnoutcheff

FWIW, I disabled DRI with
  Option DRI false
in xorg.conf, but I still got a hang just now.  That would seem to confirm that 
this regression is not related to the mesa driver.

This is still with the xserver-xorg-video-intel package shipped with
Ubuntu oneric (2:2.15.901-1ubuntu2.1).  I'll see about re-testing with
updated versions of everything.

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

Title:
  [i965gm] GPU lockup EIR:0x0010, followed by PLL state assertion
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/850939/+subscriptions

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

[Bug 500367] Looks like this is fixed.

2012-02-26 Thread Daniel Gnoutcheff

Judging from my quick test, the root cause of this bug is fixed.  I just
saved a .jpg attachment from an e-mail with mime headers that
incorrectly claim that the image is an FLV video, and I selected Do
this automatically for files like this from now on.  In the past, it
seems this would cause mimeTypes.rdf to be infected with an entry that
claimed that files ending in .jpg where FLV videos, and thunderbird
would proceed to use that association when sending .jpg attachments.
But now, with thunderbird version 10.0.2+build1-0ubuntu0.11.10.1,
mimeTypes.rdf remains unaffected.

So, I think we can close this bug, unless we want to do an SRU or
something.  (The bug is gone in oneiric, I don't know about other Ubuntu
versions.)  If you have bugzilla.mozilla.org account, I think you can
close the upstream one as well.

On 02/12/2012 05:07 PM, Don Cristóbal wrote:
 @ Vseerror: I veryfied and I don't see the bug any more. However, I
 don't understand all of the discussion above, so I won't change the
 bug's status. Anyway, I don't see such an entry as worksforme.

It seems that the message you replied to was imported by launchpad from
the upstream bugzilla.mozilla.org entry.  Launchpad doesn't have a
worksforme resolution, but bugzilla does.


** Changed in: thunderbird (Ubuntu)
   Status: New = 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/500367

Title:
  Thunderbird sends .doc attachments with wrong mime-type
  (text/richtext)

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

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

[Bug 925218] Re: Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255

2012-02-24 Thread Daniel Gnoutcheff

This bug continues to affect the updated openjdk-6-jre-headless version 
6b23~pre11-0ubuntu1.11.10.2
It also affects openjdk-7-jre-headless version 7~b147-2.0-0ubuntu0.11.10.1

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

Title:
  Crash in java.net.NetworkInterface.getNetworkInterfaces() when
  ifr_ifindex exceeds 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+subscriptions

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

[Bug 925218] Re: Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255

2012-02-24 Thread Daniel Gnoutcheff

Reported upstream here:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7078386

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

Title:
  Crash in java.net.NetworkInterface.getNetworkInterfaces() when
  ifr_ifindex exceeds 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+subscriptions

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

[Bug 925218] Re: Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255

2012-02-24 Thread Daniel Gnoutcheff

** Also affects: openjdk-7 (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/925218

Title:
  Crash in java.net.NetworkInterface.getNetworkInterfaces() when
  ifr_ifindex exceeds 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+subscriptions

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

[Bug 923372] Re: Thunderbird 10 update

2012-02-17 Thread Daniel Gnoutcheff

Indeed, both xul-ext-lightning and enigmail are rendered worthless (for
thunderbird at least) by this update.  Meanwhile, removing the packages
and installing the extensions from addons.mozilla.org works fine (at
least on this amd64 machine).

If stable updates are going to continue to cause these kinds of random
(and *severe*) regressions in these packages, then nobody should be
relying on them. I'd like to see them removed from the archive,
especially since an (apparently *much* better supported) update
mechanism already exists from addons.mozilla.org.

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

Title:
  Thunderbird 10 update

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

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

[Bug 925218] [NEW] Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255

Public bug reported:

If the system contains at least one network interface in state UP
whose interface index (ifr_ifindex) is greater than 255, any calls to
java.net.NetworkInterface.getNetworkInterfaces() will fail horribly,
usually with a glibc-detected buffer overflow.  This is on Ubuntu 11.10
amd64 with openjdk-6-jre-headless version 6b23~pre11-0ubuntu1.11.10.1 0

Interface index numbers can get quite large when we're on a system where
network interfaces are added and removed frequently.  For example,
miredo (a teredo implementation) seems to create and destroy a tuntap
interface whenever we need to reestablish the teredo tunnel -- which can
be quite often on a laptop.  High interface numbers can also be induced
artificially by repeatedly adding and removing, say, a macvlan
interface.

I'm attaching a simple shell script that demonstrates this bug, along
with the glibc buffer overflow crash output that results. I'm also
attaching a gdb backtrace.

The problem seems to be caused by the Linux version of the
enumIPv6Interfaces function in
openjdk/jdk/src/solaris/native/java/net/NetworkInterface.c, which
attempts to parse the contents of /proc/net/if_inet6.  When we have an
interface with a high index, that file looks something like this:

 fe80 10b 40 20 80   teredo
 2001--address-edited-out-- 10b 20 00 80   teredo
 fe80021558fffec629b6 02 40 20 80 eth0
 fe8002197efffec16a76 03 40 20 80wlan0
 0001 01 80 10 80   lo

The second column contains the interface index in hex.  Notice that it's 
normally two characters long, but it becomes longer when the index exceeds 255. 
 However, enumIPv6Interfaces uses fscanf with the format string
  %4s%4s%4s%4s%4s%4s%4s%4s %02x %02x %02x %02x %20s\n
which insists that the index is only two characters long.  Thus, an index 
that's 3 chars long causes fscanf to give us lots of garbage, eventually 
resulting in a crash when we try to do something with the nonsense.

I'm attaching a patch that contains a simple fix.  However, it might be
a good idea to find a better way to do this and replace this fragile
parsing stuff altogether, esp. since the kernel docs don't even bother
to document the format of /proc/net/if_inet6.  (Netlink, maybe?  How
does 'ip addr list' do it?)

** Affects: openjdk-6 (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/925218

Title:
  Crash in java.net.NetworkInterface.getNetworkInterfaces() when
  ifr_ifindex exceeds 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+subscriptions

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

[Bug 925218] Re: Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255

** Attachment added: Shell script to reproduce bug
   
https://bugs.launchpad.net/bugs/925218/+attachment/2706628/+files/test-case.sh

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

Title:
  Crash in java.net.NetworkInterface.getNetworkInterfaces() when
  ifr_ifindex exceeds 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+subscriptions

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

[Bug 925218] Re: Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255

** Attachment added: Crash output from test script
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+attachment/2706629/+files/test-case-output.txt

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

Title:
  Crash in java.net.NetworkInterface.getNetworkInterfaces() when
  ifr_ifindex exceeds 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+subscriptions

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

[Bug 925218] Re: Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255

** Attachment added: Backtrace of crash from GDB
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+attachment/2706630/+files/gdb-backtrace.txt

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

Title:
  Crash in java.net.NetworkInterface.getNetworkInterfaces() when
  ifr_ifindex exceeds 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/925218/+subscriptions

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

[Bug 925218] Re: Crash in java.net.NetworkInterface.getNetworkInterfaces() when ifr_ifindex exceeds 255