@Jonas: If KDE is launching apps in the same way gnome-shell was, it is
inherently racy. It needs to make sure the child process is in the new
cgroup before executing the application.
Doing the cgroup move after the app is already running causes problems
if the application itself wants to
Public bug reported:
It could be a problem with the network, but I'm seeing cups-browsed
appearing to keep one CPU core busy. According to systemctl, it has used
51 minutes of CPU time since being started 6 hours ago (the laptop has
been suspended a few times in that time):
Active: active
I did a search through the KDE bug tracker, and it looks like someone
reported the same root problem back in 2020:
https://bugs.kde.org/show_bug.cgi?id=423756
** Bug watch added: KDE Bug Tracking System #423756
https://bugs.kde.org/show_bug.cgi?id=423756
--
You received this bug
I've filed https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565
upstream to cover the gnome-shell problem.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6565
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565
** Also affects: gnome-shell via
Public bug reported:
After upgrading to Lunar, I see the following warning messages when I
start Emacs:
Warning (comp): Cannot look-up eln file as no source file was found
for /usr/share/emacs/site-lisp/elpa/use-package-2.4.1/use-package.elc
Disable showing Disable logging
After the
> So, I feel snapd tracker should somewhat be able to track that an app
> changed its cgroup and move it back to what it belongs, but as discussed
> in https://github.com/systemd/systemd/issues/26925 there's nothing
> telling us that right now.
There is no "snapd tracker". It's the "snap run"
Another idea for how to synchronise the StartTransientUnit call without
resorting to passing pipe file descriptors to the child: we could simply
have the child_setup_func call kill(getpid(), SIGSTOP). The parent
process can now do the cgroup move at its leisure, and then send a
SIGCONT to the
@Batuhan: it's different code, but looks to be the same type of problem:
https://github.com/KDE/kio/blob/5bda428992cbd168fc1898661d80a089a8217449/src/gui/systemd/scopedprocessrunner.cpp#L13-L41
It's moving the process to a new cgroup after the application has
started executing (so happens
I've created https://github.com/snapcore/snapd/pull/12627 as a proposed
fix for the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2008279
Title:
glib2.0 2.75.3-3 breaks text
Okay. In a clean Lunar VM with glib 2.75.3 installed and ibus enabled as
described in the bug description, I could reproduce the input problems
in Firefox. I saw the following AppArmor denial in the dmesg logs:
[ +0.343553] audit: type=1400 audit(1678248386.012:62):
apparmor="DENIED"
This seems like the most likely culprit:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3005
This basically means that code that would have created an abstract
namespace socket in glib 2.74.x now creates a regular unix domain socket
in 2.75.x. We have AppArmor rules in snapd's
I think last time we had problems like this it was due to changes in the
location of the socket for ibus's private D-Bus bus. Looking into the
glib diffs for clues.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
*** This bug is a duplicate of bug 1966108 ***
https://bugs.launchpad.net/bugs/1966108
** This bug has been marked a duplicate of bug 1966108
Chromium snap on Jammy system with nvidia-510 does not start
--
You received this bug notification because you are a member of Desktop
Packages,
> Is there any option to do this via portals - ie can evince use
> org.freedesktop.portal.OpenURI to open the URI? Would then this
> allow to avoid going via xdg-open?
Evince is using g_app_info_launch_default_for_uri(), which can use the
portal interface:
> Is there such a snap you could point me to so I can test?
The candidate channel of the gedit snap is built with core20 and the
gnome-3-38-2004 platform snap. But as I said, I don't think that
platform snap currently includes the fcitx5 input module.
--
You received this bug notification
I hadn't realised that they renamed the IM module with the version bump:
that means snaps built against older platforms won't load the old (but
working) Fcitx 4 module when run on a host system configured with Fcitx
5.
We can certainly look at adding the new IM module to the platform snaps,
but
Just repeating what I said on the forum, I believe this could be
implemented through updates to the base snaps with no changes to snapd
or any application snaps.
The mdns4_minimal NSS plugin is an 18K binary (which compresses to about
6KB) that delegates its lookups to avahi-daemon using a single
I've updated the description with the SRU bug template. I think this
includes all the relevant info?
** Description changed:
- I'm trying to run chromium installed via snap in Ubuntu 20.10 when
- running Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
+ [Impact]
- > chromium
I had a go at fixing this in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 -- taking
the patches from that MR and applying them to the Groovy mutter source
package gave me a Wayland session that supported X11 snaps again.
It is probably worth waiting for a review from upstream
I've filed https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 upstream
about this regression.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1454
https://gitlab.gnome.org/GNOME/mutter/-/issues/1454
--
You received this bug notification because you are a member of Desktop
Looking at the reasoning behind that change, Mutter introduced lazy
initialisation of Xwayland: binding the two sockets, and starting
Xwayland when someone connected to the abstract namespace socket.
Flatpak apps apparently can't speak to the abstract namespace socket, so
would hang forever when
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1424 is
definitely the culprit here. Snaps depend on access to the abstract
namespace socket to function correctly.
Inside the sandboxes, snaps see a private /tmp that is under their
complete control. So there is no /tmp/.X11-unix directory
This is the in-progress fix I've been working on. It does not quite
work right though: switching to an async hook for these commands is
resulting in the daemon killing the client on a protocol error.
This might be a problem with the hooks patch set itself. I need to
investigate a bit further.
Sorry for taking so long to get back to you. I now understand the non-
deterministic behaviour you're seeing.
I'm working on a fix for the server side to allow classic snaps to
access these commands. It will require a small change to your Pulse
Audio client library to fix the non-determinism
I think I need to dig into this further. The fact you're seeing a few
successful module loads with different module indexes would indicate it
is the same Pulse Audio instance.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
I think there's two issues at play here.
The hooks we added for module loading/unloading as part of USN-4355-1
simply check if the client has an AppArmor label that looks like it
belongs to a snap and denies access if found. This will also deny
access to classic snaps, which is probably a
I've just been reading through the code used to build the bin/fc-
cache-v6 and bin/fc-cache-v7 binaries in the core snap:
https://github.com/snapcore/fc-cache-static-builder
I think I understand what the problem is: while it is rebuilding copies
of xenial's and bionic's fontconfig tools that
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080/+attachment/5335924/+files/lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
When I upgraded my desktop yesterday, I could no longer see the mouse
cursor on the screen. It still responded to mouse clicks (e.g. context
menu on right click, pushing the mouse to the top left and left clicking
went to spread mode, etc).
This only seems to affect the
I noticed something like this on my desktop system after upgrading. It
only seems to affect Wayland sessions (i.e. GDM login screen and Ubuntu
on Wayland). The mouse still works (i.e. desktop responds to clicks),
but no cursor is drawn. Everything seems fine on my laptop though.
The main
Is there some way gnome-software can inform the plugin that it is
performing a non-interactive operation?
If so, then the plugin could use snapd_client_set_allow_interaction() to
suppress any potential pokit dialogs from the operation. It wouldn't
allow the operation to succeed, but it also
If you are worried about what the Pulse Audio change is actually doing,
here's a description:
1. there is a new "snap-policy" PA module that is loaded by default.
2. when a client attempts to use the microphone and has a "snap.*"
AppArmor label, it contacts snapd to check whether that app has
The two packages are in the upload queue now:
https://launchpad.net/ubuntu/xenial/+queue?queue_state=1_text=pulseaudio
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=pulseaudio
One additional acceptance test would be to verify that the policy module
continues to work
required by the snap policy module due to a symbol name clash with
libjson-glib.
- 0805-remove-libjson-c-dependency.patch: new file.
-- James Henstridge Tue, 05 Nov 2019
17:16:22 +0800
** Bug watch added: freedesktop.org Bugzilla #95135
https://bugs.freedesktop.org/show_bug.cgi?id=9
efault configuration.
- Build depend on libsnapd-glib-dev.
* Remove module-trust-store patch set:
- 0409-Trust-store-patch.patch: trimmed down to pulsecore changes.
- 0410-Add-thread-to-activate-trust-store-interface.patch: removed.
- 0417-increase-timeout-check-apparmor.patch: removed.
The xenial backport is non-functional due to a symbol collision between
libjson-c.so (required by libpulse) and libjson-glib.so (required by
snapd-glib). This doesn't affect the Bionic backport though.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Does it actually make sense to have symbols files for plugins? As long
as they work with the libsane.so.1 that they're shipped with, does it
matter what symbols they export?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends
If you are running an X session, then you are running into a different
issue.
The set of circumstances that lead to the problem on Wayland (different
gsettings defaults inside and outside of confinement) do not apply to
X11 where the theme is exposed by the host over XSETTINGS (so sees the
At didrocks' request, I've also filed this here:
https://github.com/ubuntu/yaru/issues/1196
** Bug watch added: github.com/ubuntu/yaru/issues #1196
https://github.com/ubuntu/yaru/issues/1196
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
I am using gnome-terminal 3.31.90-1ubuntu1 on a Disco desktop. If I
create a gnome-terminal window and add a second tab, the window will
shrink by one line each time I switch tabs.
This seems to be theme related, since it happens with Yaru but not with
Adwaita. Some
This bug occurs when using the "SaveFile" desktop portal API and the
user chooses a new file name rather than overwriting an existing file.
It can easily be reproduced with the following steps:
1. install the test-snapd-portal-client snap:
snap install --edge test-snapd-portal-client
2.
*** This bug is a duplicate of bug 1810757 ***
https://bugs.launchpad.net/bugs/1810757
Public bug reported:
When using the desktop portal API to save a file, the xdg-document-
portal service crashes if we try to save to a new file name.
Steps to reproduce:
1. On an Ubuntu 18.10 system,
** Description changed:
Fontconfig 2.13.0 changed the cache file naming scheme to be based on
the contents of ".uuid" file in the directory rather than a hash of the
directory name. On a pure debs system this doesn't really matter since
everything is using the same libfontconfig.so.
Looking at the gnome-shell JS code referenced by the stack trace, it
appears it is indeed disabling extensions when locking the screen.
The screenShield.js code handles the lock screen, and pushes and pops a
"session mode" of "lock-screen". In sessioMode.js, the "lock-screen"
mode is defined
The above stack trace seems to be tied to this other message:
Nov 16 11:41:38 scruffy gnome-shell[5626]: Object Meta.WindowActor
(0x560d5092bb00), has been already deallocated — impossible to access
it. This might be caused by the object having been destroyed from C code
using something such as
I noticed this behaviour on my Ubuntu 18.10 system. It is running the
Wayland session, and I only have the ubuntu-d...@ubuntu.com and ubuntu-
appindicat...@ubuntu.com extensions installed (i.e. no upstream dash-to-
dock).
I looked in the journal and found the attached GJS stack trace, which
A backport of the UUID cache file directory feature from fontconfig
2.13.
** Patch added: "fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+attachment/5213086/+files/fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff
--
You
Public bug reported:
Fontconfig 2.13.0 changed the cache file naming scheme to be based on
the contents of ".uuid" file in the directory rather than a hash of the
directory name. On a pure debs system this doesn't really matter since
everything is using the same libfontconfig.so.
When snaps are
Public bug reported:
The xenial backport of the fix for 1781428 malfunctioned due to the use
of snapd-glib behaviour introduced after the version included in xenial:
namely auto-connection (and reconnection) to the snapd socket that was
introduced in snapd-glib 1.24.
With the policy module
Here is a debdiff based on the attached branch.
** Patch added: "pulseaudio_12.2-0ubuntu2_12.2-0ubuntu3.diff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+attachment/5181694/+files/pulseaudio_12.2-0ubuntu2_12.2-0ubuntu3.diff
--
You received this bug notification
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-audio-dev/pulseaudio/+git/pulseaudio/+merge/353214
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1787324
Title:
skype.skype /usr/bin/parecord foo.wav
Stream error: Access denied
[note that the Skype app itself still functions because it bypasses
PulseAudio all together]
The above command should result in audio being recorded from the
microphone.
** Affects: pulseaudio (Ubuntu)
Importance: High
Attached is a debdiff for a 1:12.2-0ubuntu2 release of pulseaudio with
an updated snap policy module and the default configuration modified to
enable it.
I also took the opportunity to remove the Ubuntu Phone era trust-store
module, which hasn't been built since February.
** Patch added:
bionic-proposed has a 3.28.2 package, so this should be resolved for
that release shortly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1774560
Title:
xdg-desktop-portal-gtk
@simosx: I gave this another test on a clean xenial VM with the same
gnome-software version as you. Each time it launched the main
"libreoffice" command (showing a window asking to open recent files or
create a new document in one of the libreoffice applications).
gnome-software continues
** Bug watch added: GNOME Bug Tracker #793473
https://bugzilla.gnome.org/show_bug.cgi?id=793473
** Also affects: gnome-screenshot via
https://bugzilla.gnome.org/show_bug.cgi?id=793473
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Description changed:
[Impact]
Apps that use classic confinement show up in search results but don't install.
[Test Case]
1. Open GNOME Software
2. Search for a classic snap, e.g. "atom"
3. Install snap
Expected result:
Either:
a) Snap is installed
b) Snap is not
Here's a debdiff for the Xenial package update based on Robert's work.
I don't have upload rights to upload it myself.
** Patch added:
"gnome-software_3.20.5-0ubuntu0.16.04.7_3.20.5-0ubuntu0.16.04.8.diff"
I've got an (as yet unmerged) snapd branch to help with this:
https://github.com/snapcore/snapd/pull/4055
It got a review yesterday, so should go in the next snapd release.
This is basically doing (1), returning a Forbidden error when the user
dismisses the dialog.
--
You received this bug
Snapd side changes:
https://github.com/snapcore/snapd/pull/4061
It looks like snapd-glib might need a change too, since it looks like
this will still be mapped to SNAPD_ERROR_FAILED in parse_result() (I
think falling back to treating 401 as SNAPD_AUTH_DATA_REQUIRED will do).
--
You received
Yep. There is code to prevent refreshing the macaroon if the user has
changed their password since it was created:
http://bazaar.launchpad.net/~canonical-isd-hackers/canonical-identity-
provider/trunk/view/head:/src/identityprovider/auth.py#L661
This should help in reproducing the bug.
--
You
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1724316
Title:
"Sorry, something went wrong cannot
Discussion started here:
https://forum.snapcraft.io/t/handling-invalid-credentials/2526
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1724316
Title:
"Sorry, something went
So further investigation, the "cannot authenticate to snap store: " part
of the error is only added by snapd for an unexpected error:
https://github.com/snapcore/snapd/blob/master/store/auth.go#L190-L204
I believe this is being called via the refreshDischarges() method,
intended to keep the
The "Provided email/password is not correct." part of the error message
appears to be coming through straight from the store. This most likely
means you logged in to gnome-software using Ubuntu One credentials at
some point in the past, and the credentials snapd has stored are no
longer valid.
I set up a clean VM running up to date artful, which includes
snapd-2.28.5+17.10 (so no copying of policy files or changing channel
for core snap), and couldn't reproduce this. I started gnome-software,
and tried to install the Hiri snap and got the expected polkit prompt.
I did get the
(Ubuntu)
Importance: Medium => Low
** Changed in: whoopsie-preferences (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie
So I think I've got things sorted out by (a) switching to call
SetReportCrashes async to avoid blocking the UI, and (b) not calling
SetReportCrashes if we're asked to set it to the current (cached) value
of the property.
I've noticed that if whoopsie-preferences exits while the privacy panel
is
rol-center (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie continually relaunching
St
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie
** Bug watch added: Red Hat Bugzilla #1448962
https://bugzilla.redhat.com/show_bug.cgi?id=1448962
** Also affects: libinput (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1448962
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
While looking around for code that might resume the touchpad, I noticed
that the libinput master code was a bit different to the version we
ship: there's a tp_resume_conditional() function that checks sendevents.
And checking the history shows up this patch:
So, I don't think there is any problem on the gnome-control-center side:
it just sets the org.gnome.desktop.peripherals.touchpad/send-events
GSetting key to disabled, and that is persisting over sleeps.
The code in mutter watches this key, and calls
MetaInputSettings::set_send_events() on each
I've sent our patch upstream to see if we can get a version of it
included. I suspect it'll need some changes in order to be acceptable,
assuming they want it. So I'll try to address that as needed.
** Bug watch added: GNOME Bug Tracker #788216
** Branch linked: lp:~jamesh/gnome-control-center/ubuntu-whoopsie-
support
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1698035
Title:
gnome-control-center lacks any
ged in: snapd (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1581713
Title:
Ubuntu Software always asks for an
** Bug watch added: GNOME Bug Tracker #785117
https://bugzilla.gnome.org/show_bug.cgi?id=785117
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=785117
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Bug watch added: GNOME Bug Tracker #784773
https://bugzilla.gnome.org/show_bug.cgi?id=784773
** Also affects: gnome-software via
https://bugzilla.gnome.org/show_bug.cgi?id=784773
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Bug watch added: GNOME Bug Tracker #784600
https://bugzilla.gnome.org/show_bug.cgi?id=784600
** Also affects: gnome-software via
https://bugzilla.gnome.org/show_bug.cgi?id=784600
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I put together a gnome-software patch to use the extra info from mvo's
snapd change:
https://code.launchpad.net/~jamesh/gnome-software/+git/gnome-
software/+ref/pick-launch-app
It still only supports running one application, but it now favours apps
that provide a desktop file, and the snap's
I've made some simple UI changes in the following branch forked from
ubuntu-master, based on Robert's patch:
https://code.launchpad.net/~jamesh/gnome-software/+git/gnome-
software/+ref/classic-snap-install
This adds a warning message at the top of the details list when viewing
an snap that is
** Summary changed:
- Mediascanner is not working
+ frieza_arm64, staging #99: SD card not mounted
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1649313
Title:
frieza_arm64,
** Also affects: udisks2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1649313
Title:
Mediascanner is not working
Status in
Public bug reported:
Please add an account-plugin-nextcloud package.
For now, this could essentially be a copy of the ownCloud provider code
with different branding. Having both providers side-by-side has a few
benefits:
1. we can pick which one to install to get desired branding
2. if the
This is looking like a case of the code being miscompiled under
optimisation. To reproduce, build mediascanner2 using the
"RelWithDebInfo" build type and then run:
./test/test_dbus --gtest_filter=*filter_codec
The test program segfaults when calling Variant::as() on a
variant that should
Public bug reported:
When trying to build a new mediascanner2 release, tests failed on a
number of architectures when building under Yakkety. Some relevant
logs:
https://launchpadlibrarian.net/281862518/buildlog_ubuntu-yakkety-armhf.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
I'm not convinced my bug is the same as this one. That said, the
changes in the latest dbus-cpp package don't look particularly ABI
compatible, which may be the cause of this bug:
https://launchpadlibrarian.net/279409841/dbus-
I'm not sure if it is related, but I've encountered test failures in my
mediascanner2 silo for dbus-cpp code that previously ran without issue:
https://launchpadlibrarian.net/281863370/buildlog_ubuntu-yakkety-
arm64.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
It also failed on
One last comment: I tried downloading upstream pygobject 3.20.0 (which
was released two days ago), and the scopes run fine using the Xenial
typelib.
So I think the underlying problem is that we've got a problem of version
skew, with the versions of gobject-introspection and pygobject currently
in
Public bug reported:
The package install failed when trying to restart the brltty service.
It suggested checking the status using systemctl, which showed the
following errors:
Jan 12 11:32:13 scruffy systemd[1]: [/lib/systemd/system/brltty.service:16]
Unbalanced quoting, ignoring: "/bin/sh -c
** Package changed: flashplugin-nonfree (Ubuntu) => youtube-dl (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1518235
Title:
youtube-dl is outdated
Status in
For what it is worth, I managed to catch a segfault on shutdown of
music-app (i.e. swiping vertically in the app spread) on the phone. I
couldn't get a usable apport crash dump, but managed to catch it in gdb.
This is with libdbus-cpp 4.3.0+15.04.20151126-0ubuntu1 and libmedia-hub-
client
This sounds a lot like bug 1422304, by the look of it.
Both QtDBus and dbus-cpp make use of libdbus. Libdbus provides a
dbus_shutdown() function that will release various internal global
state, which can be used to remove those allocation from the report
valgrind produces when analysing your
** Branch linked: lp:~jamesh/thumbnailer/qml-module-package-name
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to qtlocation-opensource-src in Ubuntu.
https://bugs.launchpad.net/bugs/1342031
Title:
Rename QML modules to follow
** No longer affects: gstreamer (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1466273
Title:
gstreamer fails intermittently
Status in Thumbnail generator for all
I gave michi's branch and test videos a try. For the six videos being
thumbnailed in parallel, I see two successful thumbnails, two instances
that look like they died due to invalid memory allocations:
(vs-thumb:15299): GLib-ERROR **:
/build/buildd/glib2.0-2.45.1/./glib/gmem.c:357: overflow
gbAnd ultimately the select() call in waitForFinished() was blocking on
a pipe that would be written to when the SIGCHLD signal handler was
called and waitid() returned the subprocess's pid. So this is
functionally the same as the direct waitpid() call.
--
You received this bug notification
This seems to be related to the androidmedia elements from
gstreamer1.0-hybris, so changing the source package link: I can't
reproduce it with the standard elements.
In the hope that this might be a quirk of the pipeline used by vs-thumb,
I've ported the utility over to using the standard playbin
Public bug reported:
dbus-cpp includes a library, yet the package description still claims it
is a header-only dbus-binding. This should be updated to reflect the
current state of the package.
** Affects: dbus-cpp (Ubuntu)
Importance: Undecided
Status: New
--
You received this
1 - 100 of 111 matches
Mail list logo
