Please file a new bug. If you run "ubuntu-bug cups-browsed" to start
writing your report, it'll automatically include some relevant
diagnostics. If there are any relevant log messages in the journal, that
would be useful too.
Marking a bug as duplicate is very easy to do. Untangling two problems
@Raffaele: I'm not saying that there isn't a problem: rather that the
cause is probably different to the one from this closed bug, even if the
symptom is the same.
You'd be better off reporting a new bug, or looking through the open bug
reports to see if any of those match what you're seeing.
--
Note that the problem this bug was opened to address was fixed in an
update to 23.04.
If you are seeing a problem on 24.04, it is most likely a different
issue (possibly bug 2049315). Comments on long closed bug reports are
likely to be missed.
--
You received this bug notification because you
*** 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 Ubuntu
Bugs, which
> 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:
** Changed in: ubiquity (Ubuntu Jammy)
Milestone: None => ubuntu-22.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965805
Title:
Ubiquity failure - Error while installing packages
I just tried installing a system using the 20220324.3 daily image (which
includes the new snapd). The installation completed successfully, and
the /usr/bin/snap panic I'd previously observed when run under "sudo
chroot /target" was now gone.
** Changed in: ubiquity (Ubuntu Jammy)
Status:
Looking further, it seems this is a problem that has already been fixed
in snapd:
https://github.com/snapcore/snapd/pull/11275
The change was included in snapd 2.55. The ENOENT check is not present
in 2.54.4, as is being used in the installer environment:
I tried to do a clean install in a VM with the current daily install
media and managed to reproduce the problem.
The Firefox preinst script was stuck in its loop calling "snap info
firefox", so I opened a shell with "sudo chroot /proc/$pid/root" and ran
the same command. That led to a panic that
> 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 Ubuntu
Bugs,
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
getent isn't the problem here: it is just returning whatever data the
nameservice switch provides.
The underlying cause is that libnss-extrausers ignores entries in the
extrausers database that have a uid or gid less than 500:
https://git.launchpad.net/ubuntu/+source/libnss-
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
This looks like a good candidate for the "desktop" interface. Security
is significantly better than the traditional IBus communication method,
since access to IBusContexts are restricted to their owner:
https://github.com/ibus/ibus/blob/master/portal/portal.c#L354-L370
... and IBusContext
Public bug reported:
This is something we might want to fix to help people who build snaps
based on Focal's Qt.
The QGenericUnixServices implementation of openUrl() passes an O_PATH
file descriptor to xdg-desktop-portal when it detects it is running
under snap confinement. This is rejected
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867080
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
I detailed the configuration file workaround here:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1856428/comments/2
I wonder if the underlying cause of the problem is that Bionic's Mumble
is compiled against Qt 4, which predates the newer TLS versions. I
would have thought it'd get new
For anyone who finds this bug, and wonders about the "Users can override
this behaviour with a config file" part, here's what I did to get an
OpenSSL-using application to talk to an old server that only supported
TLSv1 (in my case, an old Mumble server):
1. create an "openssl.cnf" file somewhere
Sure. But if this is controllable from a configuration file, then it
might be possible to come up with a temporary work around until the
server you want to connect to is upgraded. With any luck, the
configuration can be changed in such a way that only Mumble is affected.
--
You received this
This is likely caused by bug 1856428, which indicates that support for
the older TLS versions can be enabled in a configuration file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861791
Title:
I encountered this today too. This seems to be an OpenSSL problem,
given that "openssl s_client" refuses to connect to the server, where it
succeeds with older releases. Presumably the server only supports
ciphers or TLS versions the new OpenSSL rejects.
--
You received this bug notification
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 Ubuntu
Bugs, 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
I've put together a PR to set XDG_DATA_DIRS via environment.d, as was
done for PATH:
https://github.com/snapcore/snapd/pull/6813
When this is merged and released, it should remove the need for any
special user configuration.
--
You received this bug notification because you are a member of
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 Ubuntu
Bugs, which is subscribed
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
The patch was accepted upstream as is, so we can backport it:
https://github.com/flatpak/xdg-desktop-
portal/commit/1737e30f5115fea144ab5e3f5f455e40d43dc974
While chatting on IRC, Alex suggested the following set of crash fixes
for the xdg-document-portal from 1.0.3 that we may want to consider
I've submitted a patch upstream here:
https://github.com/flatpak/xdg-desktop-portal/pull/236
I'll give them a chance to respond and then look at putting together an
update to our package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So judging by the logs in some of the related error reports, we get the
following log messages:
xdg-desktop-por[3113]: Failed to create file chooser proxy: Error calling
StartServiceByName for org.freedesktop.impl.portal.desktop.gtk: Timeout was
reached
xdg-desktop-por[3113]:
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
This appears to be referring to the "onedrive" package in current
versions of Ubuntu, rather than the discontinued Ubuntu Phone "storage-
provider-onedrive" package.
** Project changed: storage-provider-onedrive => onedrive (Ubuntu)
--
You received this bug notification because you are a member
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787324
Title:
Snap policy module
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774560
Title:
xdg-desktop-portal-gtk malfunctions on
Public bug reported:
When running on a Wayland session, if xdg-desktop-portal-gtk is asked to
display a window on behalf of a Wayland app, it gets disconnected from
gnome-shell with one of these messages:
Gdk-Message: 09:49:31.837: Lost connection to Wayland compositor.
Gdk-Message:
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724316
Title:
"Sorry, something went wrong cannot authenticate to snap store ..."
Discussion started here:
https://forum.snapcraft.io/t/handling-invalid-credentials/2526
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724316
Title:
"Sorry, something went wrong cannot
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720331
** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie continually relaunching
To manage
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie continually relaunching
To manage notifications about
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie continually relaunching
To manage
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698035
Title:
gnome-control-center lacks any replacement for
ged in: snapd (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581713
Title:
Ubuntu Software always asks for an Ubuntu Single Sign-On a
** 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
With Chris's help we got the tests to get past the D-Bus errors on Zesty
by creating a file /etc/polkit-1/localauthority/50-local.d/manage-
units.pkla on the test system with the following contents:
# Allow the "ubuntu" user to manage systemd units unconditionally
for testing
[Allow
Anastasia asked me to take a look at this. I'm still not sure what the
underlying cause is, but here is some of what I've discovered so far.
1. There has been a change in policykit-1 that sounds like it might be
relevant. Namely:
[ Martin Pitt ]
* Use PAM's common-session-noninteractive
Public bug reported:
[this is in conjunction with python-fastimport 0.9.6-2]
While trying to use "bzr fast-export" on some of my branches, I ran
into a few unicode related problems:
1. it seems python-fastimport expects the user's name/email to be in
Unicode now.
2. python-fastimport expects
Public bug reported:
If I run the keeper command line client with no arguments, it prints a
debug message and then sits sits hangs seemingly doing nothing:
$ /usr/lib/x86_64-linux-gnu/keeper/keeper
[debug] More or none arguments (src/cli/command-line.cpp:98)
I assume the tool is
Public bug reported:
When I was running through the storage-provider-webdav test plan, I had
the backup stall due to bug 1676361. I tried using ctrl+C to kill the
client, but it just kept on running.
It also seems to ignore SIGTERM, so I could only kill it with SIGKILL or
ctrl+\.
** Affects:
** Description changed:
While running through the test plan for storage-framework, I had keeper-
service segfault inside libubuntu-app-launch
I suspect that this is related to the recent ubuntu-app-launch 0.11
landing, which says it removes upstart and click support.
Attached is a
Public bug reported:
While running through the test plan for storage-framework, I had keeper-
service segfault inside libubuntu-app-launch
I suspect that this is related to the recent ubuntu-app-launch 0.11
landing, which says it removes upstart and click support.
Attached is a backtrace I
** Changed in: storage-framework (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604640
Title:
provider-test dumps core if second instance is
** Changed in: storage-framework (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668872
Title:
provider::Item should have its own header file
To
1 - 100 of 660 matches
Mail list logo
