[Desktop-packages] [Bug 2065432] Re: Unable to authenticate with smartcard: gnome-shell throws on unhandled promise rejection
Hi, There was already a SRU upload for noble --- gnome-shell (46.0-0ubuntu6~24.04.5) noble; urgency=medium * Add shell-app-Warn-instead-of-crashing-if-disposed-before-sta.patch to avoid crashing the shell if an app misbehaves coincidentally close to a garbage collection run (LP: #2037055) -- Daniel van Vugt Fri, 13 Sep 2024 17:09:18 +0800 --- I apologise for imposing extra work, but would it be possible to rebase the patch on the latest upload? Please resubscribe Sponsors once the patch is ready. Best Regards, Vladimir. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2065432 Title: Unable to authenticate with smartcard: gnome-shell throws on unhandled promise rejection Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Noble: In Progress Bug description: [Impact] * Starting from gnome-shell version 46.0, which is available in noble, logging in to the Ubuntu system with smart card does not work. * Only workaround is to downgrade gnome-shell to a version 45.0 * Login problem is caused by two seperate issues, one caused by the bug in the upstream [1], second is related to ubuntu specific code added as part of patch: gdm-util-Figure-out-default-service-from-service-definiti.patch * Upstream issue has been alraedy fixed with [2], issue was caused by feature which was checking conflicting sessions during login. * To fix login problem, upstream patch needs to be backported as well as ubuntu specific code fixed [Test Plan] * To reproduce an issue, smart card (with at least self signed certificate) is required. * The simplest steps to reproduce the problem: 1. Create user "test" 2. Configure sssd.conf: root@rmalz:/etc/sssd# cat sssd.conf [sssd] services = pam enable_files_domain = True certificate_verification = no_verification [certmap/implicit_files/test] matchrule = .* [pam] pam_cert_auth = True 3. Enable smart card login: pam-auth-update --disable sss-smart-card-required --enable sss-smart-card-optional * With these settings, login "test" user. Two problems will occurr. First, gnome-shell will not prompt for a smart card PIN and will continue to ask for password. This is caused by incorrect detection of default auth service, issue introduced with: gdm-util-Figure-out-default-service-from-service-definiti.patch Second, if first problem is fixed, login screen will freeze. This issue is caused by upstream bug [1]. [Where problems could occur] * Upstream patch is changing behavior of finding conflicting sessions, possible risk of regression for non smart card cases * There is additional patch [3], introduced as part of fix for [1]. It seems that this patch is fixing presentation issue which is different from initial login problem and no part of this SRU. * Patches for both [2] and gdm-util-Figure-out-default-service-from-service-definiti.patch have been tested locally, allowing to login without issues. [Other Info] * Links: [1] - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7526 [2] - https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3448/diffs?commit_id=e5d9a0fec869adbe610c46114afaede04f8c89e2 [3] - https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3448/diffs?commit_id=647747fbd6afef2f9f939682ab6527f3877ffbfb * Original case description: Upstream report: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7526 Opening as part of response to support ticket. After boot, GDM does not prompt for smartcard authentication correctly. It is possible to strike Esc and get GDM to prompt for a username and a smartcard PIN from the initial locked-out state, but this does not start a new desktop session and instead hangs. Striking Esc allows for the login to be attempted again, but with the same results. Syslog entries include unhandled promise rejections from the onSessionOpened event in loginDialog, and perhaps more importantly also from the user verification stack that is used to create the initial authentication options prompt (stack traces of the syslog entries attached). Affects GDM 46.0-2ubuntu1 in Noble. To reproduce, configure smartcard auth for a network user on a new Noble install and try to sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2065432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2065432] Re: Unable to authenticate with smartcard: gnome-shell throws on unhandled promise rejection
** Description changed: - [ Impact ] + [Impact] - * Starting from gnome-shell version 46.0, which is available in noble, logging in to the -Ubuntu system with smart card does not work. - - * Only workaround is to downgrade gnome-shell to a version 45.0 + * Starting from gnome-shell version 46.0, which is available in noble, logging in to the + Ubuntu system with smart card does not work. - * Login problem is caused by two seperate issues, one caused by the bug in the upstream [1], -second is related to ubuntu specific code added as part of patch: -gdm-util-Figure-out-default-service-from-service-definiti.patch - - * Upstream issue has been alraedy fixed with [2], issue was caused by feature -which was checking conflicting sessions during login. - - * To fix login problem, upstream patch needs to be backported as well as -ubuntu specific code fixed + * Only workaround is to downgrade gnome-shell to a version 45.0 - [ Test Plan ] + * Login problem is caused by two seperate issues, one caused by the bug in the upstream [1], + second is related to ubuntu specific code added as part of patch: + gdm-util-Figure-out-default-service-from-service-definiti.patch - * To reproduce an issue, smart card (with at least self signed certificate) is required. - - * The simplest steps to reproduce the problem: -1. Create user "test" -2. Configure sssd.conf: - root@rmalz:/etc/sssd# cat sssd.conf - [sssd] - services = pam - enable_files_domain = True - certificate_verification = no_verification + * Upstream issue has been alraedy fixed with [2], issue was caused by feature + which was checking conflicting sessions during login. - [certmap/implicit_files/test] - matchrule = .* + * To fix login problem, upstream patch needs to be backported as well as + ubuntu specific code fixed - [pam] - pam_cert_auth = True -3. Enable smart card login: -pam-auth-update --disable sss-smart-card-required --enable sss-smart-card-optional + [Test Plan] - * With these settings, login "test" user. Two problems will occurr. -First, gnome-shell will not prompt for a smart card PIN and will continue to ask for password. -This is caused by incorrect detection of default auth service, issue introduced with: -gdm-util-Figure-out-default-service-from-service-definiti.patch - -Second, if first problem is fixed, login screen will freeze. This issue is caused by upstream -bug [1]. + * To reproduce an issue, smart card (with at least self signed + certificate) is required. - [ Where problems could occur ] + * The simplest steps to reproduce the problem: + 1. Create user "test" + 2. Configure sssd.conf: + root@rmalz:/etc/sssd# cat sssd.conf + [sssd] + services = pam + enable_files_domain = True + certificate_verification = no_verification - * Upstream patch is changing behavior of finding conflicting sessions, + [certmap/implicit_files/test] + matchrule = .* + + [pam] + pam_cert_auth = True + 3. Enable smart card login: + pam-auth-update --disable sss-smart-card-required --enable sss-smart-card-optional + + * With these settings, login "test" user. Two problems will occurr. + First, gnome-shell will not prompt for a smart card PIN and will continue to ask for password. + This is caused by incorrect detection of default auth service, issue introduced with: + gdm-util-Figure-out-default-service-from-service-definiti.patch + + Second, if first problem is fixed, login screen will freeze. This issue is caused by upstream + bug [1]. + + [Where problems could occur] + + * Upstream patch is changing behavior of finding conflicting sessions, possible risk of regression for non smart card cases - * There is additional patch [3], introduced as part of fix for [1]. It seems that this patch is fixing presentation issue -which is different from initial login problem and no part of this SRU. + * There is additional patch [3], introduced as part of fix for [1]. It seems that this patch is fixing presentation issue + which is different from initial login problem and no part of this SRU. - * Patches for both [2] and gdm-util-Figure-out-default-service-from-service-definiti.patch have been tested locally, allowing -to login without issues. + * Patches for both [2] and gdm-util-Figure-out-default-service-from-service-definiti.patch have been tested locally, allowing + to login without issues. - [ Other Info ] + [Other Info] - * Links: -[1] - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7526 -[2] - https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3448/diffs?commit_id=e5d9a0fec869adbe610c46114afaede04f8c89e2 -[3] - https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3448/diffs?commit_id=647747fbd6afef2f9f939682ab6527f3877ffbfb + * Links: +
[Desktop-packages] [Bug 2076221] Re: [SRU] Add fibocom mbim service to send at command
Hi, I have unsubscribed sponsors as the Impact section of the bug needs an update as requested here[1]. Please resubscribe sponsors once Impact section the bug description is updated. Best Regards, Vladimir. [1] https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2076221/comments/6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2076221 Title: [SRU] Add fibocom mbim service to send at command Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Incomplete Status in libmbim source package in Noble: Fix Released Status in libmbim source package in Oracular: Fix Released Bug description: [ Impact ] * Add fibocom mbim service to libmbim [ Test Plan ] * execute "mbimcli --help-fibocom" can get Fibocom options [ Where problems could occur ] * This SRU is going to add new fibocom command to CLI interface and should not affect other already working commands [Other information] * upstream patch from https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/commit/482fc42a9059d3e7ef7102d850f46155911949ae To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078674] Re: Please merge lp-solve 5.5.2.11-2 (main) from Debian unstable (main)
*** This bug is a duplicate of bug 2078715 *** https://bugs.launchpad.net/bugs/2078715 ** This bug has been marked a duplicate of bug 2078715 [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lp-solve in Ubuntu. https://bugs.launchpad.net/bugs/2078674 Title: Please merge lp-solve 5.5.2.11-2 (main) from Debian unstable (main) Status in lp-solve package in Ubuntu: In Progress Bug description: 08/06/17 version 5.5.2.6 (temp release) - Modified generating MPS file with some new options: - MPSLINDO: Write semi-continious variables in different order as required by LINDO - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format xli_MPS is modified to handle these new options. - Reading an lp file with a semi-cont variable failed if the minimum is larger than the maximum. This is allowed because if the semi-cont attribute on the variables in which case a 0 is also a valid solution. - Some models with degeneraracy returned a "Unacceptable accuracy found" error. 30/07/17 version 5.5.2.7 (temp release) - Lower/Upper objective sensitivity was sometimes not given for some variables. Was ok when scaling was disabled. xx/xx/xx version 5.5.2.8 - Modified PHP driver for PHP 5.4 - In some cases an accuracy error was given by check_solution which was not always true 13/03/20 version 5.5.2.9 - When a model is infeasible it can happen that the returned solution is not initialised and returning NAN values 15/11/20 version 5.5.2.10 - write_MPS doesn't generate an SC BOUND on a variable that is semi-continious and the upper bound is equal to the lower bound. - The VB.NET demo application wasn't adapted yet for 64-bit 29/12/20 version 5.5.2.11 - version 5.5.2.9 introduced a problem for some models. They give infeasible or let even lpsolve crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
** Merge proposal unlinked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/curl/+git/curl/+merge/471101
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
defined
Status in asymptote package in Ubuntu:
Fix Released
Status in biosig package in Ubuntu:
New
Status in curl package in Ubuntu:
Fix Released
Status in deal.ii package in Ubuntu:
New
Status in doxygen package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Triaged
Status in gcl27 package in Ubuntu:
New
Status in graphite2 package in Ubuntu:
Fix Released
Status in gsequencer package in Ubuntu:
Fix Released
Status in gsl package in Ubuntu:
New
Status in haskell-devscripts package in Ubuntu:
Fix Released
Status in jose package in Ubuntu:
New
Status in ksmtuned package in Ubuntu:
Fix Released
Status in libreoffice package in Ubuntu:
Fix Released
Status in libtpms package in Ubuntu:
New
Status in mosh package in Ubuntu:
Fix Released
Status in mpich package in Ubuntu:
New
Status in mwrap package in Ubuntu:
Fix Released
Status in proftpd package in Ubuntu:
New
Status in proftpd-dfsg package in Ubuntu:
Fix Released
Status in quantlib package in Ubuntu:
Fix Released
Status in serf package in Ubuntu:
Fix Released
Status in setserial package in Ubuntu:
Fix Released
Status in speech-dispatcher package in Ubuntu:
New
Status in squid package in Ubuntu:
Fix Released
Status in swtpm package in Ubuntu:
Fix Released
Status in texinfo package in Ubuntu:
Triaged
Status in tix package in Ubuntu:
Fix Released
Bug description:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
(refined in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
metadata.specs` parameter is set but the needed environment variables
are not set. Cases:
1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
rp-pppoe fail to build)
2. autopkgtests
3. debugging a crash of an application build with the -spec parameter
4. People like to iteratively continue building the software in the
build dir while hacking on the package and then have no environment
variable set.
This approach is too fragile. An alternative approach would be to specify the
`--package-metadata` linker flag directly. The problem with that approach is
that the curly brackets and quotation marks need to be escaped. Example
failure: Building dpkg would add this parameter to the LDFLAGS:
```
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
```
The following configure script call (non-relevant parameters deleted):
```
$ gcc
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
/usr/bin/ld: cannot find {type:deb: No such file or directory
/usr/bin/ld: cannot find os:ubuntu: No such file or directory
/usr/bin/ld: cannot find name:dpkg: No such file or directory
/usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
/usr/bin/ld: cannot find architecture:amd64}: No such file or directory
```
Proposed solution: Add support for an `--escaped-package-metadata` parameter
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
```
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
```
Solution (see comment #31)
==
dpkg 1.22.11ubuntu1 stops passing the --specs option. It will be
replaced by
- dpkg-buildpackage setting ELF_PACKAGE_METADATA in the environment,
which gets picked up GCC and clang, and added as a linker option.
- the linkers ld.bfd, gold, mold and lld picking up ELF_PACKAGE_METADATA
if they don't see a package-metadata option.
This is committed, and will be uploaded later.
- dpkg-buildflags passing an option --encoded-package-metadata, which
can be safely passed.
This option has to go upstream first into the linkers, so that we
don't have API incompatible linker versions in the archive.
If the fix for the other packages in this report is the only Ubuntu delta,
it can be safely dropped.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
** Merge proposal unlinked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/curl/+git/curl/+merge/471101
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
defined
Status in asymptote package in Ubuntu:
Fix Released
Status in biosig package in Ubuntu:
New
Status in curl package in Ubuntu:
Fix Released
Status in deal.ii package in Ubuntu:
New
Status in doxygen package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Triaged
Status in gcl27 package in Ubuntu:
New
Status in graphite2 package in Ubuntu:
Fix Released
Status in gsequencer package in Ubuntu:
Fix Released
Status in gsl package in Ubuntu:
New
Status in haskell-devscripts package in Ubuntu:
Fix Released
Status in jose package in Ubuntu:
New
Status in ksmtuned package in Ubuntu:
Fix Released
Status in libreoffice package in Ubuntu:
Fix Released
Status in libtpms package in Ubuntu:
New
Status in mosh package in Ubuntu:
Fix Released
Status in mpich package in Ubuntu:
New
Status in mwrap package in Ubuntu:
Fix Released
Status in proftpd package in Ubuntu:
New
Status in proftpd-dfsg package in Ubuntu:
Fix Released
Status in quantlib package in Ubuntu:
Fix Released
Status in serf package in Ubuntu:
Fix Released
Status in setserial package in Ubuntu:
Fix Released
Status in speech-dispatcher package in Ubuntu:
New
Status in squid package in Ubuntu:
Fix Released
Status in swtpm package in Ubuntu:
Fix Released
Status in texinfo package in Ubuntu:
Triaged
Status in tix package in Ubuntu:
Fix Released
Bug description:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
(refined in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
metadata.specs` parameter is set but the needed environment variables
are not set. Cases:
1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
rp-pppoe fail to build)
2. autopkgtests
3. debugging a crash of an application build with the -spec parameter
4. People like to iteratively continue building the software in the
build dir while hacking on the package and then have no environment
variable set.
This approach is too fragile. An alternative approach would be to specify the
`--package-metadata` linker flag directly. The problem with that approach is
that the curly brackets and quotation marks need to be escaped. Example
failure: Building dpkg would add this parameter to the LDFLAGS:
```
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
```
The following configure script call (non-relevant parameters deleted):
```
$ gcc
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
/usr/bin/ld: cannot find {type:deb: No such file or directory
/usr/bin/ld: cannot find os:ubuntu: No such file or directory
/usr/bin/ld: cannot find name:dpkg: No such file or directory
/usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
/usr/bin/ld: cannot find architecture:amd64}: No such file or directory
```
Proposed solution: Add support for an `--escaped-package-metadata` parameter
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
```
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
```
Solution (see comment #31)
==
dpkg 1.22.11ubuntu1 stops passing the --specs option. It will be
replaced by
- dpkg-buildpackage setting ELF_PACKAGE_METADATA in the environment,
which gets picked up GCC and clang, and added as a linker option.
- the linkers ld.bfd, gold, mold and lld picking up ELF_PACKAGE_METADATA
if they don't see a package-metadata option.
This is committed, and will be uploaded later.
- dpkg-buildflags passing an option --encoded-package-metadata, which
can be safely passed.
This option has to go upstream first into the linkers, so that we
don't have API incompatible linker versions in the archive.
If the fix for the other packages in this report is the only Ubuntu delta,
it can be safely dropped.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
** Merge proposal unlinked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/curl/+git/curl/+merge/471100
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
defined
Status in asymptote package in Ubuntu:
Fix Released
Status in biosig package in Ubuntu:
New
Status in curl package in Ubuntu:
Fix Released
Status in deal.ii package in Ubuntu:
New
Status in doxygen package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Triaged
Status in gcl27 package in Ubuntu:
New
Status in graphite2 package in Ubuntu:
Fix Released
Status in gsequencer package in Ubuntu:
Fix Released
Status in gsl package in Ubuntu:
New
Status in haskell-devscripts package in Ubuntu:
Fix Released
Status in jose package in Ubuntu:
New
Status in ksmtuned package in Ubuntu:
Fix Released
Status in libreoffice package in Ubuntu:
Fix Released
Status in libtpms package in Ubuntu:
New
Status in mosh package in Ubuntu:
Fix Released
Status in mpich package in Ubuntu:
New
Status in mwrap package in Ubuntu:
Fix Released
Status in proftpd package in Ubuntu:
New
Status in proftpd-dfsg package in Ubuntu:
Fix Released
Status in quantlib package in Ubuntu:
Fix Released
Status in serf package in Ubuntu:
Fix Released
Status in setserial package in Ubuntu:
Fix Released
Status in speech-dispatcher package in Ubuntu:
New
Status in squid package in Ubuntu:
Fix Released
Status in swtpm package in Ubuntu:
Fix Released
Status in texinfo package in Ubuntu:
Triaged
Status in tix package in Ubuntu:
Fix Released
Bug description:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
(refined in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
metadata.specs` parameter is set but the needed environment variables
are not set. Cases:
1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
rp-pppoe fail to build)
2. autopkgtests
3. debugging a crash of an application build with the -spec parameter
4. People like to iteratively continue building the software in the
build dir while hacking on the package and then have no environment
variable set.
This approach is too fragile. An alternative approach would be to specify the
`--package-metadata` linker flag directly. The problem with that approach is
that the curly brackets and quotation marks need to be escaped. Example
failure: Building dpkg would add this parameter to the LDFLAGS:
```
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
```
The following configure script call (non-relevant parameters deleted):
```
$ gcc
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
/usr/bin/ld: cannot find {type:deb: No such file or directory
/usr/bin/ld: cannot find os:ubuntu: No such file or directory
/usr/bin/ld: cannot find name:dpkg: No such file or directory
/usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
/usr/bin/ld: cannot find architecture:amd64}: No such file or directory
```
Proposed solution: Add support for an `--escaped-package-metadata` parameter
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
```
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
```
Solution (see comment #31)
==
dpkg 1.22.11ubuntu1 stops passing the --specs option. It will be
replaced by
- dpkg-buildpackage setting ELF_PACKAGE_METADATA in the environment,
which gets picked up GCC and clang, and added as a linker option.
- the linkers ld.bfd, gold, mold and lld picking up ELF_PACKAGE_METADATA
if they don't see a package-metadata option.
This is committed, and will be uploaded later.
- dpkg-buildflags passing an option --encoded-package-metadata, which
can be safely passed.
This option has to go upstream first into the linkers, so that we
don't have API incompatible linker versions in the archive.
If the fix for the other packages in this report is the only Ubuntu delta,
it can be safely dropped.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
It seems that the bug is not fixed in the release channel. I am trying to fix lintian warning W: openjdk-22-doc: embedded-javascript-library /usr [usr/share/doc/openjdk-22-jre-headless/api/resource-files/jquery-ui.min.css] But the search bar becomes inactive when I start using symlinks: $snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox - firefox.geckodriver snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-22.10 refresh-date: 3 days ago, at 06:25 NZST channels: latest/stable:128.0.3-1 2024-07-26 (4650) 281MB - latest/candidate: 129.0-1 2024-07-31 (4684) 282MB - latest/beta: 129.0b9-1 2024-07-26 (4659) 282MB - latest/edge: 130.0a1 2024-07-31 (4692) 302MB - esr/stable: 115.13.0esr-3 2024-07-09 (4532) 256MB - esr/candidate:115.14.0esr-1 2024-07-30 (4679) 257MB - esr/beta: ↑ esr/edge: ↑ installed: 128.0.3-1(4650) 281MB - $snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 11 days ago, at 14:15 NZST channels: latest/stable:127.0.6533.72 2024-07-30 (2921) 173MB - latest/candidate: 127.0.6533.88 2024-07-31 (2923) 174MB - latest/beta: 127.0.6533.57 2024-07-23 (2914) 179MB - latest/edge: 129.0.6614.3 2024-07-29 (2920) 181MB - installed: 126.0.6478.182(2910) 171MB - $ ls -alrt /usr/share/doc/openjdk-21-doc/api/script-dir/ total 12 lrwxrwxrwx 1 root root 43 Jul 23 13:34 jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js drwxr-xr-x 64 root root 4096 Aug 1 06:52 .. lrwxrwxrwx 1 root root 48 Aug 1 13:52 jquery-ui.min.js -> /usr/share/javascript/jquery-ui/jquery-ui.min.js lrwxrwxrwx 1 root root 61 Aug 1 13:54 jquery-ui.min.css -> /usr/share/javascript/jquery-ui-themes/base/jquery-ui.min.css drwxr-xr-x 2 root root 4096 Aug 1 13:54 . $ cat /usr/share/doc/openjdk-21-doc/api/script-dir/jquery-3.6.1.min.js /*! jQuery v3.6.1 | (c) OpenJS Foundation and other contributors | jquery.org/license */ ... Firefox error: Loading failed for the
[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
Hi, Here it is: summary: Daemon and tooling that enable snap packages publisher: Canonical✓ store-url: https://snapcraft.io/snapd contact: https://github.com/snapcore/snapd/issues license: GPL-3.0 description: | Install, configure, refresh and remove snap packages. Snaps are 'universal' packages that work across many different Linux systems, enabling secure distribution of the latest apps and utilities for cloud, servers, desktops and the internet of things. Start with 'snap list' to see installed snaps. type: snapd snap-id: PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4 tracking: latest/stable refresh-date: 2024-05-24 channels: latest/stable:2.632024-05-23 (21759) 40MB - latest/candidate: 2.632024-05-16 (21759) 40MB - latest/beta: 2.642024-07-25 (22509) 39MB - latest/edge: 2.64+git75.g3fc1621 2024-08-01 (22553) 39MB - installed: 2.63 (21759) 40MB snapd Best Regards, Vladimir. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 17 13:31 /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js prints the file contents Downloaded version of chrome opens documentation with active search bar and no javascript errors /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html Expected results: Chromium snap should be able to follow symlink into /usr/share/javascript and correctly load OpenJDK API documentation. Note: this probably should be a specific exclusion for Debian-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2032992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
Hi, OpenJDK documentation only links to libjquery-ui in addition to jquery. In a general sense this is a bit of cat and mouse. Lintian issues warnings for a number of embedded libraries[1] and the browser snap policy should closely follow the current state of lintian development to allow browsing HTML documentation that complies with Ubuntu/Debian policy. The alternative is to whitelist javascript libraries installation location. Best Regards, Vladimir. [1] https://git.launchpad.net/ubuntu/+source/lintian/tree/lib/Lintian/Check/Languages/Javascript/Embedded.pm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 17 13:31 /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js prints the file contents Downloaded version of chrome opens documentation with active search bar and no javascript errors /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html Expected results: Chromium snap should be able to follow symlink into /usr/share/javascript and correctly load OpenJDK API documentation. Note: this probably should be a specific exclusion for Debian-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2032992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
** Merge proposal unlinked:
https://code.launchpad.net/~dviererbe/ubuntu/+source/curl/+git/curl/+merge/470121
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to graphite2 in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
defined
Status in asymptote package in Ubuntu:
Fix Released
Status in curl package in Ubuntu:
Fix Released
Status in doxygen package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Triaged
Status in graphite2 package in Ubuntu:
Fix Released
Status in gsequencer package in Ubuntu:
Fix Released
Status in haskell-devscripts package in Ubuntu:
Fix Released
Status in jose package in Ubuntu:
New
Status in ksmtuned package in Ubuntu:
Fix Released
Status in libreoffice package in Ubuntu:
Fix Released
Status in libtpms package in Ubuntu:
New
Status in mosh package in Ubuntu:
Fix Released
Status in mpich package in Ubuntu:
New
Status in mwrap package in Ubuntu:
Fix Released
Status in proftpd package in Ubuntu:
New
Status in proftpd-dfsg package in Ubuntu:
Fix Released
Status in serf package in Ubuntu:
Fix Released
Status in speech-dispatcher package in Ubuntu:
New
Status in squid package in Ubuntu:
Fix Released
Status in swtpm package in Ubuntu:
Fix Released
Status in texinfo package in Ubuntu:
Triaged
Bug description:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
(refined in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
metadata.specs` parameter is set but the needed environment variables
are not set. Cases:
1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
rp-pppoe fail to build)
2. autopkgtests
3. debugging a crash of an application build with the -spec parameter
4. People like to iteratively continue building the software in the
build dir while hacking on the package and then have no environment
variable set.
This approach is too fragile. An alternative approach would be to specify the
`--package-metadata` linker flag directly. The problem with that approach is
that the curly brackets and quotation marks need to be escaped. Example
failure: Building dpkg would add this parameter to the LDFLAGS:
```
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
```
The following configure script call (non-relevant parameters deleted):
```
$ gcc
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
/usr/bin/ld: cannot find {type:deb: No such file or directory
/usr/bin/ld: cannot find os:ubuntu: No such file or directory
/usr/bin/ld: cannot find name:dpkg: No such file or directory
/usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
/usr/bin/ld: cannot find architecture:amd64}: No such file or directory
```
Proposed solution: Add support for an `--escaped-package-metadata` parameter
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
```
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
I think the issue is on Ubuntu side, please do not add it to the workaround yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-8 package in Debian: Fix Released Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060241] [NEW] prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1
Public bug reported: The autopkgest for network-manager fail due to the missing module dependency: 3988s autopkgtest [18:31:02]: test nm_netplan.py: [--- 3988s Traceback (most recent call last): 3988s File "/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 3988s import gi 3988s ModuleNotFoundError: No module named 'gi' 3988s autopkgtest [18:31:02]: test nm_netplan.py: ---] 3989s autopkgtest [18:31:03]: test nm_netplan.py: - - - - - - - - - - results - - - - - - - - - - 3989s nm_netplan.pyFAIL non-zero exit status 1 --- [1] [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz ** Affects: audit (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2060241 Title: prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1 Status in audit package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: The autopkgest for network-manager fail due to the missing module dependency: 3988s autopkgtest [18:31:02]: test nm_netplan.py: [--- 3988s Traceback (most recent call last): 3988s File "/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 3988s import gi 3988s ModuleNotFoundError: No module named 'gi' 3988s autopkgtest [18:31:02]: test nm_netplan.py: ---] 3989s autopkgtest [18:31:03]: test nm_netplan.py: - - - - - - - - - - results - - - - - - - - - - 3989s nm_netplan.pyFAIL non-zero exit status 1 --- [1] [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/2060241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
I have tested the updated snapd in a Noble VM. I have installed: firefox latest/stable: installed: 124.0.1-1 (4033) 281MB - chromium latest/stable: installed: 123.0.6312.86(2805) 168MB - openjdk-21-doc/noble,noble,now 21.0.3~7ea-1 all [installed] snapd/noble-proposed,now 2.62+24.04build1 amd64 [installed] I have opened openjdk documentation with $firefox /usr/share/doc/openjdk-21-doc/index.html update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot open directory "/usr/local/share": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot open directory "/var/lib": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc /usr/share/javascript/sphinxdoc none bind,ro 0 0): cannot open directory "/var/lib": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme none bind,ro 0 0): cannot open directory "/var/lib": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": permission denied The snap output some errors, but the documentation opened correctly and the search bar was active. chromium: -- $ chromium /usr/share/doc/openjdk-21-doc/index.html Gtk-Message: 10:59:34.732: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. (chrome:5433): Gtk-WARNING **: 10:59:34.780: GTK+ module /snap/chromium/2805/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 10:59:34.780: Failed to load module "canberra-gtk-module" (chrome:5433): Gtk-WARNING **: 10:59:34.782: GTK+ module /snap/chromium/2805/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 10:59:34.782: Failed to load module "canberra-gtk-module" [5433:5433:0402/105934.824524:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. libva error: /snap/chromium/2805/gnome-platform/usr/lib/x86_64-linux-gnu/dri/virtio_gpu_drv_video.so init failed [5630:5630:0402/105934.916687:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [5433:5433:0402/105935.190773:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not part of the idle inhibition specification: https://specifications.freedesktop.org/idle-inhibit-spec/latest/ libva error: /snap/chromium/2805/gnome-platform/usr/lib/x86_64-linux-gnu/dri/virtio_gpu_drv_video.so init failed [5694:5694:0402/105935.271618:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization libva error: /snap/chromium/2805/gnome-platform/usr/lib/x86_64-linux-gnu/dri/virtio_gpu_drv_video.so init failed [5668:8:0402/105935.322068:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. The snap output some video driver-related errors, but the documentation opened correctly and the search bar was active. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 1
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
** Bug watch added: Debian Bug tracker #1064191 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064191 ** Also affects: openjdk-8 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064191 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Status in openjdk-8 package in Debian: Unknown Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
piuparts install/purge tests for openjdk-8 noble ** Attachment added: "piuparts-openjdk-8-noble.tar.gz" https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/2053110/+attachment/5746473/+files/piuparts-openjdk-8-noble.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
piuparts tests for focal i386 (install/purge) ** Attachment added: "piuparts-openjdk-8-focal.tar.gz" https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/2053110/+attachment/5746414/+files/piuparts-openjdk-8-focal.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
piuparts tests for jammy i386 (install/purge) ** Attachment added: "piuparts-openjdk-8-jammy.tar.gz" https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/2053110/+attachment/5746413/+files/piuparts-openjdk-8-jammy.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
piuparts test for mantic i386 (install/purge) ** Attachment added: "piuparts-openjdk-8-mantic.tar.gz" https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/2053110/+attachment/5746412/+files/piuparts-openjdk-8-mantic.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
** Description changed: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. + + + Options: + a) rollback the fix in Ubuntu + b) publish atk-wrapper ** Description changed: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. - Options: - a) rollback the fix in Ubuntu - b) publish atk-wrapper + a) rollback the fix in Ubuntu + b) publish atk-wrapper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
** Description changed: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them + + The alternative is to publish atk-wrapper for i386 in mantic, jammy and + focal. ** Description changed: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them + See LP: #1916327 + The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
Note linked merge proposal for the option when we do not publish atk- wrapper in security update ** Description changed: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: - java-atk-wrapper is present in noble on i386 + java-atk-wrapper is present in noble on i386 + + This is a regression introduced in 8u402-ga-2: + + * Restore M-A installability of focal/i386 package (LP#1916327) + by adding xenial, bionic, focal, jammy to the list of releases + built with the ATK bridge, but not enabling it by default; + keep jessie on, stretch and sid and mantic/noble off the list: + please report bugs for issues with the bridge, so sthibault + can find, debug, fix them ** Also affects: java-atk-wrapper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050033] Re: gettext: msgfmt --java2 does not support Java 21
** Description changed: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. + + Note: gettext 0.22.4 refactors Java support. This delta can be safely + dropped after a new upstream release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/2050033 Title: gettext: msgfmt --java2 does not support Java 21 Status in gettext package in Ubuntu: New Status in gettext package in Debian: New Bug description: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. Note: gettext 0.22.4 refactors Java support. This delta can be safely dropped after a new upstream release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050033] Re: gettext: msgfmt --java2 does not support Java 21
Piuparts gettext install/purge tests ** Attachment added: "noble-gettext.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+attachment/5741749/+files/noble-gettext.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/2050033 Title: gettext: msgfmt --java2 does not support Java 21 Status in gettext package in Ubuntu: New Status in gettext package in Debian: New Bug description: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050033] [NEW] gettext: msgfmt --java2 does not support Java 21
Public bug reported: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. ** Affects: gettext (Ubuntu) Importance: Undecided Status: New ** Affects: gettext (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1056293 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056293 ** Also affects: gettext (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056293 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/2050033 Title: gettext: msgfmt --java2 does not support Java 21 Status in gettext package in Ubuntu: New Status in gettext package in Debian: Unknown Bug description: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016408] Re: Running all KDE (Qt) apps on Wayland - apps bad working
same problem in 23.10 :( -- 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/2016408 Title: Running all KDE (Qt) apps on Wayland - apps bad working Status in Yaru Theme: New Status in mutter package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Hi, on Ubuntu 23.04 all KDE apps work not properly. When I run KDE apps (like clementine, kaffeine, smplayer), the cursor on HDPi monitor (scale 200%) is so huge than in Gnome apps. KDE apps discrespect windows decorations (like max, min, close buttons - I have them on the left site, but kde apps have it on right site). When I start smplayer, it crashes because can't play video over mplayer/mpv player...blank window and crashes. Same problems here: https://www.reddit.com/r/kde/comments/xev3jq/is_there_a_way_to_make_smplayermpv_work_under/ Solution for me is run KDE apps like: QT_QPA_PLATFORM=xcb smplayer If i try tu run application like that, everything is working properly. Can you pleas repair it on Ubuntu 23.04 for wayland? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 16 11:16:28 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed v4l2loopback/0.12.7, 6.2.0-20-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694] InstallationDate: Installed on 2023-04-14 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230414) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d6cce96a-9549-40b0-8d45-aeb37eabc158 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1805 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1805:bd05/13/2016:br5.11:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2016408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031340] Re: slic3r-prusa autopkgtest flaky
Submitted: https://github.com/prusa3d/PrusaSlicer/issues/11429 While I have a MP that hides the problem by making tests verbose, I do not want to proceed with it unless absolutely necessary as this is a quite breaking bug for the GUI. ** Bug watch added: github.com/prusa3d/PrusaSlicer/issues #11429 https://github.com/prusa3d/PrusaSlicer/issues/11429 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky Status in fontconfig package in Ubuntu: Fix Released Status in gmp package in Ubuntu: Fix Released Status in nlopt package in Ubuntu: Fix Released Status in slic3r-prusa package in Ubuntu: New Bug description: autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest. In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031340] Re: slic3r-prusa autopkgtest flaky
The tests use boost background worker and are prone to race conditions. Increasing verbosity of the test runner provides a band-aid by shifting the test timings. ** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/slic3r-prusa/+git/slic3r-prusa/+merge/453027 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky Status in fontconfig package in Ubuntu: Fix Released Status in gmp package in Ubuntu: Fix Released Status in nlopt package in Ubuntu: Fix Released Status in slic3r-prusa package in Ubuntu: New Bug description: autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest. In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031340] Re: slic3r-prusa autopkgtest flaky
** Attachment added: "prusa-slicer.log.gz" https://bugs.launchpad.net/ubuntu/+source/slic3r-prusa/+bug/2031340/+attachment/5707297/+files/prusa-slicer.log.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky Status in fontconfig package in Ubuntu: Fix Released Status in gmp package in Ubuntu: Fix Released Status in nlopt package in Ubuntu: Fix Released Status in slic3r-prusa package in Ubuntu: New Bug description: autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest. In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031340] Re: slic3r-prusa autopkgtest flaky
I have added a build watch script to output to the terminal, but s390x still failed: https://launchpad.net/~vpa1977/+archive/ubuntu/plusone/+sourcepub/15186846/+listing-archive-extra Looks like one of the tests is getting stuck, I will try to debug it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky Status in fontconfig package in Ubuntu: Fix Released Status in gmp package in Ubuntu: Fix Released Status in nlopt package in Ubuntu: Fix Released Status in slic3r-prusa package in Ubuntu: New Bug description: autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest. In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012978] Re: Memory leak
the cmd: gnome-extensions list --enabled shows: ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com d...@rastersoft.com disabling extensions does not make effects -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak Status in gnome-shell package in Ubuntu: New Bug description: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012978] [NEW] Memory leak
Public bug reported: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak Status in gnome-shell package in Ubuntu: New Bug description: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
I'm having the same problem with HP Elitebook 860 G9. I get sound through headphones and HDMI output, but not through built-in speakers. Upgrading to kernel 5.9.17 seems to fix the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006060] [NEW] bbswitch-dkms 0.8-10ubuntu2: bbswitch kernel module failed to build
Public bug reported: error with building bbswitch module 1) lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 2) apt-cache policy bbswitch-dkms bbswitch-dkms: 0.8-10ubuntu2 3) What you expected to happen error during linux-headers-5.19.0-28-generic installation 4) What happened instead smooth installation of linux-headers and bbswitch module built ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bbswitch-dkms 0.8-10ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 5.19.0-28-generic Date: Sun Feb 5 23:01:49 2023 DuplicateSignature: dkms:bbswitch-dkms:0.8-10ubuntu2:/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:272:13: error: implicit declaration of function ‘acpi_bus_get_device’; did you mean ‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2023-01-26 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageVersion: 0.8-10ubuntu2 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: bbswitch Title: bbswitch-dkms 0.8-10ubuntu2: bbswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2006060 Title: bbswitch-dkms 0.8-10ubuntu2: bbswitch kernel module failed to build Status in bbswitch package in Ubuntu: New Bug description: error with building bbswitch module 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) apt-cache policy bbswitch-dkms bbswitch-dkms: 0.8-10ubuntu2 3) What you expected to happen error during linux-headers-5.19.0-28-generic installation 4) What happened instead smooth installation of linux-headers and bbswitch module built ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bbswitch-dkms 0.8-10ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 5.19.0-28-generic Date: Sun Feb 5 23:01:49 2023 DuplicateSignature: dkms:bbswitch-dkms:0.8-10ubuntu2:/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:272:13: error: implicit declaration of function ‘acpi_bus_get_device’; did you mean ‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2023-01-26 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageVersion: 0.8-10ubuntu2 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: bbswitch Title: bbswitch-dkms 0.8-10ubuntu2: bbswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2006060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: saaj (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bi
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: octave (Ubuntu Cosmic) Status: New => Invalid ** Changed in: octave (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in B
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: metro-policy (Ubuntu Cosmic) Status: New => Invalid ** Changed in: mongo-java-driver (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jyth
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: metro-policy (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source packa
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jws-api (Ubuntu Cosmic) Status: New => Invalid ** Changed in: libpdfbox-java (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython sourc
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jws-api (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jaxws-api (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source p
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jaxws-api (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jasperreports (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source pack
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jasperreports (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java sour
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jameica-util (Ubuntu) Status: New => Invalid ** Changed in: jameica-util (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jameica-datasource (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: jameica-datasource (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: gkl (Ubuntu) Status: New => Invalid ** Changed in: htsjdk (Ubuntu) Status: New => Invalid ** Changed in: jameica (Ubuntu) Status: New => Fix Released ** Changed in: openhft-chronicle-threads (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in j
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: gkl (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: htsjdk (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source pack
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: saaj (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source packag
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: geogebra (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source pa
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: gatk-native-bindings (Ubuntu) Status: New => Invalid ** Changed in: gatk-native-bindings (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status i
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: ca-certificates-java (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java sour
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
cosmic reached eol on July, 2019 ** Changed in: ca-certificates-java (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: Invalid Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: Invalid Status in geogebra package in Ubuntu: Fix Released Status in gkl package in Ubuntu: Invalid Status in htsjdk package in Ubuntu: Invalid Status in jameica package in Ubuntu: Fix Released Status in jameica-datasource package in Ubuntu: Invalid Status in jameica-util package in Ubuntu: Invalid Status in jasperreports package in Ubuntu: Invalid Status in jaxws-api package in Ubuntu: Invalid Status in jws-api package in Ubuntu: Invalid Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: Invalid Status in mongo-java-driver package in Ubuntu: Fix Released Status in octave package in Ubuntu: Invalid Status in openhft-chronicle-threads package in Ubuntu: Fix Released Status in saaj package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-ja
[Desktop-packages] [Bug 2001580] [NEW] Thunderbird 102.6.0-2 snap cant save files
Public bug reported: Can't save pdf file from attachment Ubuntu 22.04.1 LTS thunderbird102.6.0-2 281latest/stable snap-id: k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460 with terminal output (no reaction in GUI) (thunderbird:24618): Gtk-WARNING **: 09:35:43.338: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files installed xdg-desktop-portal-gtk and get: (thunderbird:24618): Gtk-WARNING **: 09:38:40.128: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.FileChooser” on object at path /org/freedesktop/portal/desktop pretty similar to https://forum.snapcraft.io/t/firefox-snap-77-cannot- download-anything/18167 bug ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2001580 Title: Thunderbird 102.6.0-2 snap cant save files Status in thunderbird package in Ubuntu: New Bug description: Can't save pdf file from attachment Ubuntu 22.04.1 LTS thunderbird102.6.0-2 281latest/stable snap-id: k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460 with terminal output (no reaction in GUI) (thunderbird:24618): Gtk-WARNING **: 09:35:43.338: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files installed xdg-desktop-portal-gtk and get: (thunderbird:24618): Gtk-WARNING **: 09:38:40.128: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.FileChooser” on object at path /org/freedesktop/portal/desktop pretty similar to https://forum.snapcraft.io/t/firefox-snap-77-cannot- download-anything/18167 bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2001580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
What the fuck? Can't resolve problem from 2013? Have a fresh install ubuntu 22.04 and cant setup ctrl-alt-etc keyboard layout switch? Need to use tweaks, google, etc Ubuntu user friendly? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in GNOME Settings Daemon: Unknown Status in System76: New Status in Ubuntu Flashback: New Status in Ubuntu GNOME: Fix Released Status in Ubuntu GNOME Flashback: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-control-center package in ALT Linux: Unknown Status in gnome-control-center package in Baltix: Confirmed Status in gnome-control-center package in Gentoo Linux: Unknown Status in gnome-control-center package in Mandriva: Unknown Bug description: [Impact] Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift, etc. Shift, Caps Lock keys are just ignored in settings. [Test Case] - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a combination of two modifier keys such as Ctrl+Shift -> the UI should reflect the new keys - add at least two input sources through gnome-control-center's text entry settings - press and release Ctrl+Shift -> the current input source should change [Regression Potential] That UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). You can use the tag keyboard-layout-switching-hotkeys to find related bugs. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys For using layout switching hotkeys in Unity Greeter, see bug 1245137. For using layout switching hotkeys in GNOME lockscreen, see bug 1244548. For using layout switching hotkeys in GNOME FlashBack sessions, see bug 1687466 (at least ). -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
The same problem happens with LANG=C and standard ubuntu environment. both Transmission-gtk 3.00-2ubuntu2 and Transmission-gtk 3.00-2.1 ... (transmission-gtk:2763463): GLib-GObject-WARNING **: 23:29:33.568: invalid unclassed pointer in cast to 'GtkTreeModel' (transmission-gtk:2763463): Gtk-CRITICAL **: 23:29:33.568: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (transmission-gtk:2763463): Gtk-CRITICAL **: 23:29:33.568: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (transmission-gtk:2763463): Gtk-CRITICAL **: 23:29:33.568: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed (transmission-gtk:2763463): GLib-GObject-WARNING **: 23:29:33.568: invalid unclassed pointer in cast to 'GtkToggleButton' (transmission-gtk:2763463): Gtk-CRITICAL **: 23:29:33.568: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968379] [NEW] software-properties-gtk crashes with DBus.Error.ServiceUnknown
Public bug reported: Ubuntu 20.04.4 LTS software-properties-gtk crashes immediately after start DBus.Error.ServiceUnknown apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.9.8 Candidate: 0.99.9.8 Version table: *** 0.99.9.8 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages sudo software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.1625:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 222, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1625 was not provided by any .service files problem only in software-properties-gtk, software-properties-qt runs OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.99.9.8 ProcVersionSignature: Ubuntu 5.4.0-107.121-lowlatency 5.4.174 Uname: Linux 5.4.0-107-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 01:02:27 2022 InstallationDate: Installed on 2019-05-18 (1056 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968379 Title: software-properties-gtk crashes with DBus.Error.ServiceUnknown Status in software-properties package in Ubuntu: New Bug description: Ubuntu 20.04.4 LTS software-properties-gtk crashes immediately after start DBus.Error.ServiceUnknown apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.9.8 Candidate: 0.99.9.8 Version table: *** 0.99.9.8 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages sudo software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.1625:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 222, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBu
[Desktop-packages] [Bug 1967176] [NEW] gnome-shell crashed with SIGSEGV
Public bug reported: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42~beta-1ubuntu3 Candidate: 42~beta-1ubuntu3 Version table: *** 42~beta-1ubuntu3 500 500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status nvidia 1030. nvidia-driver-510 3) What you expected to happen just logout and login again 4) What happened instead after logout and login again, apport reported this crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 22:40:45 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ffbc79eda7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967176 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42~beta-1ubuntu3 Candidate: 42~beta-1ubuntu3 Version table: *** 42~beta-1ubuntu3 500 500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status nvidia 1030. nvidia-driver-510 3) What you expected to happen just logout and login again 4) What happened instead after logout and login again, apport reported this crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 22:40:45 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ffbc79eda7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957172] Re: Graphics acceleration like WebGL is broken on nvidia-390
Thanks Olivier, I've checked version 98.0.4758.80 and confirming that WebGL acceleration is now working fine. ``` Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled OpenGL: Enabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1957172 Title: Graphics acceleration like WebGL is broken on nvidia-390 Status in chromium-browser package in Ubuntu: Incomplete Bug description: ``` % lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ``` Snap: ``` chromium 97.0.4692.711864 latest/stable canonical✓- ``` I'm using proprietary nvidia drivers `nvidia-driver-390` package. I've migrated my home system to ubuntu 20.04 some time ago and noticed that all acceleration is broken in snap-based chromium. If I go into chrome://gpu/ ``` Graphics Feature Status Canvas: Software only. Hardware acceleration disabled Canvas out-of-process rasterization: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Disabled Out-of-process Rasterization: Disabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Disabled WebGL2: Disabled Problems Detected Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Accelerated video decode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_decode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing GPU process was unable to boot: GPU process crashed too many times with SwiftShader. Disabled Features: all ... Log Messages GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. [137727:137727:0112/173138.821608:ERROR:angle_platform_impl.cc(44)] : Display.cpp:894 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1068. [137727:137727:0112/173138.822966:ERROR:gl_surface_egl.cc(783)] : EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1068. [137727:137727:0112/173138.823496:ERROR:gl_surface_egl.cc(1391)] : eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED [137727:137727:0112/17
[Desktop-packages] [Bug 1957172] [NEW] Graphics acceleration like WebGL is broken on nvidia-390
Public bug reported: ``` % lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ``` Snap: ``` chromium 97.0.4692.711864 latest/stable canonical✓- ``` I'm using proprietary nvidia drivers `nvidia-driver-390` package. I've migrated my home system to ubuntu 20.04 some time ago and noticed that all acceleration is broken in snap-based chromium. If I go into chrome://gpu/ ``` Graphics Feature Status Canvas: Software only. Hardware acceleration disabled Canvas out-of-process rasterization: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Disabled Out-of-process Rasterization: Disabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Disabled WebGL2: Disabled Problems Detected Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Accelerated video decode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_decode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing GPU process was unable to boot: GPU process crashed too many times with SwiftShader. Disabled Features: all ... Log Messages GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. GpuProcessHost: The GPU process exited normally. Everything is okay. [137727:137727:0112/173138.821608:ERROR:angle_platform_impl.cc(44)] : Display.cpp:894 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1068. [137727:137727:0112/173138.822966:ERROR:gl_surface_egl.cc(783)] : EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1068. [137727:137727:0112/173138.823496:ERROR:gl_surface_egl.cc(1391)] : eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED [137727:137727:0112/173138.824148:ERROR:gl_ozone_egl.cc(20)] : GLSurfaceEGL::InitializeOneOff failed. [137727:137727:0112/173138.858669:ERROR:viz_main_impl.cc(161)] : Exiting GPU process due to errors during initialization GpuProcessHost: The GPU process exited normally. Everything is okay. [137735:137735:0112/173138.988272:WARNING:vaapi_wrapper.cc(606)] : VAAPI video acceleration not available for disabled [137735:137735:0112/173138.989446:ERROR:gpu_init.cc(457)] : Passthrough is not supported, GL is disabled, ANGLE is ``` I suspect that chromium snap cannot access `/dev/nvidia*` files. If I run chromium binary directly like `/snap/chromium/current/usr/lib/chromium-browser/chrome` or run flatpak version of chromium, acceleration works fine and there are no such error messages. In the journalctl logs I also see a DENIED message at the startup, not sure if this is related ``` Jan 12 17:31:32 home kernel: audit: type=1107 audit(1641990692.085:180): pid=1524 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.fre
[Desktop-packages] [Bug 1955733] [NEW] [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: I have a dell inspiron 15 3000 with audio problems, bluetooth is working fine, hdmi speaker is working fine but internal speaker sounds bad. The sound kind of crackles. Information Description:Ubuntu 20.04.3 LTS Release:20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 25 00:30:18 2021 InstallationDate: Installed on 2021-12-09 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: dic 24 23:12:16 valaro dbus-daemon[909]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29' (uid=125 pid=2170 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") dic 24 23:13:22 valaro pulseaudio[2170]: After module unload, module 'module-null-sink' was still loaded! dic 24 23:13:22 valaro systemd[2152]: pulseaudio.service: Succeeded. dic 24 23:13:32 valaro systemd[2152]: pulseaudio.socket: Succeeded. Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 03TNDR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/05/2021:br1.7:svnDellInc.:pnInspiron3501:pvr:sku0A25:rvnDellInc.:rn03TNDR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3501 dmi.product.sku: 0A25 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-12-24T21:32:37.421378 mtime.conffile..etc.pulse.default.pa: 2021-12-24T22:17:32.506068 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1955733 Title: [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: New Bug description: I have a dell inspiron 15 3000 with audio problems, bluetooth is working fine, hdmi speaker is working fine but internal speaker sounds bad. The sound kind of crackles. Information Description: Ubuntu 20.04.3 LTS Release: 20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 25 00:30:18 2021 InstallationDate: Installed on 2021-12-09 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: dic 24 23:12:16 valaro dbus-daemon[909]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29'
[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
I had the same problem with Ubuntu 20.04 LTSP client: black screen during boot, keyboard and mouse don't work, ssh works and "ring 0 stalled" messages in the system log. I had to switch to Ubuntu 18.04 which works fine. CPU: AMD A8-5500B APU with Radeon(tm) HD Graphics lshw -C display *-display description: VGA compatible controller product: Trinity [Radeon HD 7560D] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 1 bus info: pci@:00:01.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:35 memory:c000-cfff ioport:f000(size=256) memory:feb0-feb3 memory:c-d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: Since the update: xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; which resulted from: https://bugs.launchpad.net/fedora/+source/xserver-xorg-video- ati/+bug/1841718 I've experienced GPU freezes where all video becomes unresponsive, both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am still able to access the system via SSH. Sometimes dmesg ends up full of this message repeating over and over: radeon :01:00.0: ring 0 stalled for more than 24040msec radeon :01:00.0: GPU lockup (current fence id 0x9e44 last fence id 0x9e49 on ring 0) I sometimes get a few GPU soft reset which seem to fail in drm(?): radeon :01:00.0: Saved 110839 dwords of commands on ring 0. radeon :01:00.0: GPU softreset: 0x0008 ... radeon :01:00.0: Wait for MC idle timedout ! radeon :01:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 1024M enabled (table at 0x00162000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x725651ad radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc3678ed8 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xdbd9e01b [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Even if the above reset doesn't happen, this freeze always results in a unable to handle page fault" BUG in radeon_ring_backup, entered from various call paths, eg: BUG: unable to handle page fault for address: bc2d80574ffc ... Oops: [#1] SMP PTI CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic #202001262030 Workqueue: radeon-crtc radeon_flip_work_func [radeon] RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon] Call Trace: radeon_gpu_reset+0xc3/0x2f0 [radeon] radeon_flip_work_func+0x1f3/0x250 [radeon] ? __schedule+0x2e0/0x760 process_one_work+0x1b5/0x370 worker_thread+0x50/0x3d0 kthread+0x104/0x140 ? process_one_work+0x370/0x370 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 or: BUG: unable to handle page fault for address: c03901000ffc ... Oops: [#1] SMP PTI CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon] Call Trace: radeon_gpu_reset+0xb9/0x340 [radeon] ? dma_fence_wait_timeout+0x48/0x110 ? reservation_object_wait_timeout_rcu+0x19d/0x340 radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon] radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] drm_ioctl_kernel+0xb0/0x100 [drm] drm_ioctl+0x389/0x450 [drm] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 radeon_drm_ioctl+0x4f/0x80 [radeon] do_vfs_ioctl+0xa9/0x640 ? __schedule+0x2b0/0x670 ksys_ioctl+0x75/0x80 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel- ppa but that made no difference. It appears to be a bug in radeon. Nothing specific makes this happen, just regular usage with a compositing window manager. I'm not playing games or particularly exercising the GPU. The last two times I was just reading in web browser. It's also happened in the middle
[Desktop-packages] [Bug 1942928] [NEW] Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Public bug reported: I see this error messages: Sep 7 20:39:05 MacBuntu gnome-shell[1334]: libinput error: client bug: timer event4 debounce short: scheduled expiry is in the past (-0ms), your system is too slow Sep 7 20:40:28 MacBuntu gnome-shell[1334]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). How to fix this? My device: MacBook Pro 12.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-35.37-generic 5.11.22 Uname: Linux 5.11.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 7 20:56:24 2021 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANGUAGE=ru_UA:ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 gnome-shell hirsute libinput ** Attachment added: "log.txt" https://bugs.launchpad.net/bugs/1942928/+attachment/5523566/+files/log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1942928 Title: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Status in gnome-shell package in Ubuntu: New Bug description: I see this error messages: Sep 7 20:39:05 MacBuntu gnome-shell[1334]: libinput error: client bug: timer event4 debounce short: scheduled expiry is in the past (-0ms), your system is too slow Sep 7 20:40:28 MacBuntu gnome-shell[1334]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). How to fix this? My device: MacBook Pro 12.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-35.37-generic 5.11.22 Uname: Linux 5.11.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 7 20:56:24 2021 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANGUAGE=ru_UA:ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932343] Re: rtl8188fu is not supported by default, popular driver freezes Ubuntu upon device connection
Attaching more information: dmesg output when attaching the device and lsusb line for the device Thank you! ** Attachment added: "realtek.crash.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1932343/+attachment/5505328/+files/realtek.crash.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1932343 Title: rtl8188fu is not supported by default, popular driver freezes Ubuntu upon device connection Status in network-manager package in Ubuntu: New Bug description: When you plug-in a rtl8188fu USB dongle it's not supported by default in Ubuntu. When using https://github.com/kelebek333/rtl8188fu to add support, any time you plug the USB dongle everything freezes in Ubuntu, you can't longer use sudo. Looks like systemd-udevd starts to hog the CPU at 100% until you disconnect the dongle and reboot the system ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-20.21-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 17 10:28:13 2021 IpRoute: default via 192.168.1.1 dev enp1s0 proto dhcp metric 100 169.254.0.0/16 dev enp1s0 scope link metric 1000 172.16.97.0/24 dev vmnet1 proto kernel scope link src 172.16.97.1 192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.2 metric 100 192.168.217.0/24 dev vmnet8 proto kernel scope link src 192.168.217.1 RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1932343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932343] [NEW] rtl8188fu is not supported by default, popular driver freezes Ubuntu upon device connection
Public bug reported: When you plug-in a rtl8188fu USB dongle it's not supported by default in Ubuntu. When using https://github.com/kelebek333/rtl8188fu to add support, any time you plug the USB dongle everything freezes in Ubuntu, you can't longer use sudo. Looks like systemd-udevd starts to hog the CPU at 100% until you disconnect the dongle and reboot the system ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-20.21-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 17 10:28:13 2021 IpRoute: default via 192.168.1.1 dev enp1s0 proto dhcp metric 100 169.254.0.0/16 dev enp1s0 scope link metric 1000 172.16.97.0/24 dev vmnet1 proto kernel scope link src 172.16.97.1 192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.2 metric 100 192.168.217.0/24 dev vmnet8 proto kernel scope link src 192.168.217.1 RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1932343 Title: rtl8188fu is not supported by default, popular driver freezes Ubuntu upon device connection Status in network-manager package in Ubuntu: New Bug description: When you plug-in a rtl8188fu USB dongle it's not supported by default in Ubuntu. When using https://github.com/kelebek333/rtl8188fu to add support, any time you plug the USB dongle everything freezes in Ubuntu, you can't longer use sudo. Looks like systemd-udevd starts to hog the CPU at 100% until you disconnect the dongle and reboot the system ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-20.21-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 17 10:28:13 2021 IpRoute: default via 192.168.1.1 dev enp1s0 proto dhcp metric 100 169.254.0.0/16 dev enp1s0 scope link metric 1000 172.16.97.0/24 dev vmnet1 proto kernel scope link src 172.16.97.1 192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.2 metric 100 192.168.217.0/24 dev vmnet8 proto kernel scope link src 192.168.217.1 RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1932343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue with: Ubuntu 20.04.1 LTS Lenovo ThinkPad P1 (2nd Gen) Jabra Elite 85h -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
This is still an issue in Ubuntu 20.20 VMWare vmnet1 and vmnet2 are displayed in NetworkManager applet in Gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
I have ubuntu 18.04 with ru locale and same issue
How I fixed it:
install snap versions
snap install duplicity --classic
snap install deja-dup --classic
remove apt version of deja-dup
sudo apt purge deja-dup
backup (option)
sudo mv duplicity duplicity_apt
link duplicity bin from snap pkg
sudo ln /snap/bin/duplicity /usr/bin/duplicity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
Fix Released
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887149] Re: "gnome-session --version" prints nothing
** Description changed: - According to the documentation which "gnome-shell --help" prints to - console, the "gnome-shell --version" command must print version to - console, but it prints nothing. + According to the documentation which "gnome-session --help" prints to + console, the "gnome-session --version" must print version, but it prints + nothing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1887149 Title: "gnome-session --version" prints nothing Status in gnome-session package in Ubuntu: Confirmed Bug description: According to the documentation which "gnome-session --help" prints to console, the "gnome-session --version" must print version, but it prints nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1887149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
"nautilus --version" crashes always (vanilla Ubuntu 2020.04 desktop installation). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835644] Re: CRL files are not accessible for the Verify CRL options
The problem persists on 20.04 (network-manager-openvpn, network-manager- openvpn-gnome 1.8.12-1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1835644 Title: CRL files are not accessible for the Verify CRL options Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Hello, The Network Manager GUI options 'Verify CRL from file' and 'Verify CRL from directory' won't work because the openvpn process cannot access the files since being run with chroot, so the connection fails: nm-openvpn[5069]: chroot to '/var/lib/openvpn/chroot' and cd to '/' succeeded nm-openvpn[6135]: Options error: --crl-verify fails with '/var/lib/openvpn/chroot//home/steve/VPN/config/crl.rsa.4096.pem': No such file or directory (errno=2) Thanks. Ubuntu 19.04 network-manager-openvpn, network-manager-openvpn-gnome 1.8.10-1 openvpn 2.4.6-1ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1835644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset
This is also an issue with Kubuntu 19.10 eoan 5.3.0-40-generic and pulseaudio 13.0 I use this headset interchangeably with Windows and it's not an issue there. I have noticed that using the bundle Jabra link 370 makes the headset work perfectly, it's just an issue when using it as USB headphone. Attached is the pulseaudio output from pacmd list-sinks ** Attachment added: "Output of pacmd list-sinks" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+attachment/5329009/+files/pacmd%20list-sinks.txt -- 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/1710060 Title: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Fedora: Confirmed Bug description: Whenever I choose the Jabra Evolve 65 UC Headset as the playback device, there are sound chipmunks. The same was the case with Jabra Motion Headset as well. But those two headsets worked perfectly in Windows, Mac OS and Android. There was a workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the contents of /etc/pulseaudio/daemon.conf : Changing ;default-sample-rate=44100 to default-sample-rate=48000 and then running pulseaudio -k made the sound on Jabra good (no more chipmunks). Also, when I opened the Sound Settings with the changes in daemon.conf in place, there seems to be some distortions in headset sound, which goes away few seconds after I close the sound settings window. This problem should be fixed, as many new Linux users will find it difficult to edit files requiring root access, and those who do not use command line won't be okay with it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: itachi10880 F...m pulseaudio /dev/snd/controlC2: itachi10880 F pulseaudio /dev/snd/controlC1: itachi10880 F pulseaudio /dev/snd/controlC0: itachi10880 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 10 21:11:18 2017 InstallationDate: Installed on 2016-08-27 (349 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I do not have any GNOME shell extension, and extensions are disable in "Tweaks", but problem with copy paste/paste exits. I can also confirm that double-copy works in some cases. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I have the same problem with Wine applications. Ubuntu 19.10, both X11 and Wayland sessions. Copy/paste works very inconsistent. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798840] Re: Night Light is not functioning
I confirm that on my Dell XPS 13 night light does not work in Waylay session. All is OK in with XOrg. I'm using Ubuntu 19.10, new installation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1798840 Title: Night Light is not functioning Status in gnome-control-center package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: New Bug description: Night Light is not shading/filtering the screen anymore after the update to Cosmic (Ubuntu 18.10) from Bionic (Ubuntu 18.04 LTS). It still appears as an option and all the settings work, but the feature itself isn't filtering out blue light from the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 11:03:28 2018 InstallationDate: Installed on 2018-08-17 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
After transition to snap the Chromium is not usable for me. I have a lot of PDFs with hyperlinks and they stopped working. Is there any workaround other then migrating to deb Chrome? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in evince package in Ubuntu: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838240] [NEW] Wallpaper corrupts after hibernate
Public bug reported: Steps to reproduce: 1. Set wallpapers to lock and desktop screens 2. Have a lock screen 3. Press hibernate (?) button 4. Turn on PC after hibernation Lock screen and desktop wallpapers are corrupted (see screenshot). They are corrupted in a different way. If i restart PC then it wallpaper is shown fine, until another hibernation. The bug is easily reproduced on my machine. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 29 10:29:06 2019 InstallationDate: Installed on 2019-07-20 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wallpaper ** Attachment added: "2019-07-28 10-33-10.JPG" https://bugs.launchpad.net/bugs/1838240/+attachment/5279792/+files/2019-07-28%2010-33-10.JPG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1838240 Title: Wallpaper corrupts after hibernate Status in gdm3 package in Ubuntu: New Bug description: Steps to reproduce: 1. Set wallpapers to lock and desktop screens 2. Have a lock screen 3. Press hibernate (?) button 4. Turn on PC after hibernation Lock screen and desktop wallpapers are corrupted (see screenshot). They are corrupted in a different way. If i restart PC then it wallpaper is shown fine, until another hibernation. The bug is easily reproduced on my machine. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 29 10:29:06 2019 InstallationDate: Installed on 2019-07-20 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1838240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831218] [NEW] xorg
Public bug reported: ubuntu 16.04 GF106GL $ sudo ubuntu-drivers autoinstall nvidia-384 $ sudo ubuntu-bug xorg Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 31 12:33:50 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-50-generic, x86_64: installed nvidia-384, 384.130, 4.15.0-50-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF106GL [Quadro 2000] [10de:0dd8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF106GL [Quadro 2000] [10de:084a] InstallationDate: Installed on 2019-05-24 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=010c1118-5303-4b15-9fc0-a5cb2c806fb5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z270-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri May 31 11:53:07 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831218 Title: xorg Status in xorg package in Ubuntu: New Bug description: ubuntu 16.04 GF106GL $ sudo ubuntu-drivers autoinstall nvidia-384 $ sudo ubuntu-bug xorg Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130
[Desktop-packages] [Bug 1826549] [NEW] Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0
Public bug reported: I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse wheel does not work any more. My mouse is Microsoft Wireless Optical Mouse 2000. The mouse is connected to USB port via wireless receiver (Microsoft Wireless Mouse Receiver v1.0). I've found that problem is related to new Linux kernel 5.0. When I boot with previous kernel 4.18 all works good. The problem is reproducible with xorg and with wayland. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:23:34 2019 DistUpgraded: 2019-04-26 14:07:47,232 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2017-09-12 (591 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012 Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=249a1929-c0a6-4e3c-98dd-3a16b38e6c07 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-26 (0 days ago) dmi.bios.date: 07/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z270 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1826549 Title: Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0 Status in xorg package in Ubuntu: New Bug description: I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse wheel does not work any more. My mouse is Microsoft Wireless Optical Mouse 2000. The mouse is connected to USB port via wireless receiver (Microsoft Wireless Mouse Receiver v1.0). I've found that problem is related to new Linux kernel 5.0. When I boot with previous kernel 4.18 all works good. The problem is reproducible with xorg and with wayland. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:23:34 2019 DistUpgraded: 2019-04-26 14:07:47,232 ERR
[Desktop-packages] [Bug 1822464] [NEW] iThe installer ignores deliberately selected /boot/efi partition
Public bug reported: I've noticed that Ubuntu installer ignores explicitly selected /boot/efi partition. I have 2 ssd drives: the first one is nvme (/dev/nvme0n1) the second one is sata (/dev/sda), both have their EFI partitions for multiboot purposes. During the installation process the installer generates fstab with /dev/nvme0n1p1 as /boot/efi despite the fact that the partition chosen for this mount point was /dev/sda1. Device for bootloader installation was /dev/sda. Moreover, /dev/nvme0n1p1 was even marked as "do not use this partition", but anyway it got put in requisition. Moving bootloader files (grubx64.efi,etc) to initially desired location, editing fstab correspondingly, remounting partitions and re-installation of grub helps but these actions are not user-friendly and the situation itself is not good at all. This issue affects Ubuntu 18.04 onwards (18.10 and 19.04 too). $ lsb_release -rd Description:Ubuntu Disco Dingo (development branch) Release:19.04 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Package changed: ibus-anthy (Ubuntu) => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-anthy in Ubuntu. https://bugs.launchpad.net/bugs/1822464 Title: iThe installer ignores deliberately selected /boot/efi partition Status in ubiquity package in Ubuntu: New Bug description: I've noticed that Ubuntu installer ignores explicitly selected /boot/efi partition. I have 2 ssd drives: the first one is nvme (/dev/nvme0n1) the second one is sata (/dev/sda), both have their EFI partitions for multiboot purposes. During the installation process the installer generates fstab with /dev/nvme0n1p1 as /boot/efi despite the fact that the partition chosen for this mount point was /dev/sda1. Device for bootloader installation was /dev/sda. Moreover, /dev/nvme0n1p1 was even marked as "do not use this partition", but anyway it got put in requisition. Moving bootloader files (grubx64.efi,etc) to initially desired location, editing fstab correspondingly, remounting partitions and re-installation of grub helps but these actions are not user-friendly and the situation itself is not good at all. This issue affects Ubuntu 18.04 onwards (18.10 and 19.04 too). $ lsb_release -rd Description: Ubuntu Disco Dingo (development branch) Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
Still no fix in official repos? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)
** Tags added: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1296020 Title: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04) Status in nvidia-prime package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Precise: Triaged Status in ubuntu-drivers-common source package in Precise: Invalid Status in nvidia-prime source package in Trusty: Invalid Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: SRU Request Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. [Impact] * The ghost VGA output confuses lightdm and the gnome-settings-daemon making the system unusable. [Test Case] * Install the nvidia binary driver, reboot, and check the output of the "xrandr -q" command - Expected: only the outputs that are actually connected will be marked as active. - Bad behavior: a non-existent VGA device will show up in the output. [Regression Potential] * Low, as it only disables CRT outputs in the nvidia driver. [Other Info] * N/A -- There is a non existent display detected in both intel driver only and nvidia 331 driver installation. The non existent display is "Unknown Display" shown in gnome-control-center --> display and "CRT-0" in nvidia-settings, and "VGA-0" in xrandr -q output. It will cause gdm failed to start. gnome-shell has some crazy layouts. lightdm will only occupy 2/3 of monitor in top left corner. I tested this in intel driver only environment. and nvidia-331 installation environment. My laptop is Asus U36JC. My monitor correct resolution is 1366x768. The following is the output of "xrandr -q" in gnome-shell with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 680x384+0+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x384 60.0*+ 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x720 60.0 928x696 60.1 896x672 60.0 960x600 60.0 960x540 60.0 800x600 60.0 60.3 56.2 840x525 60.0 59.9 800x512 60.2 700x525 60.0 640x512 60.0 720x450 59.9 640x480 60.0 59.9 680x384 59.8 60.0 576x432 60.1 512x384 60.0 400x300 60.3 56.3 320x240 60.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) 1366x768 (0x46) 69.3MHz h: width 1366 start 1425 end 1464 total 1472 skew 0 clock 47.1KHz v: height 768 start 773 end 782 total 785 clock 60.0Hz 1360x768 (0x48) 72.0MHz h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.4KHz v: height 768 start 771 end 781 total 790 clock 60.0Hz 680x384 (0x5c) 36.0MHz h: width 680 start 704 end 720 total 760 skew 0 clock 47.4KHz v: height 384 start 385 end 390 total 395 clock 60.0Hz The following is the output of "xrandr -q" in lxde with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 1024x768+31+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x38460.0 + 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x72060.0 928x69660.1 896x67260.0 960x60060.0 960x54060.0 800x60060.0 60.3 56.2 840x52560.0 59.9 800x51260.2 700x52560.0 640x51260.0 720x45059.9 640x48060.0 59.9 680x38459.8 60.0 576x43260.1 512x38460.0 400x30060.3 56.3 320x24060.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) 1366x768 (0x46) 69.3MHz h: width 1366 start 1425 end 1464 to
[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager
Xorg.0.log too ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+attachment/5055938/+files/Xorg.0.log ** Tags added: amd64 nvidia packaging -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1749769 Title: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager Status in nvidia-prime package in Ubuntu: New Bug description: Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. 1) Ubuntu 16.04.3 LTS 2) nvidia-prime 0.8.2 3) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia-graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot there only one active output in xrandr --verbose is LVDS. 4) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia- graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot and here you go in xrandr --verbose there non-existent display detected VGA-0 (Ghost screen with wrong resolution 1360x768). it's same bug as here https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1296020 but on LTS version of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager
And here my gpu-manager.log ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+attachment/5055936/+files/gpu-manager.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1749769 Title: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager Status in nvidia-prime package in Ubuntu: New Bug description: Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. 1) Ubuntu 16.04.3 LTS 2) nvidia-prime 0.8.2 3) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia-graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot there only one active output in xrandr --verbose is LVDS. 4) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia- graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot and here you go in xrandr --verbose there non-existent display detected VGA-0 (Ghost screen with wrong resolution 1360x768). it's same bug as here https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1296020 but on LTS version of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager
and in kern.log there always: Feb 15 21:13:09 volnes-TWH kernel: [ 1284.817144] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device VGA-0 Feb 15 21:13:20 volnes-TWH kernel: [ 1295.056345] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device VGA-0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1749769 Title: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager Status in nvidia-prime package in Ubuntu: New Bug description: Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. 1) Ubuntu 16.04.3 LTS 2) nvidia-prime 0.8.2 3) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia-graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot there only one active output in xrandr --verbose is LVDS. 4) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia- graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot and here you go in xrandr --verbose there non-existent display detected VGA-0 (Ghost screen with wrong resolution 1360x768). it's same bug as here https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1296020 but on LTS version of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager
And lspci ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+attachment/5055937/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1749769 Title: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager Status in nvidia-prime package in Ubuntu: New Bug description: Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. 1) Ubuntu 16.04.3 LTS 2) nvidia-prime 0.8.2 3) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia-graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot there only one active output in xrandr --verbose is LVDS. 4) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia- graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot and here you go in xrandr --verbose there non-existent display detected VGA-0 (Ghost screen with wrong resolution 1360x768). it's same bug as here https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1296020 but on LTS version of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749769] [NEW] Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager
Public bug reported: Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. 1) Ubuntu 16.04.3 LTS 2) nvidia-prime 0.8.2 3) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia-graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot there only one active output in xrandr --verbose is LVDS. 4) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia- graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot and here you go in xrandr --verbose there non-existent display detected VGA-0 (Ghost screen with wrong resolution 1360x768). it's same bug as here https://bugs.launchpad.net/ubuntu/+source/nvidia- prime/+bug/1296020 but on LTS version of ubuntu ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 nvidia packaging xenial ** Attachment added: "xrandr.txt" https://bugs.launchpad.net/bugs/1749769/+attachment/5055935/+files/xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1749769 Title: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager Status in nvidia-prime package in Ubuntu: New Bug description: Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. 1) Ubuntu 16.04.3 LTS 2) nvidia-prime 0.8.2 3) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia-graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot there only one active output in xrandr --verbose is LVDS. 4) When i enable PRIME Synchronization by set option options nvidia_390_drm modeset from '0' to '1' in /etc/modprobe.d/nvidia- graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and after reboot and here you go in xrandr --verbose there non-existent display detected VGA-0 (Ghost screen with wrong resolution 1360x768). it's same bug as here https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1296020 but on LTS version of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)
Same problem with my setup Quanta Laptop i3 2310m + Geforce GT 540M and Ubuntu 16.04.03 Package: ubuntu-drivers-common Version: 1:0.4.17.3 Screen 0: minimum 8 x 8, current 1366 x 768, maximum 16384 x 16384 VGA-0 connected 1024x768+0+0 (0x4a) normal (normal left inverted right x axis y axis) 0mm x 0mm Identifier: 0x2be Timestamp: 414965 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 1 CRTCs: 1 2 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: BorderDimensions: 4 supported: 4 Border: 0 0 0 0 range: (0, 65535) SignalFormat: VGA supported: VGA ConnectorType: VGA ConnectorNumber: 4 _ConnectorLocation: 4 1024x768 (0x4a) 65.000MHz -HSync -VSync *current +preferred h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 1360x768 (0x48) 72.000MHz +HSync -VSync h: width 1360 start 1408 end 1440 total 1520 skew0 clock 47.37KHz v: height 768 start 771 end 781 total 790 clock 59.96Hz 1360x768 (0x47) 84.750MHz -HSync +VSync h: width 1360 start 1432 end 1568 total 1776 skew0 clock 47.72KHz v: height 768 start 771 end 781 total 798 clock 59.80Hz 1152x864 (0x2bf) 81.620MHz -HSync +VSync h: width 1152 start 1216 end 1336 total 1520 skew0 clock 53.70KHz v: height 864 start 865 end 868 total 895 clock 60.00Hz 800x600 (0x2c0) 50.000MHz +HSync +VSync h: width 800 start 856 end 976 total 1040 skew0 clock 48.08KHz v: height 600 start 637 end 643 total 666 clock 72.19Hz 800x600 (0x51) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x52) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 680x384 (0x5c) 36.000MHz +HSync -VSync DoubleScan h: width 680 start 704 end 720 total 760 skew0 clock 47.37KHz v: height 384 start 385 end 390 total 395 clock 59.96Hz 680x384 (0x5b) 42.375MHz -HSync +VSync DoubleScan h: width 680 start 716 end 784 total 888 skew0 clock 47.72KHz v: height 384 start 385 end 390 total 399 clock 59.80Hz 640x480 (0x5a) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz 512x384 (0x5e) 32.500MHz -HSync -VSync DoubleScan h: width 512 start 524 end 592 total 672 skew0 clock 48.36KHz v: height 384 start 385 end 388 total 403 clock 60.00Hz 400x300 (0x2c1) 25.000MHz +HSync +VSync DoubleScan h: width 400 start 428 end 488 total 520 skew0 clock 48.08KHz v: height 300 start 318 end 321 total 333 clock 72.19Hz 320x240 (0x61) 12.587MHz -HSync -VSync DoubleScan h: width 320 start 328 end 376 total 400 skew0 clock 31.47KHz v: height 240 start 245 end 246 total 262 clock 60.05Hz LVDS-1-1 connected primary 1366x768+0+0 (0x46) normal (normal left inverted right x axis y axis) 344mm x 194mm Identifier: 0x41 Timestamp: 414965 Subpixel: horizontal rgb Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 3 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00000e14c714 09150103802213780a4e4d9e57549126 0f50540001010101010101010101 010101010101781d56c2500026303b27 360058c21018781d56c250002630 3b27360058c2101800fe0043 50540a202020202020202020 00434c414131353657423131412000e0 PRIME Synchronization: 1 supported: 0, 1 scaling mode: Full aspect supported: Full, Center, Full aspect link-status: Good supported: Good, Bad 1366x768 (0x46) 75.440MHz -HSync -VSync *current +preferred h: width 1366 start 1425 end 1464 total 1560 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 1360x768 (0x47) 84.750MHz -HSync +VSync
[Desktop-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
FWIW. I experience the same state of affairs on Ubuntu 17.10 Jan 9 00:07:13 planb colord[999]: failed to get session [pid 10836]: No data available > ps ax | grep 10836 10836 ?Ss 0:00 /usr/sbin/cupsd -l -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736775] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: покушавам да препишем дељени „/lib/udev/hwdb.d/20-sane.hwdb“, који се разликује од др
Public bug reported: I will install wine and I kant.My English ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Wed Dec 6 18:03:49 2017 ErrorMessage: покушавам да препишем дељени „/lib/udev/hwdb.d/20-sane.hwdb“, који се разликује од других примерака пакета „libsane1:i386“ InstallationDate: Installed on 2017-05-11 (209 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: покушавам да препишем дељени „/lib/udev/hwdb.d/20-sane.hwdb“, који се разликује од других примерака пакета „libsane1:i386“ UpgradeStatus: Upgraded to artful on 2017-10-22 (45 days ago) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1736775 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: покушавам да препишем дељени „/lib/udev/hwdb.d/20-sane.hwdb“, који се разликује од других примерака пакета „libsane1:i386“ Status in sane-backends package in Ubuntu: New Bug description: I will install wine and I kant.My English ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Wed Dec 6 18:03:49 2017 ErrorMessage: покушавам да препишем дељени „/lib/udev/hwdb.d/20-sane.hwdb“, који се разликује од других примерака пакета „libsane1:i386“ InstallationDate: Installed on 2017-05-11 (209 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: покушавам да препишем дељени „/lib/udev/hwdb.d/20-sane.hwdb“, који се разликује од других примерака пакета „libsane1:i386“ UpgradeStatus: Upgraded to artful on 2017-10-22 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1736775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662227] Re: Error with command "apt-get update" when using versioned "Provides:" (apt is too old to support that case)
Using: Ubuntu 14.04.5 LTS x86_64 Kernel: 3.13.0-116-generic --- Problem: LibreOffice 5.3.2.2 (1:5.3.2~rc2-0ubuntu1~trusty1) 1. PPA package libreoffice-common DEBIAN/control -> Conflicts: ..., libreoffice-l10n-5.2, ... 2. PPA package libreoffice-l10n-ru DEBIAN/control -> Provides: libreoffice-l10n-5.2 3. PPA package libreoffice-help-ru DEBIAN/control -> Provides: libreoffice-help-5.2 May be -ru or -de or -it etc. "Transaction failed: Package dependencies cannot be resolved" The update to 5.3.2.2 (1:5.3.2~rc2-0ubuntu1~trusty1) is interrupted. --- My temporary solution (example for -ru): 1. my-libreoffice-langpack-ru-reinstall.sh: #!/bin/bash sudo apt-get purge libreoffice-help-ru libreoffice-l10n-ru sudo apt-get update sudo apt-get upgrade mkdir /var/tmp/my-libreoffice-l10n-ru cd /var/tmp/my-libreoffice-l10n-ru apt-get download libreoffice-l10n-ru dpkg --extract *.deb . dpkg --control *.deb . sed -i 's/libreoffice-l10n-5.2/libreoffice-l10n-5.3/g' control fakeroot tar czf data.tar.gz usr fakeroot tar czf control.tar.gz control md5sums echo 2.0 > debian-binary ar -r my-libreoffice-l10n-ru_1%3a5.3.2~rc2-0ubuntu1~trusty1_all.deb debian-binary control.tar.gz data.tar.gz sudo dpkg -i my-libreoffice-l10n-ru_1%3a5.3.2~rc2-0ubuntu1~trusty1_all.deb mkdir /var/tmp/my-libreoffice-help-ru cd /var/tmp/my-libreoffice-help-ru apt-get download libreoffice-help-ru dpkg --extract *.deb . dpkg --control *.deb . sed -i 's/libreoffice-help-5.2/libreoffice-help-5.3/g' control fakeroot tar czf data.tar.gz usr fakeroot tar czf control.tar.gz control md5sums echo 2.0 > debian-binary ar -r my-libreoffice-help-ru_1%3a5.3.2~rc2-0ubuntu1~trusty1_all.deb debian-binary control.tar.gz data.tar.gz sudo dpkg -i my-libreoffice-help-ru_1%3a5.3.2~rc2-0ubuntu1~trusty1_all.deb 2. my-libreoffice-langpack-ru-list.sh: #!/bin/bash sudo sed -i 's/: libreoffice-l10n-5.2/: libreoffice-l10n-5.3/g' /var/lib/apt/lists/ppa.launchpad.net_libreoffice_ppa_ubuntu_dists_trusty_main_binary-amd64_Packages sudo sed -i 's/: libreoffice-help-5.2/: libreoffice-help-5.3/g' /var/lib/apt/lists/ppa.launchpad.net_libreoffice_ppa_ubuntu_dists_trusty_main_binary-amd64_Packages --- Alas, after each command 'apt-get update' run my-libreoffice-langpack-ru-list.sh again. Not yet fixed in ppa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1662227 Title: Error with command "apt-get update" when using versioned "Provides:" (apt is too old to support that case) Status in libreoffice package in Ubuntu: Triaged Bug description: I'm getting this error every time I do "apt-get update" Ign http://ni.archive.ubuntu.com trusty/multiverse Translation-en_US Ign http://ni.archive.ubuntu.com trusty/restricted Translation-en_US Ign http://ni.archive.ubuntu.com trusty/universe Translation-en_US Reading package lists... Done W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n ... ... ... ... W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n W: You may want to run apt-get update to correct these problems This error started to show after I upgraded LibreOffice form 5.2 to 5.3 with the LibreOffice PPA: ppa:libreoffice/ppa. The thing is that everything is working fine. I can update/upgrade the system, I can install packages, delete packages, etc. The problem is just with the error. I tried: "apt-get autoclean". "apt-get clean", "apt-get autoremove", apt-get install -f", and a lot of other things and nothing removes that ugly error. If I remove all PPA packages and remove the PPA itself the error goes away. This has been reported in askubuntu.com: http://askubuntu.com/questions/880447/ubuntu-14-04-error-with-apt-get-update-w-ignoring-provides-line-with-depcom http://askubuntu.com/questions/879497/apt-spewing-warnings-after- libreoffice-update Help please. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1662227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1336068] Re: Provide Option for Ensuring Scale Mode by Default
As a workaround this can be used: ~/.remmina/remmina.pref add: scale=1 to the section [remmina] This creates scaled mode as a default settings for any new connection. Enjoy ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1336068 Title: Provide Option for Ensuring Scale Mode by Default Status in remmina package in Ubuntu: New Bug description: As a frequent Remmina user, I desperately want an option to be added so that I can ensure that all new connections are scaled by default. Every time I open a new connection, the first thing I do is hit the scale button. Therefore, if there were an option to set all new connections to scale upon opening, it would save me this step numerous times per day. Here's how I use Remmina: 1) I almost always open connections at the client's resolution. 2) I always use tabs instead of full screen, so that I can tab between sessions like you'd tab between web pages in a modern browser. 3) I always scale the sessions so that they take up the full space of each tab's display area. I appreciate the magnification this provides in most cases. Since I do item 3 every time, it would very be nice if I had a user preference for setting it as default for me. Furthermore I will also suggest setting this as default generally, because I can't image anyone preferring scrolling over scaling in situations where the client's resolution is larger than the tab's available area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1336068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633912] Re: Problem with DNS resolution after suspend
** Attachment added: "dhclient.conf" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+attachment/4764469/+files/dhclient.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633912] Re: Problem with DNS resolution after suspend
Hi, I don't know, if it is a same bug, but i have problems with wired connection after boot too. When I turn on my computer (PC, not laptop) I cannot access some https sites in firefox or chromium (but in chrome i can). Or some extentions for Gnome shell (like weather) doesn't connect to server to receive data from servers. If i use sudo killall dhclient then network works correct and everything is ok, but only for some time (sometimes few minutes, sometimes hour, sometimes more). Then sometimes mess up and i must use same command to repair my connection. I made a new profile in network manager and if i use command: nmcli con up Drátové\ připojení\ 1 it work properly too, but same as with killall dhclient (so not permanently). So something with NM or dhclient is wrong. My Mobo: Asus Z170 Pro Gaming Ubuntu Gnome 16.10 64bit If you want some logs, just write and i will add attachments here for you Sorry, attachment of dhclient.conf added in #5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629610] Re: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
The mono packages have been causing a lot of problems during and after the upgrade. When I tried to remove them, apt was complaining about missing files under /usr/share/cli-common/packages.d/ that it tried to delete. I had to run the following command: touch \ '/usr/share/cli-common/packages.d/policy.2.10.atk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.10.gdk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.10.glade-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.10.glib-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.10.gtk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.10.gtk-dotnet.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.4.atk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.4.glade-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.4.glib-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.4.gtk-dotnet.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.4.gtk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.4.pango-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.atk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.gdk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.glade-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.glib-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.gtk-dotnet.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.gtk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.nunit-console-runner.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.nunit.core.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.nunit.core.interfaces.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.nunit.framework.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.nunit.mocks.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.nunit.util.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.6.pango-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.atk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.gtk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.gtk-dotnet.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.gdk-dotnet.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.gdk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.glade-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.glib-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.gtk-dotnet.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.gtk-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.8.pango-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.10.pango-sharp.installcligac' \ '/usr/share/cli-common/packages.d/policy.2.4.gdk-sharp.installcligac' \ && apt --yes remove mono-runtime -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1629610 Title: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in mono package in Ubuntu: New Bug description: I'm not sure what details to provide. The upgrade tool asked me to fill in this form, so here I am doing that. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mono-gac 4.2.1.102+dfsg2-7ubuntu4 Uname: Linux 3.19.3--grspax-ipv6-64 x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 1 23:48:19 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2013-04-26 (1254 days ago) InstallationMedia: PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: mono Title: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to xenial on 2016-10-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1629610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629610] [NEW] package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Public bug reported: I'm not sure what details to provide. The upgrade tool asked me to fill in this form, so here I am doing that. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mono-gac 4.2.1.102+dfsg2-7ubuntu4 Uname: Linux 3.19.3--grspax-ipv6-64 x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 1 23:48:19 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2013-04-26 (1254 days ago) InstallationMedia: PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: mono Title: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to xenial on 2016-10-01 (0 days ago) ** Affects: mono (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1629610 Title: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in mono package in Ubuntu: New Bug description: I'm not sure what details to provide. The upgrade tool asked me to fill in this form, so here I am doing that. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mono-gac 4.2.1.102+dfsg2-7ubuntu4 Uname: Linux 3.19.3--grspax-ipv6-64 x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 1 23:48:19 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2013-04-26 (1254 days ago) InstallationMedia: PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: mono Title: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to xenial on 2016-10-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1629610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616044] Re: System freeze after changing users
No, update of ubuntu-core-launcher package doesn't solve the problem. Aslo I noticed that sometimes I need to reenter password after returning from consoles (Ctrl+Alt+FN). And when I don't need to do that all work fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1616044 Title: System freeze after changing users Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I use Ubuntu 16.04. I have no Nvidia card, just Intel HD3000. I can work for long time with just one user. When I try to change user 2-5 times all system freeze and I can do nothing. I can switch to console with ctrl+alt+FN only after some time (one minute or something like this). I tried to kill all X and lightdm processes and stop lightdm service and restart it - it doesn't work. I can have working desktop only after reboot. I attach syslog fragment where I tried to log in as guest, got system freeze, killed all X and lightdm processes, restarted lightdm with "systemctl restart lightdm" and tried to log in as usual user. It's common for all users, not just guest. Also system freeze happen even if I not just switch users but log out and log in. I also tried to move .config/dconf and it doesn't help. May be bug somehow related to this https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1369216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1616044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616044] Re: System freeze after changing users
Seems like update of ubuntu-core-launcher package solve this bug. I will close bug after one or two days. I need to make sure that system really work properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1616044 Title: System freeze after changing users Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I use Ubuntu 16.04. I have no Nvidia card, just Intel HD3000. I can work for long time with just one user. When I try to change user 2-5 times all system freeze and I can do nothing. I can switch to console with ctrl+alt+FN only after some time (one minute or something like this). I tried to kill all X and lightdm processes and stop lightdm service and restart it - it doesn't work. I can have working desktop only after reboot. I attach syslog fragment where I tried to log in as guest, got system freeze, killed all X and lightdm processes, restarted lightdm with "systemctl restart lightdm" and tried to log in as usual user. It's common for all users, not just guest. Also system freeze happen even if I not just switch users but log out and log in. I also tried to move .config/dconf and it doesn't help. May be bug somehow related to this https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1369216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1616044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
