Re: [Bug 1779907] Re: Object St.BoxLayout has been already deallocated - impossible to connect to signal.

2018-07-03 Thread Chris Hermansen
I don't have a problem with reporting this to the authors of the
openweather extension, but I guess I'm surprised the extension can cause
hundreds of error messages to be written to the syslog - seems like that
might be some sign of weakness in Gnome Shell... but I'm certainly no
expert.

On Tue, Jul 3, 2018 at 7:15 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thanks. In that case please report the problem to the authors of the
> openweather extension.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1779907
>
> Title:
>   Object St.BoxLayout has been already deallocated - impossible to
>   connect to signal.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779907/+subscriptions
>


-- 
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.

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

Title:
  Object St.BoxLayout has been already deallocated - impossible to
  connect to signal.

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

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

[Bug 1779907] [NEW] Object St.BoxLayout has been already deallocated - impossible to connect to signal.

2018-07-03 Thread Chris Hermansen
Public bug reported:

On system boot, syslog is filled with messages of the form:

Object St.BoxLayout (0x55736a43df40), has been already deallocated -
impossible to connect to signal. This might be caused by the fact that
the object has been destroyed from C code using something such as
destroy(), dispose(), or remove() vfuncs

Object St.Label (0x55736a684930), has been already finalized. Impossible
to set any property to it.

followed by stack traces

followed by more messages of the form

Object St.Label (0x55736a684930), has been already finalized. Impossible
to set any property to it.

These seem to relate to specific resource:///... extensions such as
ubuntu-doc, openweather-extension, and so on.

There are also assertions that fail of the form

clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  3 09:53:35 2018
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-07 (268 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-05-15 (48 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Object St.BoxLayout has been already deallocated - impossible to
  connect to signal.

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

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

[Bug 1779907] Re: Object St.BoxLayout has been already deallocated - impossible to connect to signal.

2018-07-03 Thread Chris Hermansen
Huh.  Just for fun I decided to disable the openweather extension in
Tweak Tool and reboot.  All those messages went away...

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

Title:
  Object St.BoxLayout has been already deallocated - impossible to
  connect to signal.

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

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

[Bug 1762035] Re: mutter crashed while selecting a running application from the launcher

2018-04-17 Thread Chris Hermansen
Hmmm ok I cannot open the bibliography database.  Every time I try, I am
informed I need to restart.  Seems like I have to chase a LibreOffice
bug first.

Sorry!

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

Title:
  mutter crashed while selecting a running application from the launcher

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

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

[Bug 1762035] Re: mutter crashed while selecting a running application from the launcher

2018-04-17 Thread Chris Hermansen
Interesting perhaps that trying to start the bibliography window
required a restart of the LibreOffice window.

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

Title:
  mutter crashed while selecting a running application from the launcher

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

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

[Bug 1762035] Re: mutter crashed while selecting a running application from the launcher

2018-04-17 Thread Chris Hermansen
In my /etc/apport/crashdb.conf the offending line is no longer 23, it's
20.

Testing now

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

Title:
  mutter crashed while selecting a running application from the launcher

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

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

[Bug 1762035] Re: mutter crashed while selecting a running application from the launcher

2018-04-17 Thread Chris Hermansen
Restarting didn't help, still was informed I needed to restart.  I feel
like Alice...

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

Title:
  mutter crashed while selecting a running application from the launcher

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

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

[Bug 1762035] Re: mutter crashed while selecting a running application from the launcher

2018-04-16 Thread Chris Hermansen
Daniel, thanks for pointing out this need to reconfigure a bit.  I'm
sorry I missed that.

I will follow your steps and see if I can reproduce the mutter failure.

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

Title:
  mutter crashed while selecting a running application from the launcher

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

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

[Bug 1762035] [NEW] mutter crashed while selecting a running application from the launcher

2018-04-07 Thread Chris Hermansen
Public bug reported:

I had two windows running in LibreOffice - the document window and the
bibliographic entry window.  When I tried to select the document window
from the Gnome3 launcher, the desktop froze - no mouse movement, no
keyboard.  After about 1 minute the Gnome 3 session restarted.  This
message in the log file:

[94877.938951] gnome-shell[1993]: segfault at 30 ip 7f38e21f3f98 sp
7ffc9d8bbfe0 error 4 in libmutter-1.so.0.0.0[7f38e211e000+142000]

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: mutter 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  7 10:50:21 2018
InstallationDate: Installed on 2017-11-01 (157 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  mutter crashed while selecting a running application from the launcher

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

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

[Bug 1706097] Re: gvfsd-mtp crashed with SIGSEGV

2017-10-19 Thread Chris Hermansen
I reported this separately as 1725030 but it is apparently a duplicate
of this.

I'm a bit surprised at that because this problem never occurred in 17.04
but did so the first time I plugged my phone into 17.10.

Anyway if anyone here needs more info, I'm your person.

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1725030] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-10-19 Thread Chris Hermansen
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Public bug reported:

I had my Pixel XL mounted in 17.10 Nautilus and selected all the files
in the Music subfolder for deletion.  This error occurred "right away"
when I started the delete.

I was subsequently able to continue with deleting the files, without
restarting Nautilus or anything else obvious in terms of resetting...

Description:Ubuntu 17.10
Release:17.10

gvfs:
  Installed: 1.34.1-1ubuntu1
  Candidate: 1.34.1-1ubuntu1
  Version table:
 *** 1.34.1-1ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 16:14:25 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2017-10-07 (11 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 /org/gtk/gvfs/exec_spaw/8
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f696d23a5a9:  mov0x18(%rax),%rax
 PC (0x7f696d23a5a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash artful wayland-session

** Information type changed from Private to Public

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1713880] [NEW] glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

2017-08-29 Thread Chris Hermansen
Public bug reported:

Not a lot,really - a massive number of packages upgraded in Artful,
rebooted with systemctl,then this happened after logging in and before
firing anything else up.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libglib2.0-0 2.53.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Tue Aug 29 17:34:27 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
InstallationDate: Installed on 2017-07-27 (33 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:mov
(%rax),%rdi
 PC (0x7f4dda0a1d52) ok
 source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: glib2.0
StacktraceTop:
 __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
 ?? ()
Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1713880/+subscriptions

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


[Bug 1633979] [NEW] gnome-terminal appears in launcher twice when running

2016-10-16 Thread Chris Hermansen
Public bug reported:

In Ubuntu 16.10, I have gnome-terminal in my launcher.  When I start it,
I see two terminals in the launcher - one representing the running
terminal(s), one that allows me to open another terminal.  No other
application seems to behave this way.  I don't believe this behaviour
was evident in 16.04.

FWIW I have Ubuntu Tweak Tool also installed and I have selected
minimize single window applications on click (which works).  Also this
was an upgrade from 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-terminal 3.20.2-1ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 16 21:06:42 2016
InstallationDate: Installed on 2016-02-03 (256 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (3 days ago)

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "In this screenshot two gnome-terminals can be seen in 
launcher; only one EasyTag though, even though also open."
   
https://bugs.launchpad.net/bugs/1633979/+attachment/4762276/+files/two_gnome_terminals.png

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

Title:
  gnome-terminal appears in launcher twice when running

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

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


[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

2016-10-16 Thread Chris Hermansen
My steps are similar to #4 above but the problem occurs when I am logged
in as regular user (me).

Seems to be no workaround.

FWIW my 16.10 is upgraded from 16.04 and not a fresh install.

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

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

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

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


[Bug 934291] Re: Deleting or stopping print jobs does not work

2013-06-03 Thread Chris Hermansen
Sebastien, I am running 13,04 and confirm that the System Settings 
Printers as invoked from Gnome Shell is

- unable to cancel my jobs
- unable to display others' jobs that are hung / clogging up the printer queue
- absent of some useful features like the enabled checkbox

I can make screen shots if that is useful

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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


[Bug 1063905] [NEW] nautilus crashed with SIGSEGV in g_list_foreach()

2012-10-08 Thread Chris Hermansen
Public bug reported:

In the middle of signing into Ubuntu One, just beginning step Syncing
your computer with the cloud, when this error popped up.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Mon Oct  8 09:29:49 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta i386 (20121007)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6a4f738 g_list_foreach+24:  mov0x4(%eax),%esi
 PC (0xb6a4f738) ok
 source 0x4(%eax) (0x0014) not located in a known VMA region (needed 
readable region)!
 destination %esi ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_list_foreach () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_list_free_full () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in g_list_foreach()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: apport-crash i386 need-i386-retrace quantal running-unity

** Visibility changed to: Public

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

Title:
  nautilus crashed with SIGSEGV in g_list_foreach()

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

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


[Bug 982559] Re: [power]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

2012-04-15 Thread Chris Hermansen
** Visibility changed to: Public

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

Title:
  [power]: gnome-settings-daemon crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

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

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


[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

2009-11-25 Thread Chris Hermansen
I am suddenly having problems with launching applications in 9.10
(perhaps an unrelated issue) but I see a fresh copy of .xsession-errors
containing something very similar to this (latest attached) on session
startup.  May have something to do with gstreamer but I have not started
any audio / video apps at this point.

** Attachment added: .xsession-errors
   http://launchpadlibrarian.net/36075962/.xsession-errors

-- 
GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
https://bugs.launchpad.net/bugs/384439
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 148672] Re: USB mass storage and rhythmbox problems

2008-02-11 Thread Chris Hermansen
With respect to the second part of the bug report, the UI requested
exists already.

Edit Rhythmbox preferences.  Select the Music tab.  Then click on the
Edit button next to the Preferred format dropdown.

Using the editor that pops up, the user can:

* activate / deactivate the support for the format (e.g. turn off MP3 support);
* change the extension;
* alter the bitrate.

It even looks as though by editing the command string a different codec
could be used.

I have confirmed that changing the quality for Ogg files produces the
desired bit rate upon (automatic) transcoding.

I guess the only other thing I would say is that the functioning of this
feature doesn't seem really obvious to me.

You still need to edit the HAL config file if your device is not known
or the config file is incorrect.

-- 
USB mass storage and rhythmbox problems
https://bugs.launchpad.net/bugs/148672
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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