[Desktop-packages] [Bug 1802520] Re: gnome-terminal prints gnome settings daemon log messages (?) every time I launch it

2019-05-08 Thread Joe Mooring
Same issue. Output:

# _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for 
‘gio-vfs’
# _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for 
 gsettings-backend’
# watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
# unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
# watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)

Environment:

Ubuntu 19.04
GNOME Shell 3.32.0
GNOME Terminal 3.32.1 using VTE 0.56.1 +GNUTLS
x11 (not wayland)

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

Title:
  gnome-terminal prints gnome settings daemon log messages (?) every
  time I launch it

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  $ gnome-terminal
  # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
  # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
  # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
  $ 

  Those three log messages printed when I run gnome-terminal are new in
  18.10.

  See also https://gitlab.gnome.org/GNOME/gnome-terminal/issues/42.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-terminal 3.30.1-1ubuntu1 [modified: 
usr/share/applications/org.gnome.Terminal.desktop]
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  9 09:18:38 2018
  InstallationDate: Installed on 2018-09-27 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1802520/+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 1062186] Re: 'Backup Failed' message when external backup drive first inserted

2014-04-07 Thread Joe Mooring
Thanks Matthias.  Your suggestion to connect another USB device to
trigger the backups works nicely.  I'm experiencing this problem on
14.04 Beta 2.

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

Title:
  'Backup Failed' message when external backup drive first inserted

Status in Déjà Dup Backup Tool:
  Confirmed
Status in “deja-dup” package in Ubuntu:
  Confirmed
Status in “deja-dup” package in Fedora:
  Unknown

Bug description:
  An error message entitled 'Backup Failed' with the text 'An operation
  is already pending' is displayed when I first plug in by external
  backup drive and Deja Dup attempts to perform a scheduled backup,
  although it succeeds on subsequent attempts (either scheduled or
  manual).

  The fstab entry for the drive is as follows:
  /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 
/media/thomas/Tom\040WD\040HD auto 
nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0

  I presume this is either due to both Gnome and Deja Dup attempting to
  mount the drive, or Deja Dup not waiting until the drive has been
  successfully mounted.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: deja-dup 24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  5 11:45:05 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120913)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1062186/+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 1274667] Re: messages are gone after reboot on the phone

2014-03-27 Thread Joe Mooring
On 14.04 beta 2 desktop, the timeline is blank every time I login.  I
have friends-app set to start automatically at startup (Startup
Applications).  As a workaround, I have changed the startup command to:

sh -c rm ~/.cache/friends/*  friends-app 

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

Title:
  messages are gone after reboot on the phone

Status in “friends” package in Ubuntu:
  Confirmed

Bug description:
  When I reboot my Ubuntu Phone all tweets/messages are gone.

  However, friends seems to remember the last time it refreshed and only
  fetches a few new messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1274667/+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 877642] Re: Status on messaging indicator is greyed out if Empathy is added to the Startup Applications list

2012-04-04 Thread Joe Mooring
** Changed in: telepathy-indicator (Ubuntu)
   Status: Incomplete = New

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

Title:
  Status on messaging indicator is greyed out if Empathy is added to the
  Startup Applications list

Status in “telepathy-indicator” package in Ubuntu:
  New

Bug description:
  Like the title says.

  I'm on the laptop I use for work, and I always want Empathy to load on
  startup.  So I added it to the list of Startup Applications.  Now,
  when I login, Empathy starts, but indicator-messages displays my
  status as offline and all of the status options are grey.  I have to
  change status in the Empathy app itself in order to make available
  those options in the messaging indicator.

  If I start Empathy via the messaging indicator, I do not have this
  problem.

  It is small, but annoying.  I think it is simply a case of Unity
  loading after Empathy.  There used to be a way to prioritize what
  loaded first in the startup applicaiton pile, but I haven't seen that
  available in quite a while.  I think it'd probably be best to make
  sure unity loads *first* before anything on that list, but that's a
  guess on my part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-indicator/+bug/877642/+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 877642] Re: Status on messaging indicator is greyed out if Empathy is added to the Startup Applications list

2012-04-04 Thread Joe Mooring
See attached screen capture when /usr/bin/empathy -h is called at
startup.

** Attachment added: screen-capture-877642.jpeg
   
https://bugs.launchpad.net/ubuntu/+source/telepathy-indicator/+bug/877642/+attachment/3004650/+files/screen-capture-877642.jpeg

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

Title:
  Status on messaging indicator is greyed out if Empathy is added to the
  Startup Applications list

Status in “telepathy-indicator” package in Ubuntu:
  New

Bug description:
  Like the title says.

  I'm on the laptop I use for work, and I always want Empathy to load on
  startup.  So I added it to the list of Startup Applications.  Now,
  when I login, Empathy starts, but indicator-messages displays my
  status as offline and all of the status options are grey.  I have to
  change status in the Empathy app itself in order to make available
  those options in the messaging indicator.

  If I start Empathy via the messaging indicator, I do not have this
  problem.

  It is small, but annoying.  I think it is simply a case of Unity
  loading after Empathy.  There used to be a way to prioritize what
  loaded first in the startup applicaiton pile, but I haven't seen that
  available in quite a while.  I think it'd probably be best to make
  sure unity loads *first* before anything on that list, but that's a
  guess on my part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-indicator/+bug/877642/+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 958238] [NEW] Several options for rhythmbox-client are non-functional

2012-03-17 Thread Joe Mooring
Public bug reported:

lsb_release -rd:

Description:Ubuntu precise (development branch)
Release:12.04

apt-cache policy rhythmbox:

rhythmbox:
  Installed: 2.96-0ubuntu1
  Candidate: 2.96-0ubuntu1
  Version table:
 *** 2.96-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status

Several of the options listed on the man page for rhythmbox-client are
non-functional.

$rhythmbox-client --hide
Rhythmbox-WARNING **: Unknown option --hide


$rhythmbox-client --notify
Rhythmbox-WARNING **: Unknown option --notify

$rhythmbox-client --mute
Rhythmbox-WARNING **: Unknown option --mute

$rhythmbox-client --unmute
Rhythmbox-WARNING **: Unknown option --unmute

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

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

Title:
  Several options for rhythmbox-client are non-functional

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  lsb_release -rd:

  Description:  Ubuntu precise (development branch)
  Release:  12.04

  apt-cache policy rhythmbox:

  rhythmbox:
Installed: 2.96-0ubuntu1
Candidate: 2.96-0ubuntu1
Version table:
   *** 2.96-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  Several of the options listed on the man page for rhythmbox-client are
  non-functional.

  $rhythmbox-client --hide
  Rhythmbox-WARNING **: Unknown option --hide

  
  $rhythmbox-client --notify
  Rhythmbox-WARNING **: Unknown option --notify

  $rhythmbox-client --mute
  Rhythmbox-WARNING **: Unknown option --mute

  $rhythmbox-client --unmute
  Rhythmbox-WARNING **: Unknown option --unmute

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