[Desktop-packages] [Bug 1877038]
Any updates on the estimated completion date on this P1 item? This bug has been open for 4 years (since 2/25/2019) and impacting customers from raising the security bar to migrate to FIDO2 security keys; ultimately driving millions of users AWAY from using Firefox. Google Chrome, Microsoft Edge, and Safari support FIDO2 for years now. Also, U2F is a deprecated API and major security token providers only sell FIDO2 tokens. Currently, Firefox only supports U2F on Mac and Linux, and with that, this is a critical security blocker. On a different note, can someone from Mozilla provide a knowledge transfer so that we understand the blocker and the remaining work? Is there a feature branch we can test FIDO2 in Firefox on Mac and Linux? I'm curious to know the current state of the FIDO2 support in Firefox. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 381017]
Ubuntu 20.04 Thunderbird 102.2.2 Thunar 4.16.10 Not work. Location specified is not compatible. -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 1877038]
Greeting, any progress on this bug? If you have a branch, I can help review and collaborate on the feature. Please provide the blockers and estimated completion date. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
I've updated the MR on the freedesktop gitlab instance. Olivier, it
might be worth updating again with a new SRU to include Elvis' further
patch?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1877038]
Thanks for the update and suggestion. Can we prioritize this item? It has a large impact on 2 major tech companies. Also, do you have an estimated completion date when FIDO2 will be available on Mac and Linux? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1980933] Re: Blanked screen doesn't wake up after put into powersave
Out of the system journal I think these are the smoking guns: Jul 06 23:14:20 Excelsior kernel: INFO: task firefox:cs0:6721 blocked for more than 120 seconds. Jul 06 23:14:20 Excelsior kernel: Tainted: P C O 5.15.0-40-generic #43-Ubuntu Jul 06 23:14:20 Excelsior kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 06 23:14:20 Excelsior kernel: task:firefox:cs0 state:D stack:0 pid: 6721 ppid: 3462 flags:0x0220 Jul 06 23:14:20 Excelsior kernel: Call Trace: Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: __schedule+0x23d/0x590 Jul 06 23:14:20 Excelsior kernel: schedule+0x4e/0xb0 Jul 06 23:14:20 Excelsior kernel: schedule_timeout+0xfb/0x140 Jul 06 23:14:20 Excelsior kernel: ? __wake_up_locked+0x16/0x20 Jul 06 23:14:20 Excelsior kernel: dma_fence_default_wait+0x1c4/0x1f0 Jul 06 23:14:20 Excelsior kernel: ? dma_fence_free+0x20/0x20 Jul 06 23:14:20 Excelsior kernel: dma_fence_wait_timeout+0xb7/0xd0 Jul 06 23:14:20 Excelsior kernel: gmc_v10_0_flush_gpu_tlb+0x285/0x310 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_gart_invalidate_tlb+0x43/0x60 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_ttm_alloc_gart+0x150/0x1a0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_cs_parser_bos+0x406/0x4e0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_ib_fill+0x1e3/0x230 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_cs_ioctl+0xf8/0x230 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_vm_handling+0x420/0x420 [amdgpu] Jul 06 23:14:20 Excelsior kernel: drm_ioctl_kernel+0xae/0xf0 [drm] Jul 06 23:14:20 Excelsior kernel: drm_ioctl+0x264/0x4b0 [drm] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_vm_handling+0x420/0x420 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? __seccomp_filter+0x4a/0x4a0 Jul 06 23:14:20 Excelsior kernel: amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Jul 06 23:14:20 Excelsior kernel: __x64_sys_ioctl+0x91/0xc0 Jul 06 23:14:20 Excelsior kernel: do_syscall_64+0x5c/0xc0 Jul 06 23:14:20 Excelsior kernel: ? exit_to_user_mode_prepare+0x92/0xb0 Jul 06 23:14:20 Excelsior kernel: ? syscall_exit_to_user_mode+0x27/0x50 Jul 06 23:14:20 Excelsior kernel: ? do_syscall_64+0x69/0xc0 Jul 06 23:14:20 Excelsior kernel: ? do_syscall_64+0x69/0xc0 Jul 06 23:14:20 Excelsior kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Jul 06 23:14:20 Excelsior kernel: RIP: 0033:0x7fa97fc3a3ab Jul 06 23:14:20 Excelsior kernel: RSP: 002b:7fa95f32fa18 EFLAGS: 0246 ORIG_RAX: 0010 Jul 06 23:14:20 Excelsior kernel: RAX: ffda RBX: 7fa95f32fa80 RCX: 7fa97fc3a3ab Jul 06 23:14:20 Excelsior kernel: RDX: 7fa95f32fa80 RSI: c0186444 RDI: 0026 Jul 06 23:14:20 Excelsior kernel: RBP: c0186444 R08: 7fa95f32fbb0 R09: 0020 Jul 06 23:14:20 Excelsior kernel: R10: 7fa95f32fbb0 R11: 0246 R12: 7fa969dd7e00 Jul 06 23:14:20 Excelsior kernel: R13: 0026 R14: R15: 7fa916022090 Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: INFO: task kworker/13:0:20618 blocked for more than 120 seconds. Jul 06 23:14:20 Excelsior kernel: Tainted: P C O 5.15.0-40-generic #43-Ubuntu Jul 06 23:14:20 Excelsior kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 06 23:14:20 Excelsior kernel: task:kworker/13:0state:D stack:0 pid:20618 ppid: 2 flags:0x4000 Jul 06 23:14:20 Excelsior kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] Jul 06 23:14:20 Excelsior kernel: Call Trace: Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: __schedule+0x23d/0x590 Jul 06 23:14:20 Excelsior kernel: schedule+0x4e/0xb0 Jul 06 23:14:20 Excelsior kernel: schedule_preempt_disabled+0xe/0x10 Jul 06 23:14:20 Excelsior kernel: __mutex_lock.constprop.0+0x263/0x490 Jul 06 23:14:20 Excelsior kernel: __mutex_lock_slowpath+0x13/0x20 Jul 06 23:14:20 Excelsior kernel: mutex_lock+0x34/0x40 Jul 06 23:14:20 Excelsior kernel: dm_suspend+0xaa/0x270 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? nv_common_set_clockgating_state+0x9f/0xb0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_device_set_cg_state+0x12f/0x280 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_ip_suspend_phase1+0xa3/0x180 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_ip_suspend+0x21/0x70 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_pre_asic_reset+0xdd/0x480 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? drm_fb_helper_set_suspend_unlocked+0x33/0xa0 [drm_kms_helper] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_gpu_recover.cold+0x6ec/0x8f8 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_job_timedout+0x14f/0x170 [amdgpu] Jul 06 23:14:20 Excelsior kernel: drm_sched_job_timedout+0x6f/0x110 [gpu_sched] Jul 06 23:14:20 Excelsior kernel: process_one_work+0x22b/0x3d0 Jul 06 23:14:20 Excelsior kernel: worker_thread+0x53/0x410 Jul
[Desktop-packages] [Bug 1980933] Re: Blanked screen doesn't wake up after put into powersave
** Attachment added: "output of journalctl --user --no-pager (XZipped to match the system journal)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+attachment/5601834/+files/user-journal.log.xz -- 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/1980933 Title: Blanked screen doesn't wake up after put into powersave Status in mutter package in Ubuntu: New Bug description: This is *similar* to #1968040 but I'm raising it as a separate issue as the workarounds there do not work for my system suggesting that this is indeed a separate bug. When allowing the system to blank the screen, it becomes impossible to awaken the screen some unknown length of time after DPMS poweroff is triggered. Neither the keyboard nor the mouse can be used to trigger the screens to power back on again once powered down by DPMS. My system is a custom-build desktop PC with a discrete AMD 6600XT GPU and two external 4k monitors. I have tried the workarounds in the above bug and neither worked. Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with ctrl+alt) does not bring the monitors back to life, and adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change the behaviour in any way. The system is still responsive to the network and I can SSH into the box to investigate when in this scenario. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 7 09:32:16 2022 InstallationDate: Installed on 2022-05-11 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+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 1980933] [NEW] Blanked screen doesn't wake up after put into powersave
Public bug reported: This is *similar* to #1968040 but I'm raising it as a separate issue as the workarounds there do not work for my system suggesting that this is indeed a separate bug. When allowing the system to blank the screen, it becomes impossible to awaken the screen some unknown length of time after DPMS poweroff is triggered. Neither the keyboard nor the mouse can be used to trigger the screens to power back on again once powered down by DPMS. My system is a custom-build desktop PC with a discrete AMD 6600XT GPU and two external 4k monitors. I have tried the workarounds in the above bug and neither worked. Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with ctrl+alt) does not bring the monitors back to life, and adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change the behaviour in any way. The system is still responsive to the network and I can SSH into the box to investigate when in this scenario. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 7 09:32:16 2022 InstallationDate: Installed on 2022-05-11 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "output of journalctl --system --no-pager (XZipped due to being huge - ~900MB)" https://bugs.launchpad.net/bugs/1980933/+attachment/5601831/+files/system-journal.log.xz -- 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/1980933 Title: Blanked screen doesn't wake up after put into powersave Status in mutter package in Ubuntu: New Bug description: This is *similar* to #1968040 but I'm raising it as a separate issue as the workarounds there do not work for my system suggesting that this is indeed a separate bug. When allowing the system to blank the screen, it becomes impossible to awaken the screen some unknown length of time after DPMS poweroff is triggered. Neither the keyboard nor the mouse can be used to trigger the screens to power back on again once powered down by DPMS. My system is a custom-build desktop PC with a discrete AMD 6600XT GPU and two external 4k monitors. I have tried the workarounds in the above bug and neither worked. Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with ctrl+alt) does not bring the monitors back to life, and adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change the behaviour in any way. The system is still responsive to the network and I can SSH into the box to investigate when in this scenario. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 7 09:32:16 2022 InstallationDate: Installed on 2022-05-11 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
Yamiyukisenpai, that is working correctly. The error message does not
impact the functionality of the program. It is merely ugly. There is a
patch upstream that fixes this, but it isn't appropriate to SRU this
fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
I've updated the PR with a fix for this ugly message
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
Unknown
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Committed
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample]
** Tags added: jammy ** Tags added: xorg-session -- 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/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Fresh install of Artful, using gnome-session to access vanilla GNOME session on Wayland (also tried on xorg). Attempting to calibrate monitors through Gnome Control Center->Devices->Color. All attempts ended at the point where I was asked to put the device onto the monitor, with the error: Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device. Syslog: Sep 24 12:19:31 desktop kernel: [ 262.849675] usb 3-6: new full-speed USB device number 7 using xhci_hcd Sep 24 12:19:32 desktop kernel: [ 262.990880] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:19:32 desktop kernel: [ 262.990882] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:19:32 desktop kernel: [ 262.990884] usb 3-6: Product: colormunki Sep 24 12:19:32 desktop kernel: [ 262.990885] usb 3-6: Manufacturer: X-Rite Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop gnome-shell[876]: drmModeSetCursor2 failed with (Permission denied), drawing cursor with OpenGL from now on Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) I attempted to fix the permissions error for /dev/dri/card0. Current permissions: rwh@desktop:~$ ls -l /dev/dri/card0 crw-rw+ 1 root video 226, 0 Sep 24 12:15 /dev/dri/card0 Tried adding my user to video group, which made no difference. Then made file world r/w: rwh@desktop:~$ sudo chmod o+rw /dev/dri/card0 Which fixed that problem. Now, in the calibrate wizard, on the second step (Display Type) I am offered three options (LCD, CRT, Projector) where I only saw LCD previously. However, the calibration step failed the same as before. Syslog: Sep 24 12:36:46 desktop kernel: [ 1298.430546] usb 3-6: new full-speed USB device number 12 using xhci_hcd Sep 24 12:36:46 desktop kernel: [ 1298.571756] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:36:46 desktop kernel: [ 1298.571759] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:36:46 desktop kernel: [ 1298.571760] usb 3-6: Product: colormunki Sep 24 12:36:46 desktop kernel: [ 1298.571762] usb 3-6: Manufacturer: X-Rite Sep 24 12:36:46 desktop pulseaudio[953]: message repeated 3 times: [ W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Sep 24 12:36:47 desktop gnome-control-c[5206]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:36:47 desktop gnome-control-c[5206]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:37:21 desktop dbus-daemon[4121]: Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' Sep 24 12:37:21 desktop systemd[3601]: Starting Color management helper... Sep 24 12:37:21 desktop dbus-daemon[4121]: Successfully activated service 'org.freedesktop.ColorHelper' Sep 24 12:37:21 desktop systemd[3601]: Started Color management helper. Sep 24 12:37:21 desktop
[Desktop-packages] [Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
** Also affects: xdg-utils via
https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/10
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
Unknown
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
Why in stock Ubuntu and not Kubuntu, I think is because the offending
code is inside functions that are named as though only KDE is supposed
to use them. For example, the default browser break is inside a function
named `check_browser_kde()`. There might be some logic to determine that
your stock Ubuntu, even if it is currently running a KDE session,
supports testing via the gnome code paths: i.e. via
`check_browser_gnome()`
With regards to bash specifics inside a project declaring /bin/sh as the
interpreter I would guess it is a bug that has crept through without
being caught. The upstream project likely wants to remain portable and
not rely on BASH so they probably should drop the BASH-isms.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in kubuntu-meta package in Ubuntu:
New
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1970594/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
There is also a similar statement that needs fixing for DASH on line
1090:
if [ x"!" == x"${binary:0:1}" ]; then
** Changed in: xdg-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in kubuntu-meta package in Ubuntu:
New
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1970594/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
Can you try replacing the line with:
if [ x"!" == x"$(printf %.1s "$browser")" ]; then
and reverting back to dash? I think this might work in most posix
shells, without requiring to move to bash.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in kubuntu-meta package in Ubuntu:
New
Status in xdg-utils package in Ubuntu:
New
Bug description:
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1970594/+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 1946499] Re: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all
Brian, I've filled out the SRU template. ** Summary changed: - installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed + SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
The localisation changes were adjusting the translation files to match the line numbers of the amended python source code. It was picked up accidentally by my compiling in the checked-out source when testing the fix - the compile generated new templates with the change. There are zero changes made to the strings themselves, only the line numbers used to generate the templates changed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
For Norbert, this is the same debdiff without the localisation changes ** Patch added: "gdebi-no-ubuntu-specfics.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1946499/+attachment/5532985/+files/gdebi-no-ubuntu-specfics.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
https://launchpad.net/~diddledani/+archive/ubuntu/gdebi- fix-1946499/+packages contains my patch above (the debdiff of gdebi) for reference once it's built by LP. I agree that downgrading VTE is not gonna fly. We might be able to convince SRU managers to rebuild without the patch now it's not needed, but won't convince them on an outright downgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
With this patch we can drop the 91_keep_fds.patch in vte -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
Identical to patch added to #1756238. ** Patch added: "Patch to drop ubuntu-specific hack from gdebi because it is not needed any more" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1946499/+attachment/5532964/+files/gdebi-no-ubuntu-specfics.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
@Marco Trevisan (@3v1n0) With this change, the 91_keep_fds.patch in vte can be dropped -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
** Patch added: "Patch to drop ubuntu-specific hack from gdebi because it is not needed any more" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+attachment/5532963/+files/gdebi-no-ubuntu-specfics.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 381017]
(In reply to Martin Stránský [:stransky] (ni? me) from comment #104) > I can reproduce it with TB91. +1 -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 508220] Re: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic
This issue is for Lucid Lynx, which reached EOL in 2013 for desktop packages. I vote we close this issue as WONTFIX (I don't have permission to set WONTFIX status on this issue). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/508220 Title: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic Status in gtk+2.0 package in Ubuntu: New Status in synaptic package in Ubuntu: Fix Released Bug description: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line (e.g. Preparing blahpackage0-dev) are italic, while the rest of the characters are not. This isn't a major issue, and is purely cosmetic. Screenshots: http://azabani.com/images/lucid-synaptic-italic-1 http://azabani.com/images/lucid-synaptic-italic-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/508220/+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 1917705] Re: "profile will be deleted" at startup after chromium 89 update
I am a happy user of the Ubuntu systems "account online" service happy, so far I think .. or maybe not now?!? it makes me think that between now and March 15 we could all be left on foot ... but what is Google? Did she start strangling her babies one after another? -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
I don't know if this can help, but for me, the fail only happens after login and then I never see it again. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: 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 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 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/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed
I'm running mutter version 3.36.3-0ubuntu0.20.04.1 but I still have the same problem. -- 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/1877075 Title: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [Impact] This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's duplicated across multiple problem reports according to locale: https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7 https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0 [Test Case] None known. The plan is to just continue monitoring crash reports. Still, we are confident this is the fix because: * The offending source code in libx11 tells us it is :) and * The crash only started in Ubuntu with gnome-shell 3.34, which is the exact release in which XInitThreads was removed from mutter. [Regression Potential] Low. We add a single function call that tells libX11 to enable thread safety. This is the same as what we had in bionic, cosmic and disco, so it's well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1877075/+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 1882524] [NEW] [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem
Public bug reported: i have no audio from speakers in my laptop but i have audio output on hdmi. i have another harddrive with windows 7 on it and the speakers work correctly on that. they used to work on this distro Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dani 1677 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 12:59:05 2020 InstallationDate: Installed on 2020-03-24 (75 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago) dmi.bios.date: 05/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.00L15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CF53-1 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.00L15:bd05/25/2012:svnPanasonicCorporation:pnCF-53DA502FW:pvr001:rvnPanasonicCorporation:rnCF53-1:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF53-1 dmi.product.name: CF-53DA502FW dmi.product.sku: CF-53DA502FW dmi.product.version: 001 dmi.sys.vendor: Panasonic Corporation ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1882524 Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: i have no audio from speakers in my laptop but i have audio output on hdmi. i have another harddrive with windows 7 on it and the speakers work correctly on that. they used to work on this distro Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dani 1677 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 12:59:05 2020 InstallationDate: Installed on 2020-03-24 (75 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago) dmi.bios.date: 05/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.00L15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CF53-1 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.00L15:bd05/25/2012:svnPanasonicCorporation:pnCF-53DA502FW:pvr001:rvnPanasonicCorporation:rnCF53-1:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF53-1 dmi.product.name: CF-53DA502FW dmi.product.sku: CF-53DA502FW dmi.product.version: 001 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882524/+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 1879615] [NEW] headset microphone not working
Public bug reported: I can here sound in my bluetooth headsets (I tried several) but I cannot make the microphone work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 07:29:30 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-13 (188 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic root=UUID=a07ae209-275c-4c8b-985d-ba52e5f7f214 ro quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-13 (6 days ago) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:1D:96:DA:9E:12 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:130281 acl:173 sco:0 events:15048 errors:0 TX bytes:4105451 acl:5549 sco:12 commands:8979 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/1879615 Title: headset microphone not working Status in bluez package in Ubuntu: New Bug description: I can here sound in my bluetooth headsets (I tried several) but I cannot make the microphone work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 07:29:30 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-13 (188 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic root=UUID=a07ae209-275c-4c8b-985d-ba52e5f7f214 ro quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-13 (6 days ago) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:1D:96:DA:9E:12 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:130281 acl:173 sco:0 events:15048 errors:0 TX bytes:4105451 acl:5549 sco:12 commands:8979 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879615/+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 381017]
That would be great... +1 -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]
The same: Also I have found this bug with: - Thunderbird 52.9.0 - Thunar 1.6.11 (the package depends on libgtk2.0-0 package) - Debian 9.4 - Xfce 4.12 -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]
+1 Romano Giannetti Suggestion: ditch the thing completely. Remove drag and drop. For good. -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 1854486] [NEW] cannot build with jhbuild due to libxml2
Public bug reported: I have ubuntu 19.10 If I do: jhbuild build yelp-xsl I get "ModuleNotFoundError: No module named 'libxml2' thanks itstool -o "yelp-xsl.xml" -j "/home/dani/jhbuild/checkout/yelp-xsl/xslt/common/domains/yelp-xsl.xml.in" af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo; \ rm af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo) Traceback (most recent call last): File "/usr/bin/itstool", line 27, in import libxml2 ModuleNotFoundError: No module named 'libxml2' ** Affects: yelp-xsl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp-xsl in Ubuntu. https://bugs.launchpad.net/bugs/1854486 Title: cannot build with jhbuild due to libxml2 Status in yelp-xsl package in Ubuntu: New Bug description: I have ubuntu 19.10 If I do: jhbuild build yelp-xsl I get "ModuleNotFoundError: No module named 'libxml2' thanks itstool -o "yelp-xsl.xml" -j "/home/dani/jhbuild/checkout/yelp-xsl/xslt/common/domains/yelp-xsl.xml.in" af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo; \ rm af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo) Traceback (most recent call last): File "/usr/bin/itstool", line 27, in import libxml2 ModuleNotFoundError: No module named 'libxml2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp-xsl/+bug/1854486/+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 1685439] Re: Firefox 53 conflicts with window manager theme
Confirm: It affects Ubuntu 14.05 with GNOME.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1685439 Title: Firefox 53 conflicts with window manager theme Status in firefox package in Ubuntu: Confirmed Bug description: Firefox overrides the default window manager font color in some of its pop up dialog and buttons (included buttons rendered in webpages) This leads to unreadable buttons text. See the top of the attached Screenshot1.png for an example: The "Quit" "Save" "Save and Quit" text is white (should be black). Hovering over the "Do no ask next time" also turns that text white. Problem appeared after update of firefox:amd64 (from 52.0.2+build1-0ubuntu0.14.04.1 to 53.0+build6-0ubuntu0.14.04.1). Using the default Firefox theme or the other 2 new "compact" provided themes produces the same result. On Xubuntu 14.04 with XFCE 4.10 In the snapshot above the XFCE theme is the standard "Adwaita" but the problem can be reproduced with other themes thought it is not present for example with the similar XFCE theme "Orion". Changing the XFCE theme back and forth when firefox is open sometimes "fixes" the issue until Firefox is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1685439/+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 1496542] Re: Running processes left after disabling screen reader
Hello: Same problem on xubuntu 16.04 $ ps xa | grep -P 'speech-dispatcher.*\.conf' 22217 ?Sl 0:02 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 1 ?Sl 0:02 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 4 ?Sl 0:03 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 9 ?Sl 0:02 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 27986 pts/2S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf Never used the screen reader. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader Status in speech-dispatcher package in Ubuntu: Triaged Bug description: After I disabled my screen reader, I noticed that when running "ps xa | grep -P 'speech-dispatcher.*\.conf'" I get: 17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf So it seems as though it left some running processes behind after I disabled it. I have also attached a screenshot of my Sound settings which show that they are still running (Sound_Application_List2.png). --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: speech-dispatcher: Installed: 0.8.1-0ubuntu1 Candidate: 0.8.1-0ubuntu1 Version table: *** 0.8.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: speech-dispatcher 0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 16 20:27:00 2015 InstallationDate: Installed on 2015-07-29 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
anything new on this? =( -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1445530] [NEW] internet connection
Public bug reported: my wifi modem work perfect on ubuntu 10.04, 10.10 but very poor on ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 14 10:49:39 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98M [GeForce G 103M] [10de:06ef] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:306a] InstallationDate: Installed on 2015-03-09 (35 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=b7446113-11d8-4dc2-8467-b4470ee45d9a ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 306A dmi.board.vendor: Quanta dmi.board.version: 21.10 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.08:bd07/16/2009:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn306A:rvr21.10:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 14 10:27:32 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1445530 Title: internet connection Status in xorg package in Ubuntu: New Bug description: my wifi modem work perfect on ubuntu 10.04, 10.10 but very poor on ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 14 10:49:39 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98M [GeForce G 103M] [10de:06ef] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:306a] InstallationDate: Installed on 2015-03-09 (35 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=b7446113-11d8-4dc2-8467-b4470ee45d9a ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 306A dmi.board.vendor: Quanta dmi.board.version: 21.10 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.08:bd07/16/2009:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn306A:rvr21.10:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
[Desktop-packages] [Bug 1396081] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
Public bug reported: Hi, I dont' now if it's related, but the clikkig of mouse detect more than 1 clik when I clik, about 2-5 clik, and the default font now have a smoot effect. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 03:54:04 2014 InstallationDate: Installed on 2014-10-16 (39 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-28 (27 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1396081 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Hi, I dont' now if it's related, but the clikkig of mouse detect more than 1 clik when I clik, about 2-5 clik, and the default font now have a smoot effect. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 03:54:04 2014 InstallationDate: Installed on 2014-10-16 (39 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-28 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1396081/+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 500947] Re: Brasero won't burn Dvd
4.7 Gb ( if i understand you question) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/500947 Title: Brasero won't burn Dvd Status in “brasero” package in Ubuntu: Incomplete Bug description: Binary package hint: brasero When I try and burn any type of file (Iso, MPEG, AVI) in Brasero, i get an error that says Please replace the disc with a supported CD or DVD It is not possible to write with the current set of plugins I'm using DVD+R, which should be supported (i think), and i can't seem to find a plugin stating that it pertains to that error, nor can i find one online to fix it. I am completely new to Ubuntu and Linux in General, so... 'nuff said ProblemType: Bug Architecture: i386 Date: Sun Dec 27 23:41:21 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: brasero 2.28.2-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: brasero Uname: Linux 2.6.31-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/500947/+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 500947] Re: Brasero won't burn Dvd
thankx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/500947 Title: Brasero won't burn Dvd Status in “brasero” package in Ubuntu: Incomplete Bug description: Binary package hint: brasero When I try and burn any type of file (Iso, MPEG, AVI) in Brasero, i get an error that says Please replace the disc with a supported CD or DVD It is not possible to write with the current set of plugins I'm using DVD+R, which should be supported (i think), and i can't seem to find a plugin stating that it pertains to that error, nor can i find one online to fix it. I am completely new to Ubuntu and Linux in General, so... 'nuff said ProblemType: Bug Architecture: i386 Date: Sun Dec 27 23:41:21 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: brasero 2.28.2-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: brasero Uname: Linux 2.6.31-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/500947/+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 500947] Re: Brasero won't burn Dvd
BraseroLibburn SCSI error condition on command 2Ah WRITE(10): [3 0C 00] Write error BraseroLibburn called brasero_job_get_session_output_size BraseroLibburn called brasero_job_set_current_action BraseroLibburn Libburn reported an error SCSI error on write(32,16): [3 0C 00] Write error BraseroLibburn called brasero_job_error BraseroLibburn finished with an error BraseroLibburn asked to stop because of an error error = 1 message = SCSI error on write(32,16): [3 0C 00] Write error BraseroLibisofs stopping BraseroLibisofs Getting out thread BraseroLibisofs disconnecting BraseroLibisofs from BraseroChecksumImage BraseroChecksumImage stopping BraseroChecksumImage disconnecting BraseroChecksumImage from BraseroLibburn BraseroChecksumImage closing connection for BraseroChecksumImage BraseroLibburn stopping BraseroLibburn closing connection for BraseroLibburn Session error : SCSI error on write(32,16): [3 0C 00] Write error (brasero_burn_record brasero-burn.c:2856) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/500947 Title: Brasero won't burn Dvd Status in “brasero” package in Ubuntu: Incomplete Bug description: Binary package hint: brasero When I try and burn any type of file (Iso, MPEG, AVI) in Brasero, i get an error that says Please replace the disc with a supported CD or DVD It is not possible to write with the current set of plugins I'm using DVD+R, which should be supported (i think), and i can't seem to find a plugin stating that it pertains to that error, nor can i find one online to fix it. I am completely new to Ubuntu and Linux in General, so... 'nuff said ProblemType: Bug Architecture: i386 Date: Sun Dec 27 23:41:21 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: brasero 2.28.2-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: brasero Uname: Linux 2.6.31-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/500947/+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 1183780] [NEW] Sound app does not list an option for my on-board analogue 2-speaker sound
Public bug reported: Ubuntu 12.10 The sound stopped working after a software update. So did the nVidia driver, but I am getting used to having to rejigger the driver at random points. This is the first time that the sound stopped working, and now a Dummy sound thing has shown up. Check out what the sound dialog looks like here if the attachment goes through: http://daniepstein.com/daniepstein/wp-content/uploads/2013/05/sound-dialog.jpg ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-31.52-generic 3.5.7.11 Uname: Linux 3.5.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dani 4398 F pulseaudio /dev/snd/controlC2: dani 4398 F pulseaudio /dev/snd/controlC0: dani 4398 F pulseaudio /dev/snd/controlC1: dani 4398 F pulseaudio Date: Fri May 24 11:51:50 2013 InstallationDate: Installed on 2013-05-08 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_AlsaPlaybackTestStderr: A L S A l i b p c m _ h w . c : 1 4 0 1 : ( _ s n d _ p c m _ h w _ o p e n ) I n v a l i d v a l u e f o r c a r d Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dani 4398 F pulseaudio /dev/snd/controlC2: dani 4398 F pulseaudio /dev/snd/controlC0: dani 4398 F pulseaudio /dev/snd/controlC1: dani 4398 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r a t t a c h h w : I n t e l e r r o r : N o s u c h d e v i c e Title: [P5K-E, Analog Devices AD1988B, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd12/10/2007:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity ** Attachment added: Screen grab of sound panel https://bugs.launchpad.net/bugs/1183780/+attachment/3685571/+files/sound%20dialog.jpg -- 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/1183780 Title: Sound app does not list an option for my on-board analogue 2-speaker sound Status in “alsa-driver” package in Ubuntu: New Bug description: Ubuntu 12.10 The sound stopped working after a software update. So did the nVidia driver, but I am getting used to having to rejigger the driver at random points. This is the first time that the sound stopped working, and now a Dummy sound thing has shown up. Check out what the sound dialog looks like here if the attachment goes through: http://daniepstein.com/daniepstein/wp-content/uploads/2013/05/sound-dialog.jpg ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-31.52-generic 3.5.7.11 Uname: Linux 3.5.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dani 4398 F pulseaudio /dev/snd/controlC2: dani 4398 F pulseaudio /dev/snd/controlC0: dani 4398 F pulseaudio /dev/snd/controlC1: dani 4398 F pulseaudio Date: Fri May 24 11:51:50 2013 InstallationDate: Installed on 2013-05-08 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_AlsaPlaybackTestStderr: A L S A l i b p c m _ h w . c : 1 4 0 1 : ( _ s n d _ p c m _ h w _ o p e n ) I n v a l i d v a l u e f o r c a r d Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dani
Re: [Desktop-packages] [Bug 1183780] Re: Sound app does not list an option for my on-board analogue 2-speaker sound
Very much appreciated. This is quite embarrassing, but a reboot solved the problem. I think I jumped the gun because the various suggestions I tried got simply refused to work. Everything seemed to show up OK, but still no sound. Ah well, I have learned my lesson. In my defence, however, this is very un-Linux behaviour! On Fri, May 24, 2013 at 3:10 PM, Raymond 1183...@bugs.launchpad.net wrote: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS try latest alsa driver which has support of Jack detection for ad1988 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1183780 Title: Sound app does not list an option for my on-board analogue 2-speaker sound Status in “alsa-driver” package in Ubuntu: New Bug description: Ubuntu 12.10 The sound stopped working after a software update. So did the nVidia driver, but I am getting used to having to rejigger the driver at random points. This is the first time that the sound stopped working, and now a Dummy sound thing has shown up. Check out what the sound dialog looks like here if the attachment goes through: http://daniepstein.com/daniepstein/wp-content/uploads/2013/05/sound-dialog.jpg ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-31.52-generic 3.5.7.11 Uname: Linux 3.5.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dani 4398 F pulseaudio /dev/snd/controlC2: dani 4398 F pulseaudio /dev/snd/controlC0: dani 4398 F pulseaudio /dev/snd/controlC1: dani 4398 F pulseaudio Date: Fri May 24 11:51:50 2013 InstallationDate: Installed on 2013-05-08 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_AlsaPlaybackTestStderr: A L S A l i b p c m _ h w . c : 1 4 0 1 : ( _ s n d _ p c m _ h w _ o p e n ) I n v a l i d v a l u e f o r c a r d Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dani 4398 F pulseaudio /dev/snd/controlC2: dani 4398 F pulseaudio /dev/snd/controlC0: dani 4398 F pulseaudio /dev/snd/controlC1: dani 4398 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r a t t a c h h w : I n t e l e r r o r : N o s u c h d e v i c e Title: [P5K-E, Analog Devices AD1988B, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd12/10/2007:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1183780/+subscriptions -- 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/1183780 Title: Sound app does not list an option for my on-board analogue 2-speaker sound Status in “alsa-driver” package in Ubuntu: New Bug description: Ubuntu 12.10 The sound stopped working after a software update. So did the nVidia driver, but I am getting used to having to rejigger the driver at random points. This is the first time that the sound stopped working, and now a Dummy sound thing has shown up. Check out what the sound dialog looks like here if the attachment goes through: http://daniepstein.com/daniepstein/wp-content/uploads/2013/05/sound-dialog.jpg ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-31.52-generic 3.5.7.11 Uname: Linux 3.5.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dani
[Desktop-packages] [Bug 1087739] Re: Promoting/demoting items in a bulleted list not working in Impress
In my case I can reproduce when importing a .ppt file. I can attach if it helps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1087739 Title: Promoting/demoting items in a bulleted list not working in Impress Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: On Ubuntu 12.10 64 bit: - create a new empty presentation with Impress - create a bulleted list with a few items - demote or promote an item by pressing the relative buttons in the toolbar, or using the the keyboard shortcuts (ALT+SHIFT+LEFT, ALT+SHIFT+RIGHT) Expected behavior: the item gets promoted or demoted What happens instead: nothing, the buttons in the toolbar appear disabled --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2012-06-13 (177 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) MarkForUpload: True Package: libreoffice 1:3.6.2~rc2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: Upgraded to quantal on 2012-10-30 (38 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1087739/+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 1087739] Re: Promoting/demoting items in a bulleted list not working in Impress
Sorry for my boldness, but imho, this is the most basic functionality of a presentations application, and it does not work in LibreOffice 3.x nor 4.0.2.2 Is there at least a workaround? I have ubuntu 12.4 32 bit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1087739 Title: Promoting/demoting items in a bulleted list not working in Impress Status in “libreoffice” package in Ubuntu: Confirmed Bug description: On Ubuntu 12.10 64 bit: - create a new empty presentation with Impress - create a bulleted list with a few items - demote or promote an item by pressing the relative buttons in the toolbar, or using the the keyboard shortcuts (ALT+SHIFT+LEFT, ALT+SHIFT+RIGHT) Expected behavior: the item gets promoted or demoted What happens instead: nothing, the buttons in the toolbar appear disabled --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2012-06-13 (177 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) MarkForUpload: True Package: libreoffice 1:3.6.2~rc2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: Upgraded to quantal on 2012-10-30 (38 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1087739/+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 1011473] Re: Please update to latest libsoup 2.39.2
I'd also like to build latest webkit with Ubuntu 12.4, but libsoup2.39.2 does not compile because it needs GLIB 2.33.1 Is there any workaround? thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1011473 Title: Please update to latest libsoup 2.39.2 Status in Webkit Direct Port: Fix Released Status in “libsoup2.4” package in Ubuntu: Fix Released Status in “webkit” package in Ubuntu: Fix Released Bug description: i'm a midori user, and continously get this error logged, as it flooding xsession-errors: (midori:5132): libsoup-WARNING **: (soup- uri.c:1023):soup_uri_set_path: runtime check failed: (path != NULL) Quantal package is 2.38-1.2 , but the 2.39 serie exist and have many fixes: http://ftp.acc.umu.se/pub/gnome/sources/libsoup/2.39/ http://ftp.acc.umu.se/pub/gnome/sources/libsoup/2.39/libsoup-2.39.1.news http://ftp.acc.umu.se/pub/gnome/sources/libsoup/2.39/libsoup-2.39.2.news so hopes to see this new release packaged asap. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libsoup2.4-1 2.38.1-2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.1.1-0ubuntu2 Architecture: i386 Date: Mon Jun 11 10:17:18 2012 SourcePackage: libsoup2.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1011473/+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
