[Desktop-packages] [Bug 2021484] Re: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway
[Expired for ubuntu-settings (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-settings (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2021484 Title: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway Status in ubuntu-settings package in Ubuntu: Expired Bug description: I'm logged as a normal user without admin privileges. When I try to edit a VPN I'm asked to introduce the credentials of the admin, nevertheless if I click cancel I can still access to the VPN configuration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-settings 20.04.6 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 29 11:16:38 2023 InstallationDate: Installed on 2022-05-04 (389 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2021484/+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
Re: [Desktop-packages] [Bug 2033571] Re: Thunderbug hangs on trying to retrieve new email list
I have no idea of the type of email server. It is hosted by hostgo.com. I am trying to receive emails via imap. I am running 115 now (upgraded yestarday). It still won't download current messages. I did find that library libotr wasn't installed (console message) so I installed it. Still no luck. The console shows the following: services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource. Utils.sys.mjs:322 WebGL context was lost. 2 Troubleshoot.sys.mjs:710:17 I have 3 3 machines running ubuntu 22.04. The others run thunderbird fine. It is just this one that has troubles. Evolution runs OK (it's just not as good an email client). ...Michael Flower On Thu, 2023-10-05 at 13:37 +, Sebastien Bacher wrote: > Thank you for your bug report, could you provide some details on the > type of server? Could you also check if the new 115 update fixes it? > Also do you have any error printed out in the journal? > > ** Changed in: thunderbird (Ubuntu) > Importance: Undecided => Low > > ** Changed in: thunderbird (Ubuntu) > Status: New => Incomplete > -- 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/2033571 Title: Thunderbug hangs on trying to retrieve new email list Status in thunderbird package in Ubuntu: Incomplete Bug description: Connects to server Checks server capabilities Never comes back. inbox tab shows activity forever. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.13.0+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcf1530 F pulseaudio /dev/snd/controlC0: mcf1530 F pulseaudio BuildID: 20230704155023 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Aug 31 12:36:00 2023 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2023-06-03 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.181 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 MostRecentCrashID: bp-0b813420-2716-4e1f-8e16-189a30230720 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile0PrefSources: prefs.js Profile0Prefs: accessibility.typeaheadfind.flashBar: 0 (prefs.js) extensions.lastAppVersion: "102.13.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) places.database.lastMaintenance: 1693361930 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile2PrefSources: prefs.js Profile2Prefs: extensions.lastAppVersion: "115.2.0" (prefs.js) places.database.lastMaintenance: 1693433736 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile2 - LastVersion=115.2.0/20230828145448 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.13.0/20230704155023 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-0b813420-2716-4e1f-8e16-189a30230720 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version:
[Desktop-packages] [Bug 2038439] Re: Update network-manager to 1.44.2
This bug was fixed in the package network-manager - 1.44.2-1ubuntu1 --- network-manager (1.44.2-1ubuntu1) mantic; urgency=medium * Merge with Debian (LP: #2038439) network-manager (1.44.2-1) unstable; urgency=medium * New upstream version 1.44.2 * Rebase patches -- Jeremy Bícha Wed, 04 Oct 2023 09:40:22 -0400 ** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Released -- 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/2038439 Title: Update network-manager to 1.44.2 Status in network-manager package in Ubuntu: Fix Released Bug description: New upstream bugfix release in the stable 1.44 series https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/compare/1.44.0...1.44.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2038439/+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 2038656] Re: Proxy settings are changed after switching off
Great, let's consider that as resolved in 23.10 ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038656 Title: Proxy settings are changed after switching off Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Preconditions: - Having an access to a actual http(s) proxy would allow to perform test with actual network traffic, but the bug is reproducible without it. Steps to reproduce: 1. Go to Settings -> Network -> Proxy 2a. Switch on the proxy 2b. Change proxy configuration to manual 2c. Set http and https proxy ip and port 2d. Make sure there are multiple entries on a list of ignored hosts, for example: localhost,127.0.0.0/8,::1 2e. Press end. 3. If it is possible make sure that the proxy settings have been apllied 4a. Turn off the proxy. 4b. Please tests with proxy settings page left open in a background and with settings closed. 5. Wait. I have not got the time to measure how much time is exactly needed. 5 minutes should be alright. 6. Go to proxy settings and switch ut on. Expected reult: Settings remain the same. Configuration is set to "manual" and ignored host list did not change. Actual result: Proxy settings were changed. Configuration is again "automatic" and there are extra commas on ignored hosts list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038656/+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 2038681] Re: nvidia-driver-535.113.01 crash
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (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/2038681 Title: nvidia-driver-535.113.01 crash Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: It was running RealVNC server, VMware Workstation Pro with Windows 11 guest, Firefox and Thunderbird. I used it with RealVNC Viewer on another machine and suddenly my VNC connection dropped. Coming to my nVIDIA laptop it was showing no gnome desktop anymore but a black screen. I could still ssh to the laptop to trigger a reboot. Via journalctl I saw that nVIDIA driver had crashed. I have seen this now with both 535.113.01-0ubuntu0.23.04.1 535.113.01-0ubuntu0.23.04.3 Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): recover... Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(GPU-0): Failed to initialize DMA. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Failed to allocate push buffer Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Error recovery failed. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): *** Aborting *** Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: Fatal server error: Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Failed to recover from error! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12 19:41:24 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: GNOME Date: Fri Oct 6 19:12:16 2023 DistUpgraded: 2023-04-14 13:11:36,442 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/535.113.01, 6.2.0-33-generic, x86_64: installed nvidia/535.113.01, 6.2.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3f8c] InstallationDate: Installed on 2021-05-17 (871 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 81Y6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=998a3bca-88e2-4d44-ab68-6776750daa09 ro nvidia-drm.modeset=1 acpi_backlight=native nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to lunar on 2023-04-14 (175 days ago) dmi.bios.date: 06/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: EFCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15IMH05H dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrEFCN59WW:bd06/09/2023:br1.59:efr1.59:svnLENOVO:pn81Y6:pvrLenovoLegion515IMH05H:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegion515IMH05H:skuLENOVO_MT_81Y6_BU_idea_FM_Legion515IMH05H: dmi.product.family: Legion 5 15IMH05H dmi.product.name: 81Y6 dmi.product.sku: LENOVO_MT_81Y6_BU_idea_FM_Legion 5 15IMH05H dmi.product.version: Lenovo Legion 5 15IMH05H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 2024377] Re: Adsys can't fetch GPOs
root@LCXVDU22NPE4030:~# export KRB5CCNAME=/var/run/adsys/krb5cc/LCXVDU22NPE4030
adsysctl policy debug gpolist-script
chmod +x adsys-gpolist
./adsys-gpolist --objectclass computer ldap://N060ADKCDC109.domain.com
LCXVDU22NPE4030
00cEntCTX-Ubuntu-Edge
smb://domain.com/SysVol/domain.com/Policies/{F7E97A8D-7DB1-4571-956A-005D1658DC35}
00cEntCtx-Ubuntu-Test
smb://domain.com/SysVol/domain.com/Policies/{5B925A10-9572-4FB8-B9A0-DB2DFF9EF34B}
root@LCXVDU22NPE4030:~# smbclient --option='log level=10'
//N060ADKCDC109.domain.com/SYSVOL/ -k -c 'get
domain.com/Policies/{5B925A10-9572-4FB8-B9A0-DB2DFF9EF34B}/GPT.INI /dev/fd/1' |
cat
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
auth_audit: 10
auth_json_audit: 10
kerberos: 10
drs_repl: 10
smb2: 10
smb2_credits: 10
dsdb_audit: 10
dsdb_json_audit: 10
dsdb_password_audit: 10
dsdb_password_json_audit: 10
dsdb_transaction_audit: 10
dsdb_transaction_json_audit: 10
dsdb_group_audit: 10
dsdb_group_json_audit: 10
WARNING: The option -k|--kerberos is deprecated!
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
auth_audit: 10
auth_json_audit: 10
kerberos: 10
drs_repl: 10
smb2: 10
smb2_credits: 10
dsdb_audit: 10
dsdb_json_audit: 10
dsdb_password_audit: 10
dsdb_password_json_audit: 10
dsdb_transaction_audit: 10
dsdb_transaction_json_audit: 10
dsdb_group_audit: 10
dsdb_group_json_audit: 10
Processing section "[global]"
doing parameter workgroup = domain
doing parameter security = ADS
doing parameter realm = domain.COM
doing parameter encrypt passwords = yes
lpcfg_do_global_parameter: WARNING: The "encrypt passwords" option is deprecated
doing parameter idmap config *:range = 16777216-33554431
doing parameter winbind use default domain = yes
doing parameter kerberos method = secrets and keytab
doing parameter winbind refresh tickets = yes
doing parameter template shell = /bin/bash
pm_process() returned Yes
lp_servicenumber: couldn't find homes
added interface eth0 ip=10.34.204.247 bcast=10.34.207.255 netmask=255.255.252.0
Client started (version 4.15.13-Ubuntu).
Opening cache file at /run/samba/gencache.tdb
sitename_fetch: Returning sitename for realm 'domain.COM': "703-XX001"
internal_resolve_name: looking up N060ADKCDC109.domain.com#20 (sitename
703-XX001)
namecache_fetch: name N060ADKCDC109.domain.com#20 found.
remove_duplicate_addrs2: looking for duplicate address/port pairs
Connecting to 10.254.163.93 at port 445
convert_string_handle: E2BIG: convert_string(UTF-8,CP850): srclen=25 destlen=16
error: No more room
Connecting to 10.254.163.93 at port 139
socket options: SO_KEEPALIVE=0, SO_REUSEADDR=0, SO_BROADCAST=0, TCP_NODELAY=1,
TCP_KEEPCNT=9, TCP_KEEPIDLE=7200, TCP_KEEPINTVL=75, IPTOS_LOWDELAY=0,
IPTOS_THROUGHPUT=0, SO_REUSEPORT=0, SO_SNDBUF=87040, SO_RCVBUF=131072,
SO_SNDLOWAT=1, SO_RCVLOWAT=1, SO_SNDTIMEO=0, SO_RCVTIMEO=0, TCP_QUICKACK=1,
TCP_DEFER_ACCEPT=0, TCP_USER_TIMEOUT=0
session request ok
negotiated dialect[SMB3_11] against server[N060ADKCDC109.domain.com]
cli_session_setup_spnego_send: Connect to N060ADKCDC109.domain.com as
LCXVDU22NPE4030$@domain.COM using SPNEGO
GENSEC backend 'gssapi_spnego' registered
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'spnego' registered
GENSEC backend 'schannel' registered
GENSEC backend 'naclrpc_as_system' registered
GENSEC backend 'sasl-EXTERNAL' registered
GENSEC backend 'ntlmssp' registered
GENSEC backend 'ntlmssp_resume_ccache' registered
GENSEC backend 'http_basic' registered
GENSEC backend 'http_ntlm' registered
GENSEC backend 'http_negotiate' registered
GENSEC backend 'krb5' registered
GENSEC backend 'fake_gssapi_krb5' registered
Starting GENSEC mechanism spnego
Starting GENSEC submechanism gse_krb5
gensec_update_send: gse_krb5[0x55f4ae1acd70]: subreq: 0x55f4ae1909a0
gensec_update_send: spnego[0x55f4ae1a6030]: subreq: 0x55f4ae1ab820
gensec_update_done: gse_krb5[0x55f4ae1acd70]:
NT_STATUS_MORE_PROCESSING_REQUIRED
tevent_req[0x55f4ae1909a0/../../source3/librpc/crypto/gse.c:848]: state[2]
error[0 (0x0)] state[struct gensec_gse_update_state (0x55f4ae190b60)]
timer[(nil)] finish[../../source3/librpc/crypto/gse.c:859]
gensec_update_done: spnego[0x55f4ae1a6030]: NT_STATUS_MORE_PROCESSING_REQUIRED
[Desktop-packages] [Bug 2033688] Re: [mantic] gnome-shell fails to follow accent colours
** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** No longer affects: yaru-theme (Ubuntu) ** No longer affects: yaru-theme (Ubuntu Mantic) -- 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/2033688 Title: [mantic] gnome-shell fails to follow accent colours Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Mantic: Triaged Bug description: When accent colors are selected in gnome-control-center, gnome-shell fails to follow with the exception of blue and orange. Screenshots attached. Test Case - 1. Open the Settings app 2. Switch to the Appearance page 3. Choose the Purple color 4. Click the quick settings area in the far right side of GNOME Shell's top bar 5. The highlights should be purple What Happens Instead The highlights are still orange ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 31 13:50:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-04 (180 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2033688/+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 2038681] [NEW] nvidia-driver-535.113.01 crash
Public bug reported: It was running RealVNC server, VMware Workstation Pro with Windows 11 guest, Firefox and Thunderbird. I used it with RealVNC Viewer on another machine and suddenly my VNC connection dropped. Coming to my nVIDIA laptop it was showing no gnome desktop anymore but a black screen. I could still ssh to the laptop to trigger a reboot. Via journalctl I saw that nVIDIA driver had crashed. I have seen this now with both 535.113.01-0ubuntu0.23.04.1 535.113.01-0ubuntu0.23.04.3 Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to Oct 06 17:01:57 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): recover... Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(GPU-0): Failed to initialize DMA. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Failed to allocate push buffer Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): Error recovery failed. Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) NVIDIA(0): *** Aborting *** Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: Fatal server error: Oct 06 17:02:37 legion5ubuntu /usr/libexec/gdm-x-session[3110]: (EE) Failed to recover from error! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12 19:41:24 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: GNOME Date: Fri Oct 6 19:12:16 2023 DistUpgraded: 2023-04-14 13:11:36,442 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/535.113.01, 6.2.0-33-generic, x86_64: installed nvidia/535.113.01, 6.2.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3f8c] InstallationDate: Installed on 2021-05-17 (871 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 81Y6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=998a3bca-88e2-4d44-ab68-6776750daa09 ro nvidia-drm.modeset=1 acpi_backlight=native nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to lunar on 2023-04-14 (175 days ago) dmi.bios.date: 06/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: EFCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15IMH05H dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrEFCN59WW:bd06/09/2023:br1.59:efr1.59:svnLENOVO:pn81Y6:pvrLenovoLegion515IMH05H:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegion515IMH05H:skuLENOVO_MT_81Y6_BU_idea_FM_Legion515IMH05H: dmi.product.family: Legion 5 15IMH05H dmi.product.name: 81Y6 dmi.product.sku: LENOVO_MT_81Y6_BU_idea_FM_Legion 5 15IMH05H dmi.product.version: Lenovo Legion 5 15IMH05H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lunar ubuntu -- You received this bug notification because you are a member of Desktop
[Desktop-packages] [Bug 2038679] [NEW] gnome-shell-extension-ubuntu-dock crashes ubuntu 20.04 when i return from the folder ALWAYS
Public bug reported: when i open the launcher to any folder and clicked on outside the folder itself it freezes the screen of my computer that requires me a reboot from the black screen when : CTRL + ALT + F3 is clicked on the keyboard and displays both frequent and all sections ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: when i open the launcher to any folder and clicked on outside the folder itself it freezes the screen of my computer that requires me a - reboot from the black screen when : CTRL + ALT + F3 is clicked + reboot from the black screen when : CTRL + ALT + F3 is clicked on the + keyboard and displays both frequent and all sections -- 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/2038679 Title: gnome-shell-extension-ubuntu-dock crashes ubuntu 20.04 when i return from the folder ALWAYS Status in gnome-shell package in Ubuntu: New Bug description: when i open the launcher to any folder and clicked on outside the folder itself it freezes the screen of my computer that requires me a reboot from the black screen when : CTRL + ALT + F3 is clicked on the keyboard and displays both frequent and all sections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2038679/+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 2038670] [NEW] Gnome crashes and forces logout.
Public bug reported: While using only Chrome gnome-shell crashes and forces me to logout. Usually restart is needed too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 17:38:14 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-06 (1095 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2038670 Title: Gnome crashes and forces logout. Status in gnome-shell package in Ubuntu: New Bug description: While using only Chrome gnome-shell crashes and forces me to logout. Usually restart is needed too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 17:38:14 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-06 (1095 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/2038670/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
No, it is not a bug, hardware decoding for video conferencing on google meet only works for very few specific use cases, -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the Chromium snap from either beta or edge channels, sudo snap install --beta chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples. 4.Check with intel_gpu_top (from intel-gpu-tools package) that the video engine bars are non zero during playback. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I can confirm @cmmrandau findings. mutter 45.0-3ubuntu 3 does not fix the bug but Martin's workaround works for me. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2038669] [NEW] Add Raspberry Pi 5 support
Public bug reported: placeholder ** Affects: libcamera (Ubuntu) Importance: Undecided Status: New ** Affects: libcamera (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: libcamera (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/2038669 Title: Add Raspberry Pi 5 support Status in libcamera package in Ubuntu: New Status in libcamera source package in Mantic: New Bug description: placeholder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2038669/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Indeed, chromim-beta has hardware video acceleration. All videos on youtube are accelerated. But this is not observed in video conferences. Verified in Google Meet. Is this a bug? -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the Chromium snap from either beta or edge channels, sudo snap install --beta chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples. 4.Check with intel_gpu_top (from intel-gpu-tools package) that the video engine bars are non zero during playback. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Changed in: mutter (Ubuntu Mantic) Status: Fix Released => Triaged -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I can confirm @cmmrandau findings. mutter 45.0-3ubuntu 3 does not fix the bug but Martin's workaround works for me. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2038665] [NEW] bluetooth not working proper; ly
Public bug reported: My bluetooth it's loosing connection every 3 or 4 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:21:08 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=9828ca97-751b-4832-b775-db6c7dab004d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx: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: ASUS hciconfig: hci0: Type: Primary Bus: USB BD Address: 2C:0D:A7:1D:E9:2F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2128 acl:114 sco:417074 events:3840 errors:0 TX bytes:24227828 acl:3643 sco:414720 commands:147 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/2038665 Title: bluetooth not working proper;ly Status in bluez package in Ubuntu: New Bug description: My bluetooth it's loosing connection every 3 or 4 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:21:08 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=9828ca97-751b-4832-b775-db6c7dab004d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx: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: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 2C:0D:A7:1D:E9:2F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2128 acl:114 sco:417074 events:3840 errors:0 TX bytes:24227828 acl:3643 sco:414720 commands:147 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2038665/+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 2037497]
FEDORA-2023-86e10b6cae has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-86e10b6cae` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-86e10b6cae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Fix Committed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
FEDORA-2023-86e10b6cae has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-86e10b6cae -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Fix Committed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
Thanks James, I've sent an official update as you can see. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Fix Committed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
Scratch build is done for x86_64: https://koji.fedoraproject.org/koji/taskinfo?taskID=107101328 can folks test that and see if it helps? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Fix Committed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497] Re: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
** Changed in: mesa (Fedora) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Fix Committed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
(In reply to Adam Williamson from comment #20) > Scratch build is done for x86_64: > https://koji.fedoraproject.org/koji/taskinfo?taskID=107101328 > > can folks test that and see if it helps? Thanks! Works after updating to the packages in that Koji task. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Fix Committed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
Some upstream discussion indicates https://gitlab.freedesktop.org/mesa/mesa/-/commit/9590bce3e249a34665b2c42b20bfdbdc7f32147f may fix this. Setting POST, will do a scratch build for folks to test shortly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Fix Committed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Just updated and mutter 45.0-3ubuntu3 does not fix this error. Still crash when lock screen and works with MUTTER_DEBUG_KMS_THREAD_TYPE=user added to /etc/environment -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Fix Released Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2038656] Re: Proxy settings are changed after switching off
It does seam similar to that GNOME bug. I am using the 23.04, so I guess I will be able to test the fix soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038656 Title: Proxy settings are changed after switching off Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Preconditions: - Having an access to a actual http(s) proxy would allow to perform test with actual network traffic, but the bug is reproducible without it. Steps to reproduce: 1. Go to Settings -> Network -> Proxy 2a. Switch on the proxy 2b. Change proxy configuration to manual 2c. Set http and https proxy ip and port 2d. Make sure there are multiple entries on a list of ignored hosts, for example: localhost,127.0.0.0/8,::1 2e. Press end. 3. If it is possible make sure that the proxy settings have been apllied 4a. Turn off the proxy. 4b. Please tests with proxy settings page left open in a background and with settings closed. 5. Wait. I have not got the time to measure how much time is exactly needed. 5 minutes should be alright. 6. Go to proxy settings and switch ut on. Expected reult: Settings remain the same. Configuration is set to "manual" and ignored host list did not change. Actual result: Proxy settings were changed. Configuration is again "automatic" and there are extra commas on ignored hosts list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038656/+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 2038656] Re: Proxy settings are changed after switching off
It seems similar to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/2401 upstream which should be fixed in the current Ubuntu serie -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038656 Title: Proxy settings are changed after switching off Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Preconditions: - Having an access to a actual http(s) proxy would allow to perform test with actual network traffic, but the bug is reproducible without it. Steps to reproduce: 1. Go to Settings -> Network -> Proxy 2a. Switch on the proxy 2b. Change proxy configuration to manual 2c. Set http and https proxy ip and port 2d. Make sure there are multiple entries on a list of ignored hosts, for example: localhost,127.0.0.0/8,::1 2e. Press end. 3. If it is possible make sure that the proxy settings have been apllied 4a. Turn off the proxy. 4b. Please tests with proxy settings page left open in a background and with settings closed. 5. Wait. I have not got the time to measure how much time is exactly needed. 5 minutes should be alright. 6. Go to proxy settings and switch ut on. Expected reult: Settings remain the same. Configuration is set to "manual" and ignored host list did not change. Actual result: Proxy settings were changed. Configuration is again "automatic" and there are extra commas on ignored hosts list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038656/+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 2038656] Re: Proxy settings are changed after switching off
Thank you for your bug report. What Ubuntu serie do you use? Is the 'wait' in 5 making a difference? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2401 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2401 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038656 Title: Proxy settings are changed after switching off Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Preconditions: - Having an access to a actual http(s) proxy would allow to perform test with actual network traffic, but the bug is reproducible without it. Steps to reproduce: 1. Go to Settings -> Network -> Proxy 2a. Switch on the proxy 2b. Change proxy configuration to manual 2c. Set http and https proxy ip and port 2d. Make sure there are multiple entries on a list of ignored hosts, for example: localhost,127.0.0.0/8,::1 2e. Press end. 3. If it is possible make sure that the proxy settings have been apllied 4a. Turn off the proxy. 4b. Please tests with proxy settings page left open in a background and with settings closed. 5. Wait. I have not got the time to measure how much time is exactly needed. 5 minutes should be alright. 6. Go to proxy settings and switch ut on. Expected reult: Settings remain the same. Configuration is set to "manual" and ignored host list did not change. Actual result: Proxy settings were changed. Configuration is again "automatic" and there are extra commas on ignored hosts list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038656/+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 2033440] Re: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"
We're not going to change the ubuntu-desktop metapackage to allow switching to pulseaudio for Ubuntu 23.10. There was a pipewire 1.0 RC (versioned as 0.3.81) release today with further JACK improvements. That version is too late for Ubuntu 23.10 but it will be in Ubuntu 24.04 LTS. https://gitlab.freedesktop.org/pipewire/pipewire/-/releases I'm curious if pipewire will be good enough for Ubuntu 24.04 LTS for professional audio users. It is much easier and more reliable to simply depend on pipewire-audio, especially since we need to upgrade people from Ubuntu 22.04 LTS which had pulseaudio as default. Trying to allow people to intentionally opt out also means that people can accidentally end up with the option that is not our recommended audio server. ** Tags removed: rls-mm-incoming ** Tags added: rls-mm-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2033440 Title: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio" Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Lunar: Won't Fix Bug description: Recommend demoting pipewire-audio from Depends: to Recommends:. Reason: While it's not ideal, the Ubuntu Desktop can still function on the pulseaudio backend rather than using the direct pipewire-alsa backend which conflicts with the pulseaudio package. This would help people who wish to have a more traditional JACK setup that is bridged to pulseaudio. Right now, this setup is incompatible. Original description: I have installed successfully the standard Ubuntu 23.04 (on a 500 GB external USB drive). Immediately after the installation, I have also installed with apt the "ubuntustudio-installer" package. In the dialog provided by the ubuntustudio-installer, I have selected the following metapackages: - linux-lowlatency - ubuntustudio-lowlatency-settings - ubuntustudio-performance-tweaks - ubuntustudio-audio - ubuntu-pulseaudio-config and pressed "Modify installed Package Selection" After a while a "qaptbatch" dialog has appeared with title "Commit Error" and message "An error occurred while applying changes" So the installation has failed. Then I have tried to manually install each metapackage in the list above with apt and every package was installed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+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 2038656] [NEW] Proxy settings are changed after switching off
Public bug reported: Preconditions: - Having an access to a actual http(s) proxy would allow to perform test with actual network traffic, but the bug is reproducible without it. Steps to reproduce: 1. Go to Settings -> Network -> Proxy 2a. Switch on the proxy 2b. Change proxy configuration to manual 2c. Set http and https proxy ip and port 2d. Make sure there are multiple entries on a list of ignored hosts, for example: localhost,127.0.0.0/8,::1 2e. Press end. 3. If it is possible make sure that the proxy settings have been apllied 4a. Turn off the proxy. 4b. Please tests with proxy settings page left open in a background and with settings closed. 5. Wait. I have not got the time to measure how much time is exactly needed. 5 minutes should be alright. 6. Go to proxy settings and switch ut on. Expected reult: Settings remain the same. Configuration is set to "manual" and ignored host list did not change. Actual result: Proxy settings were changed. Configuration is again "automatic" and there are extra commas on ignored hosts list. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038656 Title: Proxy settings are changed after switching off Status in gnome-control-center package in Ubuntu: New Bug description: Preconditions: - Having an access to a actual http(s) proxy would allow to perform test with actual network traffic, but the bug is reproducible without it. Steps to reproduce: 1. Go to Settings -> Network -> Proxy 2a. Switch on the proxy 2b. Change proxy configuration to manual 2c. Set http and https proxy ip and port 2d. Make sure there are multiple entries on a list of ignored hosts, for example: localhost,127.0.0.0/8,::1 2e. Press end. 3. If it is possible make sure that the proxy settings have been apllied 4a. Turn off the proxy. 4b. Please tests with proxy settings page left open in a background and with settings closed. 5. Wait. I have not got the time to measure how much time is exactly needed. 5 minutes should be alright. 6. Go to proxy settings and switch ut on. Expected reult: Settings remain the same. Configuration is set to "manual" and ignored host list did not change. Actual result: Proxy settings were changed. Configuration is again "automatic" and there are extra commas on ignored hosts list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038656/+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 2033440] Re: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"
** Changed in: ubuntu-meta (Ubuntu Mantic) Status: New => Won't Fix ** No longer affects: ubuntu-meta (Ubuntu Mantic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2033440 Title: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio" Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Lunar: Won't Fix Bug description: Recommend demoting pipewire-audio from Depends: to Recommends:. Reason: While it's not ideal, the Ubuntu Desktop can still function on the pulseaudio backend rather than using the direct pipewire-alsa backend which conflicts with the pulseaudio package. This would help people who wish to have a more traditional JACK setup that is bridged to pulseaudio. Right now, this setup is incompatible. Original description: I have installed successfully the standard Ubuntu 23.04 (on a 500 GB external USB drive). Immediately after the installation, I have also installed with apt the "ubuntustudio-installer" package. In the dialog provided by the ubuntustudio-installer, I have selected the following metapackages: - linux-lowlatency - ubuntustudio-lowlatency-settings - ubuntustudio-performance-tweaks - ubuntustudio-audio - ubuntu-pulseaudio-config and pressed "Modify installed Package Selection" After a while a "qaptbatch" dialog has appeared with title "Commit Error" and message "An error occurred while applying changes" So the installation has failed. Then I have tried to manually install each metapackage in the list above with apt and every package was installed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+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 2037503] Re: [jammy]backport #1453 from upstream
Why would they go to the command line rather than switching to performance from the top panel indicator or the settings? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037503 Title: [jammy]backport #1453 from upstream Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-control-center package in Debian: New Bug description: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in Snap Store Server: New Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapstore-server/+bug/2038609/+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 2037503] Re: [jammy]backport #1453 from upstream
The selector defaults to balance, but an inexperienced gamer or a desparate power user may force the performance profile via the command line, despite the fact gnome-control-center thinks it is not available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037503 Title: [jammy]backport #1453 from upstream Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-control-center package in Debian: New Bug description: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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 2037497] Re: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
** Changed in: mesa (Ubuntu) Milestone: mantic-updates => ubuntu-23.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2024377] Re: Adsys can't fetch GPOs
Thanks for getting back. Noticing a couple of things about your pasted output:
- Did you run the first set of commands in a root session? This is necessary
because the user needs to be able to read the
`/var/run/adsys/krb5cc/$(hostname)` file. You can confirm this by trying to
`cat` the file - it shouldn't give you a Permission denied error.
- The export command looks a bit wrong, we need
`KRB5CCNAME=/var/run/adsys/krb5cc/$(hostname)` since `hostname` is a
shell command. You can confirm that the variable is set correctly by
running klist (provided by the krb5-user package). See an example below:
root@jammy-337515ec:~# export KRB5CCNAME=/var/run/adsys/krb5cc/jammy-337515ec
root@jammy-337515ec:~# klist
Ticket cache: FILE:/var/run/adsys/krb5cc/jammy-337515ec
Default principal: JAMMY-337515EC$@DOMAIN.COM
- You ran `smbclient` with sudo - unfortunately sudo does not preserve
environment variables which is why the KRB5CCNAME value defaults to
`FILE:/tmp/krb5cc_0` (as seen from the second command logs). This is why
I suggested running everything as root. Or, pass the -E flag to sudo in
order to preserve environment variables.
If there's no file at `/var/run/adsys/krb5cc/$(hostname)`, please run `adsysctl
update -m` as root and it should be created (even if the command fails).
Thanks for your patience, and let me know how this goes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Confirmed
Bug description:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums,
Reddit or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
backend, I can log with Active Directory users however when adsys is
installed I can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get
policies for "ubuntu": can't download all gpos and assets: one or more
error while fetching GPOs and assets: can't download "ubuntuRoot":
can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
After upgrade to 23.04 the error persist same as the above.
Full info 22.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
We will only use the defaults, env variables or flags.
DEBUG Connecting as [[2504:109556]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
DEBUG Analyzing "assets"
DEBUG Analyzing "ubuntuRoot"
INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
Full info 23.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
DEBUG Connecting as [[58811:006019]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as
[Desktop-packages] [Bug 2037497] Re: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
I'll add that patch to mantic now, as it would take some time to get it via a bugfix release ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
I cannot reproduce it. Given the nature of the error this must be something in Snapd or in the Snapstore. Are you able to install the snap from a different channel, say, snap install --candidate chromium ? Are you able to install different snaps? ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: snapstore-server Importance: Undecided Status: New -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in Snap Store Server: New Status in chromium-browser package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapstore-server/+bug/2038609/+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
Re: [Desktop-packages] [Bug 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status
On Fri, 6 Oct 2023, Nathan Teodosio wrote: >> - Fetch and check assertions for snap "chromium" (2642) (cannot verify > snap "chromium", no matching signatures found) > > Looks like a transient failure, could you please try again? I tried at least four times, twice after a reboot, same error each time. David Lang -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038609/+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
Re: [Desktop-packages] [Bug 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status
On Fri, 6 Oct 2023, David Lang wrote: > On Fri, 6 Oct 2023, Nathan Teodosio wrote: > >>> - Fetch and check assertions for snap "chromium" (2642) (cannot verify >> snap "chromium", no matching signatures found) >> >> Looks like a transient failure, could you please try again? > > I tried at least four times, twice after a reboot, same error each time. still reporting unable to validate the snap, no matching signatures (and I did do apt update to make sure I had the latest) David Lang -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038609/+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 2037642] Re: [FFe] Raspberry Pi 5 support
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: New Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Thank you, Nathan Teodosio. I installed chromium as described here: https://discourse.ubuntu.com/t/chromium-hardware-accelerated-build-for-intel-based-platforms-available-for-beta-testing/35625?u=d0od That is, like this: To install hardware accelerated Chromium: snap install chromium --channel=latest/candidate/hwacc Maybe it should have been this way? snap install --channel candidate/hwacc chromium -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the Chromium snap from either beta or edge channels, sudo snap install --beta chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples. 4.Check with intel_gpu_top (from intel-gpu-tools package) that the video engine bars are non zero during playback. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
** Changed in: gnome-shell
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2016217
Title:
gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
from GjsAutoPointer()
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Confirmed
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
44.0-2ubuntu3, the problem page at
https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9
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/.
#0 0x7f3aa429dd82 in clutter_actor_remove_effect
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at
../clutter/clutter/clutter-actor.c:14830
__inst = 0x55d6101c48a0
__t = 94377826055744
__r =
_g_boolean_var_274 =
__func__ = "clutter_actor_remove_effect"
#1 0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at
../src/st/st-scroll-view.c:246
priv = 0x55d60fa59a00
#2 0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at
../../../gobject/gobject.c:3891
_pp =
gaig_temp =
gaig_temp =
weak_locations =
nqueue = 0x55d60fa6da60
_ptr =
object = 0x55d60fa59e90
old_ref =
retry_atomic_decrement1 =
__func__ = "g_object_unref"
#3 0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
old_ptr =
#4 GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::~GjsAutoPointer (this=, this=) at
../gjs/jsapi-util.h:172
No locals.
#5 GjsSmartPointer<_GObject>::~GjsSmartPointer (this=,
this=) at ../gjs/jsapi-util.h:349
No locals.
#6 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
No locals.
#7 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
No locals.
#8 0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
was_using_toggle_refs = false
had_toggle_up = false
had_toggle_down =
had_toggle_up =
had_toggle_down =
was_using_toggle_refs =
#9 GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
No locals.
#10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820,
this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6
"StScrollView", class_size = 664, instance_size = 48}
query =
_g_boolean_var_74 =
#11 GIWrapperBase::finalize
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
priv = 0x55d60fa0ce80
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2016217/+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 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
> - Fetch and check assertions for snap "chromium" (2642) (cannot verify snap "chromium", no matching signatures found) Looks like a transient failure, could you please try again? -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038609/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hi Peter, thanks, the bug description was not up to date, you need the snap from beta or edge. What is 'snap info chromium' for you? If it doesn't work on those channels, please attach snap run chromium --enable-logging=stderr &> chr.log ** Description changed: To test the snap with VA-API changes, - 1. Install the Chromium snap, + 1. Install the Chromium snap from either beta or edge channels, - sudo snap install --channel candidate/hwacc chromium + sudo snap install --beta chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video-media- samples. - 4. Enter about:media-internals in the address bar, click the - corresponding box (if the video is playing, it will have the "(kPlay)" - identifier) and note if the page says VaapiVideoDecoder for - kVideoDecoderName. You can alternatively check with intel_gpu_top (from - intel-gpu-tools package) that the video engine bars are non zero during - playback. + 4.Check with intel_gpu_top (from intel-gpu-tools package) that the video + engine bars are non zero during playback. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the Chromium snap from either beta or edge channels, sudo snap install --beta chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples. 4.Check with intel_gpu_top (from intel-gpu-tools package) that the video engine bars are non zero during playback. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 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 1816497] Re: [snap] vaapi chromium no video hardware decoding
CPU: 12th Gen Intel i5-12400 (12) @ 4.400GHz GPU: Intel Alder Lake-S GT1 [UHD Graphics 730] intel_gpu_top shows 0% Kubuntu 23.04 -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the Chromium snap, sudo snap install --channel candidate/hwacc chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples. 4. Enter about:media-internals in the address bar, click the corresponding box (if the video is playing, it will have the "(kPlay)" identifier) and note if the page says VaapiVideoDecoder for kVideoDecoderName. You can alternatively check with intel_gpu_top (from intel-gpu-tools package) that the video engine bars are non zero during playback. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 2038609] [NEW] package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
Public bug reported: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038609/+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
