from:"Ernie 07"

** Attachment added: BUG_SoftwareCenter_ChromeInstall_2014-03-25 21:41:05.png

https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+attachment/4045973/+files/BUG_SoftwareCenter_ChromeInstall_2014-03-25%2021%3A41%3A05.png

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1298188

Title:
Software Center KAPUT on or about 2014-03_12

Status in “software-center” package in Ubuntu:
New

Bug description:
Software Center correctly installed the following programs when
executed following the 64-bit 2014-03_11.iso Desktop Installation
(3.13.0-16-generic #36-Ubuntu SMP Tue Mar 4 23:02:40 UTC 2014):

1. Ubuntu Restricted Extras
2. Google Chrome Debian install
3. GParted
4. VLC
5. Unetbootin

Software Center will hang if the first program installed is Ubuntu
Restricted Extras. This bug manifests in every install after
2014-03_11 that I tested including the 2014-03_25 iso.

Software Center will fail with a Package operation failed error when a
Google Chorme Debian install is attempted. After that an attempt to
install Ubuntu Restricted Extras or GParted would fail with the same
error. Note, if the first program installed was GParted rather than
Google Chrome or Unbuntu Restricted Extras, the GParted installation
would be successful.

Knowing the approximate date that the failure was introduced should
help. Also, I am somewhat concerned that usability regression testing
may not catch this because the problem manifests differently depending
upon which program is installed first.

Finally, if I install from 2014-03-11 and then update to
(3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:06 UTC 2014) the
failures described above will occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1298188] Re: Software Center KAPUT on or about 2014-03_12

** Attachment added: BUG_SofwareCenter_OnlyInstall_UbuntuRestricted_2014-03-25
22:08:08.png

https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+attachment/4045972/+files/BUG_SofwareCenter_OnlyInstall_UbuntuRestricted_2014-03-25%2022%3A08%3A08.png

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1298188

Title:
Software Center KAPUT on or about 2014-03_12

Status in “software-center” package in Ubuntu:
New

1. Ubuntu Restricted Extras
2. Google Chrome Debian install
3. GParted
4. VLC
5. Unetbootin

Software Center will hang if the first program installed is Ubuntu
Restricted Extras. This bug manifests in every install after
2014-03_11 that I tested including the 2014-03_25 iso.

Finally, if I install from 2014-03-11 and then update to
(3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:06 UTC 2014) the
failures described above will occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+subscriptions

[Desktop-packages] [Bug 1298188] Re: Software Center KAPUT on or about 2014-03_12

** Attachment added: BUG_SoftwareCenter_GpartedInstall_After failed
Chrome_2014-03-25 21:53:52.png

https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+attachment/4045976/+files/BUG_SoftwareCenter_GpartedInstall_After%20failed%20Chrome_2014-03-25%2021%3A53%3A52.png

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1298188

Title:
Software Center KAPUT on or about 2014-03_12

Status in “software-center” package in Ubuntu:
New

1. Ubuntu Restricted Extras
2. Google Chrome Debian install
3. GParted
4. VLC
5. Unetbootin

Software Center will hang if the first program installed is Ubuntu
Restricted Extras. This bug manifests in every install after
2014-03_11 that I tested including the 2014-03_25 iso.

Finally, if I install from 2014-03-11 and then update to
(3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:06 UTC 2014) the
failures described above will occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+subscriptions

[Desktop-packages] [Bug 1298188] [NEW] Software Center KAPUT on or about 2014-03_12

Public bug reported:

Software Center correctly installed the following programs when executed
following the 64-bit 2014-03_11.iso Desktop Installation
(3.13.0-16-generic #36-Ubuntu SMP Tue Mar 4 23:02:40 UTC 2014):

1. Ubuntu Restricted Extras
2. Google Chrome Debian install
3. GParted
4. VLC
5. Unetbootin

Software Center will hang if the first program installed is Ubuntu
Restricted Extras. This bug manifests in every install after 2014-03_11
that I tested including the 2014-03_25 iso.

Software Center will fail with a Package operation failed error when a
Google Chorme Debian install is attempted. After that an attempt to
install Ubuntu Restricted Extras or GParted would fail with the same
error. Note, if the first program installed was GParted rather than
Google Chrome or Unbuntu Restricted Extras, the GParted installation
would be successful.

Knowing the approximate date that the failure was introduced should
help. Also, I am somewhat concerned that usability regression testing
may not catch this because the problem manifests differently depending
upon which program is installed first.

Finally, if I install from 2014-03-11 and then update to
(3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:06 UTC 2014) the
failures described above will occur.

** Affects: software-center (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1298188

Title:
  Software Center KAPUT on or about 2014-03_12

Status in “software-center” package in Ubuntu:
  New

Bug description:
  Software Center correctly installed the following programs when
  executed following the 64-bit 2014-03_11.iso Desktop Installation
  (3.13.0-16-generic #36-Ubuntu SMP Tue Mar 4 23:02:40 UTC 2014):

  1. Ubuntu Restricted Extras
  2. Google Chrome Debian install
  3. GParted
  4. VLC
  5. Unetbootin

  Software Center will hang if the first program installed is Ubuntu
  Restricted Extras. This bug manifests in every install after
  2014-03_11 that I tested including the 2014-03_25 iso.

  Software Center will fail with a Package operation failed error when a
  Google Chorme Debian install is attempted. After that an attempt to
  install Ubuntu Restricted Extras or GParted would fail with the same
  error. Note, if the first program installed was GParted rather than
  Google Chrome or Unbuntu Restricted Extras, the GParted installation
  would be successful.

  Knowing the approximate date that the failure was introduced should
  help. Also, I am somewhat concerned that usability regression testing
  may not catch this because the problem manifests differently depending
  upon which program is installed first.

  Finally, if I install from 2014-03-11 and then update to
  (3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:06 UTC 2014) the
  failures described above will occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1298188] Re: Software Center KAPUT on or about 2014-03_12

** Attachment added: BUG_SoftwareCenter_UbuntuRestrictedInstall_After failed
Chrome_2014-03-25 21:56:32.png

https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+attachment/4045975/+files/BUG_SoftwareCenter_UbuntuRestrictedInstall_After%20failed%20Chrome_2014-03-25%2021%3A56%3A32.png

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1298188

Title:
Software Center KAPUT on or about 2014-03_12

Status in “software-center” package in Ubuntu:
New

1. Ubuntu Restricted Extras
2. Google Chrome Debian install
3. GParted
4. VLC
5. Unetbootin

Software Center will hang if the first program installed is Ubuntu
Restricted Extras. This bug manifests in every install after
2014-03_11 that I tested including the 2014-03_25 iso.

Finally, if I install from 2014-03-11 and then update to
(3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:06 UTC 2014) the
failures described above will occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298188/+subscriptions

[Desktop-packages] [Bug 1293770] [NEW] Ubuntu Restricted Extras Installation Hangs in Ubuntu14.04

2014-03-17 Thread Ernie 07

Public bug reported:

64-bit 14.04 iso (2014-03_17_07:46)

1. Launch Software Center.
2. Select Ubuntu Restricted Extras, begin install, supply credentials.

3. In the past, the installation would appear to hang while actually
waiting for user response to a Eula dialog that was not visible. If the
launcher was not extremely cluttered by the HUGE number of partitions
locked to it, a Question mark icon would appear in the launcher which
could be clicked to make the Eula dialog visible.

4. Now the installation hangs but the Question mark icon never appears.
5. After killing the software-center process and then launching the Software 
Center,  I was able to successfully install  Gparted which leads me to point 
the finger at Ubuntu Restricted Extras.

I believe that this bug got introduced/uncovered after 64-bit 14.04 iso
(2014-03_12) and may be related the bug where Google-chrome-stable
cannot be installed via the Software Center although the same version
can be installed via PPA.

** Affects: software-center (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1293770

Title:
  Ubuntu Restricted Extras Installation Hangs in Ubuntu14.04

Status in “software-center” package in Ubuntu:
  New

Bug description:
  64-bit 14.04 iso (2014-03_17_07:46)

  1. Launch Software Center.
  2. Select Ubuntu Restricted Extras, begin install, supply credentials.

  3. In the past, the installation would appear to hang while actually
  waiting for user response to a Eula dialog that was not visible. If
  the launcher was not extremely cluttered by the HUGE number of
  partitions locked to it, a Question mark icon would appear in the
  launcher which could be clicked to make the Eula dialog visible.

  4. Now the installation hangs but the Question mark icon never appears.
  5. After killing the software-center process and then launching the Software 
Center,  I was able to successfully install  Gparted which leads me to point 
the finger at Ubuntu Restricted Extras.

  I believe that this bug got introduced/uncovered after 64-bit 14.04
  iso (2014-03_12) and may be related the bug where Google-chrome-stable
  cannot be installed via the Software Center although the same version
  can be installed via PPA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1293770/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1255558] Re: Can't type my password after cold boot

2014-03-12 Thread Ernie 07

A non-technical person managed to cause a system to crash a few minutes
after she entered a certain sequence of keystrokes on a terminal that
was NOT logged on. The programmer failed to flush the buffer and
accepted contamination as well as logon commands. So I have attempted to
use her non-technical methods to work around this problem.

Click on the word Guest.
Click on your user name.
Right click and select select all
Put the mouse pointer over the text box then press backspace.

Now you should be able to enter your password.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/128

Title:
  Can't type my password after cold boot

Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  Can't type my password after cold boot unless I change my keyboard
  layout to next (or change and then re-change to same layout)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1
  Uname: Linux 3.12.0-4-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Wed Nov 27 16:27:13 2013
  InstallationDate: Installed on 2013-11-19 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131119)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/128/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1255558] Re: Can't type my password after cold boot

2014-03-11 Thread Ernie 07

I too cannot always enter my password.
64-bit Desktop 14.04 2014-03-10 07:49 iso
Fiddling with right-click, etc. enabled password input

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/128

Title:
  Can't type my password after cold boot

Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  Can't type my password after cold boot unless I change my keyboard
  layout to next (or change and then re-change to same layout)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1
  Uname: Linux 3.12.0-4-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Wed Nov 27 16:27:13 2013
  InstallationDate: Installed on 2013-11-19 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131119)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/128/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1200898] Re: nautilus crashed with SIGSEGV in g_slice_free1()

2013-09-27 Thread Ernie 07

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

??? Could not find related bug 1196063.  Was the bug number mistyped?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1200898

Title:
  nautilus crashed with SIGSEGV in g_slice_free1()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Nautilus crashed after clicking on the close button of the window.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 13 13:02:05 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b'839x550+759+321'
  InstallationDate: Installed on 2013-02-27 (136 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x7f081495107f:mov0x8(%rax),%rcx
   PC (0x7f081495107f) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rcx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_type_free_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_tree_view_remove_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV in g_slice_free1()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   evince 3.8.2-0ubuntu4
   file-roller3.8.3-0ubuntu1
   ubuntuone-client-gnome 4.2.0-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-09-04 Thread Ernie 07

Another data point.

In addition to failing via the right click extract here menu, the CLI
file-roller -h command produces the same failure.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in File Roller:
  Fix Released
Status in “file-roller” package in Ubuntu:
  Triaged

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-09-03 Thread Ernie 07

** Attachment added: file-roller 3.9.90.png
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+attachment/3801754/+files/file-roller%203.9.90.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in File Roller:
  Fix Released
Status in “file-roller” package in Ubuntu:
  Triaged

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-09-03 Thread Ernie 07

Please re-open this bug. I tested using a recent 13.10 and file-roller
3.9.90 and observed that extract here fails to delay directory restore
causing EVERY non-empty extracted folder to assume the date/time of
extraction.

I will attempt to attach a screenshot of the relevant portion of the
GNOME file-roller 3.8.4 change log and a screenshot of a terminal window
indicating stats on the OS in use, an ls -al of the iso used to install
the OS and the current file-roller version.

** Attachment added: file-roller 3.9.90.png
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+attachment/3801753/+files/file-roller%203.9.90.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in File Roller:
  Fix Released
Status in “file-roller” package in Ubuntu:
  Triaged

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-09-03 Thread Ernie 07

** Attachment added: file-roller 3.8.4 changes.png
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+attachment/3801755/+files/file-roller%203.8.4%20changes.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in File Roller:
  Fix Released
Status in “file-roller” package in Ubuntu:
  Triaged

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-08-06 Thread Ernie 07

This BUG still exists in file-roller 3.8.3 (13.10 dev)
The bug report submitted to GNOME several months ago indicates NO activity  
which would lead one to believe that it is being ignored. Might there be a 
Ubuntu-centric workaround?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in File Roller:
  New
Status in “file-roller” package in Ubuntu:
  Triaged

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1110025] Re: gksu nautllus Can't change preferences MISSING file menu

2013-07-11 Thread Ernie 07

Jeremy,

Thanks for the update.

I have been using gksu nautilus to change ownership of each newly
formatted ext4 partition and/or  root-owned files that I need to rename,
modify or delete from time to time. One such use is with fstab.  I
prefer to rename it and modify a copy.  When happy with the
modification, I delete the renamed version.  Doing so via the CLI can be
tedious and error-prone.  Is there another way to accomplish changes of
ownership and/or content of root-owned files via a GUI now that gksu
nautilus is no longer supported?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1110025

Title:
  gksu nautllus Can't change preferences MISSING file menu

Status in “nautilus” package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 64-bit 13.04 3.8.0-2 generic

  Alt-F2 to launch gksu nautilus with ROOT privilege.
  Unable to change preferences due to MISSING file menu.

  File menu does provide the preferences option when nautilus is
  launched with USER privilege.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-05-09 Thread Ernie 07

Except for dependency upon Nvidia drivers,  I would be quite satisfied with 
12,04.
I really would like to put Nvidia drivers in the trash where they belong. 

The list of 13.xx BUGs preventing the switch from 12.04 is getting shorter.
Please shorten the list by fixing this BUG promptly.  Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-05-05 Thread Ernie 07

This BUG manifests in 12.10, 13.04 and 13.10 but NOT in 12.04
Apparently this functionality is either considered perfect and/or not
important enough to warrant QA regression testing.

When a non-empty directory gets extracted, its datetime stamp is
immediately restored but recursive extraction of its content (files,
folders, etc) will update that directory's datetime stamp with the time
of extraction. In 12.04, the datetime stamp restoration was delayed
until after all content had been extracted.

Until it gets fixed upstream (2013 perhaps), the following CLI command
will allow proper extraction of a tar.bz2 archive:

tar --delay -xvf tar-archive-name

tar -xvf tar-archive-name  MAY yield unpredictable results

My eyes have trouble seeing the double hypen in --dash as I type this,
so I will refer to them as hyphen hyphen.

hypen hypen delay is an acceptable abbreviation of the option hypen
hyphen delay-directory-restore

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-04-30 Thread Ernie 07

Max,

I did a quick search for the NetworkManger source code. Many variations
and levels of development exist.

Since I have no experience as a developer or QA type in the Ubuntu arena
and have repeatedly submitted DETAILED steps for this 100% reproducible
problem, I will pass on trying to fix it myself.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-04-27 Thread Ernie 07

Sebastian,

Bug 697756 was filed a couple of weeks ago but has not been
acknowledged.

Perhaps 100% reproducible bugs offer little technical challenge and are
therefore ignored.

** Attachment added: Bug 697756 - file-roller 3.6.x delay-directory-restore 
failing during non-empty folder extraction.png
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+attachment/3657032/+files/Bug%20697756%20-%20file-roller%203.6.x%20delay-directory-restore%20failing%20during%20non-empty%20folder%20extraction.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-04-26 Thread Ernie 07

ABSOLUTELY!

64-bit Desktop  3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC
2013

IF
Internet connection to the modem exists and
Ethernet connection from my desktop to the modem and
Enable Networking checked and
Shutdown or Restart or Reboot
THEN
Bad shutdown
fsck from another copy of Ubuntu will indicate problems, see attachment
END

Dropping the Ethernet connection by unplugging the Ethernet cable or
unchecking Enable Networking before a shutdown or reboot will ALWAYS
keep the problem from occurring. This problem has existed since 12.10
and has been discussed but not fixed.

If it is helpful to know, while the Ethernet connection is up small
keepalive packets seem to be sent and received from time to time.

** Attachment added: Dirty fsck from BAD network enabled restart_2013-04-26 
18:45:45.png
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3655573/+files/Dirty%20fsck%20from%20BAD%20network%20enabled%20restart_2013-04-26%2018%3A45%3A45.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-04-26 Thread Ernie 07

Hi Max,

The last time I touched a compiler was in the windoze world about ten
years ago.

1. Will I have to download and install a compiler and a linker?
2. Will I have to recompile the kernel to use the updated NetworkManager?

Advise please.  Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-04-16 Thread Ernie 07

Russel,

When using the CLI, I got an error and could not install wicd on 13.04
However, I was able to install it via the software center.

Each time that I attempted to use it, a connection failure message
occurred immediately after the requested password was entered. Are you
able to install/execute wicd using 13.04?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-04-16 Thread Ernie 07

Another data set:

1. ATT is my ISP. My Desktop connects to a DSL modem via Ethernet.
2. There seems to be some keepalive traffic. A packet of 64 or 121 bytes gets
sent or received about every 10 seconds. This activity appears to happen in
12.04 which functions correctly and in 13.04 which fails 100% of the time.
3. Shutting down in this state (Enable Networking checked but NO explicit
Internet activity) will result in an error every time.
4. The connection will drop if I unplug the Ethernet cable. In that state I
can reboot with NO errors.

Since I can manually force the connection to drop by either unplugging
the Ethernet cable or unchecking Enable Networking, shouldn't the
network manager also drop the Ethernet connection when a
restart/reboot/shutdown is requested?

I pose the question because the failure will never occur if the network
connection has been dropped. Perhaps the keepalive traffic is not being
forcibly killed.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
Confirmed
Status in “linux” package in Ubuntu:
Incomplete
Status in “network-manager” package in Ubuntu:
Triaged
Status in “upstart” package in Ubuntu:
Confirmed

Bug description:
1. Format and label a target Ext4 partion using Ubuntu 12.04
2. Install 64bit 12.10 OS using that target without reformatting it
3. Shut down
4. Boot an alternate copy of Ubuntu
5. Restart selecting the newly installed OS
6. Login then shutdown
6. Boot an alternate copy of Ubuntu
7.Fsck the newly installed OS allowing corrections to be made

Each time the the newly installed OS is executed and then shutdown,
even if execution only consists of logging on, a subsequent fsck will
FAIL.

I used Acronis True Image Home 2013 to create an image of the newly
installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
filesystem corruption 100% of the time by restoring from the image,
booting, logging on and shutting down.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: aguru 1871 F pulseaudio
/dev/snd/controlC0: aguru 1871 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Tue Oct 30 22:24:54 2012
HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
IwConfig:
eth0 no wireless extensions.

lono wireless extensions.
MachineType: System manufacturer P5Q-E
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-17-generic N/A
linux-backports-modules-3.5.0-17-generic N/A
linux-firmware1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

[Desktop-packages] [Bug 1124803] Re: NetworkManager doesn't respond to SIGTERM in daemon mode

2013-04-14 Thread Ernie 07

Unfortunately wicd would not install on amd64.deb for me.  Failure
indicated partway through the installation.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803

Title:
  NetworkManager doesn't respond to SIGTERM in daemon mode

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Gentoo Linux:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-04-14 Thread Ernie 07

In another perhaps related bug 1124803, it was suggested to try wicd.
Unfortunately wicd would not install on 13.04 amd64.deb for me.  Failure 
indicated partway through the installation.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1124803] Re: NetworkManager doesn't respond to SIGTERM in daemon mode

2013-04-14 Thread Ernie 07

Forget to mention that the wicd failure occurred on 13.04 amd64.deb.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803

Title:
  NetworkManager doesn't respond to SIGTERM in daemon mode

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Gentoo Linux:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1124803] Re: NetworkManager doesn't respond to SIGTERM in daemon mode

2013-04-12 Thread Ernie 07

Max,

I have given up on 12.10 but would like to make use of 13.04.

The  Raring daily amd64.iso contains network-manager version 9.8.0 and it 
exhibits the same failure pattern as 9.6.0 in 12.04.
The failure is 100% reproducible and will manifest each time the OS is shut 
down UNLESS enable networking has been unchecked first.

Can you get your fix into the raring daily build?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803

Title:
  NetworkManager doesn't respond to SIGTERM in daemon mode

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Gentoo Linux:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1124803] Re: NetworkManager doesn't respond to SIGTERM in daemon mode

2013-04-11 Thread Ernie 07

I strongly believe this problem is associated with termination rather
than startup.

I can establish conditions for failure by checking  enable networking or
prevent failure by unchecking enable networking prior to reboot, restart
or shutdown.

Using a separate OS (12.04), fsck can be used to demonstrate the failure
of the 13.04 under test 100% of the time.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803

Title:
  NetworkManager doesn't respond to SIGTERM in daemon mode

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Gentoo Linux:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1166971] Re: file-roller 3.6.x delay-directory-restore failing during non-empty folder extraction

2013-04-10 Thread Ernie 07

Link to upstream bug report follows:

https://bugzilla.gnome.org/show_bug.cgi?id=697756

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1166971

Title:
  file-roller 3.6.x delay-directory-restore failing during non-empty
  folder extraction

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  file-roller 3.6.x delay-directory-restore failing during non-empty
  folder extraction

  64-bit File-Roller 3.6.0 via 1210 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 
19:31:23 UTC 2012 fails
  64-bit File-Roller 3.6.3 via 1304 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 
19:52:57 UTC 2013 fails

  64-bit File-Roller 3.4.1 via 1204 3.5.0-26-generic #42~precise1-Ubuntu
  SMP Mon Mar 11 22:17:58 UTC 2013 functions correctly

  1. Extract a tar.bz2 archive containing non-empty folders.
  2. Date-time stamps will be restored BEFORE folder content.
  3. Date-time stamp restoration should be delayed until after folder content 
is restored.

  This failure causes the date-time stamp of each non-empty folder to be
  overwritten with the date and time that folder content was restored.
  This failure can be reproduced 100% of the time using either the
  right-click menu extract option or the file-roller from the cli.

  Apparently file-roller is NOT included in regression testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1166971/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1166971] [NEW] file-roller 3.6.x delay-directory-restore failing during non-empty folder extraction

2013-04-09 Thread Ernie 07

Public bug reported:

file-roller 3.6.x delay-directory-restore failing during non-empty
folder extraction

64-bit File-Roller 3.6.0 via 1210 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 
19:31:23 UTC 2012 fails
64-bit File-Roller 3.6.3 via 1304 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 
19:52:57 UTC 2013 fails

64-bit File-Roller 3.4.1 via 1204 3.5.0-26-generic #42~precise1-Ubuntu
SMP Mon Mar 11 22:17:58 UTC 2013 functions correctly

1. Extract a tar.bz2 archive containing non-empty folders.
2. Date-time stamps will be restored BEFORE folder content.
3. Date-time stamp restoration should be delayed until after folder content is 
restored.

This failure causes the date-time stamp of each non-empty folder to be
overwritten with the date and time that folder content was restored.
This failure can be reproduced 100% of the time using either the right-
click menu extract option or the file-roller from the cli.

Apparently file-roller is NOT included in regression testing.

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1166971

Title:
  file-roller 3.6.x delay-directory-restore failing during non-empty
  folder extraction

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  file-roller 3.6.x delay-directory-restore failing during non-empty
  folder extraction

  64-bit File-Roller 3.6.0 via 1210 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 
19:31:23 UTC 2012 fails
  64-bit File-Roller 3.6.3 via 1304 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 
19:52:57 UTC 2013 fails

  64-bit File-Roller 3.4.1 via 1204 3.5.0-26-generic #42~precise1-Ubuntu
  SMP Mon Mar 11 22:17:58 UTC 2013 functions correctly

  1. Extract a tar.bz2 archive containing non-empty folders.
  2. Date-time stamps will be restored BEFORE folder content.
  3. Date-time stamp restoration should be delayed until after folder content 
is restored.

  This failure causes the date-time stamp of each non-empty folder to be
  overwritten with the date and time that folder content was restored.
  This failure can be reproduced 100% of the time using either the
  right-click menu extract option or the file-roller from the cli.

  Apparently file-roller is NOT included in regression testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1166971/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1166996] [NEW] Unity locks EVERY partition to the launcher at startup - UGLY useless CLUTTER

2013-04-09 Thread Ernie 07

Public bug reported:

Unity locks EVERY partition to the launcher at startup - UGLY useless
CLUTTER

64-bit unity via 1210 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 
2012 fails
64-bit unity via 1304 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 
2013 fails

64-bit unity via 1204 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar
11 22:17:58 UTC 2013 functions correctly

This change may have occurred to assist a user who is too naive or lazy to 
mount a partition.
Please provide an option to disable this UGLY useless CLUTTER

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1166996

Title:
  Unity locks EVERY partition to the launcher at startup - UGLY useless
  CLUTTER

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Unity locks EVERY partition to the launcher at startup - UGLY useless
  CLUTTER

  64-bit unity via 1210 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 
2012 fails
  64-bit unity via 1304 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 
2013 fails

  64-bit unity via 1204 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar
  11 22:17:58 UTC 2013 functions correctly

  This change may have occurred to assist a user who is too naive or lazy to 
mount a partition.
  Please provide an option to disable this UGLY useless CLUTTER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1166996/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1167002] [NEW] Gparted locks EVERY partition to the launcher when launched - UGLY useless CLUTTER

2013-04-09 Thread Ernie 07

Public bug reported:

Gparted locks EVERY partition to the launcher when launched - UGLY
useless CLUTTER

64-bit gparted via 1210 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 
2012 fails
64-bit gparted via 1304 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 
2013 fails

64-bit gparted via 1204 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar
11 22:17:58 UTC 2013 functions correctly

This change may have occurred to assist a user who is too naive or lazy to 
mount a partition.
Please provide an option to disable this UGLY useless CLUTTER

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1167002

Title:
  Gparted locks EVERY partition to the launcher when launched - UGLY
  useless CLUTTER

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Gparted locks EVERY partition to the launcher when launched - UGLY
  useless CLUTTER

  64-bit gparted via 1210 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 
UTC 2012 fails
  64-bit gparted via 1304 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 
UTC 2013 fails

  64-bit gparted via 1204 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon
  Mar 11 22:17:58 UTC 2013 functions correctly

  This change may have occurred to assist a user who is too naive or lazy to 
mount a partition.
  Please provide an option to disable this UGLY useless CLUTTER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1167002/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1124803] Re: NetworkManager doesn't respond to SIGTERM in daemon mode

2013-04-03 Thread Ernie 07

Hi Max,

Using 64-bit  3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC
2013 from the 2013-04_02 daily build:

1. NetworkManager stopped correctly (immediately) via sudo stop network-manager.
2. A reboot to an alternate system and fsck of the system under test presented 
errors.

Regardless of whether I stopped or restarted NetworkManager, as long as
I manually unchecked Enable Networking, a clean shutdown would occur and
a subsequent fsck would show no errors.

A process (maybe more than one) is being gracefully shut down when I
manually uncheck Enable Networking but is not getting properly shutdown
via sudo stop network-manager.  Hope this data point is helpful.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803

Title:
  NetworkManager doesn't respond to SIGTERM in daemon mode

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Gentoo Linux:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-04-03 Thread Ernie 07

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

Using 64-bit 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 2013
from the 2013-04_02 daily build:

1. NetworkManager stopped correctly (immediately) via sudo stop network-manager.
2. A reboot to an alternate system and fsck of the system under test presented 
errors.

Regardless of whether I stopped or restarted NetworkManager, as long as
I manually unchecked Enable Networking, a clean shutdown would occur and
a subsequent fsck would show no errors.

A process (maybe more than one) is being gracefully shut down when I
manually uncheck Enable Networking but is not getting properly shutdown
via sudo stop network-manager. Hope this data point is helpful.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1163146] [NEW] unable to locate libudev0

Public bug reported:

64-bit  D07-1304 3.8.0-15-generic #25-Ubuntu SMP Wed Mar 27 19:19:30 UTC
2013

1. Attempted to install Chrome Stable but got a dependency error message 
concerning libudev0
2. Attempted to install libudev0 via apt-get isntall libudev0 and got a message 
indicating that it could not be located.

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1163146

Title:
  unable to locate libudev0

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  64-bit  D07-1304 3.8.0-15-generic #25-Ubuntu SMP Wed Mar 27 19:19:30
  UTC 2013

  1. Attempted to install Chrome Stable but got a dependency error message 
concerning libudev0
  2. Attempted to install libudev0 via apt-get isntall libudev0 and got a 
message indicating that it could not be located.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1163146/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1163151] [NEW] 13.04 Update HANGs

Public bug reported:

 D07-1304 3.8.0-15-generic #25-Ubuntu SMP Wed Mar 27 19:19:30 UTC 2013

1. Atempt to install upgrades.
2. Hang trying to install 3.8.0-16 following an install of the 2013-04_01 daily 
build.

Had the same symptoms trying to upgrade from 3.8.0-14 to 3.8.0-15
IN both cases, the error gathering process reports this as known bug but points 
to a bug that does not seem at all related.
This last process happens IF Chrome has been installed and is the default 
browser.
If FireFox is the default it just hangs.  FireFox on Ubuntu functions so poorly 
that it must have come from Redmond!

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1163151

Title:
  13.04 Update HANGs

Status in “file-roller” package in Ubuntu:
  New

Bug description:
   D07-1304 3.8.0-15-generic #25-Ubuntu SMP Wed Mar 27 19:19:30 UTC 2013

  1. Atempt to install upgrades.
  2. Hang trying to install 3.8.0-16 following an install of the 2013-04_01 
daily build.

  Had the same symptoms trying to upgrade from 3.8.0-14 to 3.8.0-15
  IN both cases, the error gathering process reports this as known bug but 
points to a bug that does not seem at all related.
  This last process happens IF Chrome has been installed and is the default 
browser.
  If FireFox is the default it just hangs.  FireFox on Ubuntu functions so 
poorly that it must have come from Redmond!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1163151/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1124803] Re: NetworkManager doesn't respond to SIGTERM in daemon mode

64-bit   D07-1304 3.8.0-15-generic #25-Ubuntu SMP Wed Mar 27 19:19:30
UTC 2013 downloaded via the 2013-04_01 build FAILS!

1. Boot system
2. Enable networking
3. Shutdown system
4. Boot an alternate system fsck check throws errors EVERY time.

Disabling networking prior to shutdown results in a proper shutdown with
NO fsck errors reported via an alternate system.

These symptoms which have existed since the release of 12.10 are
obvious, 100% repeatable and can give Ubuntu developers the reputation
that they were trained in Redmond by the Vista team.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803

Title:
  NetworkManager doesn't respond to SIGTERM in daemon mode

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Gentoo Linux:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1124803] Re: NetworkManager doesn't respond to SIGTERM in daemon mode

NetworkManger version = 0.9.8.0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803

Title:
  NetworkManager doesn't respond to SIGTERM in daemon mode

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Gentoo Linux:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-03-18 Thread Ernie 07

Do not be deceived.  This is a 1210 and 13.04 problem.

64-bit 1204 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013
and prior 12.04 64-bit versions work just fine!

It would be quite delightful if someone would correct this problem of
failing to shutdown properly.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-03-18 Thread Ernie 07

I repeat. This is a 12.10 and 13.04 problem.

64-bit 1204 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar 11 22:17:58 UTC 
2013 and prior 12.04
64-bit versions work just fine!

A fix for this problem of failing to shutdown properly would be much
appreciated.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1152338] Re: evince crashed with SIGSEGV Following Ctrl-F

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

b

On Thu, Mar 7, 2013 at 11:10 PM, Apport retracing service 
1152...@bugs.launchpad.net wrote:

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

 Thank you for taking the time to report this crash and helping to make
 this software better.  This particular crash has already been reported
 and is a duplicate of bug #1044002, so is being marked as such.  Please
 look at the other bug report to see if there is any missing information
 that you can provide, or to see if there is a workaround for the bug.
 Additionally, any further discussion regarding the bug should occur in
 the other report.  Please continue to report any other bugs you may
 find.

 ** Attachment removed: CoreDump.gz

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562813/+files/CoreDump.gz

 ** Attachment removed: Disassembly.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562815/+files/Disassembly.txt

 ** Attachment removed: ProcMaps.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562817/+files/ProcMaps.txt

 ** Attachment removed: ProcStatus.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562818/+files/ProcStatus.txt

 ** Attachment removed: Registers.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562819/+files/Registers.txt

 ** Attachment removed: Stacktrace.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562821/+files/Stacktrace.txt

 ** Attachment removed: ThreadStacktrace.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562822/+files/ThreadStacktrace.txt

 ** This bug has been marked a duplicate of private bug 1044002

 ** Tags removed: need-amd64-retrace

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1152338

 Title:
   evince crashed with SIGSEGV Following Ctrl-F

 Status in “evince” package in Ubuntu:
   New

 Bug description:
   64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
   2013

   Open a PDF.
   Prepare to search for text by pressing Control F
   CRASH!

   ProblemType: Crash
   DistroRelease: Ubuntu 13.04
   Package: evince 3.6.1-1ubuntu3
   ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
   Uname: Linux 3.8.0-11-generic x86_64
   ApportVersion: 2.9.1-0ubuntu1
   Architecture: amd64
   CrashCounter: 1
   Date: Thu Mar  7 13:31:53 2013
   ExecutablePath: /usr/bin/evince
   InstallationDate: Installed on 2013-02-26 (9 days ago)
   InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64
 (20130225)
   MarkForUpload: True
   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic
 root=UUID=ee725bf1-d26e-498a-8cdb-1c14e1ec571f ro quiet splash vt.handoff=7
   ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
   SegvAnalysis:
Segfault happened at: 0x7fa4c6d873e8:cmpq   $0x0,0x30(%r12)
PC (0x7fa4c6d873e8) ok
source $0x0 ok
destination 0x30(%r12) (0x0030) not located in a known VMA region
 (needed writable region)!
Stack memory exhausted (SP below stack segment)
   SegvReason: writing NULL VMA
   Signal: 11
   SourcePackage: evince
   StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   Title: evince crashed with SIGSEGV
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1152338/+subscriptions


-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1152338

Title:
  evince crashed with SIGSEGV Following Ctrl-F

Status in “evince” package in Ubuntu:
  New

Bug description:
  64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
  2013

  Open a PDF.
  Prepare to search for text by pressing Control F
  CRASH!

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Mar  7 13:31:53 2013
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2013-02-26 (9 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225)
  MarkForUpload: True
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ee725bf1-d26e-498a-8cdb-1c14e1ec571f ro quiet splash vt.handoff=7
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8

Re: [Desktop-packages] [Bug 1152338] Re: evince crashed with SIGSEGV Following Ctrl-F

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

On Fri, Mar 8, 2013 at 1:19 AM, Ernest Boyd ernestb...@gmail.com wrote

Bug 1044002 appears to be a private bug and is therefore NOT accessible.



 On Thu, Mar 7, 2013 at 11:10 PM, Apport retracing service 
 1152...@bugs.launchpad.net wrote:

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

 Thank you for taking the time to report this crash and helping to make
 this software better.  This particular crash has already been reported
 and is a duplicate of bug #1044002, so is being marked as such.  Please
 look at the other bug report to see if there is any missing information
 that you can provide, or to see if there is a workaround for the bug.
 Additionally, any further discussion regarding the bug should occur in
 the other report.  Please continue to report any other bugs you may
 find.

 ** Attachment removed: CoreDump.gz

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562813/+files/CoreDump.gz

 ** Attachment removed: Disassembly.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562815/+files/Disassembly.txt

 ** Attachment removed: ProcMaps.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562817/+files/ProcMaps.txt

 ** Attachment removed: ProcStatus.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562818/+files/ProcStatus.txt

 ** Attachment removed: Registers.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562819/+files/Registers.txt

 ** Attachment removed: Stacktrace.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562821/+files/Stacktrace.txt

 ** Attachment removed: ThreadStacktrace.txt

 https://bugs.launchpad.net/bugs/1152338/+attachment/3562822/+files/ThreadStacktrace.txt

 ** This bug has been marked a duplicate of private bug 1044002

 ** Tags removed: need-amd64-retrace

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1152338

 Title:
   evince crashed with SIGSEGV Following Ctrl-F

 Status in “evince” package in Ubuntu:
   New

 Bug description:
   64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
   2013

   Open a PDF.
   Prepare to search for text by pressing Control F
   CRASH!

   ProblemType: Crash
   DistroRelease: Ubuntu 13.04
   Package: evince 3.6.1-1ubuntu3
   ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
   Uname: Linux 3.8.0-11-generic x86_64
   ApportVersion: 2.9.1-0ubuntu1
   Architecture: amd64
   CrashCounter: 1
   Date: Thu Mar  7 13:31:53 2013
   ExecutablePath: /usr/bin/evince
   InstallationDate: Installed on 2013-02-26 (9 days ago)
   InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64
 (20130225)
   MarkForUpload: True
   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic
 root=UUID=ee725bf1-d26e-498a-8cdb-1c14e1ec571f ro quiet splash vt.handoff=7
   ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
   SegvAnalysis:
Segfault happened at: 0x7fa4c6d873e8:cmpq   $0x0,0x30(%r12)
PC (0x7fa4c6d873e8) ok
source $0x0 ok
destination 0x30(%r12) (0x0030) not located in a known VMA
 region (needed writable region)!
Stack memory exhausted (SP below stack segment)
   SegvReason: writing NULL VMA
   Signal: 11
   SourcePackage: evince
   StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   Title: evince crashed with SIGSEGV
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1152338/+subscriptions




-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1152338

Title:
  evince crashed with SIGSEGV Following Ctrl-F

Status in “evince” package in Ubuntu:
  New

Bug description:
  64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
  2013

  Open a PDF.
  Prepare to search for text by pressing Control F
  CRASH!

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Mar  7 13:31:53 2013
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2013-02-26 (9 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225)
  MarkForUpload: True
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic

[Desktop-packages] [Bug 1062733] Re: evince crashed with SIGSEGV

** This bug is no longer a duplicate of private bug 1044002

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1062733

Title:
  evince crashed with SIGSEGV

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  trying to go to next page in pdf causes evince to crash,

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: evince 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  6 10:54:50 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110831)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=40936c16-94d7-4e91-bd15-09848311802b ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7facf2355fc8:cmpq   $0x0,0x30(%r12)
   PC (0x7facf2355fc8) ok
   source $0x0 ok
   destination 0x30(%r12) (0x0030) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: evince crashed with SIGSEGV
  UpgradeStatus: Upgraded to quantal on 2012-09-17 (18 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1044002] Re: evince crashed with SIGSEGV

64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
2013

Open a PDF.
Prepare to search for text by pressing Control F
CRASH!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1044002

Title:
  evince crashed with SIGSEGV

Status in “cairo” package in Ubuntu:
  Fix Released

Bug description:
  Opening this document,

  http://www.eurail.com/sites/all/files/eurail.com/downloads/2012
  /eurail-railwaymap-2012.pdf

  causes the crash when scrolling to the second page of the document:

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: evince 3.5.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Aug 30 14:42:56 2012
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  KernLog:
   
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic 
root=UUID=12c3b175-1d70-4a6d-a247-03a07e1e28d4 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fc9664d8f58:cmpq   $0x0,0x30(%r12)
   PC (0x7fc9664d8f58) ok
   source $0x0 ok
   destination 0x30(%r12) (0x0030) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: evince crashed with SIGSEGV
  UpgradeStatus: Upgraded to quantal on 2012-08-17 (12 days ago)
  UserGroups: sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1152338] [NEW] evince crashed with SIGSEGV Following Ctrl-F

2013-03-07 Thread Ernie 07

Public bug reported:

64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
2013

Open a PDF.
Prepare to search for text by pressing Control F
CRASH!

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: evince 3.6.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
Uname: Linux 3.8.0-11-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Mar  7 13:31:53 2013
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2013-02-26 (9 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ee725bf1-d26e-498a-8cdb-1c14e1ec571f ro quiet splash vt.handoff=7
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa4c6d873e8:  cmpq   $0x0,0x30(%r12)
 PC (0x7fa4c6d873e8) ok
 source $0x0 ok
 destination 0x30(%r12) (0x0030) not located in a known VMA region 
(needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
Title: evince crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apparmor apport-crash need-amd64-retrace raring

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1152338

Title:
  evince crashed with SIGSEGV Following Ctrl-F

Status in “evince” package in Ubuntu:
  New

Bug description:
  64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
  2013

  Open a PDF.
  Prepare to search for text by pressing Control F
  CRASH!

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Mar  7 13:31:53 2013
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2013-02-26 (9 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225)
  MarkForUpload: True
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ee725bf1-d26e-498a-8cdb-1c14e1ec571f ro quiet splash vt.handoff=7
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa4c6d873e8:cmpq   $0x0,0x30(%r12)
   PC (0x7fa4c6d873e8) ok
   source $0x0 ok
   destination 0x30(%r12) (0x0030) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: evince crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1152338] Re: evince crashed with SIGSEGV Following Ctrl-F

2013-03-07 Thread Ernie 07

Apparently, the PDF that I used causes the failure in 13.04 but not 12.04
I will attach the PDF associated with the failure.

** Attachment added: PDF Associated with Evince crash
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1152338/+attachment/3563096/+files/Alcatel%20OT%20838%20User%20Manual.pdf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1152338

Title:
  evince crashed with SIGSEGV Following Ctrl-F

Status in “evince” package in Ubuntu:
  New

Bug description:
  64-bit D07-1304 3.8.0-11-generic #20-Ubuntu SMP Tue Mar 5 20:32:48 UTC
  2013

  Open a PDF.
  Prepare to search for text by pressing Control F
  CRASH!

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Mar  7 13:31:53 2013
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2013-02-26 (9 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225)
  MarkForUpload: True
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ee725bf1-d26e-498a-8cdb-1c14e1ec571f ro quiet splash vt.handoff=7
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa4c6d873e8:cmpq   $0x0,0x30(%r12)
   PC (0x7fa4c6d873e8) ok
   source $0x0 ok
   destination 0x30(%r12) (0x0030) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: evince crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1125759] Re: Intel integrated graphics boots in low graphics mode

2013-03-03 Thread Ernie 07

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

64-bit 3.8.0-9-generic #18-Ubuntu SMP Thu Feb 28 17:02:06 UTC 2013
Desktop with Intel e8500 cpu, Nvidia GT9500 and default (non-Nvidia) video 
driver.

I get this problem frequently following a restart from 12.04.

Pressing the reset button or executing a FULL power shutdown  prior to
completion of booting 13.04 will usually eliminate this problem. This
would imply that a hardware state that is properly initialized following
a reset or full power shutdown is NOT being properly initialized during
a warm reboot.

On occasion, I have also had to update/install grub, either from 12.04
or a via fix a broken system from a server CD.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1125759

Title:
  Intel integrated graphics boots in low graphics mode

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Incomplete

Bug description:
  After successfully installing 13.04 on my Dell XPS 15z, I restarted
  the laptop, successfully booting into Ubuntu with no issues.

  Restarting after that then gives the 'System is running in low
  graphics mode' message.

  I can only boot in recovery mode

  UPDATE: In the ubuntu forums thread
  (http://ubuntuforums.org/showthread.php?t=2115355), jbicha,
  recommended the following which fixed (or worked around) the problem

  Perhaps this is a problem with SNA which has been enabled by default
  for raring.

  Add (or edit if it already exists) /etc/X11/xorg.conf and I think this
  is the code you need:

  Code:

  Section Device
 Identifier Intel Graphics
 Driver intel
 Option AccelMethod uxa
  EndSection

  
  Extra info:

  This is an repost of bug 1124661 as I submitted that in recovery mode

  Other dell users seem to be experiencing similar issues:
  http://ubuntuforums.org/showthread.php?t=2115355

  I installed and use the parameters mentioned here:
  https://wiki.ubuntu.com/HardwareSupport/Machines/Laptops/Dell/XPS/15z

  I have an optimus card, which the Nvidia card should be disabled as it
  does not work

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb 15 01:50:36 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0446]
   NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:0446]
  InstallationDate: Installed on 2013-02-11 (3 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: Dell Inc. Dell System XPS 15Z
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic 
root=UUID=93acc5a7-d531-4af3-a215-472a7bd065d6 ro acpi_backlight=vendor 
dell_laptop.backlight=0 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
  Identifier  Intel Graphics
  Driver  intel
  Option  AccelMethod  uxa
   EndSection
  dmi.bios.date: 07/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 060G42
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd07/27/2011:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS 15Z
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel:

[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver

2013-03-03 Thread Ernie 07

64-bit 3.8.0-9-generic #18-Ubuntu SMP Thu Feb 28 17:02:06 UTC 2013
Desktop with Intel e8500 cpu, Nvidia GT9500 and default (non-Nvidia) video 
driver.

I get this problem frequently following a restart from 12.04.

Pressing the reset button or executing a FULL power shutdown prior to
completion of booting 13.04 will usually eliminate this problem. This
would imply that a hardware state that is properly initialized following
a reset or full power shutdown is NOT being properly initialized during
a warm reboot.

On occasion, I have also had to update/install grub, either from 12.04
or a via fix a broken system from a server CD.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/982889

Title:
  X trying to start before plymouth has finished using the drm driver

Status in “libdrm” package in Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  In Progress

Bug description:
  X server fails to start the first time after boot, it works fine when
  I start it again.

  Looks like a race condition with intel drm initialization, i guess X
  tries to start faster than drm driver is initialized so it fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Apr 16 10:35:28 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7750]
   Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] 
[1002:6738] (prog-if 00 [VGA controller])
 Subsystem: Giga-byte Technology Device [1458:21fa]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: MSI MS-7750
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic 
root=/dev/mapper/ssd-ubuntu--precise ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68A-G43 (G3) (MS-7750)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7750
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.7.6-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1071101] Re: nearly every other boot I get Low Graphics Mode message.

2013-03-03 Thread Ernie 07

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

64-bit 3.8.0-9-generic #18-Ubuntu SMP Thu Feb 28 17:02:06 UTC 2013
Desktop with Intel e8500 cpu, Nvidia GT9500 and default (non-Nvidia) video 
driver.

I get this problem frequently following a restart from 12.04.

Pressing the reset button or executing a FULL power shutdown prior to
completion of booting 13.04 will usually eliminate this problem. This
would imply that a hardware state that is properly initialized following
a reset or full power shutdown is NOT being properly initialized during
a warm reboot.

On occasion, I have also had to update/install grub, either from 12.04
or a via fix a broken system from a server CD.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1071101

Title:
  nearly every other boot I get Low Graphics Mode message.

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I'm not entirely sure that this is xorg, I can't figure out which log file to 
look in to find out. The log files with likely names did not give me usefull 
info.
  I've seen similar errors, but never the same hardware or circumstanses.

  Behavior started immediatly after upgrade to 12.10

  I'm running GNOME classic (though I think this bug is occuring before
  this becomes relevent), using an ATI HD4850 video card with open
  source drivers.

  About every other boot, I get a white message box telling me that something 
went wrong and the system will boot in low graphics mode. I'll try and write 
down the exact message next time this happens.
  The first time this happend (the next day after upgrading to 12.10, I was 
able to select the use defaults option to continue. every time after this, 
the use defaults or use latest backup goes right back to the same question. 
The only way forward is to boot into low graphics mode.

  I usually shut down the computer at the login screen when it is in low
  graphics mode (from the menu, not the switch), and turn the computer
  back on. This has booted cleanly with the correct graphics mode every
  time I have done it (about 4 times). The one time I tried sudo
  shutdown -r now, it rebooted and had the same problem again

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,snap,expo,move,resize,scale,regex]
  CompositorRunning: None
  Date: Wed Oct 24 19:12:16 2012
  DistUpgraded: 2012-10-21 15:14:45,536 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] 
(prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2266]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=c2921384-38b9-419e-b7ef-007bcc801561 ro nosplash debug --verbose
  SourcePackage: xorg
  UpgradeStatus: Upgraded to quantal on 2012-10-21 (3 days ago)
  dmi.bios.date: 09/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2209
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2209:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.8.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1133663] Re: Extract Here fails to preserve timestamps for non-empty folders

2013-02-28 Thread Ernie 07

Great Idea Sebastian

This bug is 100% reproducible.
However, my attempt at filing a report via Bugzilla was more difficult than 
being confronted by the US tax code for the first time.
Perhaps someone with knowledge if the secret ritual would be so kind as to 
report this.

Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1076716] Re: Extract Here fails to preserve timestamps (non-empty folders)

2013-02-26 Thread Ernie 07

This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP Tue
Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP Thu
Feb 21 20:07:18 UTC 2013

Since I make use of this functionally frequently each day, I have
avoided 12.10 except to determine if certain bugs have been fixed.

I would appreciate it if this ROADBLOCK to using 13.04 is removed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1076716

Title:
  Extract Here fails to preserve timestamps (non-empty folders)

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Use Right-Click Extract Here command to untar a tar.bz2 archive.
  Non-empty folders will lose original timestamps and show date/time of 
extraction.
  Empty folders and files are processed correctly and retain original 
timestamps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1076716/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1133663] [NEW] Extract Here fails to preserve timestamps for non-empty folders

2013-02-26 Thread Ernie 07

Public bug reported:

Extract Here fails to preserve timestamps for non-empty folders.

This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP Tue
Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP Thu
Feb 21 20:07:18 UTC 2013

Since I make use of this functionally frequently each day, I have
avoided 12.10 except to determine if certain bugs have been fixed.

I would appreciate having this ROADBLOCK to using 13.04 removed.

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1133663

Title:
  Extract Here fails to preserve timestamps  for non-empty folders

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Extract Here fails to preserve timestamps for non-empty folders.

  This functionally WORKED in 12.04, got DESTROYED in 12.10 and has not
  been fixed in either 64-bit 3.5.0-25-generic #39~precise1-Ubuntu SMP
  Tue Feb 26 00:07:14 UTC 2013 or 64-bit 3.8.0-7-generic #15-Ubuntu SMP
  Thu Feb 21 20:07:18 UTC 2013

  Since I make use of this functionally frequently each day, I have
  avoided 12.10 except to determine if certain bugs have been fixed.

  I would appreciate having this ROADBLOCK to using 13.04 removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1133663/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1110025] Re: gksu nautllus Can't change preferences MISSING file menu

2013-02-16 Thread Ernie 07

This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-6-generic.
Tested Friday 2013-02_16

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1110025

Title:
  gksu nautllus Can't change preferences MISSING file menu

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Ubuntu 64-bit 13.04 3.8.0-2 generic

  Alt-F2 to launch gksu nautilus with ROOT privilege.
  Unable to change preferences due to MISSING file menu.

  File menu does provide the preferences option when nautilus is
  launched with USER privilege.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1076716] Re: Extract Here fails to preserve timestamps (non-empty folders)

2013-02-16 Thread Ernie 07

This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-6-generic.
Tested Friday 2013-02_16

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1076716

Title:
  Extract Here fails to preserve timestamps (non-empty folders)

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Use Right-Click Extract Here command to untar a tar.bz2 archive.
  Non-empty folders will lose original timestamps and show date/time of 
extraction.
  Empty folders and files are processed correctly and retain original 
timestamps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1076716/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-02-16 Thread Ernie 07

This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-6-generic.
Tested Friday 2013-02_16

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1110025] Re: gksu nautllus Can't change preferences MISSING file menu

This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-3-generic.
Tested Friday 2013-02_01

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1110025

Title:
  gksu nautllus Can't change preferences MISSING file menu

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Ubuntu 64-bit 13.04 3.8.0-2 generic

  Alt-F2 to launch gksu nautilus with ROOT privilege.
  Unable to change preferences due to MISSING file menu.

  File menu does provide the preferences option when nautilus is
  launched with USER privilege.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1076716] Re: Extract Here fails to preserve timestamps (non-empty folders)

This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-3-generic.
Tested Friday 2013-02_01

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1076716

Title:
  Extract Here fails to preserve timestamps (non-empty folders)

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  Use Right-Click Extract Here command to untar a tar.bz2 archive.
  Non-empty folders will lose original timestamps and show date/time of 
extraction.
  Empty folders and files are processed correctly and retain original 
timestamps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1076716/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-3-generic.
Tested Friday 2013-02_01

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1076716] Re: Extract Here fails to preserve timestamps (non-empty folders)