Public bug reported:
First seen in the autopkgtest:
https://autopkgtest.ubuntu.com/packages/g/gtk4/noble/s390x
mesa 25.0.7-0ubuntu0.24.04.1 regresses the autopkgtest of gtk4
4.14.5+ds-0ubuntu0.1 on s390x.
42515s build-x11PASS (superficial)
42515s build-waylandFAIL timed out
I was unable to reproduce this error.
Can you describe what happened before this happened?
Also, would you please try:
python3 -c 'import logging'
** Changed in: glib2.0 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop
Enabling the face recognition feature depends on the opencv pacakage
which is currently not in Ubuntu main. The are no plans to change this
soon.
** Changed in: shotwell (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Deskt
I tried in a PPA with -proposed enabled and saw the following:
native | [module-protocol-: 812 socket_data()] server 0x2aa4079b340: failed to
accept: Invalid argument
[E][02151.048565] mod.protocol-native | [module-protocol-: 812 socket_data()]
server 0x2aa4079b910: failed to accept: Invalid arg
Public bug reported:
Seen in the test rebuild with coreutils-from 0.0.0~ubuntu8
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250530-questing-coreutils-questing.html
but not in the reference rebuild
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250530-questin
Public bug reported:
Seen in the test rebuild with coreutils-from 0.0.0~ubuntu8
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250530-questing-coreutils-questing.html
but not in the reference rebuild
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250530-questin
FTBFS report of amd64 packages in questing -release with coreutils-from
0.0.0~ubuntu8:
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250530-questing-coreutils-questing.html
FTBFS report of amd64 packages in questing -release:
https://people.canonical.com/~ginggs/ftbfs-report/te
mutter 48.1-1ubuntu4 has failed multiple times with no log against
coreutils-from 0.0.0~ubuntu8.
It built successfully on first attempt in questing -release.
I'm not sure if this link is helpful:
https://launchpad.net/ubuntu/+archive/test-rebuild-20250530-questing-
coreutils/+build/30875360
**
** Changed in: coreutils-from (Ubuntu)
Status: Fix Released => New
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.laun
** Tags added: root-on-zfs
--
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/2083686
Title:
On ZFS rpool and bpool stays visible on dash
To manage notifications about this bug go to:
** Bug watch added: Debian Bug tracker #1087052
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087052
** Also affects: rhythmbox-plugin-alternative-toolbar (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087052
Importance: Unknown
Status: Unknown
--
You receiv
The wsdd MIR is LP: #2070025
--
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/2081735
Title:
[FFE] Enable wsdd backend by default
To manage notifications about this bug go to:
https://
At the time of writing, the wsdd MIR is still 'In Progress' and wsdd is
still in Universe. This needs to be resolved before release.
As far as adding wsdd as a Recommended dependency goes, FFe granted,
please go ahead.
** Changed in: gvfs (Ubuntu)
Status: New => Triaged
--
You received
Thanks Jeremy, it's fine to add those packages to this bug and consider
them covered by this exception.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/2061090
Title:
[FFe] add li
FFe granted, please go ahead
** Changed in: file-roller (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/2059335
Title:
FFe: Sync file-rol
Uploaded as 42.3-0ubuntu3.1, because we can re-use version numbers that
never make it into the archive.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hype
** Changed in: evince (Ubuntu Jammy)
Assignee: (unassigned) => Graham Inggs (ginggs)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink i
** Also affects: gnome-shell (Ubuntu Mantic)
Importance: High
Status: Triaged
** Also affects: gnome-themes-extra (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: yaru-theme (Ubuntu Mantic)
Importance: Undecided
Status: Won't Fix
** Also affect
** Also affects: xdg-desktop-portal (Ubuntu Mantic)
Importance: High
Status: Triaged
** Also affects: xdg-desktop-portal-gnome (Ubuntu Mantic)
Importance: High
Status: Triaged
** Also affects: xdg-desktop-portal (Ubuntu Lunar)
Importance: Undecided
Status: New
** Al
** Also affects: gtk4 (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: libadwaita-1 (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: gtk4 (Ubuntu Mantic)
Importance: Critical
Status: Triaged
** Also affects: libadwaita-1 (Ubuntu Man
Is there any update on this particular issue?
Rocky and RedHat version 8 systems can successfully use PIV
authentication in conjunction with SSSD and can be used on Government
systems. Ubuntu can not as of now.
Jim Graham
--
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #1031524
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031524
** Also affects: fuse3 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031524
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #10313
There may be more detail with these two bug reports:
The issue is the upstream changes for the screen auto-rotation impacts the
touchpad on majority of 2-in-1 laptops.
See https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1846 and
https://gitlab.gnome.org/GNOME/mutter/-/issues/1686#note_1271
I have a Lenovo Yoga 7 Gen7 (14ial7) 12thGen Intel CPU and I am having
the exact same issue. Monitor-sensor reports everything is correct and
yet the rotation doesn't work under Wayland but it does with X.
Only adding a comment here are this is another model number of a 2-in-1
exhibiting this iss
I've just upgraded a machine from focal to jammy and been hit by this
issue. The workaround provided by wastrel doesn't seem to resolve the
issue.
I'm using a Yubikey 5 Nano - which appears to be the device being
identified as a smart card. When removing the Yubikey the auth process
runs normally.
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https://bugs.launchpad.net/bugs/1975724
Title:
Dock right click me
I've installed Evolution 3.44.1-0ubuntu1 from the proposed updates and
text now displays background as expected. This is resolved for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/
Hi,
Sure, the output is as follows:
gsettings get org.gnome.desktop.interface gtk-theme
'Yaru-blue-dark'
gsettings get org.gnome.desktop.interface color-scheme
'prefer-dark'
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in
One quick question.
On 21.10 the preview rendered with a white background even when using a dark
theme.
Please see the attached.
And thanks for looking at this bug/question. I appreciate it. :)
G.
** Attachment added: "White background previously with 21.10"
https://bugs.launchpad.net/ubu
Public bug reported:
When using a dark theme in Jammy (22.04) beta, Evolution will display a
dark background with black text for HTML emails in the message preview.
Previously in Impish, the background was white with dark text.
This only occurs when using a dark theme, If you use a light theme, t
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10 as su
** Changed in: pytest-twisted (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with pyt
python-b2sdk was removed from jammy in LP: #1961976
** Changed in: python-b2sdk (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
pytest-twisted's autopkgtests pass with twisted 22.1.0
** Changed in: pytest-twisted (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/19
** Changed in: ipywidgets (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3
** Changed in: ipywidgets (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10 as su
** Changed in: vorta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10 as supporte
** Changed in: python-hypothesis (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10
** Changed in: supysonic (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10 as supp
Fixed in python-taskflow 4.6.3-0ubuntu1 and pygobject/3.42.0-3.
** Changed in: python-taskflow (Ubuntu)
Status: New => Fix Released
** Changed in: pygobject (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
migration-reference/0 tests for all affected packages triggered
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10 as supported
** Tags added: fr-1927
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10 as supported
To manage notifications about this bug
skimage/s390x was OOM, added to big_packages
** Changed in: skimage (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgt
** Description changed:
This bug is for tracking the packages having autopkgtest regressions
with python3.10 as a supported version, blocking migration of
python3-defaults/3.9.7-4.
+
+ All packages are in universe except pygobject and python-taskflow in
+ main.
+
+ All packages have RC bug
Public bug reported:
This bug is for tracking the packages having autopkgtest regressions
with python3.10 as a supported version, blocking migration of
python3-defaults/3.9.7-4.
All packages are in universe except pygobject and python-taskflow in
main.
All packages have RC bugs in Debian except
** Also affects: xorgxrdp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xrdp in Ubuntu.
https://bugs.launchpad.net/bugs/1931225
Title:
0.9.15 is FTFBS on ppc64el and s390x
To m
Public bug reported:
Fuse3 is a requirement for qemu 6 (LP: #1934510). Since we don't want
to support two versions of fuse in main, we'd like reverse-dependencies
of fuse to switch to fuse3.
xdg-desktop-portal FTBFS in a test rebuild changing the build-dependency
on libfuse-dev to libfuse3-dev.
Public bug reported:
There were three updates over the last two days. with poppler
(0.41.0-0ubuntu1.16) I find xpdf (3.04-1-ubuntu1.1) crashes on startup,
on any file, every time. The version 0.41.0-0ubuntu1.13 worked
correctly. I'm not sure about the ones in between.
Perhaps this is a classic
Public bug reported:
When the screen is locked, you can freeze the screensaver application by
holding escape and scrolling up to activate the unlock screen with the
mouse. 'authentication error' pops up and the password input {widget?}
is non-responsive.
this isn't likely to pose a problem, but
I've just set up a brand new workstation with Ubuntu Desktop 20.04, and
it does not seem to be affected. It has been sitting at the login
screen for 8 hours and has not suspended.
Is it possible that only upgrades could be affected by this?
--
You received this bug notification because you are
@vanvugt: Thanks, 'sudo systemctl isolate multi-user.target' does
prevent the autosuspend.
Although it doesn't survive a reboot, so maybe if one needs something
more persistent:
sudo systemctl set-default multi-user.target
--
You received this bug notification because you are a member of Ubun
@vanvugt: Enabling automatic login might do the trick, thanks.
Ideally, I'd like to figure out exactly which setting needs to be changed.
I'll poke some more.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
@seb128: As you wrote in LP: #1868260, having autosuspend on AC by
default is not a great user experience.
It's frustrating for those who want to leave their workstations running
and access them remotely during lockdown.
--
You received this bug notification because you are a member of Ubuntu
De
@marcustomlinson: Thanks, that seemed to copy over the settings, but that
didn't help.
I guess then this is not quite the same as LP: #1759325, although the behaviour
is similar.
I've also tried the following, to no avail:
sudo -u gdm dbus-launch gsettings set org.gnome.desktop.screensaver
loc
Public bug reported:
Same as LP: #1759325 in Bionic, but this time affecting Focal.
After some update in the last month, my desktop PC now suspends after 20
minutes at the login screen.
I was able to override the setting for my user account by adjusting the
power settings in gnome-control-center
I have a desktop machine running Ubuntu 20.04 Beta and it suspends when left at
the login screen.
As in LP: #1759325 , I'm able to adjust the settings for the logged in user,
but not for the system.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
If it's any bit of helpful information, I occasionally have this issue
(on 18.04) and it is fixed by a proper shutdown and boot. It seems to
happen for me when one of the servers that I sshfs to crashes/becomes
unavailable (or something else server side) and the issue persists past
the time in whic
Ergh, you're right. It is the other guy in the Gnome thread using 3.34,
not me. I should have checked my own version rather than running with
what was said in there.
I've now mentioned this on the Gnome issue tracker thread.
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
On reporting an issue in gnome-calendar, I was told "GNOME Calendar 3.34
requires EDS 3.34 running in the host system.". Ubuntu has 3.32.
See:
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/464#note_617797
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-c
I can't reproduce anymore either :(. I wish I kept a record of the exact
error message. I just grepped through so many packages to try and source
the error and couldn't find anything.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gno
Thanks for bringing up the Discourse site. I actually have a lot more I
want to talk about that is general and this seems to be the perfect
place.
I really want to contribute there but I don't seem to have posting
permission on the Discourse. Username chrisgraham.
There's no post topic button for
Public bug reported:
For FAT partitions, labels have to be upper case.
FAT is the default for a new partition, but the default example label is mixed
case.
This means just going on recommendation, it's not going to work out, and the
user will get an error message.
A better user experience woul
I'm on an iMac, so I want to make use of my Retina (hj-dpi) screen,
while also using external screens that are not hi-dpi.
I can confirm no good X11 support for separate dpis per screen. I was
able to mess around with xrandr, but I got ghosting on my mouse cursor
that I could not resolve. Possibly
This bug still affects Shotwell, and it's a major pain. It's now over 7 years
since the bug was confirmed: I am using Shtowell 0.30.2, and it will still not
import .RW2 files. There seems
to be no action on this.
--
You received this bug notification because you are a member of Ubuntu
Desktop B
*** This bug is a duplicate of bug 1740106 ***
https://bugs.launchpad.net/bugs/1740106
** This bug has been marked a duplicate of bug 1740106
Gnome terminal not starting, timeout reached (bionic)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1792843/+attachment/5189875/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
So yesterday I got the prompt to upgrade my 16LTS system to 18. This
caused a number of issues, but the most frustrating issue out of many
has to be this one.
After a period of inact
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1792843/+attachment/5189876/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
Note: for now I have worked around this by preventing my console from
being locked when the display sleep kicks in. Not ideal but at least I
don't have to reboot after every sleep.
Also, probably not relevant, but this was happening before I switched to
bionic app sources (which I needed for some
** Description changed:
- So yesterday I got the prompt to upgrade my 16LTS system to 18. Man am I
- sorry I went ahead with this; I am in a world of hurt. But the most
- frustrating issue out of many has to be this one.
+ So yesterday I got the prompt to upgrade my 16LTS system to 18. This
+ caus
A bit more about this - if I wait a while the keyboard does seem to come
back but the problem is still there - my password is not accepted and
then the keyboard does nothing for a while.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
So yesterday I got the prompt to upgrade my 16LTS system to 18. Man am I
sorry I went ahead with this; I am in a world of hurt. But the most
frustrating issue out of many has to be this one.
After a period of inactivity, the lock screen kicks in. When I then try
to log in, us
** Bug watch added: KDE Bug Tracking System #392447
https://bugs.kde.org/show_bug.cgi?id=392447
** Also affects: nautilus via
https://bugs.kde.org/show_bug.cgi?id=392447
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
D
Public bug reported:
Expected behaviour:
1 Delete item
2 Navigate to Rubbish Bin
3 Previous item can be viewed and restored
Actual Behaviour:
1 Delete item
2 Navigate to Rubbish Bin
3 Rubbish Bin is empty
3 Navigate to .Trash-1000 folder deleted item is present
ProblemType: Bug
DistroRelease: Ub
Public bug reported:
After upgrading a fresh install of 16.04 to 18.04, my desktop PC now
suspends after 20 minutes at the login screen.
This change in default probably comes from this commit:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa
The behaviour also changed for my
I'm on Ubuntu 16.04.1 (Gnome) and experienced this problem. Solved with:
sudo apt-get upgrade gnome-software
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1647187
Title:
** Changed in: wine (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1665573
Title:
package libwine-dev (not installed) failed to instal
Public bug reported:
I have found that kswapd0 is running at 100%. If i run ' echo 3 >
/proc/sys/vm/drop_caches' the transfer of data improves but not to initial
levels. If that is not done more than a few times the system eventually grinds
to a halt and reboot is required. The file transfer
What needs to be done in wine?
** Changed in: wine (Ubuntu)
Status: New => Incomplete
--
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/883138
Title:
Dim file extensions
To
** Package changed: nlpsolver (Ubuntu) => gnome-terminal (Ubuntu)
** Changed in: gnome-terminal (Ubuntu)
Status: New => Incomplete
--
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
What metadata is it missing?
Does is it not appear in GNOME/Ubuntu Software because it is i386-only?
I'm using an amd64 system and PCSX2 does not appear if it is not already
installed.
** Also affects: gnome-software (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
@caf4926: this should be fixed in trusty (and mint 17).
Please check if these packages installed.
apt-cache policy p11-kit-modules:i386
apt-cache policy libp11-kit-gnome-keyring:i386
If not, install them.
sudo apt-get install p11-kit-modules:i386 libp11-kit-gnome-keyring:i386
--
You received t
Fix released in ufraw 0.20-1.
** Bug watch added: Debian Bug tracker #757823
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757823
** Also affects: ufraw (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757823
Importance: Unknown
Status: Unknown
** Changed in: ufra
Public bug reported:
Have an account with no password set. When computer resumes from suspend
state, where user with no pasword is logged in, system now request
password and will not unlock screen.
Expected action is to automatically unlock screen without asking for a
password.
Workaround is to
Still having this problem.
$ uname -a
Linux foo 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
--
You received this bug n
This was marked as a duplicate of Bug #1261060, but is still present in
3.8.6-0ubuntu9.1 in which that bug was supposedly fixed.
** This bug is no longer a duplicate of bug 1261060
sometime empathy chat dialogs open empty/with a negative unread count
--
You received this bug notification beca
** This bug is no longer a duplicate of bug 1261060
sometime empathy chat dialogs open empty/with a negative unread count
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1195276
Ti
@peter.waller: see mterry's comment 80 in LP: #859600
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094319
Title:
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkc
I ran 'wine notepad' and saw the following:
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-
keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-
pkcs11.so: cannot open shared object file: No such file or directory
I installed gnome-keyring and libp11-kit-gnome-key
@mterry: thanks for the fixes and the upload.
I can update my patch for precise, but as it stands, it also converts gcr,
which was split out of gnome-keyring into its own package in quantal, to
multiarch.
Before we can convert gnome-keyring (including gcr) to multiarch in precise, we
would firs
I ran 'wine notepad' and saw the following:
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-
keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-
pkcs11.so: cannot open shared object file: No such file or directory
I installed gnome-keyring and libp11-kit-gnome-key
Marking 'new' in Quantal and Precise.
** Changed in: gnome-keyring (Ubuntu Precise)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Tit
This patch for Precise includes the same changes as in the Quantal patch
above, and includes the multi-arch changes in the gcr package from Saucy
( see LP: #859600).
** Patch added: "gnome-keyring-gcr-multiarch-precise.debdiff"
https://bugs.launchpad.net/debian/+source/gnome-keyring/+bug/8596
This is Rodney's Quantal patch from comment #41 with the following changes:
The gnome-keyring package depends on libp11-kit-gnome-keyring instead of
recommends.
The libp11-kit-gnome-keyring package now breaks and replaces gnome-keying (<<
${binary:Version}).
I believe this needs to be fixed in Q
** Description changed:
+ [SRU] The debiffs attached to comments #4 and #5 backport the multi-arch
+ changes from Saucy to Raring and Quantal respectively. See LP: #859600
+ for the Precise version.
+
+ [IMPACT]
+ libgcr-3-1:i386 and libgck-1-0:i386 are not installable on an x86_64 system.
+
+
** Patch added: "gcr-multiarch-quantal.debdiff"
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/998715/+attachment/3726930/+files/gcr-multiarch-quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
** Patch added: "gcr-multiarch-raring.debdiff"
https://bugs.launchpad.net/ubuntu/precise/+source/gnome-keyring/+bug/998715/+attachment/3726928/+files/gcr-multiarch-raring.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnom
** Bug watch added: Debian Bug tracker #692743
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692743
** Also affects: gcr (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692743
Importance: Unknown
Status: Unknown
--
You received this bug notification because you a
I will be able to work on this and gcr again in a couple of days' time.
Hopefully early next week I'll attach debdiffs.
In the meantime, you are welcome to test gnome-keyring from my PPA.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
1 - 100 of 256 matches
Mail list logo
