[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off

2024-01-31 Thread Force
The MUTTER_DEBUG_ENABLE_ATOMIC_KMS worked for me as well, thank you!

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

Title:
  Display powersave only blanks, but does not turn off

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to Ubuntu 22.04, and it seems like the power-saving
  feature in Gnome 42 does not actually turn off the screen(s) after X
  minutes, but just blanks them. When I manually run `xset dpms force
  off`, they do properly turn off and go to powersave mode.

  1) Description:   Ubuntu 22.04 LTS
 Release:   22.04

  2) gnome-settings-daemon:
Installed: 42.1-1ubuntu2
Candidate: 42.1-1ubuntu2

  3) In Settings -> Power -> Screen Blank, set the inactivity period to
  5 minutes. After 5 minutes, the screens should turn off.

  4) Screens go black, but remain active and consume (too much) power.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-07-04 (667 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Package: gnome-settings-daemon 42.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 1164016] Re: restore type-ahead find

2013-06-11 Thread Justin Force
The new behavior is INFURIATING. And the search functionality is
terrible. Even if it were fast (and it's terribly slow on my Core i7 and
Intel SSD), it's stupid. I'm a software developer. When I type 'lib', I
want to jump to the lib directory that I'm looking at--not find every
directory and file with lib in it recursively. That's insane! And
there's a well-established UX for this already: indicate that you want
to perform a search by pressing Ctrl-F, F3, or whatever.

This change has made it virtually impossible to navigate Nautilus
without a mouse, and so Nautilus is now completely useless to me. HUGE
step backward.

I realize that GNOME is doing weird things with Nautilus 3.6, and that
the version shipping with Ubuntu is a best effort by Canonical, the
Ubuntu community, and friends to maintain sanity. I don't mean to
criticize the folks who are doing the best they can. I just want
adequately register my frustration here. My Ubuntu desktop experience is
seriously hampered as Nautilus is completely useless to me now. It's
much more efficient to do all file operations in a shell if I can't
type-ahead find.

And I don't think this is an issue of, "Well, I guess it's time to learn
new UI." I'm not averse to drastic changes to the UI if they're
improvements. This isn't a matter of Old Dog v. New Trick. This is a
very, very bad UI decision. It makes the software less useful.

Quick side rant: the GNOME team have been stripping out features and
removing useful functionality for years. I understand the idea of
boiling down a tool to its most essential parts, the benefits that that
has for maintainability, and the elegance of a focused UI. But come on.
It's easy to cross the line and break things that people rely on, and
that seems to have been GNOME's modus operandi for at least the past 6
years.

-- 
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/1164016

Title:
  restore type-ahead find

Status in Nautilus:
  Invalid
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1174936] Re: online-accounts-preferences crashes immediately when opened

2013-05-03 Thread Justin Force
Good call, @maarten-fonville! I am also using two-factor authentication.
I'm not going to disable it to test. I have not noticed or checked
whether the problem occurs without two-factor authentication.

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

Title:
  online-accounts-preferences crashes immediately when opened

Status in “empathy” package in Ubuntu:
  Confirmed
Status in “gnome-control-center-signon” package in Ubuntu:
  Confirmed

Bug description:
  `online-accounts-preferences` crashes immediately when opened. It
  crashes when you launch it by first opening "System Settings" via the
  launcher then choosing "Online Accounts" as well as when you open it
  directly by choosing "Online Accounts" from the launcher. It also
  crashes immediately when opened by running the `online-accounts-
  preferences` command on the command line.

  Here's the output it gives:

  % online-accounts-preferences
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'shotwell' with account '1'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-scope-gdrive' with account '1'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-lens-photos' with account '1'
  **
  ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec 
!= NULL)
  Aborted

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue Apr 30 14:03:48 2013
  InstallationDate: Installed on 2012-10-18 (194 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-control-center-signon
  UpgradeStatus: Upgraded to raring on 2013-04-26 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1174936/+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 1174936] [NEW] online-accounts-preferences crashes immediately when opened

2013-04-30 Thread Justin Force
Public bug reported:

`online-accounts-preferences` crashes immediately when opened. It
crashes when you launch it by first opening "System Settings" via the
launcher then choosing "Online Accounts" as well as when you open it
directly by choosing "Online Accounts" from the launcher. It also
crashes immediately when opened by running the `online-accounts-
preferences` command on the command line.

Here's the output it gives:

% online-accounts-preferences
credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'shotwell' with account '1'
credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-scope-gdrive' with account '1'
credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-lens-photos' with account '1'
**
ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec 
!= NULL)
Aborted

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue Apr 30 14:03:48 2013
InstallationDate: Installed on 2012-10-18 (194 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcEnviron:
 TERM=xterm-color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: gnome-control-center-signon
UpgradeStatus: Upgraded to raring on 2013-04-26 (4 days ago)

** Affects: gnome-control-center-signon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug raring

** Attachment added: "This is the output when running 
`online-account-preferences` on the command line"
   
https://bugs.launchpad.net/bugs/1174936/+attachment/3660738/+files/online-accounts-preferences.log

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

Title:
  online-accounts-preferences crashes immediately when opened

Status in “gnome-control-center-signon” package in Ubuntu:
  New

Bug description:
  `online-accounts-preferences` crashes immediately when opened. It
  crashes when you launch it by first opening "System Settings" via the
  launcher then choosing "Online Accounts" as well as when you open it
  directly by choosing "Online Accounts" from the launcher. It also
  crashes immediately when opened by running the `online-accounts-
  preferences` command on the command line.

  Here's the output it gives:

  % online-accounts-preferences
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'shotwell' with account '1'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-scope-gdrive' with account '1'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-lens-photos' with account '1'
  **
  ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec 
!= NULL)
  Aborted

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue Apr 30 14:03:48 2013
  InstallationDate: Installed on 2012-10-18 (194 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-control-center-signon
  UpgradeStatus: Upgraded to raring on 2013-04-26 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1174936/+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 781844] Re: Spell check is case sensitive

2011-10-20 Thread Justin Force
In Ubuntu Oneiric, the issue no longer seems to occur.

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

Title:
  Spell check is case sensitive

Status in “empathy” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: empathy

  When typing a message in an Empathy chat window, spell check is case
  sensitive. Capitalized words are always marked as misspelled. See
  attached screen shot.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: empathy 2.34.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia wl
  Architecture: i386
  Date: Thu May 12 10:49:22 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/781844/+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 711429] Dependencies.txt

2011-08-28 Thread Justin Force
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/711429/+attachment/2327548/+files/Dependencies.txt

-- 
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/711429

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  Happened when deleting a file.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Tue Feb  1 20:08:51 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: nautilus
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4cfbee:  mov0x18(%rdi),%rdx
   PC (0x004cfbee) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin 
plugdev sambashare tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/711429/+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 711429] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

2011-08-28 Thread Justin Force
Architecture: i386
DistroRelease: Ubuntu 11.04
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.32.2.1-0ubuntu13
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Tags:  natty running-unity
Uname: Linux 2.6.38-11-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare


** Tags added: apport-collected natty running-unity

-- 
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/711429

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  Happened when deleting a file.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Tue Feb  1 20:08:51 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: nautilus
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4cfbee:  mov0x18(%rdi),%rdx
   PC (0x004cfbee) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin 
plugdev sambashare tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/711429/+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 711429] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

2011-08-28 Thread Justin Force
This bug definitely still exists in Natty. The GNOME bug also indicates
that the fix is a hack, so I think this is still a problem.

To EASILY reproduce this:

1. Create a folder in Nautilus for testing. Press Ctrl-Shift-N 30 times or so 
to get a lot of folders to play with then press Enter to create them.
2. Select the top folder and start rapidly pressing the Delete key.
3. Where'd Nautilus go? 


See my previous apport-collect submission above for details.

-- 
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/711429

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  Happened when deleting a file.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Tue Feb  1 20:08:51 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: nautilus
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4cfbee:  mov0x18(%rdi),%rdx
   PC (0x004cfbee) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin 
plugdev sambashare tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/711429/+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 711429] GConfNonDefault.txt

2011-08-28 Thread Justin Force
apport information

** Attachment added: "GConfNonDefault.txt"
   
https://bugs.launchpad.net/bugs/711429/+attachment/2327549/+files/GConfNonDefault.txt

-- 
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/711429

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  Happened when deleting a file.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Tue Feb  1 20:08:51 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: nautilus
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4cfbee:  mov0x18(%rdi),%rdx
   PC (0x004cfbee) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin 
plugdev sambashare tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/711429/+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 711429] usr_lib_nautilus.txt

2011-08-28 Thread Justin Force
apport information

** Attachment added: "usr_lib_nautilus.txt"
   
https://bugs.launchpad.net/bugs/711429/+attachment/2327550/+files/usr_lib_nautilus.txt

-- 
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/711429

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  Happened when deleting a file.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Tue Feb  1 20:08:51 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: nautilus
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4cfbee:  mov0x18(%rdi),%rdx
   PC (0x004cfbee) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin 
plugdev sambashare tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/711429/+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 768338] Re: Banshee sometimes crashes at the end of a song

2011-08-28 Thread Justin Force
Binary package hint: banshee

It just closes. I'll wonder, "Why is it quiet?" And I find that Banshee
has closed/crashed. It only happens at the end of a song, so it's never
jarring.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: banshee 2.0.0-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia wl
Architecture: i386
Date: Fri Jun 17 11:27:44 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: No upgrade log present (probably fresh install)

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/768338/+attachment/2327504/+files/Dependencies.txt

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

Title:
  Banshee sometimes crashes at the end of a song

Status in Banshee Music Player:
  Confirmed
Status in “banshee” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: banshee

  I was listening to a few songs, one song finished to play and then
  banshee crashed, not surprising though since it's crashing every day
  for something different, i've already reported those bugs. I'm
  attaching the log.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: banshee 2.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  CheckboxSubmission: 4afb8c68a8fa5938a80183a271a939ea
  CheckboxSystem: c460f5739f7c8446c3d18c3e0e7c5745
  Date: Thu Apr 21 10:41:53 2011
  ProcEnviron:
   LANGUAGE=es_CL:es:en_GB:en
   LANG=en_US.UTF-8
   LC_MESSAGES=es_CL.utf8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: Upgraded to natty on 2011-02-01 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/banshee/+bug/768338/+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 798875] Re: Banshee frequently closes after finishing a song

2011-08-28 Thread Justin Force
*** This bug is a duplicate of bug 768338 ***
https://bugs.launchpad.net/bugs/768338

** This bug has been marked a duplicate of bug 768338
   Banshee sometimes crashes at the end of a song

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

Title:
  Banshee frequently closes after finishing a song

Status in “banshee” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: banshee

  It just closes. I'll wonder, "Why is it quiet?" And I find that
  Banshee has closed/crashed. It only happens at the end of a song, so
  it's never jarring.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: banshee 2.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia wl
  Architecture: i386
  Date: Fri Jun 17 11:27:44 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/798875/+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 796835] Re: screensaver runs twice after timeout when manually activated

2011-08-28 Thread Justin Force
I have not been able to attempt the steps that you've requested, Marc.
However, this bug is trivial to reproduce. I think that anybody with an
interest in fixing this bug should be able to troubleshoot it
themselves.

To reproduce:

1. Set the screensaver timeout to 1 minute
2. Manually lock the desktop with Ctrl-Alt-L or by clicking Lock Screen
3. Wait 70 seconds
4. Unlock the screen with your password.
5. Try to use your desktop. The screensaver reactivates. You must enter your 
password again.

Thanks,
Justin

** Changed in: gnome-screensaver (Ubuntu)
   Status: Expired => Incomplete

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

Title:
  screensaver runs twice after timeout when manually activated

Status in “gnome-screensaver” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gnome-screensaver

  If I manually activate the screensaver ("Lock Screen") with the Ctrl-
  Alt-L keyboard shortcut, the screensaver will activate AGAIN after the
  normal timeout (5 minutes in my case). So when I return to my
  computer, I enter my password, the screen is unlocked, then after a
  second or two the screen locks again I am prompted to enter my
  password again. After the second password entry, my screen is
  unlocked.

  I have verified that this does not occur when the screensaver is
  allowed to activate automatically. It's only the Ctrl-Alt-L "Lock
  Screen" action that causes the duplicate instance.

  This is not a duplicate of bug #556255. That bug is purportedly fixed.
  This is a new and separate issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-screensaver 2.30.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia wl
  Architecture: i386
  Date: Mon Jun 13 13:27:37 2011
  GconfGnomeSession:
   idle_delay = 5
    /desktop/gnome/session/required_components:
     windowmanager = gnome-wm
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)
  WindowManager: gnome-wm
  XorgConf:
   Section "Device"
    Identifier  "Default Device"
    Option  "NoLogo""True"
   EndSection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/796835/+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 798875] Re: Banshee frequently closes after finishing a song

2011-08-28 Thread Justin Force
I will attach ~/.config/banshee-1/log the next time the bug occurs.

** Changed in: banshee (Ubuntu)
   Status: Expired => Incomplete

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

Title:
  Banshee frequently closes after finishing a song

Status in “banshee” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: banshee

  It just closes. I'll wonder, "Why is it quiet?" And I find that
  Banshee has closed/crashed. It only happens at the end of a song, so
  it's never jarring.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: banshee 2.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia wl
  Architecture: i386
  Date: Fri Jun 17 11:27:44 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/798875/+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