** 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
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
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
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
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
** 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
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
** 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
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
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,
** 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
** 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: 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: 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: 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
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
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
** 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
** 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
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.
** 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
*** 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
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:
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
@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
@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
@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
@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
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
** 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
** 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
** 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: 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
** 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 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
** 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
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:
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
@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
@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
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
I still see this on a local ext3 filesystem in Intrepid.
--
[intrepid] incorrect date&time on copy - remote filesystems
https://bugs.launchpad.net/bugs/319063
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing lis
*** This bug is a duplicate of bug 319063 ***
https://bugs.launchpad.net/bugs/319063
I still see this on a local ext3 filesystem in Intrepid.
--
Nautilus STILL not preserving timestamps
https://bugs.launchpad.net/bugs/315552
You received this bug notification because you are a member of Ubun
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
** Also affects: gcr (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcr (Ubuntu)
Status: New => Confirmed
--
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/
** Summary changed:
- Unable to install libgck-1-0:i386 on amd64
+ Please transition gcr to multi-arch
--
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/998715
Title:
Please tr
Fix released in Saucy (LP: #1191987).
** Changed in: gcr (Ubuntu)
Status: Confirmed => Fix Released
--
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/998715
Title:
Pleas
@eraserix: gnome-keyring is marked Multi-Arch: foreign so that, for
example, an amd64 gnome-keyring can satisfy an i386 package's dependency
on it.
The version numbers in Breaks and Replaces look wrong to me too.
As jhansonxi wrote in comment 48, libp11-kit-gnome-keyring:i386 won't be
installable
I also had a go at this today. :)
I built a gnome-keyring package for Precise in my PPA:
https://launchpad.net/~ginggs/+archive/sru
It is adam-stokes' last attempt plus the following changes:
- Change gnome-keyring's Recommends on libp11-kit-gnome-keyring
to Depends.
- Change libp11
@eraserix: as for how is the new libp11-kit-gnome-keyring supposed to find it's
way
to the affected users?
Both wine and cups got updates in Raring to Recommends and Depends the
new libp11-kit-gnome-keyring respectively:
wine1.4 (1.4.1-0ubuntu5) raring; urgency=low
* Add new libp11-kit-gnome-
For the gnome-keyring package to be considered multi-arch in Precise, surely
libgck and libgcr need to be multi-arch as well?
Then we can close LP: #998715 for Precise in this SRU.
My other concern is what will happen when someone picks up
libp11-kit-gnome-keyring in Precise and then upgrades to
I've built another gnome-keyring package for Precise in my PPA that I
hope fixes all three issues (multi-arch gnome-keyring, multi-arch gcr
and split libp11-kit-gnome-keyring).
The test case (on an x86_64 system) would be something like:
$ wine notepad
You should see the error message:
p11-kit: c
** Changed in: gnome-keyring (Ubuntu Quantal)
Status: New => Invalid
** Changed in: gnome-keyring (Ubuntu Raring)
Status: New => Invalid
** Changed in: gnome-keyring (Ubuntu Saucy)
Status: Confirmed => Invalid
** Changed in: gcr (Ubuntu Precise)
Status: New => Invalid
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
** 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
** 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
** 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
** 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.
+
+
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
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
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
** Bug watch added: GNOME Bug Tracker #640475
https://bugzilla.gnome.org/show_bug.cgi?id=640475
** Changed in: gnome-control-center
Importance: Medium => Unknown
** Changed in: gnome-control-center
Status: Invalid => Unknown
** Changed in: gnome-control-center
Remote watch: GNOME B
Public bug reported:
Binary package hint: nautilus
In Ubuntu 10.04, renaming a file would start with just the file name
highlighted, not the file extension.
In Ubuntu 10.10 and 11.04, the entire file name including the extension is
highlighted so pressing any key loses the file extension.
This
@gluxon: Where does one find the "Customize Toolbars" window?
--
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/508632
Title:
[FFe] Toggle button for Nautilus location field gone
--
I've always used RightAlt+PrtScr in Ubuntu and Windows to take a
snapshot of the active window.
I'm still using Lucid (partly because of this bug as I often take
snapshots for instructional purposes) and both LeftAlt+PrtScr and
RightAlt+PrtScr take snapshot the active window.
On 24 February 2011
> Miroslav:
> Do you have laptop or desktop?
I'm using a desktop.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
https://bugs.launchpad.net/bugs/642792
Title:
ALT+PrtSc not recognised: breaks built-in screensho
Go to Help / About in Nautilus to bring up the Desktop User Guide then
navigate to Working with Files / Browser Mode / Using the Location Bar,
in the section that describes the Text Location Bar the following text
is still there:
"To always use the text location bar, click on the toggle button at
Description:Ubuntu intrepid (development branch)
Release:8.10
--
gvfsd-computer crashed with SIGSEGV in g_main_context_prepare()
https://bugs.launchpad.net/bugs/185774
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
des
I was getting this error after upgrading from Hardy x86_64 to Intrepid
Alpha 4. I've just upgraded to Intrepid Alpha 6 and am still getting
the error.
--
gvfsd-trash crashed with SIGSEGV in g_idle_funcs()
https://bugs.launchpad.net/bugs/251910
You received this bug notification because you are a
I've been getting this error since upgrading from intrepid alpha 4 to alpha 6.
sudo chmod 775 /etc/gconf/gconf.xml.system solved it, thanks Sebastien!
--
There is a problem with the configuration server.
(/usr/lib/libgconf2-4/gconf-sanity-check-2 exited with status 256)
https://bugs.launchpad.ne
After following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash, I am unable to find the
gnome-network-admin-dbgsym package. Is this required to produce a
backtrace?
--
network-admin crashed with SIGSEGV in g_utf8_validate()
https://bugs.launchpad.net/bugs/279308
You received th
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
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://
75 matches
Mail list logo
