[Desktop-packages] [Bug 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working
This is still affecting me @23.04 Lunar Lobster -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1954628 Title: [USB-Audio - ALC4080] Front panel: Headphone output not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working
Also affects Jammy. Unfortunately my work around script doesn't work anymore due to the Audio plumbing having been changed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1954628 Title: [USB-Audio - ALC4080] Front panel: Headphone output not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working
Also affects Jammy. Unfortunately my work around script doesn't work anymore due to the Audio plumbing having been changed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1954628 Title: [USB-Audio - ALC4080] Front panel: Headphone output not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working
** Summary changed: - [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly + [USB-Audio - ALC4080] Front panel: Headphone output not working ** Description changed: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard - 'Starship/Matisse HD Audio Controller' controller that has a weird - mapping via USB audio (see bug: + 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) + controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. - After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. - Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. + After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. + Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: gijs 2129 F pulseaudio - /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio - /dev/snd/controlC0: gijs 2129 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: gijs 2129 F pulseaudio + /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio + /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1954628 Title: [USB-Audio - ALC4080] Front panel: Headphone output not working Status in alsa-driver package in Ubuntu: New Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base
[Desktop-packages] [Bug 1954628] [NEW] [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly
Public bug reported: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1954628 Title: [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly Status in alsa-driver package in Ubuntu: New Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card:
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
Confirming this bug, also affects me. We need an hotfix ASAP as this also leads to unbootable computers if root fs fills up (boot process hangs on starting of GDM, which might need to create some files). Had system locked from thursday afternoon till this morning, 38 gig syslog, completely filling the root partition. root@gijs-desktop:/var/log# tail -n60 syslog Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #4 0x7ffe182c1770 b resource:///org/gnome/shell/ui/layout.js:531 (0x7fd5e05042b8 @ 127) Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #5 0x7ffe182c17e0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #6 0x7ffe182c17e0 I self-hosted:915 (0x7fd5e06f12b8 @ 367) Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: == Stack trace for context 0x5570af9fa320 == Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #0 Jul 30 08:55:54 gijs-desktop gnome-shell[1949]: Object St.Button (0x5570b37372f0), has been already finalized. Impossible to set any property to it. Jul 30 08:55:54 gijs-desktop gnome-shell[1949]: Object St.Button (0x5570b37372f0), has been already finalized. Impossible to set any property to it. Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: == Stack trace for context 0x5570af9fa320 == Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #0 0x5570afe1a580 i resource:///org/gnome/shell/ui/messageList.js:504 (0x7fd5e05b4de0 @ 83) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #1 0x7ffe182b8480 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #2 0x7ffe182b8550 b self-hosted:917 (0x7fd5e06f12b8 @ 394) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #3 0x5570afe1a4f0 i resource:///org/gnome/shell/ui/messageTray.js:1461 (0x7fd5e05a2a28 @ 121) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #4 0x7ffe182ba4d0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #5 0x5570afe1a448 i resource:///org/gnome/shell/ui/messageTray.js:1448 (0x7fd5e05a29a0 @ 406) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #6 0x7ffe182bb0b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #7 0x5570afe1a390 i resource:///org/gnome/shell/ui/messageTray.js:1249 (0x7fd5e05a2340 @ 729) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #8 0x7ffe182bbc90 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #9 0x5570afe1a2f8 i resource:///org/gnome/shell/ui/messageTray.js:1067 (0x7fd5e05a0e68 @ 124) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #10 0x7ffe182bc880 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #11 0x7ffe182bc950 b self-hosted:917 (0x7fd5e06f12b8 @ 394) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #12 0x7ffe182bca40 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5e06d3230 @ 386) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #13 0x5570afe1a268 i resource:///org/gnome/shell/ui/messageTray.js:487 (0x7fd5e059dc48 @ 50) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #14 0x7ffe182bd6a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #15 0x5570afe1a1e8 i resource:///org/gnome/shell/ui/calendar.js:775 (0x7fd5e05aad58 @ 44) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #16 0x7ffe182be9b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5e06d3230 @ 386) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #17 0x5570afe1a160 i resource:///org/gnome/shell/ui/messageList.js:372 (0x7fd5e05b4670 @ 22) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #18 0x7ffe182bf600 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #19 0x5570afe1a0e8 i resource:///org/gnome/shell/ui/calendar.js:779 (0x7fd5e05aade0 @ 29) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #20 0x7ffe182c0910 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5e06d3230 @ 386) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #21 0x5570afe1a058 i resource:///org/gnome/shell/ui/messageTray.js:487 (0x7fd5e059dc48 @ 50) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #22 0x7ffe182c1570 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #23 0x5570afe19fc0 i
[Desktop-packages] [Bug 1769392] [NEW] BUG: networkmanager not able to disable IPv6 on OpenVPN Tap interface
Public bug reported: The system is configured to connect to an OpenVPN server set-up with tap bridging. On the remote server radvd is running on the bridged interface, in assisted set-up mode. radvd advertises a ULA prefix (assisted with DHCPv6) and a GUA prefix (slaac only) The remote-server is set-up to push def1 gateway by default. On the client 2 profiles are created; one with the intention of routing all traffic through the VPN, one with the intention of only accessing remote network sources. For the secondary profile IPv4 address assignment is left on automatic, route on manual with a static route configured for 10.0.0.0/8 through 10.0.1.1, the checkbox 'use network only for resources on its network' is ticked. For IPv6 every permutation of settings has been tried, none result in no IPv6 addresses and associated routes getting assigned. Even setting the IPv6 address assignment to Disabled still results in RA addresses getting assigned. Setting assignment to 'Disabled' /must/ remove the link local address on the tap interface, automatically failing any autoconf (RA autoconf depends on link local multicast) Setting assignment to 'Link-Local only' /must/ leave the ll address intact, while disabling autoconf (perhaps via sysctl) Ideally (low priority) an extra variant setting would be introduced that disallows GUA addressing to be assigned, but allows ULA addressing to be assigned. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 21:25:43 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-18 (47 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1769392 Title: BUG: networkmanager not able to disable IPv6 on OpenVPN Tap interface Status in network-manager-openvpn package in Ubuntu: New Bug description: The system is configured to connect to an OpenVPN server set-up with tap bridging. On the remote server radvd is running on the bridged interface, in assisted set-up mode. radvd advertises a ULA prefix (assisted with DHCPv6) and a GUA prefix (slaac only) The remote-server is set-up to push def1 gateway by default. On the client 2 profiles are created; one with the intention of routing all traffic through the VPN, one with the intention of only accessing remote network sources. For the secondary profile IPv4 address assignment is left on automatic, route on manual with a static route configured for 10.0.0.0/8 through 10.0.1.1, the checkbox 'use network only for resources on its network' is ticked. For IPv6 every permutation of settings has been tried, none result in no IPv6 addresses and associated routes getting assigned. Even setting the IPv6 address assignment to Disabled still results in RA addresses getting assigned. Setting assignment to 'Disabled' /must/ remove the link local address on the tap interface, automatically failing any autoconf (RA autoconf depends on link local multicast) Setting assignment to 'Link-Local only' /must/ leave the ll address intact, while disabling autoconf (perhaps via sysctl) Ideally (low priority) an extra variant setting would be introduced that disallows GUA addressing to be assigned, but allows ULA addressing to be assigned. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 21:25:43 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-18 (47 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769392/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
It's 2015 now, we are /4/ months further and /NO/ fix has been ported into the right channels. This is a big shame and it shows the utter lack of quality control in Canonical pushing releases -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Any news on a fix ?!? this is critical, not being able to use WINE in a deployment setting is a big NO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in “boinc” package in Ubuntu: Fix Released Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Status in “nvidia-cuda-toolkit” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-310-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-313-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pycuda” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “starpu-contrib” package in Ubuntu: Fix Released Status in “viennacl” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1380651] [NEW] Shotwell, unable to set as desktop slideshow, GLIB errors
Public bug reported: Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 shotwell: Installed: 0.20.1-0ubuntu1 Candidate: 0.20.1-0ubuntu1 Version table: *** 0.20.1-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To replicate: -launch shotwell from terminal (to see output) -import images into shotwell -drag select images -file-'Set as Desktop slideshow' -nothing happens, except terminal output (pasted below) Expected behaviour: -window spans asking to select settings Errors spawned on terminal: gijs@gijs-desktop:~$ shotwell (shotwell:19613): Gtk-CRITICAL **: gtk_window_set_type_hint: assertion 'GTK_IS_WINDOW (window)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_widget_set_parent_window: assertion 'GTK_IS_WIDGET (widget)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_window_set_transient_for: assertion 'GTK_IS_WINDOW (window)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_dialog_set_default_response: assertion 'GTK_IS_DIALOG (dialog)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (shotwell:19613): GLib-GObject-WARNING **: invalid (NULL) pointer instance (shotwell:19613): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (shotwell:19613): GLib-GObject-WARNING **: invalid (NULL) pointer instance (shotwell:19613): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (shotwell:19613): GLib-GObject-WARNING **: invalid (NULL) pointer instance (shotwell:19613): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_range_get_adjustment: assertion 'GTK_IS_RANGE (range)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_adjustment_set_value: assertion 'GTK_IS_ADJUSTMENT (adjustment)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_widget_show_all: assertion 'GTK_IS_WIDGET (widget)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_dialog_run: assertion 'GTK_IS_DIALOG (dialog)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: shotwell 0.20.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 13 16:18:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-13 (153 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: shotwell UpgradeStatus: Upgraded to utopic on 2014-10-06 (6 days ago) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1380651 Title: Shotwell, unable to set as desktop slideshow, GLIB errors Status in “shotwell” package in Ubuntu: New Bug description: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 shotwell: Installed: 0.20.1-0ubuntu1 Candidate: 0.20.1-0ubuntu1 Version table: *** 0.20.1-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To replicate: -launch shotwell from terminal (to see output) -import images into shotwell -drag select images -file-'Set as Desktop slideshow' -nothing happens, except terminal output (pasted below) Expected behaviour: -window spans asking to select settings Errors spawned on terminal: gijs@gijs-desktop:~$ shotwell (shotwell:19613): Gtk-CRITICAL **: gtk_window_set_type_hint: assertion 'GTK_IS_WINDOW (window)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_widget_set_parent_window: assertion 'GTK_IS_WIDGET (widget)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_window_set_transient_for: assertion 'GTK_IS_WINDOW (window)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_dialog_set_default_response: assertion 'GTK_IS_DIALOG (dialog)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (shotwell:19613): GLib-GObject-WARNING **: invalid (NULL) pointer instance (shotwell:19613): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (shotwell:19613): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (shotwell:19613): GLib-GObject-WARNING **:
